Upgrade the RCF version - Cisco Nexus 9808
Suggest changes
PDFs
You upgrade the reference configuration file (RCF) version on your Cisco Nexus 9808 switches to support new hardware, a new ONTAP version, or to align with a new NX-OS version in your AFX 2K system configuration.
|
Do not upgrade or downgrade your RCF version to an unsupported version. |
-
You must have read the Install or upgrade RCF overview page.
-
You must be connected to the switches using the serial console or have preserved basic configuration information. This is because the RCF upgrade procedure requires you to erase the switch settings and perform basic configuration.
-
Make sure you have a current backup of the switch configuration.
-
Verify that your cluster is fully functional, meaning that there are no errors in the logs or similar issues.
-
You must have the current 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 instantiated on future reboots.
-
Upgrading the RCF on both of the switches is a nondisruptive procedure.
-
No operational inter-switch link (ISL) is needed during this procedure. This is by design because RCF version changes can affect ISL connectivity temporarily. To ensure non-disruptive cluster operations, this procedure has you migrate all of the cluster LIFs to the operational partner switch while performing the steps on the target switch.
-
This procedure has you upgrade the RCF on the first switch (cs1) and then has you repeat the steps for the second switch (cs2).
-
-
This procedure requires the use of ONTAP commands and Cisco Nexus 9000 Series Switches commands, the steps indicate which CLI you are using to enter commands.
-
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 node1-01, node1-02, node1-03, and node1-04.
-
The cluster LIF names are:
-
node1-01_clus1 and node1-01_clus2 for node1-01
-
node1-02_clus1 and node1-02_clus2 for node1-02
-
node1-03_clus1 and node1-03_clus2 for node1-03
-
node1-04_clus1 and node1-04_clus2 for node1-04
-
-
The
cluster1::*>prompt indicates the name of the cluster.
-
Step 1: Prepare for the upgrade
You enter the commands for the following steps from the ONTAP CLI.
-
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=xhwhere x is the duration of the maintenance window in hours.
-
Change the privilege level to advanced, entering y when prompted to continue:
set -privilege advancedThe advanced prompt (*>) appears.
-
Display the ports on each node that are connected to the switches:
network device-discovery showShow example
cluster1::*> network device-discovery show Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ---------------- ---------------- node1-01/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/5 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/14 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/7 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/16 N9K-C9808 e2a cs1(FOXXXXXXXXX) Ethernet1/3 N9K-C9808 e2b cs2(FOXXXXXXXXX) Ethernet1/12 N9K-C9808 node1-01/lldp e10a cs1 (ec:bb:78:9e:c7:e8) Ethernet1/5 - e10b cs2 (ec:bb:78:9e:c8:0c) Ethernet1/14 - e8a cs1 (ec:bb:78:9e:c7:f0) Ethernet1/7 - e8b cs2 (ec:bb:78:9e:c8:14) Ethernet1/16 - e1a cs1 (ec:bb:78:9e:c7:d8) Ethernet1/1 - e1b cs2 (ec:bb:78:9e:c7:fc) Ethernet1/10 - e2a cs1 (ec:bb:78:9e:c7:e0) Ethernet1/3 - e2b cs2 (ec:bb:78:9e:c8:04) Ethernet1/12 - node1-02/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/6 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/15 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/8 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/17 N9K-C9808 e2a cs1(FOXXXXXXXXXX) Ethernet1/2 N9K-C9808 e2b cs2(FOX3005Q66Q) Ethernet1/13 N9K-C9808 node1-02/lldp e10a cs1 (ec:bb:78:9e:c7:ec) Ethernet1/6 - e10b cs2 (ec:bb:78:9e:c8:10) Ethernet1/15 - e8a cs1 (ec:bb:78:9e:c7:f4) Ethernet1/8 - e8b cs2 (ec:bb:78:9e:c8:18) Ethernet1/17 - e1a cs1 (ec:bb:78:9e:c7:dc) Ethernet1/2 - e1b cs2 (ec:bb:78:9e:c8:00) Ethernet1/11 - e2a cs1 (ec:bb:78:9e:c7:e4) Ethernet1/4 - e2b cs2 (ec:bb:78:9e:c8:08) Ethernet1/13 - . . . -
Check the administrative and operational status of each port.
-
Cluster ports
-
Verify that all the cluster ports are up with a healthy status:
network port show -ipspace ClusterShow example
cluster1::*> network port show -ipspace Cluster Node: node1-01 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-02 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-03 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-04 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false -
Verify that all the cluster interfaces (LIFs) are on the home port:
network interface show -role clusterShow example
cluster1::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ------------------ ---------- ----------------- ------------ ------- ---- Cluster node1-01_clus1 up/up 169.254.3.4/23 node1-01 e2a true node1-01_clus2 up/up 169.254.3.5/23 node1-01 e2b true node1-02_clus1 up/up 169.254.3.8/23 node1-02 e2a true node1-02_clus2 up/up 169.254.3.9/23 node1-02 e2b true node1-03_clus1 up/up 169.254.1.3/23 node1-03 e2a true node1-03_clus2 up/up 169.254.1.1/23 node1-03 e2b true node1-04_clus1 up/up 169.254.1.6/23 node1-04 e2a true node1-04_clus2 up/up 169.254.1.7/23 node1-04 e2b true -
Verify that the cluster displays information for both switches:
system cluster-switch show -is-monitoring-enabled-operational trueShow example
cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true Switch Type Address Model --------------------------- ------------------ ---------------- --------------- cs2(FDOXXXXXXXX) cluster-network 10.228.137.233 N9K-C9808 Serial Number: FDOXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.5(3)(F) Version Source: CDP/ISDP cs1(FOXXXXXXXXX) cluster-network 10.228.137.234 N9K-C9808 Serial Number: FOXXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.5(3)(F) Version Source: CDP/ISDP
-
-
HA ports
-
Verify that all the HA ports are up with a healthy status:
ha interconnect status show -node <node-name>Show example
cluster1::*> ha interconnect status show -node node1-01 (system ha interconnect status show) Node: node1-01 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE cluster1::*> ha interconnect status show -node node1-02 (system ha interconnect status show) Node: node1-02 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE . . . -
Verify that all the HA ports are correctly configured and that the interconnect type is RoCE:
ha interconnect config showShow example
cluster1::*> ha interconnect config show (system ha interconnect config show) Node: node1-01 Interconnect Type: RoCE Local System ID: 542023071 Partner System ID: 542022984 Connection Initiator: local Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.111 0x0 e1b-18 169.254.18.242 0x0 Node: node1-02 Interconnect Type: RoCE Local System ID: 542022984 Partner System ID: 542023071 Connection Initiator: partner Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.208 0x0 e1b-18 169.254.18.169 0x0 . . .
-
-
Storage ports
-
Verify that all the storage ports are up with a healthy status:
storage port show -port-type ENETShow example
cluster1::*> storage port show -port-type ENET Speed Node Port Type Mode (Gb/s) State Status ------------------ ---- ----- ------- ------ -------- ----------- node1-01 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-02 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-03 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-04 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline
-
-
Storage shelf ports
-
Verify that all the storage shelf ports are up with a healthy status:
storage shelf port showShow example
cluster1::*> storage shelf port show Shelf ID Module State Internal? ----- -- ------ ------------ --------- 1.0 0 A connected false 1 A connected false 2 A connected false 3 A connected false 4 A connected false 5 A connected false 6 A connected false 7 A connected false 8 B connected false 9 B connected false 10 B connected false 11 B connected false 12 B connected false 13 B connected false 14 B connected false 15 B connected false -
Verify that all the storage shelf ports are up with a healthy status:
storage shelf port show -fields remote-device,remote-port,connector-stateShow example
cluster1::*> storage shelf port show -fields remote-device,remote-port,connector-state shelf id connector-state remote-port remote-device ----- -- --------------- -------------- ----------------- 1.1 0 connected Ethernet1/17/1 cs1(FOXXXXXXXXX) 1.1 1 connected Ethernet1/15/1 cs2(FDOXXXXXXXX) 1.1 2 connected Ethernet1/17/2 cs1(FOXXXXXXXXX) 1.1 3 connected Ethernet1/15/2 cs2(FDOXXXXXXXX) 1.1 4 connected Ethernet1/17/3 cs1(FOXXXXXXXXX) 1.1 5 connected Ethernet1/15/3 cs2(FDOXXXXXXXX) 1.1 6 connected Ethernet1/17/4 cs1(FOXXXXXXXXX) 1.1 7 connected Ethernet1/15/4 cs2(FDOXXXXXXXX) 1.1 8 connected Ethernet1/19/1 cs1(FOXXXXXXXXX) 1.1 9 connected Ethernet1/17/1 cs2(FDOXXXXXXXX) 1.1 10 connected Ethernet1/19/2 cs1(FOXXXXXXXXX) 1.1 11 connected Ethernet1/17/2 cs2(FDOXXXXXXXX) 1.1 12 connected Ethernet1/19/3 cs1(FOXXXXXXXXX) 1.1 13 connected Ethernet1/17/3 cs2(FDOXXXXXXXX) 1.1 14 connected Ethernet1/19/4 cs1(FOXXXXXXXXX) 1.1 15 connected Ethernet1/17/4 cs2(FDOXXXXXXXX)
-
-
-
Disable auto-revert on the cluster LIFs. The cluster LIFs fail over to the partner cluster switch and remain there as you perform this procedure on the targeted switch:
network interface modify -vserver Cluster -lif * -auto-revert false
Step 2: Configure ports
-
Using the switch CLI, on switch cs1, shut down the ports connected to all the ports of the nodes for each line card.
The following example shows the commands to shut down all the ports on line card 1
e1,e1-1/1-18,e1/19/1-4,e1/20/1-4………e1/35/1-4. Repeat the commands for each line card on the switch.cs1# config terminal Enter configuration commands, one per line. End with CNTL/Z. cs1(config)# interface e1/1-18 cs1(config-if-range)# shutdown cs1(config)# interface e1/19/1-4,e1/20/1-4,e1/21/1-4,e1/22/1-4,e1/23/1-4,e1/24/1-4,e1/25/1-4,e1/26/1-4,e1/27/1-4,e1/28/1-4,e1/29/1-4,e1/30/1-4,e1/31/1-4,e1/32/1-4,e1/33/1-4,e1/34/1-4,e1/35/1-4 cs1(config-if-range)# shutdown cs1(config-if-range)# exit cs1(config)# exit
Make sure to shutdown all connected ports to avoid any network connection issues. Refer to the Knowledge Base article Node out of quorum when migrating cluster LIF during switch OS upgrade for further details. -
Using the ONTAP CLI, verify that the cluster LIFs have failed over to the ports hosted on switch cs1. This might take a few seconds.
network interface show -role clusterShow example
cluster1::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- --------------- ---------- ------------------ ----------- ------- ---- Cluster node1-01_clus1 up/up 169.254.36.44/16 node1-01 e2a true node1-01_clus2 up/up 169.254.7.5/16 node1-01 e2b true node1-02_clus1 up/up 169.254.197.206/16 node1-02 e2a true node1-02_clus2 up/up 169.254.195.186/16 node1-02 e2b true node1-03_clus1 up/up 169.254.192.49/16 node1-03 e2a true node1-03_clus2 up/up 169.254.182.76/16 node1-03 e2b true node1-04_clus1 up/up 169.254.59.49/16 node1-04 e2a true node1-04_clus2 up/up 169.254.62.244/16 node1-04 e2b true 8 entries were displayed. -
Using the ONTAP CLI, verify that the cluster is healthy:
cluster showShow example
cluster1::*> cluster show Node Health Eligibility Epsilon ----------------- ------- ------------ ------- node1-01 true true false node1-02 true true false node1-03 true true true node1-04 true true false
-
If you have not already done so, using the switch CLI, save a copy of the current switch configuration by copying the output of the following command to a text file:
show running-config-
Use the
show diff running-configcommand to compare with the saved RCF file in the bootflash. Otherwise, use a third-party diff/compare tool.
-
-
Save basic configuration details to the
write_erase.cfgfile on the bootflash.
Make sure to configure the following:
-
Username and password
-
Management IP address
-
Default gateway
-
Switch name
If the
write_erase.cfgfile already exists, rename it towrite_erase_old.cfg, as follows:cs1# move bootflash:write_erase.cfg write_erase_old.cfgcs1# show run | i "username admin password" > bootflash:write_erase.cfgcs1# show run | section "vrf context management" >> bootflash:write_erase.cfgcs1# show run | section "interface mgmt0" >> bootflash:write_erase.cfgcs1# show run | section "switchname" >> bootflash:write_erase.cfgRefer to the Knowledge Base article How to clear configuration on a Cisco interconnect switch while retaining remote connectivity for further details.
-
-
Using the switch CLI, verify that the
write_erase.cfgfile is populated as expected:show file bootflash:write_erase.cfg -
Using the switch CLI, issue the
write erasecommand to erase the current saved configuration:cs1# write eraseWarning: This command will erase the startup-configuration.Do you wish to proceed anyway? (y/n) [n] y -
Using the switch CLI, copy the previously saved basic configuration into the startup configuration.
cs1# copy bootflash:write_erase.cfg startup-config -
Using the switch CLI, reboot the switch:
cs1# reloadThis command will reboot the system. (y/n)? [n] y -
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.
-
Using the switch CLI, copy the RCF to the bootflash of switch cs1 using one of the following transfer protocols: FTP, TFTP, SFTP, or SCP.
For more information on Cisco commands, refer to the appropriate guide in the Cisco Nexus 9000 Series NX-OS Command Reference guides.
copy <protocol>: bootflash: vrf managementShow example
This example shows TFTP being used to copy an RCF to the bootflash on switch cs1:
cs1# copy tftp: bootflash: vrf management Enter source filename: RCF-v10.1-NX9808-CL1-ST1.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)...
-
Using the switch CLI, apply the RCF previously downloaded to the bootflash.
For more information on Cisco commands, refer to the appropriate guide in the Cisco Nexus 9000 Series NX-OS Command Reference guides.
This example shows the RCF
RCF-v10.1-NX9808-CL1-ST1.txtbeing installed on switch cs1:cs1# copy RCF-v10.1-NX9808-CL1-ST1.txt running-config echo-commands
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.
-
Using the switch CLI, verify that the RCF is the correct newer version:
show running-configWhen 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.
-
-
Reapply any previous customizations to the switch configuration.
If your switches are running RCF 10.1 or later, you can change the port speed configuration if needed.
-
Using the switch CLI, after you verify the RCF versions, custom additions, and switch settings are correct, copy the
running-configfile to thestartup-configfile.For more information on Cisco commands, refer to the appropriate guide in the Cisco Nexus 9000 Series NX-OS Command Reference guides.
cs1# copy running-config startup-config[] 100% Copy complete -
Using the switch CLI, reboot switch cs1. You can ignore the “cluster switch health monitor” alerts and “cluster ports down” events reported on the nodes while the switch reboots.
cs1# reloadThis command will reboot the system. (y/n)? [n] y -
Using the ONTAP CLI, verify the health of all the ports on the cluster.
-
Cluster ports
-
Verify that cluster ports are up and healthy across all nodes in the cluster:
network port show -ipspace ClusterShow example
cluster1::*> network port show -ipspace Cluster Node: node1 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-02 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-03 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-04 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false -
Verify the switch health from the cluster.
network device-discovery show -protocol cdpsystem cluster-switch show -is-monitoring-enabled-operational trueShow example
cluster1::*> network device-discovery show -protocol cdp Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ---------------- ---------------- node1-01/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/5 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/14 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/7 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/16 N9K-C9808 e2a cs1(FOXXXXXXXXX) Ethernet1/3 N9K-C9808 e2b cs2(FOXXXXXXXXX) Ethernet1/12 N9K-C9808 node1-02/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/6 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/15 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/8 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/17 N9K-C9808 e2a cs1(FOXXXXXXXXXX) Ethernet1/2 N9K-C9808 e2b cs2(FOX3005Q66Q) Ethernet1/13 N9K-C9808 . . . cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true Switch Type Address Model --------------------------- ------------------ ---------------- --------------- cs2(FDOXXXXXXXX) cluster-network 10.228.137.233 N9K-C9808 Serial Number: FDOXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.6(3)(F) Version Source: CDP/ISDP cs1(FOXXXXXXXXX) cluster-network 10.228.137.234 N9K-C9808 Serial Number: FOXXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.6(3)(F) Version Source: CDP/ISDP
-
-
HA ports
-
Verify that all the HA ports are up with a healthy status:
ha interconnect status show -node <node-name>Show example
cluster1::*> ha interconnect status show -node node1-01 (system ha interconnect status show) Node: node1-01 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE cluster1::*> ha interconnect status show -node node1-02 (system ha interconnect status show) Node: node1-02 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE . . . -
Verify that all the HA ports are correctly configured and that the interconnect type is RoCE:
ha interconnect config showShow example
cluster1::*> ha interconnect config show (system ha interconnect config show) Node: node1-01 Interconnect Type: RoCE Local System ID: 542023071 Partner System ID: 542022984 Connection Initiator: local Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.111 0x0 e1b-18 169.254.18.242 0x0 Node: node1-02 Interconnect Type: RoCE Local System ID: 542022984 Partner System ID: 542023071 Connection Initiator: partner Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.208 0x0 e1b-18 169.254.18.169 0x0 . . .
-
-
Storage ports
-
Verify that all the storage ports are up with a healthy status:
storage port show -port-type ENETShow example
cluster1::*> storage port show -port-type ENET Speed Node Port Type Mode (Gb/s) State Status ------------------ ---- ----- ------- ------ -------- ----------- node1-01 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-02 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-03 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-04 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline
-
-
Storage shelf ports
-
Verify that all the storage shelf ports are up with a healthy status:
storage shelf port showShow example
cluster1::*> storage shelf port show Shelf ID Module State Internal? ----- -- ------ ------------ --------- 1.0 0 A connected false 1 A connected false 2 A connected false 3 A connected false 4 A connected false 5 A connected false 6 A connected false 7 A connected false 8 B connected false 9 B connected false 10 B connected false 11 B connected false 12 B connected false 13 B connected false 14 B connected false 15 B connected false -
Verify the connection status of all the storage shelf ports:
storage shelf port show -fields remote-device,remote-port,connector-stateShow example
cluster1::*> storage shelf port show -fields remote-device,remote-port,connector-state shelf id connector-state remote-port remote-device ----- -- --------------- -------------- ----------------- 1.1 0 connected Ethernet1/17/1 cs1(FOXXXXXXXXX) 1.1 1 connected Ethernet1/15/1 cs2(FDOXXXXXXXX) 1.1 2 connected Ethernet1/17/2 cs1(FOXXXXXXXXX) 1.1 3 connected Ethernet1/15/2 cs2(FDOXXXXXXXX) 1.1 4 connected Ethernet1/17/3 cs1(FOXXXXXXXXX) 1.1 5 connected Ethernet1/15/3 cs2(FDOXXXXXXXX) 1.1 6 connected Ethernet1/17/4 cs1(FOXXXXXXXXX) 1.1 7 connected Ethernet1/15/4 cs2(FDOXXXXXXXX) 1.1 8 connected Ethernet1/19/1 cs1(FOXXXXXXXXX) 1.1 9 connected Ethernet1/17/1 cs2(FDOXXXXXXXX) 1.1 10 connected Ethernet1/19/2 cs1(FOXXXXXXXXX) 1.1 11 connected Ethernet1/17/2 cs2(FDOXXXXXXXX) 1.1 12 connected Ethernet1/19/3 cs1(FOXXXXXXXXX) 1.1 13 connected Ethernet1/17/3 cs2(FDOXXXXXXXX) 1.1 14 connected Ethernet1/19/4 cs1(FOXXXXXXXXX) 1.1 15 connected Ethernet1/17/4 cs2(FDOXXXXXXXX)
-
-
-
Using the ONTAP CLI, verify that the cluster is healthy:
cluster showShow example
cluster1::*> cluster show Node Health Eligibility Epsilon ----------------- -------- ------------- ------- node1-01 true true false node1-02 true true false node1-03 true true true node1-04 true true false 4 entries were displayed.
-
Repeat steps 4 to 18 on switch cs2.
-
Using the ONTAP CLI, enable auto-revert on the cluster LIFs.
network interface modify -vserver Cluster -lif * -auto-revert true
Step 3: Verify the cluster network configuration and cluster health
-
Using the switch CLI, verify that the switch ports connected to the cluster ports are up.
show interface briefShow example
cs1# show interface brief | grep up -------------------------------------------------------------------------------- Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -------------------------------------------------------------------------------- Eth1/1 1 eth trunk up none 400G(D) -- Eth1/2 1 eth trunk up none 400G(D) -- Eth1/3 1 eth trunk up none 400G(D) -- Eth1/4 1 eth trunk up none 400G(D) -- Eth1/5 1 eth trunk up none 400G(D) -- Eth1/6 1 eth trunk up none 400G(D) -- Eth1/7 1 eth trunk up none 400G(D) -- Eth1/8 1 eth trunk up none 400G(D) -- Eth1/9 1 eth trunk down XCVR not inserted auto(D) -- Eth1/10 1 eth trunk up none 400G(D) -- Eth1/11 1 eth trunk up none 400G(D) -- Eth1/12 1 eth trunk up none 400G(D) -- Eth1/13 1 eth trunk up none 400G(D) -- Eth1/14 1 eth trunk up none 400G(D) -- Eth1/15 1 eth trunk up none 400G(D) -- Eth1/16 1 eth trunk up none 400G(D) -- Eth1/17 1 eth trunk up none 400G(D) -- Eth1/18 1 eth trunk down XCVR not inserted auto(D) -- Eth1/19/1 1 eth trunk up none 100G(D) -- Eth1/19/2 1 eth trunk up none 100G(D) -- Eth1/19/3 1 eth trunk up none 100G(D) -- Eth1/19/4 1 eth trunk up none 100G(D) -- Eth1/20/1 1 eth trunk up none 100G(D) -- Eth1/20/2 1 eth trunk up none 100G(D) -- Eth1/20/3 1 eth trunk up none 100G(D) -- Eth1/20/4 1 eth trunk up none 100G(D) -- . . . Eth1/30/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/30/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/30/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/30/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/36 1 eth trunk down XCVR not inserted auto(D) 1 ------------------------------------------------------------------------------------ Port-channel VLAN Type Mode Status Reason Speed Protocol Interface ------------------------------------------------------------------------------------ Po1 1 eth trunk down No operational members auto(D) lacp Po998 1 eth access down Administratively down auto(I) none Po999 1 eth access down Administratively down auto(I) none
-
Using the switch CLI, verify that the expected nodes are still connected:
show cdp neighborsshow lldp neighborsShow example
cs1# show cdp neighbors Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge S - Switch, H - Host, I - IGMP, r - Repeater, V - VoIP-Phone, D - Remotely-Managed-Device, s - Supports-STP-Dispute Device-ID Local Intrfce Hldtme Capability Platform Port ID cs1 Eth1/3 179 H AFX-2K e7a cs2 Eth1/4 123 H AFX-2K e7a cs1 Eth1/5 179 H AFX-2K e10a cs2 Eth1/6 123 H AFX-2K e10a cs1 Eth1/7 179 H AFX-2K e11a cs2 Eth1/8 123 H AFX-2K e11a cs1 Eth1/12 179 H AFX-2K e7b cs2 Eth1/13 123 H AFX-2K e7b cs1 Eth1/14 179 H AFX-2K e10b cs2 Eth1/15 123 H AFX-2K e10b cs1 Eth1/16 179 H AFX-2K e11b cs2 Eth1/17 123 H AFX-2K e11b cs1# show lldp neighbors Capability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other Device ID Local Intf Hold-time Capability Port ID cs1 Eth1/1 121 S e1a cs2 Eth1/2 121 S e1a cs1 Eth1/3 121 S e7a cs2 Eth1/4 121 S e7a cs1 Eth1/5 121 S e10a cs2 Eth1/6 121 S e10a cs1 Eth1/7 121 S e11a cs2 Eth1/8 121 S e11a cs1 Eth1/10 121 S e1b cs2 Eth1/11 121 S e1b cs1 Eth1/12 121 S e7b cs2 Eth1/13 121 S e7b cs1 Eth1/14 121 S e10b cs2 Eth1/15 121 S e10b cs1 Eth1/16 121 S e11b cs2 Eth1/17 121 S e11b 952551000983 Eth1/19/1 120 S e1a 952551000983 Eth1/19/2 120 S e3a 952551000983 Eth1/19/3 120 S e1a 952551000983 Eth1/19/4 120 S e3a 952551000983 Eth1/20/1 120 S e2a 952551000983 Eth1/20/2 120 S e4a 952551000983 Eth1/20/3 120 S e2a 952551000983 Eth1/20/4 120 S e4a . . . -
Using the switch CLI, verify that the cluster nodes are in their correct cluster VLANs using the following commands:
show vlan briefshow interface trunkShow example
cs1# show vlan brief VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Po1, Po998, Po999, Eth1/1 Eth1/2, Eth1/3, Eth1/4, Eth1/5 Eth1/6, Eth1/7, Eth1/8, Eth1/9 Eth1/10, Eth1/11, Eth1/12 Eth1/13, Eth1/14, Eth1/15 Eth1/16, Eth1/17, Eth1/18 Eth1/36, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 . . Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 17 VLAN0017 active Eth1/1, Eth1/2, Eth1/3, Eth1/4 Eth1/5, Eth1/6, Eth1/7, Eth1/8 Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 Eth1/20/2, Eth1/20/3, Eth1/20/4 Eth1/21/1, Eth1/21/2, Eth1/21/3 . . Eth1/30/4, Eth1/31/1, Eth1/31/2 Eth1/31/3, Eth1/31/4, Eth1/32/1 Eth1/32/2, Eth1/32/3, Eth1/32/4 Eth1/33/1, Eth1/33/2, Eth1/33/3 Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 18 VLAN0018 active Eth1/1, Eth1/2, Eth1/3, Eth1/4 Eth1/5, Eth1/6, Eth1/7, Eth1/8 Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 . . Eth1/30/1, Eth1/30/2, Eth1/30/3 Eth1/30/4, Eth1/31/1, Eth1/31/2 Eth1/31/3, Eth1/31/4, Eth1/32/1 Eth1/32/2, Eth1/32/3, Eth1/32/4 Eth1/33/1, Eth1/33/2, Eth1/33/3 Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 30 VLAN0030 active Eth1/1, Eth1/2, Eth1/3, Eth1/4 Eth1/5, Eth1/6, Eth1/7, Eth1/8 Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 Eth1/20/2, Eth1/20/3, Eth1/20/4 . . Eth1/33/1, Eth1/33/2, Eth1/33/3 Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 40 VLAN0040 active Po1, Eth1/1, Eth1/2, Eth1/3 Eth1/4, Eth1/5, Eth1/6, Eth1/7 Eth1/8, Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/36, Eth1/19/1 Eth1/19/2, Eth1/19/3, Eth1/19/4 Eth1/20/1, Eth1/20/2, Eth1/20/3 Eth1/20/4, Eth1/21/1, Eth1/21/2 Eth1/21/3, Eth1/21/4, Eth1/22/1 Eth1/22/2, Eth1/22/3, Eth1/22/4 Eth1/23/1, Eth1/23/2, Eth1/23/3 Eth1/23/4, Eth1/24/1, Eth1/24/2 Eth1/24/3, Eth1/24/4, Eth1/25/1 Eth1/25/2, Eth1/25/3, Eth1/25/4 Eth1/26/1, Eth1/26/2, Eth1/26/3 Eth1/26/4, Eth1/27/1, Eth1/27/2 Eth1/27/3, Eth1/27/4, Eth1/28/1 . . Eth1/34/2, Eth1/34/3, Eth1/34/4 Eth1/35/1, Eth1/35/2, Eth1/35/3 Eth1/35/4 cs1# show interface trunk -------------------------------------------------------------------------------- Port Native Status Port Vlan Channel -------------------------------------------------------------------------------- Eth1/1 1 trunking -- Eth1/2 1 trunking -- Eth1/3 1 trunking -- Eth1/4 1 trunking -- Eth1/5 1 trunking -- Eth1/6 1 trunking -- Eth1/7 1 trunking -- Eth1/8 1 trunking -- Eth1/9 1 trunking -- Eth1/10 1 trunking -- . . . Eth1/30/1 1 trunking -- Eth1/30/2 1 trunking -- Eth1/30/3 1 trunking -- Eth1/30/4 1 trunking -- Eth1/31/1 1 trunking -- Eth1/31/2 1 trunking -- Eth1/31/3 1 trunking -- Eth1/31/4 1 trunking -- Eth1/32/1 1 trunking -- Eth1/32/2 1 trunking -- Eth1/32/3 1 trunking -- Eth1/32/4 1 trunking -- Eth1/33/1 1 trunking -- Eth1/33/2 1 trunking -- Eth1/33/3 1 trunking -- Eth1/33/4 1 trunking -- Eth1/34/1 1 trunking -- Eth1/34/2 1 trunking -- Eth1/34/3 1 trunking -- Eth1/34/4 1 trunking -- Eth1/35/1 1 trunking -- Eth1/35/2 1 trunking -- Eth1/35/3 1 trunking -- Eth1/35/4 1 trunking -- Eth1/36 1 trnk-bndl Po1 Po1 1 not-trunking -- -------------------------------------------------------------------------------- Port Vlans Allowed on Trunk -------------------------------------------------------------------------------- Eth1/1 1,17-18,30,40 Eth1/2 1,17-18,30,40 Eth1/3 1,17-18,30,40 Eth1/4 1,17-18,30,40 Eth1/5 1,17-18,30,40 Eth1/6 1,17-18,30,40 Eth1/7 1,17-18,30,40 Eth1/8 1,17-18,30,40 Eth1/9 1,17-18,30,40 Eth1/10 1,17-18,30,40 Eth1/11 1,17-18,30,40 . . . Eth1/30/1 1,17-18,30,40 Eth1/30/2 1,17-18,30,40 Eth1/30/3 1,17-18,30,40 Eth1/30/4 1,17-18,30,40 Eth1/31/1 1,17-18,30,40 Eth1/31/2 1,17-18,30,40 Eth1/31/3 1,17-18,30,40 Eth1/31/4 1,17-18,30,40 Eth1/32/1 1,17-18,30,40 Eth1/32/2 1,17-18,30,40 Eth1/32/3 1,17-18,30,40 Eth1/32/4 1,17-18,30,40 Eth1/33/1 1,17-18,30,40 Eth1/33/2 1,17-18,30,40 Eth1/33/3 1,17-18,30,40 Eth1/33/4 1,17-18,30,40 Eth1/34/1 1,17-18,30,40 Eth1/34/2 1,17-18,30,40 Eth1/34/3 1,17-18,30,40 Eth1/34/4 1,17-18,30,40 Eth1/35/1 1,17-18,30,40 Eth1/35/2 1,17-18,30,40 Eth1/35/3 1,17-18,30,40 Eth1/35/4 1,17-18,30,40 Eth1/36 1,40 Po1 1,40 -------------------------------------------------------------------------------- Port Vlans Err-disabled on Trunk -------------------------------------------------------------------------------- Eth1/1 none Eth1/2 none Eth1/3 none Eth1/4 none Eth1/5 none Eth1/6 none Eth1/7 none Eth1/8 none Eth1/9 none Eth1/10 none . . . Eth1/30/1 none Eth1/30/2 none Eth1/30/3 none Eth1/30/4 none Eth1/31/1 none Eth1/31/2 none Eth1/31/3 none Eth1/31/4 none Eth1/32/1 none Eth1/32/2 none Eth1/32/3 none Eth1/32/4 none Eth1/33/1 none Eth1/33/2 none Eth1/33/3 none Eth1/33/4 none Eth1/34/1 none Eth1/34/2 none Eth1/34/3 none Eth1/34/4 none Eth1/35/1 none Eth1/35/2 none Eth1/35/3 none Eth1/35/4 none Eth1/36 none Po1 none -------------------------------------------------------------------------------- Port STP Forwarding -------------------------------------------------------------------------------- Eth1/1 1,17-18,30,40 Eth1/2 1,17-18,30,40 Eth1/3 1,17-18,30,40 Eth1/4 1,17-18,30,40 Eth1/5 1,17-18,30,40 Eth1/6 1,17-18,30,40 Eth1/7 1,17-18,30,40 Eth1/8 1,17-18,30,40 Eth1/9 none Eth1/10 1,17-18,30,40 . . . Eth1/30/1 none Eth1/30/2 none Eth1/30/3 none Eth1/30/4 none Eth1/31/1 none Eth1/31/2 none Eth1/31/3 none Eth1/31/4 none Eth1/32/1 none Eth1/32/2 none Eth1/32/3 none Eth1/32/4 none Eth1/33/1 none Eth1/33/2 none Eth1/33/3 none Eth1/33/4 none Eth1/34/1 none Eth1/34/2 none Eth1/34/3 none Eth1/34/4 none Eth1/35/1 none Eth1/35/2 none Eth1/35/3 none Eth1/35/4 none Eth1/36 none Po1 none -------------------------------------------------------------------------------- Port Vlans in spanning tree forwarding state and not pruned -------------------------------------------------------------------------------- Eth1/1 Feature VTP is not enabled 1,17-18,30,40 Eth1/2 Feature VTP is not enabled 1,17-18,30,40 Eth1/3 Feature VTP is not enabled 1,17-18,30,40 Eth1/4 Feature VTP is not enabled 1,17-18,30,40 Eth1/5 Feature VTP is not enabled 1,17-18,30,40 Eth1/6 Feature VTP is not enabled 1,17-18,30,40 Eth1/7 Feature VTP is not enabled 1,17-18,30,40 Eth1/8 Feature VTP is not enabled 1,17-18,30,40 Eth1/9 Feature VTP is not enabled 1,17-18,30,40 Eth1/10 Feature VTP is not enabled 1,17-18,30,40 . . . Eth1/30/1 Feature VTP is not enabled none Eth1/30/2 Feature VTP is not enabled none Eth1/30/3 Feature VTP is not enabled none Eth1/30/4 Feature VTP is not enabled none Eth1/31/1 Feature VTP is not enabled none Eth1/31/2 Feature VTP is not enabled none Eth1/31/3 Feature VTP is not enabled none Eth1/31/4 Feature VTP is not enabled none Eth1/32/1 Feature VTP is not enabled none Eth1/32/2 Feature VTP is not enabled none Eth1/32/3 Feature VTP is not enabled none Eth1/32/4 Feature VTP is not enabled none Eth1/33/1 Feature VTP is not enabled none Eth1/33/2 Feature VTP is not enabled none Eth1/33/3 Feature VTP is not enabled none Eth1/33/4 Feature VTP is not enabled none Eth1/34/1 Feature VTP is not enabled none Eth1/34/2 Feature VTP is not enabled none Eth1/34/3 Feature VTP is not enabled none Eth1/34/4 Feature VTP is not enabled none Eth1/35/1 Feature VTP is not enabled none Eth1/35/2 Feature VTP is not enabled none Eth1/35/3 Feature VTP is not enabled none Eth1/35/4 Feature VTP is not enabled none Eth1/36 Feature VTP is not enabled none Po1 Feature VTP is not enabled none
For specific port and VLAN usage details, refer to the banner and important notes section in your RCF. -
Using the switch CLI, verify that the ISL between cs1 and cs2 is functional:
show port-channel summaryShow example
cs1# show port-channel summary Flags: D - Down P - Up in port-channel (members) I - Individual H - Hot-standby (LACP only) s - Suspended r - Module-removed b - BFD Session Wait S - Switched R - Routed U - Up (port-channel) p - Up in delay-lacp mode (member) M - Not in use. Min-links not met -------------------------------------------------------------------------------- Group Port- Type Protocol Member Ports Channel -------------------------------------------------------------------------------- 1 Po1(SD) Eth LACP Eth1/36(D) 998 Po998(SD) Eth NONE -- 999 Po999(SD) Eth NONE -- -
Using the ONTAP CLI, verify that the cluster LIFs have reverted to their home port:
network interface show -role clusterShow example
cluster1::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- --------------- ---------- ------------------ ----------- ------- ---- Cluster node1-01_clus1 up/up 169.254.36.44/16 node1-01 e2a true node1-01_clus2 up/up 169.254.7.5/16 node1-01 e2b true node1-02_clus1 up/up 169.254.197.206/16 node1-02 e2a true node1-02_clus2 up/up 169.254.195.186/16 node1-02 e2b true node1-03_clus1 up/up 169.254.192.49/16 node1-03 e2a true node1-03_clus2 up/up 169.254.182.76/16 node1-03 e2b true node1-04_clus1 up/up 169.254.59.49/16 node1-04 e2a true node1-04_clus2 up/up 169.254.62.244/16 node1-04 e2b trueIf any cluster LIFs have not returned to their home ports, revert them manually from the local node:
network interface revert -vserver vserver_name -lif <lif-name> -
Using the ONTAP CLI, verify that the cluster is healthy:
cluster showShow example
cluster1::*> cluster show Node Health Eligibility Epsilon ----------------- ------- ------------- ------- node1-01 true true false node1-02 true true false node1-03 true true true node1-04 true true false
-
Using the ONTAP CLI, verify the connectivity of the remote cluster interfaces:
-
You can use the
network interface check cluster-connectivity showcommand to display the details of an accessibility check for cluster connectivity:network interface check cluster-connectivity showShow example
cluster1::*> network interface check cluster-connectivity show Source Destination Packet Node Date LIF LIF Loss ------ -------------------------- ---------------- --------------- ----------- node1-01 6/4/2025 03:13:33 -04:00 node1-01_clus2 node1-02_clus1 none 6/4/2025 03:13:34 -04:00 node1-01_clus2 node1-02_clus1 none node1-02 6/4/2025 03:13:33 -04:00 node1-02_clus2 node1-01_clus1 none 6/4/2025 03:13:34 -04:00 node1-02_clus2 node1-01_clus2 none . . . -
Alternatively, you can use the
cluster ping-cluster -node <node-name>command to check the connectivity:cluster ping-cluster -node <node-name>Show example
cluster1::*> cluster ping-cluster -node local Host is node1-04 Getting addresses from network interface table... Cluster node1-01_clus1 169.254.36.44 node1-01 e7a Cluster node1-01_clus2 169.254.7.5 node1-01 e7b Cluster node1-02_clus1 169.254.197.206 node1-02 e7a Cluster node1-02_clus2 169.254.195.186 node1-02 e7b Cluster node1-03_clus1 169.254.192.49 node1-03 e7a Cluster node1-03_clus2 169.254.182.76 node1-03 e7b Cluster node1-04_clus1 169.254.59.49 node1-04 e7a Cluster node1-04_clus2 169.254.62.244 node1-04 e7b Local = 169.254.59.49 169.254.62.244 Remote = 169.254.36.44 169.254.7.5 169.254.197.206 169.254.195.186 169.254.192.49 169.254.182.76 Cluster Vserver Id = 4294967293 Ping status: ............ Basic connectivity succeeds on 12 path(s) Basic connectivity fails on 0 path(s) ................................................ Detected 9000 byte MTU on 12 path(s): Local 169.254.59.49 to Remote 169.254.182.76 Local 169.254.59.49 to Remote 169.254.192.49 Local 169.254.59.49 to Remote 169.254.195.186 Local 169.254.59.49 to Remote 169.254.197.206 Local 169.254.59.49 to Remote 169.254.36.44 Local 169.254.59.49 to Remote 169.254.7.5 Local 169.254.62.244 to Remote 169.254.182.76 Local 169.254.62.244 to Remote 169.254.192.49 Local 169.254.62.244 to Remote 169.254.195.186 Local 169.254.62.244 to Remote 169.254.197.206 Local 169.254.62.244 to Remote 169.254.36.44 Local 169.254.62.244 to Remote 169.254.7.5 Larger than PMTU communication succeeds on 12 path(s) RPC status: 6 paths up, 0 paths down (tcp check) 6 paths up, 0 paths down (udp check)
-
After you've upgraded the RCF on your switches, you verify SSH for log collection.