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

ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is ME60 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 ERPSv2

Configuring ERPSv2

ERPS eliminates loops on an Ethernet ring network when no faulty links exist and promptly restores communication if a link fault occurs. ERPSv2, compatible with ERPSv1, supports multi-ring topologies and association with CFM, in addition to ERPSv1 functions, such as single ring topologies and multi-instance.

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. As ERPSv1 supports only single ring topologies, ERPSv2 that supports multi-ring topologies can be used on the multi-ring network shown in Figure 11-6.

Figure 11-6 ERPSv2 multi-ring network

NOTE:

ERPS and other ring network protocols, such as STP and Smart Link, cannot run on the same port.

Pre-configuration Tasks

Before configuring ERPSv2, 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-7 Flowchart for configuring ERPSv2

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. Specify ERPSv2.

    ERPSv2 has the following additional functions compared with ERPSv1:
    • Supports multi-ring topologies, such as intersecting rings.
    • Allows sub-rings to use either VCs or NVCs to transmit R-APS PDUs.
    • Supports two manual port blocking modes: FS and MS.
    • Supports both revertive and non-revertive switching.
  6. Configure major rings and sub-rings.

    By default, an ERPS ring is a major ring. When you deploy ERPS on a multi-ring network, you must configure some rings as sub-rings and set the R-APS PDU Transmission Mode on Sub-rings.

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

    • ERPSv2 has been specified for the ERPS ring if the port will be specified as an RPL neighbor port.
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 version v2

    ERPSv2 is specified.

    Before specifying ERPSv1 for an ERPSv2-running device, delete all ERPS configurations that ERPSv1 does not support.

  8. (Optional) Run sub-ring

    The ERPS ring is configured as a sub-ring.

    An ERPS ring cannot be configured as a sub-ring after a port is added to the ring. Before configuring an ERPS ring that has a port as a sub-ring, 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 sub-ring command to configure the ERPS ring as a sub-ring.

    NOTE:

    Major rings are closed, and sub-rings are open.

  9. (Optional) Run virtual-channel enable

    The R-APS PDU transmission mode is specified for the sub-ring.

    This step is needed only for a sub-ring.

    If the VC mode is used for sub-ring R-APS PDU transmission, it is recommended that the major ring's VLAN with an ID same as that of the sub-ring's control VLAN transmit only sub-ring R-APS PDUs. If this major ring's VLAN also transmits data packets, attackers may construct bogus sub-ring R-APS PDUs, causing sub-ring loops or even a major ring failure.

  10. 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 | neighbour } ] command in the ERPS ring view.

    • Run the erps ring ring-id [ rpl { owner | neighbour } ] 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.

  11. Run commit

    The configuration is committed.

Configuring Topology Change Notification

The topology change notification function configured on the interconnection nodes of intersecting ERPS rings allows one ERPS ring to notify the other ERPS rings of its topology change. Then all routers on the other ERPS rings clear their MAC and ARP entries and relearn MAC addresses from the ring with a topology change. This function ensures that user traffic is not interrupted.

Context

If an upper-layer Layer 2 network is not notified of the topology change in an ERPS ring, the MAC address entries remain unchanged on the upper-layer network and therefore user traffic is interrupted. To ensure traffic transmission, you can configure the topology change notification function and specify the ERPS rings that will be notified of the topology change.

However, if an ERPS ring frequently receives topology change notification messages, its nodes will have lower CPU processing capability and repeatedly update Flush-FDB packets, consuming significant bandwidth. To resolve this problem, suppress the transmission of topology change notification messages. You can set the topology change protection interval at which topology change notification messages are sent to suppress the number of transmissions, and set the maximum number of topology change notification messages that can be processed during the topology change protection interval to prevent frequent MAC and ARP updates.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run erps ring ring-id

    The ERPS ring view is displayed.

  3. Run tc-notify erps ring { ring-id1 [ to ring-id2 ] } &<1-10>

    The ERPS ring is configured to notify other ERPS rings of its topology change.

    ring-id1 [ to ring-id2 ] specifies the start and end ring IDs of the ERPS rings that will be notified of the topology change. Ensure that the ERPS rings specified by ring-id1 and ring-id2 exist. If the specified rings do not exist, the topology change notification function does not take effect.

    After the ERPS rings receive the topology change notification from an ERPS ring, they send Flush-FDB messages on their separate rings to instruct their routers to update MAC addresses so that user traffic is not interrupted.

  4. (Optional) Run tc-protection interval interval-value

    The topology change protection interval at which topology change notification messages are sent is set.

  5. (Optional) Run tc-protection threshold threshold-value

    The maximum number of topology change notification messages that can be processed during the topology change protection interval is set.

    The topology change protection interval is the one specified by the tc-protection interval command.

  6. Run commit

    The configuration is committed.

(Optional) Configuring ERPS Protection Switching

To ensure that ERPS rings function normally when a router or link fails, you can set ERPS protection switching functions, such as revertive and non-revertive switching, port blocking modes, and timers.

Context

  • Revertive and non-revertive switching

    After link faults are rectified, whether to re-block the RPL owner port depends on the switching mode.

  • Port blocking mode

    In case the RPL has high bandwidth, blocking a link with low bandwidth and unblocking the RPL allow traffic to use the RPL and have more bandwidth. ERPS supports two manual port blocking modes: FS and MS. FS takes precedence over MS. An existing FS or MS operation can be cleared using the clear command. The clear command also has the following functions:
    • Triggers revertive switching before the WTR or WTB timer expires in the case of revertive operations.
    • Triggers revertive switching in the case of non-revertive operations.
  • Timer

    ERPS defines four timers: guard timer, hold-off timer, WTR timer, and WTB timer. The WTB timer value cannot be configured. Its value is the guard timer value plus 5. The default WTB timer value is 7s.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run erps ring ring-id

    The ERPS ring view is displayed.

  3. Run revertive { enable | disable }

    The protection switching mode is specified.

  4. Perform either of the following operations to configure a port blocking mode:

    • To configure a port blocking mode for a port in the ERPS ring view, run the port interface-type interface-number protect-switch { force | manual } command.

    • To configure a port blocking mode in the interface view, perform the following steps:

      1. Run the quit command to return to the system view.

      2. Run the interface interface-type interface-number command to enter the interface view.

      3. Run the erps ring ring-id protect-switch { force | manual } command to configure a port blocking mode for the port.

        The ERPS ring specified by ring ring-id must be the one to which the port belongs.

      4. Run the quit command to return to the system view.

    To clear the specified port blocking mode, run the clear command in the ERPS ring view.

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

  6. 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 ERPSv2 Configuration

After configuring ERPSv2, verify the configuration of ports added to an ERPS ring, port roles, control VLAN ID, ERP instances, ERPS version, and timers.

Prerequisites

ERPSv2 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.
  • Run the display erps interface interface-type interface-number [ ring ring-id ] command to check physical configurations of an ERPS ring port.

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        1          5          200  (D)Eth-Trunk1        -                   
--------------------------------------------------------------------------------

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                        : 1                                         
Protected Instance                  : 0 to 4094                                 
Service Vlan                        : 2 to 4094
WTR Timer Setting (min)             : 5      Running (s)           : 0          
Guard Timer Setting (csec)          : 200    Running (csec)        : 0          
Holdoff Timer Setting (deciseconds) : 100    Running (deciseconds) : 0          
WTB Timer Running (csec)            : 0                                         
Ring State                          : Pending                                   
RAPS_MEL                            : 7                                         
Revertive Mode                      : Revertive                                 
R-APS Channel Mode                  : -                                         
Version                             : 2                                         
Sub-ring                            : No                                        
Forced Switch Port                  : -                                         
Manual Switch Port                  : -                                         
TC-Notify                           : -                                         
Time since last topology change     : 0 days 1h:14m:38s                         
--------------------------------------------------------------------------------
Port                Port Role     Port Status     Signal Status                 
--------------------------------------------------------------------------------
Eth-Trunk1          Common        Discarding      Non-failed

Run the display erps interface interface-type interface-number [ ring ring-id ] command. The command output shows physical configurations of an ERPS ring port.

<HUAWEI> display erps interface Eth-Trunk 1 ring 1
Interface State                    : Up
--------------------------------------------------------------------------------
Ring ID                            : 1                                          
Flush Logic                                                                     
    Remote Node ID                 : 0000-0000-0000                             
    Remote BPR                     : 0                                          
Track Link Detect Protocol         : 1AG                                        
    MD Name                        : 1                                          
    MA Name                        : 1                                          
    MEP ID                         : 2270                                       
    RMEP ID                        : 2260                                       
    CFM State                      : Failed
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 26616

Downloads: 18

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