Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2183

June 10th, 2009 00:00

Changing Brocade DS200B with DS-5100B switch

Hi,

To get more ports we intend to change 2 brocade DS200B (redundent) with
2 DS5100B, what is the best way to proceed for a configuration with many
servers running (but can be stopped during the night).

Thanks for answer

Consty

2.1K Posts

June 18th, 2009 09:00

I didn't see this thread earlier, but I'll jump in now anyway...

I'm not sure what you are referring to as 'Register' and 'deregister'. From what you have described you just need to move the physical connections from the hosts and storage to the switches from the old ones to the new ones while all the switches are ISLed together.

So steps would be like this:

* ISL the 5100B switches together
* ISL the 5100B switches to the 200B switches
* move your host connections from the old switches to the new switches one connection at a time
* move your array connections from your old switches to the new switches one port at a time
* Remove the ISLs between the 200B and 5100B switches

The only thing you may have to worry about is if you have AIX (and I believe HP-UX may have similar problems). AIX specifically can have trouble with end points of SAN connections moving. Unless they are very new and properly configured for Dynamic Tracking, you may need to rescan for new paths and get rid of old paths on your AIX hosts each time you move one of their connections. To be safe you should check the available paths for the AIX hosts each time you touch any of their paths to see if you need to fix something before you move the next connection.

219 Posts

June 10th, 2009 06:00

It depends on. Here are some questions:

Use the server multipathing software?!
What storage system are connect?!
Is there one fabric or two fabrics?!
What type of zoning is used (port/wwn based?!

232 Posts

June 10th, 2009 14:00

Thanks for your answer,

These are the answers to yoiur questions :

-Multipathing : 2 servers uses Powerpath, the others MPIO (all Solaris)
-Storage : They are connected to CX3 10C will be migrated later on to CX4 240
-Is there one or 2 fabrics : 1 fabric
-Type of zoning : WWN based

Regards

Consty

219 Posts

June 11th, 2009 03:00

ok, that`s look fine.

Two more questions:
Will you still run with 1 fabric?
So, all server use multipathing?

232 Posts

June 11th, 2009 17:00

Yes, I will still run with 1 fabric
Yes, with the same multipathing issue.

Thanks

219 Posts

June 12th, 2009 05:00

Then I think it`s easy.

Connect your new 5100 to your currunt environment and get them into your fabric. So Domain ID have to be unique and no zoning have been done on new switches.

After that you could move second path per server and FA Port of CX to new switches. After this you could move first path to new switches. But first look which pathes are active!! I would choose standby path to move and then change standby to active path and move "new" standby path... Last you have to move principal switch to a new one.

I think that`s it... Could somebody verify this procedure?!

232 Posts

June 16th, 2009 03:00

Thank you for your response, please I need on precision,
Should I Deregister from the old switch, then Register on the new ?

Regards

Consty

1 Rookie

 • 

5.7K Posts

June 19th, 2009 05:00

AIX and HP-UX have that FCID "problem" you mentioned indeed.

2 Intern

 • 

1.3K Posts

June 20th, 2009 11:00

FICD problem (device file change )comes when the "end" connections are moved either at host or array side.

232 Posts

January 20th, 2010 09:00

Hello,

I come back to this issue because the switch migration was postponed,

please how to ISL switches ?

What do you think about uploading switch configuration, stopping everything

and disconnecting the old switch, then downloading the configuration into

the new switch, connecting then starting everything again ?

The servers are running Solaris with MPIO as multipathing, any precaution

to take ?

Thanks

Regards

2.1K Posts

January 25th, 2010 10:00

Sorry for the delay Consty, I was going to try to get back to this at the end of last week, but work got in the way :-)

So, I'm still going to strongly recommend you go the route of ISLing the new switches to the old ones first. ISLing is actually very simple. Assuming that the configuration of the switch ports has not been changed to prevent "E" type connections, you can ISL two switches together by simply connecting a port on each with a patch cable. If the ISL is successful, the two "fabrics" (in this case each fabric starts out as an individual switch) will merge to become a single fabric. The Zoning databases will merge and the switches will synchronize. You can tell for sure that this has happened by looking in the interface to see the port type. A port with storage or a host logged in will be an F port. If the ISL has established you will see the port configured as an E port.

A few things to consider to make sure that you can ISL successfully:

  • The ports on both switches must be configured to allow E type connections. This should be the default
  • The zoning database from each switch will merge, so you should ensure there are no zones that will conflict. In your case one switch likely won't have any zones defined at first anyway, sp it shouldn't be an issue
  • You can't ISL two switches together if the Domain IDs are the same. Make sure the Domain ID on the new switches are different from the existing switches.
  • You will want to confirm that the "Compatibility" mode on both switches are consistent. This can be found on the Compatibility tab under Configuration when you enable Advanced Mode in the Switch Administration dialog (this is for the Web interface which I'm most familiar with). You are probably going to want both set to Brocade Native

Once you have ISLed, and completed your move to the new switches, if you want to remove the 200s it is simply a matter of disconnecting them from the 5100s. The ISL will be broken automatically and you don't have to do anything special to prepare for it.

The other thing you will want to consider as you move connections over is that a single ISL can cause problems in the long run. If it fails your fabric will segment and (obviously) anything that needs to talk across the ISL will fail. Once you get the initial ISL established you may want to add a second one for safety sake. You may also add additional ISLs if you have lots of traffic crossing the ISLs at some point and don't want to artificially "throttle" it.

232 Posts

January 25th, 2010 14:00

Thanks Allen,

Ok for ISLing, do I need a license for that ?

Regards

Consty

2 Intern

 • 

20.4K Posts

January 25th, 2010 21:00

you need a license only if you want to combine multiple ISL into one trunk, otherwise you don't need one.
No Events found!

Top