Event: 1
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to get PCI configuration space handle.
- CAUSE: Driver internal error.
- ACTION: Please report the problem to Hewlett Packard.
Event: 2
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to get system cache line size.
- CAUSE: Driver internal error.
- ACTION: Please report the problem to Hewlett Packard.
Event: 3
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to allocate interrupt object.
- CAUSE: Driver internal error.
- ACTION: Please report the problem to Hewlett Packard.
Event: 4
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to set interrupt line.
- CAUSE: Driver internal error.
- ACTION: Please report the problem to Hewlett Packard.
Event: 5
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to activate interrupt.
- CAUSE: Driver internal error.
- ACTION: Please report the problem to Hewlett Packard.
Event: 6
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to allocate DMA handle.
- CAUSE: Driver internal error.
- ACTION: Please report the problem to Hewlett Packard.
Event: 20
- SEVERITY: CRITICAL
- DESCRIPTION: Driver received a suspend request.
- CAUSE: Driver received suspend request.
- ACTION: No action required, information message only.
Event: 21
- SEVERITY: CRITICAL
- DESCRIPTION: Driver is successfully suspended.
- CAUSE: Driver successfully completed suspend request.
- ACTION: No action required, information message only.
Event: 22
- SEVERITY: CRITICAL
- DESCRIPTION: Driver received a resume request.
- CAUSE: Driver received resume request.
- ACTION: No action required, information message only.
Event: 23
- SEVERITY: CRITICAL
- DESCRIPTION: Driver is successfully resumed.
- CAUSE: Driver successfully completed resume request.
- ACTION: No action required, information message only.
Event: 24
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to resume.
- CAUSE: Driver could not recover from PCI error during resume operation.
- ACTION: Please report the problem to Hewlett Packard.
Event: 25
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to resume.
- CAUSE: Driver does not support this Subsystem Vendor ID.
- ACTION: No action required. Informative message.
Event: 26
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to resume
- CAUSE: Driver does not support this Subsystem ID.
- ACTION: No action required. Informative message.
Event: 27
- SEVERITY: CRITICAL
- DESCRIPTION: Driver detected a PCI error.
- CAUSE: Driver failed to resume because of a Fatal PCI Error.
- ACTION: Contact the Hewlett Packard Customer Representative.
Event: 28
- SEVERITY: CRITICAL
- DESCRIPTION: Driver received delete request.
- CAUSE: Driver received a delete request.
- ACTION: No Action required. Informational message only.
Event: 29
- SEVERITY: CRITICAL
- DESCRIPTION: Driver received an unsupported OLAR request.
- CAUSE: Driver received an unsupported OLAR request.
- ACTION: No Action required. Informational message only.
Event: 35
- SEVERITY: INFORMATION
- DESCRIPTION: HBA is ONLINE.
- CAUSE: This message indicates that link initialization has completed successfully and that any needed fabric logins and registrations have also been completed.
- ACTION: No action required. Informational message only.
Event: 36
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has detected an unexpected condtition on the HBA.
- CAUSE: Driver has detected an unexpected condition on the HBA.
- ACTION: No action required. Driver will attempt to auto-recover from this condition.
Event: 37
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has successfully recovered.
- CAUSE: Driver has successfully recovered from the error condition.
- ACTION: No action required. Informational message only.
Event: 38
- SEVERITY: CRITICAL
- DESCRIPTION: Driver was unable to recover from an error.
- CAUSE: Driver was unable to recover from an error.
- ACTION: Driver has been disabled, manual recovery may be attempted via fcmsutil(1M) reset command.
Event: 45
- SEVERITY: MAJORWARNING
- DESCRIPTION: Driver detected a topology change.
- CAUSE: The Fibre Channel Driver HBA's topology has changed. This indicates a configuration change in the SAN.
- ACTION: If a SAN configuration change has been made, then this message is normal. Otherwise, please check the SAN configuration.
Event: 46
- SEVERITY: CRITICAL
- DESCRIPTION: came up in an unsupported topology.
- CAUSE: The HBA has come up in an unsupported topology. No devices will be seen.
- ACTION: Verify the HBA connections.
Event: 47
- SEVERITY: INFORMATION
- DESCRIPTION: Driver received an RSCN for nport_id.
- CAUSE: The Fibre Channel Driver has received a Registered State Change Notification (RSCN). This is a notification from the Fabric that there has been a change in the Fabric.
- ACTION: The Fibre Channel Driver will now query the Fabric to discover what the change is. This is an informational message and no action is required.
Event: 48
- SEVERITY: INFORMATION
- DESCRIPTION: failed to register FC4-Type with the Fabric.
- CAUSE: Driver failed to register FC4-Type with the Fabric.
- ACTION: This may indicate that the HBA port is not part of a zone. Please check zone configuration on your switch.
Event: 49
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to login with the fabric.
- CAUSE: Driver failed to login with the fabric. Possible reasons maybe: - a misbehaving device or switch - a device or switch sending PLOGI or FLOGI response that is not standard compliant
- ACTION: Report the problem to Hewlett Packard and to device or switch vendor. Provide the contents of the system log file. The system log file is at: /var/adm/syslog/sy slog.log
Event: 55
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has lost a device.
- CAUSE: Driver has detected that a previously discovered device (Nport_id) is no longer in the GPN_FT response, or it's corresponding World-Wide Name has changed. Driver won't be able to communicate with the device any more
- ACTION: please check that device. If the problem persists, please report the problem to Hewlett Packard.
Event: 56
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has detected that device is back in the Name Server database.
- CAUSE: Driver has detected that a previously lost device (Nport_id) is back in the GPN_FT response, or its corresponding World-Wide Name remains the same.
- ACTION: Driver will be able to communicate with the device. No action is needed.
Event: 57
- SEVERITY: INFORMATION
- DESCRIPTION: Driver received a login failure for device.
- CAUSE: Driver received a PLOGI failure for a device.
- ACTION: No action required, information message only.
Event: 58
- SEVERITY: INFORMATION
- DESCRIPTION: Driver received a process login failure for device.
- CAUSE: Driver received process login failure for a device.
- ACTION: No action required, information message only.
Event: 59
- SEVERITY: CRITICAL
- DESCRIPTION: Driver detected an authentication failure for device id.
- CAUSE: Fibre Channel disk addressing is based on Nport_id. To ensure integrity, we normally require the World-Wide Name for Nport_id to stay the same. Driver has detected a new World-Wide Name for the Nport_id previously occupied by a device with another World-Wide Name.
- ACTION: However, if the device has been replaced intentionally, please use the scsimgr(1M) command's replace_wwid or replace_leg_dsf options to allow the new device to be used.
Event: 60
- SEVERITY: CRITICAL
- DESCRIPTION: Driver detected that private loop device didn't acquire its hard address.
- CAUSE: In private loop topology, we require device to set hard address, and to acquire its Hard address during loop initialization. Driver has detected that a private loop device didn't acquire its hard address.It might be due to multiple devices in the loop with the same hard address setting.
- ACTION: Look for all the devices which has the reported hard address. Change their hard address settings so that they have a unique hard address. NOTE: 1. Please change hard address setting for the newly added devices, so that the old device can keep its hard address. 2. After you change the hard address settings on the devices, it may be necessary to reset or power-cycle all the devices which used to have the same hard address setting. EXAMPLE: You see this diagnostic message and find three devices with address setting 0x05. You can change one device to address 0x06 and another to 0x07. You now may need to reset or power-cycle ALL THREE devices.
Event: 61
- SEVERITY: INFORMATION
- DESCRIPTION: Driver logged out device.
- CAUSE: A device has logged out the Fibre Channel Driver.
- ACTION: No action required, information message only.
Event: 62
- SEVERITY: INFORMATION
- DESCRIPTION: Driver implicitly logged out device.
- CAUSE: Driver detected an implicitly logged out device.
- ACTION: No action required, information message only.
Event: 63
- SEVERITY: INFORMATION
- DESCRIPTION: Driver received a port LOGO for device.
- CAUSE: A device has logged out with the Driver.
- ACTION: No action required, information message only.
Event: 64
- SEVERITY: CRITICAL
- DESCRIPTION: Driver detected that device is offline.
- CAUSE: Driver detected that a device has gone offline.
- ACTION: No action required, information message only.
Event: 65
- SEVERITY: INFORMATION
- DESCRIPTION: Driver detected nport id change for device.
- CAUSE: The Fibre Channel Driver HBA's N_Port ID has changed. This indicates a configuration change in the SAN.
- ACTION: If such a configuration change has been made, then this message is normal. Otherwise, please check the SAN configuration.
Event: 66
- SEVERITY: INFORMATION
- DESCRIPTION: Driver detected that device is online.
- CAUSE: Driver detected that a device is online.
- ACTION: Driver will be able to communicate with the device. No action is needed.
Event: 70
- SEVERITY: INFORMATION
- DESCRIPTION: Driver detected probe timeout.
- CAUSE: Driver detected that probe timeout.
- ACTION: No action required, information message only.
Event: 71
- SEVERITY: INFORMATION
- DESCRIPTION: Driver detected that the system has reached its maximum device addressable limit, ioscan output will not show all the devices.
- CAUSE: The total LUNs discovered by the host bus adapter through all the fibre chann el devices is beyond the system addressable limit. This can happen if there is a large number of LUNs configured (either in a single fibre channel device or in multiple devices).
- ACTION: Configure fewer number of (larger) LUNs.
Event: 72
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has received a LUN list size from REPORT_LUNS command greater than max IO for device.
- CAUSE: The response data for the SCSI command REPORT_LUNS is larger than the maximum I/O size supported by the host bus adapter. This can happen if the disk array h as a large number of LUNs configured.
- ACTION: Please report the problem to HP.
Event: 73
- SEVERITY: CRITICAL
- DESCRIPTION: SCSI inquiry failed on FCP device.
- CAUSE: SCSI command INQUIRY to the device failed, even after retries.
- ACTION: Please check the following: 1. Verify that the fiber optic cable is functional and securely attached tothe Fibre Channel Mass Storage Adapter. 2. Verify that the device which is connected to the adapter port is functioning correctly.
Event: 74
- SEVERITY: CRITICAL
- DESCRIPTION: Driver does not allow domain 8 for backward compatibility reasons.
- CAUSE: For backward compatibility, domain 8 (private loop) is not allowed
- ACTION: Configure the switch to assign a domain value other than 8. Domains > 8 will not be recognized till this problem is fixed.
Event: 75
- SEVERITY: MAJORWARNING
- DESCRIPTION: Driver has not found any valid LUNs on the array device.
- CAUSE: This may happen if the LUNs in the array device are not configured properly.
- ACTION: Please re-check the LUN configuration in the disk array.
Event: 76
- SEVERITY: MAJORWARNING
- DESCRIPTION: Driver has found invalid LUN format on array device.
- CAUSE: Some or all of the LUNs configured in the disk array device are having an invalid or unsupported format.
- ACTION: Please report the problem to HP.
Event: 77
- SEVERITY: MAJORWARNING
- DESCRIPTION: HBA is not online. Scan of the port will not show any devices.
- CAUSE: The Fibre channel host port's link located by the device path is not online.
- ACTION: Ignore this message if there is no cable connected. Otherwise please check the following:
- Verify that there are no more than 126 FC ports on the loop.
- Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
- Verify that the device which is connected to the adapter port is functioning correctly.
- Verify that the adapter port is functioning correctly by performing internal and external loopback tests. Please attach a loopback hood to the adapter port when executing a loopback test.
#Internal loopback test /opt/fcms/bin/fcmsutil <device_file> int {crpat | cjtpat}
[count] #External loopback test /opt/fcms/bin/fcmsutil <device_file> ext {crpat | cjtpat} [count]Event: 78
- SEVERITY: INFORMATION
- DESCRIPTION: Fabric Name Server rejected GPN_FT query.
- CAUSE: The HBA port may not be part of a zone.
- ACTION: Please check zone configuration on your switch.
Event: 85
- SEVERITY: CRITICAL
- DESCRIPTION: The bus instance number has exceeded the maximum allowed instance number.
- CAUSE: Fibre Channel driver received bus instance number greater than 255, the maximum allowed instance number.
- ACTION: Cleanup of the ioconfig file might help. Please report the problem to HP.
Event: 86
- SEVERITY: CRITICAL
- DESCRIPTION: Driver received a request to delete vbus.
- CAUSE: Driver received a request to delete the virtual bus.
- ACTION: No action required. Informative message only.
Event: 90
- SEVERITY: CRITICAL
- DESCRIPTION: HBA has been disabled on user request.
- CAUSE: The HBA was disabled due to a user request.
- ACTION: Issue the following command to re-enable the adapter: /opt/fcms/bin/fcmsutil <device_file> enable
Event: 91
- SEVERITY: CRITICAL
- DESCRIPTION: HBA is being enabled on user request.
- CAUSE: The HBA was enabled due to a user request.
- ACTION: No action required. Informative message.
Event: 92
- SEVERITY: CRITICAL
- DESCRIPTION: Driver received a firmware update request.
- CAUSE: Driver has received a firmware update request.
- ACTION: No action required. Informative message.
Event: 93
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has successfully updated the firmware.
- CAUSE: Driver has successfully updated the firmware.
- ACTION: No action required. Informative message.
Event: 94
- SEVERITY: CRITICAL
- DESCRIPTION: Firmware update request has failed.
- CAUSE: An attempt to load a new firmware image into the Flash ROM of the adapter port has failed. The firmware stored in the Flash ROM may be unusable. This firmware is used only when booting through the adapter port and is not used when system has already booted. This failure may have also corrupted the EFI Driver and VPD Data, which are also stored in the adapter port Flash ROM.
- ACTION: Do not attempt to boot the system through the adapter port. Contact the HP customer representative as soon as possible.Alternatively, a work-around would be to restore the Flash ROM contents by reflashing the adapter using Offline Diagnostics Environment (ODE).
Event: 95
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has received a user initiated firmware dump request.
- CAUSE: Driver received a user initiated firmware dump request.
- ACTION: No action required, information message only.
Event: 96
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has successfully obtained the firmware dump.
- CAUSE: Driver successfully obtained the firmware dump.
- ACTION: No action required, information message only.
Event: 97
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has failed to obtain the firmware dump.
- CAUSE: Driver was unable to obtain the firmware dump.
- ACTION: No action required, other operations will continue.
Event: 98
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has received a user initiated %s loopback request.
- CAUSE: Driver received a user initiated loopback request.
- ACTION: No action required, information message only.
Event: 99
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has successfully completed loopback request.
- CAUSE: Driver successfully completed loopback request.
- ACTION: No action required, information message only.
Event: 100
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has encountered a failure during loopback.
- CAUSE: Driver encountered a failure during loopback. The failure may be due to link down or lack.
- ACTION: Please check the HBA port link and make sure the link is up and retry again.
Event: 101
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has received a user initiated reset request.
- CAUSE: Driver has received a request to issue a channel reset. Channel driver has r eceived a request to issue a channel re-initialization of the adapter. A reset c an be issued due to the following reasons:
- A Fatal Error interrupt occurred. (PCI Error, DMA Error, Memory Parity Error, Crossed 64-bit boundary.
- A Transmit PArity Frame Manager Error occurred.
- 3. An attempt to Freeze the FCP Assists timed out.
- An adapter reset request was received from fcmsutil.
- ACTION: An accompanying message should indicate the reason for the adapter reset. Action should be taken based on the accompanying error message. If there is no accompanying error message, then this reset was received from fcmsutil.
Event: 102
- SEVERITY: CRITICAL
- DESCRIPTION: Driver was successfully reset.
- CAUSE: Driver has successfully issued a channel reset.
- ACTION: No action required. Information message only.
Event: 103
- SEVERITY: CRITICAL
- DESCRIPTION: Driver has failed to reset.
- CAUSE: Driver is unable to complete the user initiated reset.
- ACTION: Driver may be busy executing another user operation or driver may be either suspended or disabled.
Event: 201
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to obtain all registers.
- CAUSE: Driver internal error.
- ACTION: Please report the problem to HP.
Event: 202
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to map register base to host memory.
- CAUSE: Driver failed to map the register base.
- ACTION: Please report the problem to HP.
Event: 210
- SEVERITY: INFORMATION
- DESCRIPTION: Driver is forcing link speed on user request.
- CAUSE: Driver is forcing link speed on user request.
- ACTION: No action required. Information message only.
Event: 211
- SEVERITY: INFORMATION
- DESCRIPTION: Driver topology is being set on user request.
- CAUSE: Driver is forcing topology change on user request.
- ACTION: No action required, information message only.
Event: 212
- SEVERITY: INFORMATION
- DESCRIPTION: Driver received link down notification.
- CAUSE: The Fibre Channel driver has declared the link to be dead because it has been down for more than 10 seconds. Please check the following:
- Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
- Verify that the device which is connected to the adapter port is functioning correctly.
- Verify that the adapter port is functioning correctly by performing internal and external loopback tests.
- ACTION: Please attach a loopback hood to the adapter port when executing a loopback test. #Internal loopback test /opt/fcms/bin/fcmsutil <device_file> int {crpat | cjtpat} [count] #External loopback test /opt/fcms/bin/fcmsutil <device_file> ext {crpat | cjtpat} [count] If loopback tests show that it is not functioning correctly contact the Hewlett Packard customer representative.
Event: 213
- SEVERITY: INFORMATION
- DESCRIPTION: Driver received link up notification.
- CAUSE: Driver has received a link-up notification.
- ACTION: No action required. Information message only.
Event: 214
- SEVERITY: CRITICAL
- DESCRIPTION: Driver found an unsupported firmware level on the HBA.
- CAUSE: Driver does not understand the firmware level found on the HBA.
- ACTION: Please upgrade the HBA firmware level to SLI-3 or higher Driver may be either suspended or disabled.
Event: 215
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to initialize because mailbox interface is not ready.
- CAUSE: Driver failed to initialize because HBA mailbox interface is not ready.
- ACTION: Replacement of the HBA is recommended.
Event: 216
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to initialize because port interface is not ready.
- CAUSE: Driver failed to initialize because port interface is not ready.
- ACTION: Replacement of the HBA is recommended.
Event: 217
- SEVERITY: CRITICAL
- DESCRIPTION: Driver failed to initialize due to invalid VPD on the HBA.
- CAUSE: Driver failed to initialize due to invalid VPD on the HBA.
- ACTION: No action required. Information message only.
Event: 218
- SEVERITY: CRITICAL
- DESCRIPTION: Driver detected an error in the response of mailbox.
- CAUSE: Driver detected an error in the response of mailbox command.
- ACTION: Driver will auto recover from the error. No action required.
Event: 219
- SEVERITY: CRITICAL
- DESCRIPTION: Driver detected an error in the response of IOCB.
- CAUSE: Driver detected an error in the response of IOCB.
- ACTION: Driver will auto recover from the error. No action required.
Event: 230
- SEVERITY: CRITICAL
- DESCRIPTION: Driver encountered a timeout for mailbox.
- CAUSE: A mailbox command issued by the driver has timed out. This indicates that the firmware could be hung as a result of which the posted mailbox command was not processed.
- ACTION: To analyze the root cause of this hang, please retrieve the firmware dump using the fcmsutil as follows: /opt/fcms/bin/fcmsutil /dev/fclp<num> dump_curr_state. The dump files will be saved in the /tmp directory. The dump files should be sent to HP for further analysis. See also the subsequent logs related to driver fatal.
Event: 250
- DESCRIPTION: Generic diag alert message.
- SEVERITY: CRITICAL
- CAUSE/ACTION: None
Event: 251
- DESCRIPTION: Generic diag warning message.
- SEVERITY: CRITICAL
- CAUSE/ACTION: None
Event: 252
- DESCRIPTION: Generic diag informational message.
- SEVERITY: CRITICAL
- CAUSE/ACTION: None
Event: 298
- DESCRIPTION: Invalid Event 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/log*.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: 299
- DESCRIPTION: The RAID SA Controller and 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: 300
- SEVERITY: Not specified
- 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/datm/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: 301
- SEVERITY: Not specified
- 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: 303
- SEVERITY: Not specified
- 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.