hit counter script
HP A8800 Configuration Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Network Router
  5. A8800 Series
  6. Configuration manual
HP A8800 Configuration Manual

HP A8800 Configuration Manual

Ip multicast
Hide thumbs Also See for A8800:
1
2
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
Table Of Contents
487
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation Manual
HP A8800 Routers
IP Multicast

Configuration Guide

Part number: 5998-1744
Software version: A8800-CMW520-R3627
Document version: 6W102-20130906

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for HP A8800

Summary of Contents for HP A8800

  • Page 1: Configuration Guide

    HP A8800 Routers IP Multicast Configuration Guide Part number: 5998-1744 Software version: A8800-CMW520-R3627 Document version: 6W102-20130906...
  • 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 additional warranty.
  • Page 3 Contents Multicast overview ······················································································································································· 1   Overview ············································································································································································ 1   Information transmission techniques ······················································································································· 1   Multicast features ······················································································································································ 3   Common notations in multicast ······························································································································· 4   Multicast advantages and applications ················································································································· 4   Multicast models ································································································································································ 5   Multicast architecture ························································································································································...
  • Page 4 Static port configuration example ······················································································································· 36   IGMP snooping querier configuration example ································································································· 40   IGMP snooping proxying configuration example ······························································································ 43   Troubleshooting IGMP snooping ·································································································································· 46   Layer 2 multicast forwarding cannot function ···································································································· 46   Configured multicast group policy fails to take effect ······················································································· 46  ...
  • Page 5 IGMPv1 overview ·················································································································································· 82   IGMPv2 enhancements ········································································································································· 84   IGMPv3 enhancements ········································································································································· 84   IGMP SSM mapping ············································································································································· 86   IGMP proxying ······················································································································································ 87   Multi-instance IGMP ·············································································································································· 88   Protocols and standards ······································································································································· 88   IGMP configuration task list ·········································································································································· 88  ...
  • Page 6 Configuration prerequisites ································································································································ 130   Enabling PIM-SM ················································································································································· 131   Configuring an RP ··············································································································································· 132   Configuring a BSR ··············································································································································· 134   Configuring administrative scoping ·················································································································· 137   Configuring multicast source registration·········································································································· 139   Configuring SPT switchover ································································································································ 140   Configuring BIDIR-PIM ·················································································································································...
  • Page 7 Configuration prerequisites ································································································································ 195   Configuring MSDP peer description·················································································································· 195   Configuring an MSDP mesh group ··················································································································· 195   Configuring MSDP peer connection control ····································································································· 196   Configuring SA messages related parameters ········································································································· 197   Configuration prerequisites ································································································································ 197   Configuring SA message content ······················································································································...
  • Page 8 Clearing MBGP information ······························································································································· 236   MBGP configuration example····································································································································· 236   Configuring multicast VPN ····································································································································· 240   Overview ······································································································································································· 240   MD-VPN overview ··············································································································································· 242   Protocols and standards ····································································································································· 245   How MD-VPN works ···················································································································································· 245   Share-MDT establishment ··································································································································· 245  ...
  • Page 9 Configuring an MLD snooping policy ························································································································ 301   Configuring an IPv6 multicast group filter ········································································································ 301   Enabling dropping unknown IPv6 multicast data ···························································································· 302   Enabling MLD report suppression ······················································································································ 303   Setting the maximum number of multicast groups that a port can join ························································· 303  ...
  • Page 10 Configuring MLD ····················································································································································· 345   Overview ······································································································································································· 345   MLD versions ························································································································································ 345   How MLDv1 works ·············································································································································· 345   How MLDv2 works ·············································································································································· 347   MLD message types············································································································································· 348   MLD SSM mapping ············································································································································· 351   MLD proxying ······················································································································································ 352  ...
  • Page 11 IPv6 PIM-SM configuration task list ···················································································································· 392   Configuration prerequisites ································································································································ 392   Enabling IPv6 PIM-SM ········································································································································· 393   Configuring an RP ··············································································································································· 393   Configuring a BSR ··············································································································································· 396   Configuring IPv6 administrative scoping ·········································································································· 399   Configuring IPv6 multicast source registration ································································································· 400  ...
  • Page 12   Clearing IPv6 MBGP information ······················································································································ 466   IPv6 MBGP configuration example ···························································································································· 466   Support and other resources ·································································································································· 470   Contacting HP ······························································································································································ 470   Subscription service ············································································································································ 470   Related information ······················································································································································ 470   Documents ···························································································································································· 470  ...

  • 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 In unicast transmission, the traffic transmitted over the network is proportional to the number of hosts that need the information. If a large number of hosts need the information, the information source must send 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.

  • Page 15: Multicast Features

    Figure 3 Multicast transmission 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 with the transmission of TV programs. Table 1 Comparing TV transmission and multicast transmission TV transmission Multicast transmission...

  • Page 17: Multicast Models

    Data warehouse and financial applications (stock quotes) • • Any other point-to-multipoint application for data distribution 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 multicast source, and receivers can join a multicast group (identified by a group address) can and obtain multicast information...

  • Page 18: Multicast Addresses

    Multicast applications—A software system that supports multicast applications, such as video • conferencing, must be installed on multicast sources and receiver hosts. The TCP/IP stack must support reception and transmission of multicast data. Multicast addresses Network-layer multicast addresses (multicast IP addresses) enables communication between multicast sources and multicast group members.
  • Page 19 Address Description 224.0.0.8 ST hosts. 224.0.0.9 RIPv2 routers. 224.0.0.11 Mobile agents. 224.0.0.12 DHCP server/relay agent. 224.0.0.13 All Protocol Independent Multicast (PIM) routers. 224.0.0.14 RSVP encapsulation. 224.0.0.15 All Core-Based Tree (CBT) routers. 224.0.0.16 Designated SBM. 224.0.0.17 All SBMs. 224.0.0.18 VRRP. IPv6 multicast addresses •...
  • Page 20 Scope—The Scope filed contains four bits, which indicate the scope of the IPv6 internetwork for which the multicast traffic is intended. Table 5 Values of the Scope field Value Meaning 0, 3, F Reserved. Interface-local scope. Link-local scope. Admin-local scope. Site-local scope.

  • Page 21: Multicast Protocols

    Figure 7 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 Protocol (MLD) 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

    incoming interface. The result of the RPF check determines whether the packet will be forwarded or discarded. The RPF check mechanism is the basis for most multicast routing protocols to implement multicast forwarding. For more information about the RPF mechanism, see "Configuring multicast routing and forwarding"...

  • Page 25: Multicast Application In Vpns

    reside on different PE devices. On a PE device, the instance for the public network is called the public network instance, and those for VPNs are called VPN instances. Multicast application in VPNs A PE device that supports multicast for VPNs does the following operations: Maintains an independent set of multicast forwarding mechanisms for each VPN, including the •...

  • Page 26: Configuring Igmp Snooping

    Configuring IGMP snooping Overview A Layer 2 device that runs IGMP snooping establishes a Layer 2 multicast forwarding table, which maps ports and multicast MAC addresses, by listening to IGMP messages exchanged between a Layer 3 multicast device and hosts to manage and control multicast data forwarding. As shown in Figure 1 1, without IGMP snooping enabled, the Layer 2 switch floods multicast packets to all...
  • Page 27 Figure 12 IGMP snooping related ports Receiver Router A Device A GE2/1/1 GE2/1/2 Host A GE2/1/3 Host B Receiver GE2/1/1 GE2/1/2 Source Host C Device B Router port Member port Multicast packets Host D The following describes the ports involved in IGMP snooping: Router port—Layer 3 multicast device-side port.

  • Page 28: How Igmp Snooping Works

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

  • Page 29: Igmp Snooping Proxying

    A device does not forward an IGMP report through a non-router port. If the device forwards a report message through a member port, the IGMP report suppression mechanism causes all the attached hosts that monitor the reported multicast address suppress their own reports. This makes the device unable to know whether the reported multicast group still has active members attached to that port.
  • Page 30 NOTE: Even though an IGMP snooping proxy is a host from the perspective of its upstream device, the IGMP membership report suppression mechanism for hosts does not take effect on it. For more information about the IGMP report suppression mechanism for hosts, see "Configuring IGMP."...

  • Page 31: Protocols And Standards

    IGMP message Actions In response to an IGMP leave message for a multicast group, the proxy sends a group-specific query out of the receiving port. After making sure that no member Leave port is contained in the forwarding entry for the multicast group, the proxy sends a leave message to the group out of all router ports.

  • Page 32: Configuring Basic Igmp Snooping Functions

    made in IGMP snooping view is effective only if you do not make the same configuration in VLAN view. The configurations made in IGMP snooping view are effective for all ports. The configurations made • in Layer 2 Ethernet interface view or Layer 2 aggregate interface view are effective for only the current port.

  • Page 33: Configuring The Maximum Number Of Global Igmp Forwarding Entries

    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. • Keeps static IGMPv3 snooping forwarding entries (*, G). •...

  • Page 34: Setting Aging Timers For Dynamic Ports

    Setting aging timers for dynamic ports If the memberships of multicast groups frequently change, you can set a relatively small value for the aging timer of the dynamic member ports. If the memberships of multicast groups rarely change, you can set a relatively large value.

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

    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, Layer 2 Use either command. interface-number aggregate interface view, or port group view. •...

  • Page 36: Enabling Fast-Leave Processing

    NOTE: Unlike a static member port, a port that you configure as a simulated member host ages out like a dynamic member port. Enabling fast-leave processing The fast-leave processing feature enables the router to process IGMP leave messages quickly. With the fast-leave processing feature enabled, when the 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 37: Disabling A Port From Becoming A Dynamic Router Port

    Disabling a port from becoming a dynamic router port The following problems exist in a multicast access network: • Upon receiving an IGMP general query or a PIM hello message from a connected host, a router port becomes a dynamic router port. Before its timer expires, this dynamic router port will receive all multicast packets within the VLAN it belongs to and forward them to the host, thus affecting normal multicast reception of the host.

  • Page 38: Enabling Igmp Snooping Querier

    Enabling IGMP snooping querier In an IP multicast network that runs IGMP, a multicast router or Layer 3 multicast switch sends IGMP queries, so that all Layer 3 multicast devices can establish and maintain multicast forwarding entries, in order to forward multicast traffic correctly at the network layer. This router or Layer 3 switch is called the "IGMP querier."...

  • Page 39: Configuring Source Ip Address For Igmp Queries

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

  • Page 40: Configuring Igmp Snooping Proxying

    Configuring IGMP snooping proxying Before you configure IGMP snooping proxying in a VLAN, complete the following tasks: • Enable IGMP snooping in the VLAN. Determine the source IP address for the IGMP reports sent by the proxy. • Determine the source IP address for the IGMP leave messages sent by the proxy. •...

  • Page 41: Configuring A Multicast Group Filter

    Determine the maximum number of multicast groups that a port can join. • Configuring a multicast group filter On an IGMP snooping–enabled router, you can configure a multicast group filter to limit multicast programs available to users. In an application, when a user requests a multicast program, the user’s host initiates an IGMP report. After receiving this report message, the router resolves the multicast group address in the report and looks up the ACL.

  • Page 42: Enabling Igmp Report Suppression

    If the function of dropping unknown multicast data is disabled, the router floods unknown multicast • data in the VLAN that the unknown multicast data belongs to. If the function of dropping unknown multicast data is enabled, the router drops all received •...

  • Page 43: Enabling Multicast Group Replacement

    When you configure this maximum number, if the number of multicast groups the port has joined exceeds the configured maximum value, the system deletes all the forwarding entries for the port from the IGMP snooping forwarding table, and the hosts attached to this port need to re-join multicast groups until the number of multicast groups that the port joins reaches the maximum value.

  • Page 44: Enabling The Igmp Snooping Host Tracking Function

    Step Command Remarks Enter system view. system-view Enter IGMP snooping view. igmp-snooping Enable multicast group overflow-replace [ vlan vlan-list ] Disabled by default. replacement. Enabling 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 45: Displaying And Maintaining Igmp Snooping

    Displaying and maintaining IGMP snooping Task Command Remarks display igmp-snooping group [ vlan Display IGMP snooping group vlan-id ] [ slot slot-number ] [ verbose ] [ | Available in any view. information. { begin | exclude | include } regular-expression ] display igmp-snooping host vlan vlan-id Display information about the hosts...
  • Page 46 Figure 14 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface as per Figure 14. (Details not shown.) On Router A, enable IP multicast routing globally, enable IGMP on GigabitEthernet 2/1/1, and enable PIM-DM on each interface. <RouterA>...
  • Page 47 [DeviceA-GigabitEthernet2/1/3] quit [DeviceA] interface GigabitEthernet 2/1/4 [DeviceA-GigabitEthernet2/1/4] port link-mode bridge [DeviceA-GigabitEthernet2/1/4] quit [DeviceA] vlan 100 [DeviceA-vlan100] port GigabitEthernet 2/1/1 to GigabitEthernet 2/1/4 [DeviceA-vlan100] igmp-snooping enable [DeviceA-vlan100] igmp-snooping drop-unknown [DeviceA-vlan100] quit # Configure a multicast group filter so that the receiver hosts in the VLAN can receive multicast data for multicast group 224.1.1.1 only.

  • Page 48: Static Port Configuration Example

    GE2/1/3 GE2/1/4 MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 2 port(s). GE2/1/3 GE2/1/4 The output shows that GigabitEthernet 2/1/3 and GigabitEthernet 2/1/4 of Device A has joined multicast group 224.1.1.1. Static port configuration example Network requirements As shown in Figure 15, IGMPv2 runs on Router A, and IGMPv2 snooping runs on Device A, Device B and Device C, with Router A acting as the IGMP querier.
  • Page 49 Figure 15 Network diagram Device B Source Device A GE2/1/2 GE2/1/1 1.1.1.2/24 10.1.1.1/24 GE2/1/1 Router A 1.1.1.1/24 IGMP querier Device C Host C Host A Receiver Receiver Host B VLAN 100 Configuration procedure Assign an IP address and subnet mask to each interface as per Figure 15.
  • Page 50 [DeviceA] interface GigabitEthernet 2/1/3 [DeviceA-GigabitEthernet2/1/3] port link-mode bridge [DeviceA-GigabitEthernet2/1/3] quit [DeviceA] vlan 100 [DeviceA-vlan100] port GigabitEthernet 2/1/1 to GigabitEthernet 2/1/3 [DeviceA-vlan100] igmp-snooping enable [DeviceA-vlan100] quit # Configure GigabitEthernet 2/1/3 to be a static router port. [DeviceA] interface GigabitEthernet 2/1/3 [DeviceA-GigabitEthernet2/1/3] igmp-snooping static-router-port vlan 100 [DeviceA-GigabitEthernet2/1/3] quit Configure Device B: # Enable IGMP snooping globally.
  • Page 51 [DeviceC-GigabitEthernet2/1/4] port link-mode bridge [DeviceC-GigabitEthernet2/1/4] quit [DeviceC] interface GigabitEthernet 2/1/5 [DeviceC-GigabitEthernet2/1/5] port link-mode bridge [DeviceC-GigabitEthernet2/1/5] quit [DeviceC] vlan 100 [DeviceC-vlan100] port GigabitEthernet 2/1/1 to GigabitEthernet 2/1/5 [DeviceC-vlan100] igmp-snooping enable [DeviceC-vlan100] quit # Configure GigabitEthernet 2/1/3 and GigabitEthernet 2/1/5 as static member ports for multicast group 224.1.1.1.

  • Page 52: Igmp Snooping Querier Configuration Example

    [DeviceC] display igmp-snooping group vlan 100 verbose 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).
  • Page 53 Figure 16 Network diagram Configuration procedure Configure Device A: # Enable IGMP snooping globally. <DeviceA> system-view [DeviceA] igmp-snooping [DeviceA-igmp-snooping] quit # Switch the link mode of GigabitEthernet 3/1/1 through GigabitEthernet 3/1/3 to Layer 2 mode, create VLAN 100 and assign GigabitEthernet 3/1/1 and GigabitEthernet 3/1/3 to VLAN 100. [DeviceA] interface GigabitEthernet 3/1/1 [DeviceA-GigabitEthernet3/1/1] port link-mode bridge [DeviceA-GigabitEthernet3/1/1] quit...
  • Page 54 Configure Device B: # Enable IGMP snooping globally. <DeviceB> system-view [DeviceB] igmp-snooping [DeviceB-igmp-snooping] quit # Switch the link mode of GigabitEthernet 3/1/1 through GigabitEthernet 3/1/4 to Layer 2 mode, create VLAN 100, add GigabitEthernet 3/1/1 through GigabitEthernet 3/1/4 to VLAN 100. [DeviceB] interface GigabitEthernet 3/1/1 [DeviceB-GigabitEthernet3/1/1] port link-mode bridge [DeviceB-GigabitEthernet3/1/1] quit...

  • Page 55: Igmp Snooping Proxying Configuration Example

    The output shows that Device B has received IGMP general queries. This means that Device A is working as the IGMP snooping querier on the network. IGMP snooping proxying configuration example Network requirements As shown in Figure 17, Router A runs IGMPv2 and Device A runs IGMPv2 snooping. Router A serves as an IGMP querier.
  • Page 56 [DeviceA-igmp-snooping] quit # Switch the link mode of GigabitEthernet 3/1/1 through GigabitEthernet 3/1/4 to Layer 2 mode, create VLAN 100, assign ports GigabitEthernet 3/1/1 through GigabitEthernet 3/1/4 to this VLAN, and enable IGMP snooping and IGMP snooping proxying in the VLAN. [DeviceA] interface GigabitEthernet 3/1/1 [DeviceA-GigabitEthernet3/1/1] port link-mode bridge [DeviceA-GigabitEthernet3/1/1] quit...
  • Page 57 MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 2 port(s). GE3/1/3 GE3/1/4 # Display information about IGMP groups on Router A. [RouterA] display igmp group Total 1 IGMP Group(s). Interface group report information of VPN-Instance: public net GigabitEthernet3/1/1(10.1.1.1): Total 1 IGMP Group reported Group Address Last Reporter Uptime...

  • Page 58: Troubleshooting Igmp Snooping

    Troubleshooting IGMP snooping Layer 2 multicast forwarding cannot function Symptom Layer 2 multicast forwarding cannot function. Analysis IGMP snooping is not enabled. Solution Use the display current-configuration command to view the running status of IGMP snooping. If IGMP snooping is not enabled, use the igmp-snooping command in system view to enable IGMP snooping globally, and then use the igmp-snooping enable command in VLAN view to enable IGMP snooping for the VLAN.

  • Page 59: Appendix

    Appendix Processing of multicast protocol messages With Layer 3 multicast routing enabled, an IGMP snooping–enabled router processes multicast protocol messages differently under different conditions, as follows: If only IGMP is enabled on the router, or if both IGMP and PIM are enabled on the router, the router •...

  • Page 60: Configuring Pim Snooping

    Configuring PIM snooping Overview Protocol Independent Multicast (PIM) snooping runs on Layer 2 devices. It determines which ports are interested in multicast data by analyzing the received PIM messages, and adds the ports to a multicast forwarding entry to make sure that multicast data can be forwarded to only the ports that are interested in the data.

  • Page 61: Configuring Pim Snooping

    When running IGMP snooping without PIM snooping, the Layer 2 switch maintains the router ports according to PIM hello messages received from PIM-capable routers, broadcasts all other types of received PIM messages in the VLAN, and forwards all multicast data to all router ports in the VLAN. Each PIM-capable router in the VLAN, whether interested in the multicast data or not, will receive all multicast data and all PIM messages except for PIM hello messages.

  • Page 62: Pim Snooping Configuration Example

    Task Command Remarks display pim-snooping neighbor [ vlan vlan-id ] Display PIM snooping [ slot slot-number ] [ | { begin | exclude | Available in any view. neighbor information. include } regular-expression ] display pim-snooping routing-table [ vlan Display PIM snooping routing vlan-id ] [ slot slot-number ] [ | { begin | exclude Available in any view.
  • Page 63 [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] pim sm [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface GigabitEthernet 3/1/2 [RouterA-GigabitEthernet3/1/2] pim sm [RouterA-GigabitEthernet3/1/2] quit [RouterA] pim [RouterA-pim] c-bsr GigabitEthernet 3/1/2 [RouterA-pim] c-rp GigabitEthernet 3/1/2 On Router B, enable IP multicast routing, and enable PIM-SM on each interface. <RouterB>...

  • Page 64: Troubleshooting Pim Snooping

    [RouterE-GigabitEthernet3/1/4] quit [RouterE] vlan 100 [RouterE-vlan100] port GigabitEthernet 3/1/1 to GigabitEthernet 3/1/4 [RouterE-vlan100] igmp-snooping enable [RouterE-vlan100] pim-snooping enable [RouterE-vlan100] quit Verify the configuration # On Router E, display PIM snooping neighbor information about VLAN 100. [RouterE] display pim-snooping neighbor vlan 100 Total number of neighbors: 4 VLAN ID: 100 Total number of neighbors: 4...

  • Page 65: Some Downstream Pim-Capable Routers Cannot Receive Multicast Data

    Analysis IGMP snooping or PIM snooping is not enabled on the router. Solution Use the display current-configuration command to check the status of IGMP snooping and PIM snooping. If IGMP snooping is not enabled, enter system view and use the igmp-snooping command to enable IGMP snooping globally.

  • Page 66: Configuring Multicast Vlans

    Configuring multicast VLANs Overview As shown in Figure 20, in the traditional multicast programs-on-demand mode, when hosts that belong to different VLANs, Host A, Host B, and Host C require the same multicast program on demand service simultaneously, Router A needs to forward a separate copy of the multicast data in each user VLAN to the Layer 2 device, Device A.

  • Page 67: Multicast Vlan Configuration Task List

    Figure 21 Sub-VLAN-based multicast VLAN After the configuration, IGMP snooping manages router ports in the multicast VLAN and member ports in the sub-VLANs. When forwarding multicast data to Device A, Router A needs to send only one copy of multicast traffic to Device A in the multicast VLAN, and Device A distributes the traffic to the multicast VLAN's sub-VLANs that contain receivers.

  • Page 68: Configuration Procedure

    You can configure the maximum number of entries in the IGMP snooping forwarding table of a multicast VLAN. When the number of forwarding entries maintained for a multicast VLAN reaches the upper limit, the system does not automatically remove any existing entries or create any new entries. HP recommends that you remove excessive entries manually.

  • Page 69: Multicast Vlan Configuration Example

    Multicast VLAN configuration example Network requirements As shown in Figure 22, IGMPv2 runs on Router A, IGMPv2 snooping runs on Switch A, and Router A acts as the IGMP querier. The multicast source sends multicast data to the multicast group 224.1.1.1. Host A, Host B, and Host C are receivers of the multicast data.
  • Page 70 [RouterA-Vlan-interface20] ip address 1.1.1.2 24 [RouterA-Vlan-interface20] pim dm [SwitchA-Vlan-interface20] quit # Create VLAN 10. Configure GigabitEthernet 3/1/1 as a hybrid port and to permit packets from VLAN 10 to pass and tag the packets when forwarding them. [RouterA] vlan 10 [RouterA-vlan10] quit [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] port link-mode bridge...
  • Page 71 # Configure VLAN 10 as a multicast VLAN and configure VLAN 2 through VLAN 4 as sub-VLANs of this multicst VLAN. [SwitchA] multicast-vlan 10 [SwitchA-mvlan-10] subvlan 2 to 4 [SwitchA-mvlan-10] quit Verify the configuration: # Display information about the multicast VLAN on Switch A. [SwitchA] display multicast-vlan Total 1 multicast-vlan(s) Multicast vlan 10...
  • Page 72 MAC group address:0100-5e01-0101 Host port(s):total 1 port(s). GE3/1/3 Vlan(id):4. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 0 port(s). 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): Host port(s):total 1 port(s).

  • Page 73: Configuring Multicast Routing And Forwarding

    Configuring multicast routing and forwarding Overview In multicast implementations, multicast routing and forwarding are implemented by the following types of tables: • 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 74 The router automatically chooses an optimal MBGP route by searching its MBGP routing table, using the IP address of the "packet source" as the destination address. The outgoing interface in the corresponding routing entry is the RPF interface and the next hop is the RPF neighbor. The router automatically chooses an optimal static multicast route by searching its static multicast routing table, using the IP address of the "packet source"...

  • Page 75: Static Multicast Routes

    If the RPF interface is not the incoming interface, this means the (S, G) entry has expired, and router replaces the incoming interface with the RPF interface. If the interface on which the packet arrived in the RPF interface, the router forwards the packet out of all the outgoing interfaces;...
  • Page 76 As shown in Figure 24, when no static multicast route is configured, Router C’s RPF neighbor on the path back to the source is Router A and the multicast information from the source travels along the path from Router A to Router C, which is the unicast route between the two routers; with a static route configured on Router C and Router B as Router C’s RPF neighbor on the path back to the source, the multicast information from the source travels from Router A to Router B and then to Router C.

  • Page 77: Multicast Forwarding Across Unicast Subnets

    NOTE: Static multicast routes affect only RPF checks and they cannot guide multicast forwarding. • A static multicast route is effective only on the multicast router on which it is configured, and will not be • advertised throughout the network or redistributed to other routers. Multicast forwarding across unicast subnets There may be routers that do not support multicast protocols in a network.

  • Page 78: Configuration Task List

    Introduction to multicast traceroute packets A multicast traceroute packet is a special IGMP packet, which differs from common IGMP packets in that its IGMP Type field is set to 0x1F or 0x1E and that its destination IP address is a unicast address. There are three types of multicast traceroute packets: •...

  • Page 79: Configuring Multicast Routing And Forwarding

    Step Command Remarks Enter system view. system-view Enable IP multicast routing. multicast routing-enable Disabled by default. Enabling IP multicast routing in a VPN instance Step Command Remarks Enter system view. system-view Create a VPN instance and ip vpn-instance vpn-instance-name enter VPN instance view. Configure a route route-distinguisher distinguisher (RD) for the VPN...

  • Page 80: Configuring A Multicast Routing Policy

    Step Command Remarks ip rpf-route-static [ vpn-instance vpn-instance-name ] source-address { mask | mask-length } [ protocol Configure a static No static multicast route [ process-id ] ] [ route-policy policy-name ] multicast route. is configured by default. { rpf-nbr-address | interface-type interface-number } [ preference preference ] [ order order-number ] Delete static multicast delete ip rpf-route-static [ vpn-instance...

  • Page 81: 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. Currently, you can define a multicast forwarding range by specifying boundary interfaces, which form a closed multicast forwarding area. You can configure a forwarding boundary specific to a particular multicast group on all interfaces that support multicast forwarding.

  • Page 82: Configuring Rpf Check Failure Processing

    Step Command Remarks Optional. The default upper limit varies with the system operating modes and views. Configure the maximum • In system view: number of forwarding entries multicast forwarding-table In SPE or SPC in the multicast forwarding route-limit limit mode—16384. table.
  • Page 83 corresponding VLAN interface, you need to use the reset igmp group port-info command to clear Layer 2 port information for all IGMP multicast groups in the VLAN and use the reset igmp group command clear all IGMP multicast group information on the corresponding VLAN interface. Otherwise this configuration cannot take effect.

  • Page 84: Tracing A Multicast Path

    Step Command Remarks Enter system view. system-view Enable delivering packets that have failed an RPF check to multicast rpf-fail-pkt trap-to-cpu Disabled by default. the CPU. Tracing a multicast path You can run the mtracert command to trace the path down which the multicast traffic flows from the first-hop router to the last-hop router.

  • Page 85: Configuration Examples

    Task Command Remarks Available in any view. Display the DF display multicast [ all-instance | vpn-instance information of the vpn-instance-name ] forwarding-table df-info For more information about multicast forwarding [ rp-address ] [ slot slot-number ] [ | { begin | exclude designated forwarder (DF), see table.
  • Page 86 Figure 27 Network diagram Router C GE3/1/2 GE3/1/1 40.1.1.1/24 20.1.1.2/24 PIM-DM GE3/1/2 GE3/1/2 40.1.1.2/24 20.1.1.1/24 Router A Router B GE3/1/3 GE3/1/3 30.1.1.2/24 30.1.1.1/24 GE3/1/1 GE3/1/1 50.1.1.1/24 10.1.1.1/24 Source Receiver 50.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 27.

  • Page 87: Creating An Rpf Route

    [RouterA] interface GigabitEthernet 3/1/3 [RouterA-GigabitEthernet3/1/3] pim dm [RouterA-GigabitEthernet3/1/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 display the RPF route to the source on Router B. [RouterB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: VPN instance: public net...
  • Page 88 Figure 28 Network diagram PIM-DM OSPF domain Router A Router B Router C GE3/1/2 GE3/1/3 GE3/1/2 30.1.1.2/24 30.1.1.1/24 20.1.1.1/24 GE3/1/2 20.1.1.2/24 GE3/1/1 GE3/1/1 GE3/1/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 Configure the IP address and subnet mask for each interface as per Figure 28.

  • Page 89: Multicast Forwarding Over Gre Tunnels

    No information is displayed. This means that no RPF route to the 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 the source 2.
  • Page 90 Figure 29 Network diagram Multicast router Unicast router Multicast router Router A Router B Router C GE3/1/2 GE3/1/2 GE3/1/1 GE3/1/2 20.1.1.1/24 30.1.1.2/24 20.1.1.2/24 30.1.1.1/24 GE3/1/1 GE3/1/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 Configure the IP address and mask for each interface as per Figure 29.
  • Page 91 <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 92: Troubleshooting Multicast Routing And Forwarding

    # View the 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...

  • Page 93: Multicast Data Fails To Reach Receivers

    Check the type of next hop interface type 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. Check that the static multicast route matches the specified routing protocol.

  • Page 94: Configuring Igmp

    Configuring IGMP Overview As a TCP/IP protocol responsible for IP multicast group membership management, the Internet Group Management Protocol (IGMP) is used by IP hosts and adjacent multicast routers to establish and maintain their multicast group memberships. IGMP has the following three versions: IGMPv1 (documented in RFC 1 1 12) •...
  • Page 95 Figure 30 IGMP queries and reports IP network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report Assume that Host B and Host C will receive multicast data addressed to multicast group G1, and Host A will receive multicast data addressed to G2, as shown in Figure 30.

  • Page 96: Igmpv2 Enhancements

    IGMPv2 enhancements 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 97 If it needs to receive multicast data from specific sources like S1, S2, …, it sends a report with the • Filter-Mode denoted as "Include Sources (S1, S2, …)". If it needs to reject multicast data from specific sources like S1, S2, …, it sends a report with the •...

  • Page 98: Igmp Ssm Mapping

    IS_EX—The source filtering mode is Exclude. Namely, the report sender requests the multicast data from any sources but those defined in the specified multicast source list. TO_IN—The filtering mode has changed from Exclude to Include. TO_EX—The filtering mode has changed from Include to Exclude. 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.

  • Page 99: Igmp Proxying

    With the IGMP SSM mapping feature configured, when Router A receives an IGMPv1 or IGMPv2 report, it checks the multicast group address G carried in the message: If G is not in the SSM group range, Router A cannot provide the SSM service but can provide the •...

  • Page 100: Multi-Instance Igmp

    Downstream interface—An interface that is running IGMP and is not in the direction toward the • root of the multicast forwarding tree. A downstream interface acts as a router that is running IGMP. Therefore, it is also called the "router interface". •...

  • Page 101: Configuring Basic Igmp Functions

    Task Remarks Enabling SSM mapping Optional. Configuring IGMP SSM mapping Configuring SSM mappings Optional. Enabling IGMP proxying Optional. Configuring IGMP proxying Configuring multicast forwarding on a downstream Optional. interface For the configuration tasks in this section: In IGMP view, the configuration is effective on all interfaces. In interface view, the configuration is •...

  • Page 102: Configuring Igmp Versions

    Step Command Remarks Enable IGMP. igmp enable Disabled by default. Enabling IGMP in a VPN instance Step Command Remarks Enter system view. system-view Create a VPN instance and ip vpn-instance vpn-instance-name enter VPN instance view. Configure an RD for the VPN route-distinguisher No RD is configured by default.

  • Page 103: Configuring Static Joining

    Step Command Remarks Configure an IGMP version igmp version version-number IGMPv2 by default. on the interface. Configuring static joining After an interface is configured as a static member of a multicast group or a multicast source group, it will act as a virtual member of the multicast group to receive multicast data addressed to that multicast group for the purpose of testing multicast data forwarding.

  • Page 104: Setting The Maximum Number Of Multicast Groups That An Interface Can Join

    A multicast group filter does not function for statically joined multicast groups on interfaces. • Configuration procedure To configure a multicast group filter: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no multicast group filter is configured on this interface.

  • Page 105: Adjusting Igmp Performance

    Adjusting IGMP performance For the configuration tasks described in this section: • In IGMP view, the configuration is effective on all interfaces. In interface view, the configuration is effective on only the current interface. If the same feature is configured in both IGMP view and interface view, the configuration in •...

  • Page 106: Configuring Igmp Query And Response Parameters

    Step Command Remarks Enter public network IGMP igmp [ vpn-instance view or VPN instance IGMP vpn-instance-name ] view. 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.
  • Page 107 For IGMP group-specific queries and IGMP group-and-source-specific queries, the maximum • response time equals the IGMP last-member query interval. 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 timer expires, it considers that the querier has failed and starts a new querier election.

  • Page 108: Configuring Igmp Fast-Leave Processing

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the IGMP querier's igmp robust-count robust-value 2 by default. robustness variable. By default, the startup query Configure the startup query igmp startup-query-interval interval is 1/4 of the "IGMP interval.

  • Page 109: Enabling The Igmp Host Tracking Function

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

  • Page 110: Configuring Igmp Ssm Mapping

    Configuring IGMP SSM mapping Due to some possible restrictions, some receiver hosts on an SSM network might run IGMPv1 or IGMPv2. To provide SSM service support for these receiver hosts, configure the IGMP mapping feature on the last hop router. 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...

  • Page 111: Configuring Igmp Proxying

    Step Command Remarks Configure an IGMP SSM ssm-mapping group-address { mask | No IGMP mappings are mapping. mask-length } source-address configured by default. Configuring IGMP proxying 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 •...

  • Page 112: Displaying And Maintaining Igmp

    However, when a downstream interface of a proxy device fails to win the querier election, you must enable multicast forwarding on this interface. On a multi-access network with more than one IGMP proxy device, you cannot enable multicast forwarding on any other non-querier downstream interface after one of the downstream interfaces of these IGMP proxy devices has been elected as the querier.
  • Page 113 Task Command display igmp [ all-instance | vpn-instance Display the information of vpn-instance-name ] proxying group Available in any view. IGMP proxying groups. [ group-address ] [ verbose ] [ | { begin | exclude | include } regular-expression ] display igmp [ all-instance | vpn-instance vpn-instance-name ] routing-table [ source-address [ mask { mask |...

  • Page 114: Igmp Configuration Examples

    IGMP configuration examples Basic IGMP functions configuration example Network requirements Receivers receive VOD information through multicast. Receivers of different organizations form stub networks N1 and N2, and Host A and Host C are receivers in N1 and N2 respectively. IGMPv2 runs between Router A and N1. IGMPv2 runs between the other two routers and N2. Router B acts as the IGMP querier in N2 because it has a lower IP address.
  • Page 115 [RouterA-Pos5/1/1] quit # On Router B, enable IP multicast routing globally, enable IGMP on GigabitEthernet 3/1/1, and enable PIM-DM on each interface. <RouterB> system-view [RouterB] multicast routing-enable [RouterB] interface GigabitEthernet 3/1/1 [RouterB-GigabitEthernet3/1/1] igmp enable [RouterB-GigabitEthernet3/1/1] pim dm [RouterB-GigabitEthernet3/1/1] quit [RouterB] interface POS 5/1/1 [RouterB-Pos5/1/1] pim dm [RouterB-Pos5/1/1] quit # On Router C, enable IP multicast routing globally, enable IGMP on GigabitEthernet 3/1/1, and...

  • Page 116: Ssm Mapping Configuration Example

    SSM mapping configuration example Network requirements The PIM-SM domain applies both the ASM model and SSM model for multicast delivery. Router D's GigabitEthernet 3/1/3 serves as the C-BSR and C-RP. The SSM group range is 232.1.1.0/24. IGMPv3 runs on Router D's GigabitEthernet 3/1/1. The Receiver host runs IGMPv2, and does not support IGMPv3.
  • Page 117 # On Router D, enable IP multicast routing, enable IGMPv3 and IGMP SSM mapping on GigabitEthernet 3/1/1, and enable PIM-SM on each interface. <RouterD> system-view [RouterD] multicast routing-enable [RouterD] interface GigabitEthernet 3/1/1 [RouterD-GigabitEthernet3/1/1] igmp enable [RouterD-GigabitEthernet3/1/1] igmp version 3 [RouterD-GigabitEthernet3/1/1] igmp ssm-mapping enable [RouterD-GigabitEthernet3/1/1] pim sm [RouterD-GigabitEthernet3/1/1] quit [RouterD] interface GigabitEthernet 3/1/2...
  • Page 118 [RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.1.1 [RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.3.1 [RouterD-igmp] quit Verify the configuration # Display the IGMP SSM mapping information for multicast group 232.1.1.1 on the public network on Router D. [RouterD] display igmp ssm-mapping 232.1.1.1 Vpn-Instance: public net Group: 232.1.1.1 Source list: 133.133.1.1...

  • Page 119: Igmp Proxying Configuration Example

    IGMP proxying configuration example Network requirements PIM-DM runs on the core network. Host A and Host C in the stub network receive VOD information sent to multicast group 224.1.1.1. Configure the IGMP proxying feature on Router B so that Router B can maintain group memberships and forward multicast traffic without running PIM-DM.

  • Page 120: Troubleshooting Igmp

    Verify the configuration # Display IGMP information on GigabitEthernet 3/1/1 of Router B. [RouterB] display igmp interface GigabitEthernet 3/1/1 verbose GigabitEthernet3/1/1(192.168.1.2): IGMP proxy is enabled Current IGMP version is 2 Multicast routing on this interface: enabled Require-router-alert: disabled Version1-querier-present-timer-expiry: 00:00:20 # Display IGMP group information on Router A.

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

    Use the display current-configuration command to verify that multicast routing is enabled. If not, use the multicast routing-enable command in system view to enable IP multicast routing. In addition, verify that IGMP is enabled on the corresponding interfaces. Use the display igmp interface command to verify that the IGMP version on the interface is lower than that on the host.

  • Page 122: Configuring Pim

    Configuring PIM Overview Protocol Independent Multicast (PIM) provides IP multicast forwarding by leveraging unicast static routes or unicast routing tables generated by any unicast routing protocol, such as routing information protocol (RIP), open shortest path first (OSPF), intermediate system to intermediate system (IS-IS), or border gateway protocol (BGP).
  • Page 123 Graft • • Assert Neighbor discovery In a PIM domain, a PIM router discovers PIM neighbors, maintains PIM neighboring relationships with other routers, and builds and maintains SPTs by periodically multicasting hello messages to all other PIM routers (224.0.0.13) on the local subnet. NOTE: Every PIM-enabled interface on a router sends hello messages periodically, and thus learns the PIM neighboring information pertinent to the interface.
  • Page 124 Figure 37 SPT establishment Host A Source Receiver Host B Server Receiver Prune message Multicast packets Host C 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.

  • Page 125: Pim-Sm Overview

    Figure 38 Assert mechanism As shown in Figure 38, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets, and both Router A and Router B, on their own downstream interface, receive a duplicate packet forwarded by the other.
  • Page 126 When a multicast source sends a multicast packet to a multicast group, the source-side designated • router (DR) first registers the multicast source with the RP by sending a register message to the RP by unicast. The arrival of this message at the RP triggers the establishment of an SPT. Then, the multicast source sends subsequent multicast packets along the SPT to the RP.
  • Page 127 Figure 39 DR election As shown in Figure 39, the DR election process is as follows: Routers on the multi-access network send hello messages to one another. The hello messages contain the router priority for DR election. The router with the highest DR priority will become the In the case of a tie in the router priority, or if any router in the network does not support carrying the DR-election priority in hello messages, the router with the highest IP address will win the DR election.
  • Page 128 mappings between multicast groups and RPs. The BSR then encapsulates the RP-set in the bootstrap messages it periodically originates and floods the bootstrap messages to the entire PIM-SM domain. Figure 40 BSR messages and C-RP advertisement messages Based on the information in the RP-sets, all routers in the network can calculate the location of the corresponding RPs based on the following rules: The C-RP with the highest priority wins.
  • Page 129 RPT establishment Figure 41 RPT establishment in a PIM-SM domain Host A Source Receiver Host B Server Receiver Join message Multicast packets Host C As shown in Figure 41, the process of building an RPT is as follows: When a receiver joins a multicast group G, it uses an IGMP message to inform the directly connected DR.
  • Page 130 Figure 42 Multicast source registration As shown in Figure 42, the multicast source registers with the RP as follows: When the multicast source S sends the first multicast packet to multicast group G, the DR directly connected with the multicast source, upon receiving the multicast packet, encapsulates the packet in a PIM register message, and sends the message to the corresponding RP by unicast.

  • Page 131: Bidir-Pim Overview

    To solve the issues, PIM-SM allows an RP or the DR at the receiver side to initiate an SPT switchover process: The RP initiates an SPT switchover process Upon receiving the first multicast packet, the RP sends an (S, G) join message hop by hop towards the multicast source to establish an SPT between the DR at the source side and the RP.
  • Page 132 RP discovery BIDIR-PIM uses the same RP discovery mechanism as PIM-SM does. For more information, see "RP discovery." In PIM-SM, an RP must be specified with a real IP address. In BIDIR-PIM, however, an RP can be specified with a virtual IP address, which is called the rendezvous point address (RPA). The link corresponding to the RPA's subnet is called the rendezvous point link (RPL).
  • Page 133 Bidirectional RPT building A bidirectional RPT comprises two parts: receiver-side RPT and source-side RPT. The receiver-side RPT is rooted at the RP and takes the routers directly connected with the receivers as leaves. The source-side RPT is also rooted at the RP but takes the routers directly connected with the sources as leaves. The processes for building these two parts are different.

  • Page 134: Administrative Scoping Overview

    Figure 45 RPT building at the multicast source side As shown in Figure 45, the process of 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 135 The administrative scoping mechanism effectively releases stress on the management in a single-BSR domain and enables provision of zone-specific services using private group addresses. Admin-scoped zones are divided specific to multicast groups. The boundary of the admin-scoped zone is formed by zone border routers (ZBRs). Each admin-scoped zone maintains one BSR, which serves multicast groups within a specific range.

  • Page 136: Pim-Ssm Overview

    Figure 47 Group address range relationship between admin-scoped zones and the global-scoped zone Admin-scope 1 Admin-scope 3 G1 address G3 address Admin-scope 2 Global-scope G2 address − − G2 address Figure 47, the group address ranges of admin-scoped 1 and admin-scoped 2 have no intersection, whereas the group address range of admin-scoped 3 is a subset of the address range of admin-scoped 1.

  • Page 137: Relationships Among Pim Protocols

    DR election • • SPT building Neighbor discovery PIM-SSM uses the same neighbor discovery mechanism as in PIM-DM and PIM-SM. For more information, "Neighbor discovery." DR election PIM-SSM uses a similar DR election mechanism as in PIM-SM. For more information, see "DR election."...

  • Page 138: Pim Support For Vpns

    Figure 49 Relationships among PIM protocols A receiver joins multicast group G. G is in the The receiver specifies a SSM group range? multicast source? BIDIR-PIM is enabled? IGMP SSM mapping is configured for G? G has corresponding Enable PIM-SM for G Enable PIM-SSM for G BIDIR-PIM RP? Enable BIDIR-PIM for G...

  • Page 139: Configuration Prerequisites

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

  • Page 140: Enabling State-Refresh Capability

    Step Command Description Enter system view. system-view Create a VPN instance and ip vpn-instance vpn-instance-name enter VPN instance view. Configure a route-distinguisher route-distinguisher (RD) for the Not configured by default. route-distinguisher VPN instance. Enable IP multicast routing. multicast routing-enable Disabled by default. interface interface-type Enter interface view.

  • Page 141: 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 may cycle in the network. To effectively control the propagation scope of state-refresh messages, you need to configure an appropriate TTL value based on the network size.

  • Page 142: Configuration Prerequisites

    Task Remarks Enabling PIM-SM Required. Configuring a static RP Use at least one approach. In a Configuring a C-RP network only with a static RP, skip the Configuring an RP task of configuring Enabling auto-RP a BSR. Configuring C-RP timers globally Optional.

  • Page 143: Enabling Pim-Sm

    Determine the BS timeout timer. • • Determine the ACL for register message filtering. Determine the register suppression timer. • Determine the register probe timer. • • Determine the ACL rule and sequencing rule for an SPT switchover. Enabling PIM-SM With PIM-SM enabled, a router sends hello messages periodically to discover PIM neighbors and processes messages from the PIM neighbors.

  • Page 144: Configuring An Rp

    For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance commands, see MPLS Command Reference. Configuring an RP An RP can be manually configured or dynamically elected through the BSR mechanism. For a large PIM network, static RP configuration is a tedious job. Generally, static RP configuration is just a backup means for the dynamic RP election mechanism to enhance the robustness and operation manageability of a multicast network.
  • Page 145 Step Command Remarks Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] c-rp interface-type interface-number [ group-policy Configure an interface to be a acl-number | priority priority | No C-RPs are configured by C-RP for PIM-SM. holdtime hold-interval | default.

  • Page 146: Configuring A Bsr

    Step Command Remarks Optional. Configure C-RP timeout time. c-rp holdtime interval 150 seconds by default. For more information about the configuration of other timers in PIM-SM, see "Configuring PIM common timers." 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.
  • Page 147 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 148 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 149: Configuring Administrative Scoping

    message exceeds the maximum transmission unit (MTU). In respect of such IP fragmentation, loss of a single IP fragment leads to unavailability of the entire message. Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to multiple bootstrap message fragments (BSMFs).
  • Page 150 Step Command Remarks Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Disabled by default. An admin-scoped zone can only Enable administrative c-bsr admin-scope serve multicast groups within the scoping. range of 239.0.0.0 to 239.255.255.255.

  • Page 151: Configuring Multicast Source Registration

    Perform the following configuration on the routers that you want to configure as C-BSRs in admin-scoped zones. To configure a C-BSR for an admin-scoped zone: Step Command Remarks Enter system view. system-view Enter public network PIM view pim [ vpn-instance or VPN instance PIM view.

  • Page 152: Configuring Spt Switchover

    probe time, it restarts its register-stop timer; otherwise, the DR starts sending register messages with encapsulated data again when the register-stop timer expires. 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 C-RP routers and configure them to calculate the checksum based on the entire register messages.

  • Page 153: Configuring Bidir-Pim

    Step Command Remarks Optional. spt-switch-threshold infinity By default, the device switches to Configure the SPT switchover. [ group-policy acl-number [ order the SPT immediately after it order-value] ] receives the first multicast packet from the RPT. Configuring BIDIR-PIM BIDIR-PIM configuration task list Task Remarks Enabling PIM-SM...

  • Page 154: Enabling Pim-Sm

    Determine the C-RP priority and the ACL that defines the range of multicast groups to be served by • each C-RP Determine the legal C-RP address range and the ACL that defines the range of multicast groups to • be served. Determine the C-RP-Adv interval.

  • Page 155: Enabling Bidir-Pim

    For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance commands, see MPLS Command Reference. Enabling BIDIR-PIM If BIDIR-PIM is enabled on the public network or in a VPN, the tunnel interfaces on the public network or in the VPN do not support Layer 3 multicasting. Perform this configuration on all routers in the BIDIR-PIM domain.
  • Page 156 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 157: Configuring A Bsr

    messages, and encapsulates its own IP address together with the RP-set information in its bootstrap messages. The BSR then floods the bootstrap messages to all PIM routers in the network. Each C-RP encapsulates a timeout value in its C-RP-Adv messages. Upon receiving a C_RP-Adv message, the BSR obtains this timeout value and starts a C-RP timeout timer.
  • Page 158 When a router in the network is controlled by an attacker or when an illegal router is present in the • network, the attacker can configure this router as a C-BSR and make it win BSR election to control the right of advertising RP information in the network. After being configured as a C-BSR, a router automatically floods the network with bootstrap messages.
  • Page 159 Configuring global C-BSR parameters In each BIDIR-PIM domain, a unique BSR is elected from C-BSRs. The C-RPs in the BIDIR-PIM domain send advertisement messages to the BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the BIDIR-PIM domain. All the routers use the same hash algorithm to get the RP address corresponding to specific multicast groups.
  • Page 160 Step Command Remarks Enter public network PIM view pim [ vpn-instance or VPN instance PIM view. vpn-instance-name ] Optional. By default, the BS period is determined by this formula: BS Configure the BS period. c-bsr interval interval period = (BS timeout – 10) / 2. The default BS timeout is 130 seconds, so the default BS period = (130 –...

  • Page 161: Configuring Administrative Scoping

    NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. However, the semantic fragmentation of BSMs originated due to learning of a new PIM neighbor is performed according to the MTU of the outgoing interface. Configuring administrative scoping With administrative scoping disabled, a BIDIR-PIM domain has only one BSR.
  • Page 162 Configuring C-BSRs for each admin-scoped zone and the global-scope zone In a network with administrative scoping enabled, group-range-specific BSRs are elected from C-BSRs. 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 163: Configuring Pim-Ssm

    Configuring PIM-SSM NOTE: The PIM-SSM model needs the support of IGMPv3. Therefore, be sure to enable IGMPv3 on PIM routers with multicast receivers. PIM-SSM configuration task list Task Remarks Enabling PIM-SM Required. Configuring the SSM group range Optional. Configuring PIM common features Optional.

  • Page 164: Configuring The Ssm Group Range

    Enabling PIM-SM in a VPN instance Step Command Description Enter system view. system-view Create a VPN instance and ip vpn-instance vpn-instance-name enter VPN instance view. Configure an RD for the VPN route-distinguisher No RD is configured by default. instance. route-distinguisher Enable IP multicast routing.

  • Page 165: Pim Common Feature Configuration Task List

    Configurations performed in PIM view are effective on all interfaces, while configurations • performed in interface view are effective on the current interface only. If the same function or parameter is configured in both PIM view and interface view, the •...

  • Page 166: Configuring A Multicast Data Filter

    Configuring a multicast data filter No matter in a PIM-DM domain or a PIM-SM domain, routers can check passing-by multicast data based on the configured filtering rules and determine whether to continue forwarding the multicast data. In other words, PIM routers can act as multicast data filters. These filters can help implement traffic control on one hand, and control the information available to receivers downstream to enhance data security on the other hand.
  • Page 167 DR_Priority (for PIM-SM only)—Priority for DR election. The device with the highest priority wins the • DR election. You can configure this parameter on all the routers in a multi-access network directly connected to multicast sources or receivers. • Holdtime—The timeout time of PIM neighbor reachability state. When this timer times out, if the router has received no hello message from a neighbor, it assumes that this neighbor has expired or become unreachable.

  • Page 168: Configuring The Prune Delay

    Configuring hello options on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the priority for DR pim hello-option dr-priority priority election. 1 by default. Optional. Configure PIM neighbor pim hello-option holdtime interval timeout time.
  • Page 169 Upon receiving a hello message, a PIM router waits a random period, which is smaller than the maximum delay between hello messages, before sending out a hello message. This avoids collisions that occur when multiple PIM routers send hello messages simultaneously. A PIM router periodically sends join/prune messages to its upstream for state update.

  • Page 170: Configuring Join/Prune Message Sizes

    Step Command Remarks Optional. Configure the join/prune pim holdtime join-prune interval timeout time. 210 seconds by default. Optional. Configure assert timeout time. pim holdtime assert interval 180 seconds by default. NOTE: If there are no special networking requirements, we recommend that you use the default settings. Configuring join/prune message sizes A larger join/prune message size will result in loss of a larger amount of information when a message is lost;...

  • Page 171: Displaying And Maintaining Pim

    Step Command Remarks Enter interface view. interface interface-type interface-number Enable PIM to work pim bfd enable Disabled by default. with BFD. For more information about BFD, see High Availability Configuration Guide. Displaying and maintaining PIM Task Command Remarks Display the BSR information display pim [ all-instance | vpn-instance in the PIM-SM domain and vpn-instance-name ] bsr-info [ | { begin |...

  • Page 172: Pim Configuration Examples

    Task Command Remarks display pim [ all-instance | vpn-instance vpn-instance-name ] routing-table [ group-address [ mask { mask-length | mask } ] | source-address [ mask { mask-length | mask } ] | incoming-interface [ interface-type Display PIM routing table. interface-number | register ] | Available in any view.
  • Page 173 Figure 50 Network diagram Table 9 shows the interface and IP address assignment, and network topology scheme. Table 9 Interface and IP address assignment Device Interface IP address Router A GigabitEthernet 3/1/1 10.110.1.1/24 Router A Serial 4/1/9/1:0 192.168.1.1/24 Router B GigabitEthernet 3/1/1 10.110.2.1/24 Router B...
  • Page 174 # Enable IP multicast routing on Router A, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 3/1/1, which connects Router A to N1. <RouterA> system-view [RouterA] multicast routing-enable [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] igmp enable [RouterA-GigabitEthernet3/1/1] pim dm [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface serial 4/1/9/1:0 [RouterA-Serial4/1/9/1:0] pim dm...
  • Page 175 Assume that Host A needs to receive the information addressed to a multicast group G 225.1.1.1. After the multicast source S 10.1 10.5.100/24 sends multicast packets to the multicast group G, an SPT is established through traffic flooding. Routers on the SPT path (Router A and Router D) have their (S, G) entries.

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

    Protocol: pim-dm, UpTime: 00:03:27, Expires: never PIM-SM non-scoped zone configuration example Network requirements Receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire PIM-SM domain contains only one BSR..
  • Page 177 Router C GigabitEthernet 3/1/1 10.110.2.2/24 Router C POS 5/1/1 192.168.3.1/24 Router D GigabitEthernet 3/1/1 10.110.5.1/24 Router D Serial 4/1/9/1:0 192.168.1.2/24 Router D POS 5/1/1 192.168.4.2/24 Router E POS 5/1/1 192.168.3.2/24 Router E POS 5/1/2 192.168.2.2/24 Router E POS 5/1/3 192.168.9.2/24 Router E POS 5/1/4 192.168.4.1/24...
  • Page 178 [RouterD-pim] quit # On Router E, configure the service scope of RP advertisements, specify a C-BSR and a C-RP, and set the hash mask length to 32 and the priority of the C-BSR to 20. . <RouterE> system-view [RouterE] acl number 2005 [RouterE-acl-basic-2005] rule permit source 225.1.1.0 0.0.0.255 [RouterE-acl-basic-2005] quit [RouterE] pim...
  • Page 179 Candidate RP: 192.168.4.2(Pos5/1/1) Priority: 0 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:34 # Display the BSR information and the locally configured C-RP information in effect on Router E. [RouterE] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.2 Priority: 20 hash mask length: 32 State: Elected...
  • Page 180 SPT. Routers on the RPT path (Router A and Router E) have a (*, G) entry, while routers on the SPT path (Router A and Router D) have an (S, G) entry. To view the PIM routing table information on a router, use the display pim routing-table command.

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

    # Display the PIM routing table information on Router E. [RouterE] display pim routing-table VPN-Instance: public net Total 1 (*, G) entry; 0 (S, G) entry (*, 225.1.1.0) RP: 192.168.9.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:13:16 Upstream interface: Register Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information:...
  • Page 182 Figure 52 Network diagram Table 1 1 shows the interface and IP address assignment, and network topology scheme. Table 11 Interface and IP address assignment Device Interface IP address Device Interface IP address Router A GE4/1/1 192.168.1.1/24 Router D S4/1/9/1:0 10.110.4.2/24 Router A S4/1/9/1:0...
  • Page 183 Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 52. (Details not shown.) Configure OSPF for interoperation among the routers in the PIM-SM domain. Ensure the network-layer interoperation among the routers in the PIM-SM domain and enable dynamic update of routing information among the routers through a unicast routing protocol.
  • Page 184 [RouterB-Pos5/1/1] multicast boundary 239.0.0.0 8 [RouterB-Pos5/1/1] quit [RouterB] interface pos 5/1/2 [RouterB-Pos5/1/2] multicast boundary 239.0.0.0 8 [RouterB-Pos5/1/2] quit # On Router C, configure POS 5/1/1 and POS 5/1/2 as the boundary of admin-scoped zone 2. <RouterC> system-view [RouterC] interface Pos 5/1/1 [RouterC-Pos5/1/1] multicast boundary 239.0.0.0 8 [RouterC-Pos5/1/1] quit [RouterC] interface Pos 5/1/2...
  • Page 185 Verify the configuration To view the BSR election information and the C-RP information on a router, use the display pim bsr-info command. For example: # Display the BSR information and the locally configured C-RP information on Router B. [RouterB] display pim bsr-info VPN-Instance: public net Elected BSR Address: 10.110.9.1 Priority: 0...
  • Page 186 Next BSR message scheduled at: 00:01:12 Candidate BSR Address: 10.110.4.2 Priority: 0 hash mask length: 30 State: Elected Scope: 239.0.0.0/8 Candidate RP: 10.110.4.2(Serial4/1/9/1:0) Priority: 0 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:10 # Display the BSR information and the locally configured C-RP information on Router F. [RouterF] display pim bsr-info VPN-Instance: public net Elected BSR Address: 10.110.9.1...

  • Page 187: Bidir-Pim Configuration Example

    Uptime: 00:07:44 Expires: 00:01:51 # Display the RP information on Router D. [RouterD] 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: 0 HoldTime: 150 Uptime: 00:03:42 Expires: 00:01:48 Group/MaskLen: 239.0.0.0/8 RP: 10.110.4.2 (local) Priority: 0 HoldTime: 150 Uptime: 00:06:54...
  • Page 188 Figure 53 Network diagram Loop0 Receiver 1 Receiver 2 Router B GE3/1/1 S2/1/9/2:0 S2/1/9/1:0 Router C Host A Host B S2/1/9/1:0 S2/1/9/2:0 BIDIR-PIM Source 1 Source 2 S2/1/9/1:0 S2/1/9/1:0 GE3/1/1 GE3/1/2 Router A Router D Table 12 shows the interface and IP address assignment, and network topology scheme. Table 12 Interface and IP address assignment Device Interface...
  • Page 189 # On Router A, enable IP multicast routing, enable PIM-SM on each interface, and enable BIDIR-PIM. <RouterA> system-view [RouterA] multicast routing-enable [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] pim sm [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface Serial 2/1/9/1:0 [RouterA-Serial2/1/9/1:0] pim sm [RouterA-Serial2/1/9/1:0] quit [RouterA] pim [RouterA-pim] bidir-pim enable [RouterA-pim] quit # On Router B, enable IP multicast routing, enable PIM-SM on each interface, enable IGMP on...
  • Page 190 [RouterD] multicast routing-enable [RouterD] interface GigabitEthernet 3/1/1 [RouterD-GigabitEthernet3/1/1] igmp enable [RouterD-GigabitEthernet3/1/1] pim sm [RouterD-GigabitEthernet3/1/1] quit [RouterD] interface GigabitEthernet 3/1/2 [RouterD-GigabitEthernet3/1/2] pim sm [RouterD-GigabitEthernet3/1/2] quit [RouterD] interface Serial 2/1/9/1:0 [RouterD-Serial2/1/9/1:0] pim sm [RouterD-Serial2/1/9/1:0] quit [RouterD] pim [RouterD-pim] bidir-pim enable [RouterD-pim] quit On Router C, configure Serial2/1/9/1:0 as a C-BSR, and loopback interface 0 as a C-RP for the entire BIDIR-PIM domain.
  • Page 191 # Display the DF information of BIDIR-PIM on Router D. [RouterD] display pim df-info VPN-Instance: public net RP Address: 1.1.1.1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address GE3/1/1 01:19:53 192.168.3.1 (local) GE3/1/2 00:39:34 192.168.4.1 (local) Ser2/1/9/1:0 Lose 01:21:40 10.110.3.1 # Display the DF information of the multicast forwarding table on Router A. [RouterA] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP...

  • Page 192: Pim-Ssm Configuration Example

    List of 2 DF interfaces: 1: Serial2/1/9/1:0 2: Serial2/1/9/2:0 # Display the DF information of the multicast forwarding table on Router D. [RouterD] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP Total 1 RP matched 00001.
  • Page 193 Figure 54 Network diagram Receiver Host A Router A GE3/1/1 POS5/1/1 Host B POS5/1/3 Receiver GE3/1/1 POS5/1/4 POS5/1/2 GE3/1/1 POS5/1/1 POS5/1/1 Source POS5/1/1 Router D Router E Router B Host C 10.110.5.100/24 POS5/1/1 GE3/1/1 PIM-SSM Host D Router C Table 13 shows the interface and IP address assignment, and network topology scheme.
  • Page 194 Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 54. (Details not shown.) Configure the OSPF protocol for interoperation among the routers in the PIM-SM domain. Ensure the network-layer interoperation in the PIM-SM domain and enable dynamic update of routing information among the routers through a unicast routing protocol.

  • Page 195: Troubleshooting Pim

    (Router A and Router D) have generated (S, G) entry, while Router E, which is not on the SPT path, does not have multicast routing entries. You can use the display pim routing-table command to view the PIM routing table information on each router. For example: # Display the PIM routing table information on Router A.

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

    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. If the router does not have a route to the multicast source, or if PIM-DM is not enabled on the router's RPF interface to the multicast source, the router cannot create (S, G) entries.

  • Page 197: Rps Cannot Join The 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 198: An Rpt Cannot Be Established Or A Source Cannot Register In Pim-Sm

    An RPT cannot be established or a source cannot register 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 199: Configuring Msdp

    Configuring MSDP Overview Multicast source discovery protocol (MSDP) is an inter-domain multicast solution developed to address the interconnection of protocol independent multicast sparse mode (PIM-SM) domains. It is used to discover 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 of a domain is isolated from that of another domain.
  • Page 200 Figure 55 Where MSDP peers are in the network As shown in Figure 55, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers that assume different roles 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 201 Figure 56 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 202 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 203 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). When RP 8 receives the SA message from RP 7, a BGP or MBGP route exists between two MSDP peers in different ASs.

  • Page 204: Multi-Instance Msdp

    The work 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 to RP 1, RP 1 de-encapsulates the message.

  • Page 205: Configuring Msdp Basic Functions

    Task Remarks Configuring SA message content Optional. Configuring SA request messages Optional. Configuring SA messages related parameters Configuring an SA message filtering rules Optional. Configuring the SA cache mechanism Optional. Configuring MSDP basic functions All the configuration tasks should be carried out on RPs in PIM-SM domains, and each of these RPs acts as an MSDP peer.

  • Page 206: Creating An Msdp Peer Connection

    Step Command Description Enable MSDP and enter VPN msdp [ vpn-instance Disabled by default. instance MSDP view. vpn-instance-name ] For more information about the ip vpn-instance and route-distinguisher commands, see MPLS Command Reference. Creating an MSDP peer connection An MSDP peering relationship is identified by an address pair, namely the address of the local MSDP peer and that of the remote MSDP peer.

  • Page 207: Configuring An Msdp Peer Connection

    Configuring an MSDP peer connection Configuration prerequisites Before configuring MSDP peer connection, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the • network layer. Configure basic MSDP functions. • •...

  • Page 208: Configuring Msdp Peer Connection Control

    If you configure more than one mesh group name on an MSDP peer, only the most recent configuration takes effect. 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 209: Configuring Sa Messages Related Parameters

    Step Command Remarks Configure an MD5 Optional. authentication password for peer peer-address password By default, MD5 authentication is the TCP connection to be { cipher cipher-password | simple not performed before a TCP established with an MSDP simple-password } connection is established. peer.

  • Page 210: Configuring Sa Request Messages

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

  • Page 211: Configuring An Sa Message Filtering Rules

    Configuring an SA message filtering rules By configuring an SA message creation rule, you can enable the router to filter the (S, G) entries to be advertised when creating an SA message, so that the propagation of messages of multicast sources is controlled.

  • Page 212: Displaying And Maintaining Msdp

    If the corresponding (S, G) entry exists in the cache, the router joins the corresponding SPT rooted • at S. To protect the router effectively against denial of service (DoS) attacks, you can set a limit on the number of (S, G) entries the router can cache. To configure the SA message cache: Step Command...

  • Page 213: Msdp Configuration Examples

    MSDP configuration examples PIM-SM Inter-domain multicast configuration Network requirements The network has two ASs: AS 100 and AS 200. OSPF is running within each AS, and BGP is running between the two ASs. PIM-SM 1 belongs to AS 100, while PIM-SM 2 and PIM-SM 3 belong to AS 200. Each PIM-SM domain has at least one multicast source or receiver.
  • Page 214 Device Interface IP address Device Interface IP address Router B Loop0 1.1.1.1/32 Router F GE3/1/1 10.110.6.2/24 Router C GE3/1/1 10.110.4.1/24 Router F GE3/1/2 10.110.7.1/24 Router C S4/1/9/1:0 192.168.3.1/24 Source 1 — 10.110.2.100/24 Router C POS5/1/1 192.168.1.2/24 Source 2 — 10.110.5.100/24 Router C Loop0 2.2.2.2/32...
  • Page 215 [RouterB-pim] quit # Configure C-BSRs and C-RPs on Router C and Router E in the same way. (Details not shown.) Configure BGP and configure mutual route redistribution between BGP and OSPF: # Configure an EBGP peer, and redistribute OSPF routes on Router B. [RouterB] bgp 100 [RouterB-bgp] router-id 1.1.1.1 [RouterB-bgp] peer 192.168.1.2 as-number 200...
  • Page 216 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.2 6 00:13:09 Established # Display information about BGP peering relationship on Router C. [RouterC] display bgp peer BGP local router ID : 2.2.2.2 Local AS number : 200 Total number of peers : 1 Peers in established state : 1 Peer MsgRcvd...

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

    192.168.1.1 00:06:39 # Display brief information about MSDP peering relationship on Router E. [RouterE] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count 192.168.3.1 01:07:08 # Display brief information about MSDP peering relationships on Router B.
  • Page 218 Configure Loopback 0 as the C-BSR and C-RP of the related PIM-SM domain on Router A, Router D and Router G. According to the RPF principle, the routers can receive SA messages that pass the filtering policy from its static RPF peers. To share multicast source information among PIM-SM domains without changing the unicast topology structure, configure MSDP peering relationships for the RPs of the PIM-SM domains and configure static RPF peering relationships for the MSDP peers to share multicast source information among the PIM-SM domains.
  • Page 219 Configuration procedure Assign an IP address and subnet mask to each interface as per Figure 60. (Details not shown.) Configure OSPF for interconnection between the routers in each AS. Ensure the network-layer interoperation in each AS, and ensure the dynamic update of routing information through a unicast routing protocol among the routers.
  • Page 220 [RouterD-bgp] router-id 2.2.2.2 [RouterD-bgp] peer 10.110.3.1 as-number 100 [RouterD-bgp] import-route ospf 1 [RouterD-bgp] quit # Configure an EBGP peer, and redistribute OSPF routing information on Router C. [RouterC] bgp 100 [RouterC-bgp] router-id 1.1.1.3 [RouterC-bgp] peer 10.110.4.2 as-number 200 [RouterC-bgp] import-route ospf 1 [RouterC-bgp] quit # Configure an EBGP peer, and redistribute OSPF routing information on Router F.
  • Page 221 [RouterD-msdp] quit # Configure Router A as the MSDP peer and static RPF peer of Router G. [RouterG] ip ip-prefix list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32 [RouterG] msdp [RouterG-msdp] peer 10.110.2.1 connect-interface GigabitEthernet 3/1/1 [RouterG-msdp] static-rpf-peer 10.110.2.1 rp-policy list-a [RouterG-msdp] quit Verify the configuration Use the display bgp peer command to display the BGP peering relationships between the routers.

  • Page 222: Anycast Rp Configuration

    Anycast RP configuration Network requirements 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 223 Device Interface IP address Device Interface IP address GE3/1/1 10.110.6.1/24 Router B Loop20 10.1.1.1/32 Router E S4/1/9/1:0 10.110.4.2/24 Configuration procedure Assign an IP address and subnet mask to each interface as per Figure 61. (Details not shown.) Configure OSPF for interconnection between the routers in the PIM-SM domain. Ensure the network-layer interoperation among the routers, and ensure the dynamic update of routing information through a unicast routing protocol.
  • Page 224 [RouterB-msdp] originating-rp loopback 0 [RouterB-msdp] peer 2.2.2.2 connect-interface loopback 0 [RouterB-msdp] quit # Configure an MSDP peer on Loopback 0 of Router D. [RouterD] msdp [RouterD-msdp] originating-rp loopback 0 [RouterD-msdp] peer 1.1.1.1 connect-interface loopback 0 [RouterD-msdp] quit Verify the configuration You can use the display msdp brief command to view the brief information of MSDP peering relationships between the routers.
  • Page 225 Protocol: igmp, UpTime: 00:15:04, Expires: - (10.110.5.100, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: SPT 2MSDP ACT UpTime: 00:46:28 Upstream interface: Serial4/1/9/1:0 Upstream neighbor: 10.110.2.2 RPF prime neighbor: 10.110.2.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet3/1/1 Protocol: pim-sm, UpTime: - , Expires: # Display PIM routing information on Router D.

  • Page 226: Sa Message Filtering Configuration

    RPF prime neighbor: 10.110.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet3/1/1 Protocol: pim-sm, UpTime: - , Expires: SA message filtering configuration Network requirements There are three PIM-SM domains, with OSPF running within each domain and among these domains to provide unicast routes.
  • Page 227 Device Interface IP address Router A Serial 4/1/9/1:0 10.110.2.1/24 Router A POS 5/1/1 192.168.1.1/24 Router A Loopback 0 1.1.1.1/32 Router B GigabitEthernet 3/1/1 10.110.3.1/24 Router B Serial 4/1/9/1:0 10.110.2.2/24 Router B POS 5/1/1 192.168.2.1/24 Router C GigabitEthernet 3/1/1 10.110.4.1/24 Router C Serial 4/1/9/1:0 10.110.5.1/24 Router C...
  • Page 228 # Configure PIM domain borders on Router C. [RouterC] interface pos 5/1/1 [RouterC-Pos5/1/1] pim sm [RouterC-Pos5/1/1] pim bsr-boundary [RouterC-Pos5/1/1] quit [RouterC] interface pos 5/1/2 [RouterC-Pos5/1/2] pim sm [RouterC-Pos5/1/2] pim bsr-boundary [RouterC-Pos5/1/2] quit [RouterC] interface serial 4/1/9/1:0 [RouterC-Serial4/1/9/1:0] pim sm [RouterC-Serial4/1/9/1:0] pim bsr-boundary [RouterC-Serial4/1/9/1:0] quit # Configure PIM domain borders on Router A, Router B, and Router D in the same way.

  • Page 229: Troubleshooting Msdp

    [RouterC-msdp] quit # Configure an SA message filter on Router D so that Router D will not create SA messages for Source 2. [RouterD] acl number 2001 [RouterD-acl-basic-2001] rule deny source 10.110.6.100 0 [RouterD-acl-basic-2001] quit [RouterD] msdp [RouterD-msdp] import-source acl 2001 [RouterD-msdp] quit Verify the configuration # Display the (S, G) entries in the SA cache on Router C.

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

    Analysis A TCP connection–based MSDP peering relationship is established between the local interface • address and the MSDP peer after the configuration. • The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer address configured on the peer router.
  • Page 231 If you configure the originating-rp command, MSDP replaces the RP address in the SA messages • with the address of the interface specified in the command. When an MSDP peer receives an SA message, it performs RPF check on the message. If the MSDP •...

  • Page 232: Configuring Mbgp

    Configuring MBGP This chapter covers configuration tasks related to multiprotocol BGP for IP multicast only. For more information about BGP, see Layer 3—IP Routing Configuration Guide. 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.

  • Page 233: Configuring Mbgp Basic Functions

    Task Remarks Configuring MBGP route dampening Optional Configuring MBGP route preferences Configuring the default local preference Configuring MBGP Configuring the MED attribute Optional route attributes Configuring the NEXT_HOP attribute Configuring the AS_PATH attribute Configuring MBGP soft reset Optional Tuning and Enabling the MBGP ORF capability Optional optimizing MBGP...

  • Page 234: 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. The ORIGIN attribute of routes redistributed into the MBGP routing table with the import-route command is Incomplete.

  • Page 235: Configuring Mbgp Route Summarization

    Step Command Remarks Enable default route redistribution into the MBGP default-route imported Not enabled by default. routing table. Configuring MBGP route summarization To reduce the routing table size on medium and large MBGP networks, you need to configure route summarization on peers. MBGP supports automatic and manual summarization modes. •...

  • Page 236: Configuring Outbound Mbgp Route Filtering

    Step Command Remarks Not advertised by default. peer { group-name | With the peer default-route-advertise ip-address } command executed, the router sends a Advertise a default route to an default-route-advertise default route with the next hop being MBGP peer or peer group. [ route-policy itself to the specified MBGP peer or peer route-policy-name ]...

  • Page 237: 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/peer group: peer { group-name | peer-address } route-policy...

  • Page 238: Configuring Mbgp Route Dampening

    Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. • 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/peer group:...

  • Page 239: Configuring Mbgp Route Attributes

    Step Command Remarks Enter BGP view. bgp as-number 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.

  • Page 240: Configuring The Med Attribute

    Step Command Remarks Optional. Configure the default local default local-preference value preference. 100 by default. 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...

  • Page 241: Configuring The As_Path Attribute

    Step Command Remarks Optional. By default, the next hop of routes sent to a MBGP Specify the router as the next peer { group-name | ip-address } EBGP peer/peer group is hop of routes sent to a peer/peer next-hop-local the advertising router, but group.

  • Page 242: Configuring Mbgp Soft Reset

    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. However, if a peer not supporting route-refresh exists in the network, you need to configure the peer keep-all-routes command to save all routes from the peer.

  • Page 243: Enabling The Mbgp Orf Capability

    Step Command Remarks 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 244: Configuring The Maximum Number Of Mbgp Routes For Load Balancing

    Table 18 Description of the both, send, and receive parameters and the negotiation result Local parameter Peer parameter Negotiation result The ORF sending capability is enabled locally and • receive send the ORF receiving capability is enabled on the • both peer.

  • Page 245: Configuring Mbgp Community

    Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number group group-name [ external | Create a BGP peer group. Not created by default. internal ] Add a peer into the peer peer ip-address group group-name By default, no peer is added. group.

  • Page 246: Configuring An Mbgp Route Reflector

    Configuring an MBGP route reflector To guarantee the connectivity between multicast IBGP peers in an AS, you need to make them fully meshed. But this becomes unpractical when large numbers of multicast IBGP peers exist. Configuring route reflectors can solve this problem. In general, it is not required that clients of a route reflector be fully meshed.
  • Page 247 Task Command Remarks display bgp multicast paths [ as-regular-expression | Available in Display AS path information. | { begin | exclude | include } regular-expression ] any view. Display MBGP peer/peer group display bgp multicast peer [ [ ip-address ] verbose ] [ | Available in information.

  • Page 248: Resetting Mbgp Connections

    Resetting MBGP connections Task Command Remarks reset bgp ipv4 multicast { all | Reset specified MBGP as-number | ip-address | group Available in user view. connections. group-name | external | internal } Clearing MBGP information Task Command Remarks Clear dampened routing reset bgp ipv4 multicast information and release dampening [ ip-address [ mask |...
  • Page 249 Figure 63 Network diagram AS 100 AS 200 Loop0 Loop0 POS5/1/1 POS5/1/1 Router B Receiver Router A GE3/1/1 Source Router D S4/1/9/1:2 S4/1/9/1:1 Router C PIM-SM 1 Loop0 Loop0 PIM-SM 2 MBGP peers Device Interface IP address Device Interface IP address Source 10.110.1.100/24 Router C...
  • Page 250 [RouterC-Serial4/1/9/1:1] quit [RouterC] interface serial 4/1/9/1:2 [RouterC-Serial4/1/9/1:2] pim sm [RouterC-Serial4/1/9/1:2] quit [RouterC] interface GigabitEthernet 3/1/1 [RouterC-GigabitEthernet3/1/1] pim sm [RouterC-GigabitEthernet3/1/1] igmp enable [RouterC-GigabitEthernet3/1/1] quit # Configure a PIM domain border on Router A. [RouterA] interface pos 5/1/1 [RouterA-Pos5/1/1] pim bsr-boundary [RouterA-Pos5/1/1] quit # Configure a PIM domain border on Router B.
  • Page 251 [RouterB] bgp 200 [RouterB-bgp] router-id 2.2.2.2 [RouterB-bgp] peer 192.168.1.1 as-number 100 [RouterB-bgp] import-route ospf 1 [RouterB-bgp] ipv4-family multicast [RouterB-bgp-af-mul] peer 192.168.1.1 enable [RouterB-bgp-af-mul] import-route ospf 1 [RouterB-bgp-af-mul] quit [RouterB-bgp] quit Configure MSDP peer: # Specify the MSDP peer on Router A. [RouterA] msdp [RouterA-msdp] peer 192.168.1.2 connect-interface pos 5/1/1 [RouterA-msdp] quit...

  • Page 252: Configuring Multicast Vpn

    Configuring multicast VPN Overview Multicast VPN is a technique that implements multicast delivery in virtual private networks (VPNs). Figure 64 Typical VPN networking diagram VPN A VPN B Site 1 Site 2 PE 1 CE 1 CE 2 VPN B VPN A Site 6 Site 3...
  • Page 253 Figure 65 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 254: Md-Vpn Overview

    MD-VPN overview NOTE: For more information about the concepts of Protocol Independent Multicast (PIM), bootstrap router (BSR), candidate-BSR (C-BSR), rendezvous point (RP), designated forwarder (DF), candidate-RP (C-RP), shortest path tree (SPT) and rendezvous point tree (RPT), see "Configuring PIM." Basic concepts in MD-VPN Concept Description An MD is a set of VPN instances running on PE devices that can send...
  • Page 255 Introduction to MD-VPN Main points in the implementation of MD-VPN are as follows: The public network of the service provider supports multicast. The PE devices need to support the public instance and multiple VPN instances, each instance running PIM independently. Private network multicast traffic between the PE devices and the CE devices is transmitted on a per-VPN-instance basis, while the public network multicast traffic between the PE devices and the P devices is transmitted through the public instance.
  • Page 256 private network 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 switching. When the rate of a private network multicast stream that entered the public network at a PE device exceeds the switching threshold, the PE chooses an idle address (namely, switch-group) from the switch-group-pool, and encapsulates the multicast packets for that VPN sing that address.

  • Page 257: Protocols And Standards

    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. Protocols and standards draft-rosen-vpn-mcast-08, Multicast in MPLS/BGP IP VPNs How MD-VPN works This section describes the implementation principle of the MD-VPN technology, including establishment of a share-MDT, packet delivery over it, and implementation of multi-AS MD-VPN.
  • Page 258 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 respectively initiate a similar flood-prune process. Finally, three independent SPTs are established in the MD.
  • Page 259 Share-MDT establishment in a BIDIR-PIM network Figure 70 Share-MDT establishment in a BIDIR-PIM network As shown in Figure 70, 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 260: Share-Mdt-Based Delivery

    Share-MDT establishment in a PIM-SSM network Figure 71 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 71, PIM-SSM is enabled in the network and all the PE devices support VPN instance...
  • Page 261 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. These packets are transmitted along the share-MDT, and then de-encapsulated on the remote PE device to go into the normal protocol procedure. Finally a distribution tree is established across the public network.
  • Page 262 Figure 72 Transmission of multicast protocol packets IBGP: 11.1.3.1/24 PE 3 Source Receiver CE 1 CE 2 PE 1 PE 2 Site 1 Site 2 IBGP: 11.1.1.1/24 IBGP: 11.1.2.1/24 S: 192.1.1.1/24 Public instance IBGP peers G: 255.1.1.1 VPN instance join (*, 255.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 263 the remote PE device and transmitted in that VPN site. VPN multicast data flows are forwarded across the public network differently in the following two circumstances: On a VPN that is running PIM-DM or PIM-SSM, the multicast source forwards multicast data to the receivers along the VPN SPT across the public network.

  • Page 264: Mdt Switchover

    PE 1 encapsulates the multicast data by means of GRE, with its BGP interface address as the multicast source address and the share-group address as the multicast group address, to convert it into a normal, public network multicast data packet (11.1.1.1, 239.1.1.1), and then passes the packet to the public instance on PE 1 to have it forwarded to the public network.

  • Page 265: Multi-As Md-Vpn

    NOTE: For a given VPN instance, the share-MDT and the switch-MDT are both forwarding tunnels in the same MD. A share-MDT is uniquely identified by a share-group address, while a switch-MDT is uniquely identified by a switch-group address. Each share-group is uniquely associated with a set of switch-group addresses, namely a switch-group-pool.

  • Page 266: Multicast Vpn Configuration Task List

    Multi-hop EBGP interconnectivity As shown in Figure 75, a VPNs network involves two ASs, AS 1 and AS 2. PE 3 and PE 4 are the autonomous system boundary router (ASBR) for AS 1 and AS 2 respectively. PE 3 and PE 4 are interconnected through their respective public network instance and treat each other as a P device.

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

    Configure MPLS L3VPN on the public network. • • Configure PIM (PIM-DM, PIM-SM, BIDIR-PIM, or PIM-SSM) on the public network. Determine the VPN instance names and route distinguishers (RDs). • Determine the share-group addresses and an MTI numbers. • • Determine the address ranges of switch-group-pools and ACL rules for MDT switching.

  • Page 268: Configuring Mdt Switching Parameters

    Configuration procedure Perform the following configuration on the PE. To configure a share-group and an MTI binding: 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.

  • Page 269: Configuring Bgp Mdt

    To enable the switch-group reuse logging function: Step Command Remarks Enter system view. system-view Enter VPN instance view. ip vpn-instance vpn-instance-name Enable the switch-group reuse multicast-domain log Disabled by default. logging function. switch-group-reuse Configuring BGP MDT If PIM-SSM is running on the public network, you must configure BGP MDT. Configuration prerequisites Before configuring BGP MDT, complete the following tasks: Configure MPLS L3VPN on the public network.

  • Page 270: Configuring A Bgp Mdt Route Reflector

    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 may cause great expenses. To reduce connections between them, you can configure one of them as a route reflector and specify other routers as clients.

  • Page 271: Multicast Vpn Configuration Example

    Task Command Remarks display multicast-domain vpn-instance vpn-instance-name switch-group send Display the switch-group [ group group-address | reuse interval | information sent by the vpn-source-address [ mask { mask-length | Available in any view. specified VPN instance in the mask } ] | vpn-group-address [ mask { mask-length | mask } ] ] * [ | { begin | exclude | include } regular-expression ] display bgp mdt group [ group-name ] [ |...
  • Page 272 Item Network requirements • PE 1: GigabitEthernet 2/1/2 and GigabitEthernet 2/1/3 belong to VPN instance a; GigabitEthernet 2/1/1 and Loopback 1 belong to the public instance. • PE 2: GigabitEthernet 2/1/2 belongs to VPN instance b; GigabitEthernet 2/1/3 belongs to VPN instance a; PE interfaces and VPN instances they GigabitEthernet 2/1/1 and Loopback 1 belong to the public belong to...
  • Page 273 Figure 76 Network diagram VPN a Loop1 VPN b CE a2 VPN a Loop1 CE b1 GE2/1/1 Loop1 Loop1 CE a3 PE 2 GE2/1/1 GE2/1/3 PE 3 Loop2 PE 1 CE b2 GE2/1/1 Public Loop1 CE a1 VPN b VPN a Table 19 shows the interface and IP address assignment, and network topology scheme.
  • Page 274 Configuration procedure Configure PE 1: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS label switching router (LSR) ID, and enable the Label Distribution Protocol (LDP) capability. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing-enable [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls...
  • Page 275 # Assign an IP address to 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 vpn-g internal [PE1-bgp] peer vpn-g connect-interface loopback 1 [PE1-bgp] peer 1.1.1.2 group vpn-g [PE1-bgp] peer 1.1.1.3 group vpn-g [PE1–bgp] ipv4-family vpn-instance a...
  • Page 276 # Create VPN instance b, configure an RD and route target attributes for it. [PE2] ip vpn-instance b [PE2-vpn-instance-b] route-distinguisher 200:1 [PE2-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE2-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 address range of the switch-group-pool.
  • Page 277 [PE2-LoopBack1] pim sm [PE2-LoopBack1] quit # Configure BGP. [PE2] bgp 100 [PE2-bgp] group vpn-g internal [PE2-bgp] peer vpn-g connect-interface loopback 1 [PE2-bgp] peer 1.1.1.1 group vpn-g [PE2-bgp] peer 1.1.1.3 group vpn-g [PE2–bgp] ipv4-family vpn-instance a [PE2-bgp-a] import-route rip 2 [PE2-bgp-a] import-route direct [PE2-bgp-a] quit [PE2–bgp] ipv4-family vpn-instance b [PE2-bgp-b] import-route rip 3...
  • Page 278 <PE3> system-view [PE3] router id 1.1.1.3 [PE3] multicast routing-enable [PE3] mpls lsr-id 1.1.1.3 [PE3] mpls [PE3-mpls] quit [PE3] mpls ldp [PE3-mpls-ldp] quit # Create VPN instance a, configure an RD and route target attributes for it. [PE3] ip vpn-instance a [PE3-vpn-instance-a] route-distinguisher 100:1 [PE3-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE3-vpn-instance-a] vpn-target 100:1 import-extcommunity...
  • Page 279 [PE3] interface GigabitEthernet 2/1/3 [PE3-GigabitEthernet2/1/3] ip binding vpn-instance b [PE3-GigabitEthernet2/1/3] ip address 10.110.6.1 24 [PE3-GigabitEthernet2/1/3] pim sm [PE3-GigabitEthernet2/1/3] quit # Assign an IP address to Loopback 1, and enable PIM-SM. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 1.1.1.3 32 [PE2-LoopBack1] pim sm [PE3-LoopBack1] quit # Bind Loopback 2 to VPN instance b, configure an IP address and enable PIM-SM on the interface.
  • Page 280 The interface MTI 1 will automatically obtain an IP address after BGP peer configuration on PE 3. This address is the loopback interface address specified in the BGP peer configuration. The PIM mode running on MTI 1 is the same as the PIM mode running in VPN instance b. # Configure OSPF.
  • Page 281 # Assign an IP address, enable PIM-SM and LDP capability on the public network interface GigabitEthernet 2/1/3. [P] interface GigabitEthernet 2/1/3 [P-GigabitEthernet2/1/3] ip address 192.168.8.2 24 [P-GigabitEthernet2/1/3] pim sm [P-GigabitEthernet2/1/3] mpls [P-GigabitEthernet2/1/3] mpls ldp [P-GigabitEthernet2/1/3] quit # Assign an IP address to Loopback 1 and enable PIM-SM on the interface. [P] interface loopback 1 [P-LoopBack1] ip address 2.2.2.2 32 [P-LoopBack1] pim sm...
  • Page 282 [CEb1-GigabitEthernet2/1/1] ip address 10.110.8.1 24 [CEb1-GigabitEthernet2/1/1] pim sm [CEb1-GigabitEthernet2/1/1] quit # Assign an IP address and enable PIM-SM on GigabitEthernet 2/1/2. [CEb1] interface GigabitEthernet 2/1/2 [CEb1-GigabitEthernet2/1/2] ip address 10.110.3.2 24 [CEb1-GigabitEthernet2/1/2] pim sm [CEb1-GigabitEthernet2/1/2] quit # Configure RIP. [CEb1] rip 3 [CEb1-rip-3] network 10.0.0.0 Configure CE a2: # Enable IP multicast routing.
  • Page 283 # Enable IP multicast routing. <CEa3> system-view [CEa3] multicast routing-enable # Assign an IP address, and enable IGMP and PIM-SM on GigabitEthernet 2/1/1. [CEa3] interface GigabitEthernet 2/1/1 [CEa3-GigabitEthernet2/1/1] ip address 10.110.10.1 24 [CEa3-GigabitEthernet2/1/1] igmp enable [CEa3-GigabitEthernet2/1/1] pim sm [CEa3-GigabitEthernet2/1/1] quit # Assign an IP address and enable PIM-SM on GigabitEthernet 2/1/2.

  • Page 284: Multi-As Md-Vpn Configuration

    # Display the local share-group information of VPN instance a on PE 2. <PE2> 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.2 # Display the local share-group information of VPN instance b on PE 2. <PE2>...
  • Page 285 Item Network requirements • Configure OSPF separately in AS 100 and AS 200, and configure OSPF between the PEs and CEs. Unicast routing • Establish BGP peer connections between PE 1, PE 2, PE 3 and PE 4 on their respective protocols and MPLS Loopback 1 interface and exchange all private network routes between them.
  • Page 286 Table 20 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 GE4/1/1 10.10.1.1/24 PE 3 GE4/1/1 10.10.2.1/24 PE 1 GE4/1/2 10.11.1.1/24 PE 3 GE4/1/2 192.168.1.2/24 PE 1 GE4/1/3 10.11.2.1/24 PE 3...
  • Page 287 # Create VPN instance b, configure an RD and route target attributes 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. [PE1] ip vpn-instance b [PE1-vpn-instance-b] route-distinguisher 200:1 [PE1-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE1-vpn-instance-b] vpn-target 200:1 import-extcommunity...
  • Page 288 [PE1-bgp] peer pe1-pe4 connect-interface loopback 1 [PE1–bgp] ipv4-family vpn-instance a [PE1-bgp-a] import-route ospf 2 [PE1-bgp-a] import-route direct [PE1-bgp-a] quit [PE1–bgp] ipv4-family vpn-instance b [PE1-bgp-b] import-route ospf 3 [PE1-bgp-b] import-route direct [PE1-bgp-b] quit [PE1–bgp] ipv4-family vpnv4 [PE1–bgp-af-vpnv4] peer 1.1.1.4 enable [PE1–bgp-af-vpnv4] quit [PE1–bgp] quit With BGP peers configured on PE 1, the interfaces MTI 0 and MTI 1 will automatically obtain IP addresses, which are the loopback interface addresses specified in the BGP peer configuration.
  • Page 289 # Assign an IP address, and enable PIM-SM and LDP capability on the public network interface GigabitEthernet 4/1/1. [PE2] interface GigabitEthernet 4/1/1 [PE2-GigabitEthernet4/1/1] ip address 10.10.1.2 24 [PE2-GigabitEthernet4/1/1] pim sm [PE2-GigabitEthernet4/1/1] mpls [PE2-GigabitEthernet4/1/1] mpls ldp [PE2-GigabitEthernet4/1/1] quit # Assign an IP address, and enable PIM-SM and MPLS on the public network interface GigabitEthernet 4/1/2.
  • Page 290 [PE2-bgp] peer 1.1.1.1 group pe2-pe1 [PE2-bgp] group pe2-pe3 external [PE2-bgp] peer pe2-pe3 as-number 200 [PE2-bgp] peer pe2-pe3 route-policy map1 export [PE2-bgp] peer pe2-pe3 label-route-capability [PE2-bgp] peer pe2-pe3 connect-interface loopback 1 [PE2-bgp] peer 1.1.1.3 group pe2-pe3 [PE2–bgp] quit # Configure OSPF. [PE2] ospf 1 [PE2-ospf-1] area 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0...
  • Page 291 [PE3-GigabitEthernet4/1/2] pim sm [PE3-GigabitEthernet4/1/2] mpls [PE3-GigabitEthernet4/1/2] quit # Assign an IP address to Loopback 1, and enable PIM-SM. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 1.1.1.3 32 [PE3-LoopBack1] pim sm [PE3-LoopBack1] quit # Assign an IP address to Loopback 2, and enable PIM-SM. [PE3] interface loopback 2 [PE3-LoopBack2] ip address 22.22.22.22 32 [PE3-LoopBack2] pim sm...
  • Page 292 [PE3-ospf-1-area-0.0.0.0] network 22.22.22.22 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 10.10.0.0 0.0.255.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure a route policy. [PE3] route-policy map1 permit node 10 [PE3-route-policy] apply mpls-label [PE3-route-policy] quit [PE3] route-policy map2 permit node 10 [PE3-route-policy] if-match mpls-label [PE3-route-policy] apply mpls-label [PE3-route-policy] quit Configure PE 4: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR...
  • Page 293 [PE4] interface GigabitEthernet 4/1/1 [PE4-GigabitEthernet4/1/1] ip address 10.10.2.2 24 [PE4-GigabitEthernet4/1/1] pim sm [PE4-GigabitEthernet4/1/1] mpls [PE4-GigabitEthernet4/1/1] mpls ldp [PE4-GigabitEthernet4/1/1] quit # Bind GigabitEthernet 4/1/2 to VPN instance a, configure an IP address and enable PIM-SM on the interface. [PE4] interface GigabitEthernet 4/1/2 [PE4-GigabitEthernet4/1/2] ip binding vpn-instance a [PE4-GigabitEthernet4/1/2] ip address 10.11.3.1 24 [PE4-GigabitEthernet4/1/2] pim sm...
  • Page 294 With BGP peers configured on PE 4, the interfaces MTI 0 and MTI 1 will automatically obtain IP addresses, which are the loopback interface addresses specified in the BGP peer configuration. The PIM mode running on MTI 0 is the same as on the interfaces in VPN instance a, and the PIM mode running on MTI 1 is the same as on the interfaces in VPN instance b.
  • Page 295 [CEa1-pim-a] quit # Configure OSPF. [CEa1] ospf 1 [CEa1-ospf-1] area 0.0.0.0 [CEa1-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [CEa1-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEa1-ospf-1-area-0.0.0.0] quit [CEa1-ospf-1] quit Configure CE b1: # Enable IP multicast routing. <CEb1> system-view [CEb1] multicast routing-enable # Assign an IP address and enable PIM-SM on GigabitEthernet 4/1/1. [CEb1] interface GigabitEthernet 4/1/1 [CEb1-GigabitEthernet4/1/1] ip address 10.11.6.1 24 [CEb1-GigabitEthernet4/1/1] pim sm...
  • Page 296 [CEa2-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEa2-ospf-1-area-0.0.0.0] quit [CEa2-ospf-1] quit Configure CE b2: # Enable IP multicast routing. <CEb2> system-view [CEb2] multicast routing-enable # Assign an IP address and enable IGMP and PIM-SM on GigabitEthernet 4/1/1. [CEb2] interface GigabitEthernet 4/1/1 [CEb2-GigabitEthernet4/1/1] ip address 10.11.8.1 24 [CEb2-GigabitEthernet4/1/1] igmp enable [CEb2-GigabitEthernet4/1/1] pim sm [CEb2-GigabitEthernet4/1/1] quit...

  • Page 297: Troubleshooting Md-Vpn

    # Display the local share-group information of VPN instance a on PE 4. <PE4> 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.4 # Display the local share-group information of VPN instance b on PE 4. <PE4>...

  • Page 298: An Mvrf Cannot Be Created

    An MVRF cannot be created Symptom A VPN instance cannot create an MVRF correctly. Analysis If PIM-SM is running in the VPN instance, the BSR information for the VPN instance is required. • Otherwise, the VPN instance’s MVRF cannot be correctly established. If PIM-SM is running in the VPN instance, the RP information for the VPN instance is required.

  • Page 299: Configuring Mld Snooping

    Configuring MLD snooping Overview A Layer 2 device that runs Multicast Listener Discovery (MLD) snooping establishes a Layer 2 IPv6 multicast forwarding table, which maps ports and IPv6 multicast MAC addresses, by listening to MLD messages exchanged between a Layer 3 multicast device and hosts to manage and control IPv6 multicast data forwarding.
  • Page 300 Figure 79 MLD snooping related ports Receiver Router A Router B GE3/1/1 GE3/1/2 Host A GE3/1/3 Host B Receiver GE3/1/1 GE3/1/2 Source Host C Router C Router port Member port IPv6 multicast packets Host D The following describes the ports involved in MLD snooping, as shown in Figure Router port—Layer 3 multicast device-side port.

  • Page 301: How Mld Snooping Works

    Message before Timer Description Action after expiration expiration When a port dynamically joins a multicast group, the The router removes this router starts or resets an Dynamic member port port from the MLD aging timer for the port. MLD report message. aging timer snooping forwarding When the timer expires,...

  • Page 302: Mld Snooping Proxying

    A router does not forward an MLD report through a non-router port. If the router forwards a report message through a member port, the MLD report suppression mechanism causes all the attached hosts that listen to the reported IPv6 multicast address to suppress their own reports after receiving this report. This makes the router unable to know whether the reported IPv6 multicast group still has active members attached to that port.

  • Page 303: Protocols And Standards

    Figure 80 Network diagram MLD Querier IP network Router A Query from Router A Report from Router B Query from Router B Proxy & Querier Router B Report from Host Host A Host C Receiver Receiver Host B As shown in Figure 80, Router B works as an MLD snooping proxy.

  • Page 304: Mld Snooping Configuration Task List

    MLD snooping configuration task list Task Remarks Enabling MLD snooping Required. Configuring MLD snooping Specifying the version of MLD snooping Optional. basic functions Setting the maximum number of MLD snooping forwarding Optional. entries Configuring aging timers for dynamic ports Optional. Configuring static ports Optional.

  • Page 305: Configuring Mld Snooping Basic Functions

    Configuring MLD snooping basic functions Before configuring the basic functions of MLD snooping, complete the following tasks: • Enable IPv6 forwarding. Configure the corresponding VLANs. • Determine the version of MLD snooping. • Enabling MLD snooping When you enable MLD snooping, follow these guidelines: You must enable MLD snooping globally before you enable it for a VLAN.

  • Page 306: Setting The Maximum Number Of Mld Snooping Forwarding Entries

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Specify the version of MLD mld-snooping version MLDv1 snooping by default. snooping. version-number Setting the maximum number of MLD snooping forwarding entries You can modify the maximum number of MLD snooping forwarding entries. When the number of forwarding entries on the router reaches the upper limit, the router gives a prompt asking you to manually remove the excessive entries.

  • Page 307: Configuring Static Ports

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

  • Page 308: 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 interface-type view or Layer 2 aggregate Use either command. interface-number interface view or enter port group view. • Enter port group view: port-group manual port-group-name...

  • Page 309: Enabling Fast-Leave Processing

    NOTE: Unlike a static member port, a port that you configure as a simulated member host ages out like a dynamic member port. Enabling fast-leave processing The fast-leave processing feature enables the router to process MLD done messages quickly. After the fast-leave processing feature is enabled, when the router receives an MLD done message on a port, it immediately removes that port from the forwarding entry for the multicast group specified in the message.

  • Page 310: Configuring Mld Snooping Querier

    multicast packets within the VLAN it belongs to and forward then to the host, thus affecting normal multicast reception of the host. In addition, the MLD general query and IPv6 PIM hello message sent from the host affects the • multicast routing protocol state on Layer 3 devices, such as the MLD querier or DR election, and may further cause network interruption.

  • Page 311: Configuring Mld Queries And Responses

    devices are present, you can enable MLD snooping querier on a Layer 2 device so that the Layer 2 device can send MLD queries periodically and establish and maintain multicast forwarding entries for IPv6 multicast forwarding at the data link layer. IMPORTANT: It is meaningless to configure an MLD snooping querier in an IPv6 multicast network running MLD.

  • Page 312: Configuring The Source Ipv6 Addresses For Mld Queries

    Step Command Remarks Set the MLD last-listener query last-listener-query-interval interval 1 second by default. interval. Configuring the parameters for MLD queries and responses in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the interval for sending mld-snooping query-interval 125 seconds by default.

  • Page 313: Enabling Mld Snooping Proxying

    Enabling MLD snooping proxying The MLD snooping proxying function works on a per-VLAN basis. After you enable the function in a VLAN, the router works as the MLD snooping proxy for the downstream hosts and upstream router in the VLAN. To enable MLD snooping proxying in a VLAN: Step Command...

  • Page 314: Enabling Dropping Unknown Ipv6 Multicast Data

    In an application, when a user requests a multicast program, the user’s host initiates an MLD report. After receiving this report message, the router resolves the IPv6 multicast group address in the report and looks up the ACL. If a match is found to permit the port that received the report can join this IPv6 multicast group, the router creates an MLD snooping forwarding entry for the IPv6 multicast group and adds the port to the entry.

  • Page 315: Enabling Mld Report Suppression

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable dropping unknown mld-snooping drop-unknown Disabled by default. IPv6 multicast data. NOTE: When enabled to drop unknown IPv6 multicast data, the router still forwards unknown IPv6 multicast data to other router ports in the VLAN.

  • Page 316: Enabling Ipv6 Multicast Group Replacement

    been configured as a simulated member host, the system establishes corresponding forwarding entry for the host after receiving a report from the host. To set the maximum number of IPv6 multicast groups that a port can join: Step Command Remarks Enter system view.

  • Page 317: Enabling The Mld Snooping Host Tracking Function

    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 interface interface-type interface view or Layer 2 Use either command. interface-number aggregate interface view or enter port group view.

  • Page 318: Mld Snooping Configuration Examples

    Task Command Remarks display mld-snooping group [ vlan vlan-id ] Display MLD snooping multicast [ slot slot-number ] [ verbose ] [ | { begin | Available in any view. group information. exclude | include } regular-expression ] display mld-snooping host vlan vlan-id group ipv6-group-address [ source Display information about the ipv6-source-address ] [ slot slot-number ] [ |...
  • Page 319 Figure 81 Network diagram Configuration procedure Enable IPv6 forwarding and assign an IPv6 address and prefix length to each interface as Figure 81. (Details not shown.) On Router A, enable IPv6 multicast routing, enable MLDv1 on GigabitEthernet 3/1/1, and enable IPv6 PIM-DM on each interface.
  • Page 320 [RouterB-acl6-basic-2001] quit [RouterB] mld-snooping [RouterB–mld-snooping] group-policy 2001 vlan 100 [RouterB–mld-snooping] quit [RouterB-vlan100] quit # Configure GigabitEthernet 3/1/3 and GigabitEthernet 3/1/4 to join multicast group FF1E::101 as simulated member hosts. [RouterB] interface GigabitEthernet 3/1/3 [RouterB-GigabitEthernet3/1/3] mld-snooping host-join ff1e::101 vlan 100 [RouterB-GigabitEthernet3/1/3] quit [RouterB] interface GigabitEthernet 3/1/4 [RouterB-GigabitEthernet3/1/4] mld-snooping host-join ff1e::101 vlan 100 [RouterB-GigabitEthernet3/1/4] quit...

  • Page 321: Static Port Configuration Example

    Static port configuration example Network requirements As shown in Figure 82, MLDv1 runs on Router A, and MLDv1 snooping runs on Router B, Router C and Router D, with Router A acting as the MLD querier. Host A and host C are permanent receivers of IPv6 multicast group FF1E::101. GigabitEthernet 3/1/3 and GigabitEthernet 3/1/5 on Switch C are required to be configured as static member ports for multicast group 224.1.1.1 to enhance the reliability of multicast traffic transmission.
  • Page 322 [RouterA-GigabitEthernet3/1/1] mld enable [RouterA-GigabitEthernet3/1/1] pim ipv6 dm [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface GigabitEthernet 3/1/2 [RouterA-GigabitEthernet3/1/2] pim ipv6 dm [RouterA-GigabitEthernet3/1/2] quit Configure Router B: # Enable MLD snooping globally. <RouterB> system-view [RouterB] mld-snooping [RouterB-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 3/1/1 through GigabitEthernet 3/1/3 to this VLAN, and enable MLD snooping in the VLAN.
  • Page 323 [RouterD-GigabitEthernet 3/1/3] mld-snooping static-group ff1e::101 vlan 100 [RouterD- GigabitEthernet 3/1/3] quit [RouterD] interface GigabitEthernet 3/1/5 [RouterD-GigabitEthernet3/1/5] mld-snooping static-group ff1e::101 vlan 100 [RouterD-GigabitEthernet 3/1/5] quit Verify the configuration # Display detailed MLD snooping multicast group information in VLAN 100 on Router B. [RouterB] display mld-snooping group vlan 100 verbose Total 1 IP Group(s).

  • Page 324: Mld Snooping Querier Configuration Example

    IP group address:FF1E::101 (::, FF1E::101): Attribute: Host Port Host port(s):total 2 port(s). GE3/1/3 GE3/1/5 MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 2 port(s). GE3/1/3 GE3/1/5 The output shows that GigabitEthernet 3/1/3 and GigabitEthernet 3/1/5 on Router D have become static member ports for IPv6 multicast group FF1E::101. MLD snooping querier configuration example Network requirements As shown in...
  • Page 325 [RouterA] ipv6 [RouterA] mld-snooping [RouterA-mld-snooping] quit # Create VLAN 100 and add GigabitEthernet 3/1/1 through GigabitEthernet 3/1/3 to VLAN 100. [RouterA] vlan 100 [RouterA-vlan100] port Gigabitethernet 3/1/1 to Gigabitethernet 3/1/3 # Enable MLD snooping and the function of dropping unknown IPv6 multicast packets in VLAN 100.

  • Page 326: Mld Snooping Proxying Configuration Example

    Sent MLDv2 specific sg queries:0. Received error MLD messages:0. MLD snooping proxying configuration example Network requirements As shown in Figure 84, Router A runs MLDv1 and Router B runs MLDv1 snooping. Router A acts as an MLD querier. Configure MLD snooping proxying on Router B, enabling the switch to forward MLD reports and done messages on behalf of attached hosts and to respond to MLD queries from Router A and forward the queries to the hosts on behalf of Router A.
  • Page 327 # Create VLAN 100, assign ports GigabitEthernet 3/1/1 through GigabitEthernet 3/1/4 to this VLAN, and enable MLD snooping and MLD snooping proxying in the VLAN. [RouterB] vlan 100 [RouterB-vlan100] port GigabitEthernet 3/1/1 to GigabitEthernet 3/1/4 [RouterB-vlan100] mld-snooping enable [RouterB-vlan100] mld-snooping proxying enable [RouterB-vlan100] quit Verify the configuration After the configuration is completed, Host A and Host B send MLD join messages addressed to group...

  • Page 328: Troubleshooting Mld Snooping

    When Host A leaves the IPv6 multicast group, it sends an MLD done message to Router B. Receiving the message, Router B removes port GigabitEthernet 3/1/4 from the member port list of the forwarding entry for the group; however, it does not remove the group or forward the done message to Router A because Host B is still in the group.

  • Page 329: Configured Ipv6 Multicast Group Policy Fails To Take Effect

    Configured IPv6 multicast group policy fails to take effect Symptom Although an IPv6 multicast group policy has been configured to allow hosts to join specific IPv6 multicast groups, the hosts can still receive IPv6 multicast data addressed to other groups. Analysis The IPv6 ACL rule is incorrectly configured.
  • Page 330 NOTE: On a router with Layer 3 IPv6 multicast routing enabled, use the display mld group port-info command to display Layer 2 port information. If IPv6 PIM is disabled on the router, one of the following occurs: • If MLD is disabled, the router deletes all its dynamic router ports. If MLD is enabled, the router maintains all its dynamic member ports and dynamic router ports.

  • Page 331: Configuring Ipv6 Pim Snooping

    Configuring IPv6 PIM snooping Overview IPv6 Protocol Independent Multicast (IPv6 PIM) snooping runs on Layer 2 devices. It determines which ports are interested in multicast data by analyzing the received IPv6 PIM messages, and adds the ports to a multicast forwarding entry to make sure that multicast data can be forwarded to only the ports that are interested in the data.

  • Page 332: Configuring Ipv6 Pim Snooping

    other types of received IPv6 PIM messages in the VLAN, and forwards all multicast data to all router ports in the VLAN. Each IPv6 PIM-capable router in the VLAN, whether interested in the multicast data or not, will receive all multicast data and all IPv6 PIM messages except for IPv6 PIM hello messages.

  • Page 333: Ipv6 Pim Snooping Configuration Example

    Task Command Remarks display pim-snooping ipv6 routing-table [ vlan Display IPv6 PIM snooping vlan-id ] [ slot slot-number ] [ | { begin | exclude Available in any view. routing entries. | include } regular-expression ] Display the statistics of IPv6 PIM display pim-snooping ipv6 statistics [ | { begin messages that IPv6 PIM Available in any view.
  • Page 334 [RouterA-GigabitEthernet3/1/1] pim ipv6 sm [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface GigabitEthernet 3/1/2 [RouterA-GigabitEthernet3/1/2] pim ipv6 sm [RouterA-GigabitEthernet3/1/2] quit [RouterA] pim ipv6 [RouterA-pim6] c-bsr 1001::1 [RouterA-pim6] c-rp 1001::1 On Router B, enable IPv6 multicast routing, and enable IPv6 PIM-SM on each interface. <RouterB> system-view [RouterB] multicast ipv6 routing-enable [RouterB] interface GigabitEthernet 3/1/1 [RouterB-GigabitEthernet3/1/1] pim ipv6 sm...

  • Page 335: Troubleshooting Ipv6 Pim Snooping

    [RouterE] vlan 100 [RouterE-vlan100] port GigabitEthernet 3/1/1 to GigabitEthernet 3/1/4 [RouterE-vlan100] mld-snooping enable [RouterE-vlan100] pim-snooping ipv6 enable [RouterE-vlan100] quit Verify the configuration # On Router E, display the IPv6 PIM snooping neighbor information of VLAN 100. [RouterE] display pim-snooping ipv6 neighbor vlan 100 Total number of neighbors: 4 VLAN ID: 100 Total number of neighbors: 4...

  • Page 336: Some Downstream Ipv6 Pim-Capable Routers Cannot Receive Multicast Data

    Solution Use the display current-configuration command to check the status of MLD snooping and IPv6 PIM snooping. If MLD snooping is not enabled, enter system view and use the mld-snooping command to enable MLD snooping globally. Then, enter VLAN view and use the mld-snooping enable and pim-snooping ipv6 enable commands to enable MLD snooping and IPv6 PIM snooping in the VLAN.

  • Page 337: Configuring Ipv6 Multicast Vlans

    Configuring IPv6 multicast VLANs Overview As shown in Figure 87, in the traditional IPv6 multicast programs-on-demand mode, when hosts (Host A, Host B and Host C) that belong to different VLANs, require the same IPv6 multicast programs on demand service simultaneously, the Layer 3 device, Router A, needs to forward a separate copy of the multicast traffic in each user VLAN to the Layer 2 device, Device A.

  • Page 338: Ipv6 Multicast Vlan Configuration Task List

    Figure 88 Sub-VLAN-based IPv6 multicast VLAN After the configuration, MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in the sub-VLANs. When forwarding IPv6 multicast data to Device A, Router A needs to send only one copy of IPv6 multicast traffic to Device A in the IPv6 multicast VLAN, and Device A distributes the traffic to the IPv6 multicast VLAN's sub-VLANs that contain receivers.

  • Page 339: Setting The Maximum Number Of Forwarding Entries For Ipv6 Multicast Vlans

    You can set the maximum number of entries in the MLD snooping forwarding table for IPv6 multicast VLANs. When the number of forwarding entries maintained for the IPv6 multicast VLANs reaches the upper limit, the system does not automatically remove any existing entries or create new entries. HP recommends that you remove excessive entries manually.

  • Page 340: Ipv6 Multicast Vlan Configuration Examples

    IPv6 multicast VLAN configuration examples Network requirements As shown in Figure 89, MLDv1 runs on Router A, MLD snooping runs on Switch A, and Router A acts as the MLD querier. The IPv6 multicast source sends IPv6 multicast data to the IPv6 multicast group FF1E::101. Host A, Host B, and Host C are receivers of the IPv6 multicast group, and they belong to VLAN 2 through VLAN 4 respectively.
  • Page 341 [RouterA] vlan 10 [RouterA-vlan10] quit [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] port link-mode bridge [RouterA-GigabitEthernet3/1/1] port link-type hybrid [RouterA-GigabitEthernet3/1/1] port hybrid vlan 10 tagged [RouterA-GigabitEthernet3/1/1] quit # Configure an IPv6 address on VLAN-interface 10 and enable MLD and IPv6 PIM-DM. [RouterA] interface vlan-interface 10 [RouterA-Vlan-interface10] ipv6 address 2001::1 64 [RouterA-Vlan-interface10] mld enable [RouterA-Vlan-interface10] pim ipv6 dm...
  • Page 342 Verify the configuration # Display the IPv6 multicast VLAN information on Switch A. [SwitchA] display multicast-vlan ipv6 Total 1 IPv6 multicast-vlan(s) IPv6 Multicast vlan 10 subvlan list: vlan 2-4 # Display the MLD snooping IPv6 multicast group information on Switch A. [SwitchA] display mld-snooping group Total 4 IP Group(s).
  • Page 343 Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 0 port(s). 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). GE3/1/4 MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 1 port(s). GE3/1/4 Vlan(id):10.

  • Page 344: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding Overview In IPv6 multicast implementations, multicast routing and forwarding are implemented by the following types of tables: • 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 345 The router automatically chooses an optimal IPv6 MBGP route by searching its IPv6 MBGP routing table, using the IP address of the "packet source" as the destination address. The outgoing interface in the corresponding routing entry is the RPF interface and the next hop is the RPF neighbor.

  • Page 346: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

    incoming interface of the (S, G) entry with the interface that received the packet and forwards the packet out of all the outgoing interfaces. CAUTION: You can configure special processing of packets that have failed an RPF check instead of simply dropping them.

  • Page 347: Configuration Task List

    Figure 91 IPv6 multicast data transmission through a tunnel As shown in Figure 91, with a GRE tunnel established between the multicast routers Router A and Router B, Router A encapsulates the IPv6 multicast data in unicast IPv6 packets, and forwards them to Router B across the GRE tunnel through unicast routers.

  • Page 348: Configuring An Ipv6 Multicast Routing Policy

    Configure IPv6 PIM-DM or IPv6 PIM-SM. • • Determine the maximum number of downstream nodes for a single route IPv6 multicast forwarding table entry. Determine the maximum number of routing entries in the IPv6 multicast forwarding table. • Configuring an IPv6 multicast routing policy You can configure the router to select an RPF route based on the longest match principle.

  • Page 349: Configuring The Ipv6 Multicast Forwarding Table Size

    Step Command Remarks multicast ipv6 boundary { ipv6-group-address prefix-length Configure an IPv6 multicast No forwarding boundary by | scope { scope-id | admin-local | forwarding boundary. default. global | organization-local | site-local } } Configuring the IPv6 multicast forwarding table size The router maintains the corresponding IPv6 forwarding entries for each IPv6 multicast data packet it receives.
  • Page 350 With this feature enabled, the router searches its multicast forwarding table upon receiving an IPv6 multicast data packet that failed RPF check. If a match is found, it multicasts the packet according to the matching entry. Otherwise, the router broadcasts the packet in the VLAN. To enable this feature, you must enable the IPv6 multicast programs-on-demand function.

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

    Delivering packets to the CPU In the following two cases, an IPv6 multicast packet that failed the RPF check must be delivered to the CPU: • If an IPv6 multicast packet arrives on an outgoing interface of the corresponding IPv6 multicast forwarding entry, the packet fails the RPF check and needs to be delivered to the CPU to trigger the assert mechanism to prune the unwanted branch.
  • Page 352 Task Command Remarks display multicast ipv6 forwarding-table [ ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface { interface-type Display the information of the IPv6 Available in any interface-number | register } | multicast forwarding table. view. outgoing-interface { exclude | include | match } { interface-type interface-number | register } | statistics | slot slot-number ] * [ port-info ] [ | { begin | exclude | include } regular-expression ]...

  • Page 353: Multicast Forwarding Over A Gre Tunnel Configuration Example

    Multicast forwarding over a GRE tunnel configuration example Network requirements IPv6 multicast routing and IPv6 PIM-DM are enabled on Router A and Router C. Router B does not support IPv6 multicast. OSPFv3 is running on Router A, Router B, and Router C. Configure a GRE tunnel so that the receiver can receive the IPv6 multicast data from the source.
  • Page 354 [RouterC-Tunnel0] source 3001::2 [RouterC-Tunnel0] destination 2001::1 [RouterC-Tunnel0] quit Configure OSPFv3: # Configure OSPFv3 on Router A. [RouterA] ospfv3 1 [RouterA-ospfv3-1] router-id 1.1.1.1 [RouterA-ospfv3-1] quit [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] ospfv3 1 area 0 [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface GigabitEthernet 3/1/2 [RouterA-GigabitEthernet3/1/2] ospfv3 1 area 0 [RouterA-GigabitEthernet3/1/2] quit [RouterA] interface tunnel 0 [RouterA-Tunnel0] ospfv3 1 area 0...

  • Page 355: Verifying The Configuration

    [RouterA] interface GigabitEthernet 3/1/2 [RouterA-GigabitEthernet3/1/2] pim ipv6 dm [RouterA-GigabitEthernet3/1/2] quit [RouterA] interface tunnel 0 [RouterA-Tunnel0] pim ipv6 dm [RouterA-Tunnel0] quit # On Router C, enable IPv6 multicast routing globally, enable MLD on GigabitEthernet 3/1//1, and enable IPv6 PIM-DM on each interface. [RouterC] multicast ipv6 routing-enable [RouterC] interface GigabitEthernet 3/1/1 [RouterC-GigabitEthernet3/1/1] mld enable...

  • Page 356: Troubleshooting Ipv6 Multicast Policy Configuration

    Protocol: pim-dm, UpTime: 00:04:25, Expires: never The output shows that Router A is the RPF neighbor of Router C and the IPv6 multicast data from Router A is delivered over a GRE tunnel to Router C. Troubleshooting IPv6 multicast policy configuration Abnormal termination of IPv6 multicast data Symptom A host sends an MLD report announcing its joining an IPv6 multicast group (G).

  • Page 357: Configuring Mld

    Configuring MLD Overview The Multicast Listener Discovery protocol (MLD) is used by an IPv6 router 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 358 Joining an IPv6 multicast group Figure 93 MLD queries and reports IPv6 network Querier Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report 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, as shown in Figure 93.

  • Page 359: 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 360: Mld Message Types

    In the case of MLDv1, Host B cannot select IPv6 multicast sources when it joins IPv6 multicast group G. Therefore, IPv6 multicast streams from both the source 1 and the source 2 will flow to Host B whether it needs them or not. When MLDv2 is running on the hosts and routers, Host B can explicitly express its interest in the IPv6 multicast data that the source 1 sends to G (denoted as (S1, G)), rather than the IPv6 multicast data that the source 2 sends to G (denoted as (S2, G)).
  • Page 361 Figure 95 Format of MLDv2 query message Table 22 Description on fields in an MLDv2 query message Field Description Type = 130 Message type. For a query message, this field is set to 130. Code Initialized to zero. Checksum Standard IPv6 checksum. Maximum Response Delay Maximum response delay allowed before a host sends a report message.
  • Page 362 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 363: 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 is running MLDv2 joins a multicast group, it can explicitly specify one or more •...

  • Page 364: 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 the 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 365: Mld Configuration Task List

    RFC 4605, Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD)-Based • Multicast Forwarding ("IGMP/MLD Proxying") MLD configuration task list Task Remarks Enabling MLD Required. Configuring the MLD version Optional. Configuring static joining Optional. Configuring basic MLD functions Configuring an IPv6 multicast group filter Optional.

  • Page 366: Enabling Mld

    Determine the maximum number of IPv6 multicast groups that an interface can join. • Enabling MLD When you enable MLD, follow these guidelines: Enable MLD on the interface on which IPv6 multicast group memberships are to be created and • maintained.

  • Page 367: Configuring Static Joining

    Configuring static joining After an interface is configured as a static member of an IPv6 multicast group or an IPv6 multicast source and group, it will act as a virtual member of the IPv6 multicast group to receive IPv6 multicast data addressed to that IPv6 multicast group for the purpose of testing IPv6 multicast data forwarding.

  • Page 368: Setting The Maximum Number Of Ipv6 Multicast Groups That An Interface Can Join

    Setting the maximum number of IPv6 multicast groups that an interface can join Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number The default value varies with interface views and the system operating modes. In Layer 2 interface view, the default value is 1024 in each system operating mode.

  • Page 369: Configuring Router-Alert Option Handling Methods

    Determine the startup query count. • • Determine the MLD query interval. Determine the MLD querier's robustness variable. • Determine the maximum response delay of MLD general query messages. • • Determine the MLD last listener query interval. Determine the MLD other querier present interval. •...

  • Page 370: Configuring Mld Query And Response Parameters

    Step Command Remarks Configure the interface to By default, the device does not discard any MLD message mld require-router-alert check MLD messages for the without the Router-Alert Router-Alert option. option. Enable the insertion of the By default, MLD messages carry Router-Alert option into MLD mld send-router-alert the Router-Alert option.
  • Page 371 Configuring MLD query and response parameters globally Step Command Remarks Enter system view. system-view Enter MLD view. Configure the MLD querier's robust-count robust-value 2 times by default. robustness variable. By default, the startup query Configure the startup query startup-query-interval interval interval is 1/4 of the "MLD query interval.

  • Page 372: Configuring Mld Fast-Leave Processing

    Step Command Remarks Configure the maximum response delay for MLD mld max-response-time interval 10 seconds by default. general query messages. Configure the MLD last mld last-listener-query-interval 1 second by default. listener query interval. interval By default, the other querier present interval is determined by the formula "Other querier present Configure the MLD other mld timer other-querier-present...

  • Page 373: Enabling The Mld Host Tracking Function

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

  • Page 374: Configuring Mld Ssm Mappings

    Step Command Remarks Enable the MLD SSM mld ssm-mapping enable Disabled by default. mapping feature. NOTE: To ensure SSM service for all hosts on a subnet, regardless of the MLD version running on the hosts, enable MLDv2 on the interface that forwards IPv6 multicast traffic onto the subnet. Configuring MLD SSM mappings By performing this configuration multiple times, you can map an IPv6 multicast group to different IPv6 multicast sources.

  • Page 375: Configuring Ipv6 Multicast Forwarding On A Downstream Interface

    You cannot enable other IPv6 multicast routing protocols (such as IPv6 PIM-DM or IPv6 PIM-SM) on interfaces with MLD proxying enabled, or vice versa. However, the source-lifetime, source-policy, and ssm-policy commands configured in IPv6 PIM view can still take effect. You cannot enable MLD proxying on a VLAN interface with MLD snooping enabled, or vice versa.
  • Page 376 Task Command Remarks display mld group [ ipv6-group-address | Display MLD group interface interface-type interface-number ] [ static Available in any view. information. | verbose ] [ | { begin | exclude | include } regular-expression ] display mld group port-info [ vlan vlan-id ] [ slot Display Layer 2 port slot-number ] [ verbose ] [ | { begin | exclude | Available in any view.

  • Page 377: Mld Configuration Examples

    Task Command Remarks reset mld ssm-mapping group { all | interface interface-type interface-number { all | Clear MLD SSM mappings. Available in user view. ipv6-group-address [ prefix-length ] [ ipv6-source-address [ prefix-length ] ] } } MLD configuration examples Basic MLD functions configuration example Network requirements As shown in Figure...
  • Page 378 # On Router A, enable IPv6 multicast routing globally, enable MLD on GigabitEthernet 3/1/1, and enable IPv6 PIM-DM on each interface. <RouterA> system-view [RouterA] multicast ipv6 routing-enable [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] mld enable [RouterA-GigabitEthernet3/1/1] pim ipv6 dm [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface pos 5/1/1 [RouterA-Pos5/1/1] pim ipv6 dm [RouterA-Pos5/1/1] quit...

  • Page 379: Mld Ssm Mapping Configuration Example

    Value of other querier present interval for MLD(in seconds): 255 Value of maximum query response time for MLD(in seconds): 10 Querier for MLD: FE80::200:5EFF:FE66:5100 (this router) Total 1 MLD Group reported MLD SSM mapping configuration example Network requirements As shown in Figure 100, the IPv6 PIM-SM domain applies both the ASM model and SSM model for IPv6 multicast delivery.
  • Page 380 Configuration procedure Enable IPv6 forwarding on each router and assign an IPv6 address and prefix length to each interface as shown in Figure 100. The detailed configuration steps are not discussed in this document. Configure OSPF among the routers to make sure the network-layer is interoperable among the routers on the IPv6 PIM-SSM domain and routing information among the routers can be dynamically updated.
  • Page 381 [RouterD-acl6-basic-2000] rule permit source ff3e:: 64 [RouterD-acl6-basic-2000] quit [RouterD] pim ipv6 [RouterD-pim6] ssm-policy 2000 [RouterD-pim6] quit # Configure the IPv6 SSM group range on Router A, Router B and Router C in the same way. (Details not shown.) Configure MLD SSM mappings on Router D. [RouterD] mld [RouterD-mld] ssm-mapping ff3e::101 64 1001::1...

  • Page 382: Mld Proxying Configuration Example

    UpTime: 00:13:25 Upstream interface: GigabitEthernet3/1/2 Upstream neighbor: 3002::1 RPF prime neighbor: 3002::1 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet3/1/1 Protocol: mld, UpTime: 00:13:25, Expires: - MLD proxying configuration example Network requirements As shown in Figure 101, IPv6 PIM-DM runs on the core network. Host A and Host C in the stub network receive VOD information sent to multicast group FF3E::101.

  • Page 383: Troubleshooting Mld

    # On Router B, enable IPv6 multicast routing globally, enable MLD proxying on GigabitEthernet 3/1/1, and enable MLD on GigabitEthernet 3/1/2. <RouterB> system-view [RouterB] multicast ipv6 routing-enable [RouterB] interface GigabitEthernet 3/1/1 [RouterB-GigabitEthernet3/1/1] mld proxying enable [RouterB-GigabitEthernet3/1/1] quit [RouterB] interface GigabitEthernet 3/1/2 [RouterB-GigabitEthernet3/1/2] mld enable [RouterB-GigabitEthernet3/1/2] quit Verify the configuration...

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

    If the mld group-policy command has been configured on an interface, the interface cannot receive • report messages that fail to pass filtering. Solution Use the display mld interface command to verify that the networking, interface connections, and IP address configuration are correct. If no information is output, the interface is in an abnormal state. The reason is that you have configured the shutdown command on the interface, that the interface is not properly connected, or that the IPv6 address configuration is not correctly done.

  • Page 385: Configuring Ipv6 Pim

    Configuring IPv6 PIM Overview Protocol Independent Multicast for IPv6 (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 reverse path forwarding (RPF) check to implement IPv6 multicast forwarding.
  • Page 386 source tree is the shortest path from the IPv6 multicast source to the receivers, it is also called shortest path tree (SPT). The working mechanism of IPv6 PIM-DM is summarized as follows: Neighbor discovery • SPT establishment • Graft • Assert •...
  • Page 387 Figure 102 SPT establishment in an IPv6 PIM-DM domain 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.

  • Page 388: Ipv6 Pim-Sm Overview

    Figure 103 Assert mechanism As shown in Figure 103, after Router A and Router B receive an (S, G) IPv6 multicast packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets, and both Router A and Router B, on their own downstream interface, receive a duplicate IPv6 multicast packet forwarded by the other.
  • Page 389 multicast group. The path along which the message goes hop by hop to the RP forms a branch of the RPT. When a multicast source sends an IPv6 multicast packet to an IPv6 multicast group, the source-side • designated router (DR) first registers the multicast source with the RP by sending a register message to the RP by unicast.
  • Page 390 Figure 104 DR election Receiver Source Receiver Hello message Register message Join message As shown in Figure 104, the DR election process is as follows: Routers on the multi-access network send hello messages to one another. The hello messages contain the router priority for DR election. The router with the highest DR priority becomes the DR. In the case of a tie in the router priority, or if any router in the network does not support carrying the DR-election priority in hello messages, The router with the highest IPv6 link-local address wins the DR election.
  • Page 391 mappings between IPv6 multicast groups and RPs. The BSR then encapsulates the RP-set in the bootstrap messages it periodically originates and floods the bootstrap messages to the entire IPv6 PIM-SM domain. Figure 105 BSR messages and C-RP advertisement messages Based on the information in the RP-sets, all routers in the network can calculate the location of the corresponding RPs based on the following rules: The C-RP with the highest priority wins.
  • Page 392 RP or the RP dynamically calculated based on the BSR mechanism. The DR does not need to know the RP address beforehand. The specific process is as follows. At the receiver side: • A receiver host initiates an MLD report to announce its joining an IPv6 multicast group. Upon receiving the MLD report, the receiver-side DR resolves the RP address embedded in the IPv6 multicast address, and sends a join message to the RP.
  • Page 393 Multicast source registration The purpose of IPv6 multicast source registration is to inform the RP about the existence of the IPv6 multicast source. Figure 107 IPv6 multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C IPv6 multicast packets As shown in...

  • Page 394: Ipv6 Bidir-Pim Overview

    register messages, the RP abstracts the multicast data and sends the multicast data down the RPT to the DRs at the receiver side. The RP acts as a transfer station for all IPv6 multicast packets. The whole process involves three issues as follows: •...
  • Page 395 The working mechanism of IPv6 BIDIR-PIM is summarized as follows: • Neighbor discovery RP discovery • DF election • • Bidirectional RPT building Neighbor discovery IPv6 BIDIR-PIM uses the same neighbor discovery mechanism as IPv6 PIM-SM does. For more information, "Neighbor discovery."...
  • Page 396 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 with the lowest metric wins the DF election.

  • Page 397: Ipv6 Administrative Scoping Overview

    Figure 110 RPT building at the multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT IPv6 Multicast packets Host C As shown in Figure 1 10, 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 398 IPv6 admin-scoped zones correspond to IPv6 multicast groups with different scope values in their group addresses. The boundary of the IPv6 admin-scoped zone is formed by zone border routers (ZBRs). Each IPv6 admin-scoped zone maintains one BSR that provides services for multicast groups within a specific scope.

  • Page 399: Ipv6 Pim-Ssm Overview

    Figure 112 IPv6 multicast address format The admin-scoped zone range increases with the value of the Scope field. For example, value E indicates IPv6 global-scoped, which contains other admin-scoped zones with the Scope field values smaller than E. Possible values of the Scope field are given in Table Table 26 Values of the Scope field Value...

  • Page 400: Relationships Among Ipv6 Pim Protocols

    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 Whether to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group the receiver is to join falls in the IPv6 SSM group range (the IPv6 SSM group range reserved by IANA is FF3x::/32, where x represents any legal address scope).

  • Page 401: Protocols And Standards

    Figure 114 Relationships among IPv6 PIM protocols For more information about MLD SSM mapping, see "Configuring MLD." Protocols and standards IPv6 PIM-related specifications are as follows: RFC 4601, Protocol Independent Multicast-Sparse Mode(PIM-SM):Protocol Specification (Revised) • • RFC 3973, Protocol Independent Multicast-Dense Mode(PIM-DM):Protocol Specification (Revised) RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address •...

  • Page 402: Configuration Prerequisites

    Task Remarks Configuring IPv6 PIM common features Optional. Configuration prerequisites Before configuring IPv6 PIM-DM, complete the following task: Enable IPv6 forwarding and configure any IPv6 unicast routing protocol so that all devices in the • domain are interoperable at the network layer. Determine the interval between state refresh messages.

  • Page 403: 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 404: Configuring Ipv6 Pim-Sm

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure graft retry period. pim ipv6 timer graft-retry interval 3 seconds by default. For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring IPv6 PIM common timers."...

  • Page 405: Enabling Ipv6 Pim-Sm

    Determine the C-RP priority and the ACL that defines the range of IPv6 multicast groups to be served • by each C-RP. Determine the legal C-RP address range and the ACL that defines the range of IPv6 multicast groups • to be served.
  • Page 406 Configuring a static RP If there is only one dynamic RP in a network, manually configuring a static RP can avoid communication interruption due to single-point failures and avoid frequent message exchange between C-RPs and the BSR. To enable a static RP to work normally, specify the same static RP address on all routers in the IPv6 PIM-SM domain.
  • Page 407 Enabling embedded RP With the Embedded RP feature 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 408: 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 C-BSRs should be configured on routers in the backbone network.
  • Page 409 Step Command Remarks Optional. Configure a legal BSR bsr-policy acl6-number address range. No restrictions by default. 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.
  • Page 410 IMPORTANT: Be sure to configure a BS period smaller than the BS timeout value. If you configure the BS period or the BS timeout timer, the system uses the configured one instead of the default one. Perform the following configuration on C-BSR routers. To configure C-BSR timers: Step Command...

  • Page 411: Configuring Ipv6 Administrative Scoping

    Step Command Remarks 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. NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. However, the semantic fragmentation of BSMs originated due to learning of a new IPv6 PIM neighbor is performed according to the MTU of the outgoing interface.

  • Page 412: Configuring Ipv6 Multicast Source Registration

    Step Command Remarks multicast ipv6 boundary { ipv6-group-address prefix-length Configure an IPv6 multicast By default, no multicast forwarding | scope { scope-id | admin-local | forwarding boundary. boundary is configured. global | organization-local | site-local } } Configuring C-BSRs for IPv6 admin-scopde zones In a network with IPv6 administrative scoping enabled, BSRs are elected from C-BSRs specific to different Scope field values.

  • Page 413: Configuring Spt Switchover

    register messages with IPv6 multicast data encapsulated from the IPv6 multicast source along SPT, the RP sends a register-stop message to the source-side DR. Upon receiving this message, the DR stops sending register messages encapsulated with IPv6 multicast data and starts a register-stop timer. Before the register-stop timer expires, the DR sends a null register message (a register message without encapsulated multicast data) to the RP.

  • Page 414: Configuring Ipv6 Bidir-Pim

    Step Command Remarks Optional. spt-switch-threshold infinity By default, the device switches to Configure the SPT switchover. [ group-policy acl6-number [ order the SPT immediately after it order-value ] ] receives the first IPv6 multicast packet from the RPT. Configuring IPv6 BIDIR-PIM IPv6 BIDIR-PIM configuration task list Task Remarks...

  • Page 415: Enabling Ipv6 Pim-Sm

    Determine the IPv6 address of a static RP and the IPv6 ACL that defines the range of IPv6 multicast • groups to be served by the static RP. Determine the C-RP priority and the IPv6 ACL that defines the range of IPv6 multicast groups to be •...

  • Page 416: Configuring An Rp

    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 417 When you configure a C-RP, ensure a relatively large bandwidth between this C-RP and the other devices in the IPv6 BIDIR-PIM domain. To configure a C-RP: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 c-rp ipv6-address [ { group-policy acl6-number | scope scope-id } | priority Configure an interface to be a No C-RP is configured by...

  • Page 418: Configuring A Bsr

    To configure C-RP timers globally: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. Configure the C-RP-Adv c-rp advertisement-interval interval interval. 60 seconds by default. Optional. Configure C-RP timeout time. c-rp holdtime interval seconds default. For more information about the configuration of other timers in IPv6 PIM-SM, see "Configuring IPv6 PIM common...
  • Page 419 The above-mentioned preventive measures can partially protect the security of BSRs in a network. However, if a legal BSR is controlled by an attacker, the above-mentioned problem still occurs. Because a large amount of information is to be exchanged between a BSR and the other devices in the IPv6 BIDIR-PIM domain, a relatively large bandwidth should be provided between the C-BSRs and the other devices in the IPv6 BIDIR-PIM domain.
  • Page 420 Step Command Remarks Enter IPv6 PIM view. pim ipv6 Optional. Configure the Hash mask c-bsr hash-length hash-length length. 126 by default. Optional. Configure the C-BSR priority. c-bsr priority priority 64 by default. Configuring C-BSR timers The BSR election winner multicasts its own IPv6 address and RP-Set information through bootstrap messages within the entire zone it serves.

  • Page 421: Configuring Ipv6 Administrative Scoping

    Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to multiple bootstrap message fragments (BSMFs). Upon receiving a BSMF that contains the RP-set information of one group range, a non-BSR router • updates corresponding RP-set information directly.
  • Page 422 Configuring an IPv6 admin-scoped zone boundary The boundary of each IPv6 admin-scoped zone is formed by ZBRs. Each admin-scoped zone maintains a BSR, which serves a specific IPv6 multicast group range. IPv6 multicast packets (such as assert messages and bootstrap messages) that belong to this range cannot cross the admin-scopde zone boundary.

  • Page 423: Configuring Ipv6 Pim-Ssm

    The SSM model is implemented 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-SM domain, HP recommends you to enable IPv6 PIM-SM on all non-border interfaces of routers.

  • Page 424: Configuring Ipv6 Pim Common Features

    Make sure that the same IPv6 SSM group range is configured on all routers in the entire domain. Otherwise, IPv6 multicast data cannot be delivered through the IPv6 SSM model. When a member of an IPv6 multicast group in the IPv6 SSM group range sends an MLDv1 report message, the device does not trigger a (*, G) join.

  • Page 425: Configuring An Ipv6 Multicast Data Filter

    Configure IPv6 PIM-DM (or IPv6 PIM-SM or IPv6 PIM-SSM). • • Determine the IPv6 ACL for filtering IPv6 multicast data. Determine the IPv6 ACL that defines a legal source address range for hello messages. • Determine the priority for DR election (global value/interface level value). •...

  • Page 426: Configuring Ipv6 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 Configure a hello message pim ipv6 neighbor-policy No hello message filter by default. filter. acl6-number NOTE: With the hello message filter configured, if hello messages of an existing IPv6 PIM neighbor fail to pass the filter, the IPv6 PIM neighbor is removed automatically when it times out.

  • Page 427: Configuring The Prune Delay

    Configuring hello options globally Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. Configure the priority for DR hello-option dr-priority priority election. 1 by default. Optional. Configure IPv6 PIM neighbor hello-option holdtime interval timeout time. 105 seconds by default.

  • Page 428: Configuring Ipv6 Pim Common Timers

    To configure the prune delay time: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Optional. Configure the prune delay prune delay interval By default, no prune delay time is time. configured. Configuring IPv6 PIM common timers IPv6 PIM routers discover IPv6 PIM neighbors and maintain IPv6 PIM neighboring relationships with other routers by periodically sending out hello messages.

  • Page 429: Configuring Join/Prune Message Sizes

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the hello interval. pim ipv6 timer hello interval 30 seconds by default. Optional. Configure the maximum delay pim ipv6 triggered-hello-delay between hello messages. interval 5 seconds by default. Optional.

  • Page 430: Displaying And Maintaining Ipv6 Pim

    IPv6 PIM to work with Bidirectional Forwarding Detection (BFD) on a multi-access network to detect failures of the links among IPv6 PIM neighbors. You must enable IPv6 PIM to work with BFD on all IPv6 PIM-capable routers on a multi-access network, so that the IPv6 PIM neighbors can fast detect DR failures and start a new DR election process.

  • Page 431: Ipv6 Pim Configuration Examples

    Task Command Remarks display pim ipv6 join-prune mode { sm [ flags flag-value ] | ssm } [ interface Display information about interface-type interface-number | Available in any view. join/prune messages to send. neighbor ipv6-neighbor-address ] * [ verbose ] [ | { begin | exclude | include } regular-expression ] display pim ipv6 neighbor [ interface interface-type interface-number |...
  • Page 432 Figure 115 Network diagram Receiver Host A Router A GE3/1/1 Host B Receiver GE3/1/1 POS5/1/1 POS5/1/1 GE3/1/1 Source Host C Router D Router B 4001::100/64 GE3/1/1 IPv6 PIM-DM Router C Host D Table 27 shows the interface and IPv6 address assignment, and network topology scheme. Table 27 Interface and IPv6 address assignment Device Interface...
  • Page 433 # Enable IPv6 multicast routing on Router A, and enable IPv6 PIM-DM on each interface and enable MLD on GigabitEthernet 3/1/1, which connects Router A to N1. <RouterA> system-view [RouterA] multicast ipv6 routing-enable [RouterA] interface GigabitEthernet 3/1/1 [RouterA-GigabitEthernet3/1/1] mld enable [RouterA-GigabitEthernet3/1/1] pim ipv6 dm [RouterA-GigabitEthernet3/1/1] quit [RouterA] interface Serial4/1/9/1:0...
  • Page 434 3001::1 Pos5/1/2 00:03:54 00:01:17 5 Assume that Host A needs to receive information addressed to an IPv6 multicast group G (FF0E::101). Once the IPv6 multicast source S (4001::100/64) sends IPv6 multicast packets to the IPv6 multicast group G, an SPT is established through traffic flooding. Routers on the SPT path (Router A and Router D) have their (S, G) entries.

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

    IPv6 PIM-SM non-scoped zone configuration example Network requirements Receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire IPv6 PIM domain operates in the sparse mode. Host A and Host C are IPv6 multicast receivers in two stub networks, N1 and N2.
  • Page 436 Device Interface IP address Router C GigabitEthernet 3/1/1 2001::2/64 Router C POS 5/1/1 3001::1/64 Router D GigabitEthernet 3/1/1 4001::1/64 Router D Serial 4/1/9/1:0 1002::2/64 Router D POS 5/1/1 4002::1/64 Router E POS 5/1/1 3001::2/64 Router E POS 5/1/2 2002::2/64 Router E POS 5/1/3 1003::2/64 Router E...
  • Page 437 [RouterD] pim ipv6 [RouterD-pim6] c-bsr 4002::1 128 10 [RouterD-pim6] c-rp 4002::1 group-policy 2005 [RouterD-pim6] quit # On Router E, configure the service scope of RP advertisements, specify a C-BSR and a C-RP, and set the hash mask length to 128 and the priority of the C-BSR to 20. <RouterE>...
  • Page 438 Next advertisement scheduled at: 00:00:48 # Display BSR information on Router E and the locally configured C-RP information in effect. [RouterE] display pim ipv6 bsr-info Elected BSR Address: 1003::2 Priority: 20 Hash mask length: 128 State: Elected Uptime: 00:01:10 Next BSR message scheduled at: 00:01:48 Candidate BSR Address: 1003::2 Priority: 20 Hash mask length: 128...
  • Page 439 Protocol: pim-sm, Flag: WC UpTime: 00:03:45 Upstream interface: Pos5/1/1 Upstream neighbor: 1003::2 RPF prime neighbor: 1003::2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet3/1/1 Protocol: mld, UpTime: 00:02:15, Expires: 00:03:06 (4001::100, FF0E::100) RP: 1003::2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:02:15 Upstream interface: Serial4/1/9/1:0 Upstream neighbor: 1002::2...

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

    Total number of downstreams: 1 1: Pos5/1/3 Protocol: pim-sm, UpTime: 00:16:56, Expires: 00:02:34 IPv6 PIM-SM admin-scoped zone configuration example Network requirements Receivers receive VOD information through multicast. The entire IPv6 PIM-SM domain is divided into IPv6 admin-scoped zone 1, IPv6 admin-scoped zone 2, and the IPv6 global-scoped zone. Router B, Router C, and Router D are ZBRs of the three domains respectively.
  • Page 441 Table 29 Interface and IPv6 address assignment Device Interface IP address Device Interface IP address Router A GE3/1/1 1001::1/64 Router D S4/1/9/1:0 3002::2/64 Router A S4/1/9/1:0 1002::1/64 Router D S4/1/9/1:1 6001::1/64 Router B GE3/1/1 2001::1/64 Router D POS5/1/1 6002::1/64 Router B S4/1/9/1:0 1002::2/64 Router E...
  • Page 442 [RouterB] multicast ipv6 routing-enable [RouterB] pim ipv6 [RouterB-pim6] c-bsr admin-scope [RouterB-pim6] quit [RouterB] interface GigabitEthernet 3/1/1 [RouterB-GigabitEthernet3/1/1] pim ipv6 sm [RouterB-GigabitEthernet3/1/1] quit [RouterB] interface serial 4/1/9/1:0 [RouterB-Serial4/1/9/1:0] pim ipv6 sm [RouterB-Serial4/1/9/1:0] quit [RouterB] interface pos 5/1/1 [RouterB-Pos5/1/1] pim ipv6 sm [RouterB-Pos5/1/1] quit [RouterB] interface pos 5/1/2 [RouterB-Pos5/1/2] pim ipv6 sm...
  • Page 443 [RouterB-pim6] c-rp 1002::2 scope 4 [RouterB-pim6] quit # On Router D, configure the service scope of RP advertisements and configure Serial 4/1/9/1:0 as a C-BSR and C-RP of admin-scoped zone 2. [RouterD] pim ipv6 [RouterD-pim6] c-bsr scope 4 [RouterD-pim6] c-bsr 3002::2 [RouterD-pim6] c-rp 3002::2 scope 4 [RouterD-pim6] quit # On Router F, configure Serial 4/1/9/1:0 as a C-BSR and C-RP in the global-scoped zone.
  • Page 444 Priority: 64 Hash mask length: 126 State: Accept Preferred Scope: 14 Uptime: 00:01:45 Expires: 00:01:25 Elected BSR Address: 3002::2 Priority: 64 Hash mask length: 126 State: Elected Scope: 4 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...
  • Page 445 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF1E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 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...
  • Page 446 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF8E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 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...
  • Page 447 prefix/prefix length: FFEE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 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...
  • Page 448 Expires: 00:01:51 prefix/prefix length: FF54::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF64::/16 RP: 1002::2 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...
  • Page 449 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFC4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFD4::/16 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...
  • Page 450 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 HoldTime: 130 Uptime: 00:03:39...
  • Page 451 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 Priority: 192 HoldTime: 130...

  • Page 452: Ipv6 Bidir-Pim Configuration Example

    IPv6 BIDIR-PIM configuration example Network requirements In the IPv6 BIDIR-PIM domain shown in Figure 1 18, Source 1 and Source 2 send different IPv6 multicast information to IPv6 multicast group FF14::101. Host A and Host B receive IPv6 multicast information from the two sources.
  • Page 453 Device Interface IPv6 address Source 2 — 5001::2/64 Receiver 1 — 2001::2/64 Receiver 2 — 4001::2/64 Configuration procedure Enable IPv6 forwarding on each router, and assign the IPv6 address and prefix length to each interface as per Figure 118. (Details not shown.) Configure OSPFv3 on the routers in the IPv6 BIDIR-PIM domain to ensure network-layer reachability among them.
  • Page 454 [RouterC-Serial2/1/9/1:0] pim ipv6 sm [RouterC-Serial2/1/9/1:0] quit [RouterC] interface Serial 2/1/9/2:0 [RouterC-Serial2/1/9/2:0] pim ipv6 sm [RouterC-Serial2/1/9/2:0] quit [RouterC] interface loopback 0 [RouterC-LoopBack0] pim ipv6 sm [RouterC-LoopBack0] quit [RouterC] pim ipv6 [RouterC-pim6] bidir-pim enable # On Router D, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, enable MLD on interface GigabitEthernet 3/1/1, and enable IPv6 BIDIR-PIM.
  • Page 455 FE38:4E01 (local) Ser2/1/9/2:0 Lose 01:23:12 FE80::20F:E2FF: FE15:5601 # Display the DF information of IPv6 BIDIR-PIM on Router C. [RouterC] display pim ipv6 df-info RP Address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Loop0 Ser2/1/9/1:0 01:06:07 FE80::20F:E2FF: FE15:5601 (local) Ser2/1/9/2:0 01:06:07 FE80::20F:E2FF: FE15:5602 (local) # Display the DF information of IPv6 BIDIR-PIM on Router D.
  • Page 456 RPF interface: Serial2/1/9/2:0 List of 2 DF interfaces: 1: GigabitEthernet3/1/1 2: Serial2/1/9/1:0 # Display the DF information of the IPv6 multicast forwarding table on Router C. [RouterC] display multicast ipv6 forwarding-table df-info Multicast DF information Total 1 RP Total 1 RP matched 00001.

  • Page 457: Ipv6 Pim-Ssm Configuration Example

    2: GigabitEthernet3/1/5 Protocol: pim-sm, UpTime: 00:00:34, Expires: 00:02:56 IPv6 PIM-SSM configuration example Network requirements Receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire IPv6 PIM domain operates in the SSM mode.
  • Page 458 Device Interface IP address Router B POS 5/1/1 2002::1/64 Router C GigabitEthernet 3/1/1 2001::2/64 Router C POS 5/1/1 3002::1/64 Router D GigabitEthernet 3/1/1 4001::1/64 Router D Serial 4/1/9/1:0 1002::2/64 Router D POS 5/1/1 4002::1/64 Router E POS 5/1/1 3001::2/64 Router E POS 5/1/2 2002::2/64 Router E...
  • Page 459 [RouterA] pim ipv6 [RouterA-pim6] ssm-policy 2000 [RouterA-pim6] quit # Configure the IPv6 SSM group range to be FF3E::/64 on Router B, Router C, Router D and Router E in the same way. (Details not shown.) Verify the configuration # Display IPv6 PIM configuration information on Router A. [RouterA] display pim ipv6 interface Interface NbrCnt HelloInt...

  • Page 460: Troubleshooting Ipv6 Pim

    Troubleshooting IPv6 PIM A multicast distribution tree cannot be built correctly Symptom None of the routers in the network (including routers directly connected with IPv6 multicast sources and receivers) have IPv6 multicast forwarding entries. That is, a multicast distribution tree cannot be built correctly and clients cannot receive IPv6 multicast data.

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

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

  • Page 462: Rpt Cannot Be Established Or A Source Cannot Register In Ipv6 Pim-Sm

    RPT cannot be established or a source cannot register in IPv6 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 463: Configuring Ipv6 Mbgp

    Configuring IPv6 MBGP This chapter covers configuration tasks related to multiprotocol BGP for IPv6 multicast. For BGP and IPv6 BGP related information, 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 464: Configuring Basic Ipv6 Mbgp Functions

    Task Remarks Configuring the AS_PATH attribute Optional Configuring IPv6 MBGP soft reset Optional Tuning and optimizing IPv6 MBGP Enabling the IPv6 MBGP ORF capability Optional networks Configuring the maximum number of ECMP routes Optional Configuring an IPv6 MBGP peer group Optional Configuring a large scale IPv6 Configuring IPv6 MBGP community...

  • Page 465: Controlling Route Distribution And Reception

    use the value set through the command. If the preferred value in the routing policy is 0, the routes that match it also use the value set through the peer { ipv6-group-name | ipv6-address } preferred-value value command. To learn how to use a routing policy to set a preferred value, see the peer { ipv6-group-name | ipv6-address } route-policy route-policy-name { import | export } command and the apply preferred-value preferred-value command in Layer 3—IP Routing Command Reference.

  • Page 466: Configuring Ipv6 Mbgp Route Summarization

    Step Command Description Enter IPv6 MBGP multicast ipv6-family multicast address family view. Optional. Enable default route redistribution into the IPv6 default-route imported By default, default route MBGP routing table. redistribution is not allowed. Not enabled by default. import-route protocol [ process-id If the default-route imported Enable route redistribution [ med med-value | route-policy...

  • Page 467: Configuring Outbound Ipv6 Mbgp Route Filtering

    Step Command Remarks Not advertised by default. With the peer default-route-advertise peer { ipv6-group-name | command executed, the router sends a Advertise a default route to an ipv6-address } default route with the next hop as itself IPv6 MBGP peer or peer default-route-advertise to the specified IPv6 MBGP peer or the group.

  • Page 468: Configuring Inbound Ipv6 Mbgp Route Filtering

    NOTE: 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. • Configuring inbound IPv6 MBGP route filtering Step Command Remarks...

  • Page 469: Configuring Ipv6 Mbgp Route Dampening

    Configuring IPv6 MBGP route dampening Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. dampening [ half-life-reachable Optional. Configure IPv6 MBGP route half-life-unreachable reuse dampening parameters. suppress ceiling | route-policy Not configured by default.

  • Page 470: Configuring The Default Local Preference

    Configuring the default local preference Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Optional. Set the default local default local-preference value By default, the default local preference. preference is 100. Configuring the MED attribute Step Command...

  • Page 471: Configuring The As_Path Attribute

    Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Optional. By default, IPv6 MBGP specifies Configure the router as the peer { ipv6-group-name | the local router as the next hop for next hop of routes sent to the ipv6-address } next-hop-local routes sent to an EBGP peer or a...

  • Page 472: Configuring Ipv6 Mbgp Soft Reset

    Configuring IPv6 MBGP soft reset After you modify a route selection policy, you must reset IPv6 MBGP connections to make the new one take effect. The current IPv6 MBGP implementation supports the route refresh feature that enables dynamic route refresh without terminating IPv6 MBGP connections. If a peer that does not support route refresh exists in the network, you must configure the peer keep-all-routes command to save all routes from the peer.

  • Page 473: Enabling The Ipv6 Mbgp Orf Capability

    Step Command Remarks refresh bgp ipv6 multicast { all | ipv6-address | group Perform soft reset manually. Optional. ipv6-group-name | external | internal } { export | import } Enabling the IPv6 MBGP ORF capability The BGP Outbound Route Filter (ORF) feature enables a BGP speaker to send a set of ORFs to its BGP peer through route-refresh messages.

  • Page 474: Configuring The Maximum Number Of Ecmp Routes

    Table 32 Description of the send, receive, and both parameters and the negotiation result Local parameter Peer parameter Negotiation result The ORF sending capability is enabled locally and • receive send the ORF receiving capability is enabled on the • both peer.

  • Page 475: Configuring Ipv6 Mbgp Community

    Step Command Remarks Enter BGP view. bgp as-number Enter IPv6 address family ipv6-family view. Create an IPv6 BGP peer group ipv6-group-name [ external group. | internal ] peer ipv6-address group Add a peer to the peer group. ipv6-group-name [ as-number By default, no peer is added.

  • Page 476: Configuring An Ipv6 Mbgp Route Reflector

    Configuring an IPv6 MBGP route reflector To guarantee connectivity between IPv6 multicast IBGP peers, you must make them fully meshed. However, this becomes unpractical when too many IPv6 multicast IBGP peers exist. Using route reflectors can solve the problem. The clients of a route reflector should not be fully meshed, and the route reflector reflects the routes of a client to the other clients.
  • Page 477 Task Command Remarks Display the prefix entries in the display bgp ipv6 multicast peer ipv6-address received Available in ORF information for the specified ipv6-prefix [ | { begin | exclude | include } any view. BGP peer. regular-expression ] display bgp ipv6 multicast routing-table [ ipv6-address Display IPv6 MBGP routing table Available in prefix-length ] [ | { begin | exclude | include }...

  • Page 478: Resetting Ipv6 Mbgp Connections

    Resetting IPv6 MBGP connections When you change an IPv6 MBGP routing policy, you can make the new configuration effective by resetting the IPv6 MBGP connections. Task Command Remarks reset bgp ipv6 multicast { as-number | ipv6-address Reset the specified IPv6 MBGP [ flap-info ] | all | group Available in user view.
  • Page 479 Figure 120 Network diagram Device Interface IP address Device Interface IP address Source 1002::100/64 Router C GE3/1/1 3002::1/64 Router A GE3/1/1 1002::1/64 S4/1/9/1:1 3001::1/64 POS5/1/1 1001::1/64 S4/1/9/1:2 2001::2/64 Router B POS5/1/1 1001::2/64 Router D S4/1/9/1:1 2002::2/64 S4/1/9/1:1 2001::1/64 S4/1/9/1:2 3001::2/64 S4/1/9/1:2 2002::1/64 Configuration procedure...
  • Page 480 [RouterC] interface serial 4/1/9/1:2 [RouterC-Serial4/1/9/1:2] pim ipv6 sm [RouterC-Serial4/1/9/1:2] quit [RouterC] interface GigabitEthernet 3/1/1 [RouterC-GigabitEthernet3/1/1] pim ipv6 sm [RouterC-GigabitEthernet3/1/1] mld enable [RouterC-GigabitEthernet3/1/1] quit # Configure an IPv6 PIM domain border on Router A. [RouterA] interface POS 5/1/1 [RouterA-Pos5/1/1] pim ipv6 bsr-boundary [RouterA-Pos5/1/1] quit # Configure an IPv6 PIM domain border on Router B.
  • Page 481 Verify the configuration: Use the display bgp ipv6 multicast peer command to display IPv6 MBGP peers on each router. For example: # Display IPv6 MBGP peers on Router B. [RouterB] display bgp ipv6 multicast peer BGP local router ID : 2.2.2.2 Local AS number : 200 Total number of peers : 3 Peers in established state : 3...

  • Page 482: 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 483: 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 484 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 485: Index

    Configuring basic IGMP functions,89 Configuring the maximum number of forwarding entries in a multicast VLAN,56 Configuring basic IGMP snooping functions,20 Contacting HP,470 Configuring basic IPv6 MBGP functions,452 Controlling route advertisement and reception,221 Configuring basic MLD functions,353 Controlling route distribution and...
  • Page 486 Displaying and maintaining multicast routing and Multicast forwarding over a GRE tunnel configuration forwarding,72 example,341 Displaying and maintaining multicast VPN,258 Multicast models,5 Displaying and maintaining PIM,159 Multicast packet forwarding mechanism,1 1 Displaying and maintaining PIM snooping,49 Multicast support for VPNs,12 Multicast VLAN configuration example,57 Multicast VLAN configuration task...

Table of Contents