Late-breaking update... Today, we just released the 8.2.1 GA version... Version: 8.2.1.121 GA Software Download ... View more

It would be best if you opened a technical case with NetApp to troubleshoot and diagnose the issue. The following info would be very valuable: 1. A few AutoSupport log files from the time period where you had failures: /etc/log/mlog/notifyd.log.<x> 2. Generate a user-triggered AutoSupport and manually upload it to NetApp. See:     https://kb.netapp.com/support/index?page=content&id=1013073    (It would contain relevant info, such as networking configuration (interfaces, routes, DNS), AutoSupport configuration/history/status and latest snippets of EMS and notifyd log files) ... View more

The SDK community link is here: https://communities.netapp.com/community/interfaces_and_tools/interfaces ... View more

Customer-facing environmental info for platforms and shelves is available in the Site Requirements Guide on the NetApp Support Site. https://library.netapp.com/ecm/ecm_get_file/ECMP1112530 ... View more

Mohamed, You'll probably get more feedback from the Data ONTAP forum. https://communities.netapp.com/community/products_and_solutions/data_ontap Do you have System Manager 2.2? Consider: https://library.netapp.com/ecm/ecm_download_file/ECMP1203769 Comprehensive information can be found in your Data ONTAP release's Online Backup and Recovery Guide E.g. for 8.1.3 7-Mode: Data Protection Online Backup and Recovery Guide ... View more

Assuming you're running 8.1+ Data ONTAP, you can check to see if the ASUP was successfully with the "autosupport history show -instance" command.   This will at least tell you if the first leg of the transmission worked.  If it did, you should proceed with the My AutoSupport ticket.  If it didn't, then you can open a technical case with NetApp Support to help you diagnose the transmission failure. For more info, read this AutoSupport troubleshooting workflow KB: https://kb.netapp.com/support/index?page=content&id=2017276 ... View more

Hi Martin, This is somewhat ironic... if you are running Data ONTAP 8.1 or later, you can specify a non-standard port, already!  However, it is not checked for "correctness", so you need to be careful with the syntax. Basically, you can append the mailhost name or address with ":<port#>". cDOT: system node autosupport modify -mail-hosts my.mail.server.com:2525 7-Mode: options autosupport.mailhost my.mail.server.com:2525 The burt I logged will drive improved input checking and documentation for this.  Let me know how it works for you... -Andris ... View more

What version of Data ONTAP is this request concerning? In Data ONTAP 8.1.x, snapmirror.conf is actually collected as the file "sm_conf.txt" in the snapmirror sub-system. Again, sub-systems are not always collected in a given ASUP message. For the "snapmirror" system, it's collected in callhome.invoke (doit "test"), callhome.invoke.all (doit) or callhome.weekly (WEEKLY_LOG). ... View more

@Patrick: The missing licenses view is a known issue with My AutoSupport. It should be addressed soon. vijayang: It looks like you are referring to a Data ONTAP 8.1 system. Yes, that is the correct file to look at (in raw form or with a XML viewer). To "decode" it, look at each record: - the "service" attribute defines the license name (cifs, cf, a_sis) - the "is-licensed" attribute defines whether it is enabled on your system. ... View more

What version of Data ONTAP are you running on the system? Starting with DOT 8.1, AutoSupport content is context-sensitive. The rc.txt file is not always included with every AutoSupport. Also, size and time budgets were introduced.  There was a known issue with the leak-data file being too large, causing the collection of the rc file to be skipped. It was fixed in 8.1.3 and later releases. If it sounds like you might be in this situation, you can verify what was supposed to be collected and its collection status by examining the manifest.xml file that is also included with the AutoSupport message. ... View more

Yes, those sources would work. If you need a nice presentation to show the customer, look for "Windows File Services in Clustered Data ONTAP 8.2-Customer Presentation" on the NetApp Field Portal. ... View more

There were some issues with that system risk being correctly detected. I believe it's fixed, and should be correct by Sunday. Please check again on Monday. ... View more

Hi Martin, I opened bug 716861 (RFE: Provide SMTP port configurability for AutoSupport) on your behalf. Regards, -Andris ... View more

Like the NetApp Support destination, the e-mail destinations specified in the autosupport.partner.to option will receive all AutoSupports NetApp Support does (i.e. essentially unfiltered). The "autosupport trigger" command only configures which events are sent to the ".to" and ".noteto" destinations. ... View more

Hi Martin, That configuration option does not exist. It's assumed that customer systems will be pointing to an SMTP relay on their internal network - where concerns over spam (the main reason for blocking 25) are minimal. Have you or customers opened any technical cases concerning this issue?  If so, please supply them. If you believe this to be an important enhancement, ask your NetApp sale representative to submit the enhancement request. ... View more

You may have already seen it, but 8.2RC1 is available as an ONTAP Simulator. http://support.netapp.com/NOW/download/tools/simulator/ontap/8.X/ ... View more

Hi Steve, You'd be looking for this HBA for your FAS2050's: 2p 3Gb SAS, PCIe X2062A-R6 You'll need MiniSAS-QSFP cables for controller to shelf connections. Part No Begin End Length Description X6543A-R6 miniSAS QSFP 2m Cable,miniSAS Cntlr-Shelf,2m X6544A-R6 miniSAS QSFP 5m Cable,miniSAS Cntlr-Shelf,5m The Hardware Universe is a handy place to look all this up. http://hwu.netapp.com I'd upgrade your systems to 7.3.7P2 for the best stability and performance. ... View more

Well, if you're running 8.0 or 8.1 Data ONTAP, you can temporarily disable the ASUP message for  USER_TRIGGERED to your .to and .noteto recipients. Invoke your fake USER_TRIGGERED (WEEKLY_LOG). Then reinstate your .to and .noteto destinations. For 8.0 instructions, see KB: 1913810 https://kb.netapp.com/support/index?page=content&id=1013810 In 8.1, use the "autosupport trigger modify" command for the "invoke.all" event. ... View more

No need. That tells me it was 8.1.2. ... View more

Sorry... I don't know. Hana might have a clearer answer. What DOT version is your VM? ... View more

Thanks.  Even with 5.1 (latest shipping), the release notes say:     Data ONTAP Edge is not supported. ... View more

Keith, What version of OCUM are you testing with? ... View more

I am not seeing any problems with My AutoSupport - this is as an employee from a VPN connection, at least. Definitely follow the instructions here to open a support ticket: https://support.netapp.com/willows/pri/feedback.do Regards, -Andris ... View more