Configuring HP-UX For Peripherals

Chapter 2 51
Managing PCI Cards with OLAR
Performing OLAR procedures from the command line
Pref-OLAR scripts return “0” (for “YES”) or “1” (for “NO”).
• If “0” is returned, you may continue with the remaining steps.
• IF “1” is returned, the script will also display a message on stderr.
Depending on the implications of the message, the user may abort, or
continue with the remaining steps.
Prep-OLAR (Prepare Operations) Scripts
Run prep-OLAR scripts just prior to suspending software driver
operations, as the first step in a PCI controller card replacement. These
scripts contain the necessary instructions to bring the target resource
out of service, before activity to and from the device is actually stopped.
For example, a prep-replace script may checks for token ring presence,
high-availability features, switch over, and/or available backup
mechanisms.
Prep-OLAR scripts accept the following parameters:
• Execute action
• Hardware path of I/O node
For example:
# sh /usr/sbin/olrad.d/drivername prep_replace hw_path
The script will return:
• “0” if it succeeded
• “1” if it failed but was able to recover or restore the system to its
original state before the script ran
• “2” if it failed and was not able to recover
Post OLAR (Post Operations) Scripts
Run post-OLAR scripts just after a PCI IO controller card is added or
replaced, and initialized. These scripts contain the necessary
instructions to bring the replaced card into service before activity to and
from the device is actually started or re-started. For example, a
post-OLAR script could be used to download microcode to an interface
cards in the case of a firmware patch. They may also be used to notify
other software of the resource’s availability.
• Each OLAR-capable device has one script that accepts the
parameters and return the completion code.