HPE FlexNetwork HSR6600 Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. FlexNetwork HSR6600
  6. Configuration manual
HPE FlexNetwork HSR6600 Configuration Manual

HPE FlexNetwork HSR6600 Configuration Manual

Comware 7 layer 3 - ip routing
Hide thumbs Also See for FlexNetwork HSR6600:
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
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation Manual
HPE FlexNetwork HSR6600 Routers
Comware 7 Layer 3—IP Routing

Configuration Guide

Part number: 5200-3472
Software version: HSR6602-CMW710-R7607
Document version: 6W100-20170412

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FlexNetwork HSR6600 and is the answer not in the manual?

Questions and answers

Related Manuals for HPE FlexNetwork HSR6600

Summary of Contents for HPE FlexNetwork HSR6600

  • Page 1: Configuration Guide

    HPE FlexNetwork HSR6600 Routers Comware 7 Layer 3—IP Routing Configuration Guide Part number: 5200-3472 Software version: HSR6602-CMW710-R7607 Document version: 6W100-20170412...
  • Page 2 © Copyright 2017 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 Extension attribute redistribution ··································································································· 3 Setting the maximum lifetime for routes and labels in the RIB ······························································...
  • Page 4 Configuration prerequisites ·································································································· 33 Setting RIP timers ············································································································· 33 Enabling split horizon and poison reverse ··············································································· 34 Setting the maximum number of ECMP routes ········································································· 34 Enabling zero field check on incoming RIPv1 messages ···························································· 35 Enabling source IP address check on incoming RIP updates ······················································ 35 Configuring RIPv2 message authentication ·············································································...
  • Page 5 Configuring OSPF route control ·································································································· 80 Configuration prerequisites ·································································································· 80 Configuring OSPF route summarization ················································································· 81 Configuring received OSPF route filtering ··············································································· 82 Configuring Type-3 LSA filtering ··························································································· 82 Setting an OSPF cost for an interface ···················································································· 82 Setting the maximum number of ECMP routes ········································································· 83 Setting OSPF preference ····································································································...
  • Page 6 BFD for OSPF configuration example ·················································································· 129 OSPF FRR configuration example ······················································································ 132 Troubleshooting OSPF configuration ·························································································· 134 No OSPF neighbor relationship established ·········································································· 134 Incorrect routing information ······························································································ 135 Configuring IS-IS ·········································································· 136 Overview ······························································································································ 136 Terminology ··················································································································· 136 IS-IS address format ········································································································...
  • Page 7 Configuration prerequisites ································································································ 169 Configuration guidelines ··································································································· 169 Configuration procedure ··································································································· 170 Configuring IS-IS MTR ············································································································ 172 Displaying and maintaining IS-IS ······························································································· 173 IS-IS configuration examples ···································································································· 175 Basic IS-IS configuration example ······················································································· 175 DIS election configuration example ····················································································· 179 IS-IS route redistribution configuration example ·····································································...
  • Page 8 Configuring BGP load balancing ························································································· 276 Configuring IPsec for IPv6 BGP ·························································································· 278 Disabling BGP to establish a session to a peer or peer group ··················································· 279 Configuring GTSM for BGP ······························································································· 280 Configuring BGP soft-reset ································································································ 281 Protecting an EBGP peer when memory usage reaches level 2 threshold ··································· 287 Configuring an update delay for local MPLS labels ·································································...
  • Page 9 PBR configuration task list ······································································································· 380 Configuring a policy ················································································································ 381 Creating a node ·············································································································· 381 Setting match criteria for a node ························································································· 381 Configuring actions for a node ···························································································· 381 Configuring PBR ···················································································································· 383 Configuring local PBR ······································································································ 383 Configuring interface PBR ·································································································...
  • Page 10 Configuring RIPng FRR ···································································································· 421 RIPng IPsec profile configuration example ············································································ 424 Configuring OSPFv3 ····································································· 427 Overview ······························································································································ 427 OSPFv3 packets ············································································································· 427 OSPFv3 LSA types ·········································································································· 427 Protocols and standards ··································································································· 428 OSPFv3 configuration task list ·································································································· 428 Enabling OSPFv3 ·················································································································· 429 Configuring OSPFv3 area parameters ························································································...
  • Page 11 OSPFv3 NSR configuration example ··················································································· 468 BFD for OSPFv3 configuration example ··············································································· 469 OSPFv3 FRR configuration example ··················································································· 471 OSPFv3 IPsec profile configuration example ········································································· 474 Configuring IPv6 IS-IS ··································································· 479 Overview ······························································································································ 479 Configuring basic IPv6 IS-IS ····································································································· 479 Configuring IPv6 IS-IS route control ···························································································...
  • Page 12 Configuring apply clauses ································································································· 517 Configuring the continue clause ·························································································· 519 Displaying and maintaining the routing policy ··············································································· 519 Routing policy configuration examples ························································································ 520 Routing policy configuration example for IPv4 route redistribution ·············································· 520 Routing policy configuration example for IPv6 route redistribution ·············································· 523 Configuring MTR ··········································································...

  • Page 13: Configuring Basic Ip Routing

    Configuring basic IP routing IP routing directs IP packet forwarding on routers based on a routing table. This chapter focuses on unicast routing protocols. For more information about multicast routing protocols, see IP Multicast Configuration Guide. Routing table A RIB contains the global routing information and related information, including route recursion, route redistribution, and route extension information.

  • Page 14: Dynamic Routing Protocols

    • Cost—If multiple routes to a destination have the same preference, the one with the smallest cost is the optimal route. • NextHop—Next hop. • Interface—Output interface. Dynamic routing protocols Static routes work well in small, stable networks. They are easy to configure and require fewer system resources.

  • Page 15: Load Sharing

    Route type Preference 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 16: Setting 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. Setting 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 17: Configuring Rib Nsr

    Step Command Remarks By default, the maximum Set the maximum lifetime for lifetime for routes in the FIB fib lifetime seconds IPv4 routes in the FIB. is 600 seconds. To set the maximum lifetime for routes in the FIB (IPv6): Step Command Remarks...

  • Page 18: Configuring Inter-Protocol Frr

    Step Command Remarks By default, RIB NSR is Enable IPv6 RIB NSR. non-stop-routing disabled. Configuring inter-protocol FRR CAUTION: This feature uses the next hop of a route from a different protocol as the backup next hop for the faulty route, which might cause loops. Inter-protocol fast reroute (FRR) enables fast rerouting between routes of different protocols to reduce the service interruption time caused by unreachable next hops.

  • Page 19: Displaying And Maintaining A Routing Table

    Displaying and maintaining a routing table Execute display commands in any view and reset commands in user view. Task Command display ip routing-table [ topology topo-name | vpn-instance Display routing table information. vpn-instance-name ] [ verbose ] Display information about routes display ip routing-table [ topology topo-name | vpn-instance permitted by an IPv4 basic ACL.
  • Page 20 Task Command Display route attribute information in display ipv6 rib attribute [ attribute-id ] the IPv6 RIB. Display IPv6 RIB GR state display ipv6 rib graceful-restart information. display ipv6 rib nib [ self-originated ] [ nib-id ] [ verbose ] Display next hop information in the IPv6 RIB.

  • Page 21: 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 22: Configuring Bfd For Static Routes

    Step Command Remarks • Method 1: ip route-static { dest-address { mask-length | mask } | group group-name } { interface-type interface-number [ next-hop-address ] | next-hop-address | vpn-instance d-vpn-instance-name next-hop-address } [ permanent | track track-entry-number ] [ preference preference ] [ tag tag-value ] [ description text ] •...

  • Page 23: Single-Hop Echo Mode

    • Specify an indirect next hop and a specific BFD packet source address for the static route. To configure BFD control mode for a static route (direct next hop): Step Command Remarks Enter system view. system-view • Method 1: ip route-static dest-address { mask-length | mask } interface-type interface-number next-hop-address bfd control-packet [ preference preference ] [ tag tag-value ]...

  • Page 24: Configuring Static Route Frr

    Step Command Remarks By default, the source address of echo packets is not configured. Configure the source address of bfd echo-source-ip ip-address For more information about echo packets. this command, see High Availability Command Reference. • Method 1: ip route-static dest-address { mask-length | mask } interface-type interface-number next-hop-address bfd echo-packet [ preference preference ] [ tag tag-value ]...

  • Page 25: Configuration Procedure

    Configuration procedure Configuring static route FRR by specifying a backup next hop Step Command Remarks Enter system view. system-view • 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 ] [ preference preference ] [ tag tag-value ] [ description text ]...

  • Page 26: Displaying And Maintaining Static Routes

    Step Command Remarks By default, the source IP address of BFD echo packets is not configured. Configure the source IP The source IP address cannot be address of BFD echo on the same network segment as bfd echo-source-ip ip-address packets. any local interface's IP address.
  • Page 27 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure static routes: # Configure a default route on Router A. <RouterA> system-view [RouterA] ip route-static 0.0.0.0 0.0.0.0 1.1.4.2 # Configure two static routes on Router B. <RouterB> system-view [RouterB] ip route-static 1.1.2.0 255.255.255.0 1.1.4.1 [RouterB] ip route-static 1.1.3.0 255.255.255.0 1.1.5.6 # Configure a default route on Router C.

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

    Pinging 1.1.2.2 with 32 bytes of data: Reply from 1.1.2.2: bytes=32 time=1ms TTL=126 Reply from 1.1.2.2: bytes=32 time=1ms TTL=126 Reply from 1.1.2.2: bytes=32 time=1ms TTL=126 Reply from 1.1.2.2: bytes=32 time=1ms TTL=126 Ping statistics for 1.1.2.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms # Use the tracert command on Host B to test the reachability of Host A.
  • Page 29 Table 4 Interface and IP address assignment Device Interface IP address Router A GigabitEthernet 1/1/1 12.1.1.1/24 Router A GigabitEthernet 1/1/2 10.1.1.102/24 Router B GigabitEthernet 1/1/1 12.1.1.2/24 Router B GigabitEthernet 1/1/2 13.1.1.1/24 Router C GigabitEthernet 1/1/1 10.1.1.100/24 Router C GigabitEthernet 1/1/2 13.1.1.2/24 Configuration procedure Configure IP addresses for interfaces.

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

    IPv4 Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr State Holdtime Interface 12.1.1.1 12.1.1.2 2000ms GE1/1/1 The output shows that the BFD session has been created. # Display static routes on Router A. <RouterA> display ip routing-table protocol static Summary Count : 1 Static Routing table Status : <Active>...
  • Page 31 Configure the following: • Configure a static route to subnet 120.1.1.0/24 on Router A. • Configure a static route to subnet 121.1.1.0/24 on Router B. • Enable BFD for both routes. • Configure a static route to subnet 120.1.1.0/24 and a static route to subnet 121.1.1.0/24 on both Router C and Router D.
  • Page 32 [RouterA] ip route-static 120.1.1.0 24 gigabitethernet 1/1/2 10.1.1.100 preference [RouterA] quit # Configure static routes on Router B and enable BFD control mode for the static route that traverses Router D. <RouterB> system-view [RouterB] bfd multi-hop min-transmit-interval 500 [RouterB] bfd multi-hop min-receive-interval 500 [RouterB] bfd multi-hop detect-multiplier 9 [RouterB] ip route-static 121.1.1.0 24 1.1.1.9 bfd control-packet bfd-source 2.2.2.9 [RouterB] ip route-static 121.1.1.0 24 gigabitethernet 1/1/2 13.1.1.2 preference 65...

  • Page 33: Static Route Frr Configuration Example

    <RouterA> display ip routing-table protocol static 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 GE1/1/2 Static Routing table Status : <Inactive> Summary Count : 0 The output shows that Router A communicates with Router B through GigabitEthernet 1/1/2.
  • Page 34 # Configure a static route on Router A, and specify GigabitEthernet 1/1/1 as the backup output interface and 12.12.12.2 as the backup next hop. <RouterA> system-view [RouterA] ip route-static 4.4.4.4 32 gigabitethernet 1/1/2 13.13.13.2 backup-interface gigabitethernet 1/1/1 backup-nexthop 12.12.12.2 # Configure a static route on Router B, and specify GigabitEthernet 1/1/1 as the backup output interface and 24.24.24.2 as the backup next hop.
  • Page 35 BkTunnel ID: Invalid BkInterface: GigabitEthernet1/1/1 FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A # Display route 1.1.1.1/32 on Router B to view the backup next hop information. [RouterB] display ip routing-table 1.1.1.1 verbose Summary Count : 1 Destination: 1.1.1.1/32 Protocol: Static Process ID: 0 SubProtID: 0x0 Age: 04h20m37s Cost: 0...

  • Page 36: 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 and an ICMP destination-unreachable packet is sent to the source.

  • Page 37: 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 38: 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 39: Configuring Basic Rip

    Tasks at a glance (Optional.) Tuning and optimizing RIP networks: • Setting RIP timers • Enabling split horizon and poison reverse • Setting the maximum number of ECMP routes • Enabling zero field check on incoming RIPv1 messages • Enabling source IP address check on incoming RIP updates •...

  • Page 40: Controlling Rip Reception And Advertisement On Interfaces

    Step Command Remarks By default, RIP is disabled on a network. network network-address The network 0.0.0.0 command Enable RIP on a network. [ wildcard-mask ] can enable RIP on all interfaces in a single process, but does not apply to multiple RIP processes. Enabling RIP on an interface Step Command...

  • Page 41: Configuring Rip Route Control

    An interface preferentially uses the interface-specific RIP version. If no interface-specific version is specified, the interface uses the global RIP version. If neither a global nor interface-specific RIP version is configured, the interface sends RIPv1 broadcasts and can receive the following: •...

  • Page 42: Configuring Ripv2 Route Summarization

    Step Command Remarks interface interface-type Enter interface view. interface-number Specify an inbound rip metricin [ route-policy The default setting is 0. additional routing metric. route-policy-name ] value Specify an outbound rip metricout [ route-policy The default setting is 1. additional routing metric. route-policy-name ] value Configuring RIPv2 route summarization Perform this task to summarize contiguous subnets into a summary network and sends the network...

  • Page 43: Disabling Host Route Reception

    Step Command Remarks By default, no summary route is rip summary-address Configure a summary route. ip-address { mask-length | mask } configured. Disabling host route reception Perform this task to disable RIPv2 from receiving host routes from the same network to save network resources.

  • Page 44: Setting A Preference For Rip

    To configure route filtering: Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] By default, the filtering of received routes is not filter-policy { ipv4-acl-number | configured. gateway prefix-list-name | prefix-list Configure the filtering of prefix-list-name [ gateway This command filters received...

  • Page 45: Tuning And Optimizing Rip Networks

    Step Command Remarks By default, RIP route import-route protocol redistribution is disabled. [ as-number ] [ process-id | This command can redistribute Redistribute routes from all-processes | allow-ibgp ] only active routes. To view active another routing protocol. [ allow-direct | cost cost-value | routes, use the display ip route-policy route-policy-name | routing-table protocol...

  • Page 46: Enabling Split Horizon And Poison Reverse

    Step Command Remarks By default: • The garbage-collect timer is 120 timers { garbage-collect seconds. garbage-collect-value | suppress Set RIP timers. • suppress-value | timeout The suppress timer is 120 timeout-value | update seconds. update-value } * • The timeout timer is 180 seconds. •...

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

    Step Command Remarks rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] Set the maximum number of By default, the maximum number maximum load-balancing ECMP routes. of RIP ECMP routes is 8. number Enabling zero field check on incoming RIPv1 messages Some fields in the RIPv1 message must be set to zero.

  • Page 48: Setting The Rip Triggered Update Interval

    To configure RIPv2 message authentication: Step Command Remarks Enter system view. system-view Enter interface view. interface interface-type interface-number rip authentication-mode { md5 { rfc2082 By default, RIPv2 Configure RIPv2 { cipher | plain } string key-id | rfc2453 authentication is not authentication.

  • Page 49: Configuring Rip Network Management

    Step Command Remarks Enter system view. system-view rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] By default, RIP does not Specify a RIP neighbor. unicast updates to any peer ip-address peer. Disable source IP By default, source IP address check on address check on inbound undo validate-source-address...

  • Page 50: Setting The Maximum Length Of Rip Packets

    Setting the maximum length of RIP packets NOTE: The supported maximum length of RIP packets varies by vendor. Use this feature with caution to avoid compatibility issues. The packet length of RIP packets determines how many routes can be carried in a RIP packet. Set the maximum length of RIP packets to make good use of link bandwidth.

  • Page 51: Enabling Rip Nsr

    Step Command Remarks rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] Enable GR for RIP. By default, RIP GR is disabled. graceful-restart (Optional.) Set the GR By default, the GR interval is 60 graceful-restart interval interval interval. seconds.

  • Page 52: Configuring Single-Hop Echo Detection (For A Directly Connected Rip Neighbor)

    Configuring single-hop echo detection (for a directly connected RIP neighbor) Step Command Remarks Enter system view. system-view Configure the source IP By default, the source IP address address of BFD echo of BFD echo packets is not bfd echo-source-ip ip-address packets.

  • Page 53: Configuring Rip Frr

    Step Command Remarks rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] By default, RIP does not unicast updates to any peer. Because the undo peer command does not remove the Specify a RIP neighbor. peer ip-address neighbor relationship immediately, executing the command cannot bring down the BFD session immediately.

  • Page 54: Configuration Restrictions And Guidelines

    As shown in Figure 6, configure FRR on Router B by using a routing policy to specify a backup next hop. When the primary link fails, RIP directs packets to the backup next hop. At the same time, RIP calculates the shortest path based on the new network topology, and forwards packets over that path after network convergence.

  • Page 55: Displaying And Maintaining Rip

    Step Command Remarks Enter system view. system-view By default, the source IP address of BFD echo packets is not configured. Configure the source IP The source IP address cannot be address of BFD echo on the same network segment as bfd echo-source-ip ip-address packets.
  • Page 56 Figure 7 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic RIP by using either of the following methods: (Method 1) # Enable RIP on the specified networks on Router A. <RouterA> system-view [RouterA] rip [RouterA-rip-1] network 1.0.0.0 [RouterA-rip-1] network 2.0.0.0 [RouterA-rip-1] network 3.0.0.0...
  • Page 57 [RouterA] rip [RouterA-rip-1] version 2 [RouterA-rip-1] undo summary [RouterA-rip-1] quit # Configure RIPv2 on Router B. [RouterB] rip [RouterB-rip-1] version 2 [RouterB-rip-1] undo summary [RouterB-rip-1] quit # Display the RIP routing table on Router A. [RouterA] display rip 1 route Route Flags: R - RIP, T - TRIP P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect D - Direct, O - Optimal, F - Flush to RIB...

  • Page 58: Configuring Rip Route Redistribution

    [RouterB] ip prefix-list aaa index 10 permit 2.1.1.0 24 [RouterB] ip prefix-list bbb index 10 deny 10.2.1.0 24 [RouterB] ip prefix-list bbb index 11 permit 0.0.0.0 0 less-equal 32 [RouterB] rip 1 [RouterB-rip-1] filter-policy prefix-list aaa import [RouterB-rip-1] filter-policy prefix-list bbb export [RouterB-rip-1] quit # Display the RIP routing table on Router A.
  • Page 59 Figure 8 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic RIP: # Enable RIP 100, and configure RIPv2 on Router A. <RouterA> system-view [RouterA] rip 100 [RouterA-rip-100] network 10.0.0.0 [RouterA-rip-100] network 11.0.0.0 [RouterA-rip-100] version 2 [RouterA-rip-100] undo summary [RouterA-rip-100] quit # Enable RIP 100 and RIP 200, and configure RIPv2 on Router B.

  • Page 60: Configuring An Additional Metric For A Rip Interface

    12.3.1.0/32 Direct 0 12.3.1.2 GE1/1/1 12.3.1.2/32 Direct 0 127.0.0.1 InLoop0 12.3.1.255/32 Direct 0 12.3.1.2 GE1/1/1 16.4.1.0/24 Direct 0 16.4.1.1 GE1/1/2 16.4.1.0/32 Direct 0 16.4.1.1 GE1/1/2 16.4.1.1/32 Direct 0 127.0.0.1 InLoop0 16.4.1.255/32 Direct 0 16.4.1.1 GE1/1/2 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 127.0.0.1...
  • Page 61 Router A has two links to Router D. The link from Router B to Router D is more stable than that from Router C to Router D. Configure an additional metric for RIP routes received from GigabitEthernet 1/1/2 on Router A so Router A prefers route 1.1.5.0/24 learned from Router B. Figure 9 Network diagram Configuration procedure Configure IP addresses for the interfaces.

  • Page 62: Configuring Rip To Advertise A Summary Route

    # Display all active routes in the RIP database on Router A. [RouterA] 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 1.1.2.0/24, cost 0, nexthop 1.1.2.1, RIP-interface 1.1.3.0/24, cost 1, nexthop 1.1.1.2 1.1.4.0/24, cost 1, nexthop 1.1.2.2 1.1.5.0/24, cost 2, nexthop 1.1.1.2 1.1.5.0/24, cost 2, nexthop 1.1.2.2 The output shows two RIP routes destined for network 1.1.5.0/24.
  • Page 63 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic OSPF: # Configure Router A. <RouterA> system-view [RouterA] ospf [RouterA-ospf-1] area 0 [RouterA-ospf-1-area-0.0.0.0] network 10.5.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] quit # Configure Router B. <RouterB> system-view [RouterB] ospf [RouterB-ospf-1] area 0 [RouterB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255...

  • Page 64: Configuring Rip Gr

    Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 10.1.1.0/24 11.3.1.1 GE1/1/1 10.2.1.0/24 11.3.1.1 GE1/1/1 10.5.1.0/24 11.3.1.1 GE1/1/1 10.6.1.0/24 11.3.1.1 GE1/1/1 11.3.1.0/24 Direct 0 11.3.1.2 GE1/1/1 11.3.1.0/32 Direct 0 11.3.1.2 GE1/1/1 11.3.1.2/32 Direct 0 127.0.0.1 InLoop0 11.4.1.0/24 Direct 0 11.4.1.2 GE1/1/2 11.4.1.0/32...

  • Page 65: Configuring Rip Nsr

    Figure 11 Network diagram Configuration procedure Configure IP addresses and subnet masks for interfaces on the routers. (Details not shown.) Configure RIPv2 on the routers to ensure the following: (Details not shown.) Router A, Router B, and Router C can communicate with each other at Layer 3. Dynamic route update can be implemented among them with RIPv2.
  • Page 66 Figure 12 Network diagram Configuration procedure Configure IP addresses and subnet masks for interfaces on the routers. (Details not shown.) Configure RIPv2 on the routers to ensure the following: (Details not shown.) Router A, Router B, and Router S can communicate with each other at Layer 3. Dynamic route update can be implemented among them with RIPv2.

  • Page 67: Configuring Bfd For Rip (Single-Hop Echo Detection For A Directly Connected Neighbor)

    D - Direct, O - Optimal, F - Flush to RIB ---------------------------------------------------------------------------- Peer 12.12.12.2 on GigabitEthernet1/1/1 Destination/Mask Nexthop Cost Flags 14.0.0.0/8 12.12.12.2 RAOF 44.0.0.0/8 12.12.12.2 RAOF Local route Destination/Mask Nexthop Cost Flags 12.12.12.0/24 0.0.0.0 RDOF 22.22.22.22/32 0.0.0.0 RDOF # Display neighbor information and route information on Router B. [RouterB] display rip 1 neighbor Neighbor Address: 14.14.14.2 Interface...
  • Page 68 Figure 13 Network diagram Configuration procedure Configure basic RIP and enable BFD on the interfaces: # Configure Router A. <RouterA> system-view [RouterA] rip 1 [RouterA-rip-1] version 2 [RouterA-rip-1] undo summary [RouterA-rip-1] network 192.168.1.0 [RouterA-rip-1] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] rip bfd enable [RouterA-GigabitEthernet1/1/1] quit [RouterA] rip 2 [RouterA-rip-2] network 192.168.2.0...

  • Page 69: Configuring Bfd For Rip (Single-Hop Echo Detection For A Specific Destination)

    [RouterA-GigabitEthernet1/1/1] bfd min-transmit-interval 500 [RouterA-GigabitEthernet1/1/1] bfd min-receive-interval 500 [RouterA-GigabitEthernet1/1/1] bfd detect-multiplier 7 [RouterA-GigabitEthernet1/1/1] return Configure a static route on Router C. [RouterC] ip route-static 120.1.1.1 24 null 0 Verifying the configuration # Display the BFD session information on Router A. <RouterA>...
  • Page 70 BFD can quickly detect the link failure and notify RIP. RIP then deletes the neighbor relationship and the route information learned on GigabitEthernet 1/1/2. It does not receive or send any packets on GigabitEthernet 1/1/2. When the route learned from Router A ages out, Router B uses the route destined for 100.1.1.1/24 through GigabitEthernet 1/1/2.

  • Page 71: Configure Static Routes

    Configure static routes: # Configure a static route on Router A. [RouterA] ip route-static 100.1.1.0 24 null 0 # Configure a static route on Router C. [RouterC] ip route-static 100.1.1.0 24 null 0 Verifying the configuration # Display the BFD session information on Router A. <RouterA>...

  • Page 72: Configuring Bfd For Rip (Bidirectional Control Detection)

    SubProtID: 0x1 Age: 00h21m23s Cost: 4 Preference: 100 IpPre: N/A QosLocalID: N/A Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0x2 OrigAs: 0 NibID: 0x12000003 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...
  • Page 73 Table 7 Interface and IP address assignment Device Interface IP address Router A GigabitEthernet 1/1/1 192.168.3.1/24 Router A GigabitEthernet 1/1/2 192.168.1.1/24 Router B GigabitEthernet 1/1/1 192.168.2.1/24 Router B GigabitEthernet 1/1/2 192.168.1.2/24 Router C GigabitEthernet 1/1/1 192.168.2.2/24 Router C GigabitEthernet 1/1/2 192.168.4.2/24 Router D GigabitEthernet 1/1/1...
  • Page 74 [RouterC-rip-1] quit [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] rip bfd enable [RouterC-GigabitEthernet1/1/1] quit # Configure Router D. <RouterD> system-view [RouterD] rip 1 [RouterD-rip-1] version 2 [RouterD-rip-1] undo summary [RouterD-rip-1] network 192.168.3.0 [RouterD-rip-1] network 192.168.4.0 [RouterD-rip-1] quit Configure BFD parameters for the interfaces: # Configure Router A.

  • Page 75: Configuring Rip Frr

    [RouterD-GigabitEthernet1/1/1] quit Configure static routes: # Configure a static route to Router C on Router A. [RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/1/2 192.168.1.2 [RouterA] quit # Configure a static route to Router A on Router C. [RouterC] ip route-static 192.168.1.0 24 gigabitethernet 1/1/1 192.168.2.1 Verifying the configuration # Display the BFD session information on Router A.
  • Page 76 Figure 16 Network diagram Router C Link B Link A Loop0 Loop0 GE1/1/2 GE1/1/2 Router B Router A Table 8 Interface and IP address assignment Device Interface IP address Router A GigabitEthernet 1/1/1 12.12.12.1/24 Router A GigabitEthernet 1/1/2 13.13.13.1/24 Router A Loopback 0 1.1.1.1/32 Router B...
  • Page 77 [RouterB] rip 1 [RouterB-rip-1] fast-reroute route-policy frr [RouterB-rip-1] quit Verifying the configuration # Display route 4.4.4.4/32 on Router A to view the backup next hop information. [RouterA] display ip routing-table 4.4.4.4 verbose Destination: 4.4.4.4/32 Protocol: RIP Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 1 Preference: 100...

  • Page 78: 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 79: 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 80 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 81: 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 82: Route Types

    Figure 21 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 83: Ospf Network Types

    • Each router transforms the LSDB to a weighted directed graph that shows the topology of the area. All the routers within the area have the same graph. • Each router uses the SPF algorithm to compute a shortest path tree that shows the routes to the nodes in the area.

  • Page 84: Protocols And Standards

    Figure 22 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 85 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 86: Enabling Ospf

    Tasks at a glance (Optional.) Tuning and optimizing OSPF networks: • Setting OSPF timers • Setting LSA transmission delay • Setting SPF calculation interval • Setting the LSA arrival interval • Setting the LSA generation interval • Disabling interfaces from receiving and sending OSPF packets •...

  • Page 87: Enabling Ospf On A Network

    A router ID uniquely identifies a router in an AS. For a router to run OSPF, it must have a router ID. You can use one of the following methods to specify a router ID: • Manual configuration—When you create an OSPF process, you can manually specify a router ID.

  • Page 88: Enabling Ospf On An Interface

    Step Command Remarks By default, no description is configured for the area. (Optional.) Configure a description text description for the area. As a best practice, configure a description for each OSPF area. Specify a network to enable the interface By default, no network is specified. network ip-address attached to the network to wildcard-mask...

  • Page 89: Configuring An Nssa Area

    Step Command Remarks ospf [ process-id | router-id { auto-select | router-id } | Enter OSPF view. vpn-instance vpn-instance-name ] * Enter area view. area area-id stub Configure the area as a [ default-route-advertise-alwa By default, no stub area is configured. stub area.

  • Page 90: Configuring A Virtual Link

    Configuring a virtual link Virtual links are configured for connecting backbone area routers that have no direct physical links. To configure a virtual link: Step Command Remarks Enter system view. system-view ospf [ process-id | router-id { auto-select | router-id } | Enter OSPF view.

  • Page 91: Configuring The Broadcast Network Type For An Interface

    Configuring the broadcast network type for an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the OSPF network By default, the network type of an type for the interface as interface depends on the link layer ospf network-type broadcast broadcast.

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

    Configuring the P2MP network type for an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the network type of an interface depends on the link layer protocol. After you configure the OSPF Configure the OSPF network type for an interface as ospf network-type p2mp...

  • Page 93: Configuring Ospf Route Summarization

    • Configure filters if routing information filtering is needed. Configuring OSPF route summarization Route summarization enables an ABR or ASBR to summarize contiguous networks into a single network and advertise the network to other areas. Route summarization reduces the routing information exchanged between areas and the size of routing tables, and improves routing performance.

  • Page 94: Configuring Received Ospf Route Filtering

    Configuring received OSPF route filtering Perform this task to filter routes calculated using received LSAs. The following filtering methods are available: • Use an ACL or IP prefix list to filter routing information by destination address. • Use the gateway keyword to filter routing information by next hop. •...

  • Page 95: Setting The Maximum Number Of Ecmp Routes

    If the calculated cost is greater than 65535, the value of 65535 is used. If the calculated cost is less than 1, the value of 1 is used. If no cost or bandwidth reference value is configured for an interface, OSPF computes the interface cost based on the interface bandwidth and default bandwidth reference value.

  • Page 96: Configuring Discard Routes For Summary Networks

    Step Command Remarks ospf [ process-id | router-id Enter OSPF view. { auto-select | router-id } | vpn-instance vpn-instance-name ] * By default, the preference of OSPF Set a preference for preference [ ase ] { preference | internal routes is 10 and the preference OSPF.
  • Page 97 Step Command Remarks By default, no route import-route protocol [ as-number ] redistribution is configured. [ process-id | all-processes | Configure OSPF to This command redistributes only allow-ibgp ] [ allow-direct | cost redistribute routes from active routes. To view cost-value | nssa-only | route-policy another routing protocol.

  • Page 98: Advertising A Host Route

    Advertising a host route Step Command Remarks Enter system view. system-view ospf [ process-id | router-id { auto-select | router-id } | Enter OSPF view. vpn-instance vpn-instance-name ] * Enter area view. area area-id By default, no host route is Advertise a host route.

  • Page 99: Setting Lsa Transmission Delay

    • Poll timer—Interval for sending hello packets to a neighbor that is down on the NBMA network. • Dead timer—Interval within which if the interface does not receive any hello packet from the neighbor, it declares the neighbor is down. •...

  • Page 100: Setting Spf Calculation Interval

    Step Command Remarks interface interface-type Enter interface view. interface-number Set the LSA transmission The default setting is 1 second. ospf trans-delay seconds delay. Setting 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.

  • Page 101: Setting The Lsa Generation Interval

    Setting the LSA generation interval Adjust the LSA generation interval to protect network resources and routers from being overwhelmed by LSAs at the time of 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 102: Configuring Stub Routers

    Configuring stub routers A stub router is used for traffic control. It reports its status as a stub router to neighboring OSPF routers. The neighboring routers can have a route to the stub router, but they do not use the stub router to forward data.

  • Page 103: Adding The Interface Mtu Into Dd Packets

    Configuring OSPF interface authentication You must configure the same authentication mode and key on both the local interface and its peer interface. To configure OSPF interface authentication: Step Command Remarks Enter system view. system-view Enter interface view. interface interface-type interface-number •...

  • Page 104: Setting The Maximum Number Of External Lsas In Lsdb

    Setting the maximum number of external LSAs in LSDB Step Command Remarks Enter system view. system-view ospf [ process-id | router-id { auto-select | Enter OSPF view. router-id } | vpn-instance vpn-instance-name ] * By default, the Set the maximum number of maximum number of lsdb-overflow-limit number external LSAs in the LSDB.

  • Page 105: Logging Neighbor State Changes

    Step Command Remarks Enter system view. system-view ospf [ process-id | router-id Enter OSPF view. { auto-select | router-id } | vpn-instance vpn-instance-name ] * Enable compatibility By default, compatibility with RFC rfc1583 compatible with RFC 1583. 1583 is enabled. Logging neighbor state changes Perform this task to enable output of neighbor state change logs to the information center.

  • Page 106: Setting The Lsu Transmit Rate

    Step Command Remarks snmp-agent trap enable ospf [ authentication-failure | bad-packet | config-error | grhelper-status-change | grrestarter-status-change | if-state-change | lsa-maxage | lsa-originate | lsdb-approaching-overflow | By default, SNMP Enable SNMP notifications lsdb-overflow | notifications for OSPF are for OSPF. neighbor-state-change | enabled.

  • Page 107: Configuring Prefix Suppression

    Step Command Remarks ospf [ process-id | router-id { auto-select | Enter OSPF view. router-id } | vpn-instance vpn-instance-name ] By default, OSPF ISPF is Enable OSPF ISPF. ispf enable enabled. Configuring prefix suppression By default, an OSPF interface advertises all of its prefixes in LSAs. To speed up OSPF convergence, you can suppress interfaces from advertising all of their prefixes.

  • Page 108: Configuring Prefix Prioritization

    Step Command Remarks Enable prefix By default, prefix suppression suppression for the ospf prefix-suppression [ disable ] is disabled on an interface. interface. Configuring prefix prioritization This feature enables the device to install prefixes in descending priority order: critical, high, medium, and low.

  • Page 109: Setting The Number Of Ospf Logs

    Step Command Remarks Enable BFD control packet By default, BFD control packet ospf primary-path-detect bfd mode for OSPF PIC. mode for OSPF PIC is disabled. ctrl To configure BFD echo packet mode for OSPF PIC: Step Command Remarks Enter system view. system-view By default, the source IP address of BFD echo packets is not...

  • Page 110: Filtering Lsas For The Specified Neighbor

    Step Command Remarks ospf database-filter { all | { ase [ acl Filter outbound ipv4-acl-number ] | nssa [ acl By default, the outbound LSAs are not LSAs on the ipv4-acl-number ] | summary [ acl filtered on the interface. interface.

  • Page 111: Configuring Ospf Dynamic Host Name Mappings

    Step Command Remarks Enter OSPF area view. area area-id Enable GTSM for the OSPF By default, GTSM is disabled for ttl-security [ hops hop-count ] area. the OSPF area. To configure GTSM in interface view: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 112: 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 113: 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 { auto-select | router-id } | view.

  • Page 114: 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 it is typically used more often than GR.

  • Page 115: Configuring Single-Hop Echo Detection

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

  • Page 116: 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 interface interface-type Enter interface view. interface-number By default, the interface is enabled (Optional.) Enable LFA on an with LFA and it can be selected as a ospf fast-reroute lfa-backup interface.

  • Page 117: Displaying And Maintaining Ospf

    To configure BFD echo packet mode for OSPF FRR: Step Command Remarks Enter system view. system-view By default, the source IP address of BFD echo packets is not configured. The source IP address cannot be on Configure the source the same network segment as any IP address of BFD bfd echo-source-ip ip-address local interface's IP address.

  • Page 118: Ospf Configuration Examples

    Task Command display ospf [ process-id ] peer [ verbose ] [ interface-type Display OSPF neighbor information. interface-number ] [ [ neighbor-id ] [ resolve-hostname ] | hostname host-name ] Display neighbor statistics for OSPF display ospf [ process-id ] peer statistics areas.
  • Page 119 Figure 24 Network diagram Area 0 Router A Router B GE1/1/1 10.1.1.1/24 GE1/1/1 10.1.1.2/24 GE1/1/2 GE1/1/2 10.3.1.1/24 10.2.1.1/24 GE1/1/1 GE1/1/1 Area 1 Area 2 10.3.1.2/24 10.2.1.2/24 GE1/1/2 GE1/1/2 10.4.1.1/24 10.5.1.1/24 Router C Router D Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Router A.
  • Page 120 <RouterD> system-view [RouterD] router id 10.5.1.1 [RouterD] ospf [RouterD-ospf-1] area 2 [RouterD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [RouterD-ospf-1-area-0.0.0.2] network 10.5.1.0 0.0.0.255 [RouterD-ospf-1-area-0.0.0.2] quit [RouterD-ospf-1] quit Verifying the configuration # Display the OSPF neighbors of Router A. [RouterA] display ospf peer verbose OSPF Process 1 with Router ID 10.2.1.1 Neighbors Area 0.0.0.0 interface 10.1.1.1(GigabitEthernet1/1/1)'s neighbors Router ID: 10.3.1.1...

  • Page 121: Ospf Route Redistribution Configuration Example

    10.1.1.0/24 Transit 10.1.1.1 10.2.1.1 0.0.0.0 Total nets: 5 Intra area: 3 Inter area: 2 ASE: 0 NSSA: 0 # Display OSPF routing information on Router D. [RouterD] display ospf routing OSPF Process 1 with Router ID 10.5.1.1 Routing Table Routing for network Destination Cost Type...
  • Page 122 Figure 25 Network diagram Area 0 Router A Router B GE1/1/1 10.1.1.1/24 GE1/1/1 10.1.1.2/24 GE1/1/2 GE1/1/2 10.3.1.1/24 10.2.1.1/24 GE1/1/1 GE1/1/1 Area 1 Area 2 10.3.1.2/24 10.2.1.2/24 GE1/1/2 GE1/1/2 10.4.1.1/24 10.5.1.1/24 Router C Router D Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF (see "Basic OSPF configuration example").

  • Page 123: Ospf Route Summarization Configuration Example

    Routing for ASEs Destination Cost Type NextHop AdvRouter 3.1.2.0/24 Type2 10.3.1.1 10.4.1.1 Total nets: 6 Intra area: 2 Inter area: 3 ASE: 1 NSSA: 0 OSPF route summarization configuration example Network requirements As shown in Figure • Configure OSPF on Router A and Router B in AS 200. •...
  • Page 124 <RouterB> system-view [RouterB] router id 11.2.1.1 [RouterB] ospf [RouterB-ospf-1] area 0 [RouterB-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.0] quit [RouterB-ospf-1] quit # Configure Router C. <RouterC> system-view [RouterC] router id 11.1.1.2 [RouterC] ospf [RouterC-ospf-1] area 0 [RouterC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] quit [RouterC-ospf-1] quit # Configure Router D.
  • Page 125 [RouterC-bgp-default-ipv4] peer 11.1.1.1 enable [RouterC-bgp-default-ipv4] import-route ospf [RouterC-bgp-default-ipv4] import-route direct [RouterB-bgp-default-ipv4] quit [RouterC-bgp-default] quit Configure Router B and Router C to redistribute BGP routes into OSPF: # Configure OSPF to redistribute routes from BGP on Router B. [RouterB] ospf [RouterB-ospf-1] import-route bgp # Configure OSPF to redistribute routes from BGP on Router C.

  • Page 126: Ospf Stub Area Configuration Example

    11.2.1.255/32 Direct 0 11.2.1.2 GE1/1/1 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 224.0.0.0/4 Direct 0 0.0.0.0 NULL0 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 The output shows that routes 10.1.1.0/24, 10.2.1.0/24, 10.3.1.0/24 and 10.4.1.0/24 are summarized into a single route 10.0.0.0/8.
  • Page 127 Type Destination Area Cost Nexthop RtType Intra 10.2.1.1 0.0.0.1 10.2.1.1 Inter 10.5.1.1 0.0.0.1 10.2.1.1 ASBR # Display OSPF routing information on Router C. <RouterC> display ospf routing OSPF Process 1 with Router ID 10.4.1.1 Routing Table Routing for network Destination Cost Type NextHop...

  • Page 128: Ospf Nssa Area Configuration Example

    0.0.0.0/0 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 Transit 0.0.0.0 10.2.1.1 0.0.0.1 10.3.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.4.1.0/24 Stub 10.4.1.1 10.4.1.1 0.0.0.1 10.5.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.1.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 Total nets: 6 Intra area: 2 Inter area: 4 ASE: 0 NSSA: 0 The output shows that a default route replaces the AS external route.
  • Page 129 Figure 28 Network diagram Area 0 Router A Router B GE1/1/1 10.1.1.1/24 GE1/1/1 10.1.1.2/24 GE1/1/2 GE1/1/2 10.3.1.1/24 10.2.1.1/24 Area 1 GE1/1/1 GE1/1/1 Area 2 10.3.1.2/24 NSSA 10.2.1.2/24 ASBR GE1/1/2 GE1/1/2 10.5.1.1/24 Router C Router D 10.4.1.1/24 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF (see "Basic OSPF configuration example").

  • Page 130: Ospf Dr Election Configuration Example

    # Configure OSPF to redistribute the static route on Router C. [RouterC] ip route-static 3.1.2.1 24 10.4.1.2 [RouterC] ospf [RouterC-ospf-1] import-route static [RouterC-ospf-1] quit # Display routing information on Router D. <RouterD> display ospf routing OSPF Process 1 with Router ID 10.5.1.1 Routing Table Routing for network Destination...
  • Page 131 Enable OSPF: # Configure Router A. <RouterA> system-view [RouterA] router id 1.1.1.1 [RouterA] ospf [RouterA-ospf-1] area 0 [RouterA-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] quit [RouterA-ospf-1] quit # Configure Router B. <RouterB> system-view [RouterB] router id 2.2.2.2 [RouterB] ospf [RouterB-ospf-1] area 0 [RouterB-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.0] quit [RouterB-ospf-1] quit...
  • Page 132 BFD status: Disabled Router ID: 3.3.3.3 Address: 192.168.1.3 GR State: Normal State: Full Mode: Nbr is master Priority: 1 DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 31 Neighbor is up for 00:01:28 Authentication Sequence: [ 0 ] Neighbor state change count: 6 BFD status: Disabled Router ID: 4.4.4.4...
  • Page 133 Authentication Sequence: [ 0 ] Neighbor state change count: 6 BFD status: Disabled Router ID: 2.2.2.2 Address: 192.168.1.2 GR State: Normal State: Full Mode:Nbr is slave Priority: 0 DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 35 Neighbor is up for 00:11:19 Authentication Sequence: [ 0 ] Neighbor state change count: 6...

  • Page 134: Ospf Virtual Link Configuration Example

    DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 35 Neighbor is up for 00:01:44 Authentication Sequence: [ 0 ] Neighbor state change count: 6 BFD status: Disabled Router ID: 3.3.3.3 Address: 192.168.1.3 GR State: Normal State: Full Mode: Nbr is slave Priority: 2...
  • Page 135 Figure 30 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Router A. <RouterA> system-view [RouterA] ospf 1 router-id 1.1.1.1 [RouterA-ospf-1] area 0 [RouterA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] quit [RouterA-ospf-1] quit # Configure Router B. <RouterB>...

  • Page 136: Ospf Gr Configuration Example

    # Display OSPF routing information on Router B. [RouterB] display ospf routing OSPF Process 1 with Router ID 2.2.2.2 Routing Table Routing for network Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 Transit 10.2.1.1 3.3.3.3 0.0.0.1 10.1.1.0/24 Transit 10.1.1.2 2.2.2.2 0.0.0.0 Total nets: 2 Intra area: 2 Inter area: 0...
  • Page 137 • Router A acts as the non-IETF GR restarter. Router B and Router C are the GR helpers, and synchronize their LSDBs with Router A through OOB communication of GR. Figure 31 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Router A.
  • Page 138 [RouterA-ospf-100] enable link-local-signaling [RouterA-ospf-100] enable out-of-band-resynchronization [RouterA-ospf-100] graceful-restart [RouterA-ospf-100] quit # Configure Router B as the GR helper: enable the link-local signaling capability and the out-of-band re-synchronization capability for OSPF process 100. [RouterB-ospf-100] enable link-local-signaling [RouterB-ospf-100] enable out-of-band-resynchronization # Configure Router C as the GR helper: enable the link-local signaling capability and the out-of-band re-synchronization capability for OSPF process 100.

  • Page 139: Ospf Nsr Configuration Example

    %Oct 21 15:29:30:921 2011 RouterA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor 192.1.1.3(GigabitEthernet1/1/1) from Full to Down. %Oct 21 15:29:33:815 2011 RouterA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor 192.1.1.3(GigabitEthernet1/1/1) from Loading to Full. %Oct 21 15:29:35:578 2011 RouterA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor 192.1.1.2(GigabitEthernet1/1/1) from Loading to Full.
  • Page 140 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 Router A to verify the neighbor relationship between Router A and Router S.

  • Page 141: Bfd For Ospf Configuration Example

    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 the following when an active/standby switchover occurs on Router S: •...
  • Page 142 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Router A. <RouterA> system-view [RouterA] ospf [RouterA-ospf-1] area 0 [RouterA-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [RouterA-ospf-1-area-0.0.0.0] network 121.1.1.1 0.0.0.0 [RouterA-ospf-1-area-0.0.0.0] quit [RouterA-ospf-1] quit # Configure Router B. <RouterB>...
  • Page 143 Verifying the configuration # Display the BFD information on Router A. <RouterA> 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 192.168.0.102 192.168.0.100 1700ms GE1/1/1 # Display routes destined for 120.1.1.1/32 on Router A.

  • Page 144: Ospf Frr Configuration Example

    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 BkNextHop: N/A Tunnel ID: Invalid Interface: GigabitEthernet1/1/2 BkTunnel ID: Invalid BkInterface: N/ A FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A The output shows that Router A communicates with Router B through GigabitEthernet 1/1/2.
  • Page 145 You can enable OSPF FRR to either calculate a backup next hop by using the LFA algorithm, or specify a backup next hop by using a routing policy. (Method 1.) Enable OSPF FRR to calculate a backup next hop by using the LFA algorithm: # Configure Router A.

  • Page 146: Troubleshooting Ospf Configuration

    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: 13.13.13.2 Label: NULL RealNextHop: 13.13.13.2 BkLabel: NULL BkNextHop: 12.12.12.2 Tunnel ID: Invalid Interface: GigabitEthernet1/1/2 BkTunnel ID: Invalid BkInterface: GigabitEthernet1/1/1 FtnIndex: 0x0 TrafficIndex: N/A...

  • Page 147: Incorrect Routing Information

    Solution To resolve the problem: Use the display ospf peer command to verify OSPF neighbor information. Use the display ospf interface command to verify OSPF interface information. Ping the neighbor router's IP address to verify that the connectivity is normal. Verify OSPF timers.

  • Page 148: 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 149: Net

    Figure 35 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 150: 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 151: 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 37 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 152: Is-Is Pdus

    As shown in Figure 38, the same level routers on a network, including non-DIS routers, establish adjacency with each other. Figure 38 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 153 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 154: Protocols And Standards

    CLV Code Name PDU Type Authentication Information IIH, LSP, SNP 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 MT-ISN M-Topologies IIH, LSP MT IP. Reach MT IPv6 IP.

  • Page 155: Is-Is Configuration Task List

    IS-IS configuration task list Tasks at a glance Configuring basic IS-IS: • (Required.) Enabling IS-IS • (Optional.) Setting the IS level and circuit level • (Optional.) Configuring P2P network type for an interface (Optional.) Configuring IS-IS route control: • Configuring IS-IS link cost •...

  • Page 156: Configuring Basic Is-Is

    Configuring basic IS-IS Configuration prerequisites Before the configuration, complete the following tasks: • Configure the link layer protocol. • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. Enabling IS-IS Step Command Remarks Enter system view. system-view isis [ process-id ] Enable IS-IS and enter IS-IS [ vpn-instance...

  • Page 157: Configuring P2P Network Type For An Interface

    Configuring P2P network type for an interface Perform this task only for a broadcast network that has up to two attached routers. Interfaces with different network types operate differently. For example, broadcast interfaces on a network must elect the DIS and flood CSNP packets to synchronize the LSDBs. However, P2P interfaces on a network do not need to elect the DIS, and have a different LSDB synchronization mechanism.
  • Page 158 Interface bandwidth Interface cost ≤ 100 Mbps ≤ 155 Mbps ≤ 622 Mbps ≤ 2500 Mbps > 2500 Mbps If none of the above costs is used, a default cost of 10 applies. Configuring an IS-IS cost for an interface Step Command Remarks...

  • Page 159: Specifying A Preference For Is-Is

    Enabling automatic IS-IS cost calculation Step Command Remarks Enter system view. system-view • Enter IS-IS view: isis [ process-id ] [ vpn-instance vpn-instance-name ] • Enter IS-IS IPv4 unicast topology view: Enter IS-IS view or IS-IS a. isis [ process-id ] [ vpn-instance IPv4 unicast topology vpn-instance-name ] view.

  • Page 160: Configuring Is-Is Route Summarization

    To configure the maximum number of ECMP routes: Step Command Remarks Enter system view. system-view • Enter IS-IS IPv4 unicast address family view: a. isis [ process-id ] [ vpn-instance vpn-instance-name ] b. address-family ipv4 [ unicast ] Enter IS-IS IPv4 unicast •...

  • Page 161: Advertising A Default Route

    Advertising a default route IS-IS cannot redistribute a default route to its neighbors. This task enables IS-IS to advertise a default route of 0.0.0.0/0 in an LSP to the same-level neighbors. Upon receiving the default route, the neighbors add it into their routing table. To advertise a default route: Step Command...

  • Page 162: Configuring Is-Is Route Filtering

    Step Command Remarks By default, no route is redistributed. By default, if no level is import-route protocol [ as-number ] specified, this command Redistribute routes from [ process-id | all-processes | allow-ibgp ] redistributes routes into the other routing protocols [ allow-direct | cost cost-value | cost-type Level-2 routing table.

  • Page 163: Configuring Is-Is Route Leaking

    Perform this task to filter redistributed routes. Only routes that are not filtered can be added to the IS-IS routing table and advertised to neighbors. To filter redistributed routes: Step Command Remarks Enter system view. system-view • Enter IS-IS IPv4 unicast address family view: a.

  • Page 164: Advertising Is-Is Link State Information To Bgp

    Step Command Remarks import-route isis level-2 into level-1 Configure route By default, IS-IS does not [ filter-policy { ipv4-acl-number | prefix-list leaking from Level-2 advertise routes from prefix-list-name | route-policy to Level-1. Level-2 to Level-1. route-policy-name } | tag tag ] * Advertising IS-IS link state information to BGP After the device advertises IS-IS link state information to BGP, BGP can advertise the information for intended applications.

  • Page 165: Specifying The Is-Is Hello Multiplier

    Specifying the IS-IS hello multiplier The hello multiplier is the number of hello packets a neighbor must miss before it declares that the router is down. If a neighbor receives no hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes.

  • Page 166: Enabling Source Address Check For Hello Packets On A Ppp Interface

    Step Command Remarks Configure a DIS priority for isis dis-priority priority [ level-1 | The default setting is 64. the interface. level-2 ] Enabling source address check for hello packets on a PPP interface An IS-IS PPP interface can have a peer on a different network. Perform this task to configure an IS-IS PPP interface to establish neighbor relationship only with a peer on the same network.

  • Page 167: Configuring Lsp Parameters

    Step Command Remarks interface interface-type Enter interface view. interface-number Enable the interface to send By default, the interface can send small hello packets without isis small-hello standard hello packets. CLVs. Configuring LSP parameters Configuring LSP timers Specify the maximum age of LSPs. Each LSP has an age that decreases in the LSDB.
  • Page 168 Step Command Remarks By default: • The maximum interval is 5 seconds. timer lsp-generation maximum-interval Specify the LSP [ minimum-interval • The minimum interval generation interval. [ incremental-interval ] ] [ level-1 | is 50 milliseconds. level-2 ] • The incremental interval is 200 milliseconds.
  • Page 169 Enabling LSP flash flooding Changed LSPs can trigger SPF recalculation. To advertise the changed LSPs before the router recalculates routes for faster network convergence, enable LSP flash flooding. To enable LSP flash flooding: Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view.

  • Page 170: Controlling Spf Calculation Interval

    Figure 41 Network diagram of a fully meshed network To avoid this problem, you can add interfaces to a mesh group or block some interfaces. • An interface in a mesh group floods a received LSP only to interfaces not in the mesh group. •...

  • Page 171: Configuring Convergence Priorities For Specific Routes

    Step Command Remarks • Enter IS-IS view: isis [ process-id ] [ vpn-instance vpn-instance-name ] • Enter IS-IS IPv4 unicast address family view: Enter IS-IS view or IS-IS a. isis [ process-id ] IPv4 unicast address [ vpn-instance family view. vpn-instance-name ] b.

  • Page 172: Setting The Lsdb Overload Bit

    Setting the LSDB overload bit By setting the overload bit in sent LSPs, a router informs other routers of failures that make it unable to select routes and forward packets. When an IS-IS router cannot record the complete LSDB, for example, because of memory insufficiency, it will calculate wrong routes.

  • Page 173: Configuring The Tag Value For An Interface

    Configuring the tag value for an interface Perform this task when the link cost style is wide, wide-compatible, or compatible. When IS-IS advertises a prefix with a tag value, IS-IS adds the tag to the IP reachability information TLV of the prefix. To configure the tag value for an interface: Step Command...

  • Page 174: Enabling The Logging Of Neighbor State Changes

    When you use dynamic system ID to host name mapping, you only need to configure a host name for each router in the network. Each router advertises the host name in a dynamic host name CLV to other routers so all routers in the network can have all mappings. To help check the origin of LSPs in the LSDB, you can configure a name for the DIS in a broadcast network.

  • Page 175: Enabling Prefix Suppression

    Step Command Remarks Enter system view. system-view • Enter IS-IS view: isis [ process-id ] [ vpn-instance vpn-instance-name ] • Enter IS-IS IPv4 unicast topology view: Enter IS-IS view or a. isis [ process-id ] [ vpn-instance IS-IS IPv4 unicast vpn-instance-name ] topology view.

  • Page 176: Configuring Is-Is Pic

    Step Command Remarks Enter system view. system-view By default, MIB is bound to the Bind MIB to an IS-IS IS-IS process with the smallest isis mib-binding process-id process. process ID. snmp-agent trap enable isis [ adjacency-state-change | area-mismatch | authentication | authentication-type | buffsize-mismatch | id-length-mismatch |...

  • Page 177: Enhancing Is-Is Network Security

    Step Command Remarks interface interface-type Enter interface view. interface-number Enable BFD control packet By default, BFD control packet isis primary-path-detect bfd ctrl mode for IS-IS PIC. mode is disabled for IS-IS PIC. To configure BFD echo packet mode for IS-IS PIC: Step Command Remarks...

  • Page 178: 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 } [ nonstandard ] | md5 | authentication is mode and key.

  • Page 179: Configuring Is-Is Gr

    All the routers in the backbone must have the same authentication mode and key. To prevent packet exchange failure in case of an authentication key change, configure IS-IS not to check the authentication information in the received packets. To configure routing domain authentication: Step Command Remarks...

  • Page 180: Configuring Is-Is Nsr

    Step Command Remarks Enter system view. system-view Enable IS-IS and isis [ process-id ] [ vpn-instance enter IS-IS view. vpn-instance-name ] By default, the GR capability for IS-IS is Enable IS-IS GR. graceful-restart disabled. By default, the SA bit is not suppressed. (Optional.) Suppress By enabling the GR restarter to suppress the SA bit during...

  • Page 181: Configuring Is-Is Frr

    To configure BFD for IS-IS: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable IS-IS on an interface. isis enable [ process-id ] By default, an IS-IS Enable BFD on an IS-IS interface is not enabled with isis bfd enable interface.

  • Page 182: Configuration Procedure

    Configuration procedure Configuring IS-IS FRR to calculate a backup next hop through LFA calculation Step Command Remarks Enter system view. system-view • Enter interface view: interface interface-type interface-number • Enter IPv4 unicast topology view of the Enter interface view or interface: IPv4 unicast topology view of the interface.
  • Page 183 Step Command Remarks • Enter interface view: interface interface-type interface-number • Enter IPv4 unicast topology view of the Enter interface view or interface: IPv4 unicast topology view of the interface. a. interface interface-type interface-number b. topology ipv4 [ unicast ] topo-name By default, the interface (Optional.) Disable LFA...

  • Page 184: Configuring Is-Is Mtr

    Step Command Remarks By default, the source IP address of BFD echo packets is not configured. Configure the source IP The source IP address cannot be bfd echo-source-ip ip-address address of BFD echo packets. on the same network segment as any local interface's IP address.

  • Page 185: Displaying And Maintaining Is-Is

    Configuration prerequisites Before you configure IPv4 IS-IS MTR, complete the following tasks: • Configure basic IS-IS to establish IS-IS neighbor relationships. • Configure MTR. For more information, see "Configuring MTR." Configuration procedure To configure IS-IS MTR: Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view.
  • Page 186 Task Command display isis lsdb [ [ level-1 | level-2 ] | local | lsp-id lspid | Display IS-IS LSDB information. [ lsp-name lspname ] | verbose ] * [ process-id ] Display IS-IS mesh group information. display isis mesh-group [ process-id ] Display the host name to system ID display isis name-table [ process-id ] mapping table.

  • Page 187: Is-Is Configuration Examples

    IS-IS configuration examples Basic IS-IS configuration example Network requirements As shown in Figure 44, Router A, Router B, Router C, and Router D reside in an AS. Router A and Router B are Level-1 routers, Router D is a Level-2 router, and Router C is a Level-1-2 router connecting two areas.
  • Page 188 [RouterC] isis 1 [RouterC-isis-1] network-entity 10.0000.0000.0003.00 [RouterC-isis-1] quit [RouterC] interface gigabitethernet 1/1/3 [RouterC-GigabitEthernet1/1/3] isis enable 1 [RouterC-GigabitEthernet1/1/3] quit [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] isis enable 1 [RouterC-GigabitEthernet1/1/1] quit [RouterC] interface gigabitethernet 1/1/2 [RouterC-GigabitEthernet1/1/2] isis enable 1 [RouterC-GigabitEthernet1/1/2] quit # Configure Router D <RouterD>...
  • Page 189 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 1189 0/0/0 0000.0000.0002.01-00* 0x00000005 0xd2b3 1188 0/0/0 0000.0000.0003.00-00 0x00000014 0x194a 1190 1/0/0 0000.0000.0003.01-00 0x00000002 0xabdb 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload [RouterC] display isis lsdb Database information for ISIS(1) --------------------------------...
  • Page 190 LSPID Seq Num Checksum Holdtime Length ATT/P/OL -------------------------------------------------------------------------- 0000.0000.0003.00-00 0x00000013 0xc73d 1003 0/0/0 0000.0000.0004.00-00* 0x0000003c 0xd647 1194 0/0/0 0000.0000.0004.01-00* 0x00000002 0xec96 1007 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload # Display the IS-IS routing information on each router. [RouterA] display isis route Route information for IS-IS(1) ------------------------------ Level-1 IPv4 Forwarding Table...

  • Page 191: Dis Election Configuration Example

    172.16.0.0/16 NULL GE1/1/2 192.168.0.2 R/-/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set [RouterD] display isis route Route information for IS-IS(1) ----------------------------- Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 192.168.0.0/24 NULL GE1/1/2 Direct D/L/-...
  • Page 192 Enable IS-IS: # Configure Router A. <RouterA> system-view [RouterA] isis 1 [RouterA-isis-1] network-entity 10.0000.0000.0001.00 [RouterA-isis-1] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] isis enable 1 [RouterA-GigabitEthernet1/1/1] quit # Configure Router B. <RouterB> system-view [RouterB] isis 1 [RouterB-isis-1] network-entity 10.0000.0000.0002.00 [RouterB-isis-1] quit [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] isis enable 1 [RouterB-GigabitEthernet1/1/1] quit...
  • Page 193 System Id: 0000.0000.0002 Interface: GigabitEthernet1/1/1 Circuit Id: 0000.0000.0004.01 State: Up HoldTime: 23s Type: L2(L1L2) PRI: 64 System Id: 0000.0000.0004 Interface: GigabitEthernet1/1/1 Circuit Id: 0000.0000.0004.01 State: Up HoldTime: 23s Type: L2 PRI: 64 # Display information about IS-IS interfaces of Router A. [RouterA] display isis interface Interface information for IS-IS(1) ---------------------------------...
  • Page 194 Interface: GigabitEthernet1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 29s Type: L1(L1L2) PRI: 64 System Id: 0000.0000.0003 Interface: GigabitEthernet1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 22s Type: L1 PRI: 64 System Id: 0000.0000.0002 Interface: GigabitEthernet1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 22s Type: L2(L1L2) PRI: 64 System Id: 0000.0000.0004...

  • Page 195: Is-Is Route Redistribution Configuration Example

    Peer information for IS-IS(1) ---------------------------- System Id: 0000.0000.0001 Interface: GigabitEthernet1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 7s Type: L2 PRI: 100 System Id: 0000.0000.0002 Interface: GigabitEthernet1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 26s Type: L2 PRI: 64 [RouterD] display isis interface Interface information for IS-IS(1) --------------------------------- Interface: GigabitEthernet1/1/1...
  • Page 196 [RouterA-isis-1] is-level level-1 [RouterA-isis-1] network-entity 10.0000.0000.0001.00 [RouterA-isis-1] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] isis enable 1 [RouterA-GigabitEthernet1/1/1] quit # Configure Router B. <RouterB> system-view [RouterB] isis 1 [RouterB-isis-1] is-level level-1 [RouterB-isis-1] network-entity 10.0000.0000.0002.00 [RouterB-isis-1] quit [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] isis enable 1 [RouterB-GigabitEthernet1/1/1] quit # Configure Router C.
  • Page 197 ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 10.1.1.0/24 NULL GE1/1/1 Direct D/L/- 10.1.2.0/24 NULL GE1/1/1 10.1.1.1 R/-/- 192.168.0.0/24 NULL GE1/1/1 10.1.1.1 R/-/- 0.0.0.0/0 NULL GE1/1/1 10.1.1.1 R/-/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set [RouterC] display isis route Route information for IS-IS(1) -----------------------------...
  • Page 198 10.1.2.0/24 NULL GE1/1/2 192.168.0.1 R/-/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Configure RIPv2 on Router D and Router E, and configure IS-IS to redistribute RIP routes on Router D: # Configure RIPv2 on Router D. [RouterD] rip 1 [RouterD-rip-1] network 10.0.0.0 [RouterD-rip-1] version 2...

  • Page 199: Is-Is Authentication Configuration Example

    Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set IS-IS authentication configuration example Network requirements As shown in Figure 47, Router A, Router B, Router C, and Router D reside in the same IS-IS routing domain. Router A, Router B, and Router C belong to Area 10, and Router D belongs to Area 20. •...
  • Page 200 [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] isis enable 1 [RouterB-GigabitEthernet1/1/1] quit # Configure Router C. <RouterC> system-view [RouterC] isis 1 [RouterC-isis-1] network-entity 10.0000.0000.0003.00 [RouterC-isis-1] quit [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] isis enable 1 [RouterC-GigabitEthernet1/1/1] quit [RouterC] interface gigabitethernet 1/1/2 [RouterC-GigabitEthernet1/1/2] isis enable 1 [RouterC-GigabitEthernet1/1/2] quit [RouterC] interface gigabitethernet 1/1/3 [RouterC-GigabitEthernet1/1/3] isis enable 1...

  • Page 201: Is-Is Gr Configuration Example

    [RouterD-GigabitEthernet1/1/1] isis authentication-mode md5 plain hSec [RouterD-GigabitEthernet1/1/1] quit Set the area authentication mode to MD5 and set the plaintext key to 10Sec on Router A, Router B, and Router C. [RouterA] isis 1 [RouterA-isis-1] area-authentication-mode md5 plain 10Sec [RouterA-isis-1] quit [RouterB] isis 1 [RouterB-isis-1] area-authentication-mode md5 plain 10Sec [RouterB-isis-1] quit...

  • Page 202: Is-Is Nsr Configuration Example

    Verifying the configuration # Restart the IS-IS process on Router A. <RouterA> reset isis all 1 graceful-restart Reset IS-IS process? [Y/N]:y # Check the GR state of the IS-IS process on Router A. <RouterA> display isis graceful-restart status Restart information for IS-IS(1) -------------------------------- Restart status: COMPLETE Restart phase: Finish...
  • Page 203 [RouterS-isis-1] non-stop-routing [RouterS-isis-1] return Verifying the configuration # Reoptimize process placement on Router S to trigger an active/standby switchover. <RouterS> system-view [RouterS] placement reoptimize Predicted changes to the placement Program Current location New location --------------------------------------------------------------------- syslog diagusageratio l3vpn lauth track ip6addr ipaddr trange...
  • Page 204 Peer information for IS-IS(1) ---------------------------- System Id: 0000.0000.0001 Interface: GE1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: Type: L1(L1L2) PRI: 64 System Id: 0000.0000.0001 Interface: GE1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: Type: L2(L1L2) PRI: 64 # Display IS-IS routing information on Router A to verify that Router A has a route to the loopback interface of Router B.

  • Page 205: Bfd For Is-Is Configuration Example

    Interface: GE1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: Type: L1(L1L2) PRI: 64 System Id: 0000.0000.0001 Interface: GE1/1/1 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: Type: L2(L1L2) PRI: 64 # Display IS-IS routing information on Router B to verify that Router B has a route to the loopback interface of Router A.
  • Page 206 Figure 50 Network diagram Router A Router B GE1/1/1 GE1/1/1 Loop0 Loop0 GE1/1/2 GE1/1/2 L2 Switch Area 0 GE1/1/1 GE1/1/2 Router C Device Interface IP address Device Interface IP address Router A GE1/1/1 192.168.0.102/24 Router B GE1/1/1 192.168.0.100/24 GE1/1/2 10.1.1.102/24 GE1/1/2 13.1.1.1/24 Loop0...
  • Page 207 [RouterB-GigabitEthernet1/1/1] isis enable [RouterB-GigabitEthernet1/1/1] quit [RouterB] interface gigabitethernet 1/1/2 [RouterB-GigabitEthernet1/1/2] isis enable [RouterB-GigabitEthernet1/1/2] quit # Configure Router C. <RouterC> system-view [RouterC] isis [RouterC-isis-1] network-entity 10.0000.0000.0003.00 [RouterC-isis-1] quit [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] isis enable [RouterC-GigabitEthernet1/1/1] quit [RouterC] interface gigabitethernet 1/1/2 [RouterC-GigabitEthernet1/1/2] isis enable [RouterC-GigabitEthernet1/1/2] quit Configure BFD functions:...

  • Page 208: Is-Is Frr Configuration Example

    Protocol: IS_L1 Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 10 Preference: 10 IpPre: N/A QosLocalID: N/A 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: 192.168.0.100 Label: NULL RealNextHop: 192.168.0.100...
  • Page 209 • Run IS-IS on all the routers to interconnect them with each other. • Configure IS-IS FRR so that when Link A fails, traffic can be switched to Link B immediately. Figure 51 Network diagram Router C Link B Link A Loop0 Loop0 GE1/1/2...
  • Page 210 [RouterA-route-policy-frr-10] if-match ip address prefix-list abc [RouterA-route-policy-frr-10] apply fast-reroute backup-interface gigabitethernet 1/1/1 backup-nexthop 12.12.12.2 [RouterA-route-policy-frr-10] quit [RouterA] isis 1 [RouterA-isis-1] address-family ipv4 [RouterA-isis-1-ipv4] fast-reroute route-policy frr [RouterA-isis-1-ipv4] quit [RouterA-isis-1] quit # Configure Router B. <RouterB> system-view [RouterB] ip prefix-list abc index 10 permit 1.1.1.1 32 [RouterB] route-policy frr permit node 10 [RouterB-route-policy-frr-10] if-match ip address prefix-list abc [RouterB-route-policy-frr-10] apply fast-reroute backup-interface...
  • Page 211 Summary Count : 1 Destination: 1.1.1.1/32 Protocol: IS_L1 Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 10 Preference: 10 IpPre: N/A QosLocalID: N/A 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...

  • Page 212: 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 213 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 214 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 215 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 216: 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 217: Bgp Load Balancing

    • When multiple feasible routes to a destination exist, BGP advertises only the optimal route to its peers. If the advertise-rib-active command is configured, BGP advertises the optimal route in the IP routing table. If not, BGP advertises the optimal route in the BGP routing table. •...

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

    Figure 56 Network diagram 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 219 Figure 57 BGP route dampening Penalty value Suppress threshold Reusable threshold Suppression time Time Half-life • Peer group You can organize BGP peers with the same attributes into a group to simplify their configurations. When a peer joins the peer group, the peer obtains the same configuration as the peer group. If the configuration of the peer group is changed, the configuration of group members is changed.
  • Page 220 The route reflector and clients form a cluster. Typically a cluster has one route reflector. The ID of the route reflector is the Cluster_ID. You can configure more than one route reflector in a cluster to improve availability, as shown in Figure 59.

  • Page 221: Mp-Bgp

    A non-confederation BGP speaker does not need to know sub-ASs in the confederation. It considers the confederation as one AS, and the confederation ID as the AS number. In the above figure, AS 200 is the confederation ID. Confederation has a deficiency. When you change an AS into a confederation, you must reconfigure the routers, and the topology will be changed.

  • Page 222: Bgp Multi-Instance

    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. Address family MP-BGP uses address families and subsequent address families to identify different network layer protocols for routes contained in the MP_REACH_NLRI and MP_UNREACH_NLRI attributes.
  • Page 223 View names Ways to enter the views Remarks <Sysname> system-view Configurations in this view apply to [Sysname] bgp 100 instance abc BGP IPv4 multicast address IPv4 multicast routes and peers of family view [Sysname-bgp-abc] the specified BGP instance. address-family ipv4 multicast [Sysname-bgp-abc-mul-ipv4] <Sysname>...

  • Page 224: Protocols And Standards

    View names Ways to enter the views Remarks <Sysname> system-view [Sysname] bgp 100 instance abc Configurations in this view apply to [Sysname-bgp-abc] ip BGP-VPN IPv6 unicast IPv6 unicast routes and peers in the vpn-instance vpn1 address family view specified VPN instance of the specified BGP instance.

  • Page 225: Bgp Configuration Task List

    BGP configuration task list On a basic BGP network, perform the following configuration tasks: • 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 226 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 227 Tasks at a glance Remarks (Optional.) Controlling route distribution and reception: • Configuring BGP route summarization BGP cannot advertise • Advertising optimal routes in the IP routing table optimal routes in the IP • Advertising a default route to a peer or peer group routing table for IPv6 multicast address •...

  • Page 228: Configuring Basic Bgp

    Tasks at a glance Remarks (Optional.) Configuring BGP LS Configuring basic BGP This section describes the basic settings required for a BGP network to run. Enabling BGP A router ID is the unique identifier of a BGP router in an AS. •...

  • Page 229: Configuring A Bgp Peer

    Step Command Remarks By default, no router ID is configured for a BGP VPN instance, and the BGP VPN instance uses (Optional.) Configure a the router ID configured in BGP router-id { router-id | router ID for the BGP VPN instance view.
  • Page 230 Step Command Remarks Create an IPv6 BGP peer By default, no IPv6 BGP peers peer ipv6-address as-number and specify its AS number. exist. as-number (Optional.) Configure a By default, no description is peer ipv6-address description description for a peer. configured for a peer. text Create the BGP IPv6 unicast By default, no BGP IPv6 unicast...

  • Page 231: Configuring Dynamic Bgp Peers

    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. After a device in the network initiates a connection request, BGP establishes a dynamic peer relationship with the device.
  • Page 232 Step Command Remarks Specify devices in a network as dynamic BGP By default, no dynamic BGP peer ipv6-address prefix-length peers and specify an AS peers exist. as-number as-number number for the peers. (Optional.) Configure a By default, no description is peer ipv6-address prefix-length description for dynamic configured for dynamic BGP...

  • Page 233: Configuring A Bgp Peer Group

    Step Command Remarks (Optional.) Configure a By default, no description is peer ipv6-address prefix-length description for dynamic BGP configured for dynamic BGP description text peers. peers. Create the BGP IPv6 By default, no BGP IPv6 multicast address family and multicast address family address-family ipv6 multicast enter its view.
  • Page 234 Step Command Remarks Create the BGP IPv4 unicast By default, no BGP IPv4 unicast address family or BGP-VPN address-family ipv4 [ unicast ] address family or BGP-VPN IPv4 IPv4 unicast address family unicast address family exists. and enter its view. Enable the router to exchange IPv4 unicast By default, the router cannot...
  • Page 235 Step Command Remarks By default, no peer exists in the peer group. peer ipv4-address [ mask-length ] Add an IPv4 peer into the group group-name [ as-number The as-number as-number IBGP peer group. as-number ] option must specify the local AS number.
  • Page 236 • Method 3—Create an EBGP peer group and add a peer with an AS number into it. Peers added in the group can have different AS numbers. To configure an EBGP peer group by using Method 1 (IPv4 unicast address family): Step Command Remarks...
  • Page 237 Step Command Remarks • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name By default, no EBGP peer groups Create an EBGP peer group.
  • Page 238 Step Command Remarks By default, no peers exist in the peer group. peer ipv4-address [ mask-length ] The as-number as-number Add an IPv4 BGP peer into group group-name [ as-number option, if used, must specify the the EBGP peer group. as-number ] same AS number as the peer group-name as-number...
  • Page 239 Step Command Remarks Enter system view. system-view • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name By default, no EBGP peer groups Create an EBGP peer group.
  • Page 240 Step Command Remarks Create an IPv6 BGP peer peer ipv6-address [ prefix-length ] By default, no IPv6 BGP peers and specify its AS number. exist. as-number as-number By default, no peers exist in the peer group. The as-number as-number peer ipv6-address [ prefix-length ] Add the peer into the EBGP option, if used, must specify the group group-name [ as-number...
  • Page 241 To configure an EBGP peer group by using Method 2 (IPv6 multicast address family): Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] By default, no EBGP peer groups Create an EBGP peer group. group group-name external exist.
  • Page 242 Step Command Remarks Create the BGP IPv4 unicast By default, no BGP IPv4 unicast address family or BGP-VPN address-family ipv4 [ unicast ] address family or BGP-VPN IPv4 IPv4 unicast address family unicast address family exists. and enter its view. Enable the router to exchange IPv4 unicast By default, the router cannot...

  • Page 243: Specifying The Source Address Of Tcp Connections

    Step Command Remarks peer ipv4-address [ mask-length ] Add an IPv4 BGP peer into By default, no peers exist in the group group-name as-number the EBGP peer group. peer group. as-number (Optional.) Configure a By default, no description is peer group-name description description for the peer configured for the peer group.
  • Page 244 • If the source interface fails on a BGP router that has multiple links to a peer, BGP must re-establish TCP connections. To avoid this problem, use a loopback interface as the source interface or use the IP address of a loopback interface as the source address. •...

  • Page 245: Generating Bgp Routes

    Generating BGP routes BGP can generate routes in the following ways: • Advertise local networks. • Redistribute IGP routes. Injecting a local network Perform this task to inject a network in the local routing table to the BGP routing table, so BGP can advertise the network to BGP peers.

  • Page 246: Redistributing Igp Routes

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

  • Page 248: Controlling Route Distribution And Reception

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

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

    Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...

  • Page 252: Advertising A Default Route To A Peer Or Peer Group

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

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

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

  • Page 256: Configuring Bgp Route Filtering Policies

    Step Command Remarks 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 router can receive from a discard | reconnect peer or peer group is not limited.
  • Page 257 Step Command Remarks • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4 [ unicast ] • Enter BGP-VPN IPv4 unicast address family view: Enter BGP IPv4 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...
  • Page 258 Step Command Remarks • Reference an ACL or IP prefix list to filter advertised BGP routes: filter-policy { ipv4-acl-number | prefix-list prefix-list-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] • Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name |...
  • Page 259 Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 260 Step Command Remarks • Reference an ACL or IPv6 prefix list to filter advertised BGP routes: filter-policy { ipv6-acl-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 261 Step Command Remarks Enter system view. system-view • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4 [ unicast ] • Enter BGP-VPN IPv4 unicast address family view: Enter BGP IPv4 unicast a.

  • Page 262: Configuring Bgp Route Update Delay

    Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number [ instance address family view, instance-name ] BGP-VPN IPv6 unicast...

  • Page 263: Configuring Bgp Route Dampening

    To configure BGP route update delay: Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] Configure BGP to delay By default, BGP immediately bgp update-delay on-startup sending route updates on sends route updates on reboot. seconds reboot.

  • Page 264: Controlling Bgp Path Selection

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

  • Page 266: Configuring Preferences For Bgp Routes

    Step Command Remarks Set a preferred value for peer { group-name | ipv6-address routes received from a peer [ prefix-length ] } preferred-value The default preferred value is 0. or peer group. value Configuring preferences for BGP routes Routing protocols each have a default preference. If they find multiple routes destined for the same network, the route found by the routing protocol with the highest preference is selected as the optimal route.

  • Page 267: Configuring The Default Local Preference

    To configure preferences for BGP routes (IPv6 unicast/multicast address family): Step Command Remarks Enter system view. system-view • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a.
  • Page 268 Step Command Remarks • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4 [ unicast ] • Enter BGP-VPN IPv4 unicast address family view: Enter BGP IPv4 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 269: Configuring The Med Attribute

    Step Command Remarks Configure the default local The default local preference is default local-preference value preference. 100. Configuring the MED attribute BGP uses MED to determine the optimal route for traffic going into an AS. When a BGP router obtains multiple routes with the same destination but with different next hops, it considers the route with the smallest MED value as the optimal route if other conditions are the same.
  • Page 270 Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 271 Figure 61 Route selection based on MED (in an IPv4 network) As shown in Figure 61, Router D establishes indirect EBGP peer relationships with Router A, Router B, and Router C, and learns addresses 1.1.1.1/32, 2.2.2.2/32, and 3.3.3.3/32 through OSPF. The following output shows the routing information on Router D.

  • Page 272: Configuring The Next_Hop Attribute

    1.1.1.1 200 400e To enable MED comparison for routes on a per-AS basis: Step Command Remarks Enter system view. system-view • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view.
  • Page 273 For example, as shown in Figure 62, Router A and Router B establish an EBGP neighbor relationship, and Router B and Router C establish an IBGP neighbor relationship. If Router C has no route destined for IP address 1.1.1.1/24, you must configure Router B to set itself 3.1.1.1/24 as the next hop for the network 2.1.1.1/24 advertised to Router C.
  • Page 274 Step Command Remarks • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4 [ unicast ] • Enter BGP-VPN IPv4 unicast address family view: Enter BGP IPv4 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 275: 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. To permit the local AS number to appear in routes from a peer or peer group and specify the appearance times (IPv4 unicast/multicast address family): Step...
  • Page 276 Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 277 Step Command Remarks Enter system view. system-view • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name By default, no fake AS number is advertised to a peer or peer...
  • Page 278 Figure 64 AS number substitution configuration (in an IPv4 network) As shown in Figure 64, 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 279 Removing private AS numbers from updates sent to an EBGP peer or peer group Private AS numbers are typically used in test networks, and should not be transmitted in public networks. The range of private AS numbers is from 64512 to 65535. To remove private AS numbers from updates sent to an EBGP peer or peer group (IPv4 unicast/multicast address family): Step...

  • Page 280: Ignoring Igp Metrics During Optimal Route Selection

    Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...

  • Page 281: Configuring The Soo Attribute

    Step Command Remarks • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name By default, BGP considers IGP metrics during optimal route Configure BGP to ignore selection.

  • Page 282: Tuning And Optimizing Bgp Networks

    Step Command Remarks By default, no SoO attribute is Configure the SoO attribute peer { group-name | ipv4-address configured for a peer or peer for a peer or peer group. [ mask-length ] } soo site-of-origin group. To configure the SoO attribute (IPv6 unicast/multicast address family): Step Command Remarks...
  • Page 283 • If the keepalive interval is not 0, the actual keepalive interval is the smaller one between 1/3 of the hold time and the keepalive interval. To configure the keepalive interval and hold time (IPv4 unicast/multicast address family): Step Command Remarks Enter system view.

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

    Step Command Remarks Use at least one method. • Configure the global By default, the keepalive interval keepalive interval and hold is 60 seconds, and hold time is time: 180 seconds. timer keepalive keepalive The timer command takes effect hold holdtime for new BGP sessions and does •...

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

    Step Command Remarks • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] 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...

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

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

  • Page 287: Enabling Md5 Authentication For Bgp Peers

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

  • Page 288: Configuring Bgp Load Balancing

    Step Command Remarks • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name Enable MD5 authentication peer { group-name | ipv4-address By default, MD5 authentication is for a BGP peer group or...
  • Page 289 Step Command Remarks • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4 [ unicast ] • Enter BGP-VPN IPv4 unicast address family view: Enter BGP IPv4 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 290: Configuring Ipsec For Ipv6 Bgp

    Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...

  • Page 291: Disabling Bgp To Establish A Session To A Peer Or Peer Group

    Step Command Remarks • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name By default, no IPsec profile is configured for any IPv6 BGP peer Apply the IPsec profile to an peer { group-name | ipv6-address...

  • Page 292: Configuring Gtsm For Bgp

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

  • Page 293: Configuring Bgp Soft-Reset

    Step Command Remarks Enter system view. system-view • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance Enter BGP instance view or view: BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name Configure GTSM for the peer { group-name | ipv6-address...
  • Page 294 Step Command Remarks • Enter BGP instance view: bgp as-number [ instance instance-name ] • Enter BGP-VPN instance view: Enter BGP instance view or BGP-VPN instance view. a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name • Enable BGP route refresh for the specified peer or peer group: peer { group-name |...
  • Page 295 Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv6-address [ prefix-length ] } capability-advertise route-refresh By default, the BGP route refresh, Enable BGP route refresh for • multi-protocol extension, and Enable the BGP route a peer or peer group.
  • Page 296 To save all route updates from the specified peer or peer group (IPv6 unicast/multicast address family): Step Command Remarks Enter system view. system-view • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] •...
  • Page 297 Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv4-address [ mask-length ] } capability-advertise route-refresh By default, the BGP route refresh, Enable BGP route refresh for • multi-protocol extension, and Enable the BGP route a peer or peer group.
  • Page 298 Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv6-address [ prefix-length ] } capability-advertise route-refresh By default, the BGP route refresh, Enable BGP route refresh for • multi-protocol extension, and Enable the BGP route a peer or peer group.

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

    Step Command Remarks • Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } capability-advertise route-refresh By default, the BGP route refresh, Enable BGP route refresh for •...

  • Page 300: Configuring An Update Delay For Local Mpls Labels

    Step Command Remarks Configure BGP to protect an By default, BGP periodically tears peer { group-name | ipv4-address EBGP peer or peer group down an EBGP session to release [ mask-length ] } when the memory usage memory resources when level 2 low-memory-exempt reaches level 2 threshold.

  • Page 301: Configuring A Large-Scale Bgp Network

    After the suboptimal route is flushed to the RIB on a network, BGP immediately switches traffic to the suboptimal route when the optimal route fails. For example, the device has a static route to the subnet 1.1.1.0/24 that has a higher priority than a BGP route.
  • Page 302 Step Command Remarks • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4 [ unicast ] • Enter BGP-VPN IPv4 unicast address family view: Enter BGP IPv4 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 303: Configuring Bgp Route Reflection

    Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6 [ unicast ] • Enter BGP-VPN IPv6 unicast address family view: Enter BGP IPv6 unicast a. bgp as-number [ instance address family view, instance-name ] BGP-VPN IPv6 unicast...
  • Page 304 Step Command Remarks • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4 [ unicast ] • Enter BGP-VPN IPv4 unicast address family view: Enter BGP IPv4 unicast a. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...
  • Page 305 Step Command Remarks Configure the router as a route reflector and specify a peer { group-name | ipv6-address By default, no route reflector or peer or peer group as its [ prefix-length ] } reflect-client client is configured. client. Enable route reflection By default, route reflection reflect between-clients between clients.

  • Page 306: Configuring A Bgp Confederation

    Step Command Remarks 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 ] } result in a routing loop. attribute. ignore-originatorid After you execute this command, BGP also ignores the CLUSTER_LIST attribute.

  • Page 307: Configuring Bgp Gr

    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: • GR restarter—Performs GR upon a BGP restart or active/standby switchover. •...

  • Page 308: Configuring Bgp Nsr

    Step Command Remarks 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. Configure the maximum time to The default setting is 180 graceful-restart timer wait for the End-of-RIB marker.

  • Page 309: Enabling Logging For Session State Changes

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

  • Page 310: Configuring Bgp Frr

    BGP maintains neighbor relationships based on the keepalive timer and hold timer in seconds. It requires that the hold time must be at least three times the keepalive interval. This mechanism slows down link failure detection. Once a failure occurs on a high-speed link, a large quantity of packets will be dropped before routing convergence completes.
  • Page 311 Figure 65 Network diagram for BGP FRR Backup nexthop: Router C Router A Router B Nexthop: Router D Router E After you configure FRR on Router B as shown in Figure 65, BGP generates a backup next hop Router C for the primary route. BGP uses ARP (for IPv4), echo-mode BFD (for IPv4), or ND (for IPv6) to detect the connectivity to Router D.
  • Page 312 Step Command Remarks By default, no routing policies exist. This step is required when Create a routing policy and Method 2 is used to enable BGP route-policy route-policy-name enter routing policy view. FRR. permit node node-number For more information about this command, see Layer 3—IP Routing Command Reference.

  • Page 313: Configuring Bgp Policy Accounting

    Step Command Remarks By default, no routing policies exist. This step is required when Method 2 route-policy Create a routing policy and is used to enable BGP FRR. route-policy-name permit enter routing policy view. For more information about this node node-number command, see Layer 3—IP Routing Command Reference.

  • Page 314: Configuring 6Pe

    Configure a routing policy, and assign an index to the matching BGP routes by using the apply traffic-index command. For more information about the apply traffic-index command, see Layer 3—IP Routing Command Reference. Configure BGP to use the routing policy. The network, import-route, aggregate, peer route-policy, and peer default-route-advertise commands can use a routing policy.

  • Page 315: Configuring Basic 6Pe

    • 6PE assigns a label to IPv6 routing information received from a CE router, and sends the labeled IPv6 routing information to the peer 6PE device through an MP-BGP session. The peer 6PE device then forwards the IPv6 routing information to the attached customer site. •...
  • Page 316 Step Command Remarks Enter BGP IPv6 unicast address-family ipv6 [ unicast ] address family view. Advertise COMMUNITY peer { group-name | ipv4-address By default, the COMMUNITY attribute to the 6PE peer or [ mask-length ] } attribute is not advertised. peer group.

  • Page 317: Configuring Bgp Ls

    Step Command Remarks 18. Return to user view. return display bgp [ instance instance-name ] peer ipv6 [ unicast ] 19. Display information about the [ ipv4-address mask-length | Available in any view. 6PE peer or peer group. { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ] display bgp [ instance...

  • Page 318: Configuring Bgp Ls Route Reflection

    Configuring BGP LS route reflection Perform this task to configure a BGP route reflector and its clients. The route reflector and its clients automatically form a cluster identified by the router ID of the route reflector. The route reflector forwards route updates among its clients. To configure BGP LS route reflection: Step Command...
  • Page 319 Task Command display bgp [ instance instance-name ] non-stop-routing Display BGP NSR status information. status display bgp [ instance instance-name ] group ipv4 [ unicast ] Display BGP IPv4 unicast peer group [ vpn-instance vpn-instance-name ] [ group-name information. group-name ] display bgp [ instance instance-name ] peer ipv4 [ unicast ] Display BGP IPv4 unicast peer or peer [ vpn-instance vpn-instance-name ] [ ipv4-address mask-length...
  • Page 320 Task Command display bgp [ instance instance-name ] peer ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length | { ipv6-address | group-name group-name } Display BGP IPv6 unicast peer or peer log-info | [ ipv6-address ] verbose ] group information.
  • Page 321 Task Command Display BGP IPv4 multicast peer group display bgp [ instance instance-name ] group ipv4 multicast information. [ group-name group-name ] display bgp [ instance instance-name ] peer ipv4 multicast Display BGP IPv4 multicast peer or peer [ ipv4-address mask-length | { ipv4-address | group-name group information.

  • Page 322: Resetting Bgp Sessions

    Task Command Display BGP dampening parameter display bgp [ instance instance-name ] dampening information. parameter ipv6 multicast display bgp [ instance instance-name ] routing-table Display BGP IPv6 multicast routing flap flap-info ipv6 multicast [ ipv6-address prefix-length | statistics. as-path-acl as-path-acl-number ] Display information about routes advertised by the network command and display bgp [ instance instance-name ] network ipv6...

  • Page 323: Clearing Bgp Information

    Task Command reset bgp [ instance instance-name ] { as-number | Reset BGP sessions for IPv4 multicast ipv4-address [ mask-length ] | all | external | group group-name address family. | internal } ipv4 multicast reset bgp [ instance instance-name ] { as-number | Reset BGP sessions for IPv6 multicast ipv6-address [ prefix-length ] | all | external | group group-name address family.
  • Page 324 Figure 67 Network diagram Requirements analysis To prevent route flapping caused by port state changes, this example uses loopback interfaces to establish IBGP connections. Because loopback interfaces are virtual interfaces, you need to use the peer connect-interface command to specify the loopback interface as the source interface for establishing BGP connections.
  • Page 325 [RouterC] ospf 1 [RouterC-ospf-1] area 0 [RouterC-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [RouterC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] quit [RouterC-ospf-1] quit [RouterC] display bgp peer ipv4 BGP local router ID : 3.3.3.3 Local AS number : 65009 Total number of peers : 1 Peers in established state : 1 * - Dynamically created peer Peer...
  • Page 326 The output shows that Router B has established an IBGP peer relationship with Router C and an EBGP peer relationship with Router A. # Display the BGP routing table on Router A. [RouterA] display bgp routing-table ipv4 Total number of routes: 1 BGP local router ID is 1.1.1.1 Status codes: * - valid, >...
  • Page 327 [RouterB-bgp-default] address-family ipv4 unicast [RouterB-bgp-default-ipv4] import-route direct [RouterB-bgp-default-ipv4] quit [RouterB-bgp-default] quit # Display the BGP routing table on Router A. [RouterA] display bgp routing-table ipv4 Total number of routes: 4 BGP local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network...

  • Page 328: Bgp And Igp Route Redistribution Configuration Example

    --- Ping statistics for 8.1.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.000/0.600/2.000/0.800 ms BGP and IGP route redistribution configuration example Network requirements As shown in Figure 68, all devices of company A belong to AS 65008 and all devices of company B belong to AS 65009.
  • Page 329 Configure the EBGP connection and inject network 8.1.1.0/24 to the BGP routing table of Router A, so Router B can obtain the route to 8.1.1.0/24. # Configure Router A. <RouterA> system-view [RouterA] bgp 65008 [RouterA-bgp-default] router-id 1.1.1.1 [RouterA-bgp-default] peer 3.1.1.1 as-number 65009 [RouterA-bgp-default] address-family ipv4 unicast [RouterA-bgp-default-ipv4] peer 3.1.1.1 enable [RouterA-bgp-default-ipv4] network 8.1.1.0 24...

  • Page 330: Bgp Route Summarization Configuration Example

    Destination Cost Type NextHop AdvRouter Area 9.1.1.0/24 Transit 9.1.1.2 3.3.3.3 0.0.0.0 2.2.2.2/32 Stub 9.1.1.1 2.2.2.2 0.0.0.0 Routing for ASEs Destination Cost Type NextHop AdvRouter 8.1.1.0/24 Type2 9.1.1.1 2.2.2.2 Total Nets: 3 Intra Area: 2 Inter Area: 0 ASE: 1 NSSA: 0 Verifying the configuration # Use ping to test connectivity.
  • Page 331 Figure 69 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure static routing between Router A and Router B: # Configure a default route with the next hop 192.168.212.1 on Router A. <RouterA> system-view [RouterA] ip route-static 0.0.0.0 0 192.168.212.1 # Configure static routes to 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 with the same next hop 192.168.212.161 on Router B.
  • Page 332 OSPF Routing table Status : <Active> Summary count : 3 Destination/Mask Proto Cost NextHop Interface 192.168.64.0/24 OSPF 172.17.100.1 GE1/1/1 192.168.74.0/24 OSPF 172.17.100.1 GE1/1/1 192.168.99.0/24 OSPF 172.17.100.1 GE1/1/1 OSPF Routing table Status : <Inactive> Summary count : 2 Destination/Mask Proto Cost NextHop Interface 10.220.2.0/24...

  • Page 333: Bgp Load Balancing Configuration Example

    BGP Routing table Status : <Inactive> Summary count : 0 The output shows that Router D has learned routes to 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 through BGP. # Ping the hosts on networks 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 from Router D. The ping operations succeed. Configure route summarization on Router C to summarize 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 into a single route 192.168.64.0/18, and disable advertisement of specific routes.
  • Page 334 Figure 70 Network diagram Requirements analysis On Router A, establish EBGP connections with Router B and Router C. Configure BGP to advertise network 8.1.1.0/24 to Router B and Router C. This allows Router B and Router C can access the internal network connected to Router A.
  • Page 335 [RouterB-bgp-default] peer 3.3.3.3 as-number 65009 [RouterB-bgp-default] peer 3.3.3.3 connect-interface loopback 0 [RouterB-bgp-default] address-family ipv4 unicast [RouterB-bgp-default-ipv4] peer 3.1.1.2 enable [RouterB-bgp-default-ipv4] peer 3.3.3.3 enable [RouterB-bgp-default-ipv4] network 9.1.1.0 24 [RouterB-bgp-default-ipv4] quit [RouterB-bgp-default] quit [RouterB] ip route-static 3.3.3.3 32 9.1.1.2 # Configure Router C. <RouterC>...

  • Page 336: Bgp Community Configuration Example

    [RouterA-bgp-default-ipv4] quit [RouterA-bgp-default] quit Verifying the configuration # Display the BGP routing table on Router A. [RouterA] display bgp routing-table ipv4 Total number of routes: 3 BGP local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network...
  • Page 337 <RouterA> system-view [RouterA] bgp 10 [RouterA-bgp-default] router-id 1.1.1.1 [RouterA-bgp-default] peer 200.1.2.2 as-number 20 [RouterA-bgp-default] address-family ipv4 unicast [RouterA-bgp-default-ipv4] peer 200.1.2.2 enable [RouterA-bgp-default-ipv4] network 9.1.1.0 255.255.255.0 [RouterA-bgp-default-ipv4] quit [RouterA-bgp-default] quit # Configure Router B. <RouterB> system-view [RouterB] bgp 20 [RouterB-bgp-default] router-id 2.2.2.2 [RouterB-bgp-default] peer 200.1.2.1 as-number 10 [RouterB-bgp-default] peer 200.1.3.2 as-number 30 [RouterB-bgp-default] address-family ipv4 unicast...
  • Page 338 Traffic index : N/A # Display advertisement information for the route 9.1.1.0 on Router B. [RouterB] display bgp routing-table ipv4 9.1.1.0 advertise-info BGP local router ID: 2.2.2.2 Local AS number: 20 Paths: 1 best BGP routing table information of 9.1.1.0/24: Advertised to peers (1 in total): 200.1.3.2 The output shows that Router B can advertise the route with the destination 9.1.1.0/24 to other...

  • Page 339: Bgp Route Reflector Configuration Example

    BGP routing table information of 9.1.1.0/24: From : 200.1.2.1 (1.1.1.1) Rely nexthop : 200.1.2.1 Original nexthop: 200.1.2.1 OutLabel : NULL Community : No-Export AS-path : 10 Origin : igp Attribute value : pref-val 0 State : valid, external, best IP precedence : N/A QoS local ID : N/A...
  • Page 340 Figure 72 Network diagram Loop0 Loop0 1.1.1.1/32 3.3.3.3/32 GE1/1/1 Route reflector 20.1.1.1/8 GE1/1/2 GE1/1/1 GE1/1/2 192.1.1.1/24 193.1.1.1/24 194.1.1.1/24 Router A Router C Loop0 Loop0 2.2.2.2/32 4.4.4.4/32 GE1/1/1 GE1/1/1 GE1/1/2 194.1.1.2/24 192.1.1.2/24 193.1.1.2/24 AS 100 AS 200 Router B Router D Configuration procedure Configure IP addresses for interfaces and configure OSPF in AS 200.
  • Page 341 [RouterC-bgp-default-ipv4] quit [RouterC-bgp-default] quit # Configure Router D. <RouterD> system-view [RouterD] bgp 200 [RouterD-bgp-default] router-id 4.4.4.4 [RouterD-bgp-default] peer 194.1.1.1 as-number 200 [RouterD-bgp-default] address-family ipv4 unicast [RouterD-bgp-default-ipv4] peer 194.1.1.1 enable [RouterD-bgp-default-ipv4] quit [RouterD-bgp-default] quit Configure Router C as the route reflector. [RouterC] bgp 200 [RouterC-bgp-default] address-family ipv4 unicast [RouterC-bgp-default-ipv4] peer 193.1.1.2 reflect-client...

  • Page 342: Bgp Confederation Configuration Example

    BGP confederation configuration example Network requirements As shown in Figure 73, split AS 200 into three sub-ASs (AS 65001, AS 65002, and AS 65003) to reduce IBGP connections. Routers in AS 65001 are fully meshed. Figure 73 Network diagram Table 15 Interface and IP address assignment Device Interface IP address...
  • Page 343 [RouterA-bgp-default-ipv4] peer 10.1.1.2 next-hop-local [RouterA-bgp-default-ipv4] peer 10.1.2.2 next-hop-local [RouterA-bgp-default-ipv4] quit [RouterA-bgp-default] quit # Configure Router B. <RouterB> system-view [RouterB] bgp 65002 [RouterB-bgp-default] router-id 2.2.2.2 [RouterB-bgp-default] confederation id 200 [RouterB-bgp-default] confederation peer-as 65001 65003 [RouterB-bgp-default] peer 10.1.1.1 as-number 65001 [RouterB-bgp-default] address-family ipv4 unicast [RouterB-bgp-default-ipv4] peer 10.1.1.1 enable [RouterB-bgp-default-ipv4] quit [RouterB-bgp-default] quit...
  • Page 344 [RouterD-bgp-default-ipv4] quit [RouterD-bgp-default] quit # Configure Router E. <RouterE> system-view [RouterE] bgp 65001 [RouterE-bgp-default] router-id 5.5.5.5 [RouterE-bgp-default] confederation id 200 [RouterE-bgp-default] peer 10.1.4.1 as-number 65001 [RouterE-bgp-default] peer 10.1.5.1 as-number 65001 [RouterE-bgp-default] address-family ipv4 unicast [RouterE-bgp-default-ipv4] peer 10.1.4.1 enable [RouterE-bgp-default-ipv4] peer 10.1.5.1 enable [RouterE-bgp-default-ipv4] quit [RouterE-bgp-default] quit Configure the EBGP connection between AS 100 and AS 200:...
  • Page 345 [RouterB] 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 BGP routing table information of 9.1.1.0/24: From : 10.1.1.1 (1.1.1.1) Rely nexthop : 10.1.1.1 Original nexthop: 10.1.1.1 OutLabel : NULL AS-path : (65001) 100 Origin...

  • Page 346: Bgp Path Selection Configuration Example

    IP precedence : N/A QoS local ID : N/A Traffic index : N/A The output shows the following: • Router F can send route information to Router B and Router C through the confederation by establishing only an EBGP connection with Router A. •...
  • Page 347 [RouterB-ospf] area 0 [RouterB-ospf-1-area-0.0.0.0] network 192.1.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.0] quit [RouterB-ospf-1] quit # Configure Router C. <RouterC> system-view [RouterC] ospf [RouterC-ospf] area 0 [RouterC-ospf-1-area-0.0.0.0] network 193.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] quit [RouterC-ospf-1] quit # Configure Router D. <RouterD>...
  • Page 348 [RouterC-bgp-default-ipv4] peer 193.1.1.1 enable [RouterC-bgp-default-ipv4] peer 195.1.1.1 enable [RouterC-bgp-default-ipv4] quit [RouterC-bgp-default] quit # Configure Router D. [RouterD] bgp 200 [RouterD-bgp-default] peer 194.1.1.2 as-number 200 [RouterD-bgp-default] peer 195.1.1.2 as-number 200 [RouterD-bgp-default] address-family ipv4 unicast [RouterD-bgp-default-ipv4] peer 194.1.1.2 enable [RouterD-bgp-default-ipv4] peer 195.1.1.2 enable [RouterD-bgp-default-ipv4] quit [RouterD-bgp-default] quit Configure local preference for the route 1.0.0.0/8 to make Router D give priority to the route...

  • Page 349: Bgp Gr Configuration Example

    BGP GR configuration example Network requirements As shown in Figure 75, run EBGP between Router A and Router B, and run IBGP between Router B and Router C. Configure BGP GR so that the communication between Router A and Router C is not affected when an active/standby switchover occurs on Router B.

  • Page 350: Bfd For Bgp Configuration Example

    # Enable Router B to exchange IPv4 unicast routing information with Router A and Router C. [RouterB-bgp-default-ipv4] peer 200.1.1.2 enable [RouterB-bgp-default-ipv4] peer 9.1.1.2 enable Configure Router C: # Configure IP addresses for interfaces. (Details not shown.) # Configure the IBGP connection. <RouterC>...
  • Page 351 # Establish two IBGP connections to Router C. <RouterA> system-view [RouterA] bgp 200 [RouterA-bgp-default] peer 3.0.2.2 as-number 200 [RouterA-bgp-default] peer 2.0.2.2 as-number 200 [RouterA-bgp-default] address-family ipv4 unicast [RouterA-bgp-default-ipv4] peer 3.0.2.2 enable [RouterA-bgp-default-ipv4] peer 2.0.2.2 enable [RouterA-bgp-default-ipv4] quit # Create IPv4 basic ACL 2000 to permit 1.1.1.0/24 to pass. [RouterA] acl basic 2000 [RouterA-acl-ipv4-basic-2000] rule permit source 1.1.1.0 0.0.0.255 [RouterA-acl-ipv4-basic-2000] quit...
  • Page 352 Verifying the configuration # Display detailed BFD session information on Router C. <RouterC> display bfd session verbose Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 Session Working Under Ctrl Mode: Local Discr: 513 Remote Discr: 513 Source IP: 3.0.2.2 Destination IP: 3.0.1.1 Session State: Up...

  • Page 353: Bgp Frr Configuration Example

    AttrID: 0x1 Neighbor: 3.0.1.1 Flags: 0x10060 OrigNextHop: 3.0.1.1 Label: NULL RealNextHop: 3.0.2.1 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: GigabitEthernet1/1/1 BkTunnel ID: Invalid BkInterface: N/A FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A The output shows that Router C communicates with network 1.1.1.0/24 through the path Router C<—>Router B<—>Router A.
  • Page 354 Figure 77 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure OSPF in AS 200 to ensure connectivity among Router B, Router C, and Router D. (Details not shown.) Configure BGP connections: # Configure Router A to establish EBGP sessions to Router B and Router C, and advertise network 1.1.1.1/32.
  • Page 355 <RouterC> system-view [RouterC] bgp 200 [RouterC-bgp-default] router-id 3.3.3.3 [RouterC-bgp-default] peer 30.1.1.1 as-number 100 [RouterC-bgp-default] peer 4.4.4.4 as-number 200 [RouterC-bgp-default] peer 4.4.4.4 connect-interface loopback 0 [RouterC-bgp-default] address-family ipv4 unicast [RouterC-bgp-default-ipv4] peer 30.1.1.1 enable [RouterC-bgp-default-ipv4] peer 4.4.4.4 enable [RouterC-bgp-default-ipv4] peer 4.4.4.4 next-hop-local [RouterC-bgp-default-ipv4] quit [RouterC-bgp-default] quit # Configure Router D to establish IBGP sessions to Router B and Router C, and advertise...
  • Page 356 [RouterA-bgp-default] address-family ipv4 unicast [RouterA-bgp-default-ipv4] fast-reroute route-policy frr [RouterA-bgp-default-ipv4] quit [RouterA-bgp-default] quit # On Router D, set the source address of BFD echo packets to 44.1.1.1. [RouterD] bfd echo-source-ip 44.1.1.1 # Create routing policy frr to set a backup next hop 3.3.3.3 (Router C) for the route destined for 1.1.1.1/32.

  • Page 357: Multicast Bgp Configuration Example

    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 AttrID: 0x1 Neighbor: 2.2.2.2 Flags: 0x10060...
  • Page 358 Table 17 Interface and IP address assignment Device Interface IP address Device Interface IP address Source 10.110.1.100/24 Router C GE1/1/1 10.110.2.1/24 Router A GE1/1/1 10.110.1.1/24 GE1/1/2 192.168.2.1/24 GE1/1/2 192.168.1.1/24 GE1/1/3 192.168.4.2/24 Loop0 1.1.1.1/32 Loop0 3.3.3.3/32 Router B GE1/1/1 192.168.1.2/24 Router D GE1/1/1 192.168.3.2/24 GE1/1/2...
  • Page 359 # Configure the BSR boundary on Router B. [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] pim bsr-boundary [RouterB-GigabitEthernet1/1/1] quit Configure Loopback 0, C-BSR, and C-RP: # Configure the Loopback 0 interface and specify it as the C-BSR and C-RP on Router A. [RouterA] interface loopback 0 [RouterA-LoopBack0] ip address 1.1.1.1 32 [RouterA-LoopBack0] pim sm...

  • Page 360: Dynamic Bgp Peer Configuration Example

    # Configure an MSDP peer on Router A. [RouterA] msdp [RouterA-msdp] peer 192.168.1.2 connect-interface gigabitethernet 1/1/2 [RouterA-msdp] quit # Configure an MSDP peer on Router B. [RouterB] msdp [RouterB-msdp] peer 192.168.1.1 connect-interface gigabitethernet 1/1/1 [RouterB-msdp] quit Verifying the configuration # Verify the BGP IPv4 multicast peer information on Router B. [RouterB] display bgp peer ipv4 multicast BGP local router ID : 2.2.2.2 Local AS number : 200...
  • Page 361 Figure 79 Network diagram Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure IBGP peer relationships: # Configure Router A to establish dynamic BGP peer relationships with routers in network 10.1.0.0/16. <RouterA> system-view [RouterA] bgp 200 [RouterA-bgp-default] router-id 1.1.1.1 [RouterA-bgp-default] peer 10.1.0.0 16 as-number 200 [RouterA-bgp-default] address-family ipv4 [RouterA-bgp-default-ipv4] peer 10.1.0.0 16 enable...

  • Page 362: Bgp Ls Configuration Example

    [RouterD-bgp-default] peer 10.1.3.1 as-number 200 [RouterD-bgp-default] address-family ipv4 [RouterD-bgp-default-ipv4] peer 10.1.3.1 enable # Display BGP peer information on Router A. The output shows that Router A has established IBGP peer relationships with Router B, Router C, and Router D. [RouterA] display bgp peer ipv4 BGP local router ID : 1.1.1.1 Local AS number : 200 Total number of peers : 3...
  • Page 363 Figure 80 Network diagram Configuration procedure Configure IP addresses for interfaces and configure OSPF on Router C and Router D. (Details not shown.) Configure BGP connections: # Configure Router A. <RouterA> system-view [RouterA] bgp 100 [RouterA-bgp-default] peer 192.1.1.2 as-number 100 [RouterA-bgp-default] address-family link-state [RouterA-bgp-default-ls] peer 192.1.1.2 enable [RouterA-bgp-default-ls] quit...
  • Page 364 [RouterC-ospf-1-area-0.0.0.0] quit [RouterC-ospf-1] quit # Configure Router D. <RouterD> system-view [RouterD] bgp 100 [RouterD-bgp-default] peer 194.1.1.2 as-number 100 [RouterD-bgp-default] address-family link-state [RouterD-bgp-default-ls] peer 194.1.1.2 enable [RouterD-bgp-default-ls] quit [RouterD-bgp-default] quit [RouterD] ospf [RouterD-ospf-1] distribute bgp-ls [RouterD-ospf-1] area 0 [RouterD-ospf-1-area-0.0.0.0] network 0.0.0.0 0.0.0.0 [RouterD-ospf-1-area-0.0.0.0] quit [RouterD-ospf-1] quit Configure Router B as the route reflector.

  • Page 365: Ipv6 Bgp Configuration Examples

    Path/Ogn: i i Network : [T][O][I0x0][N[c100][b193.1.1.1][a0.0.0.0][r193.1.1.1]][P[o0x1][p193.1.1.0/24]]/480 NextHop : 193.1.1.1 LocPrf : 100 PrefVal : 0 OutLabel : NULL Path/Ogn: i i Network : [T][O][I0x0][N[c100][b194.1.1.1][a0.0.0.0][r194.1.1.1]][P[o0x1][p194.1.1.0/24]]/480 NextHop : 194.1.1.1 LocPrf : 100 PrefVal : 0 OutLabel : NULL Path/Ogn: i IPv6 BGP configuration examples IPv6 BGP basic configuration example Network requirements As shown in...
  • Page 366 [RouterC] bgp 65009 [RouterC-bgp-default] router-id 3.3.3.3 [RouterC-bgp-default] peer 9::1 as-number 65009 [RouterC-bgp-default] address-family ipv6 [RouterC-bgp-default-ipv6] peer 9::1 enable Configure EBGP: # Configure Router A. <RouterA> system-view [RouterA] bgp 65008 [RouterA-bgp-default] router-id 1.1.1.1 [RouterA-bgp-default] peer 10::1 as-number 65009 [RouterA-bgp-default] address-family ipv6 [RouterA-bgp-default-ipv6] peer 10::1 enable # Configure Router B.
  • Page 367 # Display IPv6 BGP routing table information on Router A. [RouterA] display bgp routing-table ipv6 Total number of routes: 4 BGP local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete * >e Network : 9::...

  • Page 368: Ipv6 Bgp Route Reflector Configuration Example

    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 PrefVal : 0 OutLabel : NULL Path/Ogn: i...
  • Page 369 [RouterA] bgp 100 [RouterA-bgp-default] router-id 1.1.1.1 [RouterA-bgp-default] peer 100::2 as-number 200 [RouterA-bgp-default] address-family ipv6 [RouterA-bgp-default-ipv6] peer 100::2 enable [RouterA-bgp-default-ipv6] network 1:: 64 [RouterA-bgp-default-ipv6] network 100:: 96 [RouterA-bgp-default-ipv6] quit [RouterA-bgp-default] quit # Configure Router B. <RouterB> system-view [RouterB] bgp 200 [RouterB-bgp-default] router-id 2.2.2.2 [RouterB-bgp-default] peer 100::1 as-number 100 [RouterB-bgp-default] peer 101::1 as-number 200 [RouterB-bgp-default] address-family ipv6...

  • Page 370: 6Pe Configuration Example

    Verifying the configuration # Execute the display bgp routing-table ipv6 command on Router D. [RouterD] 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 371 • PE 1 and PE 2 are edge devices of the ISP, and establish an IPv4 IBGP connection between them. • CE 1 and CE 2 are edge devices of the IPv6 networks, and they connect the IPv6 networks to the ISP.
  • Page 372 # 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 Configure PE 2: # Enable LDP globally, and configure the LSP generation policy. <PE2> system-view [PE2] mpls lsr-id 3.3.3.3 [PE2] mpls ldp [PE2-mpls-ldp] lsp-trigger all [PE2-mpls-ldp] quit...

  • Page 373: Bfd For Ipv6 Bgp Configuration Example

    Verifying the configuration # Display the IPv6 BGP routing tables on PE 1 and PE 2. The output shows that each of them has two IPv6 network routes. The following shows the output on PE 1: [PE1] display bgp routing-table ipv6 Total number of routes: 5 BGP local router ID is 2.2.2.2 Status codes: * - valid, >...
  • Page 374 • Establish two IBGP connections between Router A and Router C. When both paths operate correctly, Router C uses the path Router A<—>Router B<—>Router C to exchange packets with network 1200::0/64. • Configure BFD over the path. When the path fails, BFD can quickly detect the failure and notify it to IPv6 BGP.
  • Page 375 # Apply routing policy apply_med_50 to routes outgoing to peer 3002::2, and apply routing policy apply_med_100 to routes outgoing to peer 2002::2. [RouterA] bgp 200 [RouterA-bgp-default] address-family ipv6 unicast [RouterA-bgp-default-ipv6] peer 3002::2 route-policy apply_med_50 export [RouterA-bgp-default-ipv6] peer 2002::2 route-policy apply_med_100 export [RouterA-bgp-default-ipv6] quit # Enable BFD for peer 3002::2.
  • Page 376 BGP local router ID: 3.3.3.3 Local AS number: 200 Total number of peers: 2 Peers in established state: 2 * - Dynamically created peer Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 2001::1 0 00:04:45 Established 3001::1 0 00:01:53 Established The output shows that Router C has established two BGP connections with Router A, and both connections are in Established state.

  • Page 377: Ipsec For Ipv6 Bgp Packets Configuration Example

    NibID: 0x25000000 LastAs: 0 AttrID: 0x0 Neighbor: 2001::1 Flags: 0x10060 OrigNextHop: 2001::1 Label: NULL RealNextHop: FE80::20C:29FF:FE40:715 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: GigabitEthernet1/1/2 BkTunnel ID: Invalid BkInterface: N/A The output shows that Router C communicates with network 1200::0/64 through the path Router C<—>Router D<—>Router A.
  • Page 378 <RouterC> system-view [RouterC] bgp 65009 [RouterC-bgp-default] router-id 3.3.3.3 [RouterC-bgp-default] group ebgp external [RouterC-bgp-default] peer 3::1 as-number 65008 [RouterC-bgp-default] peer 3::1 group ebgp [RouterC-bgp-default] address-family ipv6 unicast [RouterC-bgp-default-ipv6] peer ebgp enable [RouterC-bgp-default-ipv6] quit [RouterC-bgp-default] quit # Configure Router B. [RouterB-bgp-default] group ebgp external [RouterB-bgp-default] peer 3::2 as-number 65009 [RouterB-bgp-default] peer 3::2 group ebgp [RouterB-bgp-default] address-family ipv6 unicast...
  • Page 379 # Create IPsec profile named policy001, and specify the manual mode for it. [RouterB] ipsec profile policy001 manual # Use IPsec transform set tran1. [RouterB-ipsec-profile-policy001-manual] transform-set tran1 # Set the SPIs of the inbound and outbound SAs to 12345. [RouterB-ipsec-profile-policy001-manual] sa spi outbound esp 12345 [RouterB-ipsec-profile-policy001-manual] sa spi inbound esp 12345 # Set the keys for the inbound and outbound SAs using ESP to abcdefg.
  • Page 380 # Set the keys for the inbound and outbound SAs using ESP to gfedcba. [RouterC-ipsec-profile-policy002-manual] sa string-key outbound esp simple gfedcba [RouterC-ipsec-profile-policy002-manual] sa string-key inbound esp simple gfedcba [RouterC-ipsec-profile-policy002-manual] quit Configure IPsec to protect IPv6 BGP packets between Router A and Router B: # Configure Router A.
  • Page 381 Message statistics: Msg type Last rcvd time/ Current rcvd count/ History rcvd count/ Last sent time Current sent count History sent count Open 18:59:15-2013.4.24 18:59:15-2013.4.24 Update 18:59:16-2013.4.24 Notification - 18:59:15-2013.4.24 Keepalive 18:59:15-2013.4.24 18:59:15-2013.4.24 RouteRefresh - Total Maximum allowed prefix number: 4294967295 Threshold: 75% Minimum time between advertisements is 15 seconds Optional capabilities:...

  • Page 382: Ipv6 Bgp Frr Configuration Example

    Minimum time between advertisements is 30 seconds Optional capabilities: Multi-protocol extended capability has been enabled Route refresh capability has been enabled Peer preferred value: 0 IPsec profile name: policy002 Routing policy configured: No routing policy is configured The output shows that IBGP and EBGP peers are established and both sent and received IPv6 BGP packets are encapsulated by IPsec.
  • Page 383 [RouterA-bgp-default-ipv6] peer 2001::2 enable [RouterA-bgp-default-ipv6] network 1:: 64 [RouterA-bgp-default-ipv6] quit [RouterA-bgp-default] quit # Configure Router B to establish an EBGP session to Router A, and an IBGP session to Router <RouterB> system-view [RouterB] bgp 200 [RouterB] router-id 2.2.2.2 [RouterB-bgp-default] peer 3001::1 as-number 100 [RouterB-bgp-default] peer 3002::2 as-number 200 [RouterB-bgp-default] address-family ipv6 unicast [RouterB-bgp-default-ipv6] peer 3001::1 enable...
  • Page 384 [RouterD-bgp-default-ipv6] peer 3002::1 preferred-value 100 [RouterD-bgp-default-ipv6] quit [RouterD-bgp-default] quit Configure BGP FRR: # On Router A, create routing policy frr to set a backup next hop 2001::2 (Router C) for the route destined for 4::/64. <RouterA> system-view [RouterA] ipv6 prefix-list abc index 10 permit 4:: 64 [RouterA] route-policy frr permit node 10 [RouterA-route-policy] if-match ipv6 address prefix-list abc [RouterA-route-policy] apply ipv6 fast-reroute backup-nexthop 2001::2...

  • Page 385: Ipv6 Multicast Bgp Configuration Example

    AttrID: 0x3 Neighbor: 3001::2 Flags: 0x10060 OrigNextHop: 3001::2 Label: NULL RealNextHop: 3001::2 BkLabel: NULL BkNextHop: 2001::2 Tunnel ID: Invalid Interface: GigabitEthernet1/1/1 BkTunnel ID: Invalid BkInterface: GigabitEthernet1/1/2 FtnIndex: 0x0 # Display detailed information about the route to 1::/64 on Router D. The output shows the backup next hop for the route.
  • Page 386 Figure 87 Network diagram Table 18 Interface and IP address assignment Device Interface IP address Device Interface IP address Source 1002::100/64 Router B GE1/1/1 1001::2/64 Router A GE1/1/1 1002::1/64 GE1/1/2 2002::1/64 GE1/1/2 1001::1/64 GE1/1/3 2001::1/64 Loop0 1:1::1/128 Loop0 1:1::1/128 Loop1 1:1::2/128 Loop1 2:2::2/128...
  • Page 387 # On Router C, enable IPv6 multicast routing globally. <RouterC> system-view [RouterC] ipv6 multicast routing [RouterC-mrib6] quit # Enable IPv6 PIM-SM on interfaces, and enable MLD on GigabitEthernet 1/1/1. [RouterC] interface gigabitethernet 1/1/2 [RouterC-GigabitEthernet1/1/2] ipv6 pim sm [RouterC-GigabitEthernet1/1/2] quit [RouterC] interface gigabitethernet 1/1/3 [RouterC-GigabitEthernet1/1/3] ipv6 pim sm [RouterC-GigabitEthernet1/1/3] quit [RouterC] interface gigabitethernet 1/1/1...
  • Page 388 [RouterA-bgp-default-mul-ipv6] import-route direct [RouterA-bgp-default-mul-ipv6] quit # On Router B, establish an EBGP session to Router A. [RouterB] bgp 200 [RouterB-bgp-default] router-id 2.2.2.2 [RouterB-bgp-default] peer 1001::1 as-number 100 # Enable exchange of IPv6 unicast routes used for RPF check with Router B. [RouterB-bgp-default] address-family ipv6 multicast [RouterB-bgp-default-mul-ipv6] peer 1001::1 enable # Redistribute OSPFv3 routes into BGP.

  • Page 389: Troubleshooting Bgp

    Troubleshooting BGP Symptom The display bgp peer ipv4 unicast or display bgp peer ipv6 unicast command output shows that the state of the connection to a peer cannot become established. Analysis To become BGP peers, any two routers must establish a TCP connection using port 179 and exchange Open messages successfully.

  • Page 390: Configuring Pbr

    Configuring PBR Overview Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify parameters for packets that match specific criteria such as ACLs or that have specific lengths. The parameters include the next hop, output interface, default next hop, and default output interface. A device forwards received packets using the following process: The device uses PBR to forward matching packets.
  • Page 391 • apply next-hop • apply output-interface • apply default-next-hop • apply default-output-interface Table 19 Priorities and meanings of apply clauses Clause Meaning Priority Sets an IP precedence. This clause is always executed. apply precedence Sets the Don't Fragment This clause is always executed. apply ip-df df-value (DF) bit in the IP header.

  • Page 392: Pbr And Track

    Relationship between the match mode and clauses on the node Does a packet match Match mode all the if-match Permit Deny clauses on the node? • If the node is configured with apply clauses, PBR executes the apply clauses on the node. If the PBR-based forwarding succeeds, PBR does not compare the packet with the...

  • Page 393: Configuring A Policy

    Configuring a policy Creating a node Step Command Remarks Enter system view. system-view policy-based-route policy-name Create a node for a policy, and By default, no policy nodes [ deny | permit ] node enter its view. exist. node-number Setting match criteria for a node Step Command Remarks...
  • Page 394 Step Command Remarks By default, no VPN instance is specified. You can specify a maximum of n VPN Set VPN apply access-vpn vpn-instance instances for a node. The matching instances. vpn-instance-name&<1-n> packets are forwarded according to the forwarding table of the first available VPN instance.

  • Page 395: Configuring Pbr

    Step Command Remarks By default, no default output interface is specified. You can specify multiple default output interfaces for backup or load 13. Set default apply default-output-interface sharing in one command line or by output { interface-type interface-number [ track executing this command multiple interfaces.

  • Page 396: Displaying And Maintaining Pbr

    You can apply a policy to multiple interfaces. To configure interface PBR: Step Command Remarks Enter system system-view view. Enter interface interface interface-type interface-number view. Apply a policy By default, no policy is applied to the ip policy-based-route policy-name to the interface. interface.

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

    Configuration procedure Configure Router A: # Configure the IP addresses of GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2. <RouterA> system-view [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ip address 1.1.2.1 24 [RouterA-GigabitEthernet1/1/1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] ip address 1.1.3.1 24 [RouterA-GigabitEthernet1/1/2] quit # Configure ACL 3101 to match TCP packets.
  • Page 398 Figure 89 Network diagram Router B Router C GE1/1/2 GE1/1/3 1.1.2.2/24 1.1.3.2/24 GE1/1/2 GE1/1/3 1.1.2.1/24 1.1.3.1/24 Router A GE1/1/1 10.110.0.10/24 Subnet 10.110.0.0/24 Host A Host B 10.110.0.20/24 Gateway: 10.110.0.10 Configuration procedure Make sure Router B and Router C can reach Host A. (Details not shown.) Configure Router A: # Configure the IP addresses of GigabitEthernet 1/1/2 and GigabitEthernet 1/1/3.

  • Page 399: Packet Length-Based Interface Pbr Configuration Example

    Verifying the configuration # On Host A, Telnet to Router B that is directly connected to Router A. The operation succeeds. (Details not shown.) # On Host A, Telnet to Router C that is directly connected to Router A. The operation fails. (Details not shown.) # Ping Router C from Host A.
  • Page 400 # Configure Node 10 for the policy lab1 to forward packets with a length of 64 to 300 bytes to the next hop 150.1.1.2. [RouterA] policy-based-route lab1 permit node 10 [RouterA-pbr-lab1-10] if-match packet-length 64 300 [RouterA-pbr-lab1-10] apply next-hop 150.1.1.2 [RouterA-pbr-lab1-10] quit # Configure Node 20 for the policy lab1 to forward packets with a length of 301 to 1000 bytes to the next hop 151.1.1.2.

  • Page 401: Packet Source-Ip-Based Interface Pbr Configuration Example

    Ping statistics for 10.1.1.1: Packets: Sent = 1, Received = 1, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms The debugging information about PBR displayed on Router A is as follows: <RouterA>...
  • Page 402 Figure 91 Network diagram Configuration procedure Make sure Router B can reach Host A and Host B, and Router C can reach Host A and Host B. (Details not shown.) Configure Router A: # Configure the IP addresses of GigabitEthernet 1/1/2 and GigabitEthernet 1/1/3. <RouterA>...
  • Page 403 [RouterA-GigabitEthernet1/1/1] ip address 192.168.10.1 24 [RouterA-GigabitEthernet1/1/1] ip policy-based-route aaa [RouterA-GigabitEthernet1/1/1] quit Verifying the configuration # Configure IP address 192.168.10.3/24 for Host B, and specify its gateway address as 192.168.10.1. (Details not shown.) # Ping Router B from Host A. The operation succeeds. (Details not shown.) # Ping Router B from Host B.

  • Page 404: 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 405: Bidirectional Control Mode

    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 406: Displaying And Maintaining Ipv6 Static Routes

    Step Command Remarks By default, the source address of echo packets is not configured. The source address of echo Configure the packets must be a global source address of bfd echo-source-ipv6 ipv6-address unicast address. echo packets. For more information about this command, see High Availability Command Reference.
  • Page 407 Figure 92 Network diagram Host B 2::2/64 GE1/1/3 2::1/64 GE1/1/1 GE1/1/2 4::2/64 5::2/64 Router B GE1/1/2 GE1/1/2 4::1/64 5::1/64 GE1/1/1 GE1/1/1 1::1/64 3::1/64 Router C Host C Router A Host A 3::2/64 1::2/64 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure IPv6 static routes: # Configure the default IPv6 route on Router A.

  • Page 408: 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 : GE1/1/1 Cost Destination: 3::/64 Protocol : Static NextHop : 5::1 Preference: 60 Interface : GE1/1/2 Cost Static Routing table Status : <Inactive>...
  • Page 409 Figure 93 Network diagram Table 20 Interface and IP address assignment Device Interface IPv6 address Router A GE1/1/1 12::1/64 Router A GE1/1/2 10::102/64 Router B GE1/1/1 12::2/64 Router B GE1/1/2 13::1/64 Router C GE1/1/1 10::100/64 Router C GE1/1/2 13::2/64 Configuration procedure Configure IPv6 addresses for interfaces.
  • Page 410 <RouterC> system-view [RouterC] ipv6 route-static 120:: 64 13::1 [RouterC] ipv6 route-static 121:: 64 10::102 Verifying the configuration # Display BFD sessions on Router A. <RouterA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode: Local Discr: 513 Remote Discr: 33 Source IP: 12::1...

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

    The output shows that Router A communicates with Router B through GigabitEthernet 1/1/2. BFD for IPv6 static routes configuration example (indirect next hop) Network requirements As shown in Figure • Router A has a route to interface Loopback 1 (2::9/128) on Router B, and the output interface is GigabitEthernet 1/1/1.
  • Page 412 Device Interface IPv6 address Router D GE1/1/1 12::2/64 Router D GE1/1/2 11::1/64 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure IPv6 static routes and BFD: # Configure IPv6 static routes on Router A and enable BFD control packet mode for the IPv6 static route that traverses Router D.
  • Page 413 Destination IP: 2::9 Session State: Up Interface: N/A Hold Time: 2012ms The output shows that the BFD session has been created. # Display IPv6 static routes on Router A. <RouterA> display ipv6 routing-table protocol static Summary Count : 1 Static Routing table Status : <Active> Summary Count : 1 Destination: 120::/64 Protocol...

  • Page 414: 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 415: 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 416: 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 417: Configuring Ripng Route Control

    Step Command Remarks By default, RIPng is disabled. Enable RIPng on the If RIPng is not enabled on an ripng process-id enable interface. interface, the interface does not send or receive any RIPng route. Configuring RIPng route control Before you configure RIPng, complete the following tasks: •...

  • Page 418: Advertising A Default Route

    Step Command Remarks Enter interface view. interface interface-type interface-number By default, the Advertise a summary IPv6 ripng summary-address ipv6-address summary IPv6 prefix prefix. prefix-length is not configured. Advertising a default route You can configure RIPng to advertise a default route with the specified cost to its neighbors. To configure RIPng to advertise a default route: Step Command...

  • Page 419: Configuring Ripng Route Redistribution

    Step Command Remarks Enter system view. system-view ripng [ process-id ] Enter RIPng view. [ vpn-instance vpn-instance-name ] preference { preference | By default, the preference of Set a preference for RIPng. route-policy route-policy-name } RIPng is 100. Configuring RIPng route redistribution Step Command Remarks...

  • Page 420: Configuring Split Horizon And Poison Reverse

    Step Command Remarks By default: timers { garbage-collect • The update timer is 30 seconds. garbage-collect-value | • The timeout timer is 180 seconds. Set RIPng timers. suppress suppress-value | • The suppress timer is 120 seconds. timeout timeout-value | update •...

  • Page 421: Setting The Maximum Number Of Ecmp Routes

    Step Command Remarks ripng [ process-id ] Enter RIPng view. [ vpn-instance vpn-instance-name ] By default, zero field check is Enable the zero field check enabled for incoming RIPng checkzero on incoming RIPng packets. packets. Setting the maximum number of ECMP routes Step Command Remarks...

  • Page 422: Configuring Ripng Gr

    You can use the timer triggered command to set the maximum interval, minimum interval, and incremental interval for sending RIPng triggered updates. For a stable network, the minimum interval is used. If network changes become frequent, the triggered update sending interval is incremented by the incremental interval × 2 for each triggered update until the maximum interval is reached.

  • Page 423: Configuring Ripng Nsr

    Step Command Remarks (Optional.) Set the GR By default, the GR interval is 60 graceful-restart interval interval interval. seconds. Configuring RIPng NSR Nonstop routing (NSR) backs up RIPng routing information from the active process to the standby process. After an active/standby switchover, NSR can complete route regeneration without tearing down adjacencies or impacting forwarding services.

  • Page 424: Configuration Restrictions And Guidelines

    Configuration restrictions and guidelines • RIPng FRR is available only when the state of the primary link (with Layer 3 interfaces staying up) changes from bidirectional to unidirectional or down. • RIPng FRR is only effective for RIPng routes that are learned from directly connected neighbors.

  • Page 425: Displaying And Maintaining Ripng

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Apply an IPsec profile to the By default, no IPsec profile is ripng ipsec-profile profile-name interface. applied. Displaying and maintaining RIPng Execute display commands in any view and reset commands in user view. Task Command Display configuration information for a...
  • Page 426 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic RIPng: # Configure Router A. <RouterA> system-view [RouterA] ripng 1 [RouterA-ripng-1] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ripng 1 enable [RouterA-GigabitEthernet1/1/1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] ripng 1 enable [RouterA-GigabitEthernet1/1/2] quit # Configure Router B.
  • Page 427 Destination 5::/64, via FE80::20F:E2FF:FE00:100, cost 1, tag 0, AOF, 11 secs Local route Destination 1::/64, via ::, cost 0, tag 0, DOF Destination 3::/64, via ::, cost 0, tag 0, DOF # Display the RIPng routing table on Router A. [RouterA] display ripng 1 route Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D –...

  • Page 428: Ripng Route Redistribution Configuration Example

    Destination 1::/64, via ::, cost 0, tag 0, DOF Destination 3::/64, via ::, cost 0, tag 0, DOF [RouterA] display ripng 1 route Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D – Direct O - Optimal, F - Flush to RIB ---------------------------------------------------------------- Peer FE80::2:1 on GigabitEthernet1/1/1 Destination 4::/64,...
  • Page 429 [RouterB] ripng 200 [RouterB-ripng-200] quit [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] ripng 200 enable # Enable RIPng 200 on Router C. <RouterC> system-view [RouterC] ripng 200 [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] ripng 200 enable [RouterC-GigabitEthernet1/1/1] quit [RouterC] interface gigabitethernet 1/1/2 [RouterC-GigabitEthernet1/1/2] ripng 200 enable [RouterC-GigabitEthernet1/1/2] quit # Display the routing table on Router A.

  • Page 430: Ripng Gr Configuration Example

    [RouterB-ripng-100] import-route ripng 200 [RouterB-ripng-100] quit [RouterB] ripng 200 [RouterB-ripng-200] import-route ripng 100 [RouterB-ripng-200] quit # Display the routing table on Router A. [RouterA] display ipv6 routing-table Destinations : 8 Routes : 8 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0...

  • Page 431: Ripng Nsr Configuration Example

    Configure Router A as the GR restarter. Configure Router B and Router C as the GR helpers to synchronize their routing tables with Router A by using GR. Figure 98 Network diagram Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure RIPng on the routers to ensure the following: (Details not shown.) Router A, Router B, and Router C can communicate with each other at Layer 3.
  • Page 432 Figure 99 Network diagram Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure RIPng on the routers to ensure the following: (Details not shown.) Router S, Router A, and Router B can communicate with each other at Layer 3. Dynamic route update can be implemented among them with RIPng.

  • Page 433: Configuring Ripng Frr

    Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D - Direct O - Optimal, F - Flush to RIB ---------------------------------------------------------------- Peer FE80::AE45:5CE7:422E:2867 on GigabitEthernet1/1/1 Destination 1400:1::/64, via FE80::AE45:5CE7:422E:2867, cost 1, tag 0, AOF, 1 secs Destination 4004::4/128, via FE80::AE45:5CE7:422E:2867, cost 2, tag 0, AOF, 1 secs Local route Destination 2002::2/128,...
  • Page 434 Figure 100 Network diagram Router C Link B Link A Loop0 Loop0 GE1/1/2 GE1/1/2 Router B Router A Table 22 Interface and IP address assignment Device Interface IP address Router A GigabitEthernet 1/1/1 1::1/64 Router A GigabitEthernet 1/1/2 2::1/64 Router A Loopback 0 10::1/128 Router B...
  • Page 435 [RouterB] ripng 1 [RouterB-ripng-1] fast-reroute route-policy frr [RouterB-ripng-1] quit Verifying the configuration # Display the route 20::1/128 on Router A to view the backup next hop information. [RouterA] display ipv6 routing-table 20::1 128 verbose Summary count : 1 Destination: 20::1/128 Protocol: RIPng Process ID: 1 SubProtID: 0x0...

  • Page 436: Ripng Ipsec Profile Configuration Example

    FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A RIPng IPsec profile configuration example Network requirements As shown in Figure 101, configure RIPng on the routers, and configure IPsec profiles on the routers to authenticate and encrypt protocol packets. Figure 101 Network diagram Configuration procedure Configure IPv6 addresses for interfaces.
  • Page 437 [RouterA-ipsec-transform-set-protrf1] esp encryption-algorithm 3des-cbc [RouterA-ipsec-transform-set-protrf1] esp authentication-algorithm md5 # Specify the encapsulation mode as transport. [RouterA-ipsec-transform-set-protrf1] encapsulation-mode transport [RouterA-ipsec-transform-set-protrf1] quit # Create a manual IPsec profile named profile001. [RouterA] ipsec profile profile001 manual # Reference IPsec transform set protrf1. [RouterA-ipsec-profile-profile001-manual] transform-set protrf1 # Configure the inbound and outbound SPIs for ESP.
  • Page 438 # Reference IPsec transform set protrf1. [RouterC-ipsec-profile-profile001-manual] transform-set protrf1 # Configure the inbound and outbound SPIs for ESP. [RouterC-ipsec-profile-profile001-manual] sa spi inbound esp 256 [RouterC-ipsec-profile-profile001-manual] sa spi outbound esp 256 # Configure the inbound and outbound SA keys for ESP. [RouterC-ipsec-profile-profile001-manual] sa string-key inbound esp simple abc [RouterC-ipsec-profile-profile001-manual] sa string-key outbound esp simple abc [RouterC-ipsec-profile-profile001-manual] quit...

  • Page 439: Configuring Ospfv3

    Configuring OSPFv3 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." Overview OSPFv3 and OSPFv2 have the following in common: • 32-bit router ID and area ID. •...

  • Page 440: 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 441: Enabling Ospfv3

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

  • Page 442: Configuring Ospfv3 Area Parameters

    Step Command Remarks interface interface-type Enter interface view. interface-number Enable an OSPFv3 process By default, no OSPFv3 processes ospfv3 process-id area area-id on the interface. [ instance instance-id ] are enabled on an interface. 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 443: Configuring An Nssa Area

    Configuring an NSSA area To configure an NSSA area, configure the nssa command on all the routers attached to the area. 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...

  • Page 444: Configuring Ospfv3 Network Types

    Configuring OSPFv3 network types OSPFv3 classifies networks into the following types by the link layer protocol: • 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 Frame Relay or X.25, OSPFv3 considers the network type as NBMA by default.

  • Page 445: Configuring Ospfv3 Route Control

    Configuring OSPFv3 route control Configuration prerequisites Before you configure OSPFv3 route control, perform 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 446: 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-value | not configured on an ASBR. ASBR. not-advertise | nssa-only | tag tag ] * Configuring OSPFv3 received route filtering Step Command Remarks Enter system view.

  • Page 447: Setting The Maximum Number Of Ospfv3 Ecmp Routes

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, the OSPFv3 cost is 1 for a VLAN interface, is 0 for a loopback Set an OSPFv3 cost for the interface. The OSPFv3 cost is ospfv3 cost cost-value interface. [ instance instance-id ] automatically computed according to the interface bandwidth for other...

  • Page 448: Configuring Ospfv3 Route Redistribution

    Configuring OSPFv3 route redistribution Because OSPFv3 is a link state routing protocol, it cannot directly filter LSAs to be advertised. OSPFv3 filters only redistributed routes. Only routes that are not filtered out can be advertised in LSAs. Executing the import-route or default-route-advertise command on a router makes it become an ASBR.

  • Page 449: Tuning And Optimizing Ospfv3 Networks

    To set a tag for redistributed routes: Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * Set a tag for redistributed By default, the tag of default tag tag routes. redistributed routes is 1. Tuning and optimizing OSPFv3 networks This section describes configurations of OSPFv3 timers, interface DR priority, and the logging of neighbor state changes.

  • Page 450: Setting Spf Calculation Interval

    To set the LSA transmission delay on an interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Set the LSA transmission By default, the LSA transmission ospfv3 trans-delay seconds delay. [ instance instance-id ] delay is 1 second. Setting SPF calculation interval LSDB changes result in SPF calculations.

  • Page 451: Setting A Dr Priority For An Interface

    Setting a DR priority for an interface The router priority is used for DR election. Interfaces having the priority 0 cannot become a DR or BDR. To configure a DR priority for an interface: Step Command Remarks Enter system view. system-view Enter interface view.

  • Page 452: Enabling The Logging Of Neighbor State Changes

    Step Command Remarks By default, the interfaces are able to receive and send OSPFv3 packets. This command disables only the Disable interfaces from silent-interface { interface-type interfaces associated with the receiving and sending interface-number | all } current process. However, OSPFv3 packets.

  • Page 453: Setting The Lsu Transmit Rate

    Step Command Remarks By default, MIB is bound to the Bind MIB to an OSPFv3 process with the smallest ospfv3 mib-binding process-id process. process ID. snmp-agent trap enable ospfv3 [ grrestarter-status-change | grhelper-status-change | if-state-change | if-cfg-error | Enable SNMP notifications if-bad-pkt | neighbor-state-change | By default, SNMP notifications for OSPFv3.

  • Page 454: Configuring Prefix Suppression

    • Use the OSPFv3 max-metric router LSA feature. This feature enables OSPFv3 to advertise its locally generated Type-1 LSAs with a maximum cost of 65535. Neighbors do not send packets to the stub router as long as they have a route with a smaller cost. To configure a router as a stub router: Step Command...

  • Page 455: Setting The Maximum Number Of Ospfv3 Logs

    Configuring prefix suppression for an interface Step Command Remarks Enter system view. system-view Enter interface interface interface-type interface-number view. Enable prefix ospfv3 prefix-suppression [ disable ] By default, prefix suppression suppression for the [ instance instance-id ] is disabled for an interface. interface.

  • Page 456: Configuring Gr Helper

    To configure GR restarter: Step Command Remarks Enter system view. system-view ospfv3 [ process-id | Enter OSPFv3 view. vpn-instance vpn-instance-name ] * graceful-restart enable [ global By default, OSPFv3 GR restarter Enable the GR capability. | planned-only ] * capability is disabled. (Optional.) Set the GR By default, the GR interval is 120 graceful-restart interval interval...

  • Page 457: 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 ] * By default, OSPFv3 NSR is disabled. This command takes effect only for the Enable OSPFv3 non-stop-routing current process. As a best practice, NSR.

  • Page 458: Configuration Prerequisites

    Figure 102 Network diagram for OSPFv3 FRR As shown in Figure 102, configure FRR on Router B. OSPFv3 FRR automatically calculates a backup next hop or specifies a backup next hop by using a routing policy. When the primary link fails, OSPFv3 directs packets to the backup next hop.
  • Page 459 Configuring OSPFv3 FRR to specify a backup next hop using a routing policy Before you perform this task, use the apply ipv6 fast-reroute backup-interface command to specify a backup next hop in the routing policy to be used. For more information about the apply ipv6 fast-reroute backup-interface command and routing policy configuration, see "Configuring routing policies."...

  • Page 460: Applying An Ipsec Profile

    Step Command Remarks Enable BFD echo packet By default, BFD echo packet mode ospfv3 primary-path-detect bfd mode for OSPFv3 FRR. echo [ instance instance-id ] for OSPFv3 FRR is disabled. Applying an IPsec profile To protect routing information and prevent attacks, OSPFv3 can authenticate protocol packets by using an IPsec profile.

  • Page 461: Displaying And Maintaining Ospfv3

    To apply an IPsec profile to a virtual link: Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view. vpn-instance-name ] * Enter OSPFv3 area view. area area-id vlink-peer router-id [ dead seconds | Apply an IPsec profile to a hello seconds | instance instance-id | By default, no IPsec profile is virtual link.

  • Page 462: Ospfv3 Configuration Examples

    Task Command Display OSPFv3 next hop display ospfv3 [ process-id ] nexthop information. Display OSPFv3 neighbor display ospfv3 [ process-id ] [ area area-id ] peer [ [ interface-type information. interface-number ] [ verbose ] | peer-router-id | statistics ] Display OSPFv3 request list display ospfv3 [ process-id ] [ area area-id ] request-queue information.
  • Page 463 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic OSPFv3: # On Router A, enable OSPFv3 and specify the router ID as 1.1.1.1. <RouterA> system-view [RouterA] ospfv3 1 [RouterA-ospfv3-1] router-id 1.1.1.1 [RouterA-ospfv3-1] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ospfv3 1 area 1 [RouterA-GigabitEthernet1/1/1] quit [RouterA] interface gigabitethernet 1/1/2...
  • Page 464 Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID Pri State Dead-Time InstID Interface 3.3.3.3 Full/BDR 00:00:40 GE1/1/1 Area: 0.0.0.1 ------------------------------------------------------------------------- Router ID Pri State Dead-Time InstID Interface 1.1.1.1 Full/DR 00:00:40 GE1/1/2 # Display OSPFv3 neighbors on Router C. [RouterC] display ospfv3 peer OSPFv3 Process 1 with Router ID 3.3.3.3 Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID...
  • Page 465 AdvRouter : 4.4.4.4 Area : 0.0.0.2 Preference : 10 *Destination: 2001:3::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: GE1/1/2 AdvRouter : 3.3.3.3 Area : 0.0.0.2 Preference : 10 Total: 4 Intra area: 1 Inter area: 3 ASE: 0 NSSA: 0 Configure Area 2 as a stub area: # Configure Router D.

  • Page 466: Default Route

    Preference : 10 *Destination: 2001:2::/64 Type Cost Nexthop : :: Interface: GE1/1/2 AdvRouter : 4.4.4.4 Area : 0.0.0.2 Preference : 10 *Destination: 2001:3::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: GE1/1/2 AdvRouter : 3.3.3.3 Area : 0.0.0.2 Preference : 10 Total: 5 Intra area: 1 Inter area: 4...

  • Page 467: Ospfv3 Nssa Area Configuration Example

    OSPFv3 NSSA area configuration example Network requirements As shown in Figure 104: • Configure OSPFv3 on all routers and split the AS into three areas. • Configure Router B and Router C as ABRs to forward routing information between areas. •...
  • Page 468 *Destination: 2001::/64 Type : IA Cost NextHop : FE80::20C:29FF:FE74:59C6 Interface: GE1/1/1 AdvRouter : 2.2.2.2 Area : 0.0.0.1 Preference : 10 *Destination: 2001:1::/64 Type Cost Nexthop : :: Interface: GE1/1/1 AdvRouter : 1.1.1.1 Area : 0.0.0.1 Preference : 10 *Destination: 2001:2::/64 Type : IA Cost...

  • Page 469: Ospfv3 Dr Election Configuration Example

    *Destination: 2001:2::/64 Type Cost NextHop : :: Interface: GE1/1/2 AdvRouter : 4.4.4.4 Area : 0.0.0.2 Preference : 10 *Destination: 1234::/64 Type : E2 Cost NextHop : FE80::20C:29FF:FEB9:F2EF Interface: GE1/1/2 AdvRouter : 2.2.2.2 Area : 0.0.0.2 Preference : 10 Total: 4 Intra area: 1 Inter area: 2 ASE: 1...
  • Page 470 [RouterA-ospfv3-1] router-id 1.1.1.1 [RouterA-ospfv3-1] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ospfv3 1 area 0 [RouterA-GigabitEthernet1/1/1] quit # On Router B, enable OSPFv3, and specify the router ID as 2.2.2.2. <RouterB> system-view [RouterB] ospfv3 [RouterB-ospfv3-1] router-id 2.2.2.2 [RouterB-ospfv3-1] quit [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] ospfv3 1 area 0 [RouterB-GigabitEthernet1/1/1] quit # On Router C, enable OSPFv3, and specify the router ID as 3.3.3.3.
  • Page 471 Router ID Pri State Dead-Time InstID Interface 1.1.1.1 100 Full/DROther 00:00:30 GE1/1/1 2.2.2.2 Full/DROther 00:00:37 GE1/1/1 3.3.3.3 Full/BDR 00:00:31 GE1/1/1 Configure router priorities for interfaces: # Set the router priority to 100 for the interface GigabitEthernet 1/1/1 of Router A. [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ospfv3 dr-priority 100 [RouterA-GigabitEthernet1/1/1] quit...

  • Page 472: Ospfv3 Route Redistribution Configuration Example

    Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID Pri State Dead-Time InstID Interface 2.2.2.2 Full/DROther 00:00:36 GE1/1/1 3.3.3.3 Full/BDR 00:00:35 GE1/1/1 4.4.4.4 Full/DROther 00:00:33 GE1/1/1 # Display neighbors on Router D. [RouterD] display ospfv3 peer OSPFv3 Process 1 with Router ID 4.4.4.4 Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID Pri State...
  • Page 473 [RouterA] ospfv3 1 [RouterA-ospfv3-1] router-id 1.1.1.1 [RouterA-ospfv3-1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] ospfv3 1 area 2 [RouterA-GigabitEthernet1/1/2] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ospfv3 1 area 2 [RouterA-GigabitEthernet1/1/1] quit # Enable OSPFv3 process 1 and OSPFv3 process 2 on Router B. <RouterB>...
  • Page 474 NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 4::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : GE1/1/1 Cost Destination: 4::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: FE80::/10 Protocol : Direct NextHop : ::...

  • Page 475: Ospfv3 Route Summarization Configuration Example

    NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 4::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : GE1/1/1 Cost Destination: 4::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: FE80::/10 Protocol : Direct NextHop : ::...
  • Page 476 # Enable OSPFv3 process 1 on Router A. <RouterA> system-view [RouterA] ospfv3 1 [RouterA-ospfv3-1] router-id 1.1.1.1 [RouterA-ospfv3-1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] ospfv3 1 area 2 [RouterA-GigabitEthernet1/1/2] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ipv6 address 2:1:1::1 64 [RouterA-GigabitEthernet1/1/1] ipv6 address 2:1:2::1 64 [RouterA-GigabitEthernet1/1/1] ipv6 address 2:1:3::1 64 [RouterA-GigabitEthernet1/1/1] ospfv3 1 area 2 [RouterA-GigabitEthernet1/1/1] quit...
  • Page 477 Destinations : 12 Routes : 12 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64 Protocol : O_ASE2 NextHop : FE80::200:CFF:FE01:1C03 Preference: 150 Interface : GE1/1/2 Cost Destination: 2::/64 Protocol : O_ASE2 NextHop : FE80::200:CFF:FE01:1C03 Preference: 150 Interface...
  • Page 478 NextHop : :: Preference: 0 Interface : NULL0 Configure ASBR route summarization: # On Router B, configure OSPFv3 process 2 to advertise a summary route 2::/16. [RouterB] ospfv3 2 [RouterB-ospfv3-2] asbr-summary 2:: 16 [RouterB-ospfv3-2] quit # Display the routing table on Router C. [RouterC] display ipv6 routing-table Destinations : 9 Routes : 9 Destination: ::1/128...

  • Page 479: Ospfv3 Gr Configuration Example

    OSPFv3 GR configuration example Network requirements As shown in Figure 108: • Router A, Router B, and Router C that reside in the same AS and the same OSPFv3 routing domain are GR capable. • Router A acts as the GR restarter. Router B and Router C act as GR helpers, and synchronize their LSDBs with Router A through GR.

  • Page 480: Ospfv3 Nsr Configuration Example

    [RouterC] ospfv3 1 [RouterC-ospfv3-1] router-id 3.3.3.3 [RouterC-ospfv3-1] quit [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] ospfv3 1 area 1 [RouterC-GigabitEthernet1/1/1] quit Verifying the configuration # Perform an active/standby switchover on Router A to trigger an OSPFv3 GR operation. (Details not shown.) OSPFv3 NSR configuration example Network requirements As shown in Figure...

  • Page 481: Bfd For Ospfv3 Configuration Example

    [RouterS-ospfv3-1] router-id 3.3.3.3 [RouterS-ospfv3-1] non-stop-routing [RouterS-ospfv3-1] quit [RouterS] interface gigabitethernet 1/1/1 [RouterS-GigabitEthernet1/1/1] ospfv3 1 area 1 [RouterS-GigabitEthernet1/1/1] quit [RouterS] interface gigabitethernet 1/1/2 [RouterS-GigabitEthernet1/1/2] ospfv3 1 area 1 [RouterS-GigabitEthernet1/1/2] quit Verifying the configuration # Verify the following: • When an active/standby switchover occurs on Router S, the neighbor relationships and routing information on Router A and Router B have not changed.
  • Page 482 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic OSPFv3: # Enable OSPFv3 and set the router ID to 1.1.1.1 on Router A. <RouterA> system-view [RouterA] ospfv3 1 [RouterA-ospfv3-1] router-id 1.1.1.1 [RouterA-ospfv3-1] quit [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ospfv3 1 area 0 [RouterA-GigabitEthernet1/1/1] quit [RouterA] interface gigabitethernet 1/1/2...

  • Page 483: Ospfv3 Frr Configuration Example

    [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] ospfv3 bfd enable [RouterB-GigabitEthernet1/1/1] bfd min-transmit-interval 500 [RouterB-GigabitEthernet1/1/1] bfd min-receive-interval 500 [RouterB-GigabitEthernet1/1/1] bfd detect-multiplier 6 Verifying the configuration # Display the BFD information on Router A. <RouterA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode: Local Discr: 1441...
  • Page 484 Figure 111 Network diagram Router C Link B Link A Loop0 Loop0 GE1/1/2 GE1/1/2 Router B Router A Table 24 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A GE1/1/1 1::1/64 Router B GE1/1/1 3::1/64 GE1/1/2 2::1/64...
  • Page 485 [RouterA] ospfv3 1 [RouterA-ospfv3-1] fast-reroute route-policy frr [RouterA-ospfv3-1] quit # Configure Router B. <RouterB> system-view [RouterB] ipv6 prefix-list abc index 10 permit 20:: 128 [RouterB] route-policy frr permit node 10 [RouterB-route-policy-frr-10] if-match ipv6 address prefix-list abc [RouterB-route-policy-frr-10] apply ipv6 fast-reroute backup-interface gigabitethernet 1/1/1 backup-nexthop 3::2 [RouterB-route-policy-frr-10] quit [RouterB] ospfv3 1...

  • Page 486: Ospfv3 Ipsec Profile Configuration Example

    IpPre: N/A QosLocalID: N/A Tag: 0 State: Active Adv OrigTblID: 0x0 OrigVrf: default-vrf TableID: 0xa OrigAs: 0 NibID: 0x23000006 LastAs: 0 AttrID: 0xffffffff Neighbor: :: Flags: 0x10041 OrigNextHop: FE80::34CC:E8FF:FE5B:C02 Label: NULL RealNextHop: FE80::34CC:E8FF:FE5B:C02 BkLabel: NULL BkNextHop: FE80::7685:45FF:FEAD:102 Tunnel ID: Invalid Interface: GigabitEthernet1/1/2 BkTunnel ID: Invalid BkInterface: GigabitEthernet1/1/1...
  • Page 487 [RouterB-ospfv3-1] quit [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] ospfv3 1 area 0 [RouterB-GigabitEthernet1/1/1] quit [RouterB] interface gigabitethernet 1/1/2 [RouterB-GigabitEthernet1/1/2] ospfv3 1 area 1 [RouterB-GigabitEthernet1/1/2] quit # On Router C, enable OSPFv3 and specify the router ID as 3.3.3.3. <RouterC> system-view [RouterC] ospfv3 1 [RouterC-ospfv3-1] router-id 3.3.3.3 [RouterC-ospfv3-1] quit [RouterC] interface gigabitethernet 1/1/1...
  • Page 488 # Specify the encapsulation mode as transport. [RouterB-ipsec-transform-set-trans] encapsulation-mode transport # Specify the ESP encryption and authentication algorithms. [RouterB-ipsec-transform-set-trans] esp encryption-algorithm 3des-cbc [RouterB-ipsec-transform-set-trans] esp authentication-algorithm md5 # Specify the AH authentication algorithm. [RouterB-ipsec-transform-set-trans] ah authentication-algorithm md5 [RouterB-ipsec-transform-set-trans] quit # Create a manual IPsec profile named profile001. [RouterB] ipsec profile profile001 manual # Use IPsec transform set trans.
  • Page 489 [RouterC-ipsec-transform-set-trans] encapsulation-mode transport # Specify the ESP encryption and authentication algorithms. [RouterC-ipsec-transform-set-trans] esp encryption-algorithm 3des-cbc [RouterC-ipsec-transform-set-trans] esp authentication-algorithm md5 # Specify the AH authentication algorithm. [RouterC-ipsec-transform-set-trans] ah authentication-algorithm md5 [RouterC-ipsec-transform-set-trans] quit # Create a manual IPsec profile named profile002. [RouterC] ipsec profile profile002 manual # Use IPsec transform set trans.
  • Page 490 Verifying the configuration # Verify that OSPFv3 packets between Routers A, B, and C are protected by IPsec. (Details not shown.)

  • Page 491: 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 492: Configuring Ipv6 Is-Is Route Control

    Configuring IPv6 IS-IS route control Before you configure IPv6 IS-IS route control, complete basic IPv6 IS-IS configuration. 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 ] Enter IS-IS IPv6 address address-family ipv6 [ unicast ] family view.

  • Page 493: Configuring Ipv6 Is-Is Link Cost

    Configuring IPv6 IS-IS link cost Configuring an IPv6 IS-IS cost for an interface Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] cost-style { narrow | wide | Specify an IS-IS cost By default, the IS-IS cost wide-compatible | { compatible | style.

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

    Step Command Remarks By default, IPv6 IS-IS MTR is Enable IPv6 IS-IS MTR. multi-topology [ compatible ] disabled. Enable automatic IPv6 By default, automatic IPv6 IS-IS auto-cost enable IS-IS cost calculation. cost calculation is disabled. (Optional.) Configure a bandwidth reference The default setting is 100 Mbps.

  • Page 495: Setting The Lsdb Overload Bit

    Setting the LSDB overload bit Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] cost-style { wide | By default, the IS-IS cost style is Specify an IS-IS cost style. wide-compatible | compatible } narrow.

  • Page 496: Enabling Ipv6 Is-Is Ispf

    Step Command Remarks By default: • The maximum interval is 5 seconds. timer spf maximum-interval Set the SPF calculation [ minimum-interval • The minimum interval is interval. [ incremental-interval ] ] 50 milliseconds. • The incremental interval is 200 milliseconds. Enabling IPv6 IS-IS ISPF Step Command...

  • Page 497: Configuring Ipv6 Is-Is Frr

    Step Command Remarks Enable an IS-IS process and isis [ process-id ] [ vpn-instance enter IS-IS view. vpn-instance-name ] Configure the NET for the By default, no NET is configured. network-entity net IS-IS process. Enter IPv6 address family address-family ipv6 [ unicast ] view.

  • Page 498: Configuration Procedure

    Configuration procedure Configuring IPv6 IS-IS FRR to calculate a backup next hop through LFA calculation Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the interface (Optional.) Disable LFA participates in LFA calculation isis ipv6 fast-reroute lfa-backup calculation on the interface.

  • Page 499: Enabling Ipv6 Is-Is Mtr

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, BFD control packet Enable BFD control packet isis ipv6 primary-path-detect bfd mode for IPv6 IS-IS FRR is mode for IPv6 IS-IS FRR. ctrl disabled. To enable BFD echo packet mode for IPv6 IS-IS FRR: Step Command Remarks...

  • Page 500: Displaying And Maintaining Ipv6 Is-Is

    As shown in Figure 114, the numbers refer to the link costs. Router A, Router B, and Router D support both IPv4 and IPv6. Router C supports only IPv4 and cannot forward IPv6 packets. Enable IPv6 IS-IS MTR on Router A, Router B, Router C, and Router D to make them perform route calculation separately in IPv4 and IPv6 topologies.
  • Page 501 Router A and Router B are Level-1 routers, Router D is a Level-2 router, and Router C is a Level-1-2 router. Figure 115 Network diagram Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure IPv6 IS-IS: # Configure Router A. <RouterA>...
  • Page 502 [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] isis ipv6 enable 1 [RouterC-GigabitEthernet1/1/1] quit [RouterC] interface gigabitethernet 1/1/2 [RouterC-GigabitEthernet1/1/2] isis ipv6 enable 1 [RouterC-GigabitEthernet1/1/2] quit [RouterC] interface gigabitethernet 1/1/3 [RouterC-GigabitEthernet1/1/3] isis ipv6 enable 1 [RouterC-GigabitEthernet1/1/3] quit # Configure Router D. <RouterD> system-view [RouterD] isis 1 [RouterD-isis-1] is-level level-2 [RouterD-isis-1] network-entity 20.0000.0000.0004.00 [RouterD-isis-1] address-family ipv6...
  • Page 503 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set # Display the IPv6 IS-IS routing table on Router B. [RouterB] display isis route ipv6 Route information for IS-IS(1) ------------------------------ Level-1 IPv6 Forwarding Table ----------------------------- Destination : :: PrefixLen: 0 Flag : R/-/- Cost...
  • Page 504 Next Hop : Direct Interface: GE1/1/3 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv6 Forwarding Table ----------------------------- Destination : 2001:1:: PrefixLen: 64 Flag : D/L/- Cost : 10 Next Hop : Direct Interface: GE1/1/2 Destination : 2001:2:: PrefixLen: 64 Flag : D/L/-...

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

    Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set BFD for IPv6 IS-IS configuration example Network requirements As shown in Figure 116: • Configure IPv6 IS-IS on Router A, Router B, and Router C so that they can reach each other. •...
  • Page 506 [RouterA-GigabitEthernet1/1/1] isis ipv6 enable 1 [RouterA-GigabitEthernet1/1/1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] isis ipv6 enable 1 [RouterA-GigabitEthernet1/1/2] quit # Configure Router B. <RouterB> system-view [RouterB] isis 1 [RouterB-isis-1] is-level level-1 [RouterB-isis-1] network-entity 10.0000.0000.0002.00 [RouterB-isis-1] address-family ipv6 [RouterB-isis-1-ipv6] quit [RouterB-isis-1] quit [RouterB] interface gigabitethernet 1/1/1 [RouterB-GigabitEthernet1/1/1] isis ipv6 enable 1 [RouterB-GigabitEthernet1/1/1] quit...

  • Page 507: Ipv6 Is-Is Frr Configuration Example

    Verifying the configuration # Display BFD session information on Router A. <RouterA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode: Local Discr: 1441 Remote Discr: 1450 Source IP: FE80::20F:FF:FE00:1202 (link-local address of GigabitEthernet1/1/1 on Router A) Destination IP: FE80::20F:FF:FE00:1200 (link-local address of GigabitEthernet1/1/1 on Router B)
  • Page 508 Figure 117 Network diagram Table 26 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A GE1/1/1 1::1/64 Router B GE1/1/1 3::1/64 GE1/1/2 2::1/64 GE1/1/2 2::2/64 Loop0 10::1/128 Loop0 20::1/128 Router C GE1/1/1 1::2/64 GE1/1/2 3::2/64 Configuration procedure Configure IPv6 addresses for interfaces on the routers and enable IPv6 IS-IS.
  • Page 509 [RouterA-isis-1] address-family ipv6 [RouterA-isis-1-ipv6] fast-reroute route-policy frr [RouterA-isis-1-ipv6] quit [RouterA-isis-1] quit # Configure Router B. <RouterB> system-view [RouterB] ipv6 prefix-list abc index 10 permit 10:: 128 [RouterB] route-policy frr permit node 10 [RouterB-route-policy-frr-10] if-match ipv6 address prefix-list abc [RouterB-route-policy-frr-10] apply ipv6 fast-reroute backup-interface gigabitethernet 1/1/1 backup-nexthop 3::2 [RouterB-route-policy-frr-10] quit [RouterB] isis 1...
  • Page 510 Process ID: 1 SubProtID: 0x1 Age: 00h33m23s Cost: 10 Preference: 15 IpPre: N/A QosLocalID: N/A Tag: 0 State: Active Adv OrigTblID: 0xa OrigVrf: default-vrf TableID: 0xa OrigAs: 0 NibID: 0x24000006 LastAs: 0 AttrID: 0xffffffff Neighbor: :: Flags: 0x10041 OrigNextHop: FE80::34CC:E8FF:FE5B:C02 Label: NULL RealNextHop: FE80::34CC:E8FF:FE5B:C02 BkLabel: NULL...

  • Page 511: Configuring Ipv6 Pbr

    Configuring IPv6 PBR Overview Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify parameters for packets that match specific criteria such as ACLs or that have specific lengths. The parameters include the next hop, output interface, default next hop, and default output interface. A device forwards received packets using the following process: The device uses PBR to forward matching packets.
  • Page 512 • apply output-interface • apply default-next-hop • apply default-output-interface Table 27 Priorities and meanings of apply clauses Clause Meaning Priority Sets an IP precedence. This clause is always executed. apply precedence Multiple next hops, output interfaces, default next hops, or default output interfaces operate in either primary/backup or load sharing mode.

  • Page 513: 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 In permit mode In deny mode the node? • If the node is configured with apply clauses, IPv6 PBR executes the apply clauses on the node.

  • Page 514: Configuring An Ipv6 Policy

    Tasks at a glance (Required.) Configuring IPv6 PBR: • Configuring IPv6 local PBR • Configuring IPv6 interface PBR Configuring an IPv6 policy Creating an IPv6 node Step Command Remarks Enter system view. system-view Create an IPv6 policy ipv6 policy-based-route policy-name [ deny | By default, no IPv6 policy or policy node and permit ] node node-number...
  • Page 515 Step Command Remarks By default, no VPN instance is specified. You can specify a maximum of n Set VPN apply access-vpn vpn-instance VPN instances for a node. The instances. vpn-instance-name&<1-n> matching packets are forwarded according to the forwarding table of the first available VPN instance.

  • Page 516: Configuring Ipv6 Pbr

    Step Command Remarks By default, no default output interface is specified. You can specify multiple default output interfaces for backup or load apply default-output-interface 12. Set default sharing in one command line or by { interface-type interface-number [ track output interfaces. executing this command multiple track-entry-number ] }&<1-n>...

  • Page 517: Displaying And Maintaining Ipv6 Pbr

    To configure IPv6 interface PBR: Step Command Remarks Enter system view. system-view Enter interface interface interface-type interface-number view. Apply an IPv6 By default, no IPv6 policy is policy to the ipv6 policy-based-route policy-name applied to the interface. interface. Displaying and maintaining IPv6 PBR Execute display commands in any view and reset commands in user view.

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

    Configuration procedure Configure Router A: # Configure the IPv6 addresses of GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2. <RouterA> system-view [RouterA] interface gigabitethernet 1/1/1 [RouterA-GigabitEthernet1/1/1] ipv6 address 1::1 64 [RouterA-GigabitEthernet1/1/1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] ipv6 address 2::1 64 [RouterA-GigabitEthernet1/1/2] quit # Configure ACL 3001 to match TCP packets.
  • Page 519 Figure 119 Network diagram Configuration procedure Configure Router A: # Configure RIPng. <RouterA> system-view [RouterA] ripng 1 [RouterA-ripng-1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] ipv6 address 1::1 64 [RouterA-GigabitEthernet1/1/2] ripng 1 enable [RouterA-GigabitEthernet1/1/2] quit [RouterA] interface gigabitethernet 1/1/3 [RouterA-GigabitEthernet1/1/3] ipv6 address 2::1 64 [RouterA-GigabitEthernet1/1/3] ripng 1 enable [RouterA-GigabitEthernet1/1/3] quit # Configure ACL 3001 to match TCP packets.

  • Page 520: Packet Length-Based Ipv6 Interface Pbr Configuration Example

    [RouterA-GigabitEthernet1/1/1] ripng 1 enable [RouterA-GigabitEthernet1/1/1] ipv6 policy-based-route aaa [RouterA-GigabitEthernet1/1/1] quit Configure RIPng on Router B. <RouterB> system-view [RouterB] ripng 1 [RouterB-ripng-1] quit [RouterB] interface gigabitethernet 1/1/2 [RouterB-GigabitEthernet1/1/2] ipv6 address 1::2 64 [RouterB-GigabitEthernet1/1/2] ripng 1 enable [RouterB-GigabitEthernet1/1/2] quit Configure RIPng on Router C. <RouterC>...
  • Page 521 Figure 120 Network diagram Configuration procedure Configure Router A: # Configure RIPng. <RouterA> system-view [RouterA] ripng 1 [RouterA-ripng-1] quit [RouterA] interface gigabitethernet 1/1/2 [RouterA-GigabitEthernet1/1/2] ipv6 address 150::1 64 [RouterA-GigabitEthernet1/1/2] ripng 1 enable [RouterA-GigabitEthernet1/1/2] quit [RouterA] interface gigabitethernet 1/1/3 [RouterA-GigabitEthernet1/1/3] ipv6 address 151::1 64 [RouterA-GigabitEthernet1/1/3] ripng 1 enable [RouterA-GigabitEthernet1/1/3] quit # Configure Node 10 for policy lab1 to forward packets with a length of 64 to 100 bytes to the...
  • Page 522 [RouterB] interface gigabitethernet 1/1/2 [RouterB-GigabitEthernet1/1/2] ipv6 address 150::2 64 [RouterB-GigabitEthernet1/1/2] ripng 1 enable [RouterB-GigabitEthernet1/1/2] quit [RouterB] interface gigabitethernet 1/1/3 [RouterB-GigabitEthernet1/1/3] ipv6 address 151::2 64 [RouterB-GigabitEthernet1/1/3] ripng 1 enable [RouterB-GigabitEthernet1/1/3] quit [RouterB] interface loopback 0 [RouterB-LoopBack0] ipv6 address 10::1 128 [RouterB-LoopBack0] ripng 1 enable Verifying the configuration # Execute the debugging ipv6 policy-based-route command on Router A.
  • Page 523 Ping statistics for 10::1: Packets: Sent = 1, Received = 1, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms The debugging information about IPv6 PBR displayed on Router A is as follows: <RouterA>...

  • Page 524: 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 525: Routing Policy

    Routing policy A routing policy can contain multiple nodes, which are in a logical OR relationship. A node with a smaller number is matched first. A route matches the routing policy if it matches one node (except the node configured with the continue clause) in the routing policy. Each node has a match mode of permit or deny.

  • Page 526: Configuring An As Path List

    Step Command Remarks ip prefix-list prefix-list-name [ index index-number ] Configure an IPv4 { deny | permit } ip-address mask-length By default, no IPv4 prefix list. [ greater-equal min-mask-length ] [ less-equal prefix lists exist. max-mask-length ] Configuring an IPv6 prefix list If all items are set to deny mode, no routes can pass the IPv6 prefix list.

  • Page 527: 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 matches the extended community list if it matches one item in the list. To configure an extended community list: Step Command...

  • Page 528: Configuring If-Match Clauses

    Configuring if-match clauses You can either specify no if-match clauses or multiple if-match clauses for a routing policy node. If no if-match clause is specified for a permit node, all routes can pass the node. If no if-match clause is specified for a deny node, no routes can pass the node. The if-match clauses of a routing policy node have a logical AND relationship.

  • Page 529: Configuring Apply Clauses

    Step Command Remarks By default, no output interface match criterion is Match routes having the if-match interface { interface-type configured. specified output interface. interface-number }&<1-16> This command is not supported by BGP. By default, no local Match BGP routes having the if-match local-preference preference is configured for specified local preference.
  • Page 530 Step Command Remarks apply cost-type { external | By default, no cost type is set for Set a cost type for routes. internal | type-1 | type-2 } routes. apply extcommunity { rt Set the extended community By default, no extended community route-target }&<1-32>...

  • Page 531: Configuring The Continue Clause

    Step Command Remarks • Set an IPv4 backup link for FRR: apply fast-reroute { backup-interface interface-type interface-number [ backup-nexthop ip-address ] | backup-nexthop ip-address } 21. Set a backup link for fast By default, no backup link is set for reroute (FRR).

  • Page 532: Routing Policy Configuration Examples

    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. adv-community-list-number | name comm-list-name ] Display BGP extended community list display ip extcommunity-list [ ext-comm-list-number ] information.
  • Page 533 [RouterC] isis [RouterC-isis-1] is-level level-2 [RouterC-isis-1] network-entity 10.0000.0000.0001.00 [RouterC-isis-1] quit [RouterC] interface gigabitethernet 1/1/1 [RouterC-GigabitEthernet1/1/1] isis enable [RouterC-GigabitEthernet1/1/1] quit [RouterC] interface gigabitethernet 1/1/2 [RouterC-GigabitEthernet1/1/2] isis enable [RouterC-GigabitEthernet1/1/2] quit [RouterC] interface gigabitethernet 1/1/3 [RouterC-GigabitEthernet1/1/3] isis enable [RouterC-GigabitEthernet1/1/3] quit [RouterC] interface gigabitethernet 1/1/4 [RouterC-GigabitEthernet1/1/4] isis enable [RouterC-GigabitEthernet1/1/4] quit # Configure Router B.
  • Page 534 192.168.1.0/24 Transit 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 Configure filtering lists on Router B: # Configure IPv4 basic ACL 2002 to permit route 172.17.2.0/24.

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

    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 As shown in Figure...
  • Page 536 [RouterA] route-policy static2ripng permit node 10 [RouterA-route-policy-static2ripng-10] quit # Enable RIPng and apply routing policy static2ripng to filter redistributed static routes on Router A. [RouterA] ripng [RouterA-ripng-1] import-route static route-policy static2ripng Configure Router B: # Configure the IPv6 address of GigabitEthernet 1/1/1. <RouterB>...

  • Page 537: Configuring Mtr

    Configuring MTR Overview Multi-Topology Routing (MTR) splits a base topology into multiple topologies, which intersect or overlap with one another. Route calculation is performed on a per-topology basis. For example, IS-IS MTR enables IS-IS to perform separate route calculation for the IPv4 and IPv6 topologies in an IS-IS routing domain.
  • Page 538 • if-match—Defines a criterion to match packet attributes. The if-match clauses of a node are in an OR relationship. If a packet matches one of the if-match clauses, it matches the node. • apply—Specifies a topology for packets matching the MTR policy node. IMPORTANT: A node must contain both if-match and apply clauses.

  • Page 539: Displaying And Maintaining Mtr

    Displaying and maintaining MTR Execute display commands in any view. Task Command Display topology information. display topology [ name topo-name ] Display MTR policy information. display mtr-policy [ name mtr-policy-name ]...

  • Page 540: Configuring Dcn

    Configuring DCN Overview Data communication network (DCN) is built for the network management system (NMS) to implement operation, administration, and maintenance (OAM) on the network elements (NEs). On large-scaled networks with DCN configured, the NMS remotely manages and controls all NEs through the gateway network element (GNE), which reduces operation and maintenance costs.

  • Page 541: Enabling Dcn

    Tasks at a glance (Optional.) Enabling the automatic report (Optional.) Configuring the source MAC address of LLDP frames (Required.) Advertising the LLDP management address (Required.) Enabling the system to generate ARP entries for received management address LLDP TLVs Enabling DCN After DCN is enabled, the device assigns an NE IP to the loopback interface with the largest interface number and uses the interface for communication.

  • Page 542: Enabling The Automatic Report Feature

    Step Command Remarks Enter system view. system-view Create a VPN instance and enter its view, or enter the By default, no VPN instances ip vpn-instance view of an existing VPN exist. vpn-instance-name instance. Quit VPN instance view. quit Create a loopback interface and enter its view, or enter By default, no loopback interface loopback...

  • Page 543: Enabling The System To Generate Arp Entries For Received Management Address Lldp Tlvs

    address) for ARP entry learning. For more information about LLDP, see Layer 2—LAN Switching Configuration Guide. Step Command Remarks Enter system view. system-view Enter interface interface interface-type interface-number view. Advertise the By default, the LLDP lldp tlv-enable basic-tlv LLDP management-address-tlv [ ip-address | management address is not management interface loopback interface-number ]...
  • Page 544 Figure 124 Network diagram Configuration procedure Configure the GNE: # Enable SNMP on the GNE. (Details not shown. For more information, see Network Management and Monitoring Configuration Guide.) # Enable DCN, configure the NE ID as 100001 and NE IP as 11.1.1.1/32, and enable the automatic report feature.
  • Page 545 [GNE-GigabitEthernet1/1/2] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023 # Configure the system to issue the generated ARP entry to the Layer 3 Ethernet subinterface associated with VLAN 4094 in Dot1q termination after GigabitEthernet 1/1/2 receives an LLDP frame. [GNE-GigabitEthernet1/1/2] lldp management-address arp-learning vlan 4094 [GNE-GigabitEthernet1/1/2] quit # Create Ethernet subinterface GigabitEthernet 1/1/1.4094 that borrows the IP address of Loopback 1023, and enable Dot1q termination on the interface.
  • Page 546 [DeviceA-LoopBack1023] quit # Enable LLDP globally. [DeviceA] lldp global enable # Enable the nearest bridge agents on GigabitEthernet 1/1/1 to advertise basic LLDP TLVs and management address TLVs. The IP address of interface Loopback 1023 is specified as the management address. [DeviceA] interface gigabitethernet 1/1/1 [DeviceA-GigabitEthernet1/1/1] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023...
  • Page 547 # Set the OSPF network type for GigabitEthernet 1/1/2.4094 to P2P. [DeviceA] interface gigabitethernet 1/1/2.4094 [DeviceA-GigabitEthernet1/1/2.4094] ospf network-type p2p [DeviceA-GigabitEthernet1/1/2.4094] quit Configure Device B: # Enable DCN, configure the NE ID as 300003 and NE IP as 33.3.3.3/32. <DeviceB> system-view [DeviceB] dcn [DeviceB-dcn] ne-id 300003 [DeviceB-dcn] ne-ip 33.3.3.3 32...
  • Page 548 [GNE] display dcn ne-info DCN Network Elements Information NE ID NE IP Metric Device Type 0x100001 11.1.1.1 HPE 6604 0x200002 22.2.2.2 HPE 6608 0x300003 33.3.3.3 HPE 6616 Total number: 3 The output shows that GNE, Device A, and Device B are online. The GNE notifies the NMS of the online event.
  • Page 549 NE ID NE IP Metric Device Type 0x100001 11.1.1.1 HPE 6604 0x200002 22.2.2.2 HPE 6608 Total number: 2 The output shows that GNE and Device A are online. The GNE notifies the NMS of the offline event of Device B. You can still successfully ping the NE IP address of Device A from the GNE.

  • Page 550: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. 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. Italic Square brackets enclose syntax choices (keywords or arguments) that are optional.

  • Page 551: 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 552: 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 553: 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 554 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 555: Index

    Index BGP default route (peer/peer group)(IPv4), Numerics BGP default route (peer/peer group)(IPv6), 4-byte BGP fake AS number (IPv4), BGP AS number suppression, BGP fake AS number (IPv6), BGP optimal route (IPv4 unicast), BGP 6PE configuration, BGP optimal route (IPv6 unicast), BGP 6PE optional capabilities, BGP route advertisement rules, IPv6 BGP 6PE configuration,...
  • Page 556 IS-IS authentication (area), IPv4 BGP+IGP route redistribution, OSPF area, IPv4 multicast BGP configuration, OSPF area configuration (NSSA), 77, 116 IPv6 BGP basic configuration, OSPF area configuration (stub), 76, 114 IPv6 BGP BFD configuration, OSPF areas, IPv6 BGP configuration, OSPF authentication (area), IPv6 BGP FRR configuration, OSPF backbone, IPv6 BGP route reflector configuration,...
  • Page 557 IS-IS authentication (routing domain), IS-IS FRR BFD enable (echo packet mode), IS-IS network security, OSPF BFD, OSPF configuration, OSPF configuration, RIPng IPsec profile application, OSPF detection configuration (bidirectional control), RIPv2 message authentication configuration, OSPF detection configuration (single-hop echo), auto OSPF FRR configuration, BGP route summarization (automatic)(IPv4), OSPF PIC BFD,...
  • Page 558 fake AS number advertisement, peer, first AS number of EBGP route update peer configuration, ignore, peer configuration (IPv4 unicast address), FRR configuration, peer configuration (IPv6 unicast address), GR configuration, peer group configuration, GTSM configuration, peer MD5 authentication, IGP route redistribution, policy accounting configuration, IPv4 BFD configuration, private AS number removal,...
  • Page 559 static routing BFD bidirectional control mode confederating (direct next hop), BGP confederation, static routing BFD bidirectional control mode BGP confederation compatibility, (indirect next hop), BGP MED route comparison (confederation Border Gateway Protocol. Use peers), broadcast IPv4 BGP confederation, IS-IS network type, configuring OSPF interface network type, BGP,...
  • Page 560 BGP policy accounting, IP routing RIB NSR, BGP route dampening (IPv4), IP routing RIP route redistribution, BGP route dampening (IPv6), IPv4 BGP, BGP route distribution filtering policy IPv4 BGP basics, (IPv4), IPv4 BGP BFD, BGP route distribution filtering policy IPv4 BGP COMMUNITY, (IPv6), IPv4 BGP confederation, BGP route filtering policy,...
  • Page 561 IPv6 static route BFD control mode (direct IS-IS system ID > host name mapping next hop), (dynamic), IPv6 static route BFD control mode (indirect IS-IS system ID > host name mapping next hop), (static), IPv6 static route BFD echo mode (single local PBR, hop), local PBR (packet type-based),...
  • Page 562 OSPF redistributed route summarization OSPFv3 route summarization, (ASBR), OSPFv3 route summarization (ABR), OSPF route control, OSPFv3 route summarization (ASBR), OSPF route redistribution, OSPFv3 stub area, 430, 450 OSPF route redistribution (another routing OSPFv3 stub router, protocol), OSPFv3 virtual link, OSPF route redistribution (default route), PBR, 378, 380, 383, 384 OSPF route summarization,...
  • Page 563 RIPng split horizon, RIP interface reception, 28, 28 RIPv2 message authentication, RIP route control configuration, RIPv2 route summarization, RIPng route control, routing policy, 512, 515, 520 convergence priority (IPv6 IS-IS), routing policy (IPv4 route redistribution), convergence priority (IS-IS), routing policy (IPv6 route redistribution), cost routing policy apply clause, IPv6 IS-IS automatic link cost calculation,...
  • Page 564 RIP default route advertisement, IPv6 BGP route reflector configuration, RIPng default route advertisement, IPv6 IS-IS basic configuration, static routing configuration. See under static IPv6 IS-IS BFD configuration, routing IPv6 IS-IS configuration, delaying IPv6 IS-IS FRR configuration, BGP MPLS local label update delay, IPv6 multicast BGP configuration, BGP route update delay, IPv6 PBR configuration,...
  • Page 565 OSPFv3 stub area configuration, IPv6 IS-IS, OSPFv3 stub router, IPv6 PBR, RIP basic configuration, IPv6 static routing, RIP BFD configuration (bidirectional control IS-IS, detection), MTR, RIP BFD configuration (single-hop echo OSPF, detection/specific destination), OSPFv3, RIP BFD single-hop echo detection, PBR, RIP configuration, RIP, RIP FRR configuration,...
  • Page 566 peer group configuration (IPv6 multicast IPv6 IS-IS MTR, address), IPv6 IS-IS prefix suppression, peer group configuration (IPv6 unicast IS-IS, address), IS-IS automatic cost calculation, session establishment (multiple hop), IS-IS FRR BFD (control packet mode), echo IS-IS FRR BFD (echo packet mode), IPv6 static route BFD echo mode (single IS-IS interface hello packet send, hop),...
  • Page 567 routing policy filters, IP routing table, routing policy if-match clause, filtering routing policy IP prefix list, BGP configuration, 200, 213 routing policy MAC list, 512, 515 BGP route distribution filtering policy, routing policy prefix list, BGP route filtering policy, flooding BGP route reception filtering policy, IS-IS LSP flash flooding, IPv4 BGP basic configuration,...
  • Page 568 RIPng NSR, BGP configuration, RIPng NSR configuration, BGP NSR configuration, fragment GR helper, IS-IS LSP fragment extension, GR restarter, frame IPv4 BGP GR configuration, DCN LLDP frame ARP entry enable, IS-IS GR configuration, 167, 189 IS-IS GR helper, BFD bidirectional control detection enable, IS-IS GR restarter, BFD single-hop echo detection enable, IS-IS NSR,...
  • Page 569 RIP BFD configuration (single-hop echo detection/neighbor), BGP IGP metrics ignore, RIP BFD configuration (single-hop echo BGP IGP route redistribution, detection/specific destination), BGP ORIGIN path attribute, host IPv4 BGP+IGP route redistribution, IS-IS system ID > host name mapping, IS-IS basic configuration, OSPF host route advertisement, IS-IS basics configuration, host route reception,...
  • Page 570 IS-IS hello packet send interval, BGP peer group, IS-IS SPF calculation interval, BGP peer MD5 authentication, OSPF exit overflow interval, BGP policy accounting, OSPF LSA arrival interval, BGP protocols and standards, OSPF LSA generation interval, BGP received route preferred value, OSPF LSU transmit rate, BGP route dampening configuration, OSPF SPF calculation interval,...
  • Page 571 IS-IS ATT bit, IS-IS PDU SNP type, IS-IS authentication, IS-IS PDU types, IS-IS authentication (area), IS-IS PIC BFD, IS-IS authentication (neighbor IS-IS PICconfiguration, relationship), IS-IS preference, IS-IS authentication (routing domain), IS-IS prefix suppression, IS-IS automatic cost calculation, IS-IS protocols and standards, IS-IS basic configuration, IS-IS redistributed route filtering, IS-IS basics configuration,...
  • Page 572 OSPF host route advertisement, OSPFv3 configuration, 427, 428, 450 OSPF interface cost, OSPFv3 DD packet ignore MTU check, OSPF interface network type (broadcast), OSPFv3 display, OSPF interface network type (NBMA), OSPFv3 DR election configuration, OSPF interface network type (P2MP), OSPFv3 ECMP route max, OSPF interface network type (P2P), OSPFv3 enable, OSPF interface packet send/receive...
  • Page 573 PBR display, RIP neighbor specification, PBR maintain, RIP network management configuration, PBR node action, RIP network optimization, PBR node creation, RIP network tuning, PBR node match criteria, RIP NSR configuration, PBR policy, RIP NSR enable, PBR policy configuration, RIP operation, PBR+Track collaboration, RIP packet max length, policy apply clause,...
  • Page 574 RIPng split horizon configuration, EBGP peer group configuration (IPv4 unicast address), RIPng timer configuration, EBGP peer protection (low memory RIPng triggered update send interval, exemption), RIPv1 message zero field check, EBGP session establishment (multiple hop), RIPv2 message authentication IBGP peer group configuration (IPv4 multicast configuration, address), RIPv2 route summarization configuration,...
  • Page 575 default route advertisement (peer/peer EBGP peer protection (low memory group), exemption), display, EBGP session establishment (multiple hop), dynamic peer configuration, IBGP peer group configuration (IPv6 multicast address), dynamic peer configuration (IPv4 multicast address), IBGP peer group configuration (IPv6 unicast address), fake AS number advertisement, IP routing FIB route max lifetime, FRR,...
  • Page 576 policy-based routing. See IPv6 PBR received route preferred value, provider edge. See route dampening, RIB NSR, route distribution filtering policy, RIP, 403, RIPng route preference, See also RIPng GR configuration, route reception filtering policy, routing policy ACLs, route reflector, routing policy configuration, 512, 520 route reflector configuration, routing policy configuration (IPv6 route...
  • Page 577 local configuration (packet type-based), FRR configuration, 169, 196 local PBR, FRR configuration (routing policy), maintain, global cost configuration, match mode/node clause relationship, GR configuration, 167, 189 node action, hello multiplier, node creation, hello packet send interval, node match criteria, interface cost configuration, policy, interface DIS priority, policy configuration,...
  • Page 578 protocols and standards, OSPF configuration, 66, 72, 106 pseudonode, OSPF FRR, redistributed route filtering, OSPF link state information BGP advertisement, route control configuration, OSPF virtual link, 68, 78 route convergence priority, OSPF virtual link configuration, route filtering, OSPFv3 FRR, route leaking, OSPFv3 virtual link, route leaking configuration, list...
  • Page 579 RIP routing loop prevention, OSPF LSR packet, OSPFv3 packet type, BGP LS configuration, OSPF LSU packet, OSPF AS External LSA, OSPF LSU transmit rate, OSPF ASBR summary LSA, OSPFv3 LSU transmit rate, OSPF exit overflow interval, OSPFv3 packet type, OSPF LSA arrival interval, OSPF LSA generation interval, MAC addressing OSPF LSA retransmission packet timer,...
  • Page 580 BGP path attribute, IPv6 BGP BFD configuration, memory IPv6 BGP configuration, EBGP peer protection (low memory IPv6 BGP FRR configuration, exemption), IPv6 BGP route reflector configuration, message overview, BGP notification, protocols and standards, BGP open, MPLS BGP route-refresh, BGP 6PE configuration, BGP update, BGP 6PE optional capabilities, RIPv1 message zero field check enable,...
  • Page 581 BGP IGP metrics ignore, BGP IGP route redistribution, naming BGP large-scale network, IS-IS system ID > host name mapping, BGP load balancing, 205, 276 NBMA BGP local network injection, OSPF interface network type, BGP LS configuration, OSPF network type, 71, 78 BGP MED attribute, OSPFv3 NBMA neighbor, BGP MPLS local label update delay,...
  • Page 582 interface PBR configuration (packet IPv6 IS-IS interface cost, length-based), IPv6 IS-IS interface tag value, interface PBR configuration (packet IPv6 IS-IS ISPF enable, source-IP-based), IPv6 IS-IS link cost, interface PBR configuration (packet IPv6 IS-IS LSDB overload bit, type-based), IPv6 IS-IS network optimization, IP routing dynamic routing protocols, IPv6 IS-IS network tuning, IP routing extension attribute redistribution,...
  • Page 583 IS-IS interface cost, OSPF DD packet interface MTU, IS-IS interface DIS priority, OSPF DR election configuration, IS-IS interface hello packet send, OSPF ECMP routes max, IS-IS interface P2P network type, OSPF enable, IS-IS interface packet send/receive, OSPF exit overflow interval, IS-IS interface tag value, OSPF FRR, IS-IS IS+circuit level,...
  • Page 584 OSPF route summarization configuration, OSPFv3 stub area, OSPF route types, OSPFv3 stub area configuration, OSPF SPF calculation interval, OSPFv3 stub router, OSPF stub router, OSPFv3 timer, OSPF summary network discard route, OSPFv3 virtual link, OSPF timer set, PBR node action, OSPF tuning, PBR node creation, OSPF Type-3 LSA filtering,...
  • Page 585 RIPng default route advertisement, static routing BFD single-hop echo mode, RIPng ECMP route max, static routing configuration, RIPng FRR configuration, 411, 421 static routing FRR configuration, RIPng GR configuration, 410, 418 tuning BGP, RIPng IPsec profile application, network element (NE) RIPng IPsec profile configuration, DCN basic concept, RIPng network optimization,...
  • Page 586 OSPF NSR configuration, DCN configuration, 528, 528, 531 OSPFv3 NSR, NO_ADVERTISE OSPFv3 NSR configuration, BGP COMMUNITY path attribute, RIP configuration, NO_EXPORT RIPng NSR configuration, 411, 419 BGP COMMUNITY path attribute, NSSA NO_EXPORT_SUBCONFED OSPF area configuration, 77, 116 BGP COMMUNITY path attribute, OSPF NSSA area, node OSPF NSSA LSA,...
  • Page 587 BFD detection configuration (bidirectional outbound LSA filtering (interface), control), outbound LSA filtering (specified neighbor), BFD detection configuration (single-hop packet DSCP value configuration, echo), packet types, BFD FRR configuration, PIC configuration, configuration, 66, 72, 106 PIC enable, DD packet interface MTU add, preference configuration, display, prefix priority configuration,...
  • Page 588 FRR configuration, 445, 471 OSPF interface network type, GR configuration, 443, 467 OSPF network type, GR helper configuration, OSPFv3 P2MP neighbor, GR restarter configuration, GR trigger, IS-IS network type, Inter-Area-Prefix LSA filtering, OSPF interface network type, interface cost configuration, OSPF network type, 71, 78 interface DR priority, OSPFv3 network type,...
  • Page 589 local PBR configuration, RIP BFD configuration (single-hop echo detection/specific destination), local PBR configuration (packet type-based), RIP network management configuration, OSPF basics configuration, RIP packet max length, OSPF BFD, RIP packet send rate configuration, OSPF configuration, 66, 72, 106 RIPng, OSPF DD, RIPng packet send rate, OSPF DD packet interface MTU, RIPng packet zero field check,...
  • Page 590 Track collaboration, interface PBR configuration (packet type-based), IPv6 IS-IS FRR configuration (routing policy), IS-IS CLVs, IPv6 PBR, IS-IS hello type, IPv6 PBR apply clause, IS-IS LSP type, IPv6 PBR configuration, 499, 501, 504, 505 IS-IS SNP type, IPv6 PBR if-match clause, IS-IS types, IPv6 PBR interface configuration, IPv6 PBR interface configuration (packet...
  • Page 591 OSPF route redistribution, assigning IPv6 IS-IS route convergence priority, RIP configuration, clearing IPv4 BGP information, preferring clearing IPv6 BGP information, BGP default local preference, configuring BGP, BGP received route preferred value, configuring BGP 6PE, BGP route preference, configuring BGP 6PE basics, IS-IS preference specification, configuring BGP 6PE optional capabilities, OSPF protocol preference,...
  • Page 592 configuring BGP peer (IPv6 unicast configuring IBGP peer group (IPv4 multicast address), address), configuring BGP policy accounting, configuring IBGP peer group (IPv4 unicast address), configuring BGP route dampening (IPv4), configuring IBGP peer group (IPv6 multicast configuring BGP route dampening (IPv6), address), configuring BGP route distribution filtering configuring IBGP peer group (IPv6 unicast...
  • Page 593 configuring IPv6 IS-IS link cost, configuring IS-IS interface P2P network type, configuring IPv6 IS-IS route control, configuring IS-IS interface tag value, configuring IPv6 multicast BGP, configuring IS-IS link cost, configuring IPv6 PBR, 501, 504 configuring IS-IS LSP parameters, configuring IPv6 PBR interface, configuring IS-IS LSP timer, configuring IPv6 PBR interface (packet configuring IS-IS LSP-calculated route...
  • Page 594 configuring OSPF GR restarter (IETF), configuring OSPFv3 FRR backup next hop (routing policy), configuring OSPF GR restarter (non-IETF), configuring OSPFv3 FRR backup next hop calculation (LFA algorithm), configuring OSPF GTSM, configuring OSPFv3 FRR BFD, configuring OSPF host route advertisement, configuring OSPFv3 GR, 443, 467 configuring OSPF interface cost, configuring OSPFv3 GR helper,...
  • Page 595 configuring RIP BFD (bidirectional control configuring routing policy AS_PATH list, detection/direct neighbor), configuring routing policy COMMUNITY list, configuring RIP BFD (bidirectional control configuring routing policy continue clause, detection/indirect neighbor), configuring routing policy extended community configuring RIP BFD (single-hop echo list, detection/neighbor), configuring routing policy filter, configuring RIP BFD (single-hop echo...
  • Page 596 displaying IPv6 IS-IS, enabling IPv6 IS-IS prefix suppression, displaying IPv6 PBR, enabling IS-IS, displaying IPv6 static routing, enabling IS-IS automatic cost calculation, displaying IS-IS, enabling IS-IS FRR BFD (control packet mode), displaying MTR, enabling IS-IS FRR BFD (echo packet displaying OSPF, mode), displaying OSPFv3, enabling IS-IS interface hello packet send,...
  • Page 597 ignoring BGP ORIGINATOR_ID attribute setting IP routing RIB route max lifetime, (IPv4), setting IPv6 IS-IS LSDB overload bit, ignoring BGP ORIGINATOR_ID attribute setting IPv6 PBR node match criteria, (IPv6), setting IS-IS ATT bit Level-1 LSP, ignoring OSPFv3 DD packet MTU check, setting IS-IS IS+circuit level, injecting BGP local network (IPv4), setting IS-IS LSDB overload bit,...
  • Page 598 tuning IS-IS network, OSPF redistributed route default parameters, tuning OSPFv3 network, OSPF route redistribution, tuning RIPng network, OSPF route redistribution configuration, profile OSPFv3 redistributed route tag, OSPFv3 IPsec profile application, OSPFv3 route redistribution, 436, 460 OSPFv3 IPsec profile configuration, OSPFv3 route redistribution (another routing protocol), protecting OSPFv3 route redistribution (default route),...
  • Page 599 enabling, display, FRR BFD bidirectional control detection ECMP route max, enable, FRR configuration, 411, 421 FRR BFD single-hop echo detection GR configuration, 410, 418 enable, IPsec profile application, FRR configuration, 41, 63 IPsec profile configuration, FRR configuration restrictions, 42, 412 maintain, GR configuration, 38, 52...
  • Page 600 BGP MED route comparison (diff ASs), IPv6 static route BFD echo mode (single hop), BGP MED route comparison (per-AS), IPv6 static route configuration, BGP optimal route advertisement, IPv6 static routing basic configuration, BGP ORIGINATOR_ID attribute ignore, IPv6 static routing BFD (direct next hop), BGP route advertisement rules, IPv6 static routing BFD (indirect next hop), BGP route dampening,...
  • Page 601 RIP route entries, IS-IS Level-1 router, RIP route redistribution configuration, IS-IS Level-1-2 router, RIP split horizon configuration, IS-IS Level-2 router, RIP update source IP address check, IS-IS route leaking, RIPng default route advertisement, IS-IS routing method, RIPng ECMP route max, IS-IS system ID, RIPng preference, local PBR configuration (packet type-based),...
  • Page 602 Routing Information Protocol. Use OSPF interface packet send/receive disable, routing policy OSPFv3 interface packet send/receive disable, display, RIPng packet send rate, maintain, RIPng triggered update send interval, rule session BGP route advertisement rules, BGP session establishment disable, BGP session state change logging, saving EBGP session establishment (multiple hop), BGP route update (IPv4),...
  • Page 603 BGP attribute configuration, static routing BFD bidirectional control mode (indirect next hop), source static routing BFD configuration, DCN LLDP frame source MAC address, static routing BFD single-hop echo mode, IS-IS PPP interface hello packet source address check, static routing FRR configuration, RIP source IP address check, stub speaker...
  • Page 604 IS-IS interface tag value, IPv6 IS-IS ISPF, OSPFv3 redistributed route tag, IPv6 IS-IS MTR, IPv6 static route configuration, BGP configuration, 200, 213 IPv6 static routing basic configuration, BGP TCP connection source address, IPv6 static routing BFD (direct next hop), IPv4 BGP basic configuration, IPv6 static routing BFD (indirect next hop), IPv4 BGP BFD configuration, IPv6 static routing configuration,...
  • Page 605 OSPF virtual link, 68, 78 RIP configuration, 25, 26, 43 OSPF virtual link configuration, RIPng basic configuration, 404, 413 RIPng configuration, 403, 404, 413 BGP multi-instance, RIPng GR configuration, RIPng IPsec profile configuration, zero field check RIPng route redistribution, RIPng packet, unicast zero field check (RIPv1), BGP dynamic peer,...

Table of Contents