HPE FlexNetwork 5130 HI SERIES Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. FlexNetwork 5130 HI SERIES
  6. Configuration manual

HPE FlexNetwork 5130 HI SERIES Configuration Manual

Hide thumbs Also See for FlexNetwork 5130 HI SERIES:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual
HPE FlexNetwork 5130 HI Switch Series

High Availability

Configuration Guide

Part number: 5200-3603
Software version: Release 13xx
Document version: 6W100-20170315

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FlexNetwork 5130 HI SERIES and is the answer not in the manual?

Questions and answers

Related Manuals for HPE FlexNetwork 5130 HI SERIES

Summary of Contents for HPE FlexNetwork 5130 HI SERIES

  • Page 1: High Availability

    HPE FlexNetwork 5130 HI Switch Series High Availability Configuration Guide Part number: 5200-3603 Software version: Release 13xx Document version: 6W100-20170315...
  • Page 2 © Copyright 2015, 2017 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Contents Configuring CFD ·············································································· 1     Overview ·································································································································· 1   Basic CFD concepts ············································································································ 1   CFD functions ····················································································································· 3   EAIS ································································································································· 5   Protocols and standards ······································································································· 5   CFD configuration task list ··········································································································· 5   Configuring basic CFD settings ····································································································· 6  ...
  • Page 4   Configuring RRPP nodes ···································································································· 47   Activating an RRPP domain ······································································································· 48   Configuring RRPP timers ··········································································································· 49   Configuring an RRPP ring group ································································································· 49   Enabling SNMP notifications for RRPP ························································································· 50   Displaying and maintaining RRPP ······························································································· 50  ...
  • Page 5   Configuring collaboration between Smart Link and Track ························································· 134   Configuring an associated device ······························································································ 135   Configuration prerequisites ································································································ 135   Enabling the receiving of flush messages ············································································· 135   Displaying and maintaining Smart Link ······················································································· 136   Smart Link configuration examples ····························································································...
  • Page 6   Process ························································································································· 186   1:N process redundancy ··································································································· 186   Process placement policy and optimization ··········································································· 186   Configuration restrictions and guidelines ····················································································· 187   Process placement configuration task list ···················································································· 187   Configuring process placement policy ························································································ 188  ...

  • Page 7: Configuring Cfd

    Configuring CFD Overview Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management (CFM) and ITU-T Y.1731, is an end-to-end per-VLAN link layer OAM mechanism. CFD is used for link connectivity detection, fault verification, and fault location. Basic CFD concepts Maintenance domain A maintenance domain (MD) defines the network or part of the network where CFD plays its role.
  • Page 8 Maintenance point An MP is configured on a port and belongs to an MA. MPs include the following types: maintenance association end points (MEPs) and maintenance association intermediate points (MIPs). • MEPs define the boundary of the MA. Each MEP is identified by a MEP ID. The MA to which a MEP belongs defines the VLAN of packets sent by the MEP.

  • Page 9: Cfd Functions

    • A level 5 MIP. • A level 3 inward-facing MEP. • A level 2 inward-facing MEP. • A level 0 outward-facing MEP. Figure 3 CFD grading example Device A Device B Device C Device D Device E Device F Port 1 Inward-facing MEP (number is MD level) Interface...
  • Page 10 MEP, the link state between the two can be verified. LBM frames are multicast and unicast frames. The switch supports sending and receiving unicast LBM frames and receiving multicast LBM frames. HPE devices do not support sending multicast LBM frames. LBR frames are unicast frames.

  • Page 11: Eais

    Calculates the link transmission delay and jitter according to the DMR reception time and DMM transmission time. DMM frames and DMR frames are unicast frames. The TST function tests the bit errors between two MEPs. The source MEP sends a TST frame, which carries the test pattern, such as pseudo random bit sequence (PRBS) or all-zero, to the target MEP.

  • Page 12: Configuring Basic Cfd Settings

    Tasks at a glance • (Required.) Configuring CC • (Optional.) Configuring LB • (Optional.) Configuring LT • (Optional.) Configuring AIS • (Optional.) Configuring LM • (Optional.) Configuring one-way DM • (Optional.) Configuring two-way DM • (Optional.) Configuring TST (Optional.) Configuring EAIS Typically, a port blocked by the spanning tree feature cannot receive or send CFD messages except in the following cases: •...

  • Page 13: Configuring Meps

    Configuring MEPs CFD is implemented through various operations on MEPs. As a MEP is configured on an Ethernet service instance, the MD level and VLAN attribute of the Ethernet service instance become the attribute of the MEP. Before creating MEPs, configure the MEP list. A MEP list is a collection of local MEPs that can be configured in an MA and the remote MEPs to be monitored.

  • Page 14: Configuring Cfd Functions

    Step Command Remarks create any MIP. Configuring CFD functions Configuration prerequisites Complete basic CFD settings. Configuring CC Configure CC before you use the MEP ID of the remote MEP to configure other CFD functions. This restriction does not apply when you use the MAC address of the remote MEP to configure other CFD functions.

  • Page 15: Configuring Lb

    Configuring LB The LB function can verify the link state between the local MEP and the remote MEP or MIP. To configure LB on a MEP: Task Command Remarks cfd loopback service-instance instance-id mep mep-id Enable LB. { target-mac mac-address | Available in any view.

  • Page 16: Configuring Lm

    • Send the AIS frame to the MD of a higher level. If you enable AIS but do not configure a correct AIS frame transmission level, the target MEP can suppress the error alarms, but cannot send the AIS frames. To configure AIS: Step Command...

  • Page 17: Configuring Two-Way Dm

    Configuring two-way DM The two-way DM function measures the two-way frame delay, average two-way frame delay, and two-way frame delay variation between two MEPs. It also monitors and manages the link transmission performance. To configure two-way DM: Task Command Remarks cfd dm two-way service-instance instance-id mep mep-id { target-mac...

  • Page 18: Displaying And Maintaining Cfd

    If the intersection of the configured VLANs where the EAIS frames can be transmitted and the VLANs to which the port belongs is empty, no EAIS frame is sent. If the intersection contains more than 70 VLANs and the EAIS frame transmission interval is 1 second, the CPU usage will be too high. As a best practice, set the EAIS frame transmission interval to 60 seconds in this case.

  • Page 19: Cfd Configuration Example

    Task Command Display CFD status. display cfd status display cfd tst [ service-instance instance-id [ mep Display the TST result on the specified MEP. mep-id ] ] reset cfd dm one-way history [ service-instance Clear the one-way DM result on the specified MEP. instance-id [ mep mep-id ] ] reset cfd tst [ service-instance instance-id [ mep Clear the TST result on the specified MEP.
  • Page 20 Configuration procedure Configure a VLAN and assign ports to it: On each device shown in Figure 4, create VLAN 100 and assign ports GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to VLAN 100. Enable CFD: # Enable CFD on Device A. <DeviceA> system-view [DeviceA] cfd enable # Configure Device B through Device E in the same way Device A is configured.
  • Page 21 [DeviceD-GigabitEthernet1/0/1] cfd mep 4001 service-instance 2 outbound [DeviceD-GigabitEthernet1/0/1] quit # Create inward-facing MEP 4002 in Ethernet service instance 1 on GigabitEthernet 1/0/3. [DeviceD] interface gigabitethernet 1/0/3 [DeviceD-GigabitEthernet1/0/3] cfd mep 4002 service-instance 1 inbound [DeviceD-GigabitEthernet1/0/3] quit # On Device E, configure a MEP list in Ethernet service instance 1. [DeviceE] cfd meplist 1001 4002 5001 service-instance 1 # Create inward-facing MEP 5001 in Ethernet service instance 1 on GigabitEthernet 1/0/4.
  • Page 22 [DeviceB] cfd ais period 1 service-instance 2 Configure EAIS: # Enable port status-AIS collaboration on Device B. [DeviceB] cfd ais-track link-status global # On GigabitEthernet 1/0/3 of Device B, configure the EAIS frame transmission level as 5 and the EAIS frame transmission interval as 60 seconds. Specify the VLANs where the EAIS frames can be transmitted as VLAN 100.
  • Page 23 # Test the one-way frame delay from MEP 1001 to MEP 4002 in Ethernet service instance 1 on Device A. [DeviceA] cfd dm one-way service-instance 1 mep 1001 target-mep 4002 5 1DMs have been sent. Please check the result on the remote device. # Display the one-way DM result on MEP 4002 in Ethernet service instance 1 on Device D.

  • Page 24: Configuring Dldp

    Configuring DLDP Overview A link becomes unidirectional when only one end of the link can receive packets from the other end. Unidirectional fiber links occur in the following cases: • Fibers are cross-connected. • A fiber is not connected at one end or one fiber of a fiber pair is broken. Figure 5 shows a correct fiber connection and two types of unidirectional fiber connections.

  • Page 25: Basic Concepts

    Basic concepts DLDP neighbor states If port A can receive link-layer packets from port B on the same link, port B is a DLDP neighbor of port A. Two ports that can exchange packets are neighbors. Table 2 DLDP neighbor states DLDP timer Description Confirmed...

  • Page 26: How Dldp Works

    DLDP timer Description RecoverProbe packets to detect whether a unidirectional link has been restored to bidirectional. DLDP authentication mode You can use DLDP authentication to prevent network attacks and illegal detecting. Table 5 DLDP authentication mode Processing at the Authentication Processing at the DLDP packet sending side DLDP packet mode...
  • Page 27 Figure 7 Broken fiber Device A Device B Port 1 Port 2 Correct fiber connection Device A Device B Port 1 Port 2 One fiber is broken Ethernet Tx end Rx end Fiber link Broken fiber fiber port As shown in Figure 7, Device A and Device B are connected through an optical fiber.

  • Page 28: Configuration Restrictions And Guidelines

    Figure 8 Network diagram As shown in Figure 8, Device A through Device D are connected through a hub, and enabled with DLDP. When Ports 1, 2, and 3 detect that the link to Port 4 fails, they delete the neighborship with Port 4, but stay in bidirectional state.

  • Page 29: Setting The Interval To Send Advertisement Packets

    Step Command Remarks Enter system view. system-view By default, DLDP is globally Enable DLDP globally. dldp global enable disabled. Enter Ethernet interface interface interface-type view. interface-number By default, DLDP is disabled on Enable DLDP. dldp enable an interface. Setting the interval to send advertisement packets To make sure DLDP can detect unidirectional links before network performance deteriorates, set the advertisement interval appropriate for your network environment.

  • Page 30: Configuring Dldp Authentication

    • Manual mode—When DLDP detects a unidirectional link, it does not shut down the port. You must manually shut it down. When the link becomes bidirectional, you must manually bring up the port. Use this mode to prevent normal links from being shut down because of false unidirectional link reports in the following cases: The network performance is low.

  • Page 31: Dldp Configuration Examples

    DLDP configuration examples Configuring the auto port shutdown mode Network requirements As shown in Figure 9, Device A and Device B are connected through two fiber pairs. Configure DLDP to automatically shut down the faulty port upon detecting a unidirectional link, and automatically bring up the port after you clear the fault.
  • Page 32 [DeviceB-GigabitEthernet1/0/1] speed 1000 [DeviceB-GigabitEthernet1/0/1] dldp enable [DeviceB-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it. [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] duplex full [DeviceB-GigabitEthernet1/0/2] speed 1000 [DeviceB-GigabitEthernet1/0/2] dldp enable [DeviceB-GigabitEthernet1/0/2] quit # Set the port shutdown mode to auto.
  • Page 33 %Jul 11 17:40:31:677 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is DOWN. %Jul 11 17:40:31:678 2012 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is DOWN. %Jul 11 17:40:38:544 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is UP. %Jul 11 17:40:38:836 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is UP.

  • Page 34: Configuring The Manual Port Shutdown Mode

    %Jul 11 17:43:02:362 2012 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface GigabitEthernet1/0/2. The neighbor's system MAC is 0023-8956-3600, and the port index is 2. %Jul 11 17:43:02:362 2012 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface GigabitEthernet1/0/2. %Jul 11 17:43:02:368 2012 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is UP.
  • Page 35 # Enable DLDP globally. <DeviceB> system-view [DeviceB] dldp global enable # Configure GigabitEthernet 1/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it. [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] duplex full [DeviceB-GigabitEthernet1/0/1] speed 1000 [DeviceB-GigabitEthernet1/0/1] dldp enable [DeviceB-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.
  • Page 36 [DeviceA] quit <DeviceA> terminal monitor <DeviceA> terminal logging level 6 The following log information is displayed on Device A: <DeviceA>%Jul 12 08:29:17:786 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is DOWN. %Jul 12 08:29:17:787 2012 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is DOWN.

  • Page 37: Configuring The Hybrid Port Shutdown Mode

    %Jul 12 08:34:23:718 2012 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is DOWN. %Jul 12 08:34:23:778 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is DOWN. %Jul 12 08:34:23:779 2012 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is DOWN. The output shows that the port status and link status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are now down.
  • Page 38 Configure DLDP to detect unidirectional links. When a unidirectional link is detected, DLDP automatically shuts down the unidirectional port. The administrator needs to bring up the port after clearing the fault. Figure 11 Network diagram Configuration procedure Configure Device A: # Enable DLDP globally.
  • Page 39 [DeviceB-GigabitEthernet1/0/2] speed 1000 [DeviceB-GigabitEthernet1/0/2] dldp enable [DeviceB-GigabitEthernet1/0/2] quit # Set the port shutdown mode to hybrid. [DeviceB] dldp unidirectional-shutdown hybrid Verifying the configuration # Display the DLDP configuration globally and on all the DLDP-enabled ports of Device A. [DeviceA] display dldp DLDP global status: Enabled DLDP advertisement interval: 5s DLDP authentication-mode: None...
  • Page 40 %Jan 4 07:16:06:730 2011 DeviceA IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/2 changed to down. %Jan 4 07:16:06:736 2011 DeviceA IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/1 changed to down. %Jan 4 07:16:06:738 2011 DeviceA IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/2 changed to down.
  • Page 41 The output shows that the port status and link status of GigabitEthernet 1/0/1 are now up and its DLDP neighbors are determined. # Bring up GigabitEthernet 1/0/2. [DeviceA-GigabitEthernet1/0/1] quit [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] undo shutdown The following log information is displayed on Device A: [DeviceA-GigabitEthernet1/0/2]%Jan 4 07:35:26:574 2011 DeviceA IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/2 changed to up.

  • Page 42: Configuring Rrpp

    Configuring RRPP Overview Metropolitan area networks (MANs) and enterprise networks typically use the ring topology to improve reliability. However, services will be interrupted if any node in the ring network fails. A ring network typically uses Resilient Packet Ring (RPR) or Ethernet rings. RPR is high in cost because it needs dedicated hardware.
  • Page 43 RRPP ring A ring-shaped Ethernet topology is called an RRPP ring. RRPP rings include primary rings and subrings. You can configure a ring as either the primary ring or a subring by specifying its ring level. The primary ring is of level 0, and a subring is of level 1. An RRPP domain contains one or multiple RRPP rings, one serving as the primary ring and the others serving as subrings.

  • Page 44: Rrppdus

    Each master node or transit node has two ports connected to an RRPP ring, a primary port and a secondary port. You can determine the role of a port. In terms of functionality, the primary port and the secondary port of a master node have the following differences: The primary port and the secondary port are designed to play the role of sending and receiving Hello packets, respectively.

  • Page 45: Rrpp Timers

    Type Description When an RRPP ring transits to Health state, the master node sends Complete-Flush-FDB packets for the following purposes: • Complete-Flush-FDB Instruct the transit nodes, edge nodes, and assistant edge nodes to update their MAC address entries and ARP/ND entries. •...

  • Page 46: Typical Rrpp Networking

    Link down alarm mechanism In an RRPP domain, when the transit node, edge node, or assistant edge node finds that any of its ports is down, it immediately sends Link-Down packets to the master node. When the master node receives a Link-Down packet, it takes the following actions: •...
  • Page 47 Figure 13 Schematic diagram for a single-ring network Tangent rings As shown in Figure 14, two or more rings exist in the network topology and only one common node exists between rings. You must define an RRPP domain for each ring. Figure 14 Schematic diagram for a tangent-ring network Intersecting rings As shown in...
  • Page 48 Figure 15 Schematic diagram for an intersecting-ring network Dual-homed rings As shown in Figure 16, two or more rings exist in the network topology and two similar common nodes exist between rings. You need only define an RRPP domain and configure one ring as the primary ring and the other rings as subrings.

  • Page 49: Protocols And Standards

    Figure 17 Schematic diagram for a single-ring load balancing network Intersecting-ring load balancing In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains. As shown in Figure • Ring 1 is the primary ring and Ring 2 is the subring in both Domain 1 and Domain 2. •...

  • Page 50: Rrpp Configuration Task List

    RRPP configuration task list You can configure RRPP in the following order: • Create RRPP domains based on service planning. • Specify control VLANs and protected VLANs for each RRPP domain. • Determine the ring roles and node roles based on the traffic paths in each RRPP domain. RRPP does not have an auto election mechanism.

  • Page 51: Configuring Protected Vlans

    succeed, make sure the IDs of the two control VLANs are consecutive and have not been previously assigned. Follow these guidelines when you configure control VLANs: • Do not configure the default VLAN of a port accessing an RRPP ring as the control VLAN, and do not enable QinQ or VLAN mapping on control VLANs.

  • Page 52: Configuring Rrpp Rings

    Step Command Remarks Not required if the device is operating in PVST mode. Enter MST region view. stp region-configuration For more information about the command, see Layer 2—LAN Switching Command Reference. By default, all VLANs in an MST • region are mapped to MSTI 0 (the Method 1: CIST).

  • Page 53: Configuring Rrpp Nodes

    Step Command Remarks Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, the link type of an interface is access. Configure the link type of the port link-type trunk For more information about the command, interface as trunk.

  • Page 54: Activating An Rrpp Domain

    Specifying an edge node When you configure an edge node, you must configure the primary ring before configuring the subrings. To specify an edge node: Step Command Remarks Enter system view. system-view Enter RRPP domain rrpp domain domain-id view. Specify the current ring ring-id node-mode { master | device as a master transit } [ primary-port interface-type...

  • Page 55: Configuring Rrpp Timers

    To activate an RRPP domain: Step Command Remarks Enter system view. system-view Enable RRPP. rrpp enable By default, RRPP is disabled. Enter RRPP domain view. rrpp domain domain-id Enable the specified RRPP By default, an RRPP ring is ring ring-id enable ring.

  • Page 56: Enabling Snmp Notifications For Rrpp

    Step Command Remarks Enter system view. system-view Create an RRPP ring group By default, no RRPP ring groups and enter RRPP ring group rrpp ring-group ring-group-id exist. view. Assign the specified By default, no subrings are subrings to the RRPP ring domain domain-id ring ring-id-list assigned to an RRPP ring group.
  • Page 57 • Device A, Device B, Device C, and Device D form RRPP domain 1. Specify the primary control VLAN of RRPP domain 1 as VLAN 4092. Specify the protected VLANs of RRPP domain 1 as VLANs 1 through 30. • Device A, Device B, Device C, and Device D form primary ring 1.
  • Page 58 [DeviceA-GigabitEthernet1/0/2] link-delay 0 [DeviceA-GigabitEthernet1/0/2] undo stp enable [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/2] quit # Create RRPP domain 1. [DeviceA] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceA-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

  • Page 59: Intersecting Ring Configuration Example

    [DeviceB] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceB-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceB-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.
  • Page 60 Figure 20 Network diagram Domain 1 Device B GE1/0/1 GE1/0/1 Edge node Device A Master node GE1/0/3 GE1/0/2 GE1/0/2 GE1/0/1 Device E Ring 1 Ring 2 Master node GE1/0/2 GE1/0/2 GE1/0/1 Device D GE1/0/3 Transit node GE1/0/2 Device C GE1/0/1 Assistant edge node Configuration procedure Configure Device A:...
  • Page 61 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceA-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1. [DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceA-rrpp-domain1] ring 1 enable...
  • Page 62 [DeviceB-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceB-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device B as a transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.
  • Page 63 [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/3] quit # Create RRPP domain 1. [DeviceC] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceC-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device C as a transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.
  • Page 64 [DeviceD-GigabitEthernet1/0/2] quit # Create RRPP domain 1. [DeviceD] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceD-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceD-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device D as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.

  • Page 65: Dual-Homed Rings Configuration Example

    [DeviceE-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device E as the master node of subring 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 2. [DeviceE-rrpp-domain1] ring 2 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1 [DeviceE-rrpp-domain1] ring 2 enable [DeviceE-rrpp-domain1] quit...
  • Page 66 Figure 21 Network diagram Configuration procedure Configure Device A: # Create VLANs 1 through 30. <DeviceA> system-view [DeviceA] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.
  • Page 67 # Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured. [DeviceA] interface gigabitethernet 1/0/3 [DeviceA-GigabitEthernet1/0/3] link-delay 0 [DeviceA-GigabitEthernet1/0/3] undo stp enable [DeviceA-GigabitEthernet1/0/3] port link-type trunk [DeviceA-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/3] quit # Configure GigabitEthernet 1/0/4 in the same way GigabitEthernet 1/0/1 is configured. [DeviceA] interface gigabitethernet 1/0/4 [DeviceA-GigabitEthernet1/0/4] link-delay 0 [DeviceA-GigabitEthernet1/0/4] undo stp enable...
  • Page 68 [DeviceB-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port. [DeviceB-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceB-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.
  • Page 69 [DeviceB-rrpp-domain1] ring 3 node-mode assistant-edge edge-port gigabitethernet 1/0/3 [DeviceB-rrpp-domain1] ring 3 enable [DeviceB-rrpp-domain1] quit # Enable RRPP. [DeviceB] rrpp enable Configure Device C: # Create VLANs 1 through 30. <DeviceC> system-view [DeviceC] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration.
  • Page 70 # Create RRPP domain 1. [DeviceC] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceC-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device C as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.
  • Page 71 [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured. [DeviceD] interface gigabitethernet 1/0/3 [DeviceD-GigabitEthernet1/0/3] link-delay 0 [DeviceD-GigabitEthernet1/0/3] undo stp enable [DeviceD-GigabitEthernet1/0/3] port link-type trunk [DeviceD-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/3] quit # Configure GigabitEthernet 1/0/4 in the same way GigabitEthernet 1/0/1 is configured.
  • Page 72 [DeviceE-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceE] interface gigabitethernet 1/0/1 [DeviceE-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port. [DeviceE-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceE-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30.
  • Page 73 # Configure the port as a trunk port. [DeviceF-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceF-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceF-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceF] interface gigabitethernet 1/0/2 [DeviceF-GigabitEthernet1/0/2] link-delay 0 [DeviceF-GigabitEthernet1/0/2] undo stp enable...
  • Page 74 [DeviceG] interface gigabitethernet 1/0/2 [DeviceG-GigabitEthernet1/0/2] link-delay 0 [DeviceG-GigabitEthernet1/0/2] undo stp enable [DeviceG-GigabitEthernet1/0/2] port link-type trunk [DeviceG-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceG-GigabitEthernet1/0/2] quit # Create RRPP domain 1. [DeviceG] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceG-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

  • Page 75: Load-Balanced Intersecting-Ring Configuration Example

    # Create RRPP domain 1. [DeviceH] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceH-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceH-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device H as the master node of subring 5, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.
  • Page 76 Figure 22 Network diagram Configuration procedure Configure Device A: # Create VLANs 11 and 12. <DeviceA> system-view [DeviceA] vlan 11 to 12 # Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2. [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 11 [DeviceA-mst-region] instance 2 vlan 12 # Activate the MST region configuration.
  • Page 77 [DeviceA-GigabitEthernet1/0/2] undo stp enable [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 11 12 [DeviceA-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceA-GigabitEthernet1/0/2] quit # Create RRPP domain 1. [DeviceA] rrpp domain 1 # Configure VLAN 100 as the primary control VLAN of RRPP domain 1. [DeviceA-rrpp-domain1] control-vlan 100 # Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.
  • Page 78 [DeviceB-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceB-GigabitEthernet1/0/1] port link-type trunk # Remove the port from VLAN 1, and assign it to VLANs 11 and 12. [DeviceB-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 11 12 # Configure VLAN 11 as the default VLAN.
  • Page 79 [DeviceB-rrpp-domain1] control-vlan 100 # Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1. [DeviceB-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device B as a transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.
  • Page 80 # Disable the spanning tree feature on the port. [DeviceC-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceC-GigabitEthernet1/0/1] port link-type trunk # Remove the port from VLAN 1, and assign it to VLANs 11 and 12. [DeviceC-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 11 12 # Configure VLAN 11 as the default VLAN.
  • Page 81 # Configure VLAN 100 as the primary control VLAN of RRPP domain 1. [DeviceC-rrpp-domain1] control-vlan 100 # Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1. [DeviceC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device C as the transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port.
  • Page 82 # Disable the spanning tree feature on the port. [DeviceD-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceD-GigabitEthernet1/0/1] port link-type trunk # Remove the port from VLAN 1, and assign it to VLANs 11 and 12. [DeviceD-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 11 12 # Configure VLAN 11 as the default VLAN.
  • Page 83 # Create VLAN 12. <DeviceE> system-view [DeviceE] vlan 12 # Map VLAN 12 to MSTI 2. [DeviceE-vlan12] quit [DeviceE] stp region-configuration [DeviceE-mst-region] instance 2 vlan 12 # Activate the MST region configuration. [DeviceE-mst-region] active region-configuration [DeviceE-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceE] interface gigabitethernet 1/0/1 [DeviceE-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port.
  • Page 84 # Create VLAN 11. <DeviceF> system-view [DeviceF] vlan 11 [DeviceF-vlan11] quit # Map VLAN 11 to MSTI 1. [DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 11 # Activate the MST region configuration. [DeviceF-mst-region] active region-configuration [DeviceF-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceF] interface gigabitethernet 1/0/1 [DeviceF-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port.

  • Page 85: Troubleshooting Rrpp

    # Create RRPP ring group 1 on Device B, and add subrings 2 and 3 to the RRPP ring group. [DeviceB] rrpp ring-group 1 [DeviceB-rrpp-ring-group1] domain 2 ring 2 [DeviceB-rrpp-ring-group1] domain 1 ring 3 # Create RRPP ring group 1 on Device C, and add subrings 2 and 3 to the RRPP ring group. [DeviceC] rrpp ring-group 1 [DeviceC-rrpp-ring-group1] domain 2 ring 2 [DeviceC-rrpp-ring-group1] domain 1 ring 3...

  • Page 86: Configuring Erps

    Configuring ERPS Overview Ethernet Ring Protection Switching (ERPS) is a robust link layer protocol that ensures a loop-free topology and implements quick link recovery. ERPS structure Figure 23 ERPS ring structure Rings ERPS rings can be divided into major rings and subrings. An ERPS network consists of one major ring or multiple major rings, and multiple subrings.

  • Page 87: Erps Protocol Packets

    • RPL port—Port on an RPL link. • Interconnection port—Port that connects a subring to a major ring. • Normal port—Default type of a port that forwards both service packets and protocol packets. As shown in Figure 23, ports A1, B1, E1, and F1 are RPL ports. Ports C3 and D3 are interconnection ports.

  • Page 88: Erps Node States

    ERPS node states Table 8 ERPS states State Description State for a non-interconnection node that has less than two ERPS ring member ports or for Init an interconnection node that does not have ERPS ring member ports. Stable state when all non-RPL links are available. In this state, the owner node blocks the Idle RPL port and periodically sends NR-RB packets.

  • Page 89: Erps Operation Mechanism

    ERPS operation mechanism ERPS uses the detection mechanism defined in ITU-T G.8032/Y.1344 to locate the point of failure and identify unidirectional or bidirectional faults. ERPS uses the SF packets to report signal failures on a link and the NR packets to report link recovery.
  • Page 90 a. Starts the WTR timer. b. Blocks the RPL port and periodically sends NR-RB packets when the WTR timer expires. When other nodes receive the NR-RB packets, they perform the following operations: a. Device B (neighbor port) blocks the RPL port. b.

  • Page 91: Erps Network Diagrams

    ERPS network diagrams One major ring The network has one major ring. Figure 27 Network diagram One major ring connecting one subring The network has one major ring and one subring. Figure 28 Network diagram Device A Device B RPL ports Owner node Neighbor node Major ring RPL...
  • Page 92 Figure 29 Network diagram Device B Device A Device G Owner node Owner node Major ring Subring 2 Device C Device H Device D Subring 1 Device E Device F Owner node One subring connecting multiple subrings The network has three or more rings. As shown in Figure 30, subring 1 is connected to the major ring.

  • Page 93: Protocols And Standards

    Figure 31 Network diagram 1 Device B Device A Device G Owner node Owner node Major ring Device C Device D Subring 2 Subring 1 Device E Device H Owner node Device F Figure 32 Network diagram 2 Protocols and standards •...

  • Page 94: Configuration Prerequisites

    Task at a glance Remarks (Required.) Enabling ERPS globally (Required.) Enabling flush packet transparent transmission (Required.) Configuring an ERPS ring (Optional.) Enabling R-APS packets to carry the ring ID in the destination MAC address (Required.) Configuring ERPS ring member ports: •...

  • Page 95: Enabling Flush Packet Transparent Transmission

    Enabling flush packet transparent transmission This feature enables the interconnection nodes to forward flush packets for topology changes in the subring to the major ring. To enable flush packet transparent transmission: Step Command Remarks Enter system view. system-view By default, flush packet Enable flush packet erps tcn-propagation transparent transmission is...

  • Page 96: Configuring Erps Ring Member Port Attributes

    Configuring ERPS ring member port attributes Follow these guidelines when you configure ERPS ring member port attributes: • ERPS ring member ports automatically allow packets from the control VLAN to pass through. • For faster topology convergence, use the link-delay command on ERPS ring member ports to set the physical state change suppression interval to 0 seconds.

  • Page 97: Configuring Protected Vlans

    • Do not configure the default VLAN of an ERPS ring member port as the control VLAN, and do not enable QinQ or VLAN mapping on control VLANs. If you do, ERPS packets cannot be correctly forwarded and received. • Make sure the ERPS instance has been configured.

  • Page 98: Configuring The Node Role

    Step Command Remarks This step is not required if the device is operating in PVST mode. Activate the MST region active region-configuration For more information about this configuration. command, see Layer 2—LAN Switching Command Reference. Available in any view. The output of the command (Optional.) Display the includes VLAN-to-instance mapping between VLANs...

  • Page 99: Configuring R-Aps Packet Levels

    Step Command Remarks view. Enable ERPS for the By default, ERPS is disabled for an instance enable instance. instance. Configuring R-APS packet levels A node does not process R-APS packets whose levels are greater than the level of R-APS packets sent by the node.

  • Page 100: Setting The Ms Mode

    Step Command Remarks Configure the node as the Either port 0 or port 1 can be owner node and port 0 as node-role owner rpl port0 configured as the RPL port. the RPL port. Set the non-revertive revertive-operation By default, revertive mode is used. mode.

  • Page 101: Removing The Ms Mode And Fs Mode Settings For An Erps Ring

    Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Associate an ERPS ring port erps ring ring-id instance By default, an ERPS ring member member port with a track instance-id track port is not associated with any entry.
  • Page 102 • Configure Device A as the owner node, GigabitEthernet 1/0/1 as ERPS ring member port 0 and the RPL port, and GigabitEthernet 1/0/2 as ERPS ring member port 1. • Configure Device B as the neighbor node, GigabitEthernet 1/0/1 as ERPS ring member port 0 and the RPL port, and GigabitEthernet 1/0/2 as ERPS ring member port 1.
  • Page 103 # Enable R-APS packets to carry ring ID in the destination MAC address. [DeviceA-erps-ring1] r-aps ring-mac # Create ERPS instance 1. [DeviceA-erps-ring1] instance 1 # Configure the node role. [DeviceA-erps-ring1-inst1] node-role owner rpl port0 # Configure the control VLAN. [DeviceA-erps-ring1-inst1] control-vlan 100 # Configure the protected VLANs.
  • Page 104 # Associate GigabitEthernet 1/0/2 with track entry 2 and bring up the port. [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] port erps ring 1 instance 1 track 2 [DeviceA-GigabitEthernet1/0/2] undo shutdown [DeviceA-GigabitEthernet1/0/2] quit # Enable ERPS. [DeviceA] erps enable Configure Device B. # Create VLANs 1 to 30, map these VLANs to MSTI 1, and activate the MST region configuration.
  • Page 105 # Enable ERPS for instance 1. [DeviceB-erps-ring1-inst1] instance enable [DeviceB-erps-ring1-inst1] quit [DeviceB-erps-ring1] quit # Enable CFD, and create a level-5 MD named MD_A. [DeviceB] cfd enable [DeviceB] cfd md MD_A level 5 # Create Ethernet service instance 1, in which the MA is identified by a VLAN and serves VLAN [DeviceB] cfd service-instance 1 ma-id vlan-based md MD_A vlan 1 # Configure a MEP list in Ethernet service instance 1, create outward-facing MEP 1002 in Ethernet service instance 1, and enable CCM sending on GigabitEthernet 1/0/1.
  • Page 106 <DeviceC> system-view [DeviceC] vlan 1 to 30 [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Set the link state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port.
  • Page 107 [DeviceC] cfd meplist 3001 3002 service-instance 3 [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] cfd mep 3001 service-instance 3 outbound [DeviceC-GigabitEthernet1/0/1] cfd cc service-instance 3 mep 3001 enable [DeviceC-GigabitEthernet1/0/1] quit # Create Ethernet service instance 4, in which the MA is identified by a VLAN and serves VLAN [DeviceC] cfd service-instance 4 ma-id vlan-based md MD_A vlan 4 # Configure a MEP list in Ethernet service instance 4, create outward-facing MEP 4001 in Ethernet service instance 4, and enable CCM sending on GigabitEthernet 1/0/2.
  • Page 108 [DeviceD-GigabitEthernet1/0/1] port link-type trunk [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] link-delay 0 [DeviceD-GigabitEthernet1/0/2] undo stp enable [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/2] quit # Create ERPS ring 1.
  • Page 109 [DeviceD-GigabitEthernet1/0/1] cfd cc service-instance 4 mep 4002 enable [DeviceD-GigabitEthernet1/0/1] quit # Create track entry 1 and associate it with the CC function of CFD for MEP 2002 in Ethernet service instance 2. [DeviceD] track 1 cfd cc service-instance 2 mep 2002 # Associate GigabitEthernet 1/0/2 with track entry 1 and bring up the port.

  • Page 110: One-Subring Configuration Example

    • The ERPS ring is in idle state. • The RPL port is blocked. • The non-RPL port is unblocked. One-subring configuration example Network requirements As shown in Figure 34, perform the following tasks to eliminate loops on the network: •...
  • Page 111 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Set the link state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port. [DeviceA-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port and assign it to VLANs 1 to 30. [DeviceA-GigabitEthernet1/0/1] port link-type trunk [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/1] quit...
  • Page 112 [DeviceA-GigabitEthernet1/0/1] quit # Create Ethernet service instance 2, in which the MA is identified by a VLAN and serves VLAN [DeviceA] cfd service-instance 2 ma-id vlan-based md MD_A vlan 2 # Configure a MEP list in Ethernet service instance 2, create outward-facing MEP 2001 in Ethernet service instance 1, and enable CCM sending on GigabitEthernet 1/0/2.
  • Page 113 [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] link-delay 0 [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/2] quit # Create ERPS ring 1. [DeviceB] erps ring 1 # Configure ERPS ring member ports. [DeviceB-erps-ring1] port0 interface gigabitethernet 1/0/1 [DeviceB-erps-ring1] port1 interface gigabitethernet 1/0/2 # Create ERPS instance 1.
  • Page 114 [DeviceB] track 1 cfd cc service-instance 1 mep 1002 # Associate GigabitEthernet 1/0/1 with track entry 1 and bring up the port. [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] port erps ring 1 instance 1 track 1 [DeviceB-GigabitEthernet1/0/1] undo shutdown [DeviceB-GigabitEthernet1/0/1] quit # Create track entry 3 and associate it with the CC function of CFD for MEP 3002 in Ethernet service instance 3.
  • Page 115 # Create ERPS ring 1. [DeviceC] erps ring 1 # Configure ERPS ring member ports. [DeviceC-erps-ring1] port0 interface gigabitethernet 1/0/1 [DeviceC-erps-ring1] port1 interface gigabitethernet 1/0/2 # Create ERPS instance 1. [DeviceC-erps-ring1] instance 1 # Configure the control VLAN. [DeviceC-erps-ring1-inst1] control-vlan 100 # Configure the protected VLANs.
  • Page 116 [DeviceC] track 2 cfd cc service-instance 4 mep 4001 # Associate GigabitEthernet 1/0/1 with track entry 2 and bring up the port. [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] port erps ring 1 instance 1 track 2 [DeviceC-GigabitEthernet1/0/1] undo shutdown [DeviceC-GigabitEthernet1/0/1] quit # Create ERPS ring 2.
  • Page 117 <DeviceD> system-view [DeviceD] vlan 1 to 30 [DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 1 to 30 [DeviceD-mst-region] active region-configuration [DeviceD-mst-region] quit # Set the link state change suppression interval to 0 seconds on GigabitEthernet 1/0/1. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port.
  • Page 118 # Create Ethernet service instance 2, in which the MA is identified by a VLAN and serves VLAN [DeviceD] cfd service-instance 2 ma-id vlan-based md MD_A vlan 2 # Configure a MEP list in Ethernet service instance 2, create outward-facing MEP 2002 in Ethernet service instance 2, and enable CCM sending on GigabitEthernet 1/0/2.
  • Page 119 # Configure the protected VLANs. [DeviceD-erps-ring2-inst1] protected-vlan reference-instance 1 # Enable ERPS for instance 1. [DeviceD-erps-ring2-inst1] instance enable [DeviceD-erps-ring2-inst1] quit [DeviceD-erps-ring2] quit # Create Ethernet service instance 6, in which the MA is identified by a VLAN and serves VLAN [DeviceD] cfd service-instance 6 ma-id vlan-based md MD_A vlan 6 # Configure a MEP list in Ethernet service instance 6, create outward-facing MEP 6002 in Ethernet service instance 3, and enable CCM sending on GigabitEthernet 1/0/3.
  • Page 120 [DeviceE-GigabitEthernet1/0/2] port link-type trunk [DeviceE-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceE-GigabitEthernet1/0/2] quit # Create ERPS ring 2. [DeviceE] erps ring 2 # Configure ERPS ring member ports. [DeviceE-erps-ring2] port0 interface gigabitethernet 1/0/1 [DeviceE-erps-ring2] port1 interface gigabitethernet 1/0/2 # Configure ERPS ring 2 as the subring. [DeviceE-erps-ring2] ring-type sub-ring # Create ERPS instance 1.
  • Page 121 # Associate GigabitEthernet 1/0/2 with track entry 1 and bring up the port. [DeviceE] interface gigabitethernet 1/0/2 [DeviceE-GigabitEthernet1/0/2] port erps ring 2 instance 1 track 1 [DeviceE-GigabitEthernet1/0/2] undo shutdown [DeviceE-GigabitEthernet1/0/2] quit # Create track entry 2 and associate it with the CC function of CFD for MEP 7001 in Ethernet service instance 7.
  • Page 122 # Create ERPS instance 1. [DeviceF-erps-ring2] instance 1 # Configure the node role. [DeviceF-erps-ring2] node-role neighbor rpl port0 # Configure the control VLAN. [DeviceF-erps-ring2-inst1] control-vlan 110 # Configure the protected VLANs. [DeviceF-erps-ring2-inst1] protected-vlan reference-instance 1 # Enable ERPS for instance 1. [DeviceF-erps-ring2-inst1] instance enable [DeviceF-erps-ring2-inst1] quit [DeviceF-erps-ring2] quit...

  • Page 123: One-Ring Multi-Instance Load Balancing Configuration Example

    [DeviceF-GigabitEthernet1/0/1] port erps ring 2 instance 1 track 2 [DeviceF-GigabitEthernet1/0/1] undo shutdown [DeviceF-GigabitEthernet1/0/1] quit # Enable ERPS. [DeviceF] erps enable Verifying the configuration # Display information about ERPS instance 1 for Device A. [Device A] display erps detail ring 1 Ring ID Port0 : GigabitEthernet1/0/1...
  • Page 124 Configure VLAN 100 as the control VLAN. Configure VLANs 1 to 30 as the protected VLANs. • For ERPS instance 2, configure the following items: Configure Device A as the owner node. Configure the link between Devices C and Device D as the RPL. Configure VLAN 100 as the control VLAN.
  • Page 125 [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 60 [DeviceA-GigabitEthernet1/0/2] quit # Create ERPS ring 1. [DeviceA] erps ring 1 # Configure ERPS ring member ports. [DeviceA-erps-ring1] port0 interface gigabitethernet 1/0/1 [DeviceA-erps-ring1] port1 interface gigabitethernet 1/0/2 # Create ERPS instance 1. [DeviceA-erps-ring1] instance 1 # Configure the node role.
  • Page 126 [DeviceA] cfd meplist 2001 2002 service-instance 2 [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] cfd mep 2001 service-instance 2 outbound [DeviceA-GigabitEthernet1/0/2] cfd cc service-instance 2 mep 2001 enable [DeviceA-GigabitEthernet1/0/2] quit # Create track entry 1 and associate it with the CC function of CFD for MEP 1001 in Ethernet service instance 1.
  • Page 127 [DeviceB-GigabitEthernet1/0/2] link-delay 0 [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 60 [DeviceB-GigabitEthernet1/0/2] quit # Create ERPS ring 1. [DeviceB] erps ring 1 # Configure ERPS ring member ports. [DeviceB-erps-ring1] port0 interface gigabitethernet 1/0/1 [DeviceB-erps-ring1] port1 interface gigabitethernet 1/0/2 # Create ERPS instance 1.
  • Page 128 [DeviceB] cfd service-instance 3 ma-id vlan-based md MD_A vlan 3 # Configure a MEP list in Ethernet service instance 3, create outward-facing MEP 3002 in Ethernet service instance 3, and enable CCM sending on GigabitEthernet 1/0/2. [DeviceB] cfd meplist 3001 3002 service-instance 3 [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] cfd mep 3002 service-instance 3 outbound [DeviceB-GigabitEthernet1/0/2] cfd cc service-instance 3 mep 3002 enable...
  • Page 129 [DeviceC-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] link-delay 0 [DeviceC-GigabitEthernet1/0/2] undo stp enable [DeviceC-GigabitEthernet1/0/2] port link-type trunk [DeviceC-GigabitEthernet1/0/2] port trunk permit vlan 1 to 60 [DeviceC-GigabitEthernet1/0/2] quit # Create ERPS ring 1. [DeviceC] erps ring 1 # Configure ERPS ring member ports.
  • Page 130 [DeviceC-GigabitEthernet1/0/2] quit # Create Ethernet service instance 4, in which the MA is identified by a VLAN and serves VLAN [DeviceC] cfd service-instance 4 ma-id vlan-based md MD_A vlan 4 # Configure a MEP list in Ethernet service instance 4, create outward-facing MEP 4001 in Ethernet service instance 4, and enable CCM sending on GigabitEthernet 1/0/1.
  • Page 131 # Configure the port as a trunk port and assign it to VLANs 1 to 60. [DeviceD-GigabitEthernet1/0/1] port link-type trunk [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 60 [DeviceD-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] link-delay 0 [DeviceD-GigabitEthernet1/0/2] undo stp enable...
  • Page 132 [DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] cfd mep 2002 service-instance 2 outbound [DeviceD-GigabitEthernet1/0/2] cfd cc service-instance 2 mep 2002 enable [DeviceD-GigabitEthernet1/0/2] quit # Create Ethernet service instance 4, in which the MA is identified by a VLAN and serves VLAN [DeviceD] cfd service-instance 4 ma-id vlan-based md MD_A vlan 4 # Configure a MEP list in Ethernet service instance 4, create outward-facing MEP 4002 in Ethernet service instance 4, and enable CCM sending on GigabitEthernet 1/0/1.

  • Page 133: Troubleshooting Erps

    Connect(ring/instance): - Control VLAN : 100 Protected VLAN : Reference-instance 1 Guard timer : 500 ms Hold-off timer : 0 ms WTR timer : 5 min Revertive operation : Revertive Enable status : Yes, Active status : Yes R-APS level Port PortRole PortStatus...
  • Page 134 Analysis Possible reasons include: • ERPS is not enabled for some nodes on the ERPS ring. • The ring IDs are different for the nodes on the same ERPS ring. • The control VLAN IDs are different for the nodes in the same ERPS instance. •...

  • Page 135: Configuring Smart Link

    Configuring Smart Link Overview To avoid single-point failures and guarantee network reliability, downstream devices are usually dual-homed to upstream devices, as shown in Figure Figure 36 Dual uplink network diagram To remove network loops on a dual-homed network, you can use a spanning tree protocol or the Rapid Ring Protection Protocol (RRPP).

  • Page 136: Terminology

    Terminology Smart link group A smart link group consists of only two member ports: the primary and the secondary ports. Only one port is active for forwarding at a time, and the other port is blocked and in standby state. When link failure occurs on the active port due to port shutdown or the presence of unidirectional link, the standby port becomes active and takes over.

  • Page 137: Smart Link Collaboration Mechanisms

    Topology change Link switchover might outdate the MAC address entries and ARP/ND entries on all devices. A flush update mechanism is provided to ensure correct packet transmission. With this mechanism, a Smart Link-enabled device updates its information by transmitting flush messages over the backup link to its upstream devices.

  • Page 138: Smart Link Configuration Task List

    Smart Link configuration task list Tasks at a glance Configuring a Smart Link device: • (Required.) Configuring protected VLANs for a smart link group • (Required.) Configuring member ports for a smart link group • (Optional.) Configuring a preemption mode for a smart link group •...

  • Page 139: Configuring Member Ports For A Smart Link Group

    Step Command Remarks command, see Layer 2—LAN Switching Command Reference. Skip this step if the device is • operating in PVST mode. Method 1: instance instance-id vlan All VLANs in an MST region are Configure the vlan-id-list mapped to CIST (MSTI 0) by VLAN-to-instance mapping •...

  • Page 140: Configuring A Preemption Mode For A Smart Link Group

    Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Configure member ports for a port smart-link group group-id By default, an interface is not smart link group. { primary | secondary } a smart link group member.

  • Page 141: Configuring An Associated Device

    To configure collaboration between Smart Link and Track: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, smart link group member ports do not collaborate with track entries.

  • Page 142: Displaying And Maintaining Smart Link

    Displaying and maintaining Smart Link Perform display commands in any view and the reset command in user view: Task Command Display information about the received flush display smart-link flush messages. Display smart link group information. display smart-link group { group-id | all } Clear the statistics about flush messages.
  • Page 143 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Shut down GigabitEthernet 1/0/1. [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] shutdown # Disable the spanning tree feature on the port. [DeviceC-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceC-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30.
  • Page 144 # Shut down GigabitEthernet 1/0/1. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] shutdown # Disable the spanning tree feature on the port. [DeviceD-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceD-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.
  • Page 145 [DeviceB-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 as a trunk port. [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 # Disable the spanning tree feature on the port. [DeviceB-GigabitEthernet1/0/2] undo stp enable # Enable flush message receiving and configure VLAN 20 as the receive control VLAN on the port.
  • Page 146 # Configure GigabitEthernet 1/0/3 as a trunk port. [DeviceE] interface gigabitethernet 1/0/3 [DeviceE-GigabitEthernet1/0/3] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceE-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 # Disable the spanning tree feature on the port. [DeviceE-GigabitEthernet1/0/3] undo stp enable # Enable flush message receiving and configure VLAN 20 as the receive control VLAN on the port.

  • Page 147: Multiple Smart Link Groups Load Sharing Configuration Example

    Receiving interface of the last flush packet : GigabitEthernet1/0/3 Receiving time of the last flush packet : 16:50:21 2012/04/21 Device ID of the last flush packet : 000f-e23d-5af0 Control VLAN of the last flush packet : 10 Multiple smart link groups load sharing configuration example Network requirements As shown in Figure...
  • Page 148 # Assign the port to VLAN 1 through VLAN 200. [DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200 [DeviceC-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] shutdown [DeviceC-GigabitEthernet1/0/2] undo stp enable [DeviceC-GigabitEthernet1/0/2] port link-type trunk [DeviceC-GigabitEthernet1/0/2] port trunk permit vlan 1 to 200 [DeviceC-GigabitEthernet1/0/2] quit...
  • Page 149 [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 200. [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200 # Enable flush message receiving and configure VLAN 10 and VLAN 110 as the receive control VLANs on the port.
  • Page 150 # Configure GigabitEthernet 1/0/1 as a trunk port. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 200. [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200 # Enable flush message receiving and configure VLAN 10 and VLAN 110 as the receive control VLANs on the port.

  • Page 151: Smart Link And Track Collaboration Configuration Example

    Smart Link and Track collaboration configuration example Network requirements As shown in Figure • Device A, Device B, Device C, and Device D form maintenance domain (MD) MD_A of level 5. Device C is a Smart Link device, and Device A, Device B, and Device D are associated devices. Traffic of VLANs 1 through 200 on Device C is dually uplinked to Device A by Device B and Device D.
  • Page 152 # Enable flush message receiving and configure VLAN 10 and VLAN 110 as the receive control VLANs on the port. [DeviceA-GigabitEthernet1/0/1] smart-link flush enable control-vlan 10 110 [DeviceA-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured. [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 200...
  • Page 153 [DeviceB-GigabitEthernet1/0/2] port link-type trunk # Assign the port to VLANs 1 through 200. [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 200 # Disable the spanning tree feature on the port. [DeviceB-GigabitEthernet1/0/2] undo stp enable # Enable flush message receiving and configure VLAN 10 and VLAN 110 as the receive control VLANs on the port.
  • Page 154 [DeviceC-smlk-group1] flush enable control-vlan 10 [DeviceC-smlk-group1] quit # Create smart link group 2, and configure all VLANs mapped to MSTI 2 as the protected VLANs for smart link group 2. [DeviceC] smart-link group 2 [DeviceC-smlk-group2] protected-vlan reference-instance 2 # Configure GigabitEthernet 1/0/1 as the secondary port and GigabitEthernet 1/0/2 as the primary port for smart link group 2.
  • Page 155 [DeviceC] track 2 cfd cc service-instance 2 mep 2001 # Configure collaboration between the primary port GigabitEthernet 1/0/2 of smart link group 2 and the CC function of CFD through track entry 2, and bring up the port. [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] port smart-link group 2 track 2 [DeviceC-GigabitEthernet1/0/2] undo shutdown [DeviceC-GigabitEthernet1/0/2] quit...
  • Page 156 Device ID : 000f-e23d-5af0 Preemption mode : Role Preemption delay: 1(s) Control VLAN : 110 Protected VLAN : Reference Instance 2 Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------- GE1/0/2 PRIMARY ACTIVE 16:45:20 2012/04/21 GE1/0/1 SECONDARY STANDBY 1 16:37:20 2012/04/21 The output shows that primary port GigabitEthernet 1/0/1 of smart link group 1 fails, and secondary port GigabitEthernet 1/0/2 is in forwarding state.

  • Page 157: Configuring Monitor Link

    Configuring Monitor Link Overview Monitor Link associates the state of downlink interfaces with the state of uplink interfaces in a monitor link group. When Monitor Link shuts down the downlink interfaces because of an uplink failure, the downstream device changes connectivity to another link. Figure 40 Monitor Link application scenario A monitor link group contains uplink and downlink interfaces.

  • Page 158: Configuration Restrictions And Guidelines

    state reaches the threshold, the monitor link group comes up and brings up all its downlink interfaces. Configuration restrictions and guidelines Follow these restrictions and guidelines when you configure Monitor Link: • Do not manually shut down or bring up the downlink interfaces in a monitor link group. •...

  • Page 159: Configuring Monitor Link Group Member Interfaces

    Configuring monitor link group member interfaces You can configure member interfaces for a monitor link group in monitor link group view or interface view. Configurations made in these views have the same effect. The configuration is supported by Layer 2 Ethernet interfaces and Layer 2 aggregate interfaces. Follow these guidelines when you configure monitor link group member interfaces: •...

  • Page 160: Configuring The Switchover Delay For The Downlink Interfaces In A Monitor Link Group

    Configuring the switchover delay for the downlink interfaces in a monitor link group Step Command Remarks Enter system view. system-view Enter monitor link group view. monitor-link group group-id Configure the switchover By default, the switchover delay delay for the downlink is 0 seconds.
  • Page 161 Configuration procedure Configure Device C: # Create VLANs 1 through 30. <DeviceC> system-view [DeviceC] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30 # Activate MST region configuration. [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Shut down GigabitEthernet 1/0/1.
  • Page 162 # Create VLANs 1 through 30. <DeviceA> system-view [DeviceA] vlan 1 to 30 # Configure GigabitEthernet 1/0/1 as a trunk port. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] port link-type trunk # Assign the interface to VLANs 1 through 30. [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 # Enable flush message receiving on the interface.
  • Page 163 # Create VLANs 1 through 30. <DeviceD> system-view [DeviceD] vlan 1 to 30 # Configure GigabitEthernet 1/0/1 as a trunk port. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] port link-type trunk # Assign the interface to VLANs 1 through 30. [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 # Enable flush message receiving on the interface.
  • Page 164 Downlink up-delay: 0(s) Last-up-time : 16:37:20 2012/4/21 Last-down-time : 16:38:26 2012/4/21 Up-port-threshold: 1 Member Role Status -------------------------------------------- GE1/0/1 UPLINK DOWN GE1/0/2 DOWNLINK DOWN...

  • Page 165: Configuring Bfd

    Configuring BFD Overview Bidirectional forwarding detection (BFD) provides a general-purpose, standard, medium- and protocol-independent fast failure detection mechanism. It can detect and monitor the connectivity of links in IP to detect communication failures quickly so that measures can be taken to ensure service continuity and enhance network availability.

  • Page 166: Supported Features

    Control packet mode Both ends of the link exchange BFD control packets to monitor link status. Before a BFD session is established, BFD has two operating modes—active and passive. • Active mode—BFD actively sends BFD control packets regardless of whether any BFD control packet is received from the peer.

  • Page 167: Configuring Echo Packet Mode

    After a BFD session is established, the two ends negotiate BFD parameters, including minimum sending interval, minimum receiving interval, initialization mode, and packet authentication, by exchanging negotiation packets. They use the negotiated parameters without affecting the session status. BFD session flapping might occur on an aggregate interface with member ports on different IRF member devices.
  • Page 168 Step Command Remarks Enter system view. system-view By default, active is specified. Specify the mode for bfd session init-mode { active | BFD version 0 does not support establishing a BFD session. passive } this command. The configuration does not take effect. interface interface-type Enter interface view.

  • Page 169: Configuring A Bfd Template

    Step Command Remarks By default, active is specified. Specify the mode for bfd session init-mode { active | BFD version 0 does not support establishing a BFD session. passive } this command. The configuration does not take effect. By default, no authentication is bfd multi-hop performed.

  • Page 170: Enabling Snmp Notifications For Bfd

    Enabling SNMP notifications for BFD To report critical BFD events to an NMS, enable SNMP notifications for BFD. For BFD event notifications to be sent correctly, you must also configure SNMP as described in Network Management and Monitoring Configuration Guide. To enable SNMP notifications for BFD: Step Command...

  • Page 171: Configuring Track

    Configuring Track Overview The Track module works between application modules and detection modules. It shields the differences between various detection modules from application modules. Collaboration is enabled when you associate the Track module with a detection module and an application module, and it operates as follows: The detection module probes specific objects such as interface status, link status, network reachability, and network performance, and informs the Track module of detection results.

  • Page 172: Collaboration Application Example

    • EAA. • ERPS. When configuring a track entry for an application module, you can set a notification delay to avoid immediate notification of status changes. Collaboration application example The following is an example of collaboration between NQA, Track, and static routing. Configure a static route with the next hop 192.168.0.88 on the device.

  • Page 173: Associating The Track Module With A Detection Module

    Associating the Track module with a detection module Associating Track with NQA NQA supports multiple operation types to analyze network performance and service quality. For example, an NQA operation can periodically detect whether a destination is reachable, or whether a TCP connection can be established.

  • Page 174: Associating Track With Cfd

    Associating Track with CFD The associated Track and CFD operate as follows: • If the CFD detects that the link fails, it informs the Track module of the link failure. The Track module then sets the track entry to Negative state. •...

  • Page 175: Associating Track With Route Management

    Step Command Remarks protocol status of an interface: track track-entry-number interface interface-type interface-number protocol { ipv4 | ipv6 } [ delay { negative negative-time | positive positive-time } * ] Associating Track with route management The route management module monitors route entry changes in the routing table. The associated Track and route management operate as follows: •...

  • Page 176: Associating The Track Module With An Application Module

    Step Command Remarks track track-entry-number lldp neighbor Create a track entry and interface interface-type interface-number By default, no track entries associate it with an LLDP [ delay { negative negative-time | exist. interface. positive positive-time } * ] Associating the Track module with an application module Before you associate the Track module with an application module, make sure the associated track entry has been created.

  • Page 177: Associating Track With Pbr

    Step Command Remarks Enter system view. system-view ip route-static { dest-address { mask-length | mask } | group group-name } { interface-type interface-number [ next-hop-address ] [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] [ permanent ] | bfd Associate a static { control-packet | echo-packet } | permanent ] route with a track By default, Track is not...

  • Page 178: Associating Track With Smart Link

    Step Command Remarks By default, no next hop is set. You can configure two Set the next hop, and apply next-hop { ip-address [ direct ] [ track next hops for backup. associate it with a track track-entry-number ] }&<1-2> The first configured entry.

  • Page 179: Associating Track With Erps

    • If you specify only one track entry for a policy, EAA triggers the policy when it detects the specified state change on the track entry. • If you specify multiple track entries for a policy, EAA triggers the policy when it detects the specified state change on the last monitored track entry.

  • Page 180: Displaying And Maintaining Track Entries

    Displaying and maintaining track entries Execute display commands in any view. Task Command display track { track-entry-number | all Display information about track entries. [ negative | positive ] } [ brief ] Track configuration examples Static routing-Track-NQA collaboration configuration example Network requirements As shown in...
  • Page 181 Configuration procedure Create VLANs and assign ports to them. Configure the IP address of each VLAN interface, as shown in Figure 42. (Details not shown.) Configure Switch A: # Configure a static route to 30.1.1.0/24 with the next hop 10.1.1.2 and the default priority 60. Associate this static route with track entry 1.
  • Page 182 [SwitchD] ip route-static 20.1.1.0 24 10.2.1.2 track 1 # Configure a static route to 20.1.1.0/24 with the next hop 10.4.1.3 and the priority 80. [SwitchD] ip route-static 20.1.1.0 24 10.4.1.3 preference 80 # Configure a static route to 10.1.1.1 with the next hop 10.2.1.2. [SwitchD] ip route-static 10.1.1.1 24 10.2.1.2 # Create an NQA operation with administrator admin and operation tag test.
  • Page 183 10.2.1.0/24 Static 60 10.1.1.2 Vlan2 10.3.1.0/24 Direct 0 10.3.1.1 Vlan3 10.3.1.1/32 Direct 0 127.0.0.1 InLoop0 20.1.1.0/24 Direct 0 20.1.1.1 Vlan6 20.1.1.1/32 Direct 0 127.0.0.1 InLoop0 30.1.1.0/24 Static 60 10.1.1.2 Vlan2 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 The output shows that Switch A forwards packets to 30.1.1.0/24 through Switch B.

  • Page 184: Static Routing-Track-Bfd Collaboration Configuration Example

    [SwitchA] ping -a 20.1.1.1 30.1.1.1 Ping 30.1.1.1: 56 data bytes, press CTRL_C to break Reply from 30.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms Reply from 30.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms Reply from 30.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms Reply from 30.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms Reply from 30.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms --- Ping statistics for 30.1.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.00% packet loss...
  • Page 185 Figure 43 Network diagram Configuration procedure Create VLANs and assign ports to them. Configure the IP address of each VLAN interface, as shown in Figure 43. (Details not shown.) Configure Switch A: # Configure a static route to 30.1.1.0/24 with the next hop 10.2.1.2 and the default priority 60. Associate this static route with track entry 1.
  • Page 186 Verifying the configuration # Display information about the track entry on Switch A. [SwitchA] display track all Track ID: 1 State: Positive Duration: 0 days 0 hours 0 minutes 32 seconds Notification delay: Positive 0, Negative 0 (in seconds) Tracked object: BFD session mode: Echo Outgoing interface: Vlan-interface2 VPN instance name: --...
  • Page 187 Local IP: 10.2.1.1 The output shows that the status of the track entry is Negative, indicating that the next hop 10.2.1.2 is unreachable. # Display the routing table of Switch A. [SwitchA] display ip routing-table Destinations : 9 Routes : 9 Destination/Mask Proto Cost...

  • Page 188: Static Routing-Track-Lldp Collaboration Configuration Example

    Static routing-Track-LLDP collaboration configuration example Network requirements As shown in Figure • Device A is the default gateway of the hosts in network 20.1.1.0/24. • Device B is the default gateway of the hosts in network 30.1.1.0/24. • Hosts in the two networks communicate with each other through static routes. To ensure network availability, configure route backup and static routing-Track-LLDP collaboration on Device A and Device B as follows: •...
  • Page 189 [DeviceA] track 1 lldp neighbor interface gigabitethernet 1/0/1 Configure Device B: # Configure a static route to 20.1.1.0/24 with next hop 10.2.1.1 and the default priority (60). Associate this static route with track entry 1. <DeviceB> system-view [DeviceB] ip route-static 20.1.1.0 24 10.2.1.1 track 1 # Configure a static route to 20.1.1.0/24 with next hop 10.4.1.3 and priority 80.
  • Page 190 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 The output shows that Device A forwards packets to 30.1.1.0/24 through Device B. # Shut down GigabitEthernet1/0/1 on Device B. <DeviceB> system-view [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] shutdown # Display track entry information on Device A. [DeviceA] display track all Track ID: 1 State: Negative...

  • Page 191: Smart Link-Track-Cfd Collaboration Configuration Example

    # Verify that the hosts in 30.1.1.0/24 can communicate with the hosts in 20.1.1.0/24 when the master route fails. [DeviceB] ping -a 30.1.1.1 20.1.1.1 Ping 20.1.1.1: 56 data bytes, press CTRL_C to break Reply from 20.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms Reply from 20.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms Reply from 20.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms Reply from 20.1.1.1: bytes=56 Sequence=4 ttl=254 time=1 ms...

  • Page 192: Configuring Process Placement

    Configuring process placement Overview Process placement enables placing processes to specific CPUs (also called nodes) on the main processing units (MPUs) in your system for optimal distribution of CPU and memory resources. Process A process contains a set of codes and provides specific functionality. For example, an AAA process provides AAA functions.

  • Page 193: Configuration Restrictions And Guidelines

    • The addition of a new node does not impact current active processes. A new active process selects one node with sufficient CPU and memory resources. (You can use the display cpu-usage and display memory commands to view CPU and memory usage information.) Optimizing process placement You can configure the following settings for a process placement policy to optimize process placement:...

  • Page 194: Configuring Process Placement Policy

    Configuring process placement policy Configuring a location affinity Step Command Remarks Enter system view. system-view Settings in default • Enter default placement process view: placement process view placement program default take effect for all Enter placement process • processes. Settings in Enter placement process view: view.

  • Page 195: Configuring A Process Affinity

    Configuring a process affinity Step Command Remarks Enter system view. system-view • Enter default placement process view: Settings in default placement placement program default process view take effect for all • Enter placement process Enter placement process processes. Settings in placement view.

  • Page 196: Displaying Process Placement

    Displaying process placement Execute display commands in any view. Task Command display placement policy program { program-name | Display process placement policy information. all | default } Display the location of a process. display placement program { program-name | all } Display the running processes on a specific display placement location { slot slot-number | all } location.

  • Page 197: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional.

  • Page 198: Network Topology Icons

    Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

  • Page 199: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...

  • Page 200: Websites

    For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
  • Page 201 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 202: Index

    Index RRPP specification, Numerics RRPP type, associating ERPS network (1 major ring), ERPS port+Track entry, ERPS network (1 major ring+1 subring), ERPS ring+subring, ERPS network (1 major ring+multiple Smart Link associated device, subrings), Track+application module, ERPS network (1 subring+multiple rings), Track+BFD, ERPS network (1 subring+multiple Track+CFD,...
  • Page 203 single-hop detection, common SNMP notification enable, RRPP common port, static routing+Track+BFD collaboration, RRPPDU common-flush-FDB type, supported features, complete-flush-FDB RRPPDU type, template configuration, configuring Track+BFD association, BFD, bidirectional BFD basic functions, DLDP port state, BFD control packet mode, forwarding detection. Use BFD echo packet mode, broadcast BFD template,...
  • Page 204 process placement, 186, 187 BFD control packet mode, process placement policy, process placement policy affinity (location process placement configuration, 186, 187 type), creating process placement policy affinity Monitor Link group, (location), RRPP domain, process placement policy affinity (process), process placement policy affinity (self), data VLAN RRPP, 36, 44, 50...
  • Page 205 static routing+Track+NQA collaboration, Track association, Track configuration, EAIS disconnect state (RRPP ring), CFD EAIS configuration, displaying CFD Ethernet alarm indication signal, BFD, echo CFD, BFD echo packet mode, DLDP, DLDP echo timer, ERPS, edge Monitor Link, RRPP assistant edge node, process placement, RRPP edge node, RRPP,...
  • Page 206 node states, CFD basic configuration, nodes, CFD configuration, 1, 5, 13 non-revertive mode set, CFD functions, operation, CFD maintenance domain, port attribute configuration, fault detection port+Track entry association, BFD basic configuration, protected VLAN configuration, BFD configuration, protocols and standards, flushing R-APS packet destination MAC address ERPS flush packet transparent transmission enable ring ID,...
  • Page 207 CFD configuration, 1, 5, 13 NQA+Track+static routing collaboration, CFD display, process placement 1\N process redundancy, CFD maintain, process placement configuration, 186, 187 CFD protocols and standards, process placement configuration restrictions (centralized IRF devices), DLDP configuration, 18, 22, 25 process placement display, DLDP configuration restrictions, process placement optimization, 186, 189...
  • Page 208 Track configuration, 165, 166, 174 Track entry display, Layer 3 Track+application module association, BFD basic configuration, Track+BFD association, BFD configuration, Track+CFD association, line Track+detection module association, DLDP DelayDown line failure timer, Track+EAA association, link Track+ERPS association, DLDP configuration, 18, 22, 25 Track+interface management ERPS configuration, 80, 87, 95...
  • Page 209 Smart Link configuration, 129, 132, 136 CFD, Smart Link group configuration (multiple group CFD 1-way DM configuration, load sharing), CFD 2-way DM configuration, Smart Link group configuration (single CFD AIS configuration, group), CFD continuity check (CC), Smart Link+Track collaboration, CFD EAIS configuration, loopback CFD linktrace configuration, CFD configuration,...
  • Page 210 Track+ERPS association, CFD Ethernet service instance configuration, Track+interface management CFD function configuration, association, CFD functions, Track+LLDP association, CFD linktrace configuration, Track+policy-based routing association, CFD LM configuration, Track+route management association, CFD loopback configuration, Track+Smart Link association, CFD maintenance association, Track+static routing association, CFD maintenance point, Monitor Link CFD MEP configuration,...
  • Page 211 ERPS ring+subring association, Smart Link load sharing, ERPS timer set, Smart Link primary/secondary links, ERPS timers, Smart Link primary/secondary ports, Monitor Link global configuration, Smart Link+Track collaboration, 134, 145 Monitor Link group creation, Smart Link+Track+CFD collaboration, Monitor Link group downlink interface static routing+Track+BFD collaboration, switchover delay, static routing+Track+LLDP collaboration,...
  • Page 212 RRPP master node, process placement affinity (self), RRPP master type, process placement configuration, RRPP node configuration, process placement policy, RRPP transit node, polling mechanism (RRPP), RRPP transit type, port troubleshooting RRPP master node, DLDP configuration, 18, 22, 25 non-authentication mode (DLDP), DLDP DelayDown timer, non-revertive mode (ERPS), DLDP port shutdown mode,...
  • Page 213 associating Track+LLDP, configuring Monitor Link group downlink interface switchover delay, associating Track+NQA, configuring Monitor Link group member interface associating Track+policy-based routing, (group view), associating Track+route management, configuring Monitor Link group member interface associating Track+Smart Link, (interface view), associating Track+static routing, configuring Monitor Link group state switchover configuring BFD basic functions, trigger threshold,...
  • Page 214 configuring static routing+Track+NQA troubleshooting RRPP master node, collaboration, process placement configuring Track, 1\N process redundancy, creating Monitor Link group, configuration, 186, 187 creating RRPP domain, configuration restrictions (centralized IRF displaying BFD, devices), displaying CFD, display, displaying DLDP, optimization, 186, 189 displaying ERPS, policy, displaying Monitor Link,...
  • Page 215 removing intersecting rings load balancing, ERPS ring MS mode and FS mode intersecting rings networking, settings, link down mechanism, reporting load balancing, ERPS link-down report, load-balanced intersecting-rings configuration, restrictions maintain, DLDP configuration, master node specification, Monitor Link configuration, master node type, process placement configuration (centralized networking, IRF devices),...
  • Page 216 self affinity (process placement), group protected VLAN configuration, sending group role preemption mode configuration, Smart Link flush message send, how it works, session maintain, BFD control packet active operating Monitor Link collaboration, mode, Smart Link+Track+CFD collaboration, BFD control packet asynchronous operating terminology, mode, Track collaboration,...
  • Page 217 DLDP advertisement, Smart Link group configuration (single group), DLDP DelayDown, 19, 23 Smart Link+Track collaboration, DLDP echo, Track DLDP enhanced, application module association, DLDP entry, application module collaboration, DLDP probe, BFD association, DLDP recoverprobe, CFD association, ERPS set, configuration, 165, 166, 174 ERPS timers, detection module association, RRPP configuration,...
  • Page 218 Monitor Link group state switchover trigger threshold, troubleshooting ERPS master node cannot receive SF packets, RRPP master node, CFD functions, CFD TST configuration, unconfirmed DLDP neighbor state, unidirectional DLDP port state, updating Smart Link flush update, uplink Monitor Link group state switchover trigger threshold, VLAN CFD basic configuration,...

Table of Contents