topic Re: Error vgimport (power path) in Operating System - HP-UX

Error vgimport (power path)

Eli Daniel — Sat, 20 Mar 2010 17:24:05 GMT

I have a problem with serviceGuid. sapl907 were assigned to disk (primary node), and disk sapl909 (node Secundary) when I run the command vgimport (formerly vgexport in sapl907 run command) on the secondary node sapl909 shown:

SAPL909: / tmp/hp/rfc19032010> vgimport-m. / VgBWaudit.map-s-v vgBWaudit
Beginning the import process on Volume Group "vgBWaudit.
Could not access the list of physical volumes for volume group "/ dev / vgBWaudit"

the disk were assigned from EMC SAN Sumetric
I have to run any command with the path powet?
powermt display: see the disks, just run this command

Re: Error vgimport (power path)

Victor Fridyev — Sat, 20 Mar 2010 18:58:38 GMT

Hi,

Before you run vgimport, try to do the following:
1. Define the disks which belong to the volume group
2. mkdir /dev/vgBWaudit
ls /dev/vg*/groUp #
mknod -c 64 0x0N0000 # N here is a number, it must be unique and can be found from the above ls command
3 vgimport -m /VgBWaudit.map /dev/vgBWaudit /dev/dsk/disk1 /dev/dsk/disk2 etc, where disk1,disk2 etc - disks of the volume group.

This is old style, but it works 8)))

HTH

Re: Error vgimport (power path)

Eli Daniel — Sat, 20 Mar 2010 19:41:32 GMT

Hi Victor,

disk1,disk2 These disk are the primary node?

are showing vgexport disk? on the primary node

Re: Error vgimport (power path)

Eli Daniel — Sat, 20 Mar 2010 20:14:19 GMT

for example:

Nodo primary sapl907
run vgexport :
disk30
disk40

nodo secundary sapl909
run vgimport -m vgaudit.map -s -v vgaudit disk30 disk40??
this is correct??

if there vgimport before running disk disk30 disk40 used by another vg. there is any problem?

Re: Error vgimport (power path)

Benoy Daniel — Sun, 21 Mar 2010 01:45:04 GMT

Verify the disk is visible at secondary node before you vgimport

Re: Error vgimport (power path)

Eli Daniel — Sun, 21 Mar 2010 02:16:40 GMT

powermt display:
Symmetrix logical device count=22
CLARiiON logical device count=0
Hitachi logical device count=0
Invista logical device count=0
HP xp logical device count=0
Ess logical device count=0
HP HSx logical device count=0
==============================================================================
----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------
### HW Path Summary Total Dead IO/Sec Q-IOs Errors
==============================================================================
21 1/0/14/1/0/4/0.20.36.0.0 optimal 8 0 - 0 0
23 1/0/14/1/0/4/0.20.36.0.1 optimal 14 0 - 0 0
25 UNKNOWN failed 11 11 - 0 0
27 UNKNOWN failed 6 6 - 0 0
28 UNKNOWN failed 3 3 - 0 0

what happens if I run the following command?

September powermt policy = so dev = all

All path are activated?

Re: Error vgimport (power path)

Johnson Punniyalingam — Sun, 21 Mar 2010 02:31:03 GMT

>>>if there vgimport before running disk disk30 disk40 used by another vg. there is any problem?<<<<

no problem -> if that vg is not active in secondary Node, if the vg is active "it would blow vg info from your "lvmtab"

so if i am correct in your case you have added new disks to cluster aware vg in(Pri-Node) you need to update the change to (Sec-Node)

you are using (DSF) legacy device file so -N option while help to convert while importing the vg to secondary)

normal practise when you add (new vg to cluster aware VG ) we always "vexport -p" perview options -s -m mapfile all were the (vg is active)

Primary Node:-
pvcreate,
vgextend
vgexport -p -s -v -m /tmp/vgname.map /dev/vgname
# rcp /tmp/vgmax4.map nodee2:/tmp/vgmax4.map

Secondary Node:-

# vgexport /dev/vgname

# mkdir /dev/vgname

# mknode /dev/vgname/group c 64 0x030000

# vgimport -N -p -s -v -m /tmp/vgname.map /dev/vgname

(if above preview show no errors than proceed to vimport by removing -p preview options)

# vgimport -N -s -v -m /tmp/vgname.map /dev/vgname

Re: Error vgimport (power path)

Eli Daniel — Sun, 21 Mar 2010 04:27:14 GMT

there are 2 different divices logical, it affects this???

Nodo Primary
Server1:/> powermt display dev=all | grep "device ID"
Logical device ID=0E75
Logical device ID=0E80
Logical device ID=0E8B
Logical device ID=0E96
Logical device ID=13F9
Logical device ID=18C5
Logical device ID=18CB
Logical device ID=18D1
Logical device ID=18D7
Logical device ID=18DD
Logical device ID=18DF
Logical device ID=1BEC
Logical device ID=1BF1
Logical device ID=1BF6
Logical device ID=2098
Logical device ID=22D2""""""
Logical device ID=22D7""""""
Logical device ID=24FA
Logical device ID=24FB
Logical device ID=24FC
Logical device ID=24FD
Logical device ID=250D

Nodo secundary:
Server2:/> powermt display dev=all | grep "device ID"
Logical device ID=0E75
Logical device ID=0E80
Logical device ID=0E8B
Logical device ID=0E96
Logical device ID=13F9
Logical device ID=18C5
Logical device ID=18CB
Logical device ID=18D1
Logical device ID=18D7
Logical device ID=18DD
Logical device ID=18DF
Logical device ID=1BEC
Logical device ID=1BF1
Logical device ID=1BF6
Logical device ID=2098
Logical device ID=22E6"""""
Logical device ID=22EB"""""
Logical device ID=24FA
Logical device ID=24FB
Logical device ID=24FC
Logical device ID=24FD
Logical device ID=250D

Re: Error vgimport (power path)

Johnson Punniyalingam — Sun, 21 Mar 2010 05:05:18 GMT

Looks like "you are not able to see the disks ?

are you able to "pvcreate ,vgextend" to new disk assign to "Pri-Node" from EMC storage ?

# powermt check
# powermt config
# powermt check
# powermt display
# powermt save

It will= check and correct if there is any dead path

if Zoning should be correct, ioscan should show all paths corretly. Its only a powerpath problem, if I understand right.??

Once disk presented ,

# ioscan -fn
#insf -e
# ioscan -fnC disk

(than proceed to pvcreate,vgextend..etc) does you "vgextend" was sucesfull ?

Re: Error vgimport (power path)

Chandrahasa s — Sun, 21 Mar 2010 05:24:11 GMT

Hi,

Check with storage admin why in second node two lun id is defferent problem persits here .

Re: Error vgimport (power path)

Eli Daniel — Sun, 21 Mar 2010 10:13:41 GMT

to do with this command?
powermt check

whether or not the primary node and run the pvcreate, vgcreate and vgextend.

I am unclear powermt check command shows disk erase message

Re: Error vgimport (power path)

Eli Daniel — Sun, 21 Mar 2010 10:16:13 GMT

what happens if I run the following command?

September powermt policy = so dev = all

All path are activated?

Re: Error vgimport (power path)

Chandrahasa s — Mon, 22 Mar 2010 05:07:41 GMT

Hi

Go through link:
http://support.dell.com/support/edocs/stor-sys/powerpth/version4/uxqrefgd.pdf

Re: Error vgimport (power path)

Eli Daniel — Mon, 22 Mar 2010 19:48:03 GMT

Thanks for help