Juniper JUNOSE 11.2, Руководство по настройке

Страница: 274 / 772

event to disable an Ethernet OAM interface when a high threshold for an error is
exceeded, the link moves to the operational down status.
host1(config-if)# ethernet oam lfm high-threshold action failover
In this case, when the high threshold is exceeded for a local link error, a failover occurs
to the secondary link of the redundant port on GE-2 and GE-HDE line modules that
are paired with GE-2 SFP I/O modules.
7.
Configure the Ethernet OAM link-fault management functionality to detect failure
conditions that occurred at a remote peer and influence the state of the link based
on an Event Notification PDU received from the remote peer. You can also set the
action to be performed when a failure condition is observed in the link. If you enable
detection of faults that occurred at the remote peer, the local OAM entity monitors
unspecified critical event, unrecoverable error, and loss-of-signal conditions that
the remote peer notifies it using an Information OAM PDU with the Critical Event,
Dying Gasp, and Link Fault bits set in the Flags field.
host1(config-if)# ethernet oam lfm remote-failure critical-event action
disable-interface
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
Copyright © 2010, Juniper Networks, Inc. 242
JunosE 11.2.x Link Layer Configuration Guide