Interface Card OL* Support Guide

-r slot_id
Prepare to replace a card on the system at the specified slot. A CRA is run to
ensure that the card replacement will not cause disruption in the functioning
of the system. The driver scripts run ( pref_replace and prep_replace)
for the affected slots (if any) and the current slot. The drivers associated with
the current slot and affected slots are suspended. The target slot is powered off
and the Attention LED is set to BLINK.
-R slot_id
Post Replace phase. The target slot power is turned ON. The suspended drivers
are resumed and the driver scripts (post_replace) for the current slot and
the affected slots (if any) are run. The attention LED at the corresponding slot
is set to OFF.
-d slot_id
Delete a card on the system at the specified slot. A CRA is run to ensure that
the card removal will not cause disruption to the system operation. The driver
script (prep_delete) associated with the current slot is run prior to deletion.
The target slot is powered off and the driver instances and associated data
structures are removed. The attention LED is set to BLINK at the corresponding
slot when the operation is in progress. When it completes, the post_delete driver
scripts are run.
-D slot_id
This performs the post delete operation. This should always be performed after
an olrad -d slot_id operation to complete the delete operation of a card
at the slot. The Attention LED at the corresponding slot is set to OFF.
Scripts
When performing an OL* operation on a slot, olrad runs the pref_replace, prep_replace
and prep_delete scripts in the pre-OL* phase and post_add, post_replace and
post_delete driver scripts in post-OL* phase.
There are no preface driver scripts for online card addition and online card deletion. There are
no prepare driver scripts for online card addition.
For a given OL* operation on a slot, pref_replace driver scripts are run for the affected slots
(if any) regardless of the type of operation being performed on the given slot.
An audit trail is logged on the NetTL log file whenever an OL* operation is initiated. This
information also writes to standard output.
For additional information on scripts, see “OL* Driver Scripts” (page 84).
Logging
The olrad command uses the NetTL subsystem to log errors and audit trails for all OL* operations
performed onslots. An audit trail is logged onto NetTL log file whenever an OL* operation is
initiated.
The olrad command uses the SYSADMIN subsystem formatter to format log messages.
The following information is not logged:
• CRA report when performing OL*
• CRA report when using the -C option of olrad
• Output of view information options such as -v, -c, -g, -h, -q, and -n
• If the NetTL subsystem is not enabled, olrad continues with the operation, after writing
an error message.
70 The olrad Command