Change Of Switch Brocade

[Ivan_86]

Hello Guys.!!

In the company, have a EMC dmx2000 connect to 6 Hp9000 ( 2 particions of superdome, 3 N4000 and 1 v-class and some Sun's,)

We, need change the switch brocade of 16 to one of 32 ports, On my experience past, when change one brocade of one array XP512, the device files of the disk of the all boxes conected in this switch changed the names, reason why make import and later export with the new name of device files.

In the case of EMC can to happend the same.?

or

Sombody experimented something similiar.?

Thanks.!

[RAC_1]

I never worked on anything like this. But my (limited) understanding is that, if you keep same zoning, there should not be a problem.

[Denver Osborn]

If the new switch is given a different domain id, then the disk devices on the hpux nodes could change and along with it give you new instances/device files. LVM wouldn't be too happy about that.

how do you plan to migrate to the new switch?

will both the old and new switch be on the fabric at the same time while you selectively move the nodes over?

What model is the 16 and 32 port fc switch?

Do yuou know the PID format setting for the old/new switch?


-denver

[Stuart Abramson]

Ivan:

As you experienced before, and as Denver Osborne said above, the new switch will change the Device File Names of the disks in the VGs. This is because the Domain ID of the switch in the fabric, the Area ID and Port ID that you use on the switch in the fabric, influences the physical address of the disk, which influences the Device File Name.

If you decide to shut down and replace the switch(es) (I hope that you have two switches for HA.) you will have to vgexport and vgimport. Save mapfiles.

If you have two switches, and if all servers are connected dual access, you can do the change ON THE FLY, LIVE:

1. vgreduce ONE PATH of the PVs from the VGs.
o I mean all of the PVs from that FA
to all servers.
o Let's call this the 2nd path, because
the 1st path is still active and running.
2. Remove the volume(s) from the server
o Remove from PowerPath.
o Remove LUN masking.
o Remove zoning.
3. Connect FA to new switch.
4. Connect switch to new servers.
5. Zone new paths for 1/2 of all PVs.
6. LUN mask all PVs on 2nd path.
7. Discover 2nd path on all servers.
8. vgextend new 2nd path PVs to all VGs.

So, now you have all new PVs in all VGs on new switch. do the same thing for other path.

This is tricky and risky. Be careful.

[Kirby A. Joss · Accepted solution]

I've just about finished an EMC (brocade) to cisco migration using a variation of Stuart's ON-THE-FLY method. I offer a few additional suggestions:

1. There is no need to remove old LUN masking (until the end). We moved the FA and all host connections to new switch at the same time, so LUN masking was unchanged. In a previous (partial) migration we occasionally had to retreat (incomplete cleanup) and needed the old LUN masking to go back.

2. The old zones need not be removed unless there are ISLs (until the end), again to save time if you must retreat.

3. You may need to use fcmsutil replace_dsk to get the HBAs to log in to the new switch. Use fcmsutil get remote all to determine the N-Port-IDs.

[Stuart Abramson]

Kirby:

Good thinking. I'd give you points if I could...

Stuart

[Ivan_86]

Hi to all.!

The change to be moved to other day, but i take the cautions necesary for this.

EMC, say that change no affect to my boxes, but i make backups of LVM, maps of the disk and extract some files of configuration of the boxes. Their comments help me to gave a idea of the change.

Thanks.!

P.D The day of the change to be the next 18