1. Manuals
  2. Brands
  3. HP Manuals
  4. Switch
  5. HPE FlexNetwork 7500 series
  6. Configuration manual

HP HPE FlexNetwork 7500 series Configuration Manual

Hide thumbs
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
Table of Contents

Advertisement

Quick Links

Download this manual
HPE FlexNetwork 7500 Switch Series
Layer 3—IP Routing Configuration Guide
Part number: 5200-1940a
Software version: 7500-CMW710-R7557P01
Document version: 6W101-20171020

Advertisement

Table of Contents
loading

Related Manuals for HP HPE FlexNetwork 7500 series

Summary of Contents for HP HPE FlexNetwork 7500 series

  • Page 1 HPE FlexNetwork 7500 Switch Series Layer 3—IP Routing Configuration Guide Part number: 5200-1940a Software version: 7500-CMW710-R7557P01 Document version: 6W101-20171020...
  • 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 Advertising a default route ······················································································································· 31 Configuring received/redistributed route filtering······················································································ 32 Setting a preference for RIP ····················································································································· 32 Configuring RIP route redistribution ········································································································· 32 Tuning and optimizing RIP networks ··············································································································· 33 Configuration prerequisites ······················································································································ 33 Setting RIP timers ···································································································································· 33 Enabling split horizon and poison reverse ·······························································································...
  • Page 5 Configuring a virtual link ··························································································································· 76 Configuring OSPF network types ····················································································································· 77 Configuration prerequisites ······················································································································ 77 Configuring the broadcast network type for an interface·········································································· 77 Configuring the NBMA network type for an interface ··············································································· 77 Configuring the P2MP network type for an interface················································································ 78 Configuring the P2P network type for an interface···················································································...
  • Page 6 OSPF route summarization configuration example ················································································ 109 OSPF stub area configuration example ································································································· 112 OSPF NSSA area configuration example ······························································································ 114 OSPF DR election configuration example ······························································································ 116 OSPF virtual link configuration example ································································································ 121 OSPF GR configuration example ··········································································································· 123 OSPF NSR configuration example·········································································································...
  • Page 7 Configuring area authentication ············································································································· 162 Configuring routing domain authentication····························································································· 163 Configuring IS-IS GR ····································································································································· 163 Configuring IS-IS NSR ··································································································································· 164 Configuring BFD for IS-IS ······························································································································ 165 Configuring IS-IS FRR ··································································································································· 165 Configuration prerequisites ···················································································································· 166 Configuration guidelines ························································································································· 166 Configuration procedure ························································································································· 166 Displaying and maintaining IS-IS ···················································································································...
  • Page 8 Configuring the SoO attribute ················································································································· 270 Tuning and optimizing BGP networks ············································································································ 271 Configuring the keepalive interval and hold time ··················································································· 271 Setting the session retry timer ················································································································ 273 Configuring the interval for sending updates for the same route ··························································· 274 Enabling BGP to establish an EBGP session over multiple hops ··························································...
  • Page 9 IPv6 BGP route reflector configuration example ···················································································· 363 6PE configuration example ···················································································································· 366 BFD for IPv6 BGP configuration example ······························································································ 369 IPv6 BGP FRR configuration example ··································································································· 372 IPv6 multicast BGP configuration example ···························································································· 376 Troubleshooting BGP ····································································································································· 379 Symptom ················································································································································ 379 Analysis ··················································································································································...
  • Page 10 Configuring RIPng GR ··································································································································· 413 Configuring RIPng NSR ································································································································· 414 Configuring RIPng FRR ································································································································· 414 Configuration restrictions and guidelines ······························································································· 415 Configuration prerequisites ···················································································································· 415 Configuring RIPng FRR ························································································································· 415 Enabling BFD for RIPng FRR ················································································································ 415 Displaying and maintaining RIPng ················································································································· 416 RIPng configuration examples ·······················································································································...
  • Page 11 Configuration prerequisites ···················································································································· 446 Configuration guidelines ························································································································· 447 Configuration procedure ························································································································· 447 Displaying and maintaining OSPFv3·············································································································· 448 OSPFv3 configuration examples···················································································································· 449 OSPFv3 stub area configuration example ····························································································· 449 OSPFv3 NSSA area configuration example ·························································································· 454 OSPFv3 DR election configuration example ·························································································· 456 OSPFv3 route redistribution configuration example···············································································...
  • Page 12 Configuring an IP prefix list ···················································································································· 503 Configuring an AS path list ····················································································································· 504 Configuring a community list ·················································································································· 504 Configuring an extended community list ································································································ 505 Configuring a MAC list ··························································································································· 505 Configuring a routing policy···························································································································· 505 Configuration prerequisites ···················································································································· 505 Creating a routing policy ························································································································...

  • 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: Enabling The Rib To Flush Route Attribute Information To The Fib

    Step Command Remarks By default, the maximum Set the maximum lifetime for fib lifetime seconds lifetime for routes in the FIB 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 Rib Nsr

    Configuring RIB NSR IMPORTANT: Use this feature with protocol GR or NSR to avoid route timeouts and traffic interruption. When an active/standby switchover occurs, nonstop routing (NSR) backs up routing information from the active process to the standby process to avoid routing flapping and ensure forwarding continuity.

  • Page 19: Configuring Ipv4 Rib Inter-Protocol Frr

    Configuring IPv4 RIB inter-protocol FRR Step Command Remarks Enter system view. system-view Enter RIB view. Create the RIB IPv4 address By default, no RIB IPv4 address-family ipv4 family and enter its view. address family exists. By default, inter-protocol FRR is disabled. Enable IPv4 RIB inter-protocol fast-reroute If you do not specify a VPN...

  • Page 20: Displaying And Maintaining A Routing Table

    Step Command Remarks Configure routing protocol protocol nexthop By default, routing policy-based policy-based recursive recursive-lookup route-policy recursive lookup is not lookup. route-policy-name configured. Displaying and maintaining a routing table Execute display commands in any view and reset commands in user view. Task Command display ip routing-table [ vpn-instance vpn-instance-name ]...
  • Page 21 Task Command display ipv6 routing-table [ vpn-instance vpn-instance-name ] Display information about routes protocol protocol [ inactive | verbose ] installed by an IPv6 protocol. display ipv6 routing-table [ vpn-instance vpn-instance-name ] Display IPv6 route statistics. statistics Display brief IPv6 routing table display ipv6 routing-table [ vpn-instance vpn-instance-name ] summary information.

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

    Step Command Remarks (Optional.) Enable By default, the device does periodic sending of not send ARP requests to ARP requests to the ip route-static arp-request interval interval the next hops of static next hops of static routes. routes. (Optional.) Configure the ip route-static default-preference The default setting is 60.

  • Page 24: Single-Hop Echo Mode

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

  • Page 25: Configuring Static Route Frr

    Configuring static route FRR A link or router failure on a path can cause packet loss and even routing loop. Static route fast reroute (FRR) enables fast rerouting to minimize the impact of link or node failures. Figure 1 Network diagram Backup nexthop: Router C Router A Router B...

  • Page 26: Configuring Static Route Frr To Automatically Select A Backup Next Hop

    Configuring static route FRR to automatically select a backup next hop Step Command Remarks Enter system view. system-view Configure static route FRR to By default, static route FRR is automatically select a ip route-static fast-reroute auto disabled from automatically backup next hop. selecting a backup next hop.

  • Page 27: Static Route Configuration Examples

    Static route configuration examples Basic static route configuration example Network requirements As shown in Figure 2, configure static routes on the switches for interconnections between any two hosts. Figure 2 Network diagram Host B 1.1.6.2/24 Vlan-int100 1.1.6.1/24 Vlan-int500 Vlan-int600 1.1.4.2/30 1.1.5.5/30 Switch B Vlan-int500...

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

    Destination/Mask Proto Cost NextHop Interface 0.0.0.0/0 Static 60 1.1.4.2 Vlan500 Static Routing table Status : <Inactive> Summary Count : 0 # Display static routes on Switch B. [SwitchB] display ip routing-table protocol static Summary Count : 2 Static Routing table Status : <Active> Summary Count : 2 Destination/Mask Proto...
  • Page 29 • Configure a static route to subnet 120.1.1.0/24 on Switch A. • Configure a static route to subnet 121.1.1.0/24 on Switch B. • 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 Switch C.
  • Page 30 [SwitchB-vlan-interface10] bfd min-transmit-interval 500 [SwitchB-vlan-interface10] bfd min-receive-interval 500 [SwitchB-vlan-interface10] bfd detect-multiplier 9 [SwitchB-vlan-interface10] quit [SwitchB] ip route-static 121.1.1.0 24 vlan-interface 10 12.1.1.1 bfd control-packet [SwitchB] ip route-static 121.1.1.0 24 vlan-interface 13 13.1.1.2 preference 65 [SwitchB] quit # Configure static routes on Switch C. <SwitchC>...

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

    Static Routing table Status : <Inactive> Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 11. BFD for static routes configuration example (indirect next hop) Network requirements Figure 4 shows the network topology as follows: •...
  • Page 32 Device Interface IP address Switch C VLAN-interface 11 10.1.1.100/24 Switch C VLAN-interface 13 13.1.1.2/24 Switch D VLAN-interface 10 12.1.1.2/24 Switch D VLAN-interface 12 11.1.1.2/24 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure static routes and BFD: # Configure static routes on Switch A and enable BFD control mode for the static route that traverses Switch D.

  • Page 33: Static Route Frr Configuration Example

    # Display the static routes on Switch A. <SwitchA> 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 60 12.1.1.2 Vlan10 Static Routing table Status : <Inactive> Summary Count : 0 The output shows that Switch A communicates with Switch B through VLAN-interface 10.
  • Page 34 Table 6 Interface and IP address assignment Device Interface IP address Switch A VLAN-interface 100 12.12.12.1/24 Switch A VLAN-interface 200 13.13.13.1/24 Switch A Loopback 0 1.1.1.1/32 Switch B VLAN-interface 101 24.24.24.4/24 Switch B VLAN-interface 200 13.13.13.2/24 Switch B Loopback 0 4.4.4.4/32 Switch C VLAN-interface 100...
  • Page 35 Destination: 4.4.4.4/32 Protocol: Static Process ID: 0 SubProtID: 0x0 Age: 04h20m37s Cost: 0 Preference: 60 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: 13.13.13.2 Label: NULL...

  • 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 RIP 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 Enable RIP and enter RIP rip [ process-id ] [ vpn-instance By default, RIP is disabled. view. vpn-instance-name ] 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...

  • Page 41: Configuring A Rip Version

    Configuring a RIP version You can configure a global RIP version in RIP view or an interface-specific RIP version in interface view. 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 Enter system view. system-view 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.

  • Page 43: Disabling Host Route Reception

    Step Command Remarks interface interface-type Enter interface view. interface-number rip summary-address By default, no summary route is 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: Configuring Received/Redistributed Route Filtering

    Configuring received/redistributed route filtering Perform this task to filter received and redistributed routes by using a filtering policy. 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 |...

  • Page 45: Tuning And Optimizing Rip Networks

    Step Command Remarks rip [ process-id ] [ vpn-instance Enter RIP view. vpn-instance-name ] 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.

  • 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 ] By default, the maximum number Set the maximum number of maximum load-balancing of RIP ECMP routes equals the RIP ECMP routes. number maximum number of ECMP routes supported by the system.

  • Page 48: Setting The Rip Triggered Update Interval

    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. { cipher | plain } string } | simple { cipher | configured.

  • Page 49: Configuring Rip Network Management

    Step Command Remarks By default, RIP does not Specify a RIP neighbor. peer ip-address unicast updates to any peer. Disable source IP By default, source IP address check on undo validate-source-address address check on inbound inbound RIP updates RIP updates is enabled. Configuring RIP network management You can use network management software to manage the RIP process to which MIB is bound.

  • Page 50: Setting The Maximum Length Of Rip Packets

    Setting the maximum length of RIP packets CAUTION: 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

    With the GR feature, the restarting router (known as the GR restarter) can notify the event to its GR capable neighbors. GR capable neighbors (known as GR helpers) maintain their adjacencies with the router within a GR interval. During this process, the FIB table of the router does not change. After the restart, the router contacts its neighbors to retrieve its FIB.

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

    task to enable BFD for RIP. For more information about BFD, see High Availability Configuration Guide. RIP supports the following BFD detection modes: • Single-hop echo detection—Detection mode for a direct neighbor. In this mode, a BFD session is established only when the directly connected neighbor has route information to send. •...

  • Page 53: Configuring Bidirectional Control Detection

    Configuring bidirectional control detection Step Command Remarks Enter system view. system-view 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.

  • Page 54: Configuration Prerequisites

    Configuration prerequisites You must specify a next hop by using the apply fast-reroute backup-interface command in a routing policy and reference the routing policy for FRR. For more information about routing policy configuration, see "Configuring routing policies." Configuring RIP FRR Step Command Remarks...

  • Page 55: Rip Configuration Examples

    Task Command display rip process-id interface [ interface-type Display RIP interface information. interface-number ] display rip process-id neighbor [ interface-type Display neighbor information for a RIP process. interface-number ] Display RIP NSR information. display rip [ process-id ] non-stop-routing display rip process-id route [ ip-address { mask-length | mask } [ verbose ] | peer ip-address | Display routing information for a RIP process.
  • Page 56 [SwitchB-Vlan-interface101] rip 1 enable [SwitchB-Vlan-interface101] quit [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] rip 1 enable [SwitchB-Vlan-interface102] quit # Display the RIP routing table of Switch A. [SwitchA] display rip 1 route Route Flags: R - RIP, T - TRIP P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect D - Direct, O - Optimal, F - Flush to RIB ---------------------------------------------------------------------------- Peer 1.1.1.2 on Vlan-interface100...
  • Page 57 The output shows that RIPv2 uses classless subnet masks. NOTE: After RIPv2 is configured, RIPv1 routes might still exist in the routing table until they are aged out. # Display the RIP routing table on Switch B. [SwitchB] 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

    Peer 1.1.1.1 on Vlan-interface100 Destination/Mask Nexthop Cost Flags 2.1.1.0/24 1.1.1.3 RAOF Local route Destination/Mask Nexthop Cost Flags 1.1.1.0/24 0.0.0.0 RDOF 10.1.1.0/24 0.0.0.0 RDOF 10.2.1.0/24 0.0.0.0 RDOF Configuring RIP route redistribution Network requirements As shown in Figure 8, Switch B communicates with Switch A through RIP 100 and with Switch C through RIP 200.
  • Page 59 [SwitchB-rip-200] quit # Enable RIP 200, and configure RIPv2 on Switch C. <SwitchC> system-view [SwitchC] rip 200 [SwitchC-rip-200] network 12.0.0.0 [SwitchC-rip-200] network 16.0.0.0 [SwitchC-rip-200] version 2 [SwitchC-rip-200] undo summary [SwitchC-rip-200] quit # Display the IP routing table on Switch C. [SwitchC] display ip routing-table Destinations : 13 Routes : 13...

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

    16.4.1.0/32 Direct 0 16.4.1.1 Vlan400 16.4.1.1/32 Direct 0 127.0.0.1 InLoop0 16.4.1.255/32 Direct 0 16.4.1.1 Vlan400 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 Configuring an additional metric for a RIP interface Network requirements As shown in Figure...

  • Page 61: Configuring Rip To Advertise A Summary Route

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

  • Page 64: Configuring Rip Gr

    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 Configuring RIP GR Network requirements As shown in Figure 11, Switch A, Switch B, and Switch C all run RIPv2. • Enable GR on Switch A. Switch A acts as the GR restarter. •...
  • Page 65 Enable RIP NSR on Switch S to ensure correct routing when an active/standby switchover occurs on Switch S. Figure 12 Network diagram Loop 0 Loop 0 22.22.22.22/32 44.44.44.44/32 Switch S Vlan-int100 Vlan-int200 12.12.12.1/24 14.14.14.1/24 Vlan-int100 Vlan-int200 12.12.12.2/24 14.14.14.2/24 Switch B Switch A Configuration procedure Configure IP addresses and subnet masks for interfaces on the switches.

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

    Route Flags: R - RIP, T - TRIP P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect D - Direct, O - Optimal, F - Flush to RIB ---------------------------------------------------------------------------- Peer 12.12.12.2 on Vlan-interface200 Destination/Mask Nexthop Cost Flags 14.0.0.0/8 12.12.12.2 RAOF...
  • Page 67 • Enable BFD for RIP on VLAN-interface 100 of Switch A. When the link over VLAN-interface 100 fails, BFD can quickly detect the failure and notify RIP. RIP deletes the neighbor relationship and route information learned on VLAN-interface 100, and uses the route destined for 100.1.1.1 24 through VLAN-interface 200.
  • Page 68 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary [SwitchC-rip-1] network 192.168.1.0 [SwitchC-rip-1] network 192.168.3.0 [SwitchC-rip-1] import-route static [SwitchC-rip-1] quit Configure BFD parameters on VLAN-interface 100 of Switch A. [SwitchA] bfd echo-source-ip 11.11.11.11 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] bfd min-transmit-interval 500 [SwitchA-Vlan-interface100] bfd min-receive-interval 500 [SwitchA-Vlan-interface100] bfd detect-multiplier 7 [SwitchA-Vlan-interface100] quit [SwitchA] quit...

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

    Configuring BFD for RIP (single hop echo detection for a specific destination) Network requirements As shown in Figure 14, VLAN-interface 100 of Switch A and Switch B runs RIP process 1. VLAN-interface 200 of Switch B and Switch C runs RIP process 1. •...
  • Page 70 [SwitchB-rip-1] network 192.168.3.0 [SwitchB-rip-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] rip 1 [SwitchC-rip-1] network 192.168.3.0 [SwitchC-rip-1] import-route static cost 3 [SwitchC-rip-1] quit Configure BFD parameters on VLAN-interface 100 of Switch A. [SwitchA] bfd echo-source-ip 11.11.11.11 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] bfd min-echo-receive-interval 500 [SwitchA-Vlan-interface100] return Configure static routes:...

  • Page 71: Configuring Bfd For Rip (Bidirectional Detection In Bfd Control Packet Mode)

    Tunnel ID: Invalid Interface: vlan-interface 100 BkTunnel ID: Invalid BkInterface: N/A FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A # Display routes destined for 100.1.1.0/24 on Switch B when the link between Switch A and Switch B fails. <SwitchB> display ip routing-table 100.1.1.0 24 verbose Summary Count : 1 Destination: 100.1.1.0/24 Protocol: RIP...
  • Page 72 Figure 15 Network diagram Switch D Vlan-int300 Vlan-int400 101.1.1.0/24 100.1.1.0/24 Vlan-int300 Vlan-int400 Switch B Vlan-int100 Vlan-int200 Vlan-int100 Vlan-int200 Switch A Switch C Table 7 Interface and IP address assignment Device Interface IP address Switch A VLAN-interface 300 192.168.3.1/24 Switch A VLAN-interface 100 192.168.1.1/24 Switch B...
  • Page 73 [SwitchA-rip-2] undo summary [SwitchA-rip-2] network 192.168.3.0 [SwitchA-rip-2] quit # Configure Switch C. <SwitchC> system-view [SwitchC] rip 1 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary [SwitchC-rip-1] network 192.168.2.0 [SwitchC-rip-1] network 192.168.4.0 [SwitchC-rip-1] network 100.1.1.0 [SwitchC-rip-1] peer 192.168.1.1 [SwitchC-rip-1] undo validate-source-address [SwitchC-rip-1] import-route static [SwitchC-rip-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] rip bfd enable...

  • Page 74: Configuring Rip Frr

    Verifying the configuration # Display the BFD session information on Switch A. <SwitchA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv4 session working under Ctrl mode: LD/RD SourceAddr DestAddr State Holdtime Interface 513/513 192.168.1.1 192.168.2.2 1700ms...
  • Page 75 Device Interface IP address Switch A VLAN-interface 200 13.13.13.1/24 Switch A Loopback 0 1.1.1.1/32 Switch B VLAN-interface 101 24.24.24.4/24 Switch B VLAN-interface 200 13.13.13.2/24 Switch B Loopback 0 4.4.4.4/32 Switch C VLAN-interface 100 12.12.12.2/24 Switch C VLAN-interface 101 24.24.24.2/24 Configuration procedure Configure IP addresses and subnet masks for interfaces on the switches.
  • Page 76 SubProtID: 0x1 Age: 04h20m37s Cost: 1 Preference: 100 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: 13.13.13.2 Flags: 0x1008c OrigNextHop: 13.13.13.2 Label: NULL RealNextHop: 13.13.13.2 BkLabel: NULL BkNextHop: 12.12.12.2 Tunnel ID: Invalid...

  • Page 77: 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 78: 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 79 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 80: 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 81: 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 82: 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 83: 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 84 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 85: 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 86: Enabling Ospf On A Network

    You can specify a global router ID, or specify a router ID when you create an OSPF process. • If you specify a router ID when you create an OSPF process, any two routers in an AS must have different router IDs. A common practice is to specify the IP address of an interface as the router ID.

  • Page 87: Configuring Ospf Areas

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, OSPF is disabled on an interface. If the specified OSPF process and area do Enable an OSPF process ospf process-id area not exist, the command creates the OSPF on the interface. area-id [ exclude-subip ] process and area.

  • Page 88: Configuring An Nssa Area

    Configuring an NSSA area A stub area cannot import external routes, but an NSSA area can import external routes into the OSPF routing domain while retaining other stub area characteristics. Do not configure the backbone area as an NSSA area or totally NSSA area. To configure an NSSA area, configure the nssa command on all the routers attached to the area.

  • Page 89: Configuring Ospf Network Types

    Configuring OSPF network types OSPF classifies networks into four types, including broadcast, NBMA, P2MP, and P2P. The default network type of an interface on the device is broadcast. When you change the network type of an interface, follow these guidelines: •...

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

    Step Command Remarks The default setting is 1. (Optional.) Set a router ospf dr-priority priority The router priority configured with this priority for the interface. command is for DR election. Return to system view. quit ospf [ process-id | router-id Enter OSPF view.

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

    Configuring the P2P network type for an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the OSPF ospf network-type p2p By default, the network type of an network type for the [ peer-address-check ] interface is broadcast.

  • Page 92: Configuring Received Ospf Route Filtering

    Configuring route summarization on an ASBR Perform this task to enable an ASBR to summarize external routes within the specified address range into a single route. The ASBR advertises only the summary route to reduce the number of LSAs in the LSDB. An ASBR can summarize routes in the following LSAs: •...

  • Page 93: Setting An Ospf Cost For An Interface

    To configure Type-3 LSA filtering: Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id Enter OSPF view. | vpn-instance vpn-instance-name ] Enter area view. area area-id filter { ipv4-acl-number | prefix-list Configure Type-3 LSA prefix-list-name | route-policy By default, the ABR does not filtering.

  • Page 94: Setting The Maximum Number Of Ecmp Routes

    Setting the maximum number of ECMP routes Perform this task to implement load sharing over ECMP routes. To set the maximum number of ECMP routes: Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id Enter OSPF view. | vpn-instance vpn-instance-name ] By default, the maximum number of ECMP routes...

  • Page 95: Configuring Ospf Route Redistribution

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

  • Page 96: Advertising A Host Route

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

  • Page 97: Setting Ospf Timers

    • Enable OSPF. Setting OSPF timers An OSPF interface includes the following timers: • Hello timer—Interval for sending hello packets. It must be identical on OSPF neighbors. • Poll timer—Interval for sending hello packets to a neighbor that is down on the NBMA network. •...

  • Page 98: Setting Lsa Transmission Delay

    Setting LSA transmission delay To avoid LSAs from aging out during transmission, set an LSA retransmission delay especially for low speed links. To set the LSA transmission delay on an interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 99: Setting The Lsa Generation Interval

    Step Command Remarks The default setting is 1000 milliseconds. Make sure this interval is smaller Set the LSA arrival interval. lsa-arrival-interval interval than or equal to the interval set with the lsa-generation-interval command. 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.

  • Page 100: Configuring Stub Routers

    Step Command Remarks By default, an OSPF interface can receive and send OSPF packets. The silent-interface command disables only the interfaces Disable interfaces from silent-interface { interface-type associated with the current receiving and sending interface-number | all } process rather than other OSPF packets.

  • Page 101: Adding The Interface Mtu Into Dd Packets

    Step Command Remarks ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Enter area view. area area-id • Configure MD5 authentication: authentication-mode { hmac-md5 | By default, no md5 } key-id { cipher | plain } string authentication is •...

  • Page 102: Setting A Dscp Value For Ospf Packets

    Setting a DSCP value for OSPF packets Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * By default, the DSCP Set a DSCP value for OSPF dscp dscp-value value for OSPF packets packets.

  • Page 103: Logging Neighbor State Changes

    If RFC 2328 is not compatible with RFC 1583, the intra-area route in a non-backbone area  is preferred to reduce the burden of the backbone area. The inter-area route and intra-area route in the backbone area have equal preference. Selects the route with the lower cost if two routes have equal preference.

  • Page 104: Setting The Lsu Transmit Rate

    Step Command Remarks By default, OSPF MIB is Bind OSPF MIB to an ospf mib-binding process-id bound to the process with the OSPF process. smallest process ID. 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 |...

  • Page 105: Enabling Ospf Ispf

    Step Command Remarks ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * (Optional.) Set the LSU transmit By default, an OSPF interface interval and the sends a maximum of three maximum number transmit-pacing interval interval count count LSU packets every 20 of LSUs that can be milliseconds.

  • Page 106: Configuring Prefix Prioritization

    Step Command Remarks Enter system view. system-view ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Enable prefix By default, prefix suppression suppression for the prefix-suppression is disabled for an OSPF OSPF process. process. Configuring prefix suppression for an interface Interface prefix suppression does not suppress prefixes of secondary IP addresses.

  • Page 107: Setting The Number Of Ospf Logs

    Step Command Remarks ospf [ process-id | router-id router-id | Enter OSPF view. vpn-instance vpn-instance-name ] * Enable PIC for By default, OSPF PIC is pic [ additional-path-always ] OSPF. enabled. Configuring BFD for OSPF PIC By default, OSPF PIC does not use BFD to detect primary link failures. To speed up OSPF convergence, enable BFD for OSPF PIC to detect the primary link failures.

  • Page 108: Filtering Outbound Lsas On An Interface

    Step Command Remarks By default, the number of OSPF logs is Set the number of event-log { lsa-flush | peer | spf } 10 for each type, including LSA aging OSPF logs. size count logs, route calculation logs, and neighbor logs. Filtering outbound LSAs on an interface To reduce the LSDB size for the neighbor and save bandwidth, you can perform this task on an interface to filter LSAs to be sent to the neighbor.

  • Page 109: Configuring Ospf Gr

    You can configure GTSM in OSPF area view or interface view. • The configuration in OSPF area view applies to all OSPF interfaces in the area. • The configuration in interface view takes precedence over OSPF area view. IMPORTANT: To use GTSM, you must configure GTSM on both the local and peer devices. You can specify different hop-count values for them.

  • Page 110: Configuring Ospf Gr Helper

    IMPORTANT: You cannot enable OSPF NSR on a device that acts as GR restarter. Configuring the IETF OSPF GR restarter Step Command Remarks Enter system view. system-view ospf [ process-id | router-id Enable OSPF and enter its router-id | vpn-instance view.

  • Page 111: Triggering Ospf Gr

    Step Command Remarks (Optional.) Enable GR helper graceful-restart helper enable By default, GR helper capability is capability. [ planned-only ] enabled. (Optional.) Enable strict LSA graceful-restart helper By default, strict LSA checking for checking for the GR helper. strict-lsa-checking the GR helper is disabled. Configuring the non-IETF OSPF GR helper Step Command...

  • Page 112: Configuring Bfd For Ospf

    Step Command Remarks ospf [ process-id | router-id router-id Enter OSPF view. | vpn-instance vpn-instance-name ] By default, OSPF NSR is disabled. This command takes effect only for the Enable OSPF NSR. non-stop-routing current process. As a best practice, enable OSPF NSR for each process if multiple OSPF processes exist.

  • Page 113: Configuring Ospf Frr

    Configuring OSPF FRR A link or router failure on a path can cause packet loss and even routing loop until OSPF completes routing convergence based on the new network topology. FRR enables fast rerouting to minimize the impact of link or node failures. Figure 23 Network diagram for OSPF FRR Backup nexthop: Router C Router A...
  • Page 114 Step Command Remarks By default, OSPF FRR is disabled. Enable OSPF FRR to If abr-only is specified, the route to calculate a backup next hop fast-reroute lfa [ abr-only ] the ABR is selected as the backup by using the LFA algorithm. path.

  • Page 115: Advertising Ospf Link State Information To Bgp

    Step Command Remarks Enable BFD echo By default, BFD echo packet mode for packet mode for ospf primary-path-detect bfd echo OSPF FRR is disabled. OSPF FRR. Advertising OSPF link state information to BGP After the device advertises OSPF link state information to BGP, BGP can advertise the information for intended applications.

  • Page 116: Ospf Configuration Examples

    Task Command display ospf [ process-id ] statistics [ error | packet [ interface-type Display OSPF statistics. interface-number ] ] Display OSPF virtual link display ospf [ process-id ] vlink information. Display OSPF request queue display ospf [ process-id ] request-queue [ interface-type interface-number ] [ neighbor-id ] information.
  • Page 117 Figure 24 Network diagram Area 0 Switch A Switch B Vlan-int100 10.1.1.1/24 Vlan-int100 Vlan-int200 10.1.1.2/24 Vlan-int200 10.3.1.1/24 10.2.1.1/24 Vlan-int200 Area 1 Area 2 Vlan-int200 10.3.1.2/24 10.2.1.2/24 Vlan-int300 Vlan-int300 10.4.1.1/24 10.5.1.1/24 Switch C Switch D Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Switch A.
  • Page 118 <SwitchD> system-view [SwitchD] router id 10.5.1.1 [SwitchD] ospf [SwitchD-ospf-1] area 2 [SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.2] network 10.5.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.2] quit [SwitchD-ospf-1] quit Verifying the configuration # Display information about neighbors on Switch A. [SwitchA] 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(Vlan-interface100)'s neighbors Router ID: 10.3.1.1...

  • Page 119: 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 Switch D. [SwitchD] display ospf routing OSPF Process 1 with Router ID 10.5.1.1 Routing Table Topology base (MTID 0) Routing for network Destination Cost...
  • Page 120 Figure 25 Network diagram Switch A Area 0 Switch B Vlan-int100 10.1.1.1/24 Vlan-int100 10.1.1.2/24 Vlan-int200 Vlan-int200 10.3.1.1/24 10.2.1.1/24 Vlan-int200 Vlan-int200 Area 1 Area 2 10.3.1.2/24 10.2.1.2/24 Vlan-int300 Vlan-int500 10.4.1.1/24 10.5.1.1/24 Switch C Switch D Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF (see "Basic OSPF configuration example").

  • Page 121: Ospf Route Summarization Configuration Example

    10.4.1.0/24 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.5.1.0/24 Stub 10.5.1.1 10.5.1.1 0.0.0.2 10.1.1.0/24 Inter 10.3.1.1 10.3.1.1 0.0.0.2 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...
  • Page 122 [SwitchA-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit # Configure Switch B. <SwitchB> system-view [SwitchB] router id 11.2.1.1 [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] router id 11.1.1.2 [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255...
  • Page 123 [SwitchC] bgp 100 [SwitchC-bgp] peer 11.1.1.1 as 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] import-route ospf [SwitchC-bgp-ipv4]import-route direct [SwitchC-bgp-ipv4] quit [SwitchC-bgp] quit Configure Switch B and Switch C to redistribute BGP routes into OSPF: # Configure OSPF to redistribute routes from BGP on Switch B. [SwitchB] ospf [SwitchB-ospf-1] import-route bgp # Configure OSPF to redistribute routes from BGP on Switch C.

  • Page 124: Ospf Stub Area Configuration Example

    11.2.1.0/24 Direct 0 11.2.1.2 Vlan100 11.2.1.0/32 Direct 0 11.2.1.2 Vlan100 11.2.1.2/32 Direct 0 127.0.0.1 InLoop0 11.2.1.255/32 Direct 0 11.2.1.2 Vlan100 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 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...
  • Page 125 OSPF Process 1 with Router ID 10.4.1.1 Routing Table to ABR and ASBR Topology base (MTID 0) 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 table on Switch C. <SwitchC>...

  • Page 126: Ospf Nssa Area Configuration Example

    [SwitchC] display ospf routing OSPF Process 1 with Router ID 10.4.1.1 Routing Table Topology base (MTID 0) Routing for network Destination Cost Type NextHop AdvRouter Area 0.0.0.0/0 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 Transit 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...
  • Page 127 • Configure OSPF on all switches and split AS into three areas. • Configure Switch A and Switch B as ABRs to forward routing information between areas. • Configure Area 1 as an NSSA area and configure Switch C as an ASBR to redistribute static routes into the AS.

  • Page 128: Ospf Dr Election Configuration Example

    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: 5 Intra area: 2 Inter area: 3 ASE: 0 NSSA: 0 Configure route redistribution: # Configure Switch C to redistribute static routes. [SwitchC] ip route-static 3.1.3.1 24 10.4.1.2 [SwitchC] ospf [SwitchC-ospf-1] import-route static [SwitchC-ospf-1] quit...
  • Page 129 Figure 29 Network diagram Switch A Switch B Vlan-int1 Vlan-int1 192.168.1.1/24 192.168.1.2/24 Vlan-int1 Vlan-int1 192.168.1.4/24 192.168.1.3/24 Switch D Switch C Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable OSPF: # Configure Switch A. <SwitchA> system-view [SwitchA] router id 1.1.1.1 [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255...
  • Page 130 # Display OSPF neighbor information on Switch A. [SwitchA] display ospf peer verbose OSPF Process 1 with Router ID 1.1.1.1 Neighbors Area 0.0.0.0 interface 192.168.1.1(Vlan-interface1)'s neighbors Router ID: 2.2.2.2 Address: 192.168.1.2 GR State: Normal State: 2-Way Mode: None Priority: 1 DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0...
  • Page 131 [SwitchC-Vlan-interface1] ospf dr-priority 2 [SwitchC-Vlan-interface1] quit # Display neighbor information on Switch D. <SwitchD> display ospf peer verbose OSPF Process 1 with Router ID 4.4.4.4 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 Address: 192.168.1.1 GR State: Normal State: Full Mode:Nbr is slave Priority: 100...
  • Page 132 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 Address: 192.168.1.1 GR State: Normal State: Full Mode: Nbr is slave Priority: 100 DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0 Options is 0x02 (-|-|-|-|-|-|E|-) Dead timer due in 39 Neighbor is up for 00:01:40 Authentication Sequence: [ 0 ] Neighbor state change count: 6 BFD status: Disabled...

  • Page 133: Ospf Virtual Link Configuration Example

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

  • Page 135: Ospf Gr Configuration Example

    Topology base (MTID 0) 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.3.1.0/24 Inter 10.2.1.2 3.3.3.3 0.0.0.0 10.1.1.0/24 Transit 10.1.1.2 2.2.2.2 0.0.0.0 Total nets: 3 Intra area: 2 Inter area: 1 ASE: 0 NSSA: 0 The output shows that Switch B has learned the route 10.3.1.0/24 to Area 2.
  • Page 136 [SwitchB] ospf 100 [SwitchB-ospf-100] area 0 [SwitchB-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255 [SwitchB-ospf-100-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C. <SwitchC> system-view [SwitchC] router id 3.3.3.3 [SwitchC] ospf 100 [SwitchC-ospf-100] area 0 [SwitchC-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255 [SwitchC-ospf-100-area-0.0.0.0] quit [SwitchC-ospf-1] quit Configure OSPF GR: # Configure Switch A as the non-IETF OSPF GR restarter: enable the link-local signaling capability, the out-of-band re-synchronization capability, and non-IETF GR capability for OSPF process 100.

  • Page 137: Ospf Nsr Configuration Example

    *Oct 21 15:29:28:766 2011 SwitchA OSPF/7/DEBUG: -MDC=1; OSPF 100 created OOB Progress timer for neighbor 192.1.1.2. %Oct 21 15:29:29:902 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor 192.1.1.2(Vlan-interface100) from Loading to Full. *Oct 21 15:29:29:902 2011 SwitchA OSPF/7/DEBUG: -MDC=1; OSPF 100 deleted OOB Progress timer for neighbor 192.1.1.2. %Oct 21 15:29:30:897 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1;...
  • Page 138 [SwitchS-ospf-100] quit Verifying the configuration # Perform an active/standby switchover on Switch S. [SwitchS] placement reoptimize Predicted changes to the placement Program Current location New location --------------------------------------------------------------------- slsp rib6 routepolicy staticroute6 staticroute eviisis ospf Continue? [y/n]:y Re-optimization of the placement start. You will be notified on completion Re-optimization of the placement complete.

  • Page 139: Bfd For Ospf Configuration Example

    Intra area: 4 Inter area: 0 ASE: 0 NSSA: 0 # Display OSPF neighbors on Switch B to verify the neighbor relationship between Switch B and Switch S. <SwitchB> display ospf peer OSPF Process 1 with Router ID 4.4.4.1 Neighbor Brief Information Area: 0.0.0.0 Router ID Address...
  • Page 140 Figure 33 Network diagram Switch A Switch B Vlan-int10 Vlan-int10 Loop0 Loop0 Vlan-int11 Vlan-int13 L2 Switch Area 0 Vlan-int11 Vlan-int13 Switch C Table 9 Interface and IP address assignment Device Interface IP address Switch A Vlan-int10 192.168.0.102/24 Switch A Vlan-int11 10.1.1.102/24 Switch A Loop0...
  • Page 141 # Configure Switch C. <SwitchC> system-view [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 13.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit Configure BFD: # Enable BFD on Switch A and configure BFD parameters. [SwitchA] bfd session init-mode active [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ospf bfd enable [SwitchA-Vlan-interface10] bfd min-transmit-interval 500...

  • Page 142: Ospf Frr Configuration Example

    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 BkLabel: NULL BkNextHop: N/A Tunnel ID: Invalid Interface: Vlan-interface10 BkTunnel ID: Invalid BkInterface: N/A FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A The output shows that Switch A communicates with Switch B through VLAN-interface 10.
  • Page 143 Figure 34 Network diagram Switch C Link B Link A Loop0 Loop0 Vlan-int200 Vlan-int200 Switch A Switch B Table 10 Interface and IP address assignment Device Interface IP address Switch A Vlan-int100 12.12.12.1/24 Switch A Vlan-int200 13.13.13.1/24 Switch A Loop0 1.1.1.1/32 Switch B Vlan-int101...
  • Page 144 [SwitchA-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface 100 backup-nexthop 12.12.12.2 [SwitchA-route-policy-frr-10] quit [SwitchA] ospf 1 [SwitchA-ospf-1] fast-reroute route-policy frr [SwitchA-ospf-1] quit # Configure Switch B. <SwitchB> system-view [SwitchB] ip prefix-list abc index 10 permit 1.1.1.1 32 [SwitchB] route-policy frr permit node 10 [SwitchB-route-policy-frr-10] if-match ip address prefix-list abc [SwitchB-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface 101 backup-nexthop 24.24.24.2...

  • Page 145: Troubleshooting Ospf Configuration

    Process ID: 1 SubProtID: 0x1 Age: 04h20m37s Cost: 1 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: 13.13.13.1 Label: NULL RealNextHop: 13.13.13.1 BkLabel: NULL...
  • Page 146 Analysis The backbone area must maintain connectivity to all other areas. If a router connects to more than one area, a minimum of one area must be connected to the backbone. The backbone cannot be configured as a stub area. In a stub area, all routers cannot receive external routes, and all interfaces connected to the stub area must belong to the stub area.

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

    Figure 35 NSAP address format HO-DSP System ID (6 octet) SEL (1 octet) Area address 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 149: 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 150: 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 151: Is-Is Pdus

    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. A pseudonode represents a virtual node on the broadcast network. It is not a real router. In IS-IS, it is identified by the system ID of the DIS and a 1-byte Circuit ID (a non-zero value).
  • Page 152 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. The LSPs carry link state information.

  • Page 153: Protocols And Standards

    CLV Code Name PDU Type Inter-Domain Routing Protocol Information L2 LSP IP Interface Address IIH, LSP MT-ISN M-Topologies IIH, LSP MT IP. Reach MT IPv6 IP. Reach Protocols and standards • ISO 10589 ISO IS-IS Routing Protocol • ISO 9542 ES-IS Routing Protocol •...

  • Page 154: Configuring Basic Is-Is

    Tasks at a glance (Optional.) Configuring IS-IS route control: • Configuring IS-IS link cost • Specifying a preference for IS-IS • Configuring the maximum number of ECMP routes • Configuring IS-IS route summarization • Advertising a default route • Configuring IS-IS route redistribution •...

  • Page 155: Enabling Is-Is

    Enabling IS-IS Step Command Remarks Enter system view. system-view isis [ process-id ] Enable IS-IS and enter IS-IS [ vpn-instance By default, IS-IS is disabled. view. vpn-instance-name ] Assign a NET. network-entity net By default, NET is not assigned. Return to system view. quit interface interface-type Enter interface view.

  • Page 156: Configuring Is-Is Route Control

    If only two routers exist on a broadcast network, set the network type of attached interfaces to P2P. This avoids DIS election and CSNP flooding, saving network bandwidth and speeding up network convergence. To configure P2P network type for an interface: Step Command Remarks...

  • Page 157: Specifying A Preference For Is-Is

    Configuring an 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 | (Optional.) Specify an By default, the IS-IS cost wide-compatible | { compatible | IS-IS cost style.

  • Page 158: Configuring The Maximum Number Of Ecmp Routes

    Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] Enter IS-IS IPv4 unicast cost-style { wide | address family view. wide-compatible } address-family ipv4 [ unicast ] Configure a preference for preference { preference | The default setting is 15.

  • Page 159: Advertising A Default Route

    Step Command Remarks summary ip-address { mask-length Configure IS-IS route | mask } [ avoid-feedback | By default, route summarization summarization. generate_null0_route | [ level-1 | is not configured. level-1-2 | level-2 ] | tag tag ] * Advertising a default route IS-IS cannot redistribute a default route to its neighbors.

  • Page 160: Configuring Is-Is Route Filtering

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

  • Page 161: Configuring Is-Is Route Leaking

    Step Command Remarks isis [ process-id ] [ vpn-instance vpn-instance-name ] Enter IS-IS IPv4 unicast cost-style { wide | address family view. wide-compatible } address-family ipv4 [ unicast ] filter-policy { ipv4-acl-number | Filter routes redistributed prefix-list prefix-list-name | By default, IS-IS route from other routing protocols route-policy route-policy-name } filtering is not configured.

  • Page 162: Tuning And Optimizing Is-Is Networks

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

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

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

  • Page 164: Enabling An Interface To Send Small Hello Packets

    Enabling an interface to send small hello packets IS-IS messages cannot be fragmented at the IP layer because they are directly encapsulated in frames. Any two IS-IS neighboring routers must negotiate a common MTU. To avoid sending big hellos to save bandwidth, enable the interface to send small hello packets without CLVs. To enable an interface to send small hello packets: Step Command...
  • Page 165 Step Command Remarks Specify the LSP refresh By default, the LSP refresh timer lsp-refresh seconds interval. interval is 900 seconds. By default: • The maximum interval timer lsp-generation is 5 seconds. maximum-interval Specify the LSP generation • The minimum interval [ minimum-interval interval.
  • Page 166 Step Command Remarks By default, the maximum Specify the maximum length lsp-length receive size length of received LSPs is of received LSPs. 1497 bytes. 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.

  • Page 167: Controlling Spf Calculation Interval

    Figure 41 Network diagram of a fully meshed network Router D Router A GE1/0/1 GE1/0/3 GE1/0/2 GE1/0/2 GE1/0/3 GE1/0/1 GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/2 GE1/0/3 GE1/0/3 Router B Router C To avoid this problem, you can add interfaces to a mesh group or block some interfaces. •...

  • Page 168: Configuring Convergence Priorities For Specific Routes

    Step Command Remarks By default: • The maximum interval is 5 seconds. timer spf maximum-interval Configure the SPF • [ minimum-interval The minimum interval is calculation interval. [ incremental-interval ] ] 50 milliseconds. • The incremental interval is 200 milliseconds. Configuring convergence priorities for specific routes A topology change causes IS-IS routing convergence.

  • Page 169: Configuring The Att Bit

    Step Command Remarks set-overload [ on-startup [ [ start-from-nbr system-id [ timeout1 By default, the overload bit is Set the overload bit. [ nbr-timeout ] ] ] | timeout2 | not set. wait-for-bgp [ timeout3 ] ] ] [ allow { external | interlevel } * ] Configuring the ATT bit A Level-1-2 router sends Level-1 LSPs with an ATT bit to inform the Level-1 routers that it can reach...

  • Page 170: Configuring System Id To Host Name Mappings

    Configuring system ID to host name mappings A 6-byte system ID in hexadecimal notation uniquely identifies a router or host in an IS-IS network. To make a system ID easy to read, the system allows you to use host names to identify devices. It also provides mappings between system IDs and host names.

  • Page 171: Enabling The Logging Of Neighbor State Changes

    Step Command Remarks By default, no DIS name is configured. This command takes effect only on Configure a DIS name. isis dis-name symbolic-name a router enabled with dynamic system ID to host name mapping. This command is not available on P2P interfaces.

  • Page 172: Configuring Is-Is Network Management

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, prefix suppression is disabled on the interface. Enable prefix suppression isis prefix-suppression This command is also on the interface. applicable to the secondary IP address of the interface. Configuring IS-IS network management This task includes the following configurations: •...

  • Page 173: Enhancing Is-Is Network Security

    When both IS-IS PIC and IS-IS FRR are configured, IS-IS FRR takes effect. IS-IS PIC applies only to LSPs sent by neighbors. Enabling IS-IS PIC Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view. vpn-instance-name ] By default, IS-IS PIC is Enable PIC for IS-IS.

  • Page 174: Configuration Prerequisites

    Configuration prerequisites Before the configuration, complete the following tasks: • Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes. • Enable IS-IS. Configuring neighbor relationship authentication With neighbor relationship authentication configured, an interface adds the key in the specified mode into hello packets to the peer and checks the key in the received hello packets.

  • Page 175: Configuring Routing Domain Authentication

    Step Command Remarks area-authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224 Specify the area | hmac-sha-256 | hmac-sha-384 | By default, no area authentication authentication mode and hmac-sha-512 } [ nonstandard ] | is configured. key. md5 | simple } { cipher | plain } string | keychain keychain-name } [ ip | osi ] (Optional.) Configure the interface not to check the...

  • Page 176: Configuring Is-Is Nsr

    Configure IS-IS GR on the GR restarter. GR restarter uses the following timers: • T1 timer—Specifies the times that GR restarter can send a Restart TLV with the RR bit set. When rebooted, the GR restarter sends a Restart TLV with the RR bit set to its neighbor. If the GR restarter receives a Restart TLV with the RA set from its neighbor before the T1 timer expires, the GR process starts.

  • Page 177: Configuring Bfd For Is-Is

    IMPORTANT: IS-IS NSR and IS-IS GR are mutually exclusive. Do not configure them at the same time. To configure IS-IS NSR: Step Command Remarks Enter system view. system-view isis [ process-id ] Enter IS-IS view. [ vpn-instance vpn-instance-name ] By default, IS-IS NSR is disabled. IS-IS NSR takes effect on a Enable IS-IS NSR.

  • Page 178: Configuration Prerequisites

    hop to reduce traffic recovery time. Meanwhile, IS-IS calculates the shortest path based on the new network topology, and forwards packets over the path after network convergence. You can assign a backup next hop for IS-IS FRR through the following ways: •...
  • Page 179 Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the interface (Optional.) Disable LFA isis fast-reroute lfa-backup participates in LFA calculation, calculation on the interface. exclude and can be elected as a backup interface. Return to system view.

  • Page 180: Displaying And Maintaining Is-Is

    Displaying and maintaining IS-IS Execute display commands in any view and the reset command in user view. Task Command Display IS-IS process information. display isis [ process-id ] (In standalone mode.) Display IS-IS display isis graceful-restart event-log slot slot-number GR log information. display isis graceful-restart event-log chassis chassis-number (In IRF mode.) Display IS-IS GR log information.

  • Page 181: Is-Is Configuration Examples

    Task Command (In standalone mode.) Clear IS-IS reset isis graceful-restart event-log slot slot-number GR log information. (In IRF mode.) Clear IS-IS GR log reset isis graceful-restart event-log chassis chassis-number slot information. slot-number (In standalone mode.) Clear IS-IS reset isis non-stop-routing event-log slot slot-number NSR log information.
  • Page 182 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] isis enable 1 [SwitchB-Vlan-interface200] quit # Configure Switch C.
  • Page 183 Level-1 Link State Database --------------------------- LSPID Seq Num Checksum Holdtime Length ATT/P/OL -------------------------------------------------------------------------- 0000.0000.0001.00-00* 0x00000004 0xdf5e 1096 0/0/0 0000.0000.0002.00-00 0x00000004 0xee4d 1102 0/0/0 0000.0000.0002.01-00 0x00000001 0xdaaf 1102 0/0/0 0000.0000.0003.00-00 0x00000009 0xcaa3 1161 1/0/0 0000.0000.0003.01-00 0x00000001 0xadda 1112 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload [SwitchB] display isis lsdb Database information for IS-IS(1) ---------------------------------...
  • Page 184 --------------------------- LSPID Seq Num Checksum Holdtime Length ATT/P/OL -------------------------------------------------------------------------- 0000.0000.0003.00-00* 0x00000012 0xc93c 0/0/0 0000.0000.0004.00-00 0x00000026 0x331 1173 0/0/0 0000.0000.0004.01-00 0x00000001 0xee95 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload [SwitchD] display isis lsdb Database information for IS-IS(1) --------------------------------- Level-2 Link State Database --------------------------- LSPID Seq Num...

  • Page 185: Dis Election Configuration Example

    IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 192.168.0.0/24 NULL Vlan300 Direct D/L/- 10.1.1.0/24 NULL Vlan100 Direct D/L/- 10.1.2.0/24 NULL Vlan200 Direct D/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop...
  • Page 186 Figure 44 Network diagram Switch A Switch B L1/L2 L1/L2 Vlan-int100 Vlan-int100 10.1.1.1/24 10.1.1.2/24 Vlan-int100 Vlan-int100 10.1.1.3/24 10.1.1.4/24 Switch C Switch D Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Enable IS-IS: # Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit...
  • Page 187 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 100 [SwitchD-Vlan-interface100] isis enable 1 [SwitchD-Vlan-interface100] quit # Display information about IS-IS neighbors on Switch A. [SwitchA] display isis peer Peer information for IS-IS(1) ---------------------------- System Id: 0000.0000.0002 Interface: Vlan-interface100 Circuit Id: 0000.0000.0003.01 State: Up HoldTime: 21s Type: L1(L1L2) PRI: 64...
  • Page 188 Interface: Vlan-interface100 Index IPv4.State IPv6.State CircuitID Type 00001 Down 1497 L1/L2 No/Yes The output shows that when the default DIS priority is used, Switch C is the DIS for Level-1, and Switch D is the DIS for Level-2. The pseudonodes of Level-1 and Level-2 are 0000.0000.0003.01 and 0000.0000.0004.01.

  • Page 189: Is-Is Route Redistribution Configuration Example

    Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 25s Type: L1 PRI: 64 System Id: 0000.0000.0001 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 7s Type: L1 PRI: 100 [SwitchC] display isis interface Interface information for IS-IS(1) ---------------------------------- Interface: Vlan-interface100 Index IPv4.State IPv6.State...
  • Page 190 Figure 45 Network diagram Switch A Vlan-int100 10.1.1.2/24 Vlan-int500 10.1.5.1/24 Vlan-int100 Vlan-int300 Vlan-int400 10.1.1.1/24 192.168.0.1/24 10.1.4.1/24 Vlan-int400 Vlan-int300 Vlan-int600 Vlan-int200 10.1.4.2/24 192.168.0.2/24 10.1.6.1/24 Switch C 10.1.2.1/24 Switch E Switch D L1/L2 Vlan-int200 10.1.2.2/24 Area 20 Switch B Area 10 Configuration procedure Configure IP addresses for interfaces.
  • Page 191 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit # Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] network-entity 20.0000.0000.0004.00 [SwitchD-isis-1] quit [SwitchD] interface interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit [SwitchD] interface interface vlan-interface 400 [SwitchD-Vlan-interface400] isis enable 1 [SwitchD-Vlan-interface400] quit # Display IS-IS routing information on each switch.
  • Page 192 ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 10.1.1.0/24 NULL D/L/- 10.1.2.0/24 NULL D/L/- 192.168.0.0/24 NULL D/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set [SwitchD] display isis route Route information for IS-IS(1) ------------------------------ Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost...

  • Page 193: Is-Is Authentication Configuration Example

    ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------- 10.1.1.0/24 NULL VLAN100 Direct D/L/- 10.1.2.0/24 NULL VLAN200 Direct D/L/- 192.168.0.0/24 NULL VLAN300 Direct D/L/- Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set Level-2 IPv4 Forwarding Table ----------------------------- IPv4 Destination IntCost ExtCost ExitInterface...
  • Page 194 Figure 46 Network diagram Switch A Vlan-int100 10.1.1.2/24 Vlan-int100 Vlan-int300 10.1.1.1/24 10.1.3.1/24 Vlan-int300 Vlan-int200 10.1.3.2/24 Switch C 10.1.2.1/24 Switch D L1/L2 Vlan-int200 10.1.2.2/24 Area 20 Switch B Area 10 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure basic IS-IS: # Configure Switch A.
  • Page 195 # Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] network-entity 20.0000.0000.0001.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit Configure neighbor relationship authentication between neighbors: # Set the authentication mode to MD5 and set the plaintext key to eRq on VLAN-interface 100 of Switch A and on VLAN-interface 100 of Switch C.

  • Page 196: Is-Is Gr Configuration Example

    [SwitchD] isis 1 [SwitchD-isis-1] domain-authentication-mode md5 plain 1020Sec IS-IS GR configuration example Network requirements As shown in Figure 47, Switch A, Switch B, and Switch C belong to the same IS-IS routing domain. Figure 47 Network diagram GR restarter Switch A Vlan-int100 10.0.0.1/24 Vlan-int100...

  • Page 197: Is-Is Nsr Configuration Example

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

  • Page 200: Bfd For Is-Is Configuration Example

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

  • Page 203: Is-Is Frr Configuration Example

    FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A The output shows that Switch A and Switch B communicate through VLAN-interface 10. Then the link over VLAN-interface 10 fails. # Display routes destined for 120.1.1.1/32 on Switch A. <SwitchA> display ip routing-table 120.1.1.1 verbose Summary Count : 1 Destination: 120.1.1.1/32 Protocol: IS_L1...
  • Page 204 Table 15 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int100 12.12.12.1/24 Switch B Vlan-int101 24.24.24.4/24 Vlan-int200 13.13.13.1/24 Vlan-int200 13.13.13.2/24 Loop0 1.1.1.1/32 Loop0 4.4.4.4/32 Switch C Vlan-int100 12.12.12.2/24 Vlan-int101 24.24.24.2/24 Configuration procedure Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.) Configure IS-IS on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at Layer 3.
  • Page 205 [SwitchB] ip prefix-list abc index 10 permit 1.1.1.1 32 [SwitchB] route-policy frr permit node 10 [SwitchB-route-policy-frr-10] if-match ip address prefix-list abc [SwitchB-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface 101 backup-nexthop 24.24.24.2 [SwitchB-route-policy-frr-10] quit [SwitchB] isis 1 [SwitchB-isis-1] address-family ipv4 [SwitchB-isis-1-ipv4] fast-reroute route-policy frr [SwitchB-isis-1-ipv4] quit [SwitchB-isis-1] quit Verifying the configuration...
  • Page 206 TableID: 0x2 OrigAs: 0 NibID: 0x26000002 LastAs: 0 AttrID: 0xffffffff Neighbor: 0.0.0.0 Flags: 0x1008c OrigNextHop: 13.13.13.1 Label: NULL RealNextHop: 13.13.13.1 BkLabel: NULL BkNextHop: 24.24.24.2 Tunnel ID: Invalid Interface: Vlan-interface200 BkTunnel ID: Invalid BkInterface: Vlan-interface101 FtnIndex: 0x0 TrafficIndex: N/A Connector: N/A...

  • Page 207: 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 208 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 ...
  • Page 209 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 ...
  • Page 210 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 211: 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 ...

  • Page 212: 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 213: Settlements For Problems In Large-Scale Bgp Networks

    Figure 55 Network diagram Router A Router D Router C AS 200 AS 100 9.0.0.0/24 Router B Router E 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.
  • Page 214 Figure 56 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 215 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 58.

  • Page 216: 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 217: 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 218 View names Ways to enter the views Remarks <Sysname> system-view [Sysname] bgp 100 instance abc Configurations in this view apply to BGP IPv4 multicast address IPv4 multicast routes and peers of [Sysname-bgp-abc] family view the specified BGP instance. address-family ipv4 multicast [Sysname-bgp-abc-mul-ipv4] <Sysname>...

  • Page 219: 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 [Sysname-bgp-abc-vpn1] specified BGP instance.

  • Page 220: Bgp Configuration Task List

    • RFC 5082, The Generalized TTL Security Mechanism (GTSM) • RFC 6037, Cisco Systems' Solution for Multicast in BGP MPLS IP VPNs BGP configuration task list On a basic BGP network, perform the following configuration tasks: • Enable BGP. • Configure BGP peers or peer groups.
  • Page 221 Tasks at a glance Remarks (Optional.) Tuning and optimizing BGP networks: • Configuring the keepalive interval and hold time • Setting the session retry timer • Configuring the interval for sending updates for the same route • Enabling BGP to establish an EBGP session over multiple hops •...
  • Page 222 Tasks at a glance Remarks Configuring basic BGP: • As a best practice, (Required.) Enabling BGP configure BGP peer • (Required.) Perform one of the following tasks: groups on large scale Configuring a BGP peer  BGP networks for easy Configuring dynamic BGP peers ...

  • Page 223: Configuring Basic Bgp

    Tasks at a glance Remarks (Optional.) Tuning and optimizing BGP networks: • Configuring the keepalive interval and hold time • Setting the session retry timer • Configuring the interval for sending updates for the same route • Enabling BGP to establish an EBGP session over multiple hops •...

  • Page 224: Enabling Bgp

    Enabling BGP A router ID is the unique identifier of a BGP router in an AS. • To ensure the uniqueness of a router ID and enhance availability, specify in BGP instance view the IP address of a local loopback interface as the router ID. Different BGP instances can have the same router ID.

  • Page 225: Configuring A Bgp Peer

    Configuring a BGP peer Configuring a BGP peer (IPv4 unicast address family) 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 226: Configuring Dynamic Bgp Peers

    Step Command Remarks Enable the router to By default, the router cannot exchange IPv6 unicast peer ipv6-address enable exchange IPv6 unicast routing routing information with the information with the peer. specified peer. Configuring a BGP peer (IPv4 multicast address family) Step Command Remarks...
  • Page 227 If multiple BGP peers reside in the same network, you can use this feature to simplify BGP peer configuration. For a remote device to establish a peer relationship with the local device, you must specify the IP address of the local device on the remote device. Configuring dynamic BGP peers (IPv4 unicast address family) Step Command...
  • Page 228 Step Command Remarks Create the BGP IPv6 By default, no BGP IPv6 unicast address family or unicast address family or BGP-VPN IPv6 unicast address-family ipv6 [ unicast ] BGP-VPN IPv6 unicast address family and enter address family exists. its view. Enable BGP to exchange By default, BGP cannot IPv6 unicast routing...

  • Page 229: Configuring A Bgp Peer Group

    Step Command Remarks Enable BGP to exchange By default, BGP cannot IPv6 unicast routing exchange IPv6 unicast routing information used for RPF peer ipv6-address prefix-length information used for RPF check with dynamic BGP enable check with dynamic BGP peers in the specified peers.
  • Page 230 To configure an IBGP peer group (IPv6 unicast address family): 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.
  • Page 231 Step Command Remarks Create the BGP IPv4 By default, no BGP IPv4 multicast multicast address family and address-family ipv4 multicast address family exists. enter its view. Enable the router to By default, the router cannot exchange IPv4 unicast exchange IPv4 unicast routing routing information used for peer group-name enable information used for RPF check...
  • Page 232 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 233 Step Command Remarks By default, no AS number is specified. Specify the AS number of the peer group-name as-number If a peer group contains peers, group. as-number you cannot remove or change its AS number. By default, no peers exist in the peer group.
  • Page 234 Step Command Remarks Enable the router to By default, the router cannot exchange IPv4 unicast exchange IPv4 unicast routing routing information used for peer group-name enable information used for RPF check RPF check with peers in the with the peers in the group. specified peer group.
  • Page 235 Step Command Remarks By default, no EBGP peer groups Create an EBGP peer group. group group-name external exist. Create an IPv4 BGP peer peer ipv4-address [ mask-length ] By default, no IPv4 BGP peers and specify its AS number. as-number as-number exist.
  • Page 236 Step Command Remarks (Optional.) Configure a peer group-name description By default, no description is description for the peer text configured for the peer group. group. Create the BGP IPv6 unicast By default, no BGP IPv6 unicast address family or BGP-VPN address-family ipv6 [ unicast ] address family or BGP-VPN IPv6 IPv6 unicast address family...
  • Page 237 Step Command Remarks Create an IPv6 BGP peer peer ipv6-address [ prefix-length ] By default, no IPv6 BGP peers and specify its AS number. as-number as-number exist. 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 238 To configure an EBGP peer group by using Method 3 (IPv6 unicast address family): 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 239: Specifying The Source Address Of Tcp Connections

    To configure an EBGP peer group by using Method 3 (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 240: Generating Bgp Routes

    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 Specify the source address peer { group-name | ipv4-address of TCP connections to a peer By default, BGP uses the primary...
  • Page 241 The specified network must be available and active in the local IP routing table. To inject a local network (IPv4 unicast/multicast address family): Step Command Remarks Enter system view. system-view • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b.

  • Page 242: 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 243 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 244: 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 245 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 c.
  • Page 246 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 247: 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...

  • Page 248: 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 249 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 250: Configuring Bgp To First Send Updates Of The Default Route

    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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...

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

    Figure 60 Network diagram Internet Device A Device B Device C Device D Device E Procedure Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] Configure BGP to first By default, BGP does not first send send updates of the default-route update-first updates of the default route.
  • Page 252 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 c.

  • Page 253: Configuring Bgp Route Filtering Policies

    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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 254 peer route-policy export Only routes passing all the configured policies can be advertised. To configure BGP route distribution filtering policies (IPv4 unicast/multicast address family): Step Command Remarks Enter system view. system-view • Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b.
  • Page 255 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 256 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 257 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 258 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 c.

  • Page 259: Setting The Bgp Route Sending Rate

    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 c. bgp as-number [ instance address family view, instance-name ] BGP-VPN IPv6 unicast...

  • Page 260: Configuring Bgp Route Update Delay

    For a device with high performance, you can set a high BGP route sending rate as needed. For a device without high performance, set a relatively low BGP route sending rate as a best practice. This task applies only to IPv4 unicast routes and IPv6 unicast routes. To set the BGP route sending rate: Step Command...

  • Page 261: Configuring Bgp Route Dampening

    Figure 61 Network diagram Router B IP network Router A Router C Procedure To configure a startup policy for BGP route updates: Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] Specify the period after bgp apply-policy on-startup By default, the startup policy reboot within which the...
  • Page 262 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 c. bgp as-number [ instance address family view, instance-name ] BGP-VPN IPv4 unicast...

  • Page 263: Controlling Bgp Path Selection

    Controlling BGP path selection By configuring BGP path attributes, you can control BGP path selection. Setting a preferred value for routes received Perform this task to set a preferred value for specific routes to control BGP path selection. Among multiple routes that have the same destination/mask and are learned from different peers, the one with the greatest preferred value is selected as the optimal route.

  • Page 264: Configuring Preferences For Bgp 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 266: Configuring The Default Local Preference

    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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 267 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 268: Configuring The Med Attribute

    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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 269 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...
  • 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 271 Figure 62 Route selection based on MED (in an IPv4 network) AS 400 Router E 10.0.0.0 AS 300 AS 200 Router C Router B Router A Loop0 Loop0 Loop0 3.3.3.3/32 1.1.1.1/32 2.2.2.2/32 GE1/0/1 GE1/0/1 GE1/0/1 13.1.1.2/24 12.1.1.2/24 11.1.1.2/24 GE1/0/1 GE1/0/3 GE1/0/2 Router D AS 100...

  • 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 63, 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...

  • Page 275: Configuring The As_Path Attribute

    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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 276 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...
  • Page 277 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...
  • Page 278 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 279 Figure 65 AS number substitution configuration (in an IPv4 network) AS 100 PE 1 PE 2 MPLS backbone EBGP_Update: 10.1.0.0/16 EBGP_Update: 10.1.0.0/16 VPNv4_Update: 10.1.0.0/16 AS_PATH: 100, 100 AS_PATH: 800 RD: 100:1 AS_PATH: 800 CE 1 CE 2 AS 800 AS 800 As shown in Figure 65, CE 1 and CE 2 use the same AS number 800.
  • Page 280 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 281: 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...

  • Page 282: 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 283: 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 284 • 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 285: Setting The Session Retry Timer

    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 286: Configuring The Interval For Sending Updates For The Same Route

    Configuring the interval for sending updates for the same route A BGP router sends an update message to its peers when a route is changed. If the route changes frequently, the BGP router keeps sending updates for the same route, resulting route flapping. To prevent this situation, perform this task to configure the interval for sending updates for the same route to a peer or peer group.

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

    Enabling BGP to establish an EBGP session over multiple hops To establish an EBGP session, two routers must have a direct physical link and use directly connected interfaces. If no direct link is available, you must use the peer ebgp-max-hop command to enable BGP to establish an EBGP session over multiple hops and specify the maximum hops.

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

    Enabling immediate re-establishment of direct EBGP connections upon link failure When the link to a directly connected EBGP peer goes down, the router does not re-establish a session to the peer until the hold time timer expires. This feature enables BGP to immediately recreate the session in that situation.
  • 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 c. bgp as-number [ instance address family view, instance-name ] BGP-VPN IPv4 unicast...

  • Page 290: Enabling 4-Byte As Number Suppression

    Enabling nonstandard BGP ORF capabilities 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.

  • Page 291: Enabling Md5 Authentication For Bgp Peers

    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 peer { group-name | ipv6-address Enable 4-byte AS number...

  • Page 292: Enabling Keychain 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 Enable MD5 authentication peer { group-name | ipv6-address By default, MD5 authentication is for a BGP peer group or...

  • Page 293: 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 keychain peer { group-name | ipv6-address By default, keychain authentication for a BGP...

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

    Step Command Remarks (Optional.) Enable load By default, BGP cannot perform balancing for routes that load balancing for routes that balance as-path-relax have different AS_PATH have different AS_PATH attributes of the same length. attributes of the same length. To specify the maximum number of BGP ECMP routes for load balancing (IPv6 unicast/multicast address family): Step Command...

  • Page 295: Configuring Gtsm For Bgp

    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 Disable BGP to establish a peer { group-name | ipv4-address...

  • Page 296: Configuring Bgp Soft-Reset

    To configure GTSM for BGP (IPv4 unicast/multicast address family): 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.
  • Page 297 • Manual soft-reset—Use the refresh bgp command to enable BGP to send local routing information or advertise a route-refresh message to the specified peer. The peer then resends its routing information. After receiving the routing information, the router filters the routing information by using the new policy.
  • 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 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 300 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 301 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 302: 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 multi-protocol extension, and Enable the BGP route a peer or peer group.

  • Page 303: 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 304: Setting A Dscp Value For Outgoing Bgp Packets

    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 305: Enabling Per-Prefix Label Allocation

    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 route recursion peer { group-name | ip-address By default, the route recursion policy control for routes...

  • Page 306: Configuring Bgp Community

    reflector, and confederation features as needed. For more information about configuring peer groups, "Configuring a BGP peer group." Configuring BGP community By default, a router does not advertise the COMMUNITY or extended community attribute to its peers or peer groups. When the router receives a route carrying the COMMUNITY or extended community attribute, it removes the attribute before advertising the route to other peers or peer groups.
  • Page 307 Step Command Remarks • Advertise the COMMUNITY attribute to a peer or peer group: peer { group-name | ipv4-address [ mask-length ] } Advertise the COMMUNITY By default, the COMMUNITY or advertise-community or extended community extended community attribute is • attribute to a peer or peer Advertise the extended not advertised.

  • Page 308: Configuring Bgp Route Reflection

    Step Command Remarks • Advertise the COMMUNITY attribute to a peer or peer group: peer { group-name | ipv6-address [ prefix-length ] } Advertise the COMMUNITY By default, the COMMUNITY or advertise-community or extended community extended community attribute is • attribute to a peer or peer Advertise the extended not advertised.
  • Page 309 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 c. bgp as-number address family view, [ instance BGP-VPN IPv4 unicast instance-name ]...
  • Page 310 Step Command Remarks • Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] Enter BGP IPv6 unicast b. address-family ipv6 address family view, or BGP [ unicast ] IPv6 multicast address family • Enter BGP IPv6 multicast view.

  • Page 311: Configuring A Bgp Confederation

    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, BGP does not ignore the ORIGINATOR_ID attribute.

  • Page 312: Configuring Bgp Gr

    Configuring confederation compatibility If any routers in the confederation do not comply with RFC 3065, enable confederation compatibility to allow the router to work with those routers. To configure confederation compatibility: Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view.

  • Page 313: Configuring Bgp Nsr

    As a best practice, perform the following configuration on the GR restarter and GR helper. To configure BGP GR: Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] By default, GR capability is Enable GR capability for BGP.

  • Page 314: Enabling Snmp Notifications For Bgp

    Enabling SNMP notifications for BGP After you enable SNMP notifications for BGP, the device generates a notification when a BGP neighbor state change occurs. The notification includes the neighbor address, the error code and subcode of the most recent error, and the current neighbor state. For BGP notifications to be sent correctly, you must also configure SNMP on the device.

  • Page 315: Enabling Logging For Bgp Route Flapping

    Step Command Remarks (Optional.) Enter BGP-VPN ip vpn-instance instance view. vpn-instance-name Enable logging for session By default, logging for session peer { group-name | ipv6-address state changes for a peer or state changes is enabled for all [ prefix-length ] } log-change peer group.

  • Page 316: Configuring Bfd For 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 c. bgp as-number address family view, [ instance BGP-VPN IPv6 unicast instance-name ]...

  • Page 317: Configuring Bgp Frr

    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 BFD to detect the link to the By default, BFD is [ mask-length ] } bfd [ multi-hop |...
  • Page 318 • Method 1—Execute the pic command in BGP address family view. BGP calculates a backup next hop for each BGP route in the address family if there are two or more unequal-cost routes that reach the destination. • Method 2—Execute the fast-reroute route-policy command to use a routing policy in which a backup next hop is specified by using the command apply [ ipv6 ] fast-reroute backup-nexthop.
  • Page 319 Step Command Remarks Enter BGP IPv4 unicast address family view or address-family ipv4 [ unicast ] BGP-VPN IPv4 unicast address family view. By default, BGP FRR is disabled. Method 1 might result in routing • (Method 1) Enable BGP FRR loops.

  • Page 320: Configuring 6Pe

    Step Command Remarks By default, BGP FRR is disabled. • (Method 1) Enable BGP Method 1 might result in routing loops. FRR for the address Use it with caution. family: By default, no routing policy is applied. • (Method 2) Apply a Enable BGP FRR.

  • Page 321: Configuring Optional 6Pe Capabilities

    • Configure BGP on 6PE devices so that they can advertise tagged IPv6 routing information through BGP sessions. The following describes only BGP configurations on 6PE devices. To configure basic 6PE: Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view.
  • Page 322 Step Command Remarks Specify an IPv6 prefix list to peer { group-name | ipv4-address filter routes advertised to or By default, no IPv6 prefix list is [ mask-length ] } prefix-list received from the 6PE peer specified. ipv6-prefix-name { export | import } or peer group.

  • Page 323: Configuring Bgp Ls

    Configuring BGP LS The BGP Link State (LS) feature implements inter-domain and inter-AS advertisement of link state database (LSDB) and TE database (TEDB) information. The device sends the collected link state information to the controller, which implements end-to-end traffic management and scheduling, and meets the requirements of intended applications. Configuring basic BGP LS Step Command...

  • Page 324: Specifying An As Number And A Router Id For Bgp Ls Messages

    Specifying an AS number and a router ID for BGP LS messages Perform this task to ensure that LS messages sent by devices in the same AS have the same AS number and router ID. To specify an AS number and a router ID for BGP LS messages: Step Command Remarks...

  • Page 325: Displaying And Maintaining Bgp

    Displaying and maintaining BGP Displaying BGP Execute display commands in any view (IPv4 unicast address family). 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.
  • Page 326 Execute display commands in any view (IPv6 unicast address family). Task Command display bgp [ instance instance-name ] non-stop-routing Display BGP NSR status information. status display bgp [ instance instance-name ] group ipv6 [ unicast ] Display BGP IPv6 unicast peer group [ vpn-instance vpn-instance-name ] [ group-name information.
  • Page 327 Task Command display bgp [ instance instance-name ] peer ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] ipv6-address received Display ORF prefix information received prefix-list by a peer. display bgp [ instance instance-name ] peer ipv6 [ unicast ] ipv4-address received prefix-list Execute display commands in any view (IPv4 multicast address family).
  • Page 328 Task Command display bgp [ instance instance-name ] non-stop-routing Display BGP NSR status information. status Display BGP IPv6 multicast peer group display bgp [ instance instance-name ] group ipv6 multicast information. [ group-name group-name ] display bgp [ instance instance-name ] peer ipv6 multicast Display BGP IPv6 multicast peer or peer [ ipv6-address prefix-length | { ipv6-address | group-name group information.

  • Page 329: Resetting Bgp Sessions

    Task Command display bgp [ instance instance-name ] routing-table ipv4 rtfilter [ default-rt [ advertise-info ] | [ origin-as as-number ] Display BGP IPv4 RT filter routing [ route-target [ advertise-info ] ] | peer ipv4-address information. { advertised-routes | received-routes } [ default-rt | [ origin-as as-number ] [ route-target ] | statistics ] | statistics ] Resetting BGP sessions...

  • Page 330: Ipv4 Bgp Configuration Examples

    Task Command reset bgp [ instance instance-name ] flap-info ipv6 [ unicast ] Clear flap information for BGP IPv6 [ vpn-instance vpn-instance-name ] [ ipv6-address unicast routes. prefix-length | as-path-acl as-path-acl-number | peer ipv6-address [ prefix-length ] ] Clear dampening information for BGP reset bgp [ instance instance-name ] dampening ipv4 IPv4 multicast routes and release multicast [ ipv4-address [ mask-length | mask] ]...
  • Page 331 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure IBGP: # Configure Switch B. <SwitchB> system-view [SwitchB] bgp 65009 [SwitchB-bgp-default] router-id 2.2.2.2 [SwitchB-bgp-default] peer 3.3.3.3 as-number 65009 [SwitchB-bgp-default] peer 3.3.3.3 connect-interface loopback 0 [SwitchB-bgp-default] address-family ipv4 unicast [SwitchB-bgp-default-ipv4] peer 3.3.3.3 enable [SwitchB-bgp-default-ipv4] quit [SwitchB-bgp-default] quit [SwitchB] ospf 1...
  • Page 332 <SwitchA> system-view [SwitchA] bgp 65008 [SwitchA-bgp-default] router-id 1.1.1.1 [SwitchA-bgp-default] peer 3.1.1.1 as-number 65009 [SwitchA-bgp-default] address-family ipv4 unicast [SwitchA-bgp-default-ipv4] peer 3.1.1.1 enable [SwitchA-bgp-default-ipv4] network 8.1.1.0 24 [SwitchA-bgp-default-ipv4] quit [SwitchA-bgp-default] quit # Configure Switch B. [SwitchB] bgp 65009 [SwitchB-bgp-default] peer 3.1.1.2 as-number 65008 [SwitchB-bgp-default] address-family ipv4 unicast [SwitchB-bgp-default-ipv4] peer 3.1.1.2 enable [SwitchB-bgp-default-ipv4] quit...
  • Page 333 BGP local router ID is 2.2.2.2 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf...

  • Page 334: Bgp And Igp Route Redistribution Configuration Example

    Two routes, 2.2.2.2/32 and 9.1.1.0/24, have been added in Switch A's routing table. # Display the BGP routing table on Switch C. [SwitchC] display bgp routing-table ipv4 Total number of routes: 4 BGP local router ID is 3.3.3.3 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network...

  • Page 335: Configuration Considerations

    Configuration considerations Configure BGP to redistribute routes from OSPF on Switch B, so Switch A can obtain the route to 9.1.2.0/24. Configure OSPF to redistribute routes from BGP on Switch B, so Switch C can obtain the route to 8.1.1.0/24. Configuration procedure Configure IP addresses for interfaces.
  • Page 336 [SwitchB-bgp-default] quit [SwitchB] ospf 1 [SwitchB-ospf-1] import-route bgp [SwitchB-ospf-1] quit # Display the BGP routing table on Switch A. [SwitchA] 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: Bgp Route Summarization Configuration Example

    round-trip min/avg/max/std-dev = 2.000/8.000/12.000/3.406 ms [SwitchC] ping -a 9.1.2.1 8.1.1.1 Ping 8.1.1.1 (8.1.1.1) from 9.1.2.1: 56 data bytes, press CTRL_C to break 56 bytes from 8.1.1.1: icmp_seq=0 ttl=254 time=9.000 ms 56 bytes from 8.1.1.1: icmp_seq=1 ttl=254 time=4.000 ms 56 bytes from 8.1.1.1: icmp_seq=2 ttl=254 time=3.000 ms 56 bytes from 8.1.1.1: icmp_seq=3 ttl=254 time=3.000 ms 56 bytes from 8.1.1.1: icmp_seq=4 ttl=254 time=3.000 ms --- Ping statistics for 8.1.1.1 ---...
  • Page 338 # 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 Switch B. <SwitchB> system-view [SwitchB] ip route-static 192.168.64.0 24 192.168.212.161 [SwitchB] ip route-static 192.168.74.0 24 192.168.212.161 [SwitchB] ip route-static 192.168.99.0 24 192.168.212.161 Configure OSPF between Switch B and Switch C and configure OSPF on Switch B to redistribute static routes: # Configure OSPF to advertise the local network and enable OSPF to redistribute static routes on Switch B.
  • Page 339 [SwitchC-bgp-default] router-id 3.3.3.3 [SwitchC-bgp-default] peer 10.220.2.217 as-number 64631 [SwitchC-bgp-default] address-family ipv4 unicast [SwitchC-bgp-default-ipv4] peer 10.220.2.217 enable [SwitchC-bgp-default-ipv4] import-route ospf # Enable BGP, and configure Switch C as an EBGP peer on Switch D. [SwitchD] bgp 64631 [SwitchD-bgp-default] router-id 4.4.4.4 [SwitchD-bgp-default] peer 10.220.2.16 as-number 65106 [SwitchD-bgp-default] address-family ipv4 unicast [SwitchD-bgp-default-ipv4] peer 10.220.2.16 enable [SwitchD-bgp-default-ipv4] quit...

  • Page 340: Bgp Load Balancing Configuration Example

    [SwitchD] display ip routing-table protocol bgp Summary count : 1 BGP Routing table Status : <Active> Summary count : 1 Destination/Mask Proto Cost NextHop Interface 192.168.64.0/18 10.220.2.16 Vlan200 BGP Routing table Status : <Inactive> Summary count : 0 The output shows that Switch D has only one route 192.168.64.0/18 to AS 65106. # Verify that Switch D can ping the hosts on networks 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24.
  • Page 341 • Configure a static route to interface loopback 0 on Switch C (or use a routing protocol like OSPF) to establish the IBGP connection. On Switch C: • Establish an EBGP connection with Switch A and an IBGP connection with Switch B. •...
  • Page 342 [SwitchC-bgp-default-ipv4] peer 2.2.2.2 enable [SwitchC-bgp-default-ipv4] network 9.1.1.0 24 [SwitchC-bgp-default-ipv4] quit [SwitchC-bgp-default] quit [SwitchC] ip route-static 2.2.2.2 32 9.1.1.1 # Display the BGP routing table on Switch A. [SwitchA] display bgp routing-table ipv4 Total number of routes: 3 BGP local router ID is 1.1.1.1 Status codes: * - valid, >...

  • Page 343: Bgp Community Configuration Example

    * > 8.1.1.0/24 8.1.1.1 32768 * >e 9.1.1.0/24 3.1.1.1 65009i * >e 3.1.2.1 65009i • The route 9.1.1.0/24 has two next hops, 3.1.1.1 and 3.1.2.1, both of which are marked with a greater-than sign (>), indicating that they are the optimal routes. •...
  • Page 344 [SwitchB-bgp-default-ipv4] peer 200.1.2.1 enable [SwitchB-bgp-default-ipv4] peer 200.1.3.2 enable [SwitchB-bgp-default-ipv4] quit [SwitchB-bgp-default] quit # Configure Switch C. <SwitchC> system-view [SwitchC] bgp 30 [SwitchC-bgp-default] router-id 3.3.3.3 [SwitchC-bgp-default] peer 200.1.3.1 as-number 20 [SwitchC-bgp-default] address-family ipv4 unicast [SwitchC-bgp-default-ipv4] peer 200.1.3.1 enable [SwitchC-bgp-default-ipv4] quit [SwitchC-bgp-default] quit # Display the BGP routing table on Switch B.
  • Page 345 Total number of routes: 1 BGP local router ID is 3.3.3.3 Status codes: * - valid, > - best, d - dampened, h - history, s - suppressed, S - stale, i - internal, e - external Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf...

  • Page 346: Bgp Route Reflector Configuration Example

    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: Not advertised to any peers yet # Display the BGP routing table on Switch C. [SwitchC] display bgp routing-table ipv4 Total number of routes: 0 The output shows that BGP has not learned any route.
  • Page 347 # Configure Switch B. <SwitchB> system-view [SwitchB] bgp 200 [SwitchB-bgp-default] router-id 2.2.2.2 [SwitchB-bgp-default] peer 192.1.1.1 as-number 100 [SwitchB-bgp-default] peer 193.1.1.1 as-number 200 [SwitchB-bgp-default] address-family ipv4 unicast [SwitchB-bgp-default-ipv4] peer 192.1.1.1 enable [SwitchB-bgp-default-ipv4] peer 193.1.1.1 enable [SwitchB-bgp-default-ipv4] peer 193.1.1.1 next-hop-local [SwitchB-bgp-default-ipv4] quit [SwitchB-bgp-default] quit # Configure Switch C.

  • Page 348: Bgp Confederation Configuration Example

    Origin: i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn * >e 20.0.0.0 192.1.1.1 100i # Display the BGP routing table on Switch D. [SwitchD] display bgp routing-table ipv4 Total number of routes: 1 BGP local router ID is 4.4.4.4 Status codes: * - valid, >...
  • Page 349 Device Interface IP address Device Interface IP address Vlan-int500 10.1.4.1/24 Switch F Vlan-int100 200.1.1.2/24 Switch B Vlan-int200 10.1.1.2/24 Vlan-int600 9.1.1.1/24 Switch C Vlan-int300 10.1.2.2/24 Configuration procedure Configure IP addresses for interfaces. (Details not shown.) Configure BGP confederation: # Configure Switch A. <SwitchA>...
  • Page 350 # Configure Switch A. [SwitchA] bgp 65001 [SwitchA-bgp-default] peer 10.1.3.2 as-number 65001 [SwitchA-bgp-default] peer 10.1.4.2 as-number 65001 [SwitchA-bgp-default] address-family ipv4 unicast [SwitchA-bgp-default-ipv4] peer 10.1.3.2 enable [SwitchA-bgp-default-ipv4] peer 10.1.4.2 enable [SwitchA-bgp-default-ipv4] peer 10.1.3.2 next-hop-local [SwitchA-bgp-default-ipv4] peer 10.1.4.2 next-hop-local [SwitchA-bgp-default-ipv4] quit [SwitchA-bgp-default] quit # Configure Switch D.
  • Page 351 [SwitchF-bgp-default] address-family ipv4 unicast [SwitchF-bgp-default-ipv4] peer 200.1.1.1 enable [SwitchF-bgp-default-ipv4] network 9.1.1.0 255.255.255.0 [SwitchF-bgp-default-ipv4] quit [SwitchF-bgp-default] quit Verifying the configuration # Display the routing table on Switch B. [SwitchB] display bgp routing-table ipv4 Total number of routes: 1 BGP local router ID is 2.2.2.2 Status codes: * - valid, >...

  • Page 352: Bgp Path Selection Configuration Example

    Network NextHop LocPrf PrefVal Path/Ogn * >i 9.1.1.0/24 10.1.3.1 100i [SwitchD] display bgp routing-table ipv4 9.1.1.0 BGP local router ID: 4.4.4.4 Local AS number: 65001 Paths: 1 available, 1 best BGP routing table information of 9.1.1.0/24: From : 10.1.3.1 (1.1.1.1) Rely nexthop : 10.1.3.1 Original nexthop: 10.1.3.1...
  • Page 353 Figure 75 Network diagram AS 200 Vlan-int100 Vlan-int300 AS 100 Switch B Vlan-int101 Vlan-int300 Vlan-int100 Vlan-int400 Vlan-int200 Switch D Vlan-int400 Switch A Vlan-int200 Switch C Table 18 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int101 1.0.0.1/8...
  • Page 354 [SwitchD-ospf-1-area-0.0.0.0] quit [SwitchD-ospf-1] quit Configure BGP connections: # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 100 [SwitchA-bgp-default] peer 192.1.1.2 as-number 200 [SwitchA-bgp-default] peer 193.1.1.2 as-number 200 [SwitchA-bgp-default] address-family ipv4 unicast [SwitchA-bgp-default-ipv4] peer 192.1.1.2 enable [SwitchA-bgp-default-ipv4] peer 193.1.1.2 enable # Inject network 1.0.0.0/8 to the BGP routing table on Switch A. [SwitchA-bgp-default-ipv4] network 1.0.0.0 8 [SwitchA-bgp-default-ipv4] quit [SwitchA-bgp-default] quit...

  • Page 355: Bgp Gr Configuration Example

    # Configure a routing policy named localpref on Switch C, setting the local preference of route 1.0.0.0/8 to 200 (the default is 100). [SwitchC] route-policy localpref permit node 10 [SwitchC-route-policy-localpref-10] if-match ip address acl 2000 [SwitchC-route-policy-localpref-10] apply local-preference 200 [SwitchC-route-policy-localpref-10] quit # Apply routing policy localpref to routes from peer 193.1.1.1.
  • Page 356 <SwitchA> system-view [SwitchA] bgp 65008 [SwitchA-bgp-default] router-id 1.1.1.1 [SwitchA-bgp-default] peer 200.1.1.1 as-number 65009 # Enable GR capability for BGP. [SwitchA-bgp-default] graceful-restart # Inject network 8.0.0.0/8 to the BGP routing table. [SwitchA-bgp-default] address-family ipv4 [SwitchA-bgp-default-ipv4] network 8.0.0.0 # Enable Switch A to exchange IPv4 unicast routing information with Switch B. [SwitchA-bgp-default-ipv4] peer 200.1.1.1 enable Configure Switch B: # Configure IP addresses for interfaces.

  • Page 357: Bfd For Bgp Configuration Example

    BFD for BGP configuration example Network requirements As shown in Figure 77, configure OSPF as the IGP in AS 200. • Establish two IBGP connections between Switch A and Switch C. When both paths operate correctly, Switch C uses the path Switch A<—>Switch B<—>Switch C to exchange packets with network 1.1.1.0/24.
  • Page 358 [SwitchA-bgp-default-ipv4] peer 2.0.2.2 enable [SwitchA-bgp-default-ipv4] quit [SwitchA-bgp-default] quit # Create IPv4 basic ACL 2000 to permit 1.1.1.0/24 to pass. [SwitchA] acl basic 2000 [SwitchA-acl-ipv4-basic-2000] rule permit source 1.1.1.0 0.0.0.255 [SwitchA-acl-ipv4-basic-2000] quit # Create two routing policies to set the MED for route 1.1.1.0/24. The policy apply_med_50 sets the MED to 50, and the policy apply_med_100 sets the MED to 100.
  • Page 359 Local Discr: 513 Remote Discr: 513 Source IP: 3.0.2.2 Destination IP: 3.0.1.1 Session State: Up Interface: N/A Min Tx Inter: 500ms Act Tx Inter: 500ms Min Rx Inter: 500ms Detect Inter: 2500ms Rx Count: 135 Tx Count: 135 Connect Type: Indirect Running Up for: 00:00:58 Hold Time: 2457ms Auth mode: None...

  • Page 360: Bgp Frr Configuration Example

    Connector: N/A The output shows that Switch C communicates with network 1.1.1.0/24 through the path Switch C<—>Switch B<—>Switch A. # Break down the path Switch C<—>Switch B<—>Switch A and then display route 1.1.1.0/24 on Switch C. <SwitchC> display ip routing-table 1.1.1.0 24 verbose Summary count : 1 Destination: 1.1.1.0/24 Protocol: BGP...
  • Page 361 Figure 78 Network diagram Loop0 2.2.2.2/32 Vlan-int 100 Vlan-int 101 AS 200 10.1.1.2/24 20.1.1.2/24 Switch B Vlan-int 100 Vlan-int 101 10.1.1.1/24 20.1.1.4/24 Switch A Switch D Link B AS 100 Vlan-int 200 Vlan-int 201 Link A 30.1.1.1/24 40.1.1.4/24 Switch C Vlan-int 200 Vlan-int 201 30.1.1.3/24...
  • Page 362 # Configure Switch C to establish an EBGP session to Switch A, and an IBGP session to Switch <SwitchC> system-view [SwitchC] bgp 200 [SwitchC-bgp-default] router-id 3.3.3.3 [SwitchC-bgp-default] peer 30.1.1.1 as-number 100 [SwitchC-bgp-default] peer 4.4.4.4 as-number 200 [SwitchC-bgp-default] peer 4.4.4.4 connect-interface loopback 0 [SwitchC-bgp-default] address-family ipv4 unicast [SwitchC-bgp-default-ipv4] peer 30.1.1.1 enable [SwitchC-bgp-default-ipv4] peer 4.4.4.4 enable...
  • Page 363 [SwitchA-bgp-default] primary-path-detect bfd echo # Apply the routing policy to BGP FRR for BGP IPv4 unicast address family. [SwitchA-bgp-default] address-family ipv4 unicast [SwitchA-bgp-default-ipv4] fast-reroute route-policy frr [SwitchA-bgp-default-ipv4] quit [SwitchA-bgp-default] quit # On Switch D, set the source address of BFD echo packets to 44.1.1.1. [SwitchD] bfd echo-source-ip 44.1.1.1 # Create routing policy frr to set a backup next hop 3.3.3.3 (Switch C) for the route destined for 1.1.1.1/32.

  • Page 364: Multicast Bgp Configuration Example

    # Display detailed information about the route to 1.1.1.1/32 on Switch D. The output shows the backup next hop for the route. [SwitchD] display ip routing-table 1.1.1.1 32 verbose Summary count : 1 Destination: 1.1.1.1/32 Protocol: BGP Process ID: 0 SubProtID: 0x1 Age: 00h00m36s Cost: 0...
  • Page 365 Figure 79 Network diagram AS 100 AS 200 Loop0 Loop0 Switch B Vlan-int101 Vlan-int101 Switch A Receiver Vlan-int100 Source Switch D Vlan-int104 Switch C Vlan-int104 PIM-SM 1 Loop0 Loop0 PIM-SM 2 MBGP peers Table 20 Interface and IP address assignment Device Interface IP address...
  • Page 366 [SwitchC] multicast routing [SwitchA-mrib] quit # Enable PIM-SM on interfaces, and enable IGMP on VLAN-interface 200. [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim sm [SwitchC-Vlan-interface104] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] pim sm [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] quit # Configure the BSR boundary on Switch A.
  • Page 367 [SwitchA-bgp-default-mul-ipv4] peer 192.168.1.2 enable # Redistribute direct routes into BGP. [SwitchA-bgp-default-mul-ipv4] import-route direct [SwitchA-bgp-default-mul-ipv4] quit [SwitchA-bgp-default] quit # On Switch B, establish an EBGP session to Switch A. [SwitchB] bgp 200 [SwitchB-bgp-default] router-id 2.2.2.2 [SwitchB-bgp-default] peer 192.168.1.1 as-number 100 # Enable exchange of IPv4 unicast routes used for RPF check with Switch B. [SwitchB-bgp-default] address-family ipv4 multicast [SwitchB-bgp-default-mul-ipv4] peer 192.168.1.1 enable # Redistribute OSPF routes into BGP.

  • Page 368: Dynamic Bgp Peer Configuration Example

    Dynamic BGP peer configuration example Network requirements As shown in Figure 80, Switch A needs to establish IBGP peer relationships with Switch B, Switch C, and Switch D in network 10.1.0.0/16. Configure dynamic BGP peers to simplify the configuration. Configure Switch A as the route reflector, and configure Switch B, Switch C, and Switch D as its clients.
  • Page 369 [SwitchC-bgp-default] peer 10.1.2.1 as-number 200 [SwitchC-bgp-default] address-family ipv4 [SwitchC-bgp-default-ipv4] peer 10.1.2.1 enable # Configure Switch D to establish an IBGP peer relationship with Switch A. <SwitchD> system-view [SwitchD] bgp 200 [SwitchD-bgp-default] router-id 4.4.4.4 [SwitchD-bgp-default] peer 10.1.3.1 as-number 200 [SwitchD-bgp-default] address-family ipv4 [SwitchD-bgp-default-ipv4] peer 10.1.3.1 enable # Display BGP peer information on Switch A.

  • Page 370: Bgp Ls Configuration Example

    BGP LS configuration example Network requirements As shown in Figure 81, all switches run BGP. Run IBGP between Switch A and Switch B, between Switch B and Switch C, and between Switch B and Switch D. Configure Switch B as a route reflector with client Switch A to allow Switch A to learn LS information advertised by Switch C and Switch D.
  • Page 371 [SwitchC-bgp-default-ls] peer 193.1.1.2 enable [SwitchC-bgp-default-ls] quit [SwitchC-bgp-default] quit [SwitchC] ospf [SwitchC-ospf-1] distribute bgp-ls [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 0.0.0.0 0.0.0.0 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Configure Switch D. <SwitchD> system-view [SwitchD] bgp 100 [SwitchD-bgp-default] peer 194.1.1.2 as-number 100 [SwitchD-bgp-default] address-family link-state [SwitchD-bgp-default-ls] peer 194.1.1.2 enable [SwitchD-bgp-default-ls] quit [SwitchD-bgp-default] quit...

  • Page 372: Ipv6 Bgp Configuration Examples

    Path/Ogn: i i Network : [V][O][I0x0][N[c100][b194.1.1.1][a0.0.0.0][r194.1.1.1]]/376 NextHop : 194.1.1.1 LocPrf : 100 PrefVal : 0 OutLabel : NULL 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...
  • Page 373 # Configure Switch C. <SwitchC> system-view [SwitchC] bgp 65009 [SwitchC-bgp-default] router-id 3.3.3.3 [SwitchC-bgp-default] peer 9::1 as-number 65009 [SwitchC-bgp-default] address-family ipv6 [SwitchC-bgp-default-ipv6] peer 9::1 enable Configure EBGP: # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 65008 [SwitchA-bgp-default] router-id 1.1.1.1 [SwitchA-bgp-default] peer 10::1 as-number 65009 [SwitchA-bgp-default] address-family ipv6 [SwitchA-bgp-default-ipv6] peer 10::1 enable # Configure Switch B.
  • Page 374 The output shows that Switch A and Switch B have established an EBGP connection, and Switch B and Switch C have established an IBGP connection. # Display IPv6 BGP routing table information on Switch A. [SwitchA] display bgp routing-table ipv6 Total number of routes: 4 BGP local router ID is 1.1.1.1 Status codes: * - valid, >...

  • Page 375: Ipv6 Bgp Route Reflector Configuration Example

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

  • Page 378: 6Pe Configuration Example

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

  • Page 381: Bfd For Ipv6 Bgp Configuration Example

    BFD for IPv6 BGP configuration example Network requirements As shown in Figure 85, configure OSPFv3 as the IGP in AS 200. • Establish two IBGP connections between Switch A and Switch C. When both paths operate correctly, Switch C uses the path Switch A<—>Switch B<—>Switch C to exchange packets with network 1200::0/64.
  • Page 382 [SwitchA-bgp-default-ipv6] peer 2001::3 enable [SwitchA-bgp-default-ipv6] quit # Create IPv6 basic ACL 2000 to permit 1200::0/64 to pass. [SwitchA] acl ipv6 basic 2000 [SwitchA-acl-ipv6-basic-2000] rule permit source 1200:: 64 [SwitchA-acl-ipv6-basic-2000] quit # Create two routing policies to set the MED for route 1200::0/64. The policy apply_med_50 sets the MED to 50, and the policy apply_med_100 sets the MED to 100.
  • Page 383 Local Discr: 513 Remote Discr: 513 Source IP: 3001::3 Destination IP: 3000::1 Session State: Up Interface: N/A Min Tx Inter: 500ms Act Tx Inter: 500ms Min Rx Inter: 500ms Detect Inter: 2500ms Rx Count: 13 Tx Count: 14 Connect Type: Indirect Running Up for: 00:00:05 Hold Time: 2243ms Auth mode: None...

  • Page 384: Ipv6 Bgp Frr Configuration Example

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

  • Page 388: Ipv6 Multicast Bgp Configuration Example

    IPv6 multicast BGP configuration example Network requirements As shown in Figure 87, OSPFv3 runs within AS 100 and AS 200 to ensure intra-AS connectivity. IPv6 MBGP runs between the two ASs to exchange IPv6 unicast routes used for RPF check. Enable Anycast RP on Switch A and Switch B.
  • Page 389 [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface loopback 0 [SwitchA-LoopBack0] ipv6 pim sm [SwitchA-LoopBack0] quit # Configure Switch B and Switch D in the same way that Switch A was configured. # On Switch C, enable IPv6 multicast routing globally. <SwitchC>...
  • Page 390 [SwitchA] bgp 100 [SwitchA-bgp-default] router-id 1.1.1.1 [SwitchA-bgp-default] peer 1001::2 as-number 200 # Enable exchange of IPv6 unicast routes used for RPF check with Switch B. [SwitchA-bgp-default] address-family ipv6 multicast [SwitchA-bgp-default-mul-ipv6] peer 1001::2 enable # Redistribute direct routes into BGP. [SwitchA-bgp-default-mul-ipv6] import-route direct [SwitchA-bgp-default-mul-ipv6] quit # On Switch B, establish an EBGP session to Switch A.

  • Page 391: Troubleshooting Bgp

    [SwitchB] display ipv6 multicast rpf-info 1002::1 RPF information about source 1002::1: RPF interface: Vlan-interface101, RPF neighbor: 1001::1 Referenced prefix/prefix length: 1002::/64 Referenced route type: mbgp Route selection rule: preference-preferred Load splitting rule: disable 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.

  • Page 392: Configuring Pbr

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

  • Page 393: Pbr And Track

    • apply default-next-hop Table 23 Priorities and meanings of apply clauses Clause Meaning Priority apply precedence Sets an IP precedence. This clause is always executed. apply next-hop and apply Sets next hops and sets Only the apply next-hop clause is executed output-interface output interfaces.

  • Page 394: Pbr Configuration Task List

    PBR configuration task list Tasks at a glance (Required.) Configuring a policy: • Creating a node • Setting match criteria for a node • Configuring actions for a node (Required.) Configuring PBR: • Configuring local PBR • Configuring interface PBR Configuring a policy Creating a node Step...

  • Page 395: Configuring Actions For A Node

    Configuring actions for a node Step Command Remarks Enter system system-view view. Enter policy policy-based-route policy-name [ deny | node view. permit ] node node-number Set an IP By default, no IP precedence is apply precedence { type | value } precedence.

  • Page 396: Configuring Interface Pbr

    Local PBR might affect local services, such as ping and Telnet. Do not configure local PBR unless doing so is required. To configure local PBR: Step Command Remarks Enter system view. system-view ip local policy-based-route By default, no policy is locally Apply a policy locally.

  • Page 397: Pbr Configuration Examples

    PBR configuration examples Packet type-based local PBR configuration example Network requirements As shown in Figure 88, configure PBR on Switch A to forward all TCP packets to the next hop 1.1.2.2. Switch A forwards other packets according to the routing table. Figure 88 Network diagram Switch B Vlan-int10...

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

    # Configure the IP address of VLAN-interface 10. [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ip address 1.1.2.2 24 Configure Switch C: # Create VLAN 20. <SwitchC> system-view [SwitchC] vlan 20 [SwitchC-vlan20] quit # Configure the IP address of VLAN-interface 20. [SwitchC] interface vlan-interface 20 [SwitchC-Vlan-interface20] ip address 1.1.3.2 24 Verifying the configuration # Telnet to Switch B on Switch A.
  • Page 399 Figure 89 Network diagram Switch B Switch C Vlan-int10 Vlan-int20 1.1.2.2/24 1.1.3.2/24 Vlan-int10 Vlan-int20 1.1.2.1/24 1.1.3.1/24 Switch A Vlan-int11 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 Configure Switch A: # Create VLAN 10 and VLAN 20. <SwitchA>...

  • Page 400: Evpn-Based Service Chain Pbr Configuration Example

    [SwitchA-Vlan-interface11] ip policy-based-route aaa [SwitchA-Vlan-interface11] quit Configure Switch B: # Create VLAN 10. <SwitchB> system-view [SwitchB] vlan 10 [SwitchB-vlan10] quit # Configure the IP address of VLAN-interface 10. [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] ip address 1.1.2.2 24 [SwitchB-Vlan-interface10] quit # Configure a static route to subnet 10.110.0.0/24. [SwitchB] ip route-static 10.110.0.0 24 1.1.2.1 Configure Switch C: # Create VLAN 20.
  • Page 401 Figure 90 Network diagram Loop0 4.4.4.4/32 Switch D Vlan-int11 Vlan-int13 11.1.1.4/24 13.1.1.4/24 IP transport network Vlan-int12 12.1.1.4/24 Vlan-int13 Switch A 13.1.1.3/24 Vlan-int11 Vlan-int12 Loop0 Loop0 11.1.1.1/24 Switch C 12.1.1.2/24 1.1.1.1/32 3.3.3.3/32 Loop0 Switch B GE1/0/1 2.2.2.2/32 VSI-int1 VSI-int1 GE1/0/1 10.1.1.1/24 10.1.1.1/24 VSI-int1 10.1.1.1/24...
  • Page 402 [SwitchA-bgp-default] peer 4.4.4.4 connect-interface loopback 0 [SwitchA-bgp-default] address-family l2vpn evpn [SwitchA-bgp-default-evpn] peer 4.4.4.4 enable [SwitchA-bgp-default-evpn] quit [SwitchA-bgp-default] quit # Create VPN instance vpna. [SwitchA] ip vpn-instance vpna [SwitchA-vpn-instance-vpna] route-distinguisher 1:1 [SwitchA-vpn-instance-vpna] address-family ipv4 [SwitchA-vpn-ipv4-vpna] vpn-target 2:2 [SwitchA-vpn-ipv4-vpna] quit [SwitchA-vpn-instance-vpna] address-family evpn [SwitchA-vpn-evpn-vpna] vpn-target 1:1 # Configure VSI-interface 1.
  • Page 403 # Create node 0, use ACL 3000 to match packets with source IP address 10.1.1.1 and destination IP address 10.1.1.20. Apply next hop 10.1.1.11 and service chain path ID 1 to matching packets. [SwitchA] policy-based-route aa permit node 0 [SwitchA-pbr-aa-0] if-match acl 3000 [SwitchA-pbr-aa-0] apply service-chain path-id 1 [SwitchA-pbr-aa-0] apply next-hop vpn-instance vpna 10.1.1.11 # Apply policy aa to VSI-interface 3.
  • Page 404 [SwitchB-Vsi-interface1] mac-address 0001-0001-0001 [SwitchB-Vsi-interface1] local-proxy-arp enable [SwitchB-Vsi-interface1] distributed-gateway local [SwitchB-Vsi-interface1] quit # Associate VSI instance vpna with VSI-interface 1. [SwitchB] vsi vpna [SwitchB-vsi-vpna] gateway vsi-interface 1 [SwitchB-vsi-vpna] quit # Configure VSI-interface 3. [SwitchB] interface vsi-interface 3 [SwitchB-Vsi-interface3] ip binding vpn-instance vpna [SwitchB-Vsi-interface3] l3-vni 1000 [SwitchB-Vsi-interface3] quit # Configure GigabitEthernet 1/0/1 as an AC interface.
  • Page 405 # Configure BGP to advertise EVPN routes. [SwitchC] bgp 200 [SwitchC-bgp-default] peer 4.4.4.4 as-number 200 [SwitchC-bgp-default] peer 4.4.4.4 connect-interface loopback 0 [SwitchC-bgp-default] address-family l2vpn evpn [SwitchC-bgp-default-evpn] peer 4.4.4.4 enable [SwitchC-bgp-default-evpn] quit [SwitchC-bgp-default] quit # Create VPN instance vpna. [SwitchC] ip vpn-instance vpna [SwitchC-vpn-instance-vpna] route-distinguisher 1:1 [SwitchC-vpn-instance-vpna] address-family ipv4 [SwitchC-vpn-ipv4-vpna] vpn-target 2:2...
  • Page 406 # Configure BGP to advertise EVPN routes, and disable route target filtering for BGP EVPN routes. [SwitchD-bgp-default] address-family l2vpn evpn [SwitchD-bgp-default-evpn] peer evpn enable [SwitchD-bgp-default-evpn] undo policy vpn-target # Configure Switch D as a route reflector. [SwitchD-bgp-default-evpn] peer evpn reflect-client [SwitchD-bgp-default-evpn] quit [SwitchD-bgp-default] quit # Configure VLAN-interface 11.

  • Page 407: 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 408: 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 409: 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 410 Figure 91 Network diagram Host B 2::2/64 Vlan-int400 2::1/64 Vlan-int200 Vlan-int300 4::2/64 5::2/64 Switch B Vlan-int200 Vlan-int300 4::1/64 5::1/64 Vlan-int100 Vlan-int500 1::1/64 3::1/64 Switch C Switch A Host C Host A 3::2/64 1::2/64 Configuration procedure Configure the IPv6 addresses for all VLAN interfaces. (Details not shown.) Configure IPv6 static routes: # Configure a default IPv6 static route on Switch A.

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

    Summary Count : 2 Static Routing table Status : <Active> Summary Count : 2 Destination: 1::/64 Protocol : Static NextHop : 4::1 Preference: 60 Interface : Vlan-interface200 Cost Destination: 3::/64 Protocol : Static NextHop : 5::1 Preference: 60 Interface : Vlan-interface300 Cost Static Routing table Status : <Inactive>...
  • Page 412 Figure 92 Network diagram 121::/64 120::/64 Switch A L2 Switch Switch B Vlan-int10 Vlan-int10 Vlan-int11 Vlan-int13 Vlan-int11 Vlan-int13 Switch C Table 24 Interface and IP address assignment Device Interface IPv6 address Switch A Vlan-int10 12::1/64 Switch A Vlan-int11 10::102/64 Switch B Vlan-int10 12::2/64 Switch B...
  • Page 413 <SwitchC> system-view [SwitchC] ipv6 route-static 120:: 64 13::1 [SwitchC] ipv6 route-static 121:: 64 10::102 Verifying the configuration # Display the BFD sessions on Switch A. <SwitchA> display bfd session Total Session Num: 1 Up Session Num: 1 Init Mode: Active IPv6 Session Working Under Ctrl Mode: Local Discr: 513 Remote Discr: 33...

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

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

  • Page 417: 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 IPv6 static routing."...

  • Page 418: 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 419: 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 420: 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 421: 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 422: 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 423: 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 424: 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 checkzero enabled for incoming RIPng on incoming RIPng packets. packets. Setting the maximum number of ECMP routes Step Command Remarks...

  • Page 425: Setting The Interval For Sending Triggered Updates

    Setting the interval for sending triggered updates Perform this task to avoid network overhead and reduce system resource consumption caused by frequent RIPng triggered updates. You can use the timer triggered command to set the maximum interval, minimum interval, and incremental interval for sending RIPng triggered updates.

  • Page 426: Configuring Ripng Nsr

    Step Command Remarks ripng [ process-id ] Enable RIPng and enter [ vpn-instance RIPng view. vpn-instance-name ] Enable the GR capability for graceful-restart By default, RIPng GR is disabled. RIPng. (Optional.) Set the GR By default, the GR interval is 60 graceful-restart interval interval interval.

  • Page 427: Configuration Restrictions And Guidelines

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

  • Page 428: Displaying And Maintaining Ripng

    Displaying and maintaining RIPng Execute display commands in any view and reset commands in user view. Task Command Display configuration information for a display ripng [ process-id ] RIPng process. display ripng process-id database [ ipv6-address Display routes in the RIPng database. prefix-length ] Display RIPng GR information.
  • Page 429 [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 400 [SwitchA-Vlan-interface400] ripng 1 enable [SwitchA-Vlan-interface400] quit # Configure Switch B. <SwitchA> system-view [SwitchA] ripng 1 [SwitchA-ripng-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ripng 1 enable [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 400 [SwitchA-Vlan-interface400] ripng 1 enable [SwitchA-Vlan-interface400] quit # Configure Switch C.
  • Page 430 Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D – Direct O - Optimal, F - Flush to RIB ---------------------------------------------------------------- Peer FE80::200:2FF:FE64:8904 on Vlan-interface100 Destination 3::/64, via FE80::200:2FF:FE64:8904, cost 1, tag 0, AOF, 31 secs Destination 4::/64, via FE80::200:2FF:FE64:8904, cost 2, tag 0, AOF, 31 secs Destination 5::/64, via FE80::200:2FF:FE64:8904, cost 2, tag 0, AOF, 31 secs...

  • Page 431: Ripng Route Redistribution Configuration Example

    Peer FE80::2:100 on Vlan-interface100 Destination 4::/64, via FE80::1:100, cost 2, tag 0, AOF, 2 secs RIPng route redistribution configuration example Network requirements As shown in Figure 96, Switch B communicates with Switch A through RIPng 100 and with Switch C through RIPng 200.
  • Page 432 [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] ripng 200 enable [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ripng 200 enable [SwitchC-Vlan-interface400] quit # Display the routing table on Switch A. [SwitchA] display ipv6 routing-table Destinations : 7 Routes : 7 Destination: ::1/128 Protocol : Direct NextHop...

  • Page 433: Ripng Gr Configuration Example

    Destinations : 8 Routes : 8 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64 Protocol : Direct NextHop : 1::1 Preference: 0 Interface : Vlan100 Cost Destination: 1::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface...

  • Page 434: Ripng Nsr Configuration Example

    Figure 97 Network diagram Router ID: 1.1.1.1 GR restarter Switch A Vlan-int100 2000::1/24 Vlan-int100 Vlan-int100 2000::2/24 2000::3/24 Switch B Switch C GR helper GR helper Router ID: 3.3.3.3 Router ID: 2.2.2.2 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure RIPng on the switches to ensure the following: (Details not shown.) Switch A, Switch B, and Switch C can communicate with each other at Layer 3.
  • Page 435 Figure 98 Network diagram Loop 0 Loop 0 2002::2/128 4004::4/128 Switch S Vlan-int100 Vlan-int200 1200:1::1/64 1400:1::1/64 Vlan-int100 Vlan-int200 1200:1::2/64 1400:1::2/64 Switch B Switch A Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure RIPng on the switches to ensure the following: (Details not shown.) Switch S, Switch A, and Switch B can communicate with each other at Layer 3.

  • Page 436: 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 Vlan-interface100 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 437 Figure 99 Network diagram Switch C Link B Link A Loop0 Loop0 Vlan-int200 Vlan-int200 Switch A Switch B Device Interface IP address Switch A VLAN-interface 100 1::1/64 Switch A VLAN-interface 200 2::1/64 Switch A Loopback 0 10::1/128 Switch B VLAN-interface 101 3::1/64 Switch B VLAN-interface 200...
  • Page 438 [SwitchB-ripng-1] quit Verifying the configuration # Display the route 20::1/128 on Switch A to view the backup next hop information. [SwitchA] display ipv6 routing-table 20::1 128 verbose Summary count : 1 Destination: 20::1/128 Protocol: RIPng Process ID: 1 SubProtID: 0x0 Age: 00h17m42s Cost: 1 Preference: 100...

  • 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 Enable an OSPFv3 process ospfv3 process-id area area-id By default, no OSPFv3 processes 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 Ospfv3 Virtual Link

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

  • Page 444: Configuration Prerequisites

    Follow these guidelines when you change the network type of an OSPFv3 interface: • An NBMA network must be fully connected. Any two routers in the network must be directly reachable to each other through a virtual circuit. If no such direct link is available, you must change the network type through a command.

  • Page 445: Configuring Ospfv3 Route Summarization

    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. Configuring route summarization on an ABR If contiguous network segments exist in an area, you can summarize them into one network segment on the ABR.

  • Page 446: Configuring Inter-Area-Prefix Lsa Filtering

    Step Command Remarks By default, OSPFv3 accepts all filter-policy { ipv6-acl-number [ gateway routes calculated using received prefix-list-name ] | prefix-list LSAs. Configure OSPFv3 to prefix-list-name [ gateway filter routes calculated This command can only filter prefix-list-name ] | gateway using received LSAs.

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

    Step Command Remarks Enter system view. system-view ospfv3 [ process-id | Enter OSPFv3 view. vpn-instance vpn-instance-name ] * Set a bandwidth reference bandwidth-reference value The default setting is 100 Mbps. value. Setting the maximum number of OSPFv3 ECMP routes Perform this task to implement load sharing over ECMP routes. To set the maximum number of ECMP routes: Step Command...
  • Page 448 IMPORTANT: The import-route bgp4+ command redistributes only EBGP routes. Because the import-route bgp4+ allow-ibgp command redistributes both EBGP and IBGP routes, and might cause routing loops, use it with caution. Redistributing routes from another routing protocol Step Command Remarks Enter system view. system-view ospfv3 [ process-id | vpn-instance Enter OSPFv3 view.

  • Page 449: Tuning And Optimizing Ospfv3 Networks

    Step Command Remarks 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

    Step Command Remarks interface interface-type Enter interface view. interface-number Set the LSA transmission ospfv3 trans-delay seconds By default, the LSA transmission delay. [ instance instance-id ] delay is 1 second. 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 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 Logging For 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 ospfv3 mib-binding process-id process with the smallest 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: Configuring Ospfv3 Authentication

    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 Ospfv3 Gr

    Configuring OSPFv3 GR GR ensures forwarding continuity 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—Graceful restarting router. It must be Graceful Restart capable. •...

  • Page 457: Triggering Ospfv3 Gr

    Step Command Remarks Enable strict LSA graceful-restart helper By default, strict LSA checking is checking. strict-lsa-checking disabled. Triggering OSPFv3 GR OSPFv3 GR is triggered by an active/standby switchover or when the following command is executed. To trigger OSPFv3 GR, perform the following command in user view: Task Command reset ospfv3 [ process-id ] process graceful-restart...

  • Page 458: Configuring Ospfv3 Frr

    To configure BFD for OSPFv3, you need to configure OSPFv3 first. To configure BFD for OSPFv3: Step Command Remarks Enter system view. system-view ospfv3 [ process-id | Enter OSPFv3 view. vpn-instance vpn-instance-name ] * Specify a router ID. router-id router-id Quit the OSPFv3 view.

  • Page 459: Configuration Guidelines

    Configuration guidelines Do not use the fast-reroute lfa command together with the vlink-peer command. Configuration procedure Configuring OSPFv3 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 on which LFA (Optional.) Disable LFA on...

  • Page 460: Displaying And Maintaining Ospfv3

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable BFD control ospfv3 primary-path-detect bfd By default, BFD control packet packet mode for OSPFv3 ctrl [ instance instance-id ] mode for OSPFv3 FRR is disabled. FRR. To configure BFD echo packet mode for OSPFv3 FRR: Step Command...

  • Page 461: 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 [ interface-type interface-number ] [ neighbor-id ]...
  • Page 462 Configuration procedure Configure IPv6 addresses for interfaces. (Details not shown.) Configure basic OSPFv3: # On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1. <SwitchA> system-view [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 300 [SwitchA-Vlan-interface300] ospfv3 1 area 1 [SwitchA-Vlan-interface300] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ospfv3 1 area 1...
  • Page 463 Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID Pri State Dead-Time InstID Interface 3.3.3.3 Full/BDR 00:00:40 Vlan100 Area: 0.0.0.1 ------------------------------------------------------------------------- Router ID Pri State Dead-Time InstID Interface 1.1.1.1 Full/DR 00:00:40 Vlan200 # Display OSPFv3 neighbors on Switch C. [SwitchC] display ospfv3 peer OSPFv3 Process 1 with Router ID 3.3.3.3 Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID...
  • Page 464 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: Vlan400 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 Switch D.

  • Page 465: Default Route

    *Destination: 2001:2::/64 Type Cost Nexthop : :: Interface: Vlan400 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: Vlan400 AdvRouter : 3.3.3.3 Area : 0.0.0.2 Preference : 10 Total: 5 Intra area: 1 Inter area: 4 ASE: 0...

  • Page 466: Ospfv3 Nssa Area Configuration Example

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

  • Page 468: Ospfv3 Dr Election Configuration Example

    *Destination: 2001:2::/64 Type Cost NextHop : :: Interface: Vlan400 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: Vlan400 AdvRouter : 2.2.2.2 Area : 0.0.0.2 Preference : 10 Total: 4 Intra area: 1 Inter area: 2 ASE: 1...
  • Page 469 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 0 [SwitchA-Vlan-interface100] quit # On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2. <SwitchB> system-view [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 1 area 0 [SwitchB-Vlan-interface200] quit # On Switch C, enable OSPFv3 and specify the router ID as 3.3.3.3.
  • Page 470 Router ID Pri State Dead-Time InstID Interface 1.1.1.1 Full/DROther 00:00:30 Vlan100 2.2.2.2 Full/DROther 00:00:37 Vlan200 3.3.3.3 Full/BDR 00:00:31 Vlan100 Configure router priorities for interfaces: # Set the router priority of VLAN-interface 100 to 100 on Switch A. [SwitchA] interface Vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 dr-priority 100 [SwitchA-Vlan-interface100] quit # Set the router priority of VLAN-interface 200 to 0 on Switch B.

  • Page 471: 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 Vlan200 3.3.3.3 Full/BDR 00:00:35 Vlan100 4.4.4.4 Full/DROther 00:00:33 Vlan200 # Display neighbor information on Switch D. [SwitchD] display ospfv3 peer OSPFv3 Process 1 with Router ID 4.4.4.4 Area: 0.0.0.0 ------------------------------------------------------------------------- Router ID...
  • Page 472 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 2 [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ospfv3 1 area 2 [SwitchA-Vlan-interface200] quit # Enable OSPFv3 process 1 and OSPFv3 process 2 on Switch B. <SwitchB> system-view [SwitchB] ospfv3 1 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 100...
  • Page 473 Destination: 4::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan400 Cost Destination: 4::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol...

  • Page 474: Ospfv3 Route Summarization Configuration Example

    Destination: 4::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan400 Cost Destination: 4::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol...
  • Page 475 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 2 [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ipv6 address 2:1:1::1 64 [SwitchA-Vlan-interface200] ipv6 address 2:1:2::1 64 [SwitchA-Vlan-interface200] ipv6 address 2:1:3::1 64 [SwitchA-Vlan-interface200] ospfv3 1 area 2 [SwitchA-Vlan-interface200] quit # Enable OSPFv3 process 1 and OSPFv3 process 2 on Switch B.
  • Page 476 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 : Vlan300 Cost Destination: 2::/64 Protocol : O_ASE2 NextHop : FE80::200:CFF:FE01:1C03 Preference: 150 Interface : Vlan300 Cost Destination: 2:1:1::/64 Protocol...
  • Page 477 # On Switch B, configure OSPFv3 process 2 to advertise a single route 2::/16. [SwitchB] ospfv3 2 [SwitchB-ospfv3-2] asbr-summary 2:: 16 [SwitchB-ospfv3-2] quit # Display the routing table on Switch C. [SwitchC] display ipv6 routing-table Destinations : 9 Routes : 9 Destination: ::1/128 Protocol : Direct...

  • Page 478: Ospfv3 Gr Configuration Example

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

  • Page 479: Ospfv3 Nsr Configuration Example

    [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 1 area 1 [SwitchC-Vlan-interface100] quit Verifying the configuration # Perform a master/backup switchover on Switch A to trigger an OSPFv3 GR operation. (Details not shown.) OSPFv3 NSR configuration example Network requirements As shown in Figure 107, Switch S, Switch A, and Switch B belong to the same AS and OSPFv3 routing domain.

  • Page 480: Bfd For Ospfv3 Configuration Example

    [SwitchS] interface vlan-interface 100 [SwitchS-Vlan-interface100] ospfv3 1 area 1 [SwitchS-Vlan-interface100] quit [SwitchS] interface vlan-interface 200 [SwitchS-Vlan-interface200] ospfv3 1 area 1 [SwitchS-Vlan-interface200] quit Verifying the configuration # Verify the following: • When an active/standby switchover occurs on Switch S, the neighbor relationships and routing information on Switch A and Switch B have not changed.
  • Page 481 # On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1. <SwitchA> system-view [SwitchA] ospfv3 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] ospfv3 1 area 0 [SwitchA-Vlan-interface10] quit [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] ospfv3 1 area 0 [SwitchA-Vlan-interface11] quit # On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2.

  • Page 482: Ospfv3 Frr Configuration Example

    [SwitchB-Vlan-interface10] bfd detect-multiplier 6 Verifying the configuration # Display the BFD information on Switch A. <SwitchA> display bfd session Total Session Num: 1 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 VLAN-interface 10 on Switch A) Destination IP: FE80::20F:FF:FE00:1200 (link-local address of VLAN-interface 10 on Switch B)
  • Page 483 Figure 109 Network diagram Switch C Link B Link A Loop0 Loop0 Vlan-int200 Vlan-int200 Switch A Switch B Table 27 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int100 1::1/64 Switch B Vlan-int101 3::1/64 Vlan-int200 2::1/64...
  • Page 484 [SwitchA-route-policy-frr-10] quit [SwitchA] ospfv3 1 [SwitchA-ospfv3-1] fast-reroute route-policy frr [SwitchA-ospfv3-1] quit # Configure Switch B. <SwitchB> system-view [SwitchB] ipv6 prefix-list abc index 10 permit 20:: 128 [SwitchB] route-policy frr permit node 10 [SwitchB-route-policy-frr-10] if-match ipv6 address prefix-list abc [SwitchB-route-policy-frr-10] apply ipv6 fast-reroute backup-interface vlan-interface 101 backup-nexthop 3::2/64 [SwitchB-route-policy-frr-10] quit [SwitchB] ospfv3 1...

  • Page 485: Configuring Ipv6 Is-Is

    Cost: 1 Preference: 10 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: Vlan-interface200 BkTunnel ID: Invalid...

  • Page 486: Configuring Ipv6 Is-Is Route Control

    Step Command Remarks Configure the network entity title (NET) for the IS-IS network-entity net By default, no NET is configured. process. Create the IPv6 address By default, no IS-IS IPv6 address address-family ipv6 [ unicast ] family and enter its view. family exists.

  • Page 487: Configuring Ipv6 Is-Is Link Cost

    Step Command Remarks 10. Configure the maximum By default, the maximum number of redistributed number of redistributed import-route limit number Level 1/Level 2 IPv6 Level 1/Level 2 IPv6 routes routes. is not configured. import-route isisv6 level-2 into level-1 11. Configure route By default, IPv6 IS-IS does [ filter-policy { ipv6-acl-number | prefix-list advertisement from...

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

    Step Command Remarks Specify an IS-IS cost-style { wide | wide-compatible | By default, the IS-IS cost cost style. compatible } style is narrow. Enter IPv6 address address-family ipv6 [ unicast ] family view. Enable IPv6 IS-IS By default, IPv6 IS-IS MTR multi-topology [ compatible ] MTR.

  • Page 489: Setting The Lsdb Overload Bit

    Step Command Remarks 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. Enter IPv6 address family address-family ipv6 [ unicast ] view.

  • Page 490: Controlling Spf Calculation Interval

    Step Command Remarks Configure a tag value on the By default, no tag value is isis ipv6 tag tag interface. configured on an interface. Controlling SPF calculation interval Step Command Remarks Enter system view. system-view isis [ process-id ] [ vpn-instance Enter IS-IS view.

  • Page 491: Configuring Bfd For Ipv6 Is-Is

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable prefix suppression on By default, prefix suppression is isis ipv6 prefix-suppression the interface. disabled on an interface. Configuring BFD for IPv6 IS-IS Bidirectional forwarding detection (BFD) can quickly detect faults between IPv6 IS-IS neighbors to improve the convergence speed of IPv6 IS-IS.

  • Page 492: Configuration Prerequisites

    Figure 110 Network diagram for IPv6 IS-IS FRR Backup next hop: Router C Router B Next hop: Router D Router E Figure 110, after you enable FRR on Router B, IPv6 IS-IS FRR automatically calculates or designates a backup next hop when a link failure is detected. In this way, packets are directed to the backup next hop to reduce traffic recovery time.
  • Page 493 Configuring IPv6 IS-IS FRR using a routing policy You can use the apply ipv6 fast-reroute backup-interface command to specify a backup next hop in a routing policy for routes matching specific criteria. You can also perform this task to reference the routing policy for IPv6 IS-IS FRR.

  • Page 494: Enabling Ipv6 Is-Is Mtr

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, BFD echo packet Enable BFD echo packet isis ipv6 primary-path-detect bfd mode for IPv6 IS-IS FRR is mode for IPv6 IS-IS FRR. echo disabled. Enabling IPv6 IS-IS MTR On a network, IPv4 and IPv6 topologies must be consistent so that both IPv6 IS-IS and IPv4 IS-IS can use the SPF algorithm to perform route calculation.

  • Page 495: Displaying And Maintaining Ipv6 Is-Is

    Step Command Remarks By default, IPv6 IS-IS MTR is Enable IPv6 IS-IS MTR. multi-topology [ compatible ] disabled. Displaying and maintaining IPv6 IS-IS Execute display commands in any view. For other display and reset commands, see "Configuring IS-IS." Task Command display isis redistribute ipv6 [ ipv6-address mask-length ] Display information about routes [ level-1 | level-2 ] [ process-id ]...
  • Page 496 # Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] address-family ipv6 [SwitchA-isis-1-ipv6] quit [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis ipv6 enable 1 [SwitchA-Vlan-interface100] quit # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] address-family ipv6...
  • Page 497 [SwitchD-Vlan-interface300] quit [SwitchD] interface vlan-interface 301 [SwitchD-Vlan-interface301] isis ipv6 enable 1 [SwitchD-Vlan-interface301] quit Verifying the configuration # Display the IPv6 IS-IS routing table on Switch A. [SwitchA] display isis route ipv6 Route information for IS-IS(1) ------------------------------ Level-1 IPv6 Forwarding Table ----------------------------- Destination : :: PrefixLen: 0...
  • Page 498 Destination : 2001:2:: PrefixLen: 64 Flag : R/-/- Cost : 20 Next Hop : Direct Interface: Vlan200 Destination : 2001:3:: PrefixLen: 64 Flag : R/-/- Cost : 20 Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan200 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set # Display the IPv6 IS-IS routing table on Switch C.

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

    Flag : R/-/- Cost : 10 Next Hop : FE80::20F:E2FF:FE3E:FA3D Interface: Vlan300 Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set # Display the IPv6 IS-IS routing table on Switch D. [SwitchD] display isis route ipv6 Route information for IS-IS(1) ------------------------------ Level-2 IPv6 Forwarding Table -----------------------------...
  • Page 500 Figure 113 Network diagram 2001:1::/64 2001:4::/64 Switch A Switch B Vlan-int10 Vlan-int10 Vlan-int11 Vlan-int13 L2 Switch Area 0 Vlan-int11 Vlan-int13 Switch C Table 28 Interface and IP address assignment Device Interface IPv6 address Switch A Vlan-int10 2001::1/64 Switch A Vlan-int11 2001:2::1/64 Switch B Vlan-int10...
  • Page 501 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] isis ipv6 enable 1 [SwitchB-Vlan-interface10] quit [SwitchB] interface vlan-interface 13 [SwitchB-Vlan-interface13] isis ipv6 enable 1 [SwitchB-Vlan-interface13] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] address-family ipv6 [SwitchC-isis-1-ipv6] quit [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 11 [SwitchC-Vlan-interface11] isis ipv6 enable 1...

  • Page 502: Ipv6 Is-Is Frr Configuration Example

    Destination IP: FE80::20F:FF:FE00:1200 (link-local address of VLAN-interface 10 on Switch B) Session State: Up Interface: Vlan10 Hold Time: 2319ms # Display routes destined for 2001:4::0/64 on Switch A. <SwitchA> display ipv6 routing-table 2001:4::0 64 Summary Count : 1 Destination: 2001:4::/64 Protocol : IS_L1 NextHop...
  • Page 503 Device Interface IP address Device Interface IP address Vlan-int101 3::2/64 Configuration procedure Configure IPv6 addresses for interfaces on the switches and enable IPv6 IS-IS. (Details not shown.) Configure IPv6 IS-IS on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at Layer 3.
  • Page 504 [SwitchB-isis-1-ipv6] quit [SwitchB-isis-1] quit Verifying the configuration # Display route 20::1/128 on Switch A to view the backup next hop information. [SwitchA] display ipv6 routing-table 20::1 128 verbose Summary count : 1 Destination: 20::1/128 Protocol: IS_L1 Process ID: 1 SubProtID: 0x1 Age: 00h27m45s Cost: 10 Preference: 15...
  • Page 505 Connector: N/A...

  • Page 506: Configuring Ipv6 Pbr

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

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

  • Page 508: Configuring An Ipv6 Policy

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

  • Page 509: Configuring Ipv6 Pbr

    Configuring IPv6 PBR Configuring IPv6 local PBR Configure IPv6 PBR by applying a policy locally. IPv6 PBR uses the policy to guide the forwarding of locally generated packets. The specified policy must already exist. Otherwise, the IPv6 local PBR configuration fails. You can apply only one policy locally.

  • Page 510: Ipv6 Pbr Configuration Examples

    Task Command display ipv6 policy-based-route local [ chassis (In IRF mode.) Display IPv6 local PBR chassis-number slot slot-number ] configuration and statistics. (In standalone mode.) Display IPv6 interface display ipv6 policy-based-route interface interface-type PBR configuration and statistics. interface-number [ slot slot-number ] display ipv6 policy-based-route interface interface-type (In IRF mode.) Display IPv6 interface PBR interface-number [ chassis chassis-number slot...

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

    [SwitchA] ipv6 policy-based-route aaa permit node 5 [SwitchA-pbr6-aaa-5] if-match acl 3001 [SwitchA-pbr6-aaa-5] apply next-hop 1::2 [SwitchA-pbr6-aaa-5] quit # Configure IPv6 local PBR by applying policy aaa to Switch A. [SwitchA] ipv6 local policy-based-route aaa Configure Switch B: # Create VLAN 10. <SwitchB>...
  • Page 512 Figure 116 Network diagram Switch B Switch C Vlan-int10 Vlan-int20 1::2/64 2::2/64 Vlan-int10 Vlan-int20 1::1/64 2::1/64 Switch A Vlan-int11 10::2/64 Subnet 10::1/64 Host A Host B 10::3/64 Gateway: 10::2/64 Configuration procedure Configure Switch A: # Create VLAN 10 and VLAN 20. <SwitchA>...
  • Page 513 [SwitchA-pbr6-aaa-5] quit # Configure IPv6 interface PBR by applying policy aaa to VLAN-interface 11. [SwitchA] interface vlan-interface 11 [SwitchA-Vlan-interface11] ipv6 address 10::2 64 [SwitchA-Vlan-interface11] undo ipv6 nd ra halt [SwitchA-Vlan-interface11] ripng 1 enable [SwitchA-Vlan-interface11] ipv6 policy-based-route aaa Configure Switch B: # Create VLAN 10.

  • Page 514: 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 515: 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 516: 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 517: 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 518: 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 519: 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 520 Step Command Remarks apply community { none | additive | Set the specified { community-number&<1-32> | By default, no community attribute is COMMUNITY attribute for aa:nn&<1-32> | internet | set for BGP routes. BGP routes. no-advertise | no-export | no-export-subconfed } * [ additive ] } Set a cost for routes.

  • Page 521: 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 •...

  • Page 522: Routing Policy Configuration Examples

    Task Command display ip as-path [ as-path-number ] Display BGP AS path list information. display ip community-list [ basic-community-list-number | Display BGP community list adv-community-list-number | name comm-list-name ] information. Display BGP extended community list display ip extcommunity-list [ ext-comm-list-number ] information.
  • Page 523 [SwitchC] isis [SwitchC-isis-1] is-level level-2 [SwitchC-isis-1] network-entity 10.0000.0000.0001.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis enable [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 201 [SwitchC-Vlan-interface201] isis enable [SwitchC-Vlan-interface201] quit [SwitchC] interface vlan-interface 202 [SwitchC-Vlan-interface202] isis enable [SwitchC-Vlan-interface202] quit [SwitchC] interface vlan-interface 203 [SwitchC-Vlan-interface203] isis enable [SwitchC-Vlan-interface203] quit # Configure Switch B.
  • Page 524 192.168.1.0/24 Stub 192.168.1.1 192.168.1.1 0.0.0.0 Routing for ASEs Destination Cost Type NextHop AdvRouter 172.17.1.0/24 Type2 192.168.1.2 192.168.2.2 172.17.2.0/24 Type2 192.168.1.2 192.168.2.2 172.17.3.0/24 Type2 192.168.1.2 192.168.2.2 Total Nets: 4 Intra Area: 1 Inter Area: 0 ASE: 3 NSSA: 0 Configure filtering lists: # Configure IPv4 basic ACL 2002 to permit route 172.17.2.0/24.

  • Page 525: 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 526 [SwitchA] route-policy static2ripng permit node 10 [SwitchA-route-policy-static2ripng-10] quit # Enable RIPng and apply the routing policy to static route redistribution. [SwitchA] ripng [SwitchA-ripng-1] import-route static route-policy static2ripng Configure Switch B: # Configure the IPv6 address for VLAN-interface 100. <SwitchB> system-view [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ipv6 address 10::2 32 # Enable RIPng.

  • Page 527: 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 528: Enabling Dcn

    Tasks at a glance (Optional.) Enabling the automatic report feature (Optional.) Configuring the source MAC address of LLDP frames (Required.) Advertising the LLDP management address (Required.) Enabling the system to issue the generated ARP entry to a Layer 3 Ethernet subinterface after a port receives an LLDP frame Enabling DCN After DCN is enabled, the device assigns an NE IP to the loopback interface with the largest interface...

  • Page 529: Enabling The Automatic Report Feature

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

  • Page 530: Advertising The Lldp Management Address

    Advertising the LLDP management address An NE on the DCN network learns the MAC address of its neighbor through LLDP. Perform this task to enable an NE to advertise the IP address of the specified loopback interface (management address) for ARP entry learning. For more information about LLDP, see Layer 2—LAN Switching Configuration Guide.

  • Page 531: Dcn Configuration Examples

    DCN configuration examples Network requirements As shown in Figure 119, the GNE, Device A, and Device B run DCN in the same VPN instance. The NMS uses SNMP to manage the GNE, and the GNE automatically sends notifications to the NMS to report online or offline events of NEs.
  • Page 532 # 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/0/1 receives an LLDP frame. [GNE-GigabitEthernet1/0/1] lldp management-address arp-learning vlan 4094 [GNE-GigabitEthernet1/0/1] quit # Enable the nearest bridge agents on GigabitEthernet 1/0/2 to advertise basic LLDP TLVs and management address TLVs.
  • Page 533 [DeviceA] ip vpn-instance dcn_vpn [DeviceA-vpn-instance-dcn_vpn] quit # Create interface Loopback 1023, and associate it with VPN instance dcn_vpn. [DeviceA] interface loopback 1023 [DeviceA-LoopBack1023] ip binding vpn-instance dcn_vpn [DeviceA-LoopBack1023] quit # Enable LLDP globally. [DeviceA] lldp global enable # Enable the nearest bridge agents on GigabitEthernet 1/0/1 to advertise basic LLDP TLVs and management address TLVs.
  • Page 534 [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] ospf network-type p2p [DeviceA-GigabitEthernet1/0/1] quit # Set the OSPF network type for GigabitEthernet 1/0/2 to P2P. [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] ospf network-type p2p [DeviceA-GigabitEthernet1/0/2] quit Configure Device B: # Enable DCN, configure the NE ID as 300003 and NE IP as 33.3.3.3/32. <DeviceB>...
  • Page 535 [DeviceB-GigabitEthernet1/0/1] ip binding vpn-instance dcn_vpn [DeviceB-GigabitEthernet1/0/1] ip address unnumbered interface loopback 1023 [DeviceB-GigabitEthernet1/0/1] quit # Create GigabitEthernet 1/0/2 that borrows the IP address of Loopback 1023. [DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] ip binding vpn-instance dcn_vpn [DeviceB-GigabitEthernet1/0/2] ip address unnumbered interface loopback 1023 [DeviceB-GigabitEthernet1/0/2] quit # Enable OSPF process 65535 to run in VPN instance dcn_vpn, and create area 0.
  • Page 536 # Remove Device B from the DCN network and display all DCN NE information for the GNE. [GNE] display dcn ne-info DCN Network Elements Information NE ID NE IP Metric Device Type 0x100001 11.1.1.1 HPE 7502 0x200002 22.2.2.2 HPE 7503 Total number: 2 The output shows that GNE and Device A are online.

  • Page 537: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional.

  • Page 538: 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 539: Support And Other Resources

    Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.

  • Page 540: Websites

    Websites Website Link Networking websites Hewlett Packard Enterprise Information Library for www.hpe.com/networking/resourcefinder Networking Hewlett Packard Enterprise Networking website www.hpe.com/info/networking Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty General websites Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs Hewlett Packard Enterprise Support Center...
  • Page 541 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 542: Index

    Index BGP optimal route (IPv4 unicast), Numerics BGP optimal route (IPv6 unicast), 4-byte BGP route advertisement rules, BGP AS number suppression, BGP route generation, DCN LLDP management address, BGP 6PE configuration, IPv4 BGP basic configuration, BGP 6PE optional capabilities, IPv4 BGP BFD configuration, IPv6 BGP 6PE configuration, IPv4 BGP COMMUNITY configuration, IPv4 BGP confederation,...
  • Page 543 OSPF network type, IS-IS basic configuration, OSPF NSSA area, IS-IS basics configuration, OSPF stub area, IS-IS configuration, 135, 141, 169 OSPF totally NSSA area, IS-IS DIS election configuration, OSPF totally stub area, OSPF areas, OSPF virtual link, OSPF AS External LSA, OSPFv3 area configuration (NSSA), 430, 454 routing policy AS_PATH list,...
  • Page 544 DCN automatic report, OSPFv3 BFD configuration, 445, 468 DCN automatic report enable, OSPFv3 FRR configuration, IPv6 IS-IS automatic link cost calculation, RIP BFD configuration, IPv6 IS-IS FRR automatic backup next hop RIP BFD configuration (bidirectional control detection), LFA calculation, IS-IS automatic cost calculation, RIP BFD configuration (bidirectional detection/control packet mode), automatic...
  • Page 545 enable, optimal route selection disable for labeled routes, fake AS number advertisement, ORIGINATOR_ID attribute ignore, first AS number of EBGP route update ignore, outgoing packet DSCP value, first send default route update, path attributes, FRR configuration, path selection control, GR configuration, peer, GTSM configuration, peer configuration,...
  • Page 546 tuning network, COMMUNITY bidirectional BGP COMMUNITY path attribute, IPv6 static route BFD control mode (direct IPv4 BGP COMMUNITY configuration, next hop), community IPv6 static route BFD control mode (indirect routing policy extended community list, next hop), routing policy list, IPv6 static route BFD echo mode (single hop), COMMUNITY BGP COMMUNITY configuration, OSPF BFD detection configuration...
  • Page 547 BGP link state (LS) route reflection, EBGP peer group (IPv6 multicast address), BGP load balancing (IPv4), EBGP peer group (IPv6 unicast address), BGP load balancing (IPv6), EVPN-based service chain PBR, BGP LS, IBGP peer group (IPv4 multicast address), BGP manual soft reset (IPv4), IBGP peer group (IPv4 unicast address), BGP manual soft reset (IPv6), IBGP peer group (IPv6 multicast address),...
  • Page 548 IPv6 PBR interface, IS-IS redistributed route filtering, IPv6 PBR interface (packet type-based), IS-IS route control, IPv6 PBR local, IS-IS route convergence priority, IPv6 PBR local (packet type-based), IS-IS route filtering, IPv6 PBR node action, IS-IS route leaking, IPv6 PBR node match criteria, IS-IS route redistribution, 147, 177 IPv6 PBR policy,...
  • Page 549 OSPF prefix suppression (interface), OSPFv3 redistributed route tag, OSPF prefix suppression (OSPF process), OSPFv3 route control, OSPF received route filtering, OSPFv3 route redistribution, OSPF redistributed route default parameters, OSPFv3 route redistribution (another routing protocol), OSPF redistributed route summarization OSPFv3 route redistribution (default route), (ASBR), OSPFv3 route summarization, OSPF route control,...
  • Page 550 RIPng packet zero field check, IPv6 static route BFD control mode (direct next hop), RIPng poison reverse, IPv6 static route BFD control mode (indirect next RIPng received/redistributed route filtering, hop), IS-IS route control, RIPng route control, IS-IS SPF calculation interval, RIPng route redistribution, 410, 419 OSPF route control,...
  • Page 551 NE ID+IP configuration, IPv4 BGP GR configuration, IPv4 BGP load balancing configuration, OSPFv3 DD packet ignore MTU check, IPv4 BGP path selection, OSPFv3 packet type, IPv4 BGP route reflector configuration, dead packet timer (OSPF), IPv4 BGP route summarization, default IPv4 BGP+IGP route redistribution, BGP default local preference, IPv4 multicast BGP configuration, BGP default route advertisement (peer/peer...
  • Page 552 OSPFv3 configuration, OSPF interface packet send/receive disable, OSPFv3 DR election configuration, OSPFv3 interface packet send/receive, OSPFv3 FRR configuration, recursion policy for routes received from a peer or peer group, OSPFv3 GR configuration, RIP host route reception, OSPFv3 route redistribution, discard route (OSPF), OSPFv3 route summarization, displaying OSPFv3 stub router,...
  • Page 553 BGP confederation, BGP peer keychain authentication (IPv6), BGP first AS number of route update ignore, BGP peer MD5 authentication (IPv4), BGP peer MD5 authentication (IPv6), BGP private AS number removal from BGP per-prefix label allocation, peer/peer group update, BGP route flapping logging (IPv4), direct connections after link failure, BGP route flapping logging (IPv6), peer,...
  • Page 554 RIPng FRR BFD, OSPF outbound LSAs (specified neighbor), RIPv1 incoming message zero field check, OSPF received route filtering, RIPv2 automatic route summarization, OSPF Type-3 LSA filtering, enhancing OSPFv3 Inter-Area-Prefix LSA filtering, IS-IS network security, OSPFv3 received route filtering, establishing RIP received/redistributed route filtering, BGP session establishment disable, RIPng received/redistributed route filtering, EBGP session establishment (multiple hop),...
  • Page 555 IPv6 PBR policy configuration, OSPFv3 backup next hop calculation (LFA algorithm), IPv6 RIB NSR configuration, OSPFv3 FRR BFD, OSPF GR, OSPFv3 FRR configuration, 446, 470 OSPF GR helper, RIP configuration, 41, 62, 414 OSPF GR restarter, RIPng configuration, OSPF NSR, static routing FRR configuration, 13, 21 OSPF NSR configuration,...
  • Page 556 IS-IS hello multiplier, IS-IS hello packet send interval, BGP link state (LS) router ID, IS-IS interface hello packet send, DCN NE ID+IP configuration, IS-IS PDU type, IS-IS system ID, OSPF hello packet, IDP (IS-IS area address), OSPF hello packet timer, IETF OSPFv3 packet type, OSPF GR,...
  • Page 557 PBR configuration (interface/packet BGP first AS number of EBGP route update type-based), ignore, Intermediate System-to-Intermediate System. Use BGP first send default route update, IS-IS BGP FRR, internal BGP GR, BGP. Use IBGP BGP GTSM configuration, OSPF router type, BGP large scale network management, INTERNET BGP large-scale network, BGP COMMUNITY path attribute,...
  • Page 558 DCN VPN configuration, IS-IS interface DIS priority, displaying IPv6 static routing, IS-IS interface hello packet send, displaying PBR, IS-IS interface packet send/receive, displaying routing table, IS-IS interface tag value, displaying static routes, IS-IS ISPF, dynamic routing protocols, IS-IS link cost, EBGP peer protection (low memory IS-IS LSDB overload bit, exemption),...
  • Page 559 OSPF basic configuration, OSPF preference, OSPF BDR, OSPF prefix priority, OSPF BFD, 100, 100 OSPF prefix suppression, OSPF BFD configuration, OSPF protocols and standards, OSPF BFD detection configuration OSPF received route filtering, (bidirectional control), OSPF RFC 1583 compatibility, OSPF BFD detection configuration OSPF route control, (single-hop echo), OSPF route redistribution,...
  • Page 560 OSPFv3 network tuning, RIP basic configuration, 27, 43 OSPFv3 network type, RIP BFD configuration, OSPFv3 network type (interface), RIP BFD configuration (bidirectional control detection), OSPFv3 NSR, RIP BFD configuration (bidirectional OSPFv3 NSR configuration, detection/control packet mode), OSPFv3 P2MP neighbor, RIP BFD configuration (single-hop echo OSPFv3 preference, detection), OSPFv3 prefix suppression,...
  • Page 561 RIPng ECMP route max, troubleshooting BGP peer connection state, RIPng FRR configuration, 414, 424 troubleshooting OSPF configuration, RIPng GR configuration, 413, 421 troubleshooting OSPF incorrect routing information, RIPng maintain, troubleshooting OSPF no neighbor relationship RIPng network optimization, established, RIPng network tuning, IPv4 RIPng NSR, BGP 6PE optional capabilities,...
  • Page 562 IPv4 BGP route summarization (automatic), 4-byte AS number suppression, route summarization (manual), 6PE configuration, route update interval, AS number substitution, route update save, basic configuration, routes received (peer/peer group), BFD configuration, 304, 345 session establishment disable, COMMUNITY configuration, 294, 331 session reset, confederation configuration, session retry timer,...
  • Page 563 OSPFv3 network type (interface), multicast configuration, OSPFv3 P2MP neighbor, NEXT_HOP attribute, OSPFv3 preference, optimal route advertisement, OSPFv3 received route filtering, ORIGINATOR_ID attribute ignore, OSPFv3 route control, peer configuration (IPv6 multicast address), OSPFv3 route redistribution, 435, 459 peer keychain authentication, OSPFv3 route summarization, 433, 462 peer MD5 authentication, OSPFv3 SPF calculation interval,...
  • Page 564 IPv6 PBR DIS election, apply clause, DIS election configuration, configuration, 494, 495, 497, 498 display, displaying, ECMP routes max, if-match clause, enable, interface configuration, enabling automatic cost calculation, interface configuration (packet type-based), FRR backup next hop configuration (LFA calculation), interface PBR, FRR BFD enable (control packet mode), local configuration, FRR BFD enable (echo packet mode),...
  • Page 565 PDU SNP type, IS-IS LSP flooding, PDU types, link PIC BFD enabling, BGP BFD, PIC configuration, EBGP direct connection after link failure, point-to-point network type, IPv6 IS-IS automatic link cost calculation, preference specification, IPv6 IS-IS link cost, prefix suppression enable, IS-IS automatic cost calculation, protocols and standards, IS-IS global cost,...
  • Page 566 BGP MPLS local label update delay, LSAck IPv6 PBR local configuration, OSPF LSAck packet, IPv6 PBR local configuration (packet OSPFv3 packet type, type-based), LSDB PBR configuration (local), IPv6 IS-IS LSDB overload bit, PBR configuration (local/packet type-based), IS-IS LSDB overload bit, OSPF LSDB external LSAs max, logging BGP route flapping logging,...
  • Page 567 IS-IS system ID > host name mapping (static), MP_REACH_NLRI (MP-BGP), MP_UNREACH_NLRI (MP-BGP), matching MP-BGP, 195, See also IPv6 PBR if-match clause, address family, IPv6 PBR node action, BGP configuration, 195, 208 IPv6 PBR node match criteria, extended attributes, PBR deny match mode, IPv4 BGP basic configuration, PBR if-match clause, IPv4 BGP BFD configuration,...
  • Page 568 RIPng configuration, 406, 407 advertising OSPF link state information to BGP, multicast BGP BGP 4-byte AS number suppression, dynamic peer configuration (IPv4 multicast address), BGP 6PE configuration, dynamic peer configuration (IPv6 multicast BGP 6PE optional capabilities, address), BGP AS number substitution, IPv4 BGP dynamic peer configuration, BGP AS_PATH attribute, IPv4 configuration,...
  • Page 569 BGP route reception, IPv4 BGP BFD configuration, BGP route recursion, IPv4 BGP COMMUNITY configuration, BGP route reflection, IPv4 BGP confederation, BGP route selection, 199, 200 IPv4 BGP configuration, BGP route summarization, IPv4 BGP dynamic peer configuration, BGP route update delay, IPv4 BGP FRR configuration, BGP route update interval, IPv4 BGP GR configuration,...
  • Page 570 IPv6 static route BFD control mode (direct IS-IS NSR configuration, next hop), IS-IS PIC BFD, IPv6 static route BFD control mode (indirect IS-IS PIC configuration, next hop), IS-IS point-to-point type, IPv6 static route BFD echo mode (single hop), IS-IS preference, IS-IS prefix suppression, IPv6 static route configuration, IS-IS pseudonode,...
  • Page 571 OSPF neighbor state change logging, OSPFv3 interface cost, OSPF network LSA, OSPFv3 interface DR priority, OSPF network management, OSPFv3 interface packet send/receive disable, OSPF network summary LSA, OSPFv3 LSA generation interval, OSPF network type, OSPFv3 LSA transmission delay, OSPF NSR, OSPFv3 LSU transmit rate, OSPF NSR configuration, OSPFv3 NBMA neighbor,...
  • Page 572 RIP network tuning, routing policy AS_PATH list, RIP NSR configuration, routing policy COMMUNITY list, RIP NSR enable, routing policy configuration, RIP operation, routing policy configuration (IPv4 route redistribution), RIP packet max length, routing policy configuration (IPv6 route RIP packet send rate configuration, redistribution), RIP poison reverse configuration, routing policy continue clause,...
  • Page 573 OSPFv3 network tuning, OSPF GR restarter, PBR configuration, 380, 382, 383, 385 nonstop routing. Use PBR configuration (interface/packet nonstop routing (NSR) type-based), BGP configuration, PBR configuration (local/packet type-based), RIP NSR enable, notifying RIP configuration, 25, 26, 43 BGP notification message, RIPng configuration, 406, 407, 416 BGP SNMP notification enable,...
  • Page 574 optimizing interface network type (P2MP), BGP network, interface network type (P2P), IPv6 IS-IS networks, interface packet send/receive disable, IS-IS networks, IS-IS BFD, OSPF network, IS-IS DIS election, OSPFv3 network, ISPF enable, RIP networks, log count configuration, RIPng network, LSA arrival interval, LSA generation interval, ORIGIN BGP path attribute,...
  • Page 575 totally NSSA area, preference configuration, totally stub area, prefix suppression, troubleshoot configuration, protocols and standards, troubleshoot incorrect routing information, received route filtering, troubleshoot no neighbor relationship redistributed route tag, established, route control configuration, Type-3 LSA filtering, route redistribution, 435, 459 virtual link configuration, 76, 121 route redistribution (another routing protocol),...
  • Page 576 IS-IS interface hello packet send, PBR configuration (local), IS-IS interface packet send/receive, PBR configuration (local/packet type-based), IS-IS PDU CLVs, PBR policy configuration, IS-IS PDU hello type, RIP BFD configuration (bidirectional control detection), IS-IS PDU LSP type, RIP BFD configuration (single-hop echo IS-IS PDU SNP type, detection/neighbor), IS-IS PDU types,...
  • Page 577 node creation, EVPN-based service chain PBR configuration, node match criteria, IPv6 IS-IS FRR configuration (routing policy), policy, IPv6 PBR, policy configuration, IPv6 PBR apply clause, relationship between match mode/clauses, IPv6 PBR configuration, 494, 495, 497, 498 Track collaboration, IPv6 PBR if-match clause, IPv6 PBR interface configuration, IS-IS CLVs, IPv6 PBR interface configuration (packet...
  • Page 578 RIP configuration, configuring BGP 6PE basics, preferring configuring BGP 6PE optional capabilities, BGP default local preference, configuring BGP AS number substitution (IPv4), BGP received route preferred value, configuring BGP AS number substitution (IPv6), BGP route preference, IS-IS preference specification, configuring BGP AS_PATH attribute, OSPF protocol preference, configuring BGP basics, OSPFv3 preference,...
  • Page 579 configuring BGP peer (IPv6 multicast configuring IBGP peer group (IPv4 multicast address), address), configuring BGP peer (IPv6 unicast address), configuring IBGP peer group (IPv4 unicast address), configuring BGP route dampening (IPv4), configuring IBGP peer group (IPv6 multicast address), configuring BGP route dampening (IPv6), configuring IBGP peer group (IPv6 unicast configuring BGP route distribution filtering address),...
  • Page 580 configuring IPv6 PBR local (packet configuring IS-IS NSR, 164, 185 type-based), configuring IS-IS PIC, configuring IPv6 PBR node action, configuring IS-IS redistributed route filtering, configuring IPv6 PBR node match criteria, configuring IS-IS route control, configuring IPv6 PBR policy, configuring IS-IS route convergence priority, configuring IPv6 RIB inter-protocol FRR, configuring IS-IS route filtering, configuring IPv6 RIB NSR,...
  • Page 581 configuring OSPF LSU transmit rate, configuring OSPFv3 interface DR priority, configuring OSPF network management, configuring OSPFv3 LSU transmit rate, configuring OSPF network type, configuring OSPFv3 NBMA neighbor, configuring OSPF NSR, 99, 125 configuring OSPFv3 network management, configuring OSPF packet DSCP value, configuring OSPFv3 network type, configuring OSPF PIC, configuring OSPFv3 network type (interface),...
  • Page 582 configuring RIP GR, configuring static route, configuring RIP interface additional metric, configuring static route BFD, configuring RIP network management, configuring static route FRR (auto backup next hop), configuring RIP packet send rate, configuring static routing, configuring RIP received/redistributed route filtering, configuring static routing basics, configuring RIP route control, configuring static routing BFD (direct next hop),...
  • Page 583 displaying PBR, enabling IPv6 IS-IS ISPF, displaying RIP, enabling IPv6 IS-IS MTR, displaying RIPng, enabling IPv6 IS-IS prefix suppression, displaying routing policy, enabling IS-IS, displaying static routing, enabling IS-IS automatic cost calculation, enabling BGP, enabling IS-IS FRR BFD (control packet mode), enabling BGP 4-byte AS number suppression (IPv4), enabling IS-IS FRR BFD (echo packet mode),...
  • Page 584 ignoring BGP AS_PATH attribute, setting BGP outgoing packet DSCP value, ignoring BGP first AS number of EBGP route setting BGP received route preferred value (IPv4), updates, ignoring BGP IGP metrics during optimal route setting BGP received route preferred value (IPv6), selection, ignoring BGP ORIGINATOR_ID attribute setting BGP session retry timer (IPv4),...
  • Page 585 triggering OSPFv3 GR, redistributing troubleshooting BGP peer connection state, BGP IGP route, BGP route generation, troubleshooting OSPF incorrect routing IP routing extension attribute redistribution, information, IP routing route redistribution, troubleshooting OSPF no neighbor IPv4 BGP+IGP route redistribution, relationship established, IS-IS redistributed route filtering, tuning BGP network, IS-IS route redistribution, 147, 177...
  • Page 586 BFD configuration (bidirectional control split horizon configuration, detection), split horizon enable, BFD configuration (bidirectional summary route advertisement configuration, detection/control packet mode), timer configuration, BFD configuration (single-hop echo triggered update interval configuration, detection)(on switch), update source IP address check, BFD configuration (single-hop echo version configuration, detection/neighbor), versions,...
  • Page 587 RIP versions, IP routing RIB route max lifetime, route summarization configuration, IP routing route backup, summary route advertisement, IP routing route preference, version configuration, IP routing route recursion, route IP routing route redistribution, BGP default route advertisement (peer/peer IPv4 BGP route reflector configuration, group), IPv4 BGP route summarization, BGP first send default route update,...
  • Page 588 OSPFv3 ECMP route max, IS-IS IS+circuit level, OSPFv3 received route filtering, IS-IS Level-1 router, OSPFv3 redistributed route tag, IS-IS Level-1-2 router, OSPFv3 route control, IS-IS Level-2 router, OSPFv3 route redistribution, 435, 459 IS-IS route leaking, OSPFv3 route redistribution (another routing IS-IS routing method, protocol), IS-IS system ID,...
  • Page 589 OSPF prefix suppression, IS-IS ATT bit Level-1 LSP, OSPFv3 authentication, IS-IS IS+circuit level, OSPFv3 prefix suppression, IS-IS LSDB overload bit, OSPF ECMP routes max, IS-IS N-SEL, OSPF exit overflow interval, NET, OSPF log count, selecting OSPF LSA transmission delay, BGP load balancing through route selection, OSPF LSDB external LSAs max, OSPF timer, BGP path selection,...
  • Page 590 OSPF SPF calculation interval, OSPF route summarization (ABR), RIP neighbor, OSPF route summarization configuration, OSPF summary network discard route, IPv6 IS-IS calculation interval, OSPFv3 route summarization, IS-IS calculation interval, OSPFv3 route summarization (ABR), OSPF SPF calculation interval, OSPFv3 route summarization (ASBR), OSPFv3 SPF calculation interval, RIPng route summarization, split horizon,...
  • Page 591 IPv4 BGP configuration, IPv6 static routing configuration, 395, 397 IPv4 BGP dynamic peer configuration, IS-IS ISPF, IPv4 BGP FRR configuration, Track IPv4 BGP GR configuration, IPv6 PBR collaboration, IPv4 BGP load balancing configuration PBR collaboration, configuration, static routing configuration, IPv4 BGP path selection, transmitting IPv4 BGP route reflector configuration, OSPFv3 LSU transmit rate,...
  • Page 592 unicast zero field check BGP dynamic peer, RIPng packet, BGP dynamic peer configuration (IPv4 unicast zero field check (RIPv1), address), BGP dynamic peer configuration (IPv6 unicast address), BGP FRR configuration (IPv4 unicast address), BGP FRR configuration (IPv6 unicast address), BGP peer, EBGP peer group configuration (IPv4 unicast address), EBGP peer group configuration (IPv6 unicast...

Table of Contents