Sunday, 2 February 2014

Brief Notes on Relocating a Cluster Interconnect Switch

Not something that’s going to be done much if ever. In theory, in 100% of occasions, simply powering off the switch you want to move should be fine (be sure the configuration is backed up first though), after all, having two cluster interconnect switches is designed for resilience so that if one fails everything continues on its merry way.

Image: Two x Cisco 5010 Cluster Interconnect Switches

If you want to take the cautious approach though (always a good approach to take), here are some notes to follow:

1) General CDOT Health Checks (Use generously) / Obtaining Information

cluster show
cluster ping-cluster -node NODENAME
net int show -role cluster
net port show -role cluster
system node run -node NODENAME -command cdpd show-neighbors -v
system node run -node NODENAME -command ifstat -a -z
system node run -node NODENAME -command ifstat PORTNAME

event log show -severity EMERGENCY
event log show -severity ALERT
event log show -severity CRITICAL
event log show -severity ERROR
event log show -severity WARNING
event log show -time > 10m

2) Downing the Switch (Switch 2 here)

2.1 Migrating clus2 lifs and downing ports

Note i: Here we’re going to down switch 2 hence moving the clus2 lifs, and considering a FAS62XX with clus2 on e0e.
Note ii: Migration of cluster lifs must be done from the local node otherwise you get the error:
Error: command failed: Migration of cluster lifs must be done from the local node.
Note iii: Similarly, downing of cluster ports must be done from the local node.

Connected to NODE-X via its Node Management LIF / Service Processor (> system console):

set advanced
net int migrate -vserver  NODE-X -lif clus2 -dest-node NODE-X -dest-port e0c
net port modify -node NODE-X -port e0e -up-admin false

Repeat for as many nodes are in the cluster…

2.2 On the switch to be powered off (Switch 2 here)

copy run start
show interface brief
show port-channel summary

2.3 On the switch that remains powered on (Switch 1 here)

show interface brief
show port-channel summary

configure
interface ethernet 1/13-20
shutdown

Note: Here we’re considering a Cisco 5010 with 8 ISLs on ports 13-20. Only the ISL Port-Channel ports get shutdown!

3) Powering Off the Switch (Switch 2 here)

Power off the switch, un-cable, move, re-cable, and power up

4) Upping the Switch (Switch 2 here)

4.1 On the switch that remained powered on (Switch 1 here)

configure
interface Ethernet 1/13-20
no shutdown

show interface brief
show port-channel summary

Note: Confirm the port-channel is fully established.

4.2 Upping ports and reverting clus2 lifs

Note: This can be done from one Clustershell session

set advanced
net port modify -node NODE-X -port e0e -up-admin true
net int revert -vserver NODE-X -lif clus2

Repeat for as many nodes are in the cluster…

THE END!

No comments:

Post a Comment