HP Surestore 64 fw 05.01.00 and sw 07.01.00 - Director Product Manager - User - Page 169
Link Incident Log, Link Incident Log
View all HP Surestore 64 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 169 highlights
Using Logs Link Incident Log The Link Incident Log displays the 1000 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 56: 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. Director Product Manager User Guide 169