'new' LUN, no device file

[Chris Nelson 72]

Greetings-

We have a rp5470 with HPUX 11iv1 with an HP Tachyon XL2 FC adapter. We were connected from our server to a SAN switch, then to our SAN (NetApp). We'd like to connect directly from the server to the SAN, bypassing the SAN switch.

Prior to moving the fiber cable, I see the orig two LUNs. After moving the fiber cable I see four. The two orig LUNs have a NO_HW state. The two new LUNs do not have device files and they have a different h/w path.

I've been searching the forum and got the NO_HW LUNs removed using a combination of rmsf and a reboot. But insf -e (nor mksf) does not seem to be creating the new device files. Also, will the new device files need to have the same name as the old ones (/dev/dsk/c19t0dX) for LVM to recognize the PhysicalVolumes/VG's? I've thought about trying mknod, but I'm not sure of the minor number to use.

ioscans attached

Any suggestions?

thanks,
Chris

[Steven E. Protter]

Shalom,


insf -C disk

That and/or a reboot should reveal a properly assigned disk.

If you want the disk to be in a new volume group, you need the standard vgcreate procedure including the mknod you mention.

SEP

[Chris Nelson 72]

Thanks for the reply Steven. My only goal is to get rid of our old SAN switches by wiring the server directly to the SAN. I want to keep all the data (and LVM-PVs/VGs/LVs) on my two LUNs/disks intact.

So it looks like there will be new special files for the LUNs. This will break LVM I assume as it wont find the orig special files for the physical volumes.

I would like the newly created special files to be accessible to the existing LVM config. Is there a way to migrate the orig LVM to the new LUN file after the fact. Or would I need to do a vgexport? Change the wiring to bypass our SAN switch, then vgimport using the new LUN special file?