HP StorageWorks 2.140 Director Switch - Manual (Page 157)

Director Element Manager user guide 157
Each log entry contains:
• Date/Time—The date and time of the incident in yyyy/mm/dd format.
• 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 off line sequence.
For corrective actions in response to these link incident messages, see the diagnostics chapter in the
McDATA Intrepid Director 6064 Installation and Service Manual for the Director 2/64 and the
McDATA Intrepid Director 6140 Installation and Service Manual for the Director 2/140.
Threshold Alert Log
This log provides details of threshold alert notifications. Besides the date and time that the alert
occurred, the log also displays details about the alert as configured through the Configure Threshold
Alerts option under the Configure menu on the menu bar.
Figure 72 Threshold Alert log
• Date/Time—Date and time stamp for when the alert occurred.