Upgrade firmware on MetroCluster IP switches
Suggest changes
PDFs
You might need to upgrade the firmware on a MetroCluster IP switch.
Verify that the RCF is supported
When you change ONTAP version or the switch firmware version, you should verify that you have a reference configuration file (RCF) that is supported for that version. If you use the RcfFileGenerator tool, the correct RCF is generated for your configuration.
-
Use the following commands from the switches to verify the version of the RCF:
From this switch…
Issue this command…
Broadcom switch
(IP_switch_A_1) # show clibannerCisco switch
IP_switch_A_1# show banner motdNVIDIA SN2100 switch
cumulus@mcc1:mgmt:~$ nv config find messageLocate the line in the command output that indicates the RCF version. For example, the following output from a Cisco switch indicates that the RCF version is “v1.80”.
Filename : NX3232_v1.80_Switch-A2.txt
-
To check which files are supported for a specific ONTAP version, switch, and platform, use the RcfFileGenerator for MetroCluster IP. If you can generate the RCF for the configuration that you have or that you want to upgrade to, then it is supported.
-
To verify that the switch firmware is supported, refer to the following:
Upgrade the switch firmware
You must repeat this task on each of the switches in succession.
Enable console logging before performing this task.
-
Check the health of the configuration.
-
Check that the MetroCluster is configured and in normal mode on each cluster:
metrocluster showcluster_A::> metrocluster show Cluster Entry Name State ------------------------- ------------------- ----------- Local: cluster_A Configuration state configured Mode normal AUSO Failure Domain auso-on-cluster-disaster Remote: cluster_B Configuration state configured Mode normal AUSO Failure Domain auso-on-cluster-disaster -
Check that mirroring is enabled on each node:
metrocluster node showcluster_A::> metrocluster node show DR Configuration DR Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- 1 cluster_A node_A_1 configured enabled normal cluster_B node_B_1 configured enabled normal 2 entries were displayed. -
Check that the MetroCluster components are healthy:
metrocluster check runcluster_A::*> metrocluster check run
The operation runs in the background.
-
After the
metrocluster check runoperation completes, run:metrocluster check showAfter approximately five minutes, the following results are displayed:
cluster_A:::*> metrocluster check show Component Result ------------------- --------- nodes ok lifs ok config-replication ok aggregates ok clusters ok connections ok volumes ok 7 entries were displayed.
-
Check that there are no health alerts:
system health alert show
-
-
If your MetroCluster IP configuration has NVMe shelves connected to the MetroCluster IP switches, run the following commands to verify the shelf status.
-
Show the shelf status:
storage shelf showShow example
cluster_A::> storage shelf show Module Operational Shelf Name Shelf ID Serial Number Model Type Status ----------------- -------- --------------- ------------ ------- ----------- 1.0 0 952123456789 NS224NSM100 NSM100 Normal 1.2 0 952987654321 NS224NSM100 NSM100 Normal cluster_A::> -
Show the shelf connectivity for the switch-attached NVMe shelves:
storage shelf show -shelf <shelf_name> -connectivityShow example
cluster_A::> storage shelf show -shelf 0 -connectivity Shelf Name: 1.0 Stack ID: 1 Shelf ID: 0 Shelf UID: 00:00:00:00:00:00:00:00 Serial Number: 952123456789 Module Type: NSM100 Model: NS224NSM100 Shelf Vendor: NETAPP Disk Count: 24 Connection Type: NVMe Shelf State: Online Status: Normal Paths: Controller Initiator Initiator Side Switch Port Target Side Switch Port Target Port TPGN ------------------ --------- -------------------------- -------------------------- ------------------ ------ cluster_A-01 0x - 0x 05000005abff0000 67 cluster_A-02 0x - 0x 030f0005abff0000 44 cluster_A::> -
If required, collect the remote-device (MetroCluster switch) names:
Show example
cluster_A::> storage shelf port show -fields remote-device shelf id remote-device ----- -- ------------- 1.0 0 IP_switch_A_1 1.0 1 IP_switch_B_1 1.0 2 IP_switch_A_2 1.0 3 IP_switch_B_2 4 entries were displayed
-
Show the shelf port connectivity for the switch-attached NVMe shelves:
storage shelf port show -remote-device <switch name>Show example
cluster_A::> storage shelf port show -remote-device IP_switch_A_1 Shelf ID Module State Internal? ----- -- ------ ------------ --------- 1.0 1 A connected false 3 B connected false 1.2 1 A connected false 3 B connected false 4 entries were displayed. cluster_A::>
-
-
Move the cluster LIFs before you begin the upgrade.
-
If you are upgrading the firmware on Cisco or Broadcom MetroCluster IP switches, you can save a copy of the current switch configuration before proceeding with the upgrade.
If your workflow requires you to reset the switch in order to upgrade the RCF after the firmware upgrade, you can skip this step because the reset clears the saved switch configuration. CiscoSave the configuration:
copy running-config startup-configBroadcomSave the configuration:
write memory -
Install the software on the first switch.
You must install the switch software on the switches in the following order: switch_A_1, switch_B_1, switch_A_2, switch_B_2. Follow the steps for installing switch software in the relevant topic depending on whether the switch type is Broadcom, Cisco, or NVIDIA:
-
Repeat the previous steps for each of the switches.
After you have configured the switches in the first fabric (Switch_A_1, Switch_B_1), you must repeat the steps to move the cluster LIFs on the second fabric (Switch_A_2, Switch_B_2). Refer to Learn about configuring the MetroCluster IP switches. -
Repeat Step 1 to check the health of the configuration.