1. Manuals
  2. Brands
  3. HP Manuals
  4. Network Router
  5. MSR ASM
  6. Configuration manual

HP MSR ASM Configuration Manual

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

Advertisement

Quick Links

Download this manual
HP MSR Router Series
IP Multicast
Configuration Guide(V5)
Part number: 5998-8182
Software version: CMW520-R2513
Document version: 6PW106-20150808

Advertisement

Table of Contents
loading

Related Manuals for HP MSR ASM

Summary of Contents for HP MSR ASM

  • Page 1 HP MSR Router Series IP Multicast Configuration Guide(V5) Part number: 5998-8182 Software version: CMW520-R2513 Document version: 6PW106-20150808...
  • Page 2 The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an...

  • Page 3: Table Of Contents

    Contents Multicast overview ······················································································································································· 1   Overview ············································································································································································ 1   Multicast overview ···················································································································································· 1   Multicast features ······················································································································································ 3   Common notations in multicast ······························································································································· 4   Multicast advantages and applications ················································································································· 4   Multicast models ································································································································································ 5   Multicast architecture ························································································································································ 5  ...
  • Page 4 Basic IGMP functions configuration example ····································································································· 32   SSM mapping configuration example ················································································································ 34   IGMP proxying configuration example ··············································································································· 37   Troubleshooting IGMP ··················································································································································· 39   No membership information exists on the receiver-side router ········································································ 39   Membership information is inconsistent on the routers on the same subnet ··················································· 40  ...
  • Page 5 Displaying and maintaining PIM ·································································································································· 88   PIM configuration examples ········································································································································· 89   PIM-DM configuration example ··························································································································· 89   PIM-SM non-scoped zone configuration example ····························································································· 92   PIM-SM admin-scoped zone configuration example ························································································· 98   BIDIR-PIM configuration example ······················································································································· 104  ...
  • Page 6 Disabling a port from becoming a dynamic router port ················································································· 145   Configuring IGMP snooping querier ························································································································· 146   Configuration prerequisites ································································································································ 146   Enabling IGMP snooping querier ······················································································································ 146   Configuring parameters for IGMP queries and responses ············································································· 147  ...
  • Page 7 PIM-SM Inter-domain multicast configuration ··································································································· 181   Inter-AS multicast configuration by leveraging static RPF peers ····································································· 186   Anycast RP configuration ···································································································································· 191   SA message filtering configuration ···················································································································· 195   Troubleshooting MSDP ················································································································································ 199   MSDP peers stay in down state ························································································································· 199  ...
  • Page 8 MDT switchover ··················································································································································· 234   Multi-AS MD VPN ················································································································································ 235   Multicast VPN configuration task list ·························································································································· 236   Configuring MD-VPN ··················································································································································· 236   Configuration prerequisites ································································································································ 236   Enabling IP multicast routing in a VPN instance ······························································································ 237   Configuring a share-group and an MTI binding ······························································································...
  • Page 9 MLD SSM mapping configuration example ····································································································· 289   MLD proxying configuration example ··············································································································· 292   Troubleshooting MLD ··················································································································································· 294   No member information exists on the receiver-side router ············································································· 294   Membership information is inconsistent on the routers on the same subnet ················································· 295  ...
  • Page 10 IPv6 PIM configuration examples ······························································································································· 342   IPv6 PIM-DM configuration example ················································································································· 342   IPv6 PIM-SM non-scoped zone configuration example ··················································································· 345   IPv6 PIM-SM admin-scoped zone configuration example ··············································································· 350   IPv6 BIDIR-PIM configuration example ·············································································································· 362   IPv6 PIM-SSM configuration example ··············································································································· 367  ...
  • Page 11 Configuring the source IPv6 addresses for the MLD messages sent by the proxy ······································· 399   Configuring an MLD snooping policy ························································································································ 400   Configuration prerequisites ································································································································ 400   Configuring an IPv6 multicast group filter ········································································································ 400   Configuring IPv6 multicast source port filtering ······························································································· 401  ...
  • Page 12 IPv6 MBGP configuration example ···························································································································· 434   Network requirements ········································································································································· 434   Configuration procedure ···································································································································· 435   Support and other resources ·································································································································· 437   Contacting HP ······························································································································································ 437   Subscription service ············································································································································ 437   Related information ······················································································································································ 437   Documents ···························································································································································· 437  ...

  • Page 13: Multicast Overview

    Multicast overview Overview As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load. By using multicast technology, a network operator can easily provide new value-added services, such as live webcasting, Web TV, distance learning, telemedicine, Web radio, real-time video conferencing, and other bandwidth-critical and time-critical information services.
  • Page 14 a separate copy of the same information to each of these hosts. Sending many copies can place a tremendous pressure on the information source and the network bandwidth. Unicast is not suitable for batch transmission of information. Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information.

  • Page 15: Multicast Features

    Figure 3 Multicast transmission As shown in Figure 3, the multicast source sends only one copy of the information to a multicast group. Host B, Host D, and Host E, which are receivers of the information, must join the multicast group. The routers on the network duplicate and forward the information based on the distribution of the group members.

  • Page 16: Common Notations In Multicast

    manage multicast group memberships on stub subnets with attached group members. A multicast router itself can be a multicast group member. For a better understanding of the multicast concept, you can compare multicast transmission to the transmission of TV programs. Table 1 Comparing TV program transmission and multicast transmission TV transmission Multicast transmission...

  • Page 17: Multicast Models

    Multicast models Based on how the receivers treat the multicast sources, the multicast models include any-source multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM). ASM model—In the ASM model, any sender can send information to a multicast group as a •...

  • Page 18: Multicast Addresses

    Multicast addresses Network-layer multicast addresses (namely, multicast IP addresses) enables communication between multicast sources and multicast group members. In addition, a technique must be available to map multicast IP addresses to link-layer multicast MAC addresses. The membership of a group is dynamic. Hosts can join or leave multicast groups at any time. IP multicast addresses IPv4 multicast addresses: •...
  • Page 19 Address Description 224.0.0.12 DHCP server/relay agent. 224.0.0.13 All PIM routers. 224.0.0.14 RSVP encapsulation. 224.0.0.15 All CBT routers. 224.0.0.16 SBM. 224.0.0.17 All SBMs. 224.0.0.18 VRRP. IPv6 multicast addresses: • Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address, as shown in Figure 0xFF—Contains the most significant eight bits 1 1 1 1 1 1 1 1, which indicates that this address is an IPv6 multicast address.
  • Page 20 Scope—Contains four bits, which indicate the scope of the IPv6 internetwork for which the multicast traffic is intended. Table 5 describes the values of the Scope field. Table 5 Values of the Scope field Value Meaning 0, F Reserved. Interface-local scope. Link-local scope.

  • Page 21: Multicast Protocols

    Figure 7 An example of IPv6-to-MAC address mapping Multicast protocols Multicast protocols include the following categories: Layer 3 and Layer 2 multicast protocols: • Layer 3 multicast refers to IP multicast working at the network layer. Layer 3 multicast protocols—IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP. Layer 2 multicast refers to IP multicast working at the data link layer.
  • Page 22 Figure 8 Positions of Layer 3 multicast protocols Multicast group management protocols: • Typically, the Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) protocol is used between hosts and Layer 3 multicast devices that directly connect to the hosts. These protocols define the mechanism of establishing and maintaining group memberships between hosts and Layer 3 multicast devices.

  • Page 23: Multicast Packet Forwarding Mechanism

    Figure 9 Positions of Layer 2 multicast protocols IGMP snooping and MLD snooping: • IGMP snooping and MLD snooping are multicast constraining mechanisms that run on Layer 2 devices. They manage and control multicast groups by monitoring and analyzing IGMP or MLD messages exchanged between the hosts and Layer 3 multicast devices, effectively controlling the flooding of multicast data in a Layer 2 network.

  • Page 24: Multicast Support For Vpns

    Multicast support for VPNs Multicast support for VPNs refers to multicast applied in VPNs. Multicast support for VPNs is not available in IPv6 networks. Introduction to VPN instances VPNs must be isolated from one another and from the public network. As shown in Figure 10, VPN A and VPN B separately access the public network through PE devices.
  • Page 25 Implements information exchange and data conversion between the public network and VPN • instances. As shown in Figure 10, when a multicast source in VPN A sends a multicast stream to a multicast group, only the receivers that belong to both the multicast group and VPN A can receive the multicast stream. The multicast data is multicast both in VPN A and on the public network.

  • Page 26: Configuring Igmp

    Configuring IGMP Overview As a TCP/IP protocol responsible for IP multicast group member management, the IGMP is used by IP hosts and adjacent multicast routers to establish and maintain their multicast group memberships. IGMP versions IGMPv1 (documented in RFC 1 1 12) •...
  • Page 27 Figure 11 IGMP queries and reports As shown in Figure 1 1, assume that Host B and Host C are interested in multicast data addressed to multicast group G1, and Host A is interested in multicast data addressed to G2. The following process describes how the hosts join the multicast groups and how the IGMP querier (Router B in the figure) maintains the multicast group memberships: The hosts send unsolicited IGMP reports to the addresses of the multicast groups that they want to...

  • Page 28: Igmpv2 Overview

    IGMPv2 overview Compared with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism. Querier election mechanism In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) serves as the querier among multiple routers on the same subnet. IGMPv2 introduced an independent querier election mechanism.
  • Page 29 If it expects to reject multicast data from specific sources like S1, S2, …, it sends a report with the • Filter-Mode denoted as "Exclude Sources (S1, S2, …)." As shown in Figure 12, the network comprises two multicast sources, Source 1 (S1) and Source 2 (S2), both of which can send multicast data to multicast group G.

  • Page 30: Igmp Ssm Mapping

    ALLOW—The Source Address fields in this group record contain a list of the additional sources that the system wants to obtain data from, for packets sent to the specified multicast address. If the change was to an Include source list, these sources are the addresses that were added to the list.

  • Page 31: Igmp Proxying

    If G is in the SSM group range and the IGMP SSM mappings have been configured on Router A for • multicast group G, Router A translates the (*, G) information in the IGMP report into (G, INCLUDE, (S1, S2...)) information based on the configured IGMP SSM mappings and provides SSM service accordingly.

  • Page 32: Igmp Support For Vpns

    An IGMP proxy device performs host functions on the upstream interface based on the database. It responds to queries according to the information in the database or sends join/leave messages when the database changes. On the other hand, the IGMP proxy device performs router functions on the downstream interfaces by participating in the querier election, sending queries, and maintaining memberships based on the reports.

  • Page 33: Configuring Basic Igmp Functions

    Task Remarks Enabling IGMP proxying Optional. Configuring IGMP proxying Configuring multicast forwarding on a downstream Optional. interface Configuring basic IGMP functions This section describes how to configure basic IGMP functions. Configuration prerequisites Before you configure basic IGMP functions, complete the following tasks: •...

  • Page 34: Specifying The Igmp Version

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, an interface belongs to Bind the interface with the ip binding vpn-instance the public network, and is not VPN instance. vpn-instance-name bound with any VPN instance. Enable IGMP. igmp enable Disabled by default.

  • Page 35: Configuring A Multicast Group Filter

    does not unsolicitedly send any IGMP report or IGMP leave message. In other words, the interface is not a real member of the multicast group or the multicast source and group. Configuration procedure To configure an interface as a static member interface: Step Command Remarks...

  • Page 36: Adjusting Igmp Performance

    Adjusting IGMP performance When you adjust IGMP performance, follow these guidelines: The configurations made in IGMP view are effective on all interfaces. The configurations made in • interface view are effective only on the current interface. A configuration made in interface view always takes priority over the same configuration made in •...

  • Page 37: Configuring Igmp Query And Response Parameters

    Step Command Remarks Configure the router to discard any IGMP message By default, the device does not require-router-alert that does not carry the check the Router-Alert option. Router-Alert option. Enable insertion of the By default, IGMP messages carry Router-Alert option into IGMP send-router-alert the Router-Alert option.
  • Page 38 When multiple multicast routers exist on the same subnet, the IGMP querier is responsible for sending IGMP queries. If a non-querier router receives no IGMP query from the querier when the other querier present interval expires, it considers that the querier as having failed and starts a new querier election. Otherwise, the non-querier router resets the other querier present timer.

  • Page 39: Enabling Igmp Fast-Leave Processing

    Configuring IGMP query and response parameters on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number 2 by default. A higher robustness variable Configure the IGMP querier's igmp robust-count robust-value makes the IGMP querier more robustness variable.

  • Page 40: Enabling The Igmp Host Tracking Function

    Step Command Remarks Enter public network IGMP igmp [ vpn-instance view or VPN instance IGMP vpn-instance-name ] view. Enable IGMP fast-leave fast-leave [ group-policy Disabled by default. processing. acl-number ] Enabling IGMP fast-leave processing on an interface Step Command Remarks Enter system view.

  • Page 41: Configuration Prerequisites

    Configuration prerequisites Before you configure the IGMP SSM mapping feature, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the • network layer. • Configure basic IGMP functions. Enabling SSM mapping To ensure SSM service for all hosts on a subnet, enable IGMPv3 on the interface that forwards multicast traffic onto the subnet, regardless of the IGMP version running on the hosts.

  • Page 42: Configuration Prerequisites

    Configuration prerequisites Before you configure the IGMP proxying feature, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the • network layer. • Enable IP multicast routing. Enabling IGMP proxying You can enable IGMP proxying on the interface in the direction toward the root of the multicast forwarding tree to make the device serve as an IGMP proxy.

  • Page 43: Displaying And Maintaining Igmp

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable multicast forwarding on a non-querier downstream igmp proxying forwarding Disabled by default. interface. Displaying and maintaining IGMP Task Command Remarks display igmp [ all-instance | vpn-instance vpn-instance-name ] group [ group-address | Display IGMP group information.

  • Page 44: Igmp Configuration Examples

    Task Command Remarks display igmp [ all-instance | vpn-instance Display the multicast group vpn-instance-name ] ssm-mapping group information created from IGMPv1 [ group-address | interface interface-type Available in any view. and IGMPv2 reports based on the interface-number ] [ verbose ] [ | { begin | configured IGMP SSM mappings.
  • Page 45 Figure 15 Network diagram Configuration procedure Assign IP addresses and configure unicast routing: Assign an IP address and subnet mask to each interface according to Figure 15. (Details not shown.) Configure OSPF on the routers on the PIM network to make sure they are interoperable at the network layer and they can dynamically update their routing information.

  • Page 46: Ssm Mapping Configuration Example

    [RouterB-Pos5/0] pim dm [RouterB-Pos5/0] quit # Enable IP multicast routing on Router C, enable PIM-DM on each interface, and enable IGMP on Ethernet 1/1. <RouterC> system-view [RouterC] multicast routing-enable [RouterC] interface ethernet 1/1 [RouterC-Ethernet1/1] igmp enable [RouterC-Ethernet1/1] pim dm [RouterC-Ethernet1/1] quit [RouterC] interface pos 5/0 [RouterC-Pos5/0] pim dm [RouterC-Pos5/0] quit...
  • Page 47 Figure 16 Network diagram Table 6 Interface and IP address assignment Device Interface IP address Device Interface IP address Source 1 — 133.133.1.1/24 Source 3 — 133.133.3.1/24 Source 2 — 133.133.2.1/24 Receiver — 133.133.4.1/24 Router A Eth1/1 133.133.1.2/24 Router C Eth1/1 133.133.3.2/24 Router A...
  • Page 48 [RouterD] interface ethernet 1/2 [RouterD-Ethernet1/2] pim sm [RouterD-Ethernet1/2] quit [RouterD] interface ethernet 1/3 [RouterD-Ethernet1/3] pim sm [RouterD-Ethernet1/3] quit # Enable IP multicast routing on Router A, and enable PIM-SM on each interface. <RouterA> system-view [RouterA] multicast routing-enable [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] pim sm [RouterA-Ethernet1/1] quit [RouterA] interface ethernet 1/2...

  • Page 49: Igmp Proxying Configuration Example

    133.133.1.1 133.133.3.1 # Display the multicast group information created based on the configured IGMP SSM mappings on the public network on Router D. [RouterD] display igmp ssm-mapping group Total 1 IGMP SSM-mapping Group(s). Interface group report information of VPN-Instance: public net Ethernet1/1(133.133.4.2): Total 1 IGMP SSM-mapping Group reported Group Address...
  • Page 50 Figure 17 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 17. (Details not shown.) Enable IP multicast routing, PIM-DM, IGMP, and IGMP proxying: # Enable IP multicast routing on Router A, PIM-DM on Serial 2/1, and IGMP on Ethernet 1/1. <RouterA>...

  • Page 51: Troubleshooting Igmp

    # Display the IGMP group information on Router A. [RouterA] display igmp group Total 1 IGMP Group(s). Interface group report information of VPN-Instance: public net Ethernet1/1(192.168.1.1): Total 1 IGMP Groups reported Group Address Last Reporter Uptime Expires 224.1.1.1 192.168.1.2 00:02:04 00:01:15 The output shows that IGMP reports from the hosts are forwarded to Router A through the proxy interface, Ethernet 1/1 of Router B.

  • Page 52: Membership Information Is Inconsistent On The Routers On The Same Subnet

    Membership information is inconsistent on the routers on the same subnet Symptom The IGMP routers on the same subnet have different membership information. Analysis A router running IGMP maintains multiple parameters for each interface, and these parameters • influence one another, forming very complicated relationships. Inconsistent IGMP interface parameter configurations for routers on the same subnet will surely result in inconsistency of memberships.

  • Page 53: Configuring Pim

    Configuring PIM Overview PIM provides IP multicast forwarding by leveraging unicast static routes or unicast routing tables generated by any unicast routing protocol, such as RIP, OSPF, IS-IS, or BGP. Independent of the unicast routing protocols running on the device, multicast routing can be implemented as long as the corresponding multicast routing entries are created through unicast routes.
  • Page 54 Neighbor discovery In a PIM domain, a PIM router discovers PIM neighbors and maintains PIM neighboring relationship with other routers. It also builds and maintains SPTs by periodically multicasting hello messages to all other PIM routers (224.0.0.13) on the local subnet. Every PIM-enabled interface on a router sends hello messages periodically, and thus learns the PIM neighboring information pertinent to the interface.
  • Page 55 The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again when it no longer has any multicast receiver. Graft When a host attached to a pruned node joins a multicast group, to reduce the join latency, PIM-DM uses a graft mechanism to resume data forwarding to that branch.

  • Page 56: Pim-Sm Overview

    If both routers have the same preference to the source, the router with a smaller metric to the source wins. If a tie exists in route metric to the source, the router with a higher IP address on the downstream interface wins. PIM-SM overview PIM-DM uses the flood-and-prune principle to build SPTs for multicast data distribution.
  • Page 57 A DR must be elected in a shared-media network, no matter this network connects to multicast sources or to receivers. The receiver-side DR sends join messages to the RP. The source-side DR sends register messages to the RP. A DR is elected on a shared-media subnet by means of comparison of the priorities and IP addresses carried in hello messages.
  • Page 58 A BSR serves as the administrative core of the PIM-SM domain. A PIM-SM domain can have only one BSR, but can have multiple C-BSRs. If the BSR fails, a new BSR is automatically elected from the C-BSRs to avoid service interruption. A device can serve as a C-RP and a C-BSR at the same time. As shown in Figure 21, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages)
  • Page 59 RPT building Figure 22 RPT building in a PIM-SM domain Host A Source Receiver Host B Server Receiver Join message Multicast packets Host C As shown in Figure 22, the process of building an RPT is as follows: When a receiver joins the multicast group G, it uses an IGMP message to inform the directly connected DR.
  • Page 60 Figure 23 Multicast source registration As shown in Figure 23, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to multicast group G. After receiving the multicast packet, the DR that directly connects to the multicast source encapsulates the packet in a PIM register message, and then sends the message to the corresponding RP by unicast.

  • Page 61: Bidir-Pim Overview

    receiver-side DRs. The RP acts as a transfer station for all multicast packets. The whole process involves the following issues: The source-side DR and the RP need to implement complicated encapsulation and de-encapsulation • of multicast packets. Multicast packets are delivered along a path that might not be the shortest one. •...
  • Page 62 RP discovery • • DF election Bidirectional RPT building • Neighbor discovery BIDIR-PIM uses the same neighbor discovery mechanism as PIM-SM does. For more information, see "Neighbor discovery." RP discovery BIDIR-PIM uses the same RP discovery mechanism as PIM-SM does. For more information, see "RP discovery."...
  • Page 63 Router B and Router C multicast DF election messages to all PIM routers (224.0.0.13). The election messages carry the RP's address, and the priority and metric of the unicast route, MBGP route, or multicast static route to the RP. The router with a route of the highest priority becomes the DF. In the case of a tie, the router with the route of the lowest metric wins the DF election.

  • Page 64: Administrative Scoping Overview

    Figure 26 RPT building at the multicast source side As shown in Figure 26, the process for building a source-side RPT is relatively simple: When a multicast source sends multicast packets to multicast group G, the DF in each network segment unconditionally forwards the packets to the RP.
  • Page 65 Multicast group ranges within different admin-scoped zones can be overlapped. A multicast group is valid only within its local admin-scoped zone, and functions as a private group address. The global-scoped zone maintains a BSR, which serves the multicast groups that do not belong to any admin-scoped zone.

  • Page 66: Pim-Ssm Overview

    Figure 28 Relationship in view of multicast group address ranges Admin-scope 1 Admin-scope 3 G1 address G3 address Admin-scope 2 Global-scope G2 address − − G2 address As shown in Figure 28, the admin-scoped zones 1 and 2 have no intersection, but the admin-scoped zone 3 is a subset of the admin-scoped zone 1.

  • Page 67: Relationship Among Pim Protocols

    Figure 29 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 29, Host B and Host C are multicast information receivers. They send IGMPv3 report messages to the respective DRs to express their interest in the information about the specific multicast source S.

  • Page 68: Pim Support For Vpns

    Figure 30 Relationship among PIM protocols A receiver joins multicast group G. G is in the A multicast source is SSM group range? specified? BIDIR-PIM is enabled? An IGMP-SSM mapping is configured for G? PIM-SM runs for G. G has a BIDIR-PIM RP? PIM-SSM runs for G.

  • Page 69: Pim-Dm Configuration Task List

    PIM-DM configuration task list Task Remarks Enabling PIM-DM Required. Enabling state-refresh capability Optional. Configuring state-refresh parameters Optional. Configuring PIM-DM graft retry period Optional. Configuring common PIM features Optional. Configuration prerequisites Before you configure PIM-DM, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the •...

  • Page 70: Enabling State-Refresh Capability

    Step Command Description Create a VPN instance and For more information about this ip vpn-instance vpn-instance-name enter VPN instance view. command, see MPLS Command Reference. Not configured by default. Configure an RD for the VPN route-distinguisher For more information about this instance.

  • Page 71: Configuring Pim-Dm Graft Retry Period

    The TTL value of a state-refresh message decrements by 1 whenever it passes a router before it is forwarded to the downstream node until the TTL value comes down to 0. In a small network, a state-refresh message might cycle in the network. To effectively control the propagation scope of state-refresh messages, configure an appropriate TTL value based on the network size.

  • Page 72: Pim-Sm Configuration Task List

    PIM-SM configuration task list Task Remarks Enabling PIM-SM Required. Configuring a static RP Required. Configuring a C-RP Use any Configuring an RP method. Enabling auto-RP Configuring C-RP timers globally Optional. Configuring a C-BSR Required. Configuring a PIM domain border Optional. Configuring a BSR Configuring global C-BSR parameters Optional.

  • Page 73: Enabling Pim-Sm

    Determine the register suppression time. • • Determine the register probe time. Determine the multicast traffic rate threshold, ACL rule, and sequencing rule for a switchover to SPT. • Determine the interval of checking the traffic rate threshold before a switchover to SPT. •...

  • Page 74: Configuring An Rp

    Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. HP recommends that you configure C-RPs on backbone routers. To guard against C-RP spoofing, you must configure a legal C-RP address range and the range of multicast groups to be served on the BSR.
  • Page 75 Step Command Remarks Configure a legal C-RP Optional. address range and the range crp-policy acl-number of multicast groups to be No restrictions by default. served. Enabling auto-RP Auto-RP announcement and discovery messages are addressed to the multicast group addresses 224.0.1.39 and 224.0.1.40, respectively. With auto-RP enabled on a device, the device can receive these two types of messages and record the RP information carried in such messages.

  • Page 76: Configuring A Bsr

    Configuring a BSR A PIM-SM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR. Elected from C-BSRs, the BSR is responsible for collecting and advertising RP information in the PIM-SM domain. Configuring a C-BSR C-BSRs should be configured on routers in the backbone network.
  • Page 77 Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] c-bsr interface-type Configure an interface as a No C-BSRs are configured by interface-number [ hash-length C-BSR. default. [ priority ] ] Optional.
  • Page 78 Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Optional. Configure the hash mask c-bsr hash-length hash-length length. 30 by default. Optional. Configure the C-BSR priority. c-bsr priority priority By default, the C-BSR priority is 64.

  • Page 79: Configuring Administrative Scoping

    Disabling BSM semantic fragmentation Generally, a BSR periodically distributes the RP-set information in bootstrap messages within the PIM-SM domain. It encapsulates a BSM in an IP datagram and might split the datagram into fragments if the message exceeds the MTU. In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message.
  • Page 80 Step Command Remarks Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Enable administrative c-bsr admin-scope Disabled by default. scoping. Configuring an admin-scoped zone boundary ZBRs form the boundary of each admin-scoped zone. Each admin-scoped zone maintains a BSR, which serves a specific multicast group range.

  • Page 81: Configuring Multicast Source Registration

    Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] No C-BSRs are configured for an admin-scoped zone by default. c-bsr group group-address { mask | The group-address { mask | Configure a C-BSR for an mask-length } [ hash-length mask-length } argument can...

  • Page 82: Configuring Switchover To Spt

    Configure a filtering rule for register messages on all C-RP routers and configure them to calculate the checksum based on the entire register messages. Configure the register suppression time and the register probe time on all routers that might become source-side DRs. To configure register-related parameters: Step Command...

  • Page 83: Configuring Bidir-Pim

    Configuring BIDIR-PIM This section describes how to configure BIDIR-PIM. BIDIR-PIM configuration task list Task Remarks Enabling PIM-SM Required. Enabling BIDIR-PIM Required. Configuring a static RP Required. Configuring a C-RP Use any method. Configuring an RP Enabling auto-RP Configuring C-RP timers globally Optional.

  • Page 84: Enabling Pim-Sm

    Enabling PIM-SM Because BIDIR-PIM is implemented on the basis of PIM-SM, you must enable PIM-SM before enabling BIDIR-PIM. To deploy a BIDIR-PIM domain, enable PIM-SM on all non-border interfaces of the domain. IMPORTANT: All interfaces on a device must be enabled with the same PIM mode. Enabling PIM-SM globally for the public network Step Command...

  • Page 85: Configuring An Rp

    Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. HP recommends that you configure C-RPs on backbone routers. To guard against C-RP spoofing, configure a legal C-RP address range and the range of multicast groups to be served on the BSR.
  • Page 86 To configure a C-RP: Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance vpn-instance-name ] or VPN instance PIM view. c-rp interface-type interface-number [ group-policy acl-number | priority Configure an interface to be a No C-RP is configured by priority | holdtime hold-interval | C-RP for BIDIR-PIM.

  • Page 87: Configuring A Bsr

    Step Command Remarks Optional. Configure C-RP timeout timer. c-rp holdtime interval 150 seconds by default. Configuring a BSR A BIDIR-PIM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR. Elected from C-BSRs, the BSR collects and advertises RP information in the BIDIR-PIM domain.
  • Page 88 Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] c-bsr interface-type Configure an interface as a No C-BSRs are configured by interface-number [ hash-length C-BSR. default. [ priority ] ] Optional.
  • Page 89 Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Optional. Configure the hash mask c-bsr hash-length hash-length length. 30 by default. Optional. Configure the C-BSR priority. c-bsr priority priority 64 by default.

  • Page 90: Configuring Administrative Scoping

    Disabling BSM semantic fragmentation Generally, a BSR periodically distributes the RP-set information in bootstrap messages within the BIDIR-PIM domain. It encapsulates a BSM in an IP datagram and might split the datagram into fragments if the message exceeds the MTU. In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message.
  • Page 91 Step Command Remarks Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Enable administrative c-bsr admin-scope Disabled by default. scoping. Configuring an admin-scoped zone boundary The boundary of each admin-scoped zone is formed by ZBRs. Each admin-scoped zone maintains a BSR, which serves a specific multicast group range.

  • Page 92: Configuring Pim-Ssm

    Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] No C-BSRs are configured for an admin-scoped zone by default. c-bsr group group-address { mask | The group-address { mask | Configure a C-BSR for an mask-length } [ hash-length mask-length } argument can...

  • Page 93: Enabling Pim-Sm

    Enabling PIM-SM The implementation of the SSM model is based on some subsets of PIM-SM. Therefore, you must enable PIM-SM before configuring PIM-SSM. When you deploy a PIM-SSM domain, enable PIM-SM on non-border interfaces of the routers. IMPORTANT: All the interfaces on a device must be enabled with the same PIM mode. Enabling PIM-SM globally on the public network Step Command...

  • Page 94: Configuring Common Pim Features

    the SSM group range. All PIM-SM-enabled interfaces assume the PIM-SSM model for multicast groups within this address range. Configuration guidelines • Perform the following configuration on all routers in the PIM-SSM domain. Make sure the same SSM group range is configured on all routers in the entire domain. Otherwise, •...

  • Page 95: Configuring A Multicast Data Filter

    Determine the ACL rule for filtering multicast data. • • Determine the ACL rule defining a legal source address range for hello messages. Determine the priority for DR election (global value/interface level value). • Determine the PIM neighbor timeout timer (global value/interface value). •...

  • Page 96: Configuring Pim Hello Options

    To configure a hello message filter: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number No hello message filter by default. When the hello message filter is configured, if hello messages of an Configure a hello message pim neighbor-policy acl-number existing PIM neighbor fail to pass filter.

  • Page 97: Setting The Prune Delay Timer

    Configuring hello options globally Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Optional. Set the DR priority. hello-option dr-priority priority 1 by default. Optional. Set the neighbor lifetime. hello-option holdtime interval 105 seconds by default.

  • Page 98: Configuring Common Pim Timers

    To set the prune delay timer: Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Optional. Set the prune delay timer. prune delay interval By default, the local prune delay timer is not configured.

  • Page 99: Configuring Join/Prune Message Sizes

    Step Command Remarks Optional. Configure the multicast source source-lifetime interval lifetime. 210 seconds by default. Configuring common PIM timers on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the hello interval. pim timer hello interval 30 seconds by default.

  • Page 100: Displaying And Maintaining Pim

    Displaying and maintaining PIM Task Command Remarks Display information about the display pim [ all-instance | vpn-instance Available in any BSR in the PIM-SM domain and vpn-instance-name ] bsr-info [ | { begin | exclude | view. the locally configured C-RP. include } regular-expression ] display pim [ all-instance | vpn-instance Display information about the...

  • Page 101: Pim Configuration Examples

    Task Command Remarks reset pim [ all-instance | vpn-instance Reset PIM control message Available in user vpn-instance-name ] control-message counters counters. view. [ interface interface-type interface-number ] PIM configuration examples This section provides examples of configuring PIM on routers. PIM-DM configuration example Network requirements As shown in Figure...
  • Page 102 Device Interface IP address Router B Ethernet 1/1 10.110.2.1/24 Router B POS 5/0 192.168.2.1/24 Router C Ethernet 1/1 10.110.2.2/24 Router C POS 5/0 192.168.3.1/24 Router D Ethernet 1/1 10.110.5.1/24 Router D Serial 2/0 192.168.1.2/24 Router D POS 5/0 192.168.2.2/24 Router D POS 5/1 192.168.3.2/24 Configuration procedure...
  • Page 103 Verifying the configuration Use the display pim interface command to display PIM information on each interface. For example: # Display PIM information on Router D. [RouterD] display pim interface VPN-Instance: public net Interface NbrCnt HelloInt DR-Pri DR-Address Eth1/1 10.110.5.1 (local) Ser2/0 192.168.1.2 (local)

  • Page 104: Pim-Sm Non-Scoped Zone Configuration Example

    Upstream interface: Serial2/0 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1 Protocol: pim-dm, UpTime: 00:04:25, Expires: never # Display PIM routing table information on Router D. [RouterD] display pim routing-table VPN-Instance: public net Total 0 (*, G) entry;...
  • Page 105 Figure 32 Network diagram Receiver Host A Router A Eth1/1 POS5/0 Host B POS5/2 Receiver Eth1/1 POS5/3 POS5/1 Eth1/1 POS5/0 POS5/0 Source POS5/0 Router D Router E Router B Host C 10.110.5.100/24 POS5/0 Eth1/1 PIM-SM Host D Router C Table 9 shows the interface and IP address assignment, and network topology scheme.
  • Page 106 Configuration procedure Assign IP addresses and configure unicast routing: Assign an IP address and subnet mask to each interface according to Figure 32. (Details not shown.) Configure OSPF on the routers in the PIM-SM domain to make sure they are interoperable at the network layer.
  • Page 107 Verifying the configuration Use the display pim interface command to display PIM information on each interface. For example: # Display PIM information on Router A. [RouterA] display pim interface VPN-Instance: public net Interface NbrCnt HelloInt DR-Pri DR-Address Eth1/1 10.110.1.1 (local) Ser2/0 192.168.1.2 Pos5/0...
  • Page 108 State: Elected Scope: Not scoped Uptime: 00:01:18 Next BSR message scheduled at: 00:01:52 Candidate BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Elected Scope: Not scoped Candidate RP: 192.168.9.2(Pos5/2) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:48 # Display RP information on Router A.
  • Page 109 RPF prime neighbor: 192.168.9.2 Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1 Protocol: igmp, UpTime: 00:13:46, Expires: 00:03:06 (10.110.5.100, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: Serial2/0 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1...

  • Page 110: Pim-Sm Admin-Scoped Zone Configuration Example

    Total number of downstreams: 1 1: Pos5/2 Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22 PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 33, the receivers receive VOD information through multicast. The entire PIM-SM domain is divided into admin-scoped zone 1, admin-scoped zone 2, and the global-scoped zone. Router B, Router C, and Router D are ZBRs of the three domains, respectively.
  • Page 111 Table 10 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A Eth1/1 192.168.1.1/24 Router D S2/1 10.110.4.2/24 Router A S2/1 10.110.1.1/24 Router D S2/2 10.110.7.1/24 Router B Eth1/1 192.168.2.1/24 Router D POS5/1 10.110.8.1/24 Router B S2/1 10.110.1.2/24 Router E...
  • Page 112 # On Router B, enable IP multicast routing and administrative scoping, and enable PIM-SM on each interface. <RouterB> system-view [RouterB] multicast routing-enable [RouterB] pim [RouterB-pim] c-bsr admin-scope [RouterB-pim] quit [RouterB] interface ethernet 1/1 [RouterB-Ethernet1/1] pim sm [RouterB-Ethernet1/1] quit [RouterB] interface serial 2/1 [RouterB-Serial2/1] pim sm [RouterB-Serial2/1] quit [RouterB] interface pos 5/1...
  • Page 113 [RouterB-acl-basic-2001] quit [RouterB] pim [RouterB-pim] c-bsr group 239.0.0.0 8 [RouterB-pim] c-bsr serial 2/1 [RouterB-pim] c-rp serial 2/1 group-policy 2001 [RouterB-pim] quit # On Router D, configure the service scope of RP advertisements and configure Serial 2/1 as a C-BSR and C-RP of admin-scoped zone 2. [RouterD] acl number 2001 [RouterD-acl-basic-2001] rule permit source 239.0.0.0 0.255.255.255 [RouterD-acl-basic-2001] quit...
  • Page 114 Candidate RP: 10.110.1.2(Serial2/1) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:15 # Display information about the BSR and locally configured C-RP on Router D. [RouterD] display pim bsr-info VPN-Instance: public net Elected BSR Address: 10.110.9.1 Priority: 64 Hash mask length: 30 State: Accept Preferred Scope: Global...
  • Page 115 Candidate RP: 10.110.9.1(Serial2/1) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:55 # Display RP information on Router B. [RouterB] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 224.0.0.0/4 RP: 10.110.9.1 Priority: 192 HoldTime: 150 Uptime: 00:03:39 Expires: 00:01:51 Group/MaskLen: 239.0.0.0/8...

  • Page 116: Bidir-Pim Configuration Example

    HoldTime: 150 Uptime: 00:00:32 Expires: 00:01:58 BIDIR-PIM configuration example Network requirements In the BIDIR-PIM domain shown in Figure 34, Source 1 and Source 2 send different multicast information to multicast group 225.1.1.1. Host A and Host B receive multicast information from the two sources. Serial 2/1 of Router C acts as a C-BSR, and loopback interface 0 of Switch C acts as a C-RP of the BIDIR-PIM domain.
  • Page 117 Device Interface IP address Router D Serial 2/1 10.110.3.2/24 Source 1 — 192.168.1.100/24 Source 2 — 192.168.4.100/24 Receiver 1 — 192.168.2.100/24 Receiver 2 — 192.168.3.100/24 Configuration procedure Assign IP addresses and configure unicast routing: Assign an IP address and subnet mask to each interface according to Figure 34.
  • Page 118 # On Router C, enable IP multicast routing, enable PIM-SM on each interface, and enable BIDIR-PIM. <RouterC> system-view [RouterC] multicast routing-enable [RouterC] interface serial 2/1 [RouterC-Serial2/1] pim sm [RouterC-Serial2/1] quit [RouterC] interface serial 2/2 [RouterC-Serial2/2] pim sm [RouterC-Serial2/2] quit [RouterC] interface loopback 0 [RouterC-LoopBack0] pim sm [RouterC-LoopBack0] quit [RouterC] pim...
  • Page 119 [RouterB] display pim df-info VPN-Instance: public net RP Address: 1.1.1.1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Eth1/1 01:24:09 192.168.2.1 (local) Ser2/1 01:24:09 10.110.1.2 (local) Ser2/2 Lose 01:23:12 10.110.2.2 # Display the DF information of BIDIR-PIM on Router C. [RouterC] display pim df-info VPN-Instance: public net RP Address: 1.1.1.1 Interface...

  • Page 120: Pim-Ssm Configuration Example

    00001. RP Address: 1.1.1.1 MID: 0, Flags: 0x2100000:0 Uptime: 00:06:24 RPF interface: Serial2/2 List of 2 DF interfaces: 1: Ethernet1/1 2: Serial2/1 # Display the DF information of the multicast forwarding table on Router C. [RouterC] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP Total 1 RP matched...
  • Page 121 Figure 35 Network diagram Receiver Host A Router A Eth1/1 POS5/0 Host B POS5/2 Receiver Eth1/1 POS5/3 POS5/1 Eth1/1 POS5/0 POS5/0 Source POS5/0 Router D Router E Router B Host C 10.110.5.100/24 POS5/0 Eth1/1 PIM-SSM Host D Router C Table 12 shows the interface and IP address assignment, and network topology scheme.
  • Page 122 Configuration procedure Assign IP addresses and configure unicast routing: Assign an IP address and subnet mask to each interface according to Figure 35. (Details not shown.) Configure OSPF on the routers in the PIM-SSM domain to make sure they are interoperable at the network layer.

  • Page 123: Troubleshooting Pim

    Assume that Host A needs to receive the information a specific multicast source S 10.1 10.5.100/24 sends to multicast group G 232.1.1.1. Router A builds an SPT toward the multicast source. Routers on the SPT path (Router A and Router D) have generated (S, G) entry, but Router E, which is not on the SPT path, does not have multicast routing entries.

  • Page 124: Multicast Data Abnormally Terminated On An Intermediate Router

    Analysis When PIM-DM runs on the entire network, multicast data is flooded from the first hop router • connected with the multicast source to the last-hop router connected with the clients. When the multicast data is flooded to a router, regardless of which router it is, the router creates (S, G) entries only if it has a route to the multicast source.

  • Page 125: Rps Cannot Join Spt In Pim-Sm

    Analysis When a router receives a multicast packet, it decrements the TTL value of the multicast packet by 1 • and recalculates the checksum value. The router then forwards the packet to all outgoing interfaces. If the multicast minimum-ttl command is configured on the outgoing interfaces, the TTL value of the packet must be larger than the configured minimum TTL value.

  • Page 126: Rpt Establishment Failure Or Source Registration Failure In Pim-Sm

    RPT establishment failure or source registration failure in PIM-SM Symptom C-RPs cannot unicast advertise messages to the BSR. The BSR does not advertise bootstrap messages containing C-RP information and has no unicast route to any C-RP. An RPT cannot be established correctly, or the DR cannot perform source registration with the RP.

  • Page 127: Configuring Multicast Routing And Forwarding

    Configuring multicast routing and forwarding Overview In multicast implementations, the following types of tables implement multicast routing and forwarding: Multicast routing table of a multicast routing protocol—Each multicast routing protocol has its own • multicast routing table, such as the PIM routing table. General multicast routing table—The multicast routing information of different multicast routing •...
  • Page 128 path of the packet that the RPF interface receives from the RPF neighbor as the shortest path that leads back to the source. The router searches its MBGP routing table by using the IP address of the packet source as the destination address and automatically chooses an optimal MBGP route.

  • Page 129: Static Multicast Routes

    received the packet is the RPF interface, the router forwards the packet out of all outgoing interfaces. Otherwise, it discards the packet. As shown in Figure 36, assume that unicast routes are available in the network, MBGP is not configured, and no static multicast routes have been configured on Router C.
  • Page 130 Figure 37 Changing an RPF route As shown in Figure 37, when no static multicast route is configured, Router C's RPF neighbor on the path back to Source is Router A. The multicast information from Source travels along the path from Router A to Router C, which is the unicast route between the two routers.

  • Page 131: Multicast Forwarding Across Unicast Subnets

    Router C and Router D, to specify Router B as the RPF neighbor of Router C and Router C as the RPF neighbor of Router D, the receiver hosts will receive the multicast data from the multicast source. Multicast forwarding across unicast subnets Some networking devices might not support multicast protocols in a network.

  • Page 132: Configuration Task List

    Introduction to multicast traceroute packets A multicast traceroute packet is a special IGMP packet that is different from common IGMP packets. The difference lies in that its IGMP Type field is set to 0x1F or 0x1E and its destination IP address is a unicast address.

  • Page 133: Configuring Multicast Routing And Forwarding

    Enabling IP multicast routing in a VPN instance Step Command Remarks Enter system view. system-view Create a VPN instance and For more information about this ip vpn-instance vpn-instance-name enter VPN instance view. command, see MPLS Command Reference. No RD is configured by default. Configure a route route-distinguisher For more information about this...

  • Page 134: Configuring A Multicast Routing Policy

    Step Command Remarks By default, no static multicast route is configured. ip rpf-route-static [ vpn-instance When you configure a static vpn-instance-name ] multicast route, you cannot specify source-address { mask | an RPF neighbor by providing the mask-length } [ protocol Configure a static multicast type and number of the interface if [ process-id ] ] [ route-policy...

  • Page 135: Configuring A Multicast Forwarding Range

    Configuring a multicast forwarding range Multicast packets do not travel without a boundary in a network. The multicast data corresponding to each multicast group must be transmitted within a definite scope. You can define a multicast forwarding range by: Specifying boundary interfaces, which form a closed multicast forwarding area. •...

  • Page 136: Tracing A Multicast Path

    When the router forwards multicast data, it replicates a copy of the multicast data for each downstream node and forwards the data. Each of these downstream nodes is a branch of the multicast distribution tree. You can configure the maximum number of downstream nodes (namely, the maximum number of outgoing interfaces) for a single entry in the multicast forwarding table to lessen the burden on the router.

  • Page 137: Displaying And Maintaining Multicast Routing And Forwarding

    Task Command Remarks mtracert source-address Trace a multicast path. [ [ last-hop-router-address ] Available in any view. group-address ] Displaying and maintaining multicast routing and forwarding CAUTION: The reset commands might cause multicast transmission failures. To display and maintain multicast routing and forwarding: Task Command Remarks...

  • Page 138: Configuration Examples

    Task Command Remarks display multicast [ all-instance | vpn-instance Display RPF route vpn-instance-name ] rpf-info source-address information about the Available in any view. [ group-address ] [ | { begin | exclude | include } specified multicast source. regular-expression ] display multicast [ all-instance | vpn-instance Display minimum TTL vpn-instance-name ] minimum-ttl [ interface-type...
  • Page 139 Figure 40 Network diagram Configuration procedure Assign IP addresses and configure unicast routing: Assign an IP address and subnet mask to each interface according to Figure 40. (Details not shown.) Enable OSPF on the routers in the PIM-DM domain to make sure they are interoperable at the network layer and they can dynamically update their routing information.

  • Page 140: Creating An Rpf Route

    [RouterA] interface ethernet 1/2 [RouterA-Ethernet1/2] pim dm [RouterA-Ethernet1/2] quit [RouterA] interface ethernet 1/3 [RouterA-Ethernet1/3] pim dm [RouterA-Ethernet1/3] quit # Enable IP multicast routing and PIM-DM on Router C in the same way. (Details not shown.) # Use the display multicast rpf-info command to view the RPF route to Source on Router B. [RouterB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: Ethernet1/3, RPF neighbor: 30.1.1.2...
  • Page 141 Figure 41 Network diagram PIM-DM OSPF domain Router A Router B Router C Eth1/2 Eth1/3 Eth1/2 30.1.1.2/24 30.1.1.1/24 20.1.1.1/24 Eth1/2 20.1.1.2/24 Eth1/1 Eth1/1 Eth1/1 50.1.1.1/24 40.1.1.1/24 10.1.1.1/24 Source 2 Source 1 Receiver 50.1.1.100/24 40.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure Assign IP addresses and configure unicast routing: Assign an IP address and subnet mask to each interface according to Figure...

  • Page 142: Multicast Forwarding Over Gre Tunnels

    [RouterB] display multicast rpf-info 50.1.1.100 [RouterC] display multicast rpf-info 50.1.1.100 No information is displayed. It means that that no RPF route to Source 2 exists on Router B and Router C. Configure a static multicast route: # Configure a static multicast route on Router B, specifying Router A as its RPF neighbor on the route to Source 2.
  • Page 143 Figure 42 Network diagram Multicast router Unicast router Multicast router Router A Router B Router C Eth1/2 Eth1/2 Eth1/1 Eth1/2 20.1.1.1/24 30.1.1.2/24 20.1.1.2/24 30.1.1.1/24 Eth1/1 Eth1/1 GRE tunnel 10.1.1.1/24 40.1.1.1/24 Tunnel0 Tunnel0 50.1.1.1/24 50.1.1.2/24 Source Receiver 10.1.1.100/24 40.1.1.100/24 Configuration procedure Assign an IP address and mask to each interface according to Figure 42.
  • Page 144 <RouterB> system-view [RouterB] ospf 1 [RouterB-ospf-1] area 0 [RouterB-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [RouterB-ospf-1-area-0.0.0.0] quit [RouterB-ospf-1] quit # Configure OSPF on Router C. [RouterC] ospf 1 [RouterC-ospf-1] area 0 [RouterC-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] network 40.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] network 50.1.1.0 0.0.0.255 [RouterC-ospf-1-area-0.0.0.0] quit [RouterC-ospf-1] quit...

  • Page 145: Troubleshooting Multicast Routing And Forwarding

    # Display PIM routing table information on Router C. [RouterC] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1...

  • Page 146: Multicast Data Fails To Reach Receivers

    Solution Use the display multicast routing-table static command to view the information of static multicast routes to verify that the static multicast route has been correctly configured and that the route entry exists in the multicast routing table. Check the type of the next-hop interface of the static multicast route. If the interface is not a point-to-point interface, be sure to specify the next hop address for the outgoing interface when you configure the static multicast route.

  • Page 147: Configuring Igmp Snooping

    Configuring IGMP snooping Hardware compatibility IGMP snooping is available only on the MSR series routers with fixed Layer 2 switching interfaces or Layer 2 switching interface modules. Overview IGMP snooping is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups.
  • Page 148 IGMP snooping related ports As shown in Figure 44, Router A connects to the multicast source, IGMP snooping runs on Switch A and Switch B, and Host A and Host C are receiver hosts (namely, members of a multicast group). Figure 44 IGMP snooping related ports As shown in Figure...

  • Page 149: How Igmp Snooping Works

    Message before Timer Description Action after expiration expiration When a port dynamically joins a multicast group, The switch removes this the switch starts or resets Dynamic member port IGMP membership port from the IGMP an aging timer for the aging timer report.

  • Page 150: Igmp Snooping Proxying

    suppression mechanism causes all attached hosts that monitor the reported multicast address to suppress their own reports. This makes this router unable to know whether the reported multicast group still has active members attached to that port. For more information about the IGMP report suppression mechanism, see "Configuring IGMP."...
  • Page 151 Figure 45 Network diagram IGMP Querier IP network Router A Query from Router A Report from Switch A Query from Switch A Proxy & Querier Switch A Report from Host Host A Host C Receiver Receiver Host B As shown in Figure 45, Switch A works as an IGMP snooping proxy.

  • Page 152: Protocols And Standards

    Protocols and standards RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches IGMP snooping configuration task list For the configuration tasks in this section, the following rules apply: The configurations made in IGMP-snooping view are effective on all VLANs. The configurations •...

  • Page 153: Configuring Basic Igmp Snooping Functions

    Task Remarks Configuring a multicast group filter Optional. Configuring multicast source port filtering Optional. Enabling dropping unknown multicast data Optional. Enabling IGMP report suppression Optional. Configuring IGMP snooping Setting the maximum number of multicast groups that a policies Optional. port can join a.

  • Page 154: Configuring Igmp Snooping Port Functions

    IGMPv2 snooping can process IGMPv1 and IGMPv2 messages, but flood IGMPv3 messages in the • VLAN instead of processing them. IGMPv3 snooping can process IGMPv1, IGMPv2 and IGMPv3 messages. • If you change IGMPv3 snooping to IGMPv2 snooping, the system does the following: Clears all IGMP snooping forwarding entries that are dynamically added.

  • Page 155: Configuring Static Ports

    Setting aging timers for dynamic ports globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the aging timer for the router-aging-time interval 105 seconds by default. dynamic router ports. Set the aging timer for the host-aging-time interval 260 seconds by default.

  • Page 156: Configuring A Port As A Simulated Member Host

    Step Command Remarks • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 Use either command. interface-number aggregate interface view, or enter port group view. • Enter port group view: port-group manual port-group-name...

  • Page 157: Enabling Igmp Snooping Fast-Leave Processing

    Enabling IGMP snooping fast-leave processing The fast-leave processing feature enables the IGMP snooping-enabled router to process IGMP leave messages quickly. With this feature enabled, when the IGMP snooping-enabled router receives an IGMP leave message on a port, it immediately removes that port from the forwarding entry for the multicast group specified in the message.

  • Page 158: Configuring Igmp Snooping Querier

    To disable a port from becoming a dynamic router port: Step Command Remarks Enter system view. system-view • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 Use either command.

  • Page 159: Configuring Parameters For Igmp Queries And Responses

    To enable IGMP snooping querier: Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable IGMP snooping igmp-snooping querier Disabled by default. querier. Configuring parameters for IGMP queries and responses You can modify the IGMP general query interval based on actual condition of the network. A multicast listening host starts a timer for each multicast group that it has joined when it receives an IGMP query (general query or group-specific query).

  • Page 160: Configuring Source Ip Addresses For Igmp Queries

    To avoid this problem, when a Layer 2 switch acts as the IGMP snooping querier, HP recommends you to configure a non-all-zero IP address as the source IP address of IGMP queries.

  • Page 161: Configuring The Source Ip Addresses For The Igmp Messages Sent By The Proxy

    Step Command Remarks Enter VLAN view. vlan vlan-id Enable IGMP snooping igmp-snooping proxying enable Disabled by default. proxying in the VLAN. Configuring the source IP addresses for the IGMP messages sent by the proxy You can set source the IP addresses for the IGMP reports and leave messages that the IGMP snooping proxy sends on behalf of its attached hosts.

  • Page 162: Configuring Multicast Source Port Filtering

    report message. In this case, the multicast data for the multicast group is not sent to this port, and the user cannot retrieve the program. Configuring a multicast group filter globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping By default, no group filter is Configure a multicast group...

  • Page 163: Enabling Dropping Unknown Multicast Data

    Step Command Remarks Enter IGMP-snooping view. igmp-snooping Enable multicast source port source-deny port interface-list Disabled by default. filtering. Configuring multicast source port filtering on a port Step Command Remarks Enter system view. system-view • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type...

  • Page 164: Enabling Igmp Report Suppression

    MSR20 Feature MSR900 MSR93X MSR30 MSR50 MSR1000 Supported by the MSR30-11E or Enabling MSR30-11F with dropping Supported by fixed switching unknown the FIC interfaces. multicast modules. data in a Not supported by VLAN. the MIM and XMIM modules. NOTE: If you enable the function of dropping unknown multicast packets in the VLAN on an MSR installed with the subcard MIM-16FSW, DMIM-24FSW, FIC-16FSW, or DFIC-24FSW, VLAN interfaces cannot be configured to join the bridge group.

  • Page 165: Setting The Maximum Number Of Multicast Groups That A Port Can Join

    subsequent IGMP reports for the same multicast group. This helps reduce the number of packets being transmitted over the network. On an IGMP snooping proxy, IGMP reports for a multicast group from downstream hosts are suppressed if the forwarding entry for the multicast group exists on the proxy, whether the suppression function is enabled or not.

  • Page 166: Setting The 802.1P Precedence For Igmp Messages

    If the IPv6 multicast group replacement is disabled, the IGMP snooping-enabled router or the port • discards IGMP reports for joining a new IPv6 multicast group. In some specific applications, such as channel switching, a newly joined multicast group must automatically replace an existing multicast group.

  • Page 167: Enabling The Igmp Snooping Host Tracking Function

    Setting the 802.1p precedence for IGMP messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the 802.1p precedence for igmp-snooping dot1p-priority The default 802.1p precedence for IGMP messages in the VLAN. priority-number IGMP messages is 0.

  • Page 168: Igmp Snooping Configuration Examples

    Task Command Remarks Remove all the dynamic group entries of a specified IGMP reset igmp-snooping group { group-address | Available in user snooping group or all IGMP all } [ vlan vlan-id ] view. snooping groups. Clear statistics for the IGMP Available in user messages learned through IGMP reset igmp-snooping statistics...
  • Page 169 On Router A, enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on Ethernet 1/1. <RouterA> system-view [RouterA] multicast routing-enable [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] igmp enable [RouterA-Ethernet1/1] pim dm [RouterA-Ethernet1/1] quit [RouterA] interface ethernet 1/2 [RouterA-Ethernet1/2] pim dm [RouterA-Ethernet1/2] quit Configure Switch A: # Enable IGMP snooping globally.

  • Page 170: Static Port Configuration Example

    Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port. Eth1/1 (D) ( 00:01:30 ) IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 2 port.
  • Page 171 Figure 47 Network diagram Switch B Source Switch A Eth1/2 Eth1/1 1.1.1.2/24 10.1.1.1/24 Eth1/1 Router A 1.1.1.1/24 IGMP querier Switch C Host C Host A Receiver Receiver Host B VLAN 100 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 47.
  • Page 172 [SwitchA] interface ethernet 1/3 [SwitchA-Ethernet1/3] igmp-snooping static-router-port vlan 100 [SwitchA-Ethernet1/3] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, assign Ethernet 1/1 and Ethernet 1/2 to this VLAN, and enable IGMP snooping in the VLAN.

  • Page 173: Igmp Snooping Querier Configuration Example

    Eth1/1 (D) ( 00:01:30 ) Eth1/3 IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 1 port. Eth1/2 (D) ( 00:03:23 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port. Eth1/2 The output shows that Ethernet 1/3 of Switch A has become a static router port.
  • Page 174 As shown in Figure 48, in a Layer 2–only network environment, two multicast sources Source 1 and Source 2 send multicast data to multicast groups 224.1.1.1 and 225.1.1.1, respectively. Host A and Host C are receivers of multicast group 224.1.1.1. Host B and Host D are receivers of multicast group 225.1.1.1. IGMPv2 runs on all the receivers, and IGMPv2 snooping runs on all the switches.

  • Page 175: Igmp Snooping Proxying Configuration Example

    [SwitchA-vlan100] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, and assign Ethernet 1/1 through Ethernet 1/4 to the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port ethernet 1/1 to ethernet 1/4 # Enable IGMP snooping and the function of dropping unknown multicast traffic in VLAN 100.
  • Page 176 Figure 49 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 49. (Details not shown.) On Router A, enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on Ethernet 1/1. <RouterA>...
  • Page 177 Verifying the configuration After the configuration is completed, Host A and Host B send IGMP join messages for group 224.1.1.1. Receiving the messages, Switch A sends a join message for the group out of Ethernet 1/1 (a router port) to Router A. Use the display igmp-snooping group command and the display igmp group command to display information about IGMP snooping groups and IGMP multicast groups.

  • Page 178: Troubleshooting Igmp Snooping

    Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port.
  • Page 179 If only IGMP is enabled on the router, or if both IGMP and PIM are enabled on the router, the router • does the following: Maintains dynamic member ports or dynamic router ports according to IGMP packets Maintains dynamic router ports according to PIM hello packets If only PIM is enabled on the router, the following occur: •...

  • Page 180: Configuring Msdp

    Configuring MSDP Overview MSDP is an inter-domain multicast solution that addresses the interconnection of protocol independent multicast sparse mode (PIM-SM) domains. It discovers multicast source information in other PIM-SM domains. In the basic PIM-SM mode, a multicast source registers only with the RP in the local PIM-SM domain, and the multicast source information about a domain is isolated from that of another domain.
  • Page 181 Figure 50 Where MSDP peers are in the network As shown in Figure 50, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers, that assume different roles, will function differently. MSDP peers on RPs include the following types: Source-side MSDP peer—The MSDP peer nearest to the multicast source (Source), typically the source-side RP, like RP 1.
  • Page 182 Figure 51 Inter-domain multicast delivery through MSDP The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: When the multicast source in PIM-SM 1 sends the first multicast packet to multicast group G, DR 1 encapsulates the multicast data within a register message and sends the register message to RP 1.
  • Page 183 An MSDP mesh group refers to a group of MSDP peers that have MSDP peering relationships among one another and share the same group name. When using MSDP for inter-domain multicasting, once an RP receives information form a multicast source, it no longer relies on RPs in other PIM-SM domains.
  • Page 184 Although RP 4 and RP 5 are in the same AS (AS 3) and both are MSDP peers of RP 6, because RP 5 has a higher IP address, RP 6 accepts only the SA message from RP 5. When RP 7 receives the SA message from RP 6: Because the SA message is from a static RPF peer (RP 6), RP 7 accepts the SA message and forwards it to other peer (RP 8).

  • Page 185: Msdp Support For Vpns

    The working process of Anycast RP is as follows: The multicast source registers with the nearest RP. In this example, Source registers with RP 1, with its multicast data encapsulated in the register message. When the register message arrives at RP 1, RP 1 de-encapsulates the message.

  • Page 186: Msdp Configuration Task List

    MSDP configuration task list Task Remarks Enabling MSDP Required. Configuring basic MSDP Creating an MSDP peer connection Required. functions Configuring a static RPF peer Optional. Configuring MSDP peer description Optional. Configuring an MSDP peer Configuring an MSDP mesh group Optional. connection Configuring MSDP peer connection control Optional.

  • Page 187: Creating An Msdp Peer Connection

    MSDP peers. If an interface of the router is shared by an MSDP peer and a BGP or MBGP peer at the same time, HP recommends that you configure the IP address of the MSDP peer the same as that of the BGP or MBGP peer.

  • Page 188: Configuring An Msdp Peer Connection

    NOTE: If only one MSDP peer is configured on a router, this MSDP peer is registered as a static RPF peer. Configuring an MSDP peer connection This section describes how to configure an MSDP peer connection. Configuration prerequisites Before you configure an MSDP peer connection, complete the following tasks: •...

  • Page 189: Configuring Msdp Peer Connection Control

    Before grouping multiple routers into an MSDP mesh group, make sure these routers are interconnected with one another. To create an MSDP mesh group: Step Command Remarks Enter system view. system-view Enter public network MSDP msdp [ vpn-instance view or VPN instance MSDP vpn-instance-name ] view.

  • Page 190: Configuring Sa Message Related Parameters

    Step Command Remarks Configure the interval Optional. between MSDP peer timer retry interval 30 seconds by default. connection retries. Optional. Configure a password for peer peer-address password MD5 authentication used by By default, MD5 authentication is { cipher cipher-password | simple both MSDP peers to establish not performed before a TCP simple-password }...

  • Page 191: Configuring Sa Request Messages

    Step Command Remarks Enter system view. system-view Enter public network MSDP view or msdp [ vpn-instance VPN instance MSDP view. vpn-instance-name ] Optional. Enable encapsulation of multicast encap-data-enable data in SA messages. Disabled by default. Optional. Configure the interface address as originating-rp interface-type the RP address in SA messages.

  • Page 192: Configuring The Sa Cache Mechanism

    If the TTL value is greater than or equal to the threshold, the router encapsulates the multicast data in an SA message and sends the SA message. After receiving an SA message with an encapsulated multicast data packet, the router decreases the •...

  • Page 193: Displaying And Maintaining Msdp

    Step Command Remarks Optional. Enable the SA cache mechanism. cache-sa-enable Enabled by default. Configure the maximum number of (S, Optional. peer peer-address G) entries learned from the specified sa-cache-maximum sa-limit 8192 by default. MSDP peer that the router can cache. Displaying and maintaining MSDP Task Command...
  • Page 194 Configure Loopback 0 as the C-BSR and C-RP of the related PIM-SM domain on Router B, Router C, and Router E. Set up MSDP peering relationships between the RPs of the PIM-SM domains to share multicast source information among the PIM-SM domains. Figure 54 Network diagram Table 14 shows the interface and IP address assignment, and network topology scheme.
  • Page 195 Device Interface IP address Router E Loopback 0 3.3.3.3/32 Router F Ethernet 1/1 10.110.6.2/24 Router F Ethernet 1/2 10.110.7.1/24 Source 1 — 10.110.2.100/24 Source 2 — 10.110.5.100/24 Configuration procedure Assign IP addresses and configure unicast routing: Assign the IP address and subnet mask to each interface according to Figure 54.
  • Page 196 [RouterB] bgp 100 [RouterB-bgp] router-id 1.1.1.1 [RouterB-bgp] peer 192.168.1.2 as-number 200 [RouterB-bgp] import-route ospf 1 [RouterB-bgp] quit # Configure an eBGP peer, and redistribute OSPF routes on Router C. [RouterC] bgp 200 [RouterC-bgp] router-id 2.2.2.2 [RouterC-bgp] peer 192.168.1.1 as-number 100 [RouterC-bgp] import-route ospf 1 [RouterC-bgp] quit # Redistribute BGP routing information into OSPF on Router B.
  • Page 197 BGP local router ID : 2.2.2.2 Local AS number : 200 Total number of peers : 1 Peers in established state : 1 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.1 1 00:12:04 Established # Display BGP routing table information on Router C. [RouterC] display bgp routing-table Total Number of Routes: 5 BGP Local router ID is 2.2.2.2...

  • Page 198: Inter-As Multicast Configuration By Leveraging Static Rpf Peers

    Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count 192.168.3.1 01:07:08 # Display the detailed MSDP peer information on Router B. [RouterB] display msdp peer-status MSDP Peer Information of VPN-Instance: public net MSDP Peer 192.168.1.2, AS 200 Description: Information about connection status: State: Up...
  • Page 199 configure static RPF peering relationships for the MSDP peers to share multicast source information among the PIM-SM domains. Figure 55 Network diagram AS 100 AS 200 PIM-SM 3 Receiver Router G Eth1/1 Eth1/1 Router F Loop0 Loop0 Receiver Eth1/2 Eth1/1 Router A Router C PIM-SM 2...
  • Page 200 Device Interface IP address Router F Ethernet 1/1 10.110.6.1/24 Router F Serial 2/0 10.110.4.2/24 Router G Ethernet 1/1 10.110.6.2/24 Router G Ethernet 1/2 192.168.4.1/24 Router G Loopback 0 3.3.3.3/32 Configuration procedure Assign IP addresses and configure unicast routing: Assign an IP address and subnet mask to each interface according to Figure 55.
  • Page 201 Configure BGP, and redistribute BGP routing information into OSPF and OSPF routing information into BGP: # Configure an eBGP peer, and redistribute OSPF routing information on Router B. [RouterB] bgp 100 [RouterB-bgp] router-id 1.1.1.2 [RouterB-bgp] peer 10.110.3.2 as-number 200 [RouterB-bgp] import-route ospf 1 [RouterB-bgp] quit # Configure an eBGP peer, and redistribute OSPF routing information on Router D.
  • Page 202 [RouterA-msdp] peer 10.110.3.2 connect-interface ethernet 1/1 [RouterA-msdp] peer 10.110.6.2 connect-interface ethernet 1/2 [RouterA-msdp] static-rpf-peer 10.110.3.2 rp-policy list-dg [RouterA-msdp] static-rpf-peer 10.110.6.2 rp-policy list-dg [RouterA-msdp] quit # Configure Router A as the MSDP peer and static RPF peer of Router D. [RouterD] ip ip-prefix list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32 [RouterD] msdp [RouterD-msdp] peer 10.110.1.1 connect-interface pos 5/0 [RouterD-msdp] static-rpf-peer 10.110.1.1 rp-policy list-a...

  • Page 203: Anycast Rp Configuration

    Peer's Address State Up/Down time SA Count Reset Count 10.110.2.1 00:16:40 Anycast RP configuration Network requirements As shown in Figure 56, the PIM-SM domain in this example has multiple multicast sources and receivers. OSPF runs within the domain to provide unicast routes. Configure the Anycast RP application so that the receiver-side DRs and the source-side DRs can initiate a Join message to their respective RPs that are the topologically nearest to them.
  • Page 204 Device Interface IP address Router B POS 5/0 192.168.1.1/24 Router B Loopback 0 1.1.1.1/32 Router B Loopback 10 3.3.3.3/32 Router B Loopback 20 10.1.1.1/32 Router C POS 5/0 192.168.1.2/24 Router C POS 5/1 192.168.2.2/24 Router D Ethernet 1/1 10.110.3.1/24 Router D Serial 2/0 10.110.4.1/24 Router D...
  • Page 205 [RouterB-LoopBack10] quit [RouterB] interface loopback 20 [RouterB-LoopBack20] pim sm [RouterB-LoopBack20] quit # Enable IP multicast routing, and enable PIM-SM and IGMP on Router A, Router C, Router D, and Router E in the same way. (Details not shown.) Configure C-BSRs and C-RPs: # Configure Loopback 10 as a C-BSR and configure Loopback 20 as a C-RP on Router B.
  • Page 206 [RouterB] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: WC UpTime: 00:15:04 Upstream interface: Register Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1 Protocol: igmp, UpTime: 00:15:04, Expires: -...

  • Page 207: Sa Message Filtering Configuration

    Upstream interface: Register Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1 Protocol: igmp, UpTime: 00:12:07, Expires: - (10.110.6.100, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: SPT 2MSDP ACT UpTime: 00:40:22 Upstream interface: Serial2/0 Upstream neighbor: 10.110.4.2 RPF prime neighbor: 10.110.4.2 Downstream interface(s) information:...
  • Page 208 Figure 57 Network diagram PIM-SM 1 PIM-SM 2 PIM-SM 3 Loop0 Source 2 Eth1/1 Loop0 Receiver Router A S2/1 Host A Eth1/1 Router C S2/1 S2/1 Router D Eth1/1 Eth1/2 Source 1 S2/1 Eth1/1 Router B Receiver Receiver Host B Host C MSDP peers Table 17...
  • Page 209 Configuration procedure Assign IP addresses and configure unicast routing: Assign the IP address and subnet mask to each interface according to Figure 57. (Details not shown.) Configure OSPF on the routers in the PIM-SM domains to make sure the routers are interoperable at the network layer and they can dynamically update routing information.
  • Page 210 Configure MSDP peers: # Configure an MSDP peer on Router A. [RouterA] msdp [RouterA-msdp] peer 192.168.1.2 connect-interface pos 5/1 [RouterA-msdp] quit # Configure MSDP peers on Router C. [RouterC] msdp [RouterC-msdp] peer 192.168.1.1 connect-interface pos 5/1 [RouterC-msdp] peer 10.110.5.2 connect-interface serial 2/1 [RouterC-msdp] quit # Configure an MSDP peer on Router D.

  • Page 211: Troubleshooting Msdp

    (10.110.3.100, 226.1.1.1) 1.1.1.1 02:03:30 00:05:31 (10.110.3.100, 226.1.1.2) 1.1.1.1 02:03:30 00:05:31 (10.110.3.100, 226.1.1.3) 1.1.1.1 02:03:30 00:05:31 # Display the (S, G) entries cached in the SA cache on Router D. [RouterD] display msdp sa-cache MSDP Source-Active Cache Information of VPN-Instance: public net MSDP Total Source-Active Cache - 4 entries MSDP matched 4 entries (Source, Group)

  • Page 212: No Sa Entries Exist In The Router's Sa Cache

    Analysis The import-source command controls sending (S, G) entries through SA messages to MSDP peers. • If this command is executed without the acl-number argument, all the (S, G) entries will be filtered off. Namely, no (S, G) entries of the local domain will be advertised. •...

  • Page 213: Configuring Mbgp

    Configuring MBGP MBGP overview BGP-4 can carry routing information for IPv4 only. IETF defined Multiprotocol Border Gateway Protocol (MP-BGP) to extend BGP-4 so that BGP can carry routing information for multiple network-layer protocols. For a network, the topology for multicast might be different from that for unicast. To distinguish them, the MP-BGP enables BGP to carry the unicast Network Layer Reachability Information (NLRI) and multicast NLRI separately.

  • Page 214: Configuring Basic Mbgp Functions

    Task Remarks Configuring the MED attribute Configuring the NEXT_HOP attribute Configuring the AS_PATH attribute Configuring MBGP soft reset Optional. Optimizing MBGP Enabling the MBGP ORF capability Optional. networks Configuring the maximum number of MBGP routes for load Optional. balancing Configuring IPv4 MBGP peer groups Optional.

  • Page 215: Configuring Mbgp Route Redistribution

    Configuring MBGP route redistribution MBGP can advertise routing information in the local AS to neighboring ASs. It redistributes such routing information from IGP into its routing table rather than learns the information by itself. Follow these guidelines when you configure MBGP route redistribution: •...

  • Page 216: Configuring Mbgp Route Summarization

    Step Command Remarks No route redistribution is import-route protocol [ { process-id configured by default. Enable route redistribution | all-processes } [ allow-direct | The allow-direct keyword is from another routing protocol. med med-value | route-policy available only when the specified route-policy-name ] * ] routing protocol is OSPF.

  • Page 217: Configuring Outbound Mbgp Route Filtering

    Step Command Remarks peer { group-name | ip-address } Advertise a default route to an default-route-advertise Not advertised by default. MBGP peer or peer group. [ route-policy route-policy-name ] NOTE: After you configure the peer default-route-advertise command, the router sends a default route with the next hop as itself to the specified MBGP peer or peer group, whether the default route is available or not in the routing table.

  • Page 218: Configuring Inbound Mbgp Route Filtering

    Step Command Remarks • Configure the filtering of redistributed routes: filter-policy { acl-number | ip-prefix ip-prefix-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] • Apply a routing policy to advertisements to an IPv4 MBGP peer or a peer group: peer { group-name | peer-address } route-policy route-policy-name export •...

  • Page 219: Configuring Mbgp Route Dampening

    Step Command Remarks • Filter incoming routes using an ACL or IP prefix list: filter-policy { acl-number | ip-prefix ip-prefix-name } import • Reference a routing policy to routes from an IPv4 MBGP peer or a peer group: peer { group-name | ip-address } route-policy policy-name import •...

  • Page 220: Configuring Mbgp Route Attributes

    Step Command Remarks Enter IPv4 MBGP address ipv4-family multicast family view. dampening [ half-life-reachable Configure BGP route half-life-unreachable reuse Not configured by default. dampening parameters. suppress ceiling | route-policy route-policy-name ] * Configuring MBGP route attributes You can modify MBGP route attributes to affect route selection. Configuration prerequisites Before you configure this task, you must configure basic MBGP functions.

  • Page 221: Configuring The Med Attribute

    Configuring the MED attribute When other conditions of routes to a destination are identical, the route with the smallest MED is selected. To configure the MED attribute: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address family view. ipv4-family multicast •...

  • Page 222: Configuring The As_Path Attribute

    Step Command Remarks Optional. By default, MBGP specifies the local router as the next Specify the router as the next hop for routes advertised to peer { group-name | ip-address } hop of routes sent to a peer or a a MBGP EBGP peer or a next-hop-local peer group.

  • Page 223: Configuration Prerequisites

    Configuration prerequisites Before you configure this task, configure basic MBGP functions. Configuring MBGP soft reset After modifying a route selection policy, you have to reset MBGP connections to make it take effect. The current MBGP implementation supports the route refresh feature that enables dynamic route refresh without terminating MBGP connections.

  • Page 224: Enabling The Mbgp Orf Capability

    Step Command Remarks Return to user view. return refresh bgp ipv4 multicast { all | Soft-reset MBGP connections ip-address | group group-name | Optional. manually. external | internal } { export | import } Enabling the MBGP ORF capability The MBGP Outbound Router Filter (ORF) feature enables an MBGP speaker to send a set of ORFs to its MBGP peer through route-refresh messages.

  • Page 225: Configuring The Maximum Number Of Mbgp Routes For Load Balancing

    Step Command Remarks Enable the ORF IP prefix peer { group-name | ip-address } Optional. negotiation capability for an capability-advertise orf ip-prefix Not enabled by default. MBGP peer or a peer group. { both | receive | send } Table 18 Description of the both, send, and receive parameters and the negotiation result Local parameter Peer parameter Negotiation result...

  • Page 226: Configuring Mbgp Community

    IMPORTANT: To configure an MBGP peer group, you must enable the corresponding IPv4 BGP unicast peer group in • IPv4 MBGP address family view. Before adding an MBGP peer to an MBGP peer group, you must add the corresponding IPv4 unicast •...

  • Page 227: Configuring An Mbgp Route Reflector

    Step Command Remarks • Advertise the community attribute to an MBGP peer or a peer group: peer { group-name | ip-address } advertise-community Advertise the community Use either method. attribute to an MBGP peer or a • Advertise the extended community Not configured by default.

  • Page 228: Displaying And Maintaining Mbgp

    Displaying and maintaining MBGP Displaying MBGP Task Command Remarks display ip multicast routing-table [ verbose] Display the IPv4 MBGP routing [ | { begin | exclude | include } Available in any view. table. regular-expression ] display ip multicast routing-table ip-address Display the IPv4 MBGP routing [ mask-length | mask ] [ longer-match ] information matching the specified...

  • Page 229: Resetting Mbgp Connections

    Task Command Remarks display bgp multicast routing-table Display MBGP dampened routing dampened [ | { begin | exclude | include } Available in any view. information. regular-expression ] display bgp multicast routing-table Display MBGP dampening dampening parameter [ | { begin | exclude | Available in any view.

  • Page 230: Mbgp Configuration Example

    MBGP configuration example Network requirements PIM-SM 1 is in AS 100, and PIM-SM 2 is in AS 200. OSPF is the IGP in the two ASs, and MBGP runs between the two ASs to exchange multicast route information. The multicast source belongs to PIM-SM 1, and the receiver belongs to PIM-SM 2.
  • Page 231 [RouterA] interface pos 5/0 [RouterA-Pos5/0] pim sm [RouterA-Pos5/0] quit The configuration on Router B and Router D is similar to the configuration on Router A. # Enable IP multicast routing on Router C, enable PIM-SM on each interface, and enable IGMP on the host-side interface Ethernet 1/1.
  • Page 232 # On Router A, configure the MBGP peer and enable direct route redistribution. [RouterA] bgp 100 [RouterA-bgp] router-id 1.1.1.1 [RouterA-bgp] peer 192.168.1.2 as-number 200 [RouterA-bgp] import-route direct [RouterA-bgp] ipv4-family multicast [RouterA-bgp-af-mul] peer 192.168.1.2 enable [RouterA-bgp-af-mul] import-route direct [RouterA-bgp-af-mul] quit [RouterA-bgp] quit # On Router B, configure the MBGP peer and enable route redistribution from OSPF.
  • Page 233 Peer's Address State Up/Down time SA Count Reset Count 192.168.1.1 00:07:17...

  • Page 234: Configuring Multicast Vpn

    Configuring multicast VPN Overview Multicast VPN is a technique that implements multicast delivery in VPNs. A VPN is comprised of multiple sites and the public network provided by the network provider. The sites communicate through the public network. As shown in Figure 59, VPN A comprises Site 1, Site 3 and Site 5, and VPN B comprises Site 2, Site 4 and Site 6.
  • Page 235 Figure 60 Multicast in multiple VPN instances With multicast VPN, when a multicast source in VPN A sends a multicast stream to a multicast group, of all possible receivers on the network for that group, only those that belong to VPN A, namely, in Site 1, Site 3 or Site 5, can receive the multicast stream.

  • Page 236: Md-Vpn Overview

    MD-VPN overview The basic concepts involved in MD-VPN are described in Table Table 19 Basic concepts in MD-VPN Concept Description An MD is a set of VPN instances running on PE devices that can send Multicast domain (MD) multicast traffic to each other. Each MD uniquely corresponds to the same set of VPN instances.
  • Page 237 VPN multicast traffic between the PE devices and the CE devices is transmitted on a per-VPN-instance basis, but the public network multicast traffic between the PE devices and the P devices is transmitted through the public network. • Logically, an MD defines the transmission range of the multicast traffic of a specific VPN over the public network.
  • Page 238 multicast packets transmitted in this VPN are forwarded along this share-MDT, no matter at which PE device they entered the public network. A share-group is assigned a unique switch-group-pool for MDT switchover. When the rate of a VPN • multicast stream that entered the public network at a PE device exceeds the switchover threshold, the PE chooses an idle address (namely, switch-group) from the switch-group-pool, and encapsulates the multicast packets for that VPN using that address.

  • Page 239: Protocols And Standards

    PE-PE neighboring relationship—PIM neighboring relationship established after a VPN instance on • a PE device receives a PIM hello from a VPN instance on a remote PE device through an MTI. PE-CE neighboring relationship—PIM neighboring relationship established between a • VPN-instance-associated interface on a PE device and an interface on a peer CE device.
  • Page 240 All the other PE devices that are running VPN instance A are group members, so that a (11.1.1.1, 239.1.1.1) state entry is created on each device along the path on the public network. This forms an SPT with PE 1 as the root, and PE 2 and PE 3 as leaves. At the same time, PE 2 and PE 3 initiate a similar flood-prune process, respectively.
  • Page 241 Share-MDT establishment in a BIDIR-PIM network Figure 65 Share-MDT establishment in a BIDIR-PIM network As shown in Figure 65, BIDIR-PIM is enabled in the network and all the PE devices support VPN instance A. The process of establishing a share-MDT is as follows: The public network on PE 1 initiates a join to the public network RP, with the share-group address as the multicast group address in the join message, and a (*, 239.1.1.1) entry is created on each device along the path on the public network.
  • Page 242 Share-MDT establishment in a PIM-SSM network Figure 66 Share-MDT establishment in a PIM-SSM network BGP: 11.1.3.1/24 PE 3 Share-Group: 232.1.1.1 Public instance BGP peers SPT (11.1.1.1, 232.1.1.1) SPT (11.1.2.1, 232.1.1.1) SPT (11.1.3.1, 232.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 66, PIM-SSM is enabled in the network and all the PE devices support VPN instance...

  • Page 243: Share-Mdt-Based Delivery

    Share-MDT-based delivery A share-MDT can be used for delivering multicast packets, including both multicast protocol packets and multicast data packets. However, the transmission processes for these two types of multicast packets are different. Delivery of multicast protocol packets To forward the multicast protocol packets of a VPN over the public network, the local PE device encapsulates them into public-network multicast data packets.
  • Page 244 Figure 67 Transmission of multicast protocol packets BGP: 11.1.3.1/24 PE 3 Source Receiver CE 1 CE 2 PE 1 PE 2 Site 1 Site 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 S: 192.1.1.1/24 Public instance BGP peers G: 225.1.1.1 VPN instance join (*, 225.1.1.1) Share-Group: 239.1.1.1 Public instance join (11.1.2.1, 239.1.1.1) The work process of multicast protocol packets is as follows:...
  • Page 245 the remote PE device and transmitted in that VPN site. VPN multicast data flows are forwarded across the public network differently in the following circumstances: If PIM-DM or PIM-SSM is running in the VPN, the multicast source forwards multicast data to the receivers along the VPN SPT across the public network.

  • Page 246: Mdt Switchover

    If the outgoing interface list of the forwarding entry contains an MTI, PE 1 processes the VPN multicast data. Now, the VPN instance on PE 1 considers that the VPN multicast data has been sent out of the MTI. PE 1 encapsulates the multicast data by means of GRE. Its BGP interface address is the multicast source address and the share-group address is the multicast group address, converting it into a normal, public network multicast data packet (11.1.1.1, 239.1.1.1).

  • Page 247: Multi-As Md Vpn

    After the multicast traffic is switched from the share-MDT to the switch-MDT, PE 1 continues sending MDT switchover messages periodically, so that subsequent PE devices with attached receivers can join the switch-MDT. When a downstream PE device has no longer active receivers attached to it, it leaves the switch-MDT.

  • Page 248: Multicast Vpn Configuration Task List

    Because only VPN multicast traffic is forwarded between ASBRs, different PIM modes can run within different ASs. However, the same PIM mode (PIM-DM, PIM-SM, BIDIR-PIM, or PIM-SSM) must run on all interfaces that belong to the same VPN (including interfaces with VPN bindings on ASBRs). Multi-hop EBGP interconnectivity As shown in Figure...

  • Page 249: Enabling Ip Multicast Routing In A Vpn Instance

    Determine the share-group addresses and an MTI numbers. • • Determine the address ranges of switch-group-pools and ACL rules for MDT switchover. Determine the switch-delay period. • Determine the switch-holddown period. • Enabling IP multicast routing in a VPN instance Before you configure any MD-VPN functionality for a VPN, you must enable IP multicast routing in the VPN instance.

  • Page 250: Configuring Mdt Switchover Parameters

    Step Command Remarks Enter system view. system-view Enter VPN instance view. ip vpn-instance vpn-instance-name multicast-domain share-group Configure a share-group No share-group address or MTI group-address binding mtunnel address and an MTI binding. binding is configured. mtunnel-number Configuring MDT switchover parameters In some cases, the traffic rate of the customer network multicast data might fluctuate around the MDT switchover threshold.

  • Page 251: Configuring Bgp Mdt

    When switch-group reuse logging is enabled, the generated group address reuse logging • information will be sent to the information center, where you can configure the rules for outputting the logging information. For more information about the configuration of the information center, see Network Management and Monitoring Configuration Guide.

  • Page 252: Configuring A Bgp Mdt Route Reflector

    NOTE: A BGP MDT peer or peer group is a peer or peer group created in BGP-MDT subaddress family view. Configuring a BGP MDT route reflector BGP MDT peers in the same AS must be fully meshed to maintain connectivity. However, when many BGP MDT peers exist in an AS, connection establishment among them might cause great expenses.

  • Page 253: Multicast Vpn Configuration Examples

    Task Command Remarks display multicast-domain vpn-instance vpn-instance-name switch-group send [ group Display switch-group information group-address | reuse interval | sent by the specified VPN instance vpn-source-address [ mask { mask-length | Available in any view. in the MD. mask } ] | vpn-group-address [ mask { mask-length | mask } ] ] * [ | { begin | exclude | include } regular-expression ] display bgp mdt group [ group-name ] [ |...
  • Page 254 Item Network requirements • Configure OSPF on the public network, and configure RIP between the PE devices and the CE devices. Unicast routing protocols and • Establish BGP peer connections between PE 1, PE 2 and PE 3 on their MPLS respective Loopback 1 and exchange all VPN routes between them.
  • Page 255 Table 20 Interface and IP address assignment Device Interface IP address Device Interface IP address — 10.110.7.2/24 PE 3 Ethernet 1/1 192.168.8.1/24 — 10.110.8.2/24 PE 3 Ethernet 1/2 10.110.5.1/24 — 10.110.1.2/24 PE 3 Ethernet 1/3 10.110.6.1/24 — 10.110.9.2/24 PE 3 Loopback 1 1.1.1.3/32 —...
  • Page 256 # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface Ethernet 1/1. [PE1] interface ethernet 1/1 [PE1-Ethernet1/1] ip address 192.168.6.1 24 [PE1-Ethernet1/1] pim sm [PE1-Ethernet1/1] mpls [PE1-Ethernet1/1] mpls ldp [PE1-Ethernet1/1] quit # Bind Ethernet 1/2 with VPN instance a, configure an IP address and enable IGMP and PIM-SM on the interface.
  • Page 257 # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure RIP. [PE1] rip 2 vpn-instance a [PE1-rip-2] network 10.0.0.0 [PE1-rip-2] import-route bgp [PE1-rip-2] return Configure PE 2: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability.
  • Page 258 # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface Ethernet 1/1. [PE2] interface ethernet 1/1 [PE2-Ethernet1/1] ip address 192.168.7.1 24 [PE2-Ethernet1/1] pim sm [PE2-Ethernet1/1] mpls [PE2-Ethernet1/1] mpls ldp [PE2-Ethernet1/1] quit # Bind Ethernet 1/2 with VPN instance b, configure an IP address and enable PIM-SM on the interface.
  • Page 259 The interface MTI 0 will automatically obtain an IP address after BGP peer configuration on PE 2. This address is the loopback interface address specified in the BGP peer configuration. The PIM mode running on MTI 0 is the same as the PIM mode running on all the interfaces in VPN instance The interface MTI 1 will automatically obtain an IP address after BGP peer configuration on PE 2.
  • Page 260 # Create VPN instance b, configure an RD for it, and create an ingress route and an egress route for it. [PE3] ip vpn-instance b [PE3-vpn-instance-b] route-distinguisher 200:1 [PE3-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE3-vpn-instance-b] vpn-target 200:1 import-extcommunity # Enable IP multicast routing in VPN instance b, configure a share-group address, associate an MTI with the VPN instance, and define the switch-group-pool address range.
  • Page 261 [PE3] pim vpn-instance b [PE3-pim-b] c-bsr loopback 2 [PE3-pim-b] c-rp loopback 2 [PE3-pim-b] quit # Configure BGP. [PE3] bgp 100 [PE3-bgp] group vpn-g internal [PE3-bgp] peer vpn-g connect-interface loopback 1 [PE3-bgp] peer 1.1.1.1 group vpn-g [PE3-bgp] peer 1.1.1.2 group vpn-g [PE3–bgp] ipv4-family vpn-instance a [PE3-bgp-a] import-route rip 2 [PE3-bgp-a] import-route direct...
  • Page 262 [PE3-rip-3] return Configuring the P router: # Enable IP multicast routing, configure an MPLS LSR ID, and enable the LDP capability on the public network. <P> system-view [P] multicast routing-enable [P] mpls lsr-id 2.2.2.2 [P] mpls [P-mpls] quit [P] mpls ldp [P-mpls-ldp] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface Ethernet 1/1.
  • Page 263 [P-ospf-1] area 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255 Configure CE a1: # Enable IP multicast routing. <CEa1> system-view [CEa1] multicast routing-enable # Configure an IP address and enable PIM-SM on Ethernet 1/1. [CEa1] interface ethernet 1/1 [CEa1-Ethernet1/1] ip address 10.110.7.1 24 [CEa1-Ethernet1/1] pim sm [CEa1-Ethernet1/1] quit # Configure an IP address and enable PIM-SM on Ethernet 1/2.
  • Page 264 [CEa2-Ethernet1/1] quit # Configure an IP address and enable PIM-SM on Ethernet 1/2. [CEa2] interface ethernet 1/2 [CEa2-Ethernet1/2] ip address 10.110.4.2 24 [CEa2-Ethernet1/2] pim sm [CEa2-Ethernet1/2] quit # Configure an IP address and enable PIM-SM on Ethernet 1/3. [CEa2] interface ethernet 1/3 [CEa2-Ethernet1/3] ip address 10.110.12.1 24 [CEa2-Ethernet1/3] pim sm [CEa2-Ethernet1/3] quit...
  • Page 265 [CEa3] rip 2 [CEa3-rip-2] network 10.0.0.0 Configure CE b2: # Enable IP multicast routing. <CEb2> system-view [CEb2] multicast routing-enable # Configure an IP address, and enable IGMP and PIM-SM on Ethernet 1/1. [CEb2] interface ethernet 1/1 [CEb2-Ethernet1/1] ip address 10.110.11.1 24 [CEb2-Ethernet1/1] igmp enable [CEb2-Ethernet1/1] pim sm [CEb2-Ethernet1/1] quit...

  • Page 266: Multi-As Md Vpn Configuration Example

    MTunnel address: 1.1.1.3 Multi-AS MD VPN configuration example Network requirements Item Network requirements • In VPN a, S 1 is a multicast source, and R 2 is a receiver. • In VPN b, S 2 is a multicast source, and R 1 is a receiver. Multicast sources •...
  • Page 267 Figure 72 Network diagram Table 21 shows the interface and IP address assignment, and network topology scheme. Table 21 Interface and IP address assignment Device Interface IP address Device Interface IP address — 10.11.5.2/24 — 10.11.8.2/24 — 10.11.6.2/24 — 10.11.7.2/24 PE 1 Ethernet 1/1 10.10.1.1/24...
  • Page 268 [PE1] multicast routing-enable [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls [PE1-mpls] quit [PE1] mpls ldp [PE1-mpls-ldp] quit # Create VPN instance a, configure an RD for it, and create an ingress route and an egress route for it. Enable IP multicast routing in VPN instance a, configure a share-group address, associate an MTI with the VPN instance, and define the switch-group-pool address range.
  • Page 269 [PE1-Ethernet1/3] pim sm [PE1-Ethernet1/3] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [PE1] interface loopback 1 [PE1-LoopBack1] ip address 1.1.1.1 32 [PE1-LoopBack1] pim sm [PE1-LoopBack1] quit # Configure BGP. [PE1] bgp 100 [PE1-bgp] group pe1-pe2 internal [PE1-bgp] peer pe1-pe2 label-route-capability [PE1-bgp] peer pe1-pe2 connect-interface loopback 1 [PE1-bgp] peer 1.1.1.2 group pe1-pe2...
  • Page 270 [PE1-ospf-3] import-route bgp [PE1-ospf-3] area 0.0.0.0 [PE1-ospf-3-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [PE1-ospf-3-area-0.0.0.0] quit [PE1-ospf-3] quit Configure PE 2: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability. <PE2>...
  • Page 271 [PE2] interface ethernet 1/2 [PE2-Ethernet1/2] pim bsr-boundary [PE2-Ethernet1/2] quit # Establish an MSDP peering relationship. [PE2] msdp [PE2-msdp] encap-data-enable [PE2-msdp] peer 1.1.1.3 connect-interface loopback 1 # Configure a static route. [PE2] ip route-static 1.1.1.3 32 ethernet 1/2 192.168.1.2 # Configure BGP. [PE2] bgp 100 [PE2-bgp] import-route ospf 1 [PE2-bgp] group pe2-pe1 internal...
  • Page 272 [PE3] mpls [PE3-mpls] quit [PE3] mpls ldp [PE3-mpls-ldp] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface Ethernet 1/1. [PE3] interface ethernet 1/1 [PE3-Ethernet1/1] ip address 10.10.2.1 24 [PE3-Ethernet1/1] pim sm [PE3-Ethernet1/1] mpls [PE3-Ethernet1/1] mpls ldp [PE3-Ethernet1/1] quit # Configure an IP address, and enable PIM-SM and MPLS on the public network interface Ethernet...
  • Page 273 [PE3-bgp] group pe3-pe4 internal [PE3-bgp] peer pe3-pe4 route-policy map2 export [PE3-bgp] peer pe3-pe4 label-route-capability [PE3-bgp] peer pe3-pe4 connect-interface loopback 1 [PE3-bgp] peer 1.1.1.4 group pe3-pe4 [PE3-bgp] group pe3-pe2 external [PE3-bgp] peer pe3-pe2 as-number 100 [PE3-bgp] peer pe3-pe2 route-policy map1 export [PE3-bgp] peer pe3-pe2 label-route-capability [PE3-bgp] peer pe3-pe2 connect-interface loopback 1 [PE3-bgp] peer 1.1.1.2 group pe3-pe2...
  • Page 274 [PE4-vpn-instance-a] multicast-domain switch-group-pool 225.1.1.0 28 [PE4-vpn-instance-a] quit # Create VPN instance b, configure an RD for it, and create an ingress route and an egress route for it. Enable IP multicast routing in VPN instance b, configure a share-group address, associate an MTI with the VPN instance, and define the switch-group-pool address range.
  • Page 275 [PE4-bgp] peer pe4-pe1 as-number 100 [PE4-bgp] peer pe4-pe1 ebgp-max-hop 255 [PE4-bgp] peer 1.1.1.1 group pe4-pe1 [PE4-bgp] peer pe4-pe1 connect-interface loopback 1 [PE4–bgp] ipv4-family vpn-instance a [PE4-bgp-a] import-route ospf 2 [PE4-bgp-a] import-route direct [PE4-bgp-a] quit [PE4–bgp] ipv4-family vpn-instance b [PE4-bgp-b] import-route ospf 3 [PE4-bgp-b] import-route direct [PE4-bgp-b] quit [PE4–bgp] ipv4-family vpnv4...
  • Page 276 # Configure an IP address and enable PIM-SM on Ethernet 1/2. [CEa1] interface ethernet 1/2 [CEa1-Ethernet1/2] ip address 10.11.1.2 24 [CEa1-Ethernet1/2] pim sm [CEa1-Ethernet1/2] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [CEa1] interface loopback 1 [CEa1-LoopBack1] ip address 2.2.2.2 32 [CEa1-LoopBack1] pim sm [CEa1-LoopBack1] quit...
  • Page 277 # Configure an IP address and enable IGMP and PIM-SM on Ethernet 1/1. [CEa2] interface ethernet 1/1 [CEa2-Ethernet1/1] ip address 10.11.7.1 24 [CEa2-Ethernet1/1] igmp enable [CEa2-Ethernet1/1] pim sm [CEa2-Ethernet1/1] quit # Configure an IP address and enable PIM-SM on Ethernet 1/2. [CEa2] interface ethernet 1/2 [CEa2-Ethernet1/2] ip address 10.11.3.2 24 [CEa2-Ethernet1/2] pim sm...

  • Page 278: Troubleshooting Md-Vpn

    [CEb2-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb2-ospf-1-area-0.0.0.0] quit [CEb2-ospf-1] quit Verifying the configuration # Display the local share-group information of VPN instance a on PE 1. <PE1> display multicast-domain vpn-instance a share-group local MD local share-group information for VPN-Instance: a Share-group: 239.1.1.1 MTunnel address: 1.1.1.1 # Display the local share-group information of VPN instance b on PE 1.

  • Page 279: An Mvrf Cannot Be Created

    enabled on the MTI interface. PIM adjacencies can be established between the same VPN instance on different PE devices only after the MTI interface obtains an IP address and gets PIM enabled. Solution Use the display multicast-domain vpn-instance share-group command to verify that the same share-group address has been configured for the same VPN instance on different PE devices.

  • Page 280: Configuring Mld

    Configuring MLD Overview An IPv6 router uses the MLD protocol to discover the presence of multicast listeners on the directly attached subnets. Multicast listeners are nodes wishing to receive IPv6 multicast packets. Through MLD, the router can learn whether any IPv6 multicast listeners exist on the directly connected subnets, put corresponding records in the database, and maintain timers related to IPv6 multicast addresses.
  • Page 281 Joining an IPv6 multicast group Figure 73 MLD queries and reports IPv6 network Querier Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report As shown in Figure 73, assume that Host B and Host C will receive IPv6 multicast data addressed to IPv6 multicast group G1, and Host A will receive IPv6 multicast data addressed to G2.

  • Page 282: How Mldv2 Works

    The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::2. After receiving the MLD done message, the querier sends a configurable number of multicast-address-specific queries to the group that the host is leaving. The destination address field and group address field of the message are both filled with the address of the IPv6 multicast group that is being queried.

  • Page 283: Mld Message Types

    When MLDv2 is running on the hosts and routers, Host B can explicitly express its interest in the IPv6 multicast data that Source 1 sends to G (denoted as (S1, G)), rather than the IPv6 multicast data that Source 2 sends to G (denoted as (S2, G)). Thus, only IPv6 multicast data from Source 1 will be delivered to Host B.
  • Page 284 Figure 75 MLDv2 query message format Type = 130 Code Checksum Maximum Response Delay Reserved Multicast Address (128 bits) Reserved QQIC Number of Sources (n) Source Address [1] (128 bits) Source Address [n] (128 bits) Table 22 MLDv2 query message field description Field Description Type = 130...
  • Page 285 Field Description • This field is set to 0 in a general query message or a multicast-address-specific query message. Number of Sources • This field represents the number of source addresses in a multicast-address-and-source-specific query message. IPv6 multicast source address in a multicast-address-specific query Source Address( i ) message.

  • Page 286: Mld Ssm Mapping

    MLD SSM mapping The MLD SSM mapping feature enables you to configure static MLD SSM mappings on the last-hop router to provide SSM support for receiver hosts that are running MLDv1. The SSM model assumes that the last-hop router has identified the desired IPv6 multicast sources when receivers join IPv6 multicast groups. When a host that runs MLDv2 joins a multicast group, it can explicitly specify one or more multicast •...

  • Page 287: Mld Proxying

    MLD proxying In a simple tree-shaped topology, you do not need to configure complex IPv6 multicast routing protocols, such as IPv6 PIM, on edge devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the device serves as a proxy for the downstream hosts to send MLD messages, maintain group memberships, and implement IPv6 multicast forwarding based on the memberships.

  • Page 288: Mld Configuration Task List

    MLD configuration task list For the configuration tasks in this section, the following rules apply: In MLD view, the configuration is effective globally. In interface view, the configuration is effective • on only the current interface. The configurations made in interface view take precedence over those in MLD view. If you do not •...

  • Page 289: Enabling Mld

    Determine the maximum number of IPv6 multicast groups that an interface can join. • Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships will be created and maintained. To enable MLD: Step Command Remarks Enter system view. system-view Enable IPv6 multicast multicast ipv6 routing-enable...

  • Page 290: Configuring An Ipv6 Multicast Group Filter

    If the interface is IPv6 PIM-SM enabled, it must be an IPv6 PIM-SM DR. If this interface is MLD enabled but not IPv6 PIM-SM enabled, it must be an MLD querier. For more information about IPv6 PIM-SM and a DR, see "Configuring IPv6 PIM." A static member port does not respond to queries from the MLD querier.

  • Page 291: Adjusting Mld Performance

    Step Command Remarks The default value varies with devices. For more information, see IP Multicast Configure the maximum number of Command Reference. IPv6 multicast groups that the mld group-limit limit This configuration only limits interface can join. the number of IPv6 multicast groups that the interface dynamically joins.

  • Page 292: Configuring Mld Query And Response Parameters

    To enhance device performance, avoid unnecessary costs, and ensure protocol security, configure • the device to discard MLD messages that do not carry the Router-Alert option. Configuring Router-Alert option handling methods globally Step Command Remarks Enter system view. system-view Enter MLD view. Configure the interface to By default, the device does not discard any MLD message...
  • Page 293 To speed up the response of hosts to MLD queries and avoid simultaneous timer expirations causing MLD report traffic bursts, you must correctly set the maximum response delay: For MLD general queries, the maximum response delay is set by the max-response-time command. •...

  • Page 294: Enabling Mld Fast-Leave Processing

    Configuring MLD query and response parameters on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number 2 by default. A higher robustness variable Configure the MLD querier's mld robust-count robust-value makes the MLD querier more robustness variable.

  • Page 295: Enabling The Mld Host Tracking Function

    Step Command Remarks Enter MLD view. Enable MLD fast-leave fast-leave [ group-policy Disabled by default. processing. acl6-number ] Enabling MLD fast-leave processing on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable MLD fast-leave mld fast-leave [ group-policy Disabled by default.

  • Page 296: Enabling Mld Ssm Mapping

    Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the • domain can be interoperable at the network layer. Configure basic MLD functions. • Enabling MLD SSM mapping Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 297: Enabling Mld Proxying

    Enabling MLD proxying You can enable MLD proxying on the interface in the direction toward the root of the multicast forwarding tree to make the device serve as an MLD proxy. Configuration guidelines Each device can have only one interface serving as the MLD proxy interface. •...

  • Page 298: Displaying And Maintaining Mld

    Displaying and maintaining MLD CAUTION: The reset mld group command might cause IPv6 multicast transmission failures. To display and maintain MLD: Task Command Remarks display mld group [ ipv6-group-address | interface Available in any interface-type interface-number ] [ static | verbose ] [ | Display MLD group information.

  • Page 299: Mld Configuration Examples

    Task Command Remarks Available in user view. Remove the dynamic Layer 2 port This command reset mld group port-info { all | ipv6-group-address } entries of a specified MLD group cannot remove [ vlan vlan-id ] or all MLD groups. the Layer 2 port entries of MLD groups.
  • Page 300 Figure 79 Network diagram Receiver IPv6 PIM network Host A POS5/0 Eth1/1 3000::12/64 Router A Host B Querier Eth1/1 3001::10/64 Receiver POS5/0 Host C Router B Eth1/1 3001::12/64 POS5/0 Host D Router C Configuration procedure Enable IPv6 forwarding, assign IPv6 addresses, and configure IPv6 unicast routing: Enable IPv6 forwarding on each router and assign an IPv6 address and prefix length to each interface according to Figure...

  • Page 301: Mld Ssm Mapping Configuration Example

    [RouterB-Pos5/0] pim ipv6 dm [RouterB-Pos5/0] quit # Enable IPv6 multicast routing on Router C, enable IPv6 PIM-DM on each interface, and enable MLD on the host-side interface Ethernet 1/1. <RouterC> system-view [RouterC] multicast ipv6 routing-enable [RouterC] interface ethernet 1/1 [RouterC-Ethernet1/1] mld enable [RouterC-Ethernet1/1] pim ipv6 dm [RouterC-Ethernet1/1] quit [RouterC] interface pos 5/0...
  • Page 302 Figure 80 Network diagram Table 24 shows the interface and IPv6 address assignment, and network topology scheme. Table 24 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Source 1 — 1001::1/64 Source 3 — 3001::1/64 Source 2 —...
  • Page 303 [RouterD] interface ethernet 1/2 [RouterD-Ethernet1/2] pim ipv6 sm [RouterD-Ethernet1/2] quit [RouterD] interface ethernet 1/3 [RouterD-Ethernet1/3] pim ipv6 sm [RouterD-Ethernet1/3] quit # Enable IPv6 multicast routing on Router A, and enable IPv6 PIM-SM on each interface. <RouterA> system-view [RouterA] multicast ipv6 routing-enable [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] pim ipv6 sm [RouterA-Ethernet1/1] quit...

  • Page 304: Mld Proxying Configuration Example

    # Display information about the IPv6 multicast groups created based on the configured MLD SSM mappings on Router D. [RouterD] display mld ssm-mapping group Total 1 MLD SSM-mapping Group(s). Interface group report information Ethernet1/1(4001::2): Total 1 MLD SSM-mapping Group reported Group Address: FF3E::101 Last Reporter: 4001::1 Uptime: 00:02:04...
  • Page 305 Figure 81 Network diagram Configuration procedure Enable IPv6 forwarding on each router and assign an IPv6 address and prefix length to each interface according to Figure 81. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-DM, MLD, and MLD proxying: # Enable IPv6 multicast routing on Router A, IPv6 PIM-DM on Serial 2/1, and MLD on Ethernet 1/1.

  • Page 306: Troubleshooting Mld

    Current MLD version is 1 Multicast routing on this interface: enabled Require-router-alert: disabled # Display MLD group information on Router A. [RouterA] display mld group Total 1 MLD Group(s). Interface group report information Ethernet1/1(2001::1): Total 1 MLD Groups reported Group Address Last Reporter Uptime Expires...

  • Page 307: Membership Information Is Inconsistent On The Routers On The Same Subnet

    restrict the host from joining IPv6 multicast group G, the ACL must be modified to allow IPv6 multicast group G to receive report messages. Membership information is inconsistent on the routers on the same subnet Symptom The MLD routers on the same subnet have different membership information. Analysis •...

  • Page 308: Configuring Ipv6 Pim

    Configuring IPv6 PIM Overview IPv6 PIM provides IPv6 multicast forwarding by leveraging IPv6 unicast static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as RIPng, OSPFv3, IS-ISv6, or BGP4+. IPv6 PIM uses an IPv6 unicast routing table to perform RPF check to implement IPv6 multicast forwarding. Independent of the IPv6 unicast routing protocols running on the device, IPv6 multicast routing can be implemented as long as the corresponding IPv6 multicast routing entries are created through IPv6 unicast routes.
  • Page 309 Assert • Neighbor discovery In an IPv6 PIM domain, a PIM router discovers IPv6 PIM neighbors, maintains IPv6 PIM neighboring relationship with other routers, and builds and maintains SPTs by periodically multicasting IPv6 PIM hello messages to all other IPv6 PIM routers on the local subnet. Every IPv6 PIM enabled interface on a router sends hello messages periodically, and, therefore, learns the IPv6 PIM neighboring information pertinent to the interface.
  • Page 310 The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again when it no longer has any multicast receiver. NOTE: Pruning has a similar implementation in IPv6 PIM-SM. Graft When a host attached to a pruned node joins an IPv6 multicast group, to reduce the join latency, IPv6 PIM-DM uses the graft mechanism to resume IPv6 multicast data forwarding to that branch.

  • Page 311: Ipv6 Pim-Sm Overview

    The assert message contains the multicast source address (S), the multicast group address (G), and the preference and metric of the IPv6 unicast route/IPv6 MBGP route/IPv6 multicast static route to the source. The routers compare these parameters, and either Router A or Router B becomes the unique forwarder of the subsequent (S, G) IPv6 multicast packets on the shared-media subnet.
  • Page 312 Switchover to SPT • • Assert Neighbor discovery IPv6 PIM-SM uses the similar neighbor discovery mechanism as IPv6 PIM-DM does. For more information, "Neighbor discovery." DR election IPv6 PIM-SM also uses hello messages to elect a DR for a shared-media network (such as a LAN). The elected DR will be the only IPv6 multicast forwarder on this shared-media network.
  • Page 313 specified on each router in the IPv6 PIM-SM domain. An RP can serve multiple IPv6 multicast groups, but a given IPv6 multicast group can have only one RP to serve it at a time. In most cases, however, an IPv6 PIM-SM network covers a wide area and a huge amount of IPv6 multicast traffic must be forwarded through the RP.
  • Page 314 Value Description The digest from the exclusive-or (XOR) operation between the 32-bit segments of the IPv6 multicast group address. For example, if the IPv6 multicast address is FF0E:C20:1A3:63::101, G = 0xFF0E0C20 XOR 0x01A30063 XOR 0x00000000 XOR 0x00000101. Hash mask length. The digest from the exclusive-or (XOR) operation between the 32-bit segments of the C-RP IPv6 address.
  • Page 315 As shown in Figure 86, the process of building an RPT is as follows: When a receiver joins the IPv6 multicast group G, it uses an MLD report message to inform the directly connected DR. After getting the IPv6 multicast group G's receiver information, the DR sends a join message, which is forwarded hop-by-hop to the RP that corresponds to the multicast group.
  • Page 316 Sends an (S, G) join message hop-by-hop toward the IPv6 multicast source. The routers along the path from the RP to the IPv6 multicast source form an SPT branch. Each router on this branch generates an (S, G) entry in its forwarding table. The source-side DR is the root of the SPT, and the RP is the leaf of the SPT.

  • Page 317: Ipv6 Bidir-Pim Overview

    IPv6 PIM-SM builds SPTs through SPT switchover more economically than IPv6 PIM-DM does through the flood-and-prune mechanism. Assert IPv6 PIM-SM uses a similar assert mechanism as IPv6 PIM-DM does. For more information, see "Assert." IPv6 BIDIR-PIM overview In some many-to-many applications, such as multi-side video conference, there might be multiple receivers interested in multiple IPv6 multicast sources simultaneously.
  • Page 318 Figure 88 DF election Router E Router D Router B Router C Ethernet DF election message IPv6 Multicast packets Router A Source As shown in Figure 88, without the DF election mechanism, both Router B and Router C can receive multicast packets from Router A, and they might both forward the packets to downstream routers on the local subnet.
  • Page 319 Figure 89 RPT building at the receiver side As shown in Figure 89, the process for building a receiver-side RPT is similar to that for building an RPT in IPv6 PIM-SM: When a receiver joins IPv6 multicast group G, it uses an MLD message to inform the directly connected router.

  • Page 320: Ipv6 Administrative Scoping Overview

    Figure 90 RPT building at the multicast source side As shown in Figure 90, the process of building a source-side RPT is relatively simple: When an IPv6 multicast source sends IPv6 multicast packets to IPv6 multicast group G, the DF in each network segment unconditionally forwards the packets to the RP.
  • Page 321 cannot cross the IPv6 admin-scoped zone boundary. IPv6 multicast group ranges served by different IPv6 admin-scoped zones can overlap. An IPv6 multicast group is valid only within its local IPv6 admin-scoped zone, functioning as a private group address. The IPv6 global-scoped zone maintains a BSR, which serves the IPv6 multicast groups with the Scope field in their group addresses being 14.

  • Page 322: Ipv6 Pim-Ssm Overview

    Figure 92 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone.
  • Page 323 Neighbor discovery IPv6 PIM-SSM uses the same neighbor discovery mechanism as in IPv6 PIM-SM. For more information, "Neighbor discovery." DR election IPv6 PIM-SSM uses the same DR election mechanism as in IPv6 PIM-SM. For more information, see "DR election." SPT building The decision to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver will join falls into the IPv6 SSM group range.

  • Page 324: Relationship Among Ipv6 Pim Protocols

    Relationship among IPv6 PIM protocols In an IPv6 PIM network, IPv6 PIM-DM cannot work with IPv6 PIM-SM, IPv6 BIDIR-PIM, or IPv6 PIM-SSM. However, IPv6 PIM-SM, IPv6 BIDIR-PIM, and IPv6 PIM-SSM can work together. When they work together, which one is chosen for a receiver trying to join a group depends, as shown in Figure For more information about MLD SSM mapping, see "Configuring MLD."...

  • Page 325: Configuration Prerequisites

    Task Remarks Enabling state-refresh capability Optional. Configuring state-refresh parameters Optional. Configuring IPv6 PIM-DM graft retry period Optional. Configuring common IPv6 PIM features Optional. Configuration prerequisites Before you configure IPv6 PIM-DM, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer.

  • Page 326: Configuring State-Refresh Parameters

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Enable the state-refresh pim ipv6 state-refresh-capable capability. Enabled by default. Configuring state-refresh parameters The router directly connected with the multicast source periodically sends state-refresh messages. You can configure the interval for sending such messages.

  • Page 327: Configuring Ipv6 Pim-Sm

    To configure the IPv6 PIM-DM graft retry period: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the graft retry pim ipv6 timer graft-retry interval period. 3 seconds by default. Configuring IPv6 PIM-SM This section describes how to configure IPv6 PIM-SM. IPv6 PIM-SM configuration task list Task Remarks...

  • Page 328: Enabling Ipv6 Pim-Sm

    Determine the IP address of a static RP and the ACL rule defining the range of IPv6 multicast groups • to be served by the static RP. Determine the C-RP priority and the ACL rule defining the range of IPv6 multicast groups to be •...
  • Page 329 RP-set, which is flooded throughout the entire network. Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-Set. HP recommends that you configure C-RPs on backbone routers.
  • Page 330 Enabling embedded RP When the embedded RP feature is enabled, the router can resolve the RP address directly from the IPv6 multicast group address of an IPv6 multicast packets. This RP can replace the statically configured RP or the RP dynamically calculated based on the BSR mechanism. Thus, the DR does not need to know the RP address beforehand.

  • Page 331: Configuring A Bsr

    Configuring a BSR An IPv6 PIM-SM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR. Elected from C-BSRs, the BSR is responsible for collecting and advertising RP information in the IPv6 PIM-SM domain. Configuring a C-BSR You should configure C-BSRs on routers in the backbone network.
  • Page 332 Configuring an IPv6 PIM domain border As the administrative core of an IPv6 PIM-SM domain, the BSR sends the collected RP-set information in the form of bootstrap messages to all routers in the IPv6 PIM-SM domain. An IPv6 PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope. IPv6 PIM domain border interfaces partition a network into different IPv6 PIM-SM domains.
  • Page 333 Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. By default, the BS period is determined by the formula "BS period = (BS timeout timer – 10) / 2." The default BS timeout timer is Configure the BS period.

  • Page 334: Configuring Ipv6 Administrative Scoping

    To disable the BSM semantic fragmentation function: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Disable the BSM semantic By default, the BSM semantic undo bsm-fragment enable fragmentation function. fragmentation function is enabled. Configuring IPv6 administrative scoping With IPv6 administrative scoping disabled, an IPv6 PIM-SM domain has only one BSR.

  • Page 335: Configuring Ipv6 Multicast Source Registration

    Configuring C-BSRs for IPv6 admin-scoped zones In a network with IPv6 administrative scoping enabled, BSRs are elected from C-BSRs specific to different Scope field values. C-RPs in the network send advertisement messages to the specific BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the specific admin-scoped zone.

  • Page 336: Configuring Switchover To Spt

    The register-stop timer is set to a random value chosen uniformly from the interval (0.5 times register_suppression_time, 1.5 times register_suppression_time) minus register_probe_time. Configure a filtering rule for register messages on all C-RP routers and configure them to calculate the checksum based on the entire register messages. Configure the register suppression time and the register probe time on all routers that might become IPv6 source-side DRs.

  • Page 337: Configuring Ipv6 Bidir-Pim

    Configuring IPv6 BIDIR-PIM This section describes how to configure IPv6 BIDIR-PIM. IPv6 BIDIR-PIM configuration task list Task Remarks Enabling IPv6 PIM-SM Required. Enabling IPv6 BIDIR-PIM Required. Configuring a static RP Required. Configuring a C-RP Use any method. Configuring an RP Enabling embedded RP Configuring C-RP timers globally Optional.

  • Page 338: Enabling Ipv6 Pim-Sm

    Determine the BS timeout timer. • Enabling IPv6 PIM-SM You must enable IPv6 PIM-SM before enabling IPv6 BIDIR-PIM because IPv6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM. To deploy an IPv6 BIDIR-PIM domain, enable IPv6 PIM-SM on all non-border interfaces of the domain.
  • Page 339 It organizes the information into an RP-set, which is flooded throughout the entire network. Then, the other routers in the network calculate the mappings between specific group ranges and the corresponding RPs based on the RP-set. HP recommends that you configure C-RPs on backbone routers.

  • Page 340: Configuring A Bsr

    To enable embedded RP: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. By default, embedded RP is Enable embedded RP. embedded-rp [ acl6-number ] enabled for IPv6 multicast groups in the default embedded RP address scopes.
  • Page 341 When a C-BSR receives the bootstrap message of another C-BSR, it first compares its own priority • with the other C-BSR's priority carried in message. The C-BSR with a higher priority wins. If a tie exists in the priority, the C-BSR with a higher IPv6 address wins. The loser uses the winner's BSR address to replace its own BSR address and no longer assumes itself to be the BSR, and the winner retains its own BSR address and continues assuming itself to be the BSR.
  • Page 342 To configure an IPv6 BIDIR-PIM domain border: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure an IPv6 BIDIR-PIM By default, no IPv6 BIDIR-PIM pim ipv6 bsr-boundary domain border. domain border is configured. Configuring C-BSR parameters globally In each IPv6 BIDIR-PIM domain, a unique BSR is elected from C-BSRs.
  • Page 343 Step Command Remarks Optional. By default, the BS period is determined by the formula "BS period = (BS timeout timer – 10) / 2." The default BS timeout timer is Configure the BS period. c-bsr interval interval 130 seconds, so the default BS period is (130 –...

  • Page 344: Configuring Ipv6 Administrative Scoping

    Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Disable the BSM semantic By default, the BSM semantic undo bsm-fragment enable fragmentation function. fragmentation function is enabled. Configuring IPv6 administrative scoping When administrative scoping is disabled, an IPv6 BIDIR-PIM domain has only one BSR. The BSR manages the whole network.

  • Page 345: Configuring Ipv6 Pim-Ssm

    advertisement messages to form an RP-set and advertises it to all routers in the specific admin-scoped zone. All the routers use the same hash algorithm to get the RP address corresponding to the specific multicast group. The following rules apply to the hash mask length and C-BSR priority: You can configure the hash mask length and C-BSR priority globally and for an IPv6 admin-scoped •...

  • Page 346: Enabling Ipv6 Pim-Sm

    Enabling IPv6 PIM-SM The implementation of the SSM model is based on some subsets of IPv6 PIM-SM. Therefore, you must enable IPv6 PIM-SM before configuring IPv6 PIM-SSM. When you deploy an IPv6 PIM-SSM domain, enable IPv6 PIM-SM on all non-border interfaces of routers. IMPORTANT: All the interfaces on a device must be enabled with the same IPv6 PIM mode.

  • Page 347: Configuration Task List

    The configurations made in IPv6 PIM view are effective on all interfaces. The configurations made • in interface view are effective only on the current interface. A configuration made in interface view always has priority over the same configuration made in •...

  • Page 348: Configuring A Hello Message Filter

    multicast data. In other words, IPv6 PIM routers can act as IPv6 multicast data filters. These filters can help implement traffic control and also control the information available to downstream receivers to enhance data security. Generally, a smaller distance from the filter to the IPv6 multicast source results in a more remarkable filtering effect.
  • Page 349 Holdtime—IPv6 PIM neighbor lifetime. If a router receives no hello message from a neighbor when • the neighbor lifetime expires, it regards the neighbor failed or unreachable. LAN_Prune_Delay—Delay of forwarding prune messages on a shared-media LAN. This option • consists of LAN delay (namely, prune message delay), override interval, and neighbor tracking support (namely, the capability to disable join message suppression).

  • Page 350: Setting The Prune Delay Timer

    Configuring hello options on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. pim ipv6 hello-option dr-priority Set the DR priority. priority 1 by default. Optional. pim ipv6 hello-option holdtime Set the neighbor lifetime. interval 105 seconds by default.
  • Page 351 An IPv6 PIM router periodically sends join/prune messages to its upstream for state update. A join/prune message contains the join/prune timeout timer. The upstream router sets a join/prune timeout timer for each pruned downstream interface. Any router that has lost assert election will prune its downstream interface and maintain the assert state for a period of time.

  • Page 352: Configuring Join/Prune Message Sizes

    Step Command Remarks Optional. Configure assert timeout pim ipv6 holdtime assert interval timer. 180 seconds by default. Configuring join/prune message sizes A large size of a join/prune message might result in loss of a larger amount of information if a message is lost.

  • Page 353: Displaying And Maintaining Ipv6 Pim

    Displaying and maintaining IPv6 PIM Task Command Remarks Display information about the BSR in the IPv6 PIM-SM domain display pim ipv6 bsr-info [ | { begin | exclude | Available in any and the locally configured include } regular-expression ] view.

  • Page 354: Ipv6 Pim Configuration Examples

    IPv6 PIM configuration examples This section provides examples of configuring IPv6 PIM on routers. IPv6 PIM-DM configuration example Network requirements The receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and at least one receiver host exists in each stub network. The entire IPv6 PIM domain operates in the dense mode.
  • Page 355 Device Interface IPv6 address Router D Ethernet 1/1 4001::1/64 Router D Serial 2/0 1002::2/64 Router D POS 5/0 2002::2/64 Router D POS 5/1 3001::2/64 Configuration procedure Enable IPv6 forwarding on each router and assign an IPv6 address and prefix length to each interface according to Figure 95.
  • Page 356 [RouterD] display pim ipv6 interface Interface NbrCnt HelloInt DR-Pri DR-Address Eth1/1 4001::1 (local) Ser2/0 1002::2 (local) Pos5/0 2002::2 (local) Pos5/1 3001::2 (local) # Display IPv6 PIM neighboring relationship on Router D. [RouterD] display pim ipv6 neighbor Total Number of Neighbors = 3 Neighbor Interface Uptime...

  • Page 357: Ipv6 Pim-Sm Non-Scoped Zone Configuration Example

    # Display IPv6 PIM multicast routing table information on Router D. [RouterD] display pim ipv6 routing-table Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF0E::101) Protocol: pim-dm, Flag: LOC ACT UpTime: 00:02:19 Upstream interface: Ethernet1/1 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 2...
  • Page 358 Figure 96 Network diagram Table 28 shows the interface and IPv6 address assignment, and network topology scheme. Table 28 Interface and IPv6 address assignment Device Interface IPv6 address Router A Ethernet 1/1 1001::1/64 Router A Serial 2/0 1002::1/64 Router A POS 5/0 1003::1/64 Router B...
  • Page 359 Configuration procedure Enable IPv6 forwarding on each router and configure the IPv6 address and prefix length for each interface according to Figure 96. (Details not shown.) Configure OSPFv3 on the routers in the IPv6 PIM-DM domain to ensure network-layer reachability among them.
  • Page 360 Verifying the configuration Use the display pim ipv6 interface command to display IPv6 PIM information on each interface. For example: # Display IPv6 PIM information on Router A. [RouterA] display pim ipv6 interface Interface NbrCnt HelloInt DR-Pri DR-Address Eth1/1 1001::1 (local) Ser2/0 1002::2...
  • Page 361 Hash mask length: 128 State: Elected Candidate RP: 1003::2(Pos5/2) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:48 # Display RP information on Router A. [RouterA] display pim ipv6 rp-info PIM-SM BSR RP information: prefix/prefix length: FF0E::101/64 RP: 4002::1 Priority: 192 HoldTime: 130...

  • Page 362: Ipv6 Pim-Sm Admin-Scoped Zone Configuration Example

    RP: 1003::2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:02:15 Upstream interface: Serial2/0 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1 Protocol: pim-sm, UpTime: 00:02:15, Expires: 00:03:06 # Display IPv6 PIM multicast routing table information on Router D. [RouterD] display pim ipv6 routing-table Total 0 (*, G) entry;...
  • Page 363 Source 1 and Source 2 send different multicast information to FF14::101. Host A receives the multicast information from Source 1 only, and Host B receives the multicast information from Source 2 only. Source 3 sends multicast information to FF1E::202. Host C is a multicast receiver for this multicast group. Serial 2/1 of Router B acts as a C-BSR and C-RP of IPv6 admin-scoped zone 1, which serve the IPv6 multicast groups with the Scope field value in their group addresses being 4.
  • Page 364 Device Interface IPv6 address Device Interface IPv6 address Router C S2/1 3002::1/64 Router F POS5/1 6002::2/64 Router C S2/2 3003::1/64 Router F POS5/2 2003::2/64 Router C POS5/1 2002::2/64 Router G Eth1/1 9001::1/64 Router C POS5/2 3004::1/64 Router G S2/1 8001::2/64 Router H S2/1 4001::1/64...
  • Page 365 [RouterB-Serial2/1] quit [RouterB] interface pos 5/1 [RouterB-Pos5/1] pim ipv6 sm [RouterB-Pos5/1] quit [RouterB] interface pos 5/2 [RouterB-Pos5/2] pim ipv6 sm [RouterB-Pos5/2] quit # Enable IPv6 multicast routing and IPv6 administrative scoping, and enable IPv6 PIM-SM on Router C, Router D, Router F, Router G, and Router H in the same way. (Details not shown.) Configure an IPv6 admin-scoped zone boundary: # On Router B, configure POS 5/1 and POS 5/2 as the boundary of IPv6 admin-scoped zone 1.
  • Page 366 [RouterF] pim ipv6 [RouterF-pim6] c-bsr scope global [RouterF-pim6] c-bsr 8001::1 [RouterF-pim6] c-rp 8001::1 [RouterF-pim6] quit Verifying the configuration # Display information about the BSR and locally configured C-RP on Router B. [RouterB] display pim ipv6 bsr-info Elected BSR Address: 8001::1 Priority: 64 Hash mask length: 126 State: Accept Preferred...
  • Page 367 Uptime: 00:03:48 Next BSR message scheduled at: 00:01:12 Candidate BSR Address: 3002::2 Priority: 64 Hash mask length: 126 State: Elected Scope: 4 Candidate RP: 3002::2(Serial2/1) Priority: 192 HoldTime: 130 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:10 # Display information about the BSR and locally configured C-RP on Router F. [RouterF] display pim ipv6 bsr-info Elected BSR Address: 8001::1 Priority: 64...
  • Page 368 Expires: 00:01:51 prefix/prefix length: FF2E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF3E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF4E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF5E::/16 RP: 8001::1 Priority: 192...
  • Page 369 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF9E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFAE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFBE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFCE::/16 RP: 8001::1...
  • Page 370 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF04::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF14::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF24::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF34::/16...
  • Page 371 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF74::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF84::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF94::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51...
  • Page 372 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFE4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFF4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 # Display RP information on Router F. [RouterF] display pim rp-info PIM-SM BSR RP information: prefix/prefix length: FF0E::/16...
  • Page 373 Expires: 00:01:51 prefix/prefix length: FF4E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF5E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF6E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192...

  • Page 374: Ipv6 Bidir-Pim Configuration Example

    Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFBE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFCE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFDE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFEE::/16 RP: 8001::1...
  • Page 375 Figure 98 Network diagram Loop0 Receiver 1 Receiver 2 Router B Eth1/1 S2/2 S2/1 Router C Host A Host B S2/1 S2/2 IPv6 BIDIR-PIM Source 1 Source 2 S2/1 S2/1 Eth1/1 Eth1/2 Router A Router D Table 30 shows the interface and IPv6 address assignment, and network topology scheme. Table 30 Interface and IPv6 address assignment Device Interface...
  • Page 376 # On Router A, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM. <RouterA> system-view [RouterA] multicast ipv6 routing-enable [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] pim ipv6 sm [RouterA-Ethernet1/1] quit [RouterA] interface serial 2/1 [RouterA-Serial2/1] pim ipv6 sm [RouterA-Serial2/1] quit [RouterA] pim ipv6 [RouterA-pim6] bidir-pim enable...
  • Page 377 [RouterD] multicast ipv6 routing-enable [RouterD] interface ethernet 1/1 [RouterD-Ethernet1/1] mld enable [RouterD-Ethernet1/1] pim ipv6 sm [RouterD-Ethernet1/1] quit [RouterD] interface ethernet 1/2 [RouterD-Ethernet1/2] pim ipv6 sm [RouterD-Ethernet1/2] quit [RouterD] interface serial 2/1 [RouterD-Serial2/1] pim ipv6 sm [RouterD-Serial2/1] quit [RouterD] pim ipv6 [RouterD-pim6] bidir-pim enable [RouterD-pim6] quit On Router C, configure Serial 2/1 as a C-BSR, and loopback interface 0 as a C-RP for the entire...
  • Page 378 # Display the DF information of IPv6 BIDIR-PIM on Router D. [RouterD] display pim ipv6 df-info RP Address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Eth1/1 01:19:53 FE80::200:5EFF: FE71:2803 (local) Eth1/2 00:39:34 FE80::200:5EFF: FE71:2802 (local) Ser2/2 Lose 01:21:40 FE80::20F:E2FF: FE15:5602 To display the DF information of the IPv6 multicast forwarding table on a router, use the display multicast ipv6 forwarding-table df-info command.

  • Page 379: Ipv6 Pim-Ssm Configuration Example

    MID: 0, Flags: 0x2100000:0 Uptime: 00:07:21 RPF interface: LoopBack0 List of 2 DF interfaces: 1: Serial2/1 2: Serial2/2 # Display the DF information of the IPv6 multicast forwarding table on Router D. [RouterD] display multicast ipv6 forwarding-table df-info Multicast DF information Total 1 RP Total 1 RP matched 00001.
  • Page 380 Figure 99 Network diagram Table 31 shows the interface and IPv6 address assignment, and network topology scheme. Table 31 Interface and IPv6 address assignment Device Interface IPv6 address Router A Ethernet 1/1 1001::1/64 Router A Serial 2/0 1002::1/64 Router A POS 5/0 1003::1/64 Router B...
  • Page 381 Configuration procedure Enable IPv6 forwarding on each router and configure the IPv6 address and prefix length for each interface according to Figure 99. (Details not shown.) Configure OSPFv3 on the routers in the IPv6 PIM-SSM domain to ensure network-layer reachability among them.

  • Page 382: Troubleshooting Ipv6 Pim

    Assume that Host A needs to receive the information a specific IPv6 multicast source S (4001::100/64) sends to multicast group G (FF3E::101). Router A builds an SPT toward the multicast source. Routers on the SPT path (Router A and Router D) have generated an (S, G) entry, but Router E, which is not on the SPT path, does not have multicast routing entries.

  • Page 383: Ipv6 Multicast Data Is Abnormally Terminated On An Intermediate Router

    IPv6 PIM must be enabled on the RPF interface. An RPF neighbor must be an IPv6 PIM neighbor as • well. If IPv6 PIM is not enabled on the RPF interface or the RPF neighbor, the establishment of a multicast distribution tree will surely fail, resulting in abnormal multicast forwarding. •...

  • Page 384: Rps Cannot Join The Spt In Ipv6 Pim-Sm

    Solution Use the display current-configuration command to check the minimum hop limit value for multicast forwarding. Increase the hop limit value or cancel the configuration of the multicast ipv6 minimum-hoplimit command on the interface. Use the display current-configuration command to verify the IPv6 multicast forwarding boundary settings.
  • Page 385 Solution Use the display ipv6 routing-table command to verify that routes to the RP and the BSR are available on each router, and that a route between the RP and the BSR is available. Make sure each C-RP has a unicast route to the BSR, the BSR has a unicast route to each C-RP, and all the routers in the entire network have a unicast route to the RP.

  • Page 386: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding Overview In IPv6 multicast implementations, the following types of tables implement multicast routing and forwarding: Multicast routing table of an IPv6 multicast routing protocol—Each IPv6 multicast routing protocol • has its own multicast routing table, such as the IPv6 PIM routing table. General IPv6 multicast routing table—The multicast routing information of different IPv6 multicast •...

  • Page 387: Rpf Check Implementation In Ipv6 Multicast

    The router selects one of the optimal routes as the RPF route according to the following principles: If the router uses the longest prefix match principle, it selects the longest matching route as the RPF route. If the routes have the same prefix length, the router selects the route that has a higher priority as the RPF route.

  • Page 388: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

    Figure 100 RPF check process IPv6 Routing Table on Router C Receiver Router B Destination/Prefix Interface 2000::/16 POS5/1 POS5/0 Source Router A 2000::101/16 Receiver POS5/0 POS5/1 IPv6 Multicast packets Router C When POS 5/1 of Router C receives an IPv6 multicast packet, because the interface is the incoming interface of the (S, G) entry, the router forwards the packet to all outgoing interfaces.

  • Page 389: Configuration Task List

    across the tunnel through unicast routers. Then, Router B strips off the unicast IPv6 header and continues to forward the IPv6 multicast data down toward the receivers. Configuration task list Task Remarks Enabling IPv6 multicast routing Required. Configuring an IPv6 multicast routing policy Optional.

  • Page 390: Configuring An Ipv6 Multicast Forwarding Range

    Step Command Remarks Enter system view. system-view Optional. Configure the device to select The route with the highest priority is the RPF route based on the multicast ipv6 longest-match selected as the RPF route by longest match. default. Optional. Configure IPv6 multicast load multicast ipv6 load-splitting splitting.

  • Page 391: Configuring The Ipv6 Multicast Forwarding Table Size

    Step Command Remarks • Configure an IPv6 multicast forwarding boundary: multicast ipv6 boundary { ipv6-group-address prefix-length | scope { scope-id Use either method. | admin-local | global | organization-local | • By default, no forwarding Configure an IPv6 multicast site-local } } boundary is configured.

  • Page 392: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding

    Step Command Remarks Configure the maximum Optional. number of downstream nodes multicast ipv6 forwarding-table for a single IPv6 multicast downstream-limit limit The default is 128. forwarding entry. Displaying and maintaining IPv6 multicast routing and forwarding CAUTION: The reset commands might cause IPv6 multicast transmission failures. To display and maintain IPv6 multicast routing and forwarding: Task Command...

  • Page 393: Ipv6 Multicast Forwarding Over Gre Tunnel Configuration Example

    Task Command Remarks display mac-address [ mac-address [ vlan vlan-id ] Display IPv6 static multicast | [ multicast ] [ vlan vlan-id ] [ count ] ] [ | { begin Available in user view. MAC address entries. | exclude | include } regular-expression ] Available in user view.
  • Page 394 Configure the IP address and prefix length for each interface as shown in Figure 102. (Details not shown.) Configure a GRE tunnel: # On Router A, create interface Tunnel 0 and assign an IPv6 address and prefix length to it. <RouterA>...
  • Page 395 [RouterB-Ethernet1/2] quit # Configure OSPFv3 on Router C. [RouterC] ospfv3 1 [RouterC-ospfv3-1] router-id 3.3.3.3 [RouterC-ospfv3-1] quit [RouterC] interface ethernet 1/1 [RouterC-Ethernet1/1] ospfv3 1 area 0 [RouterC-Ethernet1/1] quit [RouterC] interface ethernet 1/2 [RouterC-Ethernet1/2] ospfv3 1 area 0 [RouterC-Ethernet1/2] quit [RouterC] interface tunnel 0 [RouterC-Tunnel0] ospfv3 1 area 0 [RouterC-Tunnel0] quit Enable IPv6 multicast routing, IPv6 PIM-DM, and MLD:...

  • Page 396: Troubleshooting Abnormal Termination Of Ipv6 Multicast Data

    (*,FF1E::101) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Ethernet1/1 Protocol: igmp, UpTime: 00:04:25, Expires: never (1001::100, FF1E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel0 Upstream neighbor: 5001::1 RPF prime neighbor: 5001::1...
  • Page 397 Solution Use the debugging mfib ipv6 command to display the debugging information. If IPv6 multicast packets are found to have been discarded because of too small hop limit value, use the display multicast ipv6 minimum-hoplimit command to view the minimum hop limit required for an IPv6 multicast packet to be forwarded.

  • Page 398: Configuring Mld Snooping

    Configuring MLD snooping Hardware compatibility • MLD snooping is available only on the MSR series routers with fixed Layer 2 switching interfaces or Layer 2 switching interface modules. The MSR-900 and MSR20- 1 routers do not support MLD snooping. • Overview MLD snooping is an IPv6 multicast constraining mechanism that runs on Layer 2 devices to manage and control IPv6 multicast groups.

  • Page 399: Basic Mld Snooping Concepts

    Basic MLD snooping concepts MLD snooping related ports As shown in Figure 104, Router A connects to the multicast source, MLD snooping runs on Switch A and Switch B, and Host A and Host C are receiver hosts (namely, members of an IPv6 multicast group). Figure 104 MLD snooping related ports As shown in Figure...

  • Page 400: How Mld Snooping Works

    Aging timers for dynamic ports in MLD snooping Table 32 Aging timers for dynamic ports in MLD snooping and related messages and actions Message before Timer Description Action after expiration expiration When a port receives an MLD general query with the source address other than 0::0 or IPv6 MLD general query with The switch removes this...

  • Page 401: Mld Snooping Proxying

    If no forwarding entry matches the group address, the switch creates a forwarding entry for the • group, adds the port that received the MLD report as a dynamic member port to the forwarding entry for the group, and starts an aging timer for the port. •...
  • Page 402 Even though an MLD snooping proxy is a host from the perspective of its upstream device, the MLD report suppression mechanism for hosts does not take effect on it. For more information about the MLD report suppression mechanism for hosts, see "Configuring MLD." Figure 105 Network diagram As shown in Figure...

  • Page 403: Protocols And Standards

    Protocols and standards RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches MLD snooping configuration task list For the configuration tasks in this section, the following rules apply: The configurations made in MLD-snooping view are effective for all VLANs. The configurations •...

  • Page 404: Configuring Basic Mld Snooping Functions

    Task Remarks Setting the maximum number of multicast groups that a port can Optional. join Enabling IPv6 multicast group replacement Optional. Setting the 802.1p precedence for MLD messages Optional. Enabling the MLD snooping host tracking function Optional. Configuring basic MLD snooping functions This section describes how to configure basic MLD snooping functions.

  • Page 405: Configuring Mld Snooping Port Functions

    Clears all MLD snooping forwarding entries that are dynamically created. • • Keeps static MLDv2 snooping forwarding entries (*, G). Clears static MLDv2 snooping forwarding entries (S, G), which will be restored when MLD • snooping is switched back to MLDv2 snooping. For more information about static MLD snooping forwarding entries, see "Configuring static ports."...

  • Page 406: Configuring Static Ports

    Step Command Remarks Set the global aging timer for host-aging-time interval 260 seconds by default. dynamic member ports. Setting the aging timers for the dynamic ports in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the aging timer for the mld-snooping router-aging-time 260 seconds by default.

  • Page 407: Configuring A Port As A Simulated Member Host

    Configuring a port as a simulated member host Generally, a host that runs MLD can respond to MLD queries. If a host fails to respond, the multicast router might deem that the IPv6 multicast group has no members on the subnet, and removes the corresponding forwarding path.

  • Page 408: Disabling A Port From Becoming A Dynamic Router Port

    Enabling MLD snooping fast-leave processing globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Enable MLD snooping fast-leave [ vlan vlan-list ] Disabled by default. fast-leave processing. Enabling MLD snooping fast-leave processing on a port Step Command Remarks Enter system view.

  • Page 409: Configuring Mld Snooping Querier

    Step Command Remarks By default, a port can become a dynamic router Disable the port from port. mld-snooping router-port-deny [ vlan becoming a dynamic router vlan-list ] This configuration does not port. affect the static router port configuration. Configuring MLD snooping querier This section describes how to configure MLD snooping querier.

  • Page 410: Configuring Parameters For Mld Queries And Responses

    Configuring parameters for MLD queries and responses You can modify the MLD general query interval based on the actual condition of the network. A multicast listening host starts a timer for each IPv6 multicast group that it has joined when it receives an MLD query (general query or multicast-address-specific query).

  • Page 411: Configuring Mld Snooping Proxying

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Configure the source IPv6 mld-snooping general-query FE80::02FF:FFFF:FE00:0001 by address for MLD general source-ip { ipv6-address | default. queries. current-interface } Configure the source IPv6 mld-snooping special-query address for MLD FE80::02FF:FFFF:FE00:0001 by source-ip { ipv6-address | multicast-address-specific...

  • Page 412: Configuring An Mld Snooping Policy

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Configure the source IPv6 mld-snooping report source-ip The default is address of MLD reports that { ipv6-address | current-interface } FE80::02FF:FFFF:FE00:0001. the proxy sends. Configure the source IPv6 address of MLD done mld-snooping done source-ip The default is...

  • Page 413: Configuring Ipv6 Multicast Source Port Filtering

    Configuring an IPv6 multicast group filter on a port Step Command Remarks Enter system view. system-view • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 Use either method.

  • Page 414: Enabling Dropping Unknown Ipv6 Multicast Data

    Step Command Remarks • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 Use either method. interface-number aggregate interface view or enter port group view. • Enter port group view: port-group manual port-group-name...

  • Page 415: Enabling Mld Report Suppression

    Enabling dropping unknown IPv6 multicast data globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Enable dropping unknown drop-unknown Disabled by default. IPv6 multicast data. Enabling dropping unknown IPv6 multicast data in a VLAN Step Command Remarks Enter system view.

  • Page 416: Enabling Ipv6 Multicast Group Replacement

    MLD snooping forwarding table, and the hosts on this port join IPv6 multicast groups again until the number of IPv6 multicast groups that the port joins reaches the maximum value. When the port joins an IPv6 multicast group, if the port has been configured as a static member port, the system applies the configurations to the port again.

  • Page 417: Setting The 802.1P Precedence For Mld Messages

    Step Command Remarks Enter MLD-snooping view. mld-snooping Enable IPv6 multicast group overflow-replace [ vlan vlan-list ] Disabled by default. replacement. Enabling IPv6 multicast group replacement on a port Step Command Remarks Enter system view. system-view • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet...

  • Page 418: Enabling The Mld Snooping Host Tracking Function

    Enabling the MLD snooping host tracking function With the MLD snooping host tracking function, the switch can record the information of the member hosts that are receiving IPv6 multicast traffic, including host IPv6 address, running duration, and timeout time. You can monitor and manage the member hosts according to the recorded information. Enabling the MLD snooping host tracking function globally Step Command...

  • Page 419: Mld Snooping Configuration Examples

    Task Command Remarks Clear statistics for all MLD messages learned through MLD reset mld-snooping statistics Available in user view. snooping. MLD snooping configuration examples This section provides examples of configuring MLD snooping. IPv6 group policy and simulated joining configuration example Network requirements As shown in Figure...
  • Page 420 [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] mld enable [RouterA-Ethernet1/1] pim ipv6 dm [RouterA-Ethernet1/1] quit [RouterA] interface ethernet 1/2 [RouterA-Ethernet1/2] pim ipv6 dm [RouterA-Ethernet1/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, assign Ethernet 1/1 through Ethernet 1/4 to this VLAN, and enable MLD snooping and the function of dropping IPv6 unknown multicast traffic in the VLAN.

  • Page 421: Static Port Configuration Example

    Router port(s):total 1 port(s). Eth1/1 (D) ( 00:01:30 ) IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Attribute: Host Port Host port(s):total 2 port(s). Eth1/3 (D) ( 00:03:23 ) Eth1/4 (D) ( 00:04:10 ) MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 2 port(s).
  • Page 422 Figure 107 Network diagram Configuration procedure Enable IPv6 forwarding and assign an IPv6 address and prefix length to each interface according Figure 107. On Router A, enable IPv6 multicast routing, enable IPv6 PIM-DM on each interface, and enable MLD on Ethernet 1/1. <RouterA>...
  • Page 423 [SwitchA] interface ethernet 1/3 [SwitchA-Ethernet1/3] mld-snooping static-router-port vlan 100 [SwitchA-Ethernet1/3] quit Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 100, assign Ethernet 1/1 and Ethernet 1/2 to this VLAN, and enable MLD snooping in the VLAN.
  • Page 424 Router port(s):total 2 port(s). Eth1/1 (D) ( 00:01:30 ) Eth1/3 IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Attribute: Host Port Host port(s):total 1 port(s). Eth1/2 (D) ( 00:03:23 ) MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 1 port(s).

  • Page 425: Mld Snooping Querier Configuration Example

    MLD snooping querier configuration example Network requirements As shown in Figure 108, in a Layer-2-only network environment, two multicast sources Source 1 and Source 2 send IPv6 multicast data to multicast groups FF1E::101 and FF1E::102, respectively, Host A and Host C are receivers of multicast group FF1E::101, and Host B and Host D are receivers of multicast group FF1E::102.

  • Page 426: Mld Snooping Proxying Configuration Example

    # Enable IPv6 forwarding and enable MLD snooping globally. <SwitchB> system-view [SwitchB] ipv6 [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 100, add Ethernet 1/1 through Ethernet 1/4 into VLAN 100. [SwitchB] vlan 100 [SwitchB-vlan100] port ethernet 1/1 to ethernet 1/4 # Enable the MLD snooping feature and the function of dropping unknown IPv6 multicast data packets in VLAN 100.
  • Page 427 Figure 109 Network diagram Configuration procedure Assign an IP address and prefix length to each interface according to Figure 109. (Details not shown.) On Router A, enable IPv6 multicast routing, enable IPv6 PIM-DM on each interface, and enable MLD on port Ethernet 1/1. <RouterA>...
  • Page 428 group command to display information about MLD snooping groups and MLD multicast groups. For example: # Display information about MLD snooping groups on Switch A. [SwitchA] display mld-snooping group Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100.

  • Page 429: Troubleshooting Mld Snooping

    Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port(s). Eth1/1 (D) ( 00:01:23 ) IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 1 port(s).

  • Page 430: Appendix

    The function of dropping unknown IPv6 multicast data is not enabled, so unknown IPv6 multicast • data is flooded. Solution Use the display acl ipv6 command to check the configured IPv6 ACL rule. Make sure the IPv6 ACL rule conforms to the IPv6 multicast group policy to be implemented. Use the display this command in MLD-snooping view or the corresponding interface view to verify that the correct IPv6 multicast group policy has been applied.

  • Page 431: Configuring Ipv6 Mbgp

    Configuring IPv6 MBGP The term router in this document refers to both routers and routing-capable Ethernet switches. This chapter covers configuration tasks related to multiprotocol BGP for IPv6 multicast. For information about BGP and IPv6 BGP, see Layer 3—IP Routing Configuration Guide. IPv6 MBGP overview IETF defined Multiprotocol BGP (MP-BGP) to enable BGP to carry routing information for multiple network-layer protocols.

  • Page 432: Configuring Basic Ipv6 Mbgp Functions

    Task Remarks Enabling the IPv6 MBGP ORF capability Optional. Configuring the maximum number of equal-cost Optional. routes for load-balancing Configuring an IPv6 MBGP peer group Optional. Configuring a large scale IPv6 Configuring IPv6 MBGP community Optional. MBGP network Configuring an IPv6 MBGP route reflector Optional.

  • Page 433: Controlling Route Distribution And Reception

    apply preferred-value preferred-value command. For more information about these commands, see Layer 3—IP Routing Command Reference. To configure a preferred value for routes from a peer or a peer group: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast...

  • Page 434: Configuring Ipv6 Mbgp Route Summarization

    Step Command Description import-route protocol [ process-id Enable route redistribution [ med med-value | route-policy Not enabled by default. from another routing protocol. route-policy-name ] * ] NOTE: If the default-route imported command is not configured, using the import-route command cannot redistribute any IGP default route.

  • Page 435: Configuring Outbound Ipv6 Mbgp Route Filtering

    Configuring outbound IPv6 MBGP route filtering IMPORTANT: Members of an IPv6 MBGP peer group must have the same outbound route filtering policy as the peer • group. IPv6 BGP advertises redistributed routes that pass the specified policy to the IPv6 MBGP peer. •...

  • Page 436: Configuring Ipv6 Mbgp Route Dampening

    Step Command Remarks Enter IPv6 MBGP ipv6-family multicast address family view. • Configure inbound route filtering: filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } Use at least one command. import By default, advertised routes are • Apply a routing policy to routes from not filtered.

  • Page 437: Configuring Ipv6 Mbgp Route Attributes

    Configuring IPv6 MBGP route attributes This section describes how to use IPv6 MBGP route attributes to affect IPv6 MBGP route selection. IPv6 MBGP route attributes involve the following: IPv6 MBGP protocol preference • Default local preference attribute • MED attribute •...

  • Page 438: Configuring The Next_Hop Attribute

    Step Command Remarks Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Optional. Configure a default MED default med med-value value. 0 by default. Enable the comparison of the Optional. MED for routes from different compare-different-as-med Not enabled by default.

  • Page 439: Optimizing Ipv6 Mbgp Networks

    Step Command Remarks Allow the local AS number to appear in the AS path of peer { ipv6-group-name | Optional. routes from a peer or a peer ipv6-address } allow-as-loop group and specify the number Not allowed by default. [ number ] of times that the local AS number can appear.

  • Page 440: Enabling The Ipv6 Mbgp Orf Capability

    Step Command Remarks peer { ipv6-group-name | Optional. Enable IPv6 BGP route refresh ipv6-address } capability-advertise for a peer or a peer group. Enabled by default. route-refresh Performing soft reset manually If the peer does not support route refresh, you can use the peer keep-all-routes command to save all the route updates from the peer, and then use the refresh bgp ipv6 multicast command to soft-reset IPv6 MBGP connections to refresh the IPv6 MBGP routing table and apply the new policy without terminating IPv6 MBGP connections.

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

    Step Command Remarks Enter IPv6 address family ipv6-family view. Optional. peer { group-name | Enable BGP route refresh for a Enabled by default. ipv6-address } capability-advertise peer or a peer group. If this feature is not enabled, you route-refresh must configure this command. Optional.

  • Page 442: Configuring A Large Scale Ipv6 Mbgp Network

    Configuring a large scale IPv6 MBGP network Configuration prerequisites Before you configure the following tasks, you must configure basic IPv6 MBGP functions. Configuring an IPv6 MBGP peer group For easy management and configuration, you can organize some IPv6 MBGP peers that have the same route update policy into a peer group.

  • Page 443: Configuring An Ipv6 Mbgp Route Reflector

    You must configure a routing policy to define the community attribute and apply the policy to outgoing routes. For more information about routing policy configuration, see Layer 3—IP Routing Configuration Guide. To advertise the community attribute to an IPv6 MBGP peer or a peer group: Step Command Remarks...

  • Page 444: Displaying And Maintaining Ipv6 Mbgp

    Step Command Remarks Optional. Configure the cluster ID of the reflector cluster-id cluster-id A route reflector uses its router ID route reflector. as the cluster ID by default. Displaying and maintaining IPv6 MBGP Displaying IPv6 MBGP Task Command Remarks display bgp ipv6 multicast group Display IPv6 MBGP peer group [ ipv6-group-name ] [ | { begin | exclude | Available in any view.

  • Page 445: Resetting Ipv6 Mbgp Connections

    Task Command Remarks Display IPv6 MBGP routing display bgp ipv6 multicast routing-table information originated from different-origin-as [ | { begin | exclude | Available in any view. different ASs. include } regular-expression ] display bgp ipv6 multicast routing-table flap-info [ regular-expression Display IPv6 MBGP routing flap as-regular-expression | [ as-path-acl Available in any view.

  • Page 446: Clearing Ipv6 Mbgp Information

    Clearing IPv6 MBGP information Task Command Remarks Clear dampened IPv6 MBGP routing information reset bgp ipv6 multicast dampening [ ipv6-address Available in user view. and release suppressed prefix-length ] routes. reset bgp ipv6 multicast flap-info Clear IPv6 MBGP route flap [ ipv6-address/prefix-length | regexp Available in user view.

  • Page 447: Configuration Procedure

    Configuration procedure Configure IPv6 addresses for router interfaces as shown in Figure 110. (Details not shown.) Configure OSPFv3. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-SM and MLD, and configure an IPv6 PIM-SM domain border: # Enable IPv6 multicast routing on Router A, and enable PIM-SM on each interface. <RouterA>...
  • Page 448 [RouterB-pim6] c-bsr 1001::2 [RouterB-pim6] c-rp 1001::2 [RouterB-pim6] quit Configure BGP, and specify the IPv6 MBGP peer: # On Router A, configure the IPv6 MBGP peer. [RouterA] ipv6 [RouterA] bgp 100 [RouterA-bgp] router-id 1.1.1.1 [RouterA-bgp] ipv6-family [RouterA-bgp-af-ipv6] peer 1001::2 as-number 200 [RouterA-bgp-af-ipv6] import-route direct [RouterA-bgp-af-ipv6] quit [RouterA-bgp] ipv6-family multicast...

  • Page 449: Support And Other Resources

    Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...

  • Page 450: Conventions

    Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
  • Page 451 Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

  • Page 452: Index

    Index Numerics configuring PIM-SM, configuring PIM-SM C-BSR for admin-scoped and 802.1p global-scoped zones, setting IGMP snooping 802.1p message enabling BIDIR-PIM administrative scoping, precedence, enabling IPv6 BIDIR-PIM, setting MLD snooping 802.1p message enabling IPv6 PIM-SM, precedence, enabling PIM-SM, IPv6 BIDIR-PIM configuration, IPv6 PIM-SM domain division, backward switching from switch-MDT to IPv6 PIM-SM relationship between admin-scoped...
  • Page 453 attribute configuring C-BSR timer, BGP AS_PATH attribute, configuring C-RP, IPv6 MBGP AS_PATH attribute, configuring C-RP timers globally, IPv6 MBGP MED, configuring domain border, IPv6 MBGP NEXT_HOP, configuring global C-BSR parameters, IPv6 MBGP route, configuring RP, MBGP default local preference, configuring static RP, MBGP MED, DF election, MBGP NEXT_HOP,...
  • Page 454 cache BGP MDT peers or peer groups, MSDP, BGP MDT route reflector, troubleshooting MSDP, 199, BIDIR-PIM, 71, C-BSR BIDIR-PIM administrative scoping, BIDIR-PIM, BIDIR-PIM admin-scoped zone boundary, configuring BIDIR-PIM C-BSR for admin-scoped BIDIR-PIM BSR, and global-scoped zones, BIDIR-PIM C-BSR, configuring BIDIR-PIM C-BSR timer, BIDIR-PIM C-BSR for admin-scoped and configuring IPv6 BIDIR-PIM admin-scoped zone global-scoped zones,...
  • Page 455 IGMP snooping proxy message source IP IPv6 MBGP NEXT_HOP attribute, address, IPv6 MBGP outbound route filtering, IGMP snooping proxying, 148, IPv6 MBGP peer group, IGMP snooping querier, IPv6 MBGP peer/peer group preferred route IGMP snooping query source IP address, value, IGMP snooping report suppression, IPv6 MBGP route attribute, IGMP snooping simulated member host...
  • Page 456 IPv6 PIM common timer, MBGP route summarization, IPv6 PIM hello message filter, MBGP soft reset, 211, IPv6 PIM hello options, MDT switchover parameters, IPv6 PIM join/prune message size, minimum packet TTL, IPv6 PIM multicast data filter, MLD, IPv6 PIM prune delay timer, MLD basic function, 276, IPv6 PIM to work with BFD, MLD fast leave processing,...
  • Page 457 PIM common features, BIDIR-PIM C-RP timer, PIM common timer, configuring IPv6 BIDIR-PIM C-RP, PIM hello message filter, configuring IPv6 BIDIR-PIM C-RP timer globally, PIM hello options, configuring IPv6 PIM-SM C-RP timer globally, PIM join/prune message size, configuring PIM-SM C-RP, PIM multicast data filter, PIM-SM, PIM-DM, 56, PIM-DM graft retry period,...
  • Page 458 configuring BIDIR-PIM domain border, dropping unknown multicast data globally, configuring global C-BSR parameters, dropping unknown multicast data in a VLAN, configuring IPv6 BIDIR-PIM C-BSR parameters IGMP, globally, IGMP fast-leave processing, configuring IPv6 BIDIR-PIM domain IGMP host tracking function, border, IGMP proxying, configuring IPv6 PIM-SM domain border, IGMP snooping, configuring PIM-SM domain border,...
  • Page 459 IPv6 PIM-SM embedded RP, configuring IPv6 MBGP outbound route filtering, MBGP ORF capability, configuring IPv6 PIM hello message filter, MLD, configuring IPv6 PIM multicast data filter, MLD host tracking function, configuring MBGP inbound route filtering, MLD proxying, configuring MBGP outbound route filtering, MLD snooping host tracking function, configuring MLD IPv6 multicast group filter, MLD snooping host tracking function...
  • Page 460 configuring IPv6 BIDIR-PIM domain enabling IPv6 BIDIR-PIM, border, enabling IPv6 BIDIR-PIM administrative configuring IPv6 BIDIR-PIM RP, scoping, configuring IPv6 BIDIR-PIM static RP, enabling IPv6 BIDIR-PIM embedded RP, configuring IPv6 PIM common features, enabling IPv6 PIM-DM, configuring IPv6 PIM common timer, enabling IPv6 PIM-DM state-refresh capability, configuring IPv6 PIM hello message filter, enabling IPv6 PIM-SM,...
  • Page 461 IPv6 PIM-SSM neighbor discovery, multicast data packet delivery, IPv6 PIM-SSM SPT building, multicast protocol packet delivery, MDT switchover, GRE tunneling multi-AS MD VPN, IPv6 multicast forwarding, multicast configuration, IPv6 multicast forwarding over, multicast data packet delivery, multicast forwarding, multicast forwarding across unicast multicast forwarding over, subnets, group...
  • Page 462 IGMP tracking function, versions, MLD host tracking function, VPN support, MLD snooping simulated member host IGMP report port, multicast protocol packet delivery, MLDv2 receiver host state listening, IGMP snooping aging timer for dynamic port, basic concepts, IGMP basic configuration, adjusting performance, configuration, 135, 140, configuration, configuring multicast source port filtering,...
  • Page 463 receiving leave message, configuring BIDIR-PIM static RP, receiving membership report, configuring forwarding table size, related ports, configuring IGMP snooping source port filtering, setting 802.1p message precedence, configuring MLD version, setting dynamic port aging timer, configuring MSDP SA cache mechanism, setting dynamic port aging timer globally, configuring MSDP SA message content, setting dynamic port aging timer in VLAN, configuring MSDP SA message related...
  • Page 464 PIM-SM administrative scoping, configuring MLD SSM mapping, 283, PIM-SM admin-scoped zone configuration, configuring MLD version, PIM-SM assert, configuring PIM-DM, PIM-SM DR election, configuring proxying, PIM-SM neighbor discovery, enabling MLD, PIM-SM non-scoped zone configuration, enabling MLD host tracking function, PIM-SM relationship between admin-scoped enabling MLD SSM mapping, and global-scoped zones, Ethernet MAC multicast address,...
  • Page 465 AS_PATH attribute configuration, configuring routing, clearing information, configuring routing policy, configuration, disabling MLD snooping dynamic router port change, configuring basic functions, displaying MLD snooping, configuring community, enabling MLD snooping host tracking function, configuring default local preference, enabling MLD snooping proxying, configuring inbound route filtering, enabling routing, configuring large scale network,...
  • Page 466 configuration, 296, configuring domain border, configuring common features, configuring IPv6 multicast source registration, configuring common timer, disabling BSM semantic fragmentation, configuring hello message data filter, DR election, configuring hello options, embedded RP, configuring IPv6 multicast data filter, enabling, 316, configuring IPv6 PIM prune delay timer, enabling administrative scoping, configuring IPv6 PIM to work with BFD, enabling embedded RP,...
  • Page 467 listening (MLDv2 receiver host state), configuring IPv6 MBGP default local preference, load balancing configuring IPv6 MBGP route preference, configuring IPv6 MBGP max number equal cost routes, configuring IPv6 MBGP route summarization, MBGP max number routes, configuring large scale network, configuring manual soft reset, configuring max number load balancing MAC address routes,...
  • Page 468 backward switching from switch-MDT to configuring IGMP snooping proxy message source share-MDT, IP address, configuring MDT switchover parameters, configuring IPv6 PIM hello message filter, switching from share-MDT to switch-MDT, configuring IPv6 PIM hello options, MD-VPN configuring IPv6 PIM join/prune message size, basic concepts, configuring MLD query/response parameters,...
  • Page 469 configuring MLD proxying, enabling proxying, configuring proxying, fast-leave processing enable, configuring query/response parameters, hardware compatibility, configuring Router-Alert option handling how it works, methods, IPv6 group policy configuration, configuring Router-Alert option handling IPv6 multicast group filter, methods globally, IPv6 multicast group replacement, configuring Router-Alert option handling IPv6 multicast MLD report, methods on interface,...
  • Page 470 receiver host state listening, mtracert (IP multicast), report message, multi-AS MD VPN SSM mapping, VRF-to-VRF PE interconnectivity, MLDv2 snooping version specification, multicast model address, multicast, adjusting MLD performance, MPLS architecture, multicast VPN configuration, basic MSDP configuration, MSDP broadcast transmission technique, Anycast RP configuration, changing RPF route, 117, configuration,...
  • Page 471 configuring IPv6 BIDIR-PIM static RP, configuring MSDP mesh group, configuring IPv6 PIM common features, configuring MSDP peer connection, configuring IPv6 PIM common timer, configuring MSDP peer connection control, configuring IPv6 PIM hello message filter, configuring MSDP peer description, configuring IPv6 PIM hello options, configuring MSDP SA message filtering rule, configuring IPv6 PIM join/prune message configuring MSDP static RPF peer,...
  • Page 472 enabling IPv6 BIDIR-PIM, IPv6 BIDIR-PIM bidirectional RPT building, enabling IPv6 BIDIR-PIM administrative IPv6 BIDIR-PIM configuration, scoping, IPv6 BIDIR-PIM DF election, enabling IPv6 BIDIR-PIM embedded RP, IPv6 BIDIR-PIM neighbor discovery, enabling IPv6 PIM-DM, IPv6 BIDIR-PIM RP discovery, enabling IPv6 PIM-DM state-refresh IPv6 PIM configuration, 296, capability, IPv6 PIM protocol relationships,...
  • Page 473 PIM-SM SPT switchover configuration, multi-hop EBGP interconnectivity, processing of multicast protocol messages, P device, routing configuration, PE device, RPF check mechanism, protocols and standards, RPF check process, public network, RPF check rules for SA messages (MSDP), share-MDT characteristics, setting IGMP snooping 802.1p message share-MDT establishment, precedence, share-MDT establishment in BIDIR-PIM...
  • Page 474 configuring MBGP inbound route filtering, NEXT_HOP configuring MBGP manual soft reset, IPv6 MBGP attribute, configuring MBGP max number load balancing MBGP attribute, routes, no member information on router (MLD configuring MBGP MED attribute, troubleshooting), configuring MBGP NEXT_HOP attribute, notation (multicast), configuring MBGP outbound route filtering, optimizing...
  • Page 475 PE (VPN instance), performing PE device, IPv6 MBGP soft reset manually, configuring BGP MDT peers or peer IPv6 MBGP soft reset through route-refresh, groups, configuring multi-AS MD VPN, BIDIR-PIM. See BIDIR-PIM configuring single-AS MD VPN, configuration, 41, multicast data packet delivery, configuring common features, multicast protocol packet delivery, configuring common timer,...
  • Page 476 share-MDT establishment, MSDP inter-AS multicast configuration leveraging static RPF peers, SPT building, MSDP inter-domain multicast configuration, PIM-SM MSDP inter-domain multicast delivery, administrative scoping, MSDP intra-domain Anycast RP, admin-scoped zone configuration, MSDP peer, assert, MSDP SA message filtering configuration, basic MSDP configuration, multicast data packet delivery, configuration, multicast protocol packet delivery,...
  • Page 477 IPv6 multicast MLD snooping group policy IPv6 multicast MLD snooping groups max number configuration, on port, IPv6 multicast MLD snooping policy, IPv6 multicast MLD snooping IPv6 multicast group filter, IPv6 multicast routing configuration, IPv6 multicast MLD snooping IPv6 multicast source port port filtering, configuring IGMP snooping multicast source...
  • Page 478 configuring global C-BSR parameters, configuring IGMP snooping query source IP address, configuring IGMP basic functions, 20, configuring IGMP snooping report configuring IGMP max number multicast groups suppression, on interface, configuring IGMP snooping simulated member host configuring IGMP multicast group filter, port, 144, configuring IGMP proxying, 29, configuring IGMP snooping static port, 143,...
  • Page 479 configuring IPv6 MBGP basic functions, configuring IPv6 multicast MLD snooping group filter globally, configuring IPv6 MBGP community, configuring IPv6 multicast MLD snooping group configuring IPv6 MBGP default local route filter on port, preference, configuring IPv6 multicast MLD snooping group configuring IPv6 MBGP inbound route policy, filtering, configuring IPv6 multicast MLD snooping IPv6...
  • Page 480 configuring IPv6 PIM-SM admin-scoped configuring MDT switchover parameters, zone, configuring MD-VPN, configuring IPv6 PIM-SM admin-scoped zone configuring MLD basic function, 276, boundary, configuring MLD fast leave processing, configuring IPv6 PIM-SM admin-scoped zone configuring MLD fast leave processing C-BSR, globally, configuring IPv6 PIM-SM BSR, configuring MLD fast leave processing on configuring IPv6 PIM-SM C-BSR, interface,...
  • Page 481 configuring MSDP SA message related configuring PIM-SSM, 80, parameters, configuring PIM-SSM group range, configuring MSDP SA request message, configuring Router-Alert option handling configuring MSDP static RPF peer, methods, 24, configuring multi-AS MD VPN, configuring Router-Alert option handling methods globally, 24, configuring multicast forwarding on downstream interface, configuring Router-Alert option handling methods...
  • Page 482 enabling dropping unknown multicast data in a enabling IPv6 multicast MLD snooping group VLAN, replacement, enabling IGMP, enabling IPv6 multicast MLD snooping group replacement globally, enabling IGMP fast leave processing globally, enabling IPv6 multicast MLD snooping group replacement on port, enabling IGMP fast leave processing on interface, enabling IPv6 multicast MLD snooping IPv6...
  • Page 483 enablingMLD snooping host tracking function setting the 802.1p precedence for MLD messages globally, in VLAN, enablingMLD snooping host tracking function in specifying IGMP snooping version, VLAN, specifying IPv6 multicast MLD snooping injecting IPv6 MBGP local route, version, maintaining IGMP, specifying the gloabal version of IGMP, maintaining IGMP snooping, specifying the version of IGMP on an interface, maintaining IPv6 MBGP,...
  • Page 484 prune MBGP connections, configuring IPv6 PIM join/prune message router size, IPv6 multicast MLD snooping router port, public network troubleshooting IGMP inconsistent memberships on multicast data packet delivery, routers on the same subnet, multicast VPN configuration, troubleshooting IGMP no membership information on the receiver-side router, troubleshooting MLD inconsistent router querying...
  • Page 485 configuring IGMP proxying, 29, configuring IPv6 MBGP max number load balancing equal cost routes, configuring IGMP query/response parameters, configuring IPv6 MBGP MED attribute, configuring IGMP snooping multicast source configuring IPv6 MBGP NEXT_HOP attribute, port filtering, configuring IPv6 MBGP outbound route configuring IGMP snooping proxy message filtering, source IP address,...
  • Page 486 configuring IPv6 PIM-SM multicast source configuring MLD version, registration, configuring MSDP mesh group, configuring IPv6 PIM-SM RP, configuring MSDP peer connection, configuring IPv6 PIM-SM static RP, configuring MSDP peer connection control, configuring IPv6 PIM-SSM, configuring MSDP peer description, configuring IPv6 PIM-SSM group range, configuring MSDP SA cache mechanism, configuring MBGP community, configuring MSDP SA message content,...
  • Page 487 controlling IPv6 MBGP route reception, enabling MLD SSM mapping, creating MSDP peer connection, enabling MSDP, creating multicast RPF route, 118, enabling PIM-DM, disabling BIDIR-PIM BSM semantic enabling PIM-DM state-refresh capability, fragmentation, enabling PIM-SM, disabling IGMP snooping dynamic router port enabling PIM-SM administrative scoping, change, Ethernet MAC multicast address, disabling IPv6 BIDIR-PIM BSM semantic...
  • Page 488 IPv6 BIDIR-PIM configuration, IPv6 PIM-SM SPT switchover, IPv6 BIDIR-PIM DF election, IPv6 PIM-SSM, IPv6 BIDIR-PIM neighbor discovery, IPv6 PIM-SSM configuration, IPv6 BIDIR-PIM RP discovery, IPv6 PIM-SSM DR election, IPv6 MBGP configuration, IPv6 PIM-SSM neighbor discovery, IPv6 MLD snooping general query, IPv6 PIM-SSM SPT building, IPv6 MLD snooping proxying, MBGP configuration, 201,...
  • Page 489 PIM-DM assert, switching from share-MDT to switch-MDT, PIM-DM configuration, 56, troubleshooting PIM multicast data abnormally terminated on an intermediate router, PIM-DM graft, VRF-to-VRF PE interconnectivity, PIM-DM neighbor discovery, PIM-DM SPT building, BIDIR-PIM bidirectional RPT building, PIM-SM, BIDIR-PIM RP discovery, PIM-SM administrative scoping, configuring BIDIR-PIM C-RP, PIM-SM admin-scoped zone configuration, configuring BIDIR-PIM C-RP timers globally,...
  • Page 490 share-MDT establishment in BIDIR-PIM 802.1p precedence for IGMP messages in network, VLAN, share-MDT establishment in PIM-SM 802.1p precedence for MLD messages network, globally, troubleshooting IPv6 PIM-SM RPT establishment 802.1p precedence for MLD messages in failure, VLAN, troubleshooting PIM-SIM RP cannot join IGMP snooping 802.1p message SPT, precedence,...
  • Page 491 troubleshooting IPv6 PIM-SM registration configuring IGMP static member interface, failure, IPv6 multicast MLD snooping static port specifying configuration, IPv6 multicast MLD snooping version, troubleshooting multicast static route failure, specifying IGMP snooping version, static port (IGMP snooping), 143, specifying the global version of IGMP, subnet specifying the version of IGMP on an interface, troubleshooting IGMP inconsistent memberships on...
  • Page 492 IGMP snooping dynamic port aging Layer 2 IPv6 multicast MLD snooping timer, 136, forwarding, IGMP snooping dynamic port aging timer MD-VPN, global configuration, MD-VPN MVRF cannot be created, IGMP snooping dynamic port aging timer MD-VPN share-MDT cannot be established, VLAN configuration, MLD, IPv6 multicast MLD snooping aging timer for MLD inconsistent router memberships on same...
  • Page 493 IGMP query/response parameters (IGMP enabling switch-group reuse logging, snooping), multicast data packet delivery, IGMP snooping configuration, 135, 140, multicast protocol packet delivery, IGMP snooping drop unknown multicast data multicast VPN configuration, enable, IGMP snooping dynamic port aging timer, zone IGMP snooping enable, configuring BIDIR-PIM admin-scoped zone IGMP snooping fast leave processing boundary,...

This manual is also suitable for:

Msr sfmMsr ssm

Table of Contents