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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Configuring EFM

Configuring EFM

This section describes how to configure EFM.

Configuring Basic EFM Functions

This section describes how to configure basic EFM functions to monitor the link.

Enabling EFM Globally

Context

Before configuring basic EFM functions, enable EFM globally.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    efm enable

    EFM is enabled globally.

    By default, EFM is disabled globally.

  3. Run:

    commit

    The configuration is committed.

(Optional) Setting the EFM Working Mode on an Interface

Context

EFM supports two connection modes: active and passive. Table 11-37 describes the differences between the active and passive modes.

Table 11-37 Capabilities for processing OAMPDUs in active and passive modes

Action

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

EFM can be configured on Layer 2 and Layer 3 Ethernet interfaces.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The view of the interface at one end of the link is displayed.

  3. Run:

    efm mode { active | passive }

    The EFM working mode on the interface is configured.

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

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

    • When using EFM to monitor a link, ensure that either of the interfaces at both ends of the link operates in active mode.
      • If both ends of a link are configured to work in active EFM mode, link detection can be implemented.

      • If both ends of a link are configured to work in passive mode, link detection cannot be implemented.

  4. Run:

    commit

    The configuration is committed.

(Optional) Setting EFM OAMPDU Parameters

Context

EFM entities exchange OAMPDUs periodically to report the link status. The network administrator can set EFM OAMPDU parameters to effectively manage networks.

EFM OAMPDU parameters include the maximum OAMPDU size and timeout interval at which OAMPDUs are received.
  • After the maximum OAMPDU size is set on an interface, the interface considers excess EFM OAMPDUs invalid and discards them.

  • After setting up an EFM connection, two EFM entities exchange OAMPDUs at a specific interval to check whether the connection is working properly. If an EFM entity does not receive any OAMPDU from its remote EFM entity within the interval at which OAMPDUs are received, it considers that the link is not working properly. The network administrator can set different intervals at which OAMPDUs are received based on user requirements. A short interval can be set for high-priority or delay-sensitive services. A long interval can be set for low-priority or delay-insensitive services.

EFM can be configured on Layer 2 and Layer 3 Ethernet interfaces. By default, an Etherent interface works in Layer 2 mode. Before configuring EFM on a Layer 3 Ethernet interface, switch the Ethernet interface to Layer 3 mode.

Perform the following steps on the interfaces at both ends of a link.

Procedure

  • Setting the maximum size of an EFM OAMPDU

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The view of the interface at one end of the link is displayed.

    3. Run:

      efm packet max-size size

      The maximum size of an EFM OAMPDU is set.

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

      If the maximum EFM OAMPDU sizes configured on the interfaces at both ends of a link are different, the interfaces negotiate the maximum EFM OAMPDU size during the discovery process. The smaller one between the maximum EFM OAMPDU sizes on the two ends is used.

    4. Run:

      commit

      The configuration is committed.

  • Setting the timeout interval at which EFM OAMPDUs are received

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The view of the interface at one end of the link is displayed.

    3. Run:

      efm timeout timeout-value

      The timeout interval at which EFM OAMPDUs are received is set.

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

      The interfaces at both ends of a link must use the same timeout interval. Otherwise, session negotiation between the two interfaces fails or the session flaps.

      NOTE:

      The timeout interval is set only after EFM is enabled globally but before EFM is enabled on an interface.

    4. Run:

      commit

      The configuration is committed.

Enabling EFM on an Interface

Context

After EFM is enabled on interfaces connecting local and remote EFM entities, the two entities start to set up an EFM connection to monitor the connectivity of the link between them.

EFM can be configured on Layer 2 and Layer 3 Ethernet interfaces. By default, an Etherent interface works in Layer 2 mode. Before configuring EFM on a Layer 3 Ethernet interface, switch the Ethernet interface to Layer 3 mode.

NOTE:

Eth-Trunks do not support EFM.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The view of the interface at one end of the link is displayed.

  3. Run:

    efm enable

    EFM is enabled on the interface.

    By default, EFM is disabled on an interface.

    NOTE:

    Before using this command, ensure that EFM has been enabled globally using the efm enable command.

  4. Run:

    commit

    The configuration is committed.

Checking the Configuration

Prerequisites

The configuration of basic EFM functions is complete.

Procedure

  • Run the display efm { all | interface interface-type interface-number } command to check the EFM configuration.
  • Run the display efm session { all | interface interface-type interface-number } command to check the EFM protocol status.

Configuring EFM Link Monitoring

After link monitoring is configured, the network administrator can detect link layer faults in various environments and dynamically monitor link quality.

Detecting Minor Link Events

Context

If an EFM entity receives a link event, it sends an Event Notification OAMPDU to notify the remote EFM entity of the event.

Select one or more detection methods to monitor links based on as needed.

EFM can be configured on Layer 2 and Layer 3 Ethernet interfaces. By default, an Etherent interface works in Layer 2 mode. Before configuring EFM on a Layer 3 Ethernet interface, switch the Ethernet interface to Layer 3 mode.

Procedure

  • Detecting errored code events

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      efm enable

      EFM is enabled globally.

    3. Run:

      interface interface-type interface-number

      The view of the interface at one end of the link is displayed.

    4. Run:

      efm error-code period period

      The period for detecting EFM errored codes is set.

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

    5. Run:

      efm error-code threshold threshold

      The threshold for detecting EFM errored codes is set.

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

    6. Run:

      efm enable

      EFM is enabled on the interface.

    7. Run:

      efm error-code notification enable

      The interface is enabled to detect EFM errored codes.

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

    8. Run:

      commit

      The configuration is committed.

  • Detecting errored frame events

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      efm enable

      EFM is enabled globally.

    3. Run:

      interface interface-type interface-number

      The view of the interface at one end of the link is displayed.

    4. Run:

      efm error-frame period period

      The period for detecting EFM errored frames is set.

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

    5. Run:

      efm error-frame threshold threshold

      The threshold for detecting EFM errored frames is set.

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

    6. Run:

      efm enable

      EFM is enabled on the interface.

    7. Run:

      efm error-frame notification enable

      The interface is enabled to detect EFM errored frames.

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

    8. Run:

      commit

      The configuration is committed.

  • Detecting errored frame seconds

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      efm enable

      EFM is enabled globally.

    3. Run:

      interface interface-type interface-number

      The view of the interface at one end of the link is displayed.

    4. Run:

      efm error-frame-second period period

      The period for detecting EFM errored frame seconds is set.

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

    5. Run:

      efm error-frame-second threshold threshold

      The threshold for detecting EFM errored frame seconds is set.

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

    6. Run:

      efm enable

      EFM is enabled on the interface.

    7. Run:

      efm error-frame-second notification enable

      The interface is enabled to detect errored frame seconds.

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

    8. Run:

      commit

      The configuration is committed.

Checking the Configuration

Prerequisites

The link monitoring configuration is complete.

Procedure

  • Run the display efm { all | interface interface-type interface-number } command to check the EFM configuration.

Configuring Remote Loopback

Remote loopback is used to test link connectivity and performance.

Configuring Remote Loopback On the Device in Active Mode

Context

Remote loopback mainly tests connectivity and quality of a single link. On the network shown in Figure 11-98, remote loopback is configured on the interface connecting the SwitchA to the PE. The interface sends test packets to its remote interface. The packet loss ratio and delay can be calculated based on returned test packets to evaluate link connectivity and performance.

Figure 11-98 Remote loopback
NOTE:
  • Remote loopback can only be initiated by an interface in active EFM mode.

  • Remote loopback affects data service forwarding. Therefore, it is recommended that you enable remote loopback to check link connectivity and quality before a new network is used or a link fault is rectified.

  • After the undo efm enable command is executed in the system view to disable EFM, all the EFM configuration is deleted. If remote loopback is performed on the device and many test packets are sent, running the undo efm enable command may cause test packets to be forwarded. As a result, network bandwidth is occupied.

EFM can be configured on Layer 2 and Layer 3 Ethernet interfaces. By default, an Etherent interface works in Layer 2 mode. Before configuring EFM on a Layer 3 Ethernet interface, switch the Ethernet interface to Layer 3 mode.

Pre-configuration Tasks
Before configuring remote loopback, complete the following tasks:

Procedure

  1. Enabling remote loopback on the device that initiates a request

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The view of an interface in active EFM mode is displayed.

    3. Run:

      efm loopback start [ timeout timeout ]

      The interface is configured to initiate remote loopback.

      By default, the timeout interval for remote loopback is 20 minutes. After 20 minutes, remote loopback is disabled automatically. You are advised not to set the timeout interval to 0. If the timeout interval is set to 0, the link retains in remote loopback state.

      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 run the display efm session { all | interface interface-type interface-number } command to check whether the EFM status on both devices is detect. The display efm { all | interface interface-type interface-number } command can be used to check the EFM modes of the interfaces at both ends of a link.

  2. Configuring the interface in active EFM mode to send test packets

    NOTE:

    Only one interface can send EFM test packets at one time.

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

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

      The device is configured to send test packets.

      By default, the size of a test packet is 64 bytes, the rate at which test packets are sent is 1 Mbit/s, and the number of sent packets is 5. During test packet transmission, parameters of sent test packets cannot be changed.

      The outbound interface of test packets should be the interface connected to the link to be tested.

      Press Ctrl+C to stop sending test packets.

  3. Disabling remote loopback

    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The interface view is displayed.

    3. Run:

      efm loopback stop

      Remote loopback is disabled on the interface.

      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. After the timeout interval expires, the local device automatically sends a message to instruct the remote device to disable remote loopback. To disable remote loopback manually, perform the preceding procedures.

(Optional) Configure a receiving device to ignore remote loopback requests

Context

If an interface is in loopback state, the interface loops back all received traffic, causing service interruption and imposing attacks. To solve the problem, configure the local device to ignore remote loopback requests.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The interface view is displayed.

  3. Run:

    efm loopback ignore-request

    The interface is configured to ignore remote loopback requests.

    By default, the local device processes remote loopback requests.

  4. Run:

    commit

    The configuration is committed.

Checking the Configuration

Prerequisites

  1. The configuration of basic EFM functions is complete.

  2. After EFM test packets are sent.

Procedure

  • Run:

    display efm test-packet result

    The information about sent test packets is displayed.

Associating EFM with an Interface

You can associate EFM with an interface to perform rapid service switchovers.

Usage Scenario

A device is usually connected to an IP network over the primary and backup links to improve network robustness and service reliability. 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 EFM Down, speeding up routing convergence. Traffic can be fast switched to the backup link.

After EFM is associated with an interface, you can adjust the delay in changing the EFM status of an interface from Down to Up by setting the time during which the EFM status of the interface remains Down, if a link connectivity fault is rectified.

Pre-configuration Tasks

Before associating EFM with an interface, Configuring Basic EFM Functions.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The view of the interface at one end of a link is displayed.

  3. Run:

    efm trigger if-down

    EFM is associated with the interface.

    By default, EFM is not associated with any interface.

  4. (Optional) Run:

    efm holdup-timer time

    The time during which the EFM status of the interface remains Down is set.

    The default time is 0 seconds.

    If the parameter time is not specified, the EFM status of an interface immediately changes from Down to Up when a link connectivity fault is rectified. If the parameter time is specified, the EFM status of an interface changes from Down to Up only when a link connectivity fault is rectified and after the time specified by the parameter time elapses. Setting the parameter time can reduce link flapping. You can run the recover efm-down command to change the EFM status of an interface from Down to Up.

  5. Run:

    commit

    The configuration is committed.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 57931

Downloads: 3621

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