Move cluster LIFs before a MetroCluster IP switch replacement, RCF change, or firmware update
Suggest changes
PDFs
When you replace a MetroCluster IP switch or change the switch firmware or reference configuration file (RCF), you need to move cluster LIFs to the partner switch to enable non-disruptive cluster operations.
-
You must perform this task before you upgrade or downgrade switch firmware, replace the switch RCF, or replace an IP switch.
If you are configuring the switches for the first time, you can skip this task unless you are performing a switch replacement. -
The task requires you to use both ONTAP commands and switch commands; ONTAP commands are used unless otherwise indicated.
-
In the examples used in this procedure, you are upgrading IP_switch_A_1, so you need to migrate the cluster LIFs to IP_switch_A_2.
-
The command output examples in this procedure show the details for a Cisco switch. The output can vary depending on your switch model and vendor.
-
Display the cluster ports that are connected to the cluster switches on each node:
network device-discovery showShow example
cluster_A::*> network device-discovery show Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ---------------- ---------------- node_A_2/cdp e10b IP_switch_A_2 Ethernet1/18 N9K-C9336C-FX2 e2a IP_switch_A_1 Ethernet1/18 N9K-C9336C-FX2 e4a IP_switch_A_1 Ethernet1/2 N9K-C9336C-FX2 e4b IP_switch_A_2 Ethernet1/2 N9K-C9336C-FX2 e5b IP_switch_A_1 Ethernet1/10 N9K-C9336C-FX2 e7b IP_switch_A_2 Ethernet1/10 N9K-C9336C-FX2 e9a local_network_switch Ethernet1/5 N9K-C9372PX e9b local_network_switch Ethernet1/6 N9K-C9372PX node_A_2/lldp e0M mgmt_switch (00:08:2f:16:8e:02) Eth121/1/1 - e10b IP_switch_A_2 (cc:90:70:e8:73:a0) Ethernet1/18 - e2a IP_switch_A_1 (cc:90:70:e8:50:48) Ethernet1/18 - e5b IP_switch_A_1 (cc:90:70:e8:50:28) Ethernet1/10 - e7b IP_switch_A_2 (cc:90:70:e8:73:80) Ethernet1/10 - e9a local_network_switch (88:f0:31:86:fe:a8) Ethernet1/5 - e9b local_network_switch (88:f0:31:86:fe:a9) Ethernet1/6 - node_A_1/cdp e10b IP_switch_A_2 Ethernet1/17 N9K-C9336C-FX2 e2a IP_switch_A_1 Ethernet1/17 N9K-C9336C-FX2 e4a IP_switch_A_1 Ethernet1/1 N9K-C9336C-FX2 e4b IP_switch_A_2 Ethernet1/1 N9K-C9336C-FX2 e5b IP_switch_A_1 Ethernet1/9 N9K-C9336C-FX2 e7b IP_switch_A_2 Ethernet1/9 N9K-C9336C-FX2 e9a local_network_switch Ethernet1/3 N9K-C9372PX e9b local_network_switch Ethernet1/4 N9K-C9372PX node_A_1/lldp e0M mgmt_switch (00:08:2f:16:8e:03) Eth121/1/2 - e10b IP_switch_A_2 (cc:90:70:e8:73:9c) Ethernet1/17 - e2a IP_switch_A_1 (cc:90:70:e8:50:44) Ethernet1/17 - e5b IP_switch_A_1 (cc:90:70:e8:50:24) Ethernet1/9 - e7b IP_switch_A_2 (cc:90:70:e8:73:7c) Ethernet1/9 - e9a local_network_switch (88:f0:31:86:fe:a6) Ethernet1/3 - e9b local_network_switch (88:f0:31:86:fe:a7) Ethernet1/4 - 30 entries were displayed. -
Check the administrative and operational status of each cluster port.
-
Verify that all the cluster ports are up with a healthy status:
network port show -role clusterShow example
cluster_A::*> network port show -role cluster Node: node_A_1 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e4a Cluster Cluster up 9000 auto/40000 healthy false e4b Cluster Cluster up 9000 auto/40000 healthy false Node: node_A_2 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e4a Cluster Cluster up 9000 auto/40000 healthy false e4b Cluster Cluster up 9000 auto/40000 healthy false 4 entries were displayed. -
Verify that all the cluster interfaces (LIFs) are on the home port:
network interface show -role clusterShow example
cluster_A::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- -------------- ---------- ------------------ ------------- ------- ---- Cluster node_A_1_clus1 up/up 101.101.101.88/18 node_A_1 e4a true node_A_1_clus2 up/up 101.101.101.93/18 node_A_1 e4b true node_A_2_clus1 up/up 101.101.101.96/18 node_A_2 e4a true node_A_2_clus2 up/up 101.101.101.97/18 node_A_2 e4b true 4 entries were displayed. cluster_A::*> -
Verify that the cluster displays information for both cluster switches:
system switch ethernet show -is-monitoring-enabled-operational trueShow example
cluster_A::*> system switch ethernet show -is-monitoring-enabled-operational true Switch Type Address Model --------------------------- ------------------ ---------------- --------------- IP_switch_A_1 cluster-network 10.231.7.251 N9K-C9336C-FX2 Serial Number: FDO26020KLJ Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.5(4) Version Source: CDP/ISDP IP_switch_A_2 cluster-network 10.231.7.252 N9K-C9336C-FX2 Serial Number: FDO26020KGL Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.5(4) Version Source: CDP/ISDP 2 entries were displayed. cluster_A::*>
-
-
Disable auto-revert on the cluster LIFs. The cluster LIFs fail over to the partner cluster switch and remain there as you perform the upgrade procedure on the targeted switch:
If you are upgrading the second fabric, you can skip this step and go to Step 4. network interface modify -vserver Cluster -lif * -auto-revert falseShow example
cluster_A::*> network interface modify -vserver Cluster -lif * -auto-revert false Warning: Disabling the auto-revert feature of the cluster logical interface may effect the availability of your cluster network. Are you sure you want to continue? {y|n}: y Warning: Changes to a cluster LIF can affect the health of the Cluster. Are you sure you want to continue? {y|n}: y 4 entries were modified. -
On cluster switch IP_switch_A1, shut down the ports connected to the cluster ports of the nodes.
CiscoIP_switch_A_1(config)# sh int eth1/1,eth1/2 brief -------------------------------------------------------------------------------- Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -------------------------------------------------------------------------------- Eth1/1 101 eth access up none 40G(D) -- Eth1/2 101 eth access up none 40G(D) -- IP_switch_A_1(config)# IP_switch_A_1(config)# int eth1/1,eth1/2 IP_switch_A_1(config-if-range)# shut IP_switch_A_1(config-if-range)#
BroadcomIP_switch_A1(config)# interface eth1/1/1-2,eth1/7-8 IP_switch_A1(config-if-range)# shutdown
NVIDIA-
Display the cluster interfaces:
cumulus@IP_switch_A_1:mgmt:~$ nv show interface Interface Admin Status Oper Status Speed MTU Type Remote Host Remote Port Summary ----------- ------------ ----------- ----- ----- -------- -------------- ----------- --------- swp1 up up 100G 9216 swp cluster1 e1a
-
Shut down the cluster interface port:
sudo python3 <RCF_name> runCmd swp1 state down
-
-
Verify that the cluster LIFs have migrated to the ports hosted on cluster switch IP_switch_A2. This might take a few seconds.
network interface show -role clusterShow example
cluster_A::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- -------------- ---------- ------------------ ------------- ------- ---- Cluster node_A_1_clus1 up/up 101.101.101.88/18 node_A_1 e4b false node_A_1_clus2 up/up 101.101.101.93/18 node_A_1 e4b true node_A_2_clus1 up/up 101.101.101.96/18 node_A_2 e4b false node_A_2_clus2 up/up 101.101.101.97/18 node_A_2 e4b true 4 entries were displayed. -
Verify that the cluster is healthy:
cluster showShow example
cluster_A::*> cluster show Node Health Eligibility Epsilon -------------------- ------- ------------ ------------ node_A_1 true true false node_A_2 true true false 2 entries were displayed.
After the cluster LIFs have moved to the partner switch, you can follow the standard configuration procedures according to your switch vendor to complete the upgrade to the target firmware or RCF version:
|
|
After configuring the switches in the first fabric, you must repeat the steps to move cluster LIFs on the second fabric. |