1863015 Members
1512 Online
110446 Solutions
New Discussion

Re: LUN

 
Kosmider
Occasional Contributor

LUN

HI,

I've got two servers HP9000 L2000 (HP-UX 11.00, SrviceGuard cluster ) that is connected via a fibre switch to a VA7400.
I defined a new LUN on array, and added the LUN's to a volume group.
I can't see new LUN's after "armtopology" command.
If I import volume group to next server the message "The volume
group already exist" is appears on console and volume group is
not imported.
5 REPLIES 5
Slawomir Gora
Honored Contributor

Re: LUN

Hi,

before you import group to next server
you must run:
a) vgexport vg_name
b) mkdir /dev/vg_name
c) mknod
d) vgimport

Shaikh Imran
Honored Contributor

Re: LUN

Hi Krzysztof KoÅ mider,

I think you are facing 2 different problems
1) LUN not getting detected as a disk on HP &
2) vgimport giving error.
For (1) :
I will ask you
a) whether he server was restarted after creating the LUN ?
b) have you done insf -e to create the device files for the new LUN ?
c) what is the o/p of
ioscan -fnC disk
what is the status of the LUN at the expected path ?
d) Try using amdsp command from unix just to
see the LUNs status intead armtopology.
(see man amdsp for details )

For (2)
This problem can be either
1) the volume group name you are giving is already in use or
2) the minor number you are giving is
already in use.

Regards,
I'll sleep when i am dead.
Kosmider
Occasional Contributor

Re: LUN

1. Volume group exists on both servers.
I've done changes ( i added new LUN to volume group) on one server.
I woud like to make the same changes on the second server.
Do I have to remove the volume group on second server befor import?

2.I restart both servers after creating LUN.
I do insf -e.
ioscan - status new LUN CLAIMED.
armdsp - status new LUN ACTIVE.
but armtopology don't display new LUN.
Slawomir Gora
Honored Contributor

Re: LUN

Hi,

Do I have to remove the volume group on second server befor import? - yes

steps are:
1. on node1
a) vgexport with preview mode
vgexport -p -s -m vgname.map vgname
b) copy map file to node2
c) rcp vgname.map node2:
d) deactive group
vgchange -a n vgname
vgchane -c n vgname

3. on node2
a) remove old vg
vgexport vgname
b) mkdir /dev/vgname
c) mknod /dev/vgname/group c 64 0xXX0000
d) vgimport -s -m vgname.map vgname
e) vgchange -a y vgname
f) vgcfgbackup vgname
e) vgchange -a n vgname
f) vgchange -c y vgname

Geoff Wild
Honored Contributor

Re: LUN

If LUN isn't seen by other node, then you have a LUN masking issue....

Once you resolve that, then you can

ioscan -fnC disk
insf -e

vgexport /dev/vgXX
mkdir /dev/vgXX
mknod /dev/vgXX/group c 64 0xHH0000
vgimport -s -v -m /tmp/yourmapfile /dev/vgXX

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.