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

NE40E-M2 V800R010C10SPC500 Configuration Guide - WAN Access 01

This is NE40E-M2 V800R010C10SPC500 Configuration Guide - WAN Access
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).
Specifying a Working Interface and a Protection Interface for an LMSP Group

Specifying a Working Interface and a Protection Interface for an LMSP Group

A working interface and a protection interface must be specified and added to an LMSP group before other LMSP configurations are performed.

Context

An LMSP group includes one working interface and one protection interface. An LMSP group is the smallest unit protected by LMSP. The communication messages between the working interface and the protection interface are transmitted within the LMSP group. Specifying a working interface and a protection interface and adding them to an LMSP group are the prerequisites for LMSP operation. The working interface is connected to a working link and the protection interface is connected to a protection link. When an LMSP group works in 1:1 mode, the working interface transmits traffic, but the protection interface does not. The protection interface takes over traffic after LMSP switching is performed. When an LMSP group works in 1+1 mode, both the working and protection interfaces transmit traffic. The receive end receives traffic only from the working link.

Perform the following steps on the Routers where the LMSP working and protection interface are located separately:

Procedure

  1. Specify an LMSP working interface.
    1. Run system-view

      The system view is displayed.

    2. Run the following commands to display the interface view:

      controller cpos cpos-number

    3. Run aps group group-id

      An LMSP group is created, and an interface is added to the LMSP group.

    4. Run aps working peer-ip local-ip

      The interface added to the LMSP group is specified as a working interface.

  2. Specify an LMSP protection interface.
    1. Run system-view

      The system view is displayed.

    2. Run the following commands to display the interface view:

      controller cpos cpos-number

    3. Run aps group group-id

      An LMSP group is created, and an interface is added to the LMSP group.

      NOTE:
      The working and protection interfaces must be added to a single LMSP group.

    4. Run aps protect peer-ip local-ip

      The interface added to the LMSP group is specified as a protection interface.

    5. (Optional) Run aps signal-low-priority

      The low-priority signal failure code for a switching request carried in the K byte is specified on the protection interface.

  3. In MC-LMSP 1+1 unidirectional mode, run:

    hold-up

    The interface is configured to remain Up.

    This command is used on the working and protection interfaces of the LMSP group that works in MC-LMSP 1+1 unidirectional mode.

    MC-LMSP 1+1 needs to be associated with dual bypass PWs. In MC-LMSP 1+1 unidirectional mode, if an AC-side interface is Down, one of the bypass PWs associated with the interface will be deleted. Then traffic will not be forwarded by the deleted bypass PW. To address this problem, the hold-up command must be run on an MC-LMSP interface.

    NOTE:

    After this command has been run, the alarm functions do not take effect on the LMSP group interface, the link indicator on the LMSP group interface is always on, and the interface remains Up even when no fiber is attached to it.

  4. Run commit

    The configuration is committed.

Download
Updated: 2019-01-02

Document ID: EDOC1100058399

Views: 15128

Downloads: 39

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