Prepare to install NX-OS software and RCF
Before you install the NX-OS software and the Reference Configuration File (RCF), follow this procedure.
-
Consult the switch compatibility table for the supported ONTAP and NX-OS versions.
-
Software Upgrade and downgrade guides
Refer to the appropriate software and upgrade guides available on the Cisco website for complete documentation on the Cisco switch upgrade and downgrade procedures.
-
Cisco Nexus 9000 and 3000 Upgrade and ISSU Matrix
Provides information on Disruptive Upgrade/Downgrade for Cisco NX-OS software on Nexus 9000 Series Switches based on your current and target releases.
On the page, select Disruptive Upgrade and select your current release and target release from the dropdown list.
The examples in this procedure use the following switch and node nomenclature:
-
The names of the two Cisco switches are cs1 and cs2.
-
The node names are cluster1-01 and cluster1-02.
-
The cluster LIF names are cluster1-01_clus1 and cluster1-01_clus2 for cluster1-01 and cluster1-02_clus1 and cluster1-02_clus2 for cluster1-02.
-
The
cluster1::*>
prompt indicates the name of the cluster.
The procedure requires the use of both ONTAP commands and Cisco Nexus 9000 Series Switches commands; ONTAP commands are used unless otherwise indicated.
-
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=x h
where x is the duration of the maintenance window in hours.
The AutoSupport message notifies technical support of this maintenance task so that automatic case creation is suppressed during the maintenance window. -
Change the privilege level to advanced, entering y when prompted to continue:
set -privilege advanced
The advanced prompt (
*>
) appears. -
Display how many cluster interconnect interfaces are configured in each node for each cluster interconnect switch:
network device-discovery show -protocol cdp
Show example
cluster1::*> network device-discovery show -protocol cdp Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ----------------- -------- cluster1-02/cdp e0a cs1 Eth1/2 N9K-C9336C e0b cs2 Eth1/2 N9K-C9336C cluster1-01/cdp e0a cs1 Eth1/1 N9K-C9336C e0b cs2 Eth1/1 N9K-C9336C 4 entries were displayed.
-
Check the administrative or operational status of each cluster interface.
-
Display the network port attributes:
network port show -ipspace Cluster
Show example
cluster1::*> network port show -ipspace Cluster Node: cluster1-02 Speed(Mbps) Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy e0b Cluster Cluster up 9000 auto/10000 healthy Node: cluster1-01 Speed(Mbps) Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status --------- ------------ ---------------- ---- ---- ----------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy e0b Cluster Cluster up 9000 auto/10000 healthy 4 entries were displayed.
-
Display information about the LIFs:
network interface show -vserver Cluster
Show example
cluster1::*> network interface show -vserver Cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ------------------ ---------- ------------------ ------------- ------- ---- Cluster cluster1-01_clus1 up/up 169.254.209.69/16 cluster1-01 e0a true cluster1-01_clus2 up/up 169.254.49.125/16 cluster1-01 e0b true cluster1-02_clus1 up/up 169.254.47.194/16 cluster1-02 e0a true cluster1-02_clus2 up/up 169.254.19.183/16 cluster1-02 e0b true 4 entries were displayed.
-
-
Verify the connectivity of the remote cluster interfaces:
You can use the network interface check cluster-connectivity
command to start an accessibility check for cluster connectivity and then display the details:
network interface check cluster-connectivity start
and network interface check cluster-connectivity show
cluster1::*> network interface check cluster-connectivity start
NOTE: Wait for a number of seconds before running the show
command to display the details.
cluster1::*> network interface check cluster-connectivity show Source Destination Packet Node Date LIF LIF Loss ------ -------------------------- -------------------- ------------------- ----------- node1 3/5/2022 19:21:18 -06:00 cluster1-01_clus2 cluster1-02-clus1 none 3/5/2022 19:21:20 -06:00 cluster1-01_clus2 cluster1-02_clus2 none node2 3/5/2022 19:21:18 -06:00 cluster1-02_clus2 cluster1-01_clus1 none 3/5/2022 19:21:20 -06:00 cluster1-02_clus2 cluster1-01_clus2 none
For all ONTAP releases, you can also use the cluster ping-cluster -node <name>
command to check the connectivity:
cluster ping-cluster -node <name>
cluster1::*> cluster ping-cluster -node local Host is cluster1-02 Getting addresses from network interface table... Cluster cluster1-01_clus1 169.254.209.69 cluster1-01 e0a Cluster cluster1-01_clus2 169.254.49.125 cluster1-01 e0b Cluster cluster1-02_clus1 169.254.47.194 cluster1-02 e0a Cluster cluster1-02_clus2 169.254.19.183 cluster1-02 e0b Local = 169.254.47.194 169.254.19.183 Remote = 169.254.209.69 169.254.49.125 Cluster Vserver Id = 4294967293 Ping status: Basic connectivity succeeds on 4 path(s) Basic connectivity fails on 0 path(s) Detected 9000 byte MTU on 4 path(s): Local 169.254.19.183 to Remote 169.254.209.69 Local 169.254.19.183 to Remote 169.254.49.125 Local 169.254.47.194 to Remote 169.254.209.69 Local 169.254.47.194 to Remote 169.254.49.125 Larger than PMTU communication succeeds on 4 path(s) RPC status: 2 paths up, 0 paths down (tcp check) 2 paths up, 0 paths down (udp check)
-
Verify that the auto-revert command is enabled on all cluster LIFs:
network interface show -vserver Cluster -fields auto-revert
Show example
cluster1::*> network interface show -vserver Cluster -fields auto-revert Logical Vserver Interface Auto-revert --------- ------------------- ------------ Cluster cluster1-01_clus1 true cluster1-01_clus2 true cluster1-02_clus1 true cluster1-02_clus2 true 4 entries were displayed.
After you've prepared to install the NX-OS software and RCF, you install or upgrade the NX-OS software.