changing disk instance number

[Matthias Oswald]

Hi,

we have to do some re-configuration on a EMC SAN switch. This will likely change the way the disks are presented to the HP-UX host.
Therefore I'm trying to test the procedure for remaping instance numbers to disk devices.

What I did:

1. generating the infile using

/sbin/ioscan -kf | grep -e INTERFACE -e DEVICE | awk '{printf "%s %s %s\n",$3,$1,$2}' >infile

root@feanor:/stand> more infile
0/0/0/0 lan 0
0/0/1/0 ext_bus 0
0/0/1/0.7 target 0
0/0/1/0.7.0 ctl 0
0/0/1/1 ext_bus 1
0/0/1/1.0 target 1
0/0/1/1.0.0 disk 0
0/0/1/1.2 target 2
0/0/1/1.2.0 disk 1
0/0/1/1.7 target 3
0/0/1/1.7.0 ctl 1
0/0/2/0 ext_bus 2
0/0/2/0.0 target 4
0/0/2/0.0.0 disk 2
0/0/2/0.2 target 5
0/0/2/0.2.0 disk 3
0/0/2/0.7 target 6
0/0/2/0.7.0 ctl 2
0/0/2/1 ext_bus 3
0/0/2/1.2 target 7
0/0/2/1.2.0 disk 4
0/0/2/1.7 target 8
0/0/2/1.7.0 ctl 3
0/0/4/0 tty 0
0/0/5/0 tty 1
0/2/0/0 fc 0
0/3/0/0 lan 1
0/4/0/0 lan 2
0/5/0/0 lan 3
0/6/0/0 fc 1
0/7/0/0 lan 4
root@feanor:/stand>


2. test the infile with no changes

root@feanor:/stand> ioinit -f infile
ioinit: Input is identical to kernel, line ignored
Input line 1: 0/0/0/0 lan 0

ioinit: Input is identical to kernel, line ignored
Input line 2: 0/0/1/0 ext_bus 0

ioinit: Input is identical to kernel, line ignored
Input line 4: 0/0/1/0.7.0 ctl 0

ioinit: Input is identical to kernel, line ignored
Input line 5: 0/0/1/1 ext_bus 1

ioinit: Input is identical to kernel, line ignored
Input line 7: 0/0/1/1.0.0 disk 0

ioinit: Input is identical to kernel, line ignored
Input line 9: 0/0/1/1.2.0 disk 1

ioinit: Input is identical to kernel, line ignored
Input line 11: 0/0/1/1.7.0 ctl 1

ioinit: Input is identical to kernel, line ignored
Input line 12: 0/0/2/0 ext_bus 2

ioinit: Input is identical to kernel, line ignored
Input line 14: 0/0/2/0.0.0 disk 2

ioinit: Input is identical to kernel, line ignored
Input line 16: 0/0/2/0.2.0 disk 3

ioinit: Input is identical to kernel, line ignored
Input line 18: 0/0/2/0.7.0 ctl 2

ioinit: Input is identical to kernel, line ignored
Input line 19: 0/0/2/1 ext_bus 3

ioinit: Input is identical to kernel, line ignored
Input line 21: 0/0/2/1.2.0 disk 4

ioinit: Input is identical to kernel, line ignored
Input line 23: 0/0/2/1.7.0 ctl 3

ioinit: Input is identical to kernel, line ignored
Input line 24: 0/0/4/0 tty 0

ioinit: Input is identical to kernel, line ignored
Input line 25: 0/0/5/0 tty 1

ioinit: Input is identical to kernel, line ignored
Input line 26: 0/2/0/0 fc 0

ioinit: Input is identical to kernel, line ignored
Input line 27: 0/3/0/0 lan 1

ioinit: Input is identical to kernel, line ignored
Input line 28: 0/4/0/0 lan 2

ioinit: Input is identical to kernel, line ignored
Input line 29: 0/5/0/0 lan 3

ioinit: Input is identical to kernel, line ignored
Input line 30: 0/6/0/0 fc 1

ioinit: Input is identical to kernel, line ignored
Input line 31: 0/7/0/0 lan 4

ioinit: libIO error - Entry not found in ioconfig file.
Input line 3: 0/0/1/0.7 target 0
root@feanor:/stand>

Also the ioinit with -r option crashes on the target line.

I looked through various articles in the forum, but do see why it crashes on the target entries.

Any help is much appreciated.

[Steven E. Protter]

http://www1.itrc.hp.com/service/cki/search.do?category=c0&mode=id&searchString=KBRC00004879&search.x=28&search.y=8&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty

KBRC00004879

Is a general guide on resetting instance numbers for devices. It worked for me.

SEP

[Alzhy]

SEP,
AS I think I may be facing similar scenarios in the future, on an LVM managed system - if the cXtYcZ entries for existing LVM PV's (currently in a VG) change, will LVM break? Is'nt LVM (VG/PV) configuration resident on some kind of a disk header on the disk themselves?
.
With VxVM, I won't have this problem as it will just be a matter of importing the DiskGroup. No need for "map files" as volume names (LVOL in LVM terminology) are also kept/preserved..

[Mark Grant]

Nelson,

Yes. However, if you have two paths to the disks through two switches it is possible to migrate the whole lot over on line by being very careful and vgreducing the alternate paths out, making the changes on the switch that handles those paths, vgextend them back in again with the new device names. Then rinse and repeat for the other set. If you can get away with off lining everything you can, of course vgexport and vgimport again instead as long as you have exported with the -s and -p and -m options.

[Matthias Oswald]

Thanks for the quick reply.
I tried Procedure I and Procedure II,
both fail on ioinit with "Entry not found in ioconfig file" for target entries.
Still I wonder why the ioinit test without changing the infile fails ???
Procedure III does not apply I guess, since all the hardware is still visible with ioscan.

[Dietmar Konermann · Accepted solution]

Matthias,

if you only need to change disk-related instance numbering, then an infile with only the ext_bus lines should be completely sufficient. Leave away all other lines and all should work fine. No need to remap target or disk instances, since they don't have any effect on your disk device file anyway.

Best regards...
Dietmar.

[william Anderson_3]

I wish you guys would check these 20 year old links to see if they are still valid, thos one is long gone

[mbarnwal]

You may refer following documents

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c01312467

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c01310829

Thanks

Manish