Fibre Channel Adapters (Events)

Fibre Channel Adapters (dm_ql_adapter Events)

Event 1

Severity: Critical

Description: Fibre Channel Driver Failed to Get PCI Configuration space handle.

Cause: Internal Error

Action: Contact the Hewlett Packard Customer Representative.

Event 2

Severity: Critical

Description: Fibre Channel Driver Failed to get system Cacheline Size.

Cause: Driver Internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 3

Severity: Critical

Description: Fibre Channel Driver Failed to allocate an interrupt Object.

Cause: Driver Internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 4

Severity: Critical

Description: Fibre Channel Driver Failed to set an Interrupt Line.

Cause: Driver Internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 5

Severity: Critical

Description: Fibre Channel Driver Failed to activate the Interrupts.

Cause: Driver Internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 6

Severity: Critical

Description: Fibre Channel Driver Failed to get All the Registers.

Cause: Driver Internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 7

Severity: Critical

Description: Fibre Channel Driver Failed to Map the ROM Base.

Cause: Driver Internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 8

Severity: Critical

Description: Fibre Channel Driver Failed to Map the ROM Base.

Cause: Driver Internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 9

Severity: Critical

Description: Fibre Channel Driver Received Suspend Request.

Cause:Fibre Channel Driver Received Suspend Request.

Action: No Action required. Information message only.

Event 10

Severity: Critical

Description: Fibre Channel Driver has been sucessfully suspended.

Cause: Fibre Channel Driver has been sucessfully suspended.

Action: No Action required. Information message only.

Event 11

Severity: Critical

Description: Fibre Channel Driver Received Resume Request.

Cause: Fibre Channel Driver received resume request.

Action: No Action required. Information message only.

Event 12

Severity: Critical

Description: Fibre Channel Driver has been Resumed Successfully.

Cause: Fibre Channel Driver has resumed successfully.

Action: No Action required. Information message only.

Event 13

Severity: Major Warning

Description: Fibre Channel Driver Received unsupported OLAR event.

Cause:The Fibre Channel Driver does not recognize the OLAR event. This is a driver internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 14

Severity: Major Warning

Description: Fibre Channel Driver Failed to Allocate DMA handles.

Cause: This is a driver internal Error.

Action: Contact the Hewlett Packard Customer Representative.

Event 15
Severity: CRITICAL
Description: Fibre Channel Driver Read bad NVRAM Header. Additional Status is 0x!
Status Code Status:
        0x1             Bad/Incorrect Signature. 
        0x2             Incorrect Minimum Version. 
        0x3             Incorrect Checksum. 
      
Cause: The NVRAM data is either corrupted or absent.

Action: Contact the Hewlett Packard Customer Representative.
Event 16

Severity: Critical

Description: Fibre Channel Driver failed to Resume because of a Fatal PCI Error.

Cause: Fibre Channel Driver cannot recover due to a PCI Error.

Action: Use olrad (1M) command to resume the card. Refer to the olrad (1M) man page and Hot Plug Documentation for additional details.

Event 17

Severity: Critical

Description: Fibre Channel Driver failed to initialize because of a PCI Error.

Cause: Fibre Channel driver detected a PCI error during initialization.

Action: Use olrad (1M) command to delete the card and add it back to recover from the failure. Refer to the olrad (1M) man page and Hot Plug Documentation for additional details.

Event 18

Severity: Critical

Description: Fibre Channel Driver received remove request.

Cause: Fibre Channel Driver received remove request.

Action: No action required. Information message only.

Event 19

Severity: Critical

Description: Fibre Channel Driver was removed successfully.

Cause: Fibre Channel Driver was removed successfully.

Action: No action required. Information message only.

Event 20

Severity: Critical

Description: Fibre Channel Driver Failed to update the RISC FW. The port might have been rendered unbootable.

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.

Action: 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. 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 21

Severity: CRITICAL

Description: Fibre Channel Driver received an unexpected fatal error from Firmware.

Cause: An unexpected fatal firmware error has occurred.

Action: If there was no unretrieved dump for the adapter port, the driver will have collected a new dump for the adapter port. This dump should be retrieved as soon as possible using the command: /opt/fcms/bin/fcmsutil <device_file> dump_saved_state <file_name> Please save the dump for HP analysis. If auto-recovery is turned on, the driver will automatically re-initialize the adapter port. If auto-recovery is turned off, the adapter port will not automatically be re-initialized. In this situation, please use the following command to re-initialize the adapter port: /opt/fcms/bin/fcmsutil <device_file> reset

Event 22

Severity: CRITICAL

Description: Fibre Channel Driver received Request Queue outbound DMA error from firmware.

Cause: An error occurred while the firmware was transferring data from system memory to adapter port memory.

Action: If there was no unretrieved dump for the adapter port, the driver will have collected a new dump for the adapter port. This dump should be retrieved as soon as possible using the command: /opt/fcms/bin/fcmsutil <device_file> dump_saved_state > <file_name> Please save the dump for HP analysis. If auto-recovery is turned on, the driver will automatically re-initialize the adapter port. If auto-recovery is turned off, the adapter port will not automatically be re-initialized. In this situation, please use the following command to re-initialize the adapter port: /opt/fcms/bin/fcmsutil <device_file> reset

Event 23

Severity: CRITICAL

Description: Fibre Channel Driver received Request Queue Inbound DMA error from firmware.

Cause: An error occurred while the firmware was transferring data from adapter port memory to system memory.

Action: If there was no unretrieved dump for the adapter port, the driver will have collected a new dump for the adapter port. This dump should be retrieved as soon as possible using the command: /opt/fcms/bin/fcmsutil <device_file> dump_saved_state > <file_name> Please save the dump for HP analysis. If auto-recovery is turned on, the driver will automatically re-initialize the adapter port. If auto-recovery is turned off, the adapter port will not automatically be re-initialized. In this situation, please use the following command to re-initialize the adapter port: /opt/fcms/bin/fcmsutil <device_file> reset

Event 24

Severity: INFORMATION

Description: Fibre Channel Driver received notification of a LIP on FC loop.

Cause: A LIP has occurred on the loop. This is a normal occurrence in Private Loop and Public Loop topologies.

Action: No action required. Informative message.

Event 25

Severity: INFORMATION

Description: Fibre Channel Driver Connected in Point-to-Point Topology.

Cause: The adapter port has completed point-to-point link initialization.

Action: This is a normal occurrence in Fabric Point-to-Point topologies. No action required. Informative message.

Event 26
Severity: MAJOR_WARNING

Description: Fibre Channel Driver received Link Down notification. Reason for Link Down is 0x!
Cause: The link has gone down due to one of the following reasons:
      Reason Code             Reason 
        0x0001             Loop Initialization Timeout  
        0x0002             Loss of Sync for more than 100 msec  
        0x0003             Loss of Receive Clock  
        0x0004             NOS or OLS received for more than 200 msec  
      
The following may cause this error:

Faulty fiber optic cabling

Loss of system clock

Signal synchronization problems
Action: In any of these cases, do the following: Verify that the fiber optic cable is functional and securely attached to the adapter port.
Event 27
Severity: MAJOR_WARNING

Description: Fibre Channel Driver received notification of LIP Failure. Reason for LIP Failure is 0x!
Cause:
 
Reason == 0x0000: LIP was not received within 45 ms (3 x AL_TIME).
   Reason == 0x1001: LISM frame was not returned within 2 sec. 
   Reason == 0x1002: Loop master, but didn't receive ARB(FO) in 2 sec. 
   Reason == 0x2003: Loop master, but didn't receive LIFA in 2 sec. 
   Reason == 0x2005: Loop master, but didn't receive LIPA in 2 sec. 
   Reason == 0x2007: Loop master, but didn't receive LIHA in 2 sec. 
   Reason == 0x2009: Loop master, but didn't receive LISA in 2 sec. 
   Reason == 0x200B: Loop master, but didn't receive LIRP in 2 sec. 
   Reason == 0x200D: Loop master, but didn't receive LILP in 2 sec. 
   Reason == 0x2011: Not loop master and didn't receive LIPA in 2 sec. 
   Reason == 0x2013: Not loop master and didn't receive LIHA in 2 sec. 
   Reason == 0x2015: Not loop master and didn't receive LISA in 2 sec. 
   Reason == 0x2017: Not loop master and didn't receive LIRP in 2 sec. 
   Reason == 0x2025: Not loop master and didn't receive LILP in 2 sec. 
   Reason == 0x2027: Not loop master and didn't receive CLS in 2 sec.
Action: This error will occasionally occur during normal operation. The driver will perform a LIP to recover and resume operation.
Event 28

Severity: INFORMATION

Description: Fibre Channel Driver received LIP F8.

Cause: Indicates that a port on the loop has detected a loop failure and is initiating a LIP in order to recover from the failure.

Action: No action required. Informative message. The adapter port will proceed with LIP.

Event 29
Severity: Critical

Description: OLAR Validation of Fibre Channel Driver Failed. Additional Status is 0x!
Cause: An Online Replacement operation has failed because the new card is not identical to the previous card. The status code gives the precise reason for the failure.
     Status Code
        0x1             Unsupported PCI Device Id 
        0x2             Unsupported PCI Vendor Id 
        0x3             Unsupported PCI Subsystem Vendor Id 
        0x4             Unsupported PCI Subsystem Id 

      
Action: Please use a card which is identical to the previous card. If you are using an identical card and problem persists, please contact your HP customer representative.
Event 30

Severity: INFORMATION

Description: Fibre Channel Driver successfully started a forced dump.

Cause: The fcd driver has received a request from fcmsutil to forcibly dump the driver and firmware of the adapter port. The fcd driver is now dumping the current state of the driver and of the adapter port firmware.

Action: No action required. Informative message.

Event 31
Severity: CRITICAL

Description: Fibre Channel Driver received Link Dead Notification.

Cause: The Fibre Channel driver has declared the link to be dead because it has been down for more than 10 seconds.
Action: 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. 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 32

Severity: CRITICAL

Description: Fibre Channel Driver received a Fatal Error Notification.

Cause: A possible cause is a Mailbox Command time out.

Action: Please see Preceding Error messages in the log files to isolate the cause. The Fibre Channel Driver will now perform fatal error handling. If there was no unretrieved dump for the adapter port, the driver will have collected a new dump for the adapter port. This dump should be retrieved as soon as possible using the command: /opt/fcms/bin/fcmsutil <device_file> dump_saved_state > <file_name> Please save the dump for HP analysis. If auto-recovery is turned on, the driver will automatically re-initialize the adapter port. If auto-recovery is turned off, the adapter port will not automatically be re-initialized. In this situation, please use the following command to re-initialize the adapter port: /opt/fcms/bin/fcmsutil <device_file> reset

Event 33

Severity: CRITICAL

Description: Fibre Channel driver received Fatal Error While processing a previous fatal error.

Cause: A fatal error occurred while the Fibre Channel Driver is in the middle of fatal error processing.

Action: No dump will be taken in this situation. If auto-recovery is turned on, the driver will automatically re-initialize the adapter port. If auto-recovery is turned off, the adapter port will not automatically be re-initialized. In this situation, please use the following command to re-initialize the adapter port: /opt/fcms/bin/fcmsutil <device_file> reset If the re-initialization or reset of the adapter port does not work, contact the HP customer representative.

Event 34

Severity: CRITICAL

Description: Fibre Channel driver awaiting user reset to come out of fatal err.

Cause: Fibre Channel Driver has completed fatal error processing and is now sitting in the fatal-error state waiting for user-intervention, because auto-recovery is turned off.

Action: To reset the adapter port, use the following command: /opt/fcms/bin/fcmsutil <device_file> reset

Event 35

Severity: CRITICAL

Description: Fibre Channel driver ROM write verification failed at location 0x!

Cause: An attempt to write into the Flash ROM of the adapter port has failed. Consequently, data in the Flash ROM may be corrupted. The Flash ROM holds the EFI Driver, the RISC firmware for booting through the adapter port, and the VPD Data.

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 try to restore the Flash ROM contents by reflashing the adapter using Offline Diagnostics Environment (ODE) tools.

Event 36
Severity: INFORMATION
Description: HBA Firmware is in the following unexpected state: 0x!
State == 0x0001: Performing or waiting to perform Loop Init. 
State == 0x0004: Loss-of-Synchronization, desynchronizing receiver.
Cause: Fibre Channel Driver has encountered an unexpected firmware state.

Action: No action required. Informative message. The Fibre Channel Driver will attempt recovery.
Event 37
Severity: CRITICAL

Description: Fibre Channel Driver is in Non-Participating state.

Cause: This means that it was unable to obtain a loop ID. This could be caused by one of the following:

There are more than 126 FC ports on the loop.

A cable or hardware problem exists.
Action: 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] 
Replace adapter if loopback tests show that it is not functioning correctly.
Event 38
Severity: CRITICAL
Description: Fibre Channel Driver has received an unexpected error status code from the Firmware in response to a Mailbox Command. The Mailbox Command code is: 0x!
Contents of Mailbox Out-Register[0] is: 0x! 
   Contents of Mailbox Out-Register[1] is: 0x! 
   MB Out[0] == 0x4001: Invalid Command.
   MB Out[0] == 0x4002: Host Interface Error.
   MB Out[0] == 0x4003: Verify Checksum Failed.
   MB Out[0] == 0x4005: Command Error.
   MB Out[0] == 0x4006: Command Parameter Error.
   MB Out[0] == 0x4007: Port ID Already in Use.
   MB Out[0] == 0x4008: Loop ID Already in Use.
   MB Out[0] == 0x4009: All IDs (80h - FFh) Already in Use.
   MB Out[0] == 0x400A: SNS not Logged in.
   MB Out[0] == 0x400B: Link Down Error.
   MB Out[0] == 0x400C: Diagnostic Echo Test Error.
Cause: This means that it was unable to obtain a loop ID. This could be caused by one of the following:

There are more than 126 FC ports on the loop.

A cable or hardware problem exists.
Action: 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]
Replace adapter if loopback tests show that it is not functioning correctly.
Event 39

Severity: INFORMATION

Description: Fibre Channel Driver has received Link Up notification.

Cause: This message indicates that link initialization is complete. This message is generated when the Link comes up after a Link Down has occurred.

Action: This is an informational message and no action is required.

Event 40

Severity: INFORMATION

Description: Fibre Channel Driver is ONLINE.

Cause: This message indicates that link initialization completed successfully and that any needed fabric logins and registrations have also been completed.

Action: This is an informational message and no action is required.

Event 41

Severity: INFORMATION

Description: Fibre Channel Driver has received the following LIP Reset: 0x!

Cause: The Fibre Channel Driver has received a LIP Reset. The rightmost byte of the LIP Reset value is the AL_PA of the device which sent the LIP Reset.

Action: The Fibre Channel Driver does not support LIP Reset, hence it will treat the LIP Reset as a regular LIP. This is an informational message and no action is required.

Event 42

Severity: MAJOR_WARNING

Description: Fibre Channel Driver HBA N_PORT ID changed from 0x! to 0x!

Cause: The Fibre Channel Driver HBA's N_Port ID has changed.

Action: This indicates a configuration change in the SAN. If such a configuration change has been made, then this message is normal. Otherwise, please check the SAN configuration.

Event 43
Severity: MAJOR_WARNING

Description: Fibre Channel Driver topology changed from ! to !.

Cause: The Fibre Channel Driver HBA's topology has changed.
Action: This indicates a configuration change in the SAN. If such a configuration change has been made, then this message is normal. Otherwise, please check the SAN configuration. Topology codes:
    0 - Private Loop 
    1 - Public Loop 
    3 - Fabric Point-to-Point
Event 44

Severity: CRITICAL

Description: Fibre Channel Driver has detected a PCI Error.

Cause: PCI error occurred.

Action: No action required. Information message only.

Event 45

Severity: CRITICAL

Description: Fibre Channel Driver Failed to update the EFI Driver. The Port might have been rendered unbootable.

Cause: An attempt to load a new EFI Driver update image into the Flash ROM of the adapter port has failed. The EFI driver 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.

Action: This failure may have also corrupted the EFI Driver and VPD Data, which are stored in the adapter port Flash ROM. 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 try to restore the Flash ROM contents by reflashing the adapter using Offline Diagnostics Environment (ODE) tools.

Event 46

Severity: INFORMATION

Description: Task Management function to port 0x! failed.

Cause: Task Management function to port 0x! failed.

Action:

Check that the device is powered and is accepting other commands.

If the device is accepting other commands, check device internal logs.

Event 47

Severity: SERIOUS

Description: Bus Instance number ! 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 Hewlett Packard.

Event 48

Severity: CRITICAL

Description: fcd driver received notification of RISC Parity Error.

Cause: Fibre Channel RISC controller chip detected a internal data and/or instruction queue parity error.

Action: fcd driver will try to take a driver and firmware dump to diagnose this problem. Please save this dump for Hewlett Packard to analyze.

Event 49

Severity: CRITICAL

Description: fcd driver received a RISC Interrupt for an unknown/unsupported reason.

Cause: fcd driver will try to take a driver and firmware dump to diagnose this occurrence.

Action: Please save this dump for Hewlett Packard to analyze.

Event 50

Severity: CRITICAL

Description: fcd driver received an Unknown/Unsupported Asynchronous Event from the Firmware. Unsupported Async Event = 0x!

Cause: Driver will try to take a driver and firmware dump to diagnose this occurrence.

Action: Please save this dump for Hewlett Packard to analyze.

Event 51

Severity: CRITICAL

Description: For backward compatibility domain 8 (private loop) is not allowed.

Cause: Configure the switch to assign a domain value other than 8.

Action: Domains > 8 will not be recognized till this problem is fixed.

Event 52
Severity: MAJOR_WARNING
Description: No valid LUNs found on array device with device id 0x!
device id = loop id, for private loop devices 
device id = nport ID, for fabric/public-loop devices
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 53
Severity: MAJOR_WARNING
Description: Invalid LUN format found on array device with device id 0x!
 
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices
The 64 bit LUN found was 0x ! !
Cause: Some or all of the LUNs configured in the disk array device are having an invalid or unsupported format.

Action: Please contact your HP representative.
Event 54

Severity: CRITICAL

Description: The system has reached its maximum device addressable limit.

Cause: The total LUNs discovered by the host bus adapter through all the fibre channel 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. Please contact your HP representative for more information.

Event 55

Severity: MINOR_WARNING

Description: Fibre channel host port's link is not online. Scan of the port will not show any devices. Ignore this message if there is no cable connected.

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] If loopback tests show that it is not functioning correctly, please contact your HP customer representative.

Event 56
Severity: CRITICAL
Description: LUN list size from REPORT_LUNS command greater than max IO for device with device id 0x!
 
          device id = loop id, for private loop devices 
          device id = nport ID, for fabric/public-loop devices 
      
Cause: The response data for the SCSI command REPORT_LUNS is larger than the maximum I/O size supported by the host bus adapter.

Action: This can happen if the disk array has a large number of LUNs configured. Please contact your HP representative.
Event 57
Severity: CRITICAL
Description: Inquiry failed on FCP device with device id 0x!
 
          device id = loop id, for private loop devices 
          device id = nport ID, for fabric/public-loop devices 
      
Cause: SCSI command INQUIRY to the device failed, even after retries.

Action: 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.
Event 58
Severity: INFORMATION
Description: Target with device id 0x! rejected PLOGI: reason code 0x!, explanation 0x!.
          device id = loop id, for private loop devices 
          device id = nport ID, for fabric/public-loop devices 
                                        
Cause: If the port is another initiator, there is no problem. Otherwise (the port is a target device), driver won't be able to communicate with the device.

Action: Please check the device. If the problem persists, please contact your HP customer representative.
Event 59
Severity: CRITICAL
Description: Port World-wide name for device id 0x! has changed.
          device id = loop id, for private loop devices 
          device id = nport ID, for fabric/public-loop devices
        
Cause: Fibre Channel disk addressing is based on Nport_id.

Action: 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. However, if the device has been replaced intentionally, please use the fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
Event 60

Severity: CRITICAL

Description: Private loop device didn't acquire the hard address: Hard Address is 0x! but acquired AL_PA is 0x!.

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.

Action: It might be due to multiple devices in the loop with the same hard address setting. 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:

Please change hard address setting for the newly added devices, so that old device can keep its hard address.

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 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: CRITICAL
Description: Port World-wide name for device id 0x! has changed OR the device id has disappeared from Name Server GPN_FT (FCP type) response.
device id = loop id, for private loop devices 
device id = nport ID, for fabric/public-loop devices.
Cause: On receiving RSCN, driver sent Name Server GPN_FT request to obtain all the FC-4 type device information in the fabric. 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.

Action: Driver won't be able to communicate with the device any more, please check that device. If the problem persists, please contact your HP customer representative.
Event 62
Severity: CRITICAL
Description: Port World-wide name for device id 0x! has changed OR the device id has disappeared from Name Server GPN_FT (FCP type) response.
device id = loop id, for private loop devices 
device id = nport ID, for fabric/public-loop devices.
Cause: This is a paired message with "Target device is lost in the Name Server GPN_FT response". No action is needed. On receiving another RSCN, driver sent Name Server GPN_FT request to obtain all the FC-4 type device information in the fabric. Driver has detected that a previously lost device (Nport_id) is back in the GPN_FT response, or it's corresponding World-Wide Name remains the same.

Action: Driver will be able to communicate with the device.
Event 63

Severity: INFORMATION

Description: Fibre Channel Driver has received an RSCN of type 0x! for N_Port 0x!

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. The Fibre Channel Driver will now query the Fabric to discover what the change is.

Action: This is an informational message and no action is required.

Event 64

Severity: INFORMATION

Description: Received Port LOGO 8014h AE for Alias ! ID 0x!

Cause: A device has logged out the Fibre Channel Driver.

Action: This is an informational message and no action is required.

Event 65
Severity: CRITICAL
Description: Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request.
Explanation: FC-4 Type not registered.
Cause: The HBA port may not be part of a zone.

Action: Please check zone configuration on your switch.
Event 66

Severity: CRITICAL

Description: Mailbox command 0x! timed out.

Cause: A mailbox command issued by the driver has timed out.

Action: This indicates that the firmware could be hung as a result of which the posted mailbox command was not processed. The analyze the root cause of this hang, please retrieve the firmware dump using the fcmsutil as follows /opt/fcms/bin/fcmsutil /dev/fcd<num> dump_saved_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.

Event 67

Severity: CRITICAL

Description: HBA encountered unrecoverable hardware error. Replacement is required.Additional data: MB2 0x! ; MB3 0x !

Cause: This event indicates a faulty hardware component on the adapter.

Action: The adapter should not be used, please replace it as soon as possible. Please return the faulty adapter to the Hewlett Packard Customer Representative for analysis. Please report the additional data in the error message to HP.

Event 68

Severity: CRITICAL

Description: HBA encountered the NVRAM to be at risk of being corrupted. Replacement of the HBA is recommended.

Cause: Failure in setting NVRAM protection bits for HBA NVRAM. Without the NVRAM protection bits being set, the NVRAM contents are at risk of being corrupted.

Action: Please report the additional data in the error message to HP.

Event 69

Severity: CRITICAL

Description: HBA encountered the VPD to be empty. Replacement of the HBA is recommended.

Cause: Failure in reading the HBA VPD.

Action: The adapter should not be used, please replace it as soon as possible. Please return the faulty adapter to the Hewlett Packard Customer Representative for analysis. Please report any additional error messages to HP.

Event 70

Severity: CRITICAL

Description: HBA reset was forced. Replacement of the HBA is recommended.

Cause: HBA reset was forced.

Action: The adapter should not be used, please replace it as soon as possible. Please return the adapter to the Hewlett Packard Customer Representative for analysis. Please report any additional error messages to HP.

Event 98

Severity: Invalid severity code

Description: The FCMS Adapter and driver received invalid severity 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 99

Severity: Invalid severity code

Description: The FCMS Adapter and driver received invalid severity 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: CRITICAL

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 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 monitoringthe 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.

Top of Page / Diagnostics HOME

URL: http://docs.hp.com/hpux/onlinedocs/diag/ems/dm_ql_adapter.htm
Last updated: Friday September 7 10:24:20 PST 2007