Event 1
Severity: Critical
Description: Driver failed to get system cacheline size
Possible Cause: Driver failed to get system cacheline size
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 2
Severity: Critical
Description: Driver failed to allocate an Interrupt Object.
Possible Cause: Driver failed to allocate an Interrupt Object.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 3
Severity: Critical
Description: Driver failed to set an Interrupt Line.
Possible Cause: Driver failed to set an Interrupt Line.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 4
Severity: Critical
Description: Driver failed to activate interrupt
Possible Cause: Driver failed to activate interrupt.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 5
Severity: Critical
Description: Driver received unsupported OLAR event. Possible olrad issues
Possible Cause: Driver
received unsupported OLAR event. Possible olrad issues.
Recommended
Action: Please Report the problem to the Hewlett Packard Customer
Representative.
Event 6
Severity: Critical
Description: Driver failed to allocate DMA handles.
Possible Cause: Driver failed to allocate DMA handles.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 7
Severity: Critical
Description: Driver failed to set DMA handle attributes
Possible Cause: Driver failed to set DMA handle attributes.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 8
Severity: Critical
Description: Driver failed to get PCI Config space handle
Possible Cause: Driver failed to get PCI Config space handle.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 9
Severity: Critical
Description: Driver failed to get all the registers
Possible Cause: Driver failed to get all the registers.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 10
Severity: Critical
Description: Driver failed to map the register base
Possible Cause: Driver failed to map the register base.
Recommended Action: Please
Report the problem to the Hewlett Packard Customer
Representative.
Event 11
Severity: Critical
Description: Driver failed to initialize because of a PCI Error. The interface is not being CLAIMED.
Possible Cause: PCI error occurred.
Recommended Action: No action
required. Information message only.
Event 12
Severity: Critical
Description: A SAS RAID volume has failed
Possible Cause: A SAS RAID volume has failed.
Recommended Action: Check all
connectors, cables and physical disks.
Event 13
Severity: Critical
Description: One or more physical disks in the RAID volume has failed.
Possible Cause: One or more
physical disks in the RAID volume has failed, but the RAID volume is still
operational.
Recommended Action: Check all connectors, cables and
physical disks. Reconnect any loose connectors and cables.
Replace failed
physical disks immediately.
Event 14
Severity: Information
Description: A RAID volume has come online
Possible Cause: A RAID volume
has come online.
Recommended Action: No action required. Only
informational.
Event 15
Severity: Information
Description: A RAID volume is re-synchronizing its physical disks
Possible Cause: A RAID volume
is re-synchronizing its physical disks.
Recommended Action: No action
required. Only informational.
Event 16
Severity: Critical
Description: One or more Inactive, Missing or Failed RAID volumes have been found. Please use sasmgr to get more information about these volumes and delete them if necessary.
Possible Cause: One or more
Inactive, Missing or Failed RAID volumes were discovered by the driver.
A
volume becomes Inactive if it is moved from one controller to another or if it
is not completely deleted.
A volume becomes Missing if all of it's physical
disks are offline or removed.
A volume becomes Failed if it does not have
sufficient physical disks to remain operational.
Recommended Action: Use sasmgr
to get more information about the RAID volumes. It is recommended that Inactive
volumes be deleted, since physical disks that are part of an Inactive volume are
inaccessible until the volume is deleted. For Missing or Failed RAID volumes,
please check all connectors, cables and physical disks. Reconnect any loose
connectors and cables. Replace failed physical disks
immediately.
Event 17
Severity: Critical
Description: Driver failed to disable the card.
Possible Cause: SASD Driver
failed to disable the card.
Recommended Action: Please Report the
problem to the Hewlett Packard Customer Representative.
Event 18
Severity: Critical
Description: Driver failed to enable the card.
Possible Cause: SASD Driver
failed to enable the card.
Recommended Action: Please Report the
problem to the Hewlett Packard Customer Representative.
Event
19
Severity: Critical
Description: Driver fault has occurred, a firmware dump will be taken and the HBA will be reset.
Possible Cause: SASD Driver
fault has occurred, a firmware dump will be taken.
Recommended Action:
Please Report the problem to the Hewlett Packard Customer
Representative.
Event 20
Severity: Critical
Description: Driver has encountered a PCI Error and is now unusable.
Possible Cause: PCI error occurred.
Recommended Action: No action
required. Information message only.
Event 21
Severity: Critical
Description: Driver Received Suspend Request.
Possible Cause: Driver received a Suspend Request.
Recommended Action: No Action
required. Information message only.
Event 22
Severity: Critical
Description: Driver has been successfully suspended.
Possible Cause: SASD driver was suspended.
Recommended Action: No Action required. Information message only.
Event 23
Severity: Critical
Description: Driver received Resume Request
Possible Cause: SASD driver received a Resume request.
Recommended Action: No action
required. Information message only.
Event 24
Severity: Critical
Description: Driver has successfully recovered and is now operational.
Possible Cause: SASD Driver was resumed.
Recommended Action: No Action
required. Information message only.
Event 25
Severity: Critical
Description: Driver failed to recover from a PCI Error.
Possible Cause: SASD Driver cannot recover because of a PCI Error.
Recommended Action: Use
olrad(1M) command to resume the card. Refer to the olrad(1M) manpage and Hot
Plug documentation for additional details.
Event 26
Severity: Critical
Description: Driver Received Suspend Request due to a PCI Error.
Possible Cause: SASD driver received Suspend Request due to a PCI error.
Recommended Action: No action
required. Information only.
Event 27
Severity: Major Warning
Description: The phy may be disconnected.
Possible Cause: The phy may be disconnected.
Recommended Action: Check
connectors, cables and devices attached to the phy.
Event 28
Severity: Major Warning
Description: Last phy in the port went down.
Possible Cause: Last phy in
the port went down.
Recommended Action: Check connectors, cables and
devices attached to the port.
Event 29
Severity: Critical
Description: Driver encountered the iport to be DOWN for an excessive period of time.
Possible Cause: SASD Driver
encountered the iport to be DOWN for an excessive period of
time.
Recommended Action: Check connectors, cables and devices
attached to the port.
Event 30
Severity: Major Warning
Description: The handle for one of the ports on the HBA has changed.
Possible Cause: The handle for
one of the ports on the HBA has changed.
Recommended Action: No action
required. Only informational.
Event 31
Severity: Information
Description: A port on the HBA has come online.
Possible Cause: A port on the
HBA has come online.
Recommended Action: No action required. Only
informational.
Event 32
Severity: Major Warning
Description: SASA target scan was requested while another one was in progress..
Possible Cause: A target scan
was requested while another one was in progress.
Recommended Action:
No action required. Only informational.
Event 33
Severity: Major Warning
Description: The device at the specified SAS address is not valid.
Possible Cause: The device at
the specified SAS address is not valid.
Recommended Action: If the SAS
address is for a valid device, verify all connections to the device. Also verify
that the device is operational.
Event 34
Severity: Critical
Description: The link between HBA port and target device is broken.
Possible Cause: The link between HBA port and target device is broken.
Recommended Action: Check
cables and target device status.
Event 35
Severity: Major Warning
Description: Driver noticed a change in the initiator address for a Target
Possible Cause:
Possible causes are:
1) HBA initiator port
reconfiguration. Ex. One wide port becoming multiple narrow ports.
2)
SAS target was moved from One HBA port to another.
Recommended Action: Verify
cable connections.
Event 36
Severity: Critical
Description: Driver received Discovery Error from Hardware/ Firmware..
Possible Cause: Driver
received Discovery Error from Hardware/ Firmware. SAS domain contains loops or
duplicate SAS addresses.
Recommended Action: Check for loops and
duplicate SAS addresses in the domain and break the loops. Resolve duplicate SAS
addresses.
Event 37
Severity: Major Warning
Description: Driver noticed initiator port went dead.
Possible Cause: A port on the
HBA has gone offline and all targets previously seen through that port are now
inaccessible.
Recommended Action: Check connectors, cables and devices
attached to the port.
Event 38
Severity: Information
Description: Target responded with command not supported.
Possible Cause: Target
responded with command not supported
Recommended Action: No action
required. Only informational.
Event 39
Severity: Critical
Description: SCSI command INQUIRY to the device failed.
Possible Cause: SCSI command
INQUIRY to the device failed, even after retries.
Recommended Action:
Please check the following:
1) Verify that all cables are securely
connected.
2) Verify that the device is functioning correctly.
Event 40
Severity: Critical
Description: Task Management function to SAS port failed
Possible Cause: Task Management function to SAS port failed.
Recommended Action: Please
check the following:
1) Verify that the device is powered on and is accepting
other commands.
2) If the device is accepting other commands, check device
internal logs.
Event 41
Severity: Critical
Description: The system has run out of ext_bus instances..
Possible Cause: The system has
run out of ext_bus instances.
Recommended Action: Please Report the
problem to the Hewlett Packard Customer Representative.
Event 98
· Invalid Severity Message
· Description: The SAS Mass Storage Adapter driver received invalid severity code #!.
· Cause/Action: Do the following and report the error to Hewlett-Packard:
1.From the system prompt, type "what vmunix" and store the output in a file.
2.Save the current MESA log file. The current MESA log is usually located at: /var/stm/logs/os/log1.raw.cur.
3.Save the current system log file. The current system log file is usually located at: /var/adm/syslog/syslog.log.
4.If the system recently panicked, save the system core files for analysis.
Event 99
· Invalid Error Message
· Description: The SAS Mass Storage Adapter driver received invalid error code #!.
· Cause/Action: Do the following and report the error to Hewlett-Packard:
From the system prompt, type "what vmunix" and store the output in a file.
Save the current MESA log file. The current MESA log is usually located at: /var/stm/logs/os/log1.raw.cur.
Save the current system log file. The current system log file is usually located at: /var/adm/syslog/syslog.log.
If the system recently panicked, save the system core files for analysis.
Event 100
· Severity: Information
· Description: The device has been added to the set of devices being monitored by this monitor.
· Cause/Action: The device was added to the system or has started responding to the system. The /var/stm/data/os_decode_xref file was modified to add information indicating this device is now supported by this monitor. If the device is in the DOWN state and this monitor does not control setting the state of the device to UP (check by running the "/etc/opt/resmon/lbin/set_fixed -L" command), use the "/etc/opt/resmon/lbin/set_fixed -n <resource_name>" command to set the state of the device to UP.
Event 101
· Severity: Critical
· Description: The device has been removed from the list of devices being monitored by this monitor.
· Cause/Action: The device was removed from the system, has stopped responding to the system or it has been replaced with a device that is not supported by this monitor. Run ioscan to determine the state and type of the device. Check the /var/stm/data/os_decode_xref for the information indicating which devices are supported by this monitor. Check other monitors to determine if they are now monitoring the device by running /etc/opt/resmon/lbin/monconfig and the using the "Check monitoring" command.
Event 103
· Severity: Information
· Description: This is a test message from the monitor to test the communication path from the monitor to the notification mechanism.
· Cause/Action: No action required.