UNSOLVED

ironcheflouie

updated

18 years ago

0

1873

August 13th, 2008 13:00

Consolidating MDS Switches

Hello all. I am a few months into the MDS world and need to consolidate 2 x 9210 (all host dual connected) to 2 x 9222i. Currently, our CX700 is connected to the 9210's and the CX3-80 is connected to the 9222i's.

I am forming a plan as follows:

1. 9222i - create fcalias ahead of time with pwwn via cli (FM will not see pwwn if not physically connected)

2. 9222i - add fcalias to zone, add zone to zoneset, activate and save via FM

3. Move a pair of sp frontend port with "all" host connected to it (must be done in pairs since each hba is zoned with 2 sp ports). This will result with a single host connected to a 9210 and a 9222i

4. Restart NaviHostAgent

5. Move the remaining sp pairs every weekend until everthing is migrated over

Questions for the experts:

1. What do you think about the plan above. How would you make it better?

2. I already have a different vsan setup on all switches. I do not plan to migrate the vsan over. Everything will be on vsan 50 on one switch and vsan 60 on the other. With that said, do you see any reason why I should at least create two vsans, one for each Array? I'm not looking for theory but practical reasons.

3. Is there a bandwidth limitation on a vsan?

Finally, we do not have performance issues today (top talking sp port is < 10%), and would like to leave it as simple as possible. The number of ports should be plenty for the next 3 years. I do not envision creating ISL's to other switches. I will like to use iSCSI at some point so not sure how it needs to factored in today.

Sorry for the loaded questions, it snowballed as I was writing.

Thanks.
  • RRR

    6 Operator

    5739 Posts

    607

    0

    Posted August 14th, 2008 00:00

    What's a 9210 ?
  • hersh1

    197 Posts

    607

    0

    Posted August 14th, 2008 05:00

    Overall I think your planning looks good. We did the same thing a month or so ago and if you have all the zoning configured prior to the move it is extremely easy (just moving cables). Is there a reason you would take multiple weekends to complete this?

    If I understand what your saying with 1. you can create aliases in FM by right clicking on a VSAN and selecting "Edit Local Full Zone Database". In there right click FC-alias and select insert.

    I don't think there is a bandwidth limit for a VSAN, my thinking is that if there was a limit and you ran the switch with 1 VSAN Cisco would be putting you in corner with regards to bandwidth.
  • 607

    0

    Posted August 14th, 2008 07:00

    Thanks dynamox. I have that info already. I was curious on how hersh migrated his switches using only FM. CLI will be needed to "pre-configure" the fc-alias.

    Thanks.
  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    607

    0

    Posted August 14th, 2008 07:00

    is this what you need ?


    Create Aliases

    1.Conf T
    2.Fcalias name [SERVER_NAME_HBAx] vsan [XX]
    3.Member pwwn [world wide name]
    4.Exit
    5.end

    Create Zones

    1.Conf t
    2.Zone name [ZNE_SERVER_STORAGE] vsan [XX]
    3.Member Fcalias [SERVER_NAME]
    4.Member Fcalias [STORAGE_NAME]
    5.Exit

    Add Zone to Active Zoneset

    1.Zoneset name set[XX] vsan [XX]
    2.Member [ZNE_SERVER_STORAGE]
    3.End

    Activate Zoneset

    1.Conf t
    2.Zoneset activate name set[XX] vsan [XX]
  • 607

    0

    Posted August 14th, 2008 07:00

    Thanks for the feedback hersh.

    But getting back to what you said, how did you pre-configure a fc-alias via FM if there is not flogi? In FM, it's all point and click and if the host is not physically connected to the new switch, I don't see how you can click/grab the pwwn.

    Thanks.
  • 607

    0

    Posted August 14th, 2008 10:00

    A couple of pieces of the equation that would be helpful to know would be what kind of hosts are involved? Are you using HP or AIX hosts? Also do you have existing connections (ISLs) between the two switches now?

    Thank you.
  • 607

    0

    Posted August 14th, 2008 11:00

    Hello,

    Process overall looks good to me. No guaranties though as the unexpected can always happen.

    I would definitely think about placement of multiple paths to different switches / modules / port groups to maximize redundancy. You also might want to look into configuration of more VSANs and DPVM at the same time. This would allow for better peformance, redundant services for failures, and allowance for ports to be moved easily if they fail.

    Thank you.
  • 607

    0

    Posted August 14th, 2008 11:00

    Hey CiscoKid. No ISL. We are running Microsoft 200x and ESX 3.x. On the 9222i's, we have the 18 and 24 port mod, more than enough FC ports. I will want to use iSCSI at some point (4 x GigE ports) but down the road.

    When all said and done, I expect no more than 25 host in production.

    Thanks.
  • 607

    0

    Posted August 14th, 2008 13:00

    How would I gain performance by creating a vsan?

    Thanks.
  • hersh1

    197 Posts

    762

    0

    Posted August 15th, 2008 07:00

    I have taken a screen shot of where you can manual type WWNs into FM. Not sure how I can get that to you other then email (doesn't look like we can post on here or even send PMs). My internet access here at work blocks online file storage, so if your patient you will have to wait until Sunday/Monday.

    I tend to use both the CLI and FM it really depends how many I'm doing and what's currently open. But I would say mass changes are much easier in CLI.