Interface Card OL* Support Guide

Messages from olrad Actions
The olrad command uses the NetTL subsystem to log errors and create an audit trail for all OL*
operations.
The olrad command uses the SYSADMIN subsystem formatter to format the log messages.
The following details are not logged:
• CRA report when performing OL*
• CRA report when using the -C option
• Output of view information options such as -v, -c, -g, -h, -q, and -n
If the NetTL subsystem is not enabled, olrad will continue with the operation, after writing an
error message to the console.
hotplugd Daemon Diagnostics
Messages logged during Attention Button events can go to either the system log file or the
hotplugd daemon log file.
Messages in the System Log File
The following messages are logged in the /var/adm/syslog/syslog.log system log file. If
an Attention Button event occurs after the daemon has been terminated following a successful
daemon start, the messages are logged in the system log file.
Table 6-2 System Log File Messages
MeaningMessage
A chunk of memory, used for storing the Attention Button event
information was not allocated.
The event is dropped after the power LED is set to PWR_RAIL mode. That
is, the power LED is set to ON if the power to the slot is ON, or the power
LED is set to OFF if the power to the slot is OFF.
Could not allocate memory for
PCI I/O Attention Button
event
The queue has not been initialized (daemon is not running) or the queue
is under flow control. The queue can go into flow control if it already has
maximum number of events. The maximum number is 128.
The event is dropped after setting the power LED to PWR_RAIL mode.
Wait until the Attention Button events are processed by the daemon.
Could not add the event to the
queue, dropping AB event
The Attention Button event was received on a slot ID that was not
registered (during system boot) with the kernel OLAR module.
The event is dropped after setting the power LED to PWR_RAIL mode (see
previous message). Contact the HP response center.
Dropping AB event, slotId not
found in the registered
slotIds
The call to get the slot information failed. olarErrMsg gives the reason
for the error. This results in an invalid PCI OL* event to the daemon.
Could not get the slot information for PCI
I/O Attention Button event: slotId,
olar_error_no = olarErrMsg
The system is clearing the Attention Button events in the queue due to the
abnormal termination of the daemon (for example, with the SIGKILL
signal (see kill(1)) and there are pending attention button events in the
queue.
hotplugd daemon (pid= pid) is
shutting down... dropping AB
event: slotId
Setting the power LED to PWR_RAIL mode failed. The system sets the
power LED to PWR_RAIL mode while clearing Attention Button events
from the queue, triggered by the abnormal termination of the hotplugd
daemon; for example, with the SIGKILL signal (see kill(1)).
Setting the power led to PWR_RAIL
mode failed: slotId,
olar_error_no = olarErrMsg
Messages in the hotplugd Daemon Log File
The following messages are logged in the hotplugd daemon log file defined by logfile.
Messages from olrad Actions 79