No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R013C00 Command Reference

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
EFM Configuration Commands

EFM Configuration Commands

Command Support

Commands provided in this section and all the parameters in the commands are supported by all switch models by default, unless otherwise specified. For details, see specific commands.

clear mgr inactive-configuration slot

Function

The clear mgr inactive-configuration slot command deletes the inactive Ethernet OAM configurations from the card that does not register.

Format

clear mgr inactive-configuration slot slot-id [ card card-id ]

Parameters

Parameter

Description

Value

slot slot-id

Specifies the slot ID of a card that does not register.

The value is an integer and the value range depends on device model.

card card-id

Specifies the offline card ID.

The value is an integer and the value range depends on device model.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

After a card or a subcard has been replaced, using the clear mgr inactive-configuration slot command deletes the configurations of the card or subcard that does not register if these configurations do not need to be saved.

Running the clear mgr inactive-configuration slot command can delete the inactive configurations and the sub-interfaces from the card that does not register.

Before using this command, note the following points:
  • Ensure that the specified card on which configurations are to be deleted does not register.
  • Ensure that the specified subcard on which configurations are to be deleted does not register.

Example

# Delete the configurations of the card that does not register in slot 1.

<HUAWEI> system-view
[HUAWEI] clear mgr inactive-configuration slot 1
Warning: The inactive oam-mgr configuration related to the interfaces of the slot or card will be deleted and cannot be restored, continue? [Y/N]:y             
Info: Operation succeeded.

display efm

Function

The display efm command displays the EFM configuration on an interface.

Format

display efm { all | interface interface-type interface-number }

Parameters

Parameter Description Value
all

Displays the EFM configuration on all the interfaces enabled with EFM.

-
interface-type interface-number

Displays the EFM configuration of a specified interface.

  • interface-type specifies the interface type.

  • interface-number specifies the interface number.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To view the EFM configuration on the device, run the display efm command.
  • If all is specified, all EFM configuration is displayed.

  • If interface interface-type interface-number is specified, the EFM configuration of a specified interface is displayed.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Display the EFM configuration on GigabitEthernet1/0/1.

<HUAWEI> display efm interface gigabitethernet 1/0/1
  Item                           Value
  ----------------------------------------------------
  Interface:                     GigabitEthernet1/0/1
  EFM Enable Flag:               enable
  Mode:                          active
  Loopback IgnoreRequest:        no
  OAMPDU MaxSize:                128
  OAMPDU Timeout:                5000
  OAMPDU Interval:               1000
  Parser:                        forward
  Multiplexer:                   forward
  ErrCodeNotification:           disable
  ErrCodePeriod:                 1
  ErrCodeThreshold:              1
  ErrFrameNotification:          disable
  ErrFramePeriod:                1
  ErrFrameThreshold:             1
  ErrFrameSecondNotification:    disable
  ErrFrameSecondPeriod:          60
  ErrFrameSecondThreshold:       1
  Hold Up Time:                  10  
  ThresholdEvtTriggerErrDown:    enable
  TriggerIfDown:                 disable
  TriggerMacRenew:               disable
  Remote MAC:                    --
  Remote EFM Enable Flag:        --
  Remote Mode:                   --
  Remote MaxSize:                --
  Remote Loopback IgnoreRequest: --
  Remote State:                  --
  Remote Parser:                 --
  Remote Multiplexer:            --
  ErrFramePeriodNotification:    disable
  ErrFramePeriodPeriod:          200000
  ErrFramePeriodThreshold:       1
  Loopback Remain Time:          1189
Table 12-40  Description of the display efm command output

Item

Description

Interface

Interface name.

EFM Enable Flag

Whether EFM is enabled on an interface:
  • disable: indicates that EFM is disabled on an interface.

  • enable: indicates that EFM is enabled on an interface.

To enable or disable EFM on an interface, run the efm enable command.

Mode

Operation mode of EFM on an interface:
  • active: indicates that EFM works in active mode.

  • passive: indicates that EFM works in passive mode.

To set the operation mode of EFM on an interface, run the efm mode command.

Loopback IgnoreRequest

Whether loopback requests from the remote end are ignored:
  • yes: Loopback requests from the remote end are ignored.

  • no: Loopback requests from the remote end are processed.

To set the parameter, run the efm loopback ignore-request command.

OAMPDU MaxSize

Maximum size of an EFM OAMPDU on an interface. The value ranges from 64 to 1518, in bytes. The default value is 128 bytes.

To set the maximum size of an EFM OAMPDU on an interface, run the efm packet max-size command.

OAMPDU Timeout

Timeout interval at which an interface receives EFM OAMPDUs. The value is an integer that ranges from 3000 to 30000, in milliseconds. It must be an integer multiple of 1000. The default value is 5000 ms.

To set the timeout interval at which an interface receives EFM OAMPDUs, run the efm timeout command.

OAMPDU Interval

Timeout interval at which an interface sends EFM OAMPDUs. The value is fixed as 1000, in milliseconds.

Parser

Parser:
  • forward: device is forwarding non-OAMPDUS to the lower sublayer.

  • loopback: device is looping back non-OAMPDUs to lower sublayer.

  • discard: device is discarding non-OAMPDUS.

Multiplexer

Multiplexer:
  • forward: device is forwarding non-OAMPDUs to higher sublayer.

  • discard: device is discarding non-OAMPDUS.

ErrCodeNotification

Whether detection of EFM errored codes is enabled:
  • disable: indicates that detection of EFM errored codes is disabled.

  • enable: indicates that detection of EFM errored codes is enabled.

To enable or disable the detection of EFM errored codes, run the efm error-code notification enable command.

ErrCodePeriod

Period for detecting EFM errored codes on an interface. The value ranges from 1 to 60, in seconds. The default value is 1s.

To set the period for detecting EFM errored codes on an interface, run the efm error-code period command.

ErrCodeThreshold

Threshold for detecting EFM errored codes on an interface. The value ranges from 0 to 65535. The default value is 1.

To set the threshold for detecting EFM errored codes on an interface, run the efm error-code threshold command.

ErrFrameNotification

Whether detection of EFM errored frames is enabled:
  • disable: indicates that detection of EFM errored frames is disabled.

  • enable: indicates that detection of EFM errored frames is enabled.

To enable or disable the detection of EFM errored frames, run the efm error-frame notification enable command.

ErrFramePeriod

Period for detecting EFM errored frames on an interface. The value ranges from 1 to 60, in seconds. The default value is 1s.

To set the period for detecting EFM errored frames on an interface, run the efm error-frame period command.

ErrFrameThreshold

Threshold for detecting EFM errored frames on an interface. The value ranges from 0 to 65535. The default value is 1.

To set the threshold for detecting EFM errored frames on an interface, run the efm error-frame threshold command.

ErrFrameSecondNotification

Whether detection of EFM errored frame seconds is enabled:
  • disable: indicates that detection of EFM errored frame seconds is disabled.

  • enable: indicates that detection of EFM errored frame seconds is enabled.

To enable or disable the detection of EFM errored frame seconds, run the efm error-frame-second notification enable command.

ErrFrameSecondPeriod

Period for detecting EFM errored frame seconds on an interface. The value ranges from 10 to 900, in seconds. The default value is 60s.

To set the period for detecting EFM errored frame seconds on an interface, run the efm error-frame-second period command.

ErrFrameSecondThreshold

Threshold for detecting EFM errored frame seconds on an interface. The value ranges from 0 to 900. The default value is 1.

To set the threshold for detecting EFM errored frame seconds on an interface, run the efm error-frame-second threshold command.

Hold Up Time

Value of the EFM faulty-state holdup timer. The value ranges from 0 to 50, in seconds. The default value is 0.

To set the value of the EFM faulty-state holdup timer, run the efm holdup-timer command.

ThresholdEvtTriggerErrDown

Whether a threshold crossing event is associated with an interface:
  • disable: A threshold crossing event is not associated with an interface.

  • enable: A threshold crossing event is associated with an interface.

To set the parameter, run the efm threshold-event trigger error-down command.

TriggerIfDown

Whether an interface is blocked when the interface detects a fault on the link between the local and peer interfaces:
  • disable: The system does not block an interface when detecting a fault on the link between the local and peer interfaces.

  • enable: The system blocks an interface when detecting a fault on the link between the local and peer interfaces.

To set the parameter, run the efm trigger if-down command.

TriggerMacRenew

Whether the MAC address entry on an interface is updated when the interface detects a fault on the link between the local and peer interfaces:
  • disable: The system does not update the MAC address entry when detecting a fault on the link between the local and peer interfaces.

  • enable: The system updates the MAC address entry when detecting a fault on the link between the local and peer interfaces.

To set the parameter, run the efm trigger mac-renew command.

Remote MAC

MAC address of the remote interface. The value -- indicates that the system cannot obtain the MAC address of the remote interface.

Remote EFM Enable Flag

Whether EFM is enabled on the remote interface:
  • disable: indicates that EFM is disabled on the remote interface.

  • enable: indicates that EFM is enabled on the remote interface.

  • --: indicates that the system cannot obtain the EFM status on the remote device.

Remote Mode

Operation mode of EFM on the remote interface:
  • active: indicates that EFM works in active mode.

  • passive: indicates that EFM works in passive mode.

  • --: indicates that the system cannot obtain the operation mode of EFM on the remote device.

Remote MaxSize

Maximum size of an OAMPDU on the remote interface, in bytes. The value -- indicates that the system cannot obtain the maximum size of an OAMPDU on the remote interface.

Remote Loopback IgnoreRequest

Whether the remote interface ignores loopback requests from the local end:
  • --: The system cannot obtain the mode in which the remote interface processes loopback requests from the local end.

  • yes: The remote interface ignores loopback requests from the local end.

  • no: The remote interface processes loopback requests from the local end.

Remote State

Active/Standby information of the peer device. The value -- indicates that the system cannot obtain the active/standby information of the peer device.

Remote Parser

Remote parser:
  • forward: device is forwarding non-OAMPDUS to the lower sublayer.

  • discard: device is discarding non-OAMPDUS.

Remote Multiplexer

Remote Multiplexer:
  • forward: device is forwarding non-OAMPDUs to higher sublayer.

  • loopback: device is looping back non-OAMPDUs to lower sublayer.

  • discard: device is discarding non-OAMPDUS.

ErrFramePeriodNotification

Whether detection of EFM errored frame periods is enabled:

  • disable: indicates that detection of EFM errored frame periods is disabled.

  • enable: indicates that detection of EFM errored frame periods is enabled.

ErrFramePeriodPeriod

Period for detecting errored frame periods on the interface. The value is an integer that ranges from 20000 to 4294967295. The default value is 200000.

ErrFramePeriodThreshold

Threshold for detecting errored frame periods on the interface. The value is an integer that ranges from 0 to 900. The default value is 1.

Loopback Remain Time

Remaining time of remote loopback:

  • --: The interface does not send a remote loopback request.

  • Never Timeout: The interface sends a remote loopback request. The value of timeout is 0, indicating that the interface is always in remote loopback state.

  • Loopback Remain Time: The interface sends a remote loopback request, and the timeout interval of remote loopback is specified.

display efm session

Function

The display efm session command displays information about an EFM session between the specified interface and the peer.

Format

display efm session { all | interface interface-type interface-number }

Parameters

Parameter Description Value
all

Displays information about EFM sessions between all interfaces configured with EFM and the peers.

-
interface-type interface-number

Displays information about the EFM session between the specified interface and the peer.

  • interface-type specifies the interface type.

  • interface-number specifies the interface number.

-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

To check whether an EFM session configured on a device is negotiated successfully, run the display efm session command. The command output includes the EFM status and timeout interval of a loopback test.
  • If all is specified, information about all EFM sessions configured on the device is displayed.

  • If interface interface-type interface-number is specified, information about EFM sessions configured on a specified interface is displayed.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Display information about EFM sessions between all interfaces and the peers.

<HUAWEI> display efm session all
Interface                 EFM State                   Loopback Timeout
----------------------------------------------------------------------
GigabitEthernet1/0/1      discovery                   --
Table 12-42  Description of the display efm session command output

Item

Description

Interface

Interface name.

EFM State

EFM protocol status on the interface:
  • disabled: The EFM protocol is disabled on the interface.

  • discovery: The interface is in OAM discovery state.

  • detect: The interface is in Detect state.

  • loopback (control): The interface initiates remote loopback and discards the packets looped back.

  • loopback (be controlled): The interface responds to remote loopback.

Loopback Timeout

Timeout interval of a loopback test.

display snmp-agent trap feature-name efm all

Function

The display snmp-agent trap feature-name efm all command displays the status of all traps of the EFM module.

Format

display snmp-agent trap feature-name efm all

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

The Simple Network Management Protocol (SNMP) is a network management standard widely used on the TCP/IP network. It uses a central computer (a network management station) that runs network management software to manage network elements. The SNMP agent reports trap messages to the network management station so that the network management station can obtain the network status in a timely manner, and the network administrator can take measures accordingly.

The display snmp-agent trap feature-name efm all command displays the following information:
  • Trap names supported by the EFM module. The trap names are the same as the trap names specified by the snmp-agent trap enable feature-name efm trap-name trap-name command. Each trap name corresponds to a network element abnormality.

  • Trap status of the EFM module. You can check whether the trap is reported based on the trap name.

Prerequisites

SNMP has been enabled. See snmp-agent.

Example

# Display the status of all traps of the EFM module.

<HUAWEI> display snmp-agent trap feature-name efm all
------------------------------------------------------------------------------
Feature name: EFM
Trap number : 5
------------------------------------------------------------------------------
Trap name                       Default switch status   Current switch status
threshold                       off                     off
nonthreshold                    off                     off
dyinggasp                       off                     off
nonthredholdrecovery            off                     off
loopbackfailed                  off                     off
Table 12-43  Description of the display snmp-agent trap feature-name efm all command output

Item

Description

Feature name

Name of the module that the trap belongs to.

Trap number

Number of traps.

Trap name

Trap name. Traps of the EFM module include:

  • nonthreshold: trap sent when a non-threshold crossing event occurs.
  • threshold: trap sent when a threshold crossing event occurs.
  • dyinggasp: trap of dying gasp.
  • nonthredholdrecovery: trap sent when a non-threshold fault is rectified.
  • loopbackfailed: trap sent when the loopback failed.

Default switch status

Default status of the trap function:
  • on: indicates that the trap function is enabled by default.
  • off: indicates that the trap function is disabled by default.

Current switch status

Status of the trap function:

  • on: indicates that the trap function is enabled.
  • off: indicates that the trap function is disabled.

display test-packet result

Function

The display test-packet result command displays information about sent test packets.

Format

display test-packet result

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After remote loopback is enabled and the test-packet start command is used to configure a device to send test packets, the display test-packet result command can be used to view information about sent test packets. You can determine link performance based on the information about test packets.

Example

# Display information about sent test packets.

<HUAWEI> display test-packet result
  TestResult                   Value
--------------------------------------------------------
  PacketsSend :                5
  PacketsReceive :             5
  PacketsLost :                0
  BytesSend :                  320
  BytesReceive :               320
  BytesLost :                  0
  StartTime :                  06-13-2012 14:44:13 UTC+03:00
  EndTime :                    06-13-2012 14:44:14 UTC+03:00
Table 12-44  Description of the display test-packet result command output

Item

Description

PacketsSend

Number of sent test packets.

PacketsReceive

Number of received test packets.

PacketsLost

Number of discarded test packets.

BytesSend

Total length of sent test packets, in bytes.

BytesReceive

Total length of received test packets, in bytes.

BytesLost

Total length of discarded test packets, in bytes.

StartTime

Start time test packets are sent.

EndTime

End time test packets are sent.

Related Topics

efm enable

Function

The efm enable command enables EFM globally or on an interface.

The undo efm enable command disables EFM globally or on an interface.

By default, EFM is disabled globally. That is, EFM is disabled on all interfaces.

Format

efm enable

undo efm enable

Parameters

None

Views

System view, GE interface view, XGE interface view, Eth-Trunk interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Before using EFM functions, you must enable EFM globally.

After EFM is enabled on an interface, the interface starts to send OAM PDUs to perform point-to-point EFM link detection. EFM link detection can be implemented between two interfaces only after EFM is enabled on the peer interface.

Precautions

When you use the undo efm enable command to disable EFM globally, the device deletes all EFM configurations. When the device is implementing remote loopback and sending a great deal of test packets, running the undo efm enable command will cause packets to be forwarded.

NOTE:

Eth-Trunks do not support EFM.

Example

# Enable EFM globally.

<HUAWEI> system-view
[HUAWEI] efm enable
Info: Operation succeeded.

# Enable EFM on Layer 2 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
Info: Operation succeeded.
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
Info: Operation succeeded.

# Enable EFM on Layer 3 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
Info: Operation succeeded.
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
Info: Operation succeeded.
Related Topics

efm error-code notification enable

Function

The efm error-code notification enable command enables an interface to detect EFM errored codes.

The undo efm error-code notification enable command disables an interface from detecting EFM errored codes.

By default, an interface is not enabled to detect EFM errored codes.

Format

efm error-code notification enable

undo efm error-code notification enable

Parameters

None

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Monitoring Ethernet links is difficult if network performance deteriorates while traffic is being transmitted over physical links. Link monitoring is used to detect link layer faults in various environments. After EFM link monitoring is configured, the device queries statistics about the physical layer data of the interface management module to monitor the quality of the link connected to an interface. EFM link monitoring implements the following functions:
  • Reports an alarm when the number of errored codes detected during a specified detection interval exceeds the preset threshold.

  • Reports an alarm when the number of errored frames detected during a specified detection interval exceeds the preset threshold.

  • Reports an alarm when the number of errored frame seconds detected during a specified interval exceeds the preset threshold.

The efm error-code notification enable command enables an interface to detect EFM errored codes. The local device considers a link faulty if the number of detected errored codes within the detection interval reaches or exceeds the preset threshold. Then the local device generates an alarm, reports the alarm to the NMS, and sends an OAM PDU to notify the peer device of the link failure.

Prerequisites

EFM has been enabled globally and on an interface using the efm enable command.

Example

# Enable Layer 2 interface GigabitEthernet1/0/1 to detect errored codes.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm error-code notification enable
Info: Operation succeeded.

# Enable Layer 3 interface GigabitEthernet1/0/1 to detect errored codes.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm error-code notification enable
Info: Operation succeeded.

efm error-code period

Function

The efm error-code period command sets the period for detecting EFM errored codes on an interface.

The undo efm error-code period command restores the default period for detecting EFM errored codes on an interface.

By default, the period for detecting EFM errored codes on an interface is 1s.

Format

efm error-code period period

undo efm error-code period

Parameters

Parameter Description Value
period

Specifies the period for detecting EFM errored codes.

The value is an integer that ranges from 1 to 60, in seconds. The default value is 1s.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the efm error-code period period command is run to set the period for detecting EFM errored codes, run the efm error-code notification enable command to enable an interface to detect EFM errored codes. When the number of detected errored codes during the period reaches or exceeds a preset threshold, the local device generates an alarm and notifies the peer device of the alarm event.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Set the period for detecting EFM errored codes on Layer 2 interface GigabitEthernet1/0/1 to 20s.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm error-code period 20
Info: Operation succeeded.

# Set the period for detecting EFM errored codes on Layer 3 interface GigabitEthernet1/0/1 to 20s.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm error-code period 20
Info: Operation succeeded.

efm error-code threshold

Function

The efm error-code threshold command sets the threshold for detecting EFM errored codes on an interface.

The undo efm error-code threshold command restores the default threshold for detecting EFM errored codes on an interface.

By default, the threshold for threshold for detecting EFM errored codes on an interface is 1.

Format

efm error-code threshold threshold

undo efm error-code threshold

Parameters

Parameter Description Value
threshold

Specifies the threshold for detecting EFM errored codes.

The value is an integer that ranges from 0 to 65535. The default value is 1. The value 0 is not recommended.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the efm error-code period period command is executed to set the period for detecting EFM errored codes, run the efm error-code threshold threshold command to set the threshold for detecting errored codes. Run the efm error-code notification enable command to enable an interface to detect EFM errored codes. When the number of detected errored codes during the period reaches or exceeds the threshold specified by threshold, the local device generates an alarm and notifies the peer device of the alarm event.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Set the threshold for detecting EFM errored codes on Layer 2 interfaceGigabitEthernet1/0/1 to 100.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm error-code threshold 100
Info: Operation succeeded.

# Set the threshold for detecting EFM errored codes on Layer 3 interface GigabitEthernet1/0/1 to 100.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm error-code threshold 100
Info: Operation succeeded.

efm error-frame notification enable

Function

The efm error-frame notification enable command enables an interface to detect EFM errored frames.

The undo efm error-frame notification enable command disables an interface from detecting EFM errored frames.

By default, an interface is not enabled to detect EFM errored frames.

Format

efm error-frame notification enable

undo efm error-frame notification enable

Parameters

None

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Monitoring Ethernet links is difficult if network performance deteriorates while traffic is being transmitted over physical links. Link monitoring is used to detect link layer faults in various environments. After EFM link monitoring is configured, the device queries statistics about the physical layer data of the interface management module to monitor the quality of the link connected to an interface. EFM link monitoring implements the following functions:
  • Reports an alarm when the number of errored codes detected during a specified detection interval exceeds the preset threshold.

  • Reports an alarm when the number of errored frames detected during a specified detection interval exceeds the preset threshold.

  • Reports an alarm when the number of errored frame seconds detected during a specified interval exceeds the preset threshold.

The efm error-frame notification enable command enables an interface to to detect EFM errored frames. The local device considers a link faulty if the number of detected errored frames within the detection interval reaches or exceeds the preset threshold. Then the local device generates an alarm, reports the alarm to the NMS, and sends an OAM PDU to notify the peer device of the link failure.

Prerequisites

EFM has been enabled globally and on an interface using the efm enable command.

Example

# Enable Layer 2 interfaceGigabitEthernet1/0/1 to detect errored frames.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm error-frame notification enable
Info: Operation succeeded.

# Enable Layer 3 interface GigabitEthernet1/0/1 to detect errored frames.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm error-frame notification enable
Info: Operation succeeded.

efm error-frame period

Function

The efm error-frame period command sets the period for detecting EFM errored frames on an interface.

The undo efm error-frame period command restores the default period for detecting EFM errored frames on an interface.

By default, the period for detecting EFM errored frames on an interface is 1s.

Format

efm error-frame period period

undo efm error-frame period

Parameters

Parameter Description Value
period Specifies the period for detecting EFM errored frames. The value is an integer that ranges from 1 to 60, in seconds. The default value is 1s.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the efm error-code period period command is run to set the period for detecting EFM errored frames on an interface, run the efm error-frame notification enable command to enable an interface to detect EFM errored frames. When the number of detected errored frames during the period reaches or exceeds a preset threshold, the local device generates an alarm and notifies the peer device of the alarm event.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Set the period for detecting EFM errored frames on Layer 2 interface GigabitEthernet1/0/1 to 20 seconds.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm error-frame period 20
Info: Operation succeeded.

# Set the period for detecting EFM errored frames on Layer 3 interface GigabitEthernet1/0/1 to 20 seconds.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm error-frame period 20
Info: Operation succeeded.

efm error-frame threshold

Function

The efm error-frame threshold command sets the threshold for detecting EFM errored frames on an interface.

The undo efm error-frame threshold command restores the default threshold for detecting EFM errored frames on an interface.

By default, the threshold for detecting EFM errored frames on an interface is 1.

Format

efm error-frame threshold threshold

undo efm error-frame threshold

Parameters

Parameter Description Value
threshold

Specifies the threshold for detecting EFM errored frames.

The value is an integer that ranges from 0 to 65535. The default value is 1. The value 0 is not recommended.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the efm error-frame period period commands is executed to set the period for detecting EFM errored frames on an interface, run the efm error-frame threshold threshold command to set the threshold for detecting errored frames. Run the efm error-frame notification enable command to enable an interface to detect EFM errored frames. When the number of detected errored frames during the period reaches or exceeds the threshold specified by threshold, the local device generates an alarm and notifies the peer device of the alarm event.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Set the threshold for detecting EFM errored frames on interface GigabitEthernet1/0/1 to 100.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm error-frame threshold 100
Info: Operation succeeded.

efm error-frame-second notification enable

Function

The efm error-frame-second notification enable command enables an interface to detect EFM errored frame seconds.

The undo efm error-frame-second notification enable command disables an interface from detecting EFM errored frame seconds.

By default, an interface is not enabled to detect EFM errored frame seconds.

Format

efm error-frame-second notification enable

undo efm error-frame-second notification enable

Parameters

None

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Monitoring Ethernet links is difficult if network performance deteriorates while traffic is being transmitted over physical links. Link monitoring is used to detect link layer faults in various environments. After EFM link monitoring is configured, the device queries statistics about the physical layer data of the interface management module to monitor the quality of the link connected to an interface. EFM link monitoring implements the following functions:
  • Reports an alarm when the number of errored codes detected during a specified detection interval exceeds the preset threshold.

  • Reports an alarm when the number of errored frames detected during a specified detection interval exceeds the preset threshold.

  • Reports an alarm when the number of errored frame seconds detected during a specified interval exceeds the preset threshold.

The efm error-frame-second notification enable command enables an interface to detect EFM errored frame seconds. The local device considers a link faulty if the number of detected errored frame seconds within the detection interval reaches or exceeds the preset threshold. Then the local device generates an alarm, reports the alarm to the NMS, and sends an OAM PDU to notify the peer device of the link failure.

Prerequisites

EFM has been enabled globally and on an interface using the efm enable command.

Example

# Enable Layer 2 interface GigabitEthernet1/0/1 to detect errored frame seconds.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm error-frame-second notification enable
Info: Operation succeeded.

# Enable Layer 3 interface GigabitEthernet1/0/1 to detect errored frame seconds.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm error-frame-second notification enable
Info: Operation succeeded.

efm error-frame-second period

Function

The efm error-frame-second period command sets the period for detecting EFM errored frame seconds on an interface.

The undo efm error-frame-second period command restores the default period for detecting EFM errored frame seconds on an interface.

By default, the period for detecting EFM errored frame seconds on an interface is 60s.

Format

efm error-frame-second period period

undo efm error-frame-second period

Parameters

Parameter Description Value
period

Specifies the period for detecting EFM errored frame seconds.

The value is an integer that ranges from 10 to 900, in seconds. The default value is 60s.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the efm error-frame-second period period command is run to set the period for detecting EFM errored frame seconds on an interface, run the efm error-frame-second notification enable command to enable an interface to detect EFM errored frame seconds. When the number of detected errored frame seconds during the period reaches or exceeds a preset threshold, the local device generates an alarm and notifies the peer device of the alarm event.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Set the period for detecting EFM errored frame seconds on Layer 2 interface GigabitEthernet1/0/1 to 20s.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm error-frame-second period 20
Info: Operation succeeded.

# Set the period for detecting EFM errored frame seconds on Layer 3 interface GigabitEthernet1/0/1 to 20s.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm error-frame-second period 20
Info: Operation succeeded.

efm error-frame-second threshold

Function

The efm error-frame-second threshold command sets the threshold for detecting EFM errored frame seconds on an interface.

The undo efm error-frame-second threshold command restores the default threshold for detecting EFM errored frame seconds on an interface.

By default, the threshold for detecting EFM errored frame seconds on an interface is 1.

Format

efm error-frame-second threshold threshold

undo efm error-frame-second threshold

Parameters

Parameter Description Value
threshold

Specifies the threshold for detecting EFM errored frame seconds.

The value is an integer that ranges from 0 to 900. The default value is 1. The value 0 is not recommended.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the efm error-frame-second period period command is executed to set the threshold for detecting EFM errored frame seconds on an interface, run the efm error-frame-second threshold threshold command to set the threshold for detecting errored frame seconds. Run the efm error-frame-second notification enable command to enable an interface to detect EFM errored frame seconds. When the number of detected errored frame seconds during the period reaches or exceeds the threshold specified by threshold, the local device generates an alarm and notifies the peer device of the alarm event.

Prerequisites

EFM has been enabled globally using the efm enable command.

Example

# Set the threshold for detecting EFM errored frame seconds on Layer 2 interface GigabitEthernet1/0/1 to 10.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm error-frame-second threshold 10
Info: Operation succeeded.

# Set the threshold for detecting EFM errored frame seconds on Layer 3 interface GigabitEthernet1/0/1 to 10.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm error-frame-second threshold 10
Info: Operation succeeded.

efm holdup-timer

Function

The efm holdup-timer command sets the value of the EFM faulty-state holdup timer on an interface.

The undo efm holdup-timer command restores the default value interval of the EFM faulty-state holdup timer on an interface.

By default, the value of the EFM faulty-state holdup timer is 0s.

Format

efm holdup-timer time

undo efm holdup-timer

Parameters

Parameter Description Value
time

Specifies the value of the EFM faulty-state holdup timer on an interface.

The value is an integer that ranges from 0 to 50, in seconds. The default value is 0.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the efm trigger if-down command is used to associate EFM with an interface, run the efm holdup-timer command to set the value of the EFM faulty-state holdup timer for connectivity faults detected by EFM. The faulty state remains unchanged within the value of the holdup timer. EFM does not detect whether the connectivity fault is cleared until the faulty-state holdup timer expires.

After the failed link recovers, EFM works as follows:
  • If time is not specified, EFM immediately changes the link status to Up.
  • If time is specified, EFM changes the link status to Up only after the time specified by time expires. This prevents the link from frequently alternating between Up and Down.

Prerequisites

EFM has been enabled globally and on interfaces using the efm enable command.

It is recommended that you run the efm trigger if-down command to associate EFM with an interface before running the efm holdup-timer command to set the value of EFM faulty-state holdup timer on the interface. Otherwise, the holdup timer does not take effect.

Example

# Set the value of EFM faulty-state holdup timer on GigabitEthernet1/0/1 to 10s.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm trigger if-down
[HUAWEI-GigabitEthernet1/0/1] efm holdup-timer 10

efm loopback

Function

The efm loopback command configures an interface to initiate or end an EFM remote loopback.

Format

efm loopback { start [ timeout timeout ] | stop }

Parameters

Parameter Description Value
start

Initiate an EFM remote loopback.

-
timeout timeout

Specifies the timeout interval of an EFM remote loopback.

The value is an integer that ranges from 0 to 1000, in minutes. The default value is 20. The value 0 indicates that no timeout interval is set. That is, the interface remains in remote loopback state.
stop

Ends an EFM remote loopback.

-

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

NOTE:

The SA series cards and ET1D2X48SEC0 can only work in the active mode in EFM remote loopback.

Usage Scenario

EFM remote loopback is used to locate link failures and test the link quality. After remote loopback is enabled, configure the local device to send test packets to the peer device. Based on the statistics about sent and received test packets, you can check connectivity and performance of a specified link.

  • If start is specified, an interface on the local device sends a remote loopback message to the peer device. After receiving the message, the peer device enters the loopback state. In loopback state, the peer sends back all received packets, except EFM OAMPDUs, to the local device through the interface that has received these packets.

  • If stop is specified, an interface on the local device sends a remote loopback stop message to the peer device. After receiving the message, the peer device exits from the loopback state.
  • If remote loopback is left enabled, the remote device keeps looping back service data, causing a service interruption. To prevent this problem, a capability can be configured to disable remote loopback automatically after a specified timeout interval. By default, the timeout interval for remote loopback is 20 minutes. The remote loopback test stops after 20 minutes. You can set the timeout interval to 0 to keep a link in remote loopback state.

    NOTE:

    The link in remote loopback state will not forward service data. Therefore, execute caution when you set the timeout interval to 0.

Prerequisites

  • EFM has been enabled and is in detect state.

  • The device has been configured to work in active mode using the efm mode active command.

Precautions

After remote loopback is enabled, all packets except EFM OAMPDUs are looped back on the remote device. EFM OAM remote loopback must be implemented on the link that does not need to forward service data. Otherwise, service data forwarding is affected.

Remote loopback is implemented successfully only when EFM protocols at the local end and the peer are in handshake state and EFM at the local end works in active mode. You can use the display efm session command to check whether EFM OAM protocols on the local interface and the peer are in handshake state.

Example

# Configure Layer 2 interface GigabitEthernet1/0/1 to initiate an EFM OAM remote loopback.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm loopback start

# Set the timeout interval for an EFM OAM remote loopback on Layer 2 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm loopback start timeout 10

# Configure Layer 2 interface GigabitEthernet1/0/1 to stop an EFM OAM remote loopback.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm loopback stop

# Configure Layer 3 interface GigabitEthernet1/0/1 to initiate an EFM OAM remote loopback.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm loopback start

# Set the timeout interval for an EFM OAM remote loopback on Layer 3 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm loopback start timeout 10

# Configure Layer 3 interface GigabitEthernet1/0/1 to stop an EFM OAM remote loopback.

<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm loopback stop

efm loopback ignore-request

Function

The efm loopback ignore-request command enables an interface to ignore loopback requests sent by the remote end.

The undo efm loopback ignore-request command restores the default setting for the loopback function on an interface.

By default, an interface supports remote loopback. After receiving a loopback request from a remote end, the interface enters the loopback state.

Format

efm loopback ignore-request

undo efm loopback ignore-request

Parameters

None

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Remote loopback is used to monitor link quality and locate link faults. Periodic loopback detection helps detect network faults in a timely manner.

If an interface is in loopback state, the interface loops back all received traffic, causing service interruption and imposing attacks. To solve this problem, run the efm loopback ignore-request command to enable the interface to reject the remote Ethernet OAM loopback request carried in a Loopback Control OAMPDU sent by a remote interface.

Prerequisites

EFM has been enabled globally and on an interface using the efm enable command and the interface is not in loopback state.

Precautions

After the efm loopback ignore-request command is run, the interface will discard an OAMPDU carrying a remote loopback request.

Example

# Enable Layer 2 interface GigabitEthernet1/0/1 to ignore loopback requests sent by a specified remote interface.

<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm loopback ignore-request

# Enable Layer 3 interface GigabitEthernet1/0/1 to ignore loopback requests sent by a specified remote interface.

<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm loopback ignore-request

efm mode

Function

The efm mode command configures the working mode of EFM on an interface.

The undo efm mode command restores the default working mode of EFM on an interface.

By default, EFM on an interface works in active mode.

Format

efm mode { active | passive }

undo efm mode

Parameters

Parameter Description Value
active

Indicates that EFM on an interface works in active mode.

-
passive

Indicates that EFM on an interface works in passive mode.

-

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

EFM supports two connection modes: active and passive. By setting the working mode of EFM OAM, you can configure whether a device can send or receive a specified type of EFM OAMPDU. Table 12-45 describes the differences between the active and passive modes.

Table 12-45  Capabilities for processing OAMPDUs in active and passive modes
Event Active Mode Passive Mode
Initiate a connection request by sending an Information OAMPDU during the discovery process Supported Not supported
Respond to a connection request during the discovery process Supported Supported
Send Information OAMPDUs Supported Supported
Send Event Notification OAMPDUs Supported Supported
Send Loopback Control OAMPDUs Supported Not supported
Respond to Loopback Control OAMPDUs Supported (The remote EFM entity must work in active mode.) Supported

Precautions

  • The working mode of EFM can be set on an interface only after EFM is enabled globally and before EFM is enabled on the interface. The working mode of EFM on an interface cannot be changed after EFM is enabled on the interface. Before changing the working mode of EFM on an interface, run the undo efm enable command to disable EFM on the interface.

  • An EFM connection can only be initiated by an OAM entity working in active mode. An OAM entity working in passive mode waits to receive a connection request from its peer entity.

  • Two OAM entities both working in passive mode cannot establish an EFM connection between them.

Example

# Configure EFM OAM on Layer 2 interface GigabitEthernet1/0/1 to work in passive mode.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm mode passive

# Configure EFM OAM on Layer 3 interface GigabitEthernet1/0/1 to work in passive mode.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm mode passive

efm packet max-size

Function

The efm packet max-size command sets the maximum size of an EFM OAMPDU on an interface. All EFM OAMPDUs that exceed the maximum size on an interface are discarded as invalid packets.

The undo efm packet max-size command restores the default maximum size of an EFM OAMPDU on an interface.

By default, the maximum size of an EFM OAMPDU on an interface is 128 bytes.

Format

efm packet max-size size

undo efm packet max-size

Parameters

Parameter Description Value
size

Specifies the maximum size of an EFM OAMPDU. The size contains the length of Layer 2 frame header and the length of the cyclic redundancy check (CRC) field.

The value is an integer that ranges from 64 to 1518, in bytes. The default value is 128 bytes.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can run the efm packet max-size command to adjust the maximum size of an EFM OAMPDU so that non-Huawei devices can communicate.

Prerequisites

EFM has been enabled globally using the efm enable command.

Precautions

The local device and the peer determine the actual value of the maximum size of an EFM OAMPDU through negotiation. The smaller maximum size of an EFM OAMPDU set on the local interface or the peer is used.

Example

# Set the maximum size of an EFM OAMPDU on Layer 2 interface GigabitEthernet1/0/1 to 120 bytes.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm packet max-size 120

# Set the maximum size of an EFM OAMPDU on Layer 3 interface GigabitEthernet1/0/1 to 120 bytes.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm packet max-size 120

efm src-mac

Function

The efm src-mac command configures an interface or bridge MAC address as the source MAC address in an OAMPDU.

The undo efm src-mac command restores the default configuration.

By default, a bridge MAC address is used as the source MAC address in an OAMPDU.

Format

efm src-mac { port | bridge }

undo efm src-mac

Parameters

Parameter Description Value
port Configures an interface MAC address as the source MAC address in an OAMPDU. -
bridge Configures a bridge MAC address as the source MAC address in an OAMPDU. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

OAMPDUs support interface or bridge MAC addresses as source MAC addresses. You can run the efm src-mac command to configure an interface or bridge MAC address as the source MAC address in an OAMPDU before enabling EFM globally.

Example

# Configure an interface MAC address as the source MAC address in an OAMPDU.

<HUAWEI> system-view
[HUAWEI] efm src-mac port

efm timeout

Function

The efm timeout command sets the timeout interval at which EFM OAMPDUs are received.

The undo efm timeout command restores the default timeout interval.

By default, the timeout interval at which EFM OAMPDUs are received is 5000 milliseconds.

Format

efm timeout timeout-value

undo efm timeout

Parameters

Parameter Description Value
timeout-value

Specifies the timeout interval at which an interface receives EFM OAMPDUs.

The value is an integer that ranges from 3000 to 30000, in milliseconds. The step is 1000 milliseconds. The default value is 5000 milliseconds.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By setting the timeout interval at which OAMPDUs are received, you can change the time required for connectivity fault detection.

Prerequisites

EFM OAM has been enabled globally but is not enabled on an interface.

Precautions

After the timeout interval expires, the EFM OAM protocol switches back to the discovery state. Ensure that interfaces on both ends of a link use the same timeout interval. Otherwise, EFM session negotiation may fail, or the EFM session may flap.

After EFM OAM is enabled on an interface, the timeout interval cannot be changed.

  • A shorter timeout interval indicates a shorter time required for connectivity fault detection.

  • A longer timeout interval indicates a longer time required for connectivity fault detection.

Example

# Set the timeout interval at which EFM OAMPDUs are received on Layer 2 interface GigabitEthernet1/0/1 to 3000 ms.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm timeout 3000

# Set the timeout interval at which EFM OAMPDUs are received on Layer 3 interface GigabitEthernet1/0/1 to 3000 ms.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm timeout 3000

efm threshold-event trigger error-down

Function

The efm threshold-event trigger error-down command associates an EFM threshold crossing event with an interface.

The undo efm threshold-event trigger error-down command disassociates an EFM threshold crossing event from an interface.

By default, a threshold crossing event is not associated with an interface.

Format

efm threshold-event trigger error-down

undo efm threshold-event trigger error-down

Parameters

None

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When link monitoring is configured for an interface on a link, the link is considered unavailable, if the number of errored frames, errored codes, or errored frame seconds detected by the interface reaches or exceeds the threshold within a period. In this case, you can run the efm threshold-event trigger error-down command to associate a threshold crossing event with an interface so that the system sets the administrative state of the interface to Down. As a result, all services on the interface are interrupted.

Prerequisites

EFM has been enabled on an interface using the efm enable command.

Follow-up Procedure

Configure the interface to go administratively Up by using either of the following methods:
  • Run the error-down auto-recovery command to set the auto-recovery delay before an interface goes administratively Up.

  • Run the shutdown command and then the undo shutdown command to restore the administrative state of the interface to Up.

Example

# Associate a threshold crossing event with Layer 2 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm threshold-event trigger error-down

# Associate a threshold crossing event with Layer 3 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm threshold-event trigger error-down

efm trigger clear-arp vlan

Function

The efm trigger clear-arp vlan command clears an ARP entry corresponding to a VLANIF interface.

The undo efm trigger clear-arp vlan command cancels the configuration.

By default, an interface does not clear an ARP entry.

Format

efm trigger clear-arp vlan vlan-id

undo efm trigger clear-arp vlan vlan-id

Parameters

Parameter Description Value
vlan-id

Specifies the VLAN ID in an ARP entry.

The value is an integer that ranges from 1 to 4094.

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

NOTE:

The efm trigger clear-arp vlan command takes effect only on Layer 2 Ethernet interfaces.

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When detecting a fault, the EFM module notifies the OAM management module of the fault. The OAM management module searches the EFM fault relationship table based on the interface number and VLAN ID, and then clears the ARP entry that corresponds to the VLANIF interface.

Prerequisites

EFM has been enabled globally and on an interface using the efm enable command.

Example

# Enable GigabitEthernet1/0/1 in VLAN 10 to clear ARP entries.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm trigger clear-arp vlan 10
Related Topics

efm trigger error-down

Function

The efm trigger error-down command associates an error event with an interface.

The undo efm trigger error-down command disassociates an error event from an interface.

By default, an error event is not associated with an interface.

Format

efm { critical-event | dying-gasp | link-fault | timeout } trigger error-down

undo efm { critical-event | dying-gasp | link-fault | timeout } trigger error-down

Parameters

Parameter

Description

Value

critical-event

Indicates an unspecified critical event. It usually refers to a fault on the interface associated with MGR.

-

dying-gasp

Indicates an unrecoverable failure. It usually refers to device restart or power-off.

-

link-fault

Indicates a physical link fault. It usually refers to a fault on an interface.

-

timeout

Indicates the timeout interval at which EFM OAMPDUs are received.

-

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When EFM OAM associated with an interface detects a connectivity fault on a link, the protocol status of the interface goes Down. The interface goes Up after the faulty link recovers.

After the efm trigger error-down command is used, the administrative status of the interface goes Down when EFM OAM detects remote critical-event, dying-gasp, or link-fault events, or local timeout event. Traffic will not be switched back after the faulty link recovers. Check link quality before switching traffic back to the original link.

Prerequisites

EFM OAM has been enabled globally and on an interface using the efm enable command.

Follow-up Procedure

When the protocols status of an interface goes Down because error events are associated with the interface. The protocol status of the interface will not go Up even if the faulty link recovers. In this case, perform either of the following operations:

To configure the shutdown interface to go Up automatically, run the error-down auto-recovery cause efm-remote-failure interval interval-value command in the system view to enable an interface to go Up and set a recovery delay before the interface enters the error-down state. The interface goes Up automatically after the delay.

Precautions

An interface can be associated with various types of error events. For example, if both efm critical-event trigger error-down and efm dying-gasp trigger error-down are used, the protocol status of the interface becomes Down when the device receives EFM OAM packets indicating critical-event or dying-gasp faults.

  • The efm critical-event trigger error-down command is used and the remote interface associated with MGR goes Down. The local device will set the protocol status of the corresponding interface to Down after receiving an EFM OAM packet indicating a critical-event fault.

  • The efm dying-gasp trigger error-down command is used and the board where the remote interface resides is reset or the system restarts. The local device will set the protocol status of the corresponding interface to Down after receiving an EFM OAM packet indicating a dying-gasp fault.

  • The efm link-fault trigger error-down command is used and the physical link of the remote device is faulty. The local device will set the protocol status of the corresponding interface to Down after receiving an EFM OAM packet indicating a link-fault fault.

  • The efm timeout trigger error-down command is used on the local device. The local device will set the protocol status of the corresponding interface to Down if it does not receive packets from the remote device in a specified period of time (5s by default).

NOTE:

The efm trigger if-down and efm trigger error-down commands cannot be used simultaneously, and the efm trigger mac-renew and efm trigger error-down commands cannot be used simultaneously.

Example

# Associate dying-gasp faults with Layer 2 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm dying-gasp trigger error-down

# Associate dying-gasp faults with Layer 3 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm dying-gasp trigger error-down
Related Topics

efm trigger if-down

Function

The efm trigger if-down command associates EFM with an interface.

The undo efm trigger if-down command disassociates EFM from an interface.

By default, EFM OAM is not associated with any interface.

Format

efm trigger if-down

undo efm trigger if-down

Parameters

None

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

EFM can be associated with interfaces. On a scenario with primary and backup links, if EFM detects a fault on the primary link, it will set the protocol status of the associated interface to ETHOAM Down, speeding up routing convergence. Traffic can be fast switched to the backup link.

Prerequisites

EFM has been enabled globally and on an interface, and is in detect state.

Precautions

If EFM is associated with an interface and detects a link fault, the protocol status of the interface becomes ETHOAM Down, and no packet except EFM OAMPDUs can be forwarded by the interface, and all Layer 2 and Layer 3 services are blocked. Therefore, associating EFM with an interface may greatly affect services. When the interface detects link recovery using EFM, the interface can forward all packets and unblocks Layer 2 and Layer 3 services.

If Layer 2 and Layer 3 services are blocked due to a misoperation, run the undo efm trigger if-down command in the interface view to restore services.

Example

# Associate EFM with Layer 2 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm trigger if-down

# Associate EFM with Layer 3 interface GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm trigger if-down

efm trigger mac-renew

Function

The efm trigger mac-renew command configures the device to clear the MAC address table on a physical interface.

The undo efm trigger mac-renew command cancels the configuration.

By default, an interface is not enabled to clear the MAC address table.

Format

efm trigger mac-renew

undo efm trigger mac-renew

Parameters

None

Views

GE interface view, XGE interface view, 40GE interface view, 100GE interface view, port group view

NOTE:

The efm trigger mac-renew command takes effect only on Layer 2 Ethernet interfaces.

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To detect a fault on a VLL configured on the PE device connected to a CE device and to perform PW switching by clearing the MAC address table, run the efm trigger mac-renew command on the corresponding interface of the CE device.

Precautions

EFM has been enabled globally and on an interface using the efm enable command.

NOTE:

The efm trigger mac-renew and efm trigger if-down commands cannot be used simultaneously on an interface.

Example

# Configure GigabitEthernet1/0/1 to delete the corresponding MAC entry after a fault notification is received.

<HUAWEI> system-view
[HUAWEI] efm enable
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] efm enable
[HUAWEI-GigabitEthernet1/0/1] efm trigger mac-renew
Related Topics

oam-bind efm interface bfd-session

Function

The oam-bind efm interface bfd-session command enables bidirectional fault notification between EFM OAM and BFD.

The undo oam-bind efm interface bfd-session command cancels the configuration.

By default, bidirectional transmission of fault messages between EFM OAM and BFD is not configured.

Format

oam-bind efm interface interface-type interface-number bfd-session bfd-session-id

undo oam-bind efm interface interface-type interface-number bfd-session bfd-session-id

Parameters

Parameter Description Value
bfd-session-id

Specifies the ID of a BFD session.

The value is an integer that ranges from 1 to 8191.

interface-type interface-number

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

  • interface-type specifies the interface type.

  • interface-number specifies the interface number.

-

Views

OAM management view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If EFM is deployed at one side and BFD is deployed at another side of a device, associate EFM with BFD on the device. This allows EFM and BFD to notify each other of faults and ensures reliable service transmission.

Association between EFM and BFD is bidirectional:
  • If EFM detects a link fault, it will notify BFD of the fault.

  • If BFD detects a link fault, it will notify EFM of the fault.

The following commands are used to associate BFD with EFM:

Choose the preceding commands in different scenarios according to Table 12-46.

Table 12-46  Association between EFM and BFD

Scenario

Configuration Solution 1

Configuration Solution 2

Bidirectional fault notification between EFM and BFD

Use the oam-bind efm interface bfd-session command to configure EFM and BFD to notify each other of faults.

Run the following commands at a random order:

Unidirectional fault notification between EFM and BFD

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

None

Prerequisites

A BFD session has been created and EFM OAM has been enabled globally and on an interface.

Precautions

The following types of BFD sessions can be used:
  • Static BFD for LSP (LDP, TE, TE LSP, static LSP, and VLL PW) sessions (a PST is required)

  • BFD for IP sessions (no PST is required)

Example

# Configure bidirectional fault notification between EFM OAM and BFD through GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind efm interface gigabitethernet 1/0/1 bfd-session 50
Related Topics

oam-bind efm interface efm interface

Function

The oam-bind efm interface efm interface command enables bidirectional fault notification between EFM modules.

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

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

Format

oam-bind efm interface interface-type interface-number efm interface interface-type interface-number

undo oam-bind efm interface interface-type interface-number efm interface interface-type interface-number

Parameters

Parameter Description Value
interface-type interface-number

Specifies the type and the number of an interface configured with bidirectional fault notification between EFM modules.

  • interface-type specifies the interface type.

  • interface-number specifies the interface number.

-

Views

OAM management view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If EFM is deployed at both sides of a device, associate EFM modules on the device to ensure reliable service transmission.

Association between EFM and EFM is bidirectional. EFM modules notify each other of faults.

The following commands are used to associate EFM modules:

Choose the preceding commands in different scenarios according to Table 12-47.

Table 12-47  Association between EFM modules

Scenario

Configuration Solution 1

Configuration Solution 2

Bidirectional fault notification between EFM modules

Run the oam-bind efm interface efm interface command.

Use the following commands:
  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

Unidirectional fault notification between EFM sessions
Choose either of the following commands based on the transmission direction:
  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

None

Prerequisites

The following conditions must be met:
  • EFM OAM has been enabled on specified interfaces.

  • Two EFM OAM sessions have been associated with each other. When an EFM OAM session is associated with another EFM OAM session, the EFM OAM session cannot be associated with other EFM OAM sessions.

Example

# Configure bidirectional fault notification between EFM OAM sessions.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind efm interface gigabitethernet1/0/1 efm interface gigabitethernet2/0/1

oam-bind efm interface trigger if-down interface

Function

The oam-bind efm interface trigger if-down interface command enables bidirectional fault notification between EFM and an interface.

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

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

Format

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

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

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

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.

  • 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.

The following commands are used to configure association between EFM and an interface in the OAM management view: Table 12-48 describes the implementation of association between EFM and an interface.
Table 12-48  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):

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.

Unidirectional fault notification between EFM and an interface

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

None

Precautions

When configuring bidirectional fault notification between EFM and an interface, pay attention to the following points:
  • EFM has been enabled on the interface specified by efm interface interface-type1 interface-number1.

  • EFM and an 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.

Example

# Configure bidirectional fault notification between an EFM session and GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind efm interface gigabitethernet 1/0/1 trigger if-down interface gigabitethernet 2/0/1

oam-bind ingress bfd-session egress efm interface

Function

The oam-bind ingress bfd-session egress efm interface command configures BFD to report faults to EFM OAM.

The undo oam-bind ingress bfd-session egress efm interface command cancels the configuration.

By default, BFD module does not send fault messages to EFM OAM.

Format

oam-bind ingress bfd-session bfd-session-id egress efm interface interface-type interface-number

undo oam-bind ingress bfd-session bfd-session-id egress efm interface interface-type interface-number

Parameters

Parameter Description Value
bfd-session-id

Specifies the ID of a BFD session.

The value is an integer that ranges from 1 to 8191.

interface-type interface-number

Specifies the type and number of an Ethernet interface. The interface must have been enabled with EFM OAM.

  • interface-type specifies the interface type.

  • interface-number specifies the interface number.

-

Views

OAM management view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If EFM is deployed at one side and BFD is deployed at another side of a device, associate EFM with BFD on the device. This allows EFM and BFD to notify each other of faults and ensures reliable service transmission.

Association between EFM and BFD is bidirectional:
  • If EFM detects a link fault, it will notify BFD of the fault.

  • If BFD detects a link fault, it will notify EFM of the fault.

The following commands are used to associate BFD with EFM:

Choose the preceding commands in different scenarios according to Table 12-49.

Table 12-49  Association between EFM and BFD

Scenario

Configuration Solution 1

Configuration Solution 2

Bidirectional fault notification between EFM and BFD

Use the oam-bind efm interface bfd-session command to configure EFM and BFD to notify each other of faults.

Run the following commands at a random order:

Unidirectional fault notification between EFM and BFD

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

None

Prerequisites

A BFD session has been created and EFM OAM has been enabled on an interface.

Precautions

The following types of BFD sessions can be used:
  • Static BFD for LSP (LDP, TE, TE LSP, static LSP, and VLL PW) sessions (a PST is required)

  • BFD for IP sessions (no PST is required)

Example

# Configure BFD to report faults to EFM OAM through GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind ingress bfd-session 50 egress efm interface gigabitethernet 1/0/1
Related Topics

oam-bind ingress efm interface egress bfd-session

Function

The oam-bind ingress efm interface egress bfd-session command configures EFM OAM to report faults to BFD.

The undo oam-bind ingress efm interface egress bfd-session command cancels the configuration.

By default, EFM OAM from sending fault messages to BFD is not configured.

Format

oam-bind ingress efm interface interface-type interface-number egress bfd-session bfd-session-id

undo oam-bind ingress efm interface interface-type interface-number egress bfd-session bfd-session-id

Parameters

Parameter Description Value
bfd-session-id

Specifies the ID of a BFD session.

The value is an integer that ranges from 1 to 8191.

interface-type interface-number

Specifies the type and number of an Ethernet interface. The interface must have been enabled with EFM OAM.

  • interface-type specifies the interface type.

  • interface-number specifies the interface number.

-

Views

OAM management view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If EFM is deployed at one side and BFD is deployed at another side of a device, associate EFM with BFD on the device. This allows EFM and BFD to notify each other of faults and ensures reliable service transmission.

Association between EFM and BFD is bidirectional:
  • If EFM detects a link fault, it will notify BFD of the fault.

  • If BFD detects a link fault, it will notify EFM of the fault.

The following commands are used to associate BFD with EFM:

Choose the preceding commands in different scenarios according to Table 12-50.

Table 12-50  Association between EFM and BFD

Scenario

Configuration Solution 1

Configuration Solution 2

Bidirectional fault notification between EFM and BFD

Use the oam-bind efm interface bfd-session command to configure EFM and BFD to notify each other of faults.

Run the following commands at a random order:

Unidirectional fault notification between EFM and BFD

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

None

Prerequisites

A BFD session has been created and EFM OAM has been enabled globally and on an interface.

Precautions

The following types of BFD sessions can be used:
  • Static BFD for LSP (LDP, TE, TE LSP, static LSP, and VLL PW) sessions (a PST is required)

  • BFD for IP sessions (no PST is required)

Example

# Configure EFM OAM to report faults to BFD through GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind ingress efm interface gigabitethernet 1/0/1 egress bfd-session 50
Related Topics

oam-bind ingress efm interface egress efm interface

Function

The oam-bind ingress efm interface egress efm interface command enables an EFM OAM session to report faults to another EFM OAM session.

The undo oam-bind ingress efm interface egress efm interface command disables an EFM OAM session from reporting faults to another EFM OAM session.

By default, unidirectional transmission of information about a fault from one EFM OAM session to another EFM OAM session is not configured.

Format

oam-bind ingress efm interface interface-type1 interface-number1 egress efm interface interface-type2 interface-number2

undo oam-bind ingress efm interface interface-type1 interface-number1 egress efm interface interface-type2 interface-number2

Parameters

Parameter Description Value
interface-type1 interface-number1

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

  • 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 OAM 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 EFM is deployed at both sides of a device, associate EFM modules on the device to ensure reliable service transmission.

Association between EFM and EFM is bidirectional. EFM modules notify each other of faults.

The following commands are used to associate EFM modules:

Choose the preceding commands in different scenarios according to Table 12-51.

Table 12-51  Association between EFM modules

Scenario

Configuration Solution 1

Configuration Solution 2

Bidirectional fault notification between EFM modules

Run the oam-bind efm interface efm interface command.

Use the following commands:
  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

Unidirectional fault notification between EFM sessions
Choose either of the following commands based on the transmission direction:
  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

  • Run the oam-bind ingress efm interface egress efm interface command to configure EFM for the link at one side of the device to notify EFM for the link at the other side of the device of faults. ingress efm interface interface-type interface-number specifies the EFM-capable interface on the link at one side of the device, and egress efm interface interface-type interface-number specifies the EFM-capable interface on the link at the other side of the device.

None

Precautions

Ingress EFM OAM reports faults to egress EFM OAM.

Example

# Configure an EFM OAM session to report faults to another EFM OAM session.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind ingress efm interface gigabitethernet 1/0/1 egress efm interface gigabitethernet 1/0/2

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

Function

The oam-bind ingress efm interface trigger if-down egress interface command enables EFM to report faults to an interface.

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

By default, unidirectional transmission of information about a fault from EFM OAM to an interface is not configured.

Format

oam-bind ingress efm interface interface-type1 interface-number1 trigger { if-down | if-notify } egress interface interface-type2 interface-number2

undo oam-bind ingress efm interface interface-type1 interface-number1 trigger { if-down | if-notify } egress interface interface-type2 interface-number2

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

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.

  • 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.

The following commands are used to configure association between EFM and an interface in the OAM management view: Table 12-52 describes the implementation of association between EFM and an interface.
Table 12-52  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):

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 andoam-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:
Unidirectional fault notification between EFM and an interface

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

None

Precautions

Before enabling EFM to report faults to 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.

Ingress EFM reports faults to the specified interface.

Example

# Configure EFM to report a fault to GigabitEthernet2/0/1.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind ingress efm interface gigabitethernet 1/0/1 trigger if-down egress interface gigabitethernet 2/0/1

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

Function

The oam-bind ingress interface egress efm interface trigger if-down command enables an interface to report faults to EFM OAM.

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

By default, unidirectional transmission of information about a fault from an interface to EFM OAM is disabled.

Format

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

undo oam-bind ingress interface interface-type1 interface-number1 egress 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 OAM 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: Table 12-53 describes the implementation of association between EFM and an interface.
Table 12-53  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):

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:
Unidirectional fault notification between EFM and an interface

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

None

Configuration Impact

After an interface goes Down, the status of the associated EFM OAM session does not change. However, the device configured with association sends a message to inform the peer of the fault and triggers the peer to generate an alarm.

Precautions

Before enabling an interface to report faults to EFM OAM, pay attention to the following points:
  • EFM has been enabled on the interface specified by efm interface interface-type2 interface-number2.

  • EFM and an 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.

The ingress interface reports faults to egress EFM.

Example

# Configure GigabitEthernet1/0/1 to report a fault to EFM.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind ingress interface gigabitethernet 1/0/1 egress efm interface gigabitethernet 2/0/1 trigger if-down

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: Table 12-54 describes the implementation of association between EFM and an interface.
Table 12-54  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):

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.

Unidirectional fault notification between EFM and an interface

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

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 GigabitEthernet1/0/1.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr] oam-bind interface gigabitethernet 1/0/1 efm interface gigabitethernet 1/0/2 trigger if-down

oam-mgr

Function

The oam-mgr command displays the OAM management view.

The undo oam-mgr command exits from the OAM management view.

Format

oam-mgr

undo oam-mgr

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

CFM can advertise fault information to interfaces or protocol modules. Ethernet OAM fault advertisement is implemented by an OAM manager, application modules, and detection modules. An OAMMGR module associates one module with another. A detection module monitors link status and network performance. If a detection module detects a fault, it instructs the OAMMGR module to notify an application module or another detection module of the fault. After receiving the notification, the application or detection module takes measures to prevent a communication interruption or service quality deterioration. Run the oam-mgr command to display the MGR view before associating the CFM module and other modules.

Example

# Enter the OAM management view.

<HUAWEI> system-view
[HUAWEI] oam-mgr
[HUAWEI-oam-mgr]

snmp-agent trap enable feature-name efm

Function

The snmp-agent trap enable feature-name efm command enables the trap function for the EFM module.

The undo snmp-agent trap enable feature-name efm command disables the trap function for the EFM module.

By default, the trap function is disabled for the EFM module.

Format

snmp-agent trap enable feature-name efm [ trap-name { nonthreshold | threshold | nonthredholdrecovery | dyinggasp | loopbackfailed } ]

undo snmp-agent trap enable feature-name efm [ trap-name { nonthreshold | threshold | nonthredholdrecovery | dyinggasp | loopbackfailed } ]

Parameters

Parameter Description Value
trap-name

Enables or disables the trap function for the specified event.

-
nonthreshold

Enables the device to send a trap when a non-threshold crossing event occurs.

-
threshold

Enables the device to send a trap when a threshold crossing event occurs.

-
nonthredholdrecovery

Enables the device to send a trap when a non-threshold fault is rectified.

-
loopbackfailed

Enables the device to send a trap when loopback fails.

-
dyinggasp

Enables the device to send a trap when a remote Dying Gasp event occurs.

-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

You can specify trap-name to enable the trap function for one or more events.

Example

# Enable the device to send a trap when a non-threshold crossing event occurs.

<HUAWEI> system-view
[HUAWEI] snmp-agent trap enable feature-name efm trap-name nonthreshold

test-packet start

Function

The test-packet start command configures the device to send test packets.

Format

test-packet start interface interface-type interface-number [ -c count | -s size ] *

Parameters

Parameter Description Value
interface-type interface-number

Specifies the outbound interface of test packets.

  • interface-type specifies the interface type.

  • interface-number specifies the interface number.

-
-c count

Specifies the number of test packets to be sent.

The value is an integer that ranges from 1 to 65535. The default value is 5.
-s size

Specifies the length of a test packet.

The value is an integer that ranges from 64 to 1518, in bytes. The default value is 64 bytes.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After remote loopback is enabled on the device, run the test-packet start command on an interface in active mode to configure the device to send test packets. Then check link connectivity and performance based on returned test packets.

Press Ctrl+C to stop sending test packets. After using this command to send test packets, use the display test-packet result command to view the test result.

Precautions

During test packet transmission, parameters of sent test packets cannot be changed.

Example

# Send test packets from outbound interface GigabitEthernet1/0/1.
<HUAWEI> system-view
[HUAWEI] test-packet start interface gigabitethernet 1/0/1
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065659

Views: 114386

Downloads: 83

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next