Alcatel-Lucent 6850-48 Guida Di Rete

Pagina di 1162
Configuring EFM (LINK OAM)
Configuring LINK OAM
OmniSwitch AOS Release 6 Network Configuration Guide
September 2009
page 16-9
Configuring LINK OAM 
This section describes how to use Alcatel-Lucent’s Command Line Interface (CLI) commands to config-
ure LINK OAM on a switch.
Enabling and Disabling LINK OAM
 should be used to enable LINK OAM globally. By default, LINK OAM is disabled on the 
switch. The 
 command can be used to enable or disable the LINK OAM on a specific 
port or a range of ports on a switch. When enabled, the port can be set to receive, transmit, or both trans-
mit and receive OAMPDUs.
To enable LINK OAM globally on a range of ports, use the efm-oam command, as shown:
-> efm-oam port 2/1-10 status enable
To disable LINK OAM globally on a range of ports, use the disable form of the command, as shown:
-> efm-oam port 2/1-10 status disable
To enable LINK OAM mode to active, use the port mode command, as shown:
-> efm-oam port 2/1-10 mode active
By default, LINK OAM port mode is active on all the ports.
Setting the Transmit Delay
LINK OAM requires that frames be exchanged with a minimum frequency to maintain the relationship
( keep-alive). If no OAMPDUs are received in a specific time interval window, the OAM peering relation-
ship is lost and must be restored to perform OAM functions. 
 command to configure the keepalive time interval. 
-> efm-oam port 2/1-10 keepalive-interval 10
To configure the time interval by which the information OAMPDUs should be transmitted out of an LINK 
OAM enabled port, use the 
 command. 
-> efm-oam port 2/1-10 hello-interval 10
Note. By default, the keep-alive interval value is 5 seconds and the hello-interval value is set to 1 second.
Enabling and Disabling Propagation of Events
In a network where traffic is interrupted due to device failures or unavailability, the flag field defined in 
OAMPDUs allows a LINK OAM enabled node to send severe error conditions to its peer. Se
 for more information on error conditions.
The ports can be enabled to report severe error conditions like critical events and dying gasp events by 
using the 
-> efm-oam port 2/1-10 propagate-events critical-event enable