HP-UX Virtual Partitions Release Notes (A.05.10)

vpar1# tdutil /dev/td0 reset
Reset Done
vpar1# tdutil /dev/td0
Vendor ID is = 0x00103c
Device ID is = 0x001028
TL Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x000006
Topology = PTTOPT_FABRIC
...
• Autoboot Fails from Fibre Channel Device via Brocade 3800 Switch
Related JAG or Patch ID Number
JAGae78109
Applicable On
vPars on PA-RISC
Description
Using a fibre channel mass storage device going through a Brocade 3800 switch with firmware
version 3.1.1, autobooting virtual partitions fails on rp5405, L3000/rp5470, or
N4000/rp7400 servers with PDC 43.22 installed.
Symptoms
Autoboot fails.
Workaround
Boot the virtual partitions manually from the vPars Monitor or HP-UX shell prompt. For example:
MON> vparload -p vpar2
or
vpar1# vparboot -p vpar2
For more information on using vPars with fibre channel devices, see the HP-UX Virtual Partitions
Ordering and Configuration Guide.
• On sx2000 Integrity Servers, Booting an OS Kernel while in the Wrong
Mode May Cause a Panic Instead of Displaying Error Messages
Related JAG or Patch ID Number
JAGag06132
Applicable On
◦ vPars A.05.xx on Integrity
◦ vPars A.04.xx on Integrity
Description
On Integrity servers, if you are in vPars mode and you boot the OS Kernel (boot vmunix)
instead of the vPars Monitor (boot vpmon), an error message is typically displayed on the
console. You may, however, receive a system panic message, instead of an error message.
Symptoms
The system panic displays messages similar to the following
EFI\HPUX\AUTO ==> boot vmunix
................
Launching /stand/vmunix
SIZE: Text:29561K + Data:7016K + BSS:7128K = Total:43705K
Console is on virtual console
Booting kernel...
16 vPars A.05.10 Release Notes