Fibre tape device connected to HP-UX cannot be seen by NetVault (4046977)

When installing NetVault on an HP-UX system, a post script runs to create NetVault specific device files for each SCSI or Fibre device. The script creates device files using mknod, and will get the minor number using ioscan output.

Issues with the library can result in it not being available to NetVault when attempting to add through Device Manager.

There are two common causes for devices not to be seen by NetVault Device Manager.

1. The device was attached to the server after NetVault was installed. If the device was not attached at install, the post script will not create device files for it.

2. HP-UX has 3 ways to address fibre devices. The NetVault post script will create device files for devices that are addressed using Peripheral Device Addressing (PDA). The script will only traverse down 'FCP Device' Interface trees as displayed in ioscan. This example will be seen by NetVault:

ext_bus 6 10/0/6/1/0.13.21.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 4 10/0/6/1/0.13.21.255.0.0 tgt CLAIMED DEVICE
tape 6 10/0/6/1/0.13.21.255.0.0.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2

If the device is on a non-PDA interface tree, the script will not create the device files. This example will not be seen in NetVault:

ext_bus 13 10/0/5/1/1.2.30.2.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
target 1 10/0/5/1/1.2.30.2.0.0 tgt CLAIMED DEVICE
autoch 0 10/0/5/1/1.2.30.2.0.0.0 schgr CLAIMED DEVICE STK L700

For scenario 1, the post exec script will need to be run again. Either, install NetVault again, or contact Technical Support for instructions.

For scenario 2, Some devices have switches to allow them to be addressed differently, for example PDA or Volume Set Addressed. Ensure that the device is set to PDA and run the script again by re-installing NetVault, or by contacting BakBone Customer support.
If this is not possible, then please contact BakBone Customer Support for further advice.