H3C S9500E Series Configuration Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S9500E Series
  6. Configuration manual

H3C S9500E Series Configuration Manual

Routing switches
Hide thumbs Also See for S9500E Series:
1
2
3
4
5
6
7
8
Table Of Contents
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
Table of Contents

Advertisement

Quick Links

Download this manual
H3C S9500E Series Routing Switches
Layer3 - IP Routing Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Document Version:
Product Version:

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for H3C S9500E Series

Summary of Contents for H3C S9500E Series

  • Page 1 H3C S9500E Series Routing Switches Layer3 - IP Routing Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Document Version: Product Version:...
  • Page 2 SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V G, V G, PSPT, XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners.

  • Page 3: Preface

    The H3C S9500E documentation set includes 13 configuration guides, which describe the software features for the H3C S9500E Series Routing Switches and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.

  • Page 4: Conventions

    Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional.
  • Page 5 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 6: About The H3C S9500E Documentation Set

    Provides a complete guide to hardware installation Installation guide and hardware specifications. Card manuals Provide the hardware specifications of cards. Cabinet Guides you through installing and remodeling H3C Installation and Remodel N68 cabinets. Hardware specifications Introduction and installation Pluggable...
  • Page 7 Category Documents Purposes Error code reference Explains the error codes for the QoS module.
  • Page 8 Obtaining documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support & Documents > Technical Documents] –...

  • Page 9: Table Of Contents

    Table of Contents Preface ·········································································································································································· 3 Audience ············································································································································································ 3 Conventions ······································································································································································· 4 About the H3C S9500E Documentation Set ·················································································································· 6 IP routing basics configuration ·································································································································· 20 IP routing and routing table ·········································································································································· 20 Routing ···································································································································································· 20 Routing table ·························································································································································· 20 Routing protocol overview ·············································································································································...
  • Page 10 Supported RIP features ·········································································································································· 46 Protocols and standards ······································································································································· 46 Configuring RIP basic functions ···································································································································· 46 Configuring RIP route control ········································································································································ 48 Configuring an additional routing metric ··········································································································· 49 Configuring RIPv2 route summarization·············································································································· 49 Disabling host route reception ····························································································································· 50 Advertising a default route ···································································································································...
  • Page 11 DR and BDR ··························································································································································· 88 OSPF packet formats ············································································································································· 89 Supported OSPF features ····································································································································· 99 Protocols and standards ····································································································································· 101 OSPF configuration tasks ············································································································································ 101 Enabling OSPF ····························································································································································· 102 Prerequisites ························································································································································· 102 Configuration procedure ···································································································································· 102 Configuring OSPF areas ············································································································································· 103 Prerequisites ·························································································································································...
  • Page 12 Configuring OSPF network management ········································································································· 124 Enabling message logging ································································································································· 125 Enabling the advertisement and reception of opaque LSAs ··········································································· 126 Configuring OSPF to give priority to receiving and processing hello packets ············································· 126 Configuring the LSU transmit rate ······················································································································ 126 Configuring OSPF FRR ········································································································································...
  • Page 13 Configuring IS-IS link cost ··································································································································· 184 Specifying a priority for IS-IS ····························································································································· 186 Configuring the maximum number of equal-cost routes ·················································································· 187 Configuring IS-IS route summarization ·············································································································· 187 Advertising a default route ································································································································· 188 Configuring IS-IS route redistribution ················································································································ 188 Configuring IS-IS route filtering ··························································································································...
  • Page 14 BGP configuration ··················································································································································· 236 BGP overview ······························································································································································· 236 Formats of BGP messages ·································································································································· 237 BGP path attributes ············································································································································· 240 BGP route selection ············································································································································· 244 iBGP and IGP synchronization ·························································································································· 246 Settlements for problems in large-scale BGP networks ···················································································· 247 BGP GR ································································································································································ 251 MP-BGP ·································································································································································...
  • Page 15 Clearing BGP information ·································································································································· 275 BGP configuration examples ······································································································································ 275 BGP basic configuration ····································································································································· 276 BGP and IGP synchronization configuration ···································································································· 281 BGP load balancing configuration ···················································································································· 284 BGP community configuration ···························································································································· 286 BGP route reflector configuration ······················································································································ 289 BGP confederation configuration ······················································································································ 291 BGP path selection configuration ······················································································································...
  • Page 16 Configuring RIPng route summarization ··········································································································· 329 Advertising a default route ································································································································· 329 Configuring a RIPng route filtering policy ········································································································· 329 Configuring a priority for RIPng ························································································································· 330 Configuring RIPng route redistribution ·············································································································· 330 Tuning and optimizing the RIPng network ················································································································· 331 Configuring RIPng timers ····································································································································...
  • Page 17 Enable the logging of neighbor state changes ································································································ 353 Configuring OSPFv3 GR ············································································································································· 354 Configuring GR Restarter ···································································································································· 354 Configuring GR Helper ······································································································································· 354 Displaying and maintaining OSPFv3 ························································································································· 355 OSPFv3 configuration examples ································································································································ 356 Configuring OSPFv3 areas ································································································································ 356 Configuring OSPFv3 DR election ·······················································································································...
  • Page 18 Tuning and optimizing IPv6 BGP networks ··············································································································· 388 Configuring IPv6 BGP timers ······························································································································ 388 Configuring IPv6 BGP soft reset ························································································································· 389 Enabling the IPv6 BGP ORF capability ············································································································· 390 Configuring the maximum number of load-balanced routes ·········································································· 391 Configuring a large-scale IPv6 BGP network ············································································································ 392 Configuring IPv6 BGP peer group ·····················································································································...
  • Page 19 Creating a routing policy ··································································································································· 420 Defining if-match clauses ···································································································································· 420 Defining apply clauses ········································································································································ 422 Defining a continue clause ································································································································· 424 Displaying and maintaining the routing policy ········································································································· 425 Routing policy configuration examples ······················································································································ 425 Applying a routing policy to IPv4 route redistribution ····················································································· 425 Applying a routing policy to IPv6 route redistribution ·····················································································...

  • Page 20: Ip Routing Basics Configuration

    IP routing basics configuration IP routing and routing table Routing Routing in the Internet is achieved through routers. Upon receiving a packet, a router finds an optimal route based on the destination address and forwards the packet to the next router in the path until the packet reaches the last router.
  • Page 21 • Preference for the route: Routes to the same destination, but having different next hops, can have different preferences, and can be found by various routing protocols or be manually configured. The optimal route is the one with the highest preference (with the smallest metric).

  • Page 22: Routing Protocol Overview

    Routing protocol overview Static routing and dynamic routing Static routing is easy to configure and requires fewer system resources. It works well in small, stable networks with simple topologies. Its major drawback is that it cannot adjust to network changes without intervention, so you must perform routing configuration again whenever the network topology changes.

  • Page 23: Routing Protocols And Routing Preference

    IP routing protocol version IPv4 routing protocols: RIP, OSPFv2, BGP4, and IS-IS. IPv6 routing protocols: RIPng, OSPFv3, BGP4+, and IPv6 IS-IS. Routing protocols and routing preference Different routing protocols can find different routes to the same destination. However, not all of those routes are optimal.

  • Page 24: Load Balancing And Route Backup

    Load balancing and route backup Load balancing A routing protocol can be configured with multiple equal-cost routes to the same destination. These routes have the same preference and will all be used to accomplish load balancing if there is no route with a higher preference available. A given routing protocol can find several routes with the same metric to the same destination.

  • Page 25: Displaying And Maintaining A Routing Table

    Displaying and maintaining a routing table To do… Use the command… Remarks display ip routing-table Display brief vpn-instance vpn- Step 1 information about the instance-name ] [ verbose | Available in any view active routes in the | { begin | exclude | routing table include } regular-expression display ip routing-table...
  • Page 26 To do… Use the command… Remarks display ipv6 routing- Display routing Step 13 information for a table ipv6-address prefix- Available in any view specified destination length [ longer-match ] [ IPv6 address verbose ] display ipv6 routing- Display routing Step 14 information permitted table acl acl6-number [ Available in any view...

  • Page 27: Static Routing Configuration

    Static routing configuration Static route Static routes are manually configured. If a network’s topology is simple, you only need to configure static routes for the network to work normally. The proper configuration and usage of static routes can improve network performance and ensure bandwidth for important network applications.

  • Page 28: Configuring A Static Route

    Output interface and next hop address While configuring a static route, specify either the output interface or the next hop address depending on the specific occasion. The next hop address cannot be a local interface IP address because the route configuration will not take effect. All route entries must have a next hop address.

  • Page 29: Configuring Bfd For Static Routes

    To do… Use the command… Remarks information ip route-static vpn-instance s-vpn-instance-name&<1- configured. 6> dest-address { mask | mask-length } { next-hop-address [ track track-entry-number ] [ public ] | interface-type interface-number next-hop-address [ bfd { control- packet | echo-packet } ] | vpn-instance d-vpn- instance-name next-hop-address [ track track-entry-number ] } [ preference preference-value ] [ tag tag-value ] [ description description-text ]...
  • Page 30 To do… Use the command… Remarks system-view Enter system view — Step 1 ip route-static dest-address { mask | mask-length } interface-type interface-number next-hop-address bfd control-packet [ preference preference-value ] [ Enable BFD tag tag-value ] [ description description-text ] Step 2 control packet Use either command...

  • Page 31: Configuring Static Route Frr

    To do… Use the command… Remarks Required Configure the Step 3 bfd echo-source-ip ip-address source address of Not configured by echo packets default ip route-static dest-address { mask | mask-length } Bind a static route next-hop-address [ track track-entry-number ] [ Step 4 Required with the track entry...

  • Page 32: Displaying And Maintaining Static Routes

    To do… Use the command… Remarks Enter system Step 1 system-view — view Configure the Step 2 Required source bfd echo-source-ip ip-address Not configured by address of default echo packets Required Configure Step 3 ip route-static [ vpn-instance vpn-instance-name ] static route Not configured by fast-reroute route-policy route-policy-name...

  • Page 33: Static Route Configuration Examples

    Static route configuration examples By default, Ethernet, VLAN, and aggregate interfaces are down. Before configuring these interfaces, bring them up using the undo shutdown command. Basic static route configuration example Network requirements Figure 3 shows the IP addresses and masks of the switches and hosts. Static routes are required for interconnection between any two hosts.
  • Page 34 [SwitchC] ip route-static 0.0.0.0 0.0.0.0 1.1.5.5 Configure the hosts. The default gateways for the three hosts A, B, and C are 1.1.2.3, 1.1.6.1, and 1.1.3.1, respectively. Display the configuration. Display the Switch A IP routing table. [SwitchA] display ip routing-table Routing Tables: Public Destinations : 7 Routes : 7...

  • Page 35: Static Route Frr Configuration Example

    Pinging 1.1.2.2 with 32 bytes of data: Reply from 1.1.2.2: bytes=32 time=1ms TTL=253 Reply from 1.1.2.2: bytes=32 time=1ms TTL=253 Reply from 1.1.2.2: bytes=32 time=1ms TTL=253 Reply from 1.1.2.2: bytes=32 time=1ms TTL=253 Ping statistics for 1.1.2.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Use the tracert command on Host B to check reachability to Host A.
  • Page 36 Configure static routes on Switch S, Switch D, and Switch A so Switch S can reach Loopback 0 on Switch D. Switch D can then reach Loopback 0 on Switch S. Configure static routes on Switch S. <SwitchS> system-view [SwitchS] ip route-static 4.4.4.4 32 vlan-interface 200 13.13.13.2 [SwitchS] ip route-static 4.4.4.4 32 12.12.12.2 preference 100 Configure static routes on Switch D.
  • Page 37 Protocol: Static Process ID: 0 Preference: 60 Cost: 0 NextHop: 13.13.13.2 Interface: vlan 200 BkNextHop: 12.12.12.2 BkInterface: vlan 100 RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h01m27s Tag: 0 Destination: 4.4.4.4/32 Protocol: Static Process ID: 0 Preference: 100 Cost: 0...

  • Page 38: Configuring Bfd Echo Packet Mode

    State: Active Adv Age: 00h01m27s Tag: 0 Configuring BFD echo packet mode Network requirements In Figure 5, configure a static route on Switch A to Switch C and enable BFD. When the link between Switch A and Switch B fails, Switch A selects Switch D to reach Switch C. Figure 5 Network diagram for BFD configuration on a static route Configuration procedure...
  • Page 39 Display static route information on Switch A. <SwitchA> display ip routing-table protocol static Public Routing Table : Static Summary Count : 2 Static Routing table Status : <Active> Summary Count : 1 Destination/Mask Proto Cost NextHop Interface 120.1.1.1/24 Static 65 10.1.1.100 Vlan10 Direct Routing table Status : <Inactive>...

  • Page 40: Configuring Bfd Control Packet Mode For Static Routing

    Configuring BFD control packet mode for static routing Network requirements Figure 6 shows that you can configure a static route to subnet 14.1.1.0/24 on Switch A and configure a static route to subnet 13.1.1.0/24 on Switch B. Both routes have BFD control packet mode enabled.
  • Page 41 Total Session Num: 1 Init Mode: Active Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr State Holdtime Interface 12.1.1.1 12.1.1.2 2000ms Vlan12 Display the static route information of Switch A. <SwitchA> display ip routing-table protocol static Public Routing Table : Static Summary Count : 1 Static Routing table Status : <...

  • Page 42: Rip Configuration

    RIP configuration The term router refers to both routers and Layer 3 switches. RIP overview RIP is a simple IGP, mainly used in small-sized networks, such as academic networks and simple LANs. RIP is not applicable to complex networks. RIP is still widely used in practical networking because it is easier to implement, configure, and maintain than OSPF and IS-IS.

  • Page 43: Routing Loops Prevention

    • Update timer: Defines the interval between routing updates. • Timeout timer: Defines the route aging time. If no update for a route is received within the aging time, the metric of the route is set to 16 in the routing table. •...

  • Page 44: Rip Message Format

    RIPv1, a classful routing protocol, supports message advertisement through broadcast only. RIPv1 protocol messages do not carry mask information, so it can only recognize routing information of natural networks, such as Class A, B, and C. For this reason, RIPv1 does not support discontiguous subnets.
  • Page 45 RIPv2 message format The format of a RIPv2 message, as shown in Figure 8, is similar to RIPv1. Figure 8 RIPv2 message format The differences between RIPv1 and RIPv2 messages are as follows: • Version: Version of RIP. For RIPv2, the value is 0x02. •...

  • Page 46: Supported Rip Features

    RFC 1723 only defines plain text authentication. For MD5 authentication information, see RFC 2453 RIP • Version 2. With RIPv1, you can configure the authentication mode in interface view; however, the configuration • will not take effect because RIPv1 does not support authentication. Supported RIP features The current implementation supports the following RIP features: •...
  • Page 47 Enabling RIP and a RIP interface To do… Use the command… Remarks Enter system view system-view –– Step 1 Required Enable a RIP process process-id vpn- Step 2 and enter RIP view instance vpn-instance-name ] Not enabled by default Enable RIP on the Step 3 Required interface attached to...

  • Page 48: Configuring Rip Route Control

    Configuring an RIP version You can configure an RIP version in RIP view or interface view under the following conditions: • If neither global nor interface RIP version is configured, then the interface sends RIPv1 broadcasts and can receive RIPv1 broadcast and unicast packets, and RIPv2 broadcast, multicast, and unicast packets.

  • Page 49: Configuring An Additional Routing Metric

    • Configure RIP basic functions. Configuring an additional routing metric An additional routing metric can be added to the metric of an inbound or outbound RIP route. If the outbound additional metric is added to the metric of a sent route, then the route’s metric in the routing table is not changed.

  • Page 50: Disabling Host Route Reception

    To do… Use the command… Remarks Optional Enabled by default If the subnet routes in the Enable RIPv2 automatic Step 3 routing table summary route summarization consecutive, disable automatic route summarization avoid black hole routing. Advertising a summary route To do… Use the command…...

  • Page 51: Advertising A Default Route

    To do… Use the command… Remarks system-view Enter system view — Step 1 vpn- process-id Enter RIP view — Step 2 instance vpn-instance-name ] Required Disable RIP from receiving Step 3 undo host-route host routes Enabled by default Advertising a default route Under the following conditions, you can configure RIP to advertise a default route with a specified metric to RIP neighbors.

  • Page 52: Configuring Inbound Or Outbound Route Filtering

    Configuring inbound or outbound route filtering The switch supports route filtering. You can filter routes by configuring the inbound and outbound route filtering policies by referencing an ACL or IP prefix list. You can also configure the router to receive routes only from a specified neighbor. To do…...

  • Page 53: Configuring Rip Route Redistribution

    Configuring RIP route redistribution If a router runs RIP and other routing protocols, then you can configure RIP to redistribute OSPF, IS-IS, BGP, static, and direct routes. To do… Use the command… Remarks Enter system view system-view –– Step 1 rip [ process-id ] [ vpn-instance Enter RIP view ––...

  • Page 54: Configuring Split Horizon And Poison Reverse

    To do… Use the command… Remarks rip [ process-id ] [ vpn-instance Enter RIP view –– Step 2 vpn-instance-name ] Optional The default update timers garbage-collect timer, timeout timer, garbage-collect-value | suppress suppress timer, and Configure values for RIP timers Step 3 suppress-value | timeout timeout- garbage-collect timer...

  • Page 55: Configuring The Maximum Number Of Load Balanced Routes

    Enabling poison reverse The poison reverse function allows an interface to advertise the routes received from neighbors. The metric of these routes is set to 16 (unreachable) so traffic will move through an interface in only one direction to avoid outing loops between neighbors. To do…...

  • Page 56: Enabling Source Ip Address Check On Incoming Rip Updates

    To do… Use the command… Remarks Optional Enable zero field check on Step 3 checkzero received RIPv1 messages Enabled by default Enabling source IP address check on incoming RIP updates You can enable source IP address check on incoming RIP updates. For a message received on an Ethernet interface, RIP compares the source IP address of the message with the IP address of the interface.

  • Page 57: Specifying A Rip Neighbor

    To do… Use the command… Remarks rip authentication-mode { md5 Configure RIPv2 rfc2082 key-string key-id Step 3 Required authentication rfc2453 key-string } | simple password } Specifying a RIP neighbor Usually, RIP sends messages to broadcast or multicast addresses. On non-broadcast or multicast links, you must manually specify RIP neighbors.

  • Page 58: Configuring Rip Frr

    Sending large numbers of RIP packets at the same time may affect switch performance and consume large network bandwidth. To solve this problem, specify the maximum number of RIP packets that can be sent at the specified interval. To do… Use the command…...

  • Page 59: Configuring Bfd For Rip

    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 with RIP FRR. For more information about routing policy configuration, see the Routing Policy in the Layer 3 – IP Routing Configuration Guide. To do…...

  • Page 60: Bidirectional Detection In Bfd Control Packet Mode

    To do… Use the command… Remarks interface interface-type interface- Enter interface view — Step 3 number Required Enable BFD on the RIP Step 4 rip bfd enable interface Disabled by default Bidirectional detection in BFD control packet mode To do… Use the command…...

  • Page 61: Rip Configuration Examples

    To do… Use the command… Remarks display rip process-id route [ statistics | ip- Display routing information about address { mask | mask-length } | peer ip- a specified RIP process address ] Reset a RIP process reset rip process-id process Available in user view reset rip process-id statistics Clear the statistics of a RIP process...
  • Page 62 [SwitchB-rip-1] network 10.0.0.0 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 ---------------------------------------------------------------------- ---- Peer 192.168.1.2 on Vlan-interface100 Destination/Mask Nexthop...

  • Page 63: Configuring Rip Route Redistribution

    Configuring RIP route redistribution Network requirements • Two RIP processes, as shown in Figure 12, are running on Switch B, which communicates with Switch A through RIP 100 and with Switch C through RIP 200. • Configure route redistribution on Switch B to make RIP 200 redistribute direct routes and routes from RIP 100.
  • Page 64 [SwitchB-rip-200] version 2 [SwitchB-rip-200] undo summary [SwitchB-rip-200] quit Enable RIP 200 and specify RIP version 2 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 Display the routing table of Switch C. [SwitchC] display ip routing-table Routing Tables: Public Destinations : 6...

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

    Configure a filtering policy to filter redistributed routes. Define ACL 2000 and reference it to a filtering policy to filter routes redistributed from RIP 100 on Switch B, making the route not advertised to Switch C. [SwitchB] acl number 2000 [SwitchB-acl-basic-2000] rule deny source 10.2.1.1 0.0.0.255 [SwitchB-acl-basic-2000] rule permit [SwitchB-acl-basic-2000] quit...
  • Page 66 Configuration procedure Configure IP addresses for the interfaces (details not shown). Configure RIP basic functions. Configure Switch A. <SwitchA> system-view [SwitchA] rip 1 [SwitchA-rip-1] network 1.0.0.0 [SwitchA-rip-1] version 2 [SwitchA-rip-1] undo summary [SwitchA-rip-1] quit Configure Switch B. <SwitchB> system-view [SwitchB] rip 1 [SwitchB-rip-1] network 1.0.0.0 [SwitchB-rip-1] version 2 [SwitchB-rip-1] undo summary...

  • Page 67: Configuring Rip To Advertise A Summary Route

    1.1.2.0/24, cost 0, nexthop 1.1.2.1, Rip-interface 1.1.3.0/24, cost 1, nexthop 1.1.1.2 1.1.4.0/24, cost 1, nexthop 1.1.2.2 1.1.5.0/24, cost 2, nexthop 1.1.1.2 1.1.5.0/24, cost 2, nexthop 1.1.2.2 The display shows two RIP routes to network 1.1.5.0/24. Their next hops are Switch B (1.1.1.2) and Switch C (1.1.2.2), respectively, with the same cost of 2.
  • Page 68 Figure 14 Network diagram for RIP summary route advertisement Configuration procedure Configure IP addresses for interfaces (details not shown). Configure OSPF basic functions. Configure Switch A. <SwitchA> system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 10.5.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit Configure Switch B.
  • Page 69 [SwitchC] rip 1 [SwitchC-rip-1] network 11.3.1.0 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary Configure Switch D. <SwitchD> system-view [SwitchD] rip 1 [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 the routes from OSPF process 1 and direct routes on Switch [SwitchC-rip-1] import-route direct [SwitchC-rip-1] import-route ospf 1 Display the routing table information of Switch D.

  • Page 70: Rip Frr Configuration Example

    Destination/Mask Proto Cost NextHop Interface 10.0.0.0/8 11.3.1.1 Vlan300 11.3.1.0/24 Direct 0 11.3.1.2 Vlan300 11.3.1.2/32 Direct 0 127.0.0.1 InLoop0 11.4.1.0/24 Direct 0 11.4.1.2 Vlan400 11.4.1.2/32 Direct 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 RIP FRR configuration example Network requirements Switch S, Switch A, and Switch D are interconnected through RIPv2, as illustrated in Figure 15.
  • Page 71 [SwitchS-route-policy] apply fast-reroute backup-interface vlan- interface 100 backup-nexthop 12.12.12.2 [SwitchS-route-policy] quit [SwitchS] rip 1 [SwitchS-rip-1] fast-reroute route-policy frr [SwitchS-rip-1] quit Configure Switch D. <SwitchD> system-view [SwitchD] bfd echo-source-ip 4.4.4.4 [SwitchD] ip ip-prefix abc index 10 permit 1.1.1.1 32 [SwitchD] route-policy frr permit node 10 [SwitchD-route-policy] if-match ip-prefix abc [SwitchD-route-policy] apply fast-reroute backup-interface vlan- interface 101 backup-nexthop 24.24.24.2...

  • Page 72: Configuring Bfd For Rip (Single-Hop Detection In Bfd Echo Packet Mode)

    NextHop: 13.13.13.1 Interface: vlan200 BkNextHop: 24.24.24.2 BkInterface: vlan101 RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h01m27s Tag: 0 Configuring BFD for RIP (single-hop detection in BFD echo packet mode) Network requirements • Switch A and Switch C are interconnected through a Layer 2 switch, as shown in Figure 16. VLAN-interface 100 of the two switches runs RIP process 1;...
  • Page 73 Configuration procedure Configure IP addresses for interfaces (details not shown). Configure RIP basic functions. Configure Switch A. <SwitchA> system-view [SwitchA] rip 1 [SwitchA-rip-1] network 192.168.1.0 [SwitchA-rip-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] rip bfd enable [SwitchA-Vlan-interface100] quit [SwitchA] rip 2 [SwitchA-rip-2] network 192.168.2.0 Configure Switch B.
  • Page 74 Verify the configuration. Display the BFD session information of Switch A. <SwitchA> display bfd session Total Session Num: 1 Init Mode: Active Session Working Under Echo Mode: SourceAddr DestAddr State Holdtime Interface 192.168.1.1 192.168.1.2 2000ms Vlan100 Display the RIP route learned from Switch B on Switch A. <SwitchA>...

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

    Route Flags: R - RIP, T - TRIP P - Permanent, A - Aging, S - Suppressed, G - Garbage- collect ---------------------------------------------------------------------- ------ Display the RIP route 100.1.1.0/24 learned on Switch A. <SwitchA> display ip routing-table 100.1.1.0 24 verbose Routing Table : Public Summary Count : 1 Destination: 100.1.1.0/24 Protocol: RIP...
  • Page 76 Figure 17 Network diagram for configuring BFD for RIP (bidirectional detection in BFD control packet mode) Switch D Vlan-int300 Vlan-int400 192.168.3.2/24 192.168.4.1/24 Vlan-int400 Vlan-int300 192.168.4.2/24 192.168.3.1/24 Switch B Vlan-int200 Vlan-int100 192.168.2.1/24 192.168.1.1/24 Vlan-int100 Vlan-int200 192.168.1.2/24 192.168.2.2/24 Switch A Switch C Configuration procedure Configure IP addresses for interfaces (details not shown).
  • Page 77 [SwitchC-rip-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] rip bfd enable [SwitchC-Vlan-interface200] quit Configure Switch D. <SwitchD> system-view [SwitchD] rip 1 [SwitchD-rip-1] network 192.168.3.0 [SwitchD-rip-1] network 192.168.4.0 Configure BFD parameters. Configure Switch A. [SwitchA] bfd session init-mode active [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] bfd min-transmit-interval 500 [SwitchA-Vlan-interface100] bfd min-receive-interval 500 [SwitchA-Vlan-interface100] bfd detect-multiplier 7...
  • Page 78 <SwitchA> display ip routing-table 100.1.1.0 24 verbose Routing Table : Public Summary Count : 2 Destination: 100.1.1.0/24 Protocol: RIP Process ID: 1 Preference: 100 Cost: 1 NextHop: 192.168.1.2 Interface: vlan-interface 100 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 0.0.0.0 Neighbor : 192.168.1.2 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h00m47s...

  • Page 79: Troubleshooting Rip

    Protocol: RIP Process ID: 2 Preference: 100 Cost: 2 NextHop: 192.168.3.2 Interface: vlan-interface 300 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 0.0.0.0 Neighbor : 192.168.3.2 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h18m40s Tag: 0 Troubleshooting RIP No RIP updates received Symptom: No RIP updates are received when the links work well.

  • Page 80: Ospf Configuration

    OSPF configuration OSPF is a link state interior gateway protocol developed by the OSPF working group of the IETF. At present, OSPF version 2 (RFC 2328) is used. The term router in this document refers to both routers and Layer 3 switches. •...
  • Page 81 • Each OSPF router collects LSAs from other routers to compose an LSDB. An LSA describes the network topology around a router, so the LSDB describes the entire network topology of the AS. • Each router transforms the LSDB in the area to a weighted directed graph, which actually reflects the topology architecture of the entire network.

  • Page 82: Ospf Area Partition

    • NSSA LSA: Type-7 LSA, as defined in RFC 1587, originated by ASBRs in NSSAs and flooded throughout a single NSSA. NSSA LSAs describe routes to other ASs. • Opaque LSA: A proposed type of LSA, the format consisting of a standard LSA header and application specific information.
  • Page 83 Figure 18 OSPF area partition Area 4 Area 1 Area 0 Area 2 Area 3 After area partition, area border routers perform route summarization to reduce the number of LSAs advertised to other areas and minimize the effect of topology changes. Backbone area and virtual links Each AS has a backbone area, which is responsible for distributing routing information between non-backbone areas.
  • Page 84 Another application of virtual links is to provide redundant links. If the backbone area cannot maintain internal connectivity due to a physical link failure, configuring a virtual link can guarantee logical connectivity in the backbone area, as shown in Figure 20. Figure 20 Virtual link application 2 The virtual link between the two ABRs acts as a point-to-point connection.
  • Page 85 NSSA area Similar to a stub area, an NSSA area imports no AS external LSA (Type-5 LSA), but can import Type-7 LSAs that are generated by the ASBR and distributed throughout the NSSA area. When traveling to the NSSA ABR, Type-7 LSAs are translated into Type-5 LSAs by the ABR for advertisement to other areas.

  • Page 86: Router Types

    • Compared with a stub area, an NSSA area can import external routes through Type-7 LSAs advertised by the ASBR. • Compared with an NSSA area, a totally NSSA area does not import inter-area routes. Router types Classification of routers The following are OSPF router types and their positions in the AS: •...

  • Page 87: Classification Of Ospf Networks

    • Inter-area route • Type-1 external route • Type-2 external route The intra-area and inter-area routes describe the network topology of the AS, while external routes describe routes to destinations outside the AS. OSPF classifies external routes into two types: Type-1 and Type-2. A Type-1 external route is an IGP route, such as a RIP or static route, that has high credibility and whose cost is comparable with the cost of an OSPF internal route.

  • Page 88: Dr And Bdr

    • NBMA networks are fully meshed, non-broadcast and multi access. P2MP networks are not required to be fully meshed. • On NBMA networks, you must elect the DR and BDR, while on P2MP networks, DR and BDR are not available. •...

  • Page 89: Ospf Packet Formats

    DR and BDR election Routers in a network elect the DR and BDR according to their router priorities and router IDs. Routers with a router priority value higher than 0 are candidates for DR and BDR election. The election votes are hello packets. Each router sends the DR elected by itself in a hello packet to all the other routers.
  • Page 90 • Type: OSPF packet type from 1 to 5, corresponding with hello, DD, LSR, LSU, and LSAck, respectively. • Packet length: Total length of the OSPF packet in bytes, including the header. • Router ID: ID of the advertising router. •...
  • Page 91 Major fields of the hello packet are as follows: • Network mask: Network mask associated with the router’s sending interface. If two routers have different network masks, they cannot become neighbors. • HelloInterval: Interval for sending hello packets. If two routers have different intervals, they cannot become neighbors.
  • Page 92 • M (More): The More bit, which is set to 0 if the packet is the last packet of DD packets, and set to 1 if more DD Packets are to follow. • MS: The Master/Subordinate bit. When set to 1, it indicates that the router is the master during the database exchange process.
  • Page 93 Figure 30 LSU packet format Version Packet length Router ID Area ID Checksum AuType Authentication Authentication Number of LSAs LSAck packet LSAck packets are used to acknowledge received LSU packets by carrying LSA headers to describe corresponding LSAs. Multiple LSAs can be acknowledged in a single LSAck packet. Figure 31 LSAck packet format LSA header format...
  • Page 94 Figure 32 LSA header format Major fields of the LSA header are as follows: • LS age: Time, in seconds, elapsed since the LSA was originated. An LSA ages in the LSDB (added by one per second), but does not age in transmission. •...
  • Page 95 Major fields of the Router LSA are as follows: • Link state ID: ID of the router originating the LSA. • V (Virtual Link): Set to 1 if the router originating the LSA is a virtual link endpoint. • E (External): Set to 1 if the router originating the LSA is an ASBR. •...
  • Page 96 Network summary LSAs (Type-3 LSAs) and ASBR summary LSAs (Type-4 LSAs) are originated by ABRs. Other than the difference in the Link state ID field, the formats of Type 3 and Type 4 summary LSAs are identical. Figure 35 Summary LSA format Major fields of the Summary LSA are as follows: •...
  • Page 97 Figure 36 AS external LSA format Major fields of the AS external LSA are as follows: • Link state ID: The IP address of another AS to be advertised. When describing a default route, the Link state ID is always set to default destination (0.0.0.0) and the network mask is set to 0.0.0.0 •...
  • Page 98 Figure 37 NSSA external LSA format Grace LSA Originating from the GR Restarter, a Grace LSA, as shown in Figure 38, is sent to GR Helpers, notifying them of a GR. Figure 38 Grace LSA format The major field of the Grace LSA is as follows: •...

  • Page 99: Supported Ospf Features

    Supported OSPF features Multiprocess With multiprocess support, multiple OSPF processes can run on a router simultaneously and independently. Routing information interactions between different processes seem like interactions between different routing protocols. Multiple OSPF processes can use the same RID. An interface of a router can only belong to a single OSPF process. Authentication OSPF supports authentication on packets.
  • Page 100 • Obtain OSPF neighbor information without changing adjacencies. • Obtain the LSDB. OSPF GR involves the following types: • IETF standard GR: Uses Opaque LSA to implement GR. • Non-IETF standard GR: Uses LLS to advertise GR capability and uses out of band synchronization to synchronize the LSDB.

  • Page 101: Protocols And Standards

    OSPF supports multi-instance, which can run on PEs in VPN networks. In BGP MPLS VPN networks, multiple sites in the same VPN can use OSPF as the internal routing protocol, but they are treated as different ASs. An OSPF route learned by a site will be forwarded to another site as an external route, which leads to heavy OSPF routing traffic and management issues.

  • Page 102: Enabling Ospf

    For details about a global Router ID, see IP Routing Basics in the Layer 3 – IP Routing Configuration Guide. H3C rec specifying a Router ID when creating the OSPF process. The system supports OSPF multiprocess and OSPF multi-instance as follows: •...

  • Page 103: Configuring Ospf Areas

    H3C recommends configuring a description for each OSPF process to help identify purposes of • processes and for ease of management and memorization. H3C recommends configuring a description for each area to help identify purposes of areas and for • ease of management and memorization.

  • Page 104: Configuring A Stub Area

    Configuring a stub area Configure a non-backbone area at the AS edge as a stub area by configuring the stub command on all the routers attached to the area. In this way, Type-5 LSAs, which describe AS external routes, will not be flooded within the stub area, reducing the routing table size. The ABR generates a default route into the stub area so all packets destined outside of the AS are sent through the default route.

  • Page 105: Configuring A Virtual Link

    To do… Use the command… Remarks Enter system view system-view Step 1 — ospf process-id Enter OSPF view router-id router-id | vpn- — Step 2 instance instance-name ] * Enter area view Step 3 area area-id Required nssa default-route- advertise | no-import- Required Configure the area as route | no-summary |...

  • Page 106: Configuring Ospf Network Types

    To do… Use the command… Remarks vlink-peer router-id [ Required hello seconds retransmit seconds | You must configure this trans-delay seconds command on both ends Configure a virtual | dead of a virtual link. Step 4 seconds link simple plain Note that hello...

  • Page 107: Configuring The Ospf Network Type For An Interface As Broadcast

    Configuring the OSPF network type for an interface as broadcast To do… Use the command… Remarks Enter system view Step 1 system-view — interface interface- Enter interface view Step 2 — type interface-number Required Configure the OSPF Step 3 By default, the network ospf network- network type for the...

  • Page 108: Configuring The Ospf Network Type For An Interface As P2Mp

    To do… Use the command… Remarks ospf [ process-id | router-id router-id | Enter OSPF view Step 6 — vpn-instance instance-name ] * peer ip-address [ cost Specify a neighbor Step 7 value | dr-priority dr- Required and its DR priority priority ] The DR priority configured with the ospf dr-priority command and the one with the peer command •...

  • Page 109: Configuring The Ospf Network Type For An Interface As P2P

    To do… Use the command… Remarks Required By default, the network type interface depends on the link layer protocol. After you configure the Configure the OSPF Step 3 OSPF network type for an ospf network-type network type for the interface P2MP p2mp [ unicast ] interface as P2MP...

  • Page 110: Configuring Ospf Route Control

    Configuring OSPF route control This section covers how to control OSPF routing information advertisement and reception, and route redistribution from other protocols. Prerequisites • IP addresses for interfaces • OSPF functions • Corresponding filters, if routing information filtering is needed Configuring OSPF route summarization Route summarization is when an ABR or ASBR summarizes routes with the same prefix into a single route and distributes it to other areas.
  • Page 111 To do… Use the command… Remarks Enter system view system-view Step 1 — ospf process-id router-id router-id Enter OSPF view Step 2 — vpn-instance instance- name ] * Enter OSPF area Step 3 area area-id — view Required abr-summary command address { mask | mask- Configure ABR route available on an ABR...

  • Page 112: Configuring Ospf Inbound Route Filtering

    Configuring OSPF inbound route filtering OSPF is a link state-based interior gateway protocol, so routing information is contained in LSAs. Routes computed by OSPF can be filtered, and only permitted routes are installed into the routing table. The filtering methods are as follows: •...

  • Page 113: Configuring An Ospf Cost For An Interface

    To do… Use the command… Remarks Required filter { acl-number | ip-prefix Configure ABR Type-3 Step 4 ip-prefix-name } { import | LSA filtering configured by export } default Configuring an OSPF cost for an interface You can configure an OSPF cost for an interface with one of the following methods: •...

  • Page 114: Configuring The Maximum Number Of Ospf Routes

    Configuring the maximum number of OSPF routes To do… Use the command… Remarks Enter system view system-view — Step 1 ospf [ process-id | router-id Enter OSPF view Step 2 vpn-instance — router-id instance-name ] * Optional By default, the maximum number Configure the maximum...

  • Page 115: Configuring Ospf Route Redistribution

    To do… Use the command… Remarks Enter system Step 1 system-view — view ospf process-id Enter OSPF router-id Step 2 router-id — view vpn-instance instance- name ] * Optional Configure a preference [ ase ] [ Step 3 The priority of OSPF internal priority for route-policy route-policy- routes defaults to 10.
  • Page 116 Only active routes can be redistributed. Use the display ip routing-table protocol command to display route state information. Configure OSPF to redistribute a default route Using the import-route command cannot redistribute a default external route; you must use the default-route-advertise command. To do…...

  • Page 117: Advertising A Host Route

    Advertising a host route To do… Use the command… Remarks Enter system view system-view — Step 1 ospf [ process-id | router-id Enter OSPF view vpn-instance — router-id Step 2 instance-name ] * Enter area view area area-id — Step 3 Required host-advertise ip-address cost Advertise a host route...

  • Page 118: Specifying An Lsa Transmission Delay

    To do… Use the command… Remarks Enter system view Step 1 system-view — Enter interface interface Step 2 interface-type — view interface-number Optional The hello interval on P2P, Broadcast Specify the hello Step 3 interfaces defaults to ospf timer hello seconds interval seconds defaults to 30 seconds...

  • Page 119: Specifying Spf Calculation Interval

    To do… Use the command… Remarks Enter system view system-view — Step 1 interface interface- Enter interface view — Step 2 type interface-number Specify an LSA Optional ospf trans-delay Step 3 transmission delay seconds Defaults to one second Specifying SPF calculation interval The LSDB changes lead to SPF calculations.

  • Page 120: Specifying The Lsa Generation Interval

    To do… Use the command… Remarks ospf [ process-id | router-id Enter OSPF view vpn-instance — Step 2 router-id instance-name ] * Optional Configure the LSA Step 3 minimum repeat arrival Defaults lsa-arrival-interval interval interval 1000 milliseconds The interval set with the lsa-arrival-interval command should be smaller or equal to the interval set with the lsa-generation-interval command.

  • Page 121: Disabling Interfaces From Receiving Or Sending Ospf Packets

    With this command configured, when network changes are not frequent, LSAs are generated at the minimum-interval. If network changes become frequent, the LSA generation interval is incremented by incremental-interval•2n-2 (n is the number of generation times) each time a generation occurs, up to the maximum-interval.

  • Page 122: Configuring Ospf Authentication

    Enter system view system-view — Step 1 ospf [ process-id | router- Enter OSPF view Step 2 id router-id | vpn-instance — instance-name ] * Configure the Required Step 3 router as a stub stub-router configured router default A stub router has nothing to do with a stub area. Configuring OSPF authentication OSPF supports packet authentication to ensure the security of packet exchange.

  • Page 123: Adding The Interface Mtu Into Dd Packets

    To do… Use the command… Remarks configured by Configure the Step 9 default ospf authentication-mode { authentication mode md5 | hmac-md5 } key-id [ (MD5 authentication) plain | cipher ] password for the interface Adding the interface MTU into DD packets Generally, when an interface sends a DD packet, it adds 0 into the interface MTU field of the DD packet rather than the interface MTU.

  • Page 124: Making External Route Selection Rules Defined In Rfc 1583 Compatible

    Step 3 rfc1583 compatible compatible Compatible by default To avoid routing loops, H3C recommends that you configure all the routers to be either compatible or incompatible with the external route selection rules defined in RFC1583. Logging neighbor state changes To do…...

  • Page 125: Enabling Message Logging

    • Level-4: alarm traps • Level-5: normal, but important, traps • Level-6: notification traps The generated traps are sent to the information center of the switch. The output rules of the traps, namely, whether to output the traps and the output direction, are determined according to the information center configuration.

  • Page 126: Enabling The Advertisement And Reception Of Opaque Lsas

    Enabling the advertisement and reception of opaque LSAs With the advertisement and reception of opaque LSAs feature enabled, the OSPF router can receive and advertise Type 9, Type 10, and Type 11 opaque LSAs. To do… Use the command… Remarks Enter system view Step 1 system-view...

  • Page 127: Configuring Ospf Frr

    To do… Use the command… Remarks Enter system Step 1 system-view — view ospf [ process-id | router-id router- Enter OSPF Step 2 id | vpn-instance instance-name ] — view Optional Configure the default, Step 3 transmit-pacing interval interval LSU transmit OSPF interface count count...

  • Page 128: Prerequisites

    shortest path based on the new network topology, and forwards packets over the path after network convergence. You can either configure OSPF FRR to calculate a backup next hop automatically, or designate a backup next hop by using a routing policy for routes matching the specified filtering conditions. Prerequisites •...

  • Page 129: Configuring Ospf Graceful Restart

    To do… Use the command… Remarks ospf [ process-id | router-id router-id | vpn- Enter OSPF view — Step 3 instance instance-name ] * Enable OSPF FRR Step 4 to designate a Required backup next hop fast-reroute route-policy route-policy-name Not configured by default by using a routing policy Configuring OSPF graceful restart...

  • Page 130: Configuring The Ospf Gr Helper

    To do… Use the command… Remarks Enable the link-local Required Step 3 enable link-local- signaling capability signaling Disabled by default Enable the out-of-band Step 4 Required enable out-of-band- re-synchronization resynchronization capability Disabled by default Enable non-IETF Step 5 standard Graceful Required graceful-restart Restart capability for...

  • Page 131: Triggering Ospf Graceful Restart

    To do… Use the command… Remarks ospf [ process-id | Enable OSPF and enter router-id router-id | Step 2 — its view vpn-instance instance-name ] * Enable the link-local Required enable link-local- Step 3 signaling capability signaling Disabled by default Enable the out-of-band Step 4 Required...

  • Page 132: Displaying And Maintaining Ospf

    established, it is in the Down state. In this state, BFD control packets are sent at an interval of not less than one second to reduce BFD control packet traffic. After the BFD session is established, BFD control packets are sent at the negotiated interval, thereby implementing fast fault detection. To configure BFD for OSPF, you must configure OSPF first.
  • Page 133 To do… Use the command… Remarks Display OSPF brief Step 1 display ospf [ process-id ] brief information display ospf process-id Display OSPF statistics Step 2 cumulative display ospf [ process-id ] lsdb [ brief | [ { ase | router | network | summary | asbr | nssa | Display LSDB Step 3...

  • Page 134: Ospf Configuration Examples

    To do… Use the command… Remarks reset ospf [ process-id ] counters [ Reset OSPF counters Step 15 neighbor [ interface-type interface- number ] [ router-id ] ] Available reset ospf [ process-id ] process [ user Reset an OSPF process Step 16 graceful-restart ] view...
  • Page 135 Configure OSPF basic functions. Configure Switch A. <SwitchA> system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] area 1 [SwitchA-ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.1] quit [SwitchA-ospf-1] quit Configure Switch B. <SwitchB> system-view [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] area 2...
  • Page 136 [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 Address: 10.1.1.2 GR State: Normal State: Full Mode: Nbr is Master Priority: 1 DR: 10.1.1.1 BDR: 10.1.1.2 MTU: 0 Dead timer due in 37 Neighbor is up for 06:03:59 Authentication Sequence: [ 0 ]...
  • Page 137 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 the LSDB on Switch A. [SwitchA] display ospf lsdb OSPF Process 1 with Router ID 10.2.1.1 Link State Database Area: 0.0.0.0 Type LinkState ID AdvRouter...

  • Page 138: Configuring Ospf Route Redistribution

    [SwitchD] display ospf routing OSPF Process 1 with Router ID 10.5.1.1 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.3.1.0/24 Transit 10.3.1.2 10.3.1.1 0.0.0.2 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...
  • Page 139 • Switch C is configured as an ASBR to redistribute external routes (static routes). Routing information is propagated properly in the AS. Figure 42 Network diagram for OSPF redistributing routes from outside an AS Configuration procedure Configure IP addresses for interfaces (details not shown). Configure OSPF basic functions (see Configuring OSPF basic functions).

  • Page 140: Configuring Ospf To Advertise A Summary Route

    Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.3.1.0/24 Transit 10.3.1.2 10.3.1.1 0.0.0.2 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...
  • Page 141 Figure 43 Network diagram for OSPF summary route advertisement Configuration procedure Configure IP addresses for interfaces (details not shown). Configure OSPF basic functions. Configure Switch A. <SwitchA> system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [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.
  • Page 142 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit Configure Switch D. <SwitchD> system-view [SwitchD] ospf [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] quit Configure Switch E. <SwitchE> system-view [SwitchE] ospf [SwitchE-ospf-1] area 0 [SwitchE-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchE-ospf-1-area-0.0.0.0] network 10.4.1.0 0.0.0.255 [SwitchE-ospf-1-area-0.0.0.0] quit [SwitchE-ospf-1] quit Configure BGP.

  • Page 143: Configuring An Ospf Stub Area

    10.1.1.0/24 O_ASE 11.2.1.1 Vlan100 10.2.1.0/24 O_ASE 11.2.1.1 Vlan100 10.3.1.0/24 O_ASE 11.2.1.1 Vlan100 10.4.1.0/24 O_ASE 11.2.1.1 Vlan100 11.2.1.0/24 Direct 0 11.2.1.2 Vlan100 11.2.1.2/32 Direct 0 127.0.0.1 InLoop0 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 Configure summary route 10.0.0.0/8 on Switch B and advertise it. [SwitchB-ospf-1] asbr-summary 10.0.0.0 8 Display the OSPF routing table of Switch A.
  • Page 144 Figure 44 Network diagram for OSPF Stub area configuration 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.2.1.1/24 10.3.1.1/24 Vlan-int200 Vlan-int200 Area 1 Area 2 10.3.1.2/24 10.2.1.2/24 Stub ASBR 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).
  • Page 145 10.2.1.0/24 Transit 10.2.1.2 10.2.1.1 0.0.0.1 10.3.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.4.1.0/24 Stub 10.4.1.1 10.4.1.1 0.0.0.1 10.5.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.1.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 Routing for ASEs Destination Cost Type NextHop AdvRouter 3.1.2.0/24 Type2 10.2.1.1 10.5.1.1 Total Nets: 6 Intra Area: 2 Inter Area: 3 ASE: 1...
  • Page 146 Routing for Network Destination Cost Type NextHop AdvRouter Area 0.0.0.0/0 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.2.1.0/24 Transit 10.2.1.2 10.2.1.1 0.0.0.1 10.3.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.4.1.0/24 Stub 10.4.1.1 10.4.1.1 0.0.0.1 10.5.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 10.1.1.0/24 Inter 10.2.1.1 10.2.1.1 0.0.0.1 Total Nets: 6 Intra Area: 2 Inter Area: 4 ASE: 0...

  • Page 147: Configuring An Ospf Nssa Area

    Total Nets: 3 Intra Area: 2 Inter Area: 1 ASE: 0 NSSA: 0 After this configuration, routing entries on the stub router are further reduced, containing only one default external route. Configuring an OSPF NSSA area Network requirements Figure 45 shows an AS split into three areas, where all switches run OSPF. Switch A and Switch B act as ABRs to forward routing information between areas.
  • Page 148 [SwitchC-ospf-1-area-0.0.0.1] nssa [SwitchC-ospf-1-area-0.0.0.1] quit [SwitchC-ospf-1] quit H3C recommends configuring the nssa command with the keyword default-route-advertise no- summary on Switch A (an ABR) to reduce the routing table size on NSSA routers. On other NSSA routers, use the nssa command.

  • Page 149: Configuring Ospf Dr Election

    Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 Inter 10.3.1.1 10.3.1.1 0.0.0.2 10.3.1.0/24 Transit 10.3.1.2 10.3.1.1 0.0.0.2 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.3.0/24 Type2 10.3.1.1 10.2.1.1...
  • Page 150 Configuration procedure Configure IP addresses for interfaces (details not shown). Configure OSPF basic functions. 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 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit Configure Switch B. <SwitchB> system-view [SwitchB] router id 2.2.2.2 [SwitchB] ospf [SwitchB-ospf-1] area 0...
  • Page 151 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 Dead timer due in 38 Neighbor is up for 00:01:31 Authentication Sequence: [ 0 ] Router ID: 3.3.3.3 Address: 192.168.1.3...
  • Page 152 [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 Subordinate Priority: 100 DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0 Dead timer due in 31 Neighbor is up for 00:11:17 Authentication Sequence: [ 0 ] Router ID: 2.2.2.2...
  • Page 153 Router ID: 1.1.1.1 Address: 192.168.1.1 GR State: Normal State: Full Mode: Nbr is Subordinate Priority: 100 DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0 Dead timer due in 39 Neighbor is up for 00:01:40 Authentication Sequence: [ 0 ] Router ID: 2.2.2.2 Address: 192.168.1.2 GR State: Normal State: 2-Way...

  • Page 154: Configuring Ospf Virtual Links

    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. Configuring OSPF virtual links Network requirements • In Figure 47, Area 2 has no direct connection to Area 0, and Area 1 acts as the Transit Area to connect Area 2 to Area 0 via a configured virtual link between Switch B and Switch •...
  • Page 155 <SwitchB> system-view [SwitchB] ospf 1 router-id 2.2.2.2 [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] area 1 [SwitchB–ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255 [SwitchB–ospf-1-area-0.0.0.1] quit Configure Switch C. <SwitchC> system-view [SwitchC] ospf 1 router-id 3.3.3.3 [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...

  • Page 156: Ospf Graceful Restart Configuration Example

    Configure a virtual link. Configure Switch B. [SwitchB] ospf [SwitchB-ospf-1] area 1 [SwitchB-ospf-1-area-0.0.0.1] vlink-peer 3.3.3.3 [SwitchB-ospf-1-area-0.0.0.1] quit [SwitchB-ospf-1] quit Configure Switch C. [SwitchC] ospf 1 [SwitchC-ospf-1] area 1 [SwitchC-ospf-1-area-0.0.0.1] vlink-peer 2.2.2.2 [SwitchC-ospf-1-area-0.0.0.1] quit Display the OSPF routing table of Switch B. [SwitchB] display ospf routing OSPF Process 1 with Router ID 2.2.2.2 Routing Tables...
  • Page 157 Figure 48 Network diagram for OSPF GR configuration Router ID: 1.1.1.1 GR restarter Switch A Vlan-int100 192.1.1.1/24 Vlan-int100 Vlan-int100 192.1.1.2/24 192.1.1.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 IP addresses for interfaces (details not shown). Configure OSPF GR.

  • Page 158: Configuring Route Filtering

    [SwitchC-acl-basic-2000] quit [SwitchC] router id 3.3.3.3 [SwitchC] ospf 100 [SwitchC-ospf-100] graceful-restart help 2000 [SwitchC-ospf-100] area 0 [SwitchC-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255 Verify the configuration. After the configurations on Switch A, Switch B, and Switch C are complete and the switches are running steadily, perform OSPF GR on Switch A. <SwitchA>...
  • Page 159 [SwitchC] ip route-static 3.1.2.0 24 10.4.1.2 On Switch C, configure a static route destined for network 3.1.3.0/24. [SwitchC] ip route-static 3.1.3.0 24 10.4.1.2 On Switch C, configure OSPF to redistribute static routes. [SwitchC] ospf 1 [SwitchC-ospf-1] import-route static [SwitchC-ospf-1] quit Display the OSPF routing table of Switch A.
  • Page 160 Destination/Mask Proto Cost NextHop Interface 3.1.1.0/24 O_ASE 10.2.1.2 Vlan200 3.1.2.0/24 O_ASE 10.2.1.2 Vlan200 10.1.1.0/24 Direct 0 10.1.1.1 Vlan100 10.1.1.1/32 Direct 0 127.0.0.1 InLoop0 10.2.1.0/24 Direct 0 10.2.1.1 Vlan200 10.2.1.1/32 Direct 0 127.0.0.1 InLoop0 10.3.1.0/24 OSPF 10.1.1.2 Vlan100 10.4.1.0/24 OSPF 10.2.1.2 Vlan200 10.5.1.0/24 OSPF...

  • Page 161: Configuring Ospf Frr

    10.4.1.0/24 OSPF 10.2.1.2 Vlan200 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 The route destined for 10.5.1.1/24 is filtered out. Configuring OSPF FRR Network requirements Switch S, Switch A, and Switch D belong to the same OSPF domain. They are interconnected through OSPF, as shown in Figure 50.
  • Page 162 [SwitchD] bfd echo-source-ip 4.4.4.4 [SwitchD] ospf 1 [SwitchD-ospf-1] fast-reroute auto [SwitchD-ospf-1] quit Method II: Enable OSPF FRR to designate a backup next hop by using a routing policy. Configure Switch S. <SwitchS> system-view [SwitchS] bfd echo-source-ip 1.1.1.1 [SwitchS] ip ip-prefix abc index 10 permit 4.4.4.4 32 [SwitchS] route-policy frr permit node 10 [SwitchS-route-policy] if-match ip-prefix abc [SwitchS-route-policy] apply fast-reroute backup-interface vlan-...

  • Page 163: Configuring Bfd For Ospf

    RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h01m27s Tag: 0 Display route 1.1.1.1/32 on Switch D, and you can view the backup next hop information. [SwitchD] display ip routing-table 1.1.1.1 verbose Routing Table : Public Summary Count : 1 Destination: 1.1.1.1/32 Protocol: OSPF...
  • Page 164 Configuration procedure Configure IP addresses for interfaces (details not shown). Configure OSPF basic functions. Configure Switch A. [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 10.1.0.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit [SwitchA] interface vlan 10 [SwitchA-Vlan-interface10] ospf bfd enable [SwitchA-Vlan-interface10] quit Configure Switch B.

  • Page 165: Troubleshooting Ospf Configuration

    Display the OSPF neighbor information of Switch A. Switch A has removed its neighbor relationship with Switch B; therefore, no information is output. <SwitchA> display ospf peer OSPF Process 1 with Router ID 192.168.1.40 Neighbor Brief Information Troubleshooting OSPF configuration No OSPF neighbor relationship established Symptom No OSPF neighbor relationship can be established.
  • Page 166 Solution Use the display ospf peer command to display neighbors. Use the display ospf interface command to display OSPF interface information. Use the display ospf lsdb command to display the LSDB to check its integrity. Display information about area configuration using the display current-configuration configuration ospf command.

  • Page 167: Is-Is Configuration

    IS-IS configuration IS-IS overview IS-IS is a dynamic routing protocol designed by the ISO to operate on the CLNP. The term router in this document refers to both routers and Layer switches. The IS-IS routing protocol was modified and extended in RFC 1195 by the IETF for application in both TCP/IP and OSI reference models, and the new one is named Integrated IS-IS or Dual IS-IS.
  • Page 168 IS-IS address format NSAP As shown in Figure 52, an NSAP address consists of the IDP and the DSP. The IDP is equal to the network ID of an IP address, and the DSP is equal to the subnet and host ID. The IDP includes the AFI and the IDI.

  • Page 169: Is-Is Area

    The area information is identified in IS-IS addresses, so a Level-1 router can easily identify packets destined to other areas. • A Level-1 router makes routing decisions based on the system ID. If the destination is not in the area, the packet is forwarded to the nearest Level-1-2 router. •...
  • Page 170 The Level-1 routers in different areas cannot establish neighbor relationships. • The neighbor relationship establishment of Level-2 routers has nothing to do with area. • Figure 53 shows an IS-IS network topology, where Area 1 comprises a set of Level-2 routers and is the backbone.

  • Page 171: Is-Is Network Types

    Figure 54 IS-IS topology 2 The IS-IS backbone does not need to be a specific area. Both the IS-IS Level-1 and Level-2 routers use the SPF algorithm to generate the SPT. Route leaking An IS-IS routing domain is comprised of only one Level-2 area and multiple Level-1 areas. A Level- 1 area consists of a group of Level-1 routers, and is connected with a Level-2 area rather than other Level-1 areas.
  • Page 172 IS-IS cannot run on P2MP links. DIS and pseudonodes On an IS-IS broadcast network, a router is elected as the DIS. The Level-1 and Level-2 DISs are elected respectively. You can assign different priorities for different level DIS elections. The higher a router’s priority is, the more likelihood the router becomes the DIS.

  • Page 173: Is-Is Pdu Format

    IS-IS PDU format PDU header format IS-IS packets are encapsulated into link layer frames. The PDU consists of two parts, the headers and the variable length fields, where the headers comprise the PDU common header and the PDU specific header. All PDUs have the same PDU common header, while the specific headers vary by PDU type.
  • Page 174 Type PDU Type Acronym Level-1 LAN IS-IS hello PDU L1 LAN IIH Level-2 LAN IS-IS hello PDU L2 LAN IIH Point-to-Point IS-IS hello PDU P2P IIH Level-1 Link State PDU L1 LSP Level-2 Link State PDU L2 LSP Level-1 Complete Sequence Numbers PDU L1 CSNP Level-2 Complete Sequence Numbers PDU L2 CSNP...
  • Page 175 • Reserved/Circuit type: The first six bits are reserved with a value of 0. The last two bits indicate the router type. Here, 00 means reserved, 01 indicates L1, 10 indicates L2, and 11 indicates L1/2. • Source ID: System ID of the router advertising the hello packet. •...
  • Page 176 Figure 60 L1/L2 LSP format Major fields of the L1/L2 LSP are as follows: • PDU length: Total length of the PDU in bytes • Remaining lifetime: LSP remaining lifetime in seconds • LSP ID: Consists of the system ID, the pseudonode ID (one byte) and the LSP fragment number (one byte) •...
  • Page 177 Figure 61 LSDB overload SNP format An SNP acknowledges the latest received LSPs. It is similar to an Acknowledge packet, but more efficient. SNP involves CSNP and PSNP, which are further divided into Level-1 CSNP, Level-2 CSNP, Level- 1 PSNP, and Level-2 PSNP. CSNP covers the summary of all LSPs in the LSDB to synchronize the LSDB between neighboring routers.
  • Page 178 PSNP only contains the sequence numbers of one or multiple latest received LSPs. It can acknowledge multiple LSPs at one time. When LSDBs are not synchronized, a PSNP is used to request new LSPs from neighbors. Figure 63 shows the PSNP packet format. Figure 63 L1/L2 PSNP format No.

  • Page 179: Supported Is-Is Features

    CLV Code Name PDU Type LSP Entries Authentication Information IIH, LSP, SNP IP Internal Reachability Information Protocols Supported IIH, LSP IP External Reachability Information L2 LSP Inter-Domain Routing Protocol Information L2 LSP IP Interface Address IIH, LSP Code 1 to 10 of CLV are defined in ISO 10589 (code 3 and 5 are not shown in Table 3), and others are defined in RFC 1195.
  • Page 180 To complete these tasks, the GR Restarter sends an OSPF GR signal to GR Helpers so the GR Helpers keep their adjacencies with the GR Restarter, and then restores the neighbor table after receiving responses from neighbors. Afterwards, the GR Restarter synchronizes the LSDB with all GR-capable neighbors, calculates routes, updates its routing table and forwarding table, and removes stale routes.
  • Page 181 Additional virtual system IDs are configured for the IS-IS router after LSP fragment extension is enabled. Each additional system ID can generate 256 LSP fragments. Both the additional system ID and the system ID must be unique in the entire routing domain. •...

  • Page 182: Protocols And Standards

    A host name is easier to remember than a system ID. After enabling this feature on the router, you can see the host names instead of system IDs using the display command. BFD provides a single mechanism to quickly detect and monitor the connectivity of links between IS-IS neighbors, which reduces network convergence time.

  • Page 183: Enabling Is-Is

    • Configure an IP address for each interface, and ensure all neighboring nodes are reachable to each other at the network layer. Enabling IS-IS To do… Use the command… Remarks system-view Enter system view –– Step 1 Required isis [ process-id ] [ vpn-instance Enable the IS-IS routing Step 2 process and enter its view...

  • Page 184: Configuring The Network Type Of An Interface As P2P

    To do… Use the command… Remarks Optional isis circuit-level [ level-1 | level-1-2 | Specify the circuit level The default is Level- Step 6 level-2 ] 1-2. Configuring the network type of an interface as P2P Interfaces with different network types operate differently. For example, broadcast interfaces on a network must elect the DIS and flood CSNP packets to synchronize the LSDBs, while P2P interfaces on a network need not elect the DIS, and have a different LSDP synchronization mechanism.
  • Page 185 IS-IS cost specified in system view. The cost is applied to the interfaces associated with the IS-IS process. Automatically calculated cost: When the cost style is wide or wide-compatible, IS-IS automatically calculates the cost using the formula: interface cost= (bandwidth reference value/interface bandwidth) ×10.

  • Page 186: Specifying A Priority For Is-Is

    To do… Use the command… Remarks system-view Enter system view — Step 1 isis [ process-id ] [ vpn-instance vpn- Enter IS-IS view — Step 2 instance-name ] Optional cost-style { narrow | wide | wide- compatible | { compatible | narrow- Specify an IS-IS cost style narrow Step 3...

  • Page 187: Configuring The Maximum Number Of Equal-Cost Routes

    To do… Use the command… Remarks isis [ process-id ] [ vpn-instance vpn- Enter IS-IS view –– Step 2 instance-name ] Required preference { route-policy route-policy- Specify a priority for IS-IS Step 3 name | preference } * 15 by default Configuring the maximum number of equal-cost routes If there are multiple equal-cost routes to the same destination, the traffic can be load balanced to enhance efficiency.

  • Page 188: Advertising A Default Route

    The cost of the summary route is the lowest one among the costs of summarized routes. • The router summarizes only the routes in the locally generated LSPs. • Advertising a default route A router running IS-IS cannot redistribute any default routes, which means it cannot advertise a default route to other neighbors.

  • Page 189: Configuring Is-Is Route Filtering

    To do… Use the command… Remarks Required import-route protocol [ process-id | all- No route is redistributed processes | allow-ibgp ] [ cost cost | Redistribute routes by default. Step 3 from another cost-type { external | internal } | [ If no level is specified, routing protocol level-1 | level-1-2 | level-2 ] | route-...

  • Page 190: Configuring Is-Is Route Leaking

    Filtering redistributed routes IS-IS can redistribute routes from other routing protocols (or other IS-IS processes), add them into the IS-IS routing table, and advertise them in LSPs. By reference, a configured ACL, IP prefix list, or routing policy, you can filter redistributed routes and only the routes matching the filter can be added into the IS-IS routing table and advertised to neighbors.

  • Page 191: Tuning And Optimizing Is-Is Networks

    Tuning and optimizing IS-IS networks Prerequisites • Configure IP addresses for interfaces, and make adjacent nodes reachable to each other at the network layer. • Enable IS-IS. Specifying intervals for sending IS-IS hello and CSNP packets To do… Use the command… Remarks system-view Enter system view...

  • Page 192: Configuring A Dis Priority For An Interface

    To do… Use the command… Remarks system-view Enter system view –– Step 1 interface interface-type interface- Enter interface view –– Step 2 number Specify the number of hello Step 3 Optional packets a neighbor must miss isis timer holding-multiplier value before declaring the router is 3 by default down...

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

    To do… Use the command… Remarks system-view Enter system view –– Step 1 Enter interface view interface interface-type interface-number –– Step 2 Required Disable the interface Step 3 from sending or isis silent disabled receiving IS-IS packets default Enabling an interface to send small hello packets IS-IS messages cannot be fragmented at the IP layer because they are directly encapsulated into frames.
  • Page 194 Specify the LSP refresh interval and generation interval Each router needs to refresh LSPs generated by itself at a configurable interval and send them to other routers to prevent valid routes from being aged out. A smaller refresh interval speeds up network convergence but consumes more bandwidth.
  • Page 195 Therefore, IS-IS routers in an area must send LSPs smaller than the smallest interface MTU in this area. If the IS-IS routers have different interface MTUs, H3C recommends configuring the maximum size of generated LSP packets to be smaller than the smallest interface MTU in this area. Otherwise, the routers must dynamically adjust the LSP packet size to fit the smallest interface MTU, which takes time and affects other services.
  • Page 196 To do… Use the command… Remarks Required flash-flood [ flood-count flooding-count | max- Enable LSP flash Step 3 timer-interval flooding-interval | [ level-1 | level- enabled flooding 2 ] ] * default Enabling LSP fragment extension To do… Use the command… Remarks Enter system view system-view...

  • Page 197: Configuring Spf Parameters

    To do… Use the command… Remarks system-view Enter system view –– Step 1 interface interface-type interface- Enter interface view –– Step 2 number Add the interface to a isis mesh-group mesh-group- Required to choose either. Step 3 mesh group number By default, the interface neither belongs to any mesh group nor isis...

  • Page 198: Configuring Is-Is Authentication

    To do… Use the command… Remarks isis [ process-id ] [ vpn-instance vpn-instance-name Enter IS-IS view –– Step 2 set-overload [ on-startup [ [ start-from-nbr Required Set the overload Step 3 system-id [ timeout1 [ nbr-timeout ] ] ] | timeout2 ] [ Not set by default allow { external | interlevel } * ] Configuring IS-IS authentication...

  • Page 199: Configuring Routing Domain Authentication

    To do… Use the command… Remarks Enter system view system-view –– Step 1 isis [ process-id ] [ vpn-instance Enter IS-IS view –– Step 2 vpn-instance-name ] Required Specify the area Step 3 area-authentication-mode { md5 No area authentication authentication mode and | simple } password [ ip | osi ] configured password...

  • Page 200: Configuring A Static System Id To Host Name Mapping

    • If you configure both dynamic and static system ID to host name mappings on a router, the host name for dynamic system ID to host name mapping applies. Configuring a static system ID to host name mapping To do… Use the command...

  • Page 201: Configuring Is-Is Gr

    To do… Use the command... Remarks Optional Not configured by default This command takes effect only on a router with dynamic system ID to Configure a DIS name isis dis-name symbolic-name Step 6 host name mapping configured. This command supported interfaces.

  • Page 202: Configuring Is-Is Nsr

    To do… Use the command… Remarks Required Enable IS-IS, and enter isis [ process-id ] [ vpn-instance vpn- Step 2 IS-IS view instance-name ] Disabled by default Required Enable the GR Step 3 graceful-restart capability for IS-IS Disabled by default Required Set the Graceful Step 4...

  • Page 203: Configuring Is-Is Frr

    To do… Use the command… Remarks Optional non-stop-routing interval interval- 0 seconds by default, that is, Set the NSR interval Step 4 value interval configured. Configuring IS-IS FRR Do not use IS-IS FRR and BFD (for IS-IS) at the same time because IS-IS FRR may fail to take effect. •...

  • Page 204: Configure Is-Is Frr To Automatically Calculate A Backup Next Hop

    Prerequisites • Configure network layer addresses for interfaces to make the neighboring nodes reachable at the network layer. • Enable IS-IS. Configure IS-IS FRR to automatically calculate a backup next hop To do… Use the command… Remarks Enter system view system-view —...

  • Page 205: Enabling The Logging Of Neighbor State Changes

    Enabling the logging of neighbor state changes To do… Use the command… Remarks Enter system view system-view –– Step 1 isis [ process-id ] [ vpn-instance vpn- Enter IS-IS view –– Step 2 instance-name ] Required Enable the logging of Step 3 log-peer-change neighbor state changes...

  • Page 206: Configuring Bfd For Is-Is

    Configuring BFD for IS-IS To do… Use the command… Remarks Enter system view system-view — Step 1 Enter interface view interface interface-type interface-number — Step 2 Required Enable IS-IS on the Step 3 isis enable [ process-id ] interface Disabled by default Required Enable BFD on the IS-IS Step 4...

  • Page 207: Is-Is Configuration Examples

    To do… Use the command… Remarks Display IS-IS SPF Step 10 display isis spf-log [ process-id | vpn- Available calculation log instance vpn-instance-name ] any view information display isis statistics [ level-1 | level-1-2 | Available Display IS-IS statistics level-2 ] [ process-id | vpn-instance vpn- Step 11 any view instance-name ]...
  • Page 208 Configuration procedure Configure IP addresses for interfaces (details not shown). Configure IS-IS. Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit Configure Switch B. <SwitchB>...
  • Page 209 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] network-entity 20.0000.0000.0004.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 100 [SwitchD-Vlan-interface100] isis enable 1 [SwitchD-Vlan-interface100] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit Verify the configuration. Display the IS-IS LSDB of each switch to check the LSP integrity. [SwitchA] display isis lsdb Database information for ISIS(1) --------------------------------...
  • Page 210 0000.0000.0001.00-00 0x00000006 0xdb60 0/0/0 0000.0000.0002.00-00* 0x00000008 0xe651 1189 0/0/0 0000.0000.0002.01-00* 0x00000005 0xd2b3 1188 0/0/0 0000.0000.0003.00-00 0x00000014 0x194a 1190 1/0/0 0000.0000.0003.01-00 0x00000002 0xabdb 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL- Overload [SwitchC] display isis lsdb Database information for ISIS(1) -------------------------------- Level-1 Link State Database LSPID Seq Num...
  • Page 211 [SwitchD] display isis lsdb Database information for ISIS(1) -------------------------------- Level-2 Link State Database LSPID Seq Num Checksum Holdtime Length ATT/P/OL ----------------------------------------------------------------------- -------- 0000.0000.0003.00-00 0x00000013 0xc73d 1003 0/0/0 0000.0000.0004.00-00* 0x0000003c 0xd647 1194 0/0/0 0000.0000.0004.01-00* 0x00000002 0xec96 1007 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL- Overload Display the IS-IS routing information of each switch.
  • Page 212 Flags: D-Direct, R-Added to RM, L-Advertised in LSPs, U-Up/Down Bit Set [SwitchC] display isis route Route information for ISIS(1) ----------------------------- ISIS(1) IPv4 Level-1 Forwarding Table ------------------------------------- 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...

  • Page 213: Dis Election Configuration

    [SwitchD] display isis route Route information for ISIS(1) ----------------------------- ISIS(1) IPv4 Level-2 Forwarding Table ------------------------------------- IPV4 Destination IntCost ExtCost ExitInterface NextHop Flags ----------------------------------------------------------------------- 192.168.0.0/24 NULL Vlan300 Direct D/L/- 10.1.1.0/24 NULL Vlan300 192.168.0.1 R/-/- 10.1.2.0/24 NULL Vlan300 192.168.0.1 R/-/- 172.16.0.0/16 NULL Vlan100 Direct D/L/-...
  • Page 214 Figure 67 Network diagram for DIS selection Configuration procedure Configure an IP address for each interface (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 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit Configure Switch B.
  • Page 215 [SwitchC-Vlan-interface100] isis enable 1 [SwitchC-Vlan-interface100] quit Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] network-entity 10.0000.0000.0004.00 [SwitchD-isis-1] is-level level-2 [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 of Switch A. [SwitchA] display isis peer Peer information for ISIS(1) ----------------------------...
  • Page 216 Display information about IS-IS interfaces of Switch C. [SwitchC] display isis interface Interface information for ISIS(1) --------------------------------- Interface: Vlan-interface100 IPV4.State IPV6.State Type Down 1497 L1/L2 Yes/No Display information about IS-IS interfaces of Switch D. [SwitchD] display isis interface Interface information for ISIS(1) --------------------------------- Interface: Vlan-interface100 IPV4.State...
  • Page 217 System Id: 0000.0000.0002 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 28s Type: L2(L1L2) PRI: 64 System Id: 0000.0000.0004 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 30s Type: L2 PRI: 64 Display information about IS-IS interfaces of Switch A. [SwitchA] display isis interface Interface information for ISIS(1) ---------------------------------...

  • Page 218: Configuring Is-Is Route Redistribution

    IPV4.State IPV6.State Type Down 1497 L1/L2 No/No Display information about IS-IS neighbors and interfaces of Switch D. [SwitchD] display isis peer Peer information for ISIS(1) ---------------------------- System Id: 0000.0000.0001 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 9s Type: L2 PRI: 100 System Id: 0000.0000.0002 Interface: Vlan-interface100...
  • Page 219 Figure 68 IS-IS route redistribution Configuration procedure Configure IP addresses for interfaces (details not shown). Configure IS-IS basic functions. Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis enable 1 [SwitchA-Vlan-interface100] quit Configure Switch B.
  • Page 220 [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis enable 1 [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis enable 1 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit 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...
  • Page 221 [SwitchC] display isis route Route information for ISIS(1) ----------------------------- ISIS(1) IPv4 Level-1 Forwarding Table ------------------------------------- IPV4 Destination IntCost ExtCost ExitInterface NextHop Flags ----------------------------------------------------------------------- 10.1.1.0/24 NULL VLAN100 Direct D/L/- 10.1.2.0/24 NULL VLAN200 Direct D/L/- 192.168.0.0/24 NULL VLAN300 Direct D/L/- Flags: D-Direct, R-Added to RM, L-Advertised in LSPs, U-Up/Down Bit Set ISIS(1) IPv4 Level-2 Forwarding Table -------------------------------------...
  • Page 222 ----------------------------- ISIS(1) IPv4 Level-2 Forwarding Table ------------------------------------- IPV4 Destination IntCost ExtCost ExitInterface NextHop Flags ----------------------------------------------------------------------- 192.168.0.0/24 NULL VLAN300 Direct D/L/- 10.1.1.0/24 NULL VLAN300 192.168.0.1 10.1.2.0/24 NULL VLAN300 192.168.0.1 Flags: D-Direct, R-Added to RM, L-Advertised in LSPs, U-Up/Down Bit Set Configure RIPv2 on Switch D and Switch E, and configure route redistribution from RIP to IS- IS on Switch D.

  • Page 223: Is-Is-Based Graceful Restart 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 RM, L-Advertised in LSPs, U-Up/Down Bit Set ISIS(1) IPv4 Level-2 Forwarding Table ------------------------------------- IPV4 Destination IntCost ExtCost ExitInterface...
  • Page 224 Figure 69 Network diagram for IS-IS-based GR configuration GR restarter Switch A Vlan-int100 10.0.0.1/24 Vlan-int100 Vlan-int100 10.0.0.2/24 10.0.0.3/24 Switch B Switch C GR helper GR helper Configuration procedure Configure IP addresses of the interfaces on each switch and configure IS-IS. Follow Figure 69 to configure the IP address and subnet mask of each interface.

  • Page 225: Is-Is Nsr Configuration Example

    Restart Interval: 150 SA Bit Supported Total Number of Interfaces = 1 Restart Status: RESTARTING Number of LSPs Awaited: 3 T3 Timer Status: Remaining Time: 140 T2 Timer Status: Remaining Time: 59 IS-IS(1) Level-2 Restart Status Restart Interval: 150 SA Bit Supported Total Number of Interfaces = 1 Restart Status: RESTARTING Number of LSPs Awaited: 3...
  • Page 226 Configure IS-IS on the switches, ensuring that Switch S, Switch A, and Switch B can communicate with each other at Layer 3, and dynamic route update can be implemented among them with IS-IS. The configuration procedure is omitted here. Configure IS-IS NSR. Enable IS-IS NSR on Switch S.
  • Page 227 ----------------------------------------------------------------------- 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 RM, L-Advertised in LSPs, U-Up/Down Bit Set ISIS(1) IPv4 Level-2 Forwarding Table ------------------------------------- IPV4 Destination IntCost ExtCost ExitInterface NextHop...

  • Page 228: Is-Is Frr 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 RM, L-Advertised in LSPs, U-Up/Down Bit Set ISIS(1) IPv4 Level-2 Forwarding Table ------------------------------------- IPV4 Destination IntCost ExtCost ExitInterface NextHop...
  • Page 229 Configuration procedure Configure IP addresses of the interfaces on each switch and configure IS-IS. Follow Figure 71 to configure the IP address and subnet mask of each interface on the switches. The configuration procedure is omitted. Configure IS-IS on the switches, ensuring that Switch A, Switch D, and Switch S can communicate with each other at Layer 3, and dynamic route update can be implemented among them with IS-IS.
  • Page 230 [SwitchD] bfd echo-source-ip 4.4.4.4 [SwitchD] ip ip-prefix abc index 10 permit 1.1.1.1 32 [SwitchD] route-policy frr permit node 10 [SwitchD-route-policy] if-match ip-prefix abc [SwitchD-route-policy] apply fast-reroute backup-interface vlan- interface 101 backup-nexthop 24.24.24.2 [SwitchD-route-policy] quit [SwitchD] isis 1 [SwitchD-isis-1] fast-reroute route-policy frr [SwitchD-isis-1] quit Verify the configuration.

  • Page 231: Is-Is Authentication Configuration Example

    Tag: 0 IS-IS authentication configuration example Network requirements As shown in Figure 72, Switch A, B, C, and D reside in the same IS-IS routing domain. Switch A, B, and C belong to Area 10, and Switch D belongs to Area 20. Configure neighbor relationship authentication between neighbors.
  • Page 232 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] isis enable 1 [RouterB--Vlan-interface200] quit Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis enable 1 [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis enable 1 [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis enable 1...

  • Page 233: Configuring Bfd For Is-Is

    [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis authentication-mode md5 t5Hr [SwitchC-Vlan-interface200] quit Specify the MD5 authentication mode and password hSec on VLAN-interface 300 of Switch D and on VLAN-interface 300 of Switch C. [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] isis authentication-mode md5 hSec [SwitchC-Vlan-interface300] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis authentication-mode md5 hSec...
  • Page 234 Figure 73 Network diagram for BFD configuration on an IS-IS link Configure IP addresses for interfaces (details not shown). Configure IS-IS basic functions. Configure Switch A. [SwitchA] isis [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] quit [SwitchA] interface vlan-interface 10 [SwitchA-Vlan-interface10] isis enable [SwitchA-Vlan-interface10] isis bfd enable [SwitchA-Vlan-interface10] quit Configure Switch B.
  • Page 235 [SwitchB] interface vlan-interface 10 [SwitchB-Vlan-interface10] bfd min-receive-interval 500 [SwitchB-Vlan-interface10] bfd min-transmit-interval 500 [SwitchB-Vlan-interface10] bfd detect-multiplier 8 Verify the configuration. Display the IS-IS neighbor information of Switch A. Switch A has removed its neighbor relationship with Switch B; therefore, no information is output. [SwitchA-Vlan-interface10] display isis peer verbose...

  • Page 236: Bgp Configuration

    BGP configuration The BGP is a dynamic inter-AS exterior gateway protocol. The term router refers to both routers and Layer 3 switches, and BGP refers to BGP-4 in this document. BGP overview There are three early BGP versions: BGP-1 (RFC 1105), BGP-2 (RFC 1163), and BGP-3 (RFC 1267).

  • Page 237: Formats Of Bgp Messages

    Formats of BGP messages Header BGP has the following type code messages: • Open • Update • Notification • Keepalive • Route-refresh They have the same header, as shown Figure 74: Figure 74 BGP message header Major fields of the BGP message header are as follows: •...
  • Page 238 Figure 75 BGP open message format Version My autonomous system Hold time BGP identifier Opt Parm Len Optional parameters Major fields of the BGP open message are as follows: • Version: This 1-byte unsigned integer indicates the protocol version number. The current BGP version is 4.
  • Page 239 • Unfeasible routes length: The total length of the withdrawn routes field in bytes. A value of 0 indicates no route is withdrawn from service, and the withdrawn routes field is not present in this Update message. • Withdrawn routes: This is a variable length field that contains a list of withdrawn IP prefixes. •...

  • Page 240: Bgp Path Attributes

    • SAFI: Subsequent address family identifier BGP path attributes Classification of path attributes • Well-known mandatory: Must be recognized by all BGP routers and must be included in every update message. Routing information errors occur without this attribute. • Well-known discretionary: Can be recognized by all BGP routers and optional to be included in every update message as needed.
  • Page 241 • Incomplete: Has the lowest priority. The source of routes with this attribute is unknown, which does not mean such routes are unreachable. The routes redistributed from other routing protocols have the incomplete attribute. AS_PATH AS_PATH is a well-known mandatory attribute. This attribute identifies the autonomous systems through which routing information carried in the Update message has passed.
  • Page 242 In some applications, you can apply a routing policy to control BGP route selection by modifying the AS_PATH length. By configuring an AS path filtering list, you can filter routes based on AS numbers contained in the AS_PATH attribute. NEXT_HOP Different from IGP, the NEXT_HOP attribute cannot be the IP address of a directly connected router.
  • Page 243 Figure 81 MED attribute MED = 0 Router B 2.1.1.1 D = 9.0.0.0 IBGP Next_hop = 2.1.1.1 9.0.0.0 MED = 0 EBGP Router D Router A IBGP EBGP D = 9.0.0.0 IBGP Next_hop = 3.1.1.1 MED = 100 3.1.1.1 AS 10 Router C AS 20 MED = 100...

  • Page 244: Bgp Route Selection

    Figure 82 LOCAL_PREF attribute Local_pref = 100 Router B EBGP IBGP 8.0.0.0 Next_hop = 2.1.1.1 Local_pref = 100 2.1.1.1 Router A Router D IBGP EBGP 3.1.1.1 D = 8.0.0.0 Next_hop = 3.1.1.1 IBGP Local_pref = 200 AS 10 AS 20 Router C Local_pref = 200 COMMUNITY...
  • Page 245 Select the route with the lowest MED value. Select routes learned from eBGP, confederation, iBGP in turn. Select the route with the smallest next hop cost. Select the route with the shortest CLUSTER_LIST. Select the route with the smallest ORIGINATOR_ID. Select the route advertised by the router with the smallest Router ID.

  • Page 246: Ibgp And Igp Synchronization

    Figure 83 Network diagram for BGP load balancing In Figure 83, Router D and Router E are iBGP peers of Router C. Router A and Router B both advertise a route destined for the same destination to Router C. If load balancing is configured, and the two routes have the same AS_PATH attribute, ORIGIN attribute, LOCAL_PREF, and MED, Router C installs both the two routes to its route table for load balancing.

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

    If a non-BGP router works in an AS, it can discard a packet because a destination is unreachable. As shown in Figure 84, Router E has learned a route of 8.0.0.0/8 from Router D via BGP. Router E then sends a packet to 8.0.0.0/8 through Router D, which finds from its routing table that Router B is the next hop (configured using the peer next-hop-local command).
  • Page 248 In most cases, BGP is used in complex networks, where route changes are very frequent. To solve the problem caused by route flaps, BGP route dampening is used to suppress unstable routes. BGP route dampening, as shown in Figure 85, uses a penalty value to judge the stability of a route.
  • Page 249 Community A peer group makes peers in it share the same policy, while a community makes a group of BGP routers in several ASs share the same policy. Community is a path attribute and advertised between BGP peers, without being limited by AS. A BGP router can modify the community attribute for a route before sending it to other peers.
  • Page 250 Figure 87 Network diagram for route reflectors When the BGP routers in an AS are fully meshed, route reflection is unnecessary because it consumes more bandwidth resources. You can use related commands to disable route reflection in this case. After route reflection is disabled between clients, routes can still be reflected between a client and a non- client.

  • Page 251: Bgp Gr

    Figure 88 Confederation network diagram From the perspective of a non-confederation BGP speaker, it needs not know sub-ASs in the confederation. The ID of the confederation is the number of the AS. In Figure 88, AS 200 is the confederation ID. The deficiency of confederation is as follows: •...

  • Page 252: Mp-Bgp

    stale. However, during the configured GR Time, it still uses these routes for packet forwarding. After the restart, the GR Restarter will reestablish a GR session with its peer and send a new GR message notifying the completion of restart. Routing information is exchanged between them for the GR Restarter to create a new routing table and forwarding table with stale routing information removed.

  • Page 253: Protocols And Standards

    Protocols and standards • RFC 1771: A Border Gateway Protocol 4 (BGP-4) • RFC 2858: Multiprotocol Extensions for BGP-4 • RFC 3392: Capabilities Advertisement with BGP-4 • RFC 2918: Route Refresh Capability for BGP-4 • RFC 2439: BGP Route Flap Damping •...

  • Page 254: Specifying The Source Interface For Tcp Connections

    • If no router ID is specified in BGP view, the global router ID is used. For information about global router ID, see IP Routing Basics in the Layer 3 – IP Routing Configuration Guide. • If the global router ID is used and then it is removed, the system will select a new router ID. If the router ID is specified in BGP view, using the undo router-id command can make the system select a new router ID.

  • Page 255: Allowing Establishment Of Ebgp Connection To A Non-Directly Connected Peer Or Peer Group

    To do… Use the command… Remarks Enter system view system-view — Step 1 Enter BGP view bgp as-number — Step 2 Required Specify the source By default, BGP uses the outbound Step 3 peer { group-name | ip-address interface for interface of the best route to the establishing TCP } connect-interface interface-...

  • Page 256: Controlling Route Distribution And Reception

    Controlling route distribution and reception Prerequisites Complete the BGP basic configuration. Configuring BGP route redistribution BGP can advertise the routing information of the local AS to peering ASs, but it redistributes routing information from IGP into BGP rather than self finding. During route redistribution, BGP can filter routing information from specific routing protocols.

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

    To do… Use the command… Remarks Enter system view system-view — Step 1 Enter BGP view bgp as-number — Step 2 Configure Required automatic route summary automatic route summarization summarization Configure configured by default. Step 3 aggregate ip-address { mask | mask- BGP route Choose either...

  • Page 258: Configuring Bgp Route Reception Filtering Policies

    To do… Use the command… Remarks filter-policy { acl-number | ip- Required prefix ip-prefix-name } export [ Use one of the commands. Configure the filtering Step 3 direct | isis process-id | ospf of redistributed routes process-id | rip process-id Not configured by default.

  • Page 259: Enabling Bgp And Igp Route Synchronization

    To do… Use the command… Remarks Filter incoming routes Required Step 3 filter-policy { acl-number | ip- with an ACL or IP prefix Use one of the commands. prefix ip-prefix-name } import list No route reception filtering is Reference a routing configured by default.

  • Page 260: Configuring Bgp Route Dampening

    To do… Use the command… Remarks Required Enable synchronization Step 3 synchronization between BGP and IGP Not enabled by default Configuring BGP route dampening By configuring BGP route dampening, you can suppress unstable routes from being added to the local routing table or from being advertised to BGP peers. To do…...
  • Page 261 To do… Use the command… Remarks Optional Configure default med med-value default MED value 0 by default Enable Optional comparison compare-different-as-med enabled routes default from different ASs Enable Configure the Step 5 Optional comparison MED attribute bestroute compare-med enabled routes default from each AS Enable...

  • Page 262: Tuning And Optimizing Bgp Networks

    To do… Use the command… Remarks Substitute local Optional number peer { group-name | ip-address substitution number of a peer or } substitute-as not configured by peer group default. AS_PATH attribute Configure BGP to not Optional keep private AS numbers peer { group-name | ip-address default, in the AS_PATH attribute...

  • Page 263: Configuring The Interval For Sending The Same Update

    If two parties have the same timer assigned with different values, the smaller one is used by the two parties. To do… Use the command… Remarks Enter system view system-view — Step 1 Enter BGP view bgp as-number — Step 2 Configure the global Step 3 timer keepalive keepalive hold...
  • Page 264 The current BGP implementation supports the route-refresh feature that enables dynamic route refresh without tearing down BGP connections. However, if a BGP peer not supporting route-refresh exists in the network, you must save updates from the peer on the local router. Afterwards, when a route selection policy is modified, the router can refresh its BGP routing table by using such updates without tearing down BGP connections.

  • Page 265: Enabling The Bgp Orf Capability

    Enabling the BGP ORF capability The BGP ORF feature allows a BGP speaker to send to its BGP peer a set of ORFs through route- refresh messages. The peer then applies the ORFs, in addition to its local routing policies (if any), to filter updates to the BGP speaker.

  • Page 266: Enabling Quick Ebgp Session Reestablishment

    Local parameter Peer parameter Negotiation result Both the ORF sending and receiving capabilities are both both enabled locally and on the peer, respectively. Enabling quick eBGP session reestablishment If the router receives no keepalive messages from a BGP peer within the holdtime, it disconnects from the peer.

  • Page 267: Forbiding Session Establishment With A Peer Or Peer Group

    To do… Use the command… Remarks Enter system view system-view — Step 1 Enter BGP view bgp as-number — Step 2 Optional Configure the maximum number Step 3 balance number Load balancing of BGP routes for load balancing enabled by default. Forbiding session establishment with a peer or peer group To do…...
  • Page 268 Configure an iBGP peer group After you create an iBGP peer group and then add a peer into it, the system creates the peer in BGP view and specifies the local AS number for the peer. To do… Use the command… Remarks Enter system view system-view...
  • Page 269 Follow these steps to configure an eBGP peer group using the second approach: To do… Use the command… Remarks Enter system view system-view — Step 1 Enter BGP view bgp as-number — Step 2 Create an eBGP peer Step 3 group group-name external Required group...

  • Page 270: Configuring Bgp Community

    To guarantee the connectivity between iBGP peers, you must make them fully meshed. It becomes impractical when there are large numbers of iBGP peers. Configuring route reflectors or confederation can solve it. In a large-scale AS, both of them can be used. Configuring BGP community To do…...

  • Page 271: Configuring A Bgp Confederation

    To do… Use the command… Remarks Optional Configure the cluster ID reflector cluster-id { cluster-id | Step 5 By default, a route reflector uses of the route reflector ip-address } its router ID as the cluster ID. Generally, it is not required to make clients of a route reflector fully meshed. The route reflector forwards •...

  • Page 272: Enabling Trap

    A switch can act as both the GR Restarter and GR Helper at the same time. To do… Use the command… Remarks Enter system view system-view — Step 1 Enable BGP and enter its Step 2 bgp as-number — view Required Enable GR Capability for Step 3...

  • Page 273: Configuring Bfd For Bgp

    Configuring BFD for BGP By default, the BGP keepalive interval is 60 seconds and the holdtime interval is 180 seconds. If neither the holdtime interval nor the keepalive interval is configured as 0, the holdtime interval must be at least three times the keepalive interval. This setting makes the detection of neighbors rather slow, and a large quantity of packets will be dropped when being transmitted or received through a high-speed interface.
  • Page 274 To do… Use the command… Remarks Display peer group Step 1 display bgp group [ group-name ] information Display advertised BGP Step 2 display bgp network routing information Display AS path Step 3 display bgp paths [ as-regular-expression ] information Display BGP peer or display bgp peer [ ip-address { log-info | verbose Step 4...

  • Page 275: Resetting Bgp Connections

    To do… Use the command… Remarks Display routing Step 17 display bgp routing-table regular-expression as- information matching a regular-expression regular expression Display BGP routing Step 18 display bgp routing-table statistic statistics Resetting BGP connections To do… Use the command… Remarks Reset all BGP connections reset bgp all Step 1...

  • Page 276: Bgp Basic Configuration

    By default, Ethernet, VLAN, and aggregate interfaces are down. Before configuring these interfaces, bring them up using the undo shutdown command. BGP basic configuration Network requirements In Figure 89, run eBGP between Switch A and Switch B, and run iBGP between Switch B and Switch C, so Switch C can access the network 8.1.1.0/24 connected to Router A.
  • Page 277 [SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.1 24 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit Configure Switch C. <SwitchC> system-view [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 2.2.2.2 as-number 65009 [SwitchC-bgp] peer 2.2.2.2 connect-interface loopback 0 [SwitchC-bgp] quit [SwitchC] ospf 1 [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 3.3.3.3 32 [SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 24 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit...
  • Page 278 [SwitchA-bgp] network 8.1.1.1 24 [SwitchA-bgp] quit Configure Switch B. [SwitchB] bgp 65009 [SwitchB-bgp] peer 3.1.1.2 as-number 65008 [SwitchB-bgp] quit Display BGP peer information on Switch B. [SwitchB] display bgp peer BGP local router ID : 2.2.2.2 Local AS number : 65009 Total number of peers : 2 Peers in established state : Peer...
  • Page 279 BGP Local router ID is 2.2.2.2 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf...
  • Page 280 BGP Local router ID is 1.1.1.1 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? – incomplete Network NextHop LocPrf...

  • Page 281: Bgp And Igp Synchronization Configuration

    Reply from 8.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms Reply from 8.1.1.1: bytes=56 Sequence=5 ttl=254 time=2 ms --- 8.1.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 2/2/2 ms BGP and IGP synchronization configuration Network requirements As shown in Figure 90, all switches of company A belong to AS 65008, while all switches of company B belong to AS 65009.
  • Page 282 [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit Configure the eBGP connection. Configure the eBGP connection and inject network 8.1.1.0/24 to the BGP routing table of Switch A, so that Switch B can obtain the route to 8.1.1.0/24. Configure Switch A.
  • Page 283 *> 9.1.2.0/24 3.1.1.1 65009? Display the routing table on Switch C. [SwitchC] display ip routing-table Routing Tables: Public Destinations : 9 Routes : 9 Destination/Mask Proto Cost NextHop Interface 2.2.2.2/32 OSPF 9.1.1.1 Vlan300 3.3.3.3/32 Direct 0 127.0.0.1 InLoop0 8.1.1.0/24 O_ASE 9.1.1.1 Vlan300 9.1.1.0/24...

  • Page 284: Bgp Load Balancing Configuration

    0.00% packet loss round-trip min/avg/max = 2/2/2 ms BGP load balancing configuration Network requirements As shown in Figure 91, all the switches run BGP. Switch A resides in AS 65008, Switch B and Switch C in AS 65009. Between Switch A and Switch B, Switch A and Switch C are eBGP connections, and between Switch B and Switch C is an iBGP connection.
  • Page 285 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 3.1.1.1 as-number 65009 [SwitchA-bgp] peer 3.1.2.1 as-number 65009 [SwitchA-bgp] network 8.1.1.1 24 [SwitchA-bgp] quit Configure Switch B. <SwitchB> system-view [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 3.1.1.2 as-number 65008 [SwitchB-bgp] peer 3.3.3.3 as-number 65009 [SwitchB-bgp] peer 3.3.3.3 connect-interface loopback 0 [SwitchB-bgp] network 9.1.1.0 255.255.255.0 [SwitchB-bgp] quit...

  • Page 286: Bgp Community Configuration

    indicating it is the best route (because the ID of Switch B is smaller); the route with next hop 3.1.2.1 is marked with an asterisk (*), indicating it is a valid route, but not the best. Using the display ip routing-table command, you can find only one route to 9.1.1.0/24 with next hop 3.1.1.1 and outbound interface VLAN-interface 200.
  • Page 287 Figure 92 Network diagram for BGP community configuration Configuration procedure Configure IP addresses for interfaces (details not shown). Configure eBGP. Configure Switch A. <SwitchA> system-view [SwitchA] bgp 10 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 200.1.2.2 as-number 20 [SwitchA-bgp] network 9.1.1.0 255.255.255.0 [SwitchA-bgp] quit Configure Switch B.
  • Page 288 Local AS number : 20 Paths: 1 available, 1 best BGP routing table entry information of 9.1.1.0/24: From : 200.1.2.1 (1.1.1.1) Original nexthop: 200.1.2.1 AS-path : 10 Origin : igp Attribute value : MED 0, pref-val 0, pre 255 State : valid, external, best, Advertised to such 1 peers: 200.1.3.2...

  • Page 289: Bgp Route Reflector Configuration

    Local AS number : 20 Paths: 1 available, 1 best BGP routing table entry information of 9.1.1.0/24: From : 200.1.2.1 (1.1.1.1) Original nexthop: 200.1.2.1 Community : No-Export AS-path : 10 Origin : igp Attribute value : MED 0, pref-val 0, pre 255 State : valid, external, best, Not advertised to any peers yet...
  • Page 290 <SwitchA> system-view [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 192.1.1.2 as-number 200 Inject network 1.0.0.0/8 to the BGP routing table. [SwitchA-bgp] network 1.0.0.0 [SwitchA-bgp] quit Configure Switch B. <SwitchB> system-view [SwitchB] bgp 200 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 192.1.1.1 as-number 100 [SwitchB-bgp] peer 193.1.1.1 as-number 200 [SwitchB-bgp] peer 193.1.1.1 next-hop-local [SwitchB-bgp] quit...

  • Page 291: Bgp Confederation Configuration

    BGP Local router ID is 200.1.2.2 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf...
  • Page 292 Figure 94 Network diagram for BGP confederation configuration Switch C Switch B Switch F Vlan-int600 Vlan-int300 Vlan-int200 AS 65002 AS 65003 Vlan-int100 Switch D AS 100 Vlan-int100 Vlan-int400 Vlan-int400 Switch A Vlan-int200 Vlan-int500 AS 65001 Vlan-int200 Vlan-int500 Switch E AS 200 Device Interface IP address...
  • Page 293 [SwitchB-bgp] confederation id 200 [SwitchB-bgp] confederation peer-as 65001 65003 [SwitchB-bgp] peer 10.1.1.1 as-number 65001 [SwitchB-bgp] quit Configure Switch C. <SwitchC> system-view [SwitchC] bgp 65003 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] confederation id 200 [SwitchC-bgp] confederation peer-as 65001 65002 [SwitchC-bgp] peer 10.1.2.1 as-number 65001 [SwitchC-bgp] quit Configure iBGP connections in AS65001.
  • Page 294 [SwitchA-bgp] peer 200.1.1.2 as-number 100 [SwitchA-bgp] quit Configure Switch F. <SwitchF> system-view [SwitchF] bgp 100 [SwitchF-bgp] router-id 6.6.6.6 [SwitchF-bgp] peer 200.1.1.1 as-number 200 [SwitchF-bgp] network 9.1.1.0 255.255.255.0 [SwitchF-bgp] quit Verify the configuration. Display the routing table on Switch B. [SwitchB] display bgp routing-table Total Number of Routes: 1 BGP Local router ID is 2.2.2.2 Status codes: * - valid, >...

  • Page 295: Bgp Path Selection Configuration

    Total Number of Routes: 1 BGP Local router ID is 4.4.4.4 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf...
  • Page 296 • OSPF is the IGP protocol in AS 200. • Configure routing policies, making Switch D use the route 1.0.0.0/8 from Switch C as the optimal. Figure 95 Network diagram for BGP path selection configuration Device Interface IP address Device Interface IP address Switch A...
  • Page 297 [SwitchC-ospf-1] quit Configure Switch D. <SwitchD> system-view [SwitchD] ospf [SwitchD-ospf] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 [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] peer 192.1.1.2 as-number 200 [SwitchA-bgp] peer 193.1.1.2 as-number 200 Inject network 1.0.0.0/8 to the BGP routing table on Switch A.
  • Page 298 [SwitchA-acl-basic-2000] quit Define two routing policies, apply_med_50, which sets the MED for route 1.0.0.0/8 to 50, and apply_med_100, which sets the MED for route 1.0.0.0/8 to 100. [SwitchA] route-policy apply_med_50 permit node 10 [SwitchA-route-policy] if-match acl 2000 [SwitchA-route-policy] apply cost 50 [SwitchA-route-policy] quit [SwitchA] route-policy apply_med_100 permit node 10 [SwitchA-route-policy] if-match acl 2000...

  • Page 299: Configuring Bfd For Bgp

    [SwitchC-route-policy] if-match acl 2000 [SwitchC-route-policy] apply local-preference 200 [SwitchC-route-policy] quit Apply routing policy localpref to routes from peer 193.1.1.1. [SwitchC] bgp 200 [SwitchC-bgp] peer 193.1.1.1 route-policy localpref import [SwitchC-bgp] quit Display the routing table on Switch D. [SwitchD] display bgp routing-table Total Number of Routes: 2 BGP Local router ID is 194.1.1.1 Status codes: * - valid, >...
  • Page 300 Figure 96 Network diagram for BFD configuration on a BGP link AS 100 Switch A Switch B Vlan-int10 Vlan-int10 10.1.0.102/24 10.1.0.100/24 L2 switch Configuration procedure Configure VLAN interfaces. Configure Switch A. <SwitchA> system-view [SwitchA] vlan 10 [SwitchA-vlan10] port GigabitEthernet 3/0/1 [SwitchA-vlan10] interface vlan 10 [SwitchA-Vlan-interface10]ip address 10.1.0.102 24 Configure Switch B.
  • Page 301 <SwitchA> system-view [SwitchA] bfd session init-mode active [SwitchA-vlan10] interface vlan 10 [SwitchA-Vlan-interface10] bfd min-transmit-interval 300 [SwitchA-Vlan-interface10] bfd min-receive-interval 300 [SwitchA-Vlan-interface10] bfd detect-multiplier 7 [SwitchA-Vlan-interface10] quit [SwitchA] quit Configure Switch B. <SwitchB> system-view [SwitchB] bfd session init-mode active [SwitchB-vlan10] interface vlan 10 [SwitchB-Vlan-interface10] bfd min-transmit-interval 300 [SwitchB-Vlan-interface10] bfd min-receive-interval 300 [SwitchB-Vlan-interface10] bfd detect-multiplier 6...

  • Page 302: Bgp Gr Configuration

    Sent: Total 0 messages, Update messages 0 Maximum allowed prefix number: 4294967295 Threshold: 75% Minimum time between advertisement runs is 15 seconds Optional capabilities: Route refresh capability has been enabled Peer Preferred Value: 0 BFD: Enabled Routing policy configured: No routing policy is configured BGP GR configuration Network requirements In Figure 97 are all BGP switches.

  • Page 303: Troubleshooting Bgp

    Configure IP addresses for interfaces (details not shown). Configure the eBGP connection. <SwitchB> system-view [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 200.1.1.2 as-number 65008 Configure the iBGP connection. [SwitchB-bgp] peer 9.1.1.2 as-number 65009 Configure BGP to redistribute direct routes. [SwitchB-bgp] import-route direct Enable GR capability for BGP.
  • Page 304 Solution Use the display current-configuration command to verify the peer’s AS number. Use the display bgp peer command to verify the peer’s IP address. If the loopback interface is used, check whether the peer connect-interface command is configured. If the peer is a non-direct eBGP peer, check whether the peer ebgp-max-hop command is configured.

  • Page 305: Ip Unicast Policy Routing Configuration

    IP unicast policy routing configuration Introduction to IP unicast policy routing Policy routing IP unicast policy routing is used to route IP unicasts based on a policy. Policy routing, also known as PBR, is a routing mechanism based on user-defined policies. Different from the traditional destination-based routing mechanism, policy routing enables you to use a policy based on the source address, and other criteria, to route packets.

  • Page 306: Configuring Ip Unicast Policy Routing

    For more information about track, see Track in the High Availability Configuration Guide. Configuring IP unicast policy routing Defining a policy A policy consists of one node or multiple nodes. A node is identified by a node number. The smaller the node number, the higher the priority of the node. The node with a higher priority is executed first.

  • Page 307: Configuring Local Policy Routing

    To do… Use the command… Remarks system-view Enter system view –– Step 1 policy-based-route Create a policy or policy policy- Step 2 node and enter PBR name [ deny | permit ] Required policy node view node node-number Define an ACL match Step 3 if-match acl acl-number Optional...

  • Page 308: Displaying And Maintaining Ip Unicast Policy Routing Configuration

    To do… Use the command… Remarks system-view Enter system view — Step 1 interface interface-type interface- Enter interface view — Step 2 number Required Configure interface policy ip policy-based-route policy- Step 3 routing based on a policy name Not configured by default Displaying and maintaining IP unicast policy routing configuration To do…...
  • Page 309 Figure 98 Network diagram for local policy routing based on packet type Configuration procedure Configure Switch A. Define ACL 3101 to match TCP packets. <SwitchA> system-view [SwitchA] acl number 3101 [SwitchA-acl-adv-3101] rule permit tcp [SwitchA-acl-adv-3101] quit Define Node 5 of policy aaa so TCP packets are forwarded to next hop 1.1.2.2. [SwitchA] policy-based-route aaa permit node 5 [SwitchA-pbr-aaa-5] if-match acl 3101 [SwitchA-pbr-aaa-5] apply ip-address next-hop 1.1.2.2...
  • Page 310 Trying 1.1.2.2 ... Press CTRL+K to abort Connected to 1.1.2.2 ... *********************************************************************** ******* * Copyright (c) 2004-2009 Hangzhou H3C Tech. Co., Ltd. All rights reserved. * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ******************************************************************** ***************************** Telnet to Switch C (1.1.3.2/24) from Switch A.

  • Page 311: Configuring Interface Policy Routing Based On Packet Type

    Configuring interface policy routing based on packet type Network requirements As shown in Figure 99, configure policy routing on Switch A so all TCP packets arriving on VLAN-interface 10 are forwarded by next hop 1.1.2.2, and other packets are forwarded according to the routing table.
  • Page 312 [Switch-pbr-aaa-5] apply ip-address next-hop 1.1.2.2 [Switch-pbr-aaa-5] quit Apply the policy aaa to VLAN-interface 10 to process the arriving packets. [Switch] interface Vlan-interface 10 [Switch-Vlan-interface10] ip policy-based-route aaa Configure the IP addresses for the VLAN interfaces. [SwitchA] interface Vlan-interface 20 [SwitchA-Vlan-interface20] ip address 1.1.2.1 255.255.255.0 [SwitchA-Vlan-interface20] quit [SwitchA] interface Vlan-interface 30 [SwitchA-Vlan-interface30] ip address 1.1.3.1 255.255.255.0...

  • Page 313: Ipv6 Static Routing Configuration

    IPv6 static routing configuration Introduction to IPv6 static routing Static routes are special routes that are manually configured by network administrators. They work well in simple networks. Configuring and using them properly can improve the performance of networks, and guarantee enough bandwidth for important applications. However, static routes also have shortcomings;...

  • Page 314: Displaying And Maintaining Ipv6 Static Routes

    To do… Use the commands… Remarks system-view — Enter system view Step 1 Configure an IPv6 static Step 2 Required ipv6 route-static ipv6-address prefix-length [ route with the output By default, no interface being a interface-type interface-number ] nexthop-address IPv6 static route broadcast or NBMA [ preference preference-value ] configured;...
  • Page 315 By default, Ethernet, VLAN, and aggregate interfaces are down. Before configuring these interfaces, bring them up using the undo shutdown command. Network requirements In Figure 100, with IPv6 static routes configured, all hosts and switches can interact with each other. Figure 100 Network diagram for static routes Configuration procedure...
  • Page 316 Routing Table : Destinations : 5 Routes : 5 Destination : ::/128 Protocol Static NextHop : FE80::510A:0:8D7:1 Preference : 60 Interface : Vlan-interface200 Cost Destination : ::1/128 Protocol Direct NextHop : ::1 Preference Interface : InLoop0 Cost Destination : 1::/64 Protocol Direct NextHop...
  • Page 317 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 62/62/63 ms advertising a host route, 1 17 resetting connections, 275 BFD for BGP, 273 route attributes, 260 configuration example, 299 route reflector configuration example, 289 BFD for IS-IS, 206, 233 route selection, 244 BFD for RIP, 59 specifying...
  • Page 318 load balancing, 266 displaying and maintaining, 308 peer group, 248 interface policy routing, 307 quick eBGP session reestablishment, 266 interface policy routing based on packet type, 31 1 route dampening, 247 local policy routing based on packet type, 308 route reflector, 249 policy routing, 305 route summarization, 247 track-policy routing collaboration, 305...
  • Page 319 route attributes, 385 address format, 168 route dampening, 385 area, 169 route redistribution, 382 basic concepts, 167 route reflector, 394 basic functions, 182 configuration examples, 207 route reflector configuration example, 403 troubleshooting, 405 configuration tasks, 182 IPv6 BGP networks, 388 displaying and maintaining, 206 large-scale, 392 enabling, 183...
  • Page 320 calculating a backup next hop automatically, IS-IS routing information control, 184 default route, 188 configuration example, 228 equal-cost routes, 187 designating a backup next hop with a routing link cost, 184 policy, 204 priority, 186 introduction, 203 route filtering, 189 IS-IS GR, 201 route leaking, 190 IS-IS network types, 171...
  • Page 321 configuration examples, 134 calculating a backup next hop automatically, configuration tasks, 101 designating a backup next hop using a routing configuring BFD, 131, 163 policy, 128 cost for an interface, 1 13 introduction, 127 displaying and maintaining, 132 OSPF graceful restart, 129 DR election, 149 configuration example, 156 enabling, 102...
  • Page 322 LSR, 92 OSPFv3 network types, 346 LSU, 92 NBMA or P2MP neighbor, 346 packet header, 89 network type for an interface, 346 OSPF packets, 121 OSPFv3 networks, 351 disabling interfaces, 353 disabling interfaces from receiving or sending, DR priority for an interface, 352 OSPF route control, 1 10 logging neighbor state changes, 353 configuring stub routers, 121...
  • Page 323 routing table, 42 RIPng, 324 timers, 42, 53 configuring basic functions example, 334 troubleshooting, 79 displaying and maintaining, 333 versions, 43 equal cost routes for load balancing, 333 introduction, 324 RIP basic functions, 46 configuring an additional metric for a RIP packet processing procedure, 327 interface, 65 protocols and standards, 327...

  • Page 324: Ripng Configuration

    applying a routing policy to IPv4 route dynamic routing, 22 redistribution example, 425 dynamic routing protocols classification, 22 applying a routing policy to IPv6 route load balancing, 24 redistribution example, 429 route backup, 24 AS-PATH list, 418 route information sharing, 24 community list, 418 route recursion, 24 configuring a routing policy, 419...

  • Page 325: Ripng Working Mechanism

    • UDP port number: RIPng uses UDP port 521 for sending and receiving routing information. • Multicast address: RIPng uses FF02:9 as the link-local-router multicast address. • Destination Prefix: 128-bit destination address prefix. • Next hop: 128-bit IPv6 address. • Source address: RIPng uses FE80::/10 as the link-local source address RIPng working mechanism RIPng is a routing protocol based on the D-V algorithm.
  • Page 326 Figure 101 RIPng basic packet format • Command: Type of message. 0x01 indicates Request, 0x02 indicates Response. • Version: Version of RIPng. It can only be 0x01. • RTE: Route table entry; it’s 20 bytes for each entry. RTE format The types of RTEs in RIPng are as follows: •...

  • Page 327: Ripng Packet Processing Procedure

    RIPng packet processing procedure Request packet When a RIPng router first starts or must update some entries in its routing table, generally a multicast request packet is sent to ask for needed routes from neighbors. The receiving RIPng router processes RTEs in the request. If there is only one RTE with the IPv6 prefix, with the prefix length both being 0 and with a metric value of 16, then the RIPng router will respond with the entire routing table information in response messages.

  • Page 328: Configuring Ripng Route Control

    To do… Use the command… Remarks quit Return to system view — Step 3 interface interface-type interface- Enter interface view –– Step 4 number Required Enable RIPng on the Step 5 ripng process-id enable interface Disabled by default If RIPng is not enabled on an interface, then the interface will not send or receive any RIPng routes. Configuring RIPng route control Before the configuration, accomplish the following tasks: •...

  • Page 329: Configuring Ripng Route Summarization

    To do… Use the command… Remarks Specify an outbound Step 4 Optional routing additional ripng metricout value 1 by default metric Configuring RIPng route summarization Remark To do… Use the command… Enter system view system-view –– Step 1 Enter interface view interface interface-type interface-number ––...

  • Page 330: Configuring A Priority For Ripng

    To do… Use the command… Remarks system-view Enter system view –– Step 1 Enter RIPng view ripng [ process-id ] –– Step 2 Required filter-policy acl6-number Configure a filter policy By default, RIPng does Step 3 ipv6-prefix ipv6-prefix-name } to filter incoming routes filter incoming import...

  • Page 331: Tuning And Optimizing The Ripng Network

    Tuning and optimizing the RIPng network This section describes how to tune and optimize the performance of the RIPng network, as well as applications under special network environments. Before tuning and optimizing the RIPng network, complete the following tasks: • Configure a network layer address for each interface •...

  • Page 332: Configuring Zero Field Check On Ripng Packets

    Enable the split horizon Step 3 ripng split-horizon function Enabled by default Generally, H3C recommends enabling split horizon to prevent routing loops. • In NBMA networks, split horizon may need to be disabled to ensure route advertisement. • Configuring the poison reverse function The poison reverse function enables a route learned from an interface to be advertised through the interface.

  • Page 333: Configuring The Maximum Number Of Equal Cost Routes For Load Balancing

    To do… Use the command… Remarks Optional Enable the zero field Step 3 checkzero check Enabled by default Configuring the maximum number of equal cost routes for load balancing To do… Use the command… Remarks Enter system view system-view –– Step 1 Enter RIPng view ripng [ process-id ]...

  • Page 334: Ripng Configuration Examples

    RIPng configuration examples By default, Ethernet, VLAN, and aggregate interfaces are down. Before configuring these interfaces, bring them up using the undo shutdown command. Configure RIPng basic functions Network requirements As shown in Figure 104, all switches run RIPng. Configure Switch B to filter the route (3::/64) learned from Switch C, which means the route will not be added to the routing table of Switch B, and Switch B will not forward it to Switch A.
  • Page 335 [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ripng 1 enable [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ripng 1 enable [SwitchB-Vlan-interface100] quit Configure Switch C. <SwitchC> system-view [SwitchC] ripng 1 [SwitchC-ripng-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface101] ripng 1 enable [SwitchC-Vlan-interface101] quit [SwitchC] interface vlan-interface 500 [SwitchC-Vlan-interface300] ripng 1 enable [SwitchC-Vlan-interface300] quit...
  • Page 336 ---------------------------------------------------------------- Peer FE80::200:2FF:FE64:8904 on Vlan-interface100 Dest 1::/64, via FE80::200:2FF:FE64:8904, cost 1, tag 0, A, 31 Sec Dest 4::/64, via FE80::200:2FF:FE64:8904, cost 2, tag 0, A, 31 Sec Dest 5::/64, via FE80::200:2FF:FE64:8904, cost 2, tag 0, A, 31 Sec Dest 3::/64, via FE80::200:2FF:FE64:8904, cost 1, tag 0, A, 31 Sec Configure Switch B to filter incoming and outgoing routes.

  • Page 337: Configuring Ripng Route Redistribution

    Dest 1::/64, via FE80::20F:E2FF:FE00:1235, cost 1, tag 0, A, 2 Sec Dest 4::/64, via FE80::20F:E2FF:FE00:1235, cost 2, tag 0, A, 2 Sec Dest 5::/64, via FE80::20F:E2FF:FE00:1235, cost 2, tag 0, A, 2 Sec Configuring RIPng route redistribution Network requirements • Two RIPng processes are running on Switch B.
  • Page 338 [SwitchB-Vlan-interface100] ripng 100 enable [SwitchB-Vlan-interface100] quit [SwitchB] ripng 200 [SwitchB-ripng-200] quit [SwitchB] interface vlan-interface 300 [SwitchB-Vlan-interface300] ripng 200 enable [SwitchB-Vlan-interface300] quit Enable RIPng 200 on Switch C. <SwitchC> system-view [SwitchC] ripng 200 [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...
  • Page 339 Destination: 2::1/128 Protocol Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: FE80::/10 Protocol Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Configure RIPng route redistribution. Configure route redistribution between the two RIPng processes on Switch B. [SwitchB] ripng 100 [SwitchB-ripng-100] default cost 3 [SwitchB-ripng-100] import-route ripng 200...
  • Page 340 Destination: 2::1/128 Protocol Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 4::/64 Protocol RIPng NextHop : FE80::200:BFF:FE01:1C02 Preference: Interface : Vlan100 Cost Destination: FE80::/10 Protocol Direct NextHop : :: Preference: 0 Interface : NULL0 Cost : 0d...

  • Page 341: Ospfv3 Configuration

    OSPFv3 configuration Introduction to OSPFv3 OSPFv3 overview OSPFv3 supports IPv6 and complies with RFC2740 (OSPF for IPv6). OSPFv3 and OSPFv2 are the same in the following ways: • A 32-bit router ID and area ID • Packets: Hello, DD, LSR, LSU, and LSAck •...

  • Page 342: Ospfv3 Lsa Types

    • Instance ID: Instance ID for a link. • 0: Reserved. It must be 0. OSPFv3 LSA types OSPFv3 sends routing information in LSAs, which, as defined in RFC2740, have the following types: • Router-LSA: Originated by all routers. This LSA describes the collected states of the router's interfaces to an area.

  • Page 343: Ospfv3 Features Supported

    neighboring interfaces. The smaller the hello interval, the faster the network convergence speed and the bigger the network load. If a router receives no hello packet from a neighbor within a period, which this period is called the dead interval, then it will declare the peer is down. After sending an LSA to its adjacency, a router waits for an acknowledgment from the adjacency.

  • Page 344: Enabling An Ospfv3 Process

    • Enable IPv6 packet forwarding. Enabling an OSPFv3 process To enable an OSPFv3 process on a router, you must enable the OSPFv3 process globally, assign the OSPFv3 process a router ID, and enable the OSPFv3 process on related interfaces. A router ID uniquely identifies a router within an AS; therefore, specify a unique router ID for each OSPFv3 router within the AS to ensure normal operation.

  • Page 345: Configuring An Ospfv3 Virtual Link

    To do… Use the command… Remarks system-view Enter system view — Step 1 Enter OSPFv3 view ospfv3 [ process-id ] — Step 2 Enter OSPFv3 area Step 3 area area-id — view Required Configure the area as a Step 4 stub [ no-summary ] stub area Not configured by default...

  • Page 346: Configuring Ospfv3 Network Types

    Configuring OSPFv3 network types OSPFv3 classifies networks into four types upon the link layer protocol. By default, the following default OSPFv3 interface network types vary with the link layer protocols of the interfaces: • When the link layer protocol is PPP, OSPFv3 considers the network type as P2P by default. •...

  • Page 347: Configuring Ospfv3 Routing Information Control

    To do… Use the command… Remarks system-view Enter system view — Step 1 interface interface-type interface- Enter interface view — Step 2 number Specify an NBMA or Step 3 ospfv3 peer ipv6-address [ dr- P2MP (unicast) priority dr-priority ] [ instance Required neighbor and its DR instance-id ]...

  • Page 348: Configuring Ospfv3 Inbound Route Filtering

    Configuring OSPFv3 inbound route filtering According to some rules, you can configure OSPFv3 to filter routes that are computed from received LSAs. To do… Use the command… Remarks Enter system Step 1 system-view — view Enter OSPFv3 Step 2 ospfv3 [ process-id ] —...

  • Page 349: Configuring The Maximum Number Of Ospfv3 Load-Balanced Routes

    Follow these steps to configure a bandwidth reference value: To do… Use the command… Remarks Enter system view system-view — Step 1 Enter OSPFv3 view ospfv3 [ process-id ] — Step 2 Configure a Step 3 Optional bandwidth reference bandwidth-reference value 100 Mbps by default value Configuring the maximum number of OSPFv3 load-...

  • Page 350: Configuring Ospfv3 Route Redistribution

    Configuring OSPFv3 route redistribution To do… Use the command… Remarks Enter system view system-view — Step 1 Enter OSPFv3 view ospfv3 [ process-id ] — Step 2 Optional Specify a default cost Step 3 default cost value for redistributed routes Defaults to 1 import-route { isisv6 process-id | ospfv3 Redistribute routes from...

  • Page 351: Tuning And Optimizing Ospfv3 Networks

    Tuning and optimizing OSPFv3 networks This section describes configurations of OSPFv3 timers, interface DR priority, MTU check ignorance for DD packets, and disabling interfaces from sending OSPFv3 packets. The following are OSPFv3 timers: • Packet timer: Specified to adjust topology convergence speed and network load •...

  • Page 352: Configuring A Dr Priority For An Interface

    To do… Use the command… Remarks Configure the LSA Step 6 Optional ospfv3 timer retransmit interval [ retransmission instance instance-id ] Defaults to 5 seconds interval Optional ospfv3 trans-delay Configure the LSA seconds Step 7 transmission delay instance instance-id ] Defaults to 1 second Return to system Step 8...

  • Page 353: Disable Interfaces From Sending Ospfv3 Packets

    To do… Use the command… Remarks Enter system view system-view — Step 1 interface interface-type interface- Enter interface view — Step 2 number Required ospfv3 mtu-ignore [ instance Ignore MTU check for Step 3 DD packets instance-id ] Not ignored by default Disable interfaces from sending OSPFv3 packets To do…...

  • Page 354: Configuring Ospfv3 Gr

    Configuring OSPFv3 GR You cannot configure OSPFv3 GR after configuring OSPFv3 virtual links, because they are not supported at the same time. To prevent service interruption after a master or backup switchover, a GR Restarter running OSPFv3 must complete the following tasks: •...

  • Page 355: Displaying And Maintaining Ospfv3

    To do… Use the command… Remarks Optional graceful-restart helper strict-lsa- Enable strict LSA checking Step 4 checking Disabled by default Displaying and maintaining OSPFv3 To do… Use the command… Remarks Display OSPFv3 Step 1 debugging state display debugging ospfv3 information Display OSPFv3 process Step 2 display ospfv3 [ process-id ]...

  • Page 356: Ospfv3 Configuration Examples

    To do… Use the command… Remarks display ospfv3 [ process-id ] retrans-list [ { Display OSPFv3 link external | inter-prefix | inter-router | intra- Step 13 state retransmission list prefix | link | network | router | grace } [ link- information state-id ] [ originate-router ip-address ] | statistics Display OSPFv3...
  • Page 357 Configuration procedure Configure IPv6 addresses for interfaces (details not shown). Configure OSPFv3 basic functions. Configure Switch A. <SwitchA> system-view [SwitchA] ipv6 [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 [SwitchA-Vlan-interface200] quit Configure Switch B.
  • Page 358 Configure Switch D. <SwitchD> system-view [SwitchD] ipv6 [SwitchD] ospfv3 [SwitchD-ospfv3-1] router-id 4.4.4.4 [SwitchD-ospfv3-1] quit [SwitchD] interface Vlan-interface 400 [SwitchD-Vlan-interface400] ospfv3 1 area 2 [SwitchD-Vlan-interface400] quit Display OSPFv3 neighbor information on Switch B. [SwitchB] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------- Neighbor ID State...
  • Page 359 E2 - Type 2 external route, - Seleted route OSPFv3 Router with ID (4.4.4.4) (Process 1) ----------------------------------------------------------------------- *Destination: 2001::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001:1::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001:2::/64 Type Cost NextHop...
  • Page 360 ---------------------------------------------------------------------- *Destination: ::/0 Type : IA Cost : 11 NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001:1::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001:2::/64 Type Cost NextHop : directly-connected Interface:...

  • Page 361: Configuring Ospfv3 Dr Election

    *Destination: 2001:2::/64 Type Cost NextHop : directly-connected Interface: Vlan400 Configuring OSPFv3 DR election Network requirements In Figure 108, the following conditions are true: • The priority of Switch A is 100, the highest priority on the network, so it will be the DR. •...
  • Page 362 [SwitchA-Vlan-interface100] quit Configure Switch B. <SwitchB> system-view [SwitchB] ipv6 [SwitchB] ospfv3 [SwitchB-ospfv3-1] router-id 2.2.2.2 [SwitchB-ospfv3-1] quit [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] ospfv3 1 area 0 [SwitchB-Vlan-interface100] quit Configure Switch C. <SwitchC> system-view [SwitchC] ipv6 [SwitchC] ospfv3 [SwitchC-ospfv3-1] router-id 3.3.3.3 [SwitchC-ospfv3-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 1 area 0 [SwitchC-Vlan-interface100] quit...
  • Page 363 [SwitchD] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------- Neighbor ID State Dead Time Interface Instance ID 1.1.1.1 Full/DROther 00:00:30 Vlan100 2.2.2.2 Full/DROther 00:00:37 Vlan100 3.3.3.3 Full/Backup 00:00:31 Vlan100 Configure DR priorities for interfaces. Configure the DR priority of VLAN-interface 100 as 100 on Switch A. [SwitchA] interface Vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 dr-priority 100 [SwitchA-Vlan-interface100] quit...

  • Page 364: Configuring Ospfv3 Route Redistribution

    Use the shutdown and undo shutdown commands on interfaces to restart DR or BDR election (omitted). Display neighbor information on Switch A. Switch C becomes the BDR. [SwitchA] display ospfv3 peer OSPFv3 Area ID 0.0.0.0 (Process 1) ---------------------------------------------------------------------- Neighbor ID State Dead Time Interface...
  • Page 365 Figure 109 Network diagram for OSPFv3 route redistribution Configuration procedure Configure IPv6 addresses for interfaces (details not shown). Configure OSPFv3 basic functions. Enable OSPFv3 process 1 on Switch A. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] ospfv3 1 [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...
  • Page 366 [SwitchB-Vlan-interface300] quit Enable OSPFv3 process 2 on Switch C. <SwitchC> system-view [SwitchC] ipv6 [SwitchC] ospfv3 2 [SwitchC-ospfv3-2] router-id 4.4.4.4 [SwitchC-ospfv3-2] quit [SwitchC] interface vlan-interface 300 [SwitchC-Vlan-interface300] ospfv3 2 area 2 [SwitchC-Vlan-interface300] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ospfv3 2 area 2 [SwitchC-Vlan-interface400] quit Display the routing table of Switch C.
  • Page 367 Destination: FE80::/10 Protocol Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Configure OSPFv3 route redistribution. Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on Switch B. [SwitchB] ospfv3 2 [SwitchB-ospfv3-2] default cost 3 [SwitchB-ospfv3-2] import-route ospfv3 1 [SwitchB-ospfv3-2] import-route direct [SwitchB-ospfv3-2] quit...

  • Page 368: Configuring Ospfv3 Gr

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

  • Page 369: Troubleshooting Ospfv3 Configuration

    [SwitchA] ipv6 [SwitchA] ospfv3 1 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] graceful-restart enable [SwitchA-ospfv3-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 1 area 1 [SwitchA-Vlan-interface100] quit Enable OSPFv3 on Switch B and set the router ID to 2.2.2.2. (By default, GR helpler is enabled on Switch B.) <SwitchB>...

  • Page 370: Incorrect Routing Information

    Analysis If the physical link and lower protocol work well, check OSPF parameters configured on interfaces. The two neighboring interfaces must have the same parameters, such as the area ID, network segment and mask, and network type. If the network type is broadcast, at least one interface must have a DR priority higher than 0.

  • Page 371: Ipv6 Is-Is Configuration

    IPv6 IS-IS configuration Introduction to IPv6 IS-IS The IS-IS routing protocol supports multiple network protocols, including IPv6. IS-IS, with IPv6 support, is called IPv6 IS-IS dynamic routing protocol. The IETF defines two TLVs and a new NLPID to enable IPv6 support for IS-IS. IPv6 IS-IS supports all the features of IPv4 IS-IS, yet it advertises IPv6 routing information instead.

  • Page 372: Configuring Ipv6 Is-Is Routing Information Control

    To do… Use command to… Remarks system-view Enter system view –– Step 1 Required isis [ process-id ] [ vpn-instance Enable an IS-IS process Step 2 and enter IS-IS view vpn-instance-name ] Not enabled by default Configure the network Step 3 Required entity title for the IS-IS network-entity net...

  • Page 373: Displaying And Maintaining Ipv6 Is-Is

    To do… Use command to… Remarks ipv6 import-route protocol Optional Configure IPv6 IS-IS to process-id ] [ allow-ibgp ] [ cost Step 7 redistribute routes from cost | [ level-1 | level-2 | level- configured another routing protocol 1-2 ] | route-policy route-policy- default name | tag tag ]* Configure the maximum...

  • Page 374: Ipv6 Is-Is Configuration Example

    To do… Use the command… Remarks display isis lsdb [ [ l1 | l2 | level- 1 | level-2 ] | [ [ lsp-id lsp-id | lsp- Display LSDB information name lspname | local ] | verbose Available in any view Step 4 ]* ]* [ process-id | vpn-instance vpn- instance-name ]...
  • Page 375 Figure 111 Network diagram for IPv6 IS-IS basic configuration Configuration procedure Configure IPv6 addresses for interfaces. Configure IPv6 IS-IS. Configure Switch A. <SwitchA> system-view [SwitchA] isis 1 [SwitchA-isis-1] is-level level-1 [SwitchA-isis-1] network-entity 10.0000.0000.0001.00 [SwitchA-isis-1] ipv6 enable [SwitchA-isis-1] quit [SwitchA] interface Vlan-interface 100 [SwitchA-Vlan-interface100] isis ipv6 enable 1 [SwitchA-Vlan-interface100] quit Configure Switch B.
  • Page 376 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] ipv6 enable [SwitchC-isis-1] quit [SwitchC] interface Vlan-interface 100 [SwitchC-Vlan-interface100] isis ipv6 enable 1 [SwitchC-Vlan-interface100] quit [SwitchC] interface Vlan-interface 200 [SwitchC-Vlan-interface200] isis ipv6 enable 1 [SwitchC-Vlan-interface200] quit [SwitchC] interface Vlan-interface 300 [SwitchC-Vlan-interface300] isis ipv6 enable 1 [SwitchC-Vlan-interface300] quit Configure Switch D.

  • Page 377: Ipv6 Bgp Configuration

    IPv6 BGP configuration The term router in this document refers to both routers and Layer 3 switches. • This chapter describes only configuration for IPv6 BGP. For BGP-related information, see BGP in the • Layer 3 – IP Routing Configuration Guide. IPv6 BGP overview BGP-4 was designed to carry only IPv4 routing information, so other network layer protocols, such as IPv6, are not supported.

  • Page 378: Specifying An Ipv6 Bgp Peer

    Create a peer group before configuring basic functions for it. For related information, see Configuring IPv6 BGP peer group. Specifying an IPv6 BGP peer To do… Use the command… Remarks system-view Enter system view — Step 1 Required Enable BGP and enter Step 2 bgp as-number BGP view...

  • Page 379: Specifying The Source Interface For Establishing Tcp Connections

    To do… Use the command… Remarks Enter IPv6 address Step 3 ipv6-family — family view Configure a preferred Step 4 Optional value for routes peer { ipv6-group-name | ipv6- By default, the preferred value is received from an IPv6 address } preferred-value value peer or peer group If you both reference a routing policy and use the command peer { ipv6-group-name | ipv6-address } preferred-value value to set a preferred value for routes from a peer or peer group, then the routing...

  • Page 380: Allowing The Establishment Of A Non-Direct Ebgp Connection

    To establish a BGP connection, specify on the local router the respective source interfaces for • establishing TCP connections to the peers on the peering BGP router. Otherwise, the local BGP router may fail to establish TCP connections to the peers when using the outbound interfaces of the best routes as the source interfaces.

  • Page 381: Disabling Session Establishment To An Ipv6 Peer Or Peer Group

    Disabling session establishment to an IPv6 peer or peer group To do… Use the command… Remarks Enter system view system-view — Step 1 bgp as-number Enter BGP view Required Step 2 Enter IPv6 address family view ipv6-family — Step 3 Optional Disable session establishment peer { ipv6-group-name | ipv6-...

  • Page 382: Configuring Ipv6 Bgp Route Redistribution

    • Configure the IPv6 BGP basic functions Configuring IPv6 BGP route redistribution To do… Use the command… Remarks Enter system view system-view — Step 1 Enter BGP view bgp as-number Required Step 2 Enter IPv6 address family view ipv6-family — Step 3 Optional Enable default route...

  • Page 383: Configuring Outbound Route Filtering

    Configuring outbound route filtering To do… Use the command… Remarks Enter system view system-view — Step 1 Enter BGP view bgp as-number Required Step 2 Enter IPv6 address Step 3 ipv6-family — family view filter-policy { acl6-number | ipv6- Required Configure the filtering Step 4 prefix ipv6-prefix-name } export [...

  • Page 384: Configuring Ipv6 Bgp And Igp Route Synchronization

    To do… Use the command… Remarks filter-policy acl6-number Required Configure inbound route Step 4 ipv6-prefix ipv6-prefix-name filtering Not configured by default import peer { ipv6-group-name | ipv6- Apply a routing policy to Step 5 Required route-policy routes from an IPv6 peer or address route- Not applied by default...

  • Page 385: Configuring Route Dampening

    To do… Use the command… Remarks Enter BGP view bgp as-number Required Step 2 Enter IPv6 address family view ipv6-family — Step 3 Required Enable route synchronization Step 4 synchronization between IPv6 BGP and IGP Not enabled by default Configuring route dampening To do…...

  • Page 386: Configuring The Med Attribute

    To do… Use the command… Remarks system-view Enter system view — Step 1 Enter BGP view bgp as-number Required Step 2 Enter IPv6 address family Step 3 ipv6-family — view Optional The default preference Configure preference values preference external-preference Step 4 values external, for IPv6 BGP external,...

  • Page 387: Configuring The As_Path Attribute

    To do… Use the command… Remarks Optional Configure a default MED Step 4 default med med-value value Defaults to 0 Optional Enable the comparison of Step 5 MED for routes from different compare-different-as-med enabled eBGP peers default Optional Enable the comparison of Step 6 bestroute compare-med MED for routes from each AS...

  • Page 388: Tuning And Optimizing Ipv6 Bgp Networks

    Tuning and optimizing IPv6 BGP networks This section describes configurations of IPv6 BGP timers, IPv6 BGP connection soft reset, and the maximum number of load balanced routes. • IPv6 BGP timers After establishing an IPv6 BGP connection, two routers send keepalive messages periodically to each other to keep the connection.

  • Page 389: Configuring Ipv6 Bgp Soft Reset

    To do… Use the command… Remarks Optional The interval for sending peer { ipv6-group-name | ipv6- Configure the interval for Step 5 the same update to an sending the same update to an address route-update- iBGP peer or an eBGP IPv6 peer or peer group interval interval peer defaults to 15...

  • Page 390: Enabling The Ipv6 Bgp Orf Capability

    To do… Use the command… Remarks return Return to user view Step 5 refresh bgp ipv6 { all | ipv6-address | Required Soft-reset BGP connections Step 6 group ipv6-group-name external manually internal } { export | import } If the peer keep-all-routes command is used, then all routes from the peer or peer group are saved regardless of whether the filtering policy is available.

  • Page 391: Configuring The Maximum Number Of Load-Balanced Routes

    To do… Use the command… Remarks Required peer { group-name | ip-address | ipv6- Enable the ORF IP prefix Step 6 address } capability-advertise orf negotiation capability for a Not supported by BGP peer or peer group ip-prefix { both | receive | send } default Table 7 Description of the both, send, and receive parameters and the negotiation result...

  • Page 392: Configuring A Large-Scale Ipv6 Bgp Network

    Configuring a large-scale IPv6 BGP network In a large-scale IPv6 BGP network, configuration and maintenance become inconvenient because of too many peers. In this case, configuring peer groups makes management easier and improves route distribution efficiency. A peer group includes an iBGP peer group, where peers belong to the same AS, and an eBGP peer group, where peers belong to different ASs.
  • Page 393 Creating a pure eBGP peer group To do… Use the command… Remarks Enter system view system-view — Step 1 Required Enable BGP and enter Step 2 bgp as-number BGP view Disabled by default Enter IPv6 address Step 3 ipv6-family — family view group Create an eBGP peer...

  • Page 394: Configuring Ipv6 Bgp Community

    Configuring IPv6 BGP community Advertise community attribute to an IPv6 peer or peer group To do… Use the command… Remarks Enter system view system-view — Step 1 Required Enable BGP and enter BGP Step 2 bgp as-number view Disabled by default Enter IPv6 address family Step 3 ipv6-family...

  • Page 395: Configuring 6Pe

    To do… Use the command… Remarks ipv6-family Enter IPv6 address family view — Step 3 Configure the router as a route Step 4 Required peer { ipv6-group-name | ipv6- reflector and specify an IPv6 address } reflect-client Not configured by default peer or peer group as a client Optional Enable route reflection between...

  • Page 396: Configuring Basic 6Pe Capabilities

    The P (Provider) router in Figure 112 refers to a backbone router in the network of a service provider. P is not directly connected with a CE, and is required to have the basic MPLS capability. When an ISP can use the existing IPv4/MPLS network to provide IPv6 traffic switching capability, only the PE routers must be upgraded.
  • Page 397 To do… Use the command… Remarks Required bgp as-number Enable BGP and enter BGP view Disabled Step 2 default Required Specify the AS number for the peer { ipv4-group-name | ipv4-address Step 3 Not specified by 6PE peer or peer group } as-number as-number default Enter IPv6 address family view...

  • Page 398: Displaying And Maintaining Ipv6 Bgp

    To do… Use the command… Remarks Optional Configure the switch as a route Step 15 peer { group-name | ipv4-address } reflector and the 6PE peer or Not configured by reflect-client peer group as a client default Configure an upper limit of IPv6 Step 16 Optional address prefixes that can be...

  • Page 399: Resetting Ipv6 Bgp Connections

    To do… Use the command… Remarks Display the prefix entries in Step 5 display bgp ipv6 peer { ip-address | ipv6- the ORF information of the address } received ipv6-prefix specified BGP peer display bgp ipv6 routing-table [ ipv6- Display IPv6 BGP routing Step 6 table information address prefix-length ]...

  • Page 400: Clearing Ipv6 Bgp Information

    To do… Use the command… Remarks Perform a Step 1 refresh bgp ipv6 { ipv4-address | ipv6-address | all | soft reset on external | group ipv6-group-name | internal } { export | IPv6 BGP import } Available in connections user view reset bgp ipv6 { as-number | ipv4-address | ipv6-address [ Reset IPv6...

  • Page 401: Ipv6 Bgp Basic Configuration

    IPv6 BGP basic configuration Network requirements In Figure 113 are IPv6 BGP switches. Between Switch A and Switch B is an eBGP connection. Switch B, Switch C, and Switch D are fully meshed through iBGP connections. Figure 113 IPv6 BGP basic configuration network diagram Configuration procedure Configure IPv6 addresses for interfaces (details not shown).
  • Page 402 Configure Switch D. <SwitchD> system-view [SwitchD] ipv6 [SwitchD] bgp 65009 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] ipv6-family [SwitchD-bgp-af-ipv6] peer 9:1::1 as-number 65009 [SwitchD-bgp-af-ipv6] peer 9:2::1 as-number 65009 [SwitchD-bgp-af-ipv6] quit [SwitchD-bgp] quit Configure the eBGP connection. Configure Switch A. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] ipv6-family...

  • Page 403: Ipv6 Bgp Route Reflector Configuration

    [SwitchC] display bgp ipv6 peer BGP local router ID : 3.3.3.3 Local AS number : 65009 Total number of peers : 2 Peers in established state : Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 9:3::1 4 65009 0 00:02:18 Established 9:2::2 4 65009 0 00:01:52...
  • Page 404 [SwitchA] bgp 100 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] ipv6-family [SwitchA-bgp-af-ipv6] peer 100::2 as-number 200 [SwitchA-bgp-af-ipv6] network 1:: 64 Configure Switch B. <SwitchB> system-view [SwitchB] ipv6 [SwitchB] bgp 200 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] ipv6-family [SwitchB-bgp-af-ipv6] peer 100::1 as-number 100 [SwitchB-bgp-af-ipv6] peer 101::1 as-number 200 [SwitchB-bgp-af-ipv6] peer 101::1 next-hop-local Configure Switch C.

  • Page 405: Troubleshooting Ipv6 Bgp Configuration

    Troubleshooting IPv6 BGP configuration No IPv6 BGP peer relationship established Symptom Display BGP peer information using the display bgp ipv6 peer command. The state of the connection to the peer cannot become established. Analysis To become IPv6 BGP peers, any two routers must establish a TCP session using port 179 and exchange open messages successfully.

  • Page 406: Ipv6 Unicast Policy Routing Configuration

    IPv6 unicast policy routing configuration The switch operates in IRF or standalone (the default) mode. For more information about the IRF mode, see IRF in the IRF Configuration Guide. Introduction to IPv6 unicast policy routing IPv6 unicast policy routing is used to route IPv6 unicasts based on a policy. Policy routing, also known as PBR, is a routing mechanism based on a user-defined policy.
  • Page 407 Then… If a packet… In permit mode In deny mode The apply clause is not executed, The apply clause is executed, and the packets will not go to the next Matches the if-match clause on the packet will not go to the next policy node for a match, and will the policy node policy node for a match.

  • Page 408: Configuring Ipv6 Local Policy Routing

    To do… Use the command… Remarks Optional If you set two next hops for a policy at the same time, only the primary apply ipv6-address next- Set a next hop for Step 4 next hop takes effect. permitted IPv6 packets hop ipv6-address The backup next hop takes effect only when...

  • Page 409: Displaying And Maintaining Ipv6 Unicast Policy Routing Configuration

    To do… Use the command… Remarks Required Configure IPv6 interface Step 3 ipv6 policy-based-route policy- policy routing based on a configured name policy default Displaying and maintaining IPv6 unicast policy routing configuration To do… Use the command… Remarks display ipv6 policy-based- Display the IPv6 PBR Available...

  • Page 410: Configuring Ipv6 Local Policy Routing Based On Packet Type

    Configuring IPv6 local policy routing based on packet type Network requirements As shown in Figure 115, configure policy routing on Switch A so all TCP packets are forwarded through next hop 1::2, and other IPv6 packets are forwarded according to the routing table. Switch A is directly connected to Switch B and Switch C, respectively.
  • Page 411 <SwitchB> system-view [SwitchB] interface Vlan-interface 10 [SwitchB-Vlan-interface10] ip address 1::2 64 [SwitchB-Vlan-interface10] quit Configure Switch C. Configure the IPv6 address for VLAN-interface 20. <SwitchC> system-view [SwitchC] interface Vlan-interface 20 [SwitchC-Vlan-interface20] ip address 2::2 64 [SwitchC-Vlan-interface20] quit Verification Telnet to Switch B (1::2/64) from Switch A. The operation succeeds. <SwitchA>...

  • Page 412: Configuring Ipv6 Interface Policy Routing Based On Packet Type

    bytes=56 Sequence=4 hop limit=64 time = 2 ms Reply from 2::2 bytes=56 Sequence=5 hop limit=64 time = 2 ms --- 2::2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 2/2/4 ms Telnet uses TCP, and ping uses IMCP. The preceding results show that all TCP packets of Switch A are forwarded to next hop 1::2, and packets except TCP packets are forwarded.
  • Page 413 Configuration procedure In this example, RIPng is configured to ensure the reachability among switches. Configure Switch A. Configure RIPng. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] ripng 1 [SwitchA-ripng-1] quit [SwitchA] interface Vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 1::1 64 [SwitchA-Vlan-interface20] ripng 1 enable [SwitchA-Vlan-interface20] quit [SwitchA] interface Vlan-interface 30 [SwitchA-Vlan-interface30] ipv6 address 2::1 64...
  • Page 414 Configure RIPng. <SwitchB> system-view [SwitchB] ipv6 [SwitchB] ripng 1 [SwitchB-ripng-1] quit [SwitchB] interface Vlan-interface 20 [SwitchB-Vlan-interface20] ipv6 address 1::2 64 [SwitchB-Vlan-interface20] ripng 1 enable [SwitchB-Vlan-interface20] quit Configure Switch C. Configure RIPng. <SwitchC> system-view [SwitchC] ipv6 [SwitchC] ripng 1 [SwitchC-ripng-1] quit [SwitchC] interface Vlan-interface 30 [SwitchC-Vlan-interface30] ipv6 address 2::2 64 [SwitchC-Vlan-interface30] ripng 1 enable...

  • Page 415: Routing Policy Configuration

    Routing policy configuration Introduction to routing policy Routing policy and policy routing A routing policy is used on a router for route filtering and attributes modification when routes are received, advertised, or redistributed. Policy routing, also called PBR, is a routing mechanism based on a user-defined policy. Routing policy involves both IPv4 routing policy and IPv6 routing policy.

  • Page 416: Routing Policy Application

    AS-PATH list An AS-PATH list, configured based on the BGP AS-PATH attribute, can only be used to match BGP routing information. Community list A community list, configured based on the BGP community attribute, can only be used to match BGP routing information. Extended community list An extended community list, configured based on the BGP extended community attribute (Route- Target for VPN and Source of Origin), can only be used to match BGP routing information.

  • Page 417: Defining An Ip-Prefix List

    Not defined by default less-equal max-mask-length ] If all the items are set to the deny mode, no routes can pass the IPv4 prefix list. Therefore, H3C recommends that you define the permit 0.0.0.0 0 less-equal 32 item following multiple deny items to allow other IPv4 routing information to pass.

  • Page 418: Defining An As-Path List

    To do… Use the command… Remarks ip ipv6-prefix ipv6-prefix-name [ index index-number ] { deny | permit } ipv6- Required Define an IPv6 Step 2 address prefix-length [ greater-equal min- prefix list Not defined by default prefix-length ] [ less-equal max-prefix-length If all items are set to the deny mode, then no routes can pass the IPv6 prefix list.

  • Page 419: Defining An Extended Community List

    To do… Use the command… Remarks ip community-list basic-comm-list- deny permit Define a basic community-number-list ] [ internet | community list Define a no-advertise | no-export | no- Step 2 Required to define either community export-subconfed ] * Not defined by default list Define ip community-list adv-comm-list-...

  • Page 420: Creating A Routing Policy

    Prerequisites • Filters • Routing protocols You must also decide on the following: • Name of the routing policy and node numbers • Match criteria • Attributes to be modified Creating a routing policy To do… Use the command… Remarks Enter system Step 1 system-view...
  • Page 421 To do… Use the command… Remarks route-policy route-policy-name Enter routing policy view deny | permit } node node- Required Step 2 number Match IPv4 routing information specified if-match acl acl-number Optional in the ACL configured Define Match IPv4 routing Step 3 default if-match ip-prefix ip-prefix-name match...

  • Page 422: Defining Apply Clauses

    To do… Use the command… Remarks if-match route-type { external- type1 external-type2 Optional external-type1or2 | is-is-level- Match routing information having Step 11 1 | is-is-level-2 | internal | configured the specified route type nssa-external-type1 nssa- default external-type2 nssa- external-type1or2 } * Optional Match RIP, OSPF, and IS-IS Step 12...
  • Page 423 To do… Use the command… Remarks apply community { none | additive | Set the community { community-number&<1-16> | aa:nn&<1- Step 5 Optional attribute for BGP 16> | internet | no-export-subconfed Not set by default routing information | no-export | no-advertise } * [ additive ] } Optional Set a cost for...

  • Page 424: Defining A Continue Clause

    To do… Use the command… Remarks Set an FRR backup Step 17 apply fast-reroute backup-interface Optional outbound interface interface-type interface-number [ backup- and a backup next Not configured by default nexthop ip-address ] The difference between IPv4 and IPv6 apply clauses is the command for setting the next hop for routing •...

  • Page 425: Displaying And Maintaining The Routing Policy

    Displaying and maintaining the routing policy To do… Use the command… Remarks Display BGP AS- Step 1 PATH list display ip as-path [ as-path-number ] information Display BGP display community-list basic- Step 2 community list community-list-number adv-community-list- information number ] Display BGP Step 3 display ip extcommunity-list [ ext-comm-...
  • Page 426 • On Switch B, enable route redistribution from IS-IS to OSPF, and apply a routing policy to set the cost of route 172.17.1.0/24 to 100 and the tag of route 172.17.2.0/24 to 20. Figure 117 Network diagram for routing policy application to route redistribution Configuration procedure Specify IP addresses for interfaces (details not shown).
  • Page 427 [SwitchB-isis-1] is-level level-2 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] isis enable [SwitchB-Vlan-interface200] quit Configure OSPF and route redistribution. Configure OSPF on Switch A. <SwitchA> system-view [SwitchA] ospf [SwitchA-ospf-1] area 0 [SwitchA-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit On Switch B, configure OSPF and enable route redistribution from IS-IS.
  • Page 428 192.168.2.0/24 Type2 192.168.1.2 192.168.2.2 Total Nets: 5 Intra Area: 1 Inter Area: 0 ASE: 4 NSSA: 0 Configure filtering lists. Configure ACL 2002 to permit route 172.17.2.0/24. [SwitchB] acl number 2002 [SwitchB-acl-basic-2002] rule permit source 172.17.2.0 0.0.0.255 [SwitchB-acl-basic-2002] quit Configure IP prefix list prefix-a to permit route 172.17.1.0/24. [SwitchB] ip ip-prefix prefix-a index 10 permit 172.17.1.0 24 Configure a routing policy.

  • Page 429: Applying A Routing Policy To Ipv6 Route Redistribution

    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 192.168.2.0/24 Type2 192.168.1.2 192.168.2.2 Total Nets: 5 Intra Area: 1 Inter Area: 0 ASE: 4 NSSA: 0 Applying a routing policy to IPv6 route redistribution Network requirements •...
  • Page 430 [SwitchA-Vlan-interface200] quit Enable RIPng on VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ripng 1 enable [SwitchA-Vlan-interface100] quit Configure three static routes. [SwitchA] ipv6 route-static 20:: 32 11::2 [SwitchA] ipv6 route-static 30:: 32 11::2 [SwitchA] ipv6 route-static 40:: 32 11::2 Configure a routing policy. [SwitchA] ip ipv6-prefix a index 10 permit 30:: 32 [SwitchA] route-policy static2ripng deny node 0 [SwitchA-route-policy] if-match ipv6 address prefix-list a...

  • Page 431: Applying A Routing Policy To Filter Received Bgp Routes

    Dest 40::/32, via FE80::7D58:0:CA03:1, cost 1, tag 0, A, 3 Sec Applying a routing policy to filter received BGP routes Network requirements • All the switches in Figure 119 run BGP. Switch C establishes eBGP connections with other switches. • Configure a routing policy on Switch D to reject routes from AS 200.
  • Page 432 [SwitchC] bgp 300 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] peer 1.1.1.1 as-number 100 [SwitchC-bgp] peer 1.1.2.1 as-number 200 [SwitchC-bgp] peer 1.1.3.2 as-number 400 Configure Switch D. <SwitchD> system-view [SwitchD] bgp 400 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] peer 1.1.3.1 as-number 300 [SwitchD-bgp] quit On Switch A, inject routes 4.4.4.4/24, 5.5.5.5/24, and 6.6.6.6/24 to BGP. [SwitchA-bgp] network 4.4.4.4 24 [SwitchA-bgp] network 5.5.5.5 24 [SwitchA-bgp] network 6.6.6.6 24...

  • Page 433: Troubleshooting Routing Policy Configuration

    *> 9.9.9.0/24 1.1.3.1 300 200i Figure 119 shows that Switch D has learned routes 4.4.4.0/24, 5.5.5.0/24, and 6.6.6.0/24 from AS 100 and 7.7.7.0/24, 8.8.8.0/24, and 9.9.9.0/24 from AS 200. Configure Switch D to reject routes from AS 200. Configure AS_PATH list 1 on Switch D. [SwitchD] ip as-path 1 permit .*200.* Configure a routing policy named rt1 on Switch D.

  • Page 434: Ipv6 Routing Information Filtering Failure

    Analysis At least one item of the IP prefix list must be configured as permit mode, and at least one node in the Routing policy must be configured as permit mode. Solution • Use the display ip ip-prefix command to display IP prefix list information. •...

  • Page 436: Obtaining Support For Your Product

    Contact your authorized reseller or 3Com for a complete list of the value-added services available in your area. Troubleshoot online You will find support tools posted on the web site at http://www.h3cnetworks.com/ under Support, Knowledgebase. The Knowledgebase helps you troubleshoot H3C products. This query-based interactive tool contains thousands of technical solutions.

  • Page 437: Access Software Downloads

    Access software downloads Software Updates are the bug fix / maintenance releases for the version of software initially purchased with the product. In order to access these Software Updates you must first register your product on the web site at http://www.h3cnetworks.com, go to Support, Product Registration.

  • Page 438: Acronyms

    Acronyms # A B C D E F G H I K L M N O P Q R S T U V W X Z Acronym Full spelling Return 10GE Ten-GigabitEthernet Return Authentication, Authorization and Accounting Activity Based Costing Area Border Router Alternating Current Acknowledgement...
  • Page 439 Acronym Full spelling Auxiliary (port) Active Virtual Forwarder Return Bearer Control Backup Designated Router Best Effort Bidirectional Forwarding Detection Border Gateway Protocol BIMS Branch Intelligent Management System BOOTP Bootstrap Protocol BPDU Bridge Protocol Data Unit Basic Rate Interface Bootstrap Router BitTorrent BSR State Burst Tolerance...
  • Page 440 Acronym Full spelling CIDR Classless Inter-Domain Routing Committed Information Rate CIST Common and Internal Spanning Tree Command Line Interface CLNP Connectionless Network Protocol Customer Premise Equipment CPOS Channelized POS Central Processing Unit Custom Queuing Carriage Return Cyclic Redundancy Check CR-LSP Constraint-based Routing LSP CR-LDP Constraint-based Routing LDP...
  • Page 441 Acronym Full spelling Designated Router DSCP Differentiated Services Code point Priority Digital Signal Processor Data Terminal Equipment Downstream Unsolicited DUID DHCP Unique Identifier DUID-LL DUID based Link Layer address Distance Vector Routing Algorithm DVMRP Distance Vector Multicast Routing Protocol DWDM Dense Wavelength Division Multiplexing Return EBGP...
  • Page 442 Acronym Full spelling Frame Relay Fast Reroute FRTT Fairness Round Trip Time Finite State Machine Functional Test File Transfer Protocol Return GARP Generic Attribute Registration Protocol Gigabit Ethernet Graceful Restart Generic Routing Encapsulation Generic Traffic Shaping GVRP GARP VLAN Registration Protocol Return High Availability HABP...
  • Page 443 Acronym Full spelling IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IGMP Internet Group Management Protocol IGMP-Snooping Internet Group Management Protocol Snooping Interior Gateway Protocol Incoming Label Map Internet Locator Service Intelligent Network IntServ Integrated Service Internet Protocol IPng IP Next Generation...
  • Page 444 Acronym Full spelling LACP Link Aggregation Control Protocol LACPDU Link Aggregation Control Protocol Data Unit Local Area Network Link Control Protocol LDAP Lightweight Directory Access Protocol Label Distribution Protocol Label Edge Router LFIB Label Forwarding Information Base Label Information Base Link Layer Control LLDP Link Layer Discovery Protocol...
  • Page 445 Acronym Full spelling Multi-VPN instance Customer Edge Multicast Domain Medium Dependent Interface Multicast Distribution Tree Multi-Exit Discriminator MAC Forced Forwarding Management Information Base Multicast Listener Discovery Protocol MLD-Snooping Multicast Listener Discovery Snooping Meet-Me Conference MODEM Modulator/Demodulator Multilink PPP MP-BGP Multiprotocol extensions for BGP-4 Middle-level PE MP-group Multilink Point to Point Protocol group...
  • Page 446 Acronym Full spelling NBMA Non Broadcast Multi-Access NetBIOS over TCP/IP Network Control Protocol Neighborhood discovery NetStream Data Analyzer Network Data Collector Neighbor Discovery Protocol NetBIOS Network Basic Input/Output System NHLFE Next Hop Label Forwarding Entry Network Load Balancing NLPID Network Layer Protocol Identifier NLRI Network Layer Reachability Information Network Management Station...
  • Page 447 Acronym Full spelling Provider P2MP Point to MultiPoint Point To Point Password Authentication Protocol Printed Circuit Board Pulse Code Modulation Powered Device, Prefix Delegation or Pure Data Protocol Data Unit Provider Edge Penultimate Hop Popping Physical layer Protocol Independent Multicast PIM-DM Protocol Independent Multicast-Dense Mode PIM-SM...
  • Page 448 Acronym Full spelling QACL QoS/ACL QinQ 802.1Q in 802.1Q Quality of Service QQIC Querier's Query Interval Code Querier's Robustness Variable Return Registration Authority or Router Advertisement RADIUS Remote Authentication Dial in User Service random-access memory Routing Domain Router Distinguisher Random Early Detection Request For comments Routing Information Protocol RIPng...
  • Page 449 Acronym Full spelling Return Source Active Sub-network Bandwidth Management SCFF Single Choke Fairness Frame Signal Degrade Synchronous Digital Hierarchy SETS Synchronous Equipment Timing Source Sampling Frequency Source-Filtered Multicast SFTP Secure FTP Share-MDT Share-Multicast Distribution Tree Session Initiation Protocol Site-of-Origin Site-of-Origin Service Level Agreement Standby Main Board SMTP...
  • Page 450 Acronym Full spelling STM-16c SDH Transport Module -16c STM-4c SDH Transport Module -4c Spanning Tree Protocol Signaling Virtual Connection SVLAN Service Provider Virtual Local Area Network Switch-MDT Switch-Multicast Distribution Tree Synchronize Return Terminal Adapter TACACS Terminal Access Controller Access Control System Time Division Multiplexing Transmission Control Protocol Topology Change Notification...
  • Page 451 Acronym Full spelling Virtual Channel Identifier Virtual Ethernet Virtual Forwarder Virtual File System VLAN Virtual Local Area Network Virtual Leased Lines Video On Demand VoIP Voice over IP Virtual Operate System VPDN Virtual Private Dial-up Network VPDN Virtual Private Data Network Virtual Path Identifier VPLS Virtual Private Local Switch...

  • Page 452: Index

    Index advertising a host route ........ 1 17 resetting connections ....... 275 BFD for BGP ..........273 route attributes ........260 configuration example ......299 route reflector configuration example ..289 BFD for IS-IS ........206, 233 route selection ........244 BFD for RIP ..........
  • Page 453 load balancing ........266 displaying and maintaining ...... 308 peer group ..........248 interface policy routing ......307 quick eBGP session reestablishment ... 266 interface policy routing based on packet type ............31 1 route dampening ........247 local policy routing based on packet type .. 308 route reflector ..........
  • Page 454 route attributes ........385 address format ........168 route dampening ........385 area ............169 route redistribution ........382 basic concepts ......... 167 route reflector .......... 394 basic functions ........182 configuration examples ......207 route reflector configuration example ..403 troubleshooting ........
  • Page 455 calculating a backup next hop automatically IS-IS routing information control ....184 ............204 default route ........... 188 configuration example ......228 equal-cost routes ........187 designating a backup next hop with a routing link cost ..........184 policy ..........204 priority ..........
  • Page 456 configuration examples ......134 calculating a backup next hop automatically ............128 configuration tasks ........101 designating a backup next hop using a routing configuring BFD ........ 131, 163 policy ..........128 cost for an interface ........1 13 introduction ..........127 displaying and maintaining ......
  • Page 457 LSR ............92 OSPFv3 network types ........ 346 LSU ............92 NBMA or P2MP neighbor ......346 packet header ........... 89 network type for an interface ....346 OSPF packets ..........121 OSPFv3 networks ........351 disabling interfaces ......... 353 disabling interfaces from receiving or sending ............
  • Page 458 routing table ..........42 RIPng ............324 timers..........42, 53 configuring basic functions example ..334 troubleshooting ......... 79 displaying and maintaining ...... 333 versions ............ 43 equal cost routes for load balancing ..333 introduction ..........324 RIP basic functions ........46 configuring an additional metric for a RIP packet processing procedure ....
  • Page 459 applying a routing policy to IPv4 route dynamic routing ........22 redistribution example ......425 dynamic routing protocols classification ..22 applying a routing policy to IPv6 route load balancing ......... 24 redistribution example ......429 route backup ..........24 AS-PATH list ..........

Table of Contents