Interface Card OL* Support Guide

OL* Driver Scripts
During OL* procedures, olrad can initiate scripts that notify the system of the addition or
replacement of an interface card. Because pdweb invokes olrad, these scripts are also run by
pdweb. The script name must be the same as the driver name.
Scripts are delivered with card drivers and are located in the /usr/sbin/olrad.d/ directory.
These scripts do any preparatory work required before an OL* operation. If the driver requires
no preparatory action, then no script is executed.
• Scripts are run by olrad and usually do not require user intervention.
• There are one or more scripts per device if required; some devices may not require scripts.
See the following descriptions for details.
Preface Operations Actions
Preface Operations (Pref-OLR) scripts are run by olrad to determine and report the ramifications
of operation suspension (such as applications using resources) and whether or not an I/O device
can be made inactive for replacement.
Prepare Operations Scripts
Prepare Operations (Prep-OLRD) scripts are run by olrad just prior to suspending software
driver operations as the first step in a card replacement. These scripts contain the necessary
instructions to bring the target resource out of service before activity to and from the device is
stopped. For example, a Prep-OLR script checks for token ring presence, high-availability features,
switch over, and available backup mechanisms.
Post Operations Scripts
Post Operations (Post-OLARD) scripts are run by olrad after a card is added, replaced and
initialized, or deleted. These scripts contain the necessary instructions to bring the added or
replaced card into service, or complete the delete operation, before activity to and from the device
is started, restarted or stopped. For example, a Post-OLARD script can create special device files
for a new card and any attached devices.
84 OL* Actions, Events, and Scripts Reference