How to Replace the CISCO MDS 9124 San Switch chassis
Storage – SAN Switch - CISCO
CISCO MDS 9124
Replacing the CISCO MDS 9124 SAN Switch chassis –
frequent reboot due to chassis faulty
1.Power off the faulty switch and remove power
cable and all FC cables.
2. Remove the switch from rack and swap all SFP
from faulty switch to new one
3. Mount the switch on the RACK and connect all the
FC Cables and Power ON the switch
To restore a switch configuration, follow these
steps:
1. Save the running configuration with the copy
running-config command.
switch1# copy running-config startup-config
[########################################] 100%
2. Copy the start up-configuration to the file
server using any of the available methods on the switch (FTP, TFTP, SFTP, and
SCP).
switch1# copy startup-config
scp://user@host1/switch1.config
user@switch1's password:
sysmgr_system.cfg 100% |*****************************|
10938 00:00
switch1#
3. Capture the port assignments using the FLOGI
database. This will be used to verify that all the cables are placed in their
correct locations.
switch1# `show flogi
database`
---------------------------------------------------------------------------
INTERFACE
VSAN
FCID PORT
NAME
NODE NAME
---------------------------------------------------------------------------
fc1/1
2 0xe30100 50:06:0e:80:14:44:b9:00
50:06:0e:80:14:44:b9:00
fc1/2
3 0x3a0000 50:06:0e:80:14:44:b9:20
50:06:0e:80:14:44:b9:20
fc1/3
2 0xe30300 21:00:00:1b:32:00:6c:90
20:00:00:1b:32:00:6c:90
fc1/4
4 0x360000 50:06:0e:80:14:44:b9:40
50:06:0e:80:14:44:b9:40
fc1/5
5 0x290000 21:00:00:1b:32:00:cb:90
20:00:00:1b:32:00:cb:90
fc1/6
5 0x290100 50:06:0e:80:14:44:b9:60
50:06:0e:80:14:44:b9:60
fc1/7
3 0x3a0100 21:00:00:1b:32:00:55:8e
20:00:00:1b:32:00:55:8e
fc1/8
4 0x360100 21:00:00:1b:32:00:64:92
20:00:00:1b:32:00:64:92
At this point the old switch is no longer needed,
so you can disconnect its mgmt0 port from the LAN.
4. Log on to the new switch using the
console connection and clear the switch configuration. Do not run the setup
script, if prompted. The write erase command erases the switch’s configuration.
switch2# write erase
Warning: This command will erase the
startup-configuration.
Do you wish to proceed anyway? (y/n) [n] y
5. Reload the switch.
switch2# reload
This command will reboot the system. (y/n)?
[n] y
6. The switch comes up in factory default mode
and prompts for basic system configuration. You can ignore the prompt by
pressing CRL+Z, because all the configuration options are contained in the old
switch’s start up configuration. Manually configure the IP address.
switch2# config terminal
Enter configuration commands, one per line.
End with CNTL/Z.
switch2(config)# int mgmt 0
switch2(config-if)# ip address x.x.x.x y.y.y.y
switch2(config-if)# no shut
7. If interface (fc X/Y)-based zoning was
done, obtain the WWN of the new switch with the show wwn switch command.
Otherwise, skip this step.
switch2# show wwn switch
Switch WWN is xx.xx.xx.xx.xx.xx.xx.xx
8. On the file server, make a copy of the
configuration file, then open the copy in a text editor such as Notepad. Make
these changes:
a. Remove the lines that contain the SNMP user
accounts, as the encrypted passwords are tied to the MAC address of the
chassis.:
$ cp switch1.config switch1.config.orig
$ vi switch1.config
The user accounts are all grouped together and
begin with snmp-server user command.
snmp-server user admin network-admin auth md5
0x46694cac2585d39d3bc00c8a4c7d48a6 localizedkey
snmp-server user guestadmin network-admin auth
md5 0xcae40d254218747bc57ee1df34826b51 localizedkey
b. If interface (fc X/Y)-based zoning was done,
replace the WWN of the old switch in the zone member commands with the WWN of
the new switch. Otherwise, skip this step.
Example
zone name Z_1 vsan 9
member interface fc1/9 swwn
20:00:00:0d:ec:02:1d:40
c. If IVR was configured on this switch, the IVR
topology will need to be modified as that is based upon the sWWN and the old
sWWN should be replaced with the new sWWN.
ivr vsan-topology database
autonomous-fabric-id 1
switch-wwn 20:00:00:0d:ec:02:1d:40 vsan-ranges 500,3002
autonomous-fabric-id 1
switch-wwn 20:00:00:0c:85:e9:d2:c0 vsan-ranges 500,3000
If the IVR topology is configured for auto and is
distributed through CFS, then this step does not need to be done as the switch
will learn of the topology via CFS.
d. Save and exit the configuration file.
9. From the new switch, copy the modified
config file from the file server to the running configuration of the new
switch. As the file is copied, it is executed and the configuration is applied.
The commands being applied are displayed in single quotes. Any errors resulting
from the commands are displayed immediately after the command that caused it.
When finished, the prompt changes to reflect the new switch name.
switch2# copy scp://user@host1/switch1.config
running-config
user@host1's password:
switch1.config 100%
|*****************************| 10938 00:00
10. Save the configuration by copying the
startup configuration to the running configuration.
switch1# copy running-config startup-config
[########################################] 100%:
11. The switch can now be accessed with the
CLI. Complete the configuration restoration:
a. Recreate SNMP user accounts.
b. If the switch is accessed with SSH, remove the
MDS switch entry from the host’s known_hosts file because the switch’s public
key has changed.
c. Install any required license keys.
12. Move the cables from the old switch to
the new switch, using the show flogi database command output on the old
switch as a reference to verify that each cable is in the correct location.
13. Verify that all devices have logged in and
all features are running is as they are supposed to be and save the running
configuration to the start up configuration with the copy running-config
startup-config command.
14. Reload the switch to verify that it boots
correctly with the configuration.
No comments:
Post a Comment