HPE FlexFabric 5700 Series Configuration Manual

Hide thumbs Also See for FlexFabric 5700 Series:

Network management and monitoring configuration manual (314 pages)

Configuration manual (64 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

208

209

210

211

212

213

214

215

216

Table of Contents

Quick Links

HPE FlexFabric 5700 Switch Series

High Availability Configuration Guide

Part number: 5998-5593R

Software version: Release 2422P01 and later

Document version: 6W100-20160331

Table of Contents

Troubleshooting

Need help?

Do you have a question about the FlexFabric 5700 Series and is the answer not in the manual?

Questions and answers

Summary of Contents for HPE FlexFabric 5700 Series

Page 1 HPE FlexFabric 5700 Switch Series High Availability Configuration Guide Part number: 5998-5593R Software version: Release 2422P01 and later Document version: 6W100-20160331...
Page 2 © Copyright 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Contents Configuring Ethernet OAM ·············································································· 1 Overview ···························································································································································· 1 Major functions of Ethernet OAM ··············································································································· 1 Ethernet OAMPDUs ··································································································································· 1 How Ethernet OAM works ·························································································································· 1 Protocols and standards ···························································································································· 3 Ethernet OAM configuration task list ·················································································································· 3 ...
Page 4 Enabling DLDP ················································································································································ 34 Setting the interval to send advertisement packets ························································································· 35 Setting the DelayDown timer ··························································································································· 35 Setting the port shutdown mode ······················································································································ 35 Configuring DLDP authentication ····················································································································· 36 Displaying and maintaining DLDP ··················································································································· 36 ...
Page 5 Enabling Monitor Link globally ······················································································································· 111 Creating a monitor link group ························································································································· 111 Configuring monitor link group member interfaces ························································································ 111 In monitor link group view ······················································································································ 112 In interface view ····································································································································· 112 Configuring the switchover delay for the downlink interfaces in a monitor link group ···································· 112 ...
Page 6 Configuring BFD basic functions ···················································································································· 167 Configuring echo packet mode ·············································································································· 167 Configuring control packet mode ··········································································································· 168 Configuring a BFD template ··················································································································· 169 Displaying and maintaining BFD ···················································································································· 169 Configuring Track ························································································ 171 ...
Page 7: Configuring Ethernet Oam
Configuring Ethernet OAM Overview Ethernet Operation, Administration, and Maintenance (OAM) is a tool that monitors Layer 2 link status and addresses common link-related issues on the "last mile." Ethernet OAM improves Ethernet management and maintainability. You can use it to monitor the status of the point-to-point link between two directly connected devices.
Page 8 Ethernet OAM connection establishment Ethernet OAM connection is the basis of all the other Ethernet OAM functions. OAM connection establishment is also known as the Discovery phase, where an Ethernet OAM entity discovers the remote OAM entity to establish a session. In this phase, two connected OAM entities exchange Information OAMPDUs to advertise their OAM configuration and capabilities to each other for a comparison.
Page 9: Protocols And Standards
Ethernet OAM link events Description An errored frame period event occurs when the number of frame errors in Errored frame period event the detection window (specified number of received frames) exceeds the predefined threshold. An errored frame seconds event occurs when the number of errored frame seconds (the second in which an errored frame appears is called an Errored frame seconds event errored frame second) detected on a port in the detection window...
Page 10: Configuring Basic Ethernet Oam Functions
Tasks at a glance (Optional.) Configuring the Ethernet OAM connection detection timers (Optional.) Configuring link monitoring • Configuring errored symbol event detection • Configuring errored frame event detection • Configuring errored frame period event detection • Configuring errored frame seconds event detection (Optional.) Configuring the action a port takes after it receives an Ethernet OAM event from the remote end (Optional.)
Page 11: 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, causing the OAM connection to disconnect. As a best practice to keep the Ethernet OAM connections stable, set the connection timeout timer to be a minimum of five times the handshake packet transmission interval.
Page 12: Configuring Errored Frame Event Detection
To configure errored symbol event detection on a port: Step Command Remarks Enter system view. system-view Enter Layer 2/Layer 3 interface interface-type Ethernet port view. interface-number Configure the errored symbol oam errored-symbol-period By default, an interface uses the event detection window. window window-value value configured globally.
Page 13: Configuring Errored Frame Seconds Event Detection
Step Command Remarks Enter system view. system-view Configure the errored frame oam global By default, the errored frame period event detection errored-frame-period window period event detection window is window. window-value 10000000. Configure the errored frame oam global By default, the errored frame period event triggering errored-frame-period threshold period event triggering threshold...
Page 14: Configuring The Action A Port Takes After It Receives An Ethernet Oam Event From The Remote End
Step Command Remarks Enter Layer 2/Layer 3 interface interface-type Ethernet port view. interface-number Configure the errored frame oam errored-frame-seconds By default, an interface uses the seconds event detection window window-value value configured globally. window. Configure the errored frame oam errored-frame-seconds By default, an interface uses the seconds event triggering threshold threshold-value...
Page 15: Enabling Ethernet Oam Remote Loopback On A Specific Port
• Ethernet OAM remote loopback must be supported by both the remote port and the sending port. • Enabling Ethernet OAM remote loopback interrupts data communications. After Ethernet OAM remote loopback is disabled, all the ports involved will shut down and then come up. Ethernet OAM remote loopback can be disabled by any of the following events: disabling Ethernet OAM, disabling Ethernet OAM remote loopback, and Ethernet OAM connection timing out.
Page 16: Displaying And Maintaining Ethernet Oam
Step Command Remarks effect when the next loopback starts on the port. Displaying and maintaining Ethernet OAM Execute display commands in any view and reset commands in user view: Purpose Command Display information about an Ethernet OAM display oam { local | remote } [ interface connection.
Page 17 # Set the errored frame event detection window to 20000 milliseconds, and set the errored frame event triggering threshold to 10. [DeviceA] oam errored-frame period 200 [DeviceA] oam errored-frame threshold 10 [DeviceA-Ten-GigabitEthernet1/0/1] quit Configure Device B: # Configure Ten-GigabitEthernet 1/0/1 to operate in passive Ethernet OAM mode (the default), and enable Ethernet OAM for it.
Page 18: Configuring Cfd
Configuring CFD Overview Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management (CFM) and ITU-T Y.1731, is an end-to-end per-VLAN link layer OAM mechanism. CFD is used for link connectivity detection, fault verification, and fault location. Basic CFD concepts Maintenance domain A maintenance domain (MD) defines the network or part of the network where CFD plays its role.
Page 19 Maintenance point An MP is configured on a port and belongs to an MA. MPs include the following types: maintenance association end points (MEPs) and maintenance association intermediate points (MIPs). • MEPs define the boundary of the MA. Each MEP is identified by a MEP ID. The MA to which a MEP belongs defines the VLAN of packets sent by the MEP.
Page 20: Cfd Functions
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. Figure 4 CFD grading example MEP list A MEP list is a collection of local MEPs allowed to be configured and the remote MEPs to be monitored in the same MA.
Page 21 MEP, the link state between the two can be verified. LBM frames are multicast and unicast frames. HPE devices support sending and receiving unicast LBM frames and receiving multicast LBM frames. HPE devices do not support sending multicast LBM frames.
Page 22: Eais
The TST function tests the bit errors between two MEPs. The source MEP sends a TST frame, which carries the test pattern, such as pseudo random bit sequence (PRBS) or all-zero, to the target MEP. When the target MEP receives the TST frame, it determines the bit errors by calculating and comparing the content of the TST frame.
Page 23: Configuring Basic Cfd Settings
Tasks at a glance • (Optional.) Configuring AIS • (Optional.) Configuring LM • (Optional.) Configuring one-way DM • (Optional.) Configuring two-way DM • (Optional.) Configuring TST (Optional.) Configuring EAIS Typically, a port blocked by the spanning tree feature cannot receive or send CFD messages except in the following cases: •...
Page 24: Configuring Meps
Configuring MEPs CFD is implemented through various operations on MEPs. As a MEP is configured on a service instance, the MD level and VLAN attribute of the service instance become the attribute of the MEP. Before creating MEPs, configure the MEP list. A MEP list is a collection of local MEPs that can be configured in an MA and the remote MEPs to be monitored.
Page 25: Configuring Cfd Functions
Step Command Remarks Enter system view. system-view By default, no rules for generating Configure MIP cfd mip-rule { default | explicit } MIPs are configured, and the auto-generation rules. service-instance instance-id system does not automatically create any MIP. Configuring CFD functions Configuration prerequisites Complete basic CFD settings.
Page 26: Configuring Lb
• Only the outward-facing MEP on a physical port supports hardware CC. The hardware CC function does not take effect on the physical port in either of the following cases: The physical port is added to an aggregation group. The MEP on the physical port is an inward-facing MEP. •...
Page 27: Configuring Ais
Step Command Remarks cfd linktrace service-instance Find the path between a instance-id mep mep-id { target-mac source MEP and a target mac-address | target-mep Available in any view. MEP. target-mep-id } [ ttl ttl-value ] [ hw-only ] Enter system view. system-view Enable LT messages cfd linktrace auto-detection [ size...
Page 28: Configuring One-Way Dm
Configuring one-way DM The one-way DM function measures the one-way frame delay between two MEPs, and monitors and manages the link transmission performance. One-way DM requires that the time settings at the transmitting MEP and the receiving MEP be the same.
Page 29: Configuring Eais
Configuring EAIS You can configure EAIS on a device that does not support or is not configured with CFD. However, EAIS must collaborate with the CFD function in the network, so you must configure CFD in the network. For a port to send the EAIS frames, configure port status-AIS collaboration, and configure the correct EAIS frame transmission level and interval.
Page 30: Cfd Configuration Example
Purpose Command associated with the status of the specified port. interface-type interface-number ] Display the one-way DM result on the specified display cfd dm one-way history MEP. [ service-instance instance-id [ mep mep-id ] ] display cfd linktrace-reply [ service-instance Display LTR information received by a MEP.
Page 31 Figure 5 Network diagram Configuration procedure Configure a VLAN and assign ports to it: On each device shown in Figure 5, create VLAN 100 and assign ports Ten-GigabitEthernet 1/0/1 through Ten-GigabitEthernet 1/0/4 to VLAN 100. Enable CFD: # Enable CFD on Device A. <DeviceA>...
Page 32 # On Device A, configure a MEP list in service instance 1, and create inward-facing MEP 1001 in service instance 1 on Ten-GigabitEthernet 1/0/1. [DeviceA] cfd meplist 1001 4002 5001 service-instance 1 [DeviceA] interface ten-gigabitethernet 1/0/1 [DeviceA-Ten-GigabitEthernet1/0/1] cfd mep 1001 service-instance 1 inbound [DeviceA-Ten-GigabitEthernet1/0/1] quit # On Device B, configure a MEP list in service instances 1 and 2.
Page 33 [DeviceD] interface ten-gigabitethernet 1/0/1 [DeviceD-Ten-GigabitEthernet1/0/1] cfd cc service-instance 2 mep 4001 enable [DeviceD-Ten-GigabitEthernet1/0/1] quit # Enable the sending of CCM frames for MEP 4002 in service instance 1 on Ten-GigabitEthernet 1/0/3. [DeviceD] interface ten-gigabitethernet 1/0/3 [DeviceD-Ten-GigabitEthernet1/0/3] cfd cc service-instance 1 mep 4002 enable [DeviceD-Ten-GigabitEthernet1/0/3] quit # On Device E, enable the sending of CCM frames for MEP 5001 in service instance 1 on Ten-GigabitEthernet 1/0/4.
Page 34 Verify the LM function after the CC function obtains the status information for the entire network: # Test the frame loss from MEP 1001 to MEP 4002 in service instance 1 on Device A. [DeviceA] cfd slm service-instance 1 mep 1001 target-mep 4002 Reply from 0010-fc00-6514 Far-end frame loss: 10 Near-end frame loss: 20...
Page 35 # Test the bit errors on the link from MEP 1001 to MEP 4002 in service instance 1 on Device A. [DeviceA] cfd tst service-instance 1 mep 1001 target-mep 4002 5 TSTs have been sent. Please check the result on the remote device. # Display the TST result on MEP 4002 in service instance 1 on Device D.
Page 36: Configuring Dldp
Configuring DLDP Overview 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 fiber links occur in the following cases: • Fibers are cross-connected.
Page 37: Basic Concepts
Basic concepts DLDP neighbor states If port A and B are on the same link and port A can receive link-layer packets from port B, port B is a DLDP neighbor of port A. Two ports that can exchange packets are neighbors. Table 6 DLDP neighbor states DLDP timer Description...
Page 38: How Dldp Works
DLDP timer Description RecoverProbe packets to detect whether a unidirectional link has been restored to bidirectional. DLDP authentication mode You can use DLDP authentication to prevent network attacks and illegal detecting. Table 9 DLDP authentication mode Processing at the Authentication Processing at the DLDP packet sending side DLDP packet mode...
Page 39 Figure 8 Broken fiber Device A Device B Port 1 Port 2 Correct fiber connection Device A Device B Port 1 Port 2 One fiber is broken Ethernet Tx end Rx end Fiber link Broken fiber fiber port As shown in Figure 8, Device and Device B are connected through an optical fiber.
Page 40: Configuration Restrictions And Guidelines
Figure 9 Network diagram As shown in Figure 9, Device A through Device D are connected through a hub, and enabled with DLDP. When Port 1, Port 2, and Port 3 detect that the link to Port 4 fails, they deletes the neighborship with Port 4, but stay in Bidirectional state.
Page 41: Setting The Interval To Send Advertisement Packets
Step Command Remarks By default, DLDP is globally Enable DLDP globally. dldp global enable disabled. Enter Layer 2 Ethernet interface interface-type interface view. interface-number By default, DLDP is disabled on Enable DLDP. dldp enable an interface. Setting the interval to send advertisement packets To make sure DLDP can detect unidirectional links before network performance deteriorates, set the advertisement interval appropriate for your network environment.
Page 42: Configuring Dldp Authentication
manually bring up the port. If the network performance is low, the device is busy, or the CPU usage is high, use this mode to prevent normal links from being shut down because of false unidirectional link reports. On a port with both remote OAM loopback and DLDP enabled, if the port shutdown mode is auto mode, the port will be shut down by DLDP when it receives a packet sent by itself.
Page 43: Dldp Configuration Examples
DLDP configuration examples Automatically shutting down unidirectional links Network requirements As shown in Figure 10, Device A and Device B are connected with two fiber pairs. Configure DLDP to automatically shut down the faulty port upon detecting a unidirectional link, and automatically bring up the port after you clear the fault.
Page 44 [DeviceB-Ten-GigabitEthernet1/0/1] speed 10000 [DeviceB-Ten-GigabitEthernet1/0/1] dldp enable [DeviceB-Ten-GigabitEthernet1/0/1] quit # Configure Ten-GigabitEthernet 1/0/2 to operate in full duplex mode and at 10000 Mbps, and enable DLDP on it. [DeviceB] interface ten-gigabitethernet 1/0/2 [DeviceB-Ten-GigabitEthernet1/0/2] duplex full [DeviceB-Ten-GigabitEthernet1/0/2] speed 10000 [DeviceB-Ten-GigabitEthernet1/0/2] dldp enable [DeviceB-Ten-GigabitEthernet1/0/2] quit # Set the port shutdown mode to auto.
Page 45 <DeviceA>%Jul 11 17:40:31:089 2014 DeviceA IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet1/0/1 link status is DOWN. %Jul 11 17:40:31:091 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet1/0/1 is DOWN. %Jul 11 17:40:31:677 2014 DeviceA IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet1/0/2 link status is DOWN. %Jul 11 17:40:31:678 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet1/0/2 is DOWN.
Page 46: Manually Shutting Down Unidirectional Links
%Jul 11 17:43:02:357 2014 DeviceA IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet1/0/2 link status is UP. %Jul 11 17:43:02:362 2014 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface Ten-GigabitEthernet1/0/2. The neighbor's system MAC is 0023-8956-3600, and the port index is 2. %Jul 11 17:43:02:362 2014 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface Ten-GigabitEthernet1/0/2.
Page 47 Configure Device B: # Enable DLDP globally. <DeviceB> system-view [DeviceB] dldp global enable # Configure Ten-GigabitEthernet 1/0/1 to operate in full duplex mode and at 10000 Mbps, and enable DLDP on it. [DeviceB] interface ten-gigabitethernet 1/0/1 [DeviceB-Ten-GigabitEthernet1/0/1] duplex full [DeviceB-Ten-GigabitEthernet1/0/1] speed 10000 [DeviceB-Ten-GigabitEthernet1/0/1] dldp enable [DeviceB-Ten-GigabitEthernet1/0/1] quit # Configure Ten-GigabitEthernet 1/0/2 to operate in full duplex mode and at 10000 Mbps, and...
Page 48 The output shows that both Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2 are in Bidirectional state, which means both links are bidirectional. # Enable the monitoring of logs on the current terminal on Device A, and set the lowest level of the logs that can be output to the current terminal to 6. [DeviceA] quit <DeviceA>...
Page 49 [DeviceA-Ten-GigabitEthernet1/0/1] shutdown The following log information is displayed on Device A: [DeviceA-Ten-GigabitEthernet1/0/1]%Jul 12 08:34:23:717 2014 DeviceA IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet1/0/1 link status is DOWN. %Jul 12 08:34:23:718 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet1/0/1 is DOWN. %Jul 12 08:34:23:778 2014 DeviceA IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet1/0/2 link status is DOWN.
Page 50: Configuring Rrpp
Configuring RRPP Overview Metropolitan area networks (MANs) and enterprise networks typically use the ring topology to improve reliability. However, services will be interrupted if any node in the ring network fails. A ring network typically uses RPR or Ethernet rings. RPR is high in cost because it needs dedicated hardware.
Page 51 RRPP ring A ring-shaped Ethernet topology is called an RRPP ring. RRPP rings include primary rings and subrings. You can configure a ring as either the primary ring or a subring by specifying its ring level. The primary ring is of level 0, and a subring is of level 1. An RRPP domain contains one or multiple RRPP rings, one serving as the primary ring and the others serving as subrings.
Page 52: Rrppdus
Each master node or transit node has two ports connected to an RRPP ring, a primary port and a secondary port. You can determine the role of a port. In terms of functionality, the primary port and the secondary port of a master node have the following differences: The primary port and the secondary port are designed to play the role of sending and receiving Hello packets, respectively.
Page 53: Rrpp Timers
Type Description Complete-Flush-FDB packets for the following purposes: • Instruct the transit nodes, edge nodes, and assistant edge nodes to update their MAC address entries and ARP/ND entries. • Instruct the transit nodes to release temporarily blocked ports. The edge node initiates Edge-Hello packets to examine the SRPTs between the Edge-Hello edge node and the assistant edge node.
Page 54: Typical Rrpp Networking
Link down alarm mechanism In an RRPP domain, when the transit node, edge node, or assistant edge node finds that any of its ports is down, it immediately sends Link-Down packets to the master node. When the master node receives a Link-Down packet, it takes the following actions: •...
Page 55 Figure 13 Schematic diagram for a single-ring network Tangent rings As shown in Figure 14, two or more rings exist in the network topology and only one common node exists between rings. You must define an RRPP domain for each ring. Figure 14 Schematic diagram for a tangent-ring network Intersecting rings As shown in...
Page 56 Figure 15 Schematic diagram for an intersecting-ring network Dual-homed rings As shown in Figure 16, two or more rings exist in the network topology and two similar common nodes exist between rings. You need only define an RRPP domain and configure one ring as the primary ring and the other rings as subrings.
Page 57: Protocols And Standards
Figure 17 Schematic diagram for a single-ring load balancing network Intersecting-ring load balancing In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains. As shown in Figure • Ring 1 is the primary ring and Ring 2 is the subring in both Domain 1 and Domain 2. •...
Page 58: Rrpp Configuration Task List
RRPP configuration task list You can configure RRPP in the following order: • Create RRPP domains based on service planning. • Specify control VLANs and data VLANs for each RRPP domain. • Determine the ring roles and node roles based on the traffic paths in each RRPP domain. RRPP does not have an auto election mechanism.
Page 59: Configuring Protected Vlans
Follow these guidelines when you configure control VLANs: • Do not configure the default VLAN of a port accessing an RRPP ring as the control VLAN, and do not enable QinQ or VLAN mapping on control VLANs. If you do, RRPPDUs cannot be correctly forwarded.
Page 60: Configuring Rrpp Rings
Step Command Remarks Use either method. By default, all VLANs in an MST • Method 1: region are mapped to MSTI 0 (the instance instance-id vlan CIST). Configure the vlan-id-list VLAN-to-instance mapping Not required if the device is • Method 2: table.
Page 61: Configuring Rrpp Nodes
Step Command Remarks interface view or Layer 2 interface-number aggregate interface view. By default, the link type of an interface is access. Configure the link type of the port link-type trunk For more information about the command, interface as trunk. see Layer 2—LAN Switching Command Reference.
Page 62: Activating An Rrpp Domain
Specifying an edge node When you configure an edge node, you must configure the primary ring before configuring the subrings. To specify an edge node: Step Command Remarks Enter system view. system-view Enter RRPP domain rrpp domain domain-id view. Specify the current ring ring-id node-mode { master | device as a master node transit } [ primary-port interface-type...
Page 63: Configuring Rrpp Timers
To activate an RRPP domain: Step Command Remarks Enter system view. system-view Enable RRPP. rrpp enable By default, RRPP is disabled. Enter RRPP domain view. rrpp domain domain-id Enable the specified RRPP By default, an RRPP ring is ring ring-id enable ring.
Page 64: Displaying And Maintaining Rrpp
Step Command Remarks Enter system view. system-view Create an RRPP ring group By default, no RRPP ring group is and enter RRPP ring group rrpp ring-group ring-group-id created. view. Assign the specified subrings By default, no subrings are domain domain-id ring ring-id-list to the RRPP ring group.
Page 65 Figure 19 Network diagram Configuration procedure Configure Device A: # Create VLANs 1 through 30. <DeviceA> system-view [DeviceA] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet...
Page 66 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceA-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceA-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device A as the master node of primary ring 1, with Ten-GigabitEthernet 1/0/1 as the primary port and Ten-GigabitEthernet 1/0/2 as the secondary port.
Page 67: Intersecting Ring Configuration Example
# Configure Device B as the transit node of primary ring 1, with Ten-GigabitEthernet 1/0/1 as the primary port and Ten-GigabitEthernet 1/0/2 as the secondary port. Enable ring 1. [DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port ten-gigabitethernet 1/0/1 secondary-port ten-gigabitethernet 1/0/2 level 0 [DeviceB-rrpp-domain1] ring 1 enable [DeviceB-rrpp-domain1] quit # Enable RRPP.
Page 68 Figure 20 Network diagram Domain 1 Device B XGE1/0/1 XGE1/0/1 Edge node Device A Master node XGE1/0/3 XGE1/0/2 XGE1/0/2 XGE1/0/1 Device E Ring 1 Ring 2 Master node XGE1/0/2 XGE1/0/2 XGE1/0/1 Device D XGE1/0/3 Transit node XGE1/0/2 Device C XGE1/0/1 Assistant edge node Configuration procedure Configure Device A:...
Page 69 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceA-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceA-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device A as the master node of primary ring 1, with Ten-GigabitEthernet 1/0/1 as the primary port and Ten-GigabitEthernet 1/0/2 as the secondary port.
Page 70 [DeviceB-Ten-GigabitEthernet1/0/3] quit # Create RRPP domain 1. [DeviceB] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceB-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceB-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device B as a transit node of primary ring 1, with Ten-GigabitEthernet 1/0/1 as the primary port and Ten-GigabitEthernet 1/0/2 as the secondary port.
Page 71 # Configure Ten-GigabitEthernet 1/0/3 in the same way Ten-GigabitEthernet 1/0/1 is configured. [DeviceC] interface ten-gigabitethernet 1/0/3 [DeviceC-Ten-GigabitEthernet1/0/3] link-delay 0 [DeviceC-Ten-GigabitEthernet1/0/3] undo stp enable [DeviceC-Ten-GigabitEthernet1/0/3] port link-type trunk [DeviceC-Ten-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceC-Ten-GigabitEthernet1/0/3] quit # Create RRPP domain 1. [DeviceC] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.
Page 72 # Configure Ten-GigabitEthernet 1/0/2 in the same way Ten-GigabitEthernet 1/0/1 is configured. [DeviceD] interface ten-gigabitethernet 1/0/2 [DeviceD-Ten-GigabitEthernet1/0/2] link-delay 0 [DeviceD-Ten-GigabitEthernet1/0/2] undo stp enable [DeviceD-Ten-GigabitEthernet1/0/2] port link-type trunk [DeviceD-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-Ten-GigabitEthernet1/0/2] quit # Create RRPP domain 1. [DeviceD] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.
Page 73: Dual-Homed Rings Configuration Example
[DeviceE-Ten-GigabitEthernet1/0/2] port link-type trunk [DeviceE-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceE-Ten-GigabitEthernet1/0/2] quit # Create RRPP domain 1. [DeviceE] rrpp domain 1 # Configure VLAN 4092 as the primary control VLAN of RRPP domain 1. [DeviceE-rrpp-domain1] control-vlan 4092 # Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1. [DeviceE-rrpp-domain1] protected-vlan reference-instance 1 # Configure Device E as the master node of subring 2, with Ten-GigabitEthernet 1/0/1 as the primary port and Ten-GigabitEthernet 1/0/2 as the secondary port.
Page 74 Figure 21 Network diagram Configuration procedure Configure Device A: # Create VLANs 1 through 30. <DeviceA> system-view [DeviceA] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet...
Page 75 [DeviceA-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-Ten-GigabitEthernet1/0/2] quit # Configure Ten-GigabitEthernet 1/0/3 in the same way Ten-GigabitEthernet 1/0/1 is configured. [DeviceA] interface ten-gigabitethernet 1/0/3 [DeviceA-Ten-GigabitEthernet1/0/3] link-delay 0 [DeviceA-Ten-GigabitEthernet1/0/3] undo stp enable [DeviceA-Ten-GigabitEthernet1/0/3] port link-type trunk [DeviceA-Ten-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceA-Ten-GigabitEthernet1/0/3] quit # Configure Ten-GigabitEthernet 1/0/4 in the same way Ten-GigabitEthernet 1/0/1 is configured.
Page 76 [DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet 1/0/1. [DeviceB] interface ten-gigabitethernet 1/0/1 [DeviceB-Ten-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port. [DeviceB-Ten-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceB-Ten-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30.
Page 77 # Configure Device B as the assistant edge node of subring 2, with Ten-GigabitEthernet 1/0/4 as the edge port. Enable subring 2. [DeviceB-rrpp-domain1] ring 2 node-mode assistant-edge edge-port ten-gigabitethernet 1/0/4 [DeviceB-rrpp-domain1] ring 2 enable # Configure Device B as the assistant edge node of subring 3, with Ten-GigabitEthernet 1/0/3 as the edge port.
Page 78 [DeviceC-Ten-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceC-Ten-GigabitEthernet1/0/3] quit # Configure Ten-GigabitEthernet 1/0/4 in the same way Ten-GigabitEthernet 1/0/1 is configured. [DeviceC] interface ten-gigabitethernet 1/0/4 [DeviceC-Ten-GigabitEthernet1/0/4] link-delay 0 [DeviceC-Ten-GigabitEthernet1/0/4] undo stp enable [DeviceC-Ten-GigabitEthernet1/0/4] port link-type trunk [DeviceC-Ten-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30 [DeviceC-Ten-GigabitEthernet1/0/4] quit # Create RRPP domain 1.
Page 79 # Disable the spanning tree feature on the port. [DeviceD-Ten-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceD-Ten-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30. [DeviceD-Ten-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-Ten-GigabitEthernet1/0/1] quit # Configure Ten-GigabitEthernet 1/0/2 in the same way Ten-GigabitEthernet 1/0/1 is configured.
Page 80 [DeviceD-rrpp-domain1] ring 5 enable [DeviceD-rrpp-domain1] quit # Enable RRPP. [DeviceD] rrpp enable Configure Device E: # Create VLANs 1 through 30. <DeviceE> system-view [DeviceE] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceE] stp region-configuration [DeviceE-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration.
Page 81 Configure Device F: # Create VLANs 1 through 30. <DeviceF> system-view [DeviceF] vlan 1 to 30 # Map these VLANs to MSTI 1. [DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceF-mst-region] active region-configuration [DeviceF-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet 1/0/1.
Page 82 # Map these VLANs to MSTI 1. [DeviceG] stp region-configuration [DeviceG-mst-region] instance 1 vlan 1 to 30 # Activate the MST region configuration. [DeviceG-mst-region] active region-configuration [DeviceG-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet 1/0/1.
Page 83: Load-Balanced Intersecting-Ring Configuration Example
[DeviceH-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet 1/0/1. [DeviceH] interface ten-gigabitethernet 1/0/1 [DeviceH-Ten-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port. [DeviceH-Ten-GigabitEthernet1/0/1] undo stp enable # Configure the port as a trunk port. [DeviceH-Ten-GigabitEthernet1/0/1] port link-type trunk # Assign the port to VLANs 1 through 30.
Page 84 • Device A, Device B, Device C, Device D, and Device E form RRPP domain 2. VLAN 105 is the primary control VLAN of the RRPP domain. Device A is the master node of the primary ring, Ring 1. Device D is the transit node of Ring 1. Device E is the master node of the subring Ring 2.
Page 85 [DeviceA-Ten-GigabitEthernet1/0/1] port link-type trunk # Remove the port from VLAN 1, and assign it to VLANs 11 and 12. [DeviceA-Ten-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceA-Ten-GigabitEthernet1/0/1] port trunk permit vlan 11 12 # Configure VLAN 11 as the default VLAN. [DeviceA-Ten-GigabitEthernet1/0/1] port trunk pvid vlan 11 [DeviceA-Ten-GigabitEthernet1/0/1] quit # Configure Ten-GigabitEthernet 1/0/2 in the same way Ten-GigabitEthernet 1/0/1 is...
Page 86 [DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 11 [DeviceB-mst-region] instance 2 vlan 12 # Activate the MST region configuration. [DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet 1/0/1. [DeviceB] interface ten-gigabitethernet 1/0/1 [DeviceB-Ten-GigabitEthernet1/0/1] link-delay 0 # Disable the spanning tree feature on the port.
Page 87 # Disable the spanning tree feature on the port. [DeviceB-Ten-GigabitEthernet1/0/4] undo stp enable # Configure the port as a trunk port. [DeviceB-Ten-GigabitEthernet1/0/4] port link-type trunk # Remove the port from VLAN 1, and assign it to VLAN 11. [DeviceB-Ten-GigabitEthernet1/0/4] undo port trunk permit vlan 1 [DeviceB-Ten-GigabitEthernet1/0/4] port trunk permit vlan 11 # Configure VLAN 11 as the default VLAN.
Page 88 # Create VLANs 11 and 12. <DeviceC> system-view [DeviceC] vlan 11 to 12 # Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2. [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 11 [DeviceC-mst-region] instance 2 vlan 12 # Activate the MST region configuration. [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet...
Page 89 # Set the physical state change suppression interval to 0 seconds on Ten-GigabitEthernet 1/0/4. [DeviceC] interface ten-gigabitethernet 1/0/4 [DeviceC-Ten-GigabitEthernet1/0/4] link-delay 0 # Disable the spanning tree feature on the port. [DeviceC-Ten-GigabitEthernet1/0/4] undo stp enable # Configure the port as a trunk port. [DeviceC-Ten-GigabitEthernet1/0/4] port link-type trunk # Remove the port from VLAN 1, and assign it to VLAN 11.
Page 90 # Enable RRPP. [DeviceC] rrpp enable Configure Device D: # Create VLANs 11 and 12. <DeviceD> system-view [DeviceD] vlan 11 to 12 # Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2. [DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 11 [DeviceD-mst-region] instance 2 vlan 12 # Activate the MST region configuration.
Page 91 [DeviceD-rrpp-domain1] ring 1 enable [DeviceD-rrpp-domain1] quit # Create RRPP domain 2. [DeviceD] rrpp domain 2 # Configure VLAN 105 as the primary control VLAN of RRPP domain 2. [DeviceD-rrpp-domain2] control-vlan 105 # Configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2. [DeviceD-rrpp-domain2] protected-vlan reference-instance 2 # Configure Device D as the transit node of primary ring 1 in RRPP domain 2, with Ten-GigabitEthernet 1/0/1 as the primary port and Ten-GigabitEthernet 1/0/2 as the secondary...
Page 92 [DeviceE-Ten-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceE-Ten-GigabitEthernet1/0/2] port trunk permit vlan 12 [DeviceE-Ten-GigabitEthernet1/0/2] port trunk pvid vlan 12 [DeviceE-Ten-GigabitEthernet1/0/2] quit # Create RRPP domain 2. [DeviceE] rrpp domain 2 # Configure VLAN 105 as the primary control VLAN of RRPP domain 2. [DeviceE-rrpp-domain2] control-vlan 105 # Configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.
Page 93: Troubleshooting Rrpp
[DeviceF-Ten-GigabitEthernet1/0/2] undo stp enable [DeviceF-Ten-GigabitEthernet1/0/2] port link-type trunk [DeviceF-Ten-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceF-Ten-GigabitEthernet1/0/2] port trunk permit vlan 11 [DeviceF-Ten-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceF-Ten-GigabitEthernet1/0/2] quit # Create RRPP domain 1. [DeviceF] rrpp domain 1 # Configure VLAN 100 as the primary control VLAN of RRPP domain 1. [DeviceF-rrpp-domain1] control-vlan 100 # Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.
Page 94 Solution • Use the display rrpp brief command to determine whether RRPP is enabled for all nodes. If it is not, use the rrpp enable command and the ring enable command to enable RRPP and RRPP rings for all nodes. •...
Page 95: Configuring Smart Link
Configuring Smart Link Overview To avoid single-point failures and guarantee network reliability, downstream devices are typically dual-homed to upstream devices, as shown in Figure Figure 23 Dual uplink network diagram To remove network loops on a dual-homed network, you can use a spanning tree protocol or the Rapid Ring Protection Protocol (RRPP).
Page 96: Terminology
Terminology Smart link group A smart link group consists of only two member ports: the primary and the secondary ports. Only one port is active for forwarding at a time, and the other port is blocked and in standby state. When link failure occurs on the active port due to port shutdown or the presence of unidirectional link, the standby port becomes active and takes over, and the original active port transits to the blocked state.
Page 97: Smart Link Collaboration Mechanisms
Topology change Link switchover can outdate the MAC address forwarding entries and ARP/ND entries on all devices, so a forwarding entry update mechanism is required to ensure proper transmission. The following update mechanisms are provided: • Uplink traffic-triggered MAC address learning—Update is triggered by uplink traffic. This mechanism is applicable to environments with devices that do not support Smart Link, including devices from other vendors.
Page 98: Smart Link Configuration Task List
Smart Link configuration task list Tasks at a glance Configuring a Smart Link device: • (Required.) Configuring protected VLANs for a smart link group • (Required.) Configuring member ports for a smart link group • (Optional.) Configuring a preemption mode for a smart link group •...
Page 99: Configuring Member Ports For A Smart Link Group
Step Command Remarks • Method 1: All VLANs in an MST region are instance instance-id vlan mapped to CIST (MSTI 0) by Configure the vlan-list default. VLAN-to-instance mapping • Method 2: For more information about the table. vlan-mapping modulo commands, see Layer 2—LAN modulo Switching Command Reference.
Page 100: Configuring A Preemption Mode For A Smart Link Group
Step Command Remarks { primary | secondary } smart link group. smart link group member. Configuring a preemption mode for a smart link group Step Command Remarks Enter system view. system-view Enter smart link group view. smart-link group group-id Configure a preemption preemption mode { role | speed By default, preemption is mode for the smart link...
Page 101: Configuring An Associated Device
Step Command Remarks Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, the collaboration between Smart Link and Track is not configured. Configure the collaboration port smart-link group group-id between Smart Link and The track entry specified in the track track-entry-number Track on the port.
Page 102: Smart Link Configuration Examples
Task Command Display information about the received flush display smart-link flush messages. Display smart link group information. display smart-link group { group-id | all } Clear the statistics about flush messages. reset smart-link statistics Smart Link configuration examples Single smart link group configuration example Network requirements As shown in Figure...
Page 103 # Shut down Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2, disable the spanning tree feature on Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2 separately, configure them as trunk ports, and assign them to VLANs 1 through 30. [DeviceC] interface ten-gigabitethernet 1/0/1 [DeviceC-Ten-GigabitEthernet1/0/1] shutdown [DeviceC-Ten-GigabitEthernet1/0/1] undo stp enable [DeviceC-Ten-GigabitEthernet1/0/1] port link-type trunk [DeviceC-Ten-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-Ten-GigabitEthernet1/0/1] quit...
Page 104: Control Vlan
[DeviceD-Ten-GigabitEthernet1/0/1] port link-type trunk [DeviceD-Ten-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-Ten-GigabitEthernet1/0/1] quit [DeviceD] interface ten-gigabitethernet 1/0/2 [DeviceD-Ten-GigabitEthernet1/0/2] shutdown [DeviceD-Ten-GigabitEthernet1/0/2] undo stp enable [DeviceD-Ten-GigabitEthernet1/0/2] port link-type trunk [DeviceD-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-Ten-GigabitEthernet1/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs.
Page 105 # Configure Ten-GigabitEthernet 1/0/3 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. [DeviceB] interface ten-gigabitethernet 1/0/3 [DeviceB-Ten-GigabitEthernet1/0/3] port link-type trunk [DeviceB-Ten-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceB-Ten-GigabitEthernet1/0/3] undo stp enable...
Page 106: Multiple Smart Link Groups Load Sharing Configuration Example
[DeviceA-Ten-GigabitEthernet1/0/1] smart-link flush enable control-vlan 10 20 [DeviceA-Ten-GigabitEthernet1/0/1] quit [DeviceA] interface ten-gigabitethernet 1/0/2 [DeviceA-Ten-GigabitEthernet1/0/2] port link-type trunk [DeviceA-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-Ten-GigabitEthernet1/0/2] smart-link flush enable control-vlan 10 20 [DeviceA-Ten-GigabitEthernet1/0/2] quit Verifying the configuration Use the display smart-link group command to display the smart link group configuration on a device.
Page 107 Figure 25 Network diagram Configuration procedure Configure Device C: # Create VLAN 1 through VLAN 200, map VLANs 1 through 100 to MSTI 1, and VLANs 101 through 200 to MSTI 2, and activate MST region configuration. <DeviceC> system-view [DeviceC] vlan 1 to 200 [DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 100 [DeviceC-mst-region] instance 2 vlan 101 to 200...
Page 108 # 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-group1] flush enable control-vlan 10 [DeviceC-smlk-group1] quit # Create smart link group 2, and configure all VLANs mapped to MSTI 2 as the protected VLANs for smart link group 2.
Page 109 [DeviceD] vlan 1 to 200 # Configure Ten-GigabitEthernet 1/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. [DeviceD] interface ten-gigabitethernet 1/0/1 [DeviceD-Ten-GigabitEthernet1/0/1] port link-type trunk [DeviceD-Ten-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200 [DeviceD-Ten-GigabitEthernet1/0/1] smart-link flush enable control-vlan 10 110...
Page 110: Smart Link And Track Collaboration Configuration Example
----------------------------------------------------------------------------- XGE1/0/1 PRIMARY ACTIVE 16:45:20 2014/04/21 XGE1/0/2 SECONDARY STANDBY 1 16:37:20 2014/04/21 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...
Page 111 Figure 26 Network diagram Configuration procedure Configure Device A: # Create VLAN 1 through VLAN 200. <DeviceA> system-view [DeviceA] vlan 1 to 200 # Configure Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/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 Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2.
Page 112 [DeviceA-Ten-GigabitEthernet1/0/1] cfd cc service-instance 1 mep 1002 enable [DeviceA-Ten-GigabitEthernet1/0/1] quit # Create service instance 2 in which the MA name is based on the VLAN ID in MD_A and configure the MA to serve VLAN 110. [DeviceA] cfd service-instance 2 ma-id vlan-based md MD_A vlan 110 # Create a MEP list in service instance 2, create outward-facing MEP 1002, and enable CCM sending in service instance 2 on Ten-GigabitEthernet 1/0/2.
Page 113 [DeviceC-Ten-GigabitEthernet1/0/1] port link-type trunk [DeviceC-Ten-GigabitEthernet1/0/1] port trunk permit vlan 1 to 200 [DeviceC-Ten-GigabitEthernet1/0/1] quit [DeviceC] interface ten-gigabitethernet 1/0/2 [DeviceC-Ten-GigabitEthernet1/0/2] shutdown [DeviceC-Ten-GigabitEthernet1/0/2] undo stp enable [DeviceC-Ten-GigabitEthernet1/0/2] port link-type trunk [DeviceC-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 200 [DeviceC-Ten-GigabitEthernet1/0/2] quit # Create smart link group 1, and configure all VLANs mapped to MSTI 1 as the protected VLANs for smart link group 1.
Page 114 # Create service instance 2 in which the MA name is based on the VLAN ID in MD_A and configure the MA to serve VLAN 110. [DeviceC] cfd service-instance 2 ma-id vlan-based md MD_A vlan 110 # Create a MEP list in service instance 2. Create outward-facing MEP 2001. Enable CCM sending in service instance 2 on Ten-GigabitEthernet 1/0/2.
Page 115 Verifying the configuration Suppose the optical fiber between Device A and Device B fails. You can use the display smart-link group command to display the smart link group configuration on a device. # Display the smart link group configuration on Device C. [DeviceC] display smart-link group all Smart link group 1 information: Device ID...
Page 116: Configuring Monitor Link
Configuring Monitor Link Overview Monitor Link associates the state of downlink interfaces with the state of uplink interfaces in a monitor link group. When Monitor Link shuts down the downlink interfaces because of an uplink failure, the downstream device changes connectivity to another link. Figure 27 Monitor Link application scenario A monitor link group contains uplink and downlink interfaces.
Page 117: Configuration Restrictions And Guidelines
Configuration restrictions and guidelines Follow these restrictions and guidelines when you configure Monitor Link: • Do not manually shut down or bring up the downlink interfaces in a monitor link group. • To avoid frequent state changes of downlink interfaces in the event that uplink interfaces in the monitor link group flap, you can configure a switchover delay.
Page 118: In Monitor Link Group View
• Member ports of Layer 2 aggregation groups • S-channel interfaces and S-channel aggregate interfaces Follow these guidelines when you configure monitor link group member interfaces: • To avoid undesired down/up state changes on the downlink interfaces, configure uplink interfaces before you configure downlink interfaces. •...
Page 119: Displaying And Maintaining Monitor Link
Displaying and maintaining Monitor Link Execute the display command in any view: Task Command Display monitor link group information. display monitor-link group { group-id | all } Monitor Link configuration example Network requirements As shown in Figure • Device C is a Smart Link device, and Device A, Device B, and Device D are associated devices. Traffic of VLANs 1 through 30 on Device C is dual-uplinked to Device A through a smart link group.
Page 120 [DeviceC-Ten-GigabitEthernet1/0/1] shutdown # Disable the spanning tree feature on the interface. [DeviceC-Ten-GigabitEthernet1/0/1] undo stp enable # Configure the interface as a trunk port. [DeviceC-Ten-GigabitEthernet1/0/1] port link-type trunk # Assign the interface to VLANs 1 through 30. [DeviceC-Ten-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-Ten-GigabitEthernet1/0/1] quit # Configure Ten-GigabitEthernet 1/0/2 in the same way Ten-GigabitEthernet 1/0/1 is configured.
Page 121 [DeviceA] interface ten-gigabitethernet 1/0/2 [DeviceA-Ten-GigabitEthernet1/0/2] port link-type trunk [DeviceA-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-Ten-GigabitEthernet1/0/2] smart-link flush enable [DeviceA-Ten-GigabitEthernet1/0/2] quit Configure Device B: # Create VLANs 1 through 30. <DeviceB> system-view [DeviceB] vlan 1 to 30 # Configure Ten-GigabitEthernet 1/0/1 as a trunk port. [DeviceB] interface ten-gigabitethernet 1/0/1 [DeviceB-Ten-GigabitEthernet1/0/1] port link-type trunk # Assign the interface to VLANs 1 through 30.
Page 122 [DeviceD] interface ten-gigabitethernet 1/0/2 [DeviceD-Ten-GigabitEthernet1/0/2] undo stp enable # Configure the interface as a trunk port. [DeviceD-Ten-GigabitEthernet1/0/2] port link-type trunk # Assign the interface to VLANs 1 through 30. [DeviceD-Ten-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 # Enable flush message receiving on the interface. [DeviceD-Ten-GigabitEthernet1/0/2] smart-link flush enable [DeviceD-Ten-GigabitEthernet1/0/2] quit # Create monitor link group 1.
Page 123: Configuring Vrrp
Configuring VRRP The term "interface" in this chapter collectively refers to VLAN interfaces. VRRP cannot be configured on member ports of aggregation groups. Overview Typically, you can configure a default gateway for every host on a LAN. All packets destined for other networks are sent through the default gateway.
Page 124: Vrrp Standard Mode
VRRP has two versions: VRRPv2 and VRRPv3. VRRPv2 supports IPv4 VRRP. VRRPv3 supports IPv4 VRRP and IPv6 VRRP. VRRP standard mode In VRRP standard mode, only the master in the VRRP group can provide gateway service. When the master fails, the backup routers elect a new master to take over for nonstop gateway service. Figure 30 VRRP networking As shown in Figure...
Page 125: Authentication Method
Authentication method To avoid attacks from unauthorized users, VRRP member routers add authentication keys in VRRP packets to authenticate one another. VRRP provides the following authentication methods: • Simple authentication The sender fills an authentication key into the VRRP packet, and the receiver compares the received authentication key with its local authentication key.
Page 126: Vrrp Tracking
• If the backup does not receive any VRRP advertisement when the timer (3 × advertisement interval + Skew_Time) expires, it becomes the master. • If the backup receives a VRRP advertisement with a greater or the same priority within the timer (3 ×...
Page 127 Figure 31 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 subnet.
Page 128: Vrrp Load Balancing Mode
• VRRP group 3—Router C is the master. Router A and Router B are the backups. To implement load sharing among Router A, Router B, and Router C, perform the following tasks: • Configure the virtual IP addresses of VRRP group 1, 2, and 3 as default gateway IP addresses for hosts on the subnet.
Page 129: Virtual Forwarder
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, and returns the virtual MAC address of Router B in response to the ARP request from Host B.
Page 130 virtual MAC address in the VRRP group and forwards packets that are sent to this virtual MAC address. VFs are created on routers in a VRRP group, as follows: The master assigns virtual MAC addresses to all routers in the VRRP group. Each member router creates a VF for this MAC address and becomes the owner of this VF.
Page 131: Protocols And Standards
Figure 36 shows the VF table on each router in the VRRP group and how the VFs back up one another. The master, Router A, assigns virtual MAC addresses 000f-e2ff-0011, 000f-e2ff-0012, and 000f-e2ff-0013 to itself, Router B, and Router C; and each router creates VF 1, VF 2, and VF 3, respectively, for the virtual MAC addresses.
Page 132: Configuring Ipv4 Vrrp
Configuring IPv4 VRRP This section describes how to configure IPv4 VRRP. IPv4 VRRP configuration task list Tasks at a glance Remarks (Required.) Specifying an IPv4 VRRP operating mode (Optional.) Specifying the IPv4 VRRP version (Required.) Creating a VRRP group and assigning a virtual IP address (Optional.) Configuring the router priority, preemptive mode, and tracking function...
Page 133: Creating A Vrrp Group And Assigning A Virtual Ip Address
Step Command Remarks Specify the version of vrrp version version-number By default, VRRPv3 is used. VRRP. Creating a VRRP group and assigning a virtual IP address A VRRP group can operate correctly after you create it and assign at least one virtual IP address to it. You can configure multiple virtual IP addresses for the VRRP group on an interface that connects to multiple subnets for router backup on different subnets.
Page 134: Configuring Ipv4 Vrrp Packet Attributes
Configuration guidelines • The running priority of an IP address owner is always 255, and you do not need to configure it. An IP address owner always operates in preemptive mode. • If you configure the vrrp vrid track priority reduced or vrrp vrid track switchover command on an IP address owner, the configuration does not take effect until the router becomes a non IP address owner.
Page 135: Configuring Vf Tracking
Step Command Remarks Configure the authentication mode and authentication key vrrp vrid virtual-router-id By default, authentication is for an IPv4 VRRP group to authentication-mode { md5 | disabled. send and receive VRRP simple } { cipher | plain } key packets.
Page 136: Enabling Snmp Notifications For Vrrp
Step Command Remarks interface interface-type Enter interface view. interface-number vrrp vrid virtual-router-id track track-entry-number Configure the VFs in a VRRP { forwarder-switchover By default, the VF tracking group to monitor a track member-ip ip-address | priority function is not configured. entry.
Page 137: Configuring Ipv6 Vrrp
Task Command groups. [ vrid virtual-router-id ] ] Clear statistics for IPv4 VRRP reset vrrp statistics [ interface interface-type interface-number [ vrid groups. virtual-router-id ] ] Configuring IPv6 VRRP This section describes how to configure IPv6 VRRP. IPv6 VRRP configuration task list Tasks at a glance Remarks (Required.)
Page 138: Creating A Vrrp Group And Assigning A Virtual Ipv6 Address
Creating a VRRP group and assigning a virtual IPv6 address A VRRP group can work correctly after you create it and assign at least one virtual IPv6 address for it. You can configure multiple virtual IPv6 addresses for the VRRP group on an interface that connects to multiple subnets for router backup.
Page 139: Configuring Vf Tracking
• If you configure the vrrp ipv6 vrid track priority reduced or vrrp ipv6 vrid track switchover command on an IP address owner, the configuration does not take effect until the router becomes a non IP address owner. • When the track entry changes from Negative to Positive or Notready, the router automatically restores its priority or the failed master router becomes the master again.
Page 140: Configuring Ipv6 Vrrp Packet Attributes
Step Command Remarks interface interface-type Enter interface view. interface-number vrrp ipv6 vrid virtual-router-id track track-entry-number { forwarder-switchover Configure the VFs in a VRRP member-ip ipv6-address | By default, the VF tracking group to monitor a track priority reduced function is not configured. entry.
Page 141: Disabling An Ipv6 Vrrp Group
Disabling an IPv6 VRRP group You can temporarily disable an IPv6 VRRP group. After being disabled, the VRRP group stays in initialized state, and its configurations remain unchanged. You can change the configuration of a VRRP group when it is disabled. Your changes take effect when you enable the VRRP group again. To disable an IPv6 VRRP group: Step Command...
Page 142 Figure 37 Network diagram Configuration procedure Configure Switch A: # Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port ten-gigabitethernet 1/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 10.1.1.1 255.255.255.0 # Create VRRP group 1 on VLAN-interface 2, and set its virtual IP address to 10.1.1.111. [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.111 # Assign Switch A a higher priority than Switch B in VRRP group 1, so Switch A can become the master.
Page 143 [SwitchB-Vlan-interface2] vrrp vrid 1 preempt-mode delay 500 Verify the configuration: # Ping Host B from Host A. (Details not shown.) # Display detailed information about VRRP group 1 on Switch A. [SwitchA-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 1 Interface Vlan-interface2...
Page 144: Multiple Vrrp Groups Configuration Example
Master IP : 10.1.1.2 The output shows that when Switch A fails, Switch B takes over to forward packets from Host A to Host B. # Recover the link between Host A and Switch A, and display detailed information about VRRP group 1 on Switch A.
Page 145 # Configure VLAN 2. <SwitchA> system-view [SwitchA] vlan 2 [SwitchA-vlan2] port ten-gigabitethernet 1/0/5 [SwitchA-vlan2] quit [SwitchA] interface vlan-interface 2 [SwitchA-Vlan-interface2] ip address 10.1.1.1 255.255.255.128 # Create VRRP group 1, and set its virtual IP address to 10.1.1.100. [SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.100 # Assign Switch A a higher priority than Switch B in VRRP group 1, so Switch A can become the master in the group.
Page 146 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 : 10.1.1.100 Virtual MAC : 0000-5e00-0101...
Page 147: Vrrp Load Balancing Configuration Example
VRRP load balancing configuration example Network requirements Switch A, Switch B, and Switch C form a load-balanced VRRP group and use the virtual IP address 10.1.1.1/24 to provide gateway service for subnet 10.1.1.0/24, as shown in Figure Configure VFs on Switch A, Switch B, and Switch C to monitor their respective VLAN-interface 3. When the interface on any one of them fails, the weights of the VFs on the problematic switch decrease so another AVF can take over.
Page 148 # Configure Switch A to operate in preemptive mode, so it can become the master whenever it operates correctly. Set the preemption delay to 500 centiseconds to avoid frequent status switchover. [SwitchA-Vlan-interface2] vrrp vrid 1 preempt-mode delay 500 [SwitchA-Vlan-interface2] quit # Create track entry 1 to monitor the upstream link status of VLAN-interface 3.
Page 149 [SwitchC-Vlan-interface2] ip address 10.1.1.4 24 [SwitchC-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.1 # Configure Switch C to operate in preemptive mode, and set the preemption delay to 500 centiseconds. [SwitchC-Vlan-interface2] vrrp vrid 1 preempt-mode delay 500 [SwitchC-Vlan-interface2] quit # Create track entry 1 to monitor the upstream link status of VLAN-interface 3. When the upstream link fails, the traffic entry transits to Negative.
Page 150 Owner ID : 0000-5e01-1105 Priority : 127 Active : 10.1.1.4 Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 # Display detailed information about VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode : Load Balance Total number of virtual routers : 1...
Page 151 Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 500 Become Master : 401ms left Auth Type : None Virtual IP...
Page 152 Virtual IP : 10.1.1.1 Member IP List : 10.1.1.2 (Local, Master) 10.1.1.3 (Backup) 10.1.1.4 (Backup) Forwarder Information: 3 Forwarders 0 Active Config Weight : 255 Running Weight : 5 Forwarder 01 State : Initialize Virtual MAC : 000f-e2ff-0011 (Owner) Owner ID : 0000-5e01-1101 Priority Active...
Page 153 Virtual MAC : 000f-e2ff-0011 (Take Over) Owner ID : 0000-5e01-1101 Priority : 85 Active : local Forwarder 02 State : Listening Virtual MAC : 000f-e2ff-0012 (Learnt) Owner ID : 0000-5e01-1103 Priority : 85 Active : 10.1.1.3 Forwarder 03 State : Active Virtual MAC : 000f-e2ff-0013 (Owner) Owner ID...
Page 154 State : Active Virtual MAC : 000f-e2ff-0013 (Owner) Owner ID : 0000-5e01-1105 Priority : 255 Active : local Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 The output shows that when the timeout timer expires, the VF for virtual MAC address 000f-e2ff-0011 is removed, and no longer forwards the packets destined for the MAC address.
Page 155: Ipv6 Vrrp Configuration Examples
IPv6 VRRP configuration examples Single VRRP group configuration example Network requirements Switch A and Switch B form a VRRP group, and use the virtual IP addresses 1::10/64 and FE80::10 to provide gateway service for the subnet where Host A resides, as shown in Figure Host A learns 1::10/64 as its default gateway from RA messages sent by the switches.
Page 156 # Enable Switch A to send RA messages, so Host A can learn the default gateway address. [SwitchA-Vlan-interface2] undo ipv6 nd ra halt Configure Switch B: # Configure VLAN 2. <SwitchB> system-view [SwitchB] vlan 2 [SwitchB-vlan2] port ten-gigabitethernet 1/0/5 [SwitchB-vlan2] quit [SwitchB] interface vlan-interface 2 [SwitchB-Vlan-interface2] ipv6 address fe80::2 link-local [SwitchB-Vlan-interface2] ipv6 address 1::2 64...
Page 157: Multiple Vrrp Groups Configuration Example
Virtual IP : FE80::10 1::10 Master IP : FE80::1 The output shows that Switch A is operating as the master in VRRP group 1 to forward packets from Host A to Host B. # Disconnect the link between Host A and Switch A, and verify that Host A can still ping Host B. (Details not shown.) # Display detailed information about VRRP group 1 on Switch B.
Page 158 virtual IPv6 addresses 2::10/64 and FE90::10 to provide gateway service for hosts in VLAN 3, as shown in Figure Hosts in VLAN 2 learn 1::10/64 as their default gateway, and hosts in VLAN 3 learn 2::10/64 as their default gateway from RA messages sent by the switches. Assign Switch A a higher priority than Switch B in VRRP group 1 but a lower priority in VRRP group 2 to distribute the traffic from VLAN 2 and VLAN 3 between the two switches.
Page 159 [SwitchA-vlan3] quit [SwitchA] interface vlan-interface 3 [SwitchA-Vlan-interface3] ipv6 address fe90::1 link-local [SwitchA-Vlan-interface3] ipv6 address 2::1 64 # Create VRRP group 2, and set its virtual IPv6 addresses to FE90::10 and 2::10. [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip fe90::10 link-local [SwitchA-Vlan-interface3] vrrp ipv6 vrid 2 virtual-ip 2::10 # Enable Switch A to send RA messages, so hosts in VLAN 3 can learn the default gateway address.
Page 160 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 : FE80::10 1::10 Virtual MAC : 0000-5e00-0201 Master IP : FE80::1 Interface Vlan-interface3 VRID...
Page 161: Vrrp Load Balancing Configuration Example
VRRP load balancing configuration example Network requirements Switch A, Switch B, and Switch C form a load balanced VRRP group and use the virtual IPv6 addresses FE80::10 and 1::10 to provide gateway service for subnet 1::/64, as shown in Figure Hosts on subnet 1::/64 learn 1::10 as their default gateway from RA messages sent by the switches.
Page 162 # Assign Switch A the highest priority in VRRP group 1, so Switch A can become the master. [SwitchA-Vlan-interface2] vrrp ipv6 vrid 1 priority 120 # Configure Switch A to operate in preemptive mode, so it can become the master whenever it operates correctly.
Page 163 # Configure VLAN 2. <SwitchC> system-view [SwitchC] vlan 2 [SwitchC-vlan2] port ten-gigabitethernet 1/0/5 [SwitchC-vlan2] quit # Configure VRRP to operate in load balancing mode. [SwitchC] vrrp ipv6 mode load-balance # Create VRRP group 1, and set its virtual IPv6 addresses to FE80::10 and 1::10. [SwitchC] interface vlan-interface 2 [SwitchC-Vlan-interface2] ipv6 address fe80::3 link-local [SwitchC-Vlan-interface2] ipv6 address 1::3 64...
Page 164 Forwarder 01 State : Active Virtual MAC : 000f-e2ff-4011 (Owner) Owner ID : 0000-5e01-1101 Priority : 255 Active : local Forwarder 02 State : Listening Virtual MAC : 000f-e2ff-4012 (Learnt) Owner ID : 0000-5e01-1103 Priority : 127 Active : FE80::2 Forwarder 03 State : Listening...
Page 165 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 State : Positive Weight Reduced : 250 # Display detailed information about VRRP group 1 on Switch C.
Page 166 Priority : 255 Active : local Forwarder Weight Track Information: Track Object State : Positive Weight Reduced : 250 The output shows that Switch A is the master in VRRP group 1, and each of the three switches has one AVF and two LVFs. # Disconnect the link of VLAN-interface 3 on Switch A and display detailed information about VRRP group 1 on Switch A.
Page 167 IPv6 Virtual Router Information: Running Mode : Load Balance Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 500...
Page 168 VRID Adver Timer : 100 Admin Status : Up State : Backup Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 500 Become Master : 400ms left Auth Type : None Virtual IP : FE80::10 1::10 Member IP List : FE80::3 (Local, Backup) FE80::1 (Master)
Page 169: Troubleshooting Vrrp
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 State : Positive...
Page 170: Fast Vrrp State Flapping
If multiple masters coexist for a longer period, it might be because the masters cannot receive advertisements from each other, or because the received advertisements are illegitimate. Solution Ping between these masters, and do the following checks: • If the ping fails, examine network connectivity. •...
Page 171: Configuring Bfd
Configuring BFD The term "interface" in this chapter refers to Layer 3 interfaces, including VLAN interfaces. The following commands can be configured in Layer 2 aggregate interface view: • bfd authentication-mode • bfd detect-multiplier • bfd min-receive-interval • bfd min-transmit-interval For more information about configuring BFD on Layer 2 aggregate interfaces, see Layer 2—LAN Switching Configuration Guide.
Page 172: Bfd Session Modes And Operating Modes
BFD session modes and operating modes BFD sessions use the following types of packets: • Echo packets—Encapsulated into UDP packets with port number 3785. • Control packets—Encapsulated into UDP packets with port number 3784 for single-hop detection or port number 4784 for multihop detection. Echo packet mode The local end of the link sends echo packets to establish BFD sessions and monitor link status.
Page 173: Protocols And Standards
• Track. For more information, see "Configuring Track." • IP fast reroute (FRR). IP FRR is supported by BGP, OSPF, RIP, IS-IS and static routing. For more information, see Layer 3—IP Routing Configuration Guide. • Link aggregation. For more information, see Layer 2—LAN Switching Configuration Guide. Protocols and standards •...
Page 174: Configuring Control Packet Mode
Configuring control packet mode To configure control packet mode for single-hop detection: Step Command Remarks Enter system view. system-view By default, active is specified. To establish a session for BFD Specify the mode for bfd session init-mode { active | MAD, the system always operates establishing a BFD session.
Page 175: Configuring A Bfd Template
Step Command Remarks bfd multi-hop Configure the authentication authentication-mode { m-md5 | By default, no authentication is mode for multihop BFD m-sha1 | md5 | sha1 | simple } performed. control packets. key-id { cipher cipher-string | plain plain-string } Set the destination port bfd multi-hop destination-port number for multihop BFD...
Page 176 Task Command display bfd session [ discriminator value | Display BFD session information. verbose ] Clear BFD session statistics. reset bfd session statistics...
Page 177: Configuring Track
Configuring Track Overview The Track module works between application modules and detection modules, as shown in Figure 43. It shields the differences between various detection modules from application modules. Collaboration is enabled when you associate the Track module with a detection module and an application module, and it operates as follows: The detection module probes specific objects such as interface status, link status, network reachability, and network performance, and informs the Track module of detection results.
Page 178: Collaboration Application Example
• CFD. • Interface management. Collaboration between the Track module and an application module The following application modules can be associated with the Track module: • VRRP. • Static routing. • Smart Link. When configuring a track entry for an application module, you can set a notification delay to avoid immediate notification of status changes.
Page 179: Associating The Track Module With A Detection Module
Tasks at a glance • Associating Track with VRRP • Associating Track with static routing • Associating Track with Smart Link Associating the Track module with a detection module Associating Track with NQA NQA supports multiple operation types to analyze network performance and service quality. For example, an NQA operation can periodically detect whether a destination is reachable, or whether a TCP connection can be established.
Page 180: Associating Track With Cfd
Step Command Remarks Enter system view. system-view No track entry is created by default. track track-entry-number bfd echo Create a track entry, interface interface-type interface-number Do not configure the associate it with a BFD remote ip remote-ip local ip local-ip virtual IP address of a session.
Page 181: Associating The Track Module With An Application Module
Step Command Remarks • Associate Track with the interface management module to monitor the link status of an interface: track track-entry-number interface interface-type interface-number [ delay { negative negative-time | positive positive-time } * ] Create a track entry, and •...
Page 182: Associating Track With Static Routing
The AVF automatically restores its weight. The failed master router becomes the master again. The failed AVF becomes active again. • You can associate a nonexistent track entry with a VRRP group or VF. The association takes effect only after you create the track entry. Associating Track with VRRP Step Command...
Page 183: Associating Track With Smart Link
• In static routing-Track-NQA collaboration, you must configure the same VPN instance name for the NQA operation and the next hop of the static route. Otherwise, the accessibility detection cannot operate correctly. • 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.
Page 184: Track Configuration Examples
Track configuration examples VRRP-Track-NQA collaboration configuration example Network requirements As shown in Figure • Host A requires access to Host B. The default gateway of Host A is 10.1.1.10/24. • Switch A and Switch B belong to VRRP group 1. The virtual IP address of VRRP group 1 is 10.1.1.10.
Page 185 [SwitchA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only [SwitchA-nqa-admin-test-icmp-echo] quit # Start the NQA operation. [SwitchA] nqa schedule admin test start-time now lifetime forever On Switch A, configure track entry 1, and associate it with reaction entry 1 of the NQA operation.
Page 186 Interface Vlan-interface2 VRID Adver Timer : 500 Admin Status : Up State : Master Config Pri : 110 Running Pri : 110 Preempt Mode : Yes Delay Time : 500 Auth Type : Simple : ****** Virtual IP : 10.1.1.10 Virtual MAC : 0000-5e00-0101 Master IP...
Page 187: Configuring Bfd For A Vrrp Backup To Monitor The Master
Running Mode : Standard Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 500 Admin Status : Up State : Master Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time : 500 Auth Type : Simple : ******...
Page 188 Figure 45 Network diagram Internet Virtual router Switch A Switch B Virtual IP address: Master Backup 192.168.0.10 Vlan-int2 Vlan-int2 192.168.0.101/24 192.168.0.102/24 L2 switch BFD probe packets VRRP packets Configuration procedure Create VLANs and assign ports to them. Configure the IP address of each VLAN interface as shown in Figure 45.
Page 189 Verifying the configuration # Display detailed information about VRRP group 1 on Switch A. <SwitchA> display vrrp verbose IPv4 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up State...
Page 190: Configuring Bfd For The Vrrp Master To Monitor The Uplinks
<SwitchB> terminal monitor <SwitchB> debugging vrrp fsm <SwitchB> debugging bfd ntfy # When Switch A fails, the following output is displayed on Switch B. *Dec 17 14:44:34:142 2014 SwitchB BFD/7/DEBUG: Notify application:TRACK State:DOWN *Dec 17 14:44:34:144 2014 SwitchB VRRP4/7/FSM: IPv4 Vlan-interface2 | Virtual Router 1 : Backup --> Master reason: The status of the tracked object changed # Display detailed information about the VRRP group on Switch B.
Page 191 Figure 46 Network diagram Internet Master Backup uplink device uplink device Vlan-int3 1.1.1.2/24 Uplink Uplink Vlan-int3 1.1.1.1/24 Switch A Virtual router Switch B Master Virtual IP address: Backup 192.168.0.10 Vlan-int2 Vlan-int2 192.168.0.101/24 192.168.0.102/24 L2 switch BFD probe packets VRRP packets Configuration procedure Create VLANs and assign ports to them.
Page 192 [SwitchB-Vlan-interface2] return Verifying the configuration # Display detailed information about the VRRP group on Switch A. <SwitchA> display vrrp verbose IPv4 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 1 Interface Vlan-interface2 VRID Adver Timer : 100 Admin Status : Up...
Page 193 <SwitchA> display track 1 Track ID: 1 State: Negative Duration: 0 days 0 hours 0 minutes 32 seconds Notification delay: Positive 0, Negative 0 (in seconds) Tracked object: BFD session mode: Echo Outgoing interface: Vlan-interface2 VPN instance name: - Remote IP: 1.1.1.2 Local IP: 1.1.1.1 # Display detailed information about VRRP group 1 on Switch A.
Page 194: Static Routing-Track-Nqa Collaboration Configuration Example
Static routing-Track-NQA collaboration configuration example Network requirements As shown in Figure • Switch A is the default gateway of the hosts in subnet 20.1.1.0/24. • Switch D is the default gateway of the hosts in subnet 30.1.1.0/24. • Hosts in the two subnets communicate with each other through static routes. To ensure network availability, configure route backup and static routing-Track-NQA collaboration on Switch A and Switch D as follows: •...
Page 195 [SwitchA] ip route-static 10.2.1.4 24 10.1.1.2 # Create an NQA operation with the administrator admin and the operation tag test. [SwitchA] nqa entry admin test # Configure the operation type as ICMP echo. [SwitchA-nqa-admin-test] type icmp-echo # Configure the destination address of the operation as 10.2.1.4 and the next hop address as 10.1.1.2.
Page 196 [SwitchD-nqa-admin-test-icmp-echo] destination ip 10.1.1.1 [SwitchD-nqa-admin-test-icmp-echo] next-hop 10.2.1.2 # Configure the ICMP echo operation to repeat at an interval of 100 milliseconds. [SwitchD-nqa-admin-test-icmp-echo] frequency 100 # Configure reaction entry 1, specifying that five consecutive probe failures trigger the Track module. [SwitchD-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only [SwitchD-nqa-admin-test-icmp-echo] quit # Start the NQA operation.
Page 197 [SwitchA] display track all Track ID: 1 State: Negative Duration: 0 days 0 hours 0 minutes 32 seconds Notification delay: Positive 0, Negative 0 (in seconds) Tracked object: NQA entry: admin test Reaction: 1 The output shows that the status of the track entry is Negative, indicating that the NQA operation has failed and the master route is unavailable.
Page 198: Static Routing-Track-Bfd Collaboration Configuration Example
Reply from 20.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms Reply from 20.1.1.1: bytes=56 Sequence=4 ttl=254 time=1 ms Reply from 20.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms --- Ping statistics for 20.1.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.00% packet loss round-trip min/avg/max/std-dev = 1/1/2/1 ms Static routing-Track-BFD collaboration configuration example Network requirements...
Page 199 # 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 to verify the connectivity between Switch A and Switch B. [SwitchA] track 1 bfd echo interface vlan-interface 2 remote ip 10.2.1.2 local ip 10.2.1.1 Configure Switch B: # Configure a static route to 20.1.1.0/24, with the next hop 10.2.1.1 and the default priority 60,...
Page 200 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 Direct 0 127.0.0.1 InLoop0 30.1.1.0/24 Static 60 10.2.1.2 Vlan2 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 The output shows that Switch A forwards packets to 30.1.1.0/24 through Switch B. The master static route has taken effect.
Page 201: Vrrp-Track-Interface Management Collaboration Configuration Example
Ping 30.1.1.1: 56 data bytes, press CTRL_C to break Reply from 30.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms Reply from 30.1.1.1: bytes=56 Sequence=2 ttl=254 time=1 ms Reply from 30.1.1.1: bytes=56 Sequence=3 ttl=254 time=1 ms Reply from 30.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms Reply from 30.1.1.1: bytes=56 Sequence=5 ttl=254 time=1 ms --- Ping statistics for 30.1.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.00% packet loss...
Page 202 Figure 49 Network diagram Configuration procedure Create VLANs and assign ports to them. Configure the IP address of each VLAN interface as shown in Figure 49. (Details not shown.) Configure Switch A: # Configure track entry 1 and associate it with the link status of the uplink interface VLAN-interface 3.
Page 203 Virtual IP : 10.1.1.10 Virtual MAC : 0000-5e00-0101 Master IP : 10.1.1.1 VRRP Track Information: Track Object State : Positive Pri Reduced : 30 # Display detailed information about VRRP group 1 on Switch B. [SwitchB-Vlan-interface2] display vrrp verbose IPv4 Virtual Router Information: Running Mode : Standard Total number of virtual routers : 1...
Page 204: Smart Link-Track-Cfd Collaboration Configuration Example
VRID Adver Timer : 100 Admin Status : Up State : Master Config Pri : 100 Running Pri : 100 Preempt Mode : Yes Delay Time Auth Type : None Virtual IP : 10.1.1.10 Virtual MAC : 0000-5e00-0101 Master IP : 10.1.1.2 The output shows that Switch A becomes the backup, and Switch B becomes the master.
Page 205: Configuring Process Placement
Configuring process placement Overview Process placement enables placing processes to specific CPUs (also called nodes) in your system for optimal distribution of CPU and memory resources. Process A process comprises a set of codes and provides specific functionality. For example, an AAA process provides AAA functions.
Page 206: Configuration Restrictions And Guidelines
• A process runs at the location where it ran the last time and does not move to any other location during startup or operation. • The addition of a new node does not impact current active processes. A new active process selects one node with sufficient CPU and memory resources.
Page 207: Configuring Process Placement Policy
Configuring process placement policy Configuring a location affinity Step Command Remarks Enter system view. system-view Settings in default • Enter default placement process view: placement process view placement program default take effect for all Enter placement process • processes. Settings in Enter placement process view: view.
Page 208: Configuring A Process Affinity
Configuring a process affinity Step Command Remarks Enter system view. system-view • Enter default placement process view: Settings in default placement placement program default process view take effect for all • Enter placement process Enter placement process processes. Settings in placement view.
Page 209: Displaying Process Placement
Displaying process placement Execute display commands in any view. Task Command display placement policy program { program-name | Display process placement policy information. all | default } Display the location of a process. display placement program { program-name | all } Display the running processes on a specific display placement location { slot slot-number [ cpu location.
Page 210: Document Conventions And Icons
Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.
Page 211: Network Topology Icons
Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Page 212: Support And Other Resources
Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...
Page 213: Websites
For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
Page 214 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
Page 215: Index
Index A B C D E F H I L M N P R S T V W Configuring errored frame period event detection,6 Configuring errored frame seconds event An error prompt is displayed,163 detection,7 Associating Track with BFD,173 Configuring errored symbol event detection,5 Associating Track with CFD,174...
Page 216 Enabling SNMP notifications for VRRP,130 Rejecting the Ethernet OAM remote loopback request from a remote port,9 Enabling the receiving of flush messages,95 Remote support,207 Enabling the sending of flush messages,94 Router priority in a VRRP group,118 Ethernet OAMPDUs,1 RRPP timers,47 RRPPDUs,46 Fast VRRP state flapping,164...

This manual is also suitable for:

Flexfabric 5940 series

HPE FlexFabric 5700 Series Configuration Manual

Configuring Ethernet OAM

Configuring CFD

Configuring DLDP

Configuring RRPP

Configuring Smart Link

Configuring Monitor Link

Configuring VRRP

Configuring BFD

Configuring Track

Configuring Process Placement

Document Conventions and Icons

Support and Other Resources

Index

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for HPE FlexFabric 5700 Series

Summary of Contents for HPE FlexFabric 5700 Series

This manual is also suitable for:

Table of Contents