Skip to main content
Install and maintain

Upgrade your Reference Configuration File (RCF)

Contributors netapp-yvonneo
PDFs

You upgrade your RCF version when you have an existing version of the RCF file installed on your operational switches.

Before you begin

Make sure you have the following:

  • A current backup of the switch configuration.

  • A fully functioning cluster (no errors in the logs or similar issues).

  • The current RCF.

  • If you are updating your RCF version, you need a boot configuration in the RCF that reflects the desired boot images.

    If you need to change the boot configuration to reflect the current boot images, you must do so before reapplying the RCF so that the correct version is included in future reboots.

Caution Before installing a new switch software version and RCFs, you must erase the switch settings and perform basic configuration. You must be connected to the switch using the serial console or have preserved basic configuration information before erasing the switch settings.

Step 1: Prepare for the upgrade

  1. If AutoSupport is enabled on this cluster, suppress automatic case creation by invoking an AutoSupport message:

    system node autosupport invoke -node * -type all -message MAINT=xh

    Where x is the duration of the maintenance window in hours.

  2. Change the privilege level to advanced, entering y when prompted to continue:

    set -privilege advanced

    The advanced prompt (*>) appears.

  3. Display the ports on each node that are connected to the switches:

    network device-discovery show
    Show example 
    cluster1::*> network device-discovery show
Node/       Local  Discovered
Protocol    Port   Device (LLDP: ChassisID) Interface       Platform
----------- ------ ------------------------ --------------- ---------
cluster1-01/cdp
            e5a    s1                       Ethernet1/7     N3K-C3232C
            e3b    s2                       Ethernet1/7     N3K-C3232C
cluster1-02/cdp
            e5a    s1                       Ethernet1/8     N3K-C3232C
            e3b    s2                       Ethernet1/8     N3K-C3232C
.
.

  4. Check the administrative or operational status of each node storage port and storage shelf port.

    1. Verify that all the node storage ports are up with a healthy status:

      storage port show -port-type ENET
      Show example 
      cluster1::*> storage port show -port-type ENET


                                      Speed
Node               Port Type  Mode    (Gb/s) State    Status
------------------ ---- ----- ------- ------ -------- -----------
cluster1-01
                   e5a ENET  -         100   enabled  online
                   e3b ENET  -         100   enabled  online
cluster1-02
                   e5a ENET  -         100   enabled  online
                   e3b ENET  -         100   enabled  online
.
.

    2. Verify that all the storage shelf ports are up with a healthy status:

      storage shelf port show
      Show example 
      cluster1::> storage shelf port show

Shelf ID Module State        Internal?
----- -- ------ ------------ ---------
1.4
       0 A      connected    false
       1 A      connected    false
       2 B      connected    false
       3 B      connected    false
.
.

    3. Verify that the switches are being monitored.

      system switch ethernet show
      Show example 
      cluster1::*> system switch ethernet show
  Switch            Type               Address          Model
  ----------------- ------------------ ---------------- ---------------
  s1                storage-network    1.2.3.4          N3K-C3232C
     Serial Number: FFFXXXXXXX1
      Is Monitored: true
            Reason: None
  Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                    10.3(4a)
    Version Source: CDP/ISDP
  s2                storage-network    2.3.4.5          N3K-C3232C
     Serial Number: FEEXXXXXXX2
      Is Monitored: true
            Reason: None
  Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                    10.3(4a)
    Version Source: CDP/ISDP

Step 2: Upgrade the RCF

  1. Log in to switch s2 using SSH or by using a serial console.

  2. Shut down the ports connected to all of the ports of the nodes.

    s2> enable
s2# configure
s2(config)# interface e1/1-32
s2(config-if-range)# shutdown
s2(config-if-range)# exit
s2(config)# exit
    Caution Make sure to shutdown all connected ports to avoid any network connection issues. See the Knowledge Base article Node out of quorum when migrating cluster LIF during switch OS upgrade for further details.

  3. If you have not already done so, save a copy of the current switch configuration by copying the output of the following command to a text file:

    show running-config

    1. Record any custom additions between the current running-config and the RCF file in use (such as an SNMP configuration for your organization).

    2. For NX-OS 10.2 and later, use the show diff running-config command to compare with the saved RCF file in the bootflash. Otherwise, use a third-party diff or compare tool.

  4. Save basic configuration details to the write_erase.cfg file on the bootflash.

    Note

    Make sure to configure the following:

    • Username and password

    • Management IP address

    • Default gateway

    • Switch name

    s2# show run | section "switchname" > bootflash:write_erase.cfg

    s2# show run | section "hostname" >> bootflash:write_erase.cfg

    s2# show run | i "username admin password" >> bootflash:write_erase.cfg

    s2# show run | section "vrf context management" >> bootflash:write_erase.cfg

    s2# show run | section "interface mgmt0" >> bootflash:write_erase.cfg

    See the Knowledge Base article How to clear configuration on a Cisco interconnect switch while retaining remote connectivity for further details.

  5. Verify that the write_erase.cfg file is populated as expected:

    show file bootflash:write_erase.cfg

  6. Issue the write erase command to erase the current saved configuration:

    s2# write erase

    Warning: This command will erase the startup-configuration.

    Do you wish to proceed anyway? (y/n) [n] y

  7. Copy the previously saved basic configuration into the startup configuration.

    s2# copy bootflash:write_erase.cfg startup-config

  8. Reboot the switch:

    s2# reload

    This command will reboot the system. (y/n)? [n] y

  9. After the management IP address is reachable again, log in to the switch through SSH.

    You might need to update host file entries related to the SSH keys.

  10. Copy the RCF to the bootflash of switch s2 using one of the following transfer protocols: FTP, TFTP, SFTP, or SCP.

    For more information on Cisco commands, see the appropriate guide in the Cisco Nexus 3000 Series NX-OS Documentation.

    Show example

    This example shows TFTP being used to copy an RCF to the bootflash on switch s2:

    s2# copy tftp: bootflash: vrf management
Enter source filename: NX3232C-RCF-v1.13-1-Storage.txt
Enter hostname for the tftp server: 172.22.201.50
Trying to connect to tftp server......Connection to Server Established.
TFTP get operation was successful
Copy complete, now saving to disk (please wait)...

  11. Apply the RCF previously downloaded to the bootflash.

    For more information on Cisco commands, see the appropriate guide in the Cisco Nexus 3000 Series documentation.

    This example shows the RCF file NX3232C-RCF-v1.13-1-Storage.txt being installed on switch s2:

    s2# copy NX3232C-RCF-v1.13-1-Storage.txt running-config echo-commands
    Caution

    Make sure to thoroughly read the Installation notes, Important Notes, and banner sections of your RCF. You must read and follow these instructions to ensure the proper configuration and operation of the switch.

  12. Verify that the RCF file is the correct newer version:

    show running-config

    When you check the output to verify you have the correct RCF, make sure that the following information is correct:

    • The RCF banner

    • The node and port settings

    • Customizations

      The output varies according to your site configuration. Check the port settings and refer to the release notes for any changes specific to the RCF that you have installed.

  13. Reapply any previous customizations to the switch configuration.

  14. After you verify the RCF versions, custom additions, and switch settings are correct, copy the running-config file to the startup-config file.

    For more information on Cisco commands, see the appropriate guide in the Cisco Nexus 9000 Series documentation.

    s2# copy running-config startup-config

    [] 100% Copy complete

  15. Reboot switch s2. You can ignore the “cluster switch health monitor” alerts and “cluster ports down” events reported on the nodes while the switch reboots.

    s2# reload

    This command will reboot the system. (y/n)? [n] y

  16. Check the administrative or operational status of each node storage port and storage shelf port.

    1. Verify that all the storage ports are up with a healthy status:

      storage port show -port-type ENET
      Show example 
      cluster1::*> storage port show -port-type ENET


                                      Speed
Node               Port Type  Mode    (Gb/s) State    Status
------------------ ---- ----- ------- ------ -------- -----------
cluster1-01
                   e5a  ENET  -          100 enabled  online
                   e3b  ENET  -          100 enabled  online
cluster1-02
                   e5a  ENET  -          100 enabled  online
                   e3b  ENET  -          100 enabled  online
.
.

    2. Verify that all the storage shelf ports are up with a healthy status:

      storage shelf port show
      Show example 
      cluster1::> storage shelf port show

Shelf ID Module State        Internal?
----- -- ------ ------------ ---------
1.4
       0 A      connected    false
       1 A      connected    false
       2 B      connected    false
       3 B      connected    false
.
.

    3. Verify that the switches are being monitored:

      system switch ethernet show
      Show example 
      cluster1::*> system switch ethernet show
  Switch           Type               Address          Model
  ---------------- ------------------ ---------------- ---------------
  s1               storage-network    1.2.3.4          N3K-C3232C
     Serial Number: FFFXXXXXXX1
      Is Monitored: true
            Reason: None
  Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                    10.3(4a)
    Version Source: CDP/ISDP
  s2               storage-network    2.3.4.5          N3K-C3232C
     Serial Number: FEEXXXXXXX2
      Is Monitored: true
            Reason: None
  Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                    10.3(4a)
    Version Source: CDP/ISDP

  17. Repeat steps 1 to 16 on switch s1.

Step 3: Verify the storage network

Complete the following steps on each storage switch to verify that the storage network is functioning properly after the RCF upgrade.

  1. Verify that the switch ports are up.

    show interface brief

  2. Verify that the expected node storage ports are still connected:

    show cdp neighbors

  3. Verify that the expected storage shelf ports are still connected:

    show lldp neighbors

  4. Verify that the node storage ports and storage shelf ports are in their correct VLANs using the following commands:

    show vlan brief
    show interface trunk
What's next?

After you've upgraded your RCF, you can verify the SSH configuration.