Hitachi Compute Blade 500 Series User Manual page 374

Logical partitioning manager
Hide thumbs Also See for Compute Blade 500 Series:
Table of Contents

Advertisement

Message Content
Explanation
What to do
Message Content
Explanation
What to do
Message Content
Explanation
What to do
Message Content
Explanation
What to do
Message Content
Explanation
What to do
Message Content
Explanation
What to do
Message Content
Explanation
What to do
Message Content
Explanation
What to do
9-40
Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide
LP auto activation process is started.
The Auto Activate operation is started.
None.
LP booted with copied configuration files.
LPAR manager was started with the configuration information
subjected to cloning.
None.
LP booted with initial parameter file.
LPAR manager was started with the initial parameter file.
None.
LP changed Management Path.
The management NIC was changed.
None.
LP changed NIC to dedicated mode.
A NIC exists for which the mode was changed into the dedicated
mode because the number of shared NICs exceeded the
maximum by changing the scheduling mode of the NIC specified
as the management NIC to the shared mode.
None.
LP completed deletion of the initial parameter file.
The initial parameter file was completely deleted.
None.
LP detected failed SR-IOV feature was recovered.
LPAR manager detected that the isolated PCI device recovered.
PCI device recovered.
Start the guest OS, then the PCI device can be used again.
LP detected Link Up recovery at Shared NIC at expansion
Shared NIC link up recovery was detected.
None.
Messages
card.

Advertisement

Table of Contents
loading

Table of Contents