olrad.1m (2010 09)

o
olrad(1M) olrad(1M)
-d -t driver_name
Re-attaches the driver module to the attach chain. This command should only be run
if a previous olrad -d -u driver_name operation failed, so as to not leave the
driver in detached state. The driver name should correspond to the name shown in
the ioscan output.
This option is provided for driver developers only. It will not work as a standalone
command and can only be invoked from the "DLKM (Dynamically Loadable Kernel
Module)"
unload context. Refer to the Driver Development Guide (DDG) available at
http://www.hp.com/go/hpux_ddk
for more details on DLKM.
-d -u driver_name
Detach the driver from the attach chain and delete all the active interfaces claimed by
the specified driver module. If this command fails,
olrad -d -t driver_name
should be executed to re-attach the driver. The driver name should correspond to the
name shown in the
ioscan output. Critical Resource Analysis is run to ensure that
the removal of the driver module will not cause any disruption to the system opera-
tion.
This option is provided for driver developers only. It will not work as a standalone
command and can only be invoked from the "DLKM (Dynamically Loadable Kernel
Module)"
unload context. Refer to the Driver Development Guide (DDG) available at
http://www.hp.com/go/hpux_ddk
for more details on DLKM.
-e slot_id Lists the affected slot IDs for the specified slot.
-F Displays the output in machine readable format. It can be used with the following
options: -q, -c, -h, and -v.
-f The -f option, if specified, overrides the "data critical" errors returned by CRA. It is
important to note that olrad will not allow "system critical" errors to be overridden
and that olrad automatically overrides "warnings".
Irrespective of whether
-f is specified or not, Critical Resource Analysis (CRA) rou-
tines are run before an OLA/R/D operation, to ensure that the current OLA/R/D
operation does not interrupt the normal operation of the system; in other words, to
identify "critical" errors.
The "data critical" errors are typically not critical to the system, but they may be criti-
cal to the user. Hence, the user needs to decide whether or not to use the
-f
option
for overriding these types of errors.
-g hw_path Displays the slot ID for the specified device or interface hardware path.
-h slot_id Displays the hardware paths of the interface node(s) for the specified slot.
-I flag slot_id Controls the state of the Attention LED for the given slot. The valid values for this
flag option are: ATTN (LED blinking) and OFF. Based on the flag value, the slot
Attention LED is set to the appropriate state. The flags are not case-sensitive.
-K cell_hw_path Verifies that all the I/O interfaces under the specified Cell are inactive and have been
de-configured from the Cell. (This is a pre-requisite for performing a Cell-OnLine
Delete or Cell-OLD operation). Refer to parolrad (1M) for more details regarding the
Cell-OLD operation.
-n Display the number of OLA/R/D capable slots in the system.
-P flag slot_id Controls the state of the power indicator. Currently, the only valid value for this flag
option is: RAIL. The -P option can be used with RAIL to set the power indicator to
follow the specified slot’s power state; in other words, the power indicator is turned
solid ON if the slot power is ON, or the power indicator is turned OFF, if the slot
power is OFF. The flag is not case sensitive.
-p flag slot_id This option has been obsoleted in HP-UX 11i Version 3.
-q Displays the status of all OLA/R/D capable slots in the system. In the output, slots
with the same bus number share the same PCI Bus. Output fields are detailed below;
some descriptions are platform dependent. N/A means Not Applicable.
On systems with OLA/R/D capable PCI-Express slots, the output fields are slightly
varied. See the
PCI Express Based Slots section below for detailed
4 Hewlett-Packard Company 4 HP-UX 11i Version 3: September 2010