< Home

oam-bind interface efm interface trigger if-down

Function

The oam-bind interface efm interface trigger if-down command enables bidirectional transmission of fault messages between an interface and EFM OAM.

The undo oam-bind interface efm interface trigger if-down command cancels the configuration.

By default, bidirectional transmission of information about a fault between an interface and EFM OAM is not configured.

Format

oam-bind interface interface-type1 interface-number1 efm interface interface-type2 interface-number2 trigger if-down

undo oam-bind interface interface-type1 interface-number1 efm interface interface-type2 interface-number2 trigger if-down

Parameters

Parameter Description Value
interface-type1 interface-number1

Specifies the type and number of the interface enabled with EFM.

  • interface-type1 specifies the interface type.
  • interface-number1 specifies the interface number.

-
interface-type2 interface-number2

Specifies the type and number of the interface bound to an EFM session.

  • interface-type2 specifies the interface type.

  • interface-number2 specifies the interface number.

-

Views

OAM management view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If an inward MEP is configured, bidirectional association between EFM and an EFM-incapable interface of a device can be configured in the OAM management view. This ensures that service traffic can be switched to the backup link if the primary link fails.

Association between EFM and an interface in the OAM management view is bidirectional:
  • After EFM OAM detects a fault, the OAM module notifies the interface associated with EFM OAM of the fault. Then the interface goes Down. After EFM detects that the fault is rectified, the OAM module notifies the interface associated with EFM OAM. Then the interface goes Up.

  • After the interface goes Down, the OAM module notifies EFM OAM of the interface Down event.

The following commands are used to configure association between EFM and an interface in the OAM management view:
  • oam-bind efm interface trigger if-down interface

  • oam-bind interface efm interface trigger if-down

  • oam-bind ingress efm interface trigger if-down egress interface

  • oam-bind ingress interface egress efm interface trigger if-down

Table 1 describes the implementation of association between EFM and an interface.
Table 1 Association between EFM and an EFM-incapable interface

Scenario

Configuration Solution 1

Configuration Solution 2

Bidirectional fault notification between EFM and an interface

Choose either of the following commands (the two commands have the same function):

  • To specify an EFM OAM session first, run the oam-bind efm interface trigger if-down interface command.

  • To specify an interface first, run the oam-bind interface efm interface trigger if-down command.

NOTE:

After configuring bidirectional fault notification between EFM and an interface, run the display current-configuration command to view the current configuration. The display current-configuration command displays oam-bind ingress interface egress efm interface trigger if-down and oam-bind ingress efm interface trigger if-down egress interface commands, but does not display the oam-bind efm interface trigger if-down interface or oam-bind interface efm interface trigger if-down command. The displayed commands configure reverse transmission directions of fault information.

Run the following commands at a random order:
  • oam-bind ingress efm interface trigger if-down egress interface

  • oam-bind ingress interface egress efm interface trigger if-down

Unidirectional fault notification between EFM and an interface

Choose either of the following commands based on the transmission direction:

  • To configure EFM OAM to report faults to an interface, run the oam-bind ingress efm interface trigger if-down egress interface command.

  • To configure an interface to report faults to EFM OAM, run the oam-bind ingress interface egress efm interface trigger if-down command.

None

Prerequisites

Basic EFM OAM functions have been configured.

Precautions

When configuring bidirectional transmission of fault messages between EFM and an interface, pay attention to the following points:

  • EFM has been enabled on the interface specified by efm interface interface-type2 interface-number2.

  • EFM and the interface are associated with each other. After an interface is associated with an EFM session, the interface cannot be associated with other EFM sessions. Similarly, when EFM is bound to an interface, EFM cannot be bound to other interfaces.

  • Association between EFM and an EFM-capable interface and association between EFM and an EFM-incapable interface cannot be configured together.

  • A physical interface associated with EFM cannot be the one that EFM monitors. If EFM is associated with a physical interface that it monitors, the link is locked.

Example

# Configure bidirectional transmission of fault messages between EFM and GigabitEthernet0/0/1.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind interface gigabitethernet 0/0/1 efm interface gigabitethernet 0/0/2 trigger if-down
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >