Configuring HP-UX For Peripherals

40 Chapter2
Managing PCI Cards with OLAR
PCI Card OLAR Overview and Concepts
OLAR Scripts
At various stages throughout most OLAR procedures, SAM may initiate
certain actions that notify the system of the addition or replacement of
an interface card.
• These actions are contained in OLAR scripts, which are developed by
software driver engineers and based on the application or system
requirements for the target interface card.
• There are one or more scripts per device (if required; some devices
may not require scripts). See the following descriptions for details.
• Scripts are run by SAM and for the most part do not require user
intervention.
OLAR Script Actions
Pref-OLAR (Preface Operations) Actions
Pref-OLAR scripts are run by SAM to determine and report the
ramifications of operation suspension (e.g., applications using resources)
and whether or not a I/O node can be made inactive for replacement.
(The task of making a I/O node inactive is performed in the prep-OLAR
scripts.)
Prep-OLAR (Prepare Operations) Scripts
Prep-OLAR scripts are run by SAM 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.
NOTE A script is delivered with the card driver and is located in the directory
/usr/sbin/olrad.d/. It does any preparatory work required before the driver
suspends operation. If the driver requires no preparatory action, then no
script will be executed.
When a prep-OLAR script is run, the subsequent actions are “forced.”
That is, subsequent commands are expected to succeed. If the script