This post is more than 5 years old
2 Intern
•
125 Posts
0
714
March 16th, 2009 23:00
replace switch: what will change
I have a HP UNIX cluster(two node) connect to a EMC DMX800 with dual fabric, each fabric is a brocade 2800 switch( a very old switch with SC port). now i want to replace the switch with brocade 5000 series switch. what will change in this replacement? any suggestion?
i heard of that since the core PID of these two generation switch is different(0, 1), so the device number(c#t#d#s#) in HP host will change, but i don't know if the LV or VG will be affected.
and should the config in DMX800 be modified? also since the device number changed, the quorum disk of HP cluster should be modified, is this true?
i heard of that since the core PID of these two generation switch is different(0, 1), so the device number(c#t#d#s#) in HP host will change, but i don't know if the LV or VG will be affected.
and should the config in DMX800 be modified? also since the device number changed, the quorum disk of HP cluster should be modified, is this true?
No Events found!


xe2sdc
6 Operator
•
2.8K Posts
0
March 17th, 2009 03:00
However before moving the thread, let me try to answer your question...
1) core pid is the last of your problems .. HPUX binds virtual controllers to switch port FCID. Moving from old to new switches probably will change the domain identifier and possibly also switch port where the storage is connected.
2) changing any of _storage port number_ or _switch DID_ will impact the "hardware path" used by HPUX to identify your disks. This will change the c#t#d# (I guess hpux isn't using slices since hpux 9) and will definitly impact LVM.
3) LVM stores its configuration in a file (/etc/lvmtab) that you can't change via usual editors. lvmtab contains name of all disks belonging to all VGs. You have to update lvmtab before c#t#d# changes (removing soon-to-be-removed paths) via vgreduce command, migrate paths from old to new switches, discover new c#t#d# and add new paths to VGs (vgextend) to reflect thanges in lvmtab.
4) yep the quorum disk will be affected. Plan an offline of the whole cluster to reconfigure it when moving Cluster Locks to new paths. However probably someone may give better/different advices here
xe2sdc
6 Operator
•
2.8K Posts
0
March 17th, 2009 03:00
Whoops move that thread ..
Message was edited by:
Stefano Del Corno
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
1
March 17th, 2009 03:00
xe2sdc
6 Operator
•
2.8K Posts
0
March 17th, 2009 03:00
dingding1
2 Intern
•
125 Posts
0
March 17th, 2009 22:00
after this task completed, i will be back to post the replace procedure.