Juniper JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010, Configuration Manual

Page: 279 / 774

host1(config-if)# ethernet oam lfm remote-failure dying-gasp action
disable-interface
host1(config-if)# ethernet oam lfm remote-failure link-fault action disable-interface
The operational status of the interface is set to down when an OAM PDU is
received from the remote peer by the local OAM entity to signal fault conditions
at the remote entity.
8.
Set an interface into loopback mode to enable the current Ethernet OAM
configuration for the interface of the local OAM entity to allow initiation of remote
loopback operation or to respond to a remote loopback request from a peer.
host1(config-if)# ethernet oam lfm remote-loopback supported
NOTE: You must configure the interface of the local OAM entity to be placed in
remote loopback mode and respond to loopback requests from the remote peer by
using the
ethernet oam lfm remote-loopback supported command before you
enable the remote peer to loop back PDUs by using the start or stop keywords with
the ethernet oam lfm remote-loopback command in Privileged Exec mode.
Otherwise, a warning message is displayed prompting you to configure the interface
of the local OAM entity to be placed in remote loopback mode.
Also, the remote peer can place the local OAM entity in loopback mode only if you
configured the
ethernet oam lfm remote-loopback supported command on the
local entity to enable remote loopback functionality on the local entity.
9.
Configure the local OAM entity to instruct the remote peer at the specified
interface to start looping back the non-OAM PDUs that it receives from the local
OAM entity or to stop the resending of such received non-OAM PDUs from the
local entity.
a. Enable the remote loopback operation on a remote OAM entity, which causes
the remote entity at the specified Gigabit Ethernet interface to loop any
received non-OAM PDUs back to the local entity.
host1# ethernet oam lfm remote-loopback start interface gigabitEthernet
1/0
This configuration setting is not preserved across a reboot. The setting that
you configured on the local OAM entity to start or stop the loopback operation
on the remote peer is not available after a warm or cold restart of the router,
because the router does not store the secure logs in NVS.
NOTE: If you attempt to enable the loopback operation on a remote OAM entity by
entering the ethernet oam lfm remote-loopback start command, an error message
is displayed if the remote entity is not configured for loopback behavior and if the
interface of the local entity is not placed into loopback mode (to send and receive
loopback PDUs).
Configuring 802.3ah OAM Link-Fault Management
■ 247
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management