Ricardo, Can you be more explicit about what RFC's and AUTH methods you are asking for? I assume you're referring to ESMTP AUTH? http://en.wikipedia.org/wiki/Extended_SMTP E.g. Compliance with RFC 4954? http://tools.ietf.org/html/rfc4954 As much details about the requirement you can provide would be appreciated. ... View more

FYI, the -type is now a mandatory field for the invoke command, starting with Data ONTAP 8.0.1. ... View more

Can you clarify what a "traceable User ID" implications are from an SMTP perspective? Alternatively, would switching to using HTTPS transport to NetApp be acceptable? ... View more

Can you download the entire AutoSupport from My AutoSupport? No. If you have access to the system, you can grab the last 40-50 AutoSupport collections (depending on DOT version) from /etc/log/autosupport. In 8.1, you have CLI that lets you specify any of those cached AutoSupport messages and retransmit them to arbitrary SMTP and HTTP destinations. If you feel there's a specific reason why this should be available from My AutoSupport, please elaborate. ... View more

The Flash Cache report is, as stated, simply reporting enabled capacity. It is not (currently) showing operational efficiency of the Flash Cache component. This report is not really useful when run against a system. It's more interesting when looking at your entire NetApp infrastructure across a site or company. Here's an example of the report from a company with a large storage footprint of NetApp systems. ... View more

The "about" link takes you (eventually) to this page. It has short explanations for the reports. https://communities.netapp.com/community/products_and_solutions/efficient_it/my_autosupport_and_autosupport/blog/2011/08/20/my-autosupport-launches-storage-efficiency-20-beta Do you have specific questions that we might be able to address? ... View more

Yes, it's a bug, but not as critical as I first thought. It will still be put on the "list". ... View more

I can confirm that once you change your Preferences to "Dashboard" view, the bottom bar becomes visible. I deleted my earlier posts. ... View more

If possible, examine EMS event logs and messages files for any problems with the storage controller's collection and transmission of the Performance Data AutoSupport message. If there are problems, open a technical case with NetApp Support and be ready to provide the info from the logs, as well as the notifyd.log file (for 8.0 systems) in the /etc/log/mlog (7-Mode) or /mroot/etc/log/mlog (Cluster-Mode) directory. If there's nothing amiss at the storage controller end, then file a support site ticket about My AutoSupport missing performance data for your specific systems at http://now.netapp.com/willows/pri/feedback.do -Andris ... View more

I’m glad to hear that you found the config error… BTW, please consider plugging in your wrench port. It gives you access to e0M to directly manage the system and allows you to leverage all of the remote management and remote support capabilities of the Service Processor. -Andris ... View more

Do you recall what was the last action made with the S300? It would be good to connect to the console port and check for relevant messages. If you had issued halt and bye to halt the S300, you may need to power cycle the unit. See: http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=330894 ... View more

Try specifying longer date ranges. -Andris ... View more

The traps are documented in the NetApp MIB file. You can find them all here: http://now.netapp.com/NOW/download/tools/mib/ Each trap has a DESCRIPTION field that usually provides good information concerning the trap. ... View more

For customers and partners, the NetApp Support site has a great resource page on AutoSupport. http://now.netapp.com/NOW/knowledge/docs/olio/autosupport/ -Andris ... View more

Thanks for the system ID's for looking up. This doesn't appear to be related to My AutoSupport - there appear to be problems with the systems being able to send typical content-rich AutoSupports via the customer's SMTP servers. This is somewhat supported by the fact that the simple "noteto" e-mails are getting through without problems.  It's likely to be an incompatibility with the customer's anti-spam/anti-malware/anti-virus scanning functionality in place for e-mail. I'd open a support case for further technical assistance. -Andris ... View more

If you do have a brand-new FAS32xx and need to revert it to 7.3.5, this KB article is useful: https://kb.netapp.com/support/index?page=content&id=1012604 NOTE: This procedure is intended ONLY for a newly installed system that is not  yet in production and contains no data. It is NOT intended for existing  systems that are in production. -Andris ... View more

Spence covered most of your questions. To be really clear... Customers can only receive AutoSupport via SMTP, using "autosupport.to". Note: This is a filtered destination - only important AutoSupport messages are sent. Partners (or Customers) can receive all AutoSupport transmissions (SMTP only), using "autosupport.partner.to". (7.3.x feature) NetApp Support can receive via the selected transport protocol, all AutoSupport messages. - If HTTP/HTTPS is selected, then they are sent to "autosupport.support.url" - optionally via a proxy (if specified) - If SMTP is selected, then they are sent to "autosupport.support.to" - Note: These NetApp Support destinations are hardcoded. If you do change it, they would revert back after a reboot. I hope that helps. ... View more

Hi gridley, The new aggregated (by site or company) performance tab allows you to perform .csv exports of the related performance tables. Unfortunately, the actual graphs are not exportable - the only thing I can think of is screen-scraping it. Why don't you click on the "online support" link at the top right corner of the web page and submit your request for enhancement. Please be as detailed as possible with your requirements in the ticket. https://now.netapp.com/willows/pri/feedback.do Thanks, -Andris ... View more

Hi Thorsten, Unfortunately, My AutoSupport does not display AutoSupports from the DFM suite of management software products, so customers cannot use My AutoSupport to verify receipt of the DFM AutoSupport message. The customer can contact their NetApp representative (or tech support) to request receipt verification using internal access methods. The DFM FAQ's include AutoSupport topics. https://kb.netapp.com/support/index?page=content&id=3012309 Choose the appropriate release link, and look for the AutoSupport category in the resulting FAQ. For instance, this question is relevant: 20.3 Can I test the autosupport feature to see what it will send back to NetApp? Yes. You can have an autosupport sent to yourself by e-mail by running the following command: $ dfm autosupport send -e <your-e-mail-address@your-domain.com> -p smtp -Andris ... View more

David, I'm sorry that it was hard to find where you can customize notifications for one of your systems in My AutoSupport. For other reading this thread, look for this icon/link at the bottom-right side of a system's dashboard page (attached file). The WEEKLY_LOG AutoSupport message is in that notifications page, but you might have to scroll down to see it. Click on the "INFO" category. Then scroll down to find the WEEKLY_LOG choice (it's alphabetical). -Andris ... View more

Hi Michael, If you're taking about the system warning LED on the physical controller, that typically indicates a hardware component failure/degradation. It would not be related to this "sam.misconfig" warning in HealthCheck. I would examine the environment, storage and EMS/messages files for evidence of a hardware problem.  If it's not obvious, open up a case with NetApp Tech Support. -Andris Message was edited by: Andris Dindzans ... View more

Jason, if you don't mind taking the time to do this, please open a technical case for the System Manager problem and ask the support engineer to open a bug report. Thanks, -Andris ... View more

Yup. The options is autosupport.support.transport, which implies it only affects the way you send the AutoSupport messages to NetApp only. autosupport.to and autosupport.partner.to always use SMTP, so the mailhost config is essential to make that work. (setting the .from field is a good idea, too). -Andris ... View more