Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Example: Configuring 802.3ah OAM Link-Fault Management and Enabling Remote Failure Monitoring on an Interface

    The following example shows how to enable the OAM link-fault management feature on an interface and configure a link monitoring operation for frame seconds events on the interface.

    1. Specify the Gigabit Ethernet interface on which OAM link-fault management needs to be enabled, and configure the link discovery mode as active. When OAM functionality is enabled on the interface, the discovery mode of the local OAM entity is set to active by default. An OAM entity in active mode initiates the discovery process by sending an Information OAM PDU to the multicast address of the slow protocol (0180.c200.0002) at a configured rate.
      host1(config)#interface gigabitEthernet 4/1 host1(config-if)#ethernet oam lfm mode active
    2. Configure the Ethernet OAM link-fault management functionality to detect link-fault and dying-gasp conditions that occurred in the receive path of the link and influence the state of the link based on an Event Notification PDU received from the remote peer. Link Fault means a loss of signal, Dying Gasp means an unrecoverable condition such as a power failure.
      host1(config-if)#ethernet oam lfm remote-failure dying-gasp action disable-interfacehost1(config-if)#ethernet oam lfm remote-failure link-fault action disable-interface
    3. Configure the local interface to be disabled when the high threshold for an error condition is exceeded. The OAM functionality unconditionally attempts to influence the operational state of the interface to down.
      host1(config-if)#ethernet oam lfm high-threshold action disable-interface
    4. Configure link monitoring operations for frame error events on the interface. Specify the high threshold in number of frames for frame error events as 200, which when exceeded causes an action to be triggered. Specify a low threshold for frame error events, which when exceeded causes an Errored Frame Seconds Summary Event TLV to be sent to the peer, as 20 frames. Also, set the window during which frame error events are counted as 300 hundred millisecond units or 30 seconds.
      host1(config-if)#ethernet oam lfm link-monitor frame-seconds threshold high 200 host1(config-if)#ethernet oam lfm link-monitor frame-seconds threshold low 20 host1(config-if)#ethernet oam lfm link-monitor frame-seconds window 300

    Published: 2014-08-14