Skip to main content
ONTAP MetroCluster

Upgrade firmware on MetroCluster IP switches

Contributors netapp-aoife netapp-martyh netapp-folivia netapp-thomi netapp-ranuk
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.

Steps

  1. 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 clibanner

    Cisco switch

    IP_switch_A_1# show banner motd

    NVIDIA SN2100 switch

    cumulus@mcc1:mgmt:~$ nv config find message

    Locate 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

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

  3. To verify that the switch firmware is supported, refer to the following:

Upgrade the switch firmware

About this task

You must repeat this task on each of the switches in succession.

Enable console logging before performing this task.

Steps

  1. Check the health of the configuration.

    1. Check that the MetroCluster is configured and in normal mode on each cluster:

      metrocluster show

      cluster_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

    2. Check that mirroring is enabled on each node:

      metrocluster node show

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

    3. Check that the MetroCluster components are healthy:

      metrocluster check run

      cluster_A::*> metrocluster check run

      The operation runs in the background.

    4. After the metrocluster check run operation completes, run:

      metrocluster check show

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

    5. Check that there are no health alerts:

      system health alert show

  2. Install the software on the first switch.

    Note 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:

  3. Repeat the previous step for each of the switches.

  4. Repeat Step 1 to check the health of the configuration.