HP A5830 series Configuration Manual

High availability

Hide thumbs Also See for A5830 series:

Configuration manual (280 pages)

Command reference manual (249 pages)

Configuration manual (246 pages)

Table Of Contents

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

Table of Contents

Quick Links

Download this manual See also: Configuration Manual

HP A5830 Switch Series

High Availability

Configuration Guide

Abstract

This document describes the software features for the HP A Series products and guides you through the

software configuration procedures. These configuration guides also provide configuration examples to

help you apply software features to different network scenarios.

This documentation is intended for network planners, field technical support and servicing engineers,

and network administrators working with the HP A Series products.

Part number: 5998-2068

Software version: Release 1109

Document version: 6W100-20110715

Table of Contents

Troubleshooting

Summary of Contents for HP A5830 series

Page 1: High Availability
Configuration Guide Abstract This document describes the software features for the HP A Series products and guides you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
Page 2 The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an...
Page 3: Table Of Contents
Contents High availability overview ··········································································································································· 7 Availability requirements ·················································································································································· 7 Availability evaluation ······················································································································································ 7 High availability technologies ········································································································································· 8 Fault detection technologies ···································································································································· 8 Protection switchover technologies ························································································································· 9 Ethernet OAM configuration ····································································································································· 11 Ethernet OAM overview ················································································································································ 11 Background ···························································································································································· 11 Major functions of Ethernet OAM ·······················································································································...
Page 4 Setting DLDP mode ························································································································································· 43 Setting the interval to send advertisement packets ····································································································· 43 Setting the delaydown timer ········································································································································· 44 Setting the port shutdown mode ··································································································································· 44 Configuring DLDP authentication ································································································································· 45 Resetting DLDP state ······················································································································································· 45 Displaying and maintaining DLDP································································································································ 46 DLDP configuration examples ·······································································································································...
Page 5 Multiple smart link groups load sharing configuration example ···································································· 106 Monitor Link configuration ······································································································································ 111 Monitor Link overview ················································································································································· 111 Terminology ························································································································································· 111 How Monitor Link works ····································································································································· 112 Configuring Monitor Link ············································································································································ 112 Configuration prerequisites ································································································································ 112 Creating a monitor link group ··························································································································· 112 Configuring monitor link group member ports ·································································································...
Page 6 Static routing-Track-BFD collaboration configuration example ······································································· 182 VRRP-track-interface management collaboration configuration example (the master monitors the uplink interface) ······························································································································································ 185 Support and other resources ·································································································································· 189 Contacting HP ······························································································································································ 189 Subscription service ············································································································································ 189 Related information ······················································································································································ 189 Documents ···························································································································································· 189 Websites ······························································································································································...
Page 7: High Availability Overview
High availability overview Communication interruptions can seriously affect widely-deployed value-added services such as IPTV and video conference. Therefore, the basic network infrastructures must be able to provide high availability. The following are effective ways to improve availability: Increasing fault tolerance •...
Page 8: High Availability Technologies
High availability technologies Increasing MTBF or decreasing MTTR can enhance the availability of a network. The high availability technologies described in this section meet the Level 3 high availability requirements by decreasing MTTR. High availability technologies can be classified as fault detection technologies or protection switchover technologies.
Page 9: Protection Switchover Technologies
Technology Introduction Reference The track module is used to implement collaboration between different modules. The collaboration here involves three parts: the application modules, the track module, and the detection modules. These modules collaborate with one another through collaboration entries. That is, the detection modules trigger the Track configuration application modules to perform certain operations through the Track...
Page 10 Technology Introduction Reference Layer 3—IP Routing GR ensures the continuity of packet forwarding when a protocol, Configuration such as BGP, IS-IS, OSPF, IPv6 BGP, IPv6 IS-IS, or OSPFv3 Guide/Configuration restarts, or during an active/standby switchover process. It needs Guide of the other devices to implement routing information backup and corresponding recovery.
Page 11: Ethernet Oam Configuration
Ethernet OAM configuration Ethernet OAM overview Throughout this document, a port with Ethernet OAM enabled is an Ethernet OAM entity or an OAM entity. Background With features such as ease of use and low price, Ethernet has gradually become the major underlying technology for today’s LANs.
Page 12: How Ethernet Oam Works
Figure 1 Formats of different types of Ethernet OAMPDUs Table 4 The fields in an OAMPDU Field Description Destination MAC address of the Ethernet OAMPDU. It is a slow protocol multicast address, 0180c2000002. Dest addr Bridges cannot forward slow protocol packets, which means you cannot forward Ethernet OAMPDUs.
Page 13 Ethernet OAM connection establishment Ethernet OAM connection is the basis of all other Ethernet OAM functions. OAM connection establishment is also known as the “Discovery phase,” where an Ethernet OAM entity discovers remote OAM entities and establishes sessions with them. In this phase, interconnected OAM entities determine whether Ethernet OAM connections can be established by exchanging Information OAMPDUs to notify the peer of their OAM configuration information and the OAM capabilities of the local nodes.
Page 14 Table 7 Ethernet OAM link error events Ethernet OAM link events Description An errored symbol event occurs when the number of detected Errored symbol event symbol errors during a specified detection interval exceeds the predefined threshold. An errored frame event occurs when the number of detected error Errored frame event frames during a specified interval exceeds the predefined threshold.
Page 15: Standards And Protocols
Standards and protocols Ethernet OAM is defined in IEEE 802.3ah (Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications. Ethernet OAM configuration task list Task Remarks Configuring basic Ethernet OAM functions Required Configuring the Ethernet OAM connection detection timers Optional Configuring errored symbol event detection Optional...
Page 16: Configuring Link Monitoring
After the timeout timer of an Ethernet OAM connection expires, the local OAM entity ages out its connection with the peer OAM entity. This causes the OAM connection to be disconnected. HP recommends that you set the connection timeout timer to at least five times the handshake packet transmission interval.
Page 17: Configuring Errored Frame Period Event Detection
To do… Use the command… Remarks • Configure the errored Optional frame event detection oam errored-frame period period-value 1 second by default. interval • Configure the errored Optional oam errored-frame threshold threshold- frame event triggering value 1 by default. threshold Configuring errored frame period event detection To configure errored frame period event detection: To do…...
Page 18: Ethernet Oam Configuration Example
To do… Use the command… Remarks • Display the statistics on critical display oam critical-event [ interface interface- events after an Ethernet OAM type interface-number ] [ | { begin | exclude | Available in any view connection is established include } regular-expression ] •...
Page 19 <DeviceB> system-view [DeviceB] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] oam mode active [DeviceB-GigabitEthernet1/0/1] oam enable [DeviceB-GigabitEthernet1/0/1] quit Verify the configuration. Use the display oam configuration command to view Ethernet OAM configuration. For example: # Display the Ethernet OAM configuration on Device A. [DeviceA] display oam configuration Configuration of the link event window/threshold : --------------------------------------------------------------------------...
Page 20 Errored Frame Threshold Errored Frame Error Running Total : 35 Event Running Total : 17 The output shows that 35 errors occurred since Ethernet OAM was enabled on Device A, 17 of which are caused by error frames. The link is unstable.
Page 21: Cfd Configuration
CFD configuration CFD overview CFD, which conforms to IEEE 802.1ag CFM, is an end-to-end per-VLAN link layer OAM mechanism used for link connectivity detection, fault verification, and fault location. Basic concepts in CFD Maintenance domain An MD defines the network where CFD plays its role. The MD boundary is defined by some MEPs configured on the ports.
Page 22 Maintenance point An MP is configured on a port and belongs to an MA. MPs fall into two types: MEPs and MIPs. • Each MEP is identified by an integer called a “MEP ID.” The MEPs of an MD define the range and boundary of the MD.
Page 23: Cfd Functions
Figure 6 demonstrates a grading example of the CFD module. Six devices exist, labeled A through F, respectively,. Suppose each device has two ports, and MEPs and MIPs are configured on some of these ports. Four levels of MDs are designed in this example. The bigger the number, the higher the level and the larger the area covered.
Page 24: Protocols And Standards
Loopback Similar to ping at the IP layer, loopback verifies the connectivity between a local device and a remote device. To implement this function, the local MEP sends LBMs to the remote MEP. Depending on whether the local MEP can receive a LBR from the remote MEP, the link state between the two can be verified. LBM frames and LBR frames are unicast frames.
Page 25: Configuring Basic Cfd Settings
Tasks Remarks functions Configuring LB on MEPs Optional Configuring LT on MEPs Optional Typically, a port blocked by STP cannot receive or send CFD messages except in the following cases: The port is configured as an outward-facing MEP. • The port is configured as a MIP or inward-facing MEP, which can still receive and send CFD •...
Page 26: Configuring Meps
A service instance is indicated by an integer to represent an MA in an MD. The MD and MA define the level and VLAN attribute of the messages handled by the MPs in a service instance. Service instances fall into these types: Service instance with the MD name, which takes effect in any version of CFD •...
Page 27: Configuring Mip Generation Rules
To do... Use the command... Remarks Required cfd meplist mep-list service- • Configure a MEP list By default, no MEP list is instance instance-id configured • Enter Layer 2 Ethernet interface interface-type interface- — interface view number cfd mep mep-id service-instance Required •...
Page 28: Configuring Cfd Functions
To do... Use the command... Remarks Required. • Configure the rules for cfd mip-rule { explicit | default } By default, neither MIPs nor the generating MIPs service-instance instance-id rules for generating MIPs are configured. Any of the following actions or cases can cause MIPs to be created or deleted after you have configured the cfd mip-rule command: Enabling CFD (use the cfd enable command) •...
Page 29: Configuring Lb On Meps
Interval field value Interval between CCM messages Timeout time of the remote MEP 600 seconds 2100 seconds Configuring LB on MEPs The LB function can verify the link state between the local MEP and the remote MEP or MIP. To configure LB on a MEP: To do...
Page 30: Cfd Configuration Example
To do... Use the command... Remarks • Display MD display cfd md [ | { begin | exclude | Available in any view configuration information include } regular-expression ] display cfd ma [ [ ma-name ] md { md- • Display MA name | level level-value } ] [ | { begin | Available in any view...
Page 31 Configure CC to monitor the connectivity among all MEPs in MD_A and MD_B. Configure the • device to use LB to locate link faults. After the status information of the entire network is obtained, use LT to identify path and locate •...
Page 32 [DeviceB] cfd ma MA_B md MD_B vlan 100 [DeviceB] cfd service-instance 2 md MD_B ma MA_B Configure Device D as you configure Device B. # Create MD_B (level 3) on Device C, create MA_B, which serves VLAN 100, in MD_B, and then create service instance 2 for MD_B and MA_B.
Page 33 # Configure the MIP generation rule in service instance 1 on Device B as explicit. [DeviceB] cfd mip-rule explicit service-instance 1 # Configure the MIP generation rule in service instance 2 on Device C as default. [DeviceC] cfd mip-rule default service-instance 2 Configure CC.
Page 34 Verify the LT function. # Identify the path between MEP 1001 and MEP 5001 in service instance 1 on Device A. [DeviceA] cfd linktrace service-instance 1 mep 1001 target-mep 5001 Linktrace to MEP 5001 with the sequence number 1001-43462 MAC Address Last MAC Relay Action 0010-FC00-6512...
Page 35: Dldp Configuration
DLDP configuration DLDP overview Background Unidirectional links occur when one end of a link can receive packets from the other end, but the other end cannot receive packets sent by the first end. Unidirectional links result in problems such as loops in an STP-enabled network.
Page 36: How Dldp Works
performs operations such as identifying peer devices, detecting unidirectional links, and shutting down unreachable ports. The auto-negotiation mechanism and DLDP work together to make sure that physical/logical unidirectional links can be detected and shut down, and to prevent failure of other protocols such as STP.
Page 37 DLDP timer Description Determines the interval for sending Probe packets, which defaults to 1 second. Probe timer 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. This timer is set to 10 seconds.
Page 38 Table 12 shows the relationship between the DLDP modes and neighbor entry aging. Table 12 DLDP mode and neighbor entry aging Detecting a neighbor Removing the neighbor Triggering the Enhanced after the corresponding DLDP mode entry immediately after the timer after an Entry timer neighbor entry ages Entry timer expires expires...
Page 39 DLDP authentication mode You can use DLDP authentication to prevent network attacks and illegal detection. There are three DLDP authentication modes. 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 the packets where the two fields conflict with the corresponding local configuration.
Page 40 Table 15 Procedures for processing different types of DLDP packets received Packet type Processing procedure If the corresponding neighbor entry does not exist, creates the neighbor entry, triggers the Entry timer, and transits to Probe Retrieves the Advertisement state. neighbor packet with RSY tag information If the corresponding neighbor entry already exists, resets the...
Page 41 Packet type Processing procedure local port is in If it is, the local port transits to Active state if the neighbor Disable state information the packet carries is consistent with the local port information. If not, performs no processing. If yes and the local port is not in Disable state, sets the state of the corresponding neighbor to unidirectional, and then checks Checks whether the the state of other neighbors.
Page 42: Dldp Configuration Task List
DLDP neighbor state A DLDP neighbor can be in one of the three states described in Table Table 17 Description on DLDP neighbor states DLDP neighbor state Description A neighbor is in this state when it is just detected and is being probed. A neighbor Unknown is in this state only when it is being probed.
Page 43: Enabling Dldp
For more information about the duplex and speed commands, see Layer 2—LAN Switching Command Reference. Enabling DLDP To properly configure DLDP on the device, first enable DLDP globally, and then enable it on each port. To enable DLDP: To do… Use the command…...
Page 44: Setting The Delaydown Timer
Instead, the DLDP state machine generates log and traps to prompt you to shut down unidirectional link ports manually with the shutdown command. HP recommends that you do as prompted. Then the DLDP state machine transits to the Disable state.
Page 45: Configuring Dldp Authentication
To do… Use the command… Remarks Optional dldp unidirectional-shutdown { auto | • Set port shutdown mode manual } auto by default If the device is busy, or the CPU usage is high, normal links may be treated as unidirectional links. In this case, you can set the port shutdown mode to manual mode to alleviate the impact caused by false unidirectional link report.
Page 46: Displaying And Maintaining Dldp
To do… Use the command… Remarks • Reset DLDP state dldp reset Required Resetting DLDP state in interface view/port group view Resetting DLDP state in interface view or port group view applies to the current port or all ports in the port group.
Page 47 Figure 11 Network diagram for configuring automatic shutdown of unidirectional links Configuration procedure Configure Device A. # Enable DLDP globally. <DeviceA> system-view [DeviceA] dldp enable # Configure GigabitEthernet 1/0/49 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.
Page 48 Configure Device B. # Enable DLDP globally. <DeviceB> system-view [DeviceB] dldp enable # Configure GigabitEthernet 1/0/49 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it. [DeviceB] interface gigabitethernet 1/0/49 [DeviceB-GigabitEthernet1/0/49] duplex full [DeviceB-GigabitEthernet1/0/49] speed 1000 [DeviceB-GigabitEthernet1/0/49] dldp enable [DeviceB-GigabitEthernet1/0/49] quit # Configure GigabitEthernet 1/0/50 to operate in full duplex mode and at 1000 Mbps, and enable...
Page 49 DLDP port state : advertisement DLDP link state : up The neighbor number of the port is 1. Neighbor mac address : 0023-8956-3600 Neighbor port index : 60 Neighbor state : two way Neighbor aged time : 12 The output shows that both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 are in Advertisement state, which means both links are bidirectional.
Page 50: Manually Shutting Down Unidirectional Links
%Jan 18 17:47:35:894 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/50 link status is UP. The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 is now up. Manually shutting down unidirectional links Network requirements As shown in Figure 12, Device A and Device B are connected with two fiber pairs. •...
Page 51 # Configure GigabitEthernet 1/0/50 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port. [DeviceA] interface gigabitethernet 1/0/50 [DeviceA-GigabitEthernet1/0/50] duplex full [DeviceA-GigabitEthernet1/0/50] speed 1000 [DeviceA-GigabitEthernet1/0/50] dldp enable [DeviceA-GigabitEthernet1/0/50] quit # Set the DLDP mode to enhanced. [DeviceA] dldp work-mode enhance # Set the port shutdown mode to manual.
Page 52 The number of enabled ports is 2. Interface GigabitEthernet1/0/49 DLDP port state : advertisement DLDP link state : up The neighbor number of the port is 1. Neighbor mac address : 0023-8956-3600 Neighbor port index : 59 Neighbor state : two way Neighbor aged time : 11 Interface GigabitEthernet1/0/50 DLDP port state : advertisement...
Page 53: Troubleshooting Dldp
[DeviceA] interface gigabitethernet 1/0/49 [DeviceA-GigabitEthernet1/0/49] shutdown %Jan 18 18:16:12:044 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/49 link status is DOWN. [DeviceA-GigabitEthernet1/0/49] quit [DeviceA] interface gigabitethernet 1/0/50 [DeviceA-GigabitEthernet1/0/50] shutdown %Jan 18 18:18:03:583 2010 DeviceA IFNET/3/LINK_UPDOWN: GigabitEthernet1/0/50 link status is DOWN. The output shows that the link status of both GigabitEthernet 1/0/49 and GigabitEthernet 1/0/50 is down.
Page 54: Rrpp Configuration
RRPP configuration The 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. Background Metropolitan area networks MANs and enterprise networks usually use the ring structure to improve reliability.
Page 55 RRPP ring A ring-shaped Ethernet topology is called an “RRPP ring.” RRPP rings fall into two types: primary ring and subring. You can configure a ring as either the primary ring or a subring by specifying its ring level. The primary ring is of level 0, and a subring is of level 1. An RRPP domain contains one or multiple RRPP rings, one serving as the primary ring and the others serving as subrings.
Page 56: Rrppdus
As shown in 13, Ring 1 is the primary ring and Ring 2 is a subring. Device A is the master node Figure of Ring 1, and Device B, Device C, and Device D are the transit nodes of Ring 1. Device E is the master node of Ring 2, Device B is the edge node of Ring 2, and Device C is the assistant-edge node of Ring 2.
Page 57: Rrpp Timers
Type Description The transit node, the edge node, or the assistant-edge node initiates Link-Down Link-Down packets to notify the master node of the disappearance of a ring in case of a link failure. The master node initiates Common-Flush-FDB (FDB stands for Forwarding Common-Flush-FDB 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.
Page 58 VLANs and sending Common-Flush-FDB packets to instruct all transit nodes to update their own MAC entries and ARP/ND entries. 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 are down.
Page 59: Typical Rrpp Networking
As shown in 17, Device B is the edge node of Ring 2 and Ring 3, and Device C is the assistant- Figure edge node of Ring 2 and Ring 3. Device B and Device C must send or receive Edge-Hello packets frequently.
Page 60 Figure 15 Schematic diagram for a tangent-ring network Intersecting rings As shown in 16, two or more rings are in the network topology and two common nodes exist Figure between rings. You only need to define an RRPP domain and configure one ring as the primary ring and the other rings as subrings.
Page 61 Figure 17 Schematic diagram for a dual-homed-ring network Single-ring load balancing In a single-ring network, you can achieve load balancing by configuring multiple domains. As shown in 18, Ring 1 is configured as the primary ring of both Domain 1 and Domain 2. Figure Domain 1 and Domain 2 are configured with different protected VLANs.
Page 62: Protocols And Standards
Figure 19 Schematic diagram for an intersecting-ring load balancing network Protocols and standards RFC 3619 Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1 is related to RRPP. 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.
Page 63: Creating An Rrpp Domain
Task Remarks Optional Configuring an RRPP ring group Perform this task on the edge node and assistant-edge node in the RRPP domain. RRPP does not have an auto election mechanism, so you must configure each node in the ring network properly for RRPP to monitor and protect the ring network.
Page 64: Configuring Protected Vlans
Configuring protected VLANs Before configuring RRPP rings in an RRPP domain, configure the same protected VLANs for all nodes in the RRPP domain first. All VLANs that the RRPP ports are assigned to should be protected by the RRPP domains. You can configure protected VLANs through referencing MSTIs.
Page 65: Configuring Rrpp Rings
Configuring RRPP rings When configuring an RRPP ring, you must make some configurations on the ports connecting each node to the RRPP ring before configuring the nodes. RRPP ports (connecting devices to an RRPP ring) must be Layer-2 Ethernet ports or Layer-2 aggregate interfaces and cannot be member ports of any aggregation group, service loopback group, or smart link group.
Page 66 To specify a master node: To do… Use the command… Remarks • Enter system view system-view — • Enter RRPP domain view rrpp domain domain-id — ring ring-id node-mode master [ • Specify the current device as primary-port interface-type the master node of the ring, interface-number ] [ secondary- Required and specify the primary port...
Page 67: Activating An Rrpp Domain
To specify an assistant-edge node: To do… Use the command… Remarks • Enter system view system-view — • Enter RRPP domain view rrpp domain domain-id — ring ring-id node-mode transit [ • Specify the current device as a primary-port interface-type transit node of the primary interface-number ] [ secondary- Required...
Page 68: Configuring An Rrpp Ring Group
To do… Use the command… Remarks Required • Configure the Hello timer and timer hello-timer hello-value fail- By default, the Hello timer value is Fail timer for the RRPP domain timer fail-value 1 second, and the Fail timer value is 3 seconds. The Fail timer value must be equal to or greater than three times the Hello timer value.
Page 69: Rrpp Configuration Examples
To do… Use the command… Remarks display rrpp ring-group [ ring-group-id ] [ | { • Display RRPP group Available in any begin | exclude | include } regular-expression configuration information view display rrpp verbose domain domain-id [ ring • Display detailed RRPP Available in any ring-id ] [ | { begin | exclude | include }...
Page 70 # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceA> system-view [DeviceA] vlan 1 to 30 [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, and disable the spanning tree feature.
Page 71: Intersecting Ring Configuration Example
[DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] undo link-delay [DeviceB-GigabitEthernet1/0/1] undo stp enable [DeviceB-GigabitEthernet1/0/1] port link-type trunk [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] quit [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] undo link-delay [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/2] quit # Create RRPP domain 1.
Page 72 Device B is the transit node of primary ring 1 and the edge node of subring 2, and GigabitEthernet • 1/0/3 is the edge port. Device C is the transit node of primary ring 1 and the assistant-edge node of subring 1, and •...
Page 73 # 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. [DeviceA] rrpp domain 1 [DeviceA-rrpp-domain1] control-vlan 4092 [DeviceA-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1.
Page 74 [DeviceB-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device B as a transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1. [DeviceB-rrpp-domain1] ring node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceB-rrpp-domain1] ring 1 enable...
Page 75 [DeviceC-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device C as a transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1. [DeviceC-rrpp-domain1] ring node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceC-rrpp-domain1] ring 1 enable...
Page 76 [DeviceD-rrpp-domain1] quit # Enable RRPP. [DeviceD] rrpp enable Configure Device E. # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceE> system-view [DeviceE] vlan 1 to 30 [DeviceE] stp region-configuration [DeviceE-mst-region] instance 1 vlan 1 to 30 [DeviceE-mst-region] active region-configuration [DeviceE-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and...
Page 77: Dual Homed Rings Configuration Example
Dual homed rings configuration example Networking requirements As shown in Figure Device A through Device H form RRPP domain 1. Specify the primary control VLAN of RRPP domain • 1 as VLAN 4092, and specify that RRPP domain 1 protects VLANs 1 through 30. Device A through Device D form primary ring 1.
Page 78 Configuration procedure Configure Device A. # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate the MST region configuration. <DeviceA> system-view [DeviceA] vlan 1 to 30 [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 through...
Page 79 # Configure Device A as the edge node of subring 2, with GigabitEthernet 1/0/4 as the edge port, and enable subring 2. [DeviceA-rrpp-domain1] ring 2 node-mode edge edge-port gigabitethernet 1/0/4 [DeviceA-rrpp-domain1] ring 2 enable # Configure Device A as the edge node of subring 3, with GigabitEthernet 1/0/3 as the edge port, and enable subring 3.
Page 80 # 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. [DeviceB] rrpp domain 1 [DeviceB-rrpp-domain1] control-vlan 4092 [DeviceB-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1.
Page 81 [DeviceC-GigabitEthernet1/0/3] undo stp enable [DeviceC-GigabitEthernet1/0/3] port link-type trunk [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/3] quit [DeviceC] interface gigabitethernet 1/0/4 [DeviceC-GigabitEthernet1/0/4] undo link-delay [DeviceC-GigabitEthernet1/0/4] undo stp enable [DeviceC-GigabitEthernet1/0/4] port link-type trunk [DeviceC-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/4] quit # Create RRPP domain 1.
Page 82 [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] quit [DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] undo link-delay [DeviceD-GigabitEthernet1/0/2] undo stp enable [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/2] quit [DeviceD] interface gigabitethernet 1/0/3 [DeviceD-GigabitEthernet1/0/3] undo link-delay [DeviceD-GigabitEthernet1/0/3] undo stp enable [DeviceD-GigabitEthernet1/0/3] port link-type trunk [DeviceD-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30...
Page 83 [DeviceE-mst-region] instance 1 vlan 1 to 30 [DeviceE-mst-region] active region-configuration [DeviceE-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, and disable the spanning tree feature. Configure the two ports as trunk ports, and assign them to VLANs 1 through 30.
Page 84 [DeviceF-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceF-GigabitEthernet1/0/1] quit [DeviceF] interface gigabitethernet 1/0/2 [DeviceF-GigabitEthernet1/0/2] undo link-delay [DeviceF-GigabitEthernet1/0/2] undo stp enable [DeviceF-GigabitEthernet1/0/2] port link-type trunk [DeviceF-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceF-GigabitEthernet1/0/2] quit # Create RRPP domain 1. Configure VLAN 4092 as the primary control VLAN of RRPP domain 1, and configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.
Page 85 [DeviceG] rrpp domain 1 [DeviceG-rrpp-domain1] control-vlan 4092 [DeviceG-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device G as the master node of subring 4, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable subring 4. [DeviceG-rrpp-domain1] ring node-mode...
Page 86: Intersecting-Ring Load Balancing Configuration Example
[DeviceH] rrpp enable Verify the configuration. Use the display command to view RRPP configuration and operational information on each device. Intersecting-ring load balancing configuration example Networking requirements As shown in Figure Device A, Device B, Device C, Device D, and Device F form RRPP domain 1, and VLAN 100 is the •...
Page 87 [DeviceA] vlan 1 to 2 [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 [DeviceA-mst-region] instance 2 vlan 2 [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2, and disable the spanning tree feature. Configure the two ports as trunk ports, and assign them to VLAN 1 and VLAN 2.
Page 88 # Create VLANs 1 and 2, map VLAN 1 to MSTI 1 and VLAN 2 to MSTI 2, and activate MST region configuration. <DeviceB> system-view [DeviceB] vlan 1 to 2 [DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 1 [DeviceB-mst-region] instance 2 vlan 2 [DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and...
Page 89 [DeviceB-rrpp-domain1] ring node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0 [DeviceB-rrpp-domain1] ring 1 enable # Configure Device B as the assistant-edge node of subring 3 in RRPP domain 1, with GigabitEthernet 1/0/4 as the edge port, and enable subring 3. [DeviceB-rrpp-domain1] ring 3 node-mode assistant-edge edge-port gigabitethernet 1/0/4 [DeviceB-rrpp-domain1] ring 3 enable [DeviceB-rrpp-domain1] quit...
Page 90 [DeviceC-GigabitEthernet1/0/2] undo stp enable [DeviceC-GigabitEthernet1/0/2] port link-type trunk [DeviceC-GigabitEthernet1/0/2] port trunk permit vlan 1 2 [DeviceC-GigabitEthernet1/0/2] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/3, and disable the spanning tree feature. Configure the port as a trunk port, and assign it to VLAN 2. [DeviceC] interface gigabitethernet 1/0/3 [DeviceC-GigabitEthernet1/0/3] undo link-delay [DeviceC-GigabitEthernet1/0/3] undo stp enable...
Page 91 # Configure Device C as the edge node of subring 2 in RRPP domain 2, with GigabitEthernet 1/0/3 as the edge port, and enable subring 2. [DeviceC-rrpp-domain2] ring 2 node-mode edge edge-port gigabitethernet 1/0/3 [DeviceC-rrpp-domain2] ring 2 enable [DeviceC-rrpp-domain2] quit # Enable RRPP.
Page 92 [DeviceD-rrpp-domain2] control-vlan 105 [DeviceD-rrpp-domain2] protected-vlan reference-instance 2 # Configure Device D as the transit node of primary ring 1 in RRPP domain 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port, and enable ring 1. [DeviceD-rrpp-domain2] ring node-mode...
Page 93 [DeviceE-rrpp-domain2] quit # Enable RRPP. [DeviceE] rrpp enable Configure Device F. # Create VLAN 1, map VLAN 1 to MSTI 1, and activate MST region configuration. <DeviceF> system-view [DeviceF] vlan 1 [DeviceF-vlan1] quit [DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 1 [DeviceF-mst-region] active region-configuration [DeviceF-mst-region] quit # Cancel the physical state change suppression interval setting on GigabitEthernet 1/0/1 and...
Page 94: Troubleshooting
[DeviceB-rrpp-ring-group1] domain 2 ring 2 [DeviceB-rrpp-ring-group1] domain 1 ring 3 # Create RRPP ring group 1 on Device C, and add subrings 2 and 3 to the RRPP ring group. [DeviceC] rrpp ring-group 1 [DeviceC-rrpp-ring-group1] domain 2 ring 2 [DeviceC-rrpp-ring-group1] domain 1 ring 3 Verify the configuration.
Page 95: Smart Link Configuration
Smart Link configuration Smart Link overview Background To avoid single-point failures and guarantee network reliability, downstream devices are usually dual- homed to upstream devices, as shown in Figure Figure 24 Diagram for a dual uplink network To remove network loops on a dual-homed network, you can use a spanning tree protocol or the RRPP. The problem with STP, however, is that STP convergence time is long, which makes it not suitable for users who have high demand on convergence speed.
Page 96: Terminology
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 master and the subordinate ports. Only one port is active for forwarding at a time, and the other port is blocked and in the standby state. When link failure occurs on the active port due to port shutdown or the presence of a unidirectional link, for example, the standby port becomes active to take over, and the original active port transits to the blocked state.
Page 97: How Smart Link Works
How Smart Link works Link backup mechanism As shown in 24, the link on Port1 of Device C is the master link, and the link on Port2 of Device Figure C is the subordinate link. Typically, Port1 is in the forwarding state, and Port2 is in the standby state. When the master link fails, Port2 takes over to forward traffic and Port1 is blocked and placed in the standby state.
Page 98: Smart Link Configuration Task List
downlink ports to the up/down state of uplink ports, triggering Smart Link to perform link switchover on the downstream device. For more information about Monitor Link, see the chapter “Monitor Link configuration.” Smart Link configuration task list Task Remarks Configuring protected VLANs for a smart link Required group Configuring member ports for a smart link...
Page 99: Configuring Member Ports For A Smart Link Group
To do… Use the command… Remarks • Enter MST region view stp region-configuration — Optional instance instance-id vlan vlan-list Use either command • Configure the VLAN-to- All VLANs in an MST region are instance mapping table vlan-mapping modulo modulo mapped to CIST (MSTI 0) by default •...
Page 100: Configuring Role Preemption For A Smart Link Group
To do… Use the command… Remarks • Enter Layer 2 Ethernet interface interface-type interface- interface view or layer 2 — number aggregate interface view • Configure member ports for a port smart-link group group-id { Required smart link group master | slave } Configuring role preemption for a smart link group To configure role preemption for a smart link group: To do…...
Page 101: Configuring An Associated Device
Configuring an associated device Configuration prerequisites Disable the spanning tree feature on the associated device’s ports that connect to the member ports of the smart link group. Otherwise, the ports will discard flush messages when they are not in the forwarding state in case of a topology change.
Page 102: Smart Link Configuration Examples
Smart Link configuration examples Single smart link group configuration example Network requirements As shown in Figure Device C and Device D are smart link devices, and Device A, Device B, and Device E are • associated devices. Traffic of VLANs 1 through 30 on Device C and Device D are dually uplinked to Device A.
Page 103 [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] shutdown [DeviceC-GigabitEthernet1/0/2] undo stp enable [DeviceC-GigabitEthernet1/0/2] port link-type trunk [DeviceC-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs. [DeviceC] smart-link group 1 [DeviceC-smlk-group1] protected-vlan reference-instance 1 # Configure GigabitEthernet 1/0/1 as the master port and GigabitEthernet 1/0/2 as the subordinate...
Page 104 [DeviceD-GigabitEthernet1/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs. [DeviceD] smart-link group 1 [DeviceD-smlk-group1] protected-vlan reference-instance 1 # Configure GigabitEthernet 1/0/1 as the master port and GigabitEthernet 1/0/2 as the subordinate port for smart link group 1.
Page 105 [DeviceB-GigabitEthernet1/0/3] undo stp enable [DeviceB-GigabitEthernet1/0/3] smart-link flush enable control-vlan 10 [DeviceB-GigabitEthernet1/0/3] quit Configure Device E. # Create VLANs 1 through 30. <DeviceE> system-view [DeviceE] vlan 1 to 30 # Configure GigabitEthernet 1/0/1 as a trunk port, and assign it to VLANs 1 through 30. Enable flush message receiving on it, and configure VLAN 10 and VLAN 20 as the receive control VLANs.
Page 106: Multiple Smart Link Groups Load Sharing Configuration Example
[DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/2] smart-link flush enable control-vlan 10 20 [DeviceA-GigabitEthernet1/0/2] quit Verify the configuration. You can use the display smart-link group command to view smart link group configuration on a device. # Display the smart link group configuration on Device C. [DeviceC] display smart-link group 1 Smart link group 1 information: Device ID: 000f-e23d-5af0...
Page 107 Figure 26 Network diagram for multiple smart link groups load sharing configuration Configuration procedure Configure Device C. # Create VLAN 1 through VLAN 200. Map VLANs 1 through 100 to MSTI 1. Map VLANs 101 through 200 to MSTI 2, and activate MST region configuration. <DeviceC>...
Page 108 [DeviceC-smlk-group1] port gigabitethernet1/0/2 slave # Enable role preemption in smart link group 1, enable flush message sending, and configure VLAN 10 as the transmit control VLAN. [DeviceC-smlk-group1] preemption mode role [DeviceC-smlk-group-1] flush enable control-vlan 10 [DeviceC-smlk-group-1] quit # Create smart link group 2, and configure all VLANs mapped to MSTI 2 as the protected VLANs for smart link group 2.
Page 109 [DeviceB-GigabitEthernet1/0/2] smart-link flush enable control-vlan 10 110 [DeviceB-GigabitEthernet1/0/2] quit Configure Device D. # Create VLAN 1 through VLAN 200. <DeviceD> system-view [DeviceD] vlan 1 to 200 # Configure GigabitEthernet 1/0/1 as a trunk port and assign it to VLANs 1 through 200. Enable flush message receiving and configure VLAN 10 and VLAN 110 as the receive control VLANs on GigabitEthernet 1/0/1.
Page 110 Device ID: 000f-e23d-5af0 Preemption delay: 1(s) Preemption mode: ROLE Control VLAN: 10 Protected VLAN: Reference Instance 1 Member Role State Flush-count Last-flush-time ----------------------------------------------------------------------------- GigabitEthernet1/0/1 MASTER ACTVIE 16:37:20 2010/02/21 GigabitEthernet1/0/2 SLAVE STANDBY 17:45:20 2010/02/21 Smart link group 2 information: Device ID: 000f-e23d-5af0 Preemption mode: ROLE Preemption delay: 1(s) Control VLAN: 110...
Page 111: Monitor Link Configuration
Monitor Link configuration Monitor Link overview Monitor Link is a port collaboration function. Monitor Link usually works together with Layer 2 topology protocols. The idea is to monitor the states of uplink ports and adapt the up/down state of downlink ports to the up/down state of uplink ports, triggering link switchover on the downstream device in time, as shown in Figure...
Page 112: How Monitor Link Works
When any uplink port goes up, the monitor link group goes up and brings up all downlink ports. HP does not recommend shutting down manually or bringing up the downlink ports in a monitor link group.
Page 113: Displaying And Maintaining Monitor Link
In interface view To configure member ports for a monitor link group in interface view: To do… Use the command… Remarks • Enter system view system-view — • Enter Layer 2 Ethernet interface view or interface interface-type interface- — Layer 2 aggregate interface view number •...
Page 114 Figure 28 Network diagram for monitor link configuration Configuration procedure Configure Device C. # Create VLANs 1 through 30, map these VLANs to MSTI 1, and activate MST region configuration. <DeviceC> system-view [DeviceC] vlan 1 to 30 [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit...
Page 115 Configure Device A. # Create VLANs 1 through 30. <DeviceA> system-view [DeviceA] vlan 1 to 30 # Configure GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 as trunk ports, assign them to VLANs 1 through 30, and enable flush message receiving on them. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] port link-type trunk [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30...
Page 116 # Configure GigabitEthernet 1/0/1 as a trunk port, assign it to VLANs 1 through 30, and enable flush message receiving on it. [DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] port link-type trunk [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] smart-link flush enable [DeviceD-GigabitEthernet1/0/1] quit # Configure GigabitEthernet 1/0/2 as a trunk port, assign it to VLANs 1 through 30, disable the spanning tree feature, and enable flush message receiving on it.
Page 117: Vrrp Configuration
VRRP configuration The term router in this document refers to both routers and Layer 3 switches. The term interface in the VRRP feature refers to Layer 3 interfaces, including VLAN interfaces and route- mode (or Layer 3) Ethernet ports. You can set an Ethernet port to operate in route mode by using the port link-mode route command (see Layer 2—LAN Switching Configuration Guide).
Page 118: Vrrp Standard Protocol Mode
VRRP standard protocol mode Introduction to 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 •...
Page 119: Vrrp Timers
VRRP priority ranges from 0 to 255. The priority is higher as the number is greater. Priorities 1 to 254 are configurable. Priority 0 is reserved for special uses and priority 255 for the IP address owner. When a router acts as the IP address owner, its running priority is always 255. That is, the IP address owner in a VRRP group acts as the master as long as it works properly.
Page 120: Packet Format
Packet format The master multicasts VRRP packets periodically to declare its existence. Also, VRRP packets are used for checking the parameters of the virtual router and electing the master. VRRP packets are encapsulated in IP packets, with the protocol number being 112. Figure 31 shows the format of a VRRPv2 packet and...
Page 121: Principles Of Vrrp
Count IP Addrs/Count IPv6 Addrs—Number of virtual IPv4 or IPv6 addresses for the VRRP group. A • VRRP group can have multiple virtual IPv4 or IPv6 addresses. Auth Type—Authentication type. 0 means no authentication, 1 means simple text authentication, • and 2 means MD5 authentication.
Page 122: Vrrp Application (Taking Ipv4-Based Vrrp For Example)
If the uplink interface of a router in a VRRP group fails, usually the VRRP group cannot be aware of the uplink interface failure. If the router is the master of the VRRP group, hosts on the LAN are not able to access external networks because of the uplink failure.
Page 123: Configuring Vrrp For Ipv4
In load sharing mode, multiple routers provide services simultaneously. This mode requires two or more VRRP groups, each of which comprises a master and one or more backups. The masters of the VRRP groups are assumed by different routers, as shown in Figure Figure 34 VRRP in load sharing mode A router can be in multiple VRRP groups and hold a different priority in a different group.
Page 124: Specifying The Type Of Mac Addresses Mapped To Virtual Ip Addresses
If VRRP groups with the same ID are created on multiple interfaces of a device, and the VRRP advertisements of these VRRP groups are to be sent through QinQ networks, HP recommends you to map the real MAC addresses of the interfaces to the virtual IP addresses of these VRRP groups. Otherwise, the VRRP advertisements of these VRRP groups cannot be sent successfully.
Page 125: Configuring Router Priority, Preemptive Mode And Tracking Function
VRRP group. In the latter case, the router is called the IP address owner. When a router is the IP address owner in a VRRP group, HP recommends you not to use the IP address of the interface (virtual IP address of the VRRP group) to establish a neighbor relationship with the adjacent router, that is, not to use the network command to enable OSPF on the interface.
Page 126: Configuring Vrrp Packet Attributes
Configuration procedure By configuring router priority, preemptive mode, interface tracking, or a track entry, you can determine which router in the VRRP group serves as the master. configure router priority, preemptive mode tracking function: To do… Use the command… Remarks •...
Page 127: Enabling The Trap Function For Vrrp
To do… Use the command… Remarks • Enter the specified interface interface interface-type interface- — view number • Configure the authentication Optional vrrp vrid virtual-router-id mode and authentication key authentication-mode { md5 | Authentication is not performed when the VRRP groups send simple } key by default and receive VRRP packets...
Page 128: Displaying And Maintaining Vrrp For Ipv4
Configuring different intervals for sending VRRP advertisements on the routers in a VRRP group might cause a backup to trigger a change of its status because the backup does not receive any VRRP advertisements for a specified period of time. To solve this problem, configure the same interval for sending VRRP advertisements on each router in the VRRP group.
Page 129: Creating A Vrrp Group And Configuring A Virtual Ipv6 Address
need to update the mapping between the IPv6 address and the MAC address when the master changes. Real MAC address of an interface—In case that an IP address owner exists in a VRRP group, if the • virtual IPv6 address is mapped to the virtual MAC address, two MAC addresses are mapped to one IPv6 address.
Page 130: Configuring Router Priority, Preemptive Mode And Tracking Function
VRRP group When a router is the IP address owner in a VRRP group, HP recommends you not to use the IPv6 address of the interface (virtual IPv6 address of the VRRP group) to establish an OSPFv3 neighbor relationship with the adjacent router, that is, not to use the ospfv3 area command to enable OSPFv3 on the interface.
Page 131: Configuring Vrrp Packet Attributes
To do… Use the command… Remarks vrrp ipv6 vrid virtual-router-id Optional • Configure VRRP to track a track track-entry-number [ reduced specified track entry Not configured by default priority-reduced | switchover ] The running priority of an IP address owner is always 255 and you do not need to configure it. An IP address owner always works in preemptive mode.
Page 132: Displaying And Maintaining Vrrp For Ipv6
advertisements for a specified period of time. To solve this problem, configure the same interval for sending VRRP advertisements on each router in the VRRP group. Displaying and maintaining VRRP for IPv6 To do… Use the command… Remarks display vrrp ipv6 [ verbose ] [ interface interface- •...
Page 133 Configuration procedure Configure Switch A. # Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port gigabitethernet 1/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 202.38.160.1 255.255.255.0 # Create VRRP group 1, and set its virtual IP address to 202.38.160.111. [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 202.38.160.111 # Set the priority of Switch A in VRRP group 1 to 110, which is higher than that of Switch B (100), so that Switch A can become the master.
Page 134 Virtual IP : 202.38.160.111 Virtual MAC : 0000-5e00-0101 Master IP : 202.38.160.1 # Display the detailed information of VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID...
Page 135: Vrrp Interface Tracking Configuration Example
Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 202.38.160.111 Virtual MAC : 0000-5e00-0101 Master IP : 202.38.160.1 The output shows that after Switch A resumes normal operation, it becomes the master, and packets sent from host A to host B are forwarded by Switch A.
Page 136 [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 202.38.160.1 255.255.255.0 # Create a VRRP group 1 and set its virtual IP address to 202.38.160.111. [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 202.38.160.111 # Configure the priority of Switch A in the VRRP group to 110, which is higher than that of Switch B (100), so that Switch A can become the master.
Page 137 Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : Simple...
Page 138: Vrrp With Multiple Vlans Configuration Example
Auth Type : Simple : hello Virtual IP : 202.38.160.111 Master IP : 202.38.160.2 VRRP Track Information: Track Interface: Vlan3 State : Down Pri Reduced : 30 # When VLAN-interface 3 on Switch A is not available, the detailed information of VRRP group 1 on Switch B is displayed.
Page 139 Figure 37 Network diagram for configuration of multiple VRRP groups in different VLANs Configuration procedure Configure Switch A. # Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port gigabitethernet 1/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 202.38.160.1 255.255.255.128 # Create a VRRP group 1 and set its virtual IP address to 202.38.160.100.
Page 140 [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] ip address 202.38.160.2 255.255.255.128 # Create a VRRP group 1 and set its virtual IP address to 202.38.160.100. [SwitchB-Vlan-interface2] vrrp vrid 1 virtual-ip 202.38.160.100 [SwitchB-Vlan-interface2] quit # Configure VLAN 3. [SwitchB] vlan 3 [SwitchB-vlan3] port gigabitethernet 1/0/6 [SwitchB-vlan3] quit [SwitchB] interface vlan-interface 3 [SwitchB-Vlan-interface3] ip address 202.38.160.131 255.255.255.128...
Page 141: Ipv6-Based Vrrp Configuration Examples
Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 2 Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Become Master : 2200ms left...
Page 142 Figure 38 Network diagram for single VRRP group configuration Configuration procedure Configure Switch A. # Configure VLAN 2. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] vlan 2 [SwitchA-vlan2] port gigabitethernet 1/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ipv6 address fe80::1 link-local [SwitchA-Vlan-interface2] ipv6 address 1::1 64 # Create a VRRP group 1 and set its virtual IPv6 addresses to FE80::10 and 1::10.
Page 143 [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] ipv6 address fe80::2 link-local [SwitchB-Vlan-interface2] ipv6 address 1::2 64 # Create a VRRP group 1 and set its virtual IPv6 addresses to FE80::10 and 1::10. [SwitchB-Vlan-interface2] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local [SwitchB-Vlan-interface2] vrrp ipv6 vrid 1 virtual-ip 1::10 # Configure Switch B to work in preemptive mode, with the preemption delay set to 5 seconds.
Page 144 The output shows that in VRRP group 1 Switch A is the master, Switch B is the backup and packets sent from Host A to Host B are forwarded by Switch A. When Switch A fails, you can still successfully ping Host B on Host A. To view the detailed information of the VRRP group on Switch B, use the display vrrp ipv6 verbose command.
Page 145: Vrrp Interface Tracking Configuration Example
VRRP interface tracking configuration example Network requirements Switch A and Switch B belong to VRRP group 1 with the virtual IP addresses of 1::10/64 and • FE80::10. Host A wants to access Host B on the Internet, and learns 1::10/64 as its default gateway through •...
Page 146 [SwitchA-Vlan-interface2] vrrp ipv6 vrid 1 priority 110 # Set the authentication mode for VRRP group 1 to simple and authentication key to hello. [SwitchA-Vlan-interface2] vrrp ipv6 vrid 1 authentication-mode simple hello # Set the VRRP advertisement interval to 400 centiseconds. [SwitchA-Vlan-interface2] vrrp ipv6 vrid 1 timer advertise 400 # Configure Switch A to work in preemptive mode, so that it can become the master whenever it works normally;...
Page 147 IPv6 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 400 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time...
Page 148: Vrrp With Multiple Vlans Configuration Example
Preempt Mode : Yes Delay Time Become Master : 4200ms left Auth Type : Simple : hello Virtual IP : FE80::10 1::10 Master IP : FE80::2 VRRP Track Information: Track Interface: Vlan3 State : Down Pri Reduced : 30 # When interface VLAN-interface 3 on Switch A is not available, the detailed information of VRRP group 1 on Switch B is displayed.
Page 149 Figure 40 Network diagram for configuration of multiple VRRP groups in different VLANs Virtual IPv6 address 1: FE80::10 1::10/64 Vlan-int2 Switch A FE80::1 1::1/64 VLAN 2 Vlan-int3 FE90::1 Gateway: 1::10/64 2::1/64 Internet Vlan-int2 VLAN 3 FE80::2 1::2/64 Gateway: 2::10/64 Vlan-int3 FE90::2 Switch B 2::2/64...
Page 150 [SwitchA-Vlan-interface3] ipv6 address 2::1 64 # Create VRRP group 2 and set its virtual IPv6 addresses to FE90::10 and 2::10. [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip fe90::10 link-local [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip 2::10 # Enable Switch A to send RA messages, so that hosts in VLAN 3 can learn the default gateway address.
Page 151 Run Method : Virtual MAC Total number of virtual routers : 2 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP...
Page 152: Troubleshooting Vrrp
The output shows that in VRRP group 1 Switch A is the master, Switch B is the backup and hosts with the default gateway of 1::10/64 accesses the Internet through Switch A; in VRRP group 2 Switch A is the backup, Switch B is the master and hosts with the default gateway of 2::10/64 accesses the Internet through Switch B.
Page 153: Bfd Configuration
BFD configuration The term router in the BFD features refers to both routers and Layer 3 switches. The term interface in the BFD features refers to Layer 3 interfaces, including VLAN interfaces and route- mode (or Layer 3) Ethernet ports. You can set an Ethernet port to operate in route mode by using the port link-mode route command (see Layer 2—LAN Switching Configuration Guide).
Page 154 Operation of BFD Figure 41 BFD session establishment (on OSPF routers) The process of BFD session establishment is as follows: A protocol sends hello messages to discover neighbors and establish neighborships. After establishing neighborships, the protocol notifies BFD of the neighbor information, including destination and source addresses.
Page 155: Bfd Packet Format
Multi-hop detection—Detects any of the paths between two systems. These paths have multiple hops • and may 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. Note that BFD LSP detection is a special case in which BFD control packets are sent in one direction, and the peer device reports the link status through other links.
Page 156 Figure 43 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...
Page 157: Supported Features
to cease 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. •...
Page 158: Configuring Bfd Basic Functions
Configuring BFD basic functions The BFD basic functions configuration is the basis for configuring BFD for other protocols. Configuration prerequisites Before configuring BFD basic functions, complete the following tasks: Configure the network layer addresses of the interfaces so that adjacent nodes are reachable to •...
Page 159: Displaying And Maintaining Bfd
To do… Use the command… Remarks Optional For relevant information, see the • Configure the minimum description of the Required Min interval for receiving BFD bfd min-receive-interval value RX Interval field in “BFD packet control packets format” 400 milliseconds by default Optional For relevant information, see the •...
Page 160: Track Configuration
Track configuration Track overview Introduction to collaboration The track module works between application and detection modules, as Figure 44 shows. 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, respectively.
Page 161: Collaboration Application Example
• • 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 action. The following application modules can be associated with the track module: VRRP •...
Page 162: Associating The Track Module With A Detection Module
Task Remarks Associating track with NQA Required Associating the track module Associating track with BFD Use any of the with a detection module approaches Associating track with interface management Associating track with VRRP Required Associating the track module Associating track with static routing Use any of the with an application module approaches...
Page 163: Associating Track With Interface Management
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 the Negative state. If the BFD detects that the link is normal, the track module sets the track entry to the Positive state. •...
Page 164: Associating The Track Module With An Application Module
To do… Use the command… Remarks • Create a track entry, associate it with the interface management module to monitor the Layer 3 protocol track track-entry-number interface status of an interface, and interface-type interface-number protocol { specify the delay time for the ipv4 | ipv6 } [ delay { negative negative- track module to notify the time | positive positive-time } * ]...
Page 165: Associating Track With Static Routing
To do… Use the command… Remarks Required vrrp [ ipv6 ] vrid virtual-router-id • Associate a track entry with a track track-entry-number [ reduced No track entry is specified for a VRRP group priority-reduced | switchover ] VRRP group by default VRRP tracking is not valid on an IP address owner.
Page 166: Associating Track With Pbr
If a static route needs route recursion, the associated track entry must monitor the next hop of the recursive route instead of that of the static route. Otherwise, a valid route may be considered invalid. For more information about static route configuration, see Layer 3 IP Routing Configuration Guide.
Page 167: Displaying And Maintaining Track Entries
To do… Use the command… Remarks apply ip-address default next-hop ip- • Set the default next hop, and address [ track track-entry-number] [ ip- associate it with a track entry address [ track track-entry-number] ] 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.
Page 168 Configuration procedure Create VLANs, and assign corresponding ports to the VLANs. Configure the IP address of each VLAN interface as shown in Figure 45. (Details not shown) Configure an NQA test group on Switch A. <SwitchA> system-view # Create an NQA test group with the administrator name admin and the operation tag test. [SwitchA] nqa entry admin test # Configure the test type as ICMP-echo.
Page 169 # Set the authentication mode of VRRP group 1 to simple, and the authentication key to hello. [SwitchB-Vlan-interface2] vrrp vrid 1 authentication-mode simple hello # Configure the master to send VRRP packets at an interval of five seconds. [SwitchB-Vlan-interface2] vrrp vrid 1 timer advertise 5 # Configure Switch B to work in preemptive mode, and set the preemption delay to five seconds.
Page 170: Configuring Bfd For A Vrrp Backup To Monitor The Master
# Display detailed information about VRRP group 1 on Switch A when a fault is on the link between Switch A and Switch C. IPv4 Standby Information: Run Mode : Standard Run Method : Virtual MAC Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer...
Page 171 which makes the switchover slow. To solve this problem, VRRP uses BFD to probe the state of the master. Once the master fails, the backup can become the new master in milliseconds. Figure 46 Network diagram for monitoring the master on the backup Internet Virtual router Switch A...
Page 172 # Create VRRP group 1, and configure the virtual IP address 192.168.0.10 for the group. VRRP group 1 monitors the status of track entry 1. When the status of the track entry becomes Negative, Switch B quickly becomes the master. [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] vrrp vrid 1 virtual-ip 192.168.0.10 [SwitchB-Vlan-interface2] vrrp vrid 1 track 1 switchover...
Page 173: Configuring Bfd For The Vrrp Master To Monitor The Uplinks
BFD session: Packet type: Echo Interface : Vlan-interface2 Remote IP : 192.168.0.101 Local IP : 192.168.0.102 The output shows that when the status of the track entry becomes Positive, Switch A is the master, and Switch B the backup. # Enable VRRP state debugging and BFD event debugging on Switch B. <SwitchB>...
Page 174 B can preempt as the master, ensuring that the hosts in the LAN can access the external network through Switch B. Figure 47 Network diagram for monitoring uplinks using BFD Internet Master Backup uplink device uplink device Vlan-int3 1.1.1.2/24 Uplink Uplink Vlan-int3 1.1.1.1/24...
Page 175 Configure VRRP on Switch B. # Create VRRP group 1, and configure the virtual IP address of the group as 192.168.0.10. <SwitchB> system-view [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] vrrp vrid 1 virtual-ip 192.168.0.10 [SwitchB-Vlan-interface2] return Verify the configuration. # Display the detailed information of the VRRP group on Switch A. <SwitchA>...
Page 176 Preempt Mode : Yes Delay Time 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, Switch A is the master, and Switch B the backup.
Page 177: Static Routing-Track-Nqa Collaboration Configuration Example
Auth Type : None Virtual IP : 192.168.0.10 Virtual MAC : 0000-5e00-0101 Master IP : 192.168.0.102 The output shows that when Switch A detects that the uplink fails through BFD, it decreases its priority by 20 to ensure that Switch B can preempt as the master. Static routing-track-NQA collaboration configuration example Network requirements As shown in...
Page 178 Figure 48 Network diagram for static routing-track-NQA collaboration configuration Configuration procedure Create VLANs, and assign corresponding ports to the VLANs. Configure the IP address of each VLAN interface as shown in Figure 48. (Details not shown) Configure Switch A. # Configure a static route to 30.1.1.0/24, with the address of the next hop as 10.1.1.2 and the default priority 60.
Page 179 # Start the NQA test. [SwitchA] 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). [SwitchA] track 1 nqa entry admin test reaction 1 Configure Switch B.
Page 180 [SwitchD] 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). [SwitchD] track 1 nqa entry admin test reaction 1 Verify the configuration.
Page 181 [SwitchA] display ip routing-table Routing Tables: Public Destinations : 10 Routes : 10 Destination/Mask Proto Cost NextHop Interface 10.1.1.0/24 Direct 0 10.1.1.1 Vlan2 10.1.1.1/32 Direct 0 127.0.0.1 InLoop0 10.2.1.0/24 Static 60 10.1.1.2 Vlan2 10.3.1.0/24 Direct 0 10.3.1.1 Vlan3 10.3.1.1/32 Direct 0 127.0.0.1 InLoop0 20.1.1.0/24...
Page 182: Static Routing-Track-Bfd Collaboration Configuration Example
Static routing-Track-BFD collaboration configuration example Network requirements As shown in 49, Switch A, Switch B, and Switch C are connected to two segments 20.1.1.0/24 Figure and 30.1.1.0/24. Configure static routes on these routers so that the two segments can communicate with each other, and configure route backup to improve reliability of the network.
Page 183 [SwitchA] ip route-static 30.1.1.0 24 10.2.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.3 and the priority [SwitchA] 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. [SwitchA] bfd echo-source-ip 10.10.10.10 # Configure track entry 1, and associate it with the BFD session.
Page 184: Interface
[SwitchA] display ip routing-table Routing Tables: Public Destinations : 9 Routes : 9 Destination/Mask Proto Cost NextHop Interface 10.2.1.0/24 Direct 0 10.2.1.1 Vlan2 10.2.1.1/32 Direct 0 127.0.0.1 InLoop0 10.3.1.0/24 Direct 0 10.3.1.1 Vlan3 10.3.1.1/32 Direct 0 127.0.0.1 InLoop0 20.1.1.0/24 Direct 0 20.1.1.1 Vlan5 20.1.1.1/32...
Page 185: Network Requirements
The output shows the BFD detection result: the next hop 10.2.1.2 is unreachable (the status of the track entry is Negative), and the backup static route takes effect, and Switch A forwards packets to 30.1.1.0/24 through Switch C and Switch B. # When the master route fails, the hosts in 20.1.1.0/24 can still communicate with the hosts in 30.1.1.0/24.
Page 186 Figure 50 Network diagram for VRRP-track-interface management collaboration configuration Configuration procedure Create VLANs, and assign corresponding ports to the VLANs. Configure the IP address of each VLAN interface as shown in Figure 50. (Details not shown) Configure a track entry on Switch A. # Configure track entry 1, and associate it with the physical status of the uplink interface VLAN-interface [SwitchA] track 1 interface vlan-interface 3 Configure VRRP on Switch A.
Page 187 Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 10.1.1.10 Virtual MAC : 0000-5e00-0101 Master IP...
Page 188 Become Master : 2200ms left Auth Type : None Virtual IP : 10.1.1.10 Master IP : 10.1.1.2 VRRP Track Information: Track Object State : Negative Pri Reduced : 30 # After shutting down the uplink interface on Switch A, display detailed information about VRRP group 1 on Switch B.
Page 189: Support And Other Resources
Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...
Page 190: Conventions
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. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 191 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.
Page 192: Index
Index auto-recovery (DLDP), 41 802.1ag CFD basic configuration, 25 availability CFD configuration, 21, 30 CFD basic configuration, 25 activating RRPP domain, 67 CFD configuration, 21, 30 configuring automatic shutdown of unidirectional active BFD operation mode, 155 link (DLDP), 46 DLDP link state, 36 configuring manual shutdown of unidirectional link DLDP timer, 36 (DLDP), 50...
Page 193 BFD for VRRP master to monitor the uplinks (track), configuring function, 28 configuring LT on MEP, 29 configuring MEP, 26 CC on MEP (CFD), 28 CFD, 21, 30 configuring MIP generation rule, 27 CFD basic settings, 25 configuring protocol version, 25 configuring service instance, 25 connection detection timer (Ethernet OAM), 15 continuity check function, 23...
Page 194 (Ethernet OAM), 15 device establishing (Ethernet OAM), 13 associated Smart Link device configuration, 101 BFD configuration, 153, 158 contacting HP, 189 BFD detection methods, 154 continuity check function (CFD), 23 control packet mode (BFD session), 155 BFD operating modes, 155...
Page 195 DLDP, 43 configuring, 35, 46 configuring authentication, 45 flush message reception, 101 configuring automatic shutdown of unidirectional flush message sending, 100 LB on MEP (CFD), 29 link, 46 trap function (VRRP IPv4), 127 configuring duplex mode (Ethernet interface), 42 configuring manual shutdown of unidirectional encapsulation (VRRP packet format), 120 link, 50 enhanced (DLDP timer), 36...
Page 196 CFD, 23 VRRP load sharing (IPv4), 122 VRRP priority, 118 configuring (CFD), 28 VRRP router working mode, 119 configuring basic Ethernet OAM, 15 configuring CC on MEP (CFD), 28 VRRP timer, 119 configuring LT on MEP (CFD), 29 Ethernet OAM configuring, 11, 18 continuity check (CFD), 23 configuring basic function, 15...
Page 197 VRRP for IPv4 multiple VLAN configuration, 138 symbols used, 190 websites, 189 VRRP for IPv4 single group configuration, 132 icons, 190 VRRP for IPv6 configuration, 128, 141 VRRP for IPv6 interface tracking configuration, 145 inactive (DLDP link state), 36 VRRP for IPv6 multiple VLAN configuration, 148 initial (DLDP link state), 36 interface VRRP for IPv6 single group configuration, 141...
Page 198 list (CFD), 23 specifying virtual IP address mapping (VRRP IPv6), message maintaining enabling flush message reception, 101 enabling flush message sending, 100 BFD, 159 flush (Smart Link), 96 DLDP, 46 Ethernet OAM configuration, 17 MA (CFD), 21 concept (CFD), 22 configuring generation rule (CFD), 27 MD (CFD), 21 MEP (CFD), 22...
Page 199 Ethernet OAM basic configuration, 15 MP (CFD maintenace point), 22 MPLS (BFD supported feature), 157 Ethernet OAM configuration, 11, 18 MTBF (high availability), 7 group member port configuration (Smart Link), 99 group role preemption configuration (Smart Link), MTTR (high availability), 7 multicast flush message (Smart Link), 96 multi-hop (BFD detection method), 154 high availability discussion, 7...
Page 200 collaboration between track and policy-based VRRP for IPv6 interface tracking configuration, 145 VRRP for IPv6 multiple VLAN configuration, 148 routing modules, 161 VRRP for IPv6 single group configuration, 141 PIM (BFD supported feature), 157 plain text (DLDP authentication mode), 39 VRRP group, 118 point VRRP load sharing (IPv4), 122...
Page 201 configuring group role preemption (Smart Link), mode (VRRP IPv4), 125 mode (VRRP IPv6), 130 mode (VRRP), 119 configuring interface tracking (VRRP IPv4), 135 configuring interface tracking (VRRP IPv6), 145 mode VRRP tracking, 121 configuring intersecting ring (RRPP), 71 priority router (VRRP IPv4), 125 configuring intersecting ring...
Page 202 specifying RRPP master node, 65 configuring tracking function (VRRP IPv4), 125 configuring tracking function (VRRP IPv6), 130 specifying RRPP transit node, 66 configuring virtual IP address (VRRP IPv4), 124 process (DLDP), 39 protected VLAN configuring virtual IP address (VRRP IPv6), 129 configuring for Smart Link group, 98 configuring VRRP, 117 configuring VRRP for IPv4, 123, 132...
Page 203 intersecting ring configuration, 71 configuring static routing-track-BFD collaboration, intersecting ring load balancing configuration, 86 configuring static routing-track-NQA collaboration, intersecting-ring load balancing, 61 intersecting-ring networking, 60 link down mechanism, 58 configuring track with NQA collaboration, 167 configuring virtual IP address (VRRP IPv4), 124 load balancing, 58 configuring virtual IP address (VRRP IPv6), 129 maintaining, 68...
Page 204 configuring VRRP-track-interface management ring network load balancing (RRPP), 61 Smart Link collaboration, 185 associated device configuration, 101 group member port configuration (Smart Link), 99 backup mechanism, 97 group role preemption configuration (Smart Link), collaborating with Monitor Link, 97 collaboration mechanism, 97 configuration, 95, 102 protected VLAN configuration (Smart Link), 98 Smart Link associated device configuration, 101...
Page 205 VRRP group, 118, 119 group role preemption configuration (Smart Link), VRRP load sharing (IPv4), 122 Monitor Link configuration, 111, 112, 113 VRRP packet format, 120 VRRP priority, 118 Monitor Link group, 111 VRRP router working mode, 119 Monitor Link group member port configuration, symbols, 190 protected VLAN (Smart Link), 96 system administration...
Page 206 static routing-track-BFD collaboration configuration, Monitor Link group member port configuration, node type (RRPP), 55 static routing-track-NQA collaboration configuration, 177 primary port (RRPP), 56 VRRP-track-interface management collaboration ring group (RRPP), 56, 58 ring recovery (RRPP), 58 configuration, 185 ring state (RRPP), 55 tracking a track entry (VRRP), 122 RRPP configuration, 54, 62, 69...
Page 207 packet format, 120 configuring static routing-track-NQA collaboration, preemption delay timer, 119 configuring track with NQA collaboration, 167 priority, 118 configuring VRRP-track-interface management router working mode, 119 timer, 119 collaboration, 185 control VLAN. See control VLAN tracking, 121 data VLAN. See data VLAN tracking a track entry, 122 tracking an interface, 121 domain (RRPP), 54...

HP A5830 series Configuration Manual

High Availability Overview

Ethernet OAM Configuration

CFD Configuration

DLDP Configuration

RRPP Configuration

Smart Link Configuration

Monitor Link Configuration

VRRP Configuration

BFD Configuration

Track Configuration

Support and Other Resources

Index

Quick Links

High Availability

Configuration Guide

Troubleshooting

Related Manuals for HP A5830 series

Summary of Contents for HP A5830 series

Table of Contents