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

Merge Compaq StorageWorks 16 and SilkWorm 3200

 
SOLVED
Go to solution
Occasional Visitor

Merge Compaq StorageWorks 16 and SilkWorm 3200

Currently we have two SANs and we want to merge into 1 fabric SAN.

SAN 1 (EVA 3000) consists of two SilkWorm 3200 switch. Fabric OS (tm) Release v3.2.0a

SAN 2 (HSG whit MA8000/RA8000) consists of 1 compaq sanwork 16 switch. Kernel:5.4, Fabric OS: v2.6.2c

On EVA system i have
W2003, W2000 and Linux(rehdat)

On HSG system i have
W2000, Tru64 (both boot from SAN)

What steps do I need to merge into fabric??
How the modification will affects the addressing mode on tru64 and windows2000?

Thank you
15 REPLIES 15
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Hi,
the best reference doc to this could be this:
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf
the pain is one part of the reality
Highlighted
Valued Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

A few things to keep in mind:
- Update the firmware to the same levels
- RA_TOV, ED_TOV and PID settings are identical on both switches ("configure" command)
- Domain ID's are different.
- No zoning naming duplication.

The way I prefer to merge fabrics is to set up all of the zoning on one switch prior to the merge, then when it comes time to merge clear the config on the switch that does not contain all of the zoning info.

cfgdisable
cfgclear
cfgsave

Those commands will remove all zoning info.

Good Luck.
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

"- Update the firmware to the same levels "

a v2.x (1GB SAN Switch) can not go to 3.x firmware (2GB SAN Switch).

Make sure the switch firmware's are at the latest supported levels. Follow the recommendations in the release notes for the latest 3.x firmware.

For Windows, you should not see any addressing changes.


Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Hi,

The modifications shouldn't affect the Tru64 systems.

You would usually identify the disks on the HSG80 with the Unit Identifier, so nothing should change with regards to the addressing.

Cheers,

Rob
Highlighted
Occasional Visitor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

First, I want to thank you for your time. I appreciate your help.

Do i need to reconfigure something in my tru64 or windows 2000??

If something go wrong can i rollback the changes?? The change would affect the tru64 and windows2000

Thnks
Highlighted
Honored Contributor
Solution

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Hi,

No. I don't think you'll have to reconfigure anything, at least not on Tru64 - not sure on Windows...

What version of Tru64 are you running ?

Can you post the output of the switchShow command from each of the three switches ?

Cheers,

Rob
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Hi,
you can find some other general fabric merge information also in e.g.

a)the new Brocade OS admin guide (does not matter that it is not yours FABOS because the general rules did not change) pages 231-232
http://www.brocade.com/education_services/docs/BCAF_docs/01_53_1000598_03_FOSAdminGuide_v610.pdf

b)FABOS 6.1.0 Troubleshooting guide (for the fabric parameters which have to be identical before the successful merge) p.31

http://www.brocade.com/education_services/docs/BCAF_docs/04_53_1000853_01_TroubleshootingGuide_v610.pdf

c) summary of the fabric merging/joining prerequisites in this thread:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1269689


the pain is one part of the reality
Highlighted
Occasional Visitor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

here is the output of switchshow command

sanWork16:admin> switchshow
switchName: sanWork16
switchType: 2.4
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:60:69:12:09:fc
switchBeacon: OFF
Zoning: OFF
port 0: -- No_Module
port 1: sw No_Light
port 2: sw Online F-Port 50:00:1f:e1:00:03:05:72
port 3: sw Online F-Port 10:00:00:00:c9:31:14:7a
port 4: sw Online F-Port 50:00:1f:e1:00:20:0f:61
port 5: -- No_Module
port 6: sw Online F-Port 50:00:1f:e1:00:03:05:71
port 7: sw Online F-Port 10:00:00:00:c9:21:7a:d7
port 8: sw No_Light
port 9: sw Online F-Port 10:00:00:00:c9:21:cf:06
port 10: -- No_Module
port 11: sw Online F-Port 50:00:1f:e1:00:20:0f:62
port 12: sw Online F-Port 10:00:00:00:c9:21:d0:31
port 13: sw Online F-Port 10:00:00:00:c9:21:d3:ef
port 14: sw Online F-Port 10:00:00:00:c9:2f:79:21
port 15: -- No_Module


Switch2:admin> switchshow
switchName: Switch2
switchType: 16.2
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:60:69:c0:a0:2d
switchBeacon: OFF
Zoning: OFF
port 0: id N2 Online F-Port 50:00:1f:e1:50:03:3f:99
port 1: id N2 Online F-Port 50:00:1f:e1:50:03:3f:9d
port 2: id N2 Online F-Port 10:00:00:00:c9:3d:17:06
port 3: id N2 Online F-Port 50:01:10:a0:00:3d:d8:68
port 4: id N2 Online F-Port 50:05:08:b2:00:c4:f6:12
port 5: id N2 Online F-Port 50:05:08:b2:00:7e:47:33
port 6: id N2 Online F-Port 50:05:08:b2:00:c5:4f:f2
port 7: id N2 Online F-Port 50:05:08:b2:00:7e:4f:02

Switch1:admin> switchshow
switchName: Switch1
switchType: 16.2
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:60:69:c0:a2:07
switchBeacon: OFF
Zoning: OFF
port 0: id N2 Online F-Port 50:00:1f:e1:50:03:3f:98
port 1: id N2 Online F-Port 50:00:1f:e1:50:03:3f:9c
port 2: id N2 No_Light
port 3: id N2 Online F-Port 21:00:00:e0:8b:8c:b0:0e
port 4: id N2 Online F-Port 21:00:00:e0:8b:8c:a9:0d
port 5: id N2 Online F-Port 50:05:08:b2:00:c4:fb:a3
port 6: id N2 Online E-Port 10:00:00:05:1e:03:cd:04 "swd77" (upstream)
port 7: id N2 Online F-Port 50:05:08:b2:00:c4:fe:13

Thnks
Highlighted
Honored Contributor

Re: Merge Compaq StorageWorks 16 and SilkWorm 3200

Tru64 Unix does persistent LUN binding.
Neither T64 nor Windows are affected if the N_port ID also-known-as FCID aka 'pid' aka (= 24-bit Fibre Channel address) of a HSG host port has changed during a shutdown/reboot cycle.
.