• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2319
  • Last Modified:

Migrating From Cisco MDS 9124 Multilayer Fabric Switch to 9148 Multilayer Fabric switch

I am currently working on a project where i need to migrate from Cisco MDS 9124 to MDS 9148 Multilayer Fabric Switch. I am novice to this technology and havent worked on it before. At the moment we got 24 different servers connected to this Cisco MDS 9124 Switch and i need to move all these 24 servers connection to new MDS 9148. The thing which i need to put into consideration is the downtime which my servers will have during this migration and how much time will it take to do it.

Can someone please advise how should i start attempting this project and secondly how much downtime one think will we be having for this whole migration. The servers we are running are all Windows 2003 servers.
In addition can someone also help me in making a project document for this project too and how can i go about the configuration of the new switch
0
novice1980
Asked:
novice1980
  • 4
  • 3
1 Solution
 
novice1980Author Commented:
Anyone got any idea about this one
0
 
Duncan MeyersCommented:
You can perform the migration with zero downtime if each SAM-attached server has dual HBAs. If the servers have a single HBA, then you'll need a reboot for each host - so allow 15 minutes per host.

The easiest way to tackle this is to hire an expert - the couple of thousand dollars it'll cost you will be money well spent. Having said that, here's an outline of how you'd tackle the migration:

Perform base config of the MDS9148 (management IP etc)
Check that the MDS9148 domain ID is numerically higher than the MDS9124 domain ID
Connect the MDS9124 and MDS9148 via a fibre channel cable
Merge the fabrics. This copies the configuration to the new switch
Move storage array ports one-by-one to the new switch. Check host connectivity is ok after you move each port
Move host ports across to the new switch - live if you gave more than one HBA per host.
Done!

There are additional steps if you have AIX or HP-UX servers.
0
 
novice1980Author Commented:
Thanks meyersd for your reply and guidence. I can tell little bit more about the cables currently attached to my MDS9124 switches.

1) We have few cables attached from SAN controllers to both switches.
2) We have few tape drives attached to both switches
3) We have few servers with dual HBA and they are attached to both switches
4) We have few nodes of Oracle servers attached to both switches.
5) We have few servers with single HBA attached to both switches

Can you please guide me through what will be the downtime for all the above instances

Perform base config of the MDS9148 (management IP etc)

I understand this bit of yours, may be i may to assign the Ip address to the management switch by connecting to it through Console via DB9 connector is that correct

Check that the MDS9148 domain ID is numerically higher than the MDS9124 domain ID

Why we need to have a higher numerically domain ID for our MDS9148 switch

Connect the MDS9124 and MDS9148 via a fibre channel cable

Should i connect both of mine MDS9148 switches to both of mine MDS9124 Switches

Merge the fabrics. This copies the configuration to the new switch

Is there any command or instruction given by which i can merge the fabric and by this way it will copies all the configuration to the new switch

Move storage array ports one-by-one to the new switch. Check host connectivity is ok after you move each port

You mean move each cable one by one from one of mine MDS9124 switches to MDS9148 switches

Move host ports across to the new switch - live if you gave more than one HBA per host.

Sorry didnt understand this bit


In addition can you please guide me through what is the major difference between Host ports and Storage Array ports.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
novice1980Author Commented:
Hello Meyersd,
Is it possible for you to help me little bit more please by answering to my queries mention above.
Thanks again for your help
0
 
Duncan MeyersCommented:
>Perform base config of the MDS9148 (management IP etc)

>I understand this bit of yours, may be i may to assign the Ip address to the management switch by connecting to it through Console via DB9 connector is that correct

Yes - that's correct.

>Check that the MDS9148 domain ID is numerically higher than the MDS9124 domain ID

>Why we need to have a higher numerically domain ID for our MDS9148 switch

Because the domain ID determines which switch will become the master in a FC fabric. The master switch copies its config to all subordinate switches. You can use this behaviour to help you migrate to your new switches. But you must also be careful - I'm sure you can imagine what would happen if you connect a switch with a blank configuration that becomes domain master...

>Connect the MDS9124 and MDS9148 via a fibre channel cable

>Should i connect both of mine MDS9148 switches to both of mine MDS9124 Switches
You should connect one new MDS9148 to only one MDS9124 like so:

[] MDS9124 switch 1      [] MDS9124 switch 2
 |                                     |
[] MDS9148 switch 1      [] MDS9148 switch 2

>Merge the fabrics. This copies the configuration to the new switch

>Is there any command or instruction given by which i can merge the fabric and by this way it will copies all the configuration to the new switch

The fabric merge is automatic once you connect the inter-switch links

>Move storage array ports one-by-one to the new switch. Check host connectivity is ok after you move each port

>You mean move each cable one by one from one of mine MDS9124 switches to MDS9148 switches

Yes - that's correct

>Move host ports across to the new switch - live if you gave more than one HBA per host.

>Sorry didnt understand this bit
You can move the dual-attached hosts with zero downtime by moving one port at a time.

Once you've moved all the storage and hosts to the new switches, you can disconnect the old switches one at a time. MAke sure you check that the paths are OK after each step. Job done.

>In addition can you please guide me through what is the major difference between Host ports and Storage Array ports.
I mean that a host port is a port that a host connects to. A storage port is a port where the storage array connects to the switch.
0
 
novice1980Author Commented:
Thanks meyersd for your reply and guiding me through. I would like to thank you personally for the time you spend in replying to my queries and helping me out.

Take care
0
 
Duncan MeyersCommented:
Thanks! Glad I could help.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now