Page 1: High Availability
HPE FlexNetwork 5510 HI Switch Series High Availability Configuration Guide Part number: 5200-3629 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 Ethernet OAM ································································· 1 Overview ·································································································································· 1 Major functions of Ethernet OAM ···························································································· 1 Ethernet OAMPDUs ············································································································· 1 How Ethernet OAM works ····································································································· 1 Protocols and standards ······································································································· 3 Ethernet OAM configuration task list ······························································································ 4 Configuring basic Ethernet OAM functions ······················································································ 4 Configuring the Ethernet OAM connection detection timers ·································································...
Page 4 Enabling DLDP ························································································································ 34 Setting the interval to send advertisement packets ·········································································· 35 Setting the DelayDown timer ······································································································ 35 Setting the port shutdown mode ·································································································· 35 Configuring DLDP authentication ································································································· 36 Displaying and maintaining DLDP ································································································ 36 DLDP configuration examples ····································································································· 37 Configuring the auto port shutdown mode ···············································································...
Page 5 Setting the non-revertive mode ································································································· 105 Setting the MS mode ·············································································································· 106 Setting the FS mode ··············································································································· 106 Associating a ring with a subring ······························································································· 106 Associating an ERPS ring member port with a track entry ······························································· 107 Removing the MS mode and FS mode settings for an ERPS ring ····················································· 107 Displaying and maintaining ERPS ·····························································································...
Page 6 IPv4 VRRP configuration task list ························································································ 180 Specifying an IPv4 VRRP operating mode ············································································ 180 Specifying the IPv4 VRRP version ······················································································ 181 Creating a VRRP group and assigning a virtual IP address ······················································ 181 Configuring the router priority, preemptive mode, and tracking function ······································· 182 Configuring IPv4 VRRP packet attributes ··············································································...
Page 7 Associating Track with VPLS ····························································································· 235 Associating Track with MPLS L2VPN ··················································································· 235 Associating Track with EAA ······························································································· 237 Associating Track with ERPS ····························································································· 238 Displaying and maintaining track entries ····················································································· 238 Track configuration examples ··································································································· 238 VRRP-Track-NQA collaboration configuration example ··························································· 238 Configuring BFD for a VRRP backup to monitor the master ······················································...
Page 8: Configuring Ethernet Oam
Configuring Ethernet OAM Overview Ethernet Operation, Administration, and Maintenance (OAM) is a tool that monitors Layer 2 link status and addresses common link-related issues on the "last mile." Ethernet OAM improves Ethernet management and maintainability. You can use it to monitor the status of the point-to-point link between two directly connected devices.
Page 9 Ethernet OAM connection establishment Ethernet OAM connection is the basis of all the other Ethernet OAM functions. OAM connection establishment is also known as the Discovery phase, where an Ethernet OAM entity discovers the remote OAM entity to establish a session. In this phase, two connected OAM entities exchange Information OAMPDUs to advertise their OAM configuration and capabilities to each other for a comparison.
Page 10: Protocols And Standards
Ethernet OAM link events Description An errored frame period event occurs when the number of frame errors in Errored frame period event the detection window (specified number of received frames) exceeds the predefined threshold. An errored frame seconds event occurs when the number of errored frame seconds (the second in which an errored frame appears is called an Errored frame seconds event errored frame second) detected on a port in the detection window...
Page 11: Ethernet Oam Configuration Task List
Ethernet OAM configuration task list Tasks at a glance (Required.) Configuring basic Ethernet OAM functions (Optional.) Configuring the Ethernet OAM connection detection timers (Optional.) Configuring link monitoring • Configuring errored symbol event detection • Configuring errored frame event detection • Configuring errored frame period event detection •...
Page 12: Configuring Link Monitoring
You can configure this command in system view or port view. The configuration in system view takes effect on all ports, and the configuration in port view takes effect on the specified port. For a port, the configuration in port view takes precedence. After the timeout timer of an Ethernet OAM connection expires, the local OAM entity ages out and terminates its connection with the peer OAM entity.
Page 13: Configuring Errored Frame Event Detection
Step Command Remarks oam global Configure the errored symbol By default, the errored symbol errored-symbol-period event triggering threshold. event triggering threshold is 1. threshold threshold-value To configure errored symbol event detection on a port: Step Command Remarks Enter system view. system-view Enter Layer 2/Layer 3 interface interface-type...
Page 14: Configuring Errored Frame Period Event Detection
Configuring errored frame period event detection An errored frame period event occurs when the number of times that frame errors in the detection window are detected exceeds the predefined threshold. The detection window refers to the specified number of received frames. You can configure this command in system view or port view.
Page 15: Configuring The Action A Port Takes After It Receives An Ethernet Oam Event From The Remote End
Step Command Remarks Configure the errored frame By default, the errored frame oam global seconds event detection seconds event detection window errored-frame-seconds window window. is 60000 milliseconds. window-value Configure the errored frame By default, the errored frame oam global seconds event triggering seconds event triggering errored-frame-seconds threshold.
Page 16: Configuration Restrictions And Guidelines
OAMPDUs. By observing how many of these packets return, you can calculate the packet loss ratio on the link and evaluate the link performance. You can enable Ethernet OAM remote loopback on a specific port in user view, system view, or Layer 2 Ethernet port view.
Page 17: Rejecting The Ethernet Oam Remote Loopback Request From A Remote Port
Rejecting the Ethernet OAM remote loopback request from a remote port The Ethernet OAM remote loopback feature impacts other services. To solve this problem, you can disable a port from being controlled by the Loopback Control OAMPDUs sent by a remote port. The local port then rejects the Ethernet OAM remote loopback request from the remote port.
Page 18: Configuration Procedure
• Determine the performance of the link between Device A and Device B by collecting statistics about the error frames received by Device A Figure 1 Network diagram GE1/0/1 GE1/0/1 Device A Device B Configuration procedure Configure Device A: # Configure GigabitEthernet 1/0/1 to operate in active Ethernet OAM mode, and enable Ethernet OAM for it.
Page 19 Link status: UP OAM local errored frame event Event time stamp : 5789 x 100 milliseconds Errored frame window : 200 x 100 milliseconds Errored frame threshold : 10 error frames Errored frame : 13 error frames Error running total : 350 error frames Event running total : 17 events...
Page 20: 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 21 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 22: 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 4 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 23 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 24: 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 25: 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 26: 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 27: 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 28: 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 { target-mac mac-address | Enable LB. Available in any view.
Page 29: 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 30: 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 31: 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.
Page 32: 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 33 Configuration procedure Configure a VLAN and assign ports to it: On each device shown in Figure 5, 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 34 [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 35 [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 36 # 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 37: 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 6 shows a correct fiber connection and two types of unidirectional fiber connections.
Page 38: 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 6 DLDP neighbor states DLDP timer Description Confirmed...
Page 39: 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 9 DLDP authentication mode Processing at the Authentication Processing at the DLDP packet sending side DLDP packet mode...
Page 40 Figure 8 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 8, Device A and Device B are connected through an optical fiber.
Page 41: Configuration Restrictions And Guidelines
Figure 9 Network diagram Port 2 Device B Port 1 Port 3 Device A Device C Port 4 Device D As shown in Figure 9, 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 42: 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 43: 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 44: Dldp Configuration Examples
Task Command through a port. interface-number ] Clear the statistics on DLDP packets passing reset dldp statistics [ interface interface-type through a port. interface-number ] DLDP configuration examples Configuring the auto port shutdown mode Network requirements As shown in Figure 10, Device A and Device B are connected through two fiber pairs.
Page 45 <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 46 <DeviceA> terminal logging level 6 The following log information is displayed on Device A: <DeviceA>%Jul 11 17:40:31:089 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is DOWN. %Jul 11 17:40:31:091 2012 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is DOWN. %Jul 11 17:40:31:677 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is DOWN.
Page 47: Configuring The Manual Port Shutdown Mode
%Jul 11 17:43:02:344 2012 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface GigabitEthernet1/0/1. %Jul 11 17:43:02:353 2012 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is UP. %Jul 11 17:43:02:357 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is UP. %Jul 11 17:43:02:362 2012 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface GigabitEthernet1/0/2.
Page 48 [DeviceA-GigabitEthernet1/0/2] dldp enable [DeviceA-GigabitEthernet1/0/2] quit # Set the port shutdown mode to manual. [DeviceA] dldp unidirectional-shutdown manual Configure Device B: # 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.
Page 49 Neighbor aged time: 12s The output shows that both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are in bidirectional state, which means both links are bidirectional. # Enable the monitoring of logs on the current terminal on Device A. Set the lowest level of the logs that can be output to the current terminal to 6.
Page 50 [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] shutdown The following log information is displayed on Device A: [DeviceA-GigabitEthernet1/0/1]%Jul 12 08:34:23:717 2012 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is DOWN. %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.
Page 51: Configuring The Hybrid Port Shutdown Mode
Configuring the hybrid port shutdown mode Network requirements As shown in Figure 12Figure 11, Device A and Device B are connected through two fiber pairs. 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.
Page 52 [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 hybrid. [DeviceB] dldp unidirectional-shutdown hybrid Verifying the configuration # Display the DLDP configuration globally and on all the DLDP-enabled ports of Device A.
Page 53 GigabitEthernet1/0/2 was deleted because the neighbor was aged. The neighbor's system MAC is 0023-8956-3600, and the port index is 165. %Jan 4 07:16:06:724 2011 DeviceA IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/1 changed to down. %Jan 4 07:16:06:730 2011 DeviceA IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/2 changed to down.
Page 54 %Jan 4 07:33:57:590 2011 DeviceA IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/1 changed to up. %Jan 4 07:33:57:609 2011 DeviceA STP/6/STP_DETECTED_TC: Instance 0's port GigabitEthernet1/0/1 detected a topology change. The output shows that the port status and link status of GigabitEthernet 1/0/1 are now up and its DLDP neighbors are determined.
Page 55: 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 56 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 57: 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 ...
Page 58: 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 59: 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 60 Figure 14 Schematic diagram for a single-ring network Domain 1 Device A Device B Master node Transit node Ring 1 Device D Device C Transit node Transit node Tangent rings As shown in Figure 15, two or more rings exist in the network topology and only one common node exists between rings.
Page 61 Figure 16 Schematic diagram for an intersecting-ring network Domain 1 Device B Device A Edge node Master node Device E Ring 1 Ring 2 Master node Device D Transit node Device C Assistant edge node Dual-homed rings As shown in Figure 17, two or more rings exist in the network topology and two similar common nodes exist between rings.
Page 62: Protocols And Standards
Figure 18 Schematic diagram for a single-ring load balancing network Device A Device B Domain 1 Ring 1 Domain 2 Device D Device C Intersecting-ring load balancing In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains.
Page 63: 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 64: 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 65: Configuring Rrpp Rings
Step Command Remarks Not required if the device is operating in PVST mode. Enter MST region view. For more information about the stp region-configuration command, see Layer 2—LAN Switching Command Reference. By default, all VLANs in an MST region are mapped to MSTI 0 (the •...
Page 66: Configuring Rrpp Nodes
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, the link type of an interface is access. Configure the link type of the For more information about the command, port link-type trunk interface as trunk.
Page 67: 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 68: Configuring Rrpp Timers
To activate an RRPP domain: Step Command Remarks Enter system view. system-view Enable RRPP. By default, RRPP is disabled. rrpp enable Enter RRPP domain view. rrpp domain domain-id Enable the specified RRPP By default, an RRPP ring is ring ring-id enable ring.
Page 69: 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 70 • 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 71 [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 72: 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 73 Figure 21 Network diagram Domain 1 Device B GE1/0/1 GE1/0/1 Edge node Device A GE1/0/3 Master node 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 74 # 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 75 [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 76 [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 77 [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 78: 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 79 Figure 22 Network diagram Domain 1 Device E Device A Device D Device G Master node Edge node & master node Edge node Master node GE1/0/1 GE1/0/4 GE1/0/2 GE1/0/2 GE1/0/3 GE1/0/1 GE1/0/1 GE1/0/1 Ring 2 Ring 4 Ring 1 Ring 3 Ring 5 GE1/0/1 GE1/0/2...
Page 80 # 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 81 [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 82 [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 83 # 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 84 [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 85 [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 86 # 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 87 [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 88: 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 89 Figure 23 Network diagram Domain 2 Device E GE1/0/1 Master node Device B GE1/0/2 Assistant edge node GE1/0/1 Ring 2 Device A GE1/0/1 GE1/0/3 Master node GE1/0/4 GE1/0/2 GE1/0/2 Ring 1 GE1/0/2 GE1/0/1 GE1/0/3 Device D Transit node GE1/0/4 GE1/0/2 Ring 3 GE1/0/1 Device C...
Page 90 [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] 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.
Page 91 # 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 # 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 92 # Configure VLAN 100 as the primary control VLAN of RRPP domain 1. [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 93 [DeviceC-GigabitEthernet1/0/1] link-delay 0 # 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 94 [DeviceC] rrpp domain 1 # 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 95 [DeviceD-GigabitEthernet1/0/1] link-delay 0 # 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 96 Configure Device E: # 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.
Page 97 Configure Device F: # 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.
Page 98: Troubleshooting Rrpp
Configure RRPP ring group settings on Device B and Device C: # 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.
Page 99: 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 24 ERPS ring structure Device A Device B Port A1 Port B1 RPL port Owner node Neighbor node Interconnection port...
Page 100: 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 24, ports A1, B1, E1, and F1 are RPL ports. Ports C3 and D3 are interconnection ports.
Page 101: Erps Node States
ERPS node states Table 12 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 102: 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 103 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 104: Erps Network Diagrams
ERPS network diagrams One major ring The network has one major ring. Figure 28 Network diagram Device A Device B Owner node Neighbor node Device D Device C One major ring connecting one subring The network has one major ring and one subring. Figure 29 Network diagram Device A Device B...
Page 105 Figure 30 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 31, subring 1 is connected to the major ring.
Page 106: Protocols And Standards
Figure 32 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 33 Network diagram 2 Device B Device A Device G Owner node...
Page 107: 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 108: 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 transparent transmission is erps tcn-propagation...
Page 109: 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. • Do not enable Ethernet OAM remote loopback for ERPS ring member ports. This feature might cause a broadcast storm.
Page 110: Configuring Control Vlans
Configuring control VLANs Follow these guidelines when you configure control VLANs: • Configure the same control VLAN for all nodes in an ERPS instance. • 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.
Page 111: Configuring The Node Role
Step Command Remarks to MSTI 0 (CIST). vlan-list • Method 2: This step is not required if the device is operating in PVST mode. vlan-mapping modulo modulo For more information about these commands, see Layer 2—LAN Switching Command Reference. This step is not required if the device is operating in PVST mode.
Page 112: Configuring R-Aps Packet Levels
Step Command Remarks Enter system view. system-view Enter ERPS ring erps ring ring-id view. Enter ERPS instance instance instance-id 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 113: Setting The Ms Mode
Step Command Remarks Enter system view. system-view Enter ERPS ring view. erps ring ring-id Enter ERPS instance instance instance-id view. 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.
Page 114: Associating An Erps Ring Member Port With A Track Entry
Associating an ERPS ring member port with a track entry Before you associate a port with a track entry, make sure the port has joined an ERPS instance. To associate an ERPS ring member port with a track entry: Step Command Remarks Enter system view.
Page 115: Erps Configuration Examples
ERPS configuration examples One-ring configuration example Network requirements As shown in Figure 34, perform the following tasks to eliminate loops on the network: • Configure the ring as ERPS ring 1. • Configure VLAN 100 as the control VLAN for ERPS ring 1. •...
Page 116 [DeviceA] interface gigabitethernet 1/0/2 [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 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 # Enable R-APS packets to carry ring ID in the destination MAC address.
Page 117 # Create track entry 1 and associate it with the CC function of CFD for MEP 1001 in Ethernet service instance 1. [DeviceA] track 1 cfd cc service-instance 1 mep 1001 # Associate GigabitEthernet 1/0/1 with track entry 1 and bring up the port. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] port erps ring 1 instance 1 track 1 [DeviceA-GigabitEthernet1/0/1] undo shutdown...
Page 118 # Enable R-APS packets to carry ring ID in the destination MAC address. [DeviceB-erps-ring1] r-aps ring-mac # Create ERPS instance 1. [DeviceB-erps-ring1] instance 1 # Configure the node role. [DeviceB-erps-ring1-inst1] node-role neighbor rpl port0 # Configure the control VLAN. [DeviceB-erps-ring1-inst1] control-vlan 100 # Configure the protected VLANs.
Page 119 # Associate GigabitEthernet 1/0/2 with track entry 3 and bring up the port. [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] port erps ring 1 instance 1 track 2 [DeviceB-GigabitEthernet1/0/2] undo shutdown [DeviceB-GigabitEthernet1/0/2] quit # Enable ERPS. [DeviceB] erps enable Configure Device C. # Create VLANs 1 to 30, map these VLANs to MSTI 1, and activate the MST region configuration.
Page 120 [DeviceC-erps-ring1-inst1] quit [DeviceC-erps-ring1] quit # Enable CFD, and create a level-5 MD named MD_A. [DeviceC] cfd enable [DeviceC] cfd md MD_A level 5 # Create Ethernet service instance 3, in which the MA is identified by a VLAN and serves VLAN [DeviceC] 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 3001 in Ethernet service instance 3, and enable CCM sending on GigabitEthernet 1/0/1.
Page 121 [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. [DeviceD-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port and assign it to VLANs 1 to 30.
Page 122 [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 123: One-Subring Configuration Example
WTR timer : 5 min Revertive operation : Revertive Enable status : Yes, Active status : Yes R-APS level Port PortRole PortStatus ---------------------------------------------------------------------------- Port0 Block Port1 Non-RPL The output shows the following information: • Device A is the owner node. •...
Page 124 Figure 35 Network diagram Device A Device B GE1/0/1 GE1/0/1 RPL port Owner node Neighbor node GE1/0/2 GE1/0/2 Major ring PRL Subring RPL Major ring GE1/0/2 GE1/0/2 GE1/0/1 GE1/0/1 Device D Device C GE1/0/3 GE1/0/3 Subring GE1/0/2 GE1/0/2 Device E Device F GE1/0/1 GE1/0/1...
Page 125 # 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. [DeviceA-erps-ring1-inst1] protected-vlan reference-instance 1 # Enable ERPS for instance 1. [DeviceA-erps-ring1-inst1] instance enable [DeviceA-erps-ring1-inst1] quit [DeviceA-erps-ring1] quit...
Page 126 [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 127 # 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 128 [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. [DeviceC-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port and assign it to VLANs 1 to 30. [DeviceC-GigabitEthernet1/0/1] port link-type trunk [DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/1] quit...
Page 129 [DeviceC] cfd meplist 3001 3002 service-instance 3 [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] cfd mep 3001 service-instance 3 outbound [DeviceC-GigabitEthernet1/0/2] cfd cc service-instance 3 mep 3001 enable [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 130 [DeviceC-erps-ring2] quit # Create Ethernet service instance 5, in which the MA is identified by a VLAN and serves VLAN [DeviceC] cfd service-instance 5 ma-id vlan-based md MD_A vlan 5 # Configure a MEP list in Ethernet service instance 5, create outward-facing MEP 5001 in Ethernet service instance 3, and enable CCM sending on GigabitEthernet 1/0/3.
Page 131 [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 # Create ERPS ring 1. [DeviceD] erps ring 1 # Configure ERPS ring member ports. [DeviceD-erps-ring1] port0 interface gigabitethernet 1/0/1 [DeviceD-erps-ring1] port1 interface gigabitethernet 1/0/2 # Create ERPS instance 1.
Page 132 [DeviceD-GigabitEthernet1/0/2] port erps ring 1 instance 1 track 1 [DeviceD-GigabitEthernet1/0/2] undo shutdown [DeviceD-GigabitEthernet1/0/2] quit # Create track entry 2 and associate it with the CC function of CFD for MEP 4002 in Ethernet service instance 4. [DeviceD] track 2 cfd cc service-instance 4 mep 4002 # Associate GigabitEthernet 1/0/1 with track entry 2 and bring up the port.
Page 133 [DeviceD] erps enable Configure Device E. # Create VLANs 1 to 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceE> system-view [DeviceE] vlan 1 to 30 [DeviceE] stp region-configuration [DeviceE-mst-region] instance 1 vlan 1 to 30 [DeviceE-mst-region] active region-configuration [DeviceE-mst-region] quit # Set the link state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.
Page 134 [DeviceE] cfd md MD_A level 5 # Create Ethernet service instance 6, in which the MA is identified by a VLAN and serves VLAN [DeviceE] 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 6001 in Ethernet service instance 6, and enable CCM sending on GigabitEthernet 1/0/2.
Page 135 # Set the link 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. [DeviceF-GigabitEthernet1/0/1] undo stp enable [DeviceF-GigabitEthernet1/0/1] port link-type trunk # Configure the port as a trunk port and assign it to VLANs 1 to 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.
Page 136 [DeviceF-GigabitEthernet1/0/2] quit # Create Ethernet service instance 7, in which the MA is identified by a VLAN and serves VLAN [DeviceF] cfd service-instance 7 ma-id vlan-based md MD_A vlan 7 # Configure a MEP list in Ethernet service instance 7, create outward-facing MEP 7002 in Ethernet service instance 7, and enable CCM sending on GigabitEthernet 1/0/1.
Page 137: One-Ring Multi-Instance Load Balancing Configuration Example
Enable status : Yes, Active status : Yes R-APS level Port PortRole PortStatus ---------------------------------------------------------------------------- Port0 Block Port1 Non-RPL The output shows the following information: • Device A is the owner node. • The ERPS ring is in idle state. • The RPL port is blocked.
Page 138 # Create VLANs 1 to 60, map VLANs 1 to 30 to MSTI 1, map VLANs 31 to 60 to MSTI 2, and activate the MST region configuration. <DeviceA> system-view [DeviceA] vlan 1 to 60 [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 [DeviceA-mst-region] instance 2 vlan 31 to 60 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit...
Page 139 [DeviceA-erps-ring1-inst2] protected-vlan reference-instance 2 # Enable ERPS for instance 2. [DeviceA-erps-ring1-inst2] instance enable [DeviceA-erps-ring1-inst2] quit [DeviceA-erps-ring1] quit # Enable CFD, and create a level-5 MD named MD_A. [DeviceA] cfd enable [DeviceA] cfd md MD_A level 5 # Create Ethernet service instance 1, in which the MA is identified by a VLAN and serves VLAN [DeviceA] 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 1001 in Ethernet service instance 1, and enable CCM sending on GigabitEthernet 1/0/1.
Page 140 [DeviceA] erps enable Configure Device B. # Create VLANs 1 to 60, map VLANs 1 to 30 to MSTI 1, map VLANs 31 to 60 to MSTI 2, and activate the MST region configuration. <DeviceB> system-view [DeviceB] vlan 1 to 60 [DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 1 to 30 [DeviceB-mst-region] instance 2 vlan 31 to 60...
Page 141 [DeviceB-erps-ring1-inst2] control-vlan 110 # Configure the protected VLANs. [DeviceB-erps-ring1-inst2] protected-vlan reference-instance 2 # Enable ERPS for instance 2. [DeviceB-erps-ring1-inst2] instance enable [DeviceB-erps-ring1-inst2] 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...
Page 142 [DeviceB-GigabitEthernet1/0/2] quit # Enable ERPS. [DeviceB] erps enable Configure Device C. # Create VLANs 1 to 60, map VLANs 1 to 30 to MSTI 1, map VLANs 31 to 60 to MSTI 2, and activate the MST region configuration. <DeviceC> system-view [DeviceC] vlan 1 to 60 [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30...
Page 143 [DeviceC-erps-ring1-inst2] node-role owner rpl port0 # Configure the control VLAN. [DeviceC-erps-ring1-inst2] control-vlan 110 # Configure the protected VLANs. [DeviceC-erps-ring1-inst2] protected-vlan reference-instance 2 # Enable ERPS for instance 2. [DeviceC-erps-ring1-inst2] instance enable [DeviceC-erps-ring1-inst2] quit [DeviceC-erps-ring1] quit # Enable CFD, and create a level-5 MD named MD_A. [DeviceC] cfd enable [DeviceC] cfd md MD_A level 5 # Create Ethernet service instance 3, in which the MA is identified by a VLAN and serves VLAN...
Page 144 [DeviceC-GigabitEthernet1/0/1] port erps ring 1 instance 2 track 2 [DeviceC-GigabitEthernet1/0/1] undo shutdown [DeviceC-GigabitEthernet1/0/1] quit # Enable ERPS. [DeviceC] erps enable Configure Device D. # Create VLANs 1 to 60, map VLANs 1 to 30 to MSTI 1, map VLANs 31 to 60 to MSTI 2, and activate the MST region configuration.
Page 145 [DeviceD-erps-ring1] instance 2 # Configure the node role. [DeviceD-erps-ring1-inst2] node-role neighbor rpl port0 # Configure the control VLAN. [DeviceD-erps-ring1-inst2] control-vlan 110 # Configure the protected VLANs. [DeviceD-erps-ring1-inst2] protected-vlan reference-instance 2 # Enable ERPS for instance 2. [DeviceD-erps-ring1-inst2] instance enable [DeviceD-erps-ring1-inst2] quit [DeviceD-erps-ring1] quit # Enable CFD, and create a level-5 MD named MD_A.
Page 146 # Associate GigabitEthernet 1/0/1 with track entry 2 and bring up the port for ERPS instances 1 and 2. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] port erps ring 1 instance 1 track 2 [DeviceD-GigabitEthernet1/0/1] port erps ring 1 instance 2 track 2 [DeviceD-GigabitEthernet1/0/1] undo shutdown [DeviceD-GigabitEthernet1/0/1] quit # Enable ERPS.
Page 147: Troubleshooting Erps
---------------------------------------------------------------------------- Port0 Non-RPL Port1 Non-RPL The output shows the following information: • For ERPS instance 1: Device A is the owner node.  The ERPS ring is in idle state.  The RPL port is blocked.  The non-RPL port is unblocked. ...
Page 148: 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 37 Dual uplink network diagram Core network Port 3 Device A Device B Device E Port 3 Port 3 Primary link...
Page 149: 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 150: 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 151: 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 152: 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: All VLANs in an MST region are instance instance-id vlan Configure the mapped to CIST (MSTI 0) by vlan-id-list VLAN-to-instance mapping default.
Page 153: 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 By default, an interface is not port smart-link group group-id smart link group. { primary | secondary } a smart link group member.
Page 154: 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 155: 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 156: Control Vlan
[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 157 # 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 158 [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 159 # 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 160: 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 161 # 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 162 [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 163 # 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 164: 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 165 # 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 166 [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 167 [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 168 [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 169 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 170: 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 41 Monitor Link application scenario Core network Port 3...
Page 171: 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 172: 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 the following interfaces: •...
Page 173: Configuring The Uplink Interface Threshold For Triggering Monitor Link Group State Switchover
Configuring the uplink interface threshold for triggering monitor link group state switchover Step Command Remarks Enter system view. system-view Enter monitor link group view. monitor-link group group-id Configure the uplink interface By default, the uplink interface uplink up-port-threshold threshold for triggering monitor threshold for triggering monitor number-of-port link group state switchover.
Page 174 Figure 42 Network diagram Device A Device B Device D Device C 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.
Page 175 # Configure GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port for smart link group 1. [DeviceC-smlk-group1] port gigabitethernet 1/0/1 primary [DeviceC-smlk-group1] port gigabitethernet 1/0/2 secondary # Enable the smart link group to transmit flush messages. [DeviceC-smlk-group1] flush enable [DeviceC-smlk-group1] quit # Bring up GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2.
Page 176 # Configure the interface as a trunk port. [DeviceB-GigabitEthernet1/0/2] port link-type trunk # Assign the interface to VLANs 1 through 30. [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 # Enable flush message receiving on the interface. [DeviceB-GigabitEthernet1/0/2] smart-link flush enable [DeviceB-GigabitEthernet1/0/2] quit # Create monitor link group 1.
Page 177 [DeviceB] display monitor-link group 1 Monitor link group 1 information: Group status : UP Downlink up-delay: 0(s) Last-up-time : 16:38:26 2012/4/21 Last-down-time : 16:37:20 2012/4/21 Up-port-threshold: 1 Member Role Status -------------------------------------------- GE1/0/1 UPLINK GE1/0/2 DOWNLINK # Verify information about monitor link group 1 on Device D. [DeviceD] display monitor-link group 1 Monitor link group 1 information: Group status...
Page 178: Configuring Vrrp
Configuring VRRP Overview Typically, you can configure a default gateway for every host on a LAN. All packets destined for other networks are sent through the default gateway. As shown in Figure 43, when the default gateway fails, no hosts can communicate with external networks. Figure 43 LAN networking Host A Network...
Page 179: Vrrp Standard Mode
VRRP standard mode In VRRP standard mode, only the master in the VRRP group can provide gateway service. When the master fails, the backup routers elect a new master to take over for nonstop gateway service. Figure 44 VRRP networking Virtual router Router A Host A...
Page 180: Vrrp Timers
The sender fills an authentication key into the VRRP packet, and the receiver compares the received authentication key with its local authentication key. If the two authentication keys match, the received VRRP packet is legitimate. Otherwise, the received packet is illegitimate and gets discarded.
Page 181: Vrrp Tracking
It remains a backup when operating in non-preemptive mode.  It becomes the master when operating in preemptive mode.  The elected master starts a VRRP advertisement interval to periodically send VRRP advertisements to notify the backups that it is operating correctly. Each of the backups starts a timer to wait for advertisements from the master.
Page 182 Figure 45 VRRP in master/backup mode Router A Master Host A Router B Backup Network Network Host B Router C Backup Host C Assume that Router A is acting as the master to forward packets to external networks, and Router B and Router C are backups in listening state.
Page 183: Vrrp Load Balancing Mode
• VRRP group 3—Router C is the master. Router A and Router B are the backups. To implement load sharing among Router A, Router B, and Router C, perform the following tasks: • Configure the virtual IP addresses of VRRP group 1, 2, and 3 as default gateway IP addresses for hosts on the subnet.
Page 184 When an ARP request arrives, the master (Router A) selects a virtual MAC address based on the load balancing algorithm to answer the ARP request. In this example, Router A returns the virtual MAC address of itself in response to the ARP request from Host A. Router A returns the virtual MAC address of Router B in response to the ARP request from Host B.
Page 185: Virtual Forwarder
For more information about ARP packet source MAC address consistency check and ARP detection, see Security Configuration Guide. Virtual forwarder Virtual forwarder creation Virtual MAC addresses enable traffic distribution across routers in a VRRP group. To enable routers in the VRRP group to forward packets, VFs must be created on them. Each VF is associated with a virtual MAC address in the VRRP group and forwards packets that are sent to this virtual MAC address.
Page 186 Figure 50 VF information Virtual MAC address VF priority State VF 1 000f-e2ff-0011 VF 2 000f-e2ff-0012 Virtual IP address: VF 3 000f-e2ff-0013 10.1.1.1/24 Virtual Router A MAC address VF priority State Master VF 1 000f-e2ff-0011 10.1.1.2/24 Host A VF 2 000f-e2ff-0012 VF 3 000f-e2ff-0013...
Page 187: Protocols And Standards
VF tracking An AVF forwards packets destined for the MAC address of the AVF. If the AVF's upstream link fails but no LVF takes over, the hosts that use the AVF's MAC address as their gateway MAC address cannot access the external network. The VF tracking function can solve this problem.
Page 188: Specifying The Ipv4 Vrrp Version
Step Command Remarks • Specify the standard mode: undo vrrp mode Specify an IPv4 VRRP By default, VRRP operates in • Specify the load balancing operating mode. standard mode. mode: vrrp mode load-balance [ version-8 ] Specifying the IPv4 VRRP version The VRRP version on all routers in an IPv4 VRRP group must be the same.
Page 189: Configuring The Router Priority, Preemptive Mode, And Tracking Function
• The virtual IP address of an IPv4 VRRP group and the downlink interface IP address of the VRRP group must be in the same subnet. Otherwise, the hosts in the subnet might fail to access external networks. Configuration procedure To create a VRRP group and assign a virtual IP address: Step Command...
Page 190: Configuring Ipv4 Vrrp Packet Attributes
Configuring IPv4 VRRP packet attributes Configuration guidelines • You can configure different authentication modes and authentication keys for VRRP groups on an interface. However, members of the same VRRP group must use the same authentication mode and authentication key. • In VRRPv2, all routers in a VRRP group must have the same VRRP advertisement interval.
Page 191: Configuring Vf Tracking
Configuring VF tracking You can configure VF tracking in both standard mode and load balancing mode, but the function takes effect only in load balancing mode. In load balancing mode, you can establish the collaboration between the VFs and NQA or BFD through the tracking function.
Page 192: Displaying And Maintaining Ipv4 Vrrp
To disable an IPv4 VRRP group: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, a VRRP group is vrrp vrid virtual-router-id Disable a VRRP group. enabled. shutdown Displaying and maintaining IPv4 VRRP Execute display commands in any view and the reset command in user view. Task Command Display states of IPv4 VRRP...
Page 193: Creating A Vrrp Group And Assigning A Virtual Ipv6 Address
After the IPv6 VRRP operating mode is specified on a router, all IPv6 VRRP groups on the router operate in the specified operating mode. To specify an IPv6 VRRP operating mode: Step Command Remarks Enter system view. system-view • Specify the standard mode: undo vrrp ipv6 mode Specify an IPv6 VRRP By default, VRRP operates in...
Page 194: Configuring The Router Priority, Preemptive Mode, And Tracking Function
Step Command Remarks address you remove. Only one link local address is allowed in a VRRP group. (Optional.) Assign a virtual By default, no global unicast vrrp ipv6 vrid virtual-router-id IPv6 address, which is a address is assigned for an IPv6 virtual-ip virtual-address global unicast address.
Page 195: Configuring Ipv6 Vrrp Packet Attributes
router decrease by a specific value. When the state of the track entry transits to Positive or Notready, the original weights of the VFs restore. Configuration guidelines • By default, the weight of a VF is 255, and its lower limit of failure is 10. •...
Page 196: Disabling An Ipv6 Vrrp Group
Step Command Remarks advertisement interval to be greater than 100 centiseconds. Return to system view. quit The DSCP value identifies the packet priority during Set a DSCP value for IPv6 transmission. vrrp ipv6 dscp dscp-value VRRP packets. By default, the DSCP value for IPv6 VRRP packets is 56.
Page 197 Figure 51 Network diagram Virtual IP address: 10.1.1.111/24 GE1/0/5 Vlan-int2 10.1.1.1/24 Switch A 10.1.2.1/24 Internet 10.1.1.3/24 Host B Host A GE1/0/5 Vlan-int2 10.1.1.2/24 Switch B Configuration procedure Configure Switch A: # Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port gigabitethernet 1/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 10.1.1.1 255.255.255.0...
Page 198 [SwitchB-Vlan-interface2] vrrp vrid 1 preempt-mode delay 5000 Verifying the configuration # Ping Host B from Host A. (Details not shown.) # Display detailed information about VRRP group 1 on Switch A. [SwitchA-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 1 Interface Vlan-interface2...
Page 199: Multiple Vrrp Groups Configuration Example
Virtual MAC : 0000-5e00-0101 Master IP : 10.1.1.2 The output shows that when Switch A fails, Switch B takes over to forward packets from Host A to Host B. # Recover the link between Host A and Switch A, and display detailed information about VRRP group 1 on Switch A.
Page 200 Configuration procedure Configure Switch A: # Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port gigabitethernet 1/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 10.1.1.1 255.255.255.128 # Create VRRP group 1, and set its virtual IP address to 10.1.1.100. [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.100 # Assign Switch A a higher priority than Switch B in VRRP group 1, so Switch A can become the master in the group.
Page 201 [SwitchA-Vlan-interface3] display vrrp verbose IPv4 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 2 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time...
Page 202: Vrrp Load Balancing Configuration Example
• Switch A is operating as the master in VRRP group 1 to forward Internet traffic for hosts that use the default gateway 10.1.1.100/25. • Switch B is operating as the master in VRRP group 2 to forward Internet traffic for hosts that use the default gateway 10.1.1.200/25.
Page 203 [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.1 # Assign Switch A the highest priority in VRRP group 1, so Switch A can become the master. [SwitchA-Vlan-interface2] vrrp vrid 1 priority 120 # Configure Switch A to operate in preemptive mode, so it can become the master whenever it operates correctly.
Page 204 [SwitchC] vrrp mode load-balance # Create VRRP group 1, and set its virtual IP address to 10.1.1.1. [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] ip address 10.1.1.4 24 [SwitchC-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.1 # Configure Switch C to operate in preemptive mode, and set the preemption delay to 5000 centiseconds.
Page 205 Forwarder 03 State : Listening Virtual MAC : 000f-e2ff-0013 (Learnt) Owner ID : 0000-5e01-1105 Priority : 127 Active : 10.1.1.4 Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 # Display detailed information about VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode...
Page 206 [SwitchC-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode : Load Balance Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes...
Page 207 Admin Status : Up State : Master Config Pri : 120 Running Pri : 120 Preempt Mode : Yes Delay Time : 5000 Auth Type : None Virtual IP : 10.1.1.1 Member IP List : 10.1.1.2 (Local, Master) 10.1.1.3 (Backup) 10.1.1.4 (Backup) Forwarder Information: 3 Forwarders 0 Active Config Weight...
Page 208 Config Weight : 255 Running Weight : 255 Forwarder 01 State : Active Virtual MAC : 000f-e2ff-0011 (Take Over) Owner ID : 0000-5e01-1101 Priority : 85 Active : local Forwarder 02 State : Listening Virtual MAC : 000f-e2ff-0012 (Learnt) Owner ID : 0000-5e01-1103 Priority : 85...
Page 209 Owner ID : 0000-5e01-1103 Priority : 127 Active : 10.1.1.3 Forwarder 03 State : Active Virtual MAC : 000f-e2ff-0013 (Owner) Owner ID : 0000-5e01-1105 Priority : 255 Active : local Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 The output shows that when the timeout timer expires, the VF for virtual MAC address 000f-e2ff-0011 is removed.
Page 210: Ipv6 Vrrp Configuration Examples
IPv6 VRRP configuration examples Single VRRP group configuration example Network requirements As shown in Figure 54, Switch A and Switch B form a VRRP group. They use the virtual IP addresses 1::10/64 and FE80::10 to provide gateway service for the subnet where Host A resides. Host A learns 1::10/64 as its default gateway from RA messages sent by the switches.
Page 211 # Enable Switch A to send RA messages, so Host A can learn the default gateway address. [SwitchA-Vlan-interface2] undo ipv6 nd ra halt Configure Switch B: # Configure VLAN 2. <SwitchB> system-view [SwitchB] vlan 2 [SwitchB-vlan2] port gigabitethernet 1/0/5 [SwitchB-vlan2] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] ipv6 address fe80::2 link-local [SwitchB-Vlan-interface2] ipv6 address 1::2 64...
Page 212 Auth Type : None Virtual IP : FE80::10 1::10 Master IP : FE80::1 The output shows that Switch A is operating as the master in VRRP group 1 to forward packets from Host A to Host B. # Disconnect the link between Host A and Switch A, and verify that Host A can still ping Host B. (Details not shown.) # Display detailed information about VRRP group 1 on Switch B.
Page 213: Multiple Vrrp Groups Configuration Example
Multiple VRRP groups configuration example Network requirements As shown in Figure 55, Switch A and Switch B form two VRRP groups. VRRP group 1 uses the virtual IPv6 addresses 1::10/64 and FE80::10 to provide gateway service for hosts in VLAN 2. VRRP group 2 uses the virtual IPv6 addresses 2::10/64 and FE90::10 to provide gateway service for hosts in VLAN 3.
Page 214 [SwitchA-Vlan-interface2] undo ipv6 nd ra halt [SwitchA-Vlan-interface2] quit # Configure VLAN 3. [SwitchA] vlan 3 [SwitchA-vlan3] port gigabitethernet 1/0/6 [SwitchA-vlan3] quit [SwitchA] interface vlan-interface 3 [SwitchA-Vlan-interface3] ipv6 address fe90::1 link-local [SwitchA-Vlan-interface3] ipv6 address 2::1 64 # Create VRRP group 2, and set its virtual IPv6 addresses to FE90::10 and 2::10. [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip fe90::10 link-local [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip 2::10 # Enable Switch A to send RA messages, so hosts in VLAN 3 can learn the default gateway...
Page 215 Verifying the configuration # Display detailed information about the VRRP groups on Switch A. [SwitchA-Vlan-interface3] display vrrp ipv6 verbose IPv6 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 2 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State...
Page 216: Vrrp Load Balancing Configuration Example
Auth Type : None Virtual IP : FE90::10 2::10 Virtual MAC : 0000-5e00-0202 Master IP : FE90::2 The output shows the following information: • Switch A is operating as the master in VRRP group 1 to forward Internet traffic for hosts that use the default gateway 1::10/64.
Page 217: Gateway Address
[SwitchA-vlan2] port gigabitethernet 1/0/5 [SwitchA-vlan2] quit # Configure VRRP to operate in load balancing mode. [SwitchA] vrrp ipv6 mode load-balance # Create VRRP group 1, and set its virtual IPv6 addresses to FE80::10 and 1::10. [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ipv6 address fe80::1 link-local [SwitchA-Vlan-interface2] ipv6 address 1::1 64 [SwitchA-Vlan-interface2] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local [SwitchA-Vlan-interface2] vrrp ipv6 vrid 1 virtual-ip 1::10...
Page 218: Default Gateway Address
# Enable Switch B to send RA messages so hosts on subnet 1::/64 can learn the default gateway address. [SwitchB-Vlan-interface2] undo ipv6 nd ra halt [SwitchB-Vlan-interface2] quit # Create track entry 1 to monitor the upstream link status of VLAN-interface 3. When the upstream link fails, the track entry transits to Negative.
Page 219 Admin Status : Up State : Master Config Pri : 120 Running Pri : 120 Preempt Mode : Yes Delay Time : 5000 Auth Type : None Virtual IP : FE80::10 1::10 Member IP List : FE80::1 (Local, Master) FE80::2 (Backup) FE80::3 (Backup) Forwarder Information: 3 Forwarders 1 Active Config Weight...
Page 220 FE80::3 (Backup) Forwarder Information: 3 Forwarders 1 Active Config Weight : 255 Running Weight : 255 Forwarder 01 State : Listening Virtual MAC : 000f-e2ff-4011 (Learnt) Owner ID : 0000-5e01-1101 Priority : 127 Active : FE80::1 Forwarder 02 State : Active Virtual MAC : 000f-e2ff-4012 (Owner) Owner ID...
Page 221 Priority : 127 Active : FE80::1 Forwarder 02 State : Listening Virtual MAC : 000f-e2ff-4012 (Learnt) Owner ID : 0000-5e01-1103 Priority : 127 Active : FE80::2 Forwarder 03 State : Active Virtual MAC : 000f-e2ff-4013 (Owner) Owner ID : 0000-5e01-1105 Priority : 255 Active...
Page 222 Priority Active : FE80::2 Forwarder 03 State : Initialize Virtual MAC : 000f-e2ff-4013 (Learnt) Owner ID : 0000-5e01-1105 Priority Active : FE80::3 Forwarder Weight Track Information: Track Object State : Negative Weight Reduced : 250 # Display detailed information about VRRP group 1 on Switch C. [SwitchC-Vlan-interface2] display vrrp ipv6 verbose IPv6 Virtual Router Information: Running Mode...
Page 223 Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 The output shows that when VLAN-interface 3 on Switch A fails, the weights of the VFs on Switch A drop below the lower limit of failure. All VFs on Switch A transit to the Initialized state and cannot forward traffic.
Page 224: Troubleshooting Vrrp
Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 5000 Auth Type : None Virtual IP : FE80::10 1::10 Member IP List : FE80::2 (Local, Master) FE80::3 (Backup) Forwarder Information: 2 Forwarders 1 Active Config Weight...
Page 225: Multiple Masters Appear In A Vrrp Group
• A device in the VRRP group receives illegitimate VRRP packets. For example, the IP address owner receives a VRRP packet with the priority 255. Solution To resolve the problem: Modify the configuration on routers in VRRP groups to ensure consistent configuration. Take fault location and anti-attack measures to eliminate potential threats.
Page 226: 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 227: 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 228: Protocols And Standards
Protocols and standards • RFC 5880, Bidirectional Forwarding Detection (BFD) • RFC 5881, Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop) • RFC 5882, Generic Application of Bidirectional Forwarding Detection (BFD) • RFC 5883, Bidirectional Forwarding Detection (BFD) for Multihop Paths •...
Page 229: Configuring Control Packet Mode
Step Command Remarks By default, no source IP address is configured for echo packets. • Configure the source IP The source IP address cannot be address of echo packets: on the same network segment as any local interface's IP address. bfd echo-source-ip Configure the source IP Otherwise, a large number of...
Page 230 Step Command Remarks By default, the echo packet mode is disabled. BFD version 0 does not support this command. The configuration does not take effect. Configure this command for BFD Enable the echo packet bfd echo [ receive | send ] sessions in which control packets mode.
Page 231: Configuring A Bfd Template
Configuring a BFD template Perform this task to specify BFD parameters in a template for sessions without next hops. You can configure BFD parameters for LSPs and PWs through a BFD template. To configure a BFD template: Step Command Remarks Enter system view.
Page 232: 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 233: Collaboration Application Example
• Redundancy group. • VPLS. • MPLS L2VPN. • EAA. • ERPS. When configuring a track entry for an application module, you can set a notification delay to avoid immediate notification of status changes. When the delay is not configured and the route convergence is slower than the link state change notification, communication failures occur.
Page 234: Associating The Track Module With A Detection Module
Tasks at a glance • Associating Track with static routing • Associating Track with PBR • Associating Track with Smart Link • Associating Track with VPLS • Associating Track with MPLS L2VPN • Associating Track with EAA • Associating Track with ERPS Associating the Track module with a detection module Associating Track with NQA...
Page 235: Associating Track With Cfd
To associate Track with BFD: Step Command Remarks Enter system view. system-view By default, no track entries exist. track track-entry-number bfd echo Create a track entry, and Do not configure the interface interface-type interface-number associate it with a BFD virtual IP address of a remote ip remote-ip-address local ip session.
Page 236: Associating Track With Route Management
Step Command Remarks • Create a track entry, and associate it with the interface management module to monitor the link status of an interface: track track-entry-number interface interface-type interface-number [ delay { negative negative-time | positive positive-time } * ] •...
Page 237: Associating The Track Module With An Application Module
• When the neighbor of the monitored LLDP interface is available, the LLDP module informs the Track module. The Track module sets the track entry to Positive state. • When the neighbor of the monitored LLDP interface is unavailable, the LLDP module informs the Track module.
Page 238: Associating Track With Static Routing
An IP address owner is the router with its interface IP address used as the virtual IP address of the VRRP group. • When the status of the track entry changes from Negative to Positive or NotReady, the associated router or VF restores its priority automatically. Associating Track with a VRRP group Step Command...
Page 239 • If the track entry is in Negative state, the following conditions exist: The next hop of the static route is not reachable.  The configured static route is invalid.  • If the track entry is in NotReady state, the following conditions exist: The accessibility of the next hop of the static route is unknown.
Page 240: Associating Track With Pbr
Step Command Remarks [ description text ] Associating Track with PBR PBR uses user-defined policies to route packets. You can specify the next hop for packets that match specific ACLs. For more information about PBR, see Layer 3—IP Routing Configuration Guide. PBR cannot detect the availability of any action taken on packets.
Page 241: Associating Track With Smart Link
Step Command Remarks Create a policy or policy ipv6 policy-based-route policy-name [ deny node and enter PBR policy | permit ] node node-number node view. Define an ACL match if-match acl { acl6-number | name By default, no ACL criterion. acl6-name } match criterion exists.
Page 242: Associating Track With Vpls
Associating Track with VPLS When you associate Track with an AC on a VPLS network, the AC is up only when one or more of the associated track entries are positive. Associating Track with an AC helps detect AC failures. For example, when an AC is a VE-L2VPN interface, the AC interface will not go down upon a link failure because the interface is a virtual interface.
Page 243 interface. To resolve the problem, you can associate Track with the AC to detect failures on the link that connects the PE-agg to the L3VPN or IP backbone. When a failure occurs on the link, the VE-L2VPN interface is set to down. Consequently, the PW bound to the AC goes down. If the PW has a backup PW, traffic can be switched to the backup PW.
Page 244: Associating Track With Eaa
Step Command Remarks track-entry-number&<1-3> To associate a track entry with an Ethernet service instance bound to a BGP cross-connect: Step Command Remarks Enter system view. system-view Enter cross-connect group xconnect-group group-name view. Enter auto-discovery auto-discovery bgp cross-connect group view. site site-id [ range range-value ] Enter site view.
Page 245: Associating Track With Erps
Step Command Remarks state { negative | positive } not monitor any track event. [ suppress-time suppress-time ] Associating Track with ERPS To detect and clear link faults typically for a fiber link, use ERPS with CFD and Track. You can associate ERPS ring member ports with the continuity check function of CFD through track entries.
Page 246 • Host A requires access to Host B. The default gateway of Host A is 10.1.1.10/24. • Switch A and Switch B belong to VRRP group 1. The virtual IP address of VRRP group 1 is 10.1.1.10. Configure VRRP-Track-NQA collaboration to monitor the uplink on the master and meet the following requirements: •...
Page 247 # Specify VRRPv2 to run on the interface VLAN-interface 2. [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] vrrp version 2 # Create VRRP group 1, and configure the virtual IP address 10.1.1.10 for the group. [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.10 # Set the priority of Switch A to 110 in VRRP group 1. [SwitchA-Vlan-interface2] vrrp vrid 1 priority 110 # Set the authentication mode of VRRP group 1 to simple, and the authentication key to hello.
Page 248 VRRP Track Information: Track Object State : Positive Pri Reduced : 30 # Display detailed information about VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer...
Page 249: Configuring Bfd For A Vrrp Backup To Monitor The Master
Virtual MAC : 0000-5e00-0101 Master IP : 10.1.1.2 The output shows that Switch A becomes the backup, and Switch B becomes the master. Switch B forwards packets from Host A to Host B. Configuring BFD for a VRRP backup to monitor the master Network requirements As shown in Figure...
Page 250 [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 192.168.0.10 # Set the priority of Switch A to 110 in VRRP group 1. [SwitchA-Vlan-interface2] vrrp vrid 1 priority 110 [SwitchA-Vlan-interface2] return Configure Switch B: # Specify 10.10.10.10 as the source address of BFD echo packets. <SwitchB>...
Page 251 VRRP Track Information: Track Object State : Positive Switchover # Display information about track entry 1 on Switch B. <SwitchB> display track 1 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...
Page 252: Configuring Bfd For The Vrrp Master To Monitor The Uplinks
Configuring BFD for the VRRP master to monitor the uplinks Network requirements As shown in Figure • Switch A and Switch B belong to VRRP group 1. The virtual IP address of VRRP group 1 is 192.168.0.10. • The default gateway of the hosts in the LAN is 192.168.0.10. Configure VRRP-Track-BFD collaboration to monitor the uplink on the master and meet the following requirements: •...
Page 253 [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 192.168.0.10 # Set the priority of Switch A to 110 in VRRP group 1. [SwitchA-Vlan-interface2] vrrp vrid 1 priority 110 # Associate VRRP group 1 with track entry 1 and decrease the router priority by 20 when the state of track entry 1 changes to negative.
Page 254 Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Become Master : 2200ms left Auth Type : None Virtual IP...
Page 255: Static Routing-Track-Nqa Collaboration Configuration Example
Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 192.168.0.10 Virtual MAC : 0000-5e00-0101 Master IP : 192.168.0.102 The output shows that when Switch A detects that the uplink fails through BFD, it decreases its priority by 20.
Page 256 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. <SwitchA> system-view [SwitchA] ip route-static 30.1.1.0 24 10.1.1.2 track 1 # Configure a static route to 30.1.1.0/24 with the next hop 10.3.1.3 and the priority 80. [SwitchA] ip route-static 30.1.1.0 24 10.3.1.3 preference 80 # Configure a static route to 10.2.1.4 with the next hop 10.1.1.2.
Page 257 # 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. [SwitchD] nqa entry admin test # Specify the ICMP echo operation type. [SwitchD-nqa-admin-test] type icmp-echo # Specify 10.1.1.1 as the destination address of the operation.
Page 258 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. # Remove the IP address of interface VLAN-interface 2 on Switch B. <SwitchB>...
Page 259: Static Routing-Track-Bfd Collaboration Configuration Example
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 round-trip min/avg/max/std-dev = 1/1/2/1 ms # 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.
Page 260 Figure 61 Network diagram Switch A Switch B Vlan-int5 Vlan-int2 Vlan-int2 Vlan-int6 20.1.1.1/24 10.2.1.1/24 10.2.1.2/24 30.1.1.1/24 30.1.1.0/24 20.1.1.0/24 Vlan-int3 Vlan-int4 10.3.1.1/24 10.4.1.2/24 Vlan-int3 Vlan-int4 10.3.1.3/24 10.4.1.3/24 Switch C Configuration procedure Create VLANs and assign ports to them. Configure the IP address of each VLAN interface, as shown in Figure 61.
Page 261 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 262 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 263: Vrrp-Track-Interface Management Collaboration Configuration Example
VRRP-Track-interface management collaboration configuration example Network requirements As shown in Figure • Host A requires access to Host B. The default gateway of Host A is 10.1.1.10/24. • Switch A and Switch B belong to VRRP group 1. The virtual IP address of VRRP group 1 is 10.1.1.10.
Page 264 [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.10 Verifying the configuration # Ping Host B from Host A to verify that Host B is reachable. (Details not shown.) # Display detailed information about VRRP group 1 on Switch A. [SwitchA-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode...
Page 265: Vrrp-Track-Route Management Collaboration Configuration Example
Admin Status : Up State : Backup Config Pri : 110 Running Pri : 80 Preempt Mode : Yes Delay Time Become Master : 2200ms left Auth Type : None Virtual IP : 10.1.1.10 Master IP : 10.1.1.2 VRRP Track Information: Track Object State : Negative Pri Reduced : 30...
Page 266 Figure 63 Network diagram Virtual IP address: 10.1.1.10/24 Vlan-int2 Vlan-int3 10.1.1.1/24 10.1.2.1/24 Vlan-int3 10.1.2.2/24 Switch A Switch C 20.1.1.1/24 10.1.1.3/24 Internet Host B Host A Vlan-int3 Vlan-int2 10.1.3.1/24 10.1.1.2/24 Vlan-int3 10.1.3.2/24 Switch B Switch D Configuration procedure Configure the IP address of each interface, as shown in Figure 63.
Page 267 <SwitchB> system-view [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.10 [SwitchB-Vlan-interface2] quit Verifying the configuration # Ping Host B from Host A to verify that Host B is reachable. (Details not shown.) # Display detailed information about VRRP group 1 on Switch A. [SwitchA] display vrrp verbose IPv4 Virtual Router Information: Running Mode...
Page 268: Static Routing-Track-Lldp Collaboration Configuration Example
Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 110 Running Pri : 80 Preempt Mode : Yes Delay Time Become Master : 2200ms left Auth Type : None Virtual IP : 10.1.1.10 Master IP : 10.1.1.2 VRRP Track Information:...
Page 269 Figure 64 Network diagram Device A Device B GE1/03 GE1/0/1 GE1/0/1 GE1/0/3 20.1.1.1/24 10.2.1.1/24 10.2.1.2/24 30.1.1.1/24 30.1.1.0/24 20.1.1.0/24 GE1/0/2 GE1/0/2 10.3.1.1/24 10.4.1.2/24 GE1/0/1 GE1/0/2 10.3.1.3/24 10.4.1.3/24 Device C Configuration procedure Configure the IP address of each interface, as shown in Figure 64.
Page 270 <DeviceC> system-view [DeviceC] ip route-static 30.1.1.0 24 10.4.1.2 # Configure a static route to 20.1.1.0/24 with next hop 10.3.1.1. [DeviceC] ip route-static 20.1.1.0 24 10.3.1.1 Verifying the configuration # Display track entry information on Device A. [DeviceA] display track all Track ID: 1 State: Positive Duration: 0 days 0 hours 0 minutes 32 seconds...
Page 271: Smart Link-Track-Cfd Collaboration Configuration Example
[DeviceA] display ip routing-table Destinations : 9 Routes : 9 Destination/Mask Proto Cost NextHop Interface 10.2.1.0/24 Direct 0 10.2.1.1 GE1/0/1 10.2.1.1/32 Direct 0 127.0.0.1 InLoop0 10.3.1.0/24 Direct 0 10.3.1.1 GE1/0/2 10.3.1.1/32 Direct 0 127.0.0.1 InLoop0 20.1.1.0/24 Direct 0 20.1.1.1 GE1/0/3 20.1.1.1/32 Direct 0 127.0.0.1...
Page 272: 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 273: 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 274: 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 take effect for all placement program default Enter placement process processes. Settings in •...
Page 275: 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 276: 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 277: Document Conventions And Icons
Document conventions and icons Conventions This section describes the conventions used in the documentation. Command conventions Convention Description Bold text represents commands and keywords that you enter literally as shown. Boldface Italic text represents arguments that you replace with actual values. Italic Square brackets enclose syntax choices (keywords or arguments) that are optional.
Page 278: 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 279: 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 280: 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 281 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 282: Index
Index Track+ERPS association, Numerics Track+MPLS L2VPN association, Track+policy-based routing association, ERPS network (1 major ring), Track+Smart Link association, ERPS network (1 major ring+1 subring), Track+static routing association, ERPS network (1 major ring+multiple Track+VPLS association, subrings), Track+VRRP association, ERPS network (1 subring+multiple rings), Track+VRRP group association, ERPS network (1 subring+multiple subrings), Track+VRRP VF association,...
Page 283 authenticating 1-way DM configuration, DLDP MD5 authentication, 2-way DM configuration, AIS configuration, DLDP MD5 mode, DLDP non-authentication mode, basic concepts, DLDP password authentication, basic configuration, configuration, 13, 17, 25 DLDP plaintext authentication, DLDP plaintext mode, continuity check (CC) configuration, DLDP simple authentication, display, VRRP MD5 authentication, EAIS configuration,...
Page 284 BFD control packet mode, IPv6 VRRP, BFD echo packet mode, IPv6 VRRP (on switch), IPv6 VRRP load balancing (on switch), BFD template, CFD, 13, 17, 25 IPv6 VRRP multiple groups (on switch), CFD 1-way DM, IPv6 VRRP packet attribute, IPv6 VRRP router preemptive mode, CFD 2-way DM, CFD AIS, IPv6 VRRP router priority,...
Page 285 static routing+Track+LLDP collaboration, Ethernet OAM errored frame event detection, static routing+Track+NQA collaboration, Ethernet OAM errored frame period event detection, Track, 225, 226, 238 Ethernet OAM errored frame seconds event Track BFD+VRRP backup master monitor, detection, Ethernet OAM errored symbol event detection, Track BFD+VRRP master uplink monitor, Ethernet OAM remote fault detection, VRRP,...
Page 286 Monitor Link group downlink interface how it works, switchover delay, maintain, Monitor Link group member interface, multiple neighbors detection, process placement configuration, 265, 266 neighbor states, RRPP domain activation, port shutdown mode, RRPP domain creation, port shutdown mode configuration (auto), Smart Link associated device, port shutdown mode configuration (hybrid), Smart Link device,...
Page 287 ERPS R-APS packet destination MAC ring MS mode and FS mode settings removal, address ring ID, Ethernet OAM remote loopback for port (in ring network, interface view), ring network (1 major ring), Ethernet OAM remote loopback for port (in ring network (1 major ring+1 subring), system view), ring network (1 major ring+multiple subrings), RRPP SNMP notification,...
Page 288 OAMPDUs, group port action configuration, IPv4 VRRP group disable, IPv6 VRRP group disable, protocols and standards, remote fault detection, Monitor Link downlink interface switchover delay, remote loopback, Monitor Link group creation, remote loopback configuration, Monitor Link group member interface, remote loopback configuration restrictions, RRPP ring, 50, 52 remote loopback for port (in interface view),...
Page 289 ERPS configuration (1 ring multi-instance load Ethernet OAM remote loopback request rejection, balancing), ERPS configuration (1 ring), IPv4 VRRP configuration, ERPS configuration (1 subring), IPv4 VRRP configuration (on switch), ERPS control VLAN configuration, IPv4 VRRP display, ERPS display, IPv4 VRRP group creation, ERPS flush packet transparent transmission IPv4 VRRP group disable, enable,...
Page 290 process placement configuration restrictions Track BFD+VRRP backup master monitor, (centralized IRF devices), Track BFD+VRRP master uplink monitor, process placement display, Track configuration, 225, 226, 238 process placement optimization, 265, 268 Track entry display, process placement policy, Track+application module association, process placement policy affinity (location Track+BFD association, type), Track+CFD association,...
Page 291 VRRP+Track+route management router tracking function configuration, collaboration, single group configuration (on switch), hybrid SNMP notification enable, DLDP port shutdown mode configuration, version specification, virtual forwarder (VF) tracking configuration, virtual IP address assignment, IPv6 ERPS R-APS packet destination MAC BFD protocols and standards, address ring ID enable, IPv6 VRRP inactive...
Page 292 RRPP link down mechanism, Smart Link, RRPPDU link-down type, Smart Link group configuration (multiple group load sharing), Smart Link backup, load-sharing Smart Link configuration, 141, 144, 148 VRRP application, Smart Link group configuration (multiple group load sharing), location Smart Link group configuration (single group), process placement affinity (location type), process placement affinity (location), Smart Link primary/secondary,...
Page 293 CFD TST configuration, DLDP plaintext authentication, major-fault RRPPDU type, DLDP port shutdown auto, DLDP port shutdown manual, manual DLDP port shutdown mode configuration, ERPS FS, master ERPS MS, ERPS non-revertive, RRPP node specification, RRPP node type, IPv4 VRRP router preemptive mode, VRRP master election, IPv6 VRRP router preemptive mode, VRRP master/backup application,...
Page 294 group member interface configuration, CFD TST configuration, group state switchover trigger threshold, DLDP authentication, DLDP authentication modes, Smart Link collaboration, monitoring DLDP basic concepts, Ethernet OAM link, DLDP multiple neighbors detection, DLDP port shutdown mode configuration (auto), Ethernet OAM link monitoring configuration, Monitor Link configuration, 163, 164, 166 DLDP port shutdown mode configuration (hybrid),...
Page 295 Ethernet OAM port action, process placement policy affinity (location type), Ethernet OAM remote loopback, process placement policy affinity (location), Ethernet OAM remote loopback for port (in interface view), process placement policy affinity (process), Ethernet OAM remote loopback for port (in process placement policy affinity (self), system view), process placement policy configuration,...
Page 296 Track+ERPS association, process placement configuration, 265, 266 Track+interface management association, RRPP assistant edge node, RRPP assistant-edge type, Track+LLDP association, RRPP edge node, Track+MPLS L2VPN association, RRPP edge type, Track+NQA association, RRPP master node, Track+policy-based routing association, RRPP master type, Track+route management association, RRPP node configuration, Track+Smart Link association, RRPP transit node,...
Page 297 plaintext troubleshooting RRPP master node, DLDP authentication, positive (attract) affinity, preempting DLDP authentication mode, point IPv4 VRRP router preemptive mode, CFD maintenance point, IPv6 VRRP router preemptive mode, Smart Link group role preemption mode, CFD MEP, CFD MEP configuration, Smart Link preemptive mode, CFD MIP, VRRP non-preemptive mode, policy...
Page 298 configuring CFD 1-way DM, configuring IPv4 VRRP single group (on switch), configuring CFD 2-way DM, configuring IPv6 VRRP, configuring CFD AIS, configuring IPv6 VRRP load balancing (on configuring CFD basic settings, switch), configuring CFD continuity check (CC), configuring IPv6 VRRP multiple groups (on configuring CFD EAIS, switch), configuring CFD Ethernet service instance,...
Page 299 configuring Smart Link group member port enabling DLDP, (group view), enabling ERPS (global), configuring Smart Link group member port enabling ERPS flush packet transparent (interface view), transmission, configuring Smart Link group protected VLAN, enabling ERPS for instance, enabling ERPS R-APS packet destination MAC configuring Smart Link group role preemption address ring ID, mode,...
Page 300 troubleshooting VRRP multiple masters recoverprobe timer (DLDP), appear in group, redundancy process placement process placement 1\N process redundancy, 1\N process redundancy, rejecting configuration, 265, 266 Ethernet OAM remote loopback request, configuration restrictions (centralized IRF remote devices), Ethernet OAM fault detection, display, Ethernet OAM remote loopback, 3, 8...
Page 301 DLDP configuration, 30, 34, 37 port types, Ethernet OAM port action, protected VLAN, protected VLAN configuration, Ethernet OAM remote loopback, Ethernet OAM remote loopback for port (in protocols and standards, interface view), ring configuration, Ethernet OAM remote loopback for port (in ring group, 50, 52 system view),...
Page 302 BFD session establishment and termination, Track+Smart Link association, SNMP setting BFD SNMP notification enable, DLDP advertisement packet send interval, RRPP SNMP notification, DLDP DelayDown timer, VRRP SNMP notification, DLDP port shutdown mode, specifying ERPS FS mode, IPv4 VRRP operating mode, ERPS MS mode, IPv4 VRRP version, ERPS non-revertive mode,...
Page 303 Monitor Link group state switchover trigger ERPS ring MS mode and FS mode settings threshold, removal, ERPS ring+subring association, RRPP configuration, 48, 56, 62 tangent rings RRPP domain, RRPP network, RRPP dual-homed rings, template RRPP dual-homed rings configuration, BFD template configuration, RRPP intersecting rings, terminating RRPP intersecting rings configuration,...
Page 304 Smart Link collaboration, 143, 146, 157 VRRP multiple masters appear in group, Smart Link+Track+CFD collaboration configuration, CFD functions, static routing association, CFD TST configuration, static routing+Track+BFD collaboration configuration, unconfirmed DLDP neighbor state, static routing+Track+LLDP collaboration configuration, unidirectional static routing+Track+NQA collaboration DLDP port state, configuration, updating...
Page 305 Smart Link transmit control VLAN, Smart Link+Track collaboration, VPLS Track+VPLS association, VRRP application, authentication methods, configuration, group router priority, load-sharing application, master election, master/backup application, operating mode, operating mode (load balancing), operating mode (standard), protocols and standards, router preemption, timers, Track BFD+VRRP backup master monitor, Track BFD+VRRP master uplink monitor, Track+VRRP association,...

This manual is also suitable for:

Flexnetwork 10500 series Flexnetwork 7500 series

HPE FlexNetwork 5510 HI Series Configuration Manual

Configuring Ethernet OAM

Configuring CFD

Configuring DLDP

Configuring RRPP

Configuring ERPS

Configuring Smart Link

Configuring Monitor Link

Configuring VRRP

Configuring BFD

Configuring Track

Configuring Process Placement

Document Conventions and Icons

Support and Other Resources

Index

Quick Links

High Availability

Configuration Guide

Troubleshooting

Need help?

Questions and answers

Related Manuals for HPE FlexNetwork 5510 HI Series

Summary of Contents for HPE FlexNetwork 5510 HI Series