HP-UX Virtual Partitions Release Notes A.05.08

• 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
Workaround
Note that in a vPars environment, when system events are reported via EMS either from system
firmware or an OS instance, the system events are decoded and reported on all virtual
partitions. The OS instance that is shown as sending the event is not necessarily indicative of
the actual virtual partition that encountered the problem. The Reporting Entity ID is the only
clue to which virtual partition reported the problem. The output will be similar to the following:
Reporting entity ID: 6 ( Cab 0 Cell 0 CPU 6 ) (possibly from one vPar)
• Virtual Partition Does Not Boot After Root Mirror is Created
Related Defect ID and Patch Number
JAGaf54464
Applicable On
◦ vPars A.05.xx on Integrity
◦ vPars A.04.xx on Integrity
Description
A virtual partition does not boot from its mirror root disk because there is no longer a valid
EFI to hardware path mapping in the vPars database.
Symptoms
After creating a mirror root disk, the virtual partition fails to boot from this disk. You may see
messages similar to the following:
Load of 1/0/8/1/0.22.31.0.0.0.1 failed: Not Found
12 vPars A.05.08 Release Notes