This section provides an overview of the multipathing support that is available on an HP-UX system that was configured for an iSCSI initiator.
After the iSCSI initiator is configured, the HP-UX native multipathing is statically linked with the kernel, which means no setup is required to use the multipathing support.
You need to find out the pseudo device or persistent device-specific file that was created by the multipathing kernel module. If you see I/Os going through the persistent device-specific file, then HP-UX native multipathing is operating. If you do not see the I/Os going through the persistent device-specific file, then native multipathing is not operating.
For more information about multipathing, see the HP-UX Web site:
http://docs.hp.com/en/native-multi-pathing/native_multipathing_wp_AR0709.pdf
If you have one LUN that is exported to the HP-UX system and the initiator logs in to both targets, the LUN is accessible from the two different paths. In this case, HP-UX 11i v3 creates only one persistent device-specific file per LUN.
The ioscan command queries the mapping combinations between LUN and lunpaths using the persistent device-specific file