Link incident log, Figure 59 link incident log, 59 link incident log – HP StorageWorks 2.64 Director Switch User Manual
Page 132: Link, Incident log
Using logs
132
Link Incident log
The Link Incident Log displays the 1,000 most recent link incidents with the date the incident
occurred, the time it occurred, and the port on which the incident took place. The information is
useful to maintenance personnel for isolating port problems [particularly expansion port (E_Port)
segmentation problems] and repair verification.
Figure 59
Link Incident Log
Each log entry contains:
•
Date/Time—The date and time of the incident.
•
Port—The number of the port on which the incident occurred.
•
Link Incident—A short description of the incident. The following events may cause a link
incident to be written to the log.
• Implicit incident—The attached node detects a condition that may cause problems on the
link.
• Bit-error threshold exceeded—The number of code violation errors has exceeded threshold.
• Loss-of-signal or loss-of-synchronization. This occurs if a cable is unplugged from an
attached node. Loss-of-synchronization condition has persisted for longer than the resource
allocation time out value (R_A_TOV).
• Not-operational (NOS) primitive sequence received—A NOS was recognized.
• Primitive sequence timeout. Link reset protocol timeout occurred. Timeout occurred for an
appropriate response while in NOS receive state and after NOS is no longer recognized.
• Invalid primitive sequence received for the current link state—Either a link reset or a link
reset response primitive sequence was recognized while waiting for the offline sequence.
For corrective actions in response to these link incident messages, refer to the diagnostics chapter
in the HP StorageWorks Director 2/64 service manual for the Director 2/64 and the HP
StorageWorks Director 2/140 service manual for the Director 2/140.