Unsolved
This post is more than 5 years old
211 Posts
1
12711
Seeking for procedures to replace both SAN switches
We are planning on replacing two old cisco switches to MDS 9xxx switches. I am not so sure on what model of CISCO switch is.
I am seeking for the help on procedures to safely replace them both, keep all configurations, and meanwhile as less interruption as possible to the user.
I'd appreciate it if somebody can provide me procedures as detail as possible.
Thank you!
zhaos2
643 Posts
0
May 12th, 2015 19:00
Hi emcmagic
You need the below information:
- What multi-path software (like PowerPath..), version. This is the key for path management to affect interruption.
- MDS 9xxx model, NX-OS version
- Need licenses for all active ports
Then you can ask local service team to create replacement procedure document with:
I generated a document based on assumed MDS 9148, 5.01a.
Please feel free to contact us for any further question!
Simon
emcmagic
211 Posts
0
May 13th, 2015 03:00
Hello Simon,
Would you please attach your document? It seems neglected.
We are using pwoerpath.
It is in primary investigating process, we are not so clear on what model of switches we are going to upgrade to. So, procedures for any model or version will help me out. I have issues to execute that software.
Looking forward your doc or messages further.
Thanks a lot
zhaos2
643 Posts
0
May 13th, 2015 18:00
Hi, as the document is EMC confidential, so please tell me your EMC email address if you are EMC employee, or you can contact one of EMC pre-sales engineer, then I can send the document by email.
Thanks & best regards!
Simon Zhao
Solutions Marketing & Enablement for Oracle
EMC² | Global Solutions Marketing
Mobile: (86) 137-6168-2306
Office: (86 21) 6094-6763
Email: simon.zhao@emc.com
Web: Everything Oracle @ EMC
emcmagic
211 Posts
0
May 14th, 2015 03:00
Or cold somebody please send me a shares public procedure?
emcmagic
211 Posts
0
May 14th, 2015 03:00
I see, could you then send me some non-confidential document on this question?
Brian_Coulombe_
107 Posts
0
May 14th, 2015 04:00
Dynamox, I agree with you. ISL the switches together or export/import the active zoneset to the new switch. I wonder if they have a principle/subordinate setup and the MDS' would be the primary switches. I've done this several times with Cisco and Brocade but sounds like you've got a handle on it.
One thing they really need to make sure is that they have dual paths the whole way. I'd perform a SAN health check before anything else.
echolaughmk
522 Posts
0
May 14th, 2015 04:00
Once you have answered dynamox's question, I also have some procedures that I can provide at a high level, but they are per OS, MPIO software, etc so those types of details are required prior to being able to come up with a procedure since it will affect what has to be done on the OS or multipathing software during each path outage (assuming you are migrating SAN ports one at a time after you ISL your new Cisco's to the fabric). The other alternative is to create a parallel set of new fabrics with the new switches if you are unable to ISL for any reason (code, limitations, etc) - but that would require you having to group hosts and storage ports together and that is much more complex as dynamox mentions above.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 14th, 2015 04:00
i dont' have any procedures written down but i can answer your questions and give you general guidelines. So you are replacing old MDS switches with new MDS switches ? If yes, are you going to ISL them together to make the transition easier or this will be a cold cut-over ? What kind of operating systems/applications ?
jeff_browning
256 Posts
1
May 14th, 2015 07:00
Hey, Simon. It’s me, Jeff. This is my personal email. I switched to this when I left EMC in March.
emcmagic
211 Posts
0
May 14th, 2015 07:00
echolaughmk,
If you could please send me the one you have that would be very helpful, since I can figure out information from it to apply into our case here.
emcmagic
211 Posts
0
May 14th, 2015 07:00
Honestly, I am not sure of what is the model of the old switch is, we are in the primary checking stage. The new model would be MDS 9500, with current version of OS.
ISL together sounds nice, but we may be not able to, since I am worried that the old one may not be working with the new one. So, we might have to use cold cut-over. We have VMware and MS exchange applications.
Thanks!
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 14th, 2015 08:00
it's important that you gather those details because that might dictate how you proceed with your migration. One extreme is a complete outage, another is an online migration by taking advantage of host multipathing (as guys alluded to above). Let's wait for you to finish doing your homework
zhaos2
643 Posts
0
May 14th, 2015 18:00
Hi, the below procedures are for your reference only
Cisco Switch Replacement Procedure
1: Preparation and data collection on original switch
switch# copy running-config startup-config
switch# copy startup-config tftp://server-IP-address/config-filename & show tech-support detail
switch# show flogi database
2: Obtain license information
switch# show license host-id
switch# show license
3: Move components from old switch to new switch
4: Configure new switch
Example:
switch2# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch2(config)# int mgmt 0
switch2(config-if)# ip address ipadress subnet
switch2(config-if)# no shut
Example:
switch2#configure terminal
switch2(config)#vsan database
switch2 (config-vsan-db)# vsan
switch2 (config-vsan-db)#exit
At this time the VSAN will be created with a random domain-id.
Example:
switch2#configure terminal
switch2(config)# fcdomain domain static vsan
switch2 (config-vsan-db)#exit
Example:
snmp-server user admin network-admin auth md5 0x46694cac2585d39d3bc00c8a4c7d48a6 localizedkey
snmp-server user guestadmin network-admin auth md5 0xcae40d254218747bc57ee1df348 26b51 localizedkey
Example:
zone name Z_1 vsan 9
member interface fc1/9 swwn 20:00:00:0d:ec:02:1d:40
Example:
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
Example:
switch(config)# fcsp dhchap devicename password 7 asdflkjh
Example:
switch(config-port-security)# swwn 20:01:33:11:00:2a:4a:66 interface port-channel 5
switch(config-fabric-binding)# swwn 21:00:05:30:23:11:11:11 domain 102
Example:
switch(config-fcalias)# member fwwn 10:01:10:01:10:ab:cd:ef
Example:
switch(config-port-security)# pwwn 20:11:00:33:11:00:2a:4a fwwn 20:81:00:44:22:00:4a:9e
Example
switch2# copy tftp://server IP address/config_file_name running-config
zhaos2
643 Posts
0
May 14th, 2015 18:00
Hi Jeff, great to see you here again!
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 14th, 2015 19:00
step 8, why would you reboot the switch that you just moved your production devices to. Should it be done before you move systems to it ?