Page 1 HPE FlexNetwork HSR6800 Routers High Availability Configuration Guide Part number: 5998-4497R Software version: HSR6800-CMW520-R3303P25 Document version: 6W105-20151231...
Page 2 © Copyright 2015 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 High availability overview ················································································ 1 Availability requirements ···································································································································· 1 Availability evaluation ········································································································································· 1 High availability technologies ····························································································································· 2 Fault detection technologies ······················································································································ 2 Protection switchover technologies ············································································································ 3 Configuring active and standby switchover ····················································· 5 Configuring active and standby switchover ········································································································ 5 Active and standby switchover configuration task list ························································································...
Page 4 Displaying and maintaining CFD ······················································································································ 26 CFD configuration example ····························································································································· 27 Configuring DLDP ························································································· 31 Overview ·························································································································································· 31 Configuring DLDP ············································································································································ 32 DLDP configuration task list ····························································································································· 38 Configuring the duplex mode and speed of an Ethernet interface ··································································· 38 Enabling DLDP ················································································································································...
Page 5 Configuring RRPP ························································································· 70 RRPP overview ················································································································································ 70 Basic RRPP concepts ······························································································································ 70 RRPPDUs ················································································································································ 72 RRPP timers ············································································································································ 73 How RRPP works ····································································································································· 73 Typical RRPP networking ························································································································ 74 Protocols and standards ·························································································································· 77 RRPP configuration task list ···························································································································· 78 Creating an RRPP domain ·······························································································································...
Page 6 Configuring VF tracking ·························································································································· 148 Enabling ARP entry backup ··················································································································· 149 Configuring VRRP packet attributes ······································································································ 150 Enabling the trap function for VRRP ······································································································ 151 Displaying and maintaining VRRP for IPv4 ···························································································· 151 Configuring VRRP for IPv6 ···························································································································· 151 VRRP for IPv6 configuration task list ····································································································· 151 Specifying the type of MAC addresses mapped to virtual IPv6 addresses ············································...
Page 7 Document conventions and icons ······························································· 232 Conventions ··················································································································································· 232 Network topology icons ·································································································································· 233 Support and other resources ······································································ 234 Accessing Hewlett Packard Enterprise Support ···························································································· 234 Accessing updates ········································································································································· 234 Websites ················································································································································ 235 Customer self repair ······························································································································· 235 Remote support ······································································································································ 235 Documentation feedback ·······················································································································...
Page 8: High Availability Overview
High availability overview Because communication interruptions can seriously affect widely-deployed value-added services such as IPTV and video conference, basic network infrastructures must be able to provide high availability. The following are the effective ways to improve availability: • Increasing fault tolerance. •...
Page 9: High Availability Technologies
High availability technologies Increasing MTBF or decreasing MTTR can enhance the availability of a network. The high availability technologies described in this section meet the level 2 and level 3 high availability requirements in the aspect of decreasing MTTR. High availability technologies can be classified as fault detection technologies or protection switchover technologies.
Page 10: Protection Switchover Technologies
Protection switchover technologies Protection switchover technologies aim at recovering network faults. They back up hardware, link, routing, and service information for switchover in case of network faults to ensure continuity of network services. A single availability technology cannot solve all problems. You should use a combination of availability technologies, chosen on the basis of detailed analysis of network environments and user requirements, to enhance network availability.
Page 11 Technology Introduction Reference NSR ensures non-stop data transmission during an active/standby switchover by backing up IP/MPLS forwarding information from the active MPU to the standby MPU. Upon an Layer 3—IP Routing active/standby switchover, NSR can complete link state recovery Configuration Guide and route re-generation without requiring the cooperation of other devices.
Page 12: Configuring Active And Standby Switchover
Configuring active and standby switchover If a device has two MPUs, the MPU that forwards and processes packets is called the active MPU, and the MPU that is in the standby state is called the standby MPU. The system uses the MPU with a smaller slot number as the active MPU, and the other MPU as the standby MPU.
Page 13: Restarting The Standby Mpu
Restarting the standby MPU After the standby MPU has restarted, the active MPU will perform initial synchronization on the standby MPU. During this process, the system does not respond to your input. After the initial synchronization is completed, you can execute all the configuration commands on the active MPU and the active MPU and standby MPU will keep a real-time synchronization process.
Page 14: Configuring Ethernet Oam
Configuring Ethernet OAM Ethernet OAM is supported only when the SAP module is operating in bridge mode. 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.
Page 15: How Ethernet Oam Works
Field Description Type of the encapsulated protocol in the Ethernet OAMPDU. Type The value is 0x8809. The specific protocol being encapsulated in the Ethernet OAMPDU. Subtype The value is 0x03. Flags Status information of an Ethernet OAM entity. Code Type of the Ethernet OAMPDU. NOTE: Throughout this document, an Ethernet OAM-enabled port is called an "Ethernet OAM entity"...
Page 16 Passive Ethernet OAM Item Active Ethernet OAM mode mode Responding to OAM Discovery Available Available Transmitting Information Available Available OAMPDUs Transmitting Event Notification Available Available OAMPDUs Transmitting Information Available Available OAMPDUs without any TLV Transmitting Loopback Control Available Unavailable OAMPDUs Responding to Loopback Control Available when both sides are Available...
Page 17: Standards And Protocols
(any critical link event type shown in Table 8) to its peer. You can use the log information to track ongoing link status and troubleshoot problems promptly. Table 8 Critical link events OAMPDU transmission Type Description frequencies Link Fault Peer link signal is lost. Once per second.
Page 18: Configuring Basic Ethernet Oam Functions
Task Remarks Rejecting the Ethernet OAM remote loopback request from a Optional remote port Configuring basic Ethernet OAM functions To set up an Ethernet OAM connection between two Ethernet OAM entities, you must set at least one entity to operate in active mode. Only in active mode can an Ethernet OAM entity initiate OAM connection.
Page 19: Configuring Link Monitoring
Configuring link monitoring After Ethernet OAM connections are established, the link monitoring periods and thresholds configured in this section automatically take effect on all Ethernet ports. Configuring errored symbol event detection An errored symbol event occurs when the number of detected symbol errors during a specific detection interval exceeds the predefined threshold.
Page 20: Configuring Errored Frame Seconds Event Detection
Configuring errored frame seconds event detection An errored frame seconds event occurs when the number of error frame seconds detected on a port during a detection interval exceeds the error threshold. IMPORTANT: Make sure the errored frame seconds triggering threshold is less than the errored frame seconds detection interval.
Page 21: Enabling Ethernet Oam Remote Loopback In User View
• Ethernet OAM remote loopback is only applicable to individual links. It is not applicable to link aggregation member ports. In addition, do not assign ports where Ethernet OAM remote loopback is being performed to link aggregation groups. For more information about link aggregation groups, see Layer 2—LAN Switching Configuration Guide.
Page 22: Displaying And Maintaining Ethernet Oam Configuration
Step Command Remarks interface interface-type Enter Ethernet port view. interface-number Reject the Ethernet OAM By default, a port does not reject the oam loopback remote loopback request Ethernet OAM remote loopback request reject-request from a remote port. from a remote port. Displaying and maintaining Ethernet OAM configuration Task...
Page 23: Configuration Procedure
Configuration procedure Configure Router A: # Configure GigabitEthernet 3/0/1 to operate in passive Ethernet OAM mode and enable Ethernet OAM for it. <RouterA> system-view [RouterA] interface gigabitethernet 3/0/1 [RouterA-GigabitEthernet3/0/1] oam mode passive [RouterA-GigabitEthernet3/0/1] oam enable [RouterA-GigabitEthernet3/0/1] quit # Set the errored frame detection interval to 20 seconds and set the errored frame event triggering threshold to 10.
Page 24 Port : GigabitEthernet3/0/1 Link Status : Up Event statistic : ------------------------------------------------------------------------- Link Fault Dying Gasp Critical Event The output shows that no critical link event occurred on the link between Router A and Router You can use the display oam link-event command to display the statistics of Ethernet OAM link error events.
Page 25: Configuring Cfd
Configuring CFD CFD is supported only when the SAP module is operating in bridge mode. Overview Connectivity Fault Detection (CFD) is an end-to-end per-VLAN link layer OAM mechanism used for link connectivity detection, fault verification, and fault location. It conforms to IEEE 802.1ag CFM. Basic CFD concepts Maintenance domain A maintenance domain (MD) defines the network or part of the network where CFD plays its role.
Page 26 Maintenance point An MP is configured on a port and belongs to an MA. MPs include two 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 that a MEP belongs to defines the VLAN of packets sent by the MEP;...
Page 27: Cfd Functions
Figure 5 CFD grading example Router A Router B Router C Router D Router E Router F Port 1 Port 2 MD level 5 MD level 3 MD Level 2 MD Level 2 MD level 0 MD level 0 MD level 0 Inward-facing MEP and MD level Port Outward-facing MEP and MD level...
Page 28: Protocols And Standards
Linktrace is similar to traceroute. It identifies the path between the source MEP and the target MEP. This function is implemented in the following way—the source MEP sends the linktrace messages (LTMs) to the target MEP. After receiving the messages, the target MEP and the MIPs that the LTM frames pass send back linktrace reply messages (LTRs) to the source MEP.
Page 29: Configuring Basic Cfd Settings
Configuring basic CFD settings Enabling CFD Step Command Remarks Enter system view. system-view Enable CFD. cfd enable CFD is disabled by default. Configuring the CFD protocol version Three CFD protocol versions are available: IEEE 802.1ag draft5.2 version, IEEE 802.1ag draft5.2 interim version, and IEEE 802.1ag standard version.
Page 30: Configuring Meps
Step Command Remarks cfd md md-name level Create an MD. Not created by default. level-value cfd ma ma-name md md-name Create an MA. Not created by default. vlan vlan-id cfd service-instance instance-id Create a service instance. Not created by default. md md-name ma ma-name Configuring a service instance with no MD name When you create a service instance with no MD name, the system automatically creates the MD and...
Page 31: Configuring Mip Generation Rules
Configuring MIP generation rules As functional entities in a service instance, MIPs respond to various CFD frames, such as LTM frames, LBM frames, 1DM frames, DMM frames, and TST frames. You can choose appropriate MIP generation rules based on your network design. To configure the rules for generating MIPs: Step Command...
Page 32: Configuring Lb On Meps
NOTE: • The value range for the interval field value varies with device models. • The following describes CCM messages with the interval field value 1 to 3 as high-speed CCM messages, and those with the interval field 4 to 7 as low-speed CCM messages. Follow these guidelines when you configure CC on a MEP: •...
Page 33: Displaying And Maintaining Cfd
Step Command Remarks cfd linktrace service-instance Find the path between a instance-id mep mep-id { target-mep source MEP and a target target-mep-id | target-mac Available in any view. MEP. mac-address } [ ttl ttl-value ] [ hw-only ] Enter system view. system-view Enable LT messages cfd linktrace auto-detection [ size...
Page 34: Cfd Configuration Example
CFD configuration example Network requirements As shown in Figure • The network comprises five devices and is divided into two MDs: MD_A (level 5) and MD_B (level 3). All ports belong to VLAN 100, and the MAs in the two MDs all serve VLAN 100. Assume that the MAC addresses of Router A through Router E are 0010-FC00-6511, 0010-FC00-6512, 0010-FC00-6513, 0010-FC00-6514, and 0010-FC00-6515, respectively.
Page 35 # Create MD_A (level 5) on Router A, create MA_A, which serves VLAN 100, in MD_A, and create service instance 1 for MD_A and MA_A. [RouterA] cfd md MD_A level 5 [RouterA] cfd ma MA_A md MD_A vlan 100 [RouterA] cfd service-instance 1 md MD_A ma MA_A Configure Router E as you configure Router A.
Page 36 [RouterD-GigabitEthernet3/0/3] cfd mep service-instance 1 mep 4002 enable [RouterD-GigabitEthernet3/0/3] quit # On Router E, configure a MEP list in service instance 1. Create and enable inward-facing MEP 5001 in service instance 1 on GigabitEthernet 3/0/4. [RouterE] cfd meplist 1001 4002 5001 service-instance 1 [RouterE] interface gigabitethernet 3/0/4 [RouterE-GigabitEthernet3/0/4] cfd mep 5001 service-instance 1 inbound [RouterE-GigabitEthernet3/0/4] cfd mep service-instance 1 mep 5001 enable...
Page 37 Reply from 0010-FC00-6515: sequence number=1001-43406 time=5ms Reply from 0010-FC00-6515: sequence number=1001-43407 time=5ms Reply from 0010-FC00-6515: sequence number=1001-43408 time=5ms Send:5 Received:5 Lost:0 After the whole network status is obtained with the CC function, use the LT function to identify the paths between source and target MEPs, and to locate faults. Verify the LT function: # Identify the path between MEP 1001 and MEP 5001 in service instance 1 on Router A.
Page 38: Configuring Dldp
Configuring DLDP DLDP is supported only when the SAP module is operating in bridge mode. Overview Unidirectional links occur when only one end of a bidirectional link can receive packets. Unidirectional links cause problems such as loops in an STP-enabled network. For example, the link between two switches, Switch A and Switch B, is a bidirectional link when they are connected through a fiber pair, with one fiber used for sending packets from A to B and the other for sending packets from B to A.
Page 39: Configuring Dldp
The auto-negotiation mechanism and DLDP work together to make sure that physical/logical unidirectional links are detected and shut down, and to prevent failure of other protocols such as STP. If both ends of a link are operating correctly at the physical layer, DLDP detects whether the link is correctly connected at the link layer and whether the two ends can exchange packets correctly.
Page 40 DLDP timer Description This timer is set to 10 seconds. It is triggered when a device transits to the Probe state or when an enhanced detect is launched. When the Echo timer expires and no Echo packet has been received from a neighbor device, the state of the link is set to unidirectional and the device transits to the Disable state.
Page 41 Table 12 DLDP mode and neighbor entry aging Detecting a neighbor after the Removing the neighbor Triggering the DLDP mode corresponding entry immediately after Enhanced timer after an neighbor entry ages the Entry timer expires Entry timer expires Normal DLDP mode Enhanced DLDP mode...
Page 42 The sending side sets the Authentication field and the Authentication type field of DLDP packets to 0. The receiving side checks the values of the two fields of received DLDP packets and drops packets where the two fields conflict with the corresponding local configuration. •...
Page 43 Packet type Processing procedure If a matching neighbor entry already exists, resets the Entry timer. Checks whether the If yes, performs no processing. Flush packet local DLDP port If no, removes the matching neighbor entry (if any). state is Disable. If no matching neighbor entry exists, creates the neighbor Retrieves the entry, transits to the Probe state, and returns Echo packets.
Page 44 Table 16 Action to take when no echo packet is received from a neighbor No echo packet received from the Action neighbor In normal mode, no echo packet is received DLDP sets the state of the neighbor to one way, and when the Echo timer expires.
Page 45: Dldp Configuration Task List
DLDP configuration task list For DLDP to work correctly, enable DLDP on both sides and make sure these settings are consistent: the interval to send Advertisement packets, DLDP authentication mode, and password. DLDP does not process any Link Aggregation Control Protocol (LACP) events. The links in an aggregation are treated as individual links in DLDP.
Page 46: Enabling Dldp
Enabling DLDP To correctly configure DLDP on the device, first enable DLDP globally, and then enable it on each port. DLDP takes effect only on Ethernet interfaces (optical or copper). DLDP can detect unidirectional links only after all physical links are connected. Therefore, before enabling DLDP, make sure that optical fibers or copper twisted pairs are connected.
Page 47: Setting The Delaydown Timer
To enable DLDP to operate correctly, make sure the two sides of the link use the same Advertisement packet sending interval. To set the Advertisement packet sending interval: Step Command Remarks Enter system view. system-view Set the interval to send Optional.
Page 48: Configuring Dldp Authentication
Step Command Remarks Enter system view. system-view Optional. Set port shutdown dldp unidirectional-shutdown { auto mode. | manual } auto by default. Configuring DLDP authentication You can guard your network against attacks and malicious probes by configuring an appropriate DLDP authentication mode, which can be simple authentication or MD5 authentication. If your network is safe, you can choose not to authenticate.
Page 49: Displaying And Maintaining Dldp
Resetting DLDP state in port view/port group view Resetting DLDP state in port view or port group view applies to the current port or all ports in the port group. To reset DLDP state in port view/port group view: Step Command Remarks Enter system view.
Page 50 Figure 9 Network diagram Correct fiber connection Cross-connected fibers Router A Router A GE3/0/1 GE3/0/2 GE3/0/1 GE3/0/2 GE3/0/1 GE3/0/2 GE3/0/1 GE3/0/2 Router B Router B Ethernet Tx end Rx end Fiber link fiber port Configuration procedure Configure Router A: # Enable DLDP globally. <RouterA>...
Page 51 <RouterB> system-view [RouterB] dldp enable # Configure GigabitEthernet 3/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it. [RouterB] interface gigabitethernet 3/0/1 [RouterB-GigabitEthernet3/0/1] duplex full [RouterB-GigabitEthernet3/0/1] speed 1000 [RouterB-GigabitEthernet3/0/1] dldp enable [RouterB-GigabitEthernet3/0/1] quit # Configure GigabitEthernet 3/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.
Page 52 Neighbor state : two way Neighbor aged time : 12 The output indicates that both GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 are in Advertisement state, which means both links are bidirectional. # Enable system information monitoring on Router A, and enable the display of log and trap information.
Page 53: Manually Shutting Down Unidirectional Links
Manually shutting down unidirectional links Network requirements As shown in Figure 10, Router A and Router B are connected with two fiber pairs. Configure DLDP to send information when a unidirectional link is detected, which reminds the network administrator to manually shut down the faulty port. Figure 10 Network diagram Correct fiber connection Cross-connected fibers...
Page 54 # Set the DLDP mode to enhanced. [RouterA] dldp work-mode enhance # Set the port shutdown mode to manual. [RouterA] dldp unidirectional-shutdown manual Configure Router B: # Enable DLDP globally. <RouterB> system-view [RouterB] dldp enable # Configure GigabitEthernet 3/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.
Page 55 Interface GigabitEthernet3/0/2 DLDP port state : advertisement DLDP link state : up The neighbor number of the port is 1. Neighbor mac address : 0023-8956-3600 Neighbor port index : 60 Neighbor state : two way Neighbor aged time : 12 The output indicates that both GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 are in Advertisement state, which means both links are bidirectional.
Page 56: Troubleshooting Dldp
Assume that in this example, the unidirectional links are caused by cross-connected fibers. Correct the fiber connections, and then bring up the ports shut down earlier. # On Router A, bring up GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2: [RouterA-GigabitEthernet3/0/2] undo shutdown [RouterA-GigabitEthernet3/0/2] %Jan 18 18:22:11:698 2010 RouterA IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/2 link status is UP.
Page 57: Configuring Rpr
Configuring RPR RPR overview Resilient Packet Ring (RPR) is a new MAC layer protocol designed for transferring mass data services over MANs. It can operate on synchronous optical network/synchronous digital hierarchy (SONET/SDH), Dense Wavelength Division Multiplexing (DWDM) and Ethernet to provide flexible and efficient networking schemes for broadband IP MANs carriers.
Page 58: Data Operations On Rpr
Data operations on RPR Stations on an RPR handle data frames by performing the following four types of operations: • Insert, to place a frame on a ringlet. • Transit, to pass a frame to the next station. • Copy, to deliver an inbound frame from the ring to the upper layer. Copying a frame does not remove the frame from the ring.
Page 59: Topology Discovery
Broadcast, multicast, and unknown unicast transmission Figure 13 Broadcast, multicast, and unknown unicast transmission on an RPR ring Figure 13 shows how a broadcast, multicast, or unknown unicast frame is transmitted on an RPR ringlet: The source station inserts the frame into the data stream on Ringlet 0 or Ringlet 1. Transit and destination stations copy and transit the frame if the TTL of the frame has not expired.
Page 60: Fault Response Methods
• TC frames convey topology checksum information. They are sent between adjacent stations to check whether the topology databases on them are synchronized, identifying stability of the RPR ring topology. All these control frames are sent at regular intervals, which are user configurable. For TP and TC frames, fast sending interval and slow sending interval are used.
Page 61 Figure 14 Schematic diagram before and after protection switchover As shown in Figure 14, traffic travels from station D to station B along Ringlet 0. The transmission path is station D—station E—station A—station B. After the span between station A and station E fails, a protection switchover occurs.
Page 62: Centralized Rpr And Distributed Rpr
requests are sent manually, whereas SF, SD, and WTR requests are sent automatically. If multiple protection requests appear at the same time, the higher priority protection request is processed preferentially. For example: • The MS request sent by a station will not be processed if a higher priority protection request is present on the RPR ring.
Page 63: Protocols And Standards
RPR master/subordinate port The first RPR physical port bound to the RPR logical interface is the master port, and the second RPR physical port bound to the RPR logical interface is the subordinate port. All calculation concerning the operation of RPR is done on the master port, and the calculation result is synchronized to the subordinate port for consistency.
Page 64: Configuring Basic Rpr Functions
Configuring basic RPR functions Configuring an RPR physical port To configure an RPRPOS interface: Step Command Remarks Enter system view. system-view Enter RPR physical port interface rprpos interface-number view. Optional. Configure the description By default, the description of an description text for the interface.
Page 65: Binding An Rpr Logical Interface With Rpr Physical Ports
Step Command Remarks Optional. By default, the card where the In standalone mode: receiving member port resides service slot slot-number processes the traffic. Specify the card for forwarding In IRF mode: Do not use the service command traffic of the interface. service chassis to configure the MPU to forward chassis-number slot...
Page 66: Configuring The Rpr Station Name
To enable RPR mate port smart connection: Step Command Remarks Enter system view. system-view Enter RPR logical interface rpr interface view. interface-number Enable RPR mate port rpr mate smart-connect Disabled by default. smart connection. Configuring the RPR station name Step Command Remarks Enter system view.
Page 67: Manually Sending A Protection Request
Step Command Remarks Enter RPR logical interface rpr interface view. interface-number Configure the rpr reversion-mode protection reversion Revertive mode applies by default. { revertive | non-revertive } mode. Manually sending a protection request You can send FS or MS protection requests to trigger protection switchover or send idle protection requests to clear manually sent protection requests on the RPR station.
Page 68: Configuring Default Ringlet Selection
Step Command Remarks Enter system view. system-view Enter RPR logical interface interface rpr interface-number view. Add a static ringlet selection rpr static-rs mac-address No static ringlet selection entry is entry. { ringlet0 | ringlet1 } created by default. NOTE: Static ringlet selection entries take effect only when the RPR ring is closed. Configuring default ringlet selection Step Command...
Page 69: Configuring Station Weight
Step Command Remarks Enter RPR logical interface rpr interface-number interface view. Configure reserved By default, no bandwidth is reserved for rpr rate-limiter { high | low | bandwidth or rate limit subclass A0. The rate limit is 2‰ for medium | reserved } { ringlet0 | for a class on a certain subclass A1, 0‰...
Page 70: Configuring The Hold Off Timer
Configuring the hold off timer The hold off timer defines the delay for the physical layer to report a protection request after detecting a link failure. To configure the hold off timer: Step Command Remarks Enter system view. system-view Enter RPR logical interface interface rpr interface-number view.
Page 71: Configuring The Tp Timers
To configure the TC timers: Step Command Remarks Enter system view. system-view Enter RPR logical interface interface rpr interface-number view. Set the TC fast timer. rpr timer tc-fast tc-fast-value 10 milliseconds by default. Set the TC slow timer. rpr timer tc-slow tc-slow-value 100 milliseconds by default.
Page 72: Displaying And Maintaining Rpr
specific ringlet. Otherwise, the connectivity between the current station and the destination station is considered as having failed. To test the connectivity to a specific RPR station: Step Command Remarks Enter system view. system-view Enter RPR logical interface interface rpr interface-number view.
Page 73: Rpr Configuration Examples
Task Command Remarks display rpr statistics { dmac | smac } [ mac-address ] [ rpr Display statistics about traffic on interface-number ] [ | { begin | Available in any view. the RPR ring. exclude | include } regular-expression ] display rpr timers [ rpr Display the settings of all interface-number ] [ | { begin |...
Page 74 Configuration procedure Create an RPR logical interface and bind two RPR physical ports to the RPR logical interface: # On Station A, create RPR logical interface RPR1, and bind RPR physical ports RPRPOS 1/1 (the west port) and RPRPOS 1/2 (the east port) to RPR 1. <StationA>...
Page 75: Rpr Protection Mode/Static Ringlet Selection Configuration Example
000f-e257-0003 Idle Idle 0 0.0.0.0 000f-e257-0004 Idle Idle 0 0.0.0.0 000f-e257-0005 Idle Idle 0 0.0.0.0 The topology information shows that the RPR ring is closed. RPR protection mode/static ringlet selection configuration example Network requirements As shown in Figure 16, Stations A through E form an RPR ring and operate in steering protection mode by default.
Page 76 Total stations on ring: 5 Jumbo preference: regular Ring topology type: closed ring # Display the static ring selection table information on Station A. [StationA] display rpr rs-table static Static ringlet selection table on interface: RPR1 MAC-Address Ringlet-ID Status ----------------------------------- 000f-e257-0002 Ringlet1 Valid...
Page 77: Configuring Rrpp
Configuring RRPP The router supports RRPP only when the SAP module is operating in bridge mode. RRPP overview The Rapid Ring Protection Protocol (RRPP) is a link layer protocol designed for Ethernet rings. RRPP can prevent broadcast storms caused by data loops when an Ethernet ring is healthy, and rapidly restore the communication paths between the nodes in the event that a link is disconnected on the ring.
Page 78 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 79: Rrppdus
In terms of functionality, the primary port and the secondary port of a master node have the following differences: The primary port and the secondary port are designed to play the role of sending and receiving loop-detect packets, respectively. When an RRPP ring is in Health state, the secondary port of the master node will logically deny data VLANs and permit only the packets from the control VLANs.
Page 80: Rrpp Timers
Type Description The edge node initiates Edge-Hello packets to examine the SRPTs between the Edge-Hello edge node and the assistant-edge node. The edge node initiates Fast-Edge-Hello packets to fast examine the SRPTs Fast-Edge-Hello between it and the assistant-edge node. The assistant-edge node initiates Major-Fault packets to notify the edge node of Major-Fault SRPT failure when an SRPT between edge node and assistant-edge node is torn down.
Page 81: Typical Rrpp Networking
again. A temporary loop might arise in the data VLAN during this period. As a result, broadcast storm occurs. To prevent temporary loops, non-master nodes block them immediately (and permit only the packets from the control VLAN to pass through) when they find their ports accessing the ring are brought up again.
Page 82 Figure 18 Schematic diagram for a single-ring network Tangent rings As shown in Figure 19, two or more rings exist in the network topology and only one common node exists between rings. You must define an RRPP domain for each ring. Figure 19 Schematic diagram for a tangent-ring network Intersecting rings As shown in...
Page 83 Figure 20 Schematic diagram for an intersecting-ring network Dual homed rings As shown in Figure 21, two or more rings exist in the network topology and two similar common nodes exist between rings. You only need to define an RRPP domain, and configure one ring as the primary ring and the other rings as subrings.
Page 84: Protocols And Standards
Figure 22 Schematic diagram for a single-ring load balancing network Device A Device B Ring 1 Domain 2 Domain 1 Device D Device C Intersecting-ring load balancing In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains.
Page 85: Rrpp Configuration Task List
RRPP configuration task list You can create RRPP domains based on service planning, specify control VLANs and data VLANs for each RRPP domain, and then determine the ring roles and node roles based on the traffic paths in each RRPP domain. RRPP does not have an auto election mechanism, so you must configure each node in the ring network correctly for RRPP to monitor and protect the ring network.
Page 86: Configuring Control Vlans
Configuring control VLANs Before configuring RRPP rings in an RRPP domain, configure the same control VLANs for all nodes in the RRPP domain first. Perform this configuration on all nodes in the RRPP domain to be configured. Follow these guidelines when you configure control VLANs: •...
Page 87: Configuring Rrpp Rings
Step Command Remarks Not required if the device is operating in PVST mode. Enter MST region view. stp region-configuration For more information about the command, see Layer 2—LAN Switching Command Reference. Optional. Use either method. • Method 1: All VLANs in an MST region are instance instance-id vlan mapped to MSTI 0 (the CIST) by Configure the...
Page 88: Configuring Rrpp Nodes
• RRPP ports always allow packets from the control VLANs to pass through. • For more information about the port link-type trunk, port trunk permit vlan, and undo stp enable commands, see Layer 2—LAN Switching Command Reference. • Do not enable OAM remote loopback function on an RRPP port. Otherwise, it might cause temporary broadcast storms.
Page 89: Activating An Rrpp Domain
Step Command Specify the current device as a transit ring ring-id node-mode transit [ primary-port node of the ring, and specify the interface-type interface-number ] [ secondary-port primary port and the secondary port. interface-type interface-number ] level level-value Specifying an edge node When configuring an edge node, you must first configure the primary ring before configuring the subrings.
Page 90: Configuring Rrpp Timers
• Disable the primary ring of an RRPP domain after disabling all subrings of the RRPP domain. To activate an RRPP domain: Step Command Remarks Enter system view. system-view Enable RRPP. rrpp enable Disabled by default. Enter RRPP domain view. rrpp domain domain-id Enable the specified RRPP ring ring-id enable...
Page 91: Displaying And Maintaining Rrpp
To configure an RRPP ring group: Step Command Enter system view. system-view Create an RRPP ring group and enter RRPP rrpp ring-group ring-group-id ring group view. Assign the specified subrings to the RRPP ring domain domain-id ring ring-id-list group. Displaying and maintaining RRPP Task Command Remarks...
Page 92 Figure 24 Network diagram Configuration procedure Configure Router A: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <RouterA> system-view [RouterA] vlan 1 to 30 [RouterA] stp region-configuration [RouterA-mst-region] instance 1 vlan 1 to 30 [RouterA-mst-region] active region-configuration [RouterA-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1 and...
Page 93 [RouterA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0 [RouterA-rrpp-domain1] ring 1 enable [RouterA-rrpp-domain1] quit # Enable RRPP. [RouterA] rrpp enable Configure Router B: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration.
Page 94: Intersecting Ring Configuration Example
Use the display command to view RRPP configuration and operational information on each device. Intersecting ring configuration example Networking requirements As shown in Figure • Router A, Router B, Router C, Router D, and Router E form RRPP domain 1, VLAN 4092 is the primary control VLAN of RRPP domain 1, and RRPP domain 1 protects VLANs 1 through 30.
Page 95 # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2. Disable the spanning tree feature, configure the two ports as trunk ports, and assign them to VLANs 1 through 30. [RouterA] interface gigabitethernet 3/0/1 [RouterA-GigabitEthernet3/0/1] link-delay 0 [RouterA-GigabitEthernet3/0/1] undo stp enable [RouterA-GigabitEthernet3/0/1] port link-type trunk...
Page 96 [RouterB-GigabitEthernet3/0/2] port link-type trunk [RouterB-GigabitEthernet3/0/2] port trunk permit vlan 1 to 30 [RouterB-GigabitEthernet3/0/2] quit [RouterB] interface gigabitethernet 3/0/3 [RouterB-GigabitEthernet3/0/3] link-delay 0 [RouterB-GigabitEthernet3/0/3] undo stp enable [RouterB-GigabitEthernet3/0/3] port link-type trunk [RouterB-GigabitEthernet3/0/3] port trunk permit vlan 1 to 30 [RouterB-GigabitEthernet3/0/3] quit # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.
Page 97 [RouterC-GigabitEthernet3/0/2] quit [RouterC] interface gigabitethernet 3/0/3 [RouterC-GigabitEthernet3/0/3] link-delay 0 [RouterC-GigabitEthernet3/0/3] undo stp enable [RouterC-GigabitEthernet3/0/3] port link-type trunk [RouterC-GigabitEthernet3/0/3] port trunk permit vlan 1 to 30 [RouterC-GigabitEthernet3/0/3] quit # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.
Page 98 # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [RouterD] rrpp domain 1 [RouterD-rrpp-domain1] control-vlan 4092 [RouterD-rrpp-domain1] protected-vlan reference-instance 1 # Configure Router D as the transit node of primary ring 1, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable ring 1.
Page 99: Dual Homed Rings Configuration Example
[RouterE] rrpp enable Verify the configuration: Use the display command to view RRPP configuration and operational information on each device. Dual homed rings configuration example Networking requirements As shown in Figure • Router A through Router H form RRPP domain 1. Specify the primary control VLAN of RRPP domain 1 as VLAN 4092, and specify that RRPP domain 1 protects VLANs 1 through 30.
Page 100 Figure 26 Network diagram Configuration procedure Configure Router A: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <RouterA> system-view [RouterA] vlan 1 to 30 [RouterA] stp region-configuration [RouterA-mst-region] instance 1 vlan 1 to 30 [RouterA-mst-region] active region-configuration [RouterA-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1...
Page 101 [RouterA-GigabitEthernet3/0/3] port trunk permit vlan 1 to 30 [RouterA-GigabitEthernet3/0/3] quit [RouterA] interface gigabitethernet 3/0/4 [RouterA-GigabitEthernet3/0/4] link-delay 0 [RouterA-GigabitEthernet3/0/4] undo stp enable [RouterA-GigabitEthernet3/0/4] port link-type trunk [RouterA-GigabitEthernet3/0/4] port trunk permit vlan 1 to 30 [RouterA-GigabitEthernet3/0/4] quit # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.
Page 102 [RouterB-GigabitEthernet3/0/2] undo stp enable [RouterB-GigabitEthernet3/0/2] port link-type trunk [RouterB-GigabitEthernet3/0/2] port trunk permit vlan 1 to 30 [RouterB-GigabitEthernet3/0/2] quit [RouterB] interface gigabitethernet 3/0/3 [RouterB-GigabitEthernet3/0/3] link-delay 0 [RouterB-GigabitEthernet3/0/3] undo stp enable [RouterB-GigabitEthernet3/0/3] port link-type trunk [RouterB-GigabitEthernet3/0/3] port trunk permit vlan 1 to 30 [RouterB-GigabitEthernet3/0/3] quit [RouterB] interface gigabitethernet 3/0/4 [RouterB-GigabitEthernet3/0/4] link-delay 0...
Page 103 # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1 through GigabitEthernet 3/0/4. Disable the spanning tree feature, configure the four ports as trunk ports, and assign them to VLANs 1 through 30. [RouterC] interface gigabitethernet 3/0/1 [RouterC-GigabitEthernet3/0/1] link-delay 0 [RouterC-GigabitEthernet3/0/1] undo stp enable [RouterC-GigabitEthernet3/0/1] port link-type trunk...
Page 104 [RouterC] rrpp enable Configure Router D: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <RouterD> system-view [RouterD] vlan 1 to 30 [RouterD] stp region-configuration [RouterD-mst-region] instance 1 vlan 1 to 30 [RouterD-mst-region] active region-configuration [RouterD-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1...
Page 105 [RouterD-rrpp-domain1] ring 4 node-mode edge edge-port gigabitethernet 3/0/3 [RouterD-rrpp-domain1] ring 4 enable # Configure Router D as the edge node of subring 5, with GigabitEthernet 3/0/4 as the edge port, and enable subring 5. [RouterD-rrpp-domain1] ring 5 node-mode edge edge-port gigabitethernet 3/0/4 [RouterD-rrpp-domain1] ring 5 enable [RouterD-rrpp-domain1] quit # Enable RRPP.
Page 106 <RouterF> system-view [RouterF] vlan 1 to 30 [RouterF] stp region-configuration [RouterF-mst-region] instance 1 vlan 1 to 30 [RouterF-mst-region] active region-configuration [RouterF-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2. Disable the spanning tree feature, configure the two ports as trunk ports, and assign them to VLANs 1 through 30.
Page 107 [RouterG-GigabitEthernet3/0/1] port link-type trunk [RouterG-GigabitEthernet3/0/1] port trunk permit vlan 1 to 30 [RouterG-GigabitEthernet3/0/1] quit [RouterG] interface gigabitethernet 3/0/2 [RouterG-GigabitEthernet3/0/2] link-delay 0 [RouterG-GigabitEthernet3/0/2] undo stp enable [RouterG-GigabitEthernet3/0/2] port link-type trunk [RouterG-GigabitEthernet3/0/2] port trunk permit vlan 1 to 30 [RouterG-GigabitEthernet3/0/2] quit # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.
Page 108: Load Balanced Intersecting-Ring Configuration Example
[RouterH-rrpp-domain1] control-vlan 4092 [RouterH-rrpp-domain1] protected-vlan reference-instance 1 # Configure Router H as the master node of subring 5, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable subring 5. [RouterH-rrpp-domain1] ring 5 node-mode master primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 1 [RouterH-rrpp-domain1] ring 5 enable [RouterH-rrpp-domain1] quit...
Page 109 Figure 27 Network diagram Configuration procedure Configure Router A: # Create VLANs 11 and 12, map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2, and activate MST region configuration. <RouterA> system-view [RouterA] vlan 11 to 12 [RouterA] stp region-configuration [RouterA-mst-region] instance 1 vlan 11 [RouterA-mst-region] instance 2 vlan 12 [RouterA-mst-region] active region-configuration...
Page 110 [RouterA-GigabitEthernet3/0/2] port trunk pvid vlan 11 [RouterA-GigabitEthernet3/0/2] quit # Create RRPP domain 1, configure VLAN 100 as the primary control VLAN of RRPP domain 1, and configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1. [RouterA] rrpp domain 1 [RouterA-rrpp-domain1] control-vlan 100 [RouterA-rrpp-domain1] protected-vlan reference-instance 1...
Page 111 [RouterB-GigabitEthernet3/0/2] link-delay 0 [RouterB-GigabitEthernet3/0/2] undo stp enable [RouterB-GigabitEthernet3/0/2] port link-type trunk [RouterB-GigabitEthernet3/0/2] undo port trunk permit vlan 1 [RouterB-GigabitEthernet3/0/2] port trunk permit vlan 11 12 [RouterB-GigabitEthernet3/0/2] port trunk pvid vlan 11 [RouterB-GigabitEthernet3/0/2] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/3, disable the spanning tree feature, and configure the port as a trunk port.
Page 112 [RouterB-rrpp-domain2] protected-vlan reference-instance 2 # Configure Router B as the transit node of primary ring 1, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable ring 1. [RouterB-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0 [RouterB-rrpp-domain2] ring 1 enable # Configure Router B as the assistant-edge node of subring 2 in RRPP domain 2, with...
Page 113 [RouterC-GigabitEthernet3/0/3] undo stp enable [RouterC-GigabitEthernet3/0/3] port link-type trunk [RouterC-GigabitEthernet3/0/3] undo port trunk permit vlan 1 [RouterC-GigabitEthernet3/0/3] port trunk permit vlan 12 [RouterC-GigabitEthernet3/0/3] port trunk pvid vlan 12 [RouterC-GigabitEthernet3/0/3] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/4, disable the spanning tree feature, and configure the port as a trunk port.
Page 114 [RouterC] rrpp enable Configure Router D: # Create VLANs 11 and 12, map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2, and activate MST region configuration. <RouterD> system-view [RouterD] vlan 11 to 12 [RouterD] stp region-configuration [RouterD-mst-region] instance 1 vlan 11 [RouterD-mst-region] instance 2 vlan 12 [RouterD-mst-region] active region-configuration [RouterD-mst-region] quit...
Page 115 # Configure Router D as the transit node of primary ring 1 in RRPP domain 2, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable ring 1. [RouterD-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0 [RouterD-rrpp-domain2] ring 1 enable [RouterD-rrpp-domain2] quit...
Page 116 # Enable RRPP. [RouterE] rrpp enable Configure Router F: # Create VLAN 11, map VLAN 11 to MSTI 1, and activate MST region configuration. <RouterF> system-view [RouterF] vlan 11 [RouterF-vlan11] quit [RouterF] stp region-configuration [RouterF-mst-region] instance 1 vlan 11 [RouterF-mst-region] active region-configuration [RouterF-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2, disable the spanning tree feature, and configure the two ports as trunk...
Page 117: Troubleshooting
[RouterB-rrpp-ring-group1] domain 1 ring 3 # Create RRPP ring group 1 on Router C, and add subrings 2 and 3 to the RRPP ring group. [RouterC] rrpp ring-group 1 [RouterC-rrpp-ring-group1] domain 2 ring 2 [RouterC-rrpp-ring-group1] domain 1 ring 3 Verify the configuration: Use the display command to view RRPP configuration and operational information on each device.
Page 118: Configuring Smart Link
Configuring Smart Link Smart Link is supported only when the SAP module is operating in bridge mode. Smart Link overview Background To avoid single-point failures and guarantee network reliability, downstream devices are usually dual-homed to upstream devices, as shown in Figure Figure 28 Diagram for a dual uplink network To remove network loops on a dual-homed network, you can use a spanning tree protocol or the...
Page 119: Terminology
• Easy to configure. 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, and the original active port transits to the blocked state.
Page 120: Smart Link Collaboration Mechanisms
When a port switches to the forwarding state, the system outputs log information to notify the user of the port state change. Topology change mechanism Because link switchover can outdate the MAC address forwarding entries and ARP/ND entries on all devices, a forwarding entry update mechanism is needed to ensure proper transmission.
Page 121: Smart Link Configuration Task List
Smart Link configuration task list A Smart Link device is a device that supports Smart Link and is configured with a smart link group and a transmit control VLAN for flush message transmission. Router C and Router D in Figure 28 two examples of Smart Link devices.
Page 122: Configuring Member Ports For A Smart Link Group
Step Command Remarks Not required if the device is operating in PVST mode. Enter MST region view. stp region-configuration For more information about the command, see Layer 2—LAN Switching Command Reference. Optional. Use either method. • Method 1: All VLANs in an MST region are instance instance-id vlan mapped to CIST (MSTI 0) by Configure the...
Page 123: Configuring Role Preemption For A Smart Link Group
Step Command port interface-type interface-number { master | Configure member ports for a smart link group. slave } In interface view To configure member ports for a smart link group in interface view: Step Command Enter system view. system-view Enter Ethernet interface view or layer 2 interface interface-type interface-number aggregate interface view.
Page 124: Configuring The Collaboration Between Smart Link And Cc Of Cfd
Step Command Remarks Optional. Enable flush update in the flush enable [ control-vlan By default, flush update is enabled, and specified control VLAN. vlan-id ] VLAN 1 is the control VLAN. Configuring the collaboration between Smart Link and CC of When configuring the collaboration between Smart Link and the CC function of CFD on a smart link member port, make sure that the control VLAN of the smart link group to which the port belongs matches the detection VLAN of the CC function of CFD.
Page 125: Displaying And Maintaining Smart Link
To enable the receiving of flush messages: Step Command Remarks Enter system view. system-view Enter Ethernet interface interface interface-type view or Layer 2 aggregate interface-number interface view. Configure the control VLANs smart-link flush enable By default, no control VLAN exists for receiving flush [ control-vlan vlan-id-list ] for receiving flush messages.
Page 126 Figure 29 Network diagram Configuration procedure Configure Router C: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <RouterC> system-view [RouterC] vlan 1 to 30 [RouterC] stp region-configuration [RouterC-mst-region] instance 1 vlan 1 to 30 [RouterC-mst-region] active region-configuration [RouterC-mst-region] quit # Shut down GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2, disable the spanning tree feature...
Page 127 # Enable flush message sending in smart link group 1, and configure VLAN 10 as the transmit control VLAN. [RouterC-smlk-group1] flush enable control-vlan 10 [RouterC-smlk-group1] quit # Bring up GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 again. [RouterC] interface gigabitethernet 3/0/1 [RouterC-GigabitEthernet3/0/1] undo shutdown [RouterC-GigabitEthernet3/0/1] quit [RouterC] interface gigabitethernet 3/0/2 [RouterC-GigabitEthernet3/0/2] undo shutdown...
Page 128 [RouterD-GigabitEthernet3/0/1] undo shutdown [RouterD-GigabitEthernet3/0/1] quit [RouterD] interface gigabitethernet 3/0/2 [RouterD-GigabitEthernet3/0/2] undo shutdown [RouterD-GigabitEthernet3/0/2] quit Configure Router B: # Create VLANs 1 through 30. <RouterB> system-view [RouterB] vlan 1 to 30 # Configure GigabitEthernet 3/0/1 as a trunk port, and assign it to VLANs 1 through 30. Enable flush message receiving on it, and configure VLAN 10 and VLAN 20 as the receive control VLANs.
Page 129 # Configure GigabitEthernet 3/0/2 as a trunk port, and assign it to VLANs 1 through 30. Disable the spanning tree feature and enable flush message receiving on it, and configure VLAN 10 as the receive control VLAN. [RouterE] interface gigabitethernet 3/0/2 [RouterE-GigabitEthernet3/0/2] port link-type trunk [RouterE-GigabitEthernet3/0/2] port trunk permit vlan 1 to 30 [RouterE-GigabitEthernet3/0/2] undo stp enable...
Page 130: Multiple Smart Link Groups Load Sharing Configuration Example
GigabitEthernet3/0/2 SLAVE STANDBY 1 17:45:20 2010/02/21 Use the display smart-link flush command to display the flush messages received on a device. # Display the flush messages received on Router B. [RouterB] display smart-link flush Received flush packets Receiving interface of the last flush packet : GigabitEthernet3/0/3 Receiving time of the last flush packet : 16:25:21 2009/02/21...
Page 131 [RouterC] interface gigabitethernet 3/0/1 [RouterC-GigabitEthernet3/0/1] shutdown [RouterC-GigabitEthernet3/0/1] undo stp enable [RouterC-GigabitEthernet3/0/1] port link-type trunk [RouterC-GigabitEthernet3/0/1] port trunk permit vlan 1 to 200 [RouterC-GigabitEthernet3/0/1] quit [RouterC] interface gigabitethernet 3/0/2 [RouterC-GigabitEthernet3/0/2] shutdown [RouterC-GigabitEthernet3/0/2] undo stp enable [RouterC-GigabitEthernet3/0/2] port link-type trunk [RouterC-GigabitEthernet3/0/2] port trunk permit vlan 1 to 200 [RouterC-GigabitEthernet3/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs for smart link group 1.
Page 132 # Configure GigabitEthernet 3/0/1 as a trunk port, assign it to VLANs 1 through 200, enable flush message receiving, and configure VLAN 10 and VLAN 110 as the receive control VLANs on the port. [RouterB] interface gigabitethernet 3/0/1 [RouterB-GigabitEthernet3/0/1] port link-type trunk [RouterB-GigabitEthernet3/0/1] port trunk permit vlan 1 to 200 [RouterB-GigabitEthernet3/0/1] smart-link flush enable control-vlan 10 110 [RouterB-GigabitEthernet3/0/1] quit...
Page 133 [RouterA-GigabitEthernet3/0/1] quit [RouterA] interface gigabitethernet 3/0/2 [RouterA-GigabitEthernet3/0/2] port link-type trunk [RouterA-GigabitEthernet3/0/2] port trunk permit vlan 1 to 200 [RouterA-GigabitEthernet3/0/2] smart-link flush enable control-vlan 10 110 [RouterA-GigabitEthernet3/0/2] quit Verify the configuration: Use the display smart-link group command to display the smart link group configuration on a device.
Page 134: Smart Link And Cfd Collaboration Configuration Example
Smart Link and CFD collaboration configuration example Network requirements As shown in Figure • Router A, Router B, Router C, and Router D form a maintenance domain (MD) of level 5. Router C is a Smart Link device, and Router A, Router B, and Router D are associated devices. Traffic of VLANs 1 through 200 on Router C is dually uplinked to Router A by Router B and Router D.
Page 135 [RouterA-GigabitEthernet3/0/2] smart-link flush enable control-vlan 10 110 [RouterA-GigabitEthernet3/0/2] quit # Enable CFD and create an MD of level 5. [RouterA] cfd enable [RouterA] cfd md MD level 5 # Create MA MA_A for the MD and configure the MA to serve VLAN 10, and create service instance 1 for the MD and MA.
Page 136 [RouterB-GigabitEthernet3/0/2] quit Configure Router C: # Create VLAN 1 through VLAN 200, map VLANs 1 through 100 to MSTI 1 and VLANs 101 through 200 to MSTI 2, and activate MST region configuration. <RouterC> system-view [RouterC] vlan 1 to 200 [RouterC] stp region-configuration [RouterC-mst-region] instance 1 vlan 1 to 100 [RouterC-mst-region] instance 2 vlan 101 to 200...
Page 137 [RouterC-smlk-group2] preemption mode role [RouterC-smlk-group2] flush enable control-vlan 110 [RouterC-smlk-group2] quit # Enable CFD and create an MD of level 5. [RouterC] cfd enable [RouterC] cfd md MD level 5 # Create MA MA_A for the MD and configure the MA to serve VLAN 10. Create service instance 1 for the MD and MA.
Page 138 [RouterD] interface gigabitethernet 3/0/1 [RouterD-GigabitEthernet3/0/1] port link-type trunk [RouterD-GigabitEthernet3/0/1] port trunk permit vlan 1 to 200 [RouterD-GigabitEthernet3/0/1] smart-link flush enable control-vlan 10 110 [RouterD-GigabitEthernet3/0/1] quit # Configure GigabitEthernet 3/0/2 as a trunk port and assign it to VLANs 1 through 200. Disable the spanning tree feature and enable flush message receiving on it.
Page 139: Configuring Vrrp
Configuring VRRP The interfaces that VRRP involves can be only Layer 3 Ethernet interfaces and subinterfaces, VLAN interfaces, Layer 3 aggregate interfaces, and RPR logical interfaces unless otherwise specified. VRRP cannot be configured on an interface of an aggregation group. VRRP overview As shown in Figure...
Page 140: Vrrp Standard Mode
VRRP standard mode VRRP group VRRP combines a group of routers (including a master and multiple backups) on a LAN into a virtual router called VRRP group. A VRRP group has the following features: • A virtual router has a virtual IP address. A host on the LAN only needs to know the IP address of the virtual router and uses the IP address as the next hop of the default route.
Page 141 Non-preemptive mode—When a router in the VRRP group becomes the master, it stays as the master as long as it operates correctly, even if a backup is assigned a higher priority later. Preemptive mode—When a backup finds its priority higher than that of the master, the backup sends VRRP advertisements to start a new master election in the VRRP group and becomes the master.
Page 142 Figure 34 IPv4 VRRPv2 packet format Figure 35 IPv6 VRRPv2 packet format Version Type Virtual Rtr ID Priority Count IPv6 Addrs Auth Type Adver Int Checksum IPv6 address 1 IPv6 address n Authentication data 1 Authentication data 2 Figure 36 IPv4/IPv6 VRRPv3 packet format A VRRP packet comprises the following fields: •...
Page 143 • Type—Type of the VRRP packet. It must be VRRP advertisement, represented by 1. • Virtual Rtr ID (VRID)—ID of the virtual router. It ranges from 1 to 255. • Priority—Priority of the router in the VRRP group, in the range 0 to 255. A greater value represents a higher priority.
Page 144 solved by tracking a specified uplink interface. If the tracked uplink interface is down or removed, the priority of the master is automatically decreased by a specified value and a higher priority router in the VRRP group becomes the master. Tracking a track entry By monitoring a track entry, you can do the following: Monitor an uplink and change the priority of the router according to the uplink state.
Page 145: Vrrp Load Balancing Mode
Figure 38 VRRP in load sharing mode A router can be in multiple VRRP groups and hold a different priority in a different group. As shown in Figure 38, the following VRRP groups are present: VRRP group 1—Router A is the master. Router B and Router C are the backups. VRRP group 2—Router B is the master.
Page 146 The master assigns virtual MAC addresses to all members, including itself. This example assumes that the virtual IP address of the VRRP group is 10.1.1.1/24, Router A is the master, and Router B is the backup. Router A assigns 000f-e2ff-0011 to itself and 000f-e2ff-0012 to Router B.
Page 147 Figure 41 Sending packets to different routers for forwarding Virtual forwarder Creating a virtual forwarder Virtual MAC addresses enable traffic distribution across the routers in a VRRP group. To enable the routers in the VRRP group to forward the packets, be sure to create virtual forwarders (VFs) on the routers.
Page 148 The VFs corresponding to a virtual MAC address on different routers in the VRRP group back up each other. Figure 42 VF information Figure 42 shows the VF table on each router in the VRRP group and how the routers back up one another.
Page 149: Configuring The Ipv4/Ipv6 Vrrp Version
VF tracking The AVF forwards packets destined to the MAC address of the AVF. If the uplink of the AVF fails and no LVF is notified to take over the AVF role, hosts on the LAN that use the MAC address of the AVF as their gateway MAC address cannot access the external network.
Page 150: Configuring Vrrp For Ipv4
Configuring VRRP for IPv4 VRRP for IPv4 configuration task list To form a VRRP group, perform the following configurations on each device in the VRRP group. Complete these tasks to configure VRRP for IPv4: Task Remarks Configuring a VRRP working mode Optional.
Page 151: Specifying The Type Of Mac Addresses Mapped To Virtual Ip Addresses
Specifying the type of MAC addresses mapped to virtual IP addresses You can configure VRRP in standard mode to map real or virtual MAC addresses to the virtual IP addresses of VRRP groups, so the master in a VRRP group uses the specified type of MAC address as the source MAC address for sending packets and answering ARP requests.
Page 152 Figure 43 VRRP control VLAN As shown in Figure 43, configure ambiguous VLAN termination for VLAN 10 and VLAN 20 on the Layer 3 Ethernet subinterfaces on routers. To enable the master periodically multicasting VRRP advertisements to the backups, be sure to enable the subinterfaces configured with VLAN termination to transmit broadcast/multicast packets.
Page 153: Creating A Vrrp Group And Configuring Virtual Ip Address
Step Command Remarks • Enter Layer 3 Ethernet subinterface view: interface interface-type interface-number.subnu mber • Enter Layer 3 Enter interface view. Use either command. aggregation subinterface view: interface route-aggregation interface-number.subnu mber • Specify a VRRP control VLAN for the subinterface configured with ambiguous Dot1q Use either command.
Page 154: Configuring Router Priority, Preemptive Mode And Tracking Function
• A VRRP group is removed after you remove all its virtual IP addresses, and all its configurations become invalid. • Removal of the VRRP group on the IP address owner causes IP address collision. To avoid the collision, change the IP address of the interface on the IP address owner before you remove the VRRP group from the interface.
Page 155: Configuring Vf Tracking
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure router priority in vrrp vrid virtual-router-id priority the VRRP group. priority-value The default is 100. Optional. Configure the router in the vrrp vrid virtual-router-id The router in the VRRP group VRRP group to operate in preempt-mode [ timer delay operates in preemptive mode and...
Page 156: Enabling Arp Entry Backup
Step Command Remarks Enter the specified interface interface interface-type view. interface-number • Configure the VF tracking function to monitor a specified track entry and specify the value by which the weight decreases: vrrp vrid virtual-router-id weight track Use either method. track-entry-number Configure VF tracking.
Page 157: Configuring Vrrp Packet Attributes
Configuring VRRP packet attributes Configuration prerequisites Before you configure the relevant attributes of VRRP packets, create a VRRP group and configure a virtual IP address for it. Configuration guidelines • You might configure different authentication modes and authentication keys for the VRRP groups on an interface.
Page 158: Enabling The Trap Function For Vrrp
Enabling the trap function for VRRP When the trap function is enabled for VRRP, VRRP generates traps with severity level errors to report its key events. The traps are sent to the information center of the device, where you can configure whether to output the trap information and the output destination.
Page 159: Specifying The Type Of Mac Addresses Mapped To Virtual Ipv6 Addresses
Task Remarks Optional. Specifying the type of MAC addresses mapped to virtual IPv6 This configuration does not apply to VRRP addresses load balancing mode. Creating a VRRP group and configuring a virtual IPv6 Required. address Configuring router priority, preemptive mode and tracking Optional.
Page 160: Creating A Vrrp Group And Configuring A Virtual Ipv6 Address
Creating a VRRP group and configuring a virtual IPv6 address When creating a VRRP group, configure a virtual IPv6 address for the VRRP group. You can configure multiple virtual IPv6 addresses for a VRRP group. A VRRP group is automatically created when you specify the first virtual IPv6 address for the VRRP group.
Page 161: Configuring Router Priority, Preemptive Mode And Tracking Function
Configuring router priority, preemptive mode and tracking function Configuration prerequisites Before you configure router priority, preemptive mode and tracking function, create a VRRP group and configure its virtual IPv6 address. Configuration guidelines • The running priority of an IP address owner is always 255 and you do not need to configure it. An IP address owner always operates in preemptive mode.
Page 162: Configuring Vf Tracking
Configuring VF tracking Configuration prerequisites Before you configure the VF tracking function, create a VRRP group and configure a virtual IPv6 address for it. Configuration procedure VRRP operates in load balancing mode. Assume that you have configured the VF tracking function to monitor a track entry and specified the value by which the weight decreases.
Page 163: Configuring Vrrp Packet Attributes
Configuring VRRP packet attributes Configuration prerequisites Before you configure the relevant attributes of VRRP packets, create a VRRP group and configure a virtual IPv6 address. Configuration guidelines • You might configure different authentication modes and authentication keys for the VRRP groups on an interface.
Page 164: Ipv4-Based Vrrp Configuration Examples
Task Command Remarks reset vrrp ipv6 statistics [ interface interface-type Clear VRRP group statistics. Available in user view. interface-number [ vrid virtual-router-id ] ] IPv4-based VRRP configuration examples Single VRRP group configuration example Network requirements • Host A needs to access Host B on the Internet, using 202.38.160.111/24 as its default gateway. •...
Page 165 <RouterB> system-view [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] ip address 202.38.160.2 255.255.255.0 # Create VRRP group 1 and configure its virtual IP address as 202.38.160.111. [RouterB-GigabitEthernet1/0/1] vrrp vrid 1 virtual-ip 202.38.160.111 # Configure Router B to operate in preemptive mode, with the preemption delay set to 5 seconds.
Page 166: Vrrp Interface Tracking Configuration Example
Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID Adver Timer Admin Status : Up State : Master Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None...
Page 167 Figure 45 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ip address 202.38.160.1 255.255.255.0 # Create VRRP group 1 and configure its virtual IP address as 202.38.160.111. [RouterA-GigabitEthernet1/0/2] vrrp vrid 1 virtual-ip 202.38.160.111 # Configure the priority of Router A in the VRRP group as 110, which is higher than that of Router B (100), so that Router A can become the master.
Page 168 [RouterB-GigabitEthernet1/0/2] vrrp vrid 1 authentication-mode simple hello # Configure the master to send VRRP packets every 4 seconds. [RouterB-GigabitEthernet1/0/2] vrrp vrid 1 timer advertise 4 # Configure Router B to operate in preemptive mode, so that Router B can become the master after the priority of Router A decreases to a value lower than 100.
Page 169: Multiple Vrrp Groups Configuration Example
[RouterA-GigabitEthernet1/0/1] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/2 VRID Adver Timer Admin Status : Up State : Backup Config Pri : 110 Running Pri : 80 Preempt Mode : Yes...
Page 170 Figure 46 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ip address 202.38.160.1 255.255.255.0 # Create VRRP group 1 and configure its virtual IP address as 202.38.160.111. [RouterA-GigabitEthernet1/0/1] vrrp vrid 1 virtual-ip 202.38.160.111 # Set the priority of Router A in VRRP group 1 to 110, which is higher than that of Router B (100), so that Router A can become the master in VRRP group 1.
Page 171 Total number of virtual routers : 2 Interface GigabitEthernet1/0/1 VRID Adver Timer Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 202.38.160.111 Virtual MAC : 0000-5e00-0101 Master IP...
Page 172: Vrrp Load Balancing Mode Configuration Example
NOTE: To implement load balancing between the VRRP groups, be sure to configure the default gateway as 202.38.160.111 or 202.38.160.112 on the hosts on network segment 202.38.160.0/24. VRRP load balancing mode configuration example Network requirements • Router A, Router B, and Router C belong to VRRP group 1 with the virtual IP address of 10.1.1.1/24.
Page 173 [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ip address 10.1.1.2 24 [RouterA-GigabitEthernet1/0/1] vrrp vrid 1 virtual-ip 10.1.1.1 # Set the priority of Router A in VRRP group 1 to 120, which is higher than that of Router B (110) and that of Router C (100), so that Router A can become the master. [RouterA-GigabitEthernet1/0/1] vrrp vrid 1 priority 120 # Configure Router A to operate in preemptive mode so that it can become the master whenever it works correctly.
Page 174 [RouterC-GigabitEthernet1/0/1] ip address 10.1.1.4 24 [RouterC-GigabitEthernet1/0/1] vrrp vrid 1 virtual-ip 10.1.1.1 # Set Router C to operate in preemptive mode and set the preemption delay to 5 seconds. [RouterC-GigabitEthernet1/0/1] vrrp vrid 1 preempt-mode timer delay 5 [RouterC-GigabitEthernet1/0/1] quit # Create track entry 1 to associate with the physical status of GigabitEthernet 1/0/2 on Router C. When the track entry becomes negative, it means that the interface fails.
Page 175 10.1.1.3 (Backup) 10.1.1.4 (Backup) Forwarder Information: 3 Forwarders 1 Active Config Weight : 255 Running Weight : 255 Forwarder 01 State : Active Virtual MAC : 000f-e2ff-0011 (Owner) Owner ID : 0000-5e01-1101 Priority : 255 Active : local Forwarder 02 State : Listening Virtual MAC...
Page 176 Virtual MAC : 000f-e2ff-0011 (Learnt) Owner ID : 0000-5e01-1101 Priority : 127 Active : 10.1.1.2 Forwarder 02 State : Active Virtual MAC : 000f-e2ff-0012 (Owner) Owner ID : 0000-5e01-1103 Priority : 255 Active : local Forwarder 03 State : Listening Virtual MAC : 000f-e2ff-0013 (Learnt) Owner ID...
Page 177 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 Forwarder Switchover Track Information: Track Object State : Positive Member IP...
Page 178 Forwarder 03 State : Initialize Virtual MAC : 000f-e2ff-0013 (Learnt) Owner ID : 0000-5e01-1105 Priority Active : 10.1.1.4 Forwarder Weight Track Information: Track Object State : Negative Weight Reduced : 250 # Use the display vrrp verbose command to display the detailed information about VRRP group 1 on Router C.
Page 179 Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 Forwarder Switchover Track Information: Track Object State : Positive Member IP : 10.1.1.2 Track Object State : Positive Member IP : 10.1.1.3 The output shows that when GigabitEthernet 1/0/2 on Router A fails, the weight of the AVF on Router A decreases to 5, which is lower than the lower limit of failure.
Page 180 Member IP : 10.1.1.2 Track Object State : Positive Member IP : 10.1.1.3 The output shows that when the timeout timer expires, the VF corresponding to virtual MAC address 000f-e2ff-0011 is removed, and no longer forwards the packets destined for the MAC address.
Page 181: Ipv6-Based Vrrp Configuration Examples
VRID Adver Timer Admin Status : Up State : Master Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 10.1.1.1 Member IP List : 10.1.1.4 (Local, Master) Forwarder Information: 2 Forwarders 2 Active Config Weight : 255 Running Weight : 255...
Page 182 Figure 48 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] ipv6 [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ipv6 address fe80::1 link-local [RouterA-GigabitEthernet1/0/1] ipv6 address 1::1 64 # Create a VRRP group 1 and set its virtual IPv6 addresses to FE80::10 and 1::10. [RouterA-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local [RouterA-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 virtual-ip 1::10 # Configure the priority of Router A in VRRP group 1 as 110, which is higher than that of Router...
Page 183 # Enable Router B to send RA messages, so that Host A can learns the default gateway address. [RouterB-GigabitEthernet1/0/1] undo ipv6 nd ra halt Verify the configuration: After the configuration, Host B can be pinged successfully on Host A. To verify your configuration, use the display vrrp ipv6 verbose command.
Page 184: Vrrp Interface Tracking Configuration Example
VRID Adver Timer : 100 Admin Status : Up State : Master Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : FE80::10 1::10 Virtual MAC : 0000-5e00-0201 Master IP : FE80::2 The output shows that when Router A fails, Router B becomes the master, and packets sent from Host A to Host B are forwarded by Router B.
Page 185 Figure 49 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] ipv6 [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ipv6 address fe80::1 link-local [RouterA-GigabitEthernet1/0/2] ipv6 address 1::1 64 # Create a VRRP group 1 and set its virtual IPv6 addresses to FE80::10 and 1::10. [RouterA-GigabitEthernet1/0/2] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local [RouterA-GigabitEthernet1/0/2] vrrp ipv6 vrid 1 virtual-ip 1::10 # Configure the priority of Router A in VRRP group 1 as 110, which is higher than that of Router...
Page 186 [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] ipv6 address fe80::2 link-local [RouterB-GigabitEthernet1/0/2] ipv6 address 1::2 64 # Create a VRRP group 1 and set its virtual IPv6 addresses to FE80::10 and 1::10. [RouterB-GigabitEthernet1/0/2] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local [RouterB-GigabitEthernet1/0/2] vrrp ipv6 vrid 1 virtual-ip 1::10 # Set the authentication mode of VRRP group 1 as simple and authentication key as hello.
Page 187 Become Master : 2200ms left Auth Type : Simple : hello Virtual IP : FE80::10 1::10 Master IP : FE80::1 The output shows that in VRRP group 1 Router A is the master, Router B is the backup and packets sent from Host A to Host B are forwarded by Router A. When interface GigabitEthernet 1/0/1 on Router A is not available, you can still ping Host B on Host A.
Page 188: Multiple Vrrp Groups Configuration Example
Multiple VRRP groups configuration example Network requirements • In the network, some hosts use 1::10/64 as their default gateway and some hosts use 1::20/64 as their default gateway. • Load sharing and mutual backup between default gateways can be implemented by using VRRP groups.
Page 189 # Create VRRP group 1 and set its virtual IPv6 addresses to FE80::10 and 1::10. [RouterB-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local [RouterB-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 virtual-ip 1::10 # Create VRRP group 2 set its virtual IPv6 addresses to FE80::20 and 1::20. [RouterB-GigabitEthernet1/0/1] vrrp ipv6 vrid 2 virtual-ip fe80::20 link-local [RouterB-GigabitEthernet1/0/1] vrrp ipv6 vrid 2 virtual-ip 1::20 # Set the priority of Router B in VRRP group 2 to 110, which is higher than that of Router A (100),...
Page 190: Vrrp Load Balancing Mode Configuration Example
Become Master : 2200ms left Auth Type : None Virtual IP : FE80::10 1::10 Master IP : FE80::1 Interface GigabitEthernet1/0/1 VRID Adver Timer : 100 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time...
Page 191 Figure 51 Network diagram Configuration procedure Configure Router A: # Configure VRRP to operate in load balancing mode. <RouterA> system-view [RouterA] vrrp mode load-balance # Create VRRP group 1 and configure its virtual IPv6 addresses as FE80::10 and 1::10. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] ipv6 address fe80::1 link-local [RouterA-GigabitEthernet1/0/1] ipv6 address 1::1 64 [RouterA-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local...
Page 192 # Configure VF tracking to monitor track entry 1 and specify the value by which the weight decreases, making the weight of Router A decrease by more than 245 (250 in this example) when track entry 1 turns to negative. In such a case, another router with a higher weight can take over.
Page 193 [RouterC-GigabitEthernet1/0/1] quit # Create track entry 1 to associate with the physical status of GigabitEthernet 1/0/2 on Router C. When the track entry becomes negative, it means that the interface fails. [RouterC] track 1 interface gigabitethernet 1/0/2 # Configure VF tracking to monitor track entry 1 and specify the value by which the weight decreases, making the weight of Router C decrease by more than 245 (250 in this example) when track entry 1 turns to negative.
Page 194 Priority : 127 Active : FE80::3 Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 # Display the detailed information about VRRP group 1 on Router B. [RouterB] display vrrp ipv6 verbose IPv6 Standby Information: Run Mode : Load Balance Run Method : Virtual MAC...
Page 195 Run Mode : Load Balance Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Become Master...
Page 196 Admin Status : Up State : Master Config Pri : 120 Running Pri : 120 Preempt Mode : Yes Delay Time 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 0 Active Config Weight : 255...
Page 197: Packet Forwarding
FE80::1 (Master) FE80::2 (Backup) Forwarder Information: 3 Forwarders 2 Active Config Weight : 255 Running Weight : 255 Forwarder 01 State : Active Virtual MAC : 000f-e2ff-4011 (Take Over) Owner ID : 0000-5e01-1101 Priority : 85 Active : local Redirect Time : 93 secs Time-out Time : 1293 secs...
Page 198 FE80::1 (Master) FE80::2 (Backup) Forwarder Information: 2 Forwarders 1 Active Config Weight : 255 Running Weight : 255 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...
Page 199: Troubleshooting Vrrp
State : Listening Virtual MAC : 000f-e2ff-4013 (Learnt) Owner ID : 0000-5e01-1105 Priority : 127 Active : FE80::3 Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 The output shows that when Router A fails, Router B becomes the master because its priority is higher than that of Router C.
Page 200 Analysis The VRRP advertisement interval is set too short. Solution Increase the interval for sending VRRP advertisements or configure a preemption delay.
Page 201: Configuring Bfd
Configuring BFD Introduction to BFD Devices must detect communication failures quickly so that measures can be taken in time to ensure service continuity and enhance network availability. Fault detection methods include the following: • Hardware detection—Detects link failures by sending hardware detection signals, such as synchronous digital hierarchy (SDH) alarms.
Page 202 After establishing neighborships, the protocol notifies BFD of the neighbor information, including destination and source addresses. BFD uses the information to establish BFD sessions. Figure 53 BFD fault detection (on OSPF routers) Router A Router B Fault BFD neighbors BFD notifies the OSPF link failure OSPF neighbors Backup link BFD fault detection...
Page 203: Bfd Packet Format
• Active mode—BFD actively sends BFD control packets regardless of whether any BFD control packet is received from the peer. • Passive mode—BFD does not send control packets until a BFD control packet is received from the peer. At least one end must operate in active mode for a BFD session to be established. After a BFD session is established, both ends must operate in one of the following BFD operating modes: •...
Page 204 • Diag—This bit indicates the reason for the last transition of the local session from up to some other state. Table 19 lists the states. Table 19 Diag bit values Diag Description No Diagnostic. Control Detection Time Expired. Echo Function Failed. Neighbor Signaled Session Down.
Page 205: Supported Features
• Required Min Echo RX Interval—This is the minimum interval (in milliseconds) between received BFD echo packets that this system is capable of supporting. If this value is zero, the transmitting system does not support the receipt of BFD echo packets. •...
Page 206: Configuration Procedure
Configuration procedure To configure BFD basic functions: Step Command Remarks Enter system view. system-view Optional. Specify the mode for bfd session init-mode { active | establishing a BFD session. passive } active by default. Configure the destination Optional. bfd multi-hop destination-port port number for multi-hop port-number 4784 by default.
Page 207: Enabling Trap
• The actual transmitting interval on Router A is 400 milliseconds, which is the greater value between the minimum interval for transmitting BFD control packets on Router A (100 milliseconds) and the minimum interval for receiving BFD control packets on Router B (400 milliseconds).
Page 208 Task Command Remarks display bfd session [ slot Display BFD session information (in slot-number [ all | verbose ] | Available in any view. verbose ] [ | { begin | exclude | standalone mode). include } regular-expression ] display bfd session [ chassis chassis-number slot Display BFD session information (in IRF slot-number [ all | verbose ] |...
Page 209: Configuring Track
Configuring Track Overview The Track module works between application and detection modules, as shown in Figure 55. It shields the differences between various detection modules from application modules. Collaboration is enabled after you associate the Track module with a detection module and an application module.
Page 210: Collaboration Application Example
Collaboration between the Track module and an application module After being associated with an application module, when the status of the Track entry changes, the Track module notifies the application module, which then takes proper actions. The following application modules can be associated with the Track module: •...
Page 211: Associating The Track Module With A Detection Module
Associating the Track module with a detection module Associating Track with NQA NQA supports multiple test types to analyze network performance, services, service quality. For example, an NQA test group can periodically detect whether a destination is reachable, or whether the TCP connection to a TCP server can be set up.
Page 212: Associating Track With Interface Management
Step Command Remarks Enter system view. system-view Create a track entry, associate it with the BFD track track-entry-number bfd echo session, and specify the interface interface-type interface-number delay time for the Track No track entry is created remote ip remote-ip local ip local-ip module to notify the by default.
Page 213: Associating The Track Module With An Application Module
Associating the Track module with an application module Associating Track with VRRP VRRP is an error-tolerant protocol. It adds a group of routers that can act as network gateways to a VRRP group, which forms a virtual router. Routers in the VRRP group elect the master acting as the gateway according to their priorities.
Page 214: Associating Track With Static Routing
Step Command Remarks Create a VRRP group and vrrp vrid virtual-router-id No VRRP group is created by configure its virtual IP virtual-ip virtual-address default. address. No track entry is specified for a VRRP group by default. vrrp [ ipv6 ] vrid virtual-router-id Associate a track entry with track track-entry-number This command is supported when...
Page 215: Associating Track With Pbr
• The Negative state of the track entry shows that the next hop of the static route is not reachable, and that the configured static route is invalid. • The Invalid state of the track entry shows that the accessibility of the next hop of the static route is unknown, and that the static route is valid.
Page 216 After you associate a track entry with an apply clause, the detection module associated with the track entry sends the detection result of the availability of the object (an interface or an IP address) specified in the apply clause. • The Positive state of the track entry shows that the object is available, and the apply clause is valid.
Page 217: Displaying And Maintaining Track Entries
Step Command Remarks • Set the outgoing interface, and associate it with a track entry: apply output-interface interface-type interface-number [ track track-entry-number ] [ interface-type interface-number [ track track-entry-number ] ] • Set the next hop, and associate it with a track entry: apply ip-address next-hop ip-address [ track track-entry-number ] [ ip-address...
Page 218 Figure 56 Network diagram Configuration procedure Configure the IP address of each interface as shown in Figure 56. (Details not shown.) Configure an NQA test group on Router A: # Create an NQA test group with the administrator name admin and the operation tag test. <RouterA>...
Page 219 [RouterA-GigabitEthernet1/0/1] vrrp vrid 1 timer advertise 5 # Configure Router A to operate in preemptive mode, and set the preemption delay to 5 seconds. [RouterA-GigabitEthernet1/0/1] vrrp vrid 1 preempt-mode timer delay 5 # Configure to monitor track entry 1 and specify the priority decrement to 30. [RouterA-GigabitEthernet1/0/1] vrrp vrid 1 track 1 reduced 30 Configure VRRP on Router B: <RouterB>...
Page 220 Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Become Master : 2200ms left Auth Type : Simple : ***** Virtual IP : 10.1.1.10 Master IP : 10.1.1.1 The output shows that in VRRP group 1, Router A is the master and Router B is a backup. Packets from Host A to Host B are forwarded through Router A.
Page 221: Configuring Bfd For A Vrrp Backup To Monitor The Master
Configuring BFD for a VRRP backup to monitor the master Network requirements • As shown in Figure 57, Router A and Router B belong to VRRP group 1, whose virtual IP address is 192.168.0.10. • The default gateway of the hosts in the LAN is 192.168.0.10. When Router A works correctly, the hosts in the LAN access the external network through Router A.
Page 222 Create a track entry to be associated with the BFD session on Router B: # Create track entry 1 to be associated with the BFD session to check whether Router A is reachable. [RouterB] track 1 bfd echo interface gigabitethernet 1/0/1 remote ip 192.168.0.101 local ip 192.168.0.102 Configure VRRP on Router B: # Create VRRP group 1, and configure the virtual IP address 192.168.0.10 for the group.
Page 223 <RouterB> debugging bfd event # When Router A fails, the following output is displayed on Router B. %Apr 1 17:35:18:236 2013 HPE VRRP/6/VRRP_STATUS_CHANGE: The status of IPv4 virt ual router 1 (configured on GigabitEthernet1/0/1) changed from Backup to Master: Timer expired.
Page 224: Configuring Bfd For The Vrrp Master To Monitor The Uplink
The output shows that when BFD detects that Router A fails, it notifies VRRP through the Track module to change the status of Router B to master without waiting for a period three times the advertisement interval. This ensures that a backup can quickly preempt as the master. Configuring BFD for the VRRP master to monitor the uplink Network requirements •...
Page 225 # Create VRRP group 1, and configure the virtual IP address of the group as 192.168.0.10. Configure the priority of Router A in VRRP group 1 as 110, and configure VRRP group 1 to monitor the status of track entry 1. When the status of the track entry becomes Negative, the priority of Router A decreases by 20.
Page 226 Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/2 VRID Adver Timer Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Become Master : 2200ms left...
Page 227: Static Routing-Track-Nqa Collaboration Configuration Example
Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/2 VRID Adver Timer Admin Status : Up State : Master Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 192.168.0.10...
Page 228 Figure 59 Network diagram Configuration procedure Specify the IP address for each interface as shown in Figure 59. (Details not shown.) Configure Router A: # Configure a static route to 30.1.1.0/24, with the address of the next hop as 10.1.1.2 and the default priority 60.
Page 229 # Configure track entry 1, and associate it with reaction entry 1 of the NQA test group (with the administrator admin, and the operation tag test). [RouterA] track 1 nqa entry admin test reaction 1 Configure Router B: # Configure a static route to 30.1.1.0/24, with the address of the next hop as 10.2.1.4. <RouterB>...
Page 230 Verifying the configuration # Display information about the track entry on Router A. [RouterA] display track all Track ID: 1 Status: Positive Duration: 0 days 0 hours 0 minutes 49 seconds Notification delay: Positive 0, Negative 0 (in seconds) Reference object: NQA entry: admin test Reaction: 1 # Display the routing table of Router A.
Page 231 10.1.1.0/24 Direct 0 10.1.1.1 GE1/0/1 10.1.1.1/32 Direct 0 127.0.0.1 InLoop0 10.2.1.0/24 Static 60 10.1.1.2 GE1/0/1 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 InLoop0 30.1.1.0/24 Static 80 10.3.1.3 GE1/0/2 127.0.0.0/8 Direct 0 127.0.0.1...
Page 232: Static Routing-Track-Bfd Collaboration Configuration Example
Static routing-Track-BFD collaboration configuration example Network requirements As shown in Figure 60, Router A, Router B, and Router C are connected to two segments 20.1.1.0/24 and 30.1.1.0/24. Configure static routes on these routers so that the two segments can communicate with each other. Configure route backup to improve network reliability. Router A is the default gateway of the hosts in segment 20.1.1.0/24.
Page 233 [RouterA] ip route-static 30.1.1.0 24 10.3.1.3 preference 80 # Configure the source address of BFD echo packets as 10.10.10.10. [RouterA] bfd echo-source-ip 10.10.10.10 # Configure track entry 1, and associate it with the BFD session. Check whether Router A can be interoperated with the next hop of static route, which is Router B.
Page 234 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 InLoop0 30.1.1.0/24 Static 60 10.2.1.2 GE1/0/1 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 the BFD detection result: the next hop 10.2.1.2 is reachable (the status of the track entry is Positive), and the master static route takes effect.
Page 235: Vrrp-Track-Interface Management Collaboration Configuration Example
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 --- 30.1.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/2 ms # The output on Router B is similar to that on Router A.
Page 236 Figure 61 Network diagram Configuration procedure Specify the IP address for each interface as shown in Figure 61. (Details not shown.) Configure a track entry on Router A: # Configure track entry 1, and associate it with the physical status of the uplink interface GigabitEthernet 1/0/2.
Page 237 Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 10.1.1.10 Virtual MAC : 0000-5e00-0101 Master IP : 10.1.1.1 VRRP Track Information: Track Object State : Positive Pri Reduced : 30 # Display detailed information about VRRP group 1 on Router B.
Page 238 VRRP Track Information: Track Object State : Negative Pri Reduced : 30 # After shutting down the uplink interface on Router A, display detailed information about VRRP group 1 on Router B. [RouterB-GigabitEthernet1/0/1] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC...
Page 239: Document Conventions And Icons
Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.
Page 240: 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 241: 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 242: 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 243 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 244: Index
Index automatic shut down (unidirectional links), 42 Numerics auto-recovery (DLDP link mechanism), 37 802.1 (configuring CFD protocol version), 22 backup mechanism (Smart Link), 112 activating RRPP domain, 82 active active operation mode, 195 operation mode (BFD), 195 associating with Track, 204 switchover (high availability technologies), 3 basic configuration, 198 switchover configuration, 5, 5...
Page 245 centralized RPR BFD for a VRRP backup to monitor the master, 214 physical port, 55 BFD for VRRP master to monitor the uplink, 217 CFD, 18, 21, 27 basic concepts, 18 CFD continuity check on MEP, 24 configuration, 18, 21, 22, 27 CFD function, 24 configuring continuity check on MEP, 24 CFD linktrace on MEP, 25...
Page 246 RPR protection, 59 Smart Link collaboration, 127 RPR protection mode, 59 control VLAN RPR protection mode/static ringlet RRPP, 71 selection, 68 RRPP configuration, 79 RPR protection reversion mode, 59 creating RPR station name, 59 IPv6 VRRP group, 153 RPR timer, 62 RPR logical interface, 57 RRPP, 70, 78, 84 RRPP domain, 78...
Page 247 creating RRPP domain, 78 setting DelayDown timer, 40 link detection protocol. Use DLDP setting mode, 39 loopback (CFD), 20 setting port shutdown mode, 40 restarting standby MPU, 6 setting send advertisement packet interval, 39 Smart Link configuration, 114 simple authentication mode, 34 disable (DLDP link state), 32 state and packet type, 35 disconnect state (RRPP ring), 71...
Page 248 RRPP load balanced intersecting rings wrapping, 53 configuration, 101 field description (Ethernet OAMPDU), 7 RRPP single ring configuration, 84 flush Ethernet OAM Smart Link message, 112, 116, 117 configuration, 7, 10, 15 update mechanism (Smart Link), 113 configuring basic function, 11 format configuring connection detection timer, 11 BFD packet, 196...
Page 249 RRPPDU type, 72 enabling ARP entry backup, 149 timer (RRPP), 73 enabling RPR mate port smart connection, 58 high availability Ethernet OAM. See Ethernet OAM active switchover configuration, 5, 5 evaluation, 1 adding static ringlet selection entry, 60 fault detection technologies, 2 BFD for a VRRP backup configuration to ignoring standby MPU version check, 5 monitor the master, 214...
Page 250 VRRP configuration, 132 IPv4 VRRP configuration, 143 VRRP working mode configuration, 143 IPv4 VRRP interface tracking configuration, 159 VRRP-track-interface management IPv4 VRRP single group configuration, 157 collaboration configuration, 228 IPv6 VRRP configuration, 151 VRRP-Track-NQA collaboration link configuration, 210 active state (DLDP), 32 advertisement state (DLDP), 32 auto shutdown of unidirectional link (DLDP), 42 ignoring standby MPU version check, 5...
Page 251 Smart Link uplink traffic-triggered MAC enabling Smart Link flush message receipt, 117 address learning, 113 enabling Smart Link flush send, 116 specifying type mapped to virtual IPv4 flush (Smart Link), 112 address (VRRP), 144 linktrace (CFD), 21 specifying type mapped to virtual IPv6 linktrace reply (CFD), 21 address (VRRP), 152 loopback (CFD), 20...
Page 252 continuity check message frame (CFD), 20 normal mode (DLDP), 39 linktrace message frame (CFD), 21 multi-hop detection (BFD), 194 associating with Track, 204 multiple groups configuration (Smart Link), 123 configuring static routing-Track-NQA collaboration, 220 high availability fault detection technologies, 2 neighbor VRRP-Track-NQA collaboration setting DLDP mode, 39...
Page 253 configuring role preemption for Smart Link configuring BFD for VRRP master to monitor the group, 116 uplink, 217 configuring RRPP port, 80 configuring CFD, 27 enabling DLDP, 39 configuring CFD continuity check on MEP, 24 IPv4 VRRP configuration, 143 configuring CFD function, 24 IPv4 VRRP interface tracking configuring CFD linktrace on MEP, 25 configuration, 159...
Page 254 configuring RPR protection, 59 enabling DLDP, 39 configuring RPR protection mode, 59 enabling RPR mate port smart connection, 58 configuring RPR protection reversion enabling Smart Link flush message receipt, 117 mode, 59 enabling Smart Link flush message send, 116 configuring RPR station name, 59 enabling trap, 200 configuring RPR timer, 62 ignoring standby MPU version check, 5...
Page 255 Rapid Ring Protection Protocol. Use RRPP configuring basic function, 57 real MAC to virtual IP mapping (VRRP), 144, 152 configuring default ringlet selection, 61 receive control VLAN (Smart Link), 112 configuring fairness algorithm, 61 recovering RRPP ring, 73 configuring hold off timer, 63 remote configuring keepalive timer, 63 loopback (Ethernet OAM), 7...
Page 256 RPR station, 55 load balancing, 74 RPR logical interface view maintaining, 84 binding RPR logical interface with RPR major-fault RRPPDU, 72 physical port, 58 master node type, 71 RPR physical port networking, 74 RPR station, 55 node types, 71 RPR physical port view polling mechanism, 73 binding RPR logical interface with RPR primary master port, 71...
Page 257 resetting DLDP state in port/port group single group configuration, 118 view, 42 terminology, 112 resetting DLDP state in system view, 41 toplogy change mechanism, 113 send advertisement packet interval transmit control VLAN, 112 (DLDP), 39 software (ignoring standby MPU version check), 5 shutdown specifying auto shutdown of unidirectional link...
Page 258 high availability active switchover RRPP configuration, 70, 78, 84 configuration, 5, 5 RRPP domain, 70 high availability standby switchover RRPP dual homed rings configuration, 92 configuration, 5, 5 RRPP intersecting rings, 75 performing active switchover manually, 6 RRPP intersecting rings configuration, 87 performing standby switchover manually, 6 RRPP load balanced intersecting rings protection switchover technologies (high...
Page 259 Track check (standby MPU), 5 associating with BFD, 204 virtual configuration, 202, 202 IP address (MAC address type mapping), 144, 152 tracking IP addressconfiguration (IPv6 VRRP), 153 VRRP, 136 MAC address assignment, 138 traffic MAC to virtual IP mapping (VRRP), 144, 152 RRPP load balancing, 74 router redundancy protocol.
Page 260 IPv4 interface tracking configuration, 159 IPv4 single group configuration, 157 IPv6 configuration, 151 load-balancing mode, 138 load-balancing operating mode, 132 packet format, 134 packet type, 142 principles, 136 specifying MAC address type mapped to virtual IPv4 address, 144 specifying MAC address type mapped to virtual IPv6 address, 152 specifying VRRP control VLAN, 144 standard mode, 133...

HPE FlexNetwork HSR6800 series Configuration Manual

High Availability Overview

Configuring Active and Standby Switchover

Configuring Ethernet OAM

Configuring CFD

Configuring DLDP

Configuring RPR

Configuring RRPP

Configuring Smart Link

Configuring VRRP

Configuring BFD

Configuring Track

Document Conventions and Icons

Support and Other Resources

Index

Quick Links

Troubleshooting

Related Manuals for HPE FlexNetwork HSR6800 series

Summary of Contents for HPE FlexNetwork HSR6800 series

Table of Contents