Link Incident Log - HP StorageWorks 2/140 - Director Switch Product Manager Manual

Using Logs
— GXXR—G_Port, mixed mode, MT-RJ connector, 1 Gigabit
— GSMR—G_Port, short wave, multimode, MT-RJ connector, 1 Gigabit.
• Position—Slot position in the chassis relative to identical components installed.
• Action—Inserted or removed.
• Part Number—Part number of the component.
• Serial Number—Serial number of the component.

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 4–5: 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).
4–8 director product manager user guide