Interface Card Critical Resource Analysis(CRA) Whitepaper for HP-UX 11i v3

Scenario 12
System Configuration:
HP-UX OS running in Service Guard (SG) cluster environment with common
lock disk between the cluster nodes, but the SG cluster is not currently running.
Operation Performed:
# olrad –C | -r | -d <slot id>
Criticality reported by CRA:
CRA_FAILURE
Explanation and user action required:
Though the SG cluster is not currently running, as long as the quorum disk is configured, the above
olrad operations on the card under which the quorum disk is present will fail with CRA Internal error.
In this scenario, if the above olrad operations must be performed for system administration purposes,
the recommended procedure is to remove the specified quorum disk from the SG cluster configuration
or remove the SG cluster configuration itself (if the user is prepared to take this recommendation and
after ensuring that the cluster configuration has been backed-up) and then re-try the above operation.
I/O in Progress Scenarios
Scenario 13
System Configuration:
I/O is in progress to a logical volume (could be either LVM or VxVM volume)
configured on a physical disk (PV) with a single lunpath through an HBA.
Note that this PV is neither a boot disk nor a disk that has any root file system mounted. The logical
volume in use is one which is other than the logical volume for the current boot disk.
Operation Performed:
# olrad –C | -r | -d <slot id>
Or
# scsimgr disable –H <lunpath>
Criticality reported by CRA:
CRA_DATA_CRITICAL
Explanation and user action required:
The olrad(1M) command with –C option reports the resource usage and its criticality.
The above operations with scsimgr and the olrad(1M) with –r or –d options will fail with
CRA_DATA_CRITICAL error.
If any of these operations must be performed for system administration purposes, then the user must
ensure that the disk under I/O is reachable through an alternative path (in case of scsimgr operation)
or alternative healthy card (in case of olrad operation) before performing the above operations.
However, the user may override this error using the olrad –f option or the scsimgr disable –F option.
Overriding the error and proceeding with the operation will make the disk unavailable and this may
result in loss of data or data inconsistency problems.
Scenario 14
System Configuration:
HP-UX OS is running and the user applications are performing disk I/O using
the path dependent device special file (DSF).
Operation Performed: # rmsf -L
Criticality reported by CRA:
CRA_DATA_CRITICAL
12