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

NE20E-S2 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - LAN Access and MAN 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).
Configuring ERPSv1

Configuring ERPSv1

ERPS eliminates loops on an Ethernet ring network when no faulty links exist and promptly restores communication if a link fault occurs. ERPSv1 supports only single rings.

Usage Scenario

Generally, redundant links are used to access an upper-layer network to provide link backup and enhance network reliability. The use of redundant links, however, may produce loops, causing broadcast storms and rendering the MAC address table unstable. As a result, the communication quality deteriorates, and communication services may even be interrupted. To resolve these problems, ERPS can be used for loop avoidance purposes. ERPS blocks redundant links under normal conditions and unblocks them to promptly restore communication if a link fault occurs. ERPSv1 and ERPSv2 are currently available. As ERPSv2 is fully compatible with ERPSv1, configuring ERPSv2 is recommended if all devices on an ERPS ring support both ERPSv1 and ERPSv2. If any devices on an ERPS ring support only ERPSv1, configure ERPSv1 on all devices on the ring.

NOTE:

ERPS and other ring network protocols, such as Spanning Tree Protocol (STP) and Smart Link, cannot run on the same port.

Pre-configuration Tasks

Before configuring ERPSv1, complete the following tasks:

  • Establish a ring network.

  • Connect interfaces and set their physical parameters to ensure that the physical status of the interfaces is Up.

Configuration Procedures

Figure 11-5 Flowchart for configuring ERPSv1

Configuring an ERPS Ring

A ring is the basic ERPS unit. After an ERPS ring is configured, ERPS runs to block redundant links and eliminate loops on Layer 2 networks.

Context

Perform the following operations to configure an ERPS ring:
  1. Create an ERPS ring.
  2. (Optional) Configure a description for the ERPS ring. The description can contain the ERPS ring ID.
  3. Configure a control VLAN for the ERPS ring. A control VLAN is different from a data VLAN that transmits service packets. On ERPS rings, a control VLAN is used to transmit Ring Auto Protection Switching (R-APS) Protocol Data Units (PDUs), also called the ERPS protocol packets. A control VLAN does not transmit service packets, enhancing ERPS security.

    All routers on an ERPS ring must use the same control VLAN. Different ERPS rings cannot have the same control VLAN.

  4. Configure an ERP instance and map the instance to a VLAN. Ports can be added to an ERPS ring only after an ERP instance is configured for the ring. VLANs can be mapped to protection instances for load balancing.
  5. Add Layer 2 ports to the ERPS rings and specify Port Role.

    Before adding a port to an ERPS ring, ensure that:
    • No spanning tree protocol is enabled on the port. If a spanning tree protocol has been enabled for a port, run the stp disable command in the interface view to disable the spanning tree protocol.

    • The port is not a Layer 3 port. If the port is a Layer 3 port, run the portswitch command to switch the port to the Layer 2 mode.

    • A control VLAN and an ERP instance have been configured for the ERPS ring to which the port will be added.

NOTE:

A ring can either has STP or ERPS enabled. If you enable ERPS, the control VLAN and data VLAN must be mapped to an Ethernet Ring Protection (ERP) instance. Otherwise, a loop may occur because STP is disabled.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run erps ring ring-id

    An ERPS ring is created, and the ERPS ring view is displayed.

    An ERPS ring can be deleted only if it does not have any port. If you attempt to delete an ERPS ring that has a port, the system prompts a deletion failure. Before deleting an ERPS ring that has a port, run the undo erps ring command in the interface view of the port or the undo port command in the ERPS ring view to remove the port from the ERPS ring. Then run the undo erps ring command to delete the ERPS ring.

  3. (Optional) Run description text

    A description is configured for the ERPS ring.

  4. Run control-vlan vlan-id

    A control VLAN is configured for the ERPS ring.

    The control VLAN specified by vlan-id must not be one that has been created or used in Smart Link protocol, VLAN mapping, VLAN stacking, port trunk allow-pass, or port default vlan applications.

    • The control VLAN for an ERPS ring cannot be modified after a port is added to the ring. Before deleting the control VLAN for an ERPS ring that has a port, run the undo erps ring command in the interface view of the port or the undo port command in the ERPS ring view to remove the port from the ERPS ring. Then run the undo control-vlan command to delete the control VLAN.

    • If an ERPS ring does not have any port, you can run the control-vlan command more than once, but only the latest configuration takes effect.

    • After a control VLAN is configured, the vlan batch vlan-id1 [ to vlan-id2 ] &<1-10> command, instead of the control-vlan command, is saved in the configuration file.

      After a port is added to an ERPS ring that has a control VLAN configured, the port is automatically added to the control VLAN, and the port trunk allow-pass vlan vlan-id command configuration is automatically generated in the interface view of this port in the configuration file.

  5. Run protected-instance { all | { instance-id1 [ to instance-id2 ] &<1-10> } }

    An ERP instance is configured for the ERPS ring.

    If you run the protected-instance command for an ERPS ring several times, all the configured ERP instances take effect.

    ERP instances for an ERPS ring cannot be modified after a port is added to the ring. Before deleting an ERP instance for an ERPS ring that has a port, run the undo erps ring command in the interface view of the port or the undo port command in the ERPS ring view to remove the port from the ERPS ring. Then run the undo protected-instance command to delete the ERP instance.

  6. Perform either of the following operations to configure the mapping between the ERP instance and VLANs and ensure that the control VLAN belongs to the configured ERP instance:

    • Configure the mapping between the instance and VLANs in the MST region view.

      1. Run the stp region-configuration command to enter the MST region view.
      2. Run the instance instance-id vlan { vlan-id [ to vlan-id ] }&<1-10> command to map VLANs to an MSTI.
      NOTE:

      A VLAN cannot be mapped to multiple MSTIs. If you map a VLAN that has already been mapped to an MSTI to another MSTI, the original mapping will be canceled.

      The vlan-mapping modulo modulo command configures the mapping between MSTIs and VLANs based on a default algorithm. However, the mapping configured using this command cannot always meet the actual demand. Therefore, running this command is not recommended.

    • Configure the mapping between the instance and VLANs in the VLAN instance view.

      1. Run the vlan instance command to enter the VLAN instance view.
      2. Run the instance instance-id vlan { vlan-id [ to vlan-id ] }&<1-10> command to map VLANs to the VLAN instance.

        NOTE:

        The vlan instance command and the stp region-configuration command are mutually exclusive. If the mapping between an MSTI and VLANs has been configured in the MST region view displayed by the stp region-configuration command, you must delete the configured mapping before using the vlan instance command.

      3. (Optional) Run the check vlan instance mapping command to check the configured mapping.

  7. Run either of the following commands to add a port to an ERPS ring and specify the port role.

    • Run the port interface-type interface-number [ rpl owner ] command in the ERPS ring view.

    • Run the erps ring ring-id [ rpl owner ] command in the interface view.

    NOTE:

    As MAC address updates cannot be separately sent currently, configuring the direct link between two upstream nodes as the RPL is not recommended.

    Before changing the port role, run the shutdown command to shut down the port. Then change the port role and run the undo shutdown command to enable the port.

  8. Run commit

    The configuration is committed.

(Optional) Configuring Timers for an ERPS Ring

To prevent the blocked port from alternating between Up and Down in case a faulty router or link on an ERPS ring recovers, enable timers for the ERPS ring to reduce the traffic interruption time.

Context

ERPS defines the following timers:
  • Guard timer

    After a faulty link or node recovers or a clear operation is executed, the nodes on the two ends of the link or the recovered node sends R-APS No Request (NR) messages to inform the other nodes of the link or node recovery and starts a guard timer. Before the timer expires, each involved node does not process any R-APS PDUs to avoid receiving out-of-date R-APS (SF) messages. After the timer expires, if the involved node still receives an R-APS (SF) message, the local port enters the Forwarding state.

  • WTR Timer

    If the RPL owner port is unblocked due to a link or node failure, the involved port may not go Up immediately after the link or node recovers. To prevent the RPL owner port from alternating between Up and Down, the node where the RPL owner port resides starts a WTR timer after receiving an R-APS (NR) message. If the node receives an R-APS Signal Fail (SF) message before the timer expires, it terminates the WTR timer (R-APS SF message: a message sent by a node to other nodes after the node in an ERPS ring detects that one of its ring ports becomes Down). If the node does not receive any R-APS (SF) message before the timer expires, it blocks the RPL owner port when the timer expires and sends an R-APS (NR, RB) message. After receiving this R-APS (NR, RB) message, the nodes set their recovered ports on the ring to the Forwarding state.

  • Hold-off timer

    Protection switching sequence requirements vary for Layer 2 networks running ERPS. For example, in a multi-layer service application, a certain period of time is required for a server to recover should it fail. (During this period, no protection switching is performed, and the client does not detect the failure.) A hold-off timer can be set to ensure that the server is given adequate time to recover. If a fault occurs, the fault is not immediately reported to ERPS. Instead, the hold-off timer starts. If the fault persists after the timer expires, the fault will be reported to ERPS.

  • WTB timer

    The WTB timer starts after an FS or MS operation is performed. When multiple nodes on an ERPS ring are in the FS or MS state, the clear operation takes effect only after the WTB timer expires. This ensures that the RPL owner port will not be blocked immediately.

    The WTB timer value cannot be configured. Its value is the guard timer value plus 5.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run erps ring ring-id

    The ERPS ring view is displayed.

  3. Run the following commands to configure one or more timers for the ERPS ring:

    • To configure the WTR timer, run the wtr-timer time-value command.

    • To configure the guard timer, run the guard-timer time_value_cs command.

    • To configure the hold-off timer, run the holdoff-timer time-value command.

  4. Run commit

    The configuration is committed.

(Optional) Configuring Association Between ERPS and Ethernet CFM

Association between Ethernet CFM and ERPS on an ERPS ring port helps promptly detect failures, converge topologies, and shorten the traffic interruption time. Currently, ERPS can be associated only with outward-facing MEPs.

Prerequisites

Ethernet CFM has been configured on an ERPS ring port. For details, see CFM Configuration.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run erps ring ring-id track cfm md md-name ma ma-name mep mep-id remote-mep rmep-id

    ERPS is associated with Ethernet CFM to promptly detect link failures.

    The association between ERPS and CFM takes effect only when the interface has ERPS associated with CFM and has an interface-based MEP created using the mep mep-id command.

  4. Run commit

    The configuration is committed.

Follow-up Procedure

After ERPS is associated with Ethernet CFM, ensure that the maintenance entity group level (MEL) in R-APS PDUs on ERPS rings is higher than that in CFM protocol packets. Otherwise, Ethernet CFM cannot allow R-APS PDUs to pass through. When ERPS is used for communication between Huawei and non-Huawei devices, the same MEL also allows them to communicate smoothly.

You can run the raps-mel level-id command in the ERPS ring view to set the MEL in R-APS PDUs.

Verifying the ERPSv1 Configuration

After configuring ERPSv1, verify the configuration of ports added to an ERPS ring, port roles, control VLAN ID, ERP instances, WTR timer, and guard timer.

Prerequisites

ERPSv1 has been configured.

Procedure

  • Run the display erps [ ring ring-id ] [ verbose ] command to check configurations of router ports added to an ERPS ring and ring configurations.

Example

Run the display erps [ ring ring-id ] command. The command output shows configurations of the router ports added to an ERPS ring and ring configurations.

<HUAWEI> display erps ring 1
D : Discarding
F : Forwarding
R : RPL owner
N  : RPL Neighbour                                                              
FS : Forced Switch                                                              
MS : Manual Switch
Ring  Control  WTR Timer  Guard Timer  Port 1              Port 2
ID    VLAN     (min)      (csec)
-----------------------------------------------------------------------
   1       10          6          100  (F)GE0/1/1          (D,R)GE0/1/2
-----------------------------------------------------------------------

Run the display erps [ ring ring-id ] [ verbose ] command. The command output shows detailed configurations of the router ports added to an ERPS ring and ring configurations.

<HUAWEI> display erps ring 1 verbose
Ring ID                             : 1
Description                         : Ring 1
Control Vlan                        : 10
Protected Instance                  : 1
Service Vlan                        : 100 to 200
WTR Timer Setting (min)             : 6      Running (s)           : 0
Guard Timer Setting (csec)          : 100    Running (csec)        : 0
Holdoff Timer Setting (deciseconds) : 0      Running (deciseconds) : 0
WTB Timer Running (csec)            : 0
Ring State                          : Idle
RAPS_MEL                            : 7
Revertive Mode                      : Revertive                                 
R-APS Channel Mode                  : -                                         
Version                             : 1                                         
Sub-ring                            : No                                        
Forced Switch Port                  : -                                         
Manual Switch Port                  : -                                         
TC-Notify                           : - 
Time since last topology change     : 0 days 0h:33m:4s
-----------------------------------------------------------------------
Port                Port Role     Port Status     Signal Status
-----------------------------------------------------------------------
GE0/1/1             Common        Forwarding      Non-failed
GE0/1/2             RPL Owner     Discarding      Non-failed 
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055378

Views: 16364

Downloads: 34

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