Complete the migration from two-node switchless clusters to two-node switched clusters
Suggest changes
PDFs
Follow these steps to complete the migration from switchless clusters to two-node switched clusters.
-
Display the cluster switch port numbers each cluster port is connected to on each node:
network device-discovery showShow example
cluster::*> network device-discovery show Local Discovered Node Port Device Interface Platform ----------- ------ ------------------- ---------------- ---------------- n1 /cdp e4a C1 Ethernet1/7 N3K-C3132Q-V e4e C2 Ethernet1/7 N3K-C3132Q-V n2 /cdp e4a C1 Ethernet1/8 N3K-C3132Q-V e4e C2 Ethernet1/8 N3K-C3132Q-V -
Display discovered and monitored cluster switches:
system cluster-switch showShow example
cluster::*> system cluster-switch show Switch Type Address Model --------------------------- ------------------ ---------------- --------------- C1 cluster-network 10.10.1.101 NX3132V Serial Number: FOX000001 Is Monitored: true Reason: Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 7.0(3)I4(1) Version Source: CDP C2 cluster-network 10.10.1.102 NX3132V Serial Number: FOX000002 Is Monitored: true Reason: Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 7.0(3)I4(1) Version Source: CDP 2 entries were displayed. -
Disable the two-node switchless configuration settings on any node:
network options switchless-clusternetwork options switchless-cluster modify -enabled false
-
Verify that the
switchless-clusteroption has been disabled.network options switchless-cluster show
-
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
------ -------------------------- --------------- ----------------- -----------
n1
3/5/2022 19:21:18 -06:00 n1_clus2 n2_clus1 none
3/5/2022 19:21:20 -06:00 n1_clus2 n2_clus2 none
n2
3/5/2022 19:21:18 -06:00 n2_clus2 n1_clus1 none
3/5/2022 19:21:20 -06:00 n2_clus2 n1_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>
cluster::*> cluster ping-cluster -node n1
Host is n1
Getting addresses from network interface table...
Cluster n1_clus1 n1 e4a 10.10.0.1
Cluster n1_clus2 n1 e4e 10.10.0.2
Cluster n2_clus1 n2 e4a 10.10.0.3
Cluster n2_clus2 n2 e4e 10.10.0.4
Local = 10.10.0.1 10.10.0.2
Remote = 10.10.0.3 10.10.0.4
Cluster Vserver Id = 4294967293
Ping status:....
Basic connectivity succeeds on 4 path(s)
Basic connectivity fails on 0 path(s)
................
Detected 1500 byte MTU on 32 path(s):
Local 10.10.0.1 to Remote 10.10.0.3
Local 10.10.0.1 to Remote 10.10.0.4
Local 10.10.0.2 to Remote 10.10.0.3
Local 10.10.0.2 to Remote 10.10.0.4
Larger than PMTU communication succeeds on 4 path(s)
RPC status:
1 paths up, 0 paths down (tcp check)
1 paths up, 0 paths down (ucp check)