About andris

andris · ‎2023-01-25

From a purely technical port connectivity perspective the UTA2 ports (e0c -> e0f) on the AFF A220 supports an optical 1GBASE-SX transceiver part available from NetApp. X6567-R6 I would also be concerned about using a 1GbE switch for your vSphere cluster. It might be a good idea to consider upgrading your switches to 10GbE levels.

andris · ‎2023-01-22

@SpindleNinjais right on... If you'd like to see the exact sizes of the partitions, the NetApp Hardware Universe shows that information via the ADP Root Partition Configuration link of the AFF A220's search results: https://hwu.netapp.com/Controller/Index?platformTypeId=5265148&platform=8626206&os=25380180

andris · ‎2023-01-17

Unfortunately, the driver/firmware for the X1154 FC ports do not support initiator mode, and there is no plan to do so. Hence the footnote in Hardware Universe.

andris · ‎2022-12-15

A1: VLANs 17 and 18 are used for HA traffic on AFF/FAS platforms that use a shared cluster+HA Ethernet ports (AFF A320, AFF A250, FAS500f). Please do not change anything related to VLANs 17 and 18. A2: The ISL ports 0/55 and 0/56 normally ONLY span VLAN 1 (default VLAN). You should NOT be spanning VLAN 17/18 (this is by design). Now with VLAN 999 being used natively for cluster traffic, I would go with this config: switchport trunk allowed vlan 1,999 I believe VLAN 1 is still used for some control traffic (e.g. CDP/ISDP), so that's why I'm keeping VLAN 1 in there. But you can remove it and see what happens 🙂

andris · ‎2022-12-14

What EFOS version are you on? Make sure you add VLAN 999 to the VLAN database. The cluster node ports are in "trunk"mode. So, you would set the native VLAN to 999 (it defaults to VLAN 1) for your untagged ingress traffic. interface 0/1-0/16 switchport trunk native vlan 999

andris · ‎2022-12-08

I'm glad to hear you found out about the reference configuration files (RCF). Here's some useful links to check out... Documentation: https://docs.netapp.com/us-en/ontap-systems-switches/switch-bes-53248/overview-bes53248.html Compatibility Matrix (to help you decide which EFOS version and RCF version to use): https://mysupport.netapp.com/site/info/broadcom-cluster-switch The support contract for the BES-53248 you have is with Broadcom. Here's info on this and how to register support for the switches. https://mysupport.netapp.com/site/info/policies-and-offerings/broadcom

andris · ‎2022-11-11

You shouldn't have to... what is your spare partition/disk situation, now? You still need to maintain spares after the aggregate expansions. nodeshell CLI "sysconfig -r" for each node might provide more clarity. Or open a technical case for formal assistance...

andris · ‎2022-09-29

+1 on Alex's reply. The customer is free to set up any management access and monitoring configurations for their environment. That said, two more points: Customers might need more breakout ports for their environment than the RCF configures. It is fine to repurpose additional switch ports for the ONTAP cluster's environment, as needed. See: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/How_to_modify_RCF_1.X_Breakout_on_Cisco_NX3232C_cluster_switch_for_specific_customer_needs ONTAP cluster switch health monitoring support for SNMPv3 is coming in a future ONTAP release. You are free to use SNMPv3 for switch monitoring with your tools, but you'll need to keep SNMPv2 community string support for ONTAP's communication with the switches, for now. See: Bug 1358228 - Only SNMPv2 with default SHM community string is supported in ONTAP SHM

andris · ‎2022-08-17

The HTML Instructions page for BIOS 11.16 should address your questions. https://mysupport.netapp.com/site/downloads/firmware/system-firmware-diagnostics/instruction-viewer/SYSTEM/30804108_signed/system-installation-instruction?fileName=index.shtml

andris · ‎2022-07-05

Upgrading your ONTAP version would also be highly recommended. 9.4 is no longer supported.

andris · ‎2022-06-03

Since it belongs to the partner node, did you try unfailing it from the partner node’s CLI?

andris · ‎2022-05-28

Closing the loop... this issue is tracked by Bug 1465232 - CIFS password change operation might fail. There are ONTAP fixes in various branches, as well as a workaround if an ONTAP upgrade is not possible at this time.

andris · ‎2022-05-24

Except... the AFF A400 platform (as do most of the newer models) dumps a coredump into a special partition on the boot device, now. So, the content about needing spare partitions for coredump no longer applies. That said, you still want spare partitions for RAID recovery operations.

andris · ‎2022-05-06

Actually, if you review the KB, it applies to both HDD and SSD. The commonality is disk partitioning, which pretty well the default for most systems.

andris · ‎2022-04-14

Though it doesn't cover your exact scenario, this KB might be useful: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_perform_graceful_shutdown_and_power_up_of_all_ONTAP_nodes_in_a_cluster The actual halt command is step 6. If the UPS only covers an HA pair/chassis, you would specify the impacted nodes. Since it's a script, a handy "set" option is to turn off confirmations. See: http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-cmpr-991%2Fset.html

andris · ‎2022-03-31

In fact, the CN1610 does not support any form of web interface. If you are trying to reach it with HTTP or HTTPS, it should fail. The only supported remote login methods are SSH and Telnet (if enabled).

andris · ‎2022-03-24

Which shelf doesn't really matter. I would key off where you physically installed the products. First, make sure the controller and shelves all have unique shelf IDs (you can set them from the front "OPS" panel). I'd recommend 00 = controller, 01, 02 going down the stack, for example.

andris · ‎2022-03-24

Storage cabling guidance is available in AFF A220/FAS2700 Systems Installation and Setup Instructions or the specific step, here: https://docs.netapp.com/us-en/ontap-systems/fas2700/install-detailed-guide.html#option-1-cable-storage-on-an-ha-pair-with-external-drive-shelves

andris · ‎2022-03-22

What switch model, firmware and RCF versions are in question, here?

andris · ‎2022-03-05

Switching personalities of a system (FAS, AFF, ASA AFF) is not supported.

andris · ‎2022-02-23

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

andris · ‎2022-02-16

+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.

andris · ‎2022-02-04

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

andris · ‎2022-02-04

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?)

andris · ‎2022-01-26

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

Re: Will this AFF A220 FC configuration work?

Re: AFF-A220 recommended drive assignment for RAID

Re: A250/FAS500f FC initiator Mode X1154

Re: BES-53248 default vLAN 1 - change for stigs

Re: BES-53248 default vLAN 1 - change for stigs

Re: BES-53248 cluster switches

Re: Aggregate expansion

Re: Nexus 3232 Custom Configurations

Re: FAS 8200 - ONTAP 9.7 - Upgrade Motherboard BIOS Firmware

Re: FAS2650 show HDD failed after disk replacement (ONTAP 9.4)

Re: disk unfail: Disk is not currently failed 7mode FAS2220

Re: Is CVE-2021-42287's updates compatible with ONTAP 9？

Re: Align spares

Re: Disk Spare Ratio Question

Re: Shutdown Netapp FAS with SSH Script

Re: cluster switch login issue

Re: About connection between disk shelf and controller

Re: About connection between disk shelf and controller

Re: Broadcom cluster switch

Re: ASA to AFF conversion

Re: FAS2650 EOSL

Re: SAS ports up and down on C190

Re: API version 1.21

Re: API version 1.21

Re: FAS2552 node missing interfaces

ONTAP 9.16.1 EAP

ONTAP 9.15.1 EAP