EVA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

Merge Compaq StorageWorks 16 and SilkWorm 3200

 
SOLVED
Go to solution
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Hi,

Your switchShow output shows that all of the switches currently have the same Domain ID, which isn't recommended. As mentioned previously each switch should have a different Domain ID.

It also appears that you have another switch connected to port 6 of Switch1.

You should check that out...

Cheers,

Rob
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Just also noticed that you don't appear to be using any Zoning.

You really should implement this to prevent any hosts being able to access storage they shouldn't...

Cheers,

Rob
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Resume

MUST
1. you need to check the switch77 and its parameters before you start to do anything
therefore telnet/ssh swd77
fabricshow
(you should see 2 switches ->swd77 and switch1. If it is so, then you have one fabric with 2 switches allready....
and you should see also their domain ids ->
from this is clear that the switch1 has domain id=1 and the swd77 has some other domain id.

2. the second must is zoning
you should zone all your hosts to communicate only with the relevant storages to isolate the Tru64 and Windows host and and the EVA3000,MA8000 and RA8000 communication. Otherwise you are risking the non stable fabric which is useless

so you can start with the swd77 and switch1 with defining the zoning - the rule is to isolate each host/storage host/lib, etc. communication...


OTHER THINGS
switch2 does not have any free ports for the ISL interconnection with the 2 other switches

sanwork16 has the port number 8 available for the ISL interconnection

Solution
you should free one port of the switch2 by adding the new SFP to the sanwork16 ports 0,5,10 or 15 which have no module (maybe from the swd77 if it is there unused - it will have no light)

Procedure

you can start the procedure to which you unfortunately need the downtime, because you need to disable the switch2 and sanwork16
Procedure


you need to do the following
telnet/ssh the switch2 and input the following commands:
switchdisable
configure

then choose the
switch fabric settings
and change the domain to the unused value
check all the fabric setting - must be identical in all switches except the domain id

then telnet/ssh the switch2 and give it the domain id from the unused values
check all the fabric setting - must be identical in all switches except the domain id

cable the switch2 and sanwork16 switches to the existing fabric

and switchenable the switch1
then fabricshow -> check if you see
3 switches, it is ok and you can add the connected hosts/storages into the zone

switchenable the switch2
then fabricshow -> if you see 4 switches, it is ok and you can add the connected hosts/storages into the zone.

then its done

The 3rd must
is upgrading the switches firwmare to be
either on the same version or on the latest/supported version.....


the pain is one part of the reality
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

errata :-)

in the section of my previous and longest post :-)

cable the switch2 and sanwork16 switches to the existing fabric

i wrote switchenable the swtich1 which is obviously sanwork16
the pain is one part of the reality
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Sorry I am repeating my whole long post once more to avoid any your possible confusion and mistake:

Resume

1st MUST
1. you need to check the switch77 and its parameters before you start to do anything
therefore telnet/ssh swd77
fabricshow
(you should see 2 switches ->swd77 and switch1. If it is so, then you have one fabric with 2 switches allready....
and you should see also their domain ids ->
from this is clear that the switch1 has domain id=1 and the swd77 has some other domain id.

2nd MUST
2. the second must is zoning
you should zone all your hosts to communicate only with the relevant storages to isolate the Tru64 and Windows host and and the EVA3000,MA8000 and RA8000 communication. Otherwise you are risking the non stable fabric which is useless

ZONING THE ORIGINAL 2 SWITCH FABRIC
so you can start with the swd77 and switch1 with defining the zoning - the rule is to isolate each host/storage host/lib, etc. communication...


OTHER THINGS
switch2 does not have any free ports for the ISL interconnection with the 2 other switches

sanwork16 has the port number 8 available for the ISL interconnection

SOLUTION
you should free one port of the switch2 by adding the new SFP to the sanwork16 ports 0,5,10 or 15 which have no module (maybe from the swd77 if it is there unused - it will have no light with the plugged SFP)

JOINING/MERGING THE FABRIC
you can start the procedure to which you unfortunately need the downtime, because you need to disable the switch2 and sanwork16

a)telnet/ssh the switch2 and input the following commands:
switchdisable
configure

then choose the
switch fabric settings
and change the domain to the unused value
check all the fabric setting - must be identical in all switches except the domain id

then telnet/ssh the sanwork16 and give it the domain id from the unused values
check all the fabric setting - must be identical in all switches except the domain id

c) cable the switch2 and sanwork16 switches to the existing fabric
and switchenable the switch2
then fabricshow -> if you see
3 switches, it is ok and you can add the connected hosts/storages into the zone

switchenable the sanwork16
then fabricshow -> if you see 4 switches, it is ok and you can add the connected hosts/storages into the zone.

then its done

3rd MUST
is upgrading the switches firmware to be
either on the same version or on the latest/supported version.....
the pain is one part of the reality
Highlighted
Occasional Visitor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Thank you very much guys, your help was very useful. See you.