HPE FlexNetwork 5510 HI Series Layer 3 - Ip Routing Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. FlexNetwork 5510 HI Series
  6. Layer 3 - ip routing configuration manual

HPE FlexNetwork 5510 HI Series Layer 3 - Ip Routing Configuration Manual

Hide thumbs Also See for FlexNetwork 5510 HI Series:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
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
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual , Installation Manual
HPE FlexNetwork 5510 HI Switch Series
Layer 3—IP Routing

Configuration Guide

Part number: 5200-0077a
Software version: Release 11xx
Document version: 6W101-20161221

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FlexNetwork 5510 HI Series and is the answer not in the manual?

Questions and answers

Related Manuals for HPE FlexNetwork 5510 HI Series

Summary of Contents for HPE FlexNetwork 5510 HI Series

  • Page 1: Configuration Guide

    HPE FlexNetwork 5510 HI Switch Series Layer 3—IP Routing Configuration Guide Part number: 5200-0077a Software version: Release 11xx Document version: 6W101-20161221...
  • Page 2 © Copyright 2015, 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 basic IP routing ············································································ 1   Routing table ······················································································································································ 1   Dynamic routing protocols ································································································································· 2   Route preference ··············································································································································· 2   Load sharing ······················································································································································ 3   Route backup ····················································································································································· 3   Route recursion ·················································································································································· 3   Route redistribution ············································································································································ 3  ...
  • Page 4 Configuring the maximum number of ECMP routes ················································································· 33   Enabling zero field check on incoming RIPv1 messages ········································································· 34   Enabling source IP address check on incoming RIP updates ·································································· 34   Configuring RIPv2 message authentication ····························································································· 34   Specifying a RIP neighbor ························································································································...
  • Page 5 Configuring OSPF preference ·················································································································· 77   Configuring OSPF route redistribution ····································································································· 78   Advertising a host route ··························································································································· 79   Tuning and optimizing OSPF networks ············································································································ 79   Configuration prerequisites ······················································································································ 79   Configuring OSPF timers ························································································································· 79   Specifying LSA transmission delay ·········································································································· 80  ...
  • Page 6 IS-IS PDUs ············································································································································· 129   Protocols and standards ························································································································ 131   IS-IS configuration task list ···························································································································· 131   Configuring basic IS-IS ·································································································································· 132   Configuration prerequisites ···················································································································· 132   Enabling IS-IS ········································································································································ 132   Configuring the IS level and circuit level ································································································ 133  ...
  • Page 7 BGP speaker and BGP peer ·················································································································· 178   BGP message types ······························································································································ 178   BGP path attributes ································································································································ 178   BGP route selection ······························································································································· 182   BGP route advertisement rules ·············································································································· 182   BGP load balancing ······························································································································· 182   Settlements for problems in large-scale BGP networks ········································································· 184  ...
  • Page 8 Displaying and maintaining BGP ··················································································································· 254   IPv4 BGP configuration examples ················································································································· 257   Basic BGP configuration example ·········································································································· 257   BGP and IGP route redistribution configuration example ······································································ 261   BGP route summarization configuration example ·················································································· 264   BGP load balancing configuration example ··························································································· 267  ...
  • Page 9 Configuring RIPng route control ····················································································································· 333   Configuring an additional routing metric ································································································· 333   Configuring RIPng route summarization ································································································ 333   Advertising a default route ····················································································································· 334   Configuring received/redistributed route filtering ···················································································· 334   Configuring a preference for RIPng ······································································································· 334  ...
  • Page 10 Triggering OSPFv3 GR ·························································································································· 364   Configuring OSPFv3 NSR ····························································································································· 364   Configuring BFD for OSPFv3 ························································································································· 365   Applying an IPsec profile ······························································································································· 365   Displaying and maintaining OSPFv3 ············································································································· 367   OSPFv3 configuration examples ··················································································································· 368   OSPFv3 stub area configuration example ····························································································· 368  ...
  • Page 11 Displaying and maintaining the routing policy ································································································ 420   Routing policy configuration examples ·········································································································· 420   Routing policy configuration example for IPv4 route redistribution ························································ 420   Routing policy configuration example for IPv6 route redistribution ························································ 423   Document conventions and icons ······························································· 425  ...

  • Page 12: Configuring Basic Ip Routing

    Configuring basic IP routing The term "interface" in this chapter collectively refers to Layer 3 interfaces, including VLAN interfaces and Layer 3 Ethernet interfaces. You can set an Ethernet port as a Layer 3 interface by using the port link-mode route command (see Layer 2—LAN Switching Configuration Guide). IP routing directs IP packet forwarding on routers based on a routing table.

  • Page 13: Dynamic Routing Protocols

    • Pre—Preference of the route. Among routes to the same destination, the route with the highest preference is optimal. • Cost—If multiple routes to a destination have the same preference, the one with the smallest cost is the optimal route. •...

  • Page 14: Load Sharing

    Route type Preference Unicast static route OSPF ASE OSPF NSSA IBGP EBGP Unknown (route from an untrusted source) Load sharing A routing protocol might find multiple optimal equal-cost routes to the same destination. You can use these routes to implement equal-cost multi-path (ECMP) load sharing. Static routing, IPv6 static routing, RIP, RIPng, OSPF, OSPFv3, BGP, IPv6 BGP, IS-IS, and IPv6 IS-IS support ECMP load sharing.

  • Page 15: Configuring The Maximum Lifetime For Routes And Labels In The Rib

    The RIB records extended attributes of each routing protocol and redistribution relationships of different routing protocol extended attributes. Configuring the maximum lifetime for routes and labels in the RIB Perform this task to prevent routes of a certain protocol from being aged out due to slow protocol convergence resulting from a large number of route entries or long GR period.

  • Page 16: Configuring The Maximum Number Of Ecmp Routes

    Step Command Remarks Create a RIB IPv4 address By default, no RIB IPv4 address-family ipv4 family and enter its view. address family is created. Configure the maximum By default, the maximum lifetime for IPv4 routes in the lifetime for routes in the FIB fib lifetime seconds FIB.

  • Page 17: Enabling Support For Ipv6 Routes With Prefixes Longer Than 64 Bits

    Enabling support for IPv6 routes with prefixes longer than 64 bits This feature enables a device to support IPv6 routes with prefixes longer than 64 bits. • Before configuration, the RIB supports a maximum of 32768 IPv4 routes or 16384 IPv6 routes with prefixes no longer than 64 bits.
  • Page 18 Task Command display rib nib [ self-originated ] [ nib-id ] [ verbose ] [ standby slot slot-number ] Display next hop information in the RIB. display rib nib protocol protocol-name [ verbose ] [ standby slot slot-number ] Display next hop information for direct display route-direct nib [ nib-id ] [ verbose ] routes.

  • Page 19: Configuring Static Routing

    Configuring static routing Static routes are manually configured. If a network's topology is simple, you only need to configure static routes for the network to work correctly. Static routes cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually.

  • Page 20: Configuring Bfd For Static Routes

    Configuring BFD for static routes IMPORTANT: Enabling BFD for a flapping route could worsen the situation. BFD provides a general-purpose, standard, medium-, and protocol-independent fast failure detection mechanism. It can uniformly and quickly detect the failures of the bidirectional forwarding paths between two routers for protocols, such as routing protocols and MPLS.

  • Page 21: Single-Hop Echo Mode

    Step Command Remarks • Method 1: ip route-static dest-address { mask-length | mask } { next-hop-address bfd control-packet bfd-source ip-address | vpn-instance d-vpn-instance-name next-hop-address bfd control-packet bfd-source ip-address } [ preference preference-value ] [ tag tag-value ] [ description description-text ] Configure BFD By default, BFD control •...

  • Page 22: Configuring Static Route Frr

    Configuring static route FRR A link or router failure on a path can cause packet loss and even routing loop. Static route fast reroute (FRR) uses BFD to detect failures and enables fast rerouting to minimize the impact of link or node failures.

  • Page 23: Displaying And Maintaining Static Routes

    Step Command Remarks • Method 1: ip route-static dest-address { mask-length | mask } interface-type interface-number [ next-hop-address [ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] ] ] [ permanent ] Configure static route By default, static route FRR • Method 2: FRR.

  • Page 24: Static Route Configuration Examples

    Task Command Display static route next hop display route-static nib [ nib-id ] [ verbose ] information. Display static routing table display route-static routing-table [ vpn-instance information. vpn-instance-name ] [ ip-address { mask-length | mask } ] Static route configuration examples Basic static route configuration example Network requirements As shown in...
  • Page 25 [SwitchA] display ip routing-table protocol static Summary Count : 1 Static Routing table Status : <Active> Summary Count : 1 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/0 Static 60 1.1.4.2 Vlan500 Static Routing table Status : <Inactive> Summary Count : 0 # Display static routes on Switch B.

  • Page 26: Bfd For Static Routes Configuration Example (Direct Next Hop)

    Trace complete. BFD for static routes configuration example (direct next hop) Network requirements Configure the following, as shown in Figure • Configure a static route to subnet 120.1.1.0/24 on Switch A. • Configure a static route to subnet 121.1.1.0/24 on Switch B. •...
  • Page 27 [SwitchA] ip route-static 120.1.1.0 24 vlan-interface 10 12.1.1.2 bfd control-packet [SwitchA] ip route-static 120.1.1.0 24 vlan-interface 11 10.1.1.100 preference 65 [SwitchA] quit # Configure static routes on Switch B and enable BFD control mode for the static route that traverses the Layer 2 switch. <SwitchB>...

  • Page 28: Bfd For Static Routes Configuration Example (Indirect Next Hop)

    Summary Count : 1 Static Routing table Status : <Active> Summary Count : 1 Destination/Mask Proto Cost NextHop Interface 120.1.1.0/24 Static 65 10.1.1.100 Vlan11 Static Routing table Status : <Inactive> Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 11. BFD for static routes configuration example (indirect next hop) Network requirements...
  • Page 29 Table 5 Interface and IP address assignment Device Interface IP address Switch A VLAN-interface 10 12.1.1.1/24 Switch A VLAN-interface 11 10.1.1.102/24 Switch A Loopback 1 1.1.1.9/32 Switch B VLAN-interface 12 11.1.1.1/24 Switch B VLAN-interface 13 13.1.1.1/24 Switch B Loopback 1 2.2.2.9/32 Switch C VLAN-interface 11...
  • Page 30 <SwitchA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr State Holdtime Interface 1.1.1.9 2.2.2.9 2000ms The output shows that the BFD session has been created. # Display the static routes on Switch A.

  • Page 31: Static Route Frr Configuration Example

    Static route FRR configuration example Network requirements As shown in Figure 5, configure static routes on Switch A, Switch B, and Switch C, and configure static route FRR. When Link A becomes unidirectional, traffic can be switched to Link B immediately. Figure 5 Network diagram Table 6 Interface and IP address assignment Device...
  • Page 32 [SwitchA] bfd echo-source-ip 4.4.4.4 [SwitchA] ip route-static 4.4.4.4 32 vlan-interface 200 13.13.13.2 [SwitchA] ip route-static 4.4.4.4 32 vlan-interface 100 12.12.12.2 preference 70 [SwitchA] ip route-static fast-reroute auto # Configure static routes on Switch B, and enable static route FRR. <SwitchB> system-view [SwitchB] bfd echo-source-ip 1.1.1.1 [SwitchB] ip route-static 1.1.1.1 32 vlan-interface 200 13.13.13.1 [SwitchB] ip route-static 1.1.1.1 32 vlan-interface 101 24.24.24.2 preference 70...
  • Page 33 AttrID: 0xffffffff Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 13.13.13.1 Label: NULL RealNextHop: 13.13.13.1 BkLabel: NULL BkNextHop: 24.24.24.2 Tunnel ID: Invalid Interface: Vlan-interface200 BkTunnel ID: Invalid BkInterface: Vlan-interface101...

  • Page 34: Configuring A Default Route

    Configuring a default route A default route is used to forward packets that do not match any specific routing entry in the routing table. Without a default route, packets that do not match any routing entries are discarded. A default route can be configured in either of the following ways: •...

  • Page 35: Configuring Rip

    Configuring RIP Overview Routing Information Protocol (RIP) is a distance-vector IGP suited to small-sized networks. It employs UDP to exchange route information through port 520. RIP uses a hop count to measure the distance to a destination. The hop count from a router to a directly connected network is 0.

  • Page 36: Rip Versions

    RIP versions There are two RIP versions, RIPv1 and RIPv2. RIPv1 is a classful routing protocol. It advertises messages only through broadcast. RIPv1 messages do not carry mask information, so RIPv1 can only recognize natural networks such as Class A, B, and C. For this reason, RIPv1 does not support discontiguous subnets. RIPv2 is a classless routing protocol.

  • Page 37: Configuring Basic Rip

    Tasks at a glance • Enabling split horizon and poison reverse • Configuring the maximum number of ECMP routes • Enabling zero field check on incoming RIPv1 messages • Enabling source IP address check on incoming RIP updates • Configuring RIPv2 message authentication •...

  • Page 38: Controlling Rip Reception And Advertisement On Interfaces

    Enabling RIP on an interface Step Command Remarks Enter system view. system-view Enable RIP and enter RIP rip [ process-id ] [ vpn-instance By default, RIP is disabled. view. vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view. interface-number By default, RIP is disabled on an rip process-id enable...

  • Page 39: Configuring Rip Route Control

    Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] By default, no global version is specified. An interface sends RIPv1 broadcasts, and can Specify a global RIP version. version { 1 | 2 } receive RIPv1 broadcasts and unicasts, and RIPv2 broadcasts, multicasts, and unicasts.

  • Page 40: Configuring Ripv2 Route Summarization

    Configuring RIPv2 route summarization Perform this task to summarize contiguous subnets into a summary network and sends the network to neighbors. The smallest metric among all summarized routes is used as the metric of the summary route. Enabling RIPv2 automatic route summarization Automatic summarization enables RIPv2 to generate a natural network for contiguous subnets.

  • Page 41: Advertising A Default Route

    Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] Disable RIP from receiving By default, RIP receives host undo host-route host routes. routes. Advertising a default route You can advertise a default route on all RIP interfaces in RIP view or on a specific RIP interface in interface view.

  • Page 42: Configuring A Preference For Rip

    Step Command Remarks By default, the filtering of received routes is not filter-policy { acl-number | gateway configured. prefix-list-name | prefix-list Configure the filtering of prefix-list-name [ gateway This command filters received received routes. prefix-list-name ] } import routes. Filtered routes are not [ interface-type interface-number ] installed into the routing table or advertised to neighbors.

  • Page 43: Tuning And Optimizing Rip Networks

    Tuning and optimizing RIP networks Configuration prerequisites Before you tune and optimize RIP networks, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. • Configure basic RIP. Configuring RIP timers You can change the RIP network convergence speed by adjusting the following RIP timers: •...

  • Page 44: Configuring The Maximum Number Of Ecmp Routes

    Enabling split horizon Split horizon disables RIP from sending routes through the interface where the routes were learned to prevent routing loops between adjacent routers. To enable split horizon: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, split horizon is Enable split horizon.

  • Page 45: Enabling Zero Field Check On Incoming Ripv1 Messages

    Enabling zero field check on incoming RIPv1 messages Some fields in the RIPv1 message must be set to zero. These fields are called "zero fields." You can enable zero field check on incoming RIPv1 messages. If a zero field of a message contains a non-zero value, RIP does not process the message.

  • Page 46: Specifying A Rip Neighbor

    Step Command Remarks rip authentication-mode { md5 { rfc2082 { cipher cipher-string | plain plain-string } By default, RIPv2 Configure RIPv2 key-id | rfc2453 { cipher cipher-string | plain authentication is not authentication. plain-string } } | simple { cipher cipher-string | configured.

  • Page 47: Setting The Maximum Length Of Rip Packets

    Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] Specify the interval for sending RIP packets and the By default, an interface sends up maximum number of RIP to three RIP packets every 20 output-delay time count count packets that can be sent at milliseconds.

  • Page 48: Configuring Bfd For Rip

    the router within a GR interval. During this process, the FIB table of the router does not change. After the restart, the router contacts its neighbors to retrieve its FIB. By default, a RIP-enabled device acts as the GR helper. Perform this task on the GR restarter. To configure GR on the GR restarter: Step Command...

  • Page 49: Configuring Bidirectional Control Detection

    This feature applies to RIP neighbors that are directly connected. To configure BFD for RIP (single hop echo detection for a specific destination): Step Command Remarks Enter system view. system-view Configure the source IP By default, no source IP address address of BFD echo is configured for BFD echo bfd echo-source-ip ip-address...

  • Page 50: Configuration Restrictions And Guidelines

    calculates the shortest path based on the new network topology, and forwards packets over that path after network convergence. Configuration restrictions and guidelines • RIP FRR takes effect only for RIP routes learned from directly connected neighbors. • Do not use RIP FRR and BFD for RIP at the same time. Otherwise, FRR might fail to work. •...

  • Page 51: Rip Configuration Examples

    Task Command Display RIP current status and configuration display rip [ process-id ] information. display rip process-id database [ ip-address Display active routes in RIP database. { mask-length | mask } ] display rip process-id interface [ interface-type Display RIP interface information. interface-number ] display rip process-id route [ ip-address Display routing information about a specified RIP...
  • Page 52 [SwitchB-Vlan-interface101] rip 1 enable [SwitchB-Vlan-interface101] quit [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] rip 1 enable [SwitchB-Vlan-interface102] quit # Display the RIP routing table of Switch A. [SwitchA] display rip 1 route Route Flags: R - RIP A - Aging, S - Suppressed, G - Garbage-collect O - Optimal, F - Flush to RIB ---------------------------------------------------------------------------- Peer 1.1.1.2 on Vlan-interface100...
  • Page 53 NOTE: After RIPv2 is configured, RIPv1 routes might still exist in the routing table until they are aged out. # Display the RIP routing table on Switch B. Route Flags: R - RIP A - Aging, S - Suppressed, G - Garbage-collect O - Optimal, F - Flush to RIB ---------------------------------------------------------------------------- Peer 1.1.1.1 on Vlan-interface100...

  • Page 54: Rip Route Redistribution Configuration Example

    Local route Destination/Mask Nexthop Cost Flags 1.1.1.0/24 0.0.0.0 RDOF 10.1.1.0/24 0.0.0.0 RDOF 10.2.1.0/24 0.0.0.0 RDOF RIP route redistribution configuration example Network requirements As shown in Figure 8, Switch B communicates with Switch A through RIP 100 and with Switch C through RIP 200.
  • Page 55 [SwitchC] rip 200 [SwitchC-rip-200] network 12.0.0.0 [SwitchC-rip-200] network 16.0.0.0 [SwitchC-rip-200] version 2 [SwitchC-rip-200] undo summary [SwitchC-rip-200] quit # Display the IP routing table on Switch C. [SwitchC] display ip routing-table Destinations : 13 Routes : 13 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0...

  • Page 56: Rip Interface Additional Metric Configuration Example

    127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 RIP interface additional metric configuration example Network requirements As shown in Figure 9, run RIPv2 on all the interfaces of Switch A, Switch B, Switch C, Switch D, and Switch E.

  • Page 57: Rip Summary Route Advertisement Configuration Example

    <SwitchD> system-view [SwitchD] rip 1 [SwitchD-rip-1] network 1.0.0.0 [SwitchD-rip-1] version 2 [SwitchD-rip-1] undo summary # Configure Switch E. <SwitchE> system-view [SwitchE] rip 1 [SwitchE-rip-1] network 1.0.0.0 [SwitchE-rip-1] version 2 [SwitchE-rip-1] undo summary # Display all active routes in the RIP database on Switch A. [SwitchA] display rip 1 database 1.0.0.0/8, auto-summary 1.1.1.0/24, cost 0, nexthop 1.1.1.1, RIP-interface...
  • Page 58 Figure 10 Network diagram Vlan-int500 Vlan-int200 10.6.1.2/24 10.1.1.1/24 Switch B Vlan-int200 10.1.1.2/24 OSPF Vlan-int600 Vlan-int100 Vlan-int300 10.5.1.2/24 10.2.1.2/24 11.3.1.1/24 Vlan-int100 10.2.1.1/24 Switch C Switch A Vlan-int400 Vlan-int300 11.4.1.2/24 11.3.1.2/24 Switch D Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic OSPF: # Configure Switch A.
  • Page 59 [SwitchD-rip-1] network 11.0.0.0 [SwitchD-rip-1] version 2 [SwitchD-rip-1] undo summary [SwitchD-rip-1] quit # Configure RIP to redistribute routes from OSPF process 1 and direct routes on Switch C. [SwitchC-rip-1] import-route direct [SwitchC-rip-1] import-route ospf 1 [SwitchC-rip-1] quit # Display the IP routing table on Switch D. [SwitchD] display ip routing-table Destinations : 15 Routes : 15...

  • Page 60: Bfd For Rip Configuration Example (Single-Hop Echo Detection For A Directly Connected Neighbor)

    127.0.0.0/32 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 BFD for RIP configuration example (single-hop echo detection for a directly connected neighbor) Network requirements As shown in Figure 11, VLAN-interface 100 of Switch A and Switch C runs RIP process 1. VLAN-interface 200 of Switch A runs RIP process 2.
  • Page 61 [SwitchA-rip-2] version 2 [SwitchA-rip-2] undo summary [SwitchA-rip-2] network 192.168.2.0 [SwitchA-rip-2] quit # Configure Switch B. <SwitchB> system-view [SwitchB] rip 1 [SwitchB-rip-1] version 2 [SwitchB-rip-1] undo summary [SwitchB-rip-1] network 192.168.2.0 [SwitchB-rip-1] network 192.168.3.0 [SwitchB-rip-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] rip 1 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary...

  • Page 62: Bfd For Rip Configuration Example (Single Hop Echo Detection For A Specific Destination)

    Protocol: RIP Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 1 Preference: 100 Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NibID: 0x26000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 192.168.1.2 Flags: 0x1008c OrigNextHop: 192.168.1.2 Label: NULL RealNextHop: 192.168.1.2 BkLabel: NULL BkNextHop: N/A...
  • Page 63 • Enable BFD for RIP on VLAN-interface 100 of Switch A, and specify VLAN-interface 100 of Switch B as the destination. When a unidirectional link occurs between Switch A and Switch B, BFD can quickly detect the link failure and notify RIP. Switch B then deletes the neighbor relationship and the route information learned on VLAN-interface 100.
  • Page 64 [SwitchA-Vlan-interface100] return Configure static routes: # Configure a static route on Switch A. [SwitchA] ip route-static 100.1.1.0 24 null 0 # Configure a static route on Switch C. [SwitchA] ip route-static 100.1.1.0 24 null 0 Verifying the configuration # Display BFD session information on Switch A. <SwitchA>...

  • Page 65: Bfd For Rip Configuration Example (Bidirectional Detection In Bfd Control Packet Mode)

    NibID: 0x12000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 192.168.3.2 Flags: 0x1008c OrigNextHop: 192.168.3.2 Label: NULL RealNextHop: 192.168.3.2 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: vlan-interface 200 BkTunnel ID: Invalid BkInterface: N/A BFD for RIP configuration example (bidirectional detection in BFD control packet mode) Network requirements As shown in Figure...
  • Page 66 Device Interface IP address Switch C VLAN-interface 200 192.168.2.2/24 Switch C VLAN-interface 400 192.168.4.2/24 Switch D VLAN-interface 300 192.168.3.2/24 Switch D VLAN-interface 400 192.168.4.1/24 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic RIP and enable static route redistribution into RIP so Switch A and Switch C have routes to send to each other: # Configure Switch A.
  • Page 67 [SwitchD-rip-1] version 2 [SwitchD-rip-1] undo summary [SwitchD-rip-1] network 192.168.3.0 [SwitchD-rip-1] network 192.168.4.0 Configure BFD parameters: # Configure Switch A. [SwitchA] bfd session init-mode active [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] bfd min-transmit-interval 500 [SwitchA-Vlan-interface100] bfd min-receive-interval 500 [SwitchA-Vlan-interface100] bfd detect-multiplier 7 [SwitchA-Vlan-interface100] quit # Configure Switch C.

  • Page 68: Rip Frr Configuration Example

    NibID: 0x12000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 192.168.2.2 Flags: 0x1008c OrigNextHop: 192.168.2.2 Label: NULL RealNextHop: 192.168.1.2 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: vlan-interface 100 BkTunnel ID: Invalid BkInterface: N/A # Display RIP routes destined for 100.1.1.0/24 on Switch A when the link between Switch B and Switch C fails.
  • Page 69 Device Interface IP address Switch A VLAN-interface 200 13.13.13.1/24 Switch A Loopback 0 1.1.1.1/32 Switch B VLAN-interface 101 24.24.24.4/24 Switch B VLAN-interface 202 13.13.13.2/24 Switch B Loopback 0 4.4.4.4/32 Switch C VLAN-interface 100 12.12.12.2/24 Switch C VLAN-interface 101 24.24.24.2/24 Configuration procedure Configure IP addresses and subnet masks for interfaces on the switches.
  • Page 70 Protocol: RIP Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 1 Preference: 100 Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NibID: 0x26000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 13.13.13.2 Flags: 0x1008c OrigNextHop: 13.13.13.2 Label: NULL RealNextHop: 13.13.13.2 BkLabel: NULL BkNextHop: 12.12.12.2...

  • Page 71: Configuring Ospf

    Configuring OSPF Overview Open Shortest Path First (OSPF) is a link-state IGP developed by the OSPF working group of the IETF. OSPF version 2 is used for IPv4. OSPF refers to OSPFv2 throughout this chapter. OSPF has the following features: •...

  • Page 72: Ospf Areas

    • Network LSA—Type-2 LSA, originated for broadcast and NBMA networks by the designated router, and flooded throughout a single area only. This LSA contains the list of routers connected to the network. • Network Summary LSA—Type-3 LSA, originated by Area Border Routers (ABRs), and flooded throughout the LSA's associated area.
  • Page 73 Backbone area and virtual links Each AS has a backbone area that distributes routing information between non-backbone areas. Routing information between non-backbone areas must be forwarded by the backbone area. OSPF has the following requirements: • All non-backbone areas must maintain connectivity to the backbone area. •...

  • Page 74: Router Types

    routes. It advertises a default route in a Type-3 LSA so that the routers in the area can reach external networks through the default route. NSSA area and totally NSSA area An NSSA area does not import AS external LSAs (Type-5 LSAs) but can import Type-7 LSAs generated by the NSSA ASBR.

  • Page 75: Route Types

    Figure 19 OSPF router types IS-IS ASBR Area 1 Area 4 Backbone router Internal router Area 0 Area 3 Area 2 Route types OSPF prioritizes routes into the following route levels: • Intra-area route. • Inter-area route. • Type-1 external route. •...

  • Page 76: Ospf Network Types

    • Each OSPF router collects LSAs from other routers to compose an LSDB. An LSA describes the network topology around a router, and the LSDB describes the entire network topology of the area. • Each router transforms the LSDB to a weighted directed graph that shows the topology of the area.

  • Page 77: Protocols And Standards

    Figure 20 DR and BDR in a network DR other DR other DR other Physical links Adjacencies NOTE: In OSPF, neighbor and adjacency are different concepts. After startup, OSPF sends a hello packet on each OSPF interface. A receiving router checks parameters in the packet. If the parameters match its own, the receiving router considers the sending router an OSPF neighbor.
  • Page 78 Tasks at a glance (Required.) Enabling OSPF (Optional.) Configuring OSPF areas: • Configuring a stub area • Configuring an NSSA area • Configuring a virtual link (Optional.) Configuring OSPF network types: • Configuring the broadcast network type for an interface •...

  • Page 79: Enabling Ospf

    Tasks at a glance (Optional.) Configuring OSPF GR • Configuring OSPF GR restarter • Configuring OSPF GR helper • Triggering OSPF GR (Optional.) Configuring OSPF NSR (Optional.) Configuring BFD for OSPF (Optional.) Configuring OSPF FRR Enabling OSPF Enable OSPF before you perform other OSPF configuration tasks. Configuration prerequisites Configure the link layer protocol and IP addresses for interfaces to ensure IP connectivity between neighboring nodes.

  • Page 80: Enabling Ospf On An Interface

    Step Command Remarks By default, no global router ID is configured. If no global router ID is configured, the highest loopback interface IP address, if (Optional.) Configure a router id router-id any, is used as the router ID. If no loopback global router ID.

  • Page 81: Configuring A Stub Area

    Configuring a stub area You can configure a non-backbone area at an AS edge as a stub area. To do so, execute the stub command on all routers attached to the area. The routing table size is reduced because Type-5 LSAs will not be flooded within the stub area.

  • Page 82: Configuring A Virtual Link

    Step Command Remarks nssa [ default-route-advertise [ cost cost | nssa-only | route-policy route-policy-name | type type ] * | no-import-route | Configure the area as an By default, no area is configured as no-summary | suppress-fa | NSSA area. an NSSA area.

  • Page 83: Configuration Prerequisites

    • An NBMA network must be fully meshed. OSPF requires that an NBMA network be fully meshed. If a network is partially meshed, change the network type to P2MP. • If a router on an NBMA network has only one neighbor, you can change the network type to P2P to save costs.

  • Page 84: Configuring The P2Mp Network Type For An Interface

    Step Command Remarks By default, no neighbor is specified. The priority configured with this command indicates whether a neighbor has the election right or not. If you configure the router priority for a neighbor as 0, the local router Specify a neighbor and its peer ip-address [ dr-priority determines the neighbor has no router priority.

  • Page 85: Configuring Ospf Route Control

    Configuring OSPF route control This section describes how to control the advertisement and reception of OSPF routing information, as well as route redistribution from other protocols. Configuration prerequisites Before you configure OSPF route control, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. •...

  • Page 86: Configuring Received Ospf Route Filtering

    To configure route summarization on an ASBR: Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id Enter OSPF view. | vpn-instance vpn-instance-name ]* asbr-summary ip-address Configure ASBR route { mask-length | mask } [ cost cost | By default, route summarization is summarization.

  • Page 87: Configuring Type-3 Lsa Filtering

    Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * filter-policy { acl-number [ gateway Configure OSPF to prefix-list-name ] | gateway prefix-list-name By default, OSPF accepts all filter routes | prefix-list prefix-list-name [ gateway routes calculated using received calculated using...

  • Page 88: Configuring The Maximum Number Of Ecmp Routes

    To configure a bandwidth reference value: Step Command Remarks Enter system view. system-view ospf [ process-id | router-id Enter OSPF view. router-id | vpn-instance vpn-instance-name ] * Configure a bandwidth The default setting is 100 Mbps. bandwidth-reference value reference value. Configuring the maximum number of ECMP routes Perform this task to implement load sharing over ECMP routes.

  • Page 89: Configuring Ospf Route Redistribution

    Configuring OSPF route redistribution On a router running OSPF and other routing protocols, you can configure OSPF to redistribute routes from other protocols, such as RIP, IS-IS, BGP, static, and direct, and advertise them in Type-5 LSAs or Type-7 LSAs. In addition, you can configure OSPF to filter redistributed routes so that OSPF advertises only permitted routes.

  • Page 90: Advertising A Host Route

    Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Configure the default parameters for By default, the cost is 1, the tag redistributed routes default { cost cost | tag tag | type type } * is 1, and the type is Type-2.

  • Page 91: Specifying Lsa Transmission Delay

    To configure OSPF timers: Step Command Remarks Enter system system-view view. Enter interface interface interface-type view. interface-number By default: • The hello interval on P2P and broadcast interfaces is 10 seconds. Specify the hello • The hello interval on P2MP and NBMA ospf timer hello seconds interval.

  • Page 92: Specifying Spf Calculation Interval

    Specifying SPF calculation interval LSDB changes result in SPF calculations. When the topology changes frequently, a large amount of network and router resources are occupied by SPF calculation. You can adjust the SPF calculation interval to reduce the impact. For a stable network, the minimum interval is used. If network changes become frequent, the SPF calculation interval is incremented by the incremental interval ×...

  • Page 93: Disabling Interfaces From Receiving And Sending Ospf Packets

    Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * By default: • The maximum interval is 5 seconds. lsa-generation-interval Configure the LSA maximum-interval [ minimum-interval • The minimum interval is 50 generation interval.

  • Page 94: Configuring Ospf Authentication

    Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * stub-router [ external-lsa By default, the router is not [ max-metric-value ] | include-stub | configured as a stub router. Configure the router as on-startup { seconds | wait-for-bgp a stub router.

  • Page 95: Adding The Interface Mtu Into Dd Packets

    Step Command Remarks • Configure simple authentication: ospf authentication-mode simple { cipher cipher-string | plain By default, no plain-string } Configure interface authentication is authentication mode. • Configure MD5 authentication: configured. ospf authentication-mode { hmac-md5 | md5 } key-id { cipher cipher-string | plain plain-string } Adding the interface MTU into DD packets By default, an OSPF interface adds a value of 0 into the interface MTU field of a DD packet rather...

  • Page 96: Configuring Ospf Exit Overflow Interval

    Configuring OSPF exit overflow interval When the number of LSAs in the LSDB exceeds the upper limit, the LSDB is in an overflow state. To save resources, OSPF does not receive any external LSAs and deletes the external LSAs generated by itself when in this state.

  • Page 97: Configuring Ospf Network Management

    To enable the logging of neighbor state changes: Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Enable the logging of By default, this feature is log-peer-change neighbor state changes. enabled.

  • Page 98: Configuring The Lsu Transmit Rate

    Configuring the LSU transmit rate Sending large numbers of LSU packets affects router performance and consumes too much network bandwidth. You can configure the router to send LSU packets at a proper interval and limit the maximum number of LSU packets sent out of an OSPF interface each time. To configure the LSU transmit rate: Step Command...

  • Page 99: Configuring Prefix Prioritization

    Configuring prefix suppression for an OSPF process Enabling prefix suppression for an OSPF process does not suppress the prefixes of secondary IP addresses, loopback interfaces, and passive interfaces. To suppress the prefixes of loopback and passive interfaces, enable prefix suppression on the interfaces. To configure prefix suppression for an OSPF process: Step Command...

  • Page 100: Configuring The Number Of Ospf Logs

    OSPF PIC applies only to inter-area routes and external routes. Enabling OSPF PIC Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Enable PIC for By default, OSPF PIC is pic [ additional-path-always ] OSPF.

  • Page 101: Configuring Ospf Gr Restarter

    • GR helper—A neighbor of the GR restarter. It helps the GR restarter to complete the GR process. OSPF GR has the following types: • IETF GR—Uses Opaque LSAs to implement GR. • Non-IETF GR—Uses link local signaling (LLS) to advertise GR capability and uses out of band synchronization to synchronize the LSDB.

  • Page 102: Configuring Ospf Gr Helper

    Configuring OSPF GR helper You can configure the IETF or non-IETF OSPF GR helper. Configuring the IETF OSPF GR helper Step Command Remarks Enter system view. system-view ospf [ process-id | router-id Enable OSPF and enter its router-id | vpn-instance view.

  • Page 103: Configuring Ospf Nsr

    Configuring OSPF NSR Nonstop routing (NSR) backs up OSPF link state information from the active process to the standby process. After an active/standby switchover, NSR can complete link state recovery and route regeneration without tearing down adjacencies or impacting forwarding services. NSR does not require the cooperation of neighboring devices to recover routing information, and is used more often than GR.

  • Page 104: Configuring Single-Hop Echo Detection

    Configuring single-hop echo detection Step Command Remarks Enter system view. system-view By default, the source Configure the source address of bfd echo-source-ip address of echo packets is echo packets. ip-address not configured. interface interface-type Enter interface view. interface-number Enable BFD single-hop echo By default, BFD single-hop ospf bfd enable echo detection.

  • Page 105: Configuration Procedure

    Configuration procedure Configuring OSPF FRR to calculate a backup next hop using the LFA algorithm Step Command Remarks Enter system view. system-view Configure the source By default, the source address of bfd echo-source-ip address of echo packets. echo packets is not configured. ip-address interface interface-type Enter interface view.

  • Page 106: Displaying And Maintaining Ospf

    Step Command Remarks Configure the By default, the source IP source IP address address of BFD echo packets bfd echo-source-ip ip-address of BFD echo is not configured. packets. Enter interface interface interface-type interface-number view. Enable BFD for By default, BFD for OSPF ospf primary-path-detect bfd echo OSPF FRR.

  • Page 107: Ospf Configuration Examples

    Task Command Display OSPF interface display ospf [ process-id ] interface [ interface-type interface-number | information. verbose ] Display OSPF route calculation display ospf [ process-id ] event-log { lsa-flush | peer | spf } log information. Display OSPF ASBR route display ospf [ process-id ] asbr-summary [ ip-address { mask-length | summarization information.
  • Page 108 [SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] area 1 [SwitchA-ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.1] quit [SwitchA-ospf-1] quit # Configure Switch B. <SwitchB> system-view [SwitchB] router id 10.3.1.1 [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] area 2 [SwitchB-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.2] quit [SwitchB-ospf-1] quit...
  • Page 109 Neighbor is up for 06:03:59 Authentication Sequence: [ 0 ] Neighbor state change count: 5 BFD status: Disabled Area 0.0.0.1 interface 10.2.1.1(Vlan-interface200)'s neighbors Router ID: 10.4.1.1 Address: 10.2.1.2 GR State: Normal State: Full Mode: Nbr is Master Priority: 1 DR: 10.2.1.1 BDR: 10.2.1.2 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-)

  • Page 110: Ospf Route Redistribution Configuration Example

    Ping 10.4.1.1 (10.4.1.1): 56 data bytes, press CTRL_C to break 56 bytes from 10.4.1.1: icmp_seq=0 ttl=253 time=1.549 ms 56 bytes from 10.4.1.1: icmp_seq=1 ttl=253 time=1.539 ms 56 bytes from 10.4.1.1: icmp_seq=2 ttl=253 time=0.779 ms 56 bytes from 10.4.1.1: icmp_seq=3 ttl=253 time=1.702 ms 56 bytes from 10.4.1.1: icmp_seq=4 ttl=253 time=1.471 ms --- Ping statistics for 10.4.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss...

  • Page 111: Ospf Route Summarization Configuration Example

    OSPF Process 1 with Router ID 10.5.1.1 Routing Table to ABR and ASBR Type Destination Area Cost Nexthop RtType Intra 10.3.1.1 0.0.0.2 10.3.1.1 Inter 10.4.1.1 0.0.0.2 10.3.1.1 ASBR # Display the OSPF routing table on Switch D. <SwitchD> display ospf routing OSPF Process 1 with Router ID 10.5.1.1 Routing Tables Routing for Network...
  • Page 112 Figure 24 Network diagram Vlan-int600 Vlan-int500 10.4.1.1/24 10.3.1.1/24 Vlan-int400 Vlan-int300 10.1.1.1/24 10.2.1.2/24 Switch E Switch D Vlan-int300 Vlan-int400 10.2.1.1/24 10.1.1.2/24 Switch C AS 100 Vlan-int200 11.1.1.2/24 EBGP Vlan-int200 11.1.1.1/24 Switch B Vlan-int100 11.2.1.1/24 Vlan-int100 11.2.1.2/24 AS 200 Switch A Configuration procedure Configure IP addresses for interfaces.
  • Page 113 <SwitchD> system-view [SwitchD] router id 10.3.1.1 [SwitchD] ospf [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] quit # Configure Switch E. <SwitchE> system-view [SwitchE] router id 10.4.1.1 [SwitchE] ospf [SwitchE-ospf-1] area 0 [SwitchE-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchE-ospf-1-area-0.0.0.0] network 10.4.1.0 0.0.0.255 [SwitchE-ospf-1-area-0.0.0.0] quit [SwitchE-ospf-1] quit...

  • Page 114: Ospf Stub Area Configuration Example

    10.1.1.0/24 OSPF 11.2.1.1 Vlan100 10.2.1.0/24 OSPF 11.2.1.1 Vlan100 10.3.1.0/24 OSPF 11.2.1.1 Vlan100 10.4.1.0/24 OSPF 11.2.1.1 Vlan100 11.2.1.0/24 Direct 0 11.2.1.2 Vlan100 11.2.1.0/32 Direct 0 11.2.1.2 Vlan100 11.2.1.2/32 Direct 0 127.0.0.1 InLoop0 11.2.1.255/32 Direct 0 11.2.1.2 Vlan100 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0...
  • Page 115 • Configure Area 1 as a stub area to reduce advertised LSAs without influencing reachability. Figure 25 Network diagram Switch A Switch B Area 0 Vlan-int100 10.1.1.1/24 Vlan-int100 10.1.1.2/24 Vlan-int200 Vlan-int200 10.2.1.1/24 10.3.1.1/24 Vlan-int200 Vlan-int200 Area 1 Area 2 10.3.1.2/24 10.2.1.2/24 Stub ASBR...
  • Page 116 Destination Cost Type NextHop AdvRouter 3.1.2.0/24 Type2 10.2.1.1 10.5.1.1 Total Nets: 6 Intra Area: 2 Inter Area: 3 ASE: 1 NSSA: 0 The output shows that Switch C's routing table contains an AS external route. Configure Area 1 as a stub area: # Configure Switch A.

  • Page 117: Ospf Nssa Area Configuration Example)

    Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 0.0.0.0/0 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 Transit 10.2.1.2 10.4.1.1 0.0.0.1 10.4.1.0/24 Stub 10.4.1.1 10.4.1.1 0.0.0.1 Total Nets: 3 Intra Area: 2 Inter Area: 1 ASE: 0 NSSA: 0 The output shows that inter-area routes are removed, and only one external route (a default route) exists on Switch C.
  • Page 118 [SwitchC] ospf [SwitchC-ospf-1] area 1 [SwitchC-ospf-1-area-0.0.0.1] nssa [SwitchC-ospf-1-area-0.0.0.1] quit [SwitchC-ospf-1] quit # Display OSPF routing information on Switch C. [SwitchC] display ospf routing OSPF Process 1 with Router ID 10.4.1.1 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 Transit 10.2.1.2...

  • Page 119: Ospf Dr Election Configuration Example

    OSPF DR election configuration example Network requirements As shown in Figure • Enable OSPF on Switches A, B, C, and D on the same network. • Configure Switch A as the DR, and configure Switch C as the BDR. Figure 27 Network diagram Configuration procedure Configure IP addresses for interfaces.
  • Page 120 <SwitchD> system-view [SwitchD] router id 4.4.4.4 [SwitchD] ospf [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] quit [SwitchD-ospf-1] return # Display OSPF neighbor information of Switch A. [SwitchA] display ospf peer verbose OSPF Process 1 with Router ID 1.1.1.1 Neighbors Area 0.0.0.0 interface 192.168.1.1(Vlan-interface1)'s neighbors Router ID: 2.2.2.2 Address: 192.168.1.2...
  • Page 121 [SwitchB-Vlan-interface1] ospf dr-priority 0 [SwitchB-Vlan-interface1] quit # Configure Switch C. [SwitchC] interface vlan-interface 1 [SwitchC-Vlan-interface1] ospf dr-priority 2 [SwitchC-Vlan-interface1] quit # Display neighbor information of Switch D. <SwitchD> display ospf peer verbose OSPF Process 1 with Router ID 4.4.4.4 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 Address: 192.168.1.1...
  • Page 122 OSPF Process 1 with Router ID 4.4.4.4 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 Address: 192.168.1.1 GR State: Normal State: Full Mode: Nbr is Slave Priority: 100 DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 39 Neighbor is up for 00:01:40 Authentication Sequence: [ 0 ] BFD status: Disabled...

  • Page 123: Ospf Virtual Link Configuration Example

    IP Address Type State Cost 192.168.1.2 Broadcast DROther 192.168.1.1 192.168.1.3 The interface state DROther means the interface is not the DR or BDR. OSPF virtual link configuration example Network requirements As shown in Figure 28, configure a virtual link between Switch B and Switch C to connect Area 2 to the backbone area.
  • Page 124 [SwitchC–ospf-1-area-0.0.0.2] quit [SwitchC-ospf-1] quit # Configure Switch D. <SwitchD> system-view [SwitchD] ospf 1 router-id 4.4.4.4 [SwitchD-ospf-1] area 2 [SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.2] quit # Display the OSPF routing table on Switch B. [SwitchB] display ospf routing OSPF Process 1 with Router ID 2.2.2.2 Routing Tables Routing for Network Destination...

  • Page 125: Ospf Gr Configuration Example

    OSPF GR configuration example Network requirements As shown in Figure • Switch A, Switch B, and Switch C that belong to the same AS and the same OSPF routing domain are GR capable. • Switch A acts as the non-IETF GR restarter. Switch B and Switch C are the GR helpers, and synchronize their LSDBs with Switch A through OOB communication of GR.
  • Page 126 # Configure Switch A as the non-IETF OSPF GR restarter: enable the link-local signaling capability, the out-of-band re-synchronization capability, and non-IETF GR capability for OSPF process 100. [SwitchA-ospf-100] enable link-local-signaling [SwitchA-ospf-100] enable out-of-band-resynchronization [SwitchA-ospf-100] graceful-restart [SwitchA-ospf-100] return # Configure Switch B as the GR helper: enable the link-local signaling capability and the out-of-band re-synchronization capability for OSPF process 100.

  • Page 127: Ospf Nsr Configuration Example

    OSPF 100 deleted GR wait timer. %Oct 21 15:29:30:920 2011 SwitchA OSPF/5/OSPF_NBR_CHG: OSPF 100 Neighbor 192.1.1.2(Vlan-interface100) from Full to Down. %Oct 21 15:29:30:921 2011 SwitchA OSPF/5/OSPF_NBR_CHG: OSPF 100 Neighbor 192.1.1.3(Vlan-interface100) from Full to Down. %Oct 21 15:29:33:815 2011 SwitchA OSPF/5/OSPF_NBR_CHG: OSPF 100 Neighbor 192.1.1.3(Vlan-interface100) from Loading to Full.
  • Page 128 staticroute eviisis ospf Continue? [y/n]:y Re-optimization of the placement start. You will be notified on completion Re-optimization of the placement complete. Use 'display placement' to view the new placement # During the switchover period, display OSPF neighbors on Switch A to verify the neighbor relationship between Switch A and Switch S.

  • Page 129: Bfd For Ospf Configuration Example

    Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 44.44.44.44/32 Stub 44.44.44.44 4.4.4.1 0.0.0.0 14.14.14.0/24 Transit 14.14.14.1 4.4.4.1 0.0.0.0 22.22.22.22/32 Stub 14.14.14.2 2.2.2.1 0.0.0.0 12.12.12.0/24 Transit 14.14.14.2 2.2.2.1 0.0.0.0 Total Nets: 4 Intra Area: 4 Inter Area: 0 ASE: 0 NSSA: 0 The output shows that when an active/standby switchover occurs on Switch S, the neighbor...
  • Page 130 Device Interface IP address Switch C Vlan-int13 13.1.1.2/24 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Switch A. <SwitchA> system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] network 121.1.1.1 0.0.0.0 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit # Configure Switch B.
  • Page 131 [SwitchB-Vlan-interface10] bfd min-receive-interval 500 [SwitchB-Vlan-interface10] bfd detect-multiplier 6 Verifying the configuration # Display the BFD information on Switch A. <SwitchA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr...

  • Page 132: Ospf Frr Configuration Example

    Flags: 0x1008c OrigNextHop: 10.1.1.100 Label: NULL RealNextHop: 10.1.1.100 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: Vlan-interface11 BkTunnel ID: Invalid BkInterface: N/A The output shows that Switch A communicates with Switch B through VLAN-interface 11. OSPF FRR configuration example Network requirements As shown in Figure 32, Switch A, Switch B, and Switch C reside in the same OSPF domain.
  • Page 133 [SwitchA] ospf 1 [SwitchA-ospf-1] fast-reroute lfa [SwitchA-ospf-1] quit # Configure Switch B. <SwitchB> system-view [SwitchB] bfd echo-source-ip 3.3.3.3 [SwitchB] ospf 1 [SwitchB-ospf-1] fast-reroute lfa [SwitchB-ospf-1] quit (Method 2.) Enable OSPF FRR to designate a backup next hop by using a routing policy. # Configure Switch A.

  • Page 134: Troubleshooting Ospf Configuration

    AttrID: 0xffffffff Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 13.13.13.2 Label: NULL RealNextHop: 13.13.13.2 BkLabel: NULL BkNextHop: 12.12.12.2 Tunnel ID: Invalid Interface: Vlan-interface200 BkTunnel ID: Invalid BkInterface: Vlan-interface100 # Display route 1.1.1.1/32 on Switch B to view the backup next hop information. [SwitchB] display ip routing-table 1.1.1.1 verbose Summary Count : 1 Destination: 1.1.1.1/32...

  • Page 135: Incorrect Routing Information

    If the problem persists, contact Hewlett Packard Enterprise Support. Incorrect routing information Symptom OSPF cannot find routes to other areas. Analysis The backbone area must maintain connectivity to all other areas. If a router connects to more than one area, at least one area must be connected to the backbone. The backbone cannot be configured as a stub area.

  • Page 136: Configuring Is-Is

    Configuring IS-IS Overview Intermediate System-to-Intermediate System (IS-IS) is a dynamic routing protocol designed by the ISO to operate on the connectionless network protocol (CLNP). IS-IS was modified and extended in RFC 1195 by the IETF for application in both TCP/IP and OSI reference models, called "Integrated IS-IS"...

  • Page 137: Net

    Figure 33 NSAP address format Area address The area address comprises the IDP and the HO-DSP of the DSP, which identify the area and the routing domain. Different routing domains cannot have the same area address. Typically, a router only needs one area address, and all nodes in the same area must have the same area address.

  • Page 138: Is-Is Area

    Typically, a router only needs one NET, but it can have a maximum of three NETs for smooth area merging and partitioning. When you configure multiple NETs, make sure the system IDs are the same. IS-IS area IS-IS has a 2-level hierarchy to support large-scale networks. A large-scale routing domain is divided into multiple areas.

  • Page 139: Is-Is Network Types

    backbone in this topology. The backbone comprises all contiguous Level-2 and Level-1-2 routers in different areas. The IS-IS backbone does not need to be a specific area. Figure 35 IS-IS topology 2 Area 1 Area 4 Area 2 L1/L2 L1/L2 Area 3 Both the Level-1 and Level-2 routers use the SPF algorithm to generate the shortest path tree.

  • Page 140: Is-Is Pdus

    As shown in Figure 36, the same level routers on a network, including non-DIS routers, establish adjacency with each other. Figure 36 DIS in the IS-IS broadcast network L1/L2 L1/L2 L2 adjacencies L1 adjacencies The DIS creates and updates pseudonodes, and generates LSPs for the pseudonodes, to describe all routers on the network.
  • Page 141 Type PDU Type Acronym Level-1 Partial Sequence Numbers PDU L1 PSNP Level-2 Partial Sequence Numbers PDU L2 PSNP Hello PDU IS-to-IS hello (IIH) PDUs are used by routers to establish and maintain neighbor relationships. On broadcast networks, Level-1 routers use Level-1 LAN IIHs, and Level-2 routers use Level-2 LAN IIHs. The P2P IIHs are used on point-to-point networks.

  • Page 142: Protocols And Standards

    CLV Code Name PDU Type IP Internal Reachability Information Protocols Supported IIH, LSP IP External Reachability Information L2 LSP Inter-Domain Routing Protocol Information L2 LSP IP Interface Address IIH, LSP Protocols and standards • ISO 10589 ISO IS-IS Routing Protocol •...

  • Page 143: Configuring Basic Is-Is

    Tasks at a glance (Optional.) Tuning and optimizing IS-IS networks: • Specifying the interval for sending IS-IS hello packets • Specifying the IS-IS hello multiplier • Specifying the interval for sending IS-IS CSNP packets • Configuring a DIS priority for an interface •...

  • Page 144: Configuring The Is Level And Circuit Level

    Step Command Remarks Enable an IS-IS process on the By default, no IS-IS process is isis enable [ process-id ] interface. enabled. Configuring the IS level and circuit level Follow these guidelines when you configure the IS level for routers in only one area: •...

  • Page 145: Configuring Is-Is Route Control

    Step Command Remarks By default, the network type of an interface depends on the Configure P2P network type for physical media. The network isis circuit-type p2p an interface. type of a VLAN interface is broadcast. Configuring IS-IS route control Configuration prerequisites Before the configuration, complete the following tasks: •...

  • Page 146: Specifying A Preference For Is-Is

    Step Command Remarks cost-style { narrow | wide | (Optional.) Specify an By default, the IS-IS cost wide-compatible | { compatible | IS-IS cost style. type is narrow. narrow-compatible } [ relax-spf-limit ] } Return to system view. quit Enter interface view. interface interface-type interface-number (Optional.) Specify a cost By default, no cost for the...

  • Page 147: Configuring The Maximum Number Of Ecmp Routes

    Step Command Remarks Configure a preference for preference { preference | route-policy The default setting is IS-IS. route-policy-name } * Configuring the maximum number of ECMP routes Perform this task to implement load sharing over ECMP routes. To configure the maximum number of ECMP routes: Step Command Remarks...

  • Page 148: Configuring Is-Is Route Redistribution

    To advertise a default route: Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] default-route-advertise [ [ level-1 | Advertise a default By default, IS-IS does not level-1-2 | level-2 ] | route-policy route.

  • Page 149: Configuring Is-Is Route Leaking

    Step Command Remarks isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] Filter routes filter-policy { acl-number | prefix-list By default, IS-IS route calculated using prefix-list-name | route-policy filtering is not configured. received LSPs. route-policy-name } import Filtering redistributed routes IS-IS can redistribute routes from other routing protocols or other IS-IS processes, add them to the IS-IS routing table, and advertise them in LSPs.

  • Page 150: Tuning And Optimizing Is-Is Networks

    Tuning and optimizing IS-IS networks Configuration prerequisites Before you tune and optimize IS-IS networks, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. • Enable IS-IS. Specifying the interval for sending IS-IS hello packets If a neighbor does not receive any hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes.

  • Page 151: Specifying The Interval For Sending Is-Is Csnp Packets

    Specifying the interval for sending IS-IS CSNP packets On a broadcast network, perform this task on the DIS that uses CSNP packets to synchronize LSDBs. To specify the interval for sending IS-IS CSNP packets: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 152: Disabling An Interface From Sending/Receiving Is-Is Packets

    Disabling an interface from sending/receiving IS-IS packets After being disabled from sending and receiving hello packets, an interface cannot form any neighbor relationship, but can advertise directly connected networks in LSPs through other interfaces. This can save bandwidth and CPU resources, and ensures that other routers know networks directly connected to the interface.
  • Page 153 Each router needs to refresh its LSPs at a configurable interval and send them to other routers to prevent valid routes from aging out. A smaller refresh interval speeds up network convergence but consumes more bandwidth. When the network topology changes, for example, a neighbor is down or up, or the interface metric, system ID, or area ID is changed, the router generates an LSP after a configurable interval.
  • Page 154 If the IS-IS routers have different interface MTUs, configure the maximum size of generated LSP packets to be smaller than the smallest interface MTU in the area. Without the configuration, the routers must dynamically adjust the LSP packet size to fit the smallest interface MTU, which takes time and affects other services.

  • Page 155: Controlling Spf Calculation Interval

    Controlling SPF calculation interval Based on the LSDB, an IS-IS router uses the SPF algorithm to calculate the shortest path tree with itself being the root, and uses the shortest path tree to determine the next hop to a destination network.

  • Page 156: Configuring System Id To Host Name Mappings

    Step Command Remarks Enter system view. system-view Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] set-overload [ on-startup [ [ start-from-nbr system-id By default, the Set the overload bit. [ timeout1 [ nbr-timeout ] ] ] | timeout2 ] [ allow { external overload bit is not | interlevel } * ] set.

  • Page 157: Enabling The Logging Of Neighbor State Changes

    Step Command Remarks Return to system quit view. interface interface-type Enter interface view. interface-number By default, no DIS name is configured. This command takes effect only on a Configure a DIS router enabled with dynamic system ID isis dis-name symbolic-name name.

  • Page 158: Enhancing Is-Is Network Security

    Notifications are delivered to the SNMP module, which outputs the notifications according to the configured output rules. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide. To configure IS-IS network management: Step Command Remarks Enter system view. system-view By default, MIB is bound to the Bind MIB to an IS-IS...

  • Page 159: Configuring Area Authentication

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number isis authentication-mode { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | By default, no Specify the authentication hmac-sha-512 } | md5 | simple } authentication is mode and password.

  • Page 160: Configuring Is-Is Gr

    Step Command Remarks domain-authentication-mode { gca key-id { hmac-sha-1 | Specify the routing domain hmac-sha-224 | hmac-sha-256 | By default, no routing domain authentication mode and hmac-sha-384 | hmac-sha-512 } authentication is configured. password. | md5 | simple } { cipher cipher-string | plain plain-string } [ ip | osi ] Configuring IS-IS GR...

  • Page 161: Configuring Is-Is Nsr

    Step Command Remarks (Optional.) By default, the T1 timer is 3 seconds and graceful-restart t1 seconds Configure the T1 can expire 10 times. count count timer. (Optional.) Configure the T2 By default, the T2 timer is 60 seconds. graceful-restart t2 seconds timer.

  • Page 162: Configuring Is-Is Frr

    Configuring IS-IS FRR A link or router failure on a path can cause packet loss and routing loop. IS-IS FRR uses BFD to detect failures and enables fast rerouting to minimize the failover time. Figure 39 Network diagram for IS-IS FRR Figure 39, after you enable FRR on Router B, IS-IS automatically calculates or designates a backup next hop when a link failure is detected.

  • Page 163: Configuring Is-Is Frr Using A Routing Policy

    Configuring IS-IS FRR using a routing policy You can use the apply fast-reroute backup-interface command to specify a backup next hop in a routing policy for routes matching specific criteria. You can also perform this task to reference the routing policy for IS-IS FRR. For more information about the apply fast-reroute backup-interface command and routing policy configurations, see "Configuring routing policies."...

  • Page 164: Is-Is Configuration Examples

    Task Command display isis lsdb [ [ level-1 | level-2 ] | local | [ lsp-id lspid | Display IS-IS backup LSDB information. lsp-name lspname ] | verbose ] * [ process-id ] [ standby slot slot-number ] Display IS-IS mesh group configuration display isis mesh-group [ process-id ] information.
  • Page 165 Figure 40 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure IS-IS: # Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B.
  • Page 166 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit # Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] network-entity 20.0000.0000.0004.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 100 [SwitchD-Vlan-interface100] isis enable 1 [SwitchD-Vlan-interface100] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit Verifying the configuration # Display the IS-IS LSDB on each switch to verify the LSPs.
  • Page 167 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload [SwitchC] display isis lsdb Database information for IS-IS(1) --------------------------------- Level-1 Link State Database --------------------------- LSPID Seq Num Checksum Holdtime Length ATT/P/OL -------------------------------------------------------------------------- 0000.0000.0001.00-00 0x00000006 0xdb60 0/0/0 0000.0000.0002.00-00 0x00000008 0xe651 1053 0/0/0 0000.0000.0002.01-00 0x00000005 0xd2b3 1052 0/0/0...
  • Page 168 Route information for IS-IS(1) ------------------------------ Level-1 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 10.1.1.0/24 NULL Vlan100 Direct D/L/- 10.1.2.0/24 NULL Vlan100 10.1.1.1 R/-/- 192.168.0.0/24 NULL Vlan100 10.1.1.1 R/-/- 0.0.0.0/0 NULL Vlan100 10.1.1.1 R/-/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set [SwitchC] display isis route Route information for IS-IS(1) ------------------------------...

  • Page 169: Dis Election Configuration Example

    IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 192.168.0.0/24 NULL Vlan300 Direct D/L/- 10.1.1.0/24 NULL Vlan300 192.168.0.1 R/-/- 10.1.2.0/24 NULL Vlan300 192.168.0.1 R/-/- 172.16.0.0/16 NULL Vlan100 Direct D/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set The output shows that the routing table of Level-1 switches contains a default route with the next hop as the Level-1-2 switch.
  • Page 170 [SwitchB] isis 1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] isis enable 1 [SwitchB-Vlan-interface100] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] is-level level-1 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis enable 1 [SwitchC-Vlan-interface100] quit # Configure Switch D.
  • Page 171 ---------------------------------- Interface: Vlan-interface100 IPv4.State IPv6.State Type Down 1497 L1/L2 No/No # Display information about IS-IS interfaces on Switch C. [SwitchC] display isis interface Interface information for IS-IS(1) ---------------------------------- Interface: Vlan-interface100 IPv4.State IPv6.State Type Down 1497 L1/L2 Yes/No # Display information about IS-IS interfaces on Switch D. [SwitchD] display isis interface Interface information for IS-IS(1) ----------------------------------...
  • Page 172 System Id: 0000.0000.0004 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 30s Type: L2 PRI: 64 # Display information about IS-IS interfaces on Switch A. [SwitchA] display isis interface Interface information for IS-IS(1) ---------------------------------- Interface: Vlan-interface100 IPv4.State IPv6.State Type Down 1497 L1/L2 Yes/Yes...

  • Page 173: Is-Is Route Redistribution Configuration Example

    Interface information for IS-IS(1) ---------------------------------- Interface: Vlan-interface100 IPv4.State IPv6.State Type Down 1497 L1/L2 No/No IS-IS route redistribution configuration example Network requirements As shown in Figure 42, Switch A, Switch B, Switch C, and Switch D reside in the same AS. They use IS-IS to interconnect.
  • Page 174 [SwitchB-Vlan-interface200] isis enable 1 [SwitchB-Vlan-interface200] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis enable 1 [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis enable 1 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit...
  • Page 175 ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 10.1.1.0/24 NULL VLAN100 Direct D/L/- 10.1.2.0/24 NULL VLAN200 Direct D/L/- 192.168.0.0/24 NULL VLAN300 Direct D/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface...

  • Page 176: Is-Is Authentication Configuration Example

    [SwitchD-rip-1] quit [SwitchD] isis 1 [SwitchD–isis-1] import-route rip level-2 # Display IS-IS routing information on Switch C. [SwitchC] display isis route Route information for IS-IS(1) ------------------------------ Level-1 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 10.1.1.0/24 NULL VLAN100 Direct...
  • Page 177 Figure 43 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic IS-IS: # Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B.
  • Page 178 # Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] network-entity 20.0000.0000.0001.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit Configure neighbor relationship authentication between neighbors: # Configure the authentication mode as MD5 and set the plaintext password to eRq on VLAN-interface 100 of Switch A and on VLAN-interface 100 of Switch C.

  • Page 179: Is-Is Gr Configuration Example

    [SwitchD] isis 1 [SwitchD-isis-1] domain-authentication-mode md5 plain 1020Sec IS-IS GR configuration example Network requirements As shown in Figure 44, Switch A, Switch B, and Switch C belong to the same IS-IS routing domain. Figure 44 Network diagram Configuration procedure Configure IP addresses and subnet masks for interfaces. (Details not shown.) Configure IS-IS on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at layer 3 and dynamic route update can be implemented among them with IS-IS.

  • Page 180: Is-Is Nsr Configuration Example

    --------------------------- Total number of interfaces: 1 Number of waiting LSPs: 0 Level-2 restart information --------------------------- Total number of interfaces: 1 Number of waiting LSPs: 0 IS-IS NSR configuration example Network requirements As shown in Figure 45, Switch S, Switch A, and Switch B belong to the same IS-IS routing domain. •...
  • Page 181 track ip6addr ipaddr trange tunnel lagg slsp usr6 fczone ethbase ipcim ip6base ipbase eviisis ifnet isis Continue? [y/n]:y Re-optimization of the placement start. You will be notified on completion Re-optimization of the placement complete. Use 'display placement' to view the new placement # Display IS-IS neighbor information on Switch A.
  • Page 182 Level-1 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 12.12.12.0/24 NULL vlan100 Direct D/L/- 22.22.22.22/32 NULL Loop0 Direct D/-/- 14.14.14.0/32 NULL vlan100 12.12.12.2 R/L/- 44.44.44.44/32 NULL vlan100 12.12.12.2 R/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination...

  • Page 183: Bfd For Is-Is Configuration Example

    14.14.14.0/24 NULL vlan200 Direct D/L/- 44.44.44.44/32 NULL Loop0 Direct D/-/- 12.12.12.0/32 NULL vlan200 14.14.14.4 R/L/- 22.22.22.22/32 NULL vlan200 14.14.14.4 R/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags -------------------------------------------------------------------------------...
  • Page 184 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic IS-IS: # Configure Switch A. <SwitchA> system-view [SwitchA] isis [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface loopback 0 [SwitchA-LoopBack0] isis enable [SwitchA-LoopBack0] quit [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] isis enable [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] isis enable...
  • Page 185 [SwitchA-Vlan-interface10] bfd min-receive-interval 500 [SwitchA-Vlan-interface10] bfd min-transmit-interval 500 [SwitchA-Vlan-interface10] bfd detect-multiplier 7 # Enable BFD and configure BFD parameters on Switch B. [SwitchB] bfd session init-mode active [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] isis bfd enable [SwitchB-Vlan-interface10] bfd min-receive-interval 500 [SwitchB-Vlan-interface10] bfd min-transmit-interval 500 [SwitchB-Vlan-interface10] bfd detect-multiplier 8 [SwitchB-Vlan-interface10] return Verifying the configuration...

  • Page 186: Is-Is Frr Configuration Example

    Destination: 120.1.1.0/24 Protocol: ISIS Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 20 Preference: 10 Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NibID: 0x26000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 10.1.1.100 Label: NULL RealNextHop: 10.1.1.100 BkLabel: NULL...
  • Page 187 [SwitchA] bfd echo-source-ip 2.2.2.2 [SwitchA] isis 1 [SwitchA-isis-1] fast-reroute auto [SwitchA-isis-1] quit # Configure Switch B. <SwitchB> system-view [SwitchB] bfd echo-source-ip 3.3.3.3 [SwitchB] isis 1 [SwitchB-isis-1] fast-reroute auto [SwitchB-isis-1] quit (Method 2.) Enable IS-IS FRR to designate a backup next hop by using a referenced routing policy: # Configure Switch A.
  • Page 188 TableID: 0x2 OrigAs: 0 NibID: 0x26000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 13.13.13.2 Label: NULL RealNextHop: 13.13.13.2 BkLabel: NULL BkNextHop: 12.12.12.2 Tunnel ID: Invalid Interface: Vlan-interface200 BkTunnel ID: Invalid BkInterface: Vlan-interface100 # Display route 1.1.1.1/32 on Switch B to view the backup next hop information. [SwitchB] display ip routing-table 1.1.1.1 verbose Summary Count : 1 Destination: 1.1.1.1/32...

  • Page 189: Configuring Bgp

    Configuring BGP Overview Border Gateway Protocol (BGP) is an exterior gateway protocol (EGP). It is called internal BGP (IBGP) when it runs within an AS and called external BGP (EBGP) when it runs between ASs. The current version in use is BGP-4 (RFC 4271). BGP has the following characteristics: •...
  • Page 190 The ORIGIN attribute specifies the origin of BGP routes. This attribute has the following types: IGP—Has the highest priority. Routes generated in the local AS have the IGP attribute. EGP—Has the second highest priority. Routes obtained through EGP have the EGP attribute.
  • Page 191 When a BGP speaker sends a received route to an EBGP peer, it sets the address of the sending interface as the NEXT_HOP. When a BGP speaker sends a route received from an EBGP peer to an IBGP peer, it does not modify the NEXT_HOP attribute.
  • Page 192 Generally BGP only compares MEDs of routes received from the same AS. You can also use the compare-different-as-med command to force BGP to compare MED values of routes received from different ASs. • LOCAL_PREF The LOCAL_PREF attribute is exchanged between IBGP peers only, and is not advertised to any other AS.

  • Page 193: Bgp Route Selection

    • Extended community attribute To meet new demands, BGP defines the extended community attribute. The extended community attribute has the following advantages over the COMMUNITY attribute: Provides more attribute values by extending the attribute length to eight bytes. Allows for using different types of extended community attributes in different scenarios to enhance route filtering and control and simplify configuration and management.
  • Page 194 • BGP load balancing through route recursion. The next hop of a BGP route may not be directly connected. One of the reasons is next hops in routing information exchanged between IBGP peers are not modified. The BGP router must find the directly-connected next hop through IGP.

  • Page 195: Settlements For Problems In Large-Scale Bgp Networks

    Settlements for problems in large-scale BGP networks You can use the following methods to facilitate management and improve route distribution efficiency on a large-scale BGP network. • Route summarization Route summarization can reduce the BGP routing table size by advertising summary routes rather than more specific routes.
  • Page 196 You can apply a community list or an extended community list to a routing policy for route control. For more information, see "BGP path attributes." • Route reflector IBGP peers must be fully meshed to maintain connectivity. If n routers exist in an AS, the number of IBGP connections is n(n-1)/2.

  • Page 197: Mp-Bgp

    After route reflection is disabled between clients, routes can still be reflected between a client and a non-client. • Confederation Confederation is another method to manage growing IBGP connections in an AS. It splits an AS into multiple sub-ASs. In each sub-AS, IBGP peers are fully meshed. As shown in Figure intra-confederation EBGP connections are established between sub-ASs in AS 200.

  • Page 198: Bgp Configuration Views

    MP-BGP uses these two attributes to advertise feasible and unfeasible routes for different network layer protocols. BGP speakers not supporting MP-BGP ignore updates containing these attributes and do not forward them to its peers. The current MP-BGP implementation supports multiple protocol extensions, including VPN, IPv6, and multicast.

  • Page 199: Protocols And Standards

    View names Ways to enter the views Remarks Configurations in this view apply to <Sysname> system-view L2VPN information and L2VPN [Sysname] bgp 100 peers. BGP L2VPN address family [Sysname-bgp] address-family view For more information about BGP l2vpn l2VPN address family view, see [Sysname-bgp-l2vpn] MPLS Configuration Guide.

  • Page 200: Bgp Configuration Task List

    • RFC 5082, The Generalized TTL Security Mechanism (GTSM) BGP configuration task list In a basic BGP network, you only need to perform the following configurations: • Enable BGP. • Configure BGP peers or peer groups. If you configure a BGP setting at both the peer group and the peer level, the most recent configuration takes effect on the peer.
  • Page 201 Tasks at a glance Remarks (Optional.) Tuning and optimizing BGP networks: • Configuring the keepalive interval and hold time • Configuring the interval for sending updates for the same route • Enabling BGP to establish an EBGP session over multiple hops •...

  • Page 202: Configuring Basic Bgp

    Tasks at a glance Remarks (Optional.) Controlling route distribution and reception: • Configuring BGP route summarization • Advertising optimal routes in the IP routing table • Advertising a default route to a peer or peer group • Limiting routes received from a peer or peer group •...

  • Page 203: Enabling Bgp

    Enabling BGP A router ID is the unique identifier of a BGP router in an AS. • To ensure the uniqueness of a router ID and enhance availability, specify in BGP view the IP address of a local loopback interface as the router ID. •...
  • Page 204 Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Create an IPv4 BGP peer By default, no IPv4 BGP peer is peer ip-address as-number and specify its AS number.

  • Page 205: Configuring Dynamic Bgp Peers

    Step Command Remarks Enable the router to By default, the router cannot exchange IPv6 unicast exchange IPv6 unicast routing peer ipv6-address enable routing information with the information with the peer. specified peer. Configuring dynamic BGP peers This feature enables BGP to establish dynamic BGP peer relationships with devices in a network. BGP accepts connection requests from the network but it does not initiate connection requests to the network.

  • Page 206: Configuring A Bgp Peer Group

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Specify devices in a network as dynamic BGP By default, no dynamic BGP peer peer ipv6-address prefix-length peers and specify an AS is specified.
  • Page 207 Step Command Remarks By default, no peer exists in the peer group. peer ip-address [ mask-length ] Add a peer into the IBGP group group-name [ as-number To use the as-number as-number peer group. as-number ] option, you must specify the local AS number.
  • Page 208 Step Command Remarks Create the BGP IPv6 unicast By default, the BGP IPv6 unicast address family or BGP-VPN address family or BGP-VPN IPv6 address-family ipv6 [ unicast ] IPv6 unicast address family unicast address family is not and enter its view. created.
  • Page 209 Step Command Remarks Create the BGP IPv4 unicast By default, the BGP IPv4 unicast address family or BGP-VPN address family or BGP-VPN IPv4 address-family ipv4 [ unicast ] IPv4 unicast address family unicast address family is not and enter its view. created.
  • Page 210 Step Command Remarks Enable the router to exchange IPv6 unicast By default, the router cannot routing information with exchange IPv6 unicast routing peer group-name enable peers in the specified peer information with the peers. group. To configure an EBGP peer group by using Method 2 (IPv4): Step Command Remarks...
  • Page 211 Step Command Remarks By default, no EBGP peer group is Create an EBGP peer group. group group-name external created. Create an IPv6 BGP peer peer ipv6-address [ prefix-length ] By default, no IPv6 BGP peer is and specify its AS number. created.
  • Page 212 Step Command Remarks (Optional.) Configure a By default, no description is peer group-name description description for the peer configured for the peer group. description-text group. Create the BGP IPv4 unicast By default, the BGP IPv4 unicast address family or BGP-VPN address family or BGP-VPN IPv4 address-family ipv4 [ unicast ] IPv4 unicast address family...

  • Page 213: Specifying The Source Address Of Tcp Connections

    Specifying the source address of TCP connections By default, BGP uses the primary IPv4/IPv6 address of the output interface in the optimal route to a peer or peer group as the source address of TCP connections to the peer or peer group. Change the source address in the following scenarios: •...

  • Page 214: Generating Bgp Routes

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name peer ipv6-address The peer source-address [ prefix-length ] source-address Specify the source IPv6 command is available in Release source-ipv6-address address of TCP connections...

  • Page 215: Redistributing Igp Routes

    To inject a local network (IPv6): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv6 unicast address family view or address-family ipv6 [ unicast ] BGP-VPN IPv6 unicast...

  • Page 216: Controlling Route Distribution And Reception

    Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv6 unicast address family view or address-family ipv6 [ unicast ] BGP-VPN IPv6 unicast address family view.
  • Page 217 Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view.

  • Page 218: Advertising Optimal Routes In The Ip Routing Table

    Step Command Remarks aggregate ipv6-address prefix-length [ as-set | attribute-policy Create a summary route in route-policy-name | By default, no summary route is the IPv6 BGP routing table. detail-suppressed | configured. origin-policy route-policy-name | suppress-policy route-policy-name ] * Advertising optimal routes in the IP routing table By default, BGP advertises optimal routes in the BGP routing table, which may not be optimal in the IP routing table.

  • Page 219: Limiting Routes Received From A Peer Or Peer Group

    Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP IPv6 unicast address-family ipv6 [ unicast ] address family view. peer { group-name | ipv6-address Advertise a default route to a [ prefix-length ] } By default, no default route is peer or peer group.

  • Page 220: Configuring Bgp Route Filtering Policies

    Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP IPv6 unicast address-family ipv6 [ unicast ] address family view. peer { group-name | ipv6-address Specify the maximum [ prefix-length ] } route-limit By default, the number of routes number of routes that a prefix-number [ { alert-only | that a router can receive from a...
  • Page 221 Step Command Remarks Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view. • Reference an ACL or IP prefix list to filter advertised BGP routes: filter-policy { acl-number | prefix-list prefix-list-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ]...
  • Page 222 Step Command Remarks • Reference an ACL or IPv6 prefix list to filter advertised BGP routes: filter-policy { acl6-number | prefix-list ipv6-prefix-name } export [ direct | isisv6 process-id | ospfv3 process-id | ripng process-id | static ] • Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name |...
  • Page 223 Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view.

  • Page 224: Configuring Bgp Update Sending Delay

    Step Command Remarks • Reference ACL or IPv6 prefix list to filter BGP routes received from all peers: filter-policy { acl6-number | prefix-list ipv6-prefix-name } import • Reference a routing policy to filter BGP routes received from a peer or peer group: peer { group-name | ipv6-address [ prefix-length ] } route-policy route-policy-name import...

  • Page 225: Configuring Bgp Route Dampening

    Configuring BGP route dampening Route dampening enables BGP to not select unstable routes as optimal routes. This feature applies to EBGP routes but not to IBGP routes. To configure BGP route dampening (IPv4): Step Command Remarks Enter system view. system-view •...

  • Page 226: Configuring Preferences For Bgp Routes

    Among multiple routes that have the same destination/mask and are learned from different peers, the one with the greatest preferred value is selected as the optimal route. To specify a preferred value for routes from a peer or peer group (IPv4): Step Command Remarks...

  • Page 227: Configuring The Default Local Preference

    has the same preference as the local BGP route. The EBGP route will more likely become the optimal route. To configure preferences for BGP routes (IPv4): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view:...

  • Page 228: Configuring The Med Attribute

    To specify the default local preference (IPv4): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast...
  • Page 229 Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view.
  • Page 230 To enable MED comparison for routes from different ASs (IPv6): Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP IPv6 unicast address-family ipv6 [ unicast ] address family view. Enable MED comparison for By default, this feature is disabled. compare-different-as-med routes from different ASs.
  • Page 231 routes from different groups. The following output shows the BGP routing table on Router D after this feature is enabled. Network 10.0.0.0 learned from Router B is the optimal route. Network NextHop LocPrf PrefVal Path/Ogn *>i 10.0.0.0 2.2.2.2 300e 3.3.3.3 200e 1.1.1.1 200e...

  • Page 232: Configuring The Next_Hop Attribute

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view.
  • Page 233 Figure 59 NEXT_HOP attribute configuration IMPORTANT: If you have configured BGP load balancing, the router sets itself as the next hop for routes sent to an IBGP peer or peer group regardless of whether the peer next-hop-local command is configured. To configure the NEXT_HOP attribute (IPv4): Step Command...

  • Page 234: Configuring The As_Path Attribute

    Configuring the AS_PATH attribute Permitting local AS number to appear in routes from a peer or peer group In general, BGP checks whether the AS_PATH attribute of a route from a peer contains the local AS number. If yes, it discards the route to avoid routing loops. In certain network environments (for example, a Hub&Spoke network in MPLS L3VPN), however, the AS_PATH attribute of a route from a peer must be allowed to contain the local AS number.
  • Page 235 Disabling BGP from considering AS_PATH during optimal route selection To disable BGP from considering AS_PATH during optimal route selection (IPv4): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view.
  • Page 236 Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name By default, no fake AS number is advertised to a peer or peer peer { group-name | ip-address group.
  • Page 237 Figure 60 AS number substitution configuration (in an IPv4 network) For example, as shown in Figure 60, CE 1 and CE 2 use the same AS number 800. To ensure bidirectional communication between the two sites, configure AS number substitution on PE 2. PE 2 replaces AS 800 with AS 100 for the BGP route update originated from CE 1 before advertising it to CE 2.
  • Page 238 Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view.

  • Page 239: Tuning And Optimizing Bgp Networks

    Tuning and optimizing BGP networks This section describes how to tune and optimize BGP networks. Configuring the keepalive interval and hold time BGP sends keepalive messages at a specific interval to keep the BGP session between two routers. If a router receives no keepalive or update message from a peer within the hold time, it tears down the session.

  • Page 240: Configuring The Interval For Sending Updates For The Same Route

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Use at least one method. By default, the keepalive interval • Configure the global is 60 seconds, and hold time is keepalive interval and hold 180 seconds.

  • Page 241: Enabling Bgp To Establish An Ebgp Session Over Multiple Hops

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Configure the interval for peer { group-name | ipv6-address By default, the interval is 15 sending updates for the [ prefix-length ] } seconds for an IBGP peer and 30...

  • Page 242: Enabling Immediate Re-Establishment Of Direct Ebgp Connections Upon Link Failure

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enable BGP to establish an By default, BGP cannot establish EBGP session to an peer { group-name | ipv6-address an EBGP session to an indirectly-connected peer or...

  • Page 243: Enabling Md5 Authentication For Bgp Peers

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name peer { group-name | ip-address Enable 4-byte AS number [ mask-length ] } By default, 4-byte AS number suppression.

  • Page 244: Configuring Bgp Load Balancing

    Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enable MD5 authentication peer { group-name | ipv6-address By default, MD5 authentication is for a BGP peer group or [ prefix-length ] } password...

  • Page 245: Configuring Ipsec For Ipv6 Bgp

    Step Command Remarks Specify the maximum balance { [ ebgp | eibgp | ibgp ] By default, load balancing is number of BGP ECMP number | as-path-neglect } disabled. routes for load balancing. With the as-path-neglect keyword specified, the balance command enables BGP to implement load balancing over routes with different AS_PATH attributes.

  • Page 246: Configuring Gtsm For Bgp

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Disable BGP to establish a peer { group-name | ip-address By default, BGP can establish a session to a peer or peer [ mask-length ] } ignore session to a peer or peer group.

  • Page 247: Configuring Bgp Soft-Reset

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance view: Enter BGP view or BGP-VPN instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Configure GTSM for the peer { group-name | ip-address By default, GTSM is not specified BGP peer or peer [ mask-length ] } ttl-security hops configured.
  • Page 248 Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ip-address [ mask-length ] }...
  • Page 249 Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view.
  • Page 250 Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ip-address [ mask-length ] } capability-advertise route-refresh By default, BGP route refresh and Enable BGP route refresh for • multi-protocol extension capability Enable BGP route refresh a peer or peer group.

  • Page 251: Protecting An Ebgp Peer When Memory Usage Reaches Level 2 Threshold

    Step Command Remarks refresh bgp { ipv6-address [ prefix-length ] | all | external | group group-name | internal } Perform manual soft-reset. { export | import } ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] Protecting an EBGP peer when memory usage reaches level 2 threshold Memory usage includes the following threshold levels: normal, level 1, level 2, and level 3.

  • Page 252: Configuring A Large-Scale Bgp Network

    Configuring a large-scale BGP network In a large network, the number of BGP connections is huge and BGP configuration and maintenance are complicated. To simply BGP configuration, you can use the peer group, community, route reflector, and confederation features as needed. For more information about configuring peer groups, "Configuring a BGP peer group."...

  • Page 253: Configuring Bgp Route Reflection

    Step Command Remarks Enter BGP view. bgp as-number Enter BGP IPv6 unicast address-family ipv6 [ unicast ] address family view. • Advertise the COMMUNITY attribute to a peer or peer group: peer { group-name | ipv6-address [ prefix-length ] } Advertise the COMMUNITY By default, the COMMUNITY or or extended community...
  • Page 254 Step Command Remarks (Optional.) Configure the reflector cluster-id { cluster-id | By default, a route reflector uses cluster ID of the route ip-address } its own router ID as the cluster ID. reflector. To configure a BGP route reflector (IPv6): Step Command Remarks...

  • Page 255: Configuring A Bgp Confederation

    Step Command Remarks • Enter BGP view: bgp as-number • Enter BGP-VPN instance Enter BGP view or BGP-VPN view: instance view. a. bgp as-number b. ip vpn-instance vpn-instance-name By default, BGP does not ignore the ORIGINATOR_ID attribute. peer { group-name | ipv6-address Make sure this command does not Ignore the ORIGINATOR_ID [ prefix-length ] }...

  • Page 256: Configuring Bgp Gr

    Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enable confederation By default, confederation confederation nonstandard compatibility. compatibility is disabled. Configuring BGP GR Graceful Restart (GR) ensures forwarding continuous when a routing protocol restarts or an active/standby switchover occurs. Two routers are required to complete a GR process. The following are router roles in a GR process: •...

  • Page 257: Configuring Bgp Nsr

    Step Command Remarks Enter BGP view. bgp as-number By default, GR capability is Enable GR capability for BGP. graceful-restart disabled for BGP. The default setting is 150 seconds. graceful-restart timer restart Configure the GR timer. The time that a peer waits to timer re-establish a session must be less than the hold time.

  • Page 258: Enabling Logging Of Session State Changes

    Step Command Remarks Enter system view. system-view Enable SNMP By default, SNMP notifications for snmp-agent trap enable bgp notifications for BGP. BGP are enabled. Enabling logging of session state changes Perform this task to enable BGP to log BGP session establishment and disconnection events. To view the log information, use the display bgp peer ipv4 unicast log-info command or the display bgp peer ipv6 unicast log-info command.

  • Page 259: Configuring Bfd For Bgp

    Step Command Remarks • Enter BGP IPv4 unicast address family view: a. bgp as-number b. address-family ipv4 [ unicast ] Enter BGP IPv4 unicast address family view or • Enter BGP-VPN IPv4 unicast BGP-VPN IPv4 unicast address family view: address family view. c.

  • Page 260: Configuring Bgp Frr

    Before you can enable BFD for the BGP peer, establish a BGP session between the local router and the peer. To enable BFD for a BGP peer (IPv4): Step Command Remarks Enter system view. system-view • Enter BGP view: bgp as-number •...
  • Page 261 • Method 1—Execute the pic command in BGP address family view. BGP calculates a backup next hop for a BGP route in the address family if there are two or more unequal-cost routes that reaches the destination. • Method 2—Execute the fast-reroute route-policy command to reference a routing policy in which a backup next hop is specified by using the apply [ ipv6 ] fast-reroute backup-nexthop command.
  • Page 262 Step Command Remarks By default, BGP FRR is disabled. • (Method 1) Enable BGP FRR for the address Method 1 might result in routing loops. family: Use it with caution. By default, no routing policy is • (Method 2) Reference a referenced.

  • Page 263: Configuring 6Pe

    Configuring 6PE IPv6 provider edge (6PE) is a transition technology that uses MPLS to connect sparsely populated IPv6 networks through an existing IPv4 backbone network. It is an efficient solution for ISP IPv4/MPLS networks to provide IPv6 traffic switching capability. Figure 62 Network diagram for 6PE 6PE mainly performs the following operations: •...

  • Page 264: Configuring Optional 6Pe Capabilities

    Step Command Remarks Enter BGP IPv6 unicast address-family ipv6 [ unicast ] address family view. Enable BGP to exchange IPv6 unicast routing peer { group-name | ip-address This function is disabled by information with the 6PE [ mask-length ] } enable default.

  • Page 265: Displaying And Maintaining Bgp

    Step Command Remarks 13. Configure BGP updates sent to the 6PE peer or peer peer { group-name | ip-address By default, this feature is not group to carry only the public [ mask-length ] } public-as-only configured. AS number. peer { group-name | ip-address 14.
  • Page 266 Task Command display bgp routing-table ipv4 [ unicast ] [ vpn-instance Display BGP IPv4 unicast routing vpn-instance-name ] peer ip-address { advertised-routes | information sent to/received from the received-routes } [ network-address [ mask | mask-length ] | specified BGP peer. statistic ] Display BGP IPv4 unicast routing display bgp routing-table ipv4 [ unicast ] [ vpn-instance...
  • Page 267 Task Command display bgp peer ipv6 [ unicast ] [ group-name group-name log-info | ip-address { log-info | verbose } | ipv6-address { log-info | verbose } | verbose ] Display BGP IPv6 unicast peer or peer group information. display bgp peer ipv6 [ unicast ] vpn-instance vpn-instance-name [ group-name group-name log-info | ipv6-address { log-info | verbose } | verbose ] display bgp routing-table ipv6 [ unicast ] [ vpn-instance...

  • Page 268: Ipv4 Bgp Configuration Examples

    Task Command Clear dampened BGP IPv6 unicast reset bgp dampening ipv6 [ unicast ] [ vpn-instance routing information and release vpn-instance-name ] [ network-address prefix-length ] suppressed routes. reset bgp flap-info ipv6 [ unicast ] [ vpn-instance Clear BGP IPv6 unicast route flap vpn-instance-name ] [ network-address prefix-length | information.
  • Page 269 [SwitchB-bgp-ipv4] quit [SwitchB-bgp] quit [SwitchB] ospf 1 [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 2.2.2.2 as-number 65009 [SwitchC-bgp] peer 2.2.2.2 connect-interface loopback 0 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 2.2.2.2 enable [SwitchC-bgp-ipv4] quit...
  • Page 270 [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] peer 3.1.1.2 enable [SwitchB-bgp-ipv4] quit [SwitchB-bgp] quit # Display BGP peer information on Switch B. [SwitchB] display bgp peer ipv4 BGP local router ID : 2.2.2.2 Local AS number : 65009 Total number of peers : 2 Peers in established state : 2 Peer MsgRcvd...
  • Page 271 BGP local router ID is 3.3.3.3 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf...

  • Page 272: Bgp And Igp Route Redistribution Configuration Example

    * >i 2.2.2.2/32 2.2.2.2 * >i 3.1.1.0/24 2.2.2.2 * >i 8.1.1.0/24 3.1.1.2 65008i * >i 9.1.1.0/24 2.2.2.2 The output shows that the route 8.1.1.0 becomes valid with the next hop as Switch A. Verifying the configuration # Ping 8.1.1.1 from Switch C. [SwitchC] ping 8.1.1.1 Ping 8.1.1.1 (8.1.1.1): 56 data bytes, press CTRL_C to break 56 bytes from 8.1.1.1: icmp_seq=0 ttl=254 time=10.000 ms...
  • Page 273 [SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] ospf 1 [SwitchC-ospf-1] import-route direct [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit Configure the EBGP connection: Configure the EBGP connection and inject network 8.1.1.0/24 to the BGP routing table of Switch A, so that Switch B can obtain the route to 8.1.1.0/24.
  • Page 274 Network NextHop LocPrf PrefVal Path/Ogn * >e 3.3.3.3/32 3.1.1.1 65009? * > 8.1.1.0/24 8.1.1.1 32768 * >e 9.1.2.0/24 3.1.1.1 65009? # Display the OSPF routing table on Switch C. [SwitchC] display ospf routing OSPF Process 1 with Router ID 3.3.3.3 Routing Tables Routing for Network Destination...

  • Page 275: Bgp Route Summarization Configuration Example

    BGP route summarization configuration example Network requirements As shown in Figure 65, run EBGP between Switch C and Switch D, so the internal network and external network can communicate with each other. • In AS 65106, perform the following configurations so the devices in the internal network can communicate: Configure static routing between Switch A and Switch B.
  • Page 276 [SwitchB-ospf-1] import-route static [SwitchB-ospf-1] quit # Configure OSPF to advertise the local networks on Switch C. [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 172.17.100.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 10.220.2.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Display the IP routing table on Switch C. [SwitchC] display ip routing-table protocol ospf Summary Count : 5 OSPF Routing table Status : <Active>...
  • Page 277 # Display the IP routing table on Switch D. [SwitchD] display ip routing-table protocol bgp Summary Count : 3 BGP Routing table Status : <Active> Summary Count : 3 Destination/Mask Proto Cost NextHop Interface 192.168.64.0/24 10.220.2.16 Vlan200 192.168.74.0/24 10.220.2.16 Vlan200 192.168.99.0/24 10.220.2.16 Vlan200...

  • Page 278: Bgp Load Balancing Configuration Example

    # Verify that Switch D can ping the hosts on networks 192.168.64.0/24, 192.168.74.0/24 and 192.168.99.0/24. (Details not shown.) BGP load balancing configuration example Network requirements As shown in Figure 66, run EBGP between Switch A and Switch B, and between Switch A and Switch C.
  • Page 279 # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 3.1.1.1 as-number 65009 [SwitchA-bgp] peer 3.1.2.1 as-number 65009 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 3.1.1.1 enable [SwitchA-bgp-ipv4] peer 3.1.2.1 enable [SwitchA-bgp-ipv4] network 8.1.1.0 24 [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit # Configure Switch B.
  • Page 280 Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn * > 8.1.1.0/24 8.1.1.1 32768 * >e 9.1.1.0/24 3.1.1.1 65009i 3.1.2.1 65009i The output shows two valid routes to destination 9.1.1.0/24. The route with next hop 3.1.1.1 is marked with a greater-than sign (>), indicating it is the optimal route (because the ID of Switch B is smaller).

  • Page 281: Bgp Community Configuration Example

    BGP community configuration example Network requirements As shown in Figure 67, Switch B establishes EBGP connections with Switch A and Switch C. Configure NO_EXPORT community attribute on Switch A to make routes from AS 10 not advertised by AS 20 to any other AS. Figure 67 Network diagram Configuration procedure Configure IP addresses for interfaces.
  • Page 282 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 200.1.3.1 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Display the BGP routing table on Switch B. [SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 20 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 200.1.2.1 (1.1.1.1)
  • Page 283 Configure BGP community: # Configure a routing policy. [SwitchA] route-policy comm_policy permit node 0 [SwitchA-route-policy-comm_policy-0] apply community no-export [SwitchA-route-policy-comm_policy-0] quit # Apply the routing policy. [SwitchA] bgp 10 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 200.1.2.2 route-policy comm_policy export [SwitchA-bgp-ipv4] peer 200.1.2.2 advertise-community Verifying the configuration # Display the routing table on Switch B.

  • Page 284: Bgp Route Reflector Configuration Example

    BGP route reflector configuration example Network requirements As shown in Figure 68, all switches run BGP. Run EBGP between Switch A and Switch B, and run IBGP between Switch C and Switch B, and between Switch C and Switch D. Configure Switch C as a route reflector with clients Switch B and Switch D to allow Switch D to learn route 20.0.0.0/8 from Switch C.
  • Page 285 <SwitchC> system-view [SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 193.1.1.2 as-number 200 [SwitchC-bgp] peer 194.1.1.2 as-number 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 193.1.1.2 enable [SwitchC-bgp-ipv4] peer 194.1.1.2 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Configure Switch D. <SwitchD> system-view [SwitchD] bgp 200 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] peer 194.1.1.1 as-number 200...

  • Page 286: Bgp Confederation Configuration Example

    s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn * >i 20.0.0.0 193.1.1.2 100i The output shows that Switch D has learned route 20.0.0.0/8 from Switch C. BGP confederation configuration example Network requirements As shown in...
  • Page 287 [SwitchA-bgp] confederation id 200 [SwitchA-bgp] confederation peer-as 65002 65003 [SwitchA-bgp] peer 10.1.1.2 as-number 65002 [SwitchA-bgp] peer 10.1.2.2 as-number 65003 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] peer 10.1.1.2 enable [SwitchA-bgp-ipv4] peer 10.1.2.2 enable [SwitchA-bgp-ipv4] peer 10.1.1.2 next-hop-local [SwitchA-bgp-ipv4] peer 10.1.2.2 next-hop-local [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit # Configure Switch B.
  • Page 288 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] confederation id 200 [SwitchD-bgp] peer 10.1.3.1 as-number 65001 [SwitchD-bgp] peer 10.1.5.2 as-number 65001 [SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 10.1.3.1 enable [SwitchD-bgp-ipv4] peer 10.1.5.2 enable [SwitchD-bgp-ipv4] quit [SwitchD-bgp] quit # Configure Switch E. <SwitchE> system-view [SwitchE] bgp 65001 [SwitchE-bgp] router-id 5.5.5.5 [SwitchE-bgp] confederation id 200 [SwitchE-bgp] peer 10.1.4.1 as-number 65001...
  • Page 289 s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn * >i 9.1.1.0/24 10.1.1.1 (65001) 100i [SwitchB] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 2.2.2.2 Local AS number: 65002 Paths: 1 available, 1 best...

  • Page 290: Bgp Path Selection Configuration Example

    AS-path : 100 Origin : igp Attribute value : MED 0, localpref 100, pref-val 0, pre 255 State : valid, internal-confed, best, The output shows the following: • Switch F can send route information to Switch B and Switch C through the confederation by establishing only an EBGP connection with Switch A.
  • Page 291 [SwitchB-ospf] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 192.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] ospf [SwitchC-ospf] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 193.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Configure Switch D. <SwitchD>...
  • Page 292 [SwitchC-bgp-ipv4] peer 193.1.1.1 enable [SwitchC-bgp-ipv4] peer 195.1.1.1 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Configure Switch D. [SwitchD] bgp 200 [SwitchD-bgp] peer 194.1.1.2 as-number 200 [SwitchD-bgp] peer 195.1.1.2 as-number 200 [SwitchD-bgp] address-family ipv4 unicast [SwitchD-bgp-ipv4] peer 194.1.1.2 enable [SwitchD-bgp-ipv4] peer 195.1.1.2 enable [SwitchD-bgp-ipv4] quit [SwitchD-bgp] quit Configure local preference for route 1.0.0.0/8, making Switch D give priority to the route learned...

  • Page 293: Bgp Gr Configuration Example

    BGP GR configuration example Network requirements As shown in Figure 71, all switches run BGP. EBGP runs between Switch A and Switch B. IBGP runs between Switch B and Switch C. Enable GR capability for BGP so that the communication between Switch A and Switch C is not affected when an active/standby switchover occurs on Switch B.

  • Page 294: Bfd For Bgp Configuration Example

    [SwitchB-bgp-ipv4] peer 200.1.1.2 enable [SwitchB-bgp-ipv4] peer 9.1.1.2 enable Configure Switch C: # Configure IP addresses for interfaces. (Details not shown.) # Configure the IBGP connection. <SwitchC> system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 9.1.1.1 as-number 65009 # Enable GR capability for BGP. [SwitchC-bgp] graceful-restart # Enable Switch C to exchange IPv4 unicast routing information with Switch B.
  • Page 295 Table 17 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int100 3.0.1.1/24 Switch C Vlan-int101 3.0.2.2/24 Vlan-int200 2.0.1.1/24 Vlan-int201 2.0.2.2/24 Switch B Vlan-int100 3.0.1.2/24 Switch D Vlan-int200 2.0.1.2/24 Vlan-int101 3.0.2.1/24 Vlan-int201 2.0.2.1/24 Configuration procedure Configure IP addresses for interfaces.
  • Page 296 Configure BGP on Switch C: # Establish two IBGP connections to Switch A. <SwitchC> system-view [SwitchC] bgp 200 [SwitchC-bgp] peer 3.0.1.1 as-number 200 [SwitchC-bgp] peer 2.0.1.1 as-number 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 3.0.1.1 enable [SwitchC-bgp-ipv4] peer 2.0.1.1 enable [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit # Enable BFD for peer 3.0.1.1.
  • Page 297 The output shows that Switch C has established two BGP connections with Switch A, and both connections are in Established state. # Display route 1.1.1.0/24 on Switch C. <SwitchC> display ip routing-table 1.1.1.0 24 verbose Summary Count : 1 Destination: 1.1.1.0/24 Protocol: BGP Process ID: 0 SubProtID: 0x1...

  • Page 298: Bgp Frr Configuration Example

    BGP FRR configuration example Network requirements As shown in Figure 73, configure BGP FRR so that when Link B fails, BGP uses Link A to forward traffic. Figure 73 Network diagram Loop0 2.2.2.2/32 Vlan-int 100 Vlan-int 101 AS 200 10.1.1.2/24 20.1.1.2/24 Switch B Vlan-int 100...
  • Page 299 [SwitchB-bgp-ipv4] peer 4.4.4.4 enable [SwitchB-bgp-ipv4] peer 4.4.4.4 next-hop-local [SwitchB-bgp-ipv4] quit [SwitchB-bgp] quit # Configure Switch C to establish an EBGP session with Switch A, and an IBGP session with Switch D. <SwitchC> system-view [SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 30.1.1.1 as-number 100 [SwitchC-bgp] peer 4.4.4.4 as-number 200 [SwitchC-bgp] peer 4.4.4.4 connect-interface loopback 0 [SwitchC-bgp] address-family ipv4 unicast...
  • Page 300 [SwitchA-route-policy] apply fast-reroute backup-nexthop 30.1.1.3 [SwitchA-route-policy] quit # Apply the routing policy to BGP FRR for BGP IPv4 unicast address family. [SwitchA] bgp 100 [SwitchA-bgp] address-family ipv4 unicast [SwitchA-bgp-ipv4] fast-reroute route-policy frr [SwitchA-bgp-ipv4] quit [SwitchA-bgp] quit # On Switch D, configure the source address of BFD echo packets as 44.1.1.1. [SwitchD] bfd echo-source-ip 44.1.1.1 # Create routing policy frr to set a backup next hop 3.3.3.3 (Switch C) for the route destined for 1.1.1.1/32.

  • Page 301: Ipv6 Bgp Configuration Examples

    [SwitchD] display ip routing-table 1.1.1.1 32 verbose Summary Count : 1 Destination: 1.1.1.1/32 Protocol: BGP Process ID: 0 SubProtID: 0x1 Age: 00h00m36s Cost: 0 Preference: 255 IpPre: N/A QosLocalID: N/A Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 100 NibID: 0x15000003 LastAs: 100...
  • Page 302 [SwitchB-bgp-ipv6] peer 9::2 enable [SwitchB-bgp-ipv6] quit # Configure Switch C. <SwitchC> system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 9::1 as-number 65009 [SwitchC-bgp] address-family ipv6 [SwitchC-bgp-ipv6] peer 9::1 enable Configure EBGP: # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 10::1 as-number 65009 [SwitchA-bgp] address-family ipv6...
  • Page 303 10::2 65008 2 00:27:20 Established The output shows that Switch A and Switch B have established an EBGP connection, and Switch B and Switch C have established an IBGP connection. # Display IPv6 BGP routing table information on Switch A. [SwitchA] display bgp routing-table ipv6 Total number of routes: 4 BGP local router ID is 1.1.1.1...

  • Page 304: Ipv6 Bgp Route Reflector Configuration Example

    NextHop : :: LocPrf PrefVal : 32768 OutLabel : NULL Path/Ogn: i i Network : 9:: PrefixLen : 64 NextHop : 9::1 LocPrf : 100 PrefVal : 0 OutLabel : NULL Path/Ogn: i * >i Network : 10:: PrefixLen : 64 NextHop : 9::1 LocPrf : 100...
  • Page 305 Configure IBGP and EBGP connections and advertise network routes through IPv6 BGP: # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 100::2 as-number 200 [SwitchA-bgp] address-family ipv6 [SwitchA-bgp-ipv6] peer 100::2 enable [SwitchA-bgp-ipv6] network 1:: 64 [SwitchA-bgp-ipv6] network 100:: 96 [SwitchA-bgp-ipv6] quit [SwitchA-bgp] quit...
  • Page 306 [SwitchC-bgp-ipv6] quit [SwitchC-bgp] quit Verifying the configuration # Execute the display bgp routing-table ipv6 command on Switch D. [SwitchD] display bgp routing-table ipv6 Total number of routes: 5 BGP local router ID is 4.4.4.4 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete * >i Network : 1::...

  • Page 307: 6Pe Configuration Example

    6PE configuration example Network requirements As shown in Figure 76, use 6PE to connect two isolated IPv6 networks over an IPv4/MPLS network. • The ISP uses OSPF as the IGP. • PE 1 and PE 2 are edge devices of the ISP, and establish an IPv4 IBGP connection between them.
  • Page 308 [PE1-bgp-ipv6] peer 3.3.3.3 enable [PE1-bgp-ipv6] peer 3.3.3.3 label-route-capability [PE1-bgp-ipv6] quit [PE1-bgp] quit # Configure a static route to CE 1. [PE1] ipv6 route-static 1::1 128 10::1 # Configure OSPF for the ISP. [PE1] ospf [PE1-ospf-1] area 0 [PE1-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.0.0 0.0.255.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit...
  • Page 309 <CE1> system-view [CE1] ipv6 route-static :: 0 10::2 Configure a static route on CE 2, with PE 2 as the default next hop. <CE2> system-view [CE2] ipv6 route-static :: 0 20::2 Verifying the configuration Display the IPv6 BGP routing tables on PE 1 and PE 2, and the output shows that each of them has two IPv6 network routes.

  • Page 310: Bfd For Ipv6 Bgp Configuration Example

    # Verify that CE 1 can ping the IPv6 address 4::4 (loopback interface address) of CE 2. (Details not shown.) BFD for IPv6 BGP configuration example Network requirements As shown in Figure 77, configure OSPFv3 as the IGP in AS 200. •...
  • Page 311 [SwitchA-bgp] peer 2001::3 as-number 200 [SwitchA-bgp] address-family ipv6 [SwitchA-bgp-ipv6] peer 3001::3 enable [SwitchA-bgp-ipv6] peer 2001::3 enable [SwitchA-bgp-ipv6] quit # Create IPv6 ACL 2000 to permit 1200::0/64 to pass. [SwitchA] acl ipv6 number 2000 [SwitchA-acl6-basic-2000] rule permit source 1200:: 64 [SwitchA-acl6-basic-2000] quit # Create two route policies, apply_med_50 and apply_med_100.
  • Page 312 Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode: Local Discr: 513 Remote Discr: 513 Source IP: 3001::3 Destination IP: 3000::1 Session State: Up Interface: N/A Min Tx Inter: 500ms Act Tx Inter: 500ms Min Rx Inter: 500ms Detect Inter: 2500ms Rx Count: 13...

  • Page 313: Ipv6 Bgp Frr Configuration Example

    BkTunnel ID: Invalid BkInterface: N/A The output shows that Switch C communicates with network 1200::0/64 through the path Switch C<—>Switch B<—>Switch A. # Break down the path Switch C<—>Switch B<—>Switch A and then display route 1200::0/64 on Switch C. <SwitchC> display ipv6 routing-table 1200::0 64 verbose Summary Count : 1 Destination: 1200::/64 Protocol: BGP4+...
  • Page 314 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure OSPFv3 in AS 200 to ensure connectivity among Switch B, Switch C and Switch D. (Details not shown.) Configure BGP connections: # Configure Switch A to establish EBGP sessions with Switch B and Switch C, and advertise network 1::/64.
  • Page 315 [SwitchD-bgp] peer 3002::1 as-number 200 [SwitchD-bgp] peer 2002::1 as-number 200 [SwitchD-bgp] address-family ipv6 unicast [SwitchD-bgp-ipv6] peer 3002::1 enable [SwitchD-bgp-ipv6] peer 2002::1 enable [SwitchD-bgp-ipv6] network 4:: 64 [SwitchD-bgp-ipv6] quit [SwitchD-bgp] quit Configure preferred values so Link B is used to forward traffic between Switch A and Switch D: # Configure Switch A to set the preferred value to 100 for routes received from Switch B.
  • Page 316 Verifying the configuration # Display detailed information about the route to 4::/64 on Switch A. The output shows the backup next hop for the route. [SwitchA] display ipv6 routing-table 4:: 64 verbose Summary Count : 1 Destination: 4::/64 Protocol: BGP4+ Process ID: 0 SubProtID: 0x2 Age: 00h00m58s...

  • Page 317: Ipsec For Ipv6 Bgp Packets Configuration Example

    IPsec for IPv6 BGP packets configuration example Network requirements As shown in Figure 79, all switches run IPv6 BGP. Establish an IBGP connection between Switch A and Switch B. Establish an EBGP connection between Switch B and Switch C. To enhance security, configure IPsec to protect IPv6 BGP packets. Figure 79 Network diagram Configuration procedure Configure IPv6 addresses for interfaces.
  • Page 318 [SwitchC-bgp] quit # Configure Switch B. [SwitchB-bgp] group ebgp external [SwitchB-bgp] peer 3::2 as-number 65009 [SwitchB-bgp] peer 3::2 group ebgp [SwitchB-bgp] address-family ipv6 unicast [SwitchB-bgp-ipv6] peer ebgp enable [SwitchB-bgp-ipv6] quit [SwitchB-bgp] quit Configure IPsec transform sets and IPsec profiles: # On Switch A, create an IPsec transform set named tran1. [SwitchA] ipsec transform-set tran1 # Set the encapsulation mode to transport mode.
  • Page 319 [SwitchB-ipsec-profile-policy001-manual] sa string-key outbound esp simple abcdefg [SwitchB-ipsec-profile-policy001-manual] sa string-key inbound esp simple abcdefg [SwitchB-ipsec-profile-policy001-manual] quit # Create an IPsec transform set named tran2. [SwitchB] ipsec transform-set tran2 # Set the encapsulation mode to transport mode. [SwitchB-ipsec-transform-set-tran2] encapsulation-mode transport # Set the security protocol to ESP, the encryption algorithm to DES, and authentication algorithm to SHA1.
  • Page 320 [SwitchA-bgp] quit # Configure Switch B. [SwitchB] bgp 65008 [SwitchB-bgp] peer 1::1 ipsec-profile policy001 [SwitchB-bgp] quit Configure IPsec to protect IPv6 BGP packets between Router B and Switch C: # Configure Switch C. [SwitchC] bgp 65009 [SwitchC-bgp] peer ebgp ipsec-profile policy002 [SwitchC-bgp] quit # Configure Switch B.

  • Page 321: Troubleshooting Bgp

    Peer: 3::2 Local: 2.2.2.2 Type: EBGP link BGP version 4, remote router ID 3.3.3.3 BGP current state: Established, Up for 00h05m00s BGP current event: KATimerExpired BGP last state: OpenConfirm Port: Local - 24897 Remote - 179 Configured: Active Hold Time: 180 sec Keepalive Time: 60 sec Received : Active Hold Time: 180 sec...
  • Page 322 a. Use the display current-configuration command to verify the current configuration, and verify that the peer's AS number is correct. b. Use the display bgp peer ipv4 unicast or display bgp peer ipv6 unicast command to verify that the peer's IP address/IPv6 address is correct. c.

  • Page 323: Configuring Pbr

    Configuring PBR Overview Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop for packets that match specific criteria such as ACLs. A device forwards received packets using the following process: The device uses PBR to forward matching packets. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets.

  • Page 324: Pbr And Track

    Relationship between the match mode and clauses on the node Does a packet match all Match mode the if-match clauses on Permit Deny the node? • If the node is configured with an apply clause, PBR executes the apply clause on the node. It does not match the packet against the The packet is forwarded according next node.

  • Page 325: Configuring Match Criteria For A Node

    Configuring match criteria for a node Step Command Remarks Enter system system-view view. Enter policy policy-based-route policy-name [ deny | permit ] node node view. node-number Configure an By default, no ACL ACL match if-match acl acl-number { acl-number | name acl-name } match criterion is criterion.

  • Page 326: Configuring Interface Pbr

    Step Command Remarks By default, no policy is locally ip local policy-based-route Apply a policy locally. applied. policy-name Configuring interface PBR Configure PBR by applying a policy to an interface. PBR uses the policy to guide the forwarding of packets received on the interface. The specified policy must already exist. Otherwise, the interface PBR configuration fails.
  • Page 327 Figure 80 Network diagram Switch B Vlan-int10 Vlan-int10 Switch A 1.1.2.1/24 1.1.2.2/24 Vlan-int20 Vlan-int20 1.1.3.1/24 1.1.3.2/24 Switch C Configuration procedure Configure Switch A: # Create VLAN 10 and VLAN 20. <SwitchA> system-view [SwitchA] vlan 10 [SwitchA-vlan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure the IP addresses of VLAN-interface 10 and VLAN-interface 20.

  • Page 328: Packet Type-Based Interface Pbr Configuration Example

    # Configure the IP address of VLAN-interface 20. [SwitchC] interface vlan-interface 20 [SwitchC-Vlan-interface20] ip address 1.1.3.2 24 Verifying the configuration # Telnet to Switch B on Switch A. The operation succeeds. # Telnet to Switch C on Switch A. The operation fails. # Ping Switch C from Switch A.
  • Page 329 [SwitchA-vlan20] quit # Configure the IP addresses of VLAN-interface 10 and VLAN-interface 20. [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ip address 1.1.2.1 24 [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ip address 1.1.3.1 24 [SwitchA-Vlan-interface20] quit # Configure ACL 3101 to match TCP packets. [SwitchA] acl number 3101 [SwitchA-acl-adv-3101] rule permit tcp [SwitchA-acl-adv-3101] quit...
  • Page 330 # On Host A, Telnet to Switch B that is directly connected to Switch A. The operation succeeds. # On Host A, Telnet to Switch C that is directly connected to Switch A. The operation fails. # Ping Switch C from Host A. The operation succeeds. Telnet uses TCP and ping uses ICMP.

  • Page 331: Configuring Ipv6 Static Routing

    Configuring IPv6 static routing Static routes are manually configured and cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually. IPv6 static routing works well in a simple IPv6 network. Configuring an IPv6 static route Before you configure an IPv6 static route, complete the following tasks: •...

  • Page 332: Bidirectional Control Mode

    IMPORTANT: Enabling BFD for a flapping route could worsen the situation. Bidirectional control mode To use BFD bidirectional control detection between two devices, enable BFD control mode for each device's static route destined to the peer. To configure a static route and enable BFD control mode, use one of the following methods: •...

  • Page 333: Displaying And Maintaining Ipv6 Static Routes

    IMPORTANT: Do not use BFD for a static route with the output interface in spoofing state. To configure BFD echo mode for an IPv6 static route: Step Command Remarks Enter system view. system-view By default, the source address of echo packets is not configured.
  • Page 334 Figure 82 Network diagram Host B 2::2/64 Vlan-int400 2::1/64 Vlan-int200 Vlan-int300 4::2/64 5::2/64 Switch B Vlan-int200 Vlan-int300 4::1/64 5::1/64 Vlan-int100 Vlan-int500 1::1/64 3::1/64 Switch C Switch A Host C Host A 3::2/64 1::2/64 Configuration procedure Configure the IPv6 addresses for all VLAN interfaces. (Details not shown.) Configure IPv6 static routes: # Configure a default IPv6 static route on Switch A.

  • Page 335: Bfd For Ipv6 Static Routes Configuration Example (Direct Next Hop)

    Summary Count : 2 Static Routing table Status : <Active> Summary Count : 2 Destination: 1::/64 Protocol : Static NextHop : 4::1 Preference: 60 Interface : Vlan-interface200 Cost Destination: 3::/64 Protocol : Static NextHop : 5::1 Preference: 60 Interface : Vlan-interface300 Cost Static Routing table Status : <Inactive>...
  • Page 336 Figure 83 Network diagram Table 19 Interface and IP address assignment Device Interface IPv6 address Switch A Vlan-int10 12::1/64 Switch A Vlan-int11 10::102/64 Switch B Vlan-int10 12::2/64 Switch B Vlan-int13 13::1/64 Switch C Vlan-int11 10::100/64 Switch C Vlan-int13 13::2/64 Configuration procedure Configure IPv6 addresses for interfaces.
  • Page 337 [SwitchB] quit # Configure IPv6 static routes on Switch C. <SwitchC> system-view [SwitchC] ipv6 route-static 120:: 64 13::1 [SwitchC] ipv6 route-static 121:: 64 10::102 Verifying the configuration # Display the BFD sessions on Switch A. <SwitchA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode:...

  • Page 338: Bfd For Ipv6 Static Routes Configuration Example (Indirect Next Hop)

    Interface : Vlan11 Cost Static Routing table Status : < Inactive> Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 11. BFD for IPv6 static routes configuration example (indirect next hop) Network requirements As shown in Figure •...
  • Page 339 Device Interface IPv6 address Switch B Loop1 2::9/128 Switch C Vlan-int11 10::100/64 Switch C Vlan-int13 13::2/64 Switch D Vlan-int10 12::2/64 Switch D Vlan-int12 11::1/64 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure IPv6 static routes and BFD: # Configure IPv6 static routes on Switch A and enable BFD control packet mode for the IPv6 static route that traverses Switch D.
  • Page 340 Destination IP: FE80::1:1B49 (link-local address of Loopback1 on Switch B) Session State: Up Interface: N/A Hold Time: 2012ms The output shows that the BFD session has been created. # Display the IPv6 static routes on Switch A. <SwitchA> display ipv6 routing-table protocol static Summary Count : 1 Static Routing table Status : <Active>...

  • Page 341: Configuring An Ipv6 Default Route

    Configuring an IPv6 default route A default IPv6 route is used to forward packets that match no entry in the routing table. A default IPv6 route can be configured in either of the following ways: • The network administrator can configure a default route with a destination prefix of ::/0. For more information, see "Configuring an IPv6 static route."...

  • Page 342: Configuring Ripng

    Configuring RIPng Overview RIP next generation (RIPng) is an extension of RIP-2 for support of IPv6. Most RIP concepts are applicable to RIPng. RIPng is a distance vector routing protocol. It employs UDP to exchange route information through port 521. RIPng uses a hop count to measure the distance to a destination. The hop count is the metric or cost.

  • Page 343: Protocols And Standards

    A response packet that fails the check is discarded. Protocols and standards • RFC 2080, RIPng for IPv6 • RFC 2081, RIPng Protocol Applicability Statement RIPng configuration task list Tasks at a glance (Required.) Configuring basic RIPng (Optional.) Configuring RIPng route control: •...

  • Page 344: Configuring Ripng Route Control

    Configuring RIPng route control Before you configure RIPng, complete the following tasks: • Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes. • Configure basic RIPng. Configuring an additional routing metric An additional routing metric (hop count) can be added to the metric of an inbound or outbound RIPng route.

  • Page 345: Advertising A Default Route

    Advertising a default route Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, RIPng does not advertise a default route. This command advertises a default Configure RIPng to advertise ripng default-route { only | route on the current interface a default route.

  • Page 346: Configuring Ripng Route Redistribution

    Configuring RIPng route redistribution Step Command Remarks Enter system view. system-view ripng [ process-id ] Enter RIPng view. [ vpn-instance vpn-instance-name ] import-route protocol By default, RIPng does not Redistribute routes from [ process-id ] [ allow-ibgp ] [ cost redistribute routes from other other routing protocols.

  • Page 347: Configuring Zero Field Check On Ripng Packets

    Configuring split horizon Split horizon disables RIPng from sending routes through the interface where the routes were learned to prevent routing loops between neighbors. As a best practice, enable split horizon to prevent routing loops in normal cases. To configure split horizon: Step Command Remarks...

  • Page 348: Configuring Ripng Gr

    Step Command Remarks ripng [ process-id ] [ vpn-instance Enter RIPng view. vpn-instance-name ] By default, the maximum number of RIPng ECMP routes equals the maximum number of ECMP routes supported by the system. Use the max-ecmp-num Configure the maximum command to configure the maximum load-balancing number number of ECMP routes.

  • Page 349: Displaying And Maintaining Ripng

    profile. If they match, the device accepts the packet. If they do not match, the device discards the packet and does not establish a neighbor relationship with the sending device. You can configure an IPsec profile for a RIPng process or interface. The IPsec profile configured for a process applies to all packets in the process.

  • Page 350: Ripng Configuration Examples

    RIPng configuration examples Basic RIPng configuration example Network requirements As shown in Figure 85, Switch A, Switch B, and Switch C run RIPng. Configure Switch B to filter the route 2::/64 learned from Switch A and to forward only the route 4::/64 to Switch A. Figure 85 Network diagram Configuration procedure Configure IPv6 addresses for interfaces.
  • Page 351 [SwitchC-Vlan-interface500] quit [SwitchC] interface vlan-interface 600 [SwitchC-Vlan-interface600] ripng 1 enable [SwitchC-Vlan-interface600] quit # Display the RIPng routing table on Switch B. [SwitchB] display ripng 1 route Route Flags: A - Aging, S - Suppressed, G - Garbage-collect O - Optimal, F - Flush to RIB ---------------------------------------------------------------- Peer FE80::20F:E2FF:FE23:82F5 on Vlan-interface100 Destination 1::/64,...

  • Page 352: Ripng Route Redistribution Configuration Example

    [SwitchB] display ripng 1 route Route Flags: A - Aging, S - Suppressed, G - Garbage-collect O - Optimal, F - Flush to RIB ---------------------------------------------------------------- Peer FE80::1:100 on Vlan-interface100 Destination 1::/64, via FE80::2:100, cost 1, tag 0, AOF, 6 secs Peer FE80::3:200 on Vlan-interface200 Destination 3::/64, via FE80::2:200, cost 1, tag 0, AOF, 11 secs...
  • Page 353 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ripng 100 enable [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ripng 100 enable [SwitchA-Vlan-interface200] quit # Enable RIPng 100 and RIPng 200 on Switch B. <SwitchB> system-view [SwitchB] ripng 100 [SwitchB-ripng-100] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ripng 100 enable [SwitchB-Vlan-interface100] quit [SwitchB] ripng 200...
  • Page 354 Destination: 2::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Configure RIPng route redistribution: # Configure route redistribution between the two RIPng processes on Switch B.

  • Page 355: Ripng Ipsec Profile Configuration Example

    Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost RIPng IPsec profile configuration example Network requirements As shown in Figure 87, configure RIPng on the switches, and configure IPsec profiles on the switches to authenticate and encrypt protocol packets.
  • Page 356 On Switch A: # Create an IPsec transform set named protrf1. [SwitchA] ipsec transform-set protrf1 # Specify the ESP encryption and authentication algorithms. [SwitchA-ipsec-transform-set-protrf1] esp encryption-algorithm 3des-cbc [SwitchA-ipsec-transform-set-protrf1] esp authentication-algorithm md5 # Specify the encapsulation mode as transport. [SwitchA-ipsec-transform-set-protrf1] encapsulation-mode transport [SwitchA-ipsec-transform-set-protrf1] quit # Create a manual IPsec profile named profile001.
  • Page 357 # Specify the encapsulation mode as transport. [SwitchC-ipsec-transform-set-protrf1] encapsulation-mode transport [SwitchC-ipsec-transform-set-protrf1] quit # Create a manual IPsec profile named profile001. [SwitchC] ipsec profile profile001 manual # Reference IPsec transform set protrf1. [SwitchC-ipsec-profile-profile001-manual] transform-set protrf1 # Configure the inbound and outbound SPIs for ESP. [SwitchC-ipsec-profile-profile001-manual] sa spi inbound esp 256 [SwitchC-ipsec-profile-profile001-manual] sa spi outbound esp 256 # Configure the inbound and outbound SA keys for ESP.

  • Page 358: Configuring Ospfv3

    Configuring OSPFv3 Overview This chapter describes how to configure RFC 2740-compliant Open Shortest Path First version 3 (OSPFv3) for an IPv6 network. For more information about OSPFv2, see "Configuring OSPF." OSPFv3 and OSPFv2 have the following in common: • 32-bit router ID and area ID. •...

  • Page 359: Protocols And Standards

    • AS External LSA—Type-5 LSA, originated by ASBRs, and flooded throughout the AS, except stub areas and Not-So-Stubby Areas (NSSAs). Each AS External LSA describes a route to another AS. A default route can be described by an AS External LSA. •...

  • Page 360: Enabling Ospfv3

    Tasks at a glance (Optional.) Tuning and optimizing OSPFv3 networks: • Configuring OSPFv3 timers • Specifying LSA transmission delay • Configuring a DR priority for an interface • Specifying SPF calculation interval • Specifying the LSA generation interval • Ignoring MTU check for DD packets •...

  • Page 361: Configuring Ospfv3 Area Parameters

    Step Command Remarks Enable an OSPFv3 process No OSPFv3 process is enabled ospfv3 process-id area area-id on the interface. [ instance instance-id ] on an interface by default. Configuring OSPFv3 area parameters OSPFv3 has the same stub area, NSSA area, and virtual link features as OSPFv2. After you split an OSPFv3 AS into multiple areas, the LSA number is reduced and OSPFv3 applications are extended.

  • Page 362: Configuring An Ospfv3 Virtual Link

    To configure a totally NSSA area, configure the nssa no-summary command on the ABR. The ABR of a totally NSSA area does not advertise inter-area routes into the area. To configure an NSSA area: Step Command Remarks Enter system view. system-view ospfv3 [ process-id | Enter OSPFv3 view.

  • Page 363: Configuration Prerequisites

    • Broadcast—When the link layer protocol is Ethernet or FDDI, OSPFv3 considers the network type as broadcast by default. • NBMA—When the link layer protocol is ATM, Frame Relay, or X.25, OSPFv3 considers the network type as NBMA by default. •...

  • Page 364: Configuring Ospfv3 Route Control

    Configuring OSPFv3 route control Configuration prerequisites Before you configure OSPFv3 route control, complete the following tasks: • Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes. • Enable OSPFv3. Configuring OSPFv3 route summarization Route summarization enables an ABR or ASBR to summarize contiguous networks into a single network and advertise it to other areas.

  • Page 365: Configuring Ospfv3 Received Route Filtering

    Step Command Remarks Configure route asbr-summary ipv6-address By default, route summarization is summarization on an prefix-length [ cost cost | not configured on an ASBR. ASBR. not-advertise | nssa-only | tag tag ] * Configuring OSPFv3 received route filtering Step Command Remarks Enter system view.

  • Page 366: Configuring The Maximum Number Of Ospfv3 Ecmp Routes

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the OSPFv3 cost is 1 for a VLAN interface, is 0 for a loopback interface. The Configure an OSPFv3 ospfv3 cost value OSPFv3 cost is automatically computed cost for the interface.

  • Page 367: Configuring Ospfv3 Route Redistribution

    Step Command Remarks Enter system view. system-view ospfv3 [ process-id | Enter OSPFv3 view. vpn-instance vpn-instance-name ] * preference [ ase ] By default, the preference of OSPFv3 Configure a preference [ route-policy internal routes is 10, and the priority of for OSPFv3.

  • Page 368: Tuning And Optimizing Ospfv3 Networks

    Step Command Remarks ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * default-route-advertise [ [ always | Redistribute a default permit-calculate-other ] | cost cost | By default, no default route is route. route-policy route-policy-name | tag tag redistributed.

  • Page 369: Specifying Lsa Transmission Delay

    Step Command Remarks By default, the poll interval is 120 ospfv3 timer poll seconds Set the poll interval. [ instance instance-id ] seconds. The default setting is 5 seconds. ospfv3 timer retransmit Set the LSA retransmission The LSA retransmission interval cannot interval [ instance interval.

  • Page 370: Specifying The Lsa Generation Interval

    Specifying the LSA generation interval You can adjust the LSA generation interval to protect network resources and routers from being over consumed by frequent network changes. For a stable network, the minimum interval is used. If network changes become frequent, the LSA generation interval is incremented by the incremental interval ×...

  • Page 371: Disabling Interfaces From Receiving And Sending Ospfv3 Packets

    Disabling interfaces from receiving and sending OSPFv3 packets After an OSPFv3 interface is set to silent, direct routes of the interface can still be advertised in Intra-Area-Prefix LSAs through other interfaces, but other OSPFv3 packets cannot be advertised. No neighboring relationship can be established on the interface. This feature can enhance the adaptability of OSPFv3 networking.

  • Page 372: Configuring The Lsu Transmit Rate

    SNMP notifications are sent to the SNMP module, which outputs SNMP notifications according to the configured output rules. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide. The standard OSPFv3 MIB provides only single-instance MIB objects. For SNMP to correctly identify OSPFv3 management information in the standard OSPFv3 MIB, you must configure a unique context name for OSPFv3.

  • Page 373: Configuring Stub Routers

    Step Command Remarks By default, an OSPFv3 Configure the LSU interface sends a maximum of transmit-pacing interval interval count count transmit rate. three LSU packets every 20 milliseconds. Configuring stub routers A stub router is used for traffic control. It reports its status as a stub router to neighboring OSPFv3 routers.

  • Page 374: Configuring Ospfv3 Gr

    IMPORTANT: If you want to use prefix suppression, as a best practice, configure prefix suppression on all OSPFv3 routers. Configuring prefix suppression for an OSPFv3 process Enabling prefix suppression for an OSPFv3 process does not suppress the prefixes of loopback interfaces and passive interfaces.

  • Page 375: Configuring Gr Helper

    IMPORTANT: You cannot enable OSPFv3 NSR on a device that acts as GR restarter. To configure GR restarter: Step Command Remarks Enter system view. system-view ospfv3 [ process-id | Enter OSPFv3 view. vpn-instance vpn-instance-name ] * Enable the GR graceful-restart enable [ global | By default, OSPFv3 GR restarter capability.

  • Page 376: Configuring Bfd For Ospfv3

    To enable OSPFv3 NSR: Step Command Remarks Enter system view. system-view Enter OSPFv3 ospfv3 [ process-id | vpn-instance view. vpn-instance-name ] * Enable OSPFv3 By default, OSPFv3 NSR is disabled. non-stop-routing NSR. Configuring BFD for OSPFv3 Bidirectional forwarding detection (BFD) provides a mechanism to quickly detect the connectivity of links between OSPFv3 neighbors, improving the convergence speed of OSPFv3.
  • Page 377 • To implement interface-based IPsec protection, configure the same IPsec profile on the interfaces between two neighboring routers. • To implement virtual link-based IPsec protection, configure the same IPsec profile on the two routers connected over the virtual link. • To implement sham link-based IPsec protection, configure the same IPsec profile on the two routers connected over the sham link.

  • Page 378: Displaying And Maintaining Ospfv3

    Step Command Remarks ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * Enter OSPFv3 area view. area area-id sham-link source-ipv6-address destination-ipv6-address [ cost cost | Apply an IPsec profile to a dead dead-interval | hello hello-interval | By default, no IPsec profile is sham link.

  • Page 379: Ospfv3 Configuration Examples

    OSPFv3 configuration examples OSPFv3 stub area configuration example Network requirements As shown in Figure • Enable OSPFv3 on all switches. • Split the AS into three areas. • Configure Switch B and Switch C as ABRs to forward routing information between areas. •...
  • Page 380 [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 1 [SwitchB-Vlan-interface200] quit # On Switch C, enable OSPFv3 and specify the router ID as 3.3.3.3. <SwitchC> system-view [SwitchC] ospfv3 [SwitchC-ospfv3-1] router-id 3.3.3.3 [SwitchC-ospfv3-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 1 area 0 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ospfv3 1 area 2...
  • Page 381 Router ID Pri State Dead-Time InstID Interface 4.4.4.4 Full/BDR 00:00:40 Vlan400 # Display OSPFv3 routing table information on Switch D. [SwitchD] display ospfv3 routing OSPFv3 Process 1 with Router ID 4.4.4.4 ------------------------------------------------------------------------- - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route IA - Inter area route, E2 - Type 2 external route,...
  • Page 382 [SwitchD] display ospfv3 routing OSPFv3 Process 1 with Router ID 4.4.4.4 ------------------------------------------------------------------------- - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route - Selected route *Destination: ::/0 Type...

  • Page 383: Ospfv3 Nssa Area Configuration Example

    OSPFv3 Process 1 with Router ID 4.4.4.4 ------------------------------------------------------------------------- - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route - Selected route *Destination: ::/0 Type...
  • Page 384 Configure Area 1 as an NSSA area: # Configure Switch A. [SwitchA] ospfv3 [SwitchA-ospfv3-1] area 1 [SwitchA-ospfv3-1-area-0.0.0.1] nssa [SwitchA-ospfv3-1-area-0.0.0.1] quit [SwitchA-ospfv3-1] quit # Configure Switch B. [SwitchB] ospfv3 [SwitchB-ospfv3-1] area 1 [SwitchB-ospfv3-1-area-0.0.0.1] nssa [SwitchB-ospfv3-1-area-0.0.0.1] quit [SwitchB-ospfv3-1] quit # Display OSPFv3 routing information on Switch A. [SwitchA] display ospfv3 1 routing OSPFv3 Process 1 with Router ID 1.1.1.1 -------------------------------------------------------------------------...

  • Page 385: Ospfv3 Dr Election Configuration Example

    [SwitchA-ospfv3-1] quit # Display OSPFv3 routing information on Switch D. [SwitchD] display ospfv3 1 routing OSPFv3 Process 1 with Router ID 4.4.4.4 ------------------------------------------------------------------------- - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route - Selected route...
  • Page 386 Figure 90 Network diagram Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic OSPFv3: # On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1. <SwitchA> system-view [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 0 [SwitchA-Vlan-interface100] quit # On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2.
  • Page 387 [SwitchD-Vlan-interface200] quit # Display neighbor information on Switch A. The switches have the same default DR priority 1, so Switch D (the switch with the highest router ID) is elected as the DR, and Switch C is the BDR. [SwitchA] display ospfv3 peer OSPFv3 Process 1 with Router ID 1.1.1.1 Area: 0.0.0.0 -------------------------------------------------------------------------...

  • Page 388: Ospfv3 Route Redistribution Configuration Example

    3.3.3.3 Full/BDR 00:00:35 Vlan200 4.4.4.4 Full/DR 00:00:33 Vlan200 # Display neighbor information on Switch D. Switch D is still the DR. [SwitchD] display ospfv3 peer OSPFv3 Process 1 with Router ID 4.4.4.4 Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID Pri State Dead-Time InstID Interface 1.1.1.1 100 Full/DROther 00:00:30...
  • Page 389 • Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on Switch B, and set the default metric for redistributed routes to 3. Switch C can then learn the routes destined for 1::0/64 and 2::0/64, and Switch A cannot learn the routes destined for 3::0/64 or 4::0/64.
  • Page 390 [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] ospfv3 2 area 2 [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ospfv3 2 area 2 [SwitchC-Vlan-interface400] quit # Display the routing table on Switch C. [SwitchC] display ipv6 routing-table Destinations : 7 Routes : 7 Destination: ::1/128 Protocol : Direct...

  • Page 391: Ospfv3 Route Summarization Configuration Example

    Destinations : 9 Routes : 9 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64 Protocol : OSPFv3 NextHop : FE80::200:CFF:FE01:1C03 Preference: 150 Interface : Vlan300 Cost Destination: 2::/64 Protocol : OSPFv3 NextHop : FE80::200:CFF:FE01:1C03 Preference: 150 Interface...
  • Page 392 • On Switch B, configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1. Switch C can then learn the routes destined for 2::/64, 2:1:1::/64, 2:1:2::/64, and 2:1:3::/64. • On Switch B, configure route summarization to advertise only summary route 2::/16 to Switch Figure 92 Network diagram Configuration procedure Configure IPv6 addresses for interfaces.
  • Page 393 <SwitchC> system-view [SwitchC] ospfv3 2 [SwitchC-ospfv3-2] router-id 4.4.4.4 [SwitchC-ospfv3-2] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] ospfv3 2 area 2 [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ospfv3 2 area 2 [SwitchC-Vlan-interface400] quit Configure OSPFv3 route redistribution: # Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on Switch B.
  • Page 394 Interface : Vlan300 Cost Destination: 3::2/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 4::/64 Protocol : Direct NextHop : 4::1 Preference: 0 Interface : Vlan400 Cost Destination: 4::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0...

  • Page 395: Ospfv3 Gr Configuration Example

    NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 4::/64 Protocol : Direct NextHop : 4::1 Preference: 0 Interface : Vlan400 Cost Destination: 4::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: FE80::/10 Protocol : Direct NextHop : ::...

  • Page 396: Ospfv3 Nsr Configuration Example

    [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 1 [SwitchA-Vlan-interface100] quit # On Switch B, enable OSPFv3 and set the router ID to 2.2.2.2. (By default, GR helper is enabled on Switch B.) <SwitchB> system-view [SwitchB] ospfv3 1 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 100...

  • Page 397: Bfd For Ospfv3 Configuration Example

    [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 1 [SwitchA-Vlan-interface100] quit # On Switch B, enable OSPFv3, and set the router ID to 2.2.2.2. <SwitchB> system-view [SwitchB] ospfv3 1 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 1 [SwitchB-Vlan-interface200] quit # On Switch S, enable OSPFv3, set the router ID to 3.3.3.3, and enable NSR.

  • Page 398: Ipv6 Address

    Figure 95 Network diagram Table 21 Interface and IP address assignment Device Interface IPv6 address Switch A Vlan-int10 2001::1/64 Switch A Vlan-int11 2001:2::1/64 Switch B Vlan-int10 2001::2/64 Switch B Vlan-int13 2001:3::2/64 Switch C Vlan-int11 2001:2::2/64 Switch C Vlan-int13 2001:3::1/64 Configuration procedure Configure IPv6 addresses for the interfaces.
  • Page 399 [SwitchB-Vlan-interface13] quit # On Switch C, enable OSPFv3 and configure the router ID as 3.3.3.3. <SwitchC> system-view [SwitchC] ospfv3 [SwitchC-ospfv3-1] router-id 3.3.3.3 [SwitchC-ospfv3-1] quit [SwitchC] interface vlan-interface 11 [SwitchC-Vlan-interface11] ospfv3 1 area 0 [SwitchC-Vlan-interface11] quit [SwitchC] interface vlan-interface 13 [SwitchC-Vlan-interface13] ospfv3 1 area 0 [SwitchC-Vlan-interface13] quit Configure BFD: # Enable BFD and configure BFD parameters on Switch A.

  • Page 400: Ospfv3 Ipsec Profile Configuration Example

    Destination: 2001:4::/64 Protocol : O_INTRA NextHop : FE80::20F:FF:FE00:1200 Preference: 10 Interface : Vlan10 Cost The output information shows that Switch A communicates with Switch B through VLAN-interface 10. The link over VLAN-interface 10 fails. # Display routes to 2001:4::0/64 on Switch A. <SwitchA>...
  • Page 401 <SwitchB> system-view [SwitchB] ospfv3 1 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ospfv3 1 area 0 [SwitchB-Vlan-interface100] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 1 [SwitchB-Vlan-interface200] quit # On Switch C, enable OSPFv3 and specify the router ID as 3.3.3.3. <SwitchC>...
  • Page 402 On Switch B: # Create an IPsec transform set named trans. [SwitchB] ipsec transform-set trans # Specify the encapsulation mode as transport. [SwitchB-ipsec-transform-set-trans] encapsulation-mode transport # Specify the ESP encryption and authentication algorithms. [SwitchB-ipsec-transform-set-trans] esp encryption-algorithm 3des-cbc [SwitchB-ipsec-transform-set-trans] esp authentication-algorithm md5 # Specify the AH authentication algorithm.
  • Page 403 # Create an IPsec transform set named trans. [SwitchC] ipsec transform-set trans # Specify the encapsulation mode as transport. [SwitchC-ipsec-transform-set-trans] encapsulation-mode transport # Specify the ESP encryption and authentication algorithms. [SwitchC-ipsec-transform-set-trans] esp encryption-algorithm 3des-cbc # Specify the AH authentication algorithm. [SwitchC-ipsec-transform-set-trans] esp authentication-algorithm md5 [SwitchC-ipsec-transform-set-trans] ah authentication-algorithm md5 [SwitchC-ipsec-transform-set-trans] quit...
  • Page 404 [SwitchC-ospfv3-1-area-0.0.0.0] enable ipsec-profile profile002 [SwitchC-ospfv3-1-area-0.0.0.0] quit [SwitchC-ospfv3-1] quit Verifying the configuration # Verify that OSPFv3 packets between Switches A, B, and C are protected by IPsec. (Details not shown.)

  • Page 405: Configuring Ipv6 Is-Is

    Configuring IPv6 IS-IS Overview IPv6 IS-IS supports all IPv4 IS-IS features except that it advertises IPv6 routing information. This chapter describes only IPv6 IS-IS specific configuration tasks. For information about IS-IS, see "Configuring IS-IS." Intermediate System-to-Intermediate System (IS-IS) supports multiple network protocols, including IPv6.
  • Page 406 To configure IPv6 IS-IS route control: Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] Specify a preference for ipv6 preference { route-policy By default, the default IPv6 IS-IS routes. route-policy-name | preference } * setting is 15.

  • Page 407: Tuning And Optimizing Ipv6 Is-Is Networks

    Tuning and optimizing IPv6 IS-IS networks Configuration prerequisites Before you tune and optimize IPv6 IS-IS networks, complete basic IPv6 IS-IS tasks. Assigning a convergence priority to IPv6 IS-IS routes A topology change causes IS-IS routing convergence. To improve convergence speed, you can assign convergence priorities to IPv6 IS-IS routes.

  • Page 408: Displaying And Maintaining Ipv6 Is-Is

    Displaying and maintaining IPv6 IS-IS Execute display commands in any view. For other display and reset commands, see "Configuring IS-IS." Task Command Display information about routes display isis redistribute ipv6 [ ipv6-address mask-length ] redistributed by IPv6 IS-IS. [ level-1 | level-2 ] [ process-id ] display isis route ipv6 [ ipv6-address ] [ [ level-1 | level-2 ] | Display IPv6 IS-IS routing information.
  • Page 409 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis ipv6 enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] ipv6 enable [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] isis ipv6 enable 1 [SwitchB-Vlan-interface200] quit # Configure Switch C.
  • Page 410 Level-1 IPv6 Forwarding Table ----------------------------- Destination : :: PrefixLen: 0 Flag : R/-/- Cost : 10 Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan100 Destination : 2001:1:: PrefixLen: 64 Flag : D/L/- Cost : 10 Next Hop : Direct Interface: Vlan100 Destination : 2001:2:: PrefixLen: 64 Flag : R/-/-...
  • Page 411 Route information for IS-IS(1) ------------------------------ Level-1 IPv6 Forwarding Table ----------------------------- Destination : 2001:1:: PrefixLen: 64 Flag : D/L/- Cost : 10 Next Hop : Direct Interface: Vlan100 Destination : 2001:2:: PrefixLen: 64 Flag : D/L/- Cost : 10 Next Hop : Direct Interface: Vlan200 Destination : 2001:3::...

  • Page 412: Bfd For Ipv6 Is-Is Configuration Example

    ----------------------------- Destination : 2001:1:: PrefixLen: 64 Flag : R/-/- Cost : 20 Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan300 Destination : 2001:2:: PrefixLen: 64 Flag : R/-/- Cost : 20 Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan300 Destination : 2001:3:: PrefixLen: 64 Flag : D/L/- Cost...
  • Page 413 Device Interface IPv6 address Switch B Vlan-int13 2001:3::2/64 Switch C Vlan-int11 2001:2::2/64 Switch C Vlan-int13 2001:3::1/64 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure IPv6 IS-IS: # Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] ipv6 enable [SwitchA-isis-1] quit...
  • Page 414 # Enable BFD and configure BFD parameters on Switch A. [SwitchA] bfd session init-mode active [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] isis ipv6 bfd enable [SwitchA-Vlan-interface10] bfd min-transmit-interval 500 [SwitchA-Vlan-interface10] bfd min-receive-interval 500 [SwitchA-Vlan-interface10] bfd detect-multiplier 7 [SwitchA-Vlan-interface10] return # Enable BFD and configure BFD parameters on Switch B. [SwitchB] bfd session init-mode active [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] isis ipv6 bfd enable...
  • Page 415 The output shows that Switch A and Switch B communicate through VLAN-interface 11.

  • Page 416: Configuring Ipv6 Pbr

    Configuring IPv6 PBR Overview Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop for packets that match specific criteria such as ACLs. A device forwards received packets using the following process: The device uses PBR to forward matching packets. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets.

  • Page 417: Pbr And Track

    Relationship between the match mode and clauses on the node Does a packet match all the Match mode if-match clauses on the In permit mode In deny mode node? • If the node is configured with an apply clause, IPv6 PBR executes the apply clause on the node.

  • Page 418: Configuring Match Criteria For An Ipv6 Node

    Step Command Remarks Create an IPv6 policy or policy node, and ipv6 policy-based-route policy-name [ deny | By default, no IPv6 policy enter IPv6 policy permit ] node node-number node is created. node view. Configuring match criteria for an IPv6 node Step Command Remarks...

  • Page 419: Configuring Ipv6 Interface Pbr

    To configure IPv6 local PBR: Step Command Remarks Enter system view. system-view By default, no policy is locally ipv6 local policy-based-route Apply a policy locally. applied. policy-name Configuring IPv6 interface PBR Configure IPv6 PBR by applying an IPv6 policy to an interface. IPv6 PBR uses the policy to guide the forwarding of IPv6 packets received on the interface.

  • Page 420: Ipv6 Pbr Configuration Examples

    IPv6 PBR configuration examples Packet type-based IPv6 local PBR configuration example Network requirements As shown in Figure 99, configure IPv6 PBR on Switch A to forward all TCP packets to the next hop 1::2. Switch A forwards other packets according to the routing table. Figure 99 Network diagram Configuration procedure Configure Switch A:...

  • Page 421: Packet Type-Based Ipv6 Interface Pbr Configuration Example

    # Configure the IPv6 address of VLAN-interface 10. [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ipv6 address 1::2 64 Configure Switch C: # Create VLAN 20. <SwitchC> system-view [SwitchC] vlan 20 [SwitchC-vlan20] quit # Configure the IPv6 address of VLAN-interface 20. [SwitchC] interface vlan-interface 20 [SwitchC-Vlan-interface20] ipv6 address 2::2 64 Verifying the configuration # Telnet to Switch B on Switch A.
  • Page 422 Figure 100 Network diagram Configuration procedure Configure Switch A: # Create VLAN 10 and VLAN 20. <SwitchA> system-view [SwitchA] vlan 10 [SwitchA-vlan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure RIPng. [SwitchA] ripng 1 [SwitchA-ripng-1] quit [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ipv6 address 1::1 64 [SwitchA-Vlan-interface10] ripng 1 enable [SwitchA-Vlan-interface10] quit...
  • Page 423 [SwitchA-pbr6-aaa-5] quit # Configure IPv6 interface PBR by applying policy aaa to VLAN-interface 11. [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] ipv6 address 10::2 64 [SwitchA-Vlan-interface11] undo ipv6 nd ra halt [SwitchA-Vlan-interface11] ripng 1 enable [SwitchA-Vlan-interface11] ipv6 policy-based-route aaa Configure Switch B: # Create VLAN 10.

  • Page 424: Configuring Routing Policies

    Configuring routing policies Overview Routing policies control routing paths by filtering and modifying routing information. This chapter describes both IPv4 and IPv6 routing policies. Routing policies can filter advertised, received, and redistributed routes, and modify attributes for specific routes. To configure a routing policy: Configure filters based on route attributes, such as destination address and the advertising router's address.

  • Page 425: Configuring Filters

    Each node has a match mode of permit or deny. • permit—Specifies the permit match mode for a routing policy node. If a route matches all the if-match clauses of the node, it is handled by the apply clauses of the node. The route does not match against the next node unless the continue clause is configured.

  • Page 426: Configuring An As Path List

    Configuring an IPv6 prefix list If all items are set to deny mode, no routes can pass the IPv6 prefix list. To allow unmatched IPv6 routes to pass, you must configure the permit :: 0 less-equal 128 item following multiple deny items.

  • Page 427: Configuring An Extended Community List

    Configuring an extended community list You can configure multiple items for an extended community list that is identified by a number. The relationship between the items is logical OR. A route that matches one item matches the extended community list. To configure an extended community list: Step Command...
  • Page 428 Step Command Remarks route-policy route-policy-name Enter routing policy node view. { deny | permit } node node-number • Match IPv4 routes whose By default, no ACL or prefix destination, next hop, or source list match criterion is matches an ACL or IPv4 prefix configured.

  • Page 429: Configuring Apply Clauses

    Configuring apply clauses Except for the apply commands used for setting the next hop for IPv4 and IPv6 routes, all apply commands are the same for IPv4 and IPv6 routing. To configure apply clauses: Step Command Remarks Enter system view. system-view route-policy Enter routing policy node...

  • Page 430: Configuring The Continue Clause

    Step Command Remarks By default, no prefix priority is set, apply prefix-priority { critical 16. Set a prefix priority. which means the prefix priority is | high | medium } low. By default, no tag value is set for 17. Set a tag value for IGP routes. apply tag value IGP routes.

  • Page 431: Displaying And Maintaining The Routing Policy

    Displaying and maintaining the routing policy Execute display commands in any view and reset commands in user view. Task Command Display BGP AS path list information. display ip as-path [ as-path-number ] Display BGP community list display ip community-list [ basic-community-list-number | information.
  • Page 432 # Configure Switch C. <SwitchC> system-view [SwitchC] isis [SwitchC-isis-1] is-level level-2 [SwitchC-isis-1] network-entity 10.0000.0000.0001.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis enable [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 201 [SwitchC-Vlan-interface201] isis enable [SwitchC-Vlan-interface201] quit [SwitchC] interface vlan-interface 202 [SwitchC-Vlan-interface202] isis enable [SwitchC-Vlan-interface202] quit [SwitchC] interface vlan-interface 203 [SwitchC-Vlan-interface203] isis enable...
  • Page 433 Routing for Network Destination Cost Type NextHop AdvRouter Area 192.168.1.0/24 Stub 192.168.1.1 192.168.1.1 0.0.0.0 Routing for ASEs Destination Cost Type NextHop AdvRouter 172.17.1.0/24 Type2 192.168.1.2 192.168.2.2 172.17.2.0/24 Type2 192.168.1.2 192.168.2.2 172.17.3.0/24 Type2 192.168.1.2 192.168.2.2 Total Nets: 4 Intra Area: 1 Inter Area: 0 ASE: 3 NSSA: 0...

  • Page 434: Routing Policy Configuration Example For Ipv6 Route Redistribution

    172.17.2.0/24 Type2 192.168.1.2 192.168.2.2 172.17.3.0/24 Type2 192.168.1.2 192.168.2.2 Total Nets: 4 Intra Area: 1 Inter Area: 0 ASE: 3 NSSA: 0 The output shows that the cost of route 172.17.1.0/24 is 100 and the tag of route 172.17.2.0/24 is 20. Routing policy configuration example for IPv6 route redistribution Network requirements...
  • Page 435 [SwitchA-route-policy-static2ripng-0] quit [SwitchA] route-policy static2ripng permit node 10 [SwitchA-route-policy-static2ripng-10] quit # Enable RIPng and apply the routing policy to static route redistribution. [SwitchA] ripng [SwitchA-ripng-1] import-route static route-policy static2ripng Configure Switch B: # Configure the IPv6 address for VLAN-interface 100. <SwitchB>...

  • Page 436: 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 Bold text represents commands and keywords that you enter literally as shown. Boldface Italic text represents arguments that you replace with actual values.

  • Page 437: 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 438: 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 439: 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 440 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 441 Index IP routing BGP optimal route advertisement, Numerics IP routing BGP route advertisement rules, 4-byte IP routing BGP route generation, IPv4 BGP AS number suppression, IP routing RIP summary route advertisement, IPv6 BGP AS number suppression, IPv4 BGP basics, IPv4 BGP BFD, IP routing BGP 6PE, IPv4 BGP COMMUNITY, 241, 270...
  • Page 442 OSPF network type, IPv6 BGP 4-byte AS number suppression, OSPF NSSA area, IPv6 BGP AS number substitution, OSPF stub area, IPv6 BGP basics, OSPF totally NSSA area, IPv6 BGP BFD, OSPF totally stub area, IPv6 BGP configuration, OSPF virtual link, IPv6 BGP fake AS number advertisement, OSPFv3 area parameter, IPv6 BGP FRR,...
  • Page 443 IPv4 BGP AS_PATH optimal route RIPv2 automatic route summarization enable, selection, IPv4 BGP COMMUNITY, 241, 241, 270 backbone IPv4 BGP fake AS number OSPF backbone area, advertisement, OSPF router type, IPv4 BGP local AS number appearance, backing up IPv4 BGP MED AS route comparison (confederation peers), IP routing route backup, IPv4 BGP MED AS route comparison (diff...
  • Page 444 static routing BFD bidirectional control mode peer group, 184, 195 (direct next hop), protocols and standards, static routing BFD bidirectional control mode route advertisement, (indirect next hop), route dampening, static routing BFD configuration, route distribution control, static routing BFD single-hop echo mode, route filtering policies, BGP, 178,...
  • Page 445 calculating IPv6 BGP MED AS route comparison (confederation peers), IS-IS SPF calculation interval, configuring OSPF FRR backup next hop calculation (LFA algorithm), BGP dynamic peer, OSPF interface cost, BGP dynamic peer (IPv4 unicast address), OSPF route calculation, BGP dynamic peer (IPv6 unicast address), OSPF SPF calculation interval, BGP update sending delay, OSPFv3 SPF calculation interval,...
  • Page 446 IP routing RIP summary route IPv6 BGP route distribution filtering policies, advertisement, IPv6 BGP route preference, IP routing static route, IPv6 BGP route reception filtering policies, IPv4 BGP, IPv6 BGP route reflector, 242, 293 IPv4 BGP AS number substitution, IPv6 BGP route update interval, IPv4 BGP basics, IPv6 default route, IPv4 BGP BFD,...
  • Page 447 IS-IS LSP-calculated route filtering, OSPF NSR, 92, 116 IS-IS network management, OSPF packet DSCP value, IS-IS NSR, 150, 169 OSPF PIC, IS-IS redistributed route filtering, OSPF PIC BFD, IS-IS route control, OSPF preference, IS-IS route convergence priority, OSPF prefix prioritization, IS-IS route filtering, OSPF prefix suppression, IS-IS route leaking,...
  • Page 448 OSPFv3 redistributed route summarization RIPng poison reverse, (ASBR), RIPng preference, OSPFv3 redistributed route tag, RIPng received/redistributed route filtering, OSPFv3 route control, RIPng route control, OSPFv3 route redistribution, RIPng route redistribution, 335, 341 OSPFv3 route redistribution (another routing RIPng route summarization, protocol), RIPng routing metric, OSPFv3 route redistribution (default...
  • Page 449 IPv6 static route BFD control mode (direct OSPFv3 route redistribution (default route), next hop), RIP default route advertisement, IPv6 static route BFD control mode (indirect RIPng default route advertisement, next hop), static routing configuration. See under static IS-IS route control, routing IS-IS SPF calculation interval, delaying...
  • Page 450 IS-IS DIS election configuration, OSPFv3 interface DR priority, IS-IS interface DIS priority, DSCP disabling OSPF packet DSCP value, IPv4 BGP AS_PATH optimal route DSP (IS-IS area address), selection, dynamic IPv4 BGP session establishment disable, BGP dynamic peer, IPv6 BGP AS_PATH optimal route IP routing dynamic routing protocols, selection, IS-IS system ID >...
  • Page 451 IP routing EBGP direct connections after link RIPv2 automatic route summarization, failure, support for IPv6 routes with prefixes longer than IP routing ECMP enhanced mode, 64 bits, IP routing RIP (interface), enhancing IP routing RIP (network), IS-IS network security, IPv4 BGP 4-byte AS number establishing suppression, IPv4 BGP multiple hop EBGP session...
  • Page 452 IPv6 BGP route reflector, OSPFv3 NSR configuration, IS-IS LSP-calculated routes, PBR configuration, 312, 313, 314, 315 IS-IS redistributed routes, PBR configuration (interface), IS-IS routes, PBR configuration (interface/packet type-based), OSPF received route filtering, PBR configuration (local), OSPF Type-3 LSA filtering, PBR configuration (local/packet type-based), OSPFv3 Inter-Area-Prefix LSA filtering, PBR policy configuration, OSPFv3 received route filtering,...
  • Page 453 OSPFv3 GR restarter configuration, OSPF configuration, 60, 66, 96 OSPFv3 trigger, OSPF DR election configuration, RIP configuration, OSPF FRR configuration, RIP GR helper configuration, OSPF GR configuration, RIP GR restarter configuration, OSPF route redistribution configuration, RIPng configuration, OSPF route summarization configuration, group OSPF virtual link configuration, IP routing BGP peer group,...
  • Page 454 PBR configuration (interface/packet BGP FRR, type-based), BGP GR, Intermediate System-to-Intermediate System. BGP GR helper, IS-IS BGP GR restarter, internal BGP GTSM configuration, IP routing BGP. Use IBGP BGP large scale network management, OSPF router type, BGP large-scale network, INTERNET BGP load balancing, IP routing BGP COMMUNITY path BGP MED attribute, attribute,...
  • Page 455 IS-IS authentication, IS-IS redistributed route filtering, IS-IS authentication (area), IS-IS route control, IS-IS authentication (neighbor IS-IS route convergence priority, relationship), IS-IS route filtering, IS-IS authentication (routing domain), IS-IS route leaking, 128, 138 IS-IS automatic cost calculation, IS-IS route redistribution, 137, 162 IS-IS basic configuration, IS-IS route summarization, IS-IS basics configuration,...
  • Page 456 OSPF LSA generation interval, OSPFv3 IPsec profile configuration, OSPF LSA transmission delay, OSPFv3 LSA generation interval, OSPF LSDB external LSAs max number, OSPFv3 LSA transmission delay, OSPF LSU transmit rate, OSPFv3 LSU transmit rate, OSPF maintain, OSPFv3 maintain, OSPF neighbor state change, OSPFv3 NBMA neighbor, OSPF network management traps, OSPFv3 neighbor state change logging,...
  • Page 457 policy creation, RIP routing loop prevention, policy display, RIP split horizon configuration, policy extended community list, RIP summary route advertisement, policy filter configuration, RIP timer configuration, policy filtering, RIP update source IP address check, policy filters, RIP version configuration, policy if-match clause, RIP versions, policy IP prefix list, RIPng basic configuration,...
  • Page 458 static routing configuration, 8, 8 AS_PATH optimal route selection, static routing default route configuration, basic configuration, static routing FRR configuration, 11, 20 BFD configuration, 248, 283 support for IPv6 routes with prefixes longer COMMUNITY configuration, 241, 270 than 64 bits, confederation configuration, troubleshooting BGP, configuration,...
  • Page 459 peer protection (low memory exemption), routing policy configuration, 413, 420 IPv4 IBGP routing policy configuration (IPv6 route redistribution), peer group, routing policy IP prefix list, IPv6 routing policy prefix list, IP routing FIB route max lifetime, IPv6 BGP IP routing RIB label max lifetime, 4-byte AS number suppression, IP routing RIB route max lifetime, 6PE configuration,...
  • Page 460 session establishment disable, area, IPv6 EBGP area address, peer group, authentication (area), peer protection (low memory exemption), authentication (neighbor relationship), IPv6 IBGP authentication (routing domain), peer group, authentication configuration, IPv6 IS-IS basic configuration, 132, 153 basic configuration, 394, 397 BFD configuration, 150, 172 BFD configuration, 396, 401...
  • Page 461 network security enhancement, IPv6 BGP routes received from peer/peer group, network tuning, link nonstop routing (NSR) configuration, 150, 169 IP routing EBGP direct connection after link NSAP address format, failure, N-SEL, IPv4 BGP BFD, PDU CLVs, IPv6 BGP BFD, PDU hello type, IS-IS automatic cost calculation, PDU LSP type, IS-IS global cost,...
  • Page 462 IS-IS neighbor state change, OSPFv3 packet type, OSPF log count, OSPF neighbor state change, OSPF LSU packet, OSPFv3 neighbor state change logging, OSPF LSU transmit rate, loop OSPFv3 LSU transmit rate, IP routing BGP FRR, OSPFv3 packet type, RIP routing loop prevention, maintaining OSPF AS External LSA, IP routing BGP,...
  • Page 463 IPv4 BGP MED AS route comparison IPv4 BGP FRR, (per-AS), IPv4 BGP GR, IPv4 BGP MED default value, IPv4 BGP load balancing, IPv6 BGP MED AS route comparison IPv4 BGP path selection, (confederation peers), IPv4 BGP route reflector, IPv6 BGP MED AS route comparison (diff IPv4 BGP route summarization, ASs), IPv4 BGP-IGP route redistribution,...
  • Page 464 OSPFv3 neighbor state change logging, IP routing BGP route selection, 182, 182 OSPFv3 NSSA area configuration, IP routing BGP route summarization, 184, 205 OSPFv3 P2MP neighbor, IP routing BGP session state change logging, OSPFv3 route control, IP routing BGP SNMP notification enable, OSPFv3 route redistribution, IP routing BGP soft reset, OSPFv3 stub area configuration,...
  • Page 465 IPv4 BGP private AS number removal, IPv6 static route BFD control mode (direct next hop), IPv4 BGP received route preferred value, IPv6 static route BFD control mode (indirect next IPv4 BGP route dampening, hop), IPv4 BGP route preference, IPv6 static route BFD echo mode (single IPv4 BGP route update interval, hop), IPv4 BGP routes received from peer/peer...
  • Page 466 IS-IS route leaking, OSPF RFC 1583 compatibility, IS-IS route redistribution, OSPF route calculation, IS-IS routing domain, OSPF route control, IS-IS security enhancement, OSPF route redistribution, IS-IS SPF calculation interval, OSPF route summarization, IS-IS system ID > host name mapping, OSPF route types, OSPF area, OSPF SPF calculation interval, OSPF area configuration (NSSA),...
  • Page 467 PBR node action, RIPng route summarization, PBR node creation, RIPng routing metric configuration, PBR node match criteria, RIPng split horizon, PBR policy, RIPng timer configuration, PBR policy configuration, RIPv1 message zero field check, PBR-Track collaboration, RIPv2 message authentication configuration, RIP additional routing metric configuration, RIPv2 route summarization configuration, RIP basic configuration, routing policy apply clause,...
  • Page 468 IPv6 BGP BFD, RIPng route redistribution, IPv6 BGP configuration, routing policy configuration, 413, 420 IPv6 BGP FRR, static routing basic configuration, IPv6 BGP packet IPsec, static routing BFD configuration (direct next hop), IPv6 BGP route reflector, static routing BFD configuration (indirect next IPv6 default route configuration, hop), IPv6 IS-IS basic configuration,...
  • Page 469 NET, IP routing BGP path attribute, N-SEL (IS-IS), OSPF, 347, OSPFv3 See also area configuration, IP routing BGP NSR, area configuration (NSSA), 70, 106 IS-IS NSR, area configuration (stub), 70, 103 IS-IS NSR configuration, areas, OSPF configuration, authentication configuration, OSPF NSR configuration, backbone area, OSPFv3 NSR, basic configuration,...
  • Page 470 LSA types, display, LSDB external LSAs max number, DR election configuration, LSU transmit rate configuration, ECMP route max number, maintain, enable, neighbor state change logging, GR configuration, 363, 384 network management configuration, GR helper configuration, network optimization, GR restarter configuration, network tuning, GR trigger, network type configuration,...
  • Page 471 P2MP OSPF GR restarter, OSPF interface network type, OSPF hello, OSPF network type, OSPF interface packet send/receive disable, OSPFv3 P2MP neighbor, OSPF ISPF, OSPF LSAck, IS-IS network type, OSPF LSDB external LSAs max number, OSPF interface network type, OSPF LSR, OSPF network type, 65, 71 OSPF LSU,...
  • Page 472 IS-IS LSP parameters, IS-IS SNP type, IS-IS route convergence priority, IS-IS types, IS-IS SPF calculation interval, OSPF redistributed route default IP routing BGP 6PE, parameters, IP routing BGP 6PE basics, OSPFv3 area parameter, IP routing BGP 6PE optional capabilities, path IPv6 BGP 6PE configuration, IP routing BGP MED attribute, peer...
  • Page 473 IPv6 PBR if-match clause, IP routing BGP received route, IPv6 PBR interface configuration, preferring IPv6 PBR interface configuration (packet IS-IS preference specification, type-based), prefix IPv6 PBR local configuration, OSPF PIC configuration, IPv6 PBR local configuration (packet OSPF prefix prioritization, type-based), OSPF prefix suppression, IPv6 PBR match mode/node clause OSPFv3 prefix suppression,...
  • Page 474 configuring IP routing BGP GR helper, configuring IPv4 BGP confederation, configuring IP routing BGP GR restarter, configuring IPv4 BGP default local preference, configuring IP routing BGP GTSM, configuring IPv4 BGP FRR, configuring IP routing BGP large-scale network, configuring IPv4 BGP GR, configuring IP routing BGP MED attribute, configuring IPv4 BGP holdtime, configuring IP routing BGP NSR,...
  • Page 475 configuring IPv6 BGP route reflector, 242, 293 configuring IS-IS LSP parameters, configuring IPv6 BGP route update configuring IS-IS LSP timer, interval, configuring IS-IS LSP-calculated route configuring IPv6 BGP soft reset manually, filtering, configuring IPv6 EBGP peer group, configuring IS-IS network management, configuring IPv6 IBGP peer group, configuring IS-IS NSR, 150, 169...
  • Page 476 configuring OSPF interface network type configuring OSPFv3 NBMA neighbor, (P2MP), configuring OSPFv3 network management, configuring OSPF interface network type configuring OSPFv3 network type, (P2P), configuring OSPFv3 network type (interface), configuring OSPF log count, configuring OSPFv3 NSR, 364, 385 configuring OSPF LSDB external LSAs max configuring OSPFv3 NSSA area, 350, 372 number,...
  • Page 477 configuring RIP network management, configuring static routing basics, configuring RIP packet send rate, configuring static routing BFD (direct next hop), configuring RIP poison reverse, configuring static routing BFD (indirect next configuring RIP preference, hop), configuring RIP received/redistributed route configuring static routing BFD bidirectional control filtering, mode (direct next hop), configuring RIP route control,...
  • Page 478 enabling IP routing BGP route flapping enabling OSPF neighbor state change logging, logging, enabling OSPF PIC, enabling IP routing BGP session state change enabling OSPF RFC 1583 compatibility, logging, enabling OSPFv3, enabling IP routing BGP SNMP enabling OSPFv3 neighbor state change notification, logging, enabling IP routing EBGP direct connections...
  • Page 479 permitting IPv4 BGP local AS number tuning IPv6 IS-IS network, appearance, tuning IS-IS network, permitting IPv6 BGP local AS number tuning OSPFv3 network, appearance, tuning RIPng network, protecting IPv4 EBGP peer (low memory protecting exemption), IPv4 EBGP peer (low memory exemption), protecting IPv6 EBGP peer (low memory IPv6 EBGP peer (low memory exemption), exemption),...
  • Page 480 OSPFv3 redistributed route tag, maintaining, OSPFv3 route (another routing protocol), neighbor specification, OSPFv3 route (default route), network management configuration, OSPFv3 route redistribution, network optimization, RIP received/redistributed route filtering, network tuning, RIP routes, operation, RIPng received/redistributed route packet max length, filtering, packet send rate configuration, RIPng route redistribution, 335, 341...
  • Page 481 route summarization, IPv4 BGP MED AS route comparison (confederation peers), routing metric configuration, IPv4 BGP MED AS route comparison (diff split horizon configuration, ASs), timer configuration, IPv4 BGP MED AS route comparison RIPv1 (per-AS), message zero field check enable, IPv4 BGP ORIGINATOR_ID attribute, protocols and standards, IPv4 BGP route dampening, RIP basic configuration,...
  • Page 482 IS-IS LSP-calculated route filtering, routing policy filters, IS-IS redistributed route filtering, static routing basic configuration, IS-IS route control, static routing BFD configuration, IS-IS route filtering, static routing BFD configuration (direct next hop), IS-IS route leaking, 138, 138 static routing BFD configuration (indirect next IS-IS route redistribution, 137, 162 hop),...
  • Page 483 display, IPv4 BGP session establishment disable, maintain, IPv6 BGP multiple hop EBGP session establishment, rule IPv6 BGP session establishment disable, IP routing BGP route advertisement rules, setting IS-IS LSDB overload bit, saving RIP packet max length, IPv4 BGP route update, SNMP IPv6 BGP route update, IP routing BGP SNMP notification enable,...
  • Page 484 basic configuration, OSPFv3 prefix suppression, BFD configuration (direct next hop), RIP suppress timer, BFD configuration (indirect next hop), switch configuration, 8, 13 IP routing IS-IS configuration, default route configuration, switchover display, IP routing BGP NSR, FRR configuration, system IPv6. See IPv6 static routing IS-IS system ID, routing configuration,...
  • Page 485 OSPF packet timer, IS-IS network, OSPF poll packet timer, OSPF network, OSPFv3 timer, OSPFv3 network, RIP garbage-collect timer, RIP networks, RIP suppress timer, RIPng network, RIP timeout timer, tunneling RIP update timer, IPv6 BGP packet IPsec, RIPng timer configuration, Type 1 external OSPF route type, IPv6 Interface Address, Type 2 external...
  • Page 486 zero field check RIPng packet, zero field check (RIPv1),...

Table of Contents