Events Common to all Operating Systems

Events Common to all Operating Systems

The following events apply to systems running any of the supported operating systems:

Event 1

• Severity: Information
• Description: The Fibre Channel Driver received a LINK DOWN interrupt
• Cause: A LIP has occurred on the loop
• Action: No action required. Informative message. The link should recover and an accompanying informative message indicating LINK UP should be seen.

Event 2

• Severity: Information
• Description: The Fibre Channel Driver received a LINK UP interrupt
• Cause: A LIP has completed on the loop
• Action: No action required. Informative message.

Event 3

• Severity: Major Warning
• Description: The Fibre Channel Driver received an interrupt from the adapter indicating an Elastic Store Error Storm
• Cause: The Tachyon TL chip controlling Fibre Channel operation has experienced an overflow or underflow in its inbound data queue.
  The following may cause this error:
  1. Cable fault
  2. Hardware fault
  3. Optical Unit Fault
  The Tachyon TL chip will recover without intervention
• Action: Verify the fiber optic cable integrity as follows:
  1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  2. After checking the cabling, execute a loopback test on the FC Adapter using fcmsutil. Command syntax is as follows: /opt/fcms/bin/fcmsutil <device file>lb plm If the problem persists, replace the adapter

Event 4

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating CREDIT ERROR while the chip was operating as an NL_PORT
• Cause: The Tachyon TL chip controlling Fibre Channel operation is connected to a remote node on the loop that is trying to send a frame and has not been able to acquire BB_credit within the configured period of time (ED_TOV).
• Action: No action is required. The driver will perform a LIP and recover.

Event 5

• Severity: Critical
• Description: The Fibre Channel Driver received an interrupt indicating a Link Fail Storm.
• Cause: The following may cause this error:

1. Faulty fiber optic cabling         2. Loss of system clock         3. Signal synchronization problems

• Action: In any of these cases, do the following:

1. Verify that the fiber optic cable is functional and securely         attached to the Fibre Channel Mass Storage Adapter.         2. After checking the cabling, reset the FCMS Adapter        using fcmsutil.        Command syntax is as follows:         /opt/fcms/bin/fcmsutil <device file >  reset

Event 6

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating that an OPEN was sent to an ALPA of 0x%x which did not respond.
• Cause: The Tachyon TL Fibre Channel Mass Storage Adapter attempted to open a device on the loop which did not respond to the OPN primitive sequence. You will observe this behavior during normal operation.
• Action: No action is required.

Event 7

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating that a LIPF has been received.
• Cause: Loop Initialization Process (LIP) will occur under normal operation LIP may be attributed to link or device failures that cause a topology change.
• Action: The System Administrator does not need to take any action. The system should recover from this condition.

Event 8

• Severity: Critical
• Description: The Fibre Channel Driver received a request to perform a chip reset.
• Cause: Fibre Channel driver has received a request to issue a channel reset. Channel driver has received a request to issue a channel re-initialization of the adapter.

A reset can be issued due to the following reasons:         1. A Fatal Error interrupt occurred.        (PCI Error, DMA Error, Memory Parity Error, Crossed 64-bit boundary.         2. A Transmit PArity Frame Manager Error occurred.        3. An attempt to Freeze the FCP Assists timed out.         4. An adapter reset request was received from fcmsutil.

An accompanying message should indicate the reason for the adapter reset.

• Action: 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 9

• Severity: Critical
• Description: The Fibre Channel Driver received a fatal PCI Error Interrupt.
• Cause: A Fatal Error Interrupt was received by the fibre channel driver. The following may cause this error:
  1. Memory Parity Error detected.
  2. Crossed 64-bit boundary interrupt detected.
  3. DMA Error detected.
  4. PCI Error Detected.
• Action: No action required. The driver will issue a channel reset to recover from this condition

Event 10

• Severity: Information
• Description: The Fibre Channel Driver received a Loop State Timeout when the Loop State Machine was in the OPENED State
• Cause: The Tachyon TL chip controlling Fibre Channel operation has been in one operating state for longer than the configured period of time (ED_TOV).
• Action: This error will occasionally occur during normal operation. The driver will recover and resume operation.

Event 11

• Severity: Information
• Description: The Fibre Channel Driver received a Loop State Timeout
• Cause: The Tachyon TL chip controlling Fibre Channel operation has been in one operating state for longer than the configured period of time (ED_TOV)
• Action: This error will occasionally occur during normal operation. The driver will perform a LIP to recover and resume operation.

Event 12

• Severity: Critical
• Description: The Fibre Channel Driver detected a NOS/OLS storm
• Cause: The Tachyon TL adapter believes it is in a different fibre channel topology than the other fibre channel devices ( e.g., pt-pt vs. loop ). The following Events may cause this interrupt to occur:

        1. A device configured in point-to-point topology is connected            to the loop.         2. Failed Loop Initialization (LIP).         3. Failure of Fibre Channel Mass Storage devices to forward LIP         messages during the LIP process.

• Action: This error may occur during normal operation. No action is required. The driver will perform a LIP to force the other ports into a loop topology. If the condition persists, examine the devices connected on the loop and verify that the connected devices are configured in loop topology and not in point-to-point topology.

Event 13

• Severity: Critical
• Description: The Fibre Channel Driver received a Loop Port Bypass
• Cause: The Tachyon TL adapter received a sequence primitive forcing it to be bypassed from the loop.
• Action: Issue the following commands from fcmsutil to enable the adapter on the loop:
  /opt/fcms/bin/fcmsutil /dev/td0 write 0x1ec 0x00050101
  /opt/fcms/bin/fcmsutil /dev/td0 write 0x1c4 0x00000062
  /opt/fcms/bin/fcmsutil /dev/td0 write 0x1c4 0x00000003

Event 14

• Severity: Critical
• Description: The Fibre Channel Driver received a Loop Port Enable
• Cause: The Tachyon TL adapter received a sequence primitive indicating it was enabled back on the loop.
• Action: No action required.

Event 15

• Severity: Critical
• Description: The Fibre Channel Driver received an interrupt from the adapter indicating a LASER FAULT which is a link failure.
• Cause: The Fibre Channel Mass Storage Adapter experienced a failure in laser operation. The problem may be faulty cabling.
• Action: Do the following:
  1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  2. After checking the cabling, execute a loopback test using fcmsutil.
  Command syntax is as follows:
  /opt/fcms/bin/fcmsutil <device file > lb plm

Event 16 This Event is no longer used. It is present here for compatibility reasons.

Event 17

• Severity: Information
• Description: The Fibre Channel Driver received an ERQ frozen interrupt from the adapter
• Cause: The Tachyon TL adapter generated an interrupt indicating that the ERQ has been frozen. This is caused by the driver requesting the Tachyon TL chip to freeze the ERQ.
• Action: No action is required. Informative message. The driver will recover from this condition

Event 18

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating that a primitive was transmitted
• Cause: The Tachyon TL adapter transmitted a primitive sequence. This is caused by the driver issuing a primitive sequence to the chip to be transmitted.
• Action: No action is required. Informative message

Event 19

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating that a primitive was received
• Cause: The Tachyon TL adapter received a primitive sequence.
• Action: No action is required. Informative message

Event 20

• Severity: Critical
• Description: The Fibre Channel Driver received a Transmit Parity Error
• Cause: The Tachyon TL Adapter generated a Transmit Parity Error. Frame Manager interrupt. This is caused when the Tachyon TL chip detects an internal parity error on the outbound data path
• Action: The driver will recover from this condition by issuing a reset. If the condition persists, replace the adapter.

Event 21

• Severity: Serious
• Description: The Fibre Channel Driver detected a Loss of Signal Storm.
• Cause: The Fibre Channel input signal has been lost for a period of time. The fault may lie with any node on the loop.
• Action: The system will recover on its own.

Event 22

• Severity: Serious
• Description: The Fibre Channel Driver detected a Out of Synchronization Storm.
• Cause: Problems with optical transmitter and link connection usually cause this error.
• Action: The system will recover. No action is required

Event 23

• Severity: Serious
• Description: The Fibre Channel Driver has gone into non-participating mode.
• Cause: A cable or hardware problem exists. This can also be caused due to the Tachyon TL adapter changing its AL_PA across a LIP
• Action: Do the following:
  1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  2. After checking the cabling, execute a loopback test using fcmsutil. Command syntax is as follows: /opt/fcms/bin/fcmsutil <device file > lb plm
  If the problem persists after verifying fiber optic cabling, replace the adapter

Event 24

• Severity: Information
• Description: The Fibre Channel Driver received a FCP assists completion message
• Cause: The Tachyon TL adapter generated an interrupt indicating that the FCP Assists have been frozen. This is caused by the driver requesting the Tachyon TL chip to freeze the FCP Assists.
• Action: No action required. Informative message. The driver will recover from this condition.

Event 25

• Severity: Information
• Description: The Fibre Channel Driver dropped an inbound exchange due to tgt_thread resource depletion
• Cause: This is caused due to non-availability of internal memory resource within the Tachyon TL fibre channel driver and can result in some exchanges being dropped. This condition only affects exchanges which are originated by another port on the loop
• Action: No action is required. System will recover.

Event 26

• Severity: Critical
• Description: The Fibre Channel Driver is being taken offline due to a user request.
• Cause: The Tachyon TL adapter was disabled due to a request from fcmsutil.
• Action: Issue the following command to re-enable the adapter:
  /opt/fcms/bin/fcmsutil <device file > enable

Event 27

• Severity: Critical
• Description: Fibre Channel Driver is brought online due to a user request
• Cause: The Tachyon TL adapter was enabled due to a request from fcmsutil
• Action: No action required.

Event 28

• Severity: Critical
• Description: The Fibre Channel card was suspended due to user request.
• Cause: Fibre Channel card is being suspended.
• Action: No action is required. Informative message.

Event 29

• Severity: Critical
• Description: The Fibre Channel card is being resumed due to user request.
• Cause: Fibre Channel card is being resumed.
• Action: No action is required. Informative message.

Event 30

• Severity: Critical
• Description: Normal suspend of Fibre Channel card timed out. Fibre Channel Driver has suspended the card by force.
• Cause: Fibre Channel card suspended by force.
• Action: Report the problem to Hewlett-Packard.

Event 31

• Severity: Critical
• Description: Resume request for Fibre Channel card failed. Reason code = 0x!
• Cause: The resume request can fail due to the following reasons:

Reason Code	Reason
0x1	Validation of the card failed
0x2	Interrupt enable failed

•  
• Action: Please refer to the earlier message in the log to get the reason for validation failure.

Event 32

• Severity: Critical
• Description: Fibre Channel card has been successfully suspended.
• Cause: This message is given out to indicate normal completion of suspend operation.
• Action: No action required. Informative message.

Event 33

• Severity: Critical
• Description: Fibre Channel card has been successfully resumed. Channel statistics and Name Server statistics has been cleared. If you need to clear device statistics please use fcmsutil(1M) with ‘clear_devstat’ all option to clear device status
• Cause: This message is given out to indicate normal completion of resume operation.
• Action: No action required. Informative message.

Event 34

• Severity: Critical
• Description: Validation of Fibre Channel card failed.
• Cause: Validation of Fibre Channel card can fail due to the following:

Reason Code	Reason
0x01	Couldn’t get IO nodes properly
0x02	Unsupported PCI Vendor ID
0x04	Unsupported PCI Device ID
0x08	Unsupported PCI Subsystem Vendor ID
0x10	Unsupported PCI Subsystem ID
0x20	Unsupported Tachyon TL/TS Chip Revision
0x40	Unsupported ROM Control Configuration

• Action: Report the problem to Hewlett-Packard.

Events Common to HP-UX 11i v1 and HP-UX 11i v2 Systems

The following events apply to systems running HP-UX 11i v1 or HP-UX 11i v2 only:

Event 35

• Severity: Information
• Description: Fibre Channel Driver received a Link Dead Notification

Cause: The Fibre Channel driver has declared the link to be dead because it has been down for more than 5 seconds.

• Action: Please check the following:

      1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.

      2. Verify that the device which is connected to the adapter port is functioning       correctly.

      3. 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 the adapter is not functioning correctly contact the       Hewlett Packard customer representative.

 

Event 36

• Severity: Information
• Description: Looping for resources to reconnect to target. nport ID = 0x!
• Cause: The device state machine is thread is trying once per second to reallocate a SF thread in order to send a PLOGI frame to keep the device open
• Action: If the message repeats, driver data structures are not being freed. check for a large number (>60) of targets on the loop or a large number of IO aborts which are not succeeding immediately

 

Event 37

• Severity: Information
• Description: Target rejected PLOGI
• Cause: The device at the loop address was unwilling to start a session with the card. If the device at that address is another initiator, there is no problem.
• Action: Check that the device is powered and connected. Check that the protocol versions supported by the device cover at least part of the range from FC-PH 4.3 and FC-PH-3 and that the device supports class 3 operation.

 

Event 38

• Severity: Critical
• Description: World wide name (unique identifier) for following device has changed
• Cause: Unlike paralled SCSI, Fibre Channel allows easy hot-swapping of disks. Due to address conflicts it is possible for disks to swap loop IDs accidentally when re-plugging them into a hub. In order to reduce the chance of user data corruption or file system panics, we normally require the world wide names for a particular device to stay the same. Requiring the fcmsutil replace_dsk command ensures that the replacement is intentional. The driver has detected a new “world-wide name” unique identifier at a loop position previously occupied by a device with a different identifier.
• Action: If this is due to a deliberate replacement of the previous device use the fcmsutil replace_dsk command to allow the new device to be used. If there has been no intentional replacing of any devices, check for conflicts in address assignments of devices on the loop.

 

Event 39

• Severity: Information 
• Description: Target Rejected PRLI
• Cause: The device with the reported Loop Identifier is not willing to be a SCSI target.
• Action: Verify that the device at the loop ID is another initiator. If the device is supposed to be a target verify with the vendor that the PRLI ACC payload reports it as a target

 

Event 40

• Severity: Information
• Description: Target Rejected ADISC
• Cause: The target device rejected a request to verify its name and address after a loop initialization.
• Action: If a new device has been installed on the loop, check that its address setting does not conflict with that of any other device. If a device has been replaced on the loop, use the fcms utility’s “replace_dsk” command to notify the driver to allow a different name at the previously used address.

 

Event 41

• Severity: Critical  
• Description: Unable to access previously accessed target. nport ID = 0x!
• Cause: An attempt to re-open a device which had been open earlier has failed.
• Action: There should be additional logging messages which will allow diagnosis of the problem.

 

Event 42

• Severity: Information 
• Description: Unable to reset target
• Cause: A device was unable to execute a reset. Status returns are:

2 – device appears to have been removed

3 – request timed out

4 – link error while receiving FCP_RSP

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

     

Event 43

• Severity: Information
• Description: Unable to reset target
• Cause: Response code values as listed in FCP table 12.
• Action: Check device internal logs

 

Event 44

• Severity: Information
• Description: Target rejected TPRLO
• Cause: The device was not able or willing to execute a Fibre Channel “third party process logout”.
• Action: If this device is being used in a ServiceGuard cluster, verify that the device is supported for use in clusters. If the device is not part of a cluster, this message may be ignored.

 

Event 45

• Severity: Information
• Description: ACC or LS_RJT frame in response to PLOGI is too short from device at nport id = 0x!
• Cause: Response frame to request was truncated probably by some transient failure
• Action: No action required unless frequently repeated

 

Event 46

• Severity: Information
• Description: Minimum version of FC-PH supported by device at nport Id 0x! is too high
  It is 0x! and card supports upto 0x20.
• Cause: The device does not support any version of the Fibre Channel protocol supported by the card.
• Action: If the device is a SCSI target which will be used by the host, it must be replaced.

 

Event 47

• Severity: Information
• Description: Maximum version of FC-PH supported by device at nport Id 0x! is too low
  It is 0x! and card needs at least 0x09.
• Cause: The device does not support any version of the Fibre Channel protocol supported by the card.
• Action: If the device is a SCSI target which will be used by the host, it must be replaced

 

Event 48

• Severity: Information
• Description: Can’t work with device at nport id 0x!. It does not support Class-3
• Cause: The device does not support “Class 3” Fibre Channel communication.
• Action: If the device is another host on the loop, or device which is not a SCSI target, no action is required. Otherwise, replace with a target which supports class 3 operation.

 

Event 49

• Severity: Information
• Description: ACC or LS_RJT response frame (to PRLI) from device at nport id 0x! is too short
• Cause: Response frame to request was truncated, probably by some transient failure.
• Action: No action required unless frequently repeated

 

Event 50

• Severity: Information
• Description: Unable to speak SCSI FCP with device at nport id 0x! because response code 0x! is not one or five
• Cause: Device is not returning the response code we require. Either it is another initiator, or it has not been qualified for use with this driver
• Action: If condition is not transient, and the device is supposed to be a target, verify that device is supported by HP or contact vendor. Check for address conflicts

 

Event 51

• Severity: Information
• Description: Will not log in with device at nport id 0x! because it is not a target.
• Cause: The device is unable to act as a SCSI target.
• Action: The device is probably another initiator, in which case no action is required. This message will be seen in multi-initiator loops where the two hosts are probing each other’s ports.

 

Event 52

• Severity: Information
• Description: ACC or LS_RJT response frame (to ADISC) from device at nport id 0x! is too short.
• Cause: Response frame to request was truncated, probably by some transient failure.
• Action: No action required unless frequently repeated.

 

Event 53

• Severity: Critical
• Description: Address conflict encountered by device at nport id 0x!
• Cause: HA is the “hard address” (port ID), configured via a switch or console, that the device is trying to acquire. Our adapter cards themselves don’t have hard addresses.
• Action: It appears that there are (or were) more than one device with the same address (loop ID) setting. One of them will be ignored. Look for two (or more) devices on the loop which have the reported address setting. Change the address settings so that all devices on the loop have a unique addresses, or remove the overlapping devices. Even after you change the address settings on the devices, it may be necessary to reset or power-cycle both the devices whose settings have been changed, and any remaining device with the address setting which encountered the conflict.

 

Event 54

• Severity: Information
• Description: Bad ADISC reply HA is 0x! but n-port is 0x!
• Cause: It appears that there are (or were) more than one device with the same address (loop ID) setting. One of them will be ignored.
• Action: Look for two (or more) devices on the loop which have the reported address setting. Change the address settings so that all devices on the loop have a unique addresses, or remove the overlapping devices. Even after you change the address settings on the devices, it may be necessary to reset or power-cycle both the devices whose settings have been changed, and any remaining device with the address setting which encountered the conflict.

 

Event 55

• Severity: Critical
• Description: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response returned by nport ID 0x! FLOGI/PLOGI Fail Code = 0x!
• Cause: The PLOGI or FLOGI response from the device or switch had a parse error. Parsing error could occur if the PLOGI/FLOGI response payload had an unexpected value. Parsing error occurs normally due to
  – 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/syslog.log

 

Event 56

• Severity: Information  
• Description: Received an unassisted FCP frame from port 0x%x
• Cause: An unexpected SCSI FCP frame was received from the target device
• Action: This may be a temporary condition caused by loop congestion. Examine the Fibre Channel logs for the device reported for any problems. If the problem does not persist, no additional action is necessary. If the problem persists, contact your HP customer representative.

 

Event 57

• Severity: Serious
• Description: Received an unassisted FCP frame from port 0x%x for OX_ID 0x%x. The sest entry associated with the OX_ID is currently in use with another device at port 0x%x
• Cause: An unexpected SCSI FCP frame was received from a target device on an exchange that was in use with another device. This may be caused by incorrect loop configurations.
• Action: Examine the fibre channel loop and devices reported above. If the problem persists, contact your HP customer representative.

 

Event 58

• Severity: Serious
• Description: Received an unassisted FCP frame from port 0x%x with originator exchange ID 0x%x The expected originator exchange ID is 0x%x
• Cause: An FCP frame was received from a target device with unexpected OXID. This might indicate a device failure.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 59

• Severity: Serious
• Description: Received an FCP_XFER_RDY frame from port 0x%x, with originator exchange ID 0x%x Unexpected value 0x%x for F_CTL in frame header
• Cause: FCP_XFER_RDY frame was received from the target device. This might indicate a device failure.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 60

• Severity: Serious
• Description: Received an invalid FCP_XFER_RDY frame from port 0x! with originator exchange id 0x! The exchange is currently used for read (cdb_flags 0x!)
• Cause: Received an FCP_XFER_RDY frame from target device with unexpected values in frame payload. This might indicate a device failure.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 61

• Severity: Serious
• Description: Received an invalid FCP_XFER_RDY frame from port 0x%x DATA_RO field 0x! in FCP_XFER_RDY is not less than the transfer length
• Cause: Received an FCP_XFER_RDY frame from target device with unexpected values in frame payload. This might indicate a device failure.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 62

• Severity: Serious
• Description: Received an invalid FCP_RSP frame from port 0x! with originator exchange ID 0x!. The frame length ! bytes exceeds what is allowed by FC-PLDA
• Cause: An FCP_RSP frame was received from the target device exceeding the maximum supported length. This might indicate an unsupported device.
• Action: If the problem persists, contact your HP customer representative.

 

Event 63

• Severity: Serious
• Description: Received an invalid FCP_DATA frame from port 0x%x with originator exchange ID 0x%x. The exchange is currently used for write operation.
• Cause: Unexpected FCP_DATA frames received from the target device. This may be a temporary condition due to loop congestion.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 64

• Severity: Serious
• Description: Received an invalid FCP_CMND frame from port 0x%x with originator exchange ID 0x%x. Incoming FCP target mode operations are not supported
• Cause: An unexpected FCP_CMND frame was received from the device. This indicates an incorrect behavior of the remote device.
• Action: Examine the remote device for incorrect function. If the problem persists, contact your HP customer representative.

 

Event 65

• Severity: Serious
• Description: Received an invalid FCP_CMND frame from port 0x! with unsupported category information 0x!
• Cause: An unsupported FCP frame was received from the remote device. This indicates a non-PLDA compliant device.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 66

• Severity: Serious
• Description: Received Host Programming Error (HPE) in Outbound Completion Message (OCM) for an I/O to the device at port 0x%x
• Cause: Remote device is requesting for more data than that was specified in the write request. This indicates an incorrectly behaving remote device.
• Action: Examine the remote device for possible errors. If the problem persists, contact your HP customer representative.

 

Event 67

• Severity: Serious
• Description: Received Frame Time Out (FTO) error in Outbound, Completion Message (OCM) for an I/O to the device at port 0x! The index of sest entry used is !
• Cause: The remote device has stopped responding to I/O requests.
• Action: Check the loop to see if the device is still operating on the loop. Examine the fibre channel device logs for errors.

 

Event 68

• Severity: Serious
• Description: Received a late ABTS response from device at port 0x%x for the exchange with OX_ID 0x%x
• Cause: A late response to an I/O abort request was received. The response was ignored.
• Action: No further action is needed. Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 69

• Severity: Serious
• Description: Overflow error while receiving FCP_RSP frame from target device at port 0x!
• Cause: An FCP_RSP frame was received from the target device exceeding the maximum supported length. This might indicate an unsupported device.
• Action: If the problem persists, contact your HP customer representative.

 

Event 70

• Severity: Serious
• Description: Received FCP frames from device at port 0x!. Remote device is the originator for the exchange. OXID of the exchange is 0x!
• Cause: An FCP frame was received from the device with an incorrect exchange context. This indicates an incorrect behavior of the remote device.
• Action: Examine the remote device for incorrect function. If the problem persists, contact your HP customer representative.

 

Event 71

• Severity: Serious
• Description: Received BA_RJT as response to ABTS from device at port 0x!. BA_RJT reason code is 0x!
  Full BA_RJT payload is 0x!
• Cause: The attempt to abort an I/O was rejected. This might indicate a non-PLDA compliant device.
• Action: Examine the reject reason code and fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 72

• Severity: Serious
• Description: Received invalid response to ABTS from device at port 0x%x.
• Cause: Received an invalid response to an I/O abort request. This indicates an incorrect behavior of the remote device.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 73

• Severity: Serious
• Description: Unexpected FCP_XFER_RDY from device at port 0x! OXID of the exchange was 0x!
• Cause: An unexpected FCP_XFER_RDY was received from the remote device. This might indicate a non-PLDA compliant device.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 74

• Severity: Serious
• Description: Unexpected FCP_RSP from device at port 0x! OXID of the exchange was 0x!
• Cause: An unexpected FCP_RSP was received from the remote device. This might be a temporary condition caused by loop disturbance.
• Action: No further action may be needed. Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 75

• Severity: Serious
• Description: Unexpected event in link down state from target device at port 0x! OXID of the exchange is 0x! The event received is 0x!
• Cause: Driver has received an unexpected event for an I/O exchange with the remote device. This might indicate an incorrect remote device behavior or a driver problem.
• Action: Report the problem to HP along with the details of remote device.

 

Event 98

Invalid Severity Message

• Description: The FCMS Adapter and driver received invalid severity code
• 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 FCMS Adapter and driver received invalid error code.
• 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 100

• Severity: Information
• Event Summary: XXXX at hardware path x/x.x.x: Device added to monitoring
• Problem Description: The device has been added to the set of devices being monitored by this monitor.
• Probable Cause / Recommended Action: The device was added to the system, 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 ” command to set the state of the device to UP.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence

 

Event 101

• Severity: Critical
• Event Summary: XXXX at hardware path x/xx/x.x.x: Device removed from monitoring
• Problem Description: The device has been removed from the list of devices being monitored by this monitor.
• Probable Cause / Recommended 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 using the “Check monitoring” command.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence

 

Event 103

• Severity: Information
• Event Summary: Test
• Problem Description: This is a test message from the monitor to test the communication path from the monitor to the notification mechanism.
• Probable Cause / Recommended Action: No action required.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence

 

Event 1001

• Severity: Critical
• Description: The FCP driver could not find the Fibre Channel Mass Storage Adapter in the HP-UX io_tree structure.
• Cause: An installation error has occurred.
• Action: Refer to the installation and troubleshooting sections of the “Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) to resolve the problem.

 

Event 1002

• Severity: Critical
• Description: A Fibre Channel device driver (FC SCSI MUX, FC Array, etc.) could not locate the associated Fibre Channel device within the HP-UX io_tree structure.
• Cause: An installation error has occurred.
• Action: Refer to the installation and troubleshooting sections of the “Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) to resolve the problem.

 

Event 1003

• Severity: Critical
• Description: A Fibre Channel device driver (FC SCSI MUX, FC Array, etc.) could not claim the associated Fibre Channel device within the HP -UX io_tree structure.
• Cause: An installation error has occurred.
• Action: Refer to the installation and troubleshooting sections of the “Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) to resolve the problem.

 

Event 1004

• Severity: Critical
• Description: An ioscan failed because the Fibre Channel Mass Storage Adapter is OFFLINE.
• Cause: The Fibre Channel Mass Storage Adapter is not connected in a supported topology. This error will occur if:
  1.The FCMS Adapter is malfunctioning.
  2. There is a failure in the fiber optic cable.
  3.The Fibre Channel topology is invalid.
• Action: Do the following:
  1. Verify that the Fiber Channel Mass Storage (FCMS) Adapter is functioning properly.
  2. Verify that the fiber optic cable is connected properly to the FCMS Adapter.
  3. Verify that all devices are ONLINE and actively participating in the loop or fabric.
  4. If no other devices are participating in the loop, verify that an optical port protector (p/n 1005-0359) is connected to the Fibre Channel Mass Storage Adapter.
  If problem persists, replace the Fibre Channel Mass Storage Adapter.

 

Event 1005

• Severity: Critical
• Description: Invalid port state for Fibre Channel Mass Storage Adapter
• Cause: The Fibre Channel driver is in an invalid operating state. This error indicates a Fibre Channel driver defect.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 1006

• Severity: Major Warning
• Description: Public loop not supported at this release.
• Cause: The currently installed Fibre Channel driver does not support a public Fibre Channel loop. You may have a switch in your topology.
• Action: Do the following:
  1. Disconnect the switch.
  2. Reconfigure the Fibre Channel loop.
  3. Close all applications.
  4. Reboot the system.

 

Event 1007

• Severity: Major Warning
• Description: Inquiry failed on FCP device.
• Cause: No satisfactory acknowledgement was received in response to an inquiry command issued to a Fibre Channel device. A Fibre Channel device may be OFFLINE or in a failure state.
• Action: Do the following:
  1. Check device panels to ensure that Fibre Channel devices are ONLINE.
  2. If all Fibre Channel devices are ONLINE, examine the log entries to detect internal device problems. If the problem persists, it may be required to isolate and replace faulty Fibre Channel devices.

 

Event 1008

• Severity: Major Warning
• Description: Invalid Logical Unit Number (LUN) format found.
• Cause: The LUN number returned in response to a “Report LUNs” command does not conform to the SCC standard.
• Action: Do either of the following: 1.Report the problem to the device manufacturer. It is likely that corrective action must be taken in the device firmware. 2.Locate the support manual for the problem device and follow the troubleshooting instructions provided. The device may need to be replaced.

 

Event 1009

• Severity: Major Warning
• Description: No valid Logical Unit Numbers (LUNs) found on array device.
• Cause: The host received an “invalid addressing mode” response to a “report LUNs” command. This error will occur under the following conditions:
  1.The device does not support the “report LUNs” command.
  2.The device sent invalid data in response to the command.
• Action: Do the following:
  1. Determine if the device supports the “report LUNs” command.
  2. Report the error to the device vendor.

 

Event 1010

• Severity: Critical
• Description: Module insertion table full.
• Cause: The Fibre Channel driver’s internal configuration table is full. The Fibre Channel driver is defective.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 1011

• Severity: Major Warning
• Description: Received a truncated LUN list. Calculated LUN list length: 1 bytes Maximum length for I/O transfer: 2 bytes
• Cause: The host received an incomplete LUN transfer from a device in response to a device query.
• Action: From the system prompt, issue an “ioscan -fn” command to reset the UNIX io_tree & Fibre Channel devices. If the problem persists, report the problem to the device manufacturer.

 

Event 1012

• Severity: Critical
• Description: Fibre Channel Inquiry data is less than 36 bytes.
• Cause: The host received inquiry data that was less than 36 bytes, in response to a device query.
• Action: From the system prompt, issue an “ioscan -fn” command to reset the UNIX io_tree and Fibre Channel devices. If the problem persists, report the problem to the device manufacturer.

 

Event 3002

• Severity: NOT AVAILABLE
• Description: Retrying BDR on a failure
• Cause: The device above failed to complete a reset command that the host issued.  
• Action: No action is required. The device will recover. The host will resume communication with the device. If this error occurs repeatedly and the Fibre Channel device does not recover, do the following:

      1. From the system prompt, issue an “ioscan -f” command to determine if device hardware is still present.

      2. From the system prompt, issue an “fcmsutil” command to check the link state.

      3. Verify that the fiber optic cables are functional and correctly attached to the device.

      4. Examine the device logs.

 

Event 4002

• Severity: Major Warning
• Description: A SCSI handshake timeout occurred.
• Cause: One of the following occurred:
  1.A “Fibre Channel link Event” (e.g., link state change, CRC errors)
  2.A SCSI card in the FC-SCSI MUX may be malfunctioning.
  3.A parallel SCSI target device may be malfunctioning.
• Action: Do the following:
  1. Verify that the Fibre Channel Mass Storage Adapter and any Fibre Channel hubs in the topology are functioning properly.
  2. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. If you are not using a fiber optic cable, verify that the optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  4. Check all parallel SCSI cables for tightness and proper installation.
  5. If the problem persists, replace the SCSI cables.
  6. If the problem persists after SCSI cable replacement, replace the SCSI interfaces on the FC-SCSI MUX and target devices. Refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance.

 

Event 4003

• Severity: Major Warning
• Description: SCSI Bus Parity Detected
• Cause: A parity error was detected on the bus.
• Action: Do the following:
  1. Verify that the Fibre Channel Mass Storage Adapter and any Fibre Channel hubs in the topology are functioning properly.
  2. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. If you are not using a fiber optic cable, verify that the optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  4. Check all parallel SCSI cables for tightness and proper installation.
  5. If the problem persists, replace the SCSI cables.
  6. If the problem persists after SCSI cable replacement, replace the SCSI interfaces on the FC-SCSI MUX and target devices. Refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance.

 

Event 4004

• Severity: Major Warning
• Description: SCSI bus data handshake error
• Cause: There is poor signal integrity due to failures in SCSI cables or SCSI interfaces on the FC-SCSI MUX or target SCSI devices.
• Action: Do the following:
  1. Verify that the Fibre Channel Mass Storage Adapter and any Fibre Channel hubs in the topology are functioning properly.
  2. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. If you are not using a fiber optic cable, verify that the optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  4. Check all parallel SCSI cables for tightness and proper installation.
  5. If the problem persists, replace the SCSI cables.
  6. If the problem persists after SCSI cable replacement, replace the SCSI interfaces on the FC-SCSI MUX and target devices. Refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance.

 

Event 4005

• Severity: Major Warning
• Description: Unexpected Bus Free Detected
• Cause: The FC-SCSI MUX detected an unexpected “bus free.” This error may indicate failures in SCSI cables or SCSI interfaces on the FC-SCSI MUX or target SCSI devices.
• Action: Do the following:
  1. Verify that the Fibre Channel Mass Storage Adapter and any Fibre Channel hubs in the topology are functioning properly.
  2. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. If you are not using a fiber optic cable, verify that the optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  4. Check all parallel SCSI cables for tightness and proper installation.
  5. If the problem persists, replace the SCSI cables.
  6. If the problem persists after SCSI cable replacement, replace the SCSI interfaces on the FC-SCSI MUX and target devices. Refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance.

 

Event 4006

• Severity: Minor Warning
• Description: FC-SCSI MUX retry required
• Cause: The following may have occurred:
  1.The FC-SCSI MUX detected Fibre Channel data errors.
  2.The FC-SCSI MUX experienced a heavy traffic load that delayed data transmission.
• Action: In either case, no action is required. All I/O operations will be retried and completed. If this error persists, do the following:
  1.Reduce the number of SCSI devices connected to each SCSI interface in the FC-SCSI MUX.
  2.Verify that all Fibre Channel connections on devices attached to the loop fabric are functional and attached to the loop.

 

Event 4007

• Severity: Information
• Description: Bus Reset Request Complete.
• Cause: A SCSI bus reset request has completed. An application or internal host error initiated the reset request.
• Action: No action is required.

 

Event 4008

• Severity: Information
• Description: Bus Device Reset Detected
• Cause: One of the following occurred:
  1.A SCSI bus device reset request has completed. An application or an internal host error initiated the reset request.
  2.Power was recently restored to the SCSI device indicated.
• Action: No action is required.

 

Event 4009

• Severity: Minor Warning
• Description: Bus Device Reset Request Complete
• Cause: A SCSI parity error occurred during a host write operation.
• Action: Normally, no action is required. If the problem persists, refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance

 

Event 4010

• Severity: Major Warning
• Description: Unsupported Protocol
• Cause: A SCSI target device used a protocol that the FC-SCSI MUX does not support. This error indicates a SCSI target device malfunction.
• Action: Do the following:
  1. Verify that the install scripts ran correctly on the host.
  2. Check the FC-SCSI MUX information log to verify that the latest firmware is installed.
  3. Verify that the SCSI and FC-SCSI MUX drivers are installed.
  4. Verify that the SCSI target device supports standard SCSI protocols. Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details

 

Event 4016

• Severity: Major Warning
• Description: Attach Failed – FC-SCSI MUX Inquiry Failed
• Cause: An inquiry to the FC-SCSI MUX device failed. This may indicate an internal FC-SCSI MUX problem.
• Action: Do the following:
  1. Run the FC-SCSI MUX diagnostics to ensure that the firmware is functioning correctly.
  2. Take any action that the diagnostics recommend.
  3. If the error persists, an update to the FC-SCSI MUX firmware may be required.

 

Event 4018

• Severity: Major Warning
• Description: Invalid task management response code.
• Cause: The host received an “invalid task management” error from the FC-SCSI MUX. Task management functions include aborts, bus-device resets, etc.
• Action: Do the following:
  1. Examine the FC-SCSI MUX internal log files.
  2. Run the FC-SCSI MUX diagnostic for further information.
  3. Take any action that FC-SCSI MUX diagnostic utility recommends.

 

Event 4019

• Severity: Minor Warning
• Description: Incomplete read transmission.
• Cause: The host detected a Fibre Channel link error resulting in incomplete data transmission.
• Action: Usually, the host will retry the request. No action is necessary. If the problem persists, do the following:
  1. Verify that the Fibre Channel Mass Storage Adapter and any Fibre Channel hubs in the topology are functioning properly.
  2. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. If you are not using a fiber optic cable, verify that the optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  4. Reboot the system.

 

Event 4020

• Severity: Minor Warning
• Description: Residue overflow of buffer
• Cause: This error may occur during normal operation.
• Action: No action is required. If the problem persists, refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance.

 

Event 4021

• Severity: Minor Warning
• Description: Write transmission overflow
• Cause: This error may occur during normal operation.
• Action: No action is required. If the problem persists, refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance.

     

Event 4022

• Severity: Minor Warning
• Description: Missing sense data
• Cause: The SCSI target device returned a failure message in response to the FC-SCSI MUX request for SCSI sense data.
• Action: This error may occur during normal operation. No action is required. The system will recover. If the problem persists, refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance.

      Do the following:

      1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.

      2. If you are not using a fiber optic cable, verify that the loopback cable (p/n 1005-0624) is functional and securely attached to the Fibre Channel Mass Storage Adapter.

      3. Check all parallel SCSI cables for tightness and proper installation.

      4. Check for presence and proper installation of SCSI bus terminator on the SCSI bus noted above.

      5. If the problem persists, replace the SCSI cables and SCSI bus terminators.

      6. If the problem persists after SCSI cable replacement, replace the SCSI    interfaces on the FC-SCSI MUX and target devices.

 

Event 4023

• Severity: Critical
• Description: Invalid SCSI request
• Cause: The Fibre Channel host issued an invalid command. This may be the result of a Fibre Channel driver defect.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 4024

• Severity: Minor Warning
• Description: FCP request aborted
• Cause: This error may occur during normal operation.
• Action: No action is required. The system will recover. If the problem persists, refer to the Troubleshooting sections of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) and the “Hewlett-Packard Fibre Channel Mass Storage Adapter Service and User Manual” (p/n A3636-96002) for assistance

      Do the following:

      1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.

      2. If you are not using a fiber optic cable, verify that the loopback cable (p/n          1005-0624) is functional and securely attached to the Fibre Channel Mass Storage Adapter.

      3. Check all parallel SCSI cables for tightness and proper installation.

      4. Check for presence and proper installation of SCSI bus terminator on the SCSI bus noted above.

      5. If the problem persists, replace the SCSI cables and SCSI bus terminators.

      6. If the problem persists after SCSI cable replacement, replace the SCSI    interfaces on the FC-SCSI MUX and target devices.

 

Event 4025

• Severity: Serious
• Description: Unknown MUX completion status.
• Cause: The host received an unknown status from the FC-SCSI MUX. This error may occur as a result of a Fibre Channel driver defect or an FC-SCSI MUX defect.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file.
  3. Examine FC-SCSI MUX information:
  a. Check the FC-SCSI MUX internal logs.
  b. Run the FC-SCSI MUX diagnostics. Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 4026

• Severity: Major Warning
• Description: Acknowledgment of Bus device reset reject.
• Cause: There is a serious problem in the FC-SCSI MUX hardware or firmware.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file
  3. Examine FC-SCSI MUX information:
  a. Check the FC-SCSI MUX internal logs.
  b. Run the FC-SCSI MUX diagnostics. Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 4027

• Severity: Major Warning
• Description: Bus reset failure
• Cause: There is a serious problem in the FC-SCSI MUX hardware or firmware.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file.
  3. Examine FC-SCSI MUX information:
  a. Check the FC-SCSI MUX internal logs.
  b. Run the FC-SCSI MUX diagnostics.
  Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 4028

• Severity: Major Warning
• Description: Bus device reset task management failed.
• Cause: There is a serious problem in the FC-SCSI MUX hardware or firmware.
• Action: Do the following and report the error to Hewlett-Packard:
  1.From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2.From the system prompt, type “what vmunix” and store the output in a file.
  3.Examine FC-SCSI MUX information:
  a. Check the FC-SCSI MUX internal logs.
  b. Run the FC-SCSI MUX diagnostics.
  Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 4029

• Severity: Minor Warning
• Description: Bus device reset task management aborted
• Cause: There may be a link problem.
• Action: No action is required. The application will retry communication during the recovery process. To obtain more detailed information, do the following:
  1.Check the FC-SCSI MUX internal logs.
  2.Run the FC-SCSI MUX diagnostics.

 

Event 4030

• Severity: Major Warning
• Description: Bus reset task management failed.
• Cause: There is a serious problem in the FC-SCSI MUX hardware or firmware.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file.
  3. Examine FC-SCSI MUX information:
  a. Check the FC-SCSI MUX internal logs.
  b. Run the FC-SCSI MUX diagnostics.
  Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 4031

• Severity: Minor Warning
• Description: Bus reset task management aborted.
• Cause: No action is required. The application will retry communication during the recovery process.
• Action: No action is required. The application will retry communication during the recovery process. To obtain more detailed information, do the following:
  1. Check the FC-SCSI MUX internal logs.
  2. Run the FC-SCSI MUX diagnostics. Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details.

 

Event 4241

• Severity: Major Warning
• Description: Fatal – Bytes received more than expected.
• Cause: There is a serious problem in the FC-SCSI MUX hardware or firmware.
• Action: Do the following and report the error to Hewlett-Packard:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file.
  3. Examine FC-SCSI MUX information:
  a. Check the FC-SCSI MUX internal logs.
  b. Run the FC-SCSI MUX diagnostics.
  Refer to the Troubleshooting section of the “Hewlett-Packard Fibre Channel SCSI Multiplexer Service and User Manual” (p/n A3308-90006) for details. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 5001

• Severity: Critical
• Description: Opt_parm not initialized. Bus = 0x7b
• Cause: An internal data structure was not initialized correctly. The Fibre Channel driver may be defective.
• Action: To report the error to Hewlett-Packard, do the following:
  1. From the console prompt, issue a command to obtain a system core dump. (Type “HE” to list of available commands.)
  2. From the system prompt, type “what vmunix” and store the output in a file. To obtain dump analysis assistance, report the error to the Hewlett-Packard support team (response center, escalation center, and WTEC) as appropriate.

 

Event 11001

• Severity: Critical
• Description: Fibre Channel Adapter received more data than expected. Inbound data overflow.
• Cause: The host system received more data than expected in response to a Fibre Channel command. There is a problem with the Fibre Channel device that sent the data.
• Action: Do the following and report the error to Hewlett-Packard:
  1.Locate the system core dump created during the system panic associated with this error.
  2.From the system prompt, type “what vmunix” and store the output in a file.
  3.Save the current MESA (STM) log file. The current MESA log is usually located at: /var/stm/logs/os/log1.raw.cur.
  4.Save the current system log file. The current system log file is usually located at: /var/adm/syslog/syslog.log.
  5.Save all log files internal to the Fibre Channel device participating in the error.

 

Event 13001

• Severity: Critical
• Description: Inbound data overflow Bus = 0x%x Target = 0x%x LUN = 0x%x
• Cause: The host received more than the expected amount of data in response to a Fibre Channel “read” request.
• Action: Do the following and report the error to Hewlett-Packard:
  1.Locate the system core dump created during the system panic associated with this error.
  2.From the system prompt, type “what vmunix” and store the output in a file. Save the current MESA (STM) 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.Save all log files internal to the Fibre Channel device participating in the error.

 

Event 15001

• Severity: Critical
• Description: Inbound data overflow Bus = 0x7b Target = 0x03 LUN = 0xa6
• Cause: The host received more than the expected amount of data in response to a Fibre Channel “read” request.
• Action: Do the following and report the error to Hewlett-Packard:
  1.Locate the system core dump created during the system panic associated with this error.
  2.From the system prompt, type “what vmunix” and store the output in a file.
  3.Save the current MESA (STM) log file. The current MESA log is usually located at: /var/stm/logs/os/log1.raw.cur.
  4.Save the current system log file. The current system log file is usually located at: /var/adm/syslog/syslog.log.
  5.Save all log files internal to the Fibre Channel device participating in the error.

 

Events on HP-UX 11i v3 Systems

The following events apply to systems running HP-UX 11i v3 only:

Event 35

• Severity: Critical
• Description: Fibre Channel Driver encountered a PCI Error and is now unusable.
• Cause: A PCI Error was detected by the driver and this interface is now unusable.  
• Action: The system will soon attempt to automatically repair it and resume normal operation No action required. Informative message.

 

Event 36

• Severity: Critical
• Description: Fibre Channel Driver has successfully recovered from a PCI Error

      and is now operational.

• Cause: The driver is being resumed as the system tries to recover from a PCI Error.
• Action: No action is required. Informative message

 

Event 37

• Severity: Critical
• Description: Fibre Channel Driver failed to recover from a PCI Error.
• Cause: Driver could not recover from a PCI Error   
• Action: Interface may be recovered using a Manual Error recovery operation Refer to olrad(1m) man page for details.

 

Event 38

• Severity: Critical
• Description: Fibre Channel Driver has received a request to remove this adapter.
• Cause: User has initiated a Fibre Channel Adapter remove request.
• Action: No action required. Information message only.

 

Event 39

• Severity: Critical
• Description: Fibre Channel Driver has successfully removed this adapter.
• Cause: User-initiated Fibre Channel Adapter remove request has succeeded. No action required. Information message only.
• Action: No action required. Information message only

 

Event 40

• Severity: Critical
• Description: Fibre Channel card has been successfully suspended
• Cause: The driver is being suspended as the system tries to recover from a PCI Error. The system is attempting to automatically repair this interface. If automatic repair fails, you would require to manually recover this interface by performing a Replace operation. Please refer to olrad(1M) for details.
• Action: No Action required. Informative message..

 

Event 41

• Severity: Information
• Description: Fibre Channel Driver received a Link Dead Notification.
• Cause: The Fibre Channel driver has declared the link to be dead because it has been down for more than 5 seconds.

Action: Please check the following:

1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.

2. Verify that the device which is connected to the adapter port is functioning correctly.

3. 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 the adapter is not functioning correctly contact the Hewlett Packard customer representative

 

Event 42

• Severity: Information
• Description: Looping for resources to reconnect to target nport ID  =  0x!
• Cause: The device state machine is thread is trying once per second to reallocate a SF thread in order to send a PLOGI frame to keep the device open.
• Action: If the message repeats, driver data structures are not being freed. check for a large number (>60) of targets on the loop or a large number of IO aborts which are not succeeding immediately

 

Event 43

• Severity: Information
• Description: Target rejected PLOGI                             
• Cause: The device at the loop address was unwilling to start a session with the card.
• Action: If the device at that address is another initiator, there is no problem.

Check that the device is powered and connected. Check that the protocol versions supported by the device cover at least part of the range from FC-PH 4.3 and FC-PH-3 and that the device supports class 3 operation.

 

Event 44

• Severity: Critical
• Description:   World wide name (unique identifier) for following device has changed.      
• Cause: Unlike paralled SCSI, Fibre Channel allows easy hot-swapping of disks Due to address conflicts it is possible for disks to swap loop IDs accidentally when re-plugging them into a hub.
• Action: In order to reduce the chance of user data corruption or file system panics, we normally require the world wide names for a particular device to stay the same. Using the scsimgr(1M) command’s replace_wwid or replace_leg_dsf options ensures that the replacement is intentional. The driver has detected a new “world-wide name” unique identifier at a loop position previously occupied by a device with a different identifier.

      If this is due to a deliberate replacement of the previous device, use the scsimgr(1M) command’s replace_wwid or replace_leg_dsf options to allow the new device to be used. If there has been no intentional replacing  of any devices, check for conflicts in address assignments of devices on the loop.

 

Event 45

• Severity: Information
• Description:   Target Rejected PRLI       
• Cause: The device with the reported Loop Identifier is not willing to be a SCSI target.
• Action: Verify that the device at the loop ID is another initiator. If the  device is supposed to be a target verify with the vendor that the  PRLI ACC payload reports it as a target.

 

Event 46

• Severity: Information
• Description:  Target rejected ADISC                             
• Cause: The target device rejected a request to verify its name and address after a loop initialization.
• Action: If a new device has been installed on the loop, check that its address setting does not conflict with that of any other device. If a device has been replaced on the loop, use the scsimgr(1M) command’s replace_wwid or replace_leg_dsf options to notify the driver to allow a different name at the previously used address.

 

Event 47

• Severity: Critical 
• Description:   Unable to access previously accessed target                             
• Cause: An attempt to re-open a device which had been opened earlier has failed.
• Action: There should be additional logging messages which will  allow diagnosis of the problem. 

 

Event 48

• Severity: Information
• Description:   Unable to reset target     
• Cause: A device was unable to execute a reset

      Status returns are:

      2 – device appears to have been removed

      3 – request timed out

      4 – link error while receiving FCP_RSP

• Action: Check that the device is powered and is accepting other commands.

 

Event 49

• Severity: Information
• Description:   Unable to reset target          
• Cause: Response code values as listed in FCP table 12     
• Action: Check device internal logs.

 

Event 50

• Severity: Information
• Description:   Target rejected TPRLO        
• Cause: The device was not able or willing to execute a Fibre Channel “third party process logout”.
• Action: If this device is being used in a Service Guard cluster, verify that the device is supported for use in clusters. check that the device is powered on and is accepting other commands. If the device is not part of cluster, this message can be ignored.

 

Event 51

• Severity: Information
• Description: ACC or LS_RJT frame in response to PLOGI is too short from device at nport id = 0x!.
• Cause: Response frame to request was truncated, probably by some transient failure.
• Action: No action required unless frequently repeated.

 

Event 52

• Severity: Information
• Description: Minimum version of FC-PH supported by device at nport Id 0x! is too high. It is 0x! and card supports upto 0x20.
• Cause: The device does not support any version of the Fibre Channel protocol supported by the card.                  
• Action:  If the device is a SCSI target which will be used by the host, it must be replaced.

 

Event 53

• Severity: Information
• Description: Maximum version of FC-PH supported by device at nport Id 0x! is too low It is 0x! and card needs at least 0x09.
• Cause: The device does not support any version of the Fibre Channel protocol supported by the card.                 
• Action: If the device is a SCSI target which will be used by the host, it  must be replaced.

 

Event 54

• Severity: Information
• Description: Can’t work with device at nport id 0x! It does not support  Class-3
• Cause: The device does not support “Class 3” Fibre Channel communication.
• Action: If the device is another host on the loop, or device which is not a SCSI target, no action is required. Otherwise, replace with a target which supports class 3 operation.

 

Event 55

• Severity: Information
• Description: ACC or LS_RJT response frame (to PRLI) from device at nport id 0x! is too short
• Cause: Response frame to request was truncated, probably by some transient failure. 
• Action: No action required unless frequently repeated.

 

Event 56

• Severity: Information
• Description: Unable to speak SCSI FCP with device at nport id 0x! because response code 0x!  is not one or five
• Cause: Device is not returning the response code we require. Either it is another initiator, or it has not been qualified for use with this driver.
• Action: If condition is not transient, and the device is supposed to be a target, verify that device is supported by HP or contact vendor. Check for address conflicts.

 

Event 57

• Severity: Information
• Description: Will not log in with device at nport id 0x! because it is not a target
• Cause: The device is unable to act as a SCSI target.
• Action:  The device is probably another initiator, in which case no action is required. This message will be seen in multi-initiator loops where the two hosts are probing each other’s ports.

 

Event 58

• Severity: Information
• Description: ACC or LS_RJT response frame (to ADISC) from device at  nport  id 0x! is too short
• Cause: Response frame to request was truncated, probably by some transient failure.
• Action: No action required unless frequently repeated

 

Event 59

• Severity: Critical
• Description: Address conflict encountered by device at nport id 0x!
• Cause: HA is the “hard address” (port ID), configured via a switch or console, that the device is trying to acquire. Our adapter cards themselves don’t have hard addresses. It appears that there are (or were) more than one device with the same address (loop ID) setting. One of them will be ignored.
• Action: Look for two (or more) devices on the loop which have the reported address setting. Change the address settings so that all devices on the loop have a unique addresses, or remove the overlapping devices.

      Even after you change the address settings on the devices, it may be necessary to reset or power-cycle both the devices whose settings have been changed, and any remaining device with the address setting which encountered the conflict.

 

Event 60

• Severity: Information 
• Description: Bad ADISC reply HA is 0x!  but n-port is 0x!
• Cause: It appears that there are (or were) more than one device with the same address (loop ID) setting. One of them will be ignored.
• Action: Look for two (or more) devices on the loop which have the reported address setting. Change the address settings so that all devices on the loop have a unique addresses, or remove the overlapping devices.

      Even after you change the address settings on the devices, it may be necessary to reset or power-cycle both the devices whose settings have been changed, and any remaining device with the address setting which encountered the conflict.

 

Event 61

• Severity: Critical
• Description:   Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
• Cause: The PLOGI or FLOGI response from the device or switch had a parse error. Parsing error could occur if the PLOGI/FLOGI response payload had an unexpected value. Parsing error occurs normally due to

–     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/syslog.log

 

Event 62

• Severity: Information
• Description: Received an unassisted FCP frame from port 0x! with originator exchange ID 0x!. The frame length ! bytes exceeds what is allowed by FC-PLDA      
• Cause: An unexpected SCSI FCP frame was received from the target device This may be a temporary condition caused by loop congestion.                  
• Action: Examine the Fibre Channel logs for the device reported for any problems. If the problem does not persist, no additional action is necessary. If the problem persists, contact your HP customer representative.

 

Event 63

• Severity: Serious
• Description: Received an unassisted FCP frame from port 0x!  for OX_ID 0x!

      The sest entry associated with the OX_ID is currently in use with another device   at port 0x!

• Cause: An unexpected SCSI FCP frame was received from a target device on an exchange that was in use with another device. This may be caused by incorrect loop configurations.
• Action: Examine the fibre channel loop and devices reported above. If the problem persists, contact your HP customer representative.

 

Event 64

• Severity: Serious
• Description: Received an unassisted FCP frame from port 0x!  with originator exchange ID 0x!  The expected originator exchange ID is 0x! 
• Cause: An FCP frame was received from a target device with unexpected OXID. This might indicate a device failure. 
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 65

• Severity: Serious
• Description: Received an FCP_XFER_RDY frame from port 0x! with originator exchange ID 0x! Unexpected value 0x!  for F_CTL in frame header
• Cause: FCP_XFER_RDY frame was received from the target device. This might indicate a device failure.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 66

• Severity: Serious
• Description: Received an invalid FCP_XFER_RDY frame from port 0x! with originator exchange id 0x! The exchange is currently used for read (cdb_flags 0x! )
• Cause: Received an FCP_XFER_RDY frame from target device with unexpected values in frame payload. This might indicate a device failure
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 67

• Severity: Serious
• Description: Received an invalid FCP_XFER_RDY frame from port 0x! DATA_RO field 0x! in FCP_XFER_RDY is not less than the transfer length 0x!
• Cause: Received an FCP_XFER_RDY frame from target device with unexpected values in frame payload. This might indicate a device failure.
• Action:.Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 68

• Severity: Serious
• Description: Received an invalid FCP_RSP frame from port 0x! with originator exchange ID 0x! The frame length bytes exceeds that is allowed by FC-PLDA
• Cause: An FCP_RSP frame was received from the target device exceeding the maximum supported length. This might indicate an unsupported device.
• Action: If the problem persists, contact your HP customer representative.

 

Event 69

• Severity: Serious
• Description: Received an invalid FCP_DATA frame from port 0x! with originator exchange ID 0x! The exchange is currently used for write operation
• Cause: Unexpected FCP_DATA frames received from the target device. This may be a temporary condition due to loop congestion.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 70

• Severity: Serious
• Description: Received an invalid FCP_CMND frame from port 0x! with originator exchange ID 0x! Incoming FCP target mode operations are not supported
• Cause: An unexpected FCP_CMND frame was received from the device. This indicates an incorrect behavior of the remote device.
• Action: Examine the remote device for incorrect function. If the problem persists, contact your HP customer representative

 Event 71

• Severity: Serious
• Description: Received an invalid FCP_CMND frame from port 0x! with unsupported category information 0x! 
• Cause: An unsupported FCP frame was received from the remote device. This indicates a non-PLDA compliant device.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative

 

Event 72

• Severity: Serious
• Description: Received Host Programming Error (HPE) in Outbound Completion Message (OCM) for an I/O to the device at port 0x! The index of sest entry used is ! 
• Cause: Remote device is requesting for more data than that was specified in the write request. This indicates an incorrectly behaving remote device.
• Action: Examine the remote device for possible errors. If the problem persists, contact your HP customer representative

 

Event 73

• Severity: Serious
• Description: Received Frame Time Out (FTO) error in Outbound, Completion Message (OCM) for an I/O to the device at port 0x! The index of sest entry used is !
• Cause: The remote device has stopped responding to I/O requests. Check the loop to see if the device is still operating on the loop.
• Action: Examine the fibre channel device logs for errors.

 

Event 74

• Severity: Serious
• Description: Received a late ABTS response from device at port 0x!, for the exchange with OX_ID 0x!.
• Cause: A late response to an I/O abort request was received. The response was ignored.
• Action: No further action is needed. Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

 

Event 75

• Severity: Serious
• Description: Overflow error while receiving FCP_RSP frame from target device at port 0x!
• Cause: An FCP_RSP frame was received from the target device exceeding the maximum supported length. This might indicate an unsupported device.
• Action: If the problem persists, contact your HP customer representative.  

 

Event 76

• Severity: Serious
• Description: Received FCP frames from device at port 0x!. Remote device is the originator for the exchange. OXID of the exchange is 0x!
• Cause: An FCP frame was received from the device with an incorrect exchange context. This indicates an incorrect behavior of the remote device
• Action: Examine the remote device for incorrect function If the problem persists, contact your HP customer representative 

 

Event 77

• Severity: Serious
• Description:  Received BA_RJT as response to ABTS from device at port 0x!     
• Cause: The attempt to abort an I/O was rejected. This might indicate a non-PLDA compliant device.
• Action:  Examine the reject reason code and fibre channel device logs for errors. If the problem persists, contact your HP customer representative.

           

Event 78

• Severity: Serious
• Description:   Received invalid response to ABTS from device at port 0x!.     
• Cause: Received an invalid response to an I/O abort request. This indicates an incorrect behavior of the remote device.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.  

 

Event 79

• Severity: Serious
• Description: Unexpected FCP_XFER_RDY from device at port 0x! OXID of the exchange was  0x!
• Cause: An unexpected FCP_XFER_RDY was received from the remote device. This might indicate a non-PLDA compliant device.
• Action: Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.  

 

Event 80

• Severity: Serious
• Description: Unexpected FCP_XFER_RDY from device at port 0x! OXID of the exchange was  0x!
• Cause: An unexpected FCP_RSP was received from the remote device. This might be a temporary condition caused by loop disturbance.
• Action: No further action may be needed. Examine the fibre channel device logs for errors. If the problem persists, contact your HP customer representative.  

 

Event 81

• Severity: Serious
• Description:   Unexpected event in link down state from target device at port 0x!        
• Cause: Driver has received an unexpected event for an I/O exchange with the remote device. This might indicate an incorrect remote device behavior or a driver problem.

        ·      Action: Report the problem to HP along with the details of remote device.