Operating System - HP-UX
1834936 Members
2357 Online
110071 Solutions
New Discussion

Re: VM migration and disks instance numbers

 
Pierre Vassellerie
Occasional Contributor

VM migration and disks instance numbers

Hi,

I'm using SAN disks (EMC Symmetrix) for my guests. But of course, the agile device is disk60 on one server and disk 93 on another one. So the migration fails because it reports it cannot find the same disk instance on the target.
Is there a way to change the agile device numbering or should I go back to legacy devices ?

Thanks for your help.
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: VM migration and disks instance numbers

Shalom,

http://www.docs.hp.com/en/J6373-90022/J6373-90022.pdf

Also, you might want to try Ignite to replicate systems. It can deal with differences in agile device numbers.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
cjb_1
Trusted Contributor

Re: VM migration and disks instance numbers

we do this to manipulate disk id's

ioinit â f file

Where file takes the form
HW address Class Number
For example â 64000/0xfa00/0x4 disk 1

obviously you need id's that don't conflict.
Pierre Vassellerie
Occasional Contributor

Re: VM migration and disks instance numbers

Thans for your replies.
I'll try to be more clear.

On server1 I have my SAN device as:
disk45 / c4t1d0
Instance #: 19
Lunpath H/W Path: 0/7/1/0/4/0.0x5006048c53685f80.0x4008000000000000
HW Path: 64000/0xfa00/0x45

On server2 I have the same SAN device as:
disk96 / c4t0d7
Instance #: 12
Lunpath H/W Path: (the same of course)
HW Path: 64000/0xfa00/0x28

So I've created /infile with:
64000/0xfa00/0x28 disk 160
and then /sbin/ioinit -f /infile -r

Same thing on server2 with the coresponding HW address but in the end, I still have the same disk45 and disk96.

How can I get the same diskXY ?

Pierre Vassellerie
Occasional Contributor

Re: VM migration and disks instance numbers

This was due to the missing SPC2 bit on the FA of our EMC symmetrix. We had no support of SCSI functions, so the computed disk WWID was different for the 2 paths instead of being the same.