Actually, the node management LIF can fail over - but it's restricted to other ports on the same node. (failover policy = local-only). You might want to look at your "Default Network" failover group's membership to see why node2 is unhappy but node1 is OK. If you truly do not want the node-mgmt LIF to fail over to another port other than e0M, you can set the failover policy of the node-mgmt LIF to "disabled" (a tip from @Overz) ::> network interface modify -vserver svm_name -lif lif_name -failover-policy disabled
... 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
Unfortunately, the root-data-data partitioning scheme is only available on 9.0+ AFF systems. Are the 4 SSD's being used for FlashPool? You can comfortably use RAID4 for them. I would stick with RAID-DP for the HDD's - reliability levels of HDD's really demand it.
... View more
@River wrote: Hi All : I am installing FAS9000 now, and I can not find out any KB about NVME modules. Do I need to setup the options like old PAM did? ex: options flexscale.xxxx Andris: Even though we evolved from PCIe cards to NVMe modules in the latest platforms, it's still Flash Cache. So, it's the same commands to configure and monitor. Configuration is mostly "enable and forget". You would use the "system controller flash-cache" commands for physical aspects and "system node external-cache" commands for the actual cache behavior configuration. The corner-case tweaking might still use the nodeshell flexscale.* options. And how can I predict the module's life? For SSD is shelf, I can use storage show disk in node shell. Andris: if you look at "system controller flash-cache show -instance", the percent-online field tells you how much of the Flash memory is operational. Also, when the module is almost at its end-of-life, the system will issue EMS events and AutoSupport messages. That said, Flash Cache modules don't really wear out before the lifetime of the platform. And if the NVME module failed, will it cause performance issue? Andris: Generally, yes. You'll get EMS events, alerts and AutoSupport messages sent if a Flash Cache module fails. And what's Quad-path used for? Only more safety? Should I cable as Quad-path right now? Andris: I answered this in your other thread. http://community.netapp.com/t5/FAS-and-V-Series-Storage-Systems-Discussions/What-s-Quad-path-used-for/m-p/127612#U127612 There's not too much information I can found on NOW site... And I had AFF700 need to install about a month later = =.
... View more
Sure... If you don't want to peruse performance graphs/counters (e.g. via OnCommand Performance Manager) to check the storage utilization percentage or worry about specific workloads, going with Quad-Path cabling for AFF storage is a great rule of thumb. There's just the minor extra costs of using extra HBA ports and cables.
... View more
In the Config Advisor tool, go to the Help menu and select "Open Support Ticket". You can describe the issue and attach any relevant files.
... View more
I would recommend the customer use a different workaround option, instead of changing to SMTP - keep the HTTPS transport, but disable X.509 certificate validation. The details are in the Support Bulletin KB: https://kb.netapp.com/support/s/article/https-autosupport-messages-will-fail-to-reach-netapp-from-your-storage-systems-after-netapp-autosupport-server-x-509-certificate-renewal-in-november-2016
... View more
Hi River, While quad-path HA provides additional path resiliency, the main purpose for the additional cabling is to double the I/O bandwidth to the SAS3 storage stack. Configuring the storage stack with quad-path HA and double-wide intrastack connections is optional. All-SSD storage stacks can benefit from the increased bandwidth, especially for for large block (e.g. 64KB) sequential read streaming workloads.
... View more
Hi, For IBM N-Series systems, those tools are only available to IBM Technical Support. I would contact them if you require an Upgrade Advisor plan.
... View more
There have been a few AutoSupport-related fixes in 8.2.1 or 8.2.2RC1 that would solve 8.2 issues. Since you're already on 8.2.1, it could be other factors at play. I'll reiterate my guidance - ensure the support engineer gets the notifyd.log files and related AutoSupport configuration/environmental information (autosupport options, hosts file, ifconfig -a, netstat, DNS, routing, SMTP servers, HTTP proxies, etc.) to troubleshoot your issue.
... View more
I can confirm that other than the FAS8000, the management (wrench) port is limited to autonegotiating 10/100 Mb/s connections only. FAS8000's wrench port is "upgraded" to 10/100/1000 Mb/s. If your main switch infrastructure can no longer provide 100Mb/s full-duplex, then your idea is OK. Two considerations: 1. If you plug a number of wrench ports into your "feeder" switch, make sure your upstream Nexus allows multiple MAC addresses on the port 2. Make sure this switch autonegotiates properly with the wrench port. The wrench port does not have any manual Ethernet configuration options - autonegotiation is required.
... 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
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