Filter
Top Products
4
Link Incident Log
4-9
Using Logs
• 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-signal occurs when 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.