About this task
The examples in this procedure describe replacing Nexus 5596 switches with Nexus 3132Q-V switches. You can use these steps (with modifications) to replace other older Cisco switches. The procedure uses the following switch and node nomenclature:
• The command outputs might vary depending on different releases of ONTAP.
• The Nexus 5596 switches to be replaced are CL1 and CL2.
• The Nexus 3132Q-V switches to replace the Nexus 5596 switches are C1 and C2.
• n1_clus1 is the first cluster logical interface (LIF) connected to cluster switch 1 (CL1 or C1) for node n1.
• n1_clus2 is the first cluster LIF connected to cluster switch 2 (CL2 or C2) for node n1.
• n1_clus3 is the second LIF connected to cluster switch 2 (CL2 or C2) for node n1.
• n1_clus4 is the second LIF connected to cluster switch 1 (CL1 or C1) for node n1.
• The nodes are n1, n2, n3, and n4.
• The examples in this procedure use four nodes: Two nodes use four 10 GbE cluster interconnect ports:
e0a, e0b, e0c, and e0d. The other two nodes use two 40/100 GbE cluster interconnect ports: e4a, e4e. The Hardware Universe lists the actual cluster ports on your platforms.
• The number of 10 GbE and 40/100 GbE ports are defined in the reference configuration files (RCFs) available on the Cisco® Cluster Network Switch Reference Configuration File Download page.
The procedure requires the use of both ONTAP commands and Cisco Nexus 3000 Series Switches commands; ONTAP commands are used unless otherwise indicated.
This procedure covers the following scenarios:
• The cluster starts with two nodes connected and functioning in a 2 Nexus 5596 cluster switches.
• The cluster switch CL2 to be replaced by C2 (Steps 1 - 19)
◦ Traffic on all cluster ports and LIFs on all nodes connected to CL2 are migrated onto the first cluster ports and LIFs connected to CL1.
◦ Disconnect cabling from all cluster ports on all nodes connected to CL2, and then use supported break-out cabling to reconnect the ports to new cluster switch C2.
◦ Disconnect cabling between ISL ports between CL1 and CL2, and then use supported break-out cabling to reconnect the ports from CL1 to C2.
◦ Traffic on all cluster ports and LIFs connected to C2 on all nodes is reverted.
• The cluster switch CL2 to be replaced by C2 (Steps 20 - 33)
◦ Traffic on all cluster ports or LIFs on all nodes connected to CL1 are migrated onto the second cluster ports or LIFs connected to C2.
◦ Disconnect cabling from all cluster port on all nodes connected to CL1 and reconnect, using supported break-out cabling, to new cluster switch C1.
◦ Disconnect cabling between ISL ports between CL1 and C2, and reconnect using supported cabling, from C1 to C2.
◦ Traffic on all cluster ports or LIFs connected to C1 on all nodes is reverted.
• Two FAS9000 nodes have been added to cluster with examples showing cluster details (Steps 34 - 37).
Steps
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 x is the duration of the maintenance window in hours.
The message notifies technical support of this maintenance task so that automatic case creation is suppressed during the maintenance window.
2. Display information about the devices in your configuration:
network device-discovery show
The following example shows how many cluster interconnect interfaces have been configured in each node for each cluster interconnect switch:
cluster::> network device-discovery show Local Discovered
Node Port Device Interface Platform
--- --- --- ---n1 /cdp
e0a CL1 Ethernet1/1 N5K-C5596UP e0b CL2 Ethernet1/1 N5K-C5596UP e0c CL2 Ethernet1/2 N5K-C5596UP e0d CL1 Ethernet1/2 N5K-C5596UP n2 /cdp
e0a CL1 Ethernet1/3 N5K-C5596UP e0b CL2 Ethernet1/3 N5K-C5596UP e0c CL2 Ethernet1/4 N5K-C5596UP e0d CL1 Ethernet1/4 N5K-C5596UP 8 entries were displayed.
3. Determine the administrative or operational status for each cluster interface:
a. Display the network port attributes:
network port show
The following example displays the network port attributes on a system:
cluster::*> network port show –role cluster
b. Display information about the logical interfaces:
network interface show
The following example displays the general information about all of the LIFs on your system:
cluster::*> network interface show -role cluster (network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
--- --- --- ---
----Cluster
n1_clus1 up/up 10.10.0.1/24 n1 e0a true
n1_clus2 up/up 10.10.0.2/24 n1 e0b true
n1_clus3 up/up 10.10.0.3/24 n1 e0c true
n1_clus4 up/up 10.10.0.4/24 n1 e0d true
n2_clus1 up/up 10.10.0.5/24 n2 e0a true
n2_clus2 up/up 10.10.0.6/24 n2 e0b true
n2_clus3 up/up 10.10.0.7/24 n2 e0c true
n2_clus4 up/up 10.10.0.8/24 n2 e0d true
8 entries were displayed.
c. Display information about the discovered cluster switches:
system cluster-switch show
The following example displays the cluster switches that are known to the cluster, along with their management IP addresses:
cluster::*> system cluster-switch show
Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
7.1(1)N1(1) Version Source: CDP
2 entries were displayed.
4. Set the -auto-revert parameter to false on cluster LIFs clus1 and clus2 on both nodes:
network interface modify
cluster::*> network interface modify -vserver node1 -lif clus1 -auto -revert false
cluster::*> network interface modify -vserver node1 -lif clus2 -auto -revert false
cluster::*> network interface modify -vserver node2 -lif clus1 -auto -revert false
cluster::*> network interface modify -vserver node2 -lif clus2 -auto -revert false
5. Verify that the appropriate RCF and image are installed on the new 3132Q-V switches as necessary for your requirements, and make the essential site customizations, such as users and passwords, network addresses, and so on.
You must prepare both switches at this time. If you need to upgrade the RCF and image, follow these
steps:
a. Go to the Cisco Ethernet Switches page on the NetApp Support Site.
b. Note your switch and the required software versions in the table on that page.
c. Download the appropriate version of the RCF.
d. Click CONTINUE on the Description page, accept the license agreement, and then follow the instructions on the Download page to download the RCF.
e. Download the appropriate version of the image software.
See the ONTAP 8.x or later Cluster and Management Network Switch Reference Configuration FilesDownload page, and then click the appropriate version.
To find the correct version, see the ONTAP 8.x or later Cluster Network Switch Download page.
6. Migrate the LIFs associated with the second Nexus 5596 switch to be replaced:
network interface migrate
The following example shows n1 and n2, but LIF migration must be done on all of the nodes:
cluster::*> network interface migrate -vserver Cluster -lif n1_clus2 -source-node n1 –
destination-node n1 -destination-port e0a
cluster::*> network interface migrate -vserver Cluster -lif n1_clus3 -source-node n1 –
destination-node n1 -destination-port e0d
cluster::*> network interface migrate -vserver Cluster -lif n2_clus2 -source-node n2 –
destination-node n2 -destination-port e0a
cluster::*> network interface migrate -vserver Cluster -lif n2_clus3 -source-node n2 –
destination-node n2 -destination-port e0d
7. Verify the cluster’s health:
network interface show
The following example shows the result of the previous network interface migrate command:
cluster::*> network interface show -role cluster (network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
--- --- --- ---
----Cluster
n1_clus1 up/up 10.10.0.1/24 n1 e0a true
n1_clus2 up/up 10.10.0.2/24 n1 e0a false
n1_clus3 up/up 10.10.0.3/24 n1 e0d false
n1_clus4 up/up 10.10.0.4/24 n1 e0d true
n2_clus1 up/up 10.10.0.5/24 n2 e0a true
n2_clus2 up/up 10.10.0.6/24 n2 e0a false
n2_clus3 up/up 10.10.0.7/24 n2 e0d false
n2_clus4 up/up 10.10.0.8/24 n2 e0d true
8 entries were displayed.
8. Shut down the cluster interconnect ports that are physically connected to switch CL2:
network port modify
The following commands shut down the specified ports on n1 and n2, but the ports must be shut down on all nodes:
cluster::*> network port modify -node n1 -port e0b -up-admin false cluster::*> network port modify -node n1 -port e0c -up-admin false cluster::*> network port modify -node n2 -port e0b -up-admin false cluster::*> network port modify -node n2 -port e0c -up-admin false
9. Ping the remote cluster interfaces and perform an RPC server check:
cluster ping-cluster
The following example shows how to ping the remote cluster interfaces:
cluster::*> cluster ping-cluster -node n1 Host is n1
Getting addresses from network interface table...
Cluster n1_clus1 n1 e0a 10.10.0.1
Local = 10.10.0.1 10.10.0.2 10.10.0.3 10.10.0.4 Remote = 10.10.0.5 10.10.0.6 10.10.0.7 10.10.0.8 Cluster Vserver Id = 4294967293
Ping status:
....
Basic connectivity succeeds on 16 path(s) Basic connectivity fails on 0 path(s) ...
Detected 1500 byte MTU on 16 path(s):
Local 10.10.0.1 to Remote 10.10.0.5 Local 10.10.0.1 to Remote 10.10.0.6 Local 10.10.0.1 to Remote 10.10.0.7 Local 10.10.0.1 to Remote 10.10.0.8 Local 10.10.0.2 to Remote 10.10.0.5 Local 10.10.0.2 to Remote 10.10.0.6 Local 10.10.0.2 to Remote 10.10.0.7 Local 10.10.0.2 to Remote 10.10.0.8 Local 10.10.0.3 to Remote 10.10.0.5 Local 10.10.0.3 to Remote 10.10.0.6 Local 10.10.0.3 to Remote 10.10.0.7 Local 10.10.0.3 to Remote 10.10.0.8 Local 10.10.0.4 to Remote 10.10.0.5 Local 10.10.0.4 to Remote 10.10.0.6 Local 10.10.0.4 to Remote 10.10.0.7 Local 10.10.0.4 to Remote 10.10.0.8
Larger than PMTU communication succeeds on 16 path(s) RPC status:
4 paths up, 0 paths down (tcp check) 4 paths up, 0 paths down (udp check
10. Shut down the ISL ports 41 through 48 on the active Nexus 5596 switch CL1:
The following example shows how to shut down ISL ports 41 through 48 on the Nexus 5596 switch CL1:
(CL1)# configure
(CL1)(Config)# interface e1/41-48 (CL1)(config-if-range)# shutdown (CL1)(config-if-range)# exit (CL1)(Config)# exit
(CL1)#
If you are replacing a Nexus 5010 or 5020, specify the appropriate port numbers for ISL from page 1.
11. Build a temporary ISL between CL1 and C2.
The following example shows a temporary ISL being set up between CL1 and C2:
C2# configure
C2(config)# interface port-channel 2 C2(config-if)# switchport mode trunk
C2(config-if)# spanning-tree port type network C2(config-if)# mtu 9216
C2(config-if)# interface breakout module 1 port 24 map 10g-4x C2(config)# interface e1/24/1-4
C2(config-if-range)# switchport mode trunk C2(config-if-range)# mtu 9216
C2(config-if-range)# channel-group 2 mode active C2(config-if-range)# exit
C2(config-if)# exit
12. On all nodes, remove all cables attached to the Nexus 5596 switch CL2.
With supported cabling, reconnect disconnected ports on all nodes to the Nexus 3132Q-V switch C2.
13. Remove all the cables from the Nexus 5596 switch CL2.
Attach the appropriate Cisco QSFP to SFP+ break-out cables connecting port 1/24 on the new Cisco 3132Q-V switch, C2, to ports 45 to 48 on existing Nexus 5596, CL1.
14. Verify that interfaces eth1/45-48 already have channel-group 1 mode active in their running configuration.
15. Bring up ISLs ports 45 through 48 on the active Nexus 5596 switch CL1.
The following example shows ISLs ports 45 through 48 being brought up:
(CL1)# configure
(CL1)(Config)# interface e1/45-48 (CL1)(config-if-range)# no shutdown (CL1)(config-if-range)# exit
(CL1)(Config)# exit (CL1)#
16. Verify that the ISLs are up on the Nexus 5596 switch CL1:
show port-channel summary
Ports eth1/45 through eth1/48 should indicate (P) meaning that the ISL ports are up in the port-channel:
Example
CL1# 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
S - Switched R - Routed U - Up (port-channel)
M - Not in use. Min-links not met
---Group Port- Type Protocol Member Ports Channel
---1 Po---1(SU) Eth LACP Eth---1/4---1(D) Eth---1/42(D) Eth---1/43(D) Eth1/44(D) Eth1/45(P) Eth1/46(P) Eth1/47(P) Eth1/48(P)
17. Verify that the ISLs are up on the 3132Q-V switch C2:
show port-channel summary
Ports eth1/24/1, eth1/24/2, eth1/24/3, and eth1/24/4 should indicate (P) meaning that the ISL ports are up in the port-channel:
C2# 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
S - Switched R - Routed U - Up (port-channel)
M - Not in use. Min-links not met
---Group Port- Type Protocol Member Ports Channel
---1 Po---1(SU) Eth LACP Eth---1/3---1(D) Eth---1/32(D) 2 Po2(SU) Eth LACP Eth1/24/1(P) Eth1/24/2(P) Eth1/24/3(P)
Eth1/24/4(P)
18. On all nodes, bring up all the cluster interconnect ports connected to the 3132Q-V switch C2:
network port modify
The following example shows the specified ports being brought up on nodes n1 and n2:
cluster::*> network port modify -node n1 -port e0b -up-admin true cluster::*> network port modify -node n1 -port e0c -up-admin true cluster::*> network port modify -node n2 -port e0b -up-admin true cluster::*> network port modify -node n2 -port e0c -up-admin true
19. On all nodes, revert all of the migrated cluster interconnect LIFs connected to C2:
network interface revert
The following example shows the migrated cluster LIFs being reverted to their home ports on nodes n1 and n2:
cluster::*> network interface revert -vserver Cluster -lif n1_clus2 cluster::*> network interface revert -vserver Cluster -lif n1_clus3 cluster::*> network interface revert -vserver Cluster -lif n2_clus2 cluster::*> network interface revert -vserver Cluster -lif n2_clus3
20. Verify all the cluster interconnect ports are now reverted to their home:
network interface show
The following example shows that the LIFs on clus2 reverted to their home ports and shows that the LIFs are successfully reverted if the ports in the Current Port column have a status of true in the Is Home column. If the Is Home value is false, the LIF has not been reverted.
cluster::*> network interface show -role cluster (network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
--- --- --- ---
----Cluster
n1_clus1 up/up 10.10.0.1/24 n1 e0a true
n1_clus2 up/up 10.10.0.2/24 n1 e0b true
n1_clus3 up/up 10.10.0.3/24 n1 e0c true
n1_clus4 up/up 10.10.0.4/24 n1 e0d true
n2_clus1 up/up 10.10.0.5/24 n2 e0a true
n2_clus2 up/up 10.10.0.6/24 n2 e0b true
n2_clus3 up/up 10.10.0.7/24 n2 e0c true
n2_clus4 up/up 10.10.0.8/24 n2 e0d true
8 entries were displayed.
21. Verify that the clustered ports are connected:
network port show
The following example shows the result of the previous network port modify command, verifying that all the cluster interconnects are up:
cluster::*> network port show -role cluster (network port show)
Node: n1
Ignore
Speed(Mbps) Health Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status
- ---- ---- ---- --- --
e0a Cluster Cluster up 9000 auto/10000 e0b Cluster Cluster up 9000 auto/10000 e0c Cluster Cluster up 9000 auto/10000 e0d Cluster Cluster up 9000 auto/10000
-Node: n2
Ignore
Speed(Mbps) Health Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status
- ---- ---- ---- --- --
e0a Cluster Cluster up 9000 auto/10000 e0b Cluster Cluster up 9000 auto/10000 e0c Cluster Cluster up 9000 auto/10000 e0d Cluster Cluster up 9000 auto/10000 -8 entries were displayed.
22. Ping the remote cluster interfaces and perform an RPC server check:
cluster ping-cluster
The following example shows how to ping the remote cluster interfaces:
cluster::*> cluster ping-cluster -node n1 Host is n1
Getting addresses from network interface table...
Cluster n1_clus1 n1 e0a 10.10.0.1
Local = 10.10.0.1 10.10.0.2 10.10.0.3 10.10.0.4 Remote = 10.10.0.5 10.10.0.6 10.10.0.7 10.10.0.8 Cluster Vserver Id = 4294967293
Ping status:
....
Basic connectivity succeeds on 16 path(s) Basic connectivity fails on 0 path(s) ...
Detected 1500 byte MTU on 16 path(s):
Local 10.10.0.1 to Remote 10.10.0.5 Local 10.10.0.1 to Remote 10.10.0.6 Local 10.10.0.1 to Remote 10.10.0.7 Local 10.10.0.1 to Remote 10.10.0.8 Local 10.10.0.2 to Remote 10.10.0.5 Local 10.10.0.2 to Remote 10.10.0.6 Local 10.10.0.2 to Remote 10.10.0.7 Local 10.10.0.2 to Remote 10.10.0.8 Local 10.10.0.3 to Remote 10.10.0.5 Local 10.10.0.3 to Remote 10.10.0.6 Local 10.10.0.3 to Remote 10.10.0.7 Local 10.10.0.3 to Remote 10.10.0.8 Local 10.10.0.4 to Remote 10.10.0.5 Local 10.10.0.4 to Remote 10.10.0.6 Local 10.10.0.4 to Remote 10.10.0.7 Local 10.10.0.4 to Remote 10.10.0.8
Larger than PMTU communication succeeds on 16 path(s) RPC status:
4 paths up, 0 paths down (tcp check) 4 paths up, 0 paths down (udp check)
23. On each node in the cluster, migrate the interfaces associated with the first Nexus 5596 switch, CL1, to be replaced:
network interface migrate
The following example shows the ports or LIFs being migrated on nodes n1 and n2:
cluster::*> network interface migrate -vserver Cluster -lif n1_clus1 sourcenode n1
-destination-node n1 -destination-port e0b
cluster::*> network interface migrate -vserver Cluster -lif n1_clus4 sourcenode n1
-destination-node n1 -destination-port e0c
cluster::*> network interface migrate -vserver Cluster -lif n2_clus1 sourcenode n2
-destination-node n2 -destination-port e0b
cluster::*> network interface migrate -vserver Cluster -lif n2_clus4 sourcenode n2
-destination-node n2 -destination-port e0c
24. Verify the cluster status:
network interface show
The following example shows that the required cluster LIFs have been migrated to appropriate cluster ports hosted on cluster switch C2:
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
--- --- --- ---
----Cluster
n1_clus1 up/up 10.10.0.1/24 n1 e0b false
n1_clus2 up/up 10.10.0.2/24 n1 e0b true
n1_clus3 up/up 10.10.0.3/24 n1 e0c true
n1_clus4 up/up 10.10.0.4/24 n1 e0c false
n2_clus1 up/up 10.10.0.5/24 n2 e0b false
n2_clus2 up/up 10.10.0.6/24 n2 e0b true
n2_clus3 up/up 10.10.0.7/24 n2 e0c true
n2_clus4 up/up 10.10.0.8/24 n2 e0c false
8 entries were displayed.
- ---
----25. On all the nodes, shut down the node ports that are connected to CL1:
network port modify
The following example shows the specified ports being shut down on nodes n1 and n2:
cluster::*> network port modify -node n1 -port e0a -up-admin false cluster::*> network port modify -node n1 -port e0d -up-admin false cluster::*> network port modify -node n2 -port e0a -up-admin false cluster::*> network port modify -node n2 -port e0d -up-admin false
26. Shut down the ISL ports 24, 31, and 32 on the active 3132Q-V switch C2: shutdown The following example shows how to shut down ISLs 24, 31, and 32:
C2# configure
C2(Config)# interface e1/24/1-4 C2(config-if-range)# shutdown C2(config-if-range)# exit C2(config)# interface 1/31-32 C2(config-if-range)# shutdown C2(config-if-range)# exit C2(config-if)# exit
C2#
27. On all nodes, remove all cables attached to the Nexus 5596 switch CL1.
With supported cabling, reconnect disconnected ports on all nodes to the Nexus 3132Q-V switch C1.
28. Remove the QSFP breakout cable from Nexus 3132Q-V C2 ports e1/24.
Connect ports e1/31 and e1/32 on C1 to ports e1/31 and e1/32 on C2 using supported Cisco QSFP optical fiber or direct-attach cables.
29. Restore the configuration on port 24 and remove the temporary Port Channel 2 on C2.
C2# configure
C2(config)# no interface breakout module 1 port 24 map 10g-4x C2(config)# no interface port-channel 2
C2(config-if)# int e1/24
C2(config-if)# description 40GbE Node Port C2(config-if)# spanning-tree port type edge C2(config-if)# spanning-tree bpduguard enable C2(config-if)# mtu 9216
C2(config-if-range)# exit C2(config)# exit
C2# copy running-config startup-config
[########################################] 100%
Copy Complete.
30. Bring up ISL ports 31 and 32 on C2, the active 3132Q-V switch: no shutdown
The following example shows how to bring up ISLs 31 and 32 on the 3132Q-V switch C2:
C2# configure
C2(config)# interface ethernet 1/31-32 C2(config-if-range)# no shutdown
C2(config-if-range)# exit C2(config)# exit
C2# copy running-config startup-config
[########################################] 100%
Copy Complete.
31. Verify that the ISL connections are up on the 3132Q-V switch C2: show port-channel summary Ports Eth1/31 and Eth1/32 should indicate (P), meaning that both the ISL ports are up in the port-channel:
C1# 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
S - Switched R - Routed U - Up (port-channel)
M - Not in use. Min-links not met
---Group Port- Type Protocol Member Ports Channel
---1 Po---1(SU) Eth LACP Eth---1/3---1(P) Eth---1/32(P)
32. On all nodes, bring up all the cluster interconnect ports connected to the new 3132Q-V switch C1:
network port modify
The following example shows all the cluster interconnect ports being brought up for n1 and n2 on the 3132Q-V switch C1:
cluster::*> network port modify -node n1 -port e0a -up-admin true cluster::*> network port modify -node n1 -port e0d -up-admin true cluster::*> network port modify -node n2 -port e0a -up-admin true cluster::*> network port modify -node n2 -port e0d -up-admin true
33. Verify the status of the cluster node port: network port show
The following example verifies that all cluster interconnect ports on all nodes on the new 3132Q-V switch C1 are up:
cluster::*> network port show –role cluster
34. On all nodes, revert the specific cluster LIFs to their home ports:
network interface revert
The following example shows the specific cluster LIFs being reverted to their home ports on nodes n1 and n2:
cluster::*> network interface revert -vserver Cluster -lif n1_clus1 cluster::*> network interface revert -vserver Cluster -lif n1_clus4 cluster::*> network interface revert -vserver Cluster -lif n2_clus1 cluster::*> network interface revert -vserver Cluster -lif n2_clus4
35. Verify that the interface is home:
network interface show
The following example shows the status of cluster interconnect interfaces is up and Is home for n1 and n2:
cluster::*> network interface show -role cluster (network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
--- --- --- ---
----Cluster
n1_clus1 up/up 10.10.0.1/24 n1 e0a true
n1_clus2 up/up 10.10.0.2/24 n1 e0b true
n1_clus3 up/up 10.10.0.3/24 n1 e0c true
n1_clus4 up/up 10.10.0.4/24 n1 e0d true
n2_clus1 up/up 10.10.0.5/24 n2 e0a true
n2_clus2 up/up 10.10.0.6/24 n2 e0b true
n2_clus3 up/up 10.10.0.7/24 n2 e0c true
n2_clus4 up/up 10.10.0.8/24 n2 e0d true
8 entries were displayed.
36. Ping the remote cluster interfaces and then perform a remote procedure call server check:
cluster ping-cluster
The following example shows how to ping the remote cluster interfaces:
cluster::*> cluster ping-cluster -node n1 Host is n1
Getting addresses from network interface table...
Cluster n1_clus1 n1 e0a 10.10.0.1
Local = 10.10.0.1 10.10.0.2 10.10.0.3 10.10.0.4 Remote = 10.10.0.5 10.10.0.6 10.10.0.7 10.10.0.8 Cluster Vserver Id = 4294967293
Ping status:
....
Basic connectivity succeeds on 16 path(s) Basic connectivity fails on 0 path(s) ...
Detected 1500 byte MTU on 16 path(s):
Local 10.10.0.1 to Remote 10.10.0.5 Local 10.10.0.1 to Remote 10.10.0.6 Local 10.10.0.1 to Remote 10.10.0.7 Local 10.10.0.1 to Remote 10.10.0.8 Local 10.10.0.2 to Remote 10.10.0.5 Local 10.10.0.2 to Remote 10.10.0.6 Local 10.10.0.2 to Remote 10.10.0.7 Local 10.10.0.2 to Remote 10.10.0.8 Local 10.10.0.3 to Remote 10.10.0.5 Local 10.10.0.3 to Remote 10.10.0.6 Local 10.10.0.3 to Remote 10.10.0.7 Local 10.10.0.3 to Remote 10.10.0.8 Local 10.10.0.4 to Remote 10.10.0.5 Local 10.10.0.4 to Remote 10.10.0.6 Local 10.10.0.4 to Remote 10.10.0.7 Local 10.10.0.4 to Remote 10.10.0.8
Larger than PMTU communication succeeds on 16 path(s) RPC status:
4 paths up, 0 paths down (tcp check)
4 paths up, 0 paths down (tcp check)