I'm glad to hear that the problem between your SMTP gateway and our SMTP servers has corrected itself...   To be clear, SMTP transport for AutoSupport to NetApp is still supported. It's just not the recommended choice.   See this technical report: Data ONTAP AutoSupport and On Demand Configuration   HTTPS   HTTPS uses TCP port 443. This protocol is the default transport protocol. This protocol supports AutoSupport On Demand and uploads of large files.   When AutoSupport messages are sent using HTTPS, the X.509 certificate of the NetApp AutoSupport server is validated, and the message content is encrypted.   NetApp strongly recommends using HTTPS transport for AutoSupport delivery for the following reasons:   HTTPS transport is significantly more secure and reliable than SMTP HTTPS is not restricted by SMTP e-mail size constraints HTTPS is easy to configure and manage HTTPS transport can be used along with SMTP delivery to internal customer personnel or systems HTTPS enables integrated AutoSupport On Demand capability to expedite case resolution ... View more

Robinpeter's suggestion was excellent - you can completely avoid SMTP issues by switching to HTTPS and all of the benefits that come with that transport protocol.   If you still need to resolve the SMTP issue, please contact NetApp via the Feedback Form on the NetApp Support Site. (select Category: AutoSupport and Sub Category: Other). Provide all of the necessary details about your SMTP relays, domain name, and ideally - detailed transaction logs. ... View more

The disks should automatically be partitioned once they are assigned to the system. Even if that doesn't happen, a whole spare disk will be automatically partitioned when it's added to an aggregate. ... View more

The "use both" feature should be supported on any platform that has both Flash Cache and Flash Pools - it's platform agnostic.   Again, if this doesn't appear to be working, I'd open a case to investigate. ... View more

Actually, you should view and modify the external cache options via clustershell, instead.   system node external-cache show   Check that -is-hya-enabled  is true.   system node external-cache modify, if necessary.   Ref: man page ... View more

@Matt99   Have you opened a case with NetApp Support concerning this?   Verify your flexscale options on these nodes.   ::> node run -node <name> options flexscale   In particular, verify that flexscale.flash_pool_caching is on.   (and make sure it's enabled, rewarm is on, etc.) ... View more

That's the right KB...   root-data-data = 3 partitions.   Only AFF systems running 9.0+ are supported for root-data-data partitioning. ... View more

I  noticed that this is an IBM N-series variant - you'd need to work with IBM Support.   That said, take a look at this public report for Bug 245162. It has some guidance (e.g. reseat the module) "CEMI Micro controller Fatal Error" leads to loss of access to AT-FCX module http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=245162 ... View more

Almost.   48 HDDs.   Root aggr: 1D + 2P = 3 Data aggr: 2 x (20D + 2P) = 44 Spare: 1   Root-data partitioning can improve the efficiency, but it's not available in your configuration. ... View more

What FAS platform?   The first SCSI reservation issue is indicative of downrev disk FW.   8.1.2 is very old. The things I would do before testing again are: - upgrade to 8.1.4P10 (at least). - download disk and shelf firmware packages and install/update - download latest compatible SP FW and update - download and install the latest DQP file.   ... View more

What ONTAP version? Try rebooting the SP's. If still issues, you can open a case to investigate further. ... View more

BMC can't proxy or forward AutoSupport on behalf of its host filer.  However, it can send a few kinds of AutoSupport for special situations (system down, etc.) via SMTP, if configured to do so via the AutoSupport options on the filer (if that makes sense - it gets that config info internall from its host).  It just needs a path to reach the SMTP gateway that is defined. ... View more

That screenshot is for a much newer ONTAP version and newer HW platforms... but the concept is sound. Are your systems sending AutoSupport? Then you can go to the My AutoSupport portal and examine the "sysconfig-a" section from a historical AutoSupport to see what the IP address was for the BMC.  My AutoSuport retains 60 days.  If you need to go further back in time, open a case with NetApp Support and they can look it up further back in time, if needed.   It will be at the bottom of the output and will look something like this:   Baseboard Management Controller: Firmware Version: 1.2 IPMI version: 2.0 DHCP: off BMC MAC address: 00:a0:98:26:7e:b2 IP address: 10.1.2.3 <<<<<<<<<<<< IP mask: 255.255.240.0 Gateway IP address: 10.1.2.1 BMC ARP interval: 10 seconds BMC has (1) user: naroot ASUP enabled: on ASUP mailhost: 0.0.0.0 ASUP from: filer@company.com ASUP recipients: filer-support@company.com Uptime: 190 Days, 03:40:25   Can you remotely log into the host system? If you don't have AutoSupport enabled (which is always a shame...), you might be able to see the IP address show up in the /etc/log/messages (and .0) files in the root volume of the system.  CIFS/NFS mount it to look around, or you can use the "dir" and "rdfile" commands from CLI advanced privilege to examine the log files.     ... View more

Hi Uwe,   You can purchase one-time support for systems with expired entitlement.  Contact NetApp Support for details.   In the meantime, it would be very helpful you had the initial panic/crash information recorded. It might still be there, if you collect an RLM diagnostic dump. From RLM CLI: > rlm status -d   Look over the output for any interesting info about the initial cause of the crash and what the console logs and system event logs say.   Since it looks like a HW issue, it would also be a good idea to pull the PCM and check/re-seat all of the cards in the enclosure.  After reseating, it wouldn't be a bad idea to run system diagnostics. Here's the link to the Diagnostics Guide applicable to the FAS3140. https://library.netapp.com/ecmdocs/ECMP1112531/html/ch1/overview.htm     ... View more

The extra data partition in the root-data-data version doesn't really change the disk assignment guidance for the physical (container) disks in an AFF system.  We're still say saying half of the shelf is owned by node 1 and the other half is owned by node 2.    See step 9 in this KB: https://kb.netapp.com/support/s/article/ka31A00000012lQ/How-to-convert-or-initialize-a-system-for-Root-Data-Data-Partitioning   ... View more

Hi Adam,   A couple of comments...   With the exception of the FAS6200 series of platforms, the Data ONTAP policy has been to not boot if it ever had less than the required system RAM. With very few exceptions, bootloader options are undocumented because they can be dangerous if mis-set. They should only be changed when instructed to do so by NetApp Support. If you're having problems with DIMMs, please open a technical case to troubleshoot and resolve it. ... View more

Hi Skip, My apologies... it turns out that "submit ticket" link is only available to NetApp partners or employees.   In the future, if you have a favorite partner or NetApp employee, they can submit on your behalf.   If you want to get this filed right away, you can send the details to Yogindra.kannukere@netapp.com  Thanks, -Andris ... View more

It's best to open a technical case with NetApp Support and have the suport engineer help you track down the source of the fault.   It's tough to diagnose this without looking at the EMS event logs (you can see the latest events with "event show") and/or the shelf logs. ... View more

That's strange.. Help -> Open Support Ticket should bring up this page: https://track.netapp.com/Ticket/config-advisor/30   Try this link, Skip. ... View more

You might want to open a technical case with Support to look into this further - there could a number of factors at work, here.   On the other hand, 8.3P2 is long in the tooth - your time might be better served moving to the recommended 8.3.x release - currently 8.3.2P9. Ref: Recommended Data ONTAP Releases on the NetApp Support Site   You can check out the bugs fixed between these two release, if you like: http://mysupport.netapp.com/NOW/cgi-bin/relcmp.on?notfirst=Go%21&rels=8.3P2%2C8.3.2P9&what=fix   Of particular interest... Bug 896685     ... View more

There's technical and philosophical arguments for not using e0M for anything but management roles.   Technically, e0M has been a lower-speed port (100Mb/s, 1Gb/s) in various platforms, sharing a link with remote management (the service processor). It also is restricted to a 1500 byte MTU limit.   Philosophically, management traffic (i.e. the control plane) should remain as isolated as possible from the data traffic.  ... View more