H3C S5800 Series Configuration Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. s5800 series
  6. Configuration manual

H3C S5800 Series Configuration Manual

Layer 3 - ip routing
Hide thumbs Also See for S5800 Series:
1
2
3
4
5
6
Table Of Contents
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Installation Manual
H3C S5820X&S5800 Series Ethernet Switches
Layer 3 - IP Routing
Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Document Version: 6W103-20100716
Product Version: Release 1110

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for H3C S5800 Series

Summary of Contents for H3C S5800 Series

  • Page 1 H3C S5820X&S5800 Series Ethernet Switches Layer 3 - IP Routing Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Document Version: 6W103-20100716 Product Version: Release 1110...
  • 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 S5800&S5820X documentation set includes 11 configuration guides, which describe the software features for the S5800&S5820X Series Ethernet 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 Means reader be careful. Improper operation may cause data loss or damage to equipment. Means a complementary description. About the H3C S5800&S5820X Documentation Set The H3C S5800&S5820X documentation set also includes: Category Documents Purposes Marketing brochures Describe product specifications and benefits.
  • Page 5 Interface Cards User available for the products. Manual Describes the benefits, features, hardware H3C OAP Cards User specifications, installation, and removal of the OAP Manual cards available for the products. H3C Low End Series...
  • Page 6 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 &...

  • Page 7: Table Of Contents

    Table of Contents 1 IP Routing Basics Configuration ·············································································································1-1 Routing····················································································································································1-1 Routing Table and FIB Table ··········································································································1-1 Routing Protocol Overview ·····················································································································1-3 Static Routing and Dynamic Routing·······························································································1-3 Classification of Dynamic Routing Protocols···················································································1-3 Routing Protocols and Routing Priority ···························································································1-4 Load Balancing and Route Backup ·································································································1-5 Route Recursion······························································································································1-6 Sharing of Routing Information········································································································1-6 Configuring a Router ID ··························································································································1-6...
  • Page 8 Configuration Procedure··················································································································3-7 Configuring RIP Route Control ···············································································································3-9 Configuring an Additional Routing Metric ······················································································3-10 Configuring RIPv2 Route Summarization······················································································3-10 Disabling Host Route Reception ···································································································3-11 Advertising a Default Route···········································································································3-12 Configuring Inbound/Outbound Route Filtering·············································································3-13 Configuring a Preference for RIP ··································································································3-14 Configuring RIP Route Redistribution ···························································································3-14 Configuring RIP Network Optimization ·································································································3-15 Configuring RIP Timers ·················································································································3-15 Configuring Split Horizon and Poison Reverse ·············································································3-15...
  • Page 9 OSPF Configuration Task List ··············································································································4-19 Enabling OSPF ·····································································································································4-21 Prerequisites··································································································································4-21 Configuration Procedure················································································································4-21 Configuring OSPF Areas ······················································································································4-22 Prerequisites··································································································································4-23 Configuring a Stub Area ················································································································4-23 Configuring an NSSA Area············································································································4-24 Configuring a Virtual Link ··············································································································4-24 Configuring OSPF Network Types········································································································4-25 Prerequisites··································································································································4-25 Configuring the OSPF Network Type for an Interface as Broadcast ············································4-26 Configuring the OSPF Network Type for an Interface as NBMA ··················································4-26 Configuring the OSPF Network Type for an Interface as P2MP···················································4-27 Configuring the OSPF Network Type for an Interface as P2P ······················································4-28...
  • Page 10 Configuring OSPF Graceful Restart······································································································4-46 Configuring the OSPF GR Restarter ·····························································································4-47 Configuring the OSPF GR Helper ·································································································4-48 Triggering OSPF Graceful Restart ································································································4-49 Configuring BFD for OSPF ···················································································································4-49 Configuring Control Packet Bidirectional Detection ······································································4-49 Configuring Echo Packet Single-Hop Detection············································································4-50 Displaying and Maintaining OSPF ········································································································4-51 OSPF Configuration Examples ·············································································································4-52 Configuring OSPF Basic Functions·······························································································4-52 Configuring OSPF Route Redistribution························································································4-55...
  • Page 11 Configuring IS-IS Route Filtering···································································································5-24 Configuring IS-IS Route Leaking···································································································5-25 Tuning and Optimizing IS-IS Networks ·································································································5-25 Configuration Prerequisites ···········································································································5-25 Specifying Intervals for Sending IS-IS Hello and CSNP Packets ·················································5-26 Specifying the IS-IS Hello Multiplier ······························································································5-26 Configuring a DIS Priority for an Interface·····················································································5-27 Disabling an Interface from Sending/Receiving IS-IS Packets ·····················································5-27 Enabling an Interface to Send Small Hello Packets······································································5-28 Configuring LSP Parameters·········································································································5-28...
  • Page 12 BGP Configuration Task List·················································································································6-17 Configuring BGP Basic Functions·········································································································6-18 Prerequisites··································································································································6-18 Creating a BGP Connection ··········································································································6-18 Specifying the Source Interface for TCP Connections··································································6-19 Allowing Establishment of eBGP Connection to a Non Directly Connected Peer/Peer Group·····6-20 Controlling Route Generation ···············································································································6-21 Prerequisites··································································································································6-21 Injecting a Local Network ··············································································································6-21 Configuring BGP Route Redistribution··························································································6-21 Enabling Default Route Redistribution into BGP···········································································6-22 Controlling Route Distribution and Reception·······················································································6-22...
  • Page 13 Enabling Logging of Peer State Changes·····························································································6-46 Configuring BFD for BGP······················································································································6-46 Displaying and Maintaining BGP ··········································································································6-47 Displaying BGP ·····························································································································6-47 Resetting BGP Connections··········································································································6-48 Clearing BGP Information ·············································································································6-49 BGP Configuration Examples ···············································································································6-49 BGP Basic Configuration···············································································································6-49 BGP and IGP Synchronization Configuration ···············································································6-52 BGP Load Balancing Configuration·······························································································6-55 BGP Community Configuration ·····································································································6-57 BGP Route Reflector Configuration ······························································································6-59 BGP Confederation Configuration·································································································6-61...
  • Page 14 Configuring Split Horizon and Poison Reverse ···············································································8-8 Configuring Zero Field Check on RIPng Packets············································································8-9 Configuring the Maximum Number of Equal Cost Routes for Load Balancing ·······························8-9 Displaying and Maintaining RIPng ········································································································8-10 RIPng Configuration Example···············································································································8-10 Configure RIPng Basic Functions ·································································································8-10 Configuring RIPng Route Redistribution ·······················································································8-13 9 OSPFv3 Configuration ······························································································································9-1 Introduction to OSPFv3···························································································································9-1 OSPFv3 Overview ···························································································································9-1...
  • Page 15 Displaying and Maintaining OSPFv3 ····································································································9-16 OSPFv3 Configuration Examples ·········································································································9-17 Configuring OSPFv3 Areas ···········································································································9-17 Configuring OSPFv3 DR Election ·································································································9-21 Configuring OSPFv3 Route Redistribution····················································································9-24 Configuring OSPFv3 GR ···············································································································9-26 Troubleshooting OSPFv3 Configuration ·······························································································9-28 No OSPFv3 Neighbor Relationship Established ···········································································9-28 Incorrect Routing Information ········································································································9-28 10 IPv6 IS-IS Configuration························································································································10-1 Introduction to IPv6 IS-IS ······················································································································10-1 Configuring IPv6 IS-IS Basic Functions ································································································10-2...
  • Page 16 Configuring the AS_PATH Attribute ····························································································11-13 Tuning and Optimizing IPv6 BGP Networks ·······················································································11-14 Prerequisites································································································································11-15 Configuring IPv6 BGP Timers ·····································································································11-15 Configuring IPv6 BGP Soft Reset ·······························································································11-15 Enabling the IPv6 BGP ORF Capability ······················································································11-16 Configuring the Maximum Number of Load-Balanced Routes····················································11-17 Configuring a Large Scale IPv6 BGP Network ···················································································11-18 Prerequisites································································································································11-18 Configuring IPv6 BGP Peer Group······························································································11-18 Configuring IPv6 BGP Community ······························································································11-20...
  • Page 17 Troubleshooting Route Policy Configuration ······················································································12-18 IPv4 Routing Information Filtering Failure ···················································································12-18 IPv6 Routing Information Filtering Failure ···················································································12-18 13 Policy Routing Configuration···············································································································13-1 Policy Routing Overview ·······················································································································13-1 Configuring Policy Routing····················································································································13-1 Configuring a QoS Policy ··············································································································13-1 Applying the QoS Policy················································································································13-2 Displaying and Maintaining QoS Policies ·····························································································13-3 Policy Routing Configuration Examples································································································13-4 IPv4 Policy Routing Configuration Example··················································································13-4 IPv6 Policy Routing Configuration Example··················································································13-5...

  • Page 18: Ip Routing Basics Configuration

    IP Routing Basics Configuration This chapter includes these sections: Routing Routing Protocol Overview Configuring a Router ID Displaying and Maintaining a Routing Table The term router in this document refers to both routers and Layer 3 switches. 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, which forwards the packet to the intended destination host.
  • Page 19 A local routing table stores the routes found by all protocols and determines the optimal routes that the router will deliver to the FIB table to guide packet forwarding. The selection of an optimal route is based on the preferences of routing protocols and metrics of routes. Contents of a routing table A routing table includes the following key items: Destination address: Destination IP address or destination network.

  • Page 20: Routing Protocol Overview

    Figure 1-1 A sample routing table Router A Router F 17.0.0.1 17.0.0.0 17.0.0.3 16.0.0.2 11.0.0.2 17.0.0.2 Router D 16.0.0.0 11.0.0.0 14.0.0.3 11.0.0.1 16.0.0.1 14.0.0.2 14.0.0.4 Router B Router G 14.0.0.0 15.0.0.2 12.0.0.1 14.0.0.1 Router E 12.0.0.0 15.0.0.0 13.0.0.2 15.0.0.1 12.0.0.2 13.0.0.3 13.0.0.1 13.0.0.0...

  • Page 21: Routing Protocols And Routing Priority

    Exterior gateway protocols (EGPs): Work between autonomous systems. The most popular one is BGP. An autonomous system refers to a group of routers that share the same routing policy and work under the same administration. Routing algorithm Distance-vector protocols: RIP and BGP. BGP is also considered a path-vector protocol. Link-state protocols: OSPF and IS-IS.

  • Page 22: Load Balancing And Route Backup

    Routing approach Priority IBGP EBGP UNKNOWN The smaller the priority value, the higher the priority. The priority for a direct route is always 0, which you cannot change. Any other type of routes can have their priorities manually configured. Each static route can be configured with a different priority. IPv4 and IPv6 routes have their own respective routing tables.

  • Page 23: Route Recursion

    Route Recursion The nexthops of some BGP routes (except eBGP routes) and static routes configured with nexthops may not be directly connected. To forward the packets, the outgoing interface to reach the nexthop must be available. Route recursion is used to find the outgoing interface based on the nexthop information of the route.

  • Page 24: Displaying And Maintaining A Routing Table

    Select the router ID configured with the router id command; Select the highest IP address among the IP addresses of loopback interfaces as the router ID: If no loopback interface IP address is available, the highest IP address among the IP addresses of physical interfaces is selected as the router ID (regardless of the interface state).
  • Page 25 To do… Use the command… Remarks reset ip routing-table statistics protocol Clear statistics for the routing table [ vpn-instance vpn-instance-name ] { all | Available in user view or a VPN routing table protocol } Display brief IPv6 routing table display ipv6 routing-table Available in any view information...

  • Page 26: Static Routing Configuration

    Static Routing Configuration This chapter includes these sections: Introduction Configuring a Static Route Configuring BFD for Static Routes Static Route Configuration Example The term router in this document refers to both routers and Layer 3 switches. Introduction Static Route A static route is a manually configured route. If a network’s topology is simple, you only need to configure static routes for the network to work normally.

  • Page 27: Configuring A Static Route

    In the ip route-static command, a specified IPv4 address is in dotted decimal format and a specified mask can be either in dotted decimal format or in the form of mask length (the number of consecutive 1s in the mask). Output interface and next hop While configuring a static route, you can specify the output interface and/or the next hop address depending on the specific occasion.

  • Page 28: Configuring Bfd For Static Routes

    To do… Use the command… Remarks ip route-static dest-address { mask | mask-length } { next-hop-address | interface-type interface-number [ next-hop-address ] | vpn-instance d-vpn-instance-name next-hop-address } track track-entry-number [ preference Required preference-value ] [ tag tag-value ] [ description By default, description-text ] preference for static...

  • Page 29: Bfd Control Packet Mode

    A dynamic routing protocol notifies BFD of its neighbor information. BFD uses such information to establish sessions with neighbors by sending BFD control packets. Static routing, which has no neighbor discovery mechanism, implements BFD as follows: BFD Control Packet Mode To use BFD control packets for bidirectional detection between two devices, you need to enable BFD control packet mode for each device’s static route destined to the peer.

  • Page 30: Configuring Static Route Frr

    To do… Use the command… Remarks ip route-static dest-address { mask | mask-length } interface-type interface-number next-hop-address bfd echo-packet [ preference preference-value ] [ tag tag-value ] [ description description-text ] Enable BFD echo packet Use either ip route-static vpn-instance s-vpn-instance-name&<1-6> mode for static routes command dest-address { mask | mask-length } interface-type...

  • Page 31: Displaying And Maintaining Static Routes

    Configuration prerequisites Configuring static route FRR needs to reference a route policy. You can specify a backup next hop in a route policy by using the apply fast-reroute backup-interface command. For details about the command and routing policy configurations, see Route Policy Configuration in the Layer 3 - IP Routing Configuration Guide.

  • Page 32: Static Route Configuration Example

    Static Route Configuration Example Basic Static Route Configuration Example Network requirements The interface IP addresses and masks of the switches and hosts are shown in the following figure. Configure static routes to enable hosts to communicate with one another. Figure 2-2 Network diagram for static route configuration Configuration procedure Configuring IP addresses for interfaces (omitted) Configuring static routes...
  • Page 33 1.1.2.0/24 Direct 0 1.1.2.3 Vlan300 1.1.2.3/32 Direct 0 127.0.0.1 InLoop0 1.1.4.0/30 Direct 0 1.1.4.1 Vlan500 1.1.4.1/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 # Display the IP routing table of Switch B. [SwitchB] display ip routing-table Routing Tables: Public Destinations : 10 Routes : 10...

  • Page 34: Static Route Bfd Configuration Example

    Static Route BFD Configuration Example Network requirements As shown in Figure 2-3: Configure a static route to subnet 120.1.1.0/24 on Switch A and configure a static route to subnet 121.1.1.0/24 on Switch B. Both routes have BFD enabled. Configure static router BFD so that when the link over which Switch A communicates with Switch B through the Layer 2 switch fails, BFD can detect the failure immediately, and then Switch A and Switch B communicate through Switch C.
  • Page 35 [SwitchB] ip route-static 121.1.1.0 24 vlan-interface 13 13.1.1.2 preference 65 [SwitchB] quit Verify the configuration. The following operations are performed on Switch A. The operations on Switch B are similar to those on Switch A, and are thus omitted. <SwitchA> display bfd session Total Session Num: 1 Init Mode: Active Session Working Under Ctrl Mode:...

  • Page 36: Static Route Frr Configuration Example

    Static Routing table Status : < Inactive> Summary Count : 1 Destination/Mask Proto Pre Cost NextHop Interface 120.1.1.0/24 Static 60 12.1.1.2 Vlan10 Static Route FRR Configuration Example Network requirements Switch S, Switch A, and Switch D are interconnected through static routes, as illustrated in Figure 2-4.
  • Page 37 [SwitchS] ip route-static fast-reroute route-policy frr # Configure Switch D. [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 backup-nexthop 24.24.24.2 [SwitchD-route-policy] quit [SwitchD] ip route-static fast-reroute route-policy frr Verify the configuration...

  • Page 38: Rip Configuration

    RIP Configuration The term router in this document refers to both routers and Layer 3 switches. This chapter includes these sections: RIP Overview RIP Configuration Task List Configuring RIP Basic Functions Configuring RIP Route Control Configuring RIP Network Optimization Configuring Static Route FRR Configuring BFD for RIP Displaying and Maintaining RIP RIP Configuration Examples...
  • Page 39 RIP routing table A RIP router has a routing table containing routing entries of all reachable destinations, and each routing entry contains: Destination address: IP address of a host or a network. Next hop: IP address of the adjacent router’s interface to reach the destination. Egress interface: Packet outgoing interface.

  • Page 40: Rip Version

    After receiving such information, the router updates its local routing table, and sends triggered update messages to its neighbors. All routers on the network do the same to keep the latest routing information. By default, a RIP router sends its routing table to neighbors every 30 seconds. RIP ages out routes by adopting an aging mechanism to keep only valid routes.
  • Page 41 Figure 3-1 RIPv1 Message Format Command: Type of message. 1 indicates request, which is used to request all or part of the routing information from the neighbor, and 2 indicates response, which contains all or part of the routing information. A response message consists of up to 25 route entries. Version: Version of RIP, 0x01 for RIPv1.

  • Page 42: Supported Rip Features

    Figure 3-3 RIPv2 Authentication Message Authentication Type: A value of 2 represents plain text authentication, while a value of 3 represents MD5. Authentication: Authentication data, including password information when plain text authentication is adopted or including key ID, MD5 authentication data length and sequence number when MD5 authentication is adopted.

  • Page 43: Rip Configuration Task List

    RFC 2082: RIPv2 MD5 Authentication RFC 2453: RIP Version 2 RIP Configuration Task List Complete the following tasks to configure RIP: Task Remarks Configuring RIP Basic Functions Required Configuring an Additional Routing Metric Optional Configuring RIPv2 Route Summarization Optional Disabling Host Route Reception Optional Configuring RIP Route Advertising a Default Route...

  • Page 44: Configuring Rip Basic Functions

    Configuring RIP Basic Functions Configuration Prerequisites Before configuring RIP basic functions, complete the following tasks. Configure the link layer protocol. Configure an IP address on each interface, and make sure all adjacent routers are reachable to each other. Configuration Procedure Enabling RIP and a RIP interface Follow these steps to enable RIP: To do…...
  • Page 45 To do… Use the command… Remarks Disable an or all interfaces from Optional sending routing updates (the silent-interface { interface-type All interfaces can send routing interfaces can still receive interface-number | all } updates by default. updates) Return to system view —...

  • Page 46: Configuring Rip Route Control

    To do… Use the command… Remarks Optional By default, if an interface has a RIP version specified, the version takes precedence over the global one. If no RIP version is specified Specify a global RIP version version { 1 | 2 } for an interface, the interface can send RIPv1 broadcasts, and receive RIPv1 broadcasts,...

  • Page 47: Configuring An Additional Routing Metric

    Configure RIP basic functions Configuring an Additional Routing Metric An additional routing metric (hop count) can be added to the metric of an inbound or outbound RIP route. The outbound additional metric is added to the metric of a sent route, and the route’s metric in the routing table is not changed.

  • Page 48: Disabling Host Route Reception

    To do… Use the command… Remarks Optional Enabled by default Enable RIPv2 automatic route If the subnet routes in the routing summary summarization table are not consecutive, disable automatic route summarization to avoid black hole routing. Advertising a summary route You can configure RIPv2 to advertise a summary route on the specified interface.

  • Page 49: Advertising A Default Route

    To do… Use the command… Remarks Enter system view system-view — rip [ process-id ] [ vpn-instance Enter RIP view — vpn-instance-name ] Required Disable RIP from receiving host undo host-route routes Enabled by default RIPv2 can be disabled from receiving host routes, but RIPv1 cannot. Advertising a Default Route You can configure RIP to advertise a default route with a specified metric to RIP neighbors.

  • Page 50: Configuring Inbound/Outbound Route Filtering

    To do… Use the command… Remarks Optional rip default-route { { only | By default, a RIP interface can Configure the RIP interface to originate } [ cost cost ] | advertise a default route if the RIP advertise a default route no-originate } process is configured with default route advertisement.

  • Page 51: Configuring A Preference For Rip

    Configuring a Preference for RIP Multiple IGP protocols may run in a router. If you want RIP routes to have a higher preference than those learned by other routing protocols, you can assign RIP a smaller preference value to influence optimal route selection.

  • Page 52: Configuring Rip Network Optimization

    Configuring RIP Network Optimization Complete the following tasks before configuring RIP network optimization: Configure network addresses for interfaces, and make neighboring nodes reachable to each other; Configure RIP basic functions. Configuring RIP Timers You can change the RIP network convergence speed by adjusting RIP timers. Follow these steps to configure RIP timers: To do…...

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

    To do… Use the command… Remarks Enter system view system-view — interface interface-type Enter interface view — interface-number Optional Enable split horizon rip split-horizon Enabled by default Enabling poison reverse The poison reverse function allows an interface to advertise the routes received from it, but the metric of these routes is set to 16, making them unreachable.

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

    This feature does not apply to RIPv2 packets that have no zero fields. Follow these steps to enable zero field check on incoming RIPv1 messages: To do… Use the command… Remarks Enter system view system-view –– rip [ process-id ] [ vpn-instance Enter RIP view ––...

  • Page 55: Specifying A Rip Neighbor

    To do… Use the command… Remarks Enter system view system-view –– interface interface-type Enter interface view –– interface-number rip authentication-mode { md5 { rfc2082 key-string key-id | Configure RIPv2 authentication Required rfc2453 key-string } | simple password } This feature does not apply to RIPv1 because RIPv1 does not support authentication. Although you can specify an authentication mode for RIPv1 in interface view, the configuration does not take effect.

  • Page 56: Configuring Rip-To-Mib Binding

    Configuring RIP-to-MIB Binding This task allows you to enable a specific RIP process to receive SNMP requests. Follow these steps to bind RIP to MIB: To do… Use the command… Remarks Enter system view system-view –– Optional Bind RIP to MIB rip mib-binding process-id By default, MIB is bound to RIP process 1.

  • Page 57: Configuring Bfd For Rip

    When the link in the RIP network below fails, the packets on the path may be discarded, or a routing loop may occur. Then, the traffic will be interrupted until RIP completes routing convergence based on the new network topology. In this case, you can enable RIP fast reroute (FRR) to reduce traffic recovery time.

  • Page 58: Single-Hop Detection In Bfd Echo Packet Mode

    For more information about BFD, see BFD Configuration in the High Availability Configuration Guide. BFD for RIP provides two link detection modes: Single-hop detection in BFD echo packet mode for a directly connected neighbor. In this mode, a BFD session is established only when the neighbor has route information to send. Bidirectional detection in BFD control packet mode for an indirectly connected neighbor.

  • Page 59: Displaying And Maintaining Rip

    To do… Use the command… Remarks Required Enable BFD on the RIP interface rip bfd enable Disabled by default Unidirectional detection in BFD echo packet mode only works for RIP neighbors that are directly connected, namely, one hop away from each other. Using the undo peer command does not remove the neighbor relationship at once and therefore cannot bring down the BFD session at once.
  • Page 60 Figure 3-5 Network diagram for RIP version configuration Configuration procedure Configure an IP address for each interface (Omitted) Configure basic RIP functions # Configure Switch A. [SwitchA] rip [SwitchA-rip-1] network 192.168.1.0 [SwitchA-rip-1] network 172.16.0.0 [SwitchA-rip-1] network 172.17.0.0 # Configure Switch B. [SwitchB] rip [SwitchB-rip-1] network 192.168.1.0 [SwitchB-rip-1] network 10.0.0.0...

  • Page 61: Configuring Rip Route Redistribution

    10.1.1.0/24 192.168.1.2 From the routing table, you can see RIPv2 uses classless subnet mask. Since RIPv1 routing information has a long aging time, it will still exist until it ages out after RIPv2 is configured. Configuring RIP Route Redistribution Network requirements As shown in the following figure: Two RIP processes are running on Switch B, which communicates with Switch A through RIP 100 and with Switch C through RIP 200.
  • Page 62 [SwitchB-rip-100] version 2 [SwitchB-rip-100] undo summary [SwitchB-rip-100] quit [SwitchB] rip 200 [SwitchB-rip-200] network 12.0.0.0 [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...

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

    [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 [SwitchB] rip 200 [SwitchB-rip-200] filter-policy 2000 export rip 100 # Display the routing table of Switch C. [SwitchC] display ip routing-table Routing Tables: Public Destinations : 7 Routes : 7 Destination/Mask Proto Pre Cost NextHop...
  • Page 64 [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 # Configure Switch C. <SwitchC> system-view [SwitchB] rip 1 [SwitchC-rip-1] network 1.0.0.0 [SwitchC-rip-1] version 2 [SwitchC-rip-1] undo summary # Configure Switch D.

  • Page 65: Configuring Rip To Advertise A Summary Route

    1.1.5.0/24, cost 2, nexthop 1.1.1.2 The display shows that there is only one RIP route to network 1.1.5.0/24, with the next hop as Switch B (1.1.1.2) and a cost of 2. Configuring RIP to Advertise a Summary Route Network requirements As shown in the following figure: Switch A and Switch B run OSPF, Switch D runs RIP, and Switch C runs OSPF and RIP.
  • Page 66 [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit Configure RIP basic functions. # Configure Switch C. <SwitchC> system-view [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...

  • Page 67: Rip Frr Configuration Example

    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 3-9.

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

    [SwitchD-route-policy] apply fast-reroute backup-interface vlan-interface backup-nexthop 24.24.24.2 [SwitchD-route-policy] quit [SwitchD] rip 1 [SwitchD-rip-1] fast-reroute route-policy frr [SwitchD-rip-1] quit Verify the configuration # Display route 4.4.4.4/32 on Switch S and you can view the backup next hop information. [SwitchS] display ip routing-table 4.4.4.4 verbose Routing Table : Public Summary Count : 1 Destination: 4.4.4.4/32...
  • Page 69 relationship with Switch C and the route information received from Switch C. Then, Switch A learns the static route sent by Switch C with the outbound interface being the interface connected to Switch B. Network diagram for configuring BFD for RIP (single-hop detection in BFD echo packet mode) Configuration procedure Configure an IP address for each interface (Omitted) Configure RIP basic functions.
  • Page 70 [SwitchA-Vlan-interface100] bfd detect-multiplier 7 [SwitchA-Vlan-interface100] quit [SwitchA] quit Configure a static route on Switch C. [SwitchC] ip route-static 100.1.1.1 24 null 0 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...

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

    # Display the RIP routes of RIP process 1 on Switch A. The RIP route learned from Switch C is no longer existent. <SwitchA> display rip 1 route 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.
  • Page 72 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 an IP address for each interface (Omitted) Configure RIP basic functions and enable static route redistribution into RIP so that Switch A and Switch C have routes to send to each other.
  • Page 73 [SwitchD-rip-1] network 192.168.3.0 [SwitchD-rip-1] network 192.168.4.0 Configure BFD parameters. # Configure Switch A. [SwitchA] bfd session init-mode active [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] bfd min-transmit-interval 500 [SwitchA-Vlan-interface100] bfd min-receive-interval 500 [SwitchA-Vlan-interface100] bfd detect-multiplier 7 [SwitchA-Vlan-interface100] quit # Configure Switch C. [SwitchC] bfd session init-mode active [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] bfd min-transmit-interval 500...
  • Page 74 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 Tag: 0 Destination: 100.1.1.0/24 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...

  • Page 75: Troubleshooting Rip

    Troubleshooting RIP No RIP Updates Received Symptom: No RIP updates are received when the links work well. Analysis: After enabling RIP, you must use the network command to enable corresponding interfaces. Make sure no interfaces are disabled from handling RIP messages. If the peer is configured to send multicast messages, the same should be configured on the local end.

  • Page 76: Ospf Configuration

    OSPF Configuration Open Shortest Path First (OSPF) is a link state interior gateway protocol developed by the OSPF working group of the Internet Engineering Task Force (IETF). At present, OSPF version 2 (RFC 2328) is used. This chapter includes these sections: Introduction to OSPF RIP Configuration Task List Enabling OSPF...

  • Page 77: Basic Concepts

    Fast convergence: Transmits updates instantly after network topology changes for routing information synchronization in the AS. Loop-free: Computes routes with the shortest path first (SPF) algorithm according to collected link states, so no route loops are generated. Area partition: Allows an AS to be split into different areas for ease of management and routing information transmitted between areas is summarized to reduce network bandwidth consumption.

  • Page 78: Ospf Area Partition

    LSAck (link state acknowledgment) packet: Acknowledges received LSU packets. It contains the headers of received LSAs (a packet can acknowledge multiple LSAs). LSA types OSPF sends routing information in LSAs, which, as defined in RFC 2328, have the following types: Router LSA: Type-1 LSA, originated by all routers, flooded throughout a single area only.
  • Page 79 In addition, as the topology of a large network is prone to changes, enormous OSPF packets may be created, reducing bandwidth utilization. Each topology change makes all routers perform route calculation. To solve this problem, OSPF splits an AS into multiple areas, which are identified by area ID. The boundaries between areas are routers rather than links.
  • Page 80 Figure 4-2 Virtual link application 1 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 below. Figure 4-3 Virtual link application 2 The virtual link between the two ABRs acts as a point-to-point connection.
  • Page 81 Virtual links cannot transit (totally) stub areas. 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 82: Router Types

    Compared with an NSSA area, a totally NSSA area does not import inter-area routes. Router Types Classification of Routers The OSPF routers fall into four types according to their positions in the AS: Internal Router All interfaces on an internal router belong to one OSPF area. Area Border Router (ABR) An area border router belongs to more than two areas, one of which must be the backbone area.

  • Page 83: Classification Of Ospf Networks

    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, which has high credibility and whose cost is comparable with the cost of an OSPF internal route.

  • Page 84: Dr And Bdr

    NBMA is the default network type, while P2MP is a conversion from other network types, such as NBMA in general. On NBMA networks, packets are unicast, and neighbors are configured manually on routers. On P2MP networks, packets are multicast. DR and BDR DR/BDR introduction On broadcast or NBMA networks, any two routers exchange routing information with each other.

  • Page 85: Ospf Packet Formats

    Note that: The DR election is available on broadcast, NBMA interfaces rather than P2P, or P2MP interfaces. A DR is an interface of a router and belongs to a single network segment. The router’s other interfaces may be a BDR or DRother. After DR/BDR election and then a new router joins, it cannot become the DR immediately even if it has the highest priority on the network.
  • Page 86 MD5 authentication data is added following an OSPF packet rather than contained in the Authentication field. Hello packet A router sends hello packets periodically to neighbors to find and maintain neighbor relationships and to elect the DR/BDR, including information about values of timers, DR, BDR and neighbors already known.
  • Page 87 LSA). The LSA header occupies small part of an LSA to reduce traffic between routers. The recipient checks whether the LSA is available using the LSA header. The DD packet format: Figure 4-11 DD packet format Version Packet length Router ID Area ID Checksum AuType...
  • Page 88 Figure 4-12 LSR packet format Major fields: LS type: Type number of the LSA to be requested. Type 1 for example indicates the Router LSA. Link State ID: Determined by LSA type. Advertising Router: ID of the router that sent the LSA. LSU packet LSU (Link State Update) packets are used to send the requested LSAs to peers, and each packet carries a collection of LSAs.
  • Page 89 Figure 4-14 LSAck packet format LSA header format All LSAs have the same header, as shown in the following figure. Figure 4-15 LSA header format Major fields: LS age: Time in seconds elapsed since the LSA was originated. A LSA ages in the LSDB (added by 1 per second), but does not in transmission.
  • Page 90 Figure 4-16 Router LSA format Major fields: Link State ID: ID of the router that originated the LSA. V (Virtual Link): Set to 1 if the router that originated the LSA is a virtual link endpoint. E (External): Set to 1 if the router that originated the LSA is an ASBR. B (Border): Set to 1 if the router that originated the LSA is an ABR.
  • Page 91 Figure 4-17 Network LSA format LS age Options Link state ID Advertising router LS sequence number LS checksum Length Network mask Attached router Major fields: Link State ID: The interface address of the DR Network mask: The mask of the network (a broadcast or NBMA network) Attached router: The IDs of the routers, which are adjacent to the DR, including the DR itself Summary LSA Network summary LSAs (Type-3 LSAs) and ASBR summary LSAs (Type-4 LSAs) are originated by...
  • Page 92 A Type-3 LSA can be used to advertise a default route, having the Link State ID and Network Mask set to 0.0.0.0. AS external LSA An AS external LSA originates from an ASBR, describing routing information to a destination outside the AS.

  • Page 93: Supported Ospf Features

    Figure 4-20 NSSA external LSA format Supported OSPF Features Multi-process With multi-process 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.

  • Page 94: Protocols And Standards

    GR Helper: The neighbor of the GR Restarter. It helps the GR Restarter to complete the GR process. After an OSPF GR Restarter restarts, it needs to perform the following two tasks in order to re-synchronize its LSDB with its neighbors. To obtain once again effective OSPF neighbor information (assume the adjacencies are not changed).
  • Page 95 Task Remarks Enabling OSPF Required Configuring a Stub Area Configuring OSPF Areas Configuring an NSSA Area Optional Configuring a Virtual Link Configuring the OSPF Network Type for an Interface as Optional Broadcast Configuring the OSPF Network Type for an Interface as Optional Configuring OSPF NBMA...

  • Page 96: Enabling Ospf

    Task Remarks Making External Route Selection Rules Defined in RFC 1583 Optional Compatible Logging Neighbor State Changes Optional Configuring OSPF Network Management Optional Enabling Message Logging Optional Enabling the Advertisement and Reception of Opaque LSAs Optional Configuring OSPF to Give Priority to Receiving and Optional Processing Hello Packets Configuring the LSU Transmit Rate...

  • Page 97: Configuring Ospf Areas

    The system supports OSPF multi-process and OSPF multi-instance: When a router runs multiple OSPF processes, you need to specify a Router ID for each process, which takes effect locally and has no influence on packet exchange between routers. Therefore, two routers having different process IDs can exchange packets. You can configure an OSPF process to run in a specified VPN instance.

  • Page 98: Prerequisites

    Prerequisites Before configuring an OSPF area, you have configured: IP addresses for interfaces, making neighboring nodes accessible with each other at the network layer. OSPF basic functions. Configuring a Stub Area You can 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.

  • Page 99: Configuring An Nssa Area

    Configuring an NSSA Area A stub area cannot redistribute routes. You can configure the area as an NSSA area to allow for route redistribution while keeping other characteristics of a stub area. Follow these steps to configure an NSSA area: To do…...

  • Page 100: Configuring Ospf Network Types

    To do… Use the command… Remarks Enter area view area area-id — vlink-peer router-id [ hello Required seconds | retransmit seconds | You need to configure this command trans-delay seconds | dead on both ends of a virtual link. Configure a virtual link seconds | simple [ plain | cipher ] Note that hello and dead intervals password | { md5 | hmac-md5 }...

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

    Configuring the OSPF Network Type for an Interface as Broadcast Follow these steps to configure the OSPF network type for an interface as broadcast: To do… Use the command… Remarks — Enter system view system-view interface interface-type — Enter interface view interface-number Required Configure the OSPF network type...

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

    To do… Use the command… Remarks Specify a neighbor and its DR peer ip-address [ cost value | Required priority dr-priority dr-priority ] The DR priority configured with the ospf dr-priority command and the one configured with the peer command have the following differences: The former is for actual DR election.

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

    To do… Use the command… Remarks ospf [ process-id | router-id Enter OSPF view router-id | vpn-instance — instance-name ] * Specify a neighbor and its DR peer ip-address [ cost value | Required if the interface type is priority on a P2MP unicast dr-priority dr-priority ] P2MP unicast network...
  • Page 104 Assume in an area are three internal routes 19.1.1.0/24, 19.1.2.0/24, and 19.1.3.0/24. By configuring route summarization on the ABR, the three routes are summarized into the route 19.1.0.0/16 that is advertised into other areas. Configuring route summarization on an ABR If contiguous network segments are available in the area, you can summarize them into a single network segment.

  • Page 105: Configuring Ospf Inbound Route Filtering

    To do… Use the command… Remarks Required asbr-summary ip-address { mask | Configure ASBR route The command is available on an mask-length } [ tag tag | summarization ASBR only. not-advertise | cost cost ] * Not configured by default. Configuring OSPF Inbound Route Filtering For details about IP prefix list, see Route Policy Configuration in the Layer 3 - IP Routing Configuration Guide.

  • Page 106: Configuring Abr Type-3 Lsa Filtering

    Configuring ABR Type-3 LSA Filtering This task is configured on an ABR to filter Type-3 LSAs to be advertised in the attached non-backbone area and the Type-3 LSAs to be advertised to other areas. Follow these steps to configure Type-3 LSA filtering on an ABR: To do…...

  • Page 107: Configuring The Maximum Number Of Ospf Routes

    To do… Use the command… Remarks — Enter system view system-view ospf [ process-id | router-id router-id | — Enter OSPF view vpn-instance instance-name ] * Optional Configure a bandwidth bandwidth-reference value The value defaults to 100 reference value Mbps. Configuring the Maximum Number of OSPF Routes Follow these steps to configure the maximum number of routes: To do…...

  • Page 108: Configuring A Preference For Ospf

    Configuring a Preference for OSPF A router may run multiple routing protocols, and it sets a preference for each protocol. When a route found by several routing protocols, the route found by the protocol with the highest preference will be selected.
  • Page 109 Only active routes can be redistributed. You can 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. To do so, you need to use the default-route-advertise command.

  • Page 110: Advertising A Host Route

    To do… Use the command… Remarks Optional By default, the default cost Configure the default is 1, default upper limit of parameters for redistributed default { cost cost | limit limit | tag tag | type routes redistributed per routes (cost, route number, tag type } * time is 1000, default tag is and type)

  • Page 111: Configuring Ospf Packet Timers

    Configuring OSPF Packet Timers You can configure the following timers on OSPF interfaces as needed: Hello timer: Interval for sending hello packets. It must be identical on OSPF neighbors. The longer the interval, the lower convergence speed and smaller network load. Poll timer: Interval for sending hello packets to the neighbor that is down on the NBMA network.

  • Page 112: Specifying An Lsa Transmission Delay

    The hello and dead intervals restore to default values after you change the network type for an interface. The dead interval should be at least four times the hello interval on an interface. The poll interval is at least four times the hello interval. The retransmission interval should not be so small for avoidance of unnecessary LSA retransmissions.

  • Page 113: Specifying The Lsa Minimum Repeat Arrival Interval

    With this task configured, when network changes are not frequent, SPF calculation applies at the minimum-interval. If network changes become frequent, SPF calculation interval is incremented by incremental-interval × 2 (n is the number of calculation times) each time a calculation occurs, up to the maximum-interval.

  • Page 114: Disabling Interfaces From Sending Ospf Packets

    To do… Use the command… Remarks Optional lsa-generation-interval By default, the maximum interval is 5 Configure the LSA maximum-interval [ initial-interval seconds, the minimum interval is 0 generation interval [ incremental-interval ] ] milliseconds and the incremental interval is 5000 milliseconds. With this command configured, when network changes are not frequent, LSAs are generated at the minimum-interval.

  • Page 115: Configuring Stub Routers

    Configuring Stub Routers A stub router is used for traffic control. It tells other OSPF routers not to use it to forward data, but they can have a route to it. The Router LSAs from the stub router may contain different link type values. A value of 3 means a link to the stub network, so the cost of the link remains unchanged.

  • Page 116: Adding The Interface Mtu Into Dd Packets

    To do… Use the command… Remarks Required Configure the authentication mode authentication-mode { md5 | simple } Not configured by default. — Exit to OSPF view quit — Exit to system view quit — Enter interface view interface interface-type interface-number Configure the authentication mode ospf authentication-mode simple [ cipher (simple authentication) for the...

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

    To do… Use the command… Remarks Optional Specify the maximum number of lsdb-overflow-limit number Not specified by external LSAs in the LSDB default Making External Route Selection Rules Defined in RFC 1583 Compatible The selection of an external route from multiple LSAs defined in RFC 2328 is different from the one defined in RFC 1583.

  • Page 118: Configuring Ospf Network Management

    Configuring OSPF Network Management After trap generation is enabled for OSPF, OSPF generates traps to report important events. Traps fall into the following levels: Level-3, for fault traps Level-4, for alarm traps Level-5, for normal but important traps Level-6, for notification traps The generated traps are sent to the Information Center of the device.

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

    Enabling the Advertisement and Reception of Opaque LSAs With this feature enabled, the OSPF router can receive and advertise Type 9, Type 10 and Type 11 opaque LSAs. Follow these steps to enable the advertisement and reception of opaque LSAs: To do…...

  • Page 120: Configuring Ospf Frr

    To do… Use the command… Remarks Optional Configure the LSU By default, an OSPF interface transmit-pacing interval interval count count transmit rate sends up to three LSU packets every 20 milliseconds. Configuring OSPF FRR Do not use OSPF FRR and BFD (for OSPF) at the same time; otherwise, OSPF FRR may fail to take effect.

  • Page 121: Configuring Ospf Graceful Restart

    Configure OSPF FRR to automatically calculate a backup next hop Follow these steps to configure automatic OSPF FRR: To do… Use the command… Remarks Enter system view system-view — Required Configure the source address of bfd echo-source-ip ip-address echo packets Not configured by default.

  • Page 122: Configuring The Ospf Gr Restarter

    OSPF GR can be implemented through: IETF standard GR capable routers. The GR restarter communicates with GR helpers by exchanging Type-9 Opaque LSAs called Grace LSAs. Non IETF standard GR capable routers. The GR restarter communicates with GR helpers by exchanging OSPF messages that carry link local signaling (LLS) and out of band re-synchronization (OOB) extension information.

  • Page 123: Configuring The Ospf Gr Helper

    To do… Use the command… Remarks Enable non IETF standard Required Graceful Restart capability for graceful-restart [ nonstandard ] Disabled by default OSPF Optional Configure Graceful Restart interval graceful-restart interval timer for OSPF 120 seconds by default Configuring the OSPF GR Helper You can configure the IETF standard or non IETF standard OSPF GR Helper.

  • Page 124: Triggering Ospf Graceful Restart

    To do… Use the command… Remarks Optional Configure the neighbors for which graceful-restart help The router can server as a GR the router can serve as a GR { acl-number | prefix prefix-list } Helper for any OSPF neighbor by Helper default.

  • Page 125: Configuring Echo Packet Single-Hop Detection

    To do… Use the command… Description Required Not enabled on Enable BFD on the interface ospf bfd enable OSPF interfaces by default One network segment can only belong to one area and you need to specify each OSPF interface to belong to the specific area.

  • Page 126: Displaying And Maintaining Ospf

    Displaying and Maintaining OSPF To do… Use the command… Remarks Display OSPF brief information display ospf [ process-id ] brief Display OSPF statistics display ospf [ process-id ] cumulative display ospf [ process-id ] lsdb [ brief | [ { ase | router | network | summary | asbr | nssa | Display Link State Database opaque-link | opaque-area | opaque-as }...

  • Page 127: Ospf Configuration Examples

    To do… Use the command… Remarks Re-enable OSPF route reset ospf [ process-id ] redistribution redistribution OSPF Configuration Examples These examples only cover commands for OSPF configuration. Configuring OSPF Basic Functions Network requirements As shown in the following figure, all switches run OSPF. The AS is split into three areas, in which, Switch A and Switch B act as ABRs to forward routing information between areas.
  • Page 128 # 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 [SwitchB-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.2] quit [SwitchB-ospf-1] quit # Configure Switch C <SwitchC> system-view [SwitchC] ospf [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] network 10.4.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.1] quit [SwitchC-ospf-1] quit...
  • Page 129 Neighbor is up for 06:03:12 Authentication Sequence: [ 0 ] Neighbor state change count: 5 # Display OSPF routing information on Switch A. [SwitchA] display ospf routing OSPF Process 1 with Router ID 10.2.1.1 Routing Tables Routing for Network Destination Cost Type NextHop...

  • Page 130: Configuring Ospf Route Redistribution

    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 Total Nets: 5 Intra Area: 2 Inter Area: 3 ASE: 0 NSSA: 0 # On Switch D, ping the IP address 10.4.1.1 to check connectivity.

  • Page 131: Configuring Ospf To Advertise A Summary Route

    Configure OSPF to redistribute routes. # On Switch C, configure a static route destined for network 3.1.2.0/24. <SwitchC> system-view [SwitchC] ip route-static 3.1.2.1 24 10.4.1.2 # On Switch C, configure OSPF to redistribute static routes. [SwitchC] ospf 1 [SwitchC-ospf-1] import-route static Verify the configuration.
  • Page 132 Switch B is configured to redistribute BGP routes into OSPF. Switch B is configured with route summarization and advertises only the summary route 10.0.0.0/8 to reduce Switch A's routing table size. Figure 4-24 Network diagram for OSPF summary route advertisement Configuration procedure Configure IP addresses for interfaces (omitted) Configure OSPF basic functions...
  • Page 133 <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 to redistribute OSPF routes and direct routes.

  • Page 134: Configuring An Ospf Stub Area

    [SwitchB-ospf-1] asbr-summary 10.0.0.0 8 # Display the OSPF routing table of Switch A. [SwitchA] display ip routing-table Routing Tables: Public Destinations : 5 Routes : 5 Destination/Mask Proto Pre Cost NextHop Interface 10.0.0.0/8 O_ASE 150 2 11.2.1.1 Vlan100 11.2.1.0/24 Direct 0 11.2.1.2 Vlan100 11.2.1.2/32...
  • Page 135 OSPF Process 1 with Router ID 10.4.1.1 Routing Table to ABR and ASBR Type Destination Area Cost Nexthop RtType Intra 10.2.1.1 0.0.0.1 10.2.1.1 Inter 10.3.1.1 0.0.0.1 10.2.1.1 Inter 10.5.1.1 0.0.0.1 10.2.1.1 ASBR # Display OSPF routing table information on Switch C. <SwitchC>...
  • Page 136 [SwitchC-ospf-1-area-0.0.0.1] quit [SwitchC-ospf-1] quit # Display OSPF routing information on Switch C [SwitchC] display ospf routing OSPF Process 1 with Router ID 10.4.1.1 Routing Tables Routing for Network Destination Cost Type NextHop AdvRouter Area 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...

  • Page 137: Configuring An Ospf Nssa Area

    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 The following figure shows an AS is split into three areas, where all switches run OSPF. Switch A and Switch B act as ABRs to forward routing information between areas.
  • Page 138 If Switch C in the NSSA area wants to obtain routes to other areas within the AS, you need to configure the nssa command with the keyword default-route-advertise on Switch A (an ABR) so that Switch C can obtain a default route. It is recommended to configure the nssa command with the keyword no-summary on Switch A to reduce the routing table size on NSSA switches.

  • Page 139: Configuring Ospf Dr Election

    Intra Area: 2 Inter Area: 3 ASE: 1 NSSA: 0 You can see on Switch D an external route imported from the NSSA area. Configuring OSPF DR Election Network requirements In the following figure, OSPF Switches A, B, C and D reside on the same network segment. It is required to configure Switch A as the DR, and configure Switch C as the BDR.
  • Page 140 [SwitchC] router id 3.3.3.3 [SwitchC] ospf [SwitchC-ospf-1] area 0 [SwitchC-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchC-ospf-1-area-0.0.0.0] quit [SwitchC-ospf-1] quit # Configure Switch D. <SwitchD> system-view [SwitchD] router id 4.4.4.4 [SwitchD] ospf [SwitchD-ospf-1] area 0 [SwitchD-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.0] quit [SwitchD-ospf-1] return # Display OSPF neighbor information on Switch A.
  • Page 141 [SwitchB-Vlan-interface1] ospf dr-priority 0 [SwitchB-Vlan-interface1] quit # Configure Switch C. [SwitchC] interface vlan-interface 1 [SwitchC-Vlan-interface1] ospf dr-priority 2 [SwitchC-Vlan-interface] quit # Display neighbor information on Switch D. <SwitchD> display ospf peer verbose OSPF Process 1 with Router ID 4.4.4.4 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 Address: 192.168.1.1...
  • Page 142 Neighbors Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors Router ID: 1.1.1.1 Address: 192.168.1.1 GR State: Normal State: Full Mode: Nbr is Slave Priority: 100 DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0 Dead timer due in 39 sec Neighbor is up for 00:01:40 Authentication Sequence: [ 0 ] Router ID: 2.2.2.2 Address: 192.168.1.2 GR State: Normal...

  • Page 143: Configuring Ospf Virtual Links

    192.168.1.2 Broadcast DROther 1 192.168.1.1 192.168.1.3 The interface state DROther means the interface is not the DR/BDR. Configuring OSPF Virtual Links Network requirements In the following figure, 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 C.
  • Page 144 [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 [SwitchC–ospf-1-area-0.0.0.2] quit [SwitchC-ospf-1] quit # Configure Switch D. <SwitchD> system-view [SwitchD] ospf 1 router-id 4.4.4.4 [SwitchD-ospf-1] area 2 [SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255 [SwitchD-ospf-1-area-0.0.0.2] quit # Display the OSPF routing table of Switch B.

  • Page 145: Configuring Ospf Graceful Restart

    Routing for Network Destination Cost Type NextHop AdvRouter Area 10.2.1.0/24 Transit 10.2.1.1 3.3.3.3 0.0.0.1 10.3.1.0/24 Inter 10.2.1.2 3.3.3.3 0.0.0.0 10.1.1.0/24 Transit 10.1.1.2 2.2.2.2 0.0.0.0 Total Nets: 3 Intra Area: 2 Inter Area: 1 ASE: 0 NSSA: 0 Switch B has learned the route 10.3.1.0/24 to Area 2. Configuring OSPF Graceful Restart Network requirements As shown in the following figure:...
  • Page 146 [SwitchB-acl-basic-2000] quit [SwitchB] router id 2.2.2.2 [SwitchB] ospf 100 [SwitchB-ospf-100] graceful-restart help 2000 [SwitchB-ospf-100] area 0 [SwitchB-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255 # Configure Switch C <SwitchC> system-view [SwitchC] acl number 2000 [SwitchC-acl-basic-2000] rule 10 permit source 192.1.1.1 0.0.0.0 [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...

  • Page 147: Configuring Route Filtering

    OSPF 1: End Flush Stale ASE + NSSA LSAs Switch A completes GR with the help of Switch B. Configuring Route Filtering Network requirements As shown in the following figure: All the switches in the network run OSPF. The AS is divided into three areas. Switch A and Switch B work as ABRs.
  • Page 148 3.1.1.0/24 O_ASE 150 1 10.2.1.2 Vlan200 3.1.2.0/24 O_ASE 150 1 10.2.1.2 Vlan200 3.1.3.0/24 O_ASE 150 1 10.2.1.2 Vlan200 10.1.1.0/24 Direct 0 10.1.1.1 Vlan200 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...

  • Page 149: Configuring Ospf Frr

    [SwitchA-ospf-1] quit # Display the OSPF routing table of Switch A. [SwitchA] display ip routing-table Routing Tables: Public Destinations : 10 Routes : 10 Destination/Mask Proto Pre Cost NextHop Interface 3.1.1.0/24 O_ASE 150 1 10.2.1.2 Vlan200 3.1.2.0/24 O_ASE 150 1 10.2.1.2 Vlan200 10.1.1.0/24...
  • Page 150 [SwitchS] bfd echo-source-ip 1.1.1.1 [SwitchS] ospf 1 [SwitchS-ospf-1] fast-reroute auto [SwitchS-ospf-1] quit # Configure Switch D. <SwitchD> system-view [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 route policy. # Configure Switch S.

  • Page 151: Configuring Bfd For Ospf

    # Display route 1.1.1.1/32 on Switch D. You can find 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 Process ID: 1 Preference: 10 Cost: 1 NextHop: 13.13.13.1 Interface: Vlan-interface200 BkNextHop: 24.24.24.2...
  • Page 152 [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] network 11.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] network 120.1.1.0 0.0.0.255 [SwitchA-ospf-1-area-0.0.0.0] quit [SwitchA-ospf-1] quit [SwitchA] interface vlan 11 [SwitchA-Vlan-interface11] ospf cost 2 [SwitchA-Vlan-interface11] 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.0.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] network 13.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] network 121.1.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit...
  • Page 153 <SwitchA> display bfd session Total Session Num: 1 Init Mode: Active Session Working Under Ctrl Mode: LD/RD SourceAddr DestAddr State Holdtime Interface 10.1.0.102 10.1.0.100 1700ms vlan10 # Display routes to 120.1.1.0/24 on Switch A, and you can see that Switch A communicates with Switch B through the Layer 2 switch.

  • Page 154: Troubleshooting Ospf Configuration

    *0.50673830 SwitchA BFD/8/SCM:Sess[10.1.0.102/10.1.0.100, vlan10], Oper: application(OSPF) *0.50673831 SwitchA BFD/8/SCM:No application session, delete session[10.1.0.102/10.1.0.100, vlan10] *0.50673831 SwitchA BFD/8/SCM:Sess[10.1.0.102/10.1.0.100, vlan10], Oper: Delete *0.50673832 SwitchA BFD/8/SCM:Delete send-packet timer *0.50673833 SwitchA BFD/8/SCM:Delete session entry *0.50673833 SwitchA BFD/8/SCM:Delete session from IP hash table *0.50673834 SwitchA BFD/8/SCM:Delete session from bfd interface *0.50673834 SwitchA BFD/8/SCM:No session under bfd-int[vlan10] with default configuration, delete bfd-if *0.50673835 SwitchA BFD/8/SCM:Bfd-if[vlan10], Oper: Delete...

  • Page 155: Incorrect Routing Information

    Analysis If the physical link and lower layer protocols work well, check OSPF parameters configured on interfaces. Two neighbors must have the same parameters, such as the area ID, network segment and mask (a P2P or virtual link may have different network segments and masks). Solution Display OSPF neighbor information using the display ospf peer command.

  • Page 156: Is-Is Configuration

    IS-IS Configuration This chapter includes these sections: IS-IS Overview IS-IS Configuration Task List Configuring IS-IS Basic Functions Configuring IS-IS Routing Information Control Tuning and Optimizing IS-IS Networks Configuring IS-IS Authentication Configuring System ID to Host Name Mappings Configuring IS-IS GR Configuring IS-IS FRR Enabling the Logging of Neighbor State Changes Enabling IS-IS SNMP Trap...

  • Page 157: Basic Concepts

    Basic Concepts IS-IS terminology Intermediate system (IS). An IS, similar to a router in TCP/IP, is the basic unit in IS-IS to generate and propagate routing information. In the following text, an IS refers to a router. End system (ES). An ES refers to a host system in TCP/IP. ISO defines the ES-IS protocol for communication between an ES and an IS, and therefore an ES does not participate in the IS-IS processing.

  • Page 158: Is-Is Area

    Generally, a router only needs one area address, and all nodes in the same routing domain must share the same area address. However, a router can have three area addresses at most to support smooth area merging, partitioning and switching. System ID A system ID identifies a host or router uniquely.
  • Page 159 Level-1 and Level-2 Level-1 router A Level-1 router establishes neighbor relationships with Level-1 and Level-1-2 routers in the same area. The LSDB maintained by the Level-1 router contains the local area routing information. It directs the packets destined for an outside area to the nearest Level-1-2 router. Level-2 router A Level-2 router establishes neighbor relationships with the Level-2 and Level-1-2 routers in the same or in different areas.
  • Page 160 Figure 5-2 IS-IS topology Figure 5-3 shows another IS-IS topology. The Level-1-2 routers connect to the Level-1 and Level-2 routers, and form the IS-IS backbone together with the Level-2 routers. There is no area defined as the backbone in this topology. The backbone comprises all contiguous Level-2 and Level-1-2 routers which can reside in different areas.

  • Page 161: Is-Is Network Type

    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. The routing information of a Level-1 area is sent to the Level-2 area through the Level-1-2 router. Therefore, the Level-2 router knows the routing information of the entire IS-IS routing domain but does not share the information of other Level-1 areas and the Level-2 area with the Level-1 area by default.

  • Page 162: Is-Is Pdu Format

    Figure 5-4 DIS in the IS-IS broadcast network The DIS creates and updates pseudonodes as well as generates their LSPs to describe all routers on the network. A pseudonode represents a virtual node on the broadcast network. It is not a real router. In IS-IS, it is identified by the system ID of the DIS and a one-byte Circuit ID (a non zero value).
  • Page 163 Figure 5-6 PDU common header format No. of Octets Intradomain routing protocol discriminator Length indicator Version/Protocol ID extension ID length PDU type Version Reserved Maximum area address Intradomain Routing Protocol Discriminator: Set to 0x83. Length Indicator: Length of the PDU header in bytes, including both common and specific headers.
  • Page 164 LAN IIHs; and the Level-2 routers use the Level-2 LAN IIHs. The P2P IIHs are used on point-to-point networks. Figure 5-7 illustrates the hello packet format in broadcast networks, where the blue fields are the common header. Figure 5-7 L1/L2 LAN IIH format Reserved/Circuit Type: The first 6 bits are reserved with a value of 0.
  • Page 165 Figure 5-8 P2P IIH format Instead of the priority and LAN ID fields in the LAN IIH, the P2P IIH has a Local Circuit ID field. LSP packet format The Link State PDUs (LSP) carry link state information. LSP involves two types: Level-1 LSP and Level-2 LSP.
  • Page 166 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). Sequence Number: LSP sequence number. Checksum: LSP checksum.
  • Page 167 Figure 5-11 L1/L2 CSNP format 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 5-12 shows the PSNP packet format.

  • Page 168: Supported Is-Is Features

    Figure 5-13 CLV format Table 5-2 shows that different PDUs contain different CLVs. Table 5-2 CLV name and the corresponding PDU type CLV Code Name PDU Type Area Addresses IIH, LSP IS Neighbors (LSP) Partition Designated Level2 IS L2 LSP IS Neighbors (MAC Address) LAN IIH IS Neighbors (SNPA Address)
  • Page 169 IS-IS Graceful Restart Graceful Restart ensures the continuity of packet forwarding when a routing protocol restarts or an active/standby switchover occurs: GR Restarter: Graceful restarting router. It must be Graceful Restart capable. GR Helper: The neighbor of the GR Restarter. It helps the GR Restarter to complete the GR process.
  • Page 170 A virtual system is identified by an additional system ID and generates extended LSP fragments. Original LSP It is the LSP generated by the originating system. The system ID in its LSP ID field is the system ID of the originating system. Extended LSP Extended LSPs are generated by virtual systems.

  • Page 171: Protocols And Standards

    For more information about BFD, see BFD Configuration in the High Availability Configuration Guide. Bidirectional forwarding detection (BFD) provides a single mechanism to quickly detect any link failures between IS-IS neighbors to reduce network convergence time. Protocols and Standards ISO 10589 ISO IS-IS Routing Protocol ISO 9542 ES-IS Routing Protocol ISO 8348/Ad2 Network Services Access Points RFC 1195: Use of OSI IS-IS for Routing in TCP/IP and Dual Environments...

  • Page 172: Configuring Is-Is Basic Functions

    Task Remarks Advertising a Default Route Optional Configuring IS-IS Route Redistribution Optional Configuring IS-IS Route Filtering Optional Configuring IS-IS Route Leaking Optional Specifying Intervals for Sending IS-IS Hello and CSNP Packets Optional Specifying the IS-IS Hello Multiplier Optional Configuring a DIS Priority for an Interface Optional Tuning and Disabling an Interface from Sending/Receiving IS-IS Packets...

  • Page 173: Enabling Is

    Configure an IP address for each interface, and make sure all neighboring nodes are reachable to each other at the network layer. Enabling IS-IS Follow these steps to enable IS-IS: To do… Use the command… Remarks Enter system view system-view ––...

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

    To do… Use the command… Remarks interface interface-type Enter interface view –– interface-number Optional isis circuit-level [ level-1 | Specify the circuit level level-1-2 | level-2 ] The default is Level-1-2. Configuring the Network Type of an Interface as P2P Interfaces with different network types operate differently.

  • Page 175: Configuring Is-Is Link Cost

    Configure network layer addresses for interfaces, and make sure adjacent nodes are reachable to each other at the network layer. Enable IS-IS. Configuring IS-IS Link Cost The IS-IS cost of an interface is determined in the following order: ISIS cost specified in interface view. ISIS cost specified in system view.

  • Page 176: Specifying A Preference For Is

    To do… Use the command… Remarks isis [ process-id ] [ vpn-instance Enter IS-IS view — vpn-instance-name ] cost-style { narrow | wide | wide-compatible | Optional Specify an IS-IS cost { compatible | narrow-compatible } style narrow by default [ relax-spf-limit ] } Required Specify a global IS-IS...

  • Page 177: Configuring The Maximum Number Of Equal Cost Routes

    To do… Use the command… Remarks Required preference { route-policy route-policy-name | Specify a preference for IS-IS 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 178: 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 route and thus cannot advertise a default route to other neighbors.

  • Page 179: Configuring Is-Is Route Filtering

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

  • Page 180: Configuring Is-Is Route Leaking

    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. Follow these steps to configure the filtering of redistributed routes: To do…...

  • Page 181: Specifying Intervals For Sending Is-Is Hello And Csnp Packets

    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 Follow these steps to configure intervals for sending IS-IS hello and CSNP packets: To do…...

  • Page 182: Configuring A Dis Priority For An Interface

    On a broadcast link, Level-1 and Level-2 hello packets are advertised separately and therefore you need to set a hello multiplier for each level. On a P2P link, Level-1 and Level-2 hello packets are advertised in P2P hello packets, and you need not specify Level-1 or Level-2. Configuring a DIS Priority for an Interface On an IS-IS broadcast network, a router should be elected as the DIS at a routing level.

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

    Enabling an Interface to Send Small Hello Packets IS-IS messages cannot be fragmented at the IP layer because they are directly encapsulated into frames. Therefore, any two IS-IS neighboring routers need to negotiate a common MTU. To avoid sending big hellos for saving bandwidth, you can enable the interface to send small hello packets without CLVs.
  • Page 184 To do… Use the command… Remarks Enter system view system-view –– isis [ process-id ] [ vpn-instance Enter IS-IS view –– vpn-instance-name ] Optional Specify the LSP refresh timer lsp-refresh seconds 900 seconds by interval default timer lsp-generation maximum-interval Optional Specify the LSP generation [ initial-interval [ second-wait-interval ] ] [ level-1 | interval...
  • Page 185 If the IS-IS routers have different interface MTUs, it is recommended to configure the maximum size of generated LSP packets to be smaller than the smallest interface MTU in this area. Otherwise, the routers have to dynamically adjust the LSP packet size to fit the smallest interface MTU, which takes time and affects other services.
  • Page 186 To do… Use the command… Remarks Required Configure a virtual system ID virtual-system virtual-system-id Not configured by default After LSP fragment extension is enabled for an IS-IS process, the MTUs of all the interfaces running the IS-IS process must not be less than 512; otherwise, LSP fragment extension will not take effect.

  • Page 187: Configuring Spf Parameters

    Before configuring this task, you need to consider redundancy for interfaces to avoid the fact that LSP packets cannot be flooded due to link failures. Follow these steps to add an interface into a mesh group and block an interface: To do…...

  • Page 188: Configuring Is-Is Authentication

    When an IS-IS router cannot record the complete LSDP due to running out of memory or some other reasons, it will calculate wrong routes. To make troubleshooting easier in this case, you can temporarily isolate the router from the IS-IS network by setting the overload bit. Follow these steps to set the LSDB overload bit: To do…...

  • Page 189: Configuring Area Authentication

    The level-1 and level-2 keywords in the isis authentication-mode command are only supported on Ethernet interfaces of routers, and VLAN interfaces and GigabitEthernet interfaces of switches, and the interfaces must be configured with the isis enable command first. Configuring Area Authentication Area authentication enables a router not to install routing information from untrusted routers into the Level-1 LSDB.

  • Page 190: Configuring System Id To Host Name Mappings

    Configuring System ID to Host Name Mappings In IS-IS, a system ID identifies a router or host uniquely. A system ID has a fixed length of 6 bytes. When an administrator needs to view IS-IS neighbor information, routing table or LSDB information, using the system IDs in dotted decimal notation is not convenient.

  • Page 191: Configuring Is-Is

    To do… Use the command... Remarks Required Specify a host name for the is-name sys-name router No specified by default. Return to system view quit –– interface interface-type Enter interface view –– interface-number Optional Not configured by default. This command takes effect only on a Configure a DIS name isis dis-name symbolic-name router with dynamic system ID to host...

  • Page 192: Configuring Is-Is Frr

    Configuring IS-IS FRR Do not use IS-IS FRR and BFD (for IS-IS) at the same time; otherwise, IS-IS FRR may fail to take effect. Introduction When the link in the IS-IS network below fails, the packets on the path may be discarded, or a routing loop may occur.

  • Page 193: Enabling The Logging Of Neighbor State Changes

    To do… Use the command… Remarks Required Configure the source address of bfd echo-source-ip ip-address echo packets Not configured by default. isis [ process-id ] [ vpn-instance Enter IS-IS view — vpn-instance-name ] Required Enable IS-IS FRR to automatically fast-reroute auto calculate a backup next hop Not configured by default.

  • Page 194: Enabling Is-Is Snmp Trap

    With this feature enabled, the router delivers information about neighbor state changes to the terminal for display. Enabling IS-IS SNMP Trap Follow these steps to enable IS-IS SNMP trap: To do… Use the command… Remarks Enter system view system-view –– isis [ process-id ] [ vpn-instance Enter IS-IS view ––...

  • Page 195: Displaying And Maintaining Is

    To do… Use the command… Remarks Required Enable IS-IS on the interface isis enable [ process-id ] Disabled by default Required Enable BFD on the IS-IS interface isis bfd enable Not enabled by default Displaying and Maintaining IS-IS To do… Use the command…...

  • Page 196: Is-Is Configuration Example

    To do… Use the command… Remarks display isis statistics [ level-1 | level-1-2 | Available in any Display IS-IS statistics level-2 ] [ process-id | vpn-instance view vpn-instance-name ] Clear ISIS process data structure reset isis all [ process-id | vpn-instance Available in user information vpn-instance-name ]...
  • Page 197 # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] isis enable 1 [SwitchB-Vlan-interface200] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 100 [SwitchC-Vlan-interface100] isis enable 1 [SwitchC-Vlan-interface100] quit...
  • Page 198 0000.0000.0003.00-00 0x00000009 0xcaa3 1161 1/0/0 0000.0000.0003.01-00 0x00000001 0xadda 1112 0/0/0 *-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload [SwitchB] display isis lsdb Database information for ISIS(1) -------------------------------- Level-1 Link State Database LSPID Seq Num Checksum Holdtime Length ATT/P/OL -------------------------------------------------------------------------- 0000.0000.0001.00-00 0x00000006 0xdb60 0/0/0 0000.0000.0002.00-00* 0x00000008...
  • Page 199 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. Level-1 switches should have a default route with the next hop being the Level-1-2 switch.

  • Page 200: Dis Election Configuration

    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 Vlan100 Direct D/L/- 10.1.2.0/24 NULL Vlan200 Direct D/L/- 172.16.0.0/16 NULL Vlan300 192.168.0.2 R/-/- Flags: D-Direct, R-Added to RM, L-Advertised in LSPs, U-Up/Down Bit Set [SwitchD] display isis route Route information for ISIS(1) -----------------------------...
  • Page 201 Figure 5-17 Network diagram for DIS selection Configuration procedure Configure an IP address for each interface (omitted) 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 202 [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) ---------------------------- System Id: 0000.0000.0002 Interface: Vlan-interface100 Circuit Id: 0000.0000.0003.01 State: Up HoldTime: 21s Type: L1(L1L2) PRI: 64 System Id: 0000.0000.0003...
  • Page 203 By using the default DIS priority, Switch C is the Level-1 DIS, and Switch D is the Level-2 DIS. The pseudonodes of Level-1 and Level-2 are 0000.0000.0003.01 and 0000.0000.0004.01 respectively. Configure the DIS priority of Switch A. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] isis dis-priority 100 [SwitchA-Vlan-interface100] quit # Display IS-IS neighbors of Switch A.

  • Page 204: Configuring Is-Is Route Redistribution

    # Display information about IS-IS neighbors and interfaces of Switch C. [SwitchC] display isis peer Peer information for ISIS(1) ---------------------------- System Id: 0000.0000.0002 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 25s Type: L1 PRI: 64 System Id: 0000.0000.0001 Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01 State: Up HoldTime: 7s...
  • Page 205 Figure 5-18 IS-IS route redistribution Configuration procedure Configure IP addresses for interfaces (omitted) 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 206 [SwitchC-Vlan-interface300] quit # Configure Switch D. <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] is-level level-2 [SwitchD-isis-1] network-entity 20.0000.0000.0004.00 [SwitchD-isis-1] quit [SwitchD] interface interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit # Display IS-IS routing information on each switch. [SwitchA] display isis route Route information for ISIS(1) ----------------------------- ISIS(1) IPv4 Level-1 Forwarding Table...
  • Page 207 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 [SwitchD] display isis route Route information for ISIS(1) ----------------------------- ISIS(1) IPv4 Level-2 Forwarding Table ------------------------------------- IPV4 Destination IntCost...

  • Page 208: Is-Is Graceful Restart Configuration Example

    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 NextHop Flags -------------------------------------------------------------------------- 10.1.1.0/24 NULL VLAN100 Direct D/L/- 10.1.2.0/24 NULL VLAN200...

  • Page 209: Is-Is Frr Configuration Example

    [SwitchA-isis-1] graceful-restart [SwitchA-isis-1] graceful-restart interval 150 [SwitchA-isis-1] return Configurations for Switch B and Switch C are similar and therefore are omitted here. Verify the configuration. After Router A establishes adjacencies with Router B and Router C, they begin to exchange routing information.
  • Page 210 Figure 5-20 Network diagram for IS-IS FRR configuration Switch A Link B Link A Loop 0 Loop 0 1.1.1.1/32 4.4.4.4/32 Vlan-int200 Vlan-int200 13.13.13.1/24 13.13.13.2/24 Switch S Switch D Configuration procedure Configure IP addresses of the interfaces on each switch and configure IS-IS Follow Figure 5-20 to configure the IP address and subnet mask of each interface on the switches.

  • Page 211: Is-Is Authentication Configuration Example

    [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 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 # Display route 4.4.4.4/32 on Switch S and you can view the backup next hop information.
  • Page 212 Figure 5-21 IS-IS authentication configuration Configuration procedure Configure IP addresses for interfaces (Omitted). Configure IS-IS basic functions. # 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 213 <SwitchD> system-view [SwitchD] isis 1 [SwitchD-isis-1] network-entity 20.0000.0000.0001.00 [SwitchD-isis-1] quit [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] isis enable 1 [SwitchD-Vlan-interface300] quit Configure neighbor relationship authentication between neighbors. # Specify the MD5 authentication mode and password eRq on VLAN-interface 100 of Switch A and on VLAN-interface 100 of Switch C.

  • Page 214: Configuring Bfd For Is

    [SwitchD-isis-1] domain-authentication-mode md5 1020Sec Configuring BFD for IS-IS Network requirements As shown in Figure 5-22, IS-IS is enabled on Switch A, Switch B and Switch C that are reachable to each other at the network layer. After the link over which Switch A and Switch B communicate through the Layer-2 switch fails, BFD can quickly detect the failure and notify IS-IS of the failure.
  • Page 215 [SwitchB-Vlan-interface10] isis enable [SwitchB-Vlan-interface10] quit [SwitchB] interface vlan-interface 13 [SwitchB-Vlan-interface13] isis enable [SwitchB-Vlan-interface13] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 11 [SwitchC-Vlan-interface11] isis enable [SwitchC-Vlan-interface11] quit [SwitchC] interface vlan-interface 13 [SwitchC-Vlan-interface13] isis enable [SwitchC-Vlan-interface13] quit Configure BFD parameters.
  • Page 216 Preference: 0 Cost: 2 NextHop: 192.168.0.100 Interface: Vlan-interface10 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 0.0.0.0 Neighbor : 0.0.0.0 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h58m10s Tag: 0 Destination: 120.1.1.0/24 Protocol: ISIS Process ID: 1 Preference: 10 Cost: 4 NextHop: 10.1.1.100 Interface: Vlan-interface11 BkNextHop: 0.0.0.0 BkInterface:...
  • Page 217 # Display route 120.1.1.0/24 on Switch A, and you can see that Switch A and Switch B communicate through Switch C. <SwitchA> display ip routing-table 120.1.1.0 verbose Routing Table : Public Summary Count : 2 Destination: 120.1.1.0/24 Protocol: ISIS Process ID: 1 Preference: 10 Cost: 4 NextHop: 10.1.1.100...

  • Page 218: Bgp Configuration

    BGP Configuration The Border Gateway Protocol (BGP) is a dynamic inter-AS Exterior Gateway Protocol. This chapter includes these sections: BGP Overview BGP Configuration Task List Configuring BGP Basic Functions Controlling Route Generation Controlling Route Distribution and Reception Configuring BGP Route Attributes Tuning and Optimizing BGP Networks Configuring a Large Scale BGP Network Configuring BGP GR...

  • Page 219: Formats Of Bgp Messages

    Reducing bandwidth consumption by advertising only incremental updates and therefore applicable to advertising a great amount of routing information on the Internet Eliminating routing loops completely by adding AS path information to BGP routes Providing abundant policies to implement flexible route filtering and selection Good scalability A router advertising BGP messages is called a BGP speaker.
  • Page 220 Type: This 1-byte unsigned integer indicates the type code of the message. The following type codes are defined: 1–Open, 2-Update, 3-Notification, 4–Keepalive, and 5–Route-refresh. The former four are defined in RFC1771, and the last one is defined in RFC2918. Open After a TCP connection is established, the first message sent by each side is an Open message for peer relationship establishment.
  • Page 221 Unfeasible routes length: The total length of the Withdrawn Routes field in bytes. A value of 0 indicates no route is withdrawn from service, nor is the Withdrawn Routes field present in this Update message. Withdrawn routes: This is a variable length field that contains a list of withdrawn IP prefixes. Total path attribute length: Total length of the Path Attributes field in bytes.

  • Page 222: Bgp Path Attributes

    BGP Path Attributes Classification of path attributes Path attributes fall into four categories: 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 223 AS_PATH is a well-known mandatory attribute. This attribute identifies the autonomous systems through which routing information carried in this Update message has passed. When a route is advertised from the local AS to another AS, each passed AS number is added into the AS_PATH attribute, thus the receiver can determine ASs to route the massage back.
  • Page 224 When advertising a self-originated route to an eBGP peer, a BGP speaker sets the NEXT_HOP for the route to the address of its sending interface. When sending a received route to an eBGP peer, a BGP speaker sets the NEXT_HOP for the route to the address of the sending interface.
  • Page 225 The current implementation supports using the compare-different-as-med command to force BGP to compare MED values of routes received from different ASs. LOCAL_PREF The LOCAL_PREF attribute is exchanged between iBGP peers only, and thus is not advertised to any other AS. It indicates the priority of a BGP router. LOCAL_PREF is used to determine the best route for traffic leaving the local AS.

  • Page 226: Bgp Route Selection

    BGP Route Selection Route selection rules The current BGP implementation supports the following route selection sequence: Discard routes with unreachable NEXT_HOPs first Select the route with the highest Preferred_value Select the route with the highest LOCAL_PREF Select the route originated by the local router Select the route with the shortest AS-PATH Select IGP, EGP, Incomplete routes in turn Select the route with the lowest MED value...
  • Page 227 BGP implements load balancing only on routes that have the same AS_PATH, ORIGIN, LOCAL_PREF and MED. BGP load balancing is applicable between eBGP peers, between iBGP peers and between confederations. If multiple routes to the same destination are available, BGP selects a configurable number of routes for load balancing.

  • Page 228: Ibgp And Igp Synchronization

    A BGP speaker advertises all routes to a newly connected peer. iBGP and IGP Synchronization Routing information synchronization between iBGP and IGP avoids giving wrong directions to routers outside of the local AS. If a non-BGP router works in an AS, it may discard a packet due to an unreachable destination. As shown in Figure 6-11, Router E has learned a route of 8.0.0.0/8 from Router D via BGP.
  • Page 229 When a route flap occurs, the routing protocol sends an update to its neighbor, and then the neighbor needs to recalculate routes and modify the routing table. Therefore, frequent route flaps consume large bandwidth and CPU resources and even affect network normal operation. In most cases, BGP is used in complex networks, where route changes are very frequent.
  • Page 230 Community A peer group makes peers in it enjoy the same policy, while a community makes a group of BGP routers in several ASs enjoy 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 231 Figure 6-14 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 232: Bgp

    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 the above figure, AS 200 is the confederation ID. The deficiency of confederation is: when changing an AS into a confederation, you need to reconfigure your routers, and the topology will be changed.

  • Page 233: Protocols And Standards

    To support more network layer protocols, IETF extended BGP-4 by introducing Multiprotocol Extensions for BGP-4 (MP-BGP) in RFC 4760. Routers supporting MP-BGP can communicate with routers not supporting MP-BGP. MP-BGP extended attributes In BGP-4, the three types of attributes for IPv4 address format, namely NLRI, NEXT_HOP and AGGREGATOR (AGGREGATOR contains the IP address of the speaker generating the summary route) are all carried in updates.

  • Page 234: Bgp Configuration Task List

    RFC5292: Address-Prefix-Based Outbound Route Filter for BGP-4 draft-ietf-idr-restart-08: Graceful Restart Mechanism for BGP BGP Configuration Task List Complete the following tasks to configure BGP: Task Remarks Creating a BGP Connection Required Specifying the Source Interface for TCP Configuring BGP Basic Optional Connections Functions...

  • Page 235: Configuring Bgp Basic Functions

    Task Remarks BGP Networks Configuring the Interval for Sending the Same Optional Update Configuring BGP Soft-Reset Optional Enabling the BGP ORF Capability Optional Enabling Quick eBGP Session Reestablishment Optional Enabling MD5 Authentication for TCP Optional Connections Configuring BGP Load Balancing Optional Forbiding Session Establishment with a Peer or Optional...

  • Page 236: Specifying The Source Interface For Tcp Connections

    To ensure the uniqueness of a router ID and enhance network reliability, you can specify in BGP view the IP address of a local loopback interface as the router ID. 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 Configuration in the Layer 3 - IP Routing Configuration Guide.

  • Page 237: Allowing Establishment Of Ebgp Connection To A Non Directly Connected Peer/Peer Group

    causing network oscillation. Therefore, it is recommended to use a loopback interface as the source interface to enhance stability of BGP connections. Follow these steps to specify the source interface of TCP connections: To do… Use the command… Remarks — Enter system view system-view —...

  • Page 238: Controlling Route Generation

    The peer ebgp-max-hop command needs not be configured if the two eBGP peers are directly connected. Controlling Route Generation Different from IGP, BGP focuses on route generation and advertisement control and optimal route selection. There are to ways to generate BGP routes: Configure BGP to advertise local networks Configure BGP to redistribute routes from other routing protocols, including the default route Prerequisites...

  • Page 239: Enabling Default Route Redistribution Into Bgp

    To do… Use the command… Remarks — Enter BGP view bgp as-number Required import-route protocol { process-id Not enabled by default Enable route redistribution from a | all-processes } [ allow-direct | Currently, the allow-direct routing protocol into BGP med med-value | route-policy keyword is available only when the route-policy-name ] * ] specified routing protocol is OSPF.

  • Page 240: Configuring Bgp Route Summarization

    Configuring BGP Route Summarization To reduce the routing table size on medium and large BGP networks, you need to configure route summarization on BGP routers. BGP supports two summarization modes: automatic and manual. Manual summary routes enjoy a higher priority than automatic ones. Configure automatic route summarization After automatic route summarization is configured, BGP summarizes redistributed IGP subnets to advertise only natural networks.

  • Page 241: Configuring Bgp Route Distribution/Reception Filtering Policies

    To do… Use the command… Remarks — Enter BGP view bgp as-number peer { group-name | ip-address } Required Advertise a default route to a peer default-route-advertise [ route-policy or peer group Not advertised by default route-policy-name ] Configuring BGP Route Distribution/Reception Filtering Policies Prerequisites You need to configure following filters as needed.

  • Page 242: Enabling Bgp And Igp Route Synchronization

    To do… Use the command… Remarks routes passing all the configured Reference an IP prefix list to filer peer { group-name | ip-address } policies, can they be advertised. routing information sent to a ip-prefix ip-prefix-name export peer/peer group Configure BGP route reception filtering policies Only routes permitted by the configured filtering policies can be installed into the local BGP routing table.

  • Page 243: Limiting Prefixes Received From A Peer/Peer Group

    To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number Required Enable synchronization between synchronization BGP and IGP Not enabled by default Limiting Prefixes Received from a Peer/Peer Group Follow these steps to configure the maximum number of prefixes allowed to be received from a peer/peer group: To do…...

  • Page 244: Configuring Bgp Route Dampening

    Configuring BGP Route Dampening By configuring BGP route dampening, you can suppress unstable routes from being added to the local routing table or being advertised to BGP peers. Follow these steps to configure BGP route dampening: To do… Use the command… Remarks —...

  • Page 245: Configuring Preferences For Bgp Routes

    To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number Optional Specify a preferred value for peer { group-name | ip-address } routes received from a peer or The preferred value is 0 by preferred-value value peer group default.

  • Page 246: Configuring The Med Attribute

    Configuring the MED Attribute MED is used to determine the best route for traffic going into an AS. When a BGP router obtains from eBGP peers multiple routes to the same destination but with different next hops, it considers the route with the smallest MED value as the best route if other conditions are the same.
  • Page 247 3.3.3.3 200e When Router D learns network 10.0.0.0 from Router C which has a smaller router ID than Router B, the route from Router C becomes optimal, as shown below. Network NextHop LocPrf PrefVal Path/Ogn *>i 10.0.0.0 1.1.1.1 200e * i 10.0.0.0 2.2.2.2 300e 3.3.3.3...

  • Page 248: Configuring The Next Hop Attribute

    The MED attributes of routes from confederation peers are not compared if their AS-path attributes contain AS numbers that don’t belong to the confederation. For example, there are three routes: AS-path attributes of them are 65006 65009, 65007 65009 and 65008 65009, and MED values of them are 2, 3, and 1.

  • Page 249: Configuring The As-Path Attribute

    Note that: if you have configured BGP load balancing on a BGP router, the router will set it as the next hop for routes sent to an iBGP peer/peer group regardless of whether the peer next-hop-local command is configured. Follow these steps to configure the next hop attribute: To do…...
  • Page 250 To do… Use the command… Remarks Optional Disable BGP from considering AS_PATH By default, BGP considers bestroute as-path-neglect during best route selection AS_PATH during best route selection. Specify a fake AS number for a peer/peer group When Router A in AS 2 is moved to AS 3, you can configure Router A to specify a fake AS number of 2 for created connections to eBGP peers/peer groups.

  • Page 251: Tuning And Optimizing Bgp Networks

    As shown in the above figure, CE 1 and CE 2 use the same AS number of 800. If AS number substitution for CE 2 is configured on PE 2, when PE 2 receives a BGP update sent from CE 1, it replaces AS number 800 as its own AS number 100.

  • Page 252: 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. Follow these steps to configure BGP keepalive interval and holdtime: To do… Use the command… Remarks — Enter system view system-view —...

  • Page 253: Configuring Bgp Soft-Reset

    Configuring BGP Soft-Reset After modifying a route selection policy, you have to reset BGP connections to make the new one take effect, causing short time disconnection. The current BGP implementation supports the route-refresh capability, with which, a router can dynamically refresh its BGP routing table when the route selection policy is modified, without tearing down BGP connections.

  • Page 254: Enabling The Bgp Orf Capability

    To do… Use the command… Remarks Optional peer { group-name | Save all routes from a peer/peer group ip-address } keep-all-routes Not saved by default — Return to user view return refresh bgp { all | ip-address | Perform manual soft reset on BGP group group-name | external | Required connections...

  • Page 255: Enabling Quick Ebgp Session Reestablishment

    To do… Use the command… Remarks peer { group-name | ip-address } Required Enable the ORF capability for a capability-advertise orf ip-prefix BGP peer/peer group Disabled by default. { both | receive | send } Table 6-2 Description of the both, send, and receive parameters and the negotiation result Local parameter Peer parameter Negotiation result...

  • Page 256: Configuring Bgp Load Balancing

    To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number Enable MD5 authentication when peer { group-name | Optional establishing a TCP connection to the ip-address } password { cipher Not enabled by default peer/peer group | simple } password Configuring BGP Load Balancing...

  • Page 257: Configuration Prerequisites

    Configuration Prerequisites Peering nodes are accessible to each other at the network layer. Configuring BGP Peer Groups A peer group is a group of peers with the same route selection policy. In a large scale network, many peers may use the same route selection policy. You can configure a peer group and add these peers into this group.
  • Page 258 To do… Use the command… Remarks — Enter BGP view bgp as-number Create an eBGP peer group group group-name external Required Specify the AS number for the peer group-name as-number Required group as-number peer ip-address group Add the peer into the group Required group-name All the added peers have the same AS number as that of the peer group.

  • Page 259: Configuring Bgp Community

    To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number Create an eBGP peer group group group-name external Required peer ip-address group Add a peer into the group and group-name as-number Required specify its AS number as-number Do not specify any AS number for a peer before adding it into the peer group.

  • Page 260: Configuring A Bgp Route Reflector

    To do… Use the command… Remarks peer/peer group default. Advertise the extended peer { group-name | ip-address } community attribute to a advertise-ext-community peer/peer group Required peer { group-name | ip-address } Apply a routing policy to routes advertised to a route-policy route-policy-name Not configured by peer/peer group...

  • Page 261: Configuring A Bgp Confederation

    In general, it is not required to make clients of a route reflector fully meshed. The route reflector forwards routing information between clients. If clients are fully meshed, you can disable route reflection between clients to reduce routing costs. In general, a cluster has only one route reflector, and the router ID is used to identify the cluster. You can configure multiple route reflectors to improve network stability.

  • Page 262: Configuring Bgp

    Configure confederation compatibility If some other routers in the confederation do not comply with RFC 3065, you need to enable confederation compatibility to allow the router to work with those routers. To do… Use the command… Remarks — Enter system view system-view —...

  • Page 263: Enabling Trap

    Enabling Trap After Trap is enabled for BGP, BGP generates Level-4 traps to report important events of it. The generated traps are sent to the Information Center of the device. 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 264: Displaying And Maintaining Bgp

    To do… Use the command… Remarks Enter BGP view bgp as-number — Required Enable peer ip-address bfd Not enabled for any BGP specified BGP peer peer by default At present, you can configure BFD for IPv4 BGP neighbors only. Before configuring BFD for BGP, you need to enable BGP.

  • Page 265: Resetting Bgp Connections

    To do… Use the command… Remarks Display BGP routing information display bgp routing-table community matching the specified BGP [ aa:nn&<1-13> ] [ no-advertise | no-export | community no-export-subconfed ] * [ whole-match ] display bgp routing-table community-list Display routing information { basic-community-list-number [ whole-match ] | matching a BGP community list adv-community-list-number }&<1-16>...

  • Page 266: Clearing Bgp Information

    To do… Use the command… Remarks Reset all iBGP connections reset bgp internal Reset all IPv4 unicast BGP connections reset bgp ipv4 all Clearing BGP Information To do… Use the command… Remarks Clear dampened MBGP routing reset bgp dampening [ ip-address [ mask | information and release suppressed mask-length ] ] routes...
  • Page 267 # Configure Switch B. <SwitchB> system-view [SwitchB] bgp 65009 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 3.3.3.3 as-number 65009 [SwitchB-bgp] peer 3.3.3.3 connect-interface loopback 0 [SwitchB-bgp] quit [SwitchB] ospf 1 [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.1 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] quit # Configure Switch C.
  • Page 268 [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 : 2 Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State 3.3.3.3...

  • Page 269: Bgp And Igp Synchronization Configuration

    # Configure Switch B. [SwitchB] bgp 65009 [SwitchB-bgp] import-route direct # Display the BGP routing table on Switch A. [SwitchA] display bgp routing-table Total Number of Routes: 4 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, ? –...
  • Page 270 that Switch A can access network 9.1.2.0/24 in AS 65009, and Switch C can access network 8.1.1.0/24 in AS 65008. Figure 6-21 Network diagram for BGP and IGP synchronization Configuration procedure Configure IP addresses for interfaces (omitted) Configure OSPF Enable OSPF in AS 65009, so that Switch B can obtain the route to 9.1.2.0/24. # Configure Switch B.
  • Page 271 Configure BGP to redistribute routes from OSPF on Switch B, so that Switch A can obtain the route to 9.1.2.0/24. Configure OSPF to redistribute routes from BGP on Switch B, so that Switch C can obtain the route to 8.1.1.0/24. # Configure BGP to redistribute routes from OSPF on Switch B.

  • Page 272: Bgp Load Balancing Configuration

    [SwitchC] ping -a 9.1.2.1 8.1.1.1 PING 8.1.1.1: 56 data bytes, press CTRL_C to break Reply from 8.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms Reply from 8.1.1.1: bytes=56 Sequence=2 ttl=254 time=2 ms Reply from 8.1.1.1: bytes=56 Sequence=3 ttl=254 time=2 ms 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...
  • Page 273 intranet through Switch C; configure a static route to interface loopback 0 on Switch B (or use another protocol like OSPF) to establish the iBGP connection. # Configure Switch A. <SwitchA> system-view [SwitchA] bgp 65008 [SwitchA-bgp] router-id 1.1.1.1 [SwitchA-bgp] peer 3.1.1.1 as-number 65009 [SwitchA-bgp] peer 3.1.2.1 as-number 65009 [SwitchA-bgp] network 8.1.1.1 24 [SwitchA-bgp] quit...

  • Page 274: Bgp Community Configuration

    Since Switch A has two routes to reach AS 65009, configuring load balancing over the two BGP routes on Switch A can improve link utilization. # Configure Switch A. [SwitchA] bgp 65008 [SwitchA-bgp] balance 2 [SwitchA-bgp] quit Verification # Display the BGP routing table on Switch A. [SwitchA] display bgp routing-table Total Number of Routes: 3 BGP Local router ID is 1.1.1.1...
  • Page 275 # 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. <SwitchB> system-view [SwitchB] bgp 20 [SwitchB-bgp] router-id 2.2.2.2 [SwitchB-bgp] peer 200.1.2.1 as-number 10 [SwitchB-bgp] peer 200.1.3.2 as-number 30 [SwitchB-bgp] quit # Configure Switch C.

  • Page 276: Bgp Route Reflector Configuration

    Switch C learned route 9.1.1.0/24 from Switch B. Configure BGP community # Configure a routing policy. [SwitchA] route-policy comm_policy permit node 0 [SwitchA-route-policy] apply community no-export [SwitchA-route-policy] quit # Apply the routing policy. [SwitchA] bgp 10 [SwitchA-bgp] peer 200.1.2.2 route-policy comm_policy export [SwitchA-bgp] peer 200.1.2.2 advertise-community # Display the routing table on Switch B.
  • Page 277 Figure 6-24 Network diagram for BGP route reflector configuration Configuration procedure Configure IP addresses for interfaces (omitted) Configure BGP connections # Configure Switch A. <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.

  • Page 278: Bgp Confederation Configuration

    [SwitchC-bgp] peer 193.1.1.2 reflect-client [SwitchC-bgp] peer 194.1.1.2 reflect-client [SwitchC-bgp] quit Verify the above configuration # Display the BGP routing table on Switch B. [SwitchB] display bgp routing-table Total Number of Routes: 1 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...
  • Page 279 Figure 6-25 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 280 [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. # Configure Switch A. [SwitchA] bgp 65001 [SwitchA-bgp] peer 10.1.3.2 as-number 65001 [SwitchA-bgp] peer 10.1.3.2 next-hop-local [SwitchA-bgp] peer 10.1.4.2 as-number 65001 [SwitchA-bgp] peer 10.1.4.2 next-hop-local [SwitchA-bgp] quit # Configure Switch D.
  • Page 281 Origin : i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn *>i 9.1.1.0/24 10.1.1.1 (65001) 100i [SwitchB] display bgp routing-table 9.1.1.0 BGP local router ID : 2.2.2.2 Local AS number : 65002 Paths: 1 available, 1 best BGP routing table entry information of 9.1.1.0/24: From : 10.1.1.1 (1.1.1.1)

  • Page 282: Bgp Path Selection Configuration

    Switch B and Switch D are in the same confederation, but belong to different sub ASs. They obtain external route information from Switch A and generate the same BGP route entries; it seems like that they reside in the same AS although they have no direct connection in between. BGP Path Selection Configuration Network requirements In the figure below, all switches run BGP.
  • Page 283 [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 284 [SwitchA] route-policy apply_med_100 permit node 10 [SwitchA-route-policy] if-match acl 2000 [SwitchA-route-policy] apply cost 100 [SwitchA-route-policy] quit # Apply routing policy apply_med_50 to the route advertised to peer 193.1.1.2 (Switch C), and apply_med_100 to the route advertised to peer 192.1.1.2 (Switch B). [SwitchA] bgp 100 [SwitchA-bgp] peer 193.1.1.2 route-policy apply_med_50 export [SwitchA-bgp] peer 192.1.1.2 route-policy apply_med_100 export...

  • Page 285: Configuring Bfd For Bgp

    Origin : i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn *>i 1.0.0.0 193.1.1.1 100i 192.1.1.1 100i You can find route 1.0.0.0/8 from Switch D to Switch C is the optimal. Configuring BFD for BGP Network requirements As shown in Figure...
  • Page 286 [SwitchA-bgp] quit # When the two links between Switch A and Switch C are both up, Switch C adopts the link Switch A<—>Switch B<—>Switch C to exchange packets with network 1.1.1.0/24. (Set a higher MED value for route 1.1.1.0/24 sent to peer 2.0.2.2 on Switch A.) Create ACL 2000 to permit 1.1.1.0/24 to pass.
  • Page 287 [SwitchA-Vlan-interface100] bfd authentication-mode simple 1 ibgpbfd [SwitchA-Vlan-interface100] quit # Configure Switch C. [SwitchC] bfd session init-mode active [SwitchC] interface vlan-interface 101 [SwitchC-Vlan-interface101] bfd min-transmit-interval 500 [SwitchC-Vlan-interface101] bfd min-receive-interval 500 [SwitchC-Vlan-interface101] bfd detect-multiplier 7 [SwitchC-Vlan-interface101] bfd authentication-mode simple 1 ibgpbfd [SwitchC-Vlan-interface101] return Verify the configuration The following operations are made on Switch C.
  • Page 288 Summary Count : 2 Destination: 1.1.1.0/24 Protocol: BGP Process ID: 0 Preference: 0 Cost: 50 NextHop: 3.0.1.1 Interface: Vlan-interface101 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 3.0.2.1 Neighbor : 3.0.1.1 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h08m54s Tag: 0 Destination: 1.1.1.0/24 Protocol: BGP Process ID: 0 Preference: 0...

  • Page 289: Bgp Gr Configuration

    Preference: 0 Cost: 100 NextHop: 2.0.1.1 Interface: Vlan-interface201 BkNextHop: 0.0.0.0 BkInterface: RelyNextHop: 2.0.2.1 Neighbor : 2.0.1.1 Tunnel ID: 0x0 Label: NULL State: Active Adv Age: 00h09m54s Tag: 0 The above output shows that Switch C has one route to reach network 1.1.1.0/24, that is, Switch C<—>Switch D<—>Switch A.

  • Page 290: Troubleshooting Bgp

    You can ping Switch C from Switch A during the whole switchover process. The S5800 series switches are centralized devices that support IRF. They can act as a GR Helper before forming an IRF; they can form a distributed chassis switch in a logical sense and act as a GR Restarter after forming an IRF.
  • Page 291 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 292: Ipv6 Static Routing Configuration

    IPv6 Static Routing Configuration This chapter includes these sections: Introduction to IPv6 Static Routing Displaying and Maintaining IPv6 Static Routes IPv6 Static Routing Configuration Example The term router in this document refers to both routers and Layer 3 switches. Introduction to IPv6 Static Routing Static routes are manually configured by network administrators.

  • Page 293: Configuration Procedure

    Enabling IPv6 packet forwarding Ensuring that neighboring nodes can reach each other Configuration procedure Follow these steps to configure an IPv6 static route: To do… Use the commands… Remarks — Enter system view system-view ipv6 route-static ipv6-address prefix-length Configure an IPv6 static route with [ interface-type interface-number ] the output interface being a nexthop-address [ preference...

  • Page 294: Ipv6 Static Routing Configuration Example

    Using the undo ipv6 route-static command can delete a single IPv6 static route, while using the delete ipv6 static-routes all command deletes all IPv6 static routes including the default route. For more information about the display ipv6 routing-table protocol static [ inactive | verbose ] command, see IP Routing Basics Configuration Commands in the Layer 3 - IP Routing Command Reference.
  • Page 295 # Display the IPv6 routing table of SwitchA. [SwitchA] display ipv6 routing-table 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...

  • Page 296: Ripng Configuration

    RIPng Configuration This chapter includes these sections: Introduction to RIPng Configuring RIPng Basic Functions Configuring RIPng Route Control Tuning and Optimizing the RIPng Network Displaying and Maintaining RIPng RIPng Configuration Example The term router in this document refers to both routers and Layer 3 switches. Introduction to RIPng RIP next generation (RIPng) is an extension of RIP-2 for IPv4.

  • Page 297: Ripng Packet Format

    Each RIPng router maintains a routing database, including route entries of all reachable destinations. A route entry contains the following information: Destination address: IPv6 address of a host or a network. Next hop address: IPv6 address of a neighbor along the path to the destination. Egress interface: Outbound interface that forwards IPv6 packets.

  • Page 298: Ripng Packet Processing Procedure

    IPv6 next hop address is the IPv6 address of the next hop. Figure 8-3 shows the format of the IPv6 prefix RTE. Figure 8-3 IPv6 prefix RTE format IPv6 prefix (16 octets) Route tag Prefix length Metric IPv6 prefix: Destination IPv6 address prefix. Route tag: Route tag.

  • Page 299: Configuration Prerequisites

    Configuration Prerequisites Before the configuration, accomplish the following tasks first: Enable IPv6 packet forwarding. Configure an IP address for each interface, and make sure all nodes are reachable to one another. Configuration Procedure Follow these steps to configure the basic RIPng functions: To do…...

  • Page 300: Configuring An Additional Routing Metric

    Define an IPv6 address prefix list before using it for route filtering. See Route Policy Configuration in the Layer 3 - IP Routing Configuration Guide. Configuring an Additional Routing Metric An additional routing metric can be added to the metric of an inbound or outbound RIP route, namely, the inbound and outbound additional metric.

  • Page 301: Configuring A Ripng Route Filtering Policy

    To do… Use the command… Remarks Required ripng default-route { only | Advertise a default route originate } [ cost cost ] Not advertised by default With this feature enabled, a default route is advertised through the specified interface regardless of whether the default route is available in the local IPv6 routing table.

  • Page 302: Configuring Ripng Route Redistribution

    To do… Use the command… Remarks Optional preference [ route-policy Configure a RIPng preference By default, the RIPng preference is route-policy-name ] preference 100. Configuring RIPng Route Redistribution Follow these steps to configure RIPng route redistribution: To do… Use the command… Remarks Enter system view system-view...

  • Page 303: Configuring Split Horizon And Poison Reverse

    To do… Use the command… Remarks Enter system view system-view — Enter RIPng view ripng [ process-id ] — Optional. timers { garbage-collect The RIPng timers have the following defaults: garbage-collect-value | 30 seconds for the update timer Configure RIPng timers suppress suppress-value | 180 seconds for the timeout timer timeout timeout-value | update...

  • Page 304: Configuring Zero Field Check On Ripng Packets

    Generally, you are recommended to enable split horizon to prevent routing loops. Configuring the poison reverse function The poison reverse function enables a route learned from an interface to be advertised through the interface. However, the metric of the route is set to 16. That is to say, the route is unreachable. Follow these steps to configure poison reverse: To do…...

  • Page 305: Displaying And Maintaining Ripng

    To do… Use the command… Remarks Configure the maximum number of Optional maximum load-balancing equal cost RIPng routes for load number The number defaults to 8. balancing Displaying and Maintaining RIPng To do… Use the command… Remarks Display configuration information display ripng [ process-id ] Available in any view of a RIPng process...
  • Page 306 # Configure Switch A. <SwitchA> system-view [SwitchA] ripng 1 [SwitchA-ripng-1] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ripng 1 enable [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 400 [SwitchA-Vlan-interface400] ripng 1 enable [SwitchA-Vlan-interface400] quit # Configure Switch B. <SwitchB> system-view [SwitchB] ripng 1 [SwitchB-ripng-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ripng 1 enable...
  • Page 307 via FE80::20F:E2FF:FE00:100, cost 1, tag 0, A, 11 Sec # Display the routing table of Switch A. [SwitchA] display ripng 1 route Route Flags: A - Aging, S - Suppressed, G - Garbage-collect ---------------------------------------------------------------- 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...

  • Page 308: Configuring Ripng Route Redistribution

    Configuring RIPng Route Redistribution Network requirements Two RIPng processes are running on Switch B, which communicates with Switch A through RIPng 100 and with Switch C through RIPng 200. Configure route redistribution on Switch B, letting the two RIPng processes redistribute routes from each other.
  • Page 309 [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ripng 200 enable [SwitchC-Vlan-interface400] quit # Display the routing table of Switch A. [SwitchA] display ipv6 routing-table Routing Table : Destinations : 6 Routes : 6 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64...
  • Page 310 NextHop : 1::1 Preference: 0 Interface : Vlan100 Cost Destination: 1::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2::/64 Protocol : Direct NextHop : 2::1 Preference: 0 Interface : Vlan200 Cost Destination: 2::1/128 Protocol : Direct NextHop : ::1 Preference: 0...

  • Page 311: Ospfv3 Configuration

    OSPFv3 Configuration The term router in this document refers to both routers and Layer 3 switches. This chapter includes these sections: Introduction to OSPFv3 IPv6 OSPFv3 Configuration Task List Enabling OSPFv3 Configuring OSPFv3 Area Parameters Configuring OSPFv3 Network Types Configuring OSPFv3 Routing Information Control Tuning and Optimizing OSPFv3 Networks Configuring OSPFv3 GR Displaying and Maintaining OSPFv3...

  • Page 312: Ospfv3 Packets

    OSPFv3 Packets OSPFv3 has also five types of packets: hello, DD, LSR, LSU, and LSAck. The five packets have the same packet header, which different from the OSPFv2 packet header is only 16 bytes in length, has no authentication field, but is added with an Instance ID field to support multi-instance per link.

  • Page 313: Timers Of Ospfv3

    Intra-Area-Prefix-LSA: Each Intra-Area-Prefix-LSA contains IPv6 prefix information on a router, stub area or transit area information, and has area flooding scope. It was introduced because Router-LSAs and Network-LSAs contain no address information now. RFC 5187 defines the Type 11 LSA, Grace-LSA. A Grace-LSA is generated by a GR (Graceful Restart) Restarter at reboot and transmitted on the local link.

  • Page 314: Protocols And Standards

    Protocols and Standards RFC 2740: OSPF for IPv6 RFC 2328: OSPF Version 2 RFC 5187: OSPFv3 Graceful Restart IPv6 OSPFv3 Configuration Task List Complete the following tasks to configure OSPFv3: Task Remarks Enabling OSPFv3 Required Configuring an OSPFv3 Stub Area Optional Configuring OSPFv3 Area Parameters...

  • Page 315: Enabling Ospfv3

    Enabling OSPFv3 Prerequisites Make neighboring nodes accessible with each other at the network layer. Enable IPv6 packet forwarding Enabling OSPFv3 To enable an OSPFv3 process on a router, you need to 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.

  • Page 316: Prerequisites

    Prerequisites Enable IPv6 packet forwarding Configure OSPFv3 basic functions Configuring an OSPFv3 Stub Area Follow these steps to configure an OSPFv3 stub area: To do… Use the command… Remarks — Enter system view system-view — Enter OSPFv3 view ospfv3 [ process-id ] —...

  • Page 317: Configuring Ospfv3 Network Types

    To do… Use the command… Remarks vlink-peer router-id [ hello seconds | retransmit Configure a virtual link seconds | trans-delay seconds | dead seconds | Required instance instance-id ] * Both ends of a virtual link are ABRs that must be configured with the vlink-peer command. Do not configure virtual links in the areas of a GR-capable process.

  • Page 318: Configuring An Nbma Or P2Mp Neighbor

    To do… Use the command… Remarks Optional ospfv3 network-type Configure a network type for the { broadcast | nbma | p2mp The network type of an interface OSPFv3 interface [ non-broadcast ] | p2p } depends on the media type of the [ instance instance-id ] interface.

  • Page 319: Configuring Ospfv3 Inbound Route Filtering

    To do… Use the command… Remarks — Enter OSPFv3 view ospfv3 [ process-id ] — Enter OSPFv3 area view area area-id Required abr-summary ipv6-address Configure a summary route prefix-length [ not-advertise ] Not configured by default The abr-summary command takes effect on ABRs only. Configuring OSPFv3 Inbound Route Filtering You can configure OSPFv3 to filter routes that are computed from received LSAs according to some rules.

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

    If the cost value is not configured for an interface, OSPFv3 computes the interface cost value automatically Follow these steps to configure an OSPFv3 cost for an interface: To do… Use the command… Remarks — Enter system view system-view interface interface-type —...

  • Page 321: Configuring A Preference For Ospfv3

    Configuring a Preference for OSPFv3 A router may run multiple routing protocols. The system assigns a preference for each protocol. When these routing protocols find the same route, the route found by the protocol with the highest preference is selected. Follow these steps to configure a preference for OSPFv3: To do…...

  • Page 322: Tuning And Optimizing Ospfv3 Networks

    Executing the import-route or default-route-advertise command on a router makes it become an ASBR. You can only inject and advertise a default route using the default-route-advertise command. Since OSPFv3 is a link state routing protocol, it cannot directly filter LSAs to be advertised. Therefore, you need to filter redistributed routes first, and thus only routes that are not filtered out can be advertised in LSAs into the routing domain.

  • Page 323: Configuring A Dr Priority For An Interface

    To do… Use the command… Remarks Optional ospfv3 timer poll seconds Specify the poll interval The poll interval defaults to 120 [ instance instance-id ] seconds. Optional ospfv3 timer dead seconds Configure the dead interval Defaults to 40 seconds on P2P, [ instance instance-id ] broadcast interfaces.

  • Page 324: Ignoring Mtu Check For Dd Packets

    The DR priority of an interface determines the interface’s qualification in DR election. Interfaces having the priority 0 cannot become a DR or BDR. Ignoring MTU Check for DD Packets When LSAs are few in DD packets, it is unnecessary to check the MTU in DD packets in order to improve efficiency.

  • Page 325: Enable The Logging Of Neighbor State Changes

    You cannot configure OSPFv3 GR after configuring OSPFv3 virtual links, because they are not supported at the same time. The S5800 series switches are centralized devices that support IRF. They can act as a GR Helper before forming an IRF virtual device. They can form a distributed chassis switch in a logical sense and act as a GR Restarter after forming an IRF virtual device.

  • Page 326: Configuring Gr Helper

    To do… Use the command… Remarks Enter system view system-view — Enter OSPFv3 view ospfv3 [ process-id ] — Required Enable the GR capability graceful-restart enable Disabled by default. Optional graceful-restart interval Configure the GR interval interval-value 120 seconds by default. Configuring GR Helper You can configure the GR Helper capability on a GR Helper.

  • Page 327: Ospfv3 Configuration Examples

    To do… Use the command… Remarks Display OSPFv3 LSDB statistics display ospfv3 lsdb statistic display ospfv3 [ process-id ] [ area area-id ] peer Display OSPFv3 neighbor [ [ interface-type interface-number ] [ verbose ] | information peer-router-id ] Display OSPFv3 neighbor statistics display ospfv3 peer statistic display ospfv3 [ process-id ] routing [ ipv6-address Display OSPFv3 routing table...
  • Page 328 Figure 9-2 Network diagram for OSPFv3 area configuration Configuration procedure Configure IPv6 addresses for interfaces (omitted) 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...
  • Page 329 [SwitchC-Vlan-interface100] quit [SwitchC] interface vlan-interface 400 [SwitchC-Vlan-interface400] ospfv3 1 area 2 [SwitchC-Vlan-interface400] quit # 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) ----------------------------------------------------------------------...
  • Page 330 NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 *Destination: 2001:2::/64 Type Cost NextHop : directly-connected Interface: Vlan400 *Destination: 2001:3::/64 Type : IA Cost NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400 Configure Area 2 as a stub area # Configure Switch D [SwitchD] ospfv3 [SwitchD-ospfv3-1] area 2 [SwitchD-ospfv3-1-area-0.0.0.2] stub # Configure Switch C, and specify the cost of the default route sent to the stub area as 10.

  • Page 331: Configuring Ospfv3 Dr Election

    # Display OSPFv3 routing table information on Switch D. You can find route entries are reduced. All non-direct routes are removed except the default route. [SwitchD] display ospfv3 routing E1 - Type 1 external route, IA - Inter area route, I - Intra area route E2 - Type 2 external route, * - Seleted route...
  • Page 332 [SwitchA-Vlan-interface100] ospfv3 1 area 0 [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 200 [SwitchB-Vlan-interface200] ospfv3 1 area 0 [SwitchB-Vlan-interface200] quit # Configure Switch C. <SwitchC> system-view [SwitchC] ipv6 [SwitchC] ospfv3 [SwitchC-ospfv3-1] router-id 3.3.3.3 [SwitchC-ospfv3-1] quit...
  • Page 333 [SwitchA] interface Vlan-interface 100 [SwitchA-Vlan-interface100] ospfv3 dr-priority 100 [SwitchA-Vlan-interface100] quit # Configure the DR priority of VLAN-interface 200 as 0 on Switch B. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] ospfv3 dr-priority 0 [SwitchB-Vlan-interface200] quit # Configure the DR priority of VLAN-interface 100 of Switch C as 2. [SwitchC] interface Vlan-interface 100 [SwitchC-Vlan-interface100] ospfv3 dr-priority 2 [SwitchC-Vlan-interface100] quit...

  • Page 334: Configuring Ospfv3 Route Redistribution

    Configuring OSPFv3 Route Redistribution Network requirements Switch A, Switch B, and Switch C are in Area 2. OSPFv3 process 1 and OSPFv3 process 2 are enabled on Switch B. Switch B communicates with Switch A and Switch C through OSPFv3 process 1 and OSPFv3 process 2 respectively. Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on Switch B and set the default metric for redistributed routes to 3.
  • Page 335 [SwitchB-ospfv3-2] quit [SwitchB] interface vlan-interface 300 [SwitchB-Vlan-interface300] ospfv3 2 area 2 [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...

  • Page 336: Configuring Ospfv3

    [SwitchB-ospfv3-2] import-route direct [SwitchB-ospfv3-2] quit # Display the routing table of Switch C. [SwitchC] display ipv6 routing-table Routing Table : Destinations : 8 Routes : 8 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64 Protocol : OSPFv3 NextHop...
  • Page 337 Figure 9-5 Network diagram for OSPFv3 GR configuration Configuration procedure Configure IPv6 addresses for interfaces (omitted). Configure OSPFv3 basic functions # On Switch A, enable OSPFv3 process 1, enable GR and set the router ID to 1.1.1.1. <SwitchA> system-view [SwitchA] ipv6 [SwitchA] ospfv3 1 [SwitchA-ospfv3-1] router-id 1.1.1.1 [SwitchA-ospfv3-1] graceful-restart enable...

  • Page 338: Troubleshooting Ospfv3 Configuration

    The S5800 series switches are centralized devices that support IRF. They can act as a GR Helper before forming an IRF; they can form a distributed chassis switch in a logical sense and act as a GR Restarter after forming an IRF. Active and standby switchover in this document refers to the switching of the master for IRF devices.
  • Page 339 Display information about area configuration using the display current-configuration configuration command. If more than two areas are configured, at least one area is connected to the backbone. In a Stub area, all routers are configured with the stub command. If a virtual link is configured, use the display ospf vlink command to check the neighbor state. 9-29...

  • Page 340: Ipv6 Is-Is Configuration

    IPv6 IS-IS Configuration IPv6 IS-IS supports all the features of IPv4 IS-IS except that it advertises IPv6 routing information instead. This document describes only IPv6 IS-IS exclusive configuration tasks. For other configuration tasks, see IS-IS Configuration in the Layer 3 - IP Routing Configuration Guide. The term router in this document refers to both routers and Layer 3 switches.

  • Page 341: Configuring Ipv6 Is-Is Basic Functions

    Configuring IPv6 IS-IS Basic Functions You can implement IPv6 inter-networking through configuring IPv6 IS-IS in IPv6 network environment. Configuration Prerequisites Before the configuration, accomplish the following tasks first: Enable IPv6 globally Configure IP addresses for interfaces, and make sure all neighboring nodes are reachable. Enable IS-IS Configuration Procedure Follow these steps to configure the basic functions of IPv6 IS-IS:...

  • Page 342: Configuration Procedure

    Configuration Procedure Follow these steps to configure IPv6 IS-IS routing information control: To do… Use command to… Remarks Enter system view system-view –– Enter IS-IS view isis [ process-id ] –– Optional Specify the preference for IPv6 ipv6 preference { route-policy IS-IS routes route-policy-name | preference } * 15 by default...

  • Page 343: Displaying And Maintaining Ipv6 Is

    The ipv6 filter-policy export command is usually used in combination with the ipv6 import-route command. If no protocol is specified for the ipv6 filter-policy export command, routes redistributed from all routing protocols are filtered before advertisement. If a protocol is specified, only routes redistributed from the routing protocol are filtered for advertisement.

  • Page 344: Ipv6 Is-Is Configuration Example

    To do… Use the command… Remarks display isis statistics [ level-1 | level-1-2 | Display the statistics of the IS-IS level-2 ] [ process-id | vpn-instance Available in any view process vpn-instance-name ] Clear all IS-IS data structure reset isis all [ process-id | vpn-instance Available in user view information vpn-instance-name ]...
  • Page 345 [SwitchA-Vlan-interface100] quit # Configure Switch B. <SwitchB> system-view [SwitchB] isis 1 [SwitchB-isis-1] is-level level-1 [SwitchB-isis-1] network-entity 10.0000.0000.0002.00 [SwitchB-isis-1] ipv6 enable [SwitchB-isis-1] quit [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] isis ipv6 enable 1 [SwitchB-Vlan-interface200] quit # Configure Switch C. <SwitchC> system-view [SwitchC] isis 1 [SwitchC-isis-1] network-entity 10.0000.0000.0003.00 [SwitchC-isis-1] ipv6 enable [SwitchC-isis-1] quit...

  • Page 346: Ipv6 Bgp Configuration

    IPv6 BGP Configuration This chapter describes only configuration for IPv6 BGP. For BGP related information, see BGP Configuration in the Layer 3 - IP Routing Configuration Guide. The term router in this document refers to both routers and Layer 3 switches. This chapter includes these sections: IPv6 BGP Overview Configuration Task List...

  • Page 347: Configuration Task List

    Configuration Task List Complete the following tasks to configure IPv6 BGP: Task Remarks Specifying an IPv6 BGP Peer Required Injecting a Local IPv6 Route Optional Configuring a Preferred Value for Routes from a Optional Peer/Peer Group Specifying the Source Interface for Establishing Optional TCP Connections Configuring IPv6 BGP Basic...

  • Page 348: Configuring Ipv6 Bgp Basic Functions

    Task Remarks Enabling the BGP ORF Capability Optional Configuring the Maximum Number of Optional Load-Balanced Routes Configuring IPv6 BGP Peer Group Optional Configuring a Large Scale Configuring IPv6 BGP Community Optional IPv6 BGP Network Configuring an IPv6 BGP Route Reflector Optional Configuring IPv6 BGP Basic Functions Prerequisites...

  • Page 349: Injecting A Local Ipv6 Route

    Injecting a Local IPv6 Route Follow these steps to configure advertise a local route into the routing table: To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number — Enter IPv6 address family view ipv6-family network ipv6-address Required...

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

    Specifying the Source Interface for Establishing TCP Connections Follow these steps to specify the source interface for establishing TCP connections to a BGP peer or peer group: To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number —...

  • Page 351: Configuring A Description For An Ipv6 Peer/Peer Group

    In general, direct links should be available between eBGP peers. If not, you can use the peer ebgp-max-hop command to establish a multi-hop TCP connection in between. However, you need not use this command for direct eBGP connections with loopback interfaces. Configuring a Description for an IPv6 Peer/Peer Group Follow these steps to configure description for an IPv6 peer/peer group: To do…...

  • Page 352: Controlling Route Distribution And Reception

    To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number Optional Enable logging of peer changes log-peer-change globally Enabled by default. — Enter IPv6 address family view ipv6-family Optional Enable the state change logging peer { ipv6-group-name | for an IPv6 peer or peer group ipv6-address } log-change...

  • Page 353: Configuring Ipv6 Bgp Route Summarization

    To do… Use the command… Remarks Required import-route protocol [ process-id [ med Enable route redistribution from another med-value | route-policy Not enabled by routing protocol route-policy-name ] * ] default. If the default-route imported command is not configured, using the import-route command cannot redistribute any IGP default route.

  • Page 354: Configuring Outbound Route Filtering

    To do… Use the command… Remarks Required peer { ipv6-group-name | ipv6-address } Advertise a default route to an default-route-advertise [ route-policy Not advertised by IPv6 peer/peer group route-policy-name ] default. With the peer default-route-advertise command executed, the local router advertises a default route with itself as the next hop to the specified IPv6 peer/peer group, regardless of whether the default route is available in the routing table.

  • Page 355: Configuring Inbound Route Filtering

    IPv6 BGP advertises routes passing the specified policy to peers. Using the protocol argument can filter only the routes redistributed from the specified protocol. If no protocol is specified, IPv6 BGP filters all routes to be advertised, including redistributed routes and routes imported with the network command.

  • Page 356: Configuring Ipv6 Bgp And Igp Route Synchronization

    Only routes passing the configured filtering can be added into the local IPv6 BGP routing table. Members of a peer group can have different inbound route filtering policies. Configuring IPv6 BGP and IGP Route Synchronization With this feature enabled and when a non-BGP router is responsible for forwarding packets in an AS, IPv6 BGP speakers in the AS cannot advertise routing information to outside ASs unless all routers in the AS know the latest routing information.

  • Page 357: Configuring Ipv6 Bgp Route Attributes

    Configuring IPv6 BGP Route Attributes This section describes how to use IPv6 BGP route attributes to modify BGP routing policy. These attributes are: IPv6 BGP protocol preference Default LOCAL_PREF attribute MED attribute NEXT_HOP attribute AS_PATH attribute Prerequisites Before configuring this task, you have: Enabled IPv6 function Configured IPv6 BGP basic functions Configuring IPv6 BGP Preference and Default LOCAL_PREF and NEXT_HOP...

  • Page 358: Configuring The Med Attribute

    To make sure an iBGP peer can find the correct next hop, you can configure routes advertised to the IPv6 iBGP peer/peer group to use the local router as the next hop. If BGP load balancing is configured, the local router specifies itself as the next hop of routes sent to an IPv6 iBGP peer/peer group regardless of whether the peer next-hop-local command is configured.

  • Page 359: Tuning And Optimizing Ipv6 Bgp Networks

    To do… Use the command… Remarks Allow the local AS number to peer { ipv6-group-name | Optional appear in AS_PATH of routes from ipv6-address } allow-as-loop a peer/peer group and specify the Not allowed by default [ number ] repeat times Optional Specify a fake AS number for an peer { ipv6-group-name |...

  • Page 360: Prerequisites

    If a peer not supporting route-refresh exists in the network, you need to configure the peer keep-all-routes command on the router to save all routes from the peer. When the routing policy is changed, the system will update the IPv6 BGP routing table and apply the new policy. Prerequisites Before configuring IPv6 BGP timers, you need to: Enable IPv6...

  • Page 361: Enabling The Ipv6 Bgp Orf Capability

    To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number Enter IPv6 address family — ipv6-family view Optional peer { ipv6-group-name | ipv6-address } Enable route refresh capability-advertise route-refresh Enabled by default. Perform manual soft-reset Follow these steps to perform manual soft reset: To do…...

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

    After you enable the BGP ORF capability, the local BGP router negotiates the ORF capability with the BGP peer through Open messages (that is, determine whether to carry ORF information in messages, and if yes, whether to carry non-standard ORF information in the packets). After completing the negotiation process and establishing the neighboring relationship, the BGP router and its BGP peer can exchange ORF information through specific route-refresh messages.

  • Page 363: Configuring A Large Scale Ipv6 Bgp Network

    To do… Use the command… Remarks — Enter system view system-view — Enter BGP view bgp as-number — Enter IPv6 address family view ipv6-family Required Configure the maximum number of balance number By default, no load balancing is load balanced routes enabled.
  • Page 364 To do… Use the command… Remarks — Enter BGP view bgp as-number — Enter IPv6 address family view ipv6-family group ipv6-group-name Create an iBGP peer group Required [ internal ] peer ipv6-address group Required Add a peer into the group ipv6-group-name [ as-number Not added by default as-number ]...

  • Page 365: Configuring Ipv6 Bgp Community

    To do… Use the command… Remarks Create an eBGP peer group group ipv6-group-name external Required Required Specify the AS number of an IPv6 peer ipv6-address as-number peer as-number Not specified by default. Required Add the IPv6 peer into the peer peer ipv6-address group group ipv6-group-name...

  • Page 366: Configuring An Ipv6 Bgp Route Reflector

    To do… Use the command… Remarks Apply a routing policy to routes peer { ipv6-group-name | Required advertised to an IPv6 peer/peer ipv6-address } route-policy Not applied by default. group route-policy-name export When configuring IPv6 BGP community, you need to configure a routing policy to define the community attribute, and apply the routing policy to route advertisement.

  • Page 367: Displaying And Maintaining Ipv6 Bgp

    In general, since the route reflector forwards routing information between clients, it is not required to make clients of a route reflector fully meshed. If clients are fully meshed, it is recommended to disable route reflection between clients to reduce routing costs. If a cluster has multiple route reflectors, you need to specify the same cluster ID for these route reflectors to avoid routing loops.

  • Page 368: Resetting Ipv6 Bgp Connections

    To do… Use the command… Remarks Display dampened IPv6 BGP display bgp ipv6 routing-table dampened routing information Display IPv6 BGP dampening display bgp ipv6 routing-table dampening parameter information parameter Display IPv6 BGP routing information originated from display bgp ipv6 routing-table different-origin-as different ASs display bgp ipv6 routing-table flap-info Display IPv6 BGP routing flap...

  • Page 369: Ipv6 Bgp Configuration Examples

    To do… Use the command… Remarks reset bgp ipv6 flap-info Clear IPv6 BGP route flap information [ ipv6-address/prefix-length | as-path-acl as-path-acl-number | regexp as-path-regexp ] IPv6 BGP Configuration Examples Some examples for IPv6 BGP configuration are similar to those of BGP4, so see BGP Configuration in the Layer 3 - IP Routing Configuration Guide for related information.
  • Page 370 [SwitchB-bgp] quit # Configure Switch C. <SwitchC> system-view [SwitchC] ipv6 [SwitchC] bgp 65009 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] ipv6-family [SwitchC-bgp-af-ipv6] peer 9:3::1 as-number 65009 [SwitchC-bgp-af-ipv6] peer 9:2::2 as-number 65009 [SwitchC-bgp-af-ipv6] quit [SwitchC-bgp] quit # Configure Switch D. <SwitchD> system-view [SwitchD] ipv6 [SwitchD] bgp 65009 [SwitchD-bgp] router-id 4.4.4.4 [SwitchD-bgp] ipv6-family...

  • Page 371: Ipv6 Bgp Route Reflector Configuration

    BGP local router ID : 3.3.3.3 Local AS number : 65009 Total number of peers : 2 Peers in established state : 2 Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State 9:3::1 65009 0 00:02:18 Established 9:2::2 65009 0 00:01:52 Established Switch A and B has established an eBGP connection;...

  • Page 372: Troubleshooting Ipv6 Bgp Configuration

    [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. <SwitchC> system-view [SwitchC] ipv6 [SwitchC] bgp 200 [SwitchC-bgp] router-id 3.3.3.3 [SwitchC-bgp] ipv6-family [SwitchC-bgp-af-ipv6] peer 101::2 as-number 200 [SwitchC-bgp-af-ipv6] peer 102::2 as-number 200 # Configure Switch D.
  • Page 373 Check whether an ACL for disabling TCP port 179 is configured. 11-28...

  • Page 374: Route Policy Configuration

    Route Policy Configuration Route policies allow a routing protocol to receive, advertise, and redistribute only specific routes, and modify their attributes. This chapter includes these sections: Introduction to Route Policy Route Policy Configuration Task List Defining Filters Configuring a Route Policy Displaying and Maintaining the Route Policy Troubleshooting Route Policy Configuration Route policy in this chapter involves both IPv4 route policy and IPv6 route policy.

  • Page 375: Filters

    Filters There are six types of filters: ACL, IP prefix list, AS path ACL, community list, extended community list and route policy. ACL involves IPv4 ACL and IPv6 ACL. An ACL is configured to match the destinations or next hops of routing information.

  • Page 376: Route Policy Application

    Follow these guidelines for configuring if-match and apply clauses. If you want to implement route filtering only, you do not need to configure apply clauses. If you do not configure any if-match clauses for a permit-mode node, the node permits all routes to pass.
  • Page 377 Follow these steps to define an IPv4 prefix list: To do… Use the command… Remarks — Enter system view system-view ip ip-prefix ip-prefix-name [ index index-number ] Required { deny | permit } ip-address mask-length Define an IPv4 prefix list [ greater-equal min-mask-length ] [ less-equal Not defined by default.

  • Page 378: Defining An As Path List

    If all items are set to the deny mode, no routes can pass the IPv6 prefix list. Therefore, you need to define the permit :: 0 less-equal 128 item following multiple deny items to allow other IPv6 routing information to pass. For example, the following configuration filters routes 2000:1::/48, 2000:2::/48 and 2000:3::/48, but allows other routes to pass.

  • Page 379: Defining An Extended Community List

    Defining an Extended Community List You can define multiple items for an extended community list that is identified by number. During matching, the relation between items is logic OR, that is, if routing information matches one of these items, it passes the extended community list. Follow these steps to define an extended community list: To do…...

  • Page 380: Defining If-Match Clauses

    If a route policy node has the permit keyword specified, routing information matching all the if-match clauses of the node will be handled using the apply clauses of this node, without needing to match against the next node. If routing information does not match the node, it will go to the next node for a match.
  • Page 381 To do… Use the command… Remarks Optional Match BGP routing information whose AS path if-match as-path Not configured by attribute is specified in the AS path list (s) AS-PATH-number&<1-16> default. if-match community Optional Match BGP routing information whose { basic-community-list-number community attribute is specified in the Not configured by [ whole-match ] |...

  • Page 382: Defining Apply Clauses

    The if-match clauses of a route policy node are in logic AND relationship, namely, routing information has to satisfy all its if-match clauses before being executed with its apply clauses. You can specify no or multiple if-match clauses for a route policy node. If no if-match clause is specified, and the route policy node is in permit mode, all routing information can pass the node.
  • Page 383 To do… Use the command… Remarks apply extcommunity { rt Optional Set the extended community { as-number:nn | attribute for BGP routing ip-address:nn } }&<1-16> Not set by default. [ additive ] Optional Not set by default. apply ip-address next-hop for IPv4 routes ip-address The setting does not apply to...

  • Page 384: Displaying And Maintaining The Route Policy

    The difference between IPv4 and IPv6 apply clauses is the command for setting the next hop for routing information. The apply ip-address next-hop and apply ipv6 next-hop commands do not apply to redistributed IPv4 and IPv6 routes respectively. Displaying and Maintaining the Route Policy To do…...
  • Page 385 Figure 12-1 Network diagram for route policy application to route redistribution Configuration procedure Specify IP addresses for interfaces (omitted). Configure IS-IS. # Configure Switch C. <SwitchC> system-view [SwitchC] isis [SwitchC-isis-1] is-level level-2 [SwitchC-isis-1] network-entity 10.0000.0000.0001.00 [SwitchC-isis-1] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] isis enable [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 201...
  • Page 386 [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. [SwitchB] ospf [SwitchB-ospf-1] area 0 [SwitchB-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [SwitchB-ospf-1-area-0.0.0.0] quit [SwitchB-ospf-1] import-route isis 1 [SwitchB-ospf-1] quit # Display the OSPF routing table on Switch A to view redistributed routes.

  • Page 387: Applying A Route Policy To Ipv6 Route Redistribution

    # On Switch B, apply the route policy when redistributing routes. [SwitchB] ospf [SwitchB-ospf-1] import-route isis 1 route-policy isis2ospf [SwitchB-ospf-1] quit # Display the OSPF routing table on Switch A. The cost of route 172.17.1.0/24 is 100, the tag of route 172.17.1.0/24 is 20.
  • Page 388 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ipv6 address 10::1 32 [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] ipv6 address 11::1 32 [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...

  • Page 389: Applying A Route Policy To Filter Received Bgp Routes

    Applying a Route Policy to Filter Received BGP Routes Network requirements As shown in the following figure: All the switches run BGP. Switch C establishes eBGP connections with other switches. Configure a route policy on Switch D to reject routes from AS 200. Figure 12-3 Route policy configuration to filter received BGP routes Swtich A Vlan-int100...
  • Page 390 [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 # On Switch B, inject routes 7.7.7.7/24, 8.8.8.8/24, and 9.9.9.9/24 to BGP. [SwitchB-bgp] network 7.7.7.7 24 [SwitchB-bgp] network 8.8.8.8 24 [SwitchB-bgp] network 9.9.9.9 24...

  • Page 391: Troubleshooting Route Policy Configuration

    Network NextHop LocPrf PrefVal Path/Ogn *> 4.4.4.0/24 1.1.3.1 300 100i *> 5.5.5.0/24 1.1.3.1 300 100i *> 6.6.6.0/24 1.1.3.1 300 100i The display above shows that Switch D has learned only routes 4.4.4.0/24, 5.5.5.0/24, and 6.6.6.0/24 from AS 100. Troubleshooting Route Policy Configuration IPv4 Routing Information Filtering Failure Symptom Filtering routing information failed, while the routing protocol runs normally.

  • Page 392: Policy Routing Configuration

    IP address. The S5820X&S5800 series switches implement policy routing through QoS policies. You can configure traffic classification and traffic redirecting action so that packets matching specific criteria will be forwarded along the specified path.

  • Page 393: Applying The Qos Policy

    To do… Use the command… Remarks Exit class view Quit — Create a behavior and enter traffic behavior behavior-name Required behavior view redirect next-hop { ipv4-add1 Configure a traffic redirect [ ipv4-add2 ] | ipv6-add1 [ interface-type Optional action interface-number ] [ ipv6-add2 [ interface-type interface-number ] ] } Exit behavior view quit...

  • Page 394: Displaying And Maintaining Qos Policies

    To do… Use the command… Remarks qos apply policy policy-name Apply the QoS policy globally Required global inbound Follow these steps to apply the QoS policy to an interface/port group: To do… Use the command… Remarks Enter system view system-view —...

  • Page 395: Policy Routing Configuration Examples

    To do… Use the command… Remarks display qos vlan-policy { name Display VLAN QoS policy policy-name | vlan vlan-id } [ slot information slot-number ] [ inbound ] Display global QoS policy display qos policy global [ slot information slot-number ] [ inbound ] Policy Routing Configuration Examples IPv4 Policy Routing Configuration Example Network requirements...

  • Page 396: Ipv6 Policy Routing Configuration Example

    # Apply QoS policy a to the incoming traffic on GigabitEthernet 1/0/1. [SwitchA] interface gigabitethernet 1/0/1 [SwitchA-GigabitEthernet1/0/1] qos apply policy a inbound Verification After completing the configuration, verify that when Switch A receives packets with destination IP address 201.1.1.2, it forwards the packets to Switch C instead of Switch B. IPv6 Policy Routing Configuration Example Network requirements As shown in...
  • Page 397 Verification After completing the configuration, verify that when Switch A receives packets with destination IP address 201::2, it forwards the packets to Switch C instead of Switch B. 13-6...

  • Page 398: Mce Configuration

    MCE Configuration The term router in this document refers to both routers and Layer 3 switches. This chapter covers information about MCE. For information about routing protocols, see relevant chapters in the Layer 3 - IP Routing Configuration Guide. MCE Overview Introduction to MPLS L3VPN MPLS L3VPN is a kind of PE-based L3VPN technology for service provider VPN solutions.

  • Page 399: Mpls L3Vpn Concepts

    Figure 14-1 Network diagram for MPLS L3VPN model VPN 1 VPN 2 Site 1 Site 3 Site 2 VPN 2 Site 4 VPN 1 CEs and PEs mark the boundary between the service providers and the customers. A CE is usually a router. After a CE establishes adjacency with a directly connected PE, it advertises its VPN routes to the PE and learns remote VPN routes from the PE.
  • Page 400 Address space overlapping Each VPN independently manages the addresses that it uses. The assembly of such addresses for a VPN is called an address space. The address spaces of VPNs may overlap. For example, if both VPN 1 and VPN 2 use the addresses on network segment 10.110.10.0/24, address space overlapping occurs.

  • Page 401: Multi-Vpn-Instance

    An RD can be in one of the following three formats distinguished by the Type field: When the value of the Type field is 0, the Administrator subfield occupies two bytes, the Assigned number subfield occupies four bytes, and the RD format is 16-bit AS number:32-bit user-defined number.

  • Page 402: How Mce Works

    How MCE works The following takes the networking illustrated in Figure 14-3 as an example to introduce how an MCE maintains the routing entries of multiple VPNs and how an MCE exchanges VPN routes with PEs. Figure 14-3 Network diagram for the MCE function VPN 1 VPN 2 Site 1...

  • Page 403: Routing Information Exchange For Mce

    By establishing multiple tunnels between two MCE devices and binding the tunnel interfaces with VPN instances, you can make the routing information and data of the VPN instances delivered to the peer devices through the bound tunnel interfaces. According to the tunnel interfaces receiving the routes, an MCE devices determine the VPN instances that the routes belong to and advertise the routes to the corresponding sites.
  • Page 404 Static route OSPF IS-IS IBGP EBGP This introduces the cooperation of routing protocols and MCE in brief. For details on routing protocols, see relevant chapters in the Layer 3 - IP Routing Configuration Guide. Static routes An MCE can communicate with a site through static routes. As static routes configure for traditional CEs take effect globally, address overlapping between multiple VPNs remains a problem till the emergence of MCE.
  • Page 405 Normally, when an OSPF route is imported to the BGP routing table as a BGP route on a PE, some attributes of the OSPF route get lost. When the BGP route is imported to the OSPF routing table on the remote CE, not all the attributes of the original OSPF routes can be restored.

  • Page 406: Configuring Multi-Vpn-Instance

    Route Exchange between MCE and PE Routing information entries are bound to specific VPN instances on an MCE device, and packets of each VPN instance are forwarded between MCE and PE according to interface. As a result, VPN routing information can be transmitted by performing relatively simple configurations between MCE and PE, such as importing the VPN routing entries on MCE devices to the routing table of the routing protocol running between MCE and PEs.
  • Page 407 To do… Use the command… Remarks Configure a description for the Optional description text VPN instance For easy management, you are recommended to set the same RD for the same VPN instance on the MCE and PE. Associating a VPN Instance with an Interface In an MPLS L3VPN application, you need to associate VPN instances with the interfaces connecting the PEs.
  • Page 408 When a VPN route learned from a site gets redistributed into BGP, BGP associates it with a VPN target extended community attribute list, which is usually the export target attribute of the VPN instance associated with the site. The VPN instance determines which routes it can accept and redistribute according to the import-extcommunity in the VPN target.

  • Page 409: Configuring Route Exchange For Mce

    Only when BGP runs between the MCE and PE, can the VPN target attribute be advertised to the PE along with the routing information. In other cases, configuring this attribute makes no sense. VPN targets configured for a VPN instance on an MCE must be consistent with those configured for the VPN instance on the PE.
  • Page 410 To do… Use the command… Remarks ip route-static vpn-instance s-vpn-instance-name&<1-6> dest-address { mask | mask-length } { gateway-address [ public ] | interface-type interface-number [ gateway-address ] | Required vpn-instance By default, for a static route, the d-vpn-instance-name precedence is 60, the tag is 0, and gateway-address } [ preference no description is configured.
  • Page 411 To do… Use the command… Remarks Required By default, no route of any other protocol is redistributed into RIP. If the RIP process is for an MCE and a site, the routes to be redistributed should be from the routing protocol process Redistribute routes of the routing import-route protocol used for advertising the routes...
  • Page 412 To do… Use the command… Remarks Required Enable the multi-VPN-instance vpn-instance-capability simple function of OSPF Disabled by default Optional 0 by default. This configuration is required on the MCE. On a VPN site, you just domain-id domain-id Configure the OSPF domain ID need to perform the common [ secondary ] OSPF configuration.
  • Page 413 To do… Use the command… Remarks Optional This configuration is used for connecting the PE. By default, the default values of Configure the default values of the the parameters are as follows: parameters for the redistributed default { cost cost | limit limit | tag Cost: 1 routes, including the route cost, tag | type type } *...
  • Page 414 To do… Use the command… Remarks Enter IS-IS view and bind the IS-IS isis [ process-id ] vpn-instance Required process to a VPN instance vpn-instance-name Optional By default, IS-IS does not redistribute routes of any other protocol. If you do not specify the route level in the command, the command will redistribute routes to the level-2 import-route { isis [ process-id ] |...
  • Page 415 VPN, you need to configure the MCE and the egress routers of the sites as a cluster and configure the MCE as the route reflector of the cluster. Table 14-1 Configure the MCE to use IBGP for route exchange with a Site To do…...
  • Page 416 On the egress router of a site, you need to configure the MCE as the IBGP peer. If the routing protocol of the site is not IBGP, you need to redistribute the routes of the routing protocol to IBGP. The configuration required is the same as that of common IBGP.
  • Page 417 To do… Use the command… Remarks Use either command Configure to allow routing loops, that is, to allow the local AS number to appear in the AS_PATH peer { group-name | ip-address } attribute of a received route, and allow-as-loop [ number ] you can also configure the maximum number of times that such case is allowed to appear.

  • Page 418: Displaying And Maintaining Mce

    Normally, BGP checks routing loops by examining AS numbers. If EBGP is used between the MCE and a site, when the MCE advertises its routing information with its AS number to the site and then receives routing update information from the site, the route update message will carry the AS number of the MCE, making the MCE unable to receive this route update message.

  • Page 419: Displaying And Maintaining Mce

    Displaying and Maintaining MCE To do… Use the command… Remarks Display information about the display ip routing-table routing table associated with a vpn-instance vpn-instance-name Available in any view VPN instance [ verbose ] display ip vpn-instance Display information about a [ instance-name Available in any view specified or all VPN instances...
  • Page 420 To do… Use the command… Remarks display bgp vpnv4 vpn-instance vpn-instance-name routing-table [ network-address [ { mask | mask-length } [ longer-prefixes ] ] | as-path-acl as-path-acl-number | cidr | community [ aa:nn ]&<1-13>[ no-export-subc onfed | no-advertise | no-export ]* [ whole-match ] | community-list { basic-community-list-number Display the BGP VPNv4 routing...

  • Page 421: Mce Configuration Examples

    For commands to display information about a routing table, see IP Routing Basics Configuration Commands in the Layer 3 - IP Routing Command Reference. MCE Configuration Examples Using OSPF to Redistribute VPN Routes Between an MCE and PE Network requirements Figure 14-6.
  • Page 422 Configure VPN instances # Configure two instances VPN1 and VPN2 on the MCE device, with the RD values of the two VPN instances being 10:1 and 20:1. <MCE> system-view [MCE] ip vpn-instance vpn1 [MCE-vpn-instance-vpn1] route-distinguisher 10:1 [MCE-vpn-instance-vpn1] quit [MCE] ip vpn-instance vpn2 [MCE-vpn-instance-vpn2] route-distinguisher 20:1 # Create VLAN 10, add GigabitEthernet 1/0/10 to VLAN 10, and create VLAN-interface 10.
  • Page 423 # Configure a default route on VR1, specifying the next hop address to 10.214.10.3. <VR1> system-view [VR1] ip route-static 0.0.0.0 0.0.0.0 10.214.10.3 # Define a static route on MCE, specify the next hop address 10.214.10.2 for packets destined for the network segment 192.168.0.0, and bind this route to VPN1.
  • Page 424 192.168.10.0/24 100 1 10.214.20.2 Vlan20 As shown in the displayed information above, MCE has obtained the routes of VPN2 through RIP, and maintains these routes in a routing table different from the routing table for routing information of VPN1 to the network segment 192.168.0.0, thus isolating the routes of VPN1 from the routes of VPN2. Configure the routing protocol running between the MCE and a PE # MCE uses GigabitEthernet 1/0/3 to connect to GigabitEthernet 1/0/18 of PE.

  • Page 425: Using Bgp To Redistribute Vpn Routes Between An Mce And

    Destinations : 6 Routes : 6 Destination/Mask Proto Pre Cost NextHop Interface 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 10.214.30.0/24 Direct 0 10.214.30.1 Vlan30 10.214.30.2/32 Direct 0 127.0.0.1 InLoop0 100.100.10.1/32 Direct 0 127.0.0.1 InLoop0 192.168.0.0/16 O_ASE 150 1 10.214.30.1 Vlan30 As shown in the displayed information above, the static routes of VPN1 have been imported to the...
  • Page 426 Figure 14-7 Network diagram for MCE configuration (B) VPN 2 Site 1 BGP 200 VPN 1 BGP 100 OSPF GE1/0/18 GE1/0/3 172.16.10.0 Vlan-int30 GE1/0/10 10.100.30.1 Site 2 Vlan-int40 Vlan-int2 10.100.40.1 10.100.10.1 VPN 1 GE1/0/20 Vlan-int3 10.100.20.1 OSPF 172.16.20.0 VPN 2 Configuration procedure Configure VPN instances # Configure two instances VPN1 and VPN2 on the MCE device, with the RD values of the two VPN...
  • Page 427 [MCE-vlan3] port GigabitEthernet 1/0/20 [MCE-vlan3] quit [MCE] interface Vlan-interface 3 [MCE-Vlan-interface3] ip binding vpn-instance vpn2 [MCE-Vlan-interface3] ip address 10.214.20.3 24 [MCE-Vlan-interface3] quit # Create VLAN 30, VLAN 40 and the corresponding VLAN interfaces. Then bind VLAN 30 to VPN 1, and VLAN 40 to VPN 2, and configure IP addresses of the VLAN interfaces.
  • Page 428 10.100.20.0. The procedure of configuring OSPF process 20 is similar to that of configuring OSPF process 10. Followed is the result of the above configuration. [MCE] display ip routing-table vpn-instance vpn2 Routing Tables: vpn2 Destinations : 5 Routes : 5 Destination/Mask Proto Pre Cost NextHop...

  • Page 429: Using Mce To Advertise Vpn Routes Through Tunnels

    Destinations : 5 Routes : 5 Destination/Mask Proto Pre Cost NextHop Interface 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 10.100.40.0/24 Direct 0 10.100.20.3 Vlan3 10.100.40.3/32 Direct 0 127.0.0.1 InLoop0 172.16.20.0/24 255 2 10.100.20.2 Vlan3 After the above configurations, MCE has imported the OSPF routing information of VPN1 and VPN2 to the EBGP routing table of PE properly.
  • Page 430 Figure 14-9 Network topology of VPN 1 with the MCEs Figure 14-10 Network topology of VPN 2 with the MCEs OSPF Vlan-int11 Tunnel1 Tunnel1 Vlan-int21 MCE1 MCE2 VPN 2 VPN 2 Site1 Site2 Configuration procedure Configure VPN instances. Configurations on MCE 1 # Create VPN instance vpn1 for VPN 1, and configure an RD for it.
  • Page 431 [MCE1-vlan11] quit [MCE1] interface vlan-interface 11 [MCE1-Vlan-interface11] ip binding vpn-instance vpn2 [MCE1-Vlan-interface11] ip address 10.214.20.1 24 [MCE1-Vlan-interface11] quit [MCE1] interface tunnel 1 [MCE1-Tunnel1] ip binding vpn-instance vpn2 [MCE1-Tunnel1] ip address 10.1.2.1 24 [MCE1-Tunnel1] quit Configurations on MCE 2 # Create VPN instance vpn1 for VPN 1, and configure the same RD as that configured on MCE 1 for the VPN instance.
  • Page 432 # On MCE 1, configure OSPF process 1 for VPN instance vpn1, and configure OSPF to support MCE. Be sure to configure the same OSPF area as that configured at site 1 of VPN 1, area 0 in this example. [MCE1] ospf 1 vpn-instance vpn1 [MCE1-ospf-1] vpn-instance-capability simple [MCE1-ospf-1] area 0...

  • Page 433: Index

    Index BGP Path Attributes BGP Path Selection Configuration 6-65 Adding the Interface MTU into DD Packets BGP Route Reflector Configuration 6-59 4-41 BGP Route Selection Advertising a Default Route to a Peer or Peer Group 6-23 Bidirectional Detection in BFD Control Packet Mode 3-21 Advertising a Default Route to an IPv6...
  • Page 434 Configuring ABR Type-3 LSA Filtering 4-31 Configuring IPv6 BGP and IGP Route Synchronization 11-11 Configuring an Additional Metric for a RIP Interface 3-26 Configuring IPv6 BGP Community 11-20 Configuring an Additional Routing Metric 3-10 Configuring IPv6 BGP Peer Group 11-18 Configuring an Additional Routing Metric Configuring IPv6 BGP Preference and Default LOCAL_PREF and NEXT_HOP...
  • Page 435 Configuring OSPFv3 Areas 9-17 Configuring Stub Routers 4-40 Configuring OSPFv3 DR Election 9-21 Configuring the AS_PATH Attribute 11-13 Configuring OSPFv3 GR 9-26 Configuring the AS-PATH Attribute 6-32 Configuring OSPFv3 Inbound Route Filtering Configuring the Interval for Sending the Same Update 6-35 Configuring OSPFv3 Route Redistribution Configuring the IS Level and Circuit Level...
  • Page 436 Configuring the RIP Packet Sending Rate Enabling MD5 Authentication for TCP 3-19 Connections 6-38 Configuring VPN Instances 14-9 Enabling Message Logging 4-43 Configuring Zero Field Check on RIPng Enabling OSPFv3 Packets Enabling Quick eBGP Session Creating a BGP Connection 6-18 Reestablishment 6-38 Enabling Source IP Address Check on...
  • Page 437 IPv6 Routing Information Filtering Failure OSPFv3 Packets 12-18 IS-IS Area Resetting BGP Connections 14-21 IS-IS Authentication Configuration Example Resetting BGP Connections 6-48 5-56 Resetting IPv6 BGP Connections 11-23 IS-IS Basic Configuration 5-41 RIP FRR Configuration Example 3-30 IS-IS Graceful Restart Configuration RIP Message Format Example 5-53...
  • Page 438 Specifying the LSA Minimum Repeat Arrival Interval 4-38 Specifying the Source Interface for Establishing TCP Connections 11-5 Specifying the Source Interface for TCP Connections 6-19 Static Route BFD Configuration Example Static Route Configuration Items Static Route FRR Configuration Example 2-11 Static Route Static Routing and Dynamic Routing Supported IS-IS Features...

This manual is also suitable for:

S5820x series

Table of Contents