Are you sure your FAS2820 is 4xSSD + 10xHDD? It's a 12-drive chassis, so it's really 4xSSD and 8xHDD.
Anyway, Fusion is conservative, but it is a good tool to estimate performance at a somewhat granular workload configuration level.
You might get some additional advice from the NetApp Discord channel. I recommended joining it and asking your questions there. https://discord.com/channels/855068651522490400/1062049107096633454 I think there's still headroom in the FAS2820 for another shelf, if you add one.
Don't be concerned over RAID group sizes - the RAID-DP maximum of 28 drives is always enforced. You simply create additional RAID groups to add to the aggregate (or just create new aggregates with the new storage, if you want).
... View more
Yes, the patch version's download page lists the specific fixes in that patch version of ONTAP.
To see a cumulative list of fixes between two ONTAP versions in general, we have this Bugs Online tool -- ONTAP - Release Bug Comparison.
Comparing 9.14.1 with 9.14.1P11 (fixed in 9.14.1P11): https://mysupport.netapp.com/site/bugs-online/release-comparison/product/ONTAP?version1=9.14.1&version2=9.14.1P11&type=fixed
... View more
The X66211B-5-C cable is a standards-based 5m 100GBASE-CR4 cable that we have formally tested with our hardware products. It is known to interoperate well with many switch vendor products.
Cisco switch software (NX-OS, iOS) is known for actively calling out transceivers and cables as "unsupported" if they are not Cisco-branded products. Furthermore, Cisco TAC might become less helpful if 3rd party cables are being used - often requiring a Cisco-branded part to be used to progress with troubleshooting.
Answer for #1:
The easiest path is to purchase Cisco cables, but that implies additional costs.
If you search for this issue on the Internet, a common solution is to run these commands to help with 3rd-party compatibility with Catalyst switches (Info from this Cisco Community Forum thread )
no errdisable detect cause gbic-invalid
service unsupported-transceiver
Answer for #2 and #3: NetApp Hardware Universe provides formal compatibility information between storage systems and supported back-end (cluster, storage, MetroCluster) switches.
But, NetApp does not formally document cable compatibility for front-end data networking use-cases. We have a more flexible policy. Using 3rd party optics/cables is permitted, as long as they are similar in technology and compliant with applicable Ethernet standards. Generally, you would avoid active copper and active optical technologies, unless we specifically have our own solutions for them (per HWU). If using another vendor’s cables/optics, best to stick with ones that are approved by the device/switch vendor.
In summary, for storage system front-end connectivity, the answer is “Try it – it might work. YMMV”.
From a hardware support perspective, the customer or switch vendor is responsible any component replacement.
... View more
Typically, the 25GbE ports on the platform support RS-FEC - usually autonegotiated. You'd have to provide specific platform and NIC/card details to get a 100% answer.
... View more
Hardware Universe images and LED views will usually tell you which is port “a”.
PCIe Adapter cards always have the convention that the top port is the first or “a” port. “Top” is the port furthest away from the PCIe connectors (which is the “bottom”). When onsite, if a card is horizontal, the connectors will tell you which side (left or right) is “bottom”. Generally, for horizontal PCIe card slots, the riser is on the left, which means connectors are on the left. So, the “a” port is furthest to the right, “b” is to the left and so on.
... View more
I haven't seen this particular question, before. Non-disruptive in-chassis HW upgrade is not supported - it would get hung up on seeing mixed controllers in the chassis, IMO. Thinking about it, it would have to be disruptive and you'd need to move any data off the FAS8300, first.
Evacuate data off attached storage
Unjoin FAS8300 (if applicable)
Use parts of the "repurpose KB" workflow to init the FAS8300 and the attached storage (MSID 0x0 for encrypting drives, wipeclean, option 9a, etc.)
Swap out the FAS8300 with FAS8700 controllers and recable
Boot and init the FAS8700, create or join the cluster
Move your data back.
... View more
Are you talking about a controller upgrade to a complete FAS8700 in its own separate chassis, or are you asking about in-chassis controller upgrades?
Top-level doc topic: https://docs.netapp.com/us-en/ontap-systems-upgrade/index.html
... View more
Another difference is that SAS2 HW components like DS2246 shelves passed EOS on 31-Jan-2025.
See: CPC-00133 -- End of Availability: DS2246 and DS4246 Disk Shelves and Media, 6TB NSE NL-SAS HDD
... View more
boot_ontap boots the ONTAP operating system from the LOADER. You use this any time you want to bring up the system from LOADER.
bye performs a warm reset of the controller (CPU complex). You use "bye" any time you have any hardware (additions, removals, replacements) or system firmware (BIOS/LOADER) changes in the system.
bye -g performs a global reset of the controller (including CPU complex and internal CPU firmware, such as the management engine). It's somewhat vestigial, in that the "bye" command will automatically invoke "bye -g" in situations where it is necessary.
In your NVDIMM example, it doesn't really matter if you use boot_ontap or bye, since the controller was pulled out for the NVDIMM replacement. So, you have already "power-cycled" the PCM/controller post-replacement, in effect.
In platforms such as the AFF-A700 where I/O and NVRAM modules can be independently added/removed/replaced while the PCM/motherboard is still sitting at the LOADER prompt, bye is required to re-enumerate all of the PCIe devices now in the system.
X9170A "Core Dump Device": See: How to configure A700 systems with X9170A core dump device
... View more
If Hardware Universe doesn't have what you're looking for, another supplementary information source is this KB article:
How to determine the NetApp part number for Brocade and NetApp SFPs
... View more
I don't believe Sanitize is even possible if you don't have the AK. The 1st KB link has the command while in Maintenance mode.
If this is a new setup or a repurposed system with no data on it, then the process is to boot (1) node to the maintenance mode then run the command from there:
*> disk encrypt revert_original <psid> <disk>
... View more
To check you have the right ONTAP image that supports encryption.. https://kb.netapp.com/on-prem/ontap/DM/Encryption/Encryption-KBs/How_to_determine_if_the_running_ONTAP_version_supports_NetApp_Volume_Encryption_NVE
If the FIPS/NSE drives were not set back to "open"/factory MSID 0x0 before decommissioning, they are probably still locked with authentication keys. Check out these articles: How to return SED to factory-configured settings after FIPS authentication key is lost How to identify the PSID on a FIPs capable drive
... View more
Please refer to:
https://kb.netapp.com/Support/General_Support/What_is_in_the_scope_of_NetApp_Technical_Support
My installed version is End of Support, but my contract is still active, can I get support?
... View more
The OP has an AFF A220, though…
See Software Support Plan here:
https://www.netapp.com/services/support/descriptions/
SSP allows you to download ONTAP and related software for your A220. You will need to register on the NetApp Support Site, first.
... View more
Yes, you can mix them in the same shelf (or same HA pair, for that matter). You would need to confirm that self-encrypting drives (SED) can be used in the country of operation.
See: Does NetApp support encrypted and non-encrypted disks on the same node?
... View more
If you might be referring to NetApp Hardware Universe, it maintains information concerning End of Support (EOS) hardware, as well. Just make sure you are not filtering them out in the UI.
Note: NetApp doesn't formally use the EOL term.
... View more
If this is in the context of https://aiq.netapp.com/, then click on the "Support" icon to report this issue to the AIQ Digital Advisor support team. Please provide the exact steps you take when this issue occurs.
... View more
The documentation for SnapMirror Active Sync clarifies that statement. https://docs.netapp.com/us-en/ontap/snapmirror-active-sync/prerequisites-reference.html
Hardware
Only two-node HA clusters are supported.
Both clusters must be either AFF (A-Series and C-Series) or ASA (A-Series and C-Series). Mixing between AFF and ASA is not supported. Replication is supported between AFF A-Series and C-Series.
... View more
Hi Antonio,
You're free to submit document feedback, but it's somewhat covered in this topic in the procedure:
https://docs.netapp.com/us-en/ontap-systems-upgrade/upgrade-arl-auto-affa900/replace-node1-aff700-fas900.html#remove-the-aff-a700-or-fas9000-nvram-module
Move all flash cache modules installed in the FAS9000 NVRAM module to the FAS9500 NVRAM module.
It's an easy stretch to believe that you can swap in a different capacity flash cache drive or even add a 2nd flash cache drive in slot 6-2 at this time, too.
... View more
You can direct-attach iSCSI or NVMe/TCP to any of our platforms. However, this is generally discouraged because it severely limits scaling and may not have sufficient redundancy. You must have a switch for FC because we rely on NPIV services from the switch to support multiple LIFs on a single physical port.
There is more information in TR-4080: Best Practices for Modern SAN
... View more
What platform and LOADER version are you using?
I'm a little confused with your post, though. You are showing an error for the bootmedia (i.e. the boot device), but you are asking how to test system memory?
You can test memory with system-level HW diagnostics (devtype = mem) See: https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_use_the_ONTAP_Hardware_SLDIAG_tool
The LOADER "memtest" command is for internal development purposes, only. It is not to be used by customers.
... View more