HP HSR6800 Routers High Availability Configuration Guide Part number: 5998-4497 Software version: HSR6800-CMW520-R3303P05 Document version: 6PW105-20140507
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents High availability overview··········································································································································· 1 Availability requirements ·················································································································································· 1 Availability evaluation ········································································································································
Configuring MEPs ·················································································································································· 24 Configuring MIP generation rules ························································································································ 25 Configuring CFD functions ············································································································································ 25 Configuration prer
Configuring the ATD timer···································································································································· 65 Configuring the hold off timer ······························································································································ 65 Configuring the keepalive timer··························································································································· 65 Configuring the topology stabili
Enabling the receiving of flush messages ········································································································· 122 Displaying and maintaining Smart Link ····················································································································· 122 Smart Link configuration examples ···························································································································· 122 Single smart link group configuration
Configuration procedure ···································································································································· 206 Enabling trap ································································································································································ 207 Displaying and maintaining BFD································································································································ 208 Configur
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. • Speeding up fault recovery. • Reducing impact of faults on services.
MTTR = fault detection time + hardware replacement time + system initialization time + link recovery time + routing time + forwarding recovery time. A smaller value of each item means a smaller MTTR and a higher availability. 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.
Technology Introduction Reference Track The Track module implements collaboration between different modules. The collaboration involves three sets of modules: application, Track, and detection. These modules collaborate with one another through collaboration entries. The detection modules trigger the application modules to perform certain operations through the Track module.
Technology Introduction Reference RRPP 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. "Configuring RRPP" FRR FRR provides a quick per-link or per-node protection on an LSP. Once a link or node fails on a path, FRR reroutes the path to a new link or node to bypass the failed link or node.
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. The standby MPU keeps its configuration the same as the active MPU through the synchronization function.
Step Command Remarks 1. Enter system view. system-view N/A 2. Ignore version check of the standby MPU. ha slave-ignore-version-check By default, version check of the standby MPU is enabled. 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.
Displaying and maintaining active and standby switchover Task Command Remarks Display the switchover state of MPUs (in standalone mode). display switchover state [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display the switchover state of MPUs (in IRF mode) display switchover state [ chassis chassis-number slot slot-number ] [ | { begin | exclude | include } regular-expression ] Available in any view.
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. You can use it to monitor the status of the point-to-point link between two directly connected devices.
Field Source addr Type Subtype Description Source MAC address of the Ethernet OAMPDU. It is the bridge MAC address of the sending side and is a unicast MAC address. Type of the encapsulated protocol in the Ethernet OAMPDU. The value is 0x8809. The specific protocol being encapsulated in the Ethernet OAMPDU. The value is 0x03. Flags Status information of an Ethernet OAM entity. Code Type of the Ethernet OAMPDU.
Table 6 Active Ethernet OAM mode and passive Ethernet OAM mode Item Active Ethernet OAM mode Passive Ethernet OAM mode Initiating OAM Discovery Available Unavailable Responding to OAM Discovery Available Available Transmitting Information OAMPDUs Available Available Transmitting Event Notification OAMPDUs Available Available Transmitting Information OAMPDUs without any TLV Available Available Transmitting Loopback Control OAMPDUs Available Unavailable Responding to Loopback Control OAMP
Remote fault detection Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the flag field defined in Information OAMPDUs allows an Ethernet OAM entity to send error information (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.
Task Remarks Configuring Ethernet OAM remote loopback Configuring errored frame seconds event detection Optional Enabling Ethernet OAM remote loopback in user view Optional Enabling Ethernet OAM remote loopback in system view Optional Enabling Ethernet OAM remote loopback in Ethernet port view Optional Rejecting the Ethernet OAM remote loopback request from a remote port Optional Configuring basic Ethernet OAM functions To set up an Ethernet OAM connection between two Ethernet OAM entities, you
Step Command Remarks N/A 1. Enter system view. system-view 2. Configure the Ethernet OAM handshake packet transmission interval. oam timer hello interval Configure the Ethernet OAM connection timeout timer. oam timer keepalive interval 3. Optional. 1000 milliseconds by default. Optional. 5000 milliseconds by default.
Configuring errored frame period event detection An errored frame period event occurs if the number of frame errors in a specific number of received frames exceeds the predefined threshold. To configure errored frame period event detection: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the errored frame period event detection period. oam errored-frame-period period period-value Optional. Configure the errored frame period event triggering threshold.
You can enable Ethernet OAM remote loopback on a specific port in user view, system view, or Layer 2 Ethernet port view. The configuration effects are the same. Configuration guidelines • Ethernet OAM remote loopback is available only after the Ethernet OAM connection is established. It can be performed only by Ethernet OAM entities operating in active Ethernet OAM mode. • Remote loopback is available only on full-duplex links that support remote loopback at both ends.
Step 3. Enable Ethernet OAM remote loopback on the port. Command Remarks oam loopback Disabled by default. Rejecting the Ethernet OAM remote loopback request from a remote port The Ethernet OAM remote loopback function impacts other services. To solve this problem, you can disable a port from being controlled by the Loopback Control OAMPDUs sent by a remote port. The local port then rejects the Ethernet OAM remote loopback request from the remote port.
Task Command Remarks Clear statistics on Ethernet OAM packets and Ethernet OAM link error events. reset oam [ interface interface-type interface-number ] Available in user view. Ethernet OAM configuration example Network requirements On the network shown in Figure 2, perform the following operations: • Enable Ethernet OAM on Router A and Router B to auto-detect link errors between the two devices.
# Display the Ethernet OAM configuration on Router A.
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. An MD is identified by its MD name.
An MA serves a VLAN. Packets sent by the MPs in an MA carry the relevant VLAN tag. An MP can receive packets sent by other MPs in the same MA. The level of an MA equals the level of the MD that the MA belongs to. 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). • MEP MEPs define the boundary of the MA. Each MEP is identified by a MEP ID.
configured on the ports of Router A through Router F. Port 1 of Router B is configured with the following MPs—a level 5 MIP, a level 3 inward-facing MEP, a level 2 inward-facing MEP, and a level 0 outward-facing MEP.
LB Similar to ping at the IP layer, loopback verifies the connectivity between a source device and a target device. To implement this function, the source MEP sends loopback messages (LBMs) to the target MEP. Depending on whether the source MEP can receive a loopback reply message (LBR) from the target MEP, the link state between the two can be verified. LBM frames and LBR frames are unicast frames. LT Linktrace is similar to traceroute. It identifies the path between the source MEP and the target MEP.
The port is configured as a MIP or inward-facing MEP, which can still receive and send CFD messages except CCM messages. • For more information about the spanning tree feature, see Layer 2—LAN Switching Configuration Guide. Configuring basic CFD settings Enabling CFD Step Command Remarks 1. Enter system view. system-view N/A 2. Enable CFD. cfd enable CFD is disabled by default. Configuring the CFD protocol version Three CFD protocol versions are available: IEEE 802.1ag draft5.
Configuring a service instance with the MD name To create a service instance, create the MD and MA for the service instance first. To configure a service instance: Step Command Remarks 1. Enter system view. system-view N/A 2. Create an MD. cfd md md-name level level-value Not created by default. 3. Create an MA. cfd ma ma-name md md-name vlan vlan-id Not created by default. 4. Create a service instance. cfd service-instance instance-id md md-name ma ma-name Not created by default.
Step Enable the MEP. 5. Command Remarks cfd mep service-instance instance-id mep mep-id enable Disabled by default. 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 Remarks 1. Enter system view. system-view N/A 2.
The interval field value in the CCM message The interval between CCM messages The timeout time of the remote MEP 5 10 second 35 seconds 6 60 seconds 210 seconds 7 600 seconds 2100 seconds 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.
• To implement the first function, the source MEP first sends LTM messages to the target MEP. Based on the LTR messages in response to the LTM messages, the path between the two MEPs can be identified. • In the latter case, after LT messages automatic sending is enabled, if the source MEP fails to receive the CCM frames from the target MEP within 3.5 times the transmission interval, the link between the two is considered faulty.
Task Command Remarks Display LTR information received by a MEP. display cfd linktrace-reply [ service-instance instance-id [ mep mep-id ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display the information of a remote MEP. display cfd remote-mep service-instance instance-id mep mep-id [ | { begin | exclude | include } regular-expression ] Available in any view. Display the content of the LTR messages received as responses to the automatically sent LTMs.
Figure 6 Network diagram Configuration procedure 1. Configure a VLAN and assign ports to it: On each device shown in Figure 6, create VLAN 100 and assign all ports to VLAN 100. 2. Enable CFD: # Enable CFD on Router A. system-view [RouterA] cfd enable Enable CFD on Router B through Router E using the same method. 3. Configure service instances: # 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.
[RouterC] cfd service-instance 2 md MD_B ma MA_B 4. Configure MEPs: # On Router A, configure a MEP list in service instance 1. Create and enable inward-facing MEP 1001 in service instance 1 on GigabitEthernet 3/0/1.
[RouterA-GigabitEthernet3/0/1] quit # On Router B, enable the sending of CCM frames for MEP 2001 in service instance 2 on GigabitEthernet 3/0/3. [RouterB] interface gigabitethernet 3/0/3 [RouterB-GigabitEthernet3/0/3] cfd cc service-instance 2 mep 2001 enable [RouterB-GigabitEthernet3/0/3] quit # On Router D, enable the sending of CCM frames for MEP 4001 in service instance 2 on GigabitEthernet 3/0/1. Enable the sending of CCM frames for MEP 4002 in service instance 1 on GigabitEthernet 3/0/3.
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.
As a data link layer protocol, DLDP cooperates with physical layer protocols to monitor link status. When the auto-negotiation mechanism provided by the physical layer detects physical signals and faults, DLDP performs operations such as identifying peer devices, detecting unidirectional links, and shutting down unreachable ports.
DLDP timer Description Advertisement timer Determines the interval for sending common advertisement packets (default is 5 seconds). Probe timer Determines the interval for sending Probe packets (default is 1 second). By default, a device in the probe state sends one Probe packet every second. The maximum number of Probe packets that can be sent successively is 10. Echo timer This timer is set to 10 seconds.
second. If no Echo packet has been received from the neighbor when the Echo timer expires, the device transits to the Disable state. Table 12 shows the relationship between the DLDP modes and neighbor entry aging.
DLDP authentication mode You can use DLDP authentication to prevent network attacks and illegal detecting. The following DLDP authentication modes are available: Non-authentication: • { { 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.
Table 15 Processing incoming DLDP packets by packet type Packet type Advertisement with RSY tag Processing procedure Retrieves the neighbor information. Normal Advertisement Retrieves the neighbor information. Flush packet Checks whether the local DLDP port state is Disable. Probe Retrieves the neighbor information. If no matching neighbor entry exists, creates the neighbor entry, triggers the Entry timer, and changes the DLDP port state to Probe.
Packet type Processing procedure If yes and the local port is not in Disable state, sets the state of the neighbor to one way, and then checks the state of other neighbors to determine the subsequent action to take: LinkDown packet Checks whether the local port operates in Enhanced mode. • If all the neighbors are in one way state, changes the local DLDP port state to Disable. • If the state of some neighbors is still unknown, takes no action until the state of these neighbors is determined.
Table 17 DLDP neighbor states DLDP neighbor state Description Unknown A neighbor is in this state when it is just detected and is being probed. A neighbor is in this state only when it is being probed. It transits to Two way state or Unidirectional state after the probe operation finishes. Two way A neighbor is in this state after it receives response from its peer. This state indicates the link is a two-way link.
Step 2. Enter Ethernet interface view. Command Remarks interface interface-type interface-number N/A Optional. 3. Set the duplex mode. By default, the duplex mode is auto for Ethernet interfaces. duplex full For more information about command, see Interface Command Reference. Optional. 4. Set the port speed. speed { 10 | 100 | 1000 | 10000 } By default, the port speed is automatically negotiated. For more information about the command, see Interface Command Reference.
Step Command Remarks N/A 1. Enter system view. system-view 2. Set DLDP mode. dldp work-mode { enhance | normal } Optional. Normal by default. Setting the interval to send advertisement packets DLDP detects unidirectional links by sending Advertisement packets. To make sure DLDP can detect unidirectional links promptly before network performance deteriorates, set the advertisement interval appropriate for your network environment.
Setting the port shutdown mode On detecting a unidirectional link, the ports can be shut down in one of the following two modes. • Manual mode—This mode applies to low performance networks, where normal links might be treated as unidirectional links. It protects data traffic transmission against false unidirectional links. In this mode, DLDP only detects unidirectional links but does not automatically shut down unidirectional link ports.
user-defined port shutdown mode. To enable the port to perform DLDP detect again, you can reset the DLDP state of the port by using one of the following methods: • If the port is shut down with the shutdown command manually, run the undo shutdown command on the port. • If DLDP automatically shuts down the port, run the dldp reset command on the port to enable the port to perform DLDP detection again.
Task Command Remarks Display the DLDP configuration of a port. display dldp [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display the statistics on DLDP packets passing through a port. display dldp statistics [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ] Available in any view. Clear the statistics on DLDP packets passing through a port.
system-view [RouterA] dldp enable # Configure GigabitEthernet 3/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port. [RouterA] interface gigabitethernet 3/0/1 [RouterA-GigabitEthernet3/0/1] duplex full [RouterA-GigabitEthernet3/0/1] speed 1000 [RouterA-GigabitEthernet3/0/1] dldp enable [RouterA-GigabitEthernet3/0/1] quit # Configure GigabitEthernet 3/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.
[RouterA] display dldp DLDP global status : enable DLDP interval : 5s DLDP work-mode : enhance DLDP authentication-mode : none DLDP unidirectional-shutdown : auto DLDP delaydown-timer : 1s The number of enabled ports is 2. Interface GigabitEthernet3/0/1 DLDP port state : advertisement DLDP link state : up The neighbor number of the port is 1.
%Jan 18 17:36:20:189 2010 RouterA IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/2 link status is DOWN. %Jan 18 17:36:20:190 2010 RouterA DLDP/3/DLDP_UNIDIRECTION_AUTO: -Slot=2; DLDP detects a unidirectional link on port GigabitEthernet3/0/2. The transceiver has malfunction in the Tx direction or cross-connected links exist between the local device and its neighbor. The shutdown mode is AUTO. DLDP shuts down the port.
Figure 10 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 Ethernet fiber port Router B Tx end Rx end Fiber link Configuration procedure 1. Configure Router A: # Enable DLDP globally. system-view [RouterA] dldp enable # Configure GigabitEthernet 3/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.
# Enable DLDP globally. 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.
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. # Enable system information monitoring on Router A, and enable the display of log and trap information.
[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. [RouterA-GigabitEthernet3/0/2] quit [RouterA] interface gigabitethernet 3/0/1 [RouterA-GigabitEthernet3/0/1] undo shutdown [RouterA-GigabitEthernet3/0/1] %Jan 18 18:22:46:065 2010 RouterA IFNET/3/LINK_UPDOWN: GigabitEthernet3/0/1 link status is UP.
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. The RPR technology delivers these benefits: • Physical layer diversity. • High bandwidth utilization.
ring contains at least one detected edge, it is called "open ring." If it does not contain any detected edges, it is called "closed ring." 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.
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: 1. The source station inserts the frame into the data stream on Ringlet 0 or Ringlet 1. 2. Transit and destination stations copy and transit the frame if the TTL of the frame has not expired. 3.
• 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.
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. • In wrapping mode, traffic that should originally travel from station E to A along Ringlet 0 is directed to Ringlet 1 to reach station A.
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.
{ { For the RPR station to forward traffic, before binding two RPR physical ports with the same RPR logical interface, you must connect their mate ports. You can bind any type of RPR physical ports to an RPR logical interface. However, the RPR physical ports bound to a logical RPR interface must be of the same type.
Task Remarks Configuring the hold off timer Optional Configuring the keepalive timer Optional Configuring the topology stability timer Optional Configuring the TC timers Optional Configuring the TP timers Optional Configuring the WTR timer Optional Testing connectivity between RPR stations Optional Configuring basic RPR functions Configuring an RPR physical port To configure an RPRPOS interface: Step Command Remarks 1. Enter system view. system-view N/A 2.
Creating and configuring an RPR logical interface Step Command Remarks 1. Enter system view. system-view N/A 2. Create an 3 RPR logical interface and enter RPR logical interface view. interface rpr interface-number N/A Optional. 3. Configure the description for the interface. description text 4. Configure the MTU of the interface. mtu size By default, the description of an RPR interface is interface-name Interface. Optional. 1500 bytes by default. Optional. 5.
Binding RPR physical ports with an RPR logical interface in RPR physical port view Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RPR physical port view. interface rprpos interface-number N/A 3. Bind the RPR logical interface with the RPR physical port. rpr bind { rpr interface-number } { ringlet0 | ringlet1 } By default, no RPR physical ports are bound with an RPR logical interface.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RPR logical interface view. interface rpr interface-number N/A 3. Configure the protection mode. rpr protect-mode { steer | wrap } By default, the steering mode applies. Configuring RPR protection reversion mode The following protection reversion modes are available: revertive and non-revertive. • Revertive mode—A station resumes the idle protection state once the WTR timer expires.
• Dynamic ringlet selection table—Built dynamically based on the topology database, also known as "shortest path ringlet selection table." • Default ringlet selection table—Specifies the default ringlet for delivering frames. • Overall ringlet selection table—Created from the above three tables. In the case of closed ringlets, static ringlet selection table has the highest priority.
Configure the RPR fairness algorithm By configuring the RPR fairness algorithm, you can better guarantee the transmission quality over RPR rings. Configuring reserved bandwidth or rate limiting RPR traffic includes three classes: class A, class B, and class C, with decreasing priorities. • Class A is further divided into two subclasses: A0 and A1. RPR can reserve bandwidth for subclass A0. When congestion occurs, the unused reserved bandwidth cannot be used by lower priority traffic.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RPR logical interface view. interface rpr interface-number N/A 3. Configure the weight of the station. rpr weight { ringlet0 | ringlet1 } value By default, the weight is 20=1. Configuring RPR timers Configuring the ATD timer The ATD timer defines the interval at which attribute discovery frames are sent. To configure the ATD timer: Step Command Remarks 1. Enter system view. system-view N/A 2.
Step Command Remarks 2. Enter RPR logical interface view. interface rpr interface-number N/A 3. Set the keepalive timer. rpr timer keepalive keepalive-value 3 milliseconds by default. Configuring the topology stability timer When a station detects a topology change on the ring, it starts the topology stability timer and begins to collect topology information to update its topology database. After the timer expires, the station checks the validity of received topology information.
Step Command Remarks 1. Enter system view. system-view N/A 2. Enter RPR logical interface view. interface rpr interface-number N/A 3. Set the TP fast timer. rpr timer tp-fast tp-fast-value 10 milliseconds by default. 4. Set the TP slow timer. rpr timer tp-slow tp-slow-value 100 milliseconds by default. Configuring the WTR timer When a protection switching event occurs on a station due to link failure, the station enters automatic protection state.
Displaying and maintaining RPR Task Command Remarks display interface [ rpr ] [ brief [ down ] ] [ | { begin | exclude | include } regular-expression ] Display information about an RPR logical interface. display interface rpr interface-number [ brief [ description ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display RPR logical interface-to-physical port bindings.
Task Command Remarks Display VRRP standby group information of RPR. display rpr vrrp-info [ rpr interface-number ] [ | { begin | exclude | include } regular-expression ] Available in any view. Clear the statistics about protection events on the RPR station. reset rpr protection statistics [ rpr interface-number ] Available in user view. Clear the statistics of the specified RPR physical ports. reset counters interface [ rprpos [ interface-number ] ] Available in user view.
2. Verify the configuration: # Display RPR interface binding information on Station A. [StationA] display rpr bind-info Bind information on interface: RPR1 PHY-Interface Ringlet-ID Role Mate-Port --------------------------------------------------RPRPOS1/1 Ringlet0 Master Up RPRPOS1/2 Ringlet1 Slave Up # Display the RPR topology summary on Station A.
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. Change the protection mode of the ring to wrapping. Configure a static ringlet selection entry to allow frames from Station A to Station B to travel Ringlet 1 when no edge occurs on the RPR ring (that is, the ring remains closed). Figure 16 Network diagram Configuration procedure 1.
# 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 Total entrie(s): 1 Valid --- # Display the information about the overall ring selection table on Station A.
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.
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. A ring can be in one of the following states: • Health state—All physical links on the Ethernet ring are connected.
Primary port and secondary port Each master node or transit node has two ports connected to an RRPP ring, one serving as the primary port and the other serving as the secondary port. You can determine the role of a port. 1. In terms of functionality, the primary port and the secondary port of a master node have the following differences: { { { 2. The primary port and the secondary port are designed to play the role of sending and receiving loop-detect packets, respectively.
Type Description Link-Down The transit node, the edge node or the assistant-edge node initiates Link-Down packets to notify the master node of the disappearance of a ring in case of a link failure. Common-Flush-FDB The master node initiates Common-Flush-FDB (FDB stands for Forwarding Database) packets to instruct the transit nodes to update their own MAC entries and ARP/ND entries when an RRPP ring transits to Disconnect state.
Link down alarm mechanism The transit node, the edge node or the assistant-edge node sends Link-Down packets to the master node immediately when they find any of its own ports belonging to an RRPP domain is down. Upon the receipt of a Link-Down packet, the master node releases the secondary port from blocking data VLANs and sending Common-Flush-FDB packet to instruct all the transit nodes, the edge nodes and the assistant-edge nodes to update their own MAC entries and ARP/ND entries.
To reduce Edge-Hello traffic, you can assign Ring 2 and Ring 3 to an RRPP ring group configured on the edge node Device B, and assign Ring 2 and Ring 3 to an RRPP ring group configured on Device C. After such configurations, if all rings are activated, only Ring 2 on Device B sends Edge-Hello packets. Typical RRPP networking Single ring As shown in Figure 18, only a single ring exists in the network topology. You only need to define an RRPP domain.
Intersecting rings As shown in Figure 20, two or more rings exist in the network topology and two 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. 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.
1. Such configurations enable the ring to block different links based on VLANs and achieve single-ring load balancing. Figure 22 Schematic diagram for a single-ring load balancing network Device A Device B Ring 1 Domain 1 Device D Domain 2 Device C Intersecting-ring load balancing In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains. As shown in Figure 23, Ring 1 is the primary ring and Ring 2 is the subring in both Domain 1 and Domain 2.
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. Before configuring RRPP, you must physically construct a ring-shaped Ethernet topology.
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: • When you configure existing VLANs as primary control VLANs or secondary control VLANs, the system prompts errors. • To ensure proper forwarding of RRPPDUs, do not enable 802.1Q in 802.
Step Command Remarks Not required if the device is operating in PVST mode. 2. Enter MST region view. stp region-configuration For more information about the command, see Layer 2—LAN Switching Command Reference. Optional. Use either method. 3. Configure the VLAN-to-instance mapping table. • Method 1: All VLANs in an MST region are mapped to MSTI 0 (the CIST) by default. • Method 2: Not required if the device is operating in PVST mode.
Configuring RRPP ports Perform this configuration on each node's ports intended for accessing RRPP rings. Follow these guidelines when you configure RRPP ports: • 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.
Specifying a transit node Perform this configuration on a device to be configured as a transit node. To specify a transit node: Step Command 1. Enter system view. system-view 2. Enter RRPP domain view. rrpp domain domain-id 3. Specify the current device as a transit node of the ring, and specify the primary port and the secondary port.
Activating an RRPP domain To activate an RRPP domain on the current device, enable the RRPP protocol and RRPP rings for the RRPP domain on the current device. Perform this operation on all nodes in the RRPP domain. To prevent Hello packets of subrings from being looped on the primary ring, enable the primary ring on its master node before enabling the subrings on their separate master nodes.
Follow these guidelines when you configure an RRPP ring group: • You can assign a subring to only one RRPP ring group. The RRPP ring group configured on the edge node and that configured on the assistant-edge node must contain the same subrings. Otherwise, the RRPP ring group cannot operate correctly. • Make sure the subrings in an RRPP ring group share the same edge node and assistant-edge node, and the edge node and the assistant edge node have the same SRPTs.
RRPP configuration examples Single ring configuration example Networking requirements As shown in Figure 24, • Router A, Router B, Router C, and Router D 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. • Router A, Router B, Router C, and Router D form primary ring 1.
[RouterA-GigabitEthernet3/0/1] port link-type trunk [RouterA-GigabitEthernet3/0/1] port trunk permit vlan 1 to 30 [RouterA-GigabitEthernet3/0/1] quit [RouterA] interface gigabitethernet 3/0/2 [RouterA-GigabitEthernet3/0/2] link-delay 0 [RouterA-GigabitEthernet3/0/2] undo stp enable [RouterA-GigabitEthernet3/0/2] port link-type trunk [RouterA-GigabitEthernet3/0/2] port trunk permit vlan 1 to 30 [RouterA-GigabitEthernet3/0/2] quit # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRP
# 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. [RouterB] rrpp domain 1 [RouterB-rrpp-domain1] control-vlan 4092 [RouterB-rrpp-domain1] protected-vlan reference-instance 1 # 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.
Figure 25 Network diagram Configuration procedure 1. Configure Router A: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. 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 GigabitEthernet 3/0/2.
[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 2. Configure Router B: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration.
[RouterB-rrpp-domain1] ring 2 node-mode edge edge-port gigabitethernet 3/0/3 [RouterB-rrpp-domain1] ring 2 enable [RouterB-rrpp-domain1] quit # Enable RRPP. [RouterB] rrpp enable 3. Configure Router C: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration.
[RouterC-rrpp-domain1] ring 2 node-mode assistant-edge edge-port gigabitethernet 3/0/3 [RouterC-rrpp-domain1] ring 2 enable [RouterC-rrpp-domain1] quit # Enable RRPP. [RouterC] rrpp enable 4. Configure Router D: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration.
[RouterE] vlan 1 to 30 [RouterE] stp region-configuration [RouterE-mst-region] instance 1 vlan 1 to 30 [RouterE-mst-region] active region-configuration [RouterE-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.
• Specify Router A as the master node of primary ring 1, GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port. Specify Router E as the master node of subring 2, GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port. Specify Router F as the master node of subring 3, GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port.
# 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.
2. Configure Router B: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. system-view [RouterB] vlan 1 to 30 [RouterB] stp region-configuration [RouterB-mst-region] instance 1 vlan 1 to 30 [RouterB-mst-region] active region-configuration [RouterB-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1 through GigabitEthernet 3/0/4.
[RouterB-rrpp-domain1] ring 2 node-mode assistant-edge edge-port gigabitethernet 3/0/4 [RouterB-rrpp-domain1] ring 2 enable # Configure Router B as the assistant-edge node of subring 3, with GigabitEthernet 3/0/3 as the edge port, and enable subring 3. [RouterB-rrpp-domain1] ring 3 node-mode assistant-edge edge-port gigabitethernet 3/0/3 [RouterB-rrpp-domain1] ring 3 enable [RouterB-rrpp-domain1] quit # Enable RRPP. [RouterB] rrpp enable 3.
# 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. [RouterC] rrpp domain 1 [RouterC-rrpp-domain1] control-vlan 4092 [RouterC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Router C 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.
[RouterD-GigabitEthernet3/0/3] link-delay 0 [RouterD-GigabitEthernet3/0/3] undo stp enable [RouterD-GigabitEthernet3/0/3] port link-type trunk [RouterD-GigabitEthernet3/0/3] port trunk permit vlan 1 to 30 [RouterD-GigabitEthernet3/0/3] quit [RouterD] interface gigabitethernet 3/0/4 [RouterD-GigabitEthernet3/0/4] link-delay 0 [RouterD-GigabitEthernet3/0/4] undo stp enable [RouterD-GigabitEthernet3/0/4] port link-type trunk [RouterD-GigabitEthernet3/0/4] port trunk permit vlan 1 to 30 [RouterD-GigabitEthernet
[RouterE-GigabitEthernet3/0/1] port link-type trunk [RouterE-GigabitEthernet3/0/1] port trunk permit vlan 1 to 30 [RouterE-GigabitEthernet3/0/1] quit [RouterE] interface gigabitethernet 3/0/2 [RouterE-GigabitEthernet3/0/2] link-delay 0 [RouterE-GigabitEthernet3/0/2] undo stp enable [RouterE-GigabitEthernet3/0/2] port link-type trunk [RouterE-GigabitEthernet3/0/2] port trunk permit vlan 1 to 30 [RouterE-GigabitEthernet3/0/2] quit # Create RRPP domain 1, configure VLAN 4092 as the primary control VLAN of RRP
# 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. [RouterF] rrpp domain 1 [RouterF-rrpp-domain1] control-vlan 4092 [RouterF-rrpp-domain1] protected-vlan reference-instance 1 # Configure Router F as the master node of subring 3, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable subring 3.
[RouterG-rrpp-domain1] quit # Enable RRPP. [RouterG] rrpp enable 8. Configure Router H: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. system-view [RouterH] vlan 1 to 30 [RouterH] stp region-configuration [RouterH-mst-region] instance 1 vlan 1 to 30 [RouterH-mst-region] active region-configuration [RouterH-mst-region] quit # Set the physical state change suppression interval to 0 seconds on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2.
Load balanced intersecting-ring configuration example Networking requirements As shown in Figure 27, • Router A, Router B, Router C, Router D, and Router F form RRPP domain 1, and VLAN 100 is the primary control VLAN of the RRPP domain. Router A is the master node of the primary ring, Ring 1. Router D is the transit node of Ring 1. Router F is the master node of the subring Ring 3. Router C is the edge node of the subring Ring 3. Router B is the assistant-edge node of the subring Ring 3.
[RouterA-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 ports. Remove the two ports from VLAN 1, assign them to VLANs 11 and 12, and configure VLAN 11 as their default VLAN.
# Create VLANs 11 and 12, map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2, and activate MST region configuration.
[RouterB-GigabitEthernet3/0/4] port trunk permit vlan 11 [RouterB-GigabitEthernet3/0/4] port trunk pvid vlan 11 [RouterB-GigabitEthernet3/0/4] 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.
# 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 ports. Remove the two ports from VLAN 1, assign them to VLANs 11 and 12, and configure VLAN 11 as their default VLAN.
# Configure Router C as the transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port, and enable ring 1. [RouterC-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 3/0/1 secondary-port gigabitethernet 3/0/2 level 0 [RouterC-rrpp-domain1] ring 1 enable # Configure Router C as the edge node of subring 3 in RRPP domain 1, with GigabitEthernet 3/0/4 as the edge port, and enable subring 3.
[RouterD-GigabitEthernet3/0/1] port trunk pvid vlan 11 [RouterD-GigabitEthernet3/0/1] quit [RouterD] interface gigabitethernet 3/0/2 [RouterD-GigabitEthernet3/0/2] link-delay 0 [RouterD-GigabitEthernet3/0/2] undo stp enable [RouterD-GigabitEthernet3/0/2] port link-type trunk [RouterD-GigabitEthernet3/0/2] undo port trunk permit vlan 1 [RouterD-GigabitEthernet3/0/2] port trunk permit vlan 11 12 [RouterD-GigabitEthernet3/0/2] port trunk pvid vlan 11 [RouterD-GigabitEthernet3/0/2] quit # Create RRPP domain 1,
[RouterE] interface gigabitethernet 3/0/1 [RouterE-GigabitEthernet3/0/1] link-delay 0 [RouterE-GigabitEthernet3/0/1] undo stp enable [RouterE-GigabitEthernet3/0/1] port link-type trunk [RouterE-GigabitEthernet3/0/1] undo port trunk permit vlan 1 [RouterE-GigabitEthernet3/0/1] port trunk permit vlan 12 [RouterE-GigabitEthernet3/0/1] port trunk pvid vlan 12 [RouterE-GigabitEthernet3/0/1] quit [RouterE] interface gigabitethernet 3/0/2 [RouterE-GigabitEthernet3/0/2] link-delay 0 [RouterE-GigabitEthernet3/0/2] u
[RouterF-GigabitEthernet3/0/1] port trunk pvid vlan 11 [RouterF-GigabitEthernet3/0/1] quit [RouterF] interface gigabitethernet 3/0/2 [RouterF-GigabitEthernet3/0/2] link-delay 0 [RouterF-GigabitEthernet3/0/2] undo stp enable [RouterF-GigabitEthernet3/0/2] port link-type trunk [RouterF-GigabitEthernet3/0/2] undo port trunk permit vlan 1 [RouterF-GigabitEthernet3/0/2] port trunk permit vlan 11 [RouterF-GigabitEthernet3/0/2] port trunk pvid vlan 11 [RouterF-GigabitEthernet3/0/2] quit # Create RRPP domain 1, co
• Some ports are abnormal. • Use the display rrpp brief command to check whether RRPP is enabled for all nodes. If not, use the rrpp enable command and the ring enable command to enable RRPP and RRPP rings for all nodes. • Use the display rrpp brief command to check whether the domain ID and primary control VLAN ID are the same for all nodes. If not, set the same domain ID and primary control VLAN ID for the nodes.
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 28. 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 Rapid Ring Protection Protocol (RRPP).
Smart Link is a feature developed to address the slow convergence issue with STP. It provides link redundancy as well as fast convergence in a dual uplink network, allowing the backup link to take over quickly when the primary link fails. Smart Link has the following features: • Dedicated to dual uplink networks. • Subsecond convergence. • Easy to configure. Terminology Smart link group A smart link group consists of only two member ports: the primary and the secondary ports.
How Smart Link works Link backup mechanism As shown in Figure 28, the link on GigabitEthernet 3/0/1 of Router C is the primary link, and the link on GigabitEthernet 3/0/2 of Router C is the secondary link. Typically, GigabitEthernet 3/0/1 is in forwarding state, and GigabitEthernet 3/0/2 is in standby state. When the primary link fails, GigabitEthernet 3/0/2 takes over to forward traffic and GigabitEthernet 3/0/1 is blocked and placed in standby state.
Smart Link collaboration mechanisms When faults such as unidirectional links, misconnected fibers, or packet loss occur on intermediate devices or network paths, Smart Link does not sense this on its own. Also, it cannot sense when faults are cleared. To check the link status, Smart Link ports must use link detection protocols. When a fault is detected or cleared, the link detection protocols inform Smart Link to switch over the links.
NOTE: A loop might occur on the network during the time when the spanning tree feature is disabled but Smart Link has not yet taken effect on a port. Configuring protected VLANs for a smart link group You can configure protected VLANs for a smart link group by referencing MSTIs. Before configuring the protected VLANs, configure the mappings between MSTIs and the VLANs to be protected (a device working in PVST mode automatically maps VLANs to MSTIs).
Configuring member ports for a smart link group You can configure member ports for a smart link group either in smart link group view or in interface view. The configurations made in these two views have the same effect. In smart link group view To configure member ports for a smart link group in smart link group view: Step Command 1. Enter system view. system-view 2. Create a smart link group and enter smart link group view. smart-link group group-id 3.
• Make sure that the configured control VLAN already exists, and assign the smart link group member ports to the control VLAN. • The control VLAN of a smart link group should also be one of its protected VLANs. Do not remove the control VLAN. Otherwise, flush messages cannot be sent correctly. To enable the sending of flush messages: Step Command Remarks 1. Enter system view. system-view N/A 2. Create a smart link group and enter smart link group view.
Enabling the receiving of flush messages You do not need to enable all ports on the associated devices to receive flush messages sent from the transmit control VLAN, only those on the primary and secondary links between the Smart Link device and the destination device. Follow these guidelines when you enable the receiving of flush messages: • Configure all the control VLANs to receive flush messages.
• Router C and Router D are Smart Link devices. Router A, Router B, and Router E are associated devices. Traffic of VLANs 1 through 30 on Router C and Router D are dually uplinked to Router A. • Configure Smart Link on Router C and Router D for dual uplink backup. Figure 29 Network diagram Configuration procedure 1. Configure Router C: # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration.
# Configure GigabitEthernet 3/0/1 as the primary port and GigabitEthernet 3/0/2 as the secondary port for smart link group 1. [RouterC-smlk-group1] port gigabitethernet3/0/1 master [RouterC-smlk-group1] port gigabitethernet3/0/2 slave # 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.
# Enable flush message sending in smart link group 1, and configure VLAN 20 as the transmit control VLAN. [RouterD-smlk-group1] flush enable control-vlan 20 [RouterD-smlk-group1] quit # Bring up GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 again. [RouterD] interface gigabitethernet 3/0/1 [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 3.
[RouterE-GigabitEthernet3/0/1] port link-type trunk [RouterE-GigabitEthernet3/0/1] port trunk permit vlan 1 to 30 [RouterE-GigabitEthernet3/0/1] smart-link flush enable control-vlan 10 20 [RouterE-GigabitEthernet3/0/1] quit # 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.
Preemption delay: 1(s) Control VLAN: 1 Protected VLAN: Reference Instance 1 Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------GigabitEthernet3/0/1 MASTER ACTVIE 5 16:37:20 2010/02/21 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.
[RouterC] stp region-configuration [RouterC-mst-region] instance 1 vlan 1 to 100 [RouterC-mst-region] instance 2 vlan 101 to 200 [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 on them, configure them as trunk ports, and assign them to VLAN 1 through VLAN 200.
[RouterC-GigabitEthernet3/0/1] undo shutdown [RouterC-GigabitEthernet3/0/1] quit [RouterC] interface gigabitethernet 3/0/2 [RouterC-GigabitEthernet3/0/2] undo shutdown [RouterC-GigabitEthernet3/0/2] quit 2. Configure Router B: # Create VLAN 1 through VLAN 200. system-view [RouterB] vlan 1 to 200 # 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.
4. Configure Router A: # Create VLAN 1 through VLAN 200. system-view [RouterA] vlan 1 to 200 # Configure GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 as trunk ports, assign them to VLANs 1 through 200, enable flush message receiving, and configure VLAN 10 and VLAN 110 as the receive control VLANs on the ports.
# Display the flush messages received on Router B.
# Configure GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2 as trunk ports and assign them to VLANs 1 through 200. Enable flush message receiving and configure VLAN 10 and VLAN 110 as the receive control VLANs on GigabitEthernet 3/0/1 and GigabitEthernet 3/0/2.
[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 # 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. Configure VLAN 10 and VLAN 110 as the receive control VLANs.
# Enable role preemption in smart link group 1, enable flush message sending, and configure VLAN 10 as the transmit control VLAN. [RouterC-smlk-group1] preemption mode role [RouterC-smlk-group1] flush enable control-vlan 10 [RouterC-smlk-group1] quit # Create smart link group 2, and configure all VLANs mapped to MSTI 2 as the protected VLANs for smart link group 2.
[RouterC] interface gigabitethernet 3/0/1 [RouterC-GigabitEthernet3/0/1] port smart-link group 1 track cfd cc [RouterC-GigabitEthernet3/0/1] undo shutdown [RouterC-GigabitEthernet3/0/1] quit # Configure the collaboration between the primary port GigabitEthernet 3/0/2 of smart link group 2 and the CC function of CFD, and bring up the port.
Smart link group 2 information: Device ID: 000f-e23d-5af0 Preemption mode: ROLE Preemption delay: 1(s) Control VLAN: 110 Protected VLAN: Reference Instance 2 Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------GigabitEthernet3/0/2 MASTER ACTVIE 5 16:37:20 2010/02/21 GigabitEthernet3/0/1 SLAVE STANDBY 1 17:45:20 2010/02/21 The output shows that primary port GigabitEthernet 3/0/1 of smart link group 1 fails, and secondary port
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 32, you can typically configure a default route with the gateway as the next hop for every host on a LAN.
• Load balancing mode—Extends the standard mode and realizes load balancing. For more information, see "VRRP load balancing 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.
VRRP priority is in the range of 0 to 255, and the greater the number, the higher the priority. Priorities 1 to 254 are configurable. Priority 0 is reserved for special uses and priority 255 is for the IP address owner. The router acting as the IP address owner in a VRRP group always has the running priority 255 and acts as the master as long as it works correctly. 2. Working mode A router in a VRRP group operates in either of the following modes: { { 3.
VRRP packets are encapsulated in IP packets, with the protocol number being 112. Figure 34 shows the IPv4 VRRPv2 packet format, Figure 35 shows the IPv4 VRRPv2 packet format, and Figure 36 shows the VRRPv3 packet format. Figure 34 IPv4 VRRPv2 packet format Figure 35 IPv6 VRRPv2 packet format 0 3 Version Auth Type 7 Type 15 23 Virtual Rtr ID Priority Adver Int 31 Count IPv6 Addrs Checksum IPv6 address 1 ...
Figure 36 IPv4/IPv6 VRRPv3 packet format A VRRP packet comprises the following fields: • Version—Version number of the protocol, 2 for IPv4 VRRPv2 and 3 for other VRRP versions. • 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.
• If the timer of a backup expires but the backup still does not receive any VRRP advertisement, it considers that the master failed. In this case, the backup considers itself as the master and sends VRRP advertisements to start a new master election. • When multiple routers in a VRRP group declare that they are the master because of inconsistent configuration or network problems, the one with the highest priority becomes the master.
Figure 37 VRRP in master/backup mode Assume that Router A is acting as the master to forward packets to external networks, and Router B and Router C are backups in listening state. When Router A fails, Router B and Router C elect a new master to forward packets for hosts on the LAN. 2. Load sharing More than one VRRP group can be created on an interface of a router to allow the router to be the master of one VRRP group but a backup of another at the same time.
{ VRRP group 1—Router A is the master. Router B and Router C are the backups. { VRRP group 2—Router B is the master. Router A and Router C are the backups. { VRRP group 3—Router C is the master. Router A and Router B are the backups. For load sharing among Router A, Router B, and Router C, hosts on the LAN need to be configured to use VRRP group 1, 2, and 3 as the default gateways, respectively.
Figure 39 Virtual MAC address assignment 2. When an ARP request arrives, the master (Router A) selects a virtual MAC address based on the load balancing algorithm to answer the ARP request. In this example, Router A returns the virtual MAC address of itself in response to the ARP request from Host A. It returns the virtual MAC address of Router B in response to the ARP request from Host B (see Figure 40). Figure 40 Answering ARP requests Network Router A Master Router B Backup Virtual IP: 10.1.1.
Figure 41 Sending packets to different routers for forwarding Virtual forwarder 1. 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. Each VF associates with a virtual MAC address in the VRRP group and forwards packets sent to this virtual MAC address. VFs are created on the routers in a VRRP group, as follows: a.
{ { 3. On a router that does not own the VF, if the weight of the VF is higher than or equal to the lower limit of failure, the priority of the VF is weight/(number of local AVFs +1). If the weight of the VF is lower than the lower limit of failure, the priority of the VF is 0. VF backup The VFs corresponding to a virtual MAC address on different routers in the VRRP group back up each other.
can share traffic load if the VF owner resumes normal operation within this time. When this timer times out, the master stops using the virtual MAC address corresponding to the failed AVF to respond to ARP/ND requests from the hosts. { 5. Timeout Timer—Duration that the new AVF takes over the VF owner. Before this timer times out, all the routers in the VRRP group keep the failed AVF, and the new AVF forwards the packets destined for the virtual MAC address corresponding to the failed AVF.
• If you configure the IPv4/IPv6 VRRPv3 version for an interface, the authentication configuration made for the VRRP group does not take effect. • If you configure the IPv4/IPv6 VRRPv3 version for an interface, the IPv4 VRRPv3 packet advertisement interval cannot exceed 40 seconds. If a greater value is configured, an advertisement interval of 40 seconds is adopted. To configure the IPv4/IPv6 VRRP version: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view.
After the VRRP working mode is specified on a router, all VRRP groups on the router operate in the specified working mode. To configure the VRRP working mode: Step Enter system view. 1. Command Remarks system-view N/A • Configure VRRP to operate in Configure the VRRP working mode. 2. standard mode: undo vrrp mode • Configure VRRP to operate in load balancing mode: vrrp mode load-balance Use either command. By default, VRRP operates in standard mode.
Specifying the VRRP control VLAN With VLAN termination, after a port receiving a VLAN packet, it removes its VLAN tags and then forwards it at Layer 3 or processes it in other ways. VLAN termination includes the following categories: • Unambiguous termination—Terminates VLAN packets from a specified VLAN only. In other words, after receiving a packet from the specific VLAN, a port configured with unambiguous VLAN termination removes its VLAN tag.
For subinterfaces configured with ambiguous QinQ termination, this type of control VLAN should be specified. You need to specify a control VLAN only for a Layer 3 Ethernet subinterface and Layer 3 aggregation subinterface configured with ambiguous VLAN termination. When VRRP operates in load balancing mode, you cannot specify the VRRP control VLAN.
• The VRRP group is automatically created when you specify the first virtual IP address. If you later specify another virtual IP address for the VRRP group, the virtual IP address is added to the virtual IP address list of the VRRP group. • The virtual IP address assigned to the VRRP group must be a legal host address and in the same subnet as the interface IP address. If not, the state of the VRRP group is always initialize and VRRP does not take effect.
• If you configure an interface to be tracked or a track entry to be monitored on a router that is the IP address owner in a VRRP group, the configuration does not take effect. If the router is not the IP address owner in the VRRP group later, the configuration takes effect.
Configuration procedure VRRP operates in load balancing mode. Assume that you have configured the VF tracking function to monitor the track entry and specified the value by which the weight decreases. When the status of the track entry becomes negative, the weight values of all VFs on the router decrease by the specified value. When the status of the track entry becomes positive or invalid, the weight values of all VFs on the router restore their original values.
Configuration prerequisites Before you enable the ARP entry backup function, create a VRRP group and configure a virtual IP address for it. Configuration guidelines • The ARP entry backup function is supported on Layer 3 Ethernet interfaces or subinterfaces. • You can enable the ARP entry backup function when VRRP operates in either standard mode or load balancing mode. Only the master can initiate ARP entry backup.
specify the interface where the VRRP group resides as the source interface for sending VRRP packets, the configuration does not take effect. Configuration procedure To configure VRRP packet attributes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter the specified interface view. interface interface-type interface-number N/A 3. Configure the authentication mode and authentication key when the VRRP groups send and receive VRRP packets.
Displaying and maintaining VRRP for IPv4 Task Command Remarks Display VRRP group status. display vrrp [ verbose ] [ interface interface-type interface-number [ vrid virtual-router-id ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Display VRRP group statistics. display vrrp statistics [ interface interface-type interface-number [ vrid virtual-router-id ] ] [ | { begin | exclude | include } regular-expression ] Available in any view. Clear VRRP group statistics.
from hosts so that the hosts in the internal network can learn the mapping between the IPv6 address and the MAC address. The following types of MAC addresses are available to be mapped to the virtual IPv6 address of a VRRP group: • Virtual MAC address—By default, a virtual MAC address is automatically created for a VRRP group when the VRRP group is created, and the virtual IPv6 address of the VRRP group is mapped to the virtual MAC address.
• When VRRP operates in load balancing mode, the virtual IPv6 address of a VRRP group cannot be the same as the IPv6 address of any interface in the VRRP group. In other words, a VRRP group does not have an IP address owner in load balancing mode. • A VRRP group is removed after you remove all the virtual IPv6 addresses in it. In addition, configurations on that VRRP group do not take effect any longer. • Removal of the VRRP group on the IP address owner causes IP address collision.
synchronous/asynchronous serial interfaces can be PPP only, and the tracked synchronous/asynchronous serial interfaces cannot be added to a virtual template or MP-group. • If the state of a tracked interface changes from down or removed to up, the priority of the router that owns the interface is automatically restored. • If the state of a track entry changes from negative or invalid to positive, the priority of the router where the track entry is configured is automatically restored.
You can configure the VF tracking function when VRRP operates in either standard mode or load balancing mode. However, the VF tracking function is effective only when VRRP operates in load balancing mode. By default, the weight of a VF is 255, and its lower limit of failure is 10. If the weight of a VF owner is higher than or equal to the lower limit of failure, the priority of the VF owner is always 255 and does not change with the weight value.
Configuration procedure To configure VRRP packet attributes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter the specified interface view. interface interface-type interface-number N/A 3. Configure the authentication mode and authentication key when the VRRP groups send or receive VRRP packets. vrrp ipv6 vrid virtual-router-id authentication-mode simple [ cipher ] key Optional. Configure the time interval for the master in the VRRP group to send VRRP advertisement.
Figure 44 Network diagram Configuration procedure 1. Configure Router A: 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 # Configure the priority of Router A in the VRRP group 1 as 110, which is higher than that of Router B (100), so that Router A can become the master.
Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 1 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 5 Auth Type : None Virtual IP : 202.38.160.111 Virtual MAC : 0000-5e00-0101 Master IP : 202.38.160.1 # Display the detailed information about VRRP group 1 on Router B.
# After Router A resumes normal operation, use the display vrrp verbose command to display the detailed information about VRRP group 1 on Router A. [RouterA] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 1 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 5 Auth Type : None Virtual IP : 202.38.160.
Configuration procedure 1. Configure Router A: 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.
Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/2 VRID : 1 Adver Timer : 4 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 5 Auth Type : Simple Key : hello Virtual IP : 202.38.160.111 Virtual MAC : 0000-5e00-0101 Master IP : 202.38.160.1 VRRP Track Information: Track Interface: GE1/0/1 State : Up Pri Reduced : 30 # Display the detailed information about VRRP group 1 on Router B.
Master IP : 202.38.160.2 VRRP Track Information: Track Interface: GE1/0/1 State : Down Pri Reduced : 30 # If interface GigabitEthernet 1/0/1 on Router A is not available, the detailed information about VRRP group 1 on Router B is displayed.
Configuration procedure 1. Configure Router A: 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.
Auth Type : None Virtual IP : 202.38.160.112 Master IP : 202.38.160.2 # Display the detailed information about the VRRP group on Router B. [RouterB] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 2 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 1 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 0 Auth Type : None Virtual IP : 202.38.160.
• Configure a track entry on Router A, Router B, and Router C to monitor their own GigabitEthernet 1/0/2. When the interface on Router A, Router B, or Router C fails, the weight of the corresponding router decreases so that another router with a higher weight can take over. • Configure track entries on Router C to monitor Router A and Router B. When Router A or Router B fails, Router C immediately takes over the AVF on Router A or Router B.
[RouterA] 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 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. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] vrrp vrid 1 weight track 1 reduced 250 2.
[RouterC-GigabitEthernet1/0/1] vrrp vrid 1 weight track 1 reduced 250 [RouterC-GigabitEthernet1/0/1] quit # Create track entries 2 and 3 to monitor Router A and Router B, respectively. If a track entry becomes negative, it indicates that the corresponding router fails. [RouterC] bfd echo-source-ip 1.2.3.4 [RouterC] track 2 bfd echo interface gigabitethernet 1/0/1 remote ip 10.1.1.2 local ip 10.1.1.4 [RouterC] track 3 bfd echo interface gigabitethernet 1/0/1 remote ip 10.1.1.3 local ip 10.1.1.
Active : local Forwarder 02 State : Listening Virtual MAC : 000f-e2ff-0012 (Learnt) Owner ID : 0000-5e01-1103 Priority : 127 Active : 10.1.1.3 Forwarder 03 State : Listening Virtual MAC : 000f-e2ff-0013 (Learnt) Owner ID : 0000-5e01-1105 Priority : 127 Active : 10.1.1.4 Forwarder Weight Track Information: Track Object : 1 State : Positive # Display the detailed information about VRRP group 1 on Router B.
State : Listening Virtual MAC : 000f-e2ff-0013 (Learnt) Owner ID : 0000-5e01-1105 Priority : 127 Active : 10.1.1.4 Forwarder Weight Track Information: Track Object : 1 State : Positive Weight Reduced : 250 # Display the detailed information about VRRP group 1 on Router C.
Track Object Member IP Track Object Member IP : 2 State : Positive : 10.1.1.2 : 3 State : Positive : 10.1.1.3 The output shows that in VRRP group 1, Router A is the master and Router B and Router C are the backups. Each router has one AVF and two LVFs that act as the backups. # When GigabitEthernet 1/0/2 on Router A fails, use the display vrrp verbose command to display the detailed information about VRRP group 1 on Router A.
[RouterC] display vrrp verbose IPv4 Standby Information: Run Mode : Load Balance Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 1 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 5 Become Master : 4200ms left Auth Type : None Virtual IP : 10.1.1.1 Member IP List : 10.1.1.4 (Local, Backup) 10.1.1.2 (Master) 10.1.1.
initialized state and cannot be used for packet forwarding. The VF corresponding to MAC address 000f-e2ff-0011 on Router C becomes the AVF, and Router C takes over Router A for packet forwarding. # When the timeout timer (about 1800 seconds) expires, display the detailed information about VRRP group 1 on Router C.
[RouterB] display vrrp verbose IPv4 Standby Information: Run Mode : Load Balance Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 1 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 5 Auth Type : None Virtual IP : 10.1.1.1 Member IP List : 10.1.1.3 (Local, Master) 10.1.1.
Forwarder Information: 2 Forwarders 2 Active Config Weight : 255 Running Weight : 255 Forwarder 02 State : Active Virtual MAC : 000f-e2ff-0012 (Take Over) Owner ID : 0000-5e01-1103 Priority : 85 Active : local Redirect Time : 93 secs Time-out Time : 1293 secs 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 : 1 State : Positive Weight Reduced : 250 Forwarder
Figure 48 Network diagram Configuration procedure 1. Configure Router A: 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.
# 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 3. 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. # Display the detailed information about VRRP group 1 on Router A.
VRID : 1 Adver Timer : 100 Admin Status : Up State : Master Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 5 Auth Type : None Virtual IP : FE80::10 Virtual MAC : 0000-5e00-0201 Master IP : FE80::2 1::10 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.
Figure 49 Network diagram Configuration procedure 1. Configure Router A: 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.
[RouterB] ipv6 [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.
Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 5 Become Master : 2200ms left Auth Type : Simple Key : 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.
The output shows that when interface GigabitEthernet 1/0/1 on Router A is not available, the priority of Router A reduces to 80 and it becomes the backup. Router B becomes the master and packets sent from Host A to Host B are forwarded by Router B. 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.
system-view [RouterB] ipv6 [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] ipv6 address fe80::2 link-local [RouterB-GigabitEthernet1/0/1] ipv6 address 1::2 64 # 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.
Total number of virtual routers : 2 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 0 Become Master : 2200ms left Auth Type : None Virtual IP : FE80::10 1::10 Master IP : FE80::1 Interface GigabitEthernet1/0/1 VRID : 2 Adver Timer : 100 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 0 Auth Type : None Virt
Figure 51 Network diagram Configuration procedure 1. Configure Router A: # Configure VRRP to operate in load balancing mode. system-view [RouterA] vrrp mode load-balance # Create VRRP group 1 and configure its virtual IPv6 addresses as FE80::10 and 1::10.
[RouterA] 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 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. [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 weight track 1 reduced 250 2.
# Enable Router C to send RA messages, so that hosts in network segment 1::/64 can learn the default gateway address. [RouterC-GigabitEthernet1/0/1] undo ipv6 nd ra halt [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.
State : Listening Virtual MAC : 000f-e2ff-4013 (Learnt) Owner ID : 0000-5e01-1105 Priority : 127 Active : FE80::3 Forwarder Weight Track Information: Track Object : 1 State : Positive Weight Reduced : 250 # Display the detailed information about VRRP group 1 on Router B.
# Display the detailed information about VRRP group 1 on Router C.
Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 100 Admin Status : Up State : Master Config Pri : 120 Running Pri : 120 Preempt Mode : Yes Delay Time : 5 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 Running Weight : 5 Forwarder 01 State : Initialize Virtual MAC : 000f-e2ff-4011
Become Master : 4200ms left Auth Type : None Virtual IP : FE80::10 1::10 Member IP List : FE80::3 (Local, Backup) 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 Forwarder 02 State : Listening Virtual MAC : 000f-e2ff-4012 (Learnt) Owner ID
Preempt Mode : Yes Become Master : 4200ms left Delay Time Auth Type : None Virtual IP : FE80::10 : 5 1::10 Member IP List : FE80::3 (Local, Backup) 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 : 000f-e2ff-4013 (Owner) Owner ID : 0000-5e01-1105
Forwarder 02 State : Active Virtual MAC : 000f-e2ff-4012 (Owner) Owner ID : 0000-5e01-1103 Priority : 255 Active : local Forwarder 03 State : Listening Virtual MAC : 000f-e2ff-4013 (Learnt) Owner ID : 0000-5e01-1105 Priority : 127 Active : FE80::3 Forwarder Weight Track Information: Track Object : 1 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.
• If the ping fails, check network connectivity. • If the ping succeeds, check that their configurations are consistent in terms of number of virtual IP addresses, virtual IP addresses, advertisement interval, and authentication. Frequent VRRP state transition Symptom Frequent VRRP state transition. Analysis The VRRP advertisement interval is set too short. Solution Increase the interval for sending VRRP advertisements or configure a preemption delay.
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. Hardware detection can quickly detect link failures, but is not supported by all media types.
BFD session establishment Figure 52 BFD session establishment (on OSPF routers) As shown in Figure 52, BFD sessions are established as follows: 1. A protocol sends Hello messages to discover neighbors and establish neighborships. 2. After establishing neighborships, the protocol notifies BFD of the neighbor information, including destination and source addresses. 3. BFD uses the information to establish BFD sessions.
• Single-hop detection—Detects the IP connectivity between two directly connected systems. • Multi-hop detection—Detects any of the paths between two systems. These paths have multiple hops and might be overlapped. • Bidirectional detection—Sends detection packets at two sides of a bidirectional link to detect the bidirectional link status, finding link failures in milliseconds.
echo packets have a similar format as BFD control packets with UDP port number 3785 except that the Desired Min TX Interval and Required Min RX Interval fields are null. Figure 54 illustrates the packet format. Figure 54 BFD packet format • Vers—Protocol version. The protocol version is 1. • 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 0 No Diagnostic.
• Demand (D)—If set, Demand mode is active in the transmitting system. The system would like to operate in Demand mode, knows that the session is up in both directions, and is directing the remote system to stop the periodic transmission of BFD control packets. If clear, Demand mode is not active in the transmitting system. • Reserved (R)—This byte must be set to zero on transmit, and ignored on receipt. • Detect Mult—Detection time multiplier. • Length—Length of the BFD control packet, in bytes.
• RFC 5882, Generic Application of Bidirectional Forwarding Detection (BFD) • RFC 5883, Bidirectional Forwarding Detection (BFD) for Multihop Paths • RFC 5884, Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs) • RFC 5885, Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV) Configuring BFD basic functions The BFD basic function configuration is the basis for configuring BFD for other protocols.
Step Command Remarks Optional. 7. Configure the minimum interval for transmitting BFD control packets. bfd min-transmit-interval value For more information, see the description of the Desired Min TX Interval field in "BFD packet format." The default setting is 400 milliseconds. Optional. 8. Configure the minimum interval for receiving BFD control packets. bfd min-receive-interval value For more information, see the description of the Required Min RX Interval field in "BFD packet format.
To enable BFD trap: Step 1. Enter system view. Command Remarks system-view N/A Optional. Enabled by default. 2. Enable BFD trap. snmp-agent trap enable bfd For more information about the command, see the snmp-agent trap enable command in Network Management and Monitoring Command Reference. Displaying and maintaining BFD Task Command Remarks Display information about BFD-enabled interfaces.
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. The detection module probes specific objects such as interface status, link status, network reachability, and network performance, and informs the Track module of detection results.
• BFD. • Interface management module. 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: • VRRP. • Static routing. • Policy-based routing. In some cases, the status of a track entry changes while a route is still recovering.
Task Remarks Associating Track with interface management Associating Track with VRRP Associating the Track module with an application module Required. Associating Track with static routing Use one of the methods. Associating Track with PBR Associating the Track module with a detection module Associating Track with NQA NQA supports multiple test types to analyze network performance, services, service quality.
The BFD functions as follows when it is associated with a track entry: • If the BFD detects that the link fails, it informs the track entry of the link failure. The Track module then sets the track entry to Negative state. • If the BFD detects that the link is normal, the Track module sets the track entry to Positive state. For more information about BFD, see "Configuring BFD." Configuration procedure To associate Track with BFD: Step Command Remarks 1. Enter system view. system-view N/A 2.
Step Command Remarks • Create a track entry, associate it with 2. Associating Track with interface management.
Monitor the master on a backup. If a fault occurs on the master, the backup working in switchover mode will switch to the master immediately to maintain normal communication. • When VRRP is operating in load balancing mode, associate the Track module with the VRRP Virtual Forwarder (VF) to implement the following functions: • Change the priority of the active VF (AVF) according to its uplink state.
Step Command Remarks • Associate a track entry with the VRRP VF: vrrp [ ipv6 ] vrid virtual-router-id weight track track-entry-number [ reduced weight-reduced ] 4. Associate Track with VRRP VF. • Configure the LVF to monitor the AVF status through the track entry: vrrp [ ipv6 ] vrid virtual-router-id track track-entry-number forwarder-switchover member-ip ip-address Use at least one command. By default, no track entry is specified for a VF.
Step 1. Enter system view. Command Remarks system-view N/A • Method 1: 2. Associate the static route with a track entry to check the accessibility of the next hop. ip route-static dest-address { mask | mask-length } { next-hop-address | vpn-instance d-vpn-instance-name next-hop-address } track track-entry-number [ preference preference-value ] [ tag tag-value ] [ description description-text ] Use either method.
Configuration prerequisites Before you associate Track with PBR, create a policy or a policy node and configure the match criteria as well. Configuration procedure You can associate a nonexistent track entry with PBR. The association takes effect only after you use the track command to create the track entry. For more information about PBR, see Layer 3—IP Routing Configuration Guide. To associate Track with PBR: Step Command Remarks 1. Enter system view. system-view N/A 2.
Task Command Remarks Display information about the specified or all track entries. display track { track-entry-number | all } [ | { begin | exclude | include } regular-expression ] Available in any view. Track configuration examples VRRP-Track -NQA collaboration configuration example In this example, the master monitors the uplink. Network requirements • As shown in Figure 56, configure Host A to access Host B on the Internet. The default gateway of Host A is 10.1.1.10/24.
# Configure the interval between two consecutive tests as 100 milliseconds. [RouterA-nqa-admin-test-icmp-echo] frequency 100 # Create reaction entry 1, specifying that five consecutive probe failures trigger the Track module. [RouterA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only [RouterA-nqa-admin-test-icmp-echo] quit # Start the NQA test. [RouterA] nqa schedule admin test start-time now lifetime forever 3.
Run Method : Virtual MAC Total number of virtual routers : 1 Interface GigabitEthernet1/0/1 VRID : 1 Adver Timer : 5 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 5 Auth Type : Simple Key : ***** Virtual IP : 10.1.1.10 Virtual MAC : 0000-5e00-0101 Master IP : 10.1.1.1 VRRP Track Information: Track Object : 1 State : Positive Pri Reduced : 30 # Display detailed information about VRRP group 1 on Router B.
Master IP : 10.1.1.2 VRRP Track Information: Track Object : 1 State : Negative Pri Reduced : 30 # Display detailed information about VRRP group 1 on Router B when a fault is on the link between Router A and Router C.
Figure 57 Network diagram Internet Router A Master Virtual Router Virtual IP address: 192.168.0.10 Router B Backup GE1/0/1 192.168.0.101/24 GE1/0/1 192.168.0.102/24 L2 switch BFD probe packets VRRP packets Configuration procedure 1. Configure VRRP on Router A: system-view [RouterA] interface gigabitethernet 1/0/1 # Create VRRP group 1, and configure the virtual IP address 192.168.0.10 for the group. Set the priority of Router A in VRRP group 1 to 110.
[RouterB-GigabitEthernet1/0/1] vrrp vrid 1 virtual-ip 192.168.0.10 [RouterB-GigabitEthernet1/0/1] vrrp vrid 1 track 1 switchover [RouterB-GigabitEthernet1/0/1] return Verifying the configuration # Display detailed information about VRRP group 1 on Router A.
Local IP : 192.168.0.102 The output shows that when the status of the track entry becomes Positive, Router A is the master, and Router B the backup. # Enable VRRP state debugging and BFD event debugging on Router B. terminal debugging terminal monitor debugging vrrp state debugging bfd event # When Router A fails, the following output is displayed on Router B.
• The default gateway of the hosts in the LAN is 192.168.0.10. • When Router A works correctly, hosts in the LAN access the external network through Router A. When Router A detects that the uplink is down through BFD, it decreases its priority so that Router B can preempt as the master, ensuring that the hosts in the LAN can access the external network through Router B. Figure 58 Network diagram Configuration procedure 1.
[RouterA-GigabitEthernet1/0/2] return 4. Configure VRRP on Router B: # Create VRRP group 1, and configure the virtual IP address of the group as 192.168.0.10. system-view [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] vrrp vrid 1 virtual-ip 192.168.0.10 [RouterB-GigabitEthernet1/0/2] return Verifying the configuration # Display detailed information about the VRRP group on Router A.
Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 0 Become Master : 2200ms left Auth Type : None Virtual IP : 192.168.0.10 Master IP : 192.168.0.101 The output shows that when the status of track entry 1 becomes Positive, Router A is the master and Router B the backup. # When the uplink of Router A goes down, the status of track entry 1 becomes Negative.
Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 0 Auth Type : None Virtual IP : 192.168.0.10 Virtual MAC : 0000-5e00-0101 Master IP : 192.168.0.102 The output shows that when Router A detects that the uplink fails through BFD, it decreases its priority by 20 to make sure Router B can preempt as the master.
Figure 59 Network diagram Configuration procedure 1. Specify the IP address for each interface as shown in Figure 59. (Details not shown.) 2. 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. This static route is associated with track entry 1. system-view [RouterA] ip route-static 30.1.1.0 24 10.1.1.2 track 1 # Configure a static route to 30.1.1.0/24, with the address of the next hop as 10.3.1.
[RouterA] nqa schedule admin test start-time now lifetime forever # 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 3. 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. system-view [RouterB] ip route-static 30.1.1.0 24 10.2.1.4 # Configure a static route to 20.1.1.
[RouterD] track 1 nqa entry admin test reaction 1 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. [RouterA] display ip routing-table Routing Tables: Public Destinations : 10 Destination/Mask Proto 10.1.1.0/24 10.1.1.
Destinations : 10 Destination/Mask Proto 10.1.1.0/24 10.1.1.1/32 Routes : 10 Pre Cost NextHop Interface Direct 0 0 10.1.1.1 GE1/0/1 Direct 0 0 127.0.0.1 InLoop0 10.2.1.0/24 Static 60 0 10.1.1.2 GE1/0/1 10.3.1.0/24 Direct 0 0 10.3.1.1 GE1/0/2 10.3.1.1/32 Direct 0 0 127.0.0.1 InLoop0 20.1.1.0/24 Direct 0 0 20.1.1.1 GE1/0/3 20.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0 30.1.1.0/24 Static 80 0 10.3.1.3 GE1/0/2 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.
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. Two static routes to 30.1.1.
[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. [RouterA] track 1 bfd echo interface gigabitethernet 1/0/1 remote ip 10.2.1.2 local ip 10.2.1.1 3. Configure Router B: # Configure a static route to 20.1.1.
10.2.1.1/32 Direct 0 0 127.0.0.1 InLoop0 10.3.1.0/24 Direct 0 0 10.3.1.1 GE1/0/2 10.3.1.1/32 Direct 0 0 127.0.0.1 InLoop0 20.1.1.0/24 Direct 0 0 20.1.1.1 GE1/0/3 20.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0 30.1.1.0/24 Static 60 0 10.2.1.2 GE1/0/1 127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0 The output shows the BFD detection result: the next hop 10.2.1.
PING 30.1.1.1: 56 data bytes, press CTRL_C to break Reply from 30.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms Reply from 30.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms Reply from 30.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms Reply from 30.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms Reply from 30.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms --- 30.1.1.1 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.
Figure 61 Network diagram Configuration procedure 1. Specify the IP address for each interface as shown in Figure 61. (Details not shown.) 2. 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. [RouterA] track 1 interface gigabitethernet 1/0/2 3. Configure VRRP on Router A: # Create VRRP group 1, and configure the virtual IP address 10.1.1.10 for the group.
VRID : 1 Adver Timer : 1 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 0 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 : 1 State : Positive Pri Reduced : 30 # Display detailed information about VRRP group 1 on Router B.
Auth Type : None Virtual IP : 10.1.1.10 Master IP : 10.1.1.2 VRRP Track Information: Track Object : 1 State : Negative Pri Reduced : 30 # After shutting down the uplink interface on Router A, display detailed information about VRRP group 1 on Router B.
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. [] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Network topology icons 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. Represents an access controller, a unified wired-WLAN module, or the switching engine on a unified wired-WLAN switch. Represents an access point.
Index ACDEHIMORSTV Configuring VRRP for IPv4,149 A Configuring VRRP for IPv6,158 Activating an RRPP domain,86 Contacting HP,240 Active and standby switchover configuration task list,5 Conventions,241 Associating the Track module with a detection module,211 Creating an RRPP domain,81 D Associating the Track module with an application module,213 Availability evaluation,1 Displaying and maintaining active and standby switchover,7 Availability requirements,1 Displaying and maintaining BFD,208 C Di
Overview,209 Setting the DelayDown timer,41 Overview,19 Setting the interval to send advertisement packets,41 Overview,32 Setting the port shutdown mode,42 Overview,8 Smart Link configuration examples,122 R Smart Link configuration task list,118 Smart Link overview,115 Related information,240 Resetting DLDP state,42 T Restarting the standby MPU,6 Testing connectivity between RPR stations,67 RPR configuration examples,69 Track configuration examples,218 RPR configuration task list,58 Track c
