HP-UX vPars and Integrity VM V6.3 Administrator Guide

11.4.6 CRA logs
The CRA infrastructure collates the detailed analysis logs from all the subsystem CRA modules and
returns the combined logs at the location /var/adm/cra.log on the VSP. When the olrad
command is invoked on a VSP, the CRA log on the VSP will have relevant entries under the following
scope:
Guest wise analysis for each vPar or VM guest that has an
NPIV resource impacted by the OLRAD operation.
HPVM NPIV
Guest wise analysis for each vPar or VM guest that has a
DIO resource impacted by the OLRAD operation.
HPVM Direct I/O
Guest wise analysis for each vPar or VM guest that has a
AVIO LAN resource impacted by the OLRAD operation.
HPVM AVIO Networking
Guest wise analysis for each vPar or VM guest that is
booted off a legacy AVIO (non-NPIV) backing store, that
is impacted by the OLRAD operation.
HPVM legacy AVIO Storage
In cases where a successful CRA can be conducted on the active guests, the guest wise analysis
displays the guest instance number along with the severity associated with each guest.
In cases where any of the HPVM components failed to perform a CRA, the guest wise analysis
displays the guest instance number along with the reason for failure in analysis, for each guest.
The CRA log on the VSP only provides the overall result of analysis per guest. The VSP administrator
has to work with the guest administrators for each of the impacted guests to get the detailed CRA
per guest. The detailed CRA for each guest is available in the guest, at the location /var/adm/
cra.log.
11.4.7 PCI OLR failures
This section describes in detail about the possible errors that can be encountered during a CRA
or OLRAD operation on an SD2 configured as a VSP and the workaround to proceed with the
CRA or OLRAD operation.
A change in guest configuration is in progress, retry the operation
A PCI OLR operation or a CRA on the VSP is not supported if any of the active vPars having IO
devices backed by the card being removed in the middle of a CPU or memory addition or removal.
The operation must be retried after the modification to CPU count or vPar base or float memory is
completed.
The guest is at EFI, retry after the guest boot completes
A PCI OLR operation or a CRA on the VSP is not supported if any of the active vPars or VM guests
with impacted IO devices is at EFI. The operation must be retried after the vPars and VM guests
have completed the boot process.
The guest is being shut down or is being rebooted, retry the operation
A PCI OLR operation or a CRA on the VSP is not supported if any of the active vPars or VM guests
with impacted IO devices are in the middle of being shut down or rebooted. The operation must
be retried after the vPars and VM guests have either completed the shutdown or the boot process.
The guest is running a pre-6.3 VirtualBase bundle upgrade to the latest VirtualBase bundle
and retry the operation
A PCI OLR operation or a CRA on the VSP is not supported if any of the active vPars or VM guests
with impacted IO has a pre V6.3 VirtualBase bundle installed. The vPars or VMs have to be brought
down to proceed with the PCI OLR operation or the CRA.
11.4 Performing PCI OLR on a VSP 167