Alcatel-Lucent 7750 Configuration Manual page 157

•
•
•
•
•
•
By default, the Event Notification OAMPDU is generated by the network element detecting the
signal failure event. The Event Notification OAMPDU is sent only when the initial frame event
occurs. No Event Notification OAMPDU is sent when the conditions clears. A port that has been
operationally affected as a result of a Link Monitoring frame error event must be recovered
manually. The typical recovery method is to shutdown the port and no shutdown the port. This
will clear all events on the port. Any function that affects the port state, physical fiber pull, soft or
hard reset functions, protocol restarts, etc will also clear the all local and remote events on the
affected node experiencing the operation. None of these frame errors recovery actions will cause
the generation of the Event Notification OAMPDU. If the chosen recovery action is not otherwise
recognized by the peer and the Information OAMPDU Flag fields have not been configured to
maintain the current event state, there is a high probability that the ports will have different
forwarding states, notwithstanding any higher level protocol verification that may be in place.
A burst of between one and five Event Notification OAMPDU packets may be sent. By default,
only a single Event Notification OAMPDU is generated, but this value can be changed under the
local-sf-action context. An Event Notification OAMPDU will only be processed if the peer had
previously advertised the EV capability. The EV capability is an indication the remote peer
supports link monitoring and may send the Event Notification OAMPDU.
The network element receiving the Event Notification OAMPDU will use the values contained in
the Link event TLVs to determine if the remote node has exceeded the failure threshold. The
locally configured action will determine how and if the local port is affected. By default,
processing of the Event Notification OAMPDU is log only and does not affect the port state. By
default, processing of the Information OAMPDU Flag fields is port affecting. When Event
Notification OAMPDU has been configured as port affecting on the receiving node, action is only
taken when errors are equal to or above the threshold and the threshold value is not zero. No action
is taken when the errors value is less than the threshold or the threshold is zero.
Symbol error, errored-symbols, monitoring is also supported but requires specific hardware
revisions and the appropriate code release. The symbol monitor differs from than the frame error
monitors. Symbols represent a constant load on the Ethernet wire whether service frames are
present or not. This means the optional signal degrade threshold sd-threshold has an additional
purpose when configured as part of the symbol error monitor. When the signal degrade threshold
7750 SR Interface Configuration Guide
Sequence Number: The unique identification indicating a new event.
Window: The size of the unique measurement period for the error type. The window is
only checked at the end. There is not mid-window checking.
Threshold: The value of the configured sf-threshold
Errors: The errors counted in that specific window
Error Running Total: The number of errors accumulated for that event type since
monitoring started and the protocol and port have been operational or a reset function has
occurred
Event Running Total: The number of events accumulated for that event type since the
monitoring started and the protocol and port have been operational
Interface Configuration
Page 157