6
6-10
Using Logs
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 of 12 errors in a 5-minute
window per port..
• 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.
Summary of Contents for Connectrix DS-32M2
Page 4: ...Connectrix DS 32M2 User Guide iv ...
Page 14: ...xiv Connectrix DS 32M2 User Guide Figures ...
Page 16: ...Connectrix DS 32M2 User Guide Tables xvi ...
Page 24: ...xxiv Connectrix DS 32M2 User Guide Warnings and Cautions ...
Page 42: ...1 1 18 Connectrix DS 32M2 User Guide Switch Operating Features ...
Page 72: ...3 3 24 Connectrix DS 32M2 User Guide Product Manager Overview ...
Page 226: ...B B 8 Connectrix DS 32M2 User Guide Configuring Network Addresses ...
Page 248: ...C C 22 Connectrix DS 32M2 User Guide Configuring the Switch from a Web Server ...
Page 332: ...F F 8 Connectrix DS 32M2 User Guide Customer Support ...
Page 351: ...Connectrix DS 32M2 User Guide g 19 Glossary ...
Page 352: ...g 20 Connectrix DS 32M2 User Guide Glossary ...