Configuring HP-UX For Peripherals

50 Chapter2
Managing PCI Cards with OLAR
Performing OLAR procedures from the command line
strongly recommends using SAM to perform OLAR operations.
OLAR Script Location and Identification
OLAR scripts reside in the following directory: /usr/sbin/olrad.d and are
identified by the driver name.
OLAR Scripts are identified by the driver name. Therefore, if the
ioscan(1M) command indicates the driver associated with a device is
named driver1, then the script associated with the device will be named
driver1.
Running OLAR Scripts
The procedures for running OLAR scripts are covered in the detailed
Add and Replace procedures as they are needed, but the basic idea is:
• Run rad -q to determine the slot id and hardware path of the target
card
• Run ioscan to determine the driver for the target card (for this
example: targetdriver)
• Run a long listing of the script directory: ls -l /usr/sbin/olrad.d
• If the targetdriver script exists, run it with the appropriate command
line parameters.
OLAR Script Actions
Pref-OLAR (Preface Operations) Actions
Run pref-OLAR scripts to determine and report the ramifications of
operation suspension or deletion (e.g., applications using resources) and
whether or not a I/O node can be made inactive for replacement or
deletion. (The task of making a I/O node inactive is performed in the
prep-OLAR scripts.)
Pref-OLAR scripts accept the following parameters:
• Execute action
• Hardware path of I/O node
For example:
# sh/usr/sbin/olrad.d/drivername pref_replace hw_path