Changing Disk Instance

[Roger Baptiste]

How does one Modify the disk
instance numbers off a system:
For eg: I would like to modify
the entry:
ext_bus 22 0/4/0/0.8.0.21.1 to -->>
ext_bus 27 0/4/0/0.8.0.21.1.

I need to do this for making two
nodes of a cluster to have the
same Diskpaths/id's to aid
in maintaining VG's.
Some of the Ext_bus instances pointing to the disks are not
similar on both the systems. So,
i am in the process of correcting it.

I tried the ioinit method as per
HP DOC Id: A5078754,
but it didnt seem to work

thanks
raj

[Juan González · Accepted solution]

Hi Raj,
I haven't read the DOC you reference, but when we had the same idea that you we made the follow:
Using your example
ext_bus 22 0/4/0/0.8.0.21.1 to -->>
ext_bus 27 0/4/0/0.8.0.21.1

1. We created a file (io.tmp) that contains

0/4/0/0.8.0.21.1 ext_bus 27

but if you have another ext_bus using this instance number (27) , for example:

ext_bus 27 0/4/0/0.8.0.255.0

you must change it too. In this case we can edit io.tmp to be

0/4/0/0.8.0.21.1 ext_bus 27
0/4/0/0.8.0.255.0 ext_bus 30

where 30 is a free ext_bus instance number.

2. Then we executed
#ioinit -f io.tmp
then we rebooted the server

3.After the server reboot we execute
#insf -e

other options of the insf as the ones that specifies the class or the instance number didn?t work for us.

Good luck
Juan Gonzalez

[John Waller]

The simple answer is you can't via software. The only way would to change the position of your SCSI controller within the system.
Having different disk paths shouldn't cause any problems with volume groups in a cluster enviroment. All you would do is export the vg from on system with the -p option (preview) and reimport on the new but specifyng the alternate disk paths.
e.g on system A disk are c1t1d0 c1t2d0 c1t3d0
on system B disks are c2t1d0 c2t2d0 c2t3d0.
on system A ,
vgexport -p -v -m /tmp/vg01.map /dev/vg01

rcp /tmp/vg01.map to system B

on system B

vgimport -m /tmp/vg01.map /v /dev/vg01 /dev/dsk/c2t1d0 /dev/dsk/c2t2d0 /dev/dsk/c2t3d0.

As you are still using the same physical disks everything will apear the same. All you need to be aware of is the different path for the lock disk within your Serviceguard config files.

[KOUNDI_2]

To change the disk instance :
$ vi /tmp/infile

0/4/0/0.8.0.21.1 ext_bus 27
Save the files
$ mv /etc/ioconfig /etc/ioconfig.sav
$ mv /stand/ioconfig /stand/ioconfig.sav
$ mv /tmp/infile /stand/infile

Reboot on single-user mode :
(in ioinitrc)#/sbin/ioinit -c
(in ioinitrc)#/sbin/ioinit -f /stand/infile -r

To create the special file
$ insf -evH 0/4/0/0.8.0.21.1

To verifie
$ ioscan -funC ext_bus

Regards

/HK

[Roger Baptiste]

Thanks for the response.
I have a question

Juan mentioned:
<ext_bus 27 0/4/0/0.8.0.255.0
you must change it too.
>>

That's what seems to be the problem! It doesn't accept
a change to instance 22 and
cribs that there is already
a device/class pointing to that
number. But, ioscan does
not show anything corresponding
to that Instance number!!
Any idea where this info can
be got from?

I came across an option
in ioscan , the -M option
which allows one to reclaim
a Hardware instance number
by assigning it false info
and then changing it
through ioinit process.

Anybody tried it??

thanks
raj

[Juan González]

Hi Raj,
can you post the output of the commands
#ionit -f "the_name_of_the_file"
#ioscan -fnCext_bus

and the file "the_name_of_the_file"

Best regards
Juan Gonzalez