Juniper JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010, Руководство по настройке

Страница: 271 / 774

Dying Gasp
This event type denotes that an unrecoverable condition, such as a power failure,
has taken place. This type of condition is vendor specific. A notification about the
condition might be sent immediately and continuously. If you configure this option,
the local OAM entity detects unrecoverable error conditions that occurred in the
receive path of the link. The local entity influences the state of the link based on an
Information OAM PDU with the Dying Gasp bit set in the Flags field that it receives
from the remote peer.
Critical Event
This event type indicates that an unspecified vendor-specific critical event has
occurred. A critical event might be sent immediately and continuously. If you
configure this option, the local OAM entity detects critical event error conditions that
occurred in the receive path of the link. The local entity influences the state of the
link based on an Information OAM PDU with the Critical Event bit set in the Flags
field that it receives from the remote peer.
You can specify the action to be taken by the system when the configured link-fault
event occurs, such as disabling the interface or failing over to the secondary port on
GE-2 and GE-HDE line modules that are paired with GE-2 SFP I/O modules with
physical link redundancy. You can also configure the OAM application to react to
event notifications received from the peer.
If a link fault is detected, any Information OAM PDUs sent with the Link Fault bit set
do not contain any TLV data. Any OAM PDU received with these flags set are
processed with priority by the router. Other link events, such as Errored Symbol
Period Event and Errored Frame Event, which result in threshold values being
exceeded are notified using TLVs in Event Notification PDUs.
In JUNOSe Software, you can configure the OAM application to monitor the receive
path of the link for quality and generate Event Notification PDUs to the remote peer.
You can also configure the OAM application to respond to event notifications received
from the peer.
Related Topics
■
OAM Feature Overview on page 234
■
OAM Messages on page 230
■
Configuring 802.3ah OAM Link-Fault Management on page 242
■
Monitoring OAM Link-Fault Management Sessions on All Configured Interfaces
on page 258
■
ethernet oam lfm remote-failure
■
show ethernet oam lfm summary
OAM Remote Fault Detection Feature
■ 239
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management