How to use the HP-UX Portable Image Tool for Integrity fluid cross-technology moves
3
High-level architecture
The HP-UX PI product consists of the following components:
• HP-UX PI shared library (/usr/lib/hpux32/libhpuxpi.so)–provides private API to enable/disable PI functionality,
add/remove/search MAC addresses in KRS, save and update PI configuration in KRS, and fix driver configuration file.
PI library interacts with DLPI to determine factory MAC address of all physical NIC and have support for message
catalogs and logging messages to NetTL.
• HP-UX PI tool (/opt/network/bin/hpuxpitool)–invokes the HP-UX PI shared library to perform actions on the
PI configuration database.
• Startup script (/sbin/rc2.d/S302hpuxpi -> /sbin/init.d/hpuxpi start)–invokes the HP-UX PI tool to update the
PI configuration upon every boot in KRS. This will fix-up drivers configuration files.
The start-up script is invoked before any LAN interfaces are configured to ensure that driver configuration files are
appropriately fixed up before LAN configuration. A dependency has been added to all LAN drivers on HP-UX PI in the
parallel framework database to ensure that this ordering is strictly enforced. When the startup script is invoked
during system boot, it invokes the hpuxpitool –u to update the HP-UX PI configuration. It logs any error to /etc/rc.log.
• Shutdown script (/sbin/rc1.d/K692hpuxpi -> /sbin/init.d/hpuxpi stop)–invokes the “hpuxpitool –s” to save (but not
update) the HP-UX PI configuration upon every shutdown in KRS.
To know more about hpuxpitool usages, see Appendix 1—/opt/network/bin/hpuxpitool
DLPI
ILAN
HDM1
HDMn
Persistent PI LAN
configuration
(KRS)
GIO
PI rc script
(/sbin/init.d/hpuxpi)
HP-UX PI shared library
(/usr/lib/hpux32/libhpuxpi.so)
PI CLI
(/opt/network/bin/hpuxpitool)
HP-UX IO Infrastructure (IOI)
GIO is responsible for associating instance numbers based on MAC addresses for “lan” class devices instead of using the
H/W path information in ioconfig. As part of the move when the source is shut down, the HP-UX PI tool saves the H/W
path, MAC address, and instance number association for all “lan” class devices in the KRS. When the system is booted up,
GIO reserves the instance numbers specified in the PI KRS. When devices are initially scanned, GIO assigns instance
numbers outside of the reserved range. When drivers determine their MAC address and call into GIO to reassign the
instance numbers, it returns the reserved instance number if the MAC address matches with any entry in the PI KRS.
Otherwise, the initial assignment during scan is preserved.
GIO also ensures that a different mechanism to assign instance numbers do not conflict with each other (e.g., ioinit and
HP-UX PI configuration).