Support entitlement is tracked at the controller (system serial number) level. For a FAS2650 HA system (2 controllers), you would purchase the entitlement for both controllers and the underlying storage. As @SpindleNinja pointed out, the support period that you can purchase might be shortened by old storage drives in the system, if those drives go "end of support" before the FAS2650 system's EOS date. Reference: Support Services Terms
... View more
+1 for @maffo's response. If you check the output of the nodeshell "sysconfig -v" command, you can see this clearly. As a technical "tidbit", the physical SAS 0a port on the back of the controller is connected to an actual SAS HBA port chip. The physical SAS 0b port on the back of the controller is connected to the internal shelf's SAS expander chip. The SAS 0a HBA port chip is internally connected to the same SAS expander chip for direct access to all of the drives in the internal shelf. That's why you see the <==> symbol beside the 0b port, to signify it being connected to the SAS expander chip.
... View more
In case it is helpful, check out: FAQ: SnapDiff Support in ONTAP https://www.netapp.com/blog/new-backup-architecture-snapdiff-v3/ CPC-00352 -Deprecation of SnapDiff v1 and v2 APIs and the impact on third-party data protection applications supporting SnapDiff
... View more
I hate to say this, but those "ONTAP API" version numbers don't ring a bell (at least for me). ONTAP REST API versioning is based on the ONTAP version, itself (9.6, 9.7, 9.8, etc.) Can you provide more details about "ONTAP API 1.21 and above, the current API from NetApp storage is 1.17" that was referenced by your backup software (vendor?)
... View more
If you're not seeing e0a, e0b, e0M or e0P in sysconfig -a output, you might want to check out: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/FAS25xx_ports_e0a%2C_e0b%2C_e0M%2C_e0P_missing_with_%22Invalid_PCIe_device_detected%22
... View more
OK. It's a bit more complicated, but you should be able to use this KB with ONTAP 9.1. https://kb.netapp.com/Advice_and_Troubleshooting/Flash_Storage/AFF_Series/How_to_convert_or_initialize_a_system_for_Root-Data-Data_Partitioning
... View more
You didn't state which ONTAP version you are using.... If using encrypting drives (NSE, SED, FIPS), you need to also return them to unprotected mode (MSID 0x0, FIPS 0x0) before reinitializing or repurposing them. Otherwise, if there are no concerns over data or configuration, it can be as simple as cabling the system up as you desire. Then, perform: option 9a on node A, option 9a on node B, option 9b on node A and option 9b on node B. See: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/What_are_the_steps_followed_to__configure_advanced_drive_partitioning_from_ONTAP_boot_menu_option_9
... View more
In an active/passive configuration, only one of the nodes in the HA pair will own a data aggregate. If you like, collect the "sysconfig -r" output from each node. See: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_run_sysconfig_-a_or_sysconfig_-r_in_ONTAP_9
... View more
I'm not really following your question... perhaps you can provide more details (what is the FAS/AFF model, is advanced disk partitioning (ADP) being used, clarify data aggregates v.s. root aggregates). Each node will have its own root aggregate (might be the small partitions on the physical disks). If you're active/passive configuration, you'd only have one large data aggregate on one of the nodes and the other node doesn't serve data during normal operation If you want both nodes to serve data, then each node would have its own data aggregate. Aggregates can only belong to one storage virtual machine (SVM) a.k.a. Vserver in ONTAP CLI. Unless you need to completely partition data access among multiple tenants, you only need one data SVM and all of the aggregates would be mapped to that single SVM. https://docs.netapp.com/us-en/ontap/concepts/storage-virtualization-concept.html
... View more
To avoid performance impacts for the SSDs, place the SSD shelves on the ends of the (MP-HA) stack. That minimizes the number of shelf hops to the SSDs from the controllers.
... View more
The .1 after .15 is the shelf ID number. Is the FAS2750 enclosure shelf "1"? "" (null) = neither PSU is failed. 1 = PSU1 is failed. 2 = PSU2 is failed.
... View more
Thank you for reporting issues with accessing Support Bulletin SU422. The KB team has been notified of the issue. SU422 primarily covers this related Support Bulletin: Support Bulletin SU480: Firmware update for HARHE*, HLBRE*, and WVELE* drives to mitigate potential data loss, disruption or unavailability
... View more
Check the System IDs of both nodes in your HA pair (sysconfig will tell you). Does 1573991370 match either of the System ID of your nodes? Review "sysconfig -r" output for those two disks to see what ONTAP is doing with them.
... View more
See: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/What_are_the_steps_followed_to__configure_advanced_drive_partitioning_from_ONTAP_boot_menu_option_9 Essentially, do this in serial order: Option 9a on Node A Option 9a on Node B Option 9b on Node A Option 9b on Node B The 12 integrated/internal disks will be partitioned with root and data partitions.
... View more
Just leave the spare whole disk alone, assigned to either one of the HA partners. ONTAP will automatically partition the disk and assign the partitions, when needed.
... View more
Yes, NetApp Hardware Universe is your friend for these types of questions... check the "Onboard Ports & Cables" link in the results. But be aware that the onboard ports on FAS8700 are reserved for internal use in most cases. e0a/e0b (25GbE) are for HA cabling. e0c/e0d (40/100GbE) are for cluster network cabling. If you have the Ethernet bundle variant, the e0e -> e0h 10/25GbE Mezzanine ports can provide your connectivity for data or SnapMirror. If you have the FC bundle variant, you'll need to acquire suitable NICs for one of your PCIe slots.
... View more
Yes... this is due to Bug 1372079 - SES not translating shelf PSU input power correctly. It will be addressed in a future release of IOM12 and IOM12E firmware.
... View more
Reboot the BMCs on both nodes in the chassis. Then update them to BMC 11.6. The sensor reading failures can indicate issues with IPMI communication or BMC unhealthiness. Create a case with Tech Support, ideally.
... View more
Do you have CN1601 management switches, by any chance? In any case, I would check what the switch health monitor is actively monitoring with the "system cluster-switch show" command. If you are monitoring management switches and you see unneeded alerts for them with "system health-alert show", it might be simpler/easier to just stop monitoring the management switches. This KB has information on the commands you can use to delete a switch you no longer wish to monitor: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/Fabric%2C_Interconnect_and_Management_Switches/AutoSupport_Message%3A_Call_home_for_Health_Monitor_process_cshm%3A_UnsupportedSwitch_Alert
... View more
These KB articles might be useful: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/How_to_maximize_storage_efficiency_on_All_Flash_FAS_systems_running_ONTAP_9.x https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_maximize_storage_efficiency_post_AFF_ONTAP_9.x_migration
... View more
A few more details? ONTAP version (and mode)? How is the PowerChute shutting down the controllers, exactly? If you have SSH access to the SP of each controller, you can run "system power on" commands from there.
... View more
One obvious reason (but uncommon) reason might be that performance data AutoSupport transmission has been disabled. system node autosupport modify | show [-perf {true|false}] - Performance Data Enable Use this parameter to specify whether performance data is sent to technical support and addresses specified in the -partner-address parameter. The default is true.
... View more