Fibre Channel Adapters Monitor (Events)

Event 1

• Severity: Critical
• Description: Fibre Channel outbound completion error occurred during boot process.
  The Fibre Channel Driver received an outbound completion error on a frame sequence posted during the bootup process.
  Outbound completion error: 0x1
• Cause: Outbound DMA commands executed while transmitting loopback packets did not complete.
  There may be a cable problem.
• Action: Do the following:
  1. Verify that the fiber optic cable is functional and securely attached to Fibre Channel Mass Storage Adapter.
  2. 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 Fibre Channel Mass Storage Adapter.
  3. Reboot the system.
  If the problem persists after verifying the cabling, replace the adapter.

Event 2

• Severity: Critical
• Description: Fibre Channel outbound completion error occurred during loopback test.
  The Fibre Channel Driver received an outbound completion error on a frame sequence posted during a user-initiated loopback test.
  Outbound completion error: 0x1
• Cause: Outbound DMA commands executed during a user-initiated loopback test did not complete.
  There may be a cable problem.
• Action: 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 optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. After checking the cabling, repeat the 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 3

• Severity: Critical
• Description: Fibre Channel transmit parity error.
  The Fibre Channel Driver received an interrupt indicating a Transmit Parity Error. This error represents a serious failure in the Fibre Channel Mass Storage Adapter's operation.
• Cause: The Tachyon chip controlling Fibre Channel data transmission detected an internal data path parity error.
• Action: Reset the card using fcmsutil. Command syntax is as follows: /opt/fcms/bin/fcmsutil <device_file> reset clear
  If the problem persists, replace the adapter.

Event 4

• Severity: Critical
• Description: Failed to initialize Fibre Channel arbitrated loop. The Fibre Channel Driver has detected initialization problems in the Arbitrated Loop.
  Frame Manager Status register: 0x1
• Cause: Loop initialization errors are not supported in the current version of the fcT1 driver.
• 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 5

• Severity: Critical
• Description: Failure in Fibre Channel point-to-point configuration. The Fibre Channel Driver has detected initialization problems in a pt-pt configuration.
• Cause: Point
• to-point configurations are not supported in the current version of the fcT1 driver.
• 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 6

• Severity: Critical
• Description: The Fibre Channel Driver has detected a programming error at the following location:
  Line: 1
• Cause: The Tachyon chip controlling Fibre Channel data transfers detected one of the following errors:
  1. Invalid programming combination when transmitting the Outbound Data Buffer (ODB) or Extended Data Buffer EDB)
  2. Unsupported transmission class
  3. Conflicting parameters within an outbound data transfer request
• Action: In any of the above cases, 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 7

• Severity: Critical
• Description: The Fibre Channel Driver detected that a user-initiated loopback test has not completed within a reasonable amount of time.
• Cause: The user loopback timer is not supported in the current version of fcT1 driver.
• 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 8

• Severity: Critical
• Description: The Fibre Channel Driver detected that a loopback test failed to complete within a reasonable amount of time.
• Cause: The loopback test executed during the bootup process failed. There may be a cable problem. :
• Action: 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 optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. Reboot the system.
  If the problem persists, replace the adapter.

Event 9

• Severity: Critical
• Description: The Fibre Channel Driver detected a checksum error when executing a loopback test. Loopback tests occur when the Fibre Channel Mass Storage Adapter is reset and when the host system is booted.
• Cause: The loopback checksum error is not supported in the current version of fcT1 driver.
• 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 10

• Severity: Critical
• Description: The Fibre Channel Driver detected a LASER FAULT.
  Frame Manager Status Register: 0x1
• 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. 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.
  3. 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, replace the adapter.

Event 11

• Severity: Critical
• Description: The Fibre Channel Driver received an interrupt indicating a Link Failure.
  Frame Manager Status Register: 0x1
• 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. 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.
  3. After checking the cabling, reset the FCMS Adapter using fcmsutil. Command syntax is as follows:
     /opt/fcms/bin/fcmsutil <device_file> reset clear

Event 12

• Severity: Serious
• Description: The Fibre Channel Driver received a Basic Reject Link Service frame.
• Cause: This error may be seen during normal operation.
  It occurs when the Tachyon chip that controls Fibre Channel operation expects an "Accept" (ACC) frame from a device and does not receive one.
• Action: The Fibre Channel Mass Storage Adapter will recover. No intervention from the system administrator is required.

Event 13

• Severity: Serious
• Description: The Fibre Channel Driver received an Unsupported Basic Link Service frame. The frame was dropped.
• Cause: The following may cause this error:
  1. A device failed on the loop.
  2. A data frame was corrupted.
  3. The FCMS Adapter is trying to communicate with a device that does not support Fibre Channel.
• Action: It may be possible to see this error during normal operation. No intervention is required from the system administrator.

Event 14

• Severity: Serious
• Description: The Fibre Channel Driver received an "Accept" (ACC) frame in response to a Fibre Channel fabric login (FLOGI) request.
  This device is not in a Fibre Channel fabric configuration. Frame was dropped.
• Cause: Fabric connectivity is not supported in the current version of fcT1 driver.
• 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 15

• Severity: Serious
• Description: The Fibre Channel Driver received a message from the adapter indicating that an Inbound Class 1 Connection has been idle for too long. The driver executed a link reset operation.
• Cause: A class 1 connection is open and no frames have been received in the configured (ED_TOV) period of time.
  The current version of the fcT1 driver does not support class 1 service.
• 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 16

• Severity: Serious
• Description: The Fibre Channel Driver received NOS/OLS interrupt.
• Cause: The host believes it is in a different topology than the other fibre channel devices ( e.g., pt-pt vs. loop ).
  The following events may cause this interrupt to occur:
  1. Failed Loop Initialization (LIP).
  2. Resetting Fibre Channel Mass Storage host adapter... which may result in LIP failure.
  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.

Event 17

• Severity: Serious
• Description: The Fibre Channel Driver received a Link Down interrupt.
• Cause: Link Down errors may occur under normal operation.
• Action: No action is required. The system will recover.

Event 18

• Severity: Serious
• Description: The Fibre Channel Driver received an interrupt indicating CREDIT ERROR while the chip was operating as an N_Port. The driver executed a Link Reset command.
• Cause: The Tachyon chip controlling Fibre Channel operation is connected to an N_Port that has not returned BB_Credit within the configured period of time (ED_TOV).
• Action: No action is required. The chip will perform a reset and recover.

Event 19

• Severity: Serious
• Description: The Fibre Channel Driver received an interrupt indicating CREDIT ERROR while the chip was operating as an NL_Port. The driver did NOT execute a Link Reset command.
• Cause: The Tachyon 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 chip will perform a reset and recover.

Event 20

• Severity: Serious
• Description: The Fibre Channel Driver received a Fabric Reject (F_RJT) frame in response to a Fabric Login (FLOGI) frame.
  The source of the error is something other than "Class Not Supported."
• Cause: Fabric connectivity is not supported in the current version of fcT1 driver.
• 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 21

• Severity: Serious
• Description: The Fibre Channel Driver received an interrupt indicating an Elastic Store Error.
• Cause: The Tachyon 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
• Action: The Tachyon chip will recover without intervention.
  Preventive Information:
  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. 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.
  3. After checking the cabling, execute a loopback test on the FCMS Adapter using fcmsutil. Command syntax is as follows:
     /opt/fcms/bin/fcmsutil <device_file> lb plm
  If the problem persists, replace the adapter.

Event 22

• Severity: Serious
• Description: The Fibre Channel Driver received a duplicate outbound completion message.
• Cause: The current version of fcT1 driver does not support duplicate outbound completion messages.
• 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 23

• Severity: Serious
• Description: The Fibre Channel Driver received a Fabric Reject (F_RJT) frame in response to an invalid Source ID.
• Cause: The frame's destination address does not match the N_Port ID that the fabric assigned.
• 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 24

• Severity: Major Warning
• Description: The Fibre Channel Driver received an IMQ FULL message from the adapter.
• Cause: Fibre Channel packets are arriving faster than the Tachyon chip can chip can process them.
• Action: This error may occur during normal operation. No action is required.

Event 25

• Severity: Major Warning
• Description: The Fibre Channel Driver received an interrupt indicating a Loop State Machine Timeout.
• Cause: The Tachyon 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 chip will recover and resume operation.
  If the error persists, 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 26

• Severity: Major Warning
• 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: No action is required. The system will recover.

Event 27

• Severity: Major Warning
• Description: The Fibre Channel Driver received an interrupt indicating that loop initialization could not be completed successfully and the port is not participating in the loop.
• Cause: A cable or hardware problem exists.
• Action: 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 optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. 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 28

• Severity: Major Warning
• Description: The Fibre Channel Driver has detected that a Class 2 SEQ_ID is not available.
• Cause: The transmitting device exceeded the number of packets it was allowed to transmit (SEQ_ID). The current fcT1 driver does not support Class 2 service.
• 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 29

• Severity: Major Warning
• Description: The Fibre Channel Driver detected an internal error sending an unknown Basic Link Service frame.
• Cause: This error may occasionally occur under normal operation. Causes may include a corrupt frame, failed device, or bad optical connection.
• Action: The system will recover. There is no need to take action.
  Preventive Information: The following steps will verify the fiber optic cable:
  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 optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. After checking the cabling, execute a loopback test using fcmsutil. Command syntax is as follows:
     /opt/fcms/bin/fcmsutil <device_file> lb plm
  If this error persists, do the following and contact the Hewlett-Packard support team:
  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 (i.e., response center, escalation center, and WTEC ) as appropriate.

Event 30

• Severity: Major Warning
• Description: The Fibre Channel Driver detected an invalid Login State.
• Cause: The current version of fcT1 driver does not support this message.
• 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 31

• Severity: Major Warning
• Description: The Fibre Channel Driver detected an internal error when trying to send an unknown Extended Link Service frame.
• Cause: This error may occasionally occur under normal operation. Causes may include a corrupt frame, failed device, or bad optical connection.
• Action: The system will recover. There is no need to take action.
  Preventive Information: The following steps will verify the fiber optic cable:
  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 optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  3. After checking the cabling, execute a loopback test using fcmsutil. Command syntax is as follows:
     /opt/fcms/bin/fcmsutil <device_file> lb plm
  If this error persists, do the following and contact the Hewlett-Packard support team:
  
  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 (i.e., response center, escalation center, and WTEC ) as appropriate.

Event 32

• Severity: Major Warning
• Description: The Fibre Channel Driver received a Link Up interrupt.
• Cause: Link Down errors may occur under normal operation. This message indicates that the link has recovered.
  The current version of the fcT1 driver does not support the link up message.
• 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 33

• Severity: Information
• Description: The Fibre Channel Driver is unable to send an Extended Link Service frame.
• Cause: A link failure or insufficient system resources may cause this error.
• Action: No action is required. The system will recover.
  Preventive Information: Reset the adapter using the following command:
  /opt/fcms/bin/fcmsutil <device_file> reset clear

Event 34

• Severity: Information
• Description: The Fibre Channel Driver is unable to send a Basic Link Service frame.
• Cause: A link failure or insufficient system resources may cause this error.
• Action: No action is required. The system will recover.
  Preventive Information: Reset the adapter using the following command:
  /opt/fcms/bin/fcmsutil <device_file> reset clear

Event 35

• Severity: Information
• Description: The Fibre Channel Driver received a frame for an invalid FC4 type.
• Cause: The current version of fcT1 driver does not support this message.
• 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 36

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating that an OPEN was sent to an ALPA of 0x1 that did not respond.
• Cause: You will observe this behavior during normal operation.
• Action: No action is required.

Event 37

• Severity: Information
• Description: The Fibre Channel Driver has detected that the Outbound Sequence Manager of the Tachyon chip is in a frozen state.
• Cause: Occasionally, you may see this error during normal operation.
• Action: The Tachyon chip will recover. No action is required.
  Preventive Information: Reset the Fibre Channel Mass Storage Adapter using the following command:
  /opt/fcms/bin/fcmsutil <device_file> reset clear.

Event 38

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating that data transmission is OUT OF SYNCHRONIZATION.
• Cause: Problems with optical transmitter and link connection usually cause this error.
• Action: The system will recover. No action is required.
  Preventive Information: Reset the adapter using the following command:
  /opt/fcms/bin/fcmsutil <device_file> reset clear.

Event 39

• Severity: Information
• Description: The Fibre Channel Driver received an interrupt indicating LOSS OF SIGNAL.
• 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: Usually, the system will recover on its own.
  Preventive Information: Reset the Fibre Channel Mass Storage Adapter using the following command:
  /opt/fcms/bin/fcmsutil <device_file> reset clear

Event 40

• Severity: Serious
• Description: The SCSI host system received an inbound SCSI data completion message that should only be sent to SCSI target devices.
• Cause: A firmware failure occurred in device sending this message.
• Action: Report the problem to the device manufacturer. It is likely that corrective action must be taken in the device firmware.

Event 41

• Severity: Critical
• Description: Fibre channel Adapter has been disabled
  
• Cause: The Fibre Channel adapter has been made off-line due to user request from fcmsutil
  
• Action: Re-enable the adapter using the following fcmsutil command
  /opt/fcms/bin/fcmsutil <device file> enable
  

Event 42

• Severity: Information
• Description: Fibre channel Adapter enabled
• Cause: The fibre Channel adapter has been made on-line due to user request from fcmsutil
• Action: No action required. Informative message.

Event 100

• Severity: Information
• Event Summary: XXXX at hardware path x/x.x.x : Device added to monitoring
• Event Class: -
• 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_fix ed -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: Disk at hardware path x/xx/x.x.x : Device removed from monitoring
• Event Class: I/O
• 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 102

• Severity: Information
• Event Summary: XXXX at hardware path x/x.x.x : Device added to monitoring
• Event Class: -
• 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_fix ed -L" command), use the "/etc/opt/resmon/lbin/set_fixed -n <RESOURCE_NAME>" command to set the state of the device to UP.
• Automated Recovery: None
• Event Generation Threshold: 1 occurrence <RESOURCE_NAME>

Event 103

• Severity: Information
• Event Summary: Test event
• Event Class: -
• 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 OFF-LINE.
• 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 ON-LINE 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 the 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 acknowledgment was received in response to an inquiry command issued to a Fibre Channel device.
  A Fibre Channel device may be OFF-LINE or in a failure state.
• Action: Do the following:
  1. Check device panels to ensure that Fibre Channel devices are ON-LINE.
  2. If all Fibre Channel devices are ON-LINE, 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 2001

• Severity: Information
• Description: Device N_Port ID was changed.
• Cause: The N_Port connected to the Fibre Channel Mass Storage Adapter was replaced with another N_Port. Some I/O requests may fail during transition.
• Action: No action is necessary. The system will recover.

Event 2002

• Severity: Serious
• Description: A topology change was detected.
• Cause: A topology change was detected. Open devices operating in the old topology have delayed transition to the new topology. Topology changes are not supported while devices are communicating.
  The topology will be switched as soon as all opened devices are closed.
• Action: Do the following:
  1. Close applications that issued I/O requests in the previous topology.
  2. From the system console, issue an "ioscan -fn" command.
  The system will recover when applications begin running.

Event 2003

• Severity: Information
• Description: Detected Fabric change.
• Cause: The Fabric connected to the Fibre Channel Mass Storage Adapter was replaced with another Fabric. Some I/O requests may fail during transition.
• Action: No action is necessary. The system will recover.

Event 2004

• Severity: Minor Warning
• Description: Host N_Port ID was changed.
• Cause:
  1. New devices were added to the loop while powered on.
  2. New hosts were added to the loop while powered on.
  In either case, I/O requests may fail during the loop transition.
• Action: No action is necessary. The system will recover.
  Preventive Information: To prevent this error in the future, do the following:
  • When adding new devices:
    1. Power off the new devices.
    2. Add the new devices to the loop.
    3. Power on the new devices.
  • When adding new hosts:
    1. Power off the new hosts.
    2. Add the new hosts to the loop.
    3. Reboot the new hosts.

Event 2005

• Severity: Serious
• Description: Link was down for more than 5 second(s).
• Cause: The following may cause the problem:
  1. Disconnected cable
  2. A Fibre Channel device is either OFFLINE or in SELF-TEST mode.
• Action: Do the following:
  
  1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
     
  2. If no fiber optic cable is attached to the Fibre Channel Mass Storage Adapter, verify that the optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.

Event 2006

• Severity: Minor Warning
• Description: A card reset request was received.
• Cause: Resets will occur as a normal part of operation.
• Action: No action is required unless the error is persistent.
  If the error is persistent, do the following:
  1. Verify that the fiber optic cable is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  2. If no fiber optic cable is attached to the Fibre Channel Mass Storage Adapter, verify that the optical port protector (p/n 1005-0359) is functional and securely attached to the Fibre Channel Mass Storage Adapter.
  If the steps above do not resolve the problem, you may need to replace the adapter.

Event 2008

• Severity: Minor Warning
• Description: Received this frame in response to PRLI to N_Port ID.
• Cause: Received this frame in response to PRLI to N_Port ID.
• Action: If the error occurs occasionally, no action is required.
  If the error persists, do the following:
  1. Verify that the device is running a version of firmware that is compatible with the Fibre Channel driver.
  2. Verify that the Fibre Channel driver supports the device listed above.

Event 2009

• Severity: Major Warning
• Description: Received ON-LINE message without receiving OFFLINE message.
• Cause: Received ON-LINE message without receiving OFFLINE message.
• Action: If devices connected to the Fibre Channel Mass Storage Adapter do not generate frequent I/O errors, no action is required.
  If I/O errors occur frequently, issue the following command from the system prompt.
  /opt/fcms/bin/fcmsutil < fcT1_cntl device file > reset
  This command will reset the Fibre Channel Mass Storage Adapter.

Event 2010

• Severity: Information
• Description: Switching topology.
• Cause: A topology transition has occurred.
  Old topology: Fabric New topology: Private Loop
• Action: No action is required.

Event 2011

• Severity: Minor Warning
• Description: SEST map_contiguous failure
• Cause: Failed to allocate and map SEST table into driver memory. The system will recover. Performance will be impaired.
• Action: No action is required unless performance level is unacceptable.
  Performance Note: A minimal SEST allocation will be attempted. This will limit the number of I/O requests that can be simultaneously active on the Fibre Channel Mass Storage Adapter.
  To improve system performance, increase the SEST table size as follows:
  Use the System Administration Management (SAM) utility to increase the "max_fcp_reqs" system parameter. The SAM utility will rebuild the kernel and reboot the system after modifications are complete.

Event 2013

• Severity: Minor Warning
• Description: Non-aligned SEST mapping
• Cause: Failed to acquire mapping for the SEST table in Fibre Channel driver memory. The Fibre Channel chip's alignment requirements have not been met. Performance will be affected.
• Action: No action is required unless performance level is unacceptable.
  Performance Note: A minimal SEST allocation will be attempted. This will limit the number of I/O requests that can be simultaneously active on the Fibre Channel Mass Storage adapter.
  If you wish to improve system performance, increase the SEST table size as follows:
  Use the System Administration Management (SAM) utility to increase the "max_fcp_reqs" system parameter. The SAM utility will rebuild the kernel and reboot the system after modifications are complete.

Event 2014

• Severity: Minor Warning
• Description: Minimal SEST allocated - performance may be degraded.
• Cause: Minimal SEST allocation has been completed.
• Action: No action is required.
  Performance Note: To improve system performance, increase the SEST table size as follows:
  Use the System Administration Management (SAM) utility to increase the "max_fcp_reqs" system parameter. The SAM utility will rebuild the kernel and reboot the system after modifications are complete.

Event 2015

• Severity: Minor Warning
• Description: SEST depleted - performance may be degraded.
• Cause: The Fibre Channel driver's SEST table is depleted. This may cause performance degradation.
• Action: No action is required unless performance level is unacceptable.
  Performance Note: To improve system performance, increase the SEST table size as follows:
  Use the System Administration Management (SAM) utility to increase the "max_fcp_reqs" system parameter. The SAM utility will rebuild the kernel and reboot the system after modifications are complete.

Event 2016

• Severity: Serious
• Description: SEST allocation failed.
• Cause: The Fibre Channel chip's SEST initialization failed.
• Action: Do the following:
  1. Increase system memory.
  2. Use the System Administration Management (SAM) utility to increase the "max_fcp_reqs" system parameter. The SAM utility will rebuild the kernel and reboot the system after modifications are complete.

Event 2017

• Severity: Information
• Description: Non-assisted exchange-ID (OX-ID) allocation failed.
• Cause: This error will occasionally occur during normal operation.
• Action: No action is required.

Event 2018

• Severity: Major Warning
• Description: Open failure: There are Link/Fibre Channel topology problems.
• Cause: If this error occurs during an ioscan operation, no action is required. It may occur due to a transient link down condition.
  If this error is persistent, it may indicate a link failure or topology transition problem.
• Action: Do the following:
  1. Verify that the fiber optic cable connected to the device is functional.
  2. Verify that Fibre Channel devices are ON-LINE and working properly.
  3. Examine the log files of the Fibre Channel device listed above. If a topology change is in progress or has recently occurred, do the following:
     1. Close all the applications that are accessing devices in the old topology.
     2. From the system prompt, type the "ioscan -fn" command to verify that all devices are available in the new topology.
     3. Restart the applications.

Event 2019

• Severity: Critical
• Description: A close command issued to the device below, failed because of active requests.
• Cause: The Fibre Channel driver was not able to disconnect from a device because several outstanding requests were in the transmission queue.
  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 (i.e., response center, escalation center, and WTEC ) as appropriate.

Event 2020

• Severity: Minor Warning
• Description: Received an unknown or unexpected frame.
• Cause: Information was received unexpectedly.
• Action: This error does NOT indicate a failure.
  To investigate, do the following:
  1. Examine Fibre Channel device logs for unexpected errors and events.
  2. Take corrective actions as described in the device logs.

Event 2021

• Severity: Major Warning
• Description: Failed to authenticate N-port.
  N-Port ID = 0x00000001
• Cause: Failed to authenticate the N-port shown below after loop initialization protocol. Probably a new N-port has been added to the loop.
  N-Port ID = 0x00000001
  The device associated with the N-port ID has disappeared from the loop. Possible causes include:
  1. A change in N-port ID
  2. The Fibre Channel device disconnected from the host.
  3. The Fibre Channel device is no longer in the loop.
• Action: Do the following:
  1. Make sure all Fibre Channel devices have unique hard addresses.
  2. Verify that the device is powered on.

Event 2022

• Severity: Information
• Description: The driver got a request to do a third party process logout. All the N-ports logged in to the remote N-port shown below are going to be logged out.
  N_Port ID = 0x00000001
• Cause: An application issued a Bus Device Reset (BDR) command.
• Action: No action required.

Event 2023

• Severity: Major Warning
• Description: The driver received a LS_RJT for RRQ, hence the device is going to be logged out. All active I/Os will be terminated.
• Cause: The host issued an I/O abort command that the Fibre Channel device rejected.
• Action: Do the following: Examine all Fibre Channel device logs for any sign of trouble. If no error entries are discovered, no further action is required.

Event 2024

• Severity: Major Warning
• Description: ABTS failed on an exchange. The device is going to be logged out. All active I/Os will be terminated.
• Cause: The host issued an I/O abort command that the Fibre Channel device rejected.
• Action: Do the following: Examine all Fibre Channel device logs for any sign of trouble. If no error entries are discovered, no further action is required.

Event 2025

• Severity: Information
• Description: Logging out due to an error. All active I/Os will be terminated.
• Cause: The Fibre Channel host detected one of the following errors:
  1. The device shown above did not respond to a Fibre Channel command.
  2. The device shown above disconnected from the host.
  As a result, the host will log out of the current connection and attempt to login again.
• Action: No action is required.

Event 2026

• Severity: Critical
• Description: Open failure: There is no valid login block.
• Cause: 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 2027

• Severity: Critical
• Description: Open failure: Fibre Channel driver is not ready.
• Cause: 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 2028

• Severity: Serious
• Description: Open failure: A link failure occurred.
• Cause: The link has been down for more than 5 seconds.
• Action: Do the following:
  1. Verify that the fiber optic cable connected to the device is functional.
  2. Verify that Fibre Channel devices are ON-LINE and working properly.
  3. 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 the error persists, 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 2029

• Severity: Critical
• Description: Open failure: incomplete port Authentication and DISCovery (ADISC)
• Cause: 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 2030

• Severity: Major Warning
• Description: Open failure: failed port Authentication and DISCovery (ADISC).
• Cause: The device associated with the N-port ID has either:
  • Rejected the authentication command issued from the host
  • Been removed from the loop
• Action: If this error rarely occurs, no action is required. It may indicate a transient condition that will correct itself.
  If this error occurs in repetitive patterns, power-cycle the target device indicated in the N_Port ID.
  If the problem persists beyond the power-cycle, 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 2031

• Severity: Major Warning
• Description: Open failure: PRocess LogIn (PRLI) timed out
• Cause: The target device shown above did not respond to the PRLI request for one of the following reasons:
  1. The target device did not receive the frame.
  2. For some internal reason, the target device chose not to respond.
• Action: If this error rarely occurs, no action is required. It may indicate a transient condition that will correct itself.
  If this error occurs in repetitive patterns, power-cycle the target device indicated in the N_Port ID above.
  If this error persists beyond the power-cycle, 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 2032

• Severity: Critical
• Description: Open failure: incomplete PRocess LogIn (PRLI).
• Cause: The Fibre Channel device shown is defective.
• Action: Do the following and report the error to the device manufacturer:
  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 2033

• Severity: Major Warning
• Description: Open failure: failed PRocess LogIn (PRLI)
• Cause: One of the following events caused the PRocess LogIn (PRLI) to fail:
  1. The target device rejected the PRLI request.
  2. The target device accepted the PRLI but replied with more data than the host expected.
• Action: If this error rarely occurs, no action is required. It may indicate a transient condition that will correct itself.
  If this error occurs in repetitive patterns, power-cycle the target device indicated in the N_Port ID above.
  If this error persists beyond the power-cycle, 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 2034

• Severity: Major Warning
• Description: The device shown above sent information to the host using the incorrect Originator eXchange IDentifier (OXID) shown below.
  Incorrect OXID = 0x0
  N_Port ID = 0x1
• Cause: Unexpected behavior in target device caused this error. The host will not be affected.
• Action: If the error persists, 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. Obtain the following information from the failing device shown above:
     1. Manufacturer name
     2. Firmware revision
     3. All internal log information
     4. All target device configuration information

Event 2035

• Severity: MINOR_WARNING
• Description: The device shown below sent a frame to the host before the N_Port was verified in an ADISC operation. N_Port ID = xx
• Cause: The firmware contained in the device associated with the N_Port above MAY contain firmware that violates the Fibre Channel protocol standard.
• Action: If the error persists, 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. Obtain the following information from the failing device shown above:
     1. Manufacturer name
     2. Firmware revision
     3. All internal log information
     4. All target device configuration information

Event 3001

• 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 3002

• Severity: Minor Warning
• Description: Retrying Fibre Channel Bus Device Reset . Retrying BDR on a failure
  Bus = 0x7b Target = 0x03 LUN = 0xa6 Retry count = 0x2c
• 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 time-out 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 shown above.
• 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.

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.

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: RCP request aborted
• Cause: This error may occur during normal operation.
• Action: No action is required. The system will recover.

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:
     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.
  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:
     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.
  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:
     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.
  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:
     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.
  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:
     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.
  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:
     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.
  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 100000-1nnnnn

Events 100000-1nnnnn are default SCSI Events. All are asynchronous. For a list of these events, see:

• New List of SCSI Events (June 2000 and later versions of diagnostics)
• Old List of SCSI Events (Feb 1999 - March 2000 versions of diagnostics)

/ Diagnostics HOME