HP-UX Virtual Partitions 6.0 Administrator Guide

Example 30 Identifying NPIV HBAs and devices in a vPar
# ioscan -kfNd gvsd
Class I H/W Path Driver S/W State H/W Type Description
ext_bus 0 0/0/0/0 gvsd CLAIMED INTERFACE VPAR AVIO Stor Adapter
ext_bus 1 0/0/4/0 gvsd CLAIMED INTERFACE VPAR NPIV Stor Adapter
ext_bus 4 0/1/3/0 gvsd CLAIMED INTERFACE VPAR NPIV Stor Adapter
Note that the ioscan output listing the NPIV devices in the vPar is exactly the same as a similar
listing of SAN LUNs in a native host.
Example 31 Identifying NPIV HBAs and devices in a vPar by specifying hardware path
# ioscan -kfNH 0/0/4/0
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
ext_bus 1 0/0/4/0 gvsd CLAIMED INTERFACE VPAR NPIV Stor Adapter
tgtpath 3 0/0/4/0.0x207000c0ffda0287 estp CLAIMED TGT_PATH Virtual Storage
HBA target served by gvsd driver, target port id 0x105ef
lunpath 5 0/0/4/0.0x207000c0ffda0287.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl1
lunpath 8 0/0/4/0.0x207000c0ffda0287.0x4001000000000000 eslpt CLAIMED LUN_PATH LUN path for disk7
lunpath 9 0/0/4/0.0x207000c0ffda0287.0x401d000000000000 eslpt CLAIMED LUN_PATH LUN path for disk8
tgtpath 4 0/0/4/0.0x247000c0ffda0287 estp CLAIMED TGT_PATH Virtual Storage
HBA target served by gvsd driver, target port id 0x104ef
lunpath 6 0/0/4/0.0x247000c0ffda0287.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl2
lunpath 11 0/0/4/0.0x247000c0ffda0287.0x4001000000000000 eslpt CLAIMED LUN_PATH LUN path for disk7
lunpath 12 0/0/4/0.0x247000c0ffda0287.0x401d000000000000 eslpt CLAIMED LUN_PATH LUN path for disk8
Installing Ignite-UX software on NPIV disks
After the LUNs are presented to the NPIV HBA, you can install the vPar image on an NPIV device.
Suspending a vPar configuration
You can suspend a vPar to remove or deallocate resources from it, while maintaining its
configuration settings. This is a way of managing shadow configurations, and allows the shadow
configuration on a per vPar basis. The -x active_config=false option must be used with
either the vparcreate or the vparmodify command.
You can suspend a vPar configuration only if the vPar is in the inactive state, that is, the run-state
must be DOWN.
To deactivate or suspend a single vPar configuration, the vparmodify command must be used
with the -x active_config=false option. Once this is done, the vPar instance no longer
consumes or reserves the resources allocated to it, and those resources may be distributed to other
partitions or the VSP, or those resources may be used to a create different vPar instance.
To reactivate the vPar configuration use vparmodify with the -x active_config=true.
However, note that a vPar configuration cannot be reactivated unless the resources it requires are
available and not reserved by other vPar instances. A vPar can still be managed while its
configuration is suspended; however, it cannot be booted.
Example 32 Suspending a vPar named Oslo
vparmodify -p Oslo -x active_config=false
Recovering a nonresponsive vPar
In the rare event that the OS of a vPar becomes nonresponsive, there is no prompt from a network
connection nor through the virtual console (vparconsole). In such a situation, you may need to
manually reset the partition. To recover a vPar that is nonresponsive, you can use the vparreset
command.
To recover a nonresponsive vPar, use the vparreset -g command. This results in a graceful
shutdown of the OS. The vPar can then be restarted. However, if the OS is nonresponsive, this
46 Creating and managing virtual partitions