Operating System - HP-UX
1833017 Members
3095 Online
110048 Solutions
New Discussion

rebuild fibre attached device files

 
SOLVED
Go to solution
BradF
Frequent Advisor

rebuild fibre attached device files

I am configuring a fibre attached tape library.

I changed the lun ID of the attached tape drives and robotic arm.

I did an rmsf -H 'hardware path' and removed the device files. When I do an ioscan and insf -e it rebuilds the devices with the old configuration.

I did an rmsf -H 'hardware path' and rebooted the server. The hardware devices were not rebuild with the new configuration.

Is there anything special that needs to be done other than a rmsf and reboot to have the device files rebuild properly.

-Brad

6 REPLIES 6
Alzhy
Honored Contributor

Re: rebuild fibre attached device files

I usually do this to have my instance numbers to HW paths freshened and re-numbered:

rm /etc/ioconfig
rm /stand/ioconfig

Reboot.


Hakuna Matata.
Colin Topliss
Esteemed Contributor

Re: rebuild fibre attached device files

You can re-instance the hardware numbers - take a look at ioinit.

Basically you need to supply ioinit with a file that has the desired instance number contained in it:

To reassign an instance number to a device and class (specified in infile) and reboot the system:

/sbin/ioinit -f infile -r

where infile contains the following:

56.52 scsi 2

56.52 is the h/w_path, scsi is the class_name, and 2 is the instance_#.

- from the ioinit man page.
BradF
Frequent Advisor

Re: rebuild fibre attached device files

0/6/0/0.1.0.255.0.0.0 schgr
0/6/0/0.1.0.255.0.0.1 stape
0/6/0/0.1.0.255.0.0.2 stape
0/6/0/0.1.0.255.0.0.3 sctl

I have reconfigured the fibre router and moved the robotic arm so it should be:
0/6/0/0.1.0.255.0.0.0 stape
0/6/0/0.1.0.255.0.0.1 stape
0/6/0/0.1.0.255.0.0.2 schgr
0/6/0/0.1.0.255.0.0.3 sctl

When I do the rmsf and reboot the system, the schgr is still configured at 0/6/0/0.1.0.255.0.0.0
Steven E. Protter
Exalted Contributor

Re: rebuild fibre attached device files

I'd try rmsf the device drivers and then insf -e

Sometimes that works without the more difficult suggestons above.

Prior to doing the ioinit stuff above, take a make_tape_recovery backup. You can accidentlly make your system unbootable.

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
Alzhy
Honored Contributor
Solution

Re: rebuild fibre attached device files

Brad.. if you are bridnging your changer (robotics and the drives), perhaps you also need to reset/reboot the bridge..

I've seen this many times wherein changes on the SCSI LUNs of a bridged (SCSI-FC) device does not filter down to the host - even with the gyrations that we are proposing.

Otherwise, try the above.. and I 2nd motion What SEP's suggesting.. take a make_recovery backup first...
Hakuna Matata.
BradF
Frequent Advisor

Re: rebuild fibre attached device files

I rebooted the switch and the fibre router. I did an rmsf, ioscan and insf and it looks to be all set now.

There were some extra 'device files' after the rmsf that I removed manually.

-Brad.