HP-UX Virtual Partitions 6.0 Release Notes

Table 5 Known behaviors in vPars v6.0 (continued)
Description / actionProblem
is no longer needed, the additional core can be moved from the VSP pool to
the vPar pool.
An ioscan issued from within a vPar does not display any LUNs behind the
NPIV HBA unless the –N option is specified. The ioscan command without
NPIV LUNs not shown by default
invocation of ioscan
the –N option only displays devices that use the old style device file format.
The NPIV LUNs use the agile device file format and require the –N option to
ioscan in order to display LUNs in the output.
What to do
Use the –N option with the ioscan command to view devices behind NPIV
HBAs.
The following message appears in the console log after booting a vPar
AvioSyscall (0):1267e06000:e00000fffefff000.. This is a
debugging message that was inadvertently retained in the product.
Unnecessary console message in vPar
What to do
There is no workaround.
The syslog in vPars v6.0 will have a message similar to the following that
describes the IPMI device as failing to enable interrupts.
IPMI interrupt setup failure message in
syslog
Jun 14 17:49:14 cutst303 vmunix:
bt_InterfaceInit_interrupt: call to enable
interrupts error -3
Jun 14 17:49:14 cutst303 vmunix: IPMI interrupt set-up
failed. Staying in
polled mode.
What to do
There is no workaround. This is a harmless message and must be ignored as
the IPMI device in vPars v6.0 does not use interrupts.
vPars v6.0 requires the HP-UX bootloader patch to be installed on each vPar
to avoid the following loader failure.
HP-UX bootloader patch
AUTOBOOTING...Could not open file vmunix to check for a
directory Could not open vmunix
loading failed
What to do
There is no workaround.
If a vPar was created with a vSwitch based on a VLAN, and that VLAN has
been removed, it is not possible to modify or remove a vNIC connected to that
vSwitch.
Cannot remove a VLAN-based vNIC
if the VLAN has been removed
What to do
Recreate the VLAN with nwmgr and restart the vSwitch. This will allow you to
remove the vNIC using the vparmodify command.
Using pc -cycle fails to restart the vPar. This can occur if the memory required
by the vPar is less than that of available VSP memory (as reported by
vparstatus -A).
Power cycle using virtual management
processor fails to restart vPar
What to do
The preferred way to shutdown and restart a vPar is to use the shutdown -r
command from the OS in the vPar. Alternately, you can manually power off
and power on a vPar by using separate power commands (PC -off followed
by PC -on). You can also use the vparreset -d -f followed by vparboot.
Use vparstatus to verify the vPar reports DOWN before using the PC -on
or the vparboot command.
20 Known behaviors and workarounds