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

ESC[0mESC[37mESC[40m> System Memory = 16335 MB
loading section 0
......................................................
(complete) loading section 1 ............ (complete)
loading symbol table loading System Directory (boot.sys) to MFS .....
loading MFSFILES directory (/stand/bootfs) to MFS
..............
Workaround
You can either:
Update the server firmware to the latest version. See the HP-UX Virtual Partitions Ordering
and Configuration Guide for firmware version details.
If the virtual partition remains in the load state (you can use vparstatus to verify the
state), perform the following:
1. Issue a hard reset using vparreset to reset the virtual partition.
For example, if winona2 remains in the load state, to issue a hard reset:
winona1# vparreset -p winona2 -h
2. When the target partition is in the down state, attempt booting the partition using
vparboot. For example:
winona1# vparboot -p winona2
The virtual partition should recover and boot properly.
System Activity Events Reported Through IPMI by EMS
Related Defect ID and Patch Number
JAGaf62654
Applicable On
vPars A.05.xx
vPars A.04.xx on Integrity
vPars A.04.xx on PA-RISC
Description
In a vPars environment, system activity events are decoded and reported on all virtual partitions.
When examining any single virtual partition, this can be misleading, such that it may appear
the events occurred on the virtual partition that reported the problem.
Symptoms
A virtual partition reports an event, similar to the following:
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Wed May 4 15:29:44 2005
winona2 sent Event Monitor notification information:
/system/events/ipmi_fpl/ipmi_fpl is >= 3.
Its current value is CRITICAL(5).
Event data from monitor:
Event Time..........: Wed May 4 15:29:44 2005
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 267
System..............: winona2
Summary:
INIT initiated
Known Problems and Workarounds 11