Oam Remote And Local Loopback Feature - Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual

Related Topics

OAM Remote and Local Loopback Feature

Copyright © 2010, Juniper Networks, Inc.
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.
OAM Feature Overview on page 230
OAM Messages on page 226
Configuring 802.3ah OAM Link-Fault Management on page 238
Monitoring OAM Link-Fault Management Sessions on All Configured Interfaces on
page 253
ethernet oam lfm remote-failure
show ethernet oam lfm summary
Remote loopback mode ensures link quality between the router and a remote peer during
installation or troubleshooting. JunosE Software can place a remote entity into loopback
mode (if remote loopback mode is supported by the remote entity). When you place a
remote entity into loopback mode, the interface receives the remote loopback request
and puts the interface into remote loopback mode. When the interface is in remote
loopback mode, all frames except OAM PDUs are looped back without any changes
made to the frames. OAM PDUs continue to be sent and processed.
A local OAM entity in active mode can start a remote loopback of its peer through a
Loopback Control OAM PDU that contains the option to enable loopback. During the
initiation phase, the local OAM entity discards any locally sourced non-OAM PDUs. When
the peer receives a loopback request, and assuming that it supports the service, it sets
the forwarding state to loop any received non-OAM PDUs; any locally generated non-OAM
PDUs are discarded while in loopback (Figure 32 on page 229). This forwarding state is
conveyed to the peer using an Information OAM PDU. When the Information OAM PDU
is received after loopback is disabled, the local OAM entity resumes transmission of
locally sourced non-OAM PDUs, in addition to OAM PDUs. You can prevent two active
mode OAM entities from simultaneously placing each other into loopback mode by
making sure that the lower valued source address is the entity that is placed in loopback
mode (Figure 32 on page 229).
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management
235