1. Manuals
  2. Brands
  3. HPP Enterprises Manuals
  4. Switch
  5. FlexNetwork 7500 Series
  6. Configuration manual

HPP Enterprises FlexNetwork 7500 Series Configuration Manual

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

Advertisement

Quick Links

Download this manual
HPE FlexNetwork 7500 Switch Series
IP Multicast Configuration Guide
Part number: 5200-1936
Software version: 7500-CMW710-R7524
Document version: 6W100-20161230

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Summary of Contents for HPP Enterprises FlexNetwork 7500 Series

  • Page 1 HPE FlexNetwork 7500 Switch Series IP Multicast Configuration Guide Part number: 5200-1936 Software version: 7500-CMW710-R7524 Document version: 6W100-20161230...
  • Page 2 © Copyright 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Contents Multicast overview ························································································· 1 Introduction to multicast ····································································································································· 1 Information transmission techniques ·········································································································· 1 Multicast features ······································································································································· 3 Common notations in multicast ·················································································································· 4 Multicast benefits and applications ············································································································ 4 Multicast models ················································································································································ 4 Multicast architecture ········································································································································· 5 Multicast addresses ··································································································································· 5 Multicast protocols ·····································································································································...
  • Page 4 Static port configuration example (for VLANs) ························································································· 38 IGMP snooping querier configuration example (for VLANs) ···································································· 40 IGMP snooping proxying configuration example (for VLANs) ·································································· 43 IGMP snooping configuration example (for VXLANs) ·············································································· 44 Troubleshooting IGMP snooping ····················································································································· 49 Layer 2 multicast forwarding cannot function ··························································································· 49 Multicast group policy does not work ·······································································································...
  • Page 5 IGMP SSM mapping ································································································································ 89 IGMP proxying ········································································································································· 90 IGMP support for VPNs ···························································································································· 91 Protocols and standards ·························································································································· 91 IGMP configuration task list ····························································································································· 92 Configuring basic IGMP features ····················································································································· 92 Enabling IGMP ········································································································································· 92 Specifying an IGMP version ····················································································································· 93 Configuring a static group member ··········································································································...
  • Page 6 Configuring PIM-SSM ···································································································································· 137 PIM-SSM configuration task list ············································································································· 138 Configuration prerequisites ···················································································································· 138 Enabling PIM-SM ··································································································································· 138 Configuring the SSM group range ·········································································································· 138 Configuring common PIM features················································································································· 139 Configuration task list ····························································································································· 139 Configuration prerequisites ···················································································································· 139 Configuring a multicast source policy ····································································································· 139 Configuring a PIM hello policy················································································································...
  • Page 7 MSDP peers stay in disabled state ········································································································ 196 No SA entries exist in the router's SA message cache ·········································································· 196 No exchange of locally registered (S, G) entries between RPs ····························································· 196 Configuring multicast VPN ········································································· 197 Overview ························································································································································ 197 MD VPN overview ··································································································································...
  • Page 8 Enabling the MLD snooping querier ······································································································· 275 Configuring parameters for MLD general queries and responses ························································· 276 Enabling MLD snooping proxying ·················································································································· 276 Configuring parameters for MLD messages ·································································································· 277 Configuration prerequisites ···················································································································· 277 Configuring source IPv6 addresses for MLD messages ········································································ 277 Setting the 802.1p priority for MLD messages ·······················································································...
  • Page 9 Configuring IPv6 multicast load splitting ································································································ 323 Configuring an IPv6 multicast forwarding boundary··············································································· 323 Enabling IPv6 multicast forwarding between sub-VLANs of a super VLAN ··········································· 324 Displaying and maintaining IPv6 multicast routing and forwarding ································································ 324 IPv6 multicast routing and forwarding configuration example ········································································ 326 Network requirements ····························································································································...
  • Page 10 IPv6 PIM-SM configuration task list ······································································································· 368 Configuration prerequisites ···················································································································· 368 Enabling IPv6 PIM-SM ··························································································································· 368 Configuring an RP ·································································································································· 369 Configuring a BSR ································································································································· 371 Configuring IPv6 multicast source registration ······················································································· 373 Configuring the switchover to SPT ········································································································· 374 Configuring IPv6 BIDIR-PIM ··························································································································...

  • Page 11: Multicast Overview

    Multicast overview Introduction to multicast 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.
  • Page 12 Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission Host A Receiver Host B Source Host C Receiver Host D A network segment Receiver Packets for all hosts Host E...

  • Page 13: Multicast Features

    Figure 3 Multicast transmission Host A Receiver Host B Source Host C Receiver Host D IP network Receiver Packets for the multicast group Host E The multicast source sends only one copy of the information to a multicast group. Host B, Host D, and Host E, which are information receivers, must join the multicast group.

  • Page 14: Common Notations In Multicast

    Table 1 Comparing TV program transmission and multicast transmission TV program transmission Multicast transmission A TV station transmits a TV program through a A multicast source sends multicast data to a multicast channel. group. A user tunes the TV set to the channel. A receiver joins the multicast group.

  • Page 15: Multicast Architecture

    multicast sources. In this model, receivers do not know the positions of the multicast sources in advance. SFM model The SFM model is derived from the ASM model. To a multicast source, the two models appear to have the same multicast membership architecture. The SFM model functionally extends the ASM model.
  • Page 16 Address block Description group addresses. A packet destined for an address in this block will not be forwarded beyond the local subnet regardless of the TTL value in the IP header. Globally scoped group addresses. This block includes the following types of designated group addresses: 224.0.1.0 to 238.255.255.255 •...
  • Page 17 Figure 4 IPv6 multicast format 0xFF Flags Scope Group ID (112 bits) The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 11111111.  Flags—The Flags field contains four bits.  Figure 5 Flags field format 0 R P T Table 4 Flags field description Description...

  • Page 18: Multicast Protocols

    Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast  group in the scope that the Scope field defines. Ethernet multicast MAC addresses • IPv4 multicast MAC addresses: As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E.
  • Page 19 Layer 2 multicast protocols—IGMP snooping, MLD snooping, PIM snooping, IPv6 PIM snooping, multicast VLAN, and IPv6 multicast VLAN. • IPv4 and IPv6 multicast protocols: For IPv4 networks—IGMP snooping, PIM snooping, multicast VLAN, IGMP, PIM, MSDP,  and MBGP. For IPv6 networks—MLD snooping, IPv6 PIM snooping, IPv6 multicast VLAN, MLD, IPv6 ...

  • Page 20: Multicast Packet Forwarding Mechanism

    MBGP is an extension of the MP-BGP for exchanging multicast routing information among different ASs. For the SSM model, multicast routes are not divided into intra-domain routes and inter-domain routes. Because receivers know the positions of the multicast sources, channels established through PIM-SM are sufficient for the transport of multicast information.

  • Page 21: Multicast Support For Vpns

    multicast packets that an incoming interface receives through multiple outgoing interfaces. Compared to a unicast model, a multicast model is more complex in the following aspects: • To ensure multicast packet transmission on the network, different routing tables are used to guide multicast forwarding.

  • Page 22: Multicast Application In Vpns

    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 multicast protocols, PIM neighbor information, and multicast routing table. In a VPN, the device forwards multicast data based on the forwarding table or routing table for that VPN.

  • Page 23: Configuring Igmp Snooping

    Configuring IGMP snooping Overview IGMP snooping runs on a Layer 2 device as a multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from IGMP packets that are exchanged between the hosts and the router. As shown in Figure 9, when IGMP snooping is not enabled, the Layer 2 switch floods multicast...
  • Page 24 Figure 10 IGMP snooping ports Receiver Router A Switch A GE1/0/1 GE1/0/2 Host A GE1/0/3 Host B Receiver GE1/0/1 Source GE1/0/2 Host C Switch B Router port Member port Multicast packets Host D Router ports On an IGMP snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.

  • Page 25: How Igmp Snooping Works

    How IGMP snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." IGMP messages types include general query, IGMP report, and leave message. An IGMP snooping-enabled Layer 2 device performs differently depending on the message types. General query The IGMP querier periodically sends IGMP general queries to all hosts and routers on the local subnet to check for the existence of multicast group members.

  • Page 26: Igmp Snooping Proxying

    • If no match is found, the Layer 2 device discards the IGMP leave message. • If a match is found but the receiving port is not an outgoing interface in the forwarding entry, the Layer 2 device discards the IGMP leave message. •...

  • Page 27: Protocols And Standards

    The IGMP snooping proxy device processes different IGMP messages as follows: • General query. After receiving an IGMP general query, the device forwards the query to all ports in the VLAN except the receiving port. The device also generates an IGMP report based on the local membership information and sends the report to all router ports.

  • Page 28: Igmp Snooping Configuration Task List For Vlans

    IGMP snooping configuration task list for VLANs Tasks at a glance Configuring basic IGMP snooping features: • (Required.) Enabling IGMP snooping • (Optional.) Specifying an IGMP snooping version • (Optional.) Setting the maximum number of IGMP snooping forwarding entries • (Optional.) Configuring static multicast MAC address entries •...

  • Page 29: Configuring Basic Igmp Snooping Features

    Tasks at a glance • (Optional.) Setting the 802.1p priority for IGMP messages Configuring IGMP snooping policies: • (Optional.) Enabling dropping unknown multicast data • (Optional.) Enabling multicast group replacement Configuring basic IGMP snooping features Before you configure basic IGMP snooping features, complete the following tasks: •...

  • Page 30: Specifying An Igmp Snooping Version

    Step Command Remarks the VLAN or VSI. disabled in a VLAN or VSI. Specifying an IGMP snooping version Different IGMP snooping versions process different versions of IGMP messages. • IGMPv2 snooping processes IGMPv1 and IGMPv2 messages, but it floods IGMPv3 messages in the VLAN instead of processing them.

  • Page 31: Configuring Static Multicast Mac Address Entries

    To set the maximum number of IGMP snooping forwarding entries: Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the maximum number of The default setting is IGMP snooping forwarding entry-limit limit 4294967295. entries. Configuring static multicast MAC address entries In Layer 2 multicast, multicast MAC address entries can be dynamically created through Layer 2 multicast protocols (such as IGMP snooping).

  • Page 32: Configuring Igmp Snooping Port Features

    The IGMP last member query interval defines the maximum response time advertised in IGMP group-specific queries. Set an appropriate value for the IGMP last member query interval to speed up hosts' responses to IGMP group-specific queries and avoid IGMP report traffic bursts. Configuration restrictions and guidelines When you set the IGMP last member query interval, follow these restrictions and guidelines: •...

  • Page 33: Configuring Static Ports

    • IGMP group-specific queries originated by the Layer 2 device trigger the adjustment of aging timers for dynamic member ports. If a dynamic member port receives such a query, its aging timer is set to twice the IGMP last member query interval. For more information about setting the IGMP last member query interval on the Layer 2 device, see "Setting the IGMP last member query...

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

    Step Command Remarks interface view or Layer 2 interface-number aggregate interface view. • Configure the port as a static member port: igmp-snooping static-group group-address [ source-ip source-address ] By default, a port is not a static Configure the port as a static vlan vlan-id member port or a static router port.

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

    Enabling fast-leave processing globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Enable fast-leave processing By default, fast-leave processing fast-leave [ vlan vlan-list ] globally. is disabled globally. Enabling fast-leave processing on a port Step Command Remarks Enter system view.

  • Page 36: Configuration Prerequisites

    Configuration prerequisites Before you configure the IGMP snooping querier, complete the following tasks: • Enable IGMP snooping for the VLAN or VSI. • Determine the IGMP general query interval. • Determine the maximum response time for IGMP general queries. Enabling the IGMP snooping querier This feature enables the device to periodically send IGMP general queries to establish and maintain multicast forwarding entries at the data link Layer.

  • Page 37: Enabling Igmp Snooping Proxying

    Set an appropriate value for the maximum response time for IGMP general queries to speed up hosts' responses to IGMP general queries and avoid IGMP report traffic bursts. You can set the maximum response time for IGMP general queries globally for all VLANs and VSIs in IGMP-snooping view, for a VSI in VSI view, or for a VLAN in VLAN view.

  • Page 38: Configuring The Source Ip Address For Igmp Messages

    • Enable IGMP snooping for the VLAN or VSI. • Determine the source IP address of IGMP general queries. • Determine the source IP address of IGMP group-specific queries. • Determine the source IP address of IGMP reports. • Determine the source IP address of IGMP leave messages. •...

  • Page 39: Setting The 802.1P Priority For Igmp Messages

    Step Command Remarks address for IGMP leave source-ip ip-address IGMP leave messages is the IP messages. address of the current VLAN interface. If the current VLAN interface does not have an IP address, the source IP address is 0.0.0.0. Configuring the source IP address for IGMP messages in a VSI Step Command Remarks...

  • Page 40: Configuring Igmp Snooping Policies

    Setting the 802.1p priority for IGMP messages globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the 802.1p priority for By default, the 802.1p priority for dot1p-priority priority IGMP messages. IGMP packets is not configured. Setting the 802.1p priority for IGMP messages in a VLAN Step Command Remarks...

  • Page 41: Enabling Multicast Source Port Filtering

    Configuring a multicast group policy on a port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, no multicast group Configure a multicast group igmp-snooping group-policy policies exist on a port, and hosts policy on the port.

  • Page 42: Enabling Igmp Report Suppression

    • The drop-unknown and igmp-snooping drop-unknown commands are mutually exclusive. You cannot configure them on the same device. • The device still forwards unknown IPv4 multicat data to router ports (excluding the incoming port) in a VLAN or VSI even though this feature is enabled. Enabling dropping unknown multicast data globally Step Command...

  • Page 43: Enabling Multicast Group Replacement

    • If the number of multicast groups on a port exceeds the limit, the system removes all the forwarding entries related to that port. The receiver hosts attached to that port can join multicast groups again before the number of multicast groups on the port reaches the limit. Configuration procedure To set the maximum number of multicast groups on a port: Step...

  • Page 44: Enabling Host Tracking

    Enabling host tracking This feature enables the device to record information about member hosts that are receiving multicast data. The information includes IP addresses of the hosts, length of time elapsed since the hosts joined multicast groups, and remaining timeout time for the hosts. This feature facilitates monitoring and managing member hosts.
  • Page 45 Task Command chassis-number slot slot-number ] display igmp-snooping static-router-port [ vlan vlan-id ] (In standalone mode.) Display static router port information. [ slot slot-number ] display igmp-snooping static-router-port [ vlan vlan-id ] (In IRF mode.) Display static router port [ chassis chassis-number slot slot-number ] information.

  • Page 46: Igmp Snooping Configuration Examples

    IGMP snooping configuration examples Group policy and simulated joining configuration example (for VLANs) Network requirements As shown in Figure 12, Router A runs IGMPv2 and acts as the IGMP querier. Switch A runs IGMPv2 snooping. Configure a multicast group policy and simulated joining to meet the following requirements: •...
  • Page 47 [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100.

  • Page 48: Static Port Configuration Example (For Vlans)

    Static port configuration example (for VLANs) Network requirements As shown in Figure • Router A runs IGMPv2 and acts as the IGMP querier. Switch A, Switch B, and Switch C run IGMPv2 snooping. • Host A and host C are permanent receivers of multicast group 224.1.1.1. Configure static ports to meet the following requirements: •...
  • Page 49 [RouterA-GigabitEthernet1/0/1] quit # Enable PIM-DM on GigabitEthernet 1/0/2. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN.

  • Page 50: Igmp Snooping Querier Configuration Example (For Vlans)

    [SwitchC-GigabitEthernet1/0/3] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-GigabitEthernet1/0/3] quit [SwitchC] interface gigabitethernet 1/0/5 [SwitchC-GigabitEthernet1/0/5] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-GigabitEthernet1/0/5] quit Verifying the configuration # Display static router port information for VLAN 100 on Switch A. [SwitchA] display igmp-snooping static-router-port vlan 100 VLAN 100: Router slots (0 in total): Router ports (1 in total):...
  • Page 51 Figure 14 Network diagram Source 1 Source 2 VLAN 100 192.168.1.10/24 192.168.1.20/24 Receiver Receiver GE1/0/2 GE1/0/2 GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 Host A Host B GE1/0/4 Switch A Switch B Querier Receiver Receiver GE1/0/2 GE1/0/1 GE1/0/2 GE1/0/3 GE1/0/1 Host D Host C Switch D Switch C Configuration procedure...
  • Page 52 [SwitchB-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100. [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] igmp-snooping drop-unknown [SwitchB-vlan100] quit Configure Switch C: # Enable IGMP snooping globally. <SwitchC> system-view [SwitchC] igmp-snooping [SwitchC-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN.

  • Page 53: Igmp Snooping Proxying Configuration Example (For Vlans)

    Received error IGMP messages: The output shows that all switches except Switch A can receive the IGMP general queries after Switch A acts as the IGMP snooping querier. IGMP snooping proxying configuration example (for VLANs) Network requirements As shown in Figure 15, Router A runs IGMPv2 and acts as the IGMP querier.

  • Page 54: Igmp Snooping Configuration Example (For Vxlans)

    # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping and IGMP snooping proxying for the VLAN. [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping proxy enable [SwitchA-vlan100] quit...
  • Page 55 Configure IGMP snooping on the switches to implement Layer 2 multicast forwarding and reduce the burden of replicating known multicast traffic for VTEPs in VXLAN 10. Figure 16 Network diagram Loop0 Loop0 Transport network GE1/0/1 GE1/0/1 Vlan-int11 Vlan-int11 Vlan-int13 Vlan-int13 VM 1 VM 3 VLAN 2...
  • Page 56 # Assign an IP address to Loopback 0. This IP address will be used as the source address of the VXLAN tunnels to Switch B and Switch C. [SwitchA] interface loopback 0 [SwitchA-Loopback0] ip address 1.1.1.1 255.255.255.255 [SwitchA-Loopback0] quit # Create a VXLAN tunnel to Switch B. The tunnel interface name is Tunnel 1.
  • Page 57 # Enable IGMP snooping globally. [SwitchB] igmp-snooping [SwitchB -igmp-snooping] quit # Enable IGMP snooping and dropping unknown multicast data packets for VSI vpna. [SwitchB] vsi vpna [SwitchB-vsi-vpna] igmp-snooping enable [SwitchB-vsi-vpna] igmp-snooping drop-unknown [SwitchB-vsi-vpna] quit # Assign an IP address to Loopback 0. This IP address will be used as the source address of the VXLAN tunnels to Switch A and Switch C.
  • Page 58 # Enable L2VPN. <SwitchC> system-view [SwitchC] l2vpn enable # Create a VSI named vpna, and create VXLAN 10. [SwitchC] vsi vpna [SwitchC-vsi-vpna] vxlan 10 [SwitchC-vsi-vpna-vxlan-10] quit [SwitchC-vsi-vpna] quit # Enable IGMP snooping globally. [SwitchB] igmp-snooping [SwitchB -igmp-snooping] quit # Enable IGMP snooping for VSI vpna. [SwitchC] vsi vpna [SwitchC-vsi-vpna] igmp-snooping enable # Enable dropping unknown multicast data packets for VSI vpna.

  • Page 59: Troubleshooting Igmp Snooping

    [SwitchC-vsi-vpna] quit # Configure GigabitEthernet 1/0/1 as a trunk port and assign it to VLAN 2. [SwitchC] interface gigabitethernet 1/0/1 [SwitchC-GigabitEthernet1/0/1] port link-type trunk [SwitchC-GigabitEthernet1/0/1] port trunk permit vlan 2 # On GigabitEthernet 1/0/1, create Ethernet service instance 1000 to match VLAN 2. [SwitchC-GigabitEthernet1/0/1] service-instance 1000 [SwitchC-GigabitEthernet1/0/1-srv1000] encapsulation s-vid 2 # Map Ethernet service instance 1000 to VSI vpna.

  • Page 60: Multicast Group Policy Does Not Work

    Multicast group policy does not work Symptom Hosts can receive multicast data for multicast groups that are not permitted by the multicast group policy. Solution To resolve the problem: Use the display acl command to verify that the configured ACL meets the multicast group policy requirements.

  • Page 61: Configuring Pim Snooping

    Configuring PIM snooping Overview PIM snooping runs on Layer 2 devices. It works with IGMP snooping to analyze received PIM messages, and adds the ports that are interested in specific multicast data to a PIM snooping routing entry. In this way, the multicast data can be forwarded to only the ports that are interested in the data. Figure 17 Multicast packet transmission without or with PIM snooping Multicast packet transmission Multicast packet transmission when...

  • Page 62: Configuring Pim Snooping

    Each PIM router in the VLAN or VSI, whether interested in the multicast data or not, can receive all multicast data and all PIM messages except PIM hello messages. • When the Layer 2 switch runs both IGMP snooping and PIM snooping, it performs the following actions: d.

  • Page 63: Displaying And Maintaining Pim Snooping

    Step Command Remarks an active/standby a downstream port or router port. switchover. Displaying and maintaining PIM snooping Execute display commands in any view and reset commands in user view. Task Command (In standalone mode.) Display PIM snooping display pim-snooping neighbor [ vlan vlan-id | vsi neighbor information.

  • Page 64: Configuration Procedure

    Figure 18 Network diagram Source 1 Receiver 1 Router A Router C GE1/0/1 GE1/0/2 GE1/0/2 GE1/0/1 1.1.1.1/24 10.1.1.1/24 10.1.1.3/24 3.1.1.1/24 1.1.1.100/24 3.1.1.100/24 Switch A GE1/0/1 GE1/0/3 GE1/0/2 GE1/0/4 Source 2 Receiver 2 GE1/0/1 GE1/0/2 GE1/0/2 GE1/0/1 2.1.1.1/24 10.1.1.2/24 10.1.1.4/24 4.1.1.1/24 2.1.1.100/24 Router B Router D...

  • Page 65: Verifying The Configuration

    [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] pim sm [RouterB-GigabitEthernet1/0/2] quit Configure Router C: # Enable IP multicast routing. <RouterC> system-view [RouterC] multicast routing [RouterC-mrib] quit # Enable IGMP on GigabitEthernet 1/0/1. [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] igmp enable [RouterC-GigabitEthernet1/0/1] quit # Enable PIM-SM on GigabitEthernet 1/0/2. [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim sm [RouterC-GigabitEthernet1/0/2] quit...
  • Page 66 Total 4 neighbors. VLAN 100: Total 4 neighbors. 10.1.1.1 Slots (0 in total): Ports (1 in total): GE1/0/1 (00:32:43) 10.1.1.2 Slots (0 in total): Ports (1 in total): GE1/0/2 (00:32:43) 10.1.1.3 Slots (0 in total): Ports (1 in total): GE1/0/3 (00:32:43) 10.1.1.4 Slots (0 in total):...

  • Page 67: Troubleshooting Pim Snooping

    Troubleshooting PIM snooping PIM snooping does not work on a Layer 2 device Symptom PIM snooping does not work on a Layer 2 device. Solution To resolve the problem: Use the display current-configuration command to display information about IGMP snooping and PIM snooping.

  • Page 68: Configuring Multicast Vlans

    Configuring multicast VLANs Overview As shown in Figure 19, Host A, Host B, and Host C are in three different VLANs and the same multicast group. When Switch A (Layer 3 device) receives multicast data for that group, it sends three copies of the multicast data to Switch B (Layer 2 device).
  • Page 69 Figure 20 Sub-VLAN-based multicast VLAN Multicast packets VLAN 10 (Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Source Switch A Switch B IGMP querier VLAN 4 Receiver Host C IGMP snooping manages router ports in the multicast VLAN and member ports in each sub-VLAN. When Switch A receives multicast data from the multicast source, it sends only one copy of the multicast data to the multicast VLAN on Switch B.

  • Page 70: Multicast Vlan Configuration Task List

    Multicast VLAN configuration task list Tasks at a glance (Required.) Perform one of the following tasks: • Configuring a sub-VLAN-based multicast VLAN • Configuring a port-based multicast VLAN: Configuring user port attributes  Assigning user ports to a multicast VLAN ...

  • Page 71: Configuration Procedure

    Configuration procedure To configure a sub-VLAN-based multicast VLAN: Step Command Remarks Enter system view. system-view Configure a VLAN as a By default, a VLAN is not a multicast VLAN and enter its multicast-vlan vlan-id multicast VLAN. view. Assign the specified VLANs By default, a multicast VLAN does to the multicast VLAN as subvlan vlan-list...

  • Page 72: Assigning User Ports To A Multicast Vlan

    Assigning user ports to a multicast VLAN You can assign user ports to a multicast VLAN in multicast VLAN view or assign a user port to a multicast VLAN in interface view. These configurations have the same priority. Configuration restrictions and guidelines When you assign user ports to a multicast VLAN, follow these restrictions and guidelines: •...

  • Page 73: Displaying And Maintaining Multicast Vlans

    Step Command Remarks Set the maximum number of By default, the maximum number multicast VLAN forwarding multicast-vlan entry-limit limit of multicast VLAN forwarding entries. entries is 16384. Displaying and maintaining multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about multicast...
  • Page 74 Figure 22 Network diagram Source IGMP querier GE1/0/2 Vlan-int20 Switch A 1.1.1.2/24 GE1/0/1 1.1.1.1/24 Vlan-int10 10.110.1.1/24 GE1/0/1 Switch B GE1/0/2 GE1/0/4 GE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure Switch A: # Enable IP multicast routing.
  • Page 75 Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 2, assign GigabitEthernet 1/0/2 to the VLAN, and enable IGMP snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port gigabitethernet 1/0/2 [SwitchB-vlan2] igmp-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign GigabitEthernet 1/0/3 to the VLAN, and enable IGMP snooping in the VLAN.

  • Page 76: Port-Based Multicast Vlan Configuration Example

    [SwitchB] display multicast-vlan group Total 1 entries. Multicast VLAN 10: Total 1 entries. (0.0.0.0, 224.1.1.1) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that multicast group 224.1.1.1 belongs to multicast VLAN 10. Multicast VLAN 10 contains sub-VLANs VLAN 2 through VLAN 4.
  • Page 77 [SwitchA] multicast routing [SwitchA-mrib] quit # Create VLAN 20, and assign GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IP address to VLAN-interface 20, and enable PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ip address 1.1.1.2 24 [SwitchA-Vlan-interface20] pim dm [SwitchA-Vlan-interface20] quit...
  • Page 78 # Assign GigabitEthernet 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 2 untagged [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 10 untagged [SwitchB-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 as a hybrid port, and configure VLAN 3 as the PVID of the hybrid port.
  • Page 79 (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (3 in total): GE1/0/2 (00:03:23) GE1/0/3 (00:04:07) GE1/0/4 (00:04:16) The output shows that IGMP snooping maintains the user ports in the multicast VLAN (VLAN 10). Switch B will forward the multicast data of VLAN 10 through these user ports.

  • Page 80: Configuring Multicast Routing And Forwarding

    Configuring multicast routing and forwarding Overview The following tables are involved in multicast routing and forwarding: • Multicast routing table of each multicast routing protocol, such as the PIM routing table. • General multicast routing table that summarizes multicast routing information generated by different multicast routing protocols.
  • Page 81 RPF check implementation in multicast Implementing an RPF check on each received multicast packet brings a big burden to the router. The use of a multicast forwarding table is the solution to this issue. When the router creates a multicast forwarding entry for an (S, G) packet, it sets the RPF interface of the packet as the incoming interface of the (S, G) entry.

  • Page 82: Static Multicast Routes

    • If a multicast packet arrives at Device C on GigabitEthernet 1/0/1, the receiving interface is not the incoming interface of the (S, G) entry. Device C searches its unicast routing table and finds that the outgoing interface to the source (the RPF interface) is GigabitEthernet 1/0/2. In this case, the (S, G) entry is correct, but the packet traveled along a wrong path.

  • Page 83: Multicast Forwarding Across Unicast Subnets

    Figure 26 Creating an RPF route Static multicast routing table on Device C OSPF domain Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 GE1/0/1 1.1.1.1/24 Receiver Device D Static multicast routing table on Device D GE1/0/1 Source/Mask Interface RPF neighbor/Mask 2.2.2.1/24 192.168.0.0/24 GE1/0/1 2.2.2.2/24 Source RIP domain...

  • Page 84: Configuration Task List

    Figure 27 Multicast data transmission through a tunnel Unicast device Multicast device Multicast device Unicast device Tunnel Source Device A Device B Receiver Unicast device Unicast device As shown in Figure 27, a tunnel is established between the multicast routers Device A and Device B. Device A encapsulates the multicast data in unicast IP packets, and forwards them to Device B across the tunnel through unicast routers.

  • Page 85: Configuring Multicast Routing And Forwarding

    Configuring multicast routing and forwarding Before you configure multicast routing and forwarding, complete the following tasks: • Configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Enable PIM-DM or PIM-SM. Configuring static multicast routes To configure a static multicast route for a given multicast source, you can specify an RPF interface or an RPF neighbor for the multicast traffic from that source.

  • Page 86: Configuring Multicast Load Splitting

    Configuring multicast load splitting You can enable the device to split multiple data flows on a per-source basis or on a per-source-and-group basis. This optimizes the traffic delivery. To configure multicast load splitting: Step Command Remarks Enter system view. system-view multicast routing [ vpn-instance Enter MRIB view.

  • Page 87: Displaying And Maintaining Multicast Routing And Forwarding

    Step Command Remarks Enable multicast forwarding By default, multicast data cannot between sub-VLANs that are multicast forwarding supervlan be forwarded between associated with a super community sub-VLANs that are associated VLAN. with a super VLAN. reset multicast [ vpn-instance vpn-instance-name ] forwarding-table Clear all multicast forwarding { { source-address [ mask...
  • Page 88 Task Command interface-type interface-number | slot slot-number | statistics ] display multicast [ vpn-instance vpn-instance-name ] forwarding-table [ source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] | (In IRF mode.) Display multicast chassis chassis-number slot slot-number | forwarding entries.

  • Page 89: Configuration Examples

    Configuration examples Changing an RPF route Network requirements As shown in Figure • PIM-DM runs on the network. • All switches on the network support multicast. • Switch A, Switch B and Switch C run OSPF. • Typically, the receiver host can receive the multicast data from Source through the path: Switch A to Switch B, which is the same as the unicast route.
  • Page 90 # Enable PIM-DM on other interfaces. [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim dm [SwitchB-Vlan-interface101] quit [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] pim dm [SwitchB-Vlan-interface102] quit # On Switch A, enable IP multicast routing. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Enable PIM-DM on each interface. [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] pim dm [SwitchA-Vlan-interface200] quit...

  • Page 91: Creating An Rpf Route

    • The RPF neighbor of Switch B is Switch C. Creating an RPF route Network requirements As shown in Figure • PIM-DM runs on the network. • All switches on the network support IP multicast. • Switch B and Switch C run OSPF, and have no unicast routes to Switch A. •...

  • Page 92: Multicast Forwarding Over A Gre Tunnel

    <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Enable PIM-DM on each interface. [SwitchA] interface vlan-interface 300 [SwitchA-Vlan-interface300] pim dm [SwitchA-Vlan-interface300] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing and PIM-DM on Switch B in the same way Switch A is configured. (Details not shown.) Display RPF information for Source 2 on Switch B and Switch C.
  • Page 93 • Multicast routing and PIM-DM are enabled on Switch A and Switch C. • Switch B does not support multicast. • Switch A, Switch B, and Switch C run OSPF. Configure the switches so that the receiver host can receive the multicast data from Source. Figure 30 Network diagram Multicast router Unicast router...
  • Page 94 # Create a GRE tunnel interface Tunnel 1, and specify the tunnel mode as GRE/IPv4. [SwitchC] interface tunnel 1 mode gre # Assign an IP address for interface Tunnel 1, and specify its source and destination addresses. [SwitchC-Tunnel1] ip address 50.1.1.2 24 [SwitchC-Tunnel1] source 30.1.1.2 [SwitchC-Tunnel1] destination 20.1.1.1 [SwitchC-Tunnel1] quit...

  • Page 95: Troubleshooting Multicast Routing And Forwarding

    Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.1.1.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel1 Upstream neighbor: 50.1.1.1 RPF prime neighbor: 50.1.1.1...

  • Page 96: Configuring Igmp

    Configuring IGMP Overview Internet Group Management Protocol (IGMP) establishes and maintains the multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. IGMP has the following versions: • IGMPv1 (defined by RFC 1112). •...

  • Page 97: Igmpv2 Enhancements

    The hosts send unsolicited IGMP reports to the multicast groups they want to join without having to wait for the IGMP queries. The IGMP querier periodically multicasts IGMP queries (with the destination address of 224.0.0.1) to all hosts and routers on the local subnet. After receiving a query message, the host whose report delay timer expires first sends an IGMP report to multicast group G1 to announce its membership for G1.

  • Page 98: Igmpv3 Enhancements

    After receiving the leave message, the querier sends a configurable number of IGMP group-specific queries to the group that the host is leaving. Both the destination address field and the group address field of the message are the address of the multicast group that is being queried.

  • Page 99: Igmp Ssm Mapping

    IGMPv3 is compatible with IGMPv1 and IGMPv2 and supports IGMP general queries and IGMP group-specific queries. It also introduces IGMP group-and-source-specific queries. A general query does not carry a group address or a source address.  A group-specific query carries a group address, but no source address. ...

  • Page 100: Igmp Proxying

    Figure 33 IGMP SSM mapping IGMPv1 report IGMPv2 report Querier IGMPv3 report Router A Receiver Receiver Receiver Host A (IGMPv1) Host B (IGMPv2) Host C (IGMPv3) As shown in Figure 33, on an SSM network, Host A, Host B, and Host C run IGMPv1, IGMPv2, and IGMPv3, respectively.

  • Page 101: Igmp Support For Vpns

    Figure 34 IGMP proxying Proxy Querier Router B Router A PIM domain Ethernet Receiver Receiver Host B Host A Host C Report from Router B Query from Router A Query from Router B Host interface Report from Host Router interface The following types of interfaces are defined in IGMP proxying: •...

  • Page 102: Igmp Configuration Task List

    IGMP configuration task list Tasks at a glance Configuring basic IGMP features: • (Required.) Enabling IGMP • (Optional.) Specifying an IGMP version • (Optional.) Configuring a static group member • (Optional.) Configuring a multicast group policy Adjusting IGMP performance: (Optional.) Configuring IGMP query and response parameters (Optional.) Enabling fast-leave processing...

  • Page 103: Specifying An Igmp Version

    Specifying an IGMP version For IGMP to operate correctly, specify the same IGMP version for all routers on the same subnet. To specify an IGMP version: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Specify an IGMP version on the igmp version version-number The default setting is 2.

  • Page 104: Adjusting Igmp Performance

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no IGMP multicast igmp group-policy group policy exists on an Configure a multicast group ipv4-acl-number interface. Hosts attached to the policy. [ version-number ] interface can join any multicast groups.
  • Page 105 • To avoid frequent IGMP querier changes, set the IGMP other querier present timer greater than the IGMP general query interval. In addition, configure the same IGMP other querier present timer for all IGMP routers on the same subnet. • To avoid mistakenly deleting multicast receivers, set the IGMP general query interval greater than the maximum response time for IGMP general queries.

  • Page 106: Enabling Fast-Leave Processing

    Configuring the IGMP query and response parameters on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Set the IGMP querier's By default, the IGMP querier's igmp robust-count count robustness variable. robustness variable is 2. By default, the IGMP startup Set the IGMP startup query igmp startup-query-interval...

  • Page 107: Configuring Igmp Ssm Mappings

    Configuring IGMP SSM mappings This feature enables the device to provide SSM services for IGMPv1 or IGMPv2 hosts. This feature does not process IGMPv3 messages. Enable IGMPv3 on the receiver-side interface to ensure that IGMPv3 reports can be processed. Configuration prerequisites Before you configure IGMP SSM mappings, complete the following tasks: •...

  • Page 108: Enabling Multicast Forwarding On A Non-Querier Interface

    ensure that the downstream receiver hosts on the router interface can receive multicast data, you must enable multicast forwarding on the interface. For more information, see "Enabling multicast forwarding on a non-querier interface." To enable IGMP proxying: Step Command Remarks Enter system view.

  • Page 109: Enabling Igmp Nsr

    Step Command Remarks By default, multicast load splitting is disabled, and only the proxy Enable multicast load splitting. proxy multipath interface with the highest IP address on the IGMP proxy device forwards multicast data. Enabling IGMP NSR This feature backs up information about IGMP interfaces and IGMP multicast groups to the standby process.

  • Page 110: Igmp Configuration Examples

    IGMP configuration examples This section provides examples of configuring IGMP on switches. Basic IGMP features configuration examples Network requirements As shown in Figure • OSPF and PIM-DM run on the network. • VOD streams are sent to receiver hosts in multicast. Receiver hosts of different organizations form stub networks N1 and N2.
  • Page 111 # Enable IGMP on VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-DM on VLAN-interface 101. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim dm [SwitchA-Vlan-interface101] quit # On Switch B, enable IP multicast routing. <SwitchB> system-view [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on VLAN-interface 200.

  • Page 112: Igmp Ssm Mapping Configuration Example

    Other querier present time for IGMP: 255s Maximum query response time for IGMP: 10s Querier for IGMP: 10.110.2.1 (This router) IGMP groups reported in total: 1 IGMP SSM mapping configuration example Network requirements As shown in Figure • OSPF runs on the network. •...
  • Page 113 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 36. (Details not shown.) Configure OSPF on the switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, PIM-SM, and IGMP: # On Switch D, enable IP multicast routing. <SwitchD>...
  • Page 114 [SwitchD-pim] ssm-policy 2000 [SwitchD-pim] quit # Configure the SSM group range on Switch A, Switch B, and Switch C in the same way Switch D is configured. (Details not shown.) Configure IGMP SSM mappings on Switch D. [SwitchD] igmp [SwitchD-igmp] ssm-mapping 133.133.1.1 2000 [SwitchD-igmp] ssm-mapping 133.133.3.1 2000 [SwitchD-igmp] quit Verifying the configuration...

  • Page 115: Igmp Proxying Configuration Example

    Total number of downstreams: 1 1: Vlan-interface400 Protocol: igmp, UpTime: 00:13:25, Expires: - IGMP proxying configuration example Network requirements As shown in Figure • PIM-DM runs on the core network. • Host A and Host C on the stub network receive VOD information sent to multicast group 224.1.1.1.

  • Page 116: Troubleshooting Igmp

    [SwitchB-mrib] quit # Enable IGMP proxying on VLAN-interface 100. [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] igmp proxy enable [SwitchB-Vlan-interface100] quit # Enable IGMP on VLAN-interface 200. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit Verifying the configuration # Display multicast group membership information maintained by the IGMP proxy on Switch B. [SwitchB] display igmp proxy group IGMP proxy group records in total: 1 Vlan-interface100(192.168.1.2):...
  • Page 117 Use the display current-configuration command to verify the IGMP information on the interfaces. Make sure the routers on the subnet have the same IGMP settings on their interfaces. Use the display igmp interface command on all routers on the same subnet to verify the IGMP-related timer settings.

  • Page 118: 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 RIP, OSPF, IS-IS, or BGP. PIM uses the underlying unicast routing to generate a multicast routing table without relying on any particular unicast routing protocol.
  • Page 119 this way, the upstream stream node stops forwarding subsequent packets addressed to that multicast group down to this node. NOTE: An (S, G) entry contains a multicast source address S, a multicast group address G, an outgoing interface list, and an incoming interface. A prune process is initiated by a leaf router.

  • Page 120: Pim-Sm Overview

    Figure 39 Assert mechanism Router A Router B Ethernet Assert message Multicast packets Receiver Router C As shown in Figure 39, 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.
  • Page 121 PIM-DM does not require a DR. However, if IGMPv1 runs on any shared-media LAN in a PIM-DM domain, a DR must be elected to act as the IGMPv1 querier for the LAN. For more information about IGMP, see "Configuring IGMP." IMPORTANT: IGMP must be enabled on the device that acts as the receiver-side DR.
  • Page 122 As shown in Figure 41, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between multicast groups and RPs.
  • Page 123 Anycast RP member address—IP address of each Anycast RP member for  communication among the RP members. Anycast RP address—IP address of the Anycast RP set for communication within the  PIM-SM domain. It is also known as RPA. As shown in Figure 42, RP 1, RP 2, and RP 3 are members of an Anycast RP set.
  • Page 124 RPT building Figure 43 RPT building in a PIM-SM domain Host A Source Receiver Host B Server Receiver Join message Multicast packets Host C As shown in Figure 43, the process of building an RPT is as follows: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR.
  • Page 125 Figure 44 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 44, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to the multicast group G. When receiving the multicast packet, the source-side DR encapsulates the packet into a PIM register message and unicasts the message to the RP.

  • Page 126: Bidir-Pim Overview

    When the RP receives the first multicast packet, it sends an (S, G) source-specific join message toward the multicast source. The routers along the path from the RP to the multicast source constitute an SPT. The subsequent multicast data is forwarded to the RP along the SPT without being encapsulated into register messages.
  • Page 127 DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF for each RP on a subnet. Only the DFs can forward multicast data to the RP. DF election is not necessary for an RPL.
  • Page 128 Figure 46 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT Multicast packets Host C As shown in Figure 46, the process for building a receiver-side RPT is the same as the process for building an RPT in PIM-SM: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the directly connected router.

  • Page 129: Administrative Scoping Overview

    Figure 47 RPT building at the multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT Multicast packets Host C As shown in Figure 47, the process for building a source-side RPT is relatively simple: When a multicast source sends multicast packets to the multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
  • Page 130 Multicast group ranges that are associated with different admin-scoped zones can have intersections. However, the multicast groups in an admin-scoped zone are valid only within the local zone, and theses multicast groups are regarded as private group addresses. The global-scoped zone maintains a BSR for the multicast groups that do not belong to any admin-scoped zones.

  • Page 131: Pim-Ssm Overview

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

  • Page 132: Relationship Among Pim Protocols

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

  • Page 133: Pim Support For Vpns

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

  • Page 134: Pim-Dm Configuration Task List

    PIM-DM configuration task list Tasks at a glance (Required.) Enabling PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring PIM-DM graft retry timer (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-DM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.

  • Page 135: Configuring State Refresh Parameters

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the state refresh By default, the state refresh pim state-refresh-capable feature. feature is enabled. Configuring state refresh parameters The state refresh interval determines the interval at which a router sends state refresh messages. It is configurable.

  • Page 136: Configuring Pim-Sm

    For more information about the configuration of other timers in PIM-DM, see "Configuring common timers." Configuring PIM-SM This section describes how to configure PIM-SM. PIM-SM configuration task list Tasks at a glance Remarks (Required.) Enabling PIM-SM (Required.) Configuring an • Configuring a static RP You must configure a static RP, a C-RP, or both in a •...

  • Page 137: Configuring An Rp

    Step Command Remarks Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast routing is and enter MRIB view. vpn-instance-name ] disabled. Return to system view. quit interface interface-type Enter interface view. interface-number Enable PIM-SM. pim sm By default, PIM-SM is disabled. Configuring an RP An RP can provide services for multiple or all multicast groups.
  • Page 138 Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] c-rp ip-address [ advertisement-interval Configure a C-RP. adv-interval | group-policy By default, no C-RPs exist. ipv4-acl-number | holdtime hold-time | priority priority ] * By default, no C-RP policy exists, (Optional.) Configure a C-RP crp-policy ipv4-acl-number and all C-RP advertisement...

  • Page 139: Configuring A Bsr

    Step Command Remarks vpn-instance-name ] By default, Anycast RP is not configured. anycast-rp anycast-rp-address Configure Anycast RP. You can repeat this command to member-rp-address add multiple RP member addresses to the Anycast RP set. Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP. You do not need to configure a BSR when you have configured only a static RP but no C-RPs.
  • Page 140 Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] c-bsr ip-address [ scope group-address { mask-length | Configure a C-BSR. By default, no C-BSRs exist. mask } ] [ hash-length hash-length | priority priority ] * By default, no BSR policy exists, (Optional.) Configure a BSR bsr-policy ipv4-acl-number...

  • Page 141: Configuring Multicast Source Registration

    Disabling the device from forwarding BSMs out of their incoming interfaces By default, the device forwards BSMs out of their incoming interfaces to avoid the situation that some devices cannot receive the BSMs due to inconsistent routing information. This results in duplicated traffic.

  • Page 142: Configuring The Switchover To Spt

    Step Command Remarks vpn-instance-name ] By default, no PIM register policy Configure a PIM register register-policy ipv4-acl-number exists, and all PIM register policy. messages are regarded as legal. Configure the device to By default, the device calculates calculate the checksum register-whole-checksum the checksum based on the based on the entire register...

  • Page 143: Configuration Prerequisites

    Tasks at a glance Remarks • (Optional.) Setting the maximum number of BIDIR-PIM RPs Configuring a BSR: • (Required.) Configuring a C-BSR • (Optional.) Configuring a PIM domain border Skip the task of configuring a BSR • on a network without C-RPs. (Optional.) Disabling BSM semantic fragmentation •...
  • Page 144 An RP can provide services for multiple or all multicast groups. However, only one RP can forward multicast traffic for a multicast group at a time. An RP can be manually configured or dynamically elected through the BSR mechanism. For a large-scaled PIM network, configuring static RPs is a tedious job.

  • Page 145: Configuring A Bsr

    Step Command Remarks services for BIDIR-PIM. [ advertisement-interval adv-interval | group-policy ipv4-acl-number | holdtime hold-time | priority priority ] * bidir Enabling Auto-RP listening This feature enables the device to receive Auto-RP announcement and discovery messages and learn RP information. The destination IP addresses for Auto-RP announcement and discovery messages are 224.0.1.39 and 224.0.1.40, respectively.
  • Page 146 Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain. When a C-BSR receives the BSM from another C-BSR, it compares its own priority with the priority carried in the message. The C-BSR with a higher priority wins the BSR election. If a tie exists in the priority, the C-BSR with a higher IP address wins.

  • Page 147: Configuring Pim-Ssm

    Step Command Remarks Configure a PIM domain By default, an interface is not a pim bsr-boundary border. PIM domain border. Disabling BSM semantic fragmentation BSM semantic fragmentation enables a BSR to split a BSM into multiple BSM fragments (BSMFs) if the BSM exceeds the MTU.

  • Page 148: Pim-Ssm Configuration Task List

    PIM-SSM configuration task list Tasks at a glance (Required.) Enabling PIM-SM (Optional.) Configuring the SSM group range (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-SSM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.

  • Page 149: Configuring Common Pim Features

    Configuration procedure To configure an SSM group range: Step Command Remarks Enter system view. system-view Enter PIM view. Configure the SSM group By default, the SSM group range ssm-policy ipv4-acl-number range. is 232.0.0.0/8. Configuring common PIM features Configuration task list Tasks at a glance (Optional.) Configuring a multicast source policy...

  • Page 150: Configuring A Pim Hello Policy

    Step Command Remarks vpn-instance-name ] By default, no multicast source Configure a multicast source source-policy ipv4-acl-number policy exists. The device does not policy. filter multicast data packets. Configuring a PIM hello policy This feature enables the device to filter PIM hello messages by using an ACL that specifies the packet source addresses.
  • Page 151 If you enable neighbor tracking on an upstream router, this router can track the states of the downstream nodes for which the joined state holdtime timer has not expired. If you want to enable neighbor tracking, you must enable it on all PIM routers on a shared-media LAN. Otherwise, the upstream router cannot track join messages from every downstream routers.

  • Page 152: Configuring Common Pim Timers

    Configuring common PIM timers IMPORTANT: To prevent the upstream neighbors from aging out, you must configure the interval for sending join/prune messages to be less than the joined/pruned state holdtime timer. The following are common timers in PIM: • Hello interval—Interval at which a PIM router sends hello messages to discover PIM neighbors, and maintain PIM neighbor relationship.

  • Page 153: Setting The Maximum Size Of A Join Or Prune Message

    Step Command Remarks Set the hello interval. pim timer hello interval The default setting is 30 seconds. Set the triggered hello delay. pim triggered-hello-delay delay The default setting is 5 seconds. The default setting is 60 seconds. Set the join/prune interval. pim timer join-prune interval This configuration takes effect after the current interval ends.

  • Page 154: Enabling Pim Nsr

    register-stop and C-RP-Adv messages), and it acts as the DR on the subnet. In BIDIR-PIM, it also acts as the DF. Configuration restrictions and guidelines When you enable PIM passive mode, follow these restrictions and guidelines: • This feature takes effect only when PIM-DM or PIM-SM is enabled on the interface. •...

  • Page 155: Displaying And Maintaining Pim

    To set a DSCP value for outgoing PIM messages: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Set a DSCP value for outgoing By default, the DSCP value for dscp dscp-value PIM messages. outgoing PIM messages is 48.
  • Page 156 • VOD streams are sent to receiver hosts in multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist on each stub network. • The entire PIM domain operates in the dense mode. •...
  • Page 157 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-DM on VLAN-interface 103. [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit # Enable IP multicast routing, IGMP, and PIM-DM on Switch B and Switch C in the same way Switch A is configured. (Details not shown.) # On Switch D, enable IP multicast routing, and enable PIM-DM on each interface.

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

    (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Vlan-interface103 Upstream neighbor: 192.168.1.2...
  • Page 159 • VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub networks, and a minimum of one receiver host exist on each stub network. • The entire PIM-SM domain contains only one BSR. • Host A and Host C are multicast receivers on two stub networks N1 and N2.
  • Page 160 Enable IP multicast routing, and enable IGMP and PIM-SM: # On Switch A, enable IP multicast routing. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Enable IGMP on the receiver-side interface (VLAN-interface 100). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-SM on the other interfaces.

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

    [SwitchA] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30...
  • Page 162 • IGMPv2 runs between Switch A, Switch E, Switch I, and the receivers that directly connect to them, respectively. Figure 54 Network diagram Admin-scope 1 Receiver Vlan-int500 Switch G Host A Source 1 Vlan-int109 Source 3 Vlan-int100 Vlan-int200 Vlan-int109 Vlan-int101 Vlan-int102 Vlan-int102 Switch F...
  • Page 163 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 54. (Details not shown.) Configure OSPF on all switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, and enable IGMP and PIM-SM: # On Switch A, enable IP multicast routing.
  • Page 164 <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 as the boundary of admin-scoped zone 2. <SwitchD> system-view [SwitchD] interface vlan-interface 107 [SwitchD-Vlan-interface107] multicast boundary 239.0.0.0 8 [SwitchD-Vlan-interface107] quit...
  • Page 165 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 Uptime: 00:04:54 Candidate BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 # Display BSR information on Switch D. [SwitchD] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44...

  • Page 166: Bidir-Pim Configuration Example

    Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 00:03:39 00:01:51 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.1.2 (local) 00:07:44 00:01:51 # Display RP information on Switch D. [SwitchD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority...
  • Page 167 Figure 55 Network diagram Receiver 1 Receiver 2 Loop0 Switch B Vlan-int200 Vlan-int102 Vlan-int102 Switch C Host A Vlan-int101 Vlan-int103 Host B BIDIR-PIM Source 1 Source 2 Vlan-int101 Vlan-int103 Vlan-int100 Vlan-int400 Switch A Switch D Table 13 Interface and IP address assignment Device Interface IP address...
  • Page 168 [SwitchA-pim] quit # On Switch B, enable IP multicast routing. <SwitchB> system-view [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit # Enable PIM-SM on the other interfaces. [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit...
  • Page 169 [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim sm [SwitchD-Vlan-interface103] quit # Enable BIDIR-PIM. [SwitchD] pim [SwitchD-pim] bidir-pim enable [SwitchD-pim] quit On Switch C, configure VLAN interface 102 as a C-BSR, and Loopback 0 as a C-RP for the entire BIDIR-PIM domain. [SwitchC-pim] c-bsr 10.110.2.2 [SwitchC-pim] c-rp 1.1.1.1 bidir [SwitchC-pim] quit...

  • Page 170: Pim-Ssm Configuration Example

    Flags: 0x0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100 # Display information about DFs for multicast forwarding on Switch B. [SwitchB] display multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 1.1.1.1 Flags: 0x0 Uptime: 00:06:24 RPF interface: Vlan-interface102 List of 2 DF interfaces:...
  • Page 171 • Host A and Host C are multicast receivers on two stub networks. • The SSM group range is 232.1.1.0/24. • IGMPv3 runs between Switch A and N1, and between Switch B, Switch C, and N2. Figure 56 Network diagram Receiver Host A Switch A...
  • Page 172 # Enable IGMPv3 on the receiver-side interface (VLAN-interface 100). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] igmp version 3 [SwitchA-Vlan-interface100] quit # Enable PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing, IGMP, and PIM-SM on Switch B and Switch C in the same way...

  • Page 173: Troubleshooting Pim

    1: Vlan-interface100 Protocol: igmp, UpTime: 00:13:25, Expires: 00:03:25 # Display the PIM routing table on Switch D. [SwitchD] display pim routing-table Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: LOC UpTime: 00:12:05 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information:...

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

    Multicast data is abnormally terminated on an intermediate router Symptom An intermediate router can receive multicast data successfully, but the data cannot reach the last-hop router. An interface on the intermediate router receives multicast data but does not create an (S, G) entry in the PIM routing table. Solution To resolve the problem: Use display current-configuration to verify the multicast forwarding boundary settings.
  • Page 175 If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 176: Configuring Msdp

    Configuring MSDP Overview Multicast Source Discovery Protocol (MSDP) is an inter-domain multicast solution that addresses the interconnection of PIM-SM domains. It discovers multicast source information in other PIM-SM domains. In the basic PIM-SM mode, a multicast source registers only with the RP in the local PIM-SM domain, and the multicast source information in each domain is isolated.
  • Page 177 As shown in Figure 57, 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 created on RPs: Source-side MSDP peer—MSDP peer closest to the multicast source, such as RP 1. The ...
  • Page 178 Figure 58 Inter-domain multicast delivery through MSDP Receiver DR 2 MSDP peers Multicast packets SA message RP 2 Join message PIM-SM 2 Register message DR 1 Source PIM-SM 4 RP 1 RP 3 PIM-SM 1 PIM-SM 3 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 data within a register message.
  • Page 179 determines whether to initiate an RPT-to-SPT switchover process based on its configuration. If no receivers exist in the domain, RP 2 neither creates an (S, G) entry nor sends a join  message toward the multicast source. In inter-domain multicasting using MSDP, once an RP gets information about a multicast source in another PIM-SM domain, it no longer relies on RPs in other PIM-SM domains.
  • Page 180 Figure 59 Anycast RP through MSDP RP 1 RP 2 Router A Router B PIM-SM Source Receiver MSDP peers SA message The following describes how Anycast RP through MSDP is implemented: a. After receiving the multicast data from Source, the source-side DR registers with the closest RP (RP 1 in this example).

  • Page 181: Msdp Support For Vpns

    Figure 60 MSDP peer-RPF forwarding Source RP 1 RP 5 RP 9 RP 8 AS 1 AS 5 Mesh group AS 3 RP 2 RP 3 AS 2 MSDP peers RP 4 RP 6 RP 7 Static RPF peers AS 4 SA message The process of peer-RPF forwarding is as follows: RP 1 creates an SA message and forwards it to its peer RP 2.

  • Page 182: Msdp Configuration Task List

    • RFC 3446, Anycast Rendezvous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) MSDP configuration task list Tasks at a glance Configuring basic MSDP features: • (Required.) Enabling MSDP • (Required.) Specifying an MSDP peer •...

  • Page 183: Specifying An Msdp Peer

    Specifying an MSDP peer An MSDP peering relationship is identified by an address pair (the addresses of the local MSDP peer and the remote MSDP peer). To create an MSDP peering connection, you must perform the following operation on both devices that are a pair of MSDP peers. If an MSDP peer and a BGP or MBGP peer share the same interface, specify the MSDP peer and the BGP or MBGP peer by using the same IP address.

  • Page 184: Configuring A Description For An Msdp Peer

    Configuring a description for an MSDP peer This feature helps administrators easily distinguish an MSDP peer from other MSDP peers. To configure a description for an MSDP peer: Step Command Remarks Enter system view. system-view msdp [ vpn-instance Enter MSDP view. vpn-instance-name ] Configure a description for peer peer-address description...

  • Page 185: Configuring Sa Message-Related Parameters

    • A new MSDP peer is created. • A previously deactivated MSDP peering connection is reactivated. • A previously failed MSDP peer attempts to resume operation. You can change the MSDP connection retry interval to adjust the interval between MSDP peering connection attempts.

  • Page 186: Configuring The Originating Rp Of Sa Messages

    messages and send them to the source-side RP. The source-side RP transmits the (S, G) information to the remote RP through SA messages. Then, the remote RP sends join messages to the source-side DR and builds an SPT. Because the (S, G) entries have timed out, remote receivers can never receive the multicast data from the multicast source.

  • Page 187: Configuring Sa Message Policies

    To configure SA request messages: Step Command Remarks Enter system view. system-view msdp [ vpn-instance Enter MSDP view. vpn-instance-name ] By default, after receiving a new join message, a device Enable the device to send SA peer peer-address does not send an SA request request messages to an request-sa-enable message to any MSDP peer.

  • Page 188: Configuring The Sa Cache Mechanism

    Configuring the SA cache mechanism The SA cache mechanism enables the router to locally cache (S, G) entries contained in SA messages. It reduces the time for obtaining multicast source information, but increases memory occupation. With the SA cache mechanism enabled, when the router receives a new (*, G) join message, it searches its SA message cache first.

  • Page 189: Msdp Configuration Examples

    Task Command listen | shutdown } ] display msdp non-stop-routing status Display MSDP NSR status information. display msdp [ vpn-instance vpn-instance-name ] Display detailed status of MSDP peers. peer-status [ peer-address ] display msdp [ vpn-instance vpn-instance-name ] Display (S, G) entries in the SA cache. sa-cache [ group-address | source-address | as-number ] * display msdp [ vpn-instance vpn-instance-name ]...
  • Page 190 Figure 61 Network diagram AS 100 AS 200 Receiver Receiver Loop0 Switch F Switch E Vlan-int105 Source 1 Vlan-int105 Vlan-int102 Vlan-int100 PIM-SM 3 Switch A PIM-SM 2 Vlan-int102 Switch B Vlan-int101 Vlan-int104 Vlan-int101 Vlan-int104 Switch C Switch D Loop0 Loop0 Source 2 PIM-SM 1 MSDP peers...
  • Page 191 [SwitchA-Vlan-interface103] pim sm [SwitchA-Vlan-interface103] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit # Enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] igmp enable [SwitchA-Vlan-interface200] quit # Enable IP multicast routing and PIM-SM on Switch B, Switch C, Switch D, Switch E, and Switch F in the same way Switch A is configured.
  • Page 192 [SwitchB-ospf-1] import-route bgp [SwitchB-ospf-1] quit Configure MSDP peers: # Configure an MSDP peer on Switch B. [SwitchB] msdp [SwitchB-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 [SwitchB-msdp] quit # Configure an MSDP peer on Switch C. [SwitchC] msdp [SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 [SwitchC-msdp] peer 192.168.3.2 connect-interface vlan-interface 102 [SwitchC-msdp] quit # Configure MSDP peers on Switch E.
  • Page 193 * > 1.1.1.1/32 192.168.1.1 100? * >i 2.2.2.2/32 0.0.0.0 * > 192.168.1.0 0.0.0.0 * > 192.168.1.1/32 0.0.0.0 * > 192.168.1.2/32 0.0.0.0 # Verify that hosts in PIM-SM 1 and PIM-SM 3 can receive the multicast data from Source 1 in PIM-SM 1 and Source 2 in PIM-SM 2.

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

    Import policy: None Export policy: None Information about SA-Requests: Policy to accept SA-Requests: None Sending SA-Requests status: Disable Minimum TTL to forward SA with encapsulated data: 0 SAs learned from this peer: 0, SA cache maximum for the peer: 4294967295 Input queue size: 0, Output queue size: 0 Counters for MSDP messages: RPF check failure: 0...
  • Page 195 Figure 62 Network diagram AS 100 AS 200 PIM-SM 3 Receiver Switch G Vlan-int106 Vlan-int106 Switch F Loop0 Loop0 Receiver Vlan-int102 Vlan-int102 Switch A Switch C PIM-SM 2 Switch D Switch E Vlan-int103 Vlan-int105 Vlan-int103 Vlan-int105 Vlan-int100 Switch B Source 1 Loop0 Source 2 PIM-SM 1...
  • Page 196 # Enable PIM-SM on each interface, and enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim sm [SwitchC-Vlan-interface104] quit # Configure Switch A, Switch B, Switch D, Switch E, Switch F, and Switch G in the same way Switch C is configured.
  • Page 197 [SwitchC] bgp 100 [SwitchC-bgp] router-id 1.1.1.3 [SwitchC-bgp] peer 10.110.4.2 as-number 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 10.110.4.2 enable [SwitchC-bgp-ipv4] import-route ospf 1 [SwitchC-bgp-ipv4]quit [SwitchC-bgp] quit # On Switch F, configure an EBGP peer, and redistribute OSPF routing information. [SwitchF] bgp 200 [SwitchF-bgp] router-id 3.3.3.1 [SwitchF-bgp] peer 10.110.4.1 as-number 100 [SwitchF-bgp] address-family ipv4 unicast...

  • Page 198: Anycast Rp Configuration

    # On Switch G, configure Switch A as the MSDP peer and static RPF peer. [SwitchG] ip prefix-list list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32 [SwitchG] msdp [SwitchG-msdp] peer 10.110.2.1 connect-interface vlan-interface 106 [SwitchG-msdp] static-rpf-peer 10.110.2.1 rp-policy list-a [SwitchG-msdp] quit Verifying the configuration # Display the BGP peering relationships on Switch A.
  • Page 199 Figure 63 Network diagram Source 1 Source 2 Switch A Switch C Switch E Vlan-int300 Vlan-int400 Receiver Receiver Switch B Switch D Vlan-int100 Vlan-int200 Host A Host B Loop10 Loop10 PIM-SM MSDP peers Table 17 Interface and IP address assignment Device Interface IP address...
  • Page 200 [SwitchB-Vlan-interface100] quit # Enable PIM-SM on the other interfaces. [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] pim sm [SwitchB-Vlan-interface103] quit [SwitchB] interface Vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] pim sm [SwitchB-LoopBack0] quit [SwitchB] interface loopback 10 [SwitchB-LoopBack10] pim sm [SwitchB-LoopBack10] quit [SwitchB] interface loopback 20...
  • Page 201 [SwitchD] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 1.1.1.1 Established 00:10:57 # Send an IGMP report from Host A to join multicast group 225.1.1.1. (Details not shown.) # Send multicast data from Source 1 to multicast group 225.1.1.1. (Details not shown.) # Display the PIM routing table on Switch D.

  • Page 202: Sa Message Filtering Configuration

    # Display the PIM routing table on Switch D. [SwitchD] display pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: WC UpTime: 00:12:07 Upstream interface: Register Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200...
  • Page 203 Figure 64 Network diagram PIM-SM 1 PIM-SM 2 PIM-SM 3 Loop0 Source 2 Vlan-int100 Switch A Receiver Loop0 Host A Vlan-int400 Switch C Vlan-int104 Vlan-int104 Switch D Vlan-int300 Vlan-int500 Source 1 Vlan-int200 Switch B Receiver Receiver Host B Host C MSDP peers Table 18 Interface and IP address assignment Device...
  • Page 204 [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit [SwitchA] interface loopback 0 [SwitchA-LoopBack0] pim sm [SwitchA-LoopBack0] quit # Enable IP multicast routing, IGMP, and PIM-SM on Switch B, Switch C, and Switch D in the same way Switch A is configured.

  • Page 205: Troubleshooting Msdp

    [SwitchC] acl advanced 3001 [SwitchC-acl-ipv4-adv-3001] rule deny ip source 10.110.3.100 0 destination 225.1.1.0 0.0.0.3 [SwitchC-acl-ipv4-adv-3001] rule permit ip source any destination any [SwitchC-acl-ipv4-adv-3001] quit [SwitchC] msdp [SwitchC-msdp] peer 10.110.5.2 sa-policy export acl 3001 [SwitchC-msdp] quit # Configure an SA creation policy on Switch D so that Switch D will not create SA messages for Source 2.

  • Page 206: Msdp Peers Stay In Disabled State

    MSDP peers stay in disabled state Symptom The configured MSDP peers stay in disabled state. Solution To resolve the problem: Use the display ip routing-table command to verify that the unicast route between the routers is reachable. Verify that a unicast route is available between the two routers that will become MSDP peers to each other.

  • Page 207: Configuring Multicast Vpn

    Configuring multicast VPN Overview Multicast VPN implements multicast delivery in VPNs. A VPN contains multiple customer network sites and the public network provided by the network service provider. The sites communicate through the public network. As shown in Figure • VPN A contains Site 1, Site 3, and Site 5.

  • Page 208: Md Vpn Overview

    Figure 66 Multicast in multiple VPN instances PE 1" PE 2" Site 3 MD A Site 1 Site 5 PE 3" VPN instance A PE 1' PE 2' PE 3' Public instance Site 4 PE 1"' MD B PE 2"' Site 2 Site 6 PE 3"'...
  • Page 209 Table 19 Basic MD VPN concepts Concept Description An MD is a set of PE devices that are in the same VPN instance. Multicast domain (MD) Each MD uniquely corresponds to a VPN instance. An MDT is a multicast distribution tree constructed by all PE devices Multicast distribution tree (MDT) in the same VPN.
  • Page 210 b. The encapsulated multicast packet is sent by the PE device and travels over the public network. c. After receiving the multicast packet, the remote PE device decapsulates the multicast packet to get the original VPN multicast packet. • The local PE device sends VPN data out of the MTI. The remote PE devices receive the private data from their MTI interfaces.

  • Page 211: Protocols And Standards

    packets with the data-group address. Then they are switched from the default-MDT to the data-MDT. For more information about MDT switchover, see "MDT switchover." NOTE: A VPN uniquely corresponds to an MD and an MD provides services for only one VPN, which is called a one-to-one relationship.

  • Page 212: Default-Mdt Establishment

    For a VPN instance, multicast data transmission on the public network is transparent. The VPN data is exchanged between the MTIs of the local PE and the remote PE. This implements the seamless transmission of the VPN data over the public network. However, the multicast data transmission process (the MDT transmission process) over the public network is very complicated.
  • Page 213 Default-MDT establishment in a PIM-SM network Figure 70 Default-MDT establishment in a PIM-SM network BGP: 11.1.3.1/24 PE 3 Default-group: 239.1.1.1 Public instance BGP peers RPT (*, 239.1.1.1) SPT (11.1.1.1, 239.1.1.1) SPT (11.1.2.1, 239.1.1.1) SPT (11.1.3.1, 239.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in...
  • Page 214 Default-MDT establishment in a BIDIR-PIM network Figure 71 Default-MDT establishment in a BIDIR-PIM network BGP: 11.1.3.1/24 PE 3 Default-Group: 239.1.1.1 Public instance BGP peers Receiver-side RPT (*, 239.1.1.1) Source-side RPT (*, 239.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 71, BIDIR-PIM runs on the network, and all the PE devices support VPN instance...

  • Page 215: Default-Mdt-Based Delivery

    Default-MDT establishment in a PIM-SSM network Figure 72 Default-MDT establishment in a PIM-SSM network BGP: 11.1.3.1/24 PE 3 Default-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 72, PIM-SSM runs on the network, and all the PE devices support VPN instance...
  • Page 216 A flood-prune process (in PIM-DM) or a join process (in PIM-SSM) is initiated across the  public network to establish an SPT across the public network. • If the VPN network runs PIM-SM: Hello packets are forwarded through MTI interfaces to establish PIM neighboring ...
  • Page 217 After receiving the join message from CE 2, the VPN instance on PE 2 creates a state entry (*, 225.1.1.1) and specifies the MTI interface as the upstream interface. The VPN instance on PE 2 considers the join message to have been sent out of the MTI interface, because step 3 is transparent to the VPN instance.

  • Page 218: Mdt Switchover

    Figure 74 Multicast data packet delivery BGP: 11.1.3.1/24 PE 3 Source Receiver CE 1 CE 2 PE 1 PE 2 Site 1 Site 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 Public instance BGP peers S: 192.1.1.1/24 G: 225.1.1.1 VPN instance packets (192.1.1.1, 225.1.1.1) Default-group: 239.1.1.1 Public instance packets (11.1.1.1, 239.1.1.1) A VPN multicast data packet is delivered across the public network as follows:...

  • Page 219: Inter-As Md Vpn

    connect VPN multicast receivers and multicast sources. When specific network criteria are met, a switchover from the default-MDT to the data-MDT occurs to forward VPN multicast traffic to receivers. The process of default-MDT to data-MDT switchover is as follows: The source-side PE device (PE 1, for example) periodically examines the forwarding rate of the VPN multicast traffic.
  • Page 220 • Multihop EBGP redistribution of labeled VPN-IPv4 routes between PE routers—PEs advertise VPN-IPv4 routes to each other through MP-EBGP. This solution is also called inter-AS option C. For more information about the three inter-AS VPN solutions, see "Configuring MPLS L3VPN." Based on these solutions, there are three ways to implement inter-AS MD VPN: •...
  • Page 221 When a device receives the join message with the RPF vector, it first checks whether the RPF vector is its own IP address. If so, the device removes the RPF vector, and sends the message to its upstream neighbor according to the route to the remote PE device. Otherwise, it keeps the RPF vector, looks up the route to the RPF vector, and sends the message to the next hop of the route.

  • Page 222: Configuration Restrictions And Guidelines

    When PE 1 joins the SPT rooted at PE 1, PE 2 also initiates a join process to the SPT rooted at PE 1. A MDT is established when the two SPTs are finished. MD VPN inter-AS option C As shown in Figure •...

  • Page 223: Configuring Md Vpn

    Tasks at a glance • (Required.) Creating an MD for a VPN instance • (Required.) Create an MD address family • (Required.) Specifying the default-group • (Required.) Specifying the MD source interface • (Optional.) Configuring MDT switchover parameters • (Optional.) Configuring the RPF vector feature •...

  • Page 224: Creating An Md For A Vpn Instance

    Step Command Remarks Enter system view. system-view By default, no VPN instances exist. Create a VPN instance and ip vpn-instance For more information about this enter its view. vpn-instance-name command, see MPLS Command Reference. By default, a VPN instance is not configured with an RD.

  • Page 225: Specifying The Default-Group

    Specifying the default-group An MTI of a VPN instance uses the default-group as the destination address to encapsulate multicast packets for the VPN instance. Configuration restrictions and guidelines When you specify the default-group, follow these restrictions and guidelines: • Perform this task on PE devices. •...

  • Page 226: Configuring Mdt Switchover Parameters

    Configuring MDT switchover parameters To decrease traffic interruption caused by frequent default-MDT to data-MDT switchovers, you can specify a data-delay period. The switchover occurs a data-delay period after the multicast VPN data first arrives, regardless of whether multicast VPN data keeps arriving during the period. Perform this task on PE devices.

  • Page 227: Enabling Data-Group Reuse Logging

    Enabling data-group reuse logging For a given VPN, the number of VPN multicast streams to be switched to data-MDTs might exceed the number of addresses in the data-group range. In this case, the VPN instance on the source-side PE device can reuse the addresses in the address range. With data-group reuse logging enabled, the address reuse information will be logged.

  • Page 228: Configuring A Bgp Mdt Route Reflector

    Step Command Remarks bgp as-number [ instance Enter BGP instance view. instance-name ] Create a BGP IPv4 MDT By default, no BGP IPv4 address address family and enter its address-family ipv4 mdt family exists. view. By default, the router cannot exchange BGP MDT routing information with a BGP peer or peer group.

  • Page 229: Displaying And Maintaining Multicast Vpn

    Step Command Remarks command, see Layer 3—IP Routing Command Reference. By default, a route reflector uses its router ID as the cluster ID. (Optional.) Configure the reflector cluster-id { cluster-id | cluster ID of the route For more information about this ip-address } reflector.
  • Page 230 Item Network requirements 225.2.2.0 to 225.2.2.15. • For VPN instance b, the default-group is 239.2.2, and the data-group range is 225.4.4.0 to 225.4.4.15. • PE 1: VLAN-interface 11 and VLAN-interface 20 belong to VPN instance a. VLAN-interface 12 and Loopback 1 belong to the public network instance. •...
  • Page 231 Figure 78 Network diagram VPN a Loop1 VPN b CE a2 VPN a Vlan-int30 Loop1 CE b1 Vlan-int50 Loop1 Loop1 GE1/0/4 CE a3 PE 2 Vlan-int19 GE1/0/4 Vlan-int19 PE 3 GE1/0/4 Loop2 Vlan-int60 PE 1 CE a1 CE b2 Public Vlan-int10 Loop1 VPN b...
  • Page 232 # Configure a global router ID, and enable IP multicast routing on the public network. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE1] service-loopback group 1 type multicast-tunnel # Assign GigabitEthernet 1/0/4 to service loopback group 1.
  • Page 233 [PE1-Vlan-interface20] ip address 10.110.1.1 24 [PE1-Vlan-interface20] igmp enable [PE1-Vlan-interface20] quit # Associate VLAN-interface 11 with VPN instance a. [PE1] interface vlan-interface 11 [PE1-Vlan-interface11] ip binding vpn-instance a # Assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface. [PE1-Vlan-interface11] ip address 10.110.2.1 24 [PE1-Vlan-interface11] pim sm [PE1-Vlan-interface11] quit...
  • Page 234 [PE2] multicast routing [PE2-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE2] service-loopback group 1 type multicast-tunnel # Assign GigabitEthernet 1/0/4 to service loopback group 1. The interface does not belong to VLAN 13, VLAN 14, or VLAN 15.
  • Page 235 [PE2-md-a-ipv4] default-group 239.1.1.1 [PE2-md-a-ipv4] source loopback 1 [PE2-md-a-ivp4] data-group 225.2.2.0 28 [PE2-md-a-ipv4] quit [PE2-md-a] quit # Assign an IP address to VLAN-interface 15. [PE2] interface vlan-interface 15 [PE2-Vlan-interface15] ip address 192.168.7.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 15. [PE2-Vlan-interface15] pim sm [PE2-Vlan-interface15] mpls enable [PE2-Vlan-interface15] mpls ldp enable...
  • Page 236 [PE2-bgp-default-ipv4-b] quit [PE2-bgp-default-b] quit [PE2–bgp-default] address-family vpnv4 [PE2–bgp-default-vpnv4] peer vpn-g enable [PE2–bgp-default-vpnv4] quit [PE2–bgp-default] 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 [PE2-ospf-1-area-0.0.0.0] network 192.168.7.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # Configure RIP. [PE2] rip 2 vpn-instance a [PE2-rip-2] network 10.110.3.0 0.0.0.255 [PE2-rip-2] import-route bgp [PE2-rip-2] quit...
  • Page 237 # Create an MD for VPN instance a. [PE3] multicast-domain vpn-instance a # Create an MD IPv4 address family for VPN instance a. [PE3-md-a] address-family ipv4 # Specify the default-group, the MD source interface, and the data-group range for VPN instance a.
  • Page 238 [PE3-Vlan-interface18] ip binding vpn-instance b # Assign an IP address to VLAN-interface 18, and enable PIM-SM on the interface. [PE3-Vlan-interface18] ip address 10.110.6.1 24 [PE3-Vlan-interface18] pim sm [PE3-Vlan-interface18] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 1.1.1.3 32 [PE3-LoopBack1] pim sm...
  • Page 239 [PE3-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure RIP. [PE3] rip 2 vpn-instance a [PE3-rip-2] network 10.110.5.0 0.0.0.255 [PE3-rip-2] import-route bgp [PE3-rip-2] quit [PE3] rip 3 vpn-instance b [PE3-rip-3] network 10.110.6.0 0.0.0.255 [PE3-rip-3] network 33.33.33.33 0.0.0.0 [PE3-rip-3] import-route bgp [PE3-rip-3] return Configure P: # Enable IP multicast routing on the public network.
  • Page 240 [P] interface loopback 1 [P-LoopBack1] ip address 2.2.2.2 32 [P-LoopBack1] pim sm [P-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP. [P] pim [P-pim] c-bsr 2.2.2.2 [P-pim] c-rp 2.2.2.2 [P-pim] quit # Configure OSPF. [P] ospf 1 [P-ospf-1] area 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 [P-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255...
  • Page 241 [CEb1-Vlan-interface13] ip address 10.110.3.2 24 [CEb1-Vlan-interface13] pim sm [CEb1-Vlan-interface13] quit # Configure RIP. [CEb1] rip 3 [CEb1-rip-3] network 10.110.3.0 0.0.0.255 [CEb1-rip-3] network 10.110.8.0 0.0.0.255 Configure CE a2: # Enable IP multicast routing. <CEa2> system-view [CEa2] multicast routing [CEa2-mrib] quit # Assign an IP address to VLAN-interface 40, and enable IGMP on the interface. [CEa2] interface vlan-interface 40 [CEa2-Vlan-interface40] ip address 10.110.9.1 24 [CEa2-Vlan-interface40] igmp enable...
  • Page 242 [CEa3-mrib] quit # Assign an IP address to VLAN-interface 50, and enable IGMP on the interface. [CEa3] interface vlan-interface 50 [CEa3-Vlan-interface50] ip address 10.110.10.1 24 [CEa3-Vlan-interface50] igmp enable [CEa3-Vlan-interface50] quit # Assign an IP address to VLAN-interface 17, and enable PIM-SM on the interface. [CEa3] interface vlan-interface 17 [CEa3-Vlan-interface17] ip address 10.110.5.2 24 [CEa3-Vlan-interface17] pim sm...

  • Page 243: Md Vpn Inter-As Option B Configuration Example

    # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 2. [PE2] display multicast-domain default-group local MD local default-group information: Group address Source address Interface VPN instance 239.1.1.1 1.1.1.2 MTunnel0 239.1.1.1 1.1.1.2 MTunnel1 # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 3.
  • Page 244 Item Network requirements • Enable IGMPv2 on VLAN-interface 23 of CE a2. IGMP • Enable IGMPv2 on VLAN-interface 24 of CE b2. Enable PIM-SSM on the public network and PIM-SM on VPN instances a and b: • Enable PIM-SM on all interfaces of P 1 and P 2. •...
  • Page 245 Device Interface IP address Device Interface IP address Vlan-int2 10.1.1.2/24 Vlan-int6 10.5.1.1/24 Vlan-int3 10.2.1.1/24 Vlan-int5 10.4.1.2/24 Loop1 5.5.5.5/32 Loop1 6.6.6.6/32 CE a1 Vlan-int21 12.1.1.1/24 CE b1 Vlan-int22 12.2.1.1/24 CE a1 Vlan-int11 11.1.1.2/24 CE b1 Vlan-int12 11.2.1.2/24 CE a2 Vlan-int23 12.3.1.1/24 CE b2 Vlan-int24 12.4.1.1/24...
  • Page 246 [PE1-md-a-ipv4] default-group 232.1.1.1 [PE1-md-a-ipv4] source loopback 1 [PE1-md-a-ipv4] data-group 232.2.2.0 28 [PE1-md-a-ipv4] quit [PE1-md-a] quit # Create a VPN instance named b, and configure the RD and route targets for VPN instance. [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 [PE1-vpn-instance-b] quit # Enable IP multicast routing for VPN instance b.
  • Page 247 [PE1-Vlan-interface12] pim sm [PE1-Vlan-interface12] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [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-default] peer 2.2.2.2 as-number 100 [PE1-bgp-default] peer 2.2.2.2 connect-interface loopback 1 [PE1–bgp-default] ip vpn-instance a [PE1-bgp-default-a] address-family ipv4...
  • Page 248 # Configure a global router ID, and enable IP multicast routing on the public network. <PE2> system-view [PE2] router id 2.2.2.2 [PE2] multicast routing [PE2-mrib] quit # Configure an LSR ID, and enable LDP globally. [PE2] mpls lsr-id 2.2.2.2 [PE2] mpls ldp [PE2-ldp] quit # Assign an IP address to VLAN-interface 3.
  • Page 249 [PE2-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit Configure PE 3: # Configure a global router ID, and enable IP multicast routing on the public network. <PE3> system-view [PE3] router id 3.3.3.3 [PE3] multicast routing [PE3-mrib] quit # Configure an LSR ID, and enable LDP globally. [PE3] mpls lsr-id 3.3.3.3 [PE3] mpls ldp [PE3-ldp] quit...
  • Page 250 [PE3–bgp-default] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 10.4.1.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit Configure PE 4: # Configure a global router ID, and enable IP multicast routing on the public network. <PE4>...
  • Page 251 # Create a VPN instance named b, and configure the RD and route targets for the VPN instance. [PE4] ip vpn-instance b [PE4-vpn-instance-b] route-distinguisher 200:1 [PE4-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE4-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE4-vpn-instance-b] quit # Enable IP multicast routing for VPN instance b. [PE4] multicast routing vpn-instance b # Enable the RPF vector feature.
  • Page 252 [PE4-LoopBack1] pim sm [PE4-LoopBack1] quit # Configure BGP. [PE4] bgp 200 [PE4-bgp-default] peer 3.3.3.3 as-number 200 [PE4-bgp-default] peer 3.3.3.3 connect-interface loopback 1 [PE4–bgp-default] ip vpn-instance a [PE4-bgp-default-a] address-family ipv4 [PE4-bgp-default-ipv4-a] import-route ospf 2 [PE4-bgp-default-ipv4-a] import-route direct [PE4-bgp-default-ipv4-a] quit [PE4-bgp-default-a] quit [PE4–bgp-default] ip vpn-instance b [PE4-bgp-default-b] address-family ipv4 [PE4-bgp-default-ipv4-b] import-route ospf 3...
  • Page 253 [P1] mpls lsr-id 5.5.5.5 [P1] mpls ldp [P1-ldp] quit # Assign an IP address to VLAN-interface 2. [P1] interface vlan-interface 2 [P1-Vlan-interface2] ip address 10.1.1.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 2. [P1-Vlan-interface2] pim sm [P1-Vlan-interface2] mpls enable [P1-Vlan-interface2] mpls ldp enable [P1-Vlan-interface2] quit # Assign an IP address to VLAN-interface 3.
  • Page 254 # Assign an IP address to VLAN-interface 5. [P2] interface vlan-interface 5 [P2-Vlan-interface5] ip address 10.4.1.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 5. [P2-Vlan-interface5] pim sm [P2-Vlan-interface5] mpls enable [P2-Vlan-interface5] mpls ldp enable [P2-Vlan-interface5] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [P2] interface loopback 1 [P2-LoopBack1] ip address 6.6.6.6 32 [P2-LoopBack1] pim sm...
  • Page 255 # Enable IP multicast routing. <CEb1> system-view [CEb1] multicast routing [CEb1-mrib] quit # Assign an IP address to VLAN-interface 22, and enable PIM-SM on the interface. [CEb1] interface vlan-interface 22 [CEb1-Vlan-interface22] ip address 12.2.1.1 24 [CEb1-Vlan-interface22] pim sm [CEb1-Vlan-interface22] quit # Assign an IP address to VLAN-interface 12, and enable PIM-SM on the interface.
  • Page 256 10. Configure CE b2: # Enable IP multicast routing. <CEb2> system-view [CEb2] multicast routing [CEb2-mrib] quit # Assign an IP address to VLAN-interface 24, and enable IGMP on the interface. [CEb2] interface vlan-interface 24 [CEb2-Vlan-interface24] ip address 12.4.1.1 24 [CEb2-Vlan-interface24] igmp enable [CEb2-Vlan-interface24] quit # Assign an IP address to VLAN-interface 14, and enable PIM-SM on the interface.

  • Page 257: Md Vpn Inter-As Option C Configuration Example

    MD remote default-group information: Group address Source address Next hop VPN instance 232.1.1.1 1.1.1.1 3.3.3.3 232.3.3.3 1.1.1.1 3.3.3.3 MD VPN inter-AS option C configuration example Network requirements As shown in Figure 80, configure MD VPN inter-AS option C to meet the following requirements: Item Network requirements •...
  • Page 258 Figure 80 Network diagram Loop0 Loop0 CE a1 CE b2 Vlan-int10 Vlan-int40 VPN a VPN b Vlan-int2 Vlan-int4 Vlan-int3 GE1/0/4 GE1/0/4 Vlan-int3 Vlan-int4 PE 1 PE 4 Vlan-int2 GE1/0/4 GE1/0/4 PE 2 PE 3 ASBR ASBR AS 100 AS 200 Vlan-int20 Vlan-int30 Service loopback port...
  • Page 259 [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE1] service-loopback group 1 type multicast-tunnel # Assign GigabitEthernet 1/0/4 to service loopback group 1. The interface does not belong to VLAN 2, VLAN 11, or VLAN 12.
  • Page 260 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b. [PE1-md-b-ipv4] default-group 239.4.4.4 [PE1-md-b-ipv4] source loopback 1 [PE1-md-b-ivp4] data-group 225.4.4.0 28 [PE1-md-b-ipv4] quit [PE1-md-b] quit # Assign an IP address to VLAN-interface 2. [PE1] interface vlan-interface 2 [PE1-Vlan-interface2] ip address 10.10.1.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 2.
  • Page 261 [PE1-bgp-default-ipv4-a] quit [PE1-bgp-default-a] quit [PE1–bgp-default] ip vpn-instance b [PE1-bgp-default-b] address-family ipv4 [PE1-bgp-default-ipv4-b] import-route ospf 3 [PE1-bgp-default-ipv4-b] import-route direct [PE1-bgp-default-ipv4-b] quit [PE1-bgp-default-b] quit [PE1–bgp-default] address-family ipv4 [PE1-bgp-default-ipv4] peer pe1-pe2 enable [PE1-bgp-default-ipv4] peer pe1-pe2 label-route-capability [PE1-bgp-default-ipv4] quit [PE1–bgp-default] address-family vpnv4 [PE1–bgp-default-vpnv4] peer pe1-pe4 enable [PE1–bgp-default-vpnv4] quit [PE1–bgp-default] quit # Configure OSPF.
  • Page 262 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 2. [PE2-Vlan-interface2] pim sm [PE2-Vlan-interface2] mpls enable [PE2-Vlan-interface2] mpls ldp enable [PE2-Vlan-interface2] quit # Assign an IP address to VLAN-interface 3. [PE2] interface vlan-interface 3 [PE2-Vlan-interface3] ip address 192.168.1.1 24 # Enable PIM-SM and MPLS on VLAN-interface 3. [PE2-Vlan-interface3] pim sm [PE2-Vlan-interface3] mpls enable [PE2-Vlan-interface3] quit...
  • Page 263 [PE2-bgp-default-ipv4] peer pe2-pe1 route-policy map2 export [PE2-bgp-default-ipv4] peer pe2-pe1 label-route-capability [PE2-bgp-default-ipv4] peer pe2-pe3 enable [PE2-bgp-default-ipv4] peer pe2-pe3 route-policy map1 export [PE2-bgp-default-ipv4] peer pe2-pe3 label-route-capability [PE2-bgp-default-ipv4] import-route ospf 1 [PE2-bgp-default-ipv4] quit [PE2–bgp-default] 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 [PE2-ospf-1-area-0.0.0.0] network 11.11.11.11 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 10.10.1.0 0.0.0.255...
  • Page 264 [PE3] interface loopback 2 [PE3-LoopBack2] ip address 22.22.22.22 32 [PE3-LoopBack2] pim sm [PE3-LoopBack2] quit # Configure Loopback 2 as a C-BSR and a C-RP. [PE3] pim [PE3-pim] c-bsr 22.22.22.22 [PE3-pim] c-rp 22.22.22.22 [PE3-pim] quit # Configure VLAN-interface 3 as a PIM-SM domain border. [PE3] interface vlan-interface 3 [PE3-Vlan-interface3] pim bsr-boundary [PE3-Vlan-interface3] quit...
  • Page 265 <PE4> system-view [PE4] router id 1.1.1.4 [PE4] multicast routing [PE4-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE4] service-loopback group 1 type multicast-tunnel # Assign GigabitEthernet 1/0/4 to service loopback group 1. The interface does not belong to VLAN 4, VLAN 13, or VLAN 14.
  • Page 266 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b. [PE4-md-b-ipv4] default-group 239.4.4.4 [PE4-md-b-ipv4] source loopback 1 [PE4-md-b-ivp4] data-group 225.4.4.0 28 [PE4-md-b-ipv4] quit [PE4-md-b] quit # Assign an IP address to VLAN-interface 4. [PE4] interface vlan-interface 4 [PE4-Vlan-interface4] ip address 10.10.2.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 4.
  • Page 267 [PE4-bgp-default-ipv4-a] quit [PE4-bgp-default-a] quit [PE4–bgp-default] ip vpn-instance b [PE4-bgp-default-b] address-family ipv4 [PE4-bgp-default-ipv4-b] import-route ospf 3 [PE4-bgp-default-ipv4-b] import-route direct [PE4-bgp-default-ipv4-b] quit [PE4-bgp-default-b] quit [PE4–bgp-default] address-family ipv4 [PE4-bgp-default-ipv4] peer pe4-pe3 enable [PE4-bgp-default-ipv4] peer pe4-pe3 label-route-capability [PE4-bgp-default-ipv4] quit [PE4–bgp-default] address-family vpnv4 [PE4–bgp-default-vpnv4] peer pe4-pe1 enable [PE4–bgp-default-vpnv4] quit [PE4–bgp-default] quit # Configure OSPF.
  • Page 268 [CEa1-Vlan-interface11] pim sm [CEa1-Vlan-interface11] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [CEa1] interface loopback 1 [CEa1-LoopBack1] ip address 2.2.2.2 32 [CEa1-LoopBack1] pim sm [CEa1-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP. [CEa1] pim [CEa1-pim] c-bsr 2.2.2.2 [CEa1-pim] c-rp 2.2.2.2...
  • Page 269 # Assign an IP address to VLAN-interface 30, and enable IGMP on the interface. [CEa2] interface vlan-interface 30 [CEa2-Vlan-interface30] ip address 10.11.7.1 24 [CEa2-Vlan-interface30] igmp enable [CEa2-Vlan-interface30] quit # Assign an IP address to VLAN-interface 13, and enable PIM-SM on the interface. [CEa2] interface vlan-interface 13 [CEa2-Vlan-interface13] ip address 10.11.3.2 24 [CEa2-Vlan-interface13] pim sm...

  • Page 270: Troubleshooting Md Vpn

    [CEb2-ospf-1-area-0.0.0.0] quit [CEb2-ospf-1] quit Verifying the configuration # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 1. [PE1] display multicast-domain default-group local MD local default-group information: Group address Source address Interface VPN instance 239.1.1.1 1.1.1.1 MTunnel0...
  • Page 271 Solution To resolve the problem: Use the display pim bsr-info command to verify that the BSR information exists on the public network and VPN instance. If it does not, verify that a unicast route exists to the BSR. Use the display pim rp-info command to examine the RP information. If no RP information is available, verify that a unicast route exists to the RP.

  • Page 272: Configuring Mld Snooping

    Configuring MLD snooping Overview MLD snooping runs on a Layer 2 device as an IPv6 multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from MLD messages that are exchanged between the hosts and the router. As shown in Figure 81, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...
  • Page 273 Figure 82 MLD snooping ports Receiver Router A Switch A GE1/0/1 GE1/0/2 Host A GE1/0/3 Host B Receiver GE1/0/1 Source GE1/0/2 Host C Switch B Router port Member port IPv6 multicast packets Host D Router ports On an MLD snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.

  • Page 274: How Mld Snooping Works

    How MLD snooping works The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." MLD messages include general query, MLD report, and done message. An MLD snooping-enabled Layer 2 device performs differently depending on the MLD message types. General query The MLD querier periodically sends MLD general queries to all hosts and routers on the local subnet to check for the existence of IPv6 multicast group members.

  • Page 275: Mld Snooping Proxying

    • If a match is found but the receiving port is not an outgoing interface in the forwarding entry, the Layer 2 device discards the MLD done message. • If a match is found and the receiving port is not the only outgoing interface in the forwarding entry, the Layer 2 device performs the following actions: Discards the MLD done message.

  • Page 276: Protocols And Standards

    The MLD snooping proxy device processes different MLD messages as follows: • General query. After receiving an MLD general query, the device forwards the query to all ports in the VLAN except the receiving port. The device also generates an MLD report based on the local membership information and sends the report to all router ports.

  • Page 277: Mld Snooping Configuration Task List

    MLD snooping configuration task list You can configure MLD snooping for VLANs or VSIs. MLD snooping configuration task list for VLANs Tasks at a glance Configuring basic MLD snooping features: • (Required.) Enabling MLD snooping • (Optional.) Specifying an MLD snooping version •...

  • Page 278: Configuring Basic Mld Snooping Features

    Tasks at a glance • (Optional.) Enabling the MLD snooping querier • (Optional.) Configuring parameters for MLD general queries and responses Configuring parameters for MLD messages: • (Optional.) Configuring source IPv6 addresses for MLD messages • (Optional.) Setting the 802.1p priority for MLD messages Configuring MLD snooping policies: •...

  • Page 279: Specifying An Mld Snooping Version

    Step Command Remarks • Enter VLAN view: vlan vlan-id Enter VLAN view or VSI • view. Enter VSI view: vsi vsi-name Enable MLD snooping for the By default, MLD snooping is mld-snooping enable VLAN or VSI. disabled in a VLAN or VSI. Specifying an MLD snooping version Different MLD snooping versions can process different versions of MLD messages: •...

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

    Setting the maximum number of MLD snooping forwarding entries You can modify the maximum number of MLD snooping forwarding entries, including dynamic entries and static entries. When the number of forwarding entries on the device reaches the upper limit, the device does not automatically remove any existing entries. To allow new entries to be created, remove some entries manually.

  • Page 281: Setting The Mld Last Listener Query Interval

    multicast MAC address mac-address vlan vlan-id MAC address entries exist. entry. Setting the MLD last listener query interval A receiver host starts a report delay timer for an IPv6 multicast group when it receives an MLD multicast-address-specific query for the group. This timer is set to a random value in the range of 0 to the maximum response time advertised in the query.

  • Page 282: Setting Aging Timers For Dynamic Ports

    • Determine the addresses of the IPv6 multicast group and IPv6 multicast source. Setting aging timers for dynamic ports When you set aging timers for dynamic ports, follow these restrictions and guidelines: • If the memberships of IPv6 multicast groups frequently change, set a relatively small value for the aging timer of the dynamic member ports.

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

    • Static member port—When you configure a port as a static member port for an IPv6 multicast group, all hosts attached to the port will receive IPv6 multicast data for the group. The static member port does not respond to MLD queries. When you complete or cancel this configuration, the port does not send an unsolicited report or done message.

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

    Configuration restrictions and guidelines When you enable fast-leave processing, follow these restrictions and guidelines: • Do not enable fast-leave processing on a port that has multiple receiver hosts attached in a VLAN. If fast-leave processing is enabled, the remaining receivers cannot receive IPv6 multicast data for a group after a receiver leaves that group.

  • Page 285: Configuring The Mld Snooping Querier

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

  • Page 286: Configuring Parameters For Mld General Queries And Responses

    Configuring parameters for MLD general queries and responses CAUTION: To avoid mistakenly deleting IPv6 multicast group members, make sure the MLD general query interval is greater than the maximum response time for MLD general queries. You can modify the MLD general query interval for a VLAN based on the actual network conditions. A receiver host starts a report delay timer for each IPv6 multicast group that it has joined when it receives an MLD general query.

  • Page 287: Configuring Parameters For Mld Messages

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable MLD snooping By default, MLD snooping mld-snooping proxy enable proxying for the VLAN. proxying is disabled for a VLAN. Configuring parameters for MLD messages This section describes how to configure parameters for MLD messages. Configuration prerequisites Before you configure parameters for MLD messages, complete the following tasks: •...
  • Page 288 • The IPv6 link-local address of the current VLAN interface if the MLD snooping querier does not receive an MLD general query. • FE80::02FF:FFFF:FE00:000 1 if the MLD snooping querier does not receive an MLD general query and the current VLAN interface does not have an IPv6 link-local address.

  • Page 289: Setting The 802.1P Priority For Mld Messages

    Step Command Remarks link-local address. By default, the source IPv6 address of MLD reports is the IPv6 link-local address of the Configure the source IPv6 mld-snooping report source-ip gateway interface for a VSI. If the address for MLD reports. ipv6-address gateway interface does not have an IPv6 link-local address, the source IPv6 address is...

  • Page 290: Configuring An Ipv6 Multicast Group Policy

    • Determine the maximum number of IPv6 multicast groups that a port can join. Configuring an IPv6 multicast group policy This feature enables the device to filter MLD reports by using an ACL that specifies the IPv6 multicast groups and the optional sources. It is used to control the IPv6 multicast groups that receiver hosts can join.

  • Page 291: Enabling Dropping Unknown Ipv6 Multicast Data

    port filtering globally. port filtering is disabled globally. Enabling IPv6 multicast source port filtering in interface view Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view. interface-number By default, IPv6 multicast source Enable IPv6 multicast source mld-snooping source-deny port filtering is disabled on the port filtering on the port.

  • Page 292: Enabling Mld Report Suppression

    IPv6 multicast data for the IPv6 multicast data is disabled, VLAN or VSI. and unknown IPv6 multicast data is flooded. Enabling MLD report suppression This feature enables the Layer 2 device to forward only the first MLD report for an IPv6 multicast group to its directly connected Layer 3 device.

  • Page 293: Enabling Host Tracking

    application. Without this feature, the device discards MLD reports for new groups, and the user cannot change to the new channel. Configuration restrictions and guidelines When you enable IPv6 multicast group replacement, follow these restrictions and guidelines: • This configuration takes effect only on the multicast groups that the port joins dynamically. •...

  • Page 294: Displaying And Maintaining Mld Snooping

    Displaying and maintaining MLD snooping Execute display commands in any view and reset commands in user view. Task Command (In standalone mode.) Display Layer display ipv6 l2-multicast fast-forwarding cache [ vlan vlan-id ] 2 IPv6 multicast fast forwarding [ ipv6-source-address | ipv6-group-address ] * [ slot slot-number ] entries.

  • Page 295: Mld Snooping Configuration Examples

    Task Command display mld-snooping router-port [ vlan vlan-id | vsi vsi-name ] (In IRF mode.) Display dynamic [ chassis chassis-number slot slot-number ] router port information. display mld-snooping static-group [ ipv6-group-address | (In standalone mode.) Display static ipv6-source-address ] * [ vlan vlan-id ] [ verbose ] [ slot MLD snooping group entries.
  • Page 296 Figure 84 Network diagram Receiver Host A Source Receiver GE1/0/4 GE1/0/2 GE1/0/1 GE1/0/1 GE1/0/3 1::2/64 2001::1/64 Switch A Host B GE1/0/2 1::1/64 Router A MLD querier Host C VLAN 100 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 84.

  • Page 297: Static Port Configuration Example (For Vlans)

    # Configure an IPv6 multicast group policy so that hosts in VLAN 100 can join only IPv6 multicast group FF1E::101. [SwitchA] acl ipv6 basic 2001 [SwitchA-acl-ipv6-basic-2001] rule permit source ff1e::101 128 [SwitchA-acl-ipv6-basic-2001] quit [SwitchA] mld-snooping [SwitchA–mld-snooping] group-policy 2001 vlan 100 [SwitchA–mld-snooping] quit # Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as simulated member hosts to join IPv6 multicast group FF1E::101.
  • Page 298 along the path of Switch A—Switch B—Switch C. When this path is blocked, a minimum of one MLD query-response cycle must be completed before IPv6 multicast data flows to the receivers along the path of Switch A—Switch C. In this case, the multicast delivery is interrupted during the process.
  • Page 299 [SwitchA-mld-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable MLD snooping for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] quit # Configure GigabitEthernet 1/0/3 as a static router port. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] mld-snooping static-router-port vlan 100 [SwitchA-GigabitEthernet1/0/3] quit...

  • Page 300: Mld Snooping Querier Configuration Example (For Vlans)

    Router slots (0 in total): Router ports (1 in total): GE1/0/3 The output shows that GigabitEthernet 1/0/3 on Switch A has become a static router port. # Display static MLD snooping group entries in VLAN 100 on Switch C. [SwitchC] display mld-snooping static-group vlan 100 Total 1 entries).
  • Page 301 Figure 86 Network diagram Source 1 Source 2 VLAN 100 1::10/64 1::20/64 Receiver Receiver GE1/0/2 GE1/0/2 GE1/0/1 GE1/0/3 GE1/0/3 GE1/0/1 Host A GE1/0/4 Host B Switch A Switch B Querier Receiver Receiver GE1/0/2 GE1/0/1 GE1/0/2 GE1/0/3 GE1/0/1 Host D Host C Switch D Switch C Configuration procedure...
  • Page 302 Configure Switch C: # Enable MLD snooping globally. <SwitchC> system-view [SwitchC] mld-snooping [SwitchC-mld-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 # Enable MLD snooping, and enable dropping unknown IPv6 multicast data for VLAN 100. [SwitchC-vlan100] mld-snooping enable [SwitchC-vlan100] mld-snooping drop-unknown [SwitchC-vlan100] quit...

  • Page 303: Mld Snooping Proxying Configuration Example (For Vlans)

    MLD snooping proxying configuration example (for VLANs) Network requirements As shown in Figure 87, Router A runs MLDv1 and acts as the MLD querier. Switch A runs MLDv1 snooping. Configure MLD snooping proxying so that Switch A can perform the following operations: •...

  • Page 304: Mld Snooping Configuration Example (For Vxlans)

    # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable MLD snooping and MLD snooping proxying for the VLAN. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] mld-snooping proxy enable [SwitchA-vlan100] quit Verifying the configuration # Send MLD reports from Host A and Host B to join IPv6 multicast group FF1E::101.
  • Page 305 Configure MLD snooping on the switches to implement IPv6 Layer 2 multicast forwarding and reduce the burden of replicating known multicast traffic for VTEPs in VXLAN 10. Figure 88 Network diagram Loop0 Loop0 Transport network Vlan-int11 Vlan-int11 Vlan-int13 Vlan-int13 GE1/0/1 GE1/0/1 VM 1 VM 3...
  • Page 306 # Assign an IP address to Loopback 0. This address will be used as the source address of the VXLAN tunnels to Switch B and Switch C. [SwitchA] interface loopback 0 [SwitchA-Loopback0] ip address 1.1.1.1 255.255.255.255 [SwitchA-Loopback0] quit # Create a VXLAN tunnel to Switch B. The tunnel interface name is Tunnel 1.
  • Page 307 # Enable MLD snooping globally. [SwitchB] mld-snooping [SwitchB -mld-snooping] quit # Enable MLD snooping and dropping unknown IPv6 multicast data packets for VSI vpna. [SwitchB] vsi vpna [SwitchB-vsi-vpna] mld-snooping enable [SwitchB-vsi-vpna] mld-snooping drop-unknown [SwitchB-vsi-vpna] quit # Assign an IP address to Loopback 0. This address will be used as the source address of the VXLAN tunnels to Switch A and Switch C.
  • Page 308 # Enable L2VPN. <SwitchC> system-view [SwitchC] l2vpn enable # Create a VSI named vpna, and create VXLAN 10. [SwitchC] vsi vpna [SwitchC-vsi-vpna] vxlan 10 [SwitchC-vsi-vpna-vxlan-10] quit [SwitchC-vsi-vpna] quit # Enable MLD snooping globally. [SwitchB] mld-snooping [SwitchB -mld-snooping] quit # Enable MLD snooping for VSI vpna. [SwitchC] vsi vpna [SwitchC-vsi-vpna] mld-snooping enable # Enable dropping unknown IPv6 multicast data packets for VSI vpna.

  • Page 309: Troubleshooting Mld Snooping

    [SwitchC-vsi-vpna] quit # Configure GigabitEthernet 1/0/1 as a trunk port and assign it to VLAN 2. [SwitchC] interface gigabitethernet 1/0/1 [SwitchC-GigabitEthernet1/0/1] port link-type trunk [SwitchC-GigabitEthernet1/0/1] port trunk permit vlan 2 # On GigabitEthernet 1/0/1, create Ethernet service instance 1000 to map VLAN 2. [SwitchC-GigabitEthernet1/0/1] service-instance 1000 [SwitchC-GigabitEthernet1/0/1-srv1000] encapsulation s-vid 2 # Map Ethernet service instance 1000 to VSI vpna.

  • Page 310: Ipv6 Multicast Group Policy Does Not Work

    IPv6 multicast group policy does not work Symptom Hosts can receive IPv6 multicast data for IPv6 multicast groups that are not permitted by the IPv6 multicast group policy. Solution To resolve the problem: Use the display acl ipv6 command to verify that the configured IPv6 ACL meets the IPv6 multicast group policy requirements.

  • Page 311: Configuring Ipv6 Pim Snooping

    Configuring IPv6 PIM snooping Overview IPv6 PIM snooping runs on Layer 2 devices. It works with MLD snooping to analyze received IPv6 PIM messages, and adds the ports that are interested in specific multicast data to an IPv6 PIM snooping routing entry. In this way, the multicast data can be forwarded to only the ports that are interested in the data.

  • Page 312: Configuring Ipv6 Pim Snooping

    b. Floods all other types of received IPv6 PIM messages except PIM hello messages in the VLAN or VSI. c. Forwards all multicast data to all router ports in the VLAN or VSI. Each IPv6 PIM-capable router in the VLAN, whether interested in the multicast data or not, can receive all multicast data and all IPv6 PIM messages except IPv6 PIM hello messages.

  • Page 313: Displaying And Maintaining Ipv6 Pim Snooping

    Step Command Remarks active/standby switchover. 2 aggregate interface or AC interface that acts as a neighbor port. The default setting is 210 (Optional.) Set the aging seconds. time for global ipv6 pim-snooping A global downstream port or a downstream ports and graceful-restart join-aging-time global router port is a Layer 2 global router ports on the...

  • Page 314: Configuration Procedure

    • Receiver 1 and Receiver 2 belong to IPv6 multicast groups FF1E::101 and FF2E::101, respectively. • Router C and Router D run MLD on GigabitEthernet 1/0/1. • Router A, Router B, Router C, and Router D run IPv6 PIM-SM. GigabitEthernet 1/0/2 on Router A acts as a C-BSR and a C-RP.
  • Page 315 <RouterB> system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable IPv6 PIM-SM on each interface. [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] ipv6 pim sm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] ipv6 pim sm [RouterB-GigabitEthernet1/0/2] quit Configure Router C: # Enable IPv6 multicast routing. <RouterC>...

  • Page 316: Verifying The Configuration

    [SwitchA-vlan100] ipv6 pim-snooping enable [SwitchA-vlan100] quit Verifying the configuration # On Switch A, display IPv6 PIM snooping neighbor information for VLAN 100. [SwitchA] display ipv6 pim-snooping neighbor vlan 100 Total 4 neighbors. VLAN 100: Total 4 neighbors. FE80::1 Slots (0 in total): Ports (1 in total): GE1/0/1 (00:32:43)

  • Page 317: Troubleshooting Ipv6 Pim Snooping

    Downstream Slots (0 in total): Downstream ports (1 in total): GE1/0/4 Expires: 00:03:01, FSM: J The output shows the following information: • Switch A will forward the multicast data intended for IPv6 multicast group FF1E::101 to only Router C. • Switch A will forward the multicast data intended for IPv6 multicast group FF2E::101 to only Router D.

  • Page 318: Configuring Ipv6 Multicast Vlans

    Configuring IPv6 multicast VLANs Overview As shown in Figure 91, Host A, Host B, and Host C are in different VLANs and the same IPv6 multicast group. When Switch A (Layer 3 device) receives IPv6 multicast data for that group, it forwards three copies of the data to Switch B (Layer 2 device).
  • Page 319 Figure 92 Sub-VLAN-based multicast VLAN IPv6 Multicast packets VLAN 10 (IPv6 Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Source Switch A Switch B MLD querier VLAN 4 Receiver Host C MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in each sub-VLAN.

  • Page 320: Ipv6 Multicast Vlan Configuration Task List

    IPv6 multicast VLAN configuration task list Tasks at a glance (Required.) Perform one of the following tasks: • Configuring a sub-VLAN-based IPv6 multicast VLAN • Configuring a port-based IPv6 multicast VLAN: Configuring user port attributes  Assigning user ports to an IPv6 multicast VLAN ...

  • Page 321: Configuration Procedure

    Configuration procedure To configure a sub-VLAN-based IPv6 multicast VLAN: Step Command Remarks Enter system view. system-view Configure a VLAN as an ipv6 multicast-vlan By default, a VLAN is not an IPv6 IPv6 multicast VLAN and vlan-id multicast VLAN. enter its view. Assign the specified VLANs By default, an IPv6 multicast VLAN does to the IPv6 multicast VLAN...

  • Page 322: Assigning User Ports To An Ipv6 Multicast Vlan

    Assigning user ports to an IPv6 multicast VLAN You can assign user ports to an IPv6 multicast VLAN in IPv6 multicast VLAN view or assign a user port to an IPv6 multicast VLAN in interface view. Configuration restrictions and guidelines When you perform this task, follow these restrictions and guidelines: •...

  • Page 323: Displaying And Maintaining Ipv6 Multicast Vlans

    Step Command Remarks Set the maximum number of By default, the maximum number ipv6 multicast-vlan entry-limit IPv6 multicast VLAN of IPv6 multicast VLAN limit forwarding entries. forwarding entries is 8192. Displaying and maintaining IPv6 multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about IPv6...
  • Page 324 Figure 94 Network diagram Source MLD querier GE1/0/2 Vlan-int20 Switch A 1::2/64 GE1/0/1 1::1/64 Vlan-int10 2001::1/64 GE1/0/1 Switch B GE1/0/2 GE1/0/4 GE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure Switch A: # Enable IPv6 multicast routing.
  • Page 325 Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 2, assign GigabitEthernet 1/0/2 to the VLAN, and enable MLD snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port gigabitethernet 1/0/2 [SwitchB-vlan2] mld-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign GigabitEthernet 1/0/3 to the VLAN, and enable MLD snooping for the VLAN.

  • Page 326: Port-Based Ipv6 Multicast Vlan Configuration Example

    [SwitchB] display ipv6 multicast-vlan group Total 1 entries. IPv6 multicast VLAN 10: Total 1 entries. (::, FF1E::101) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that IPv6 multicast group FF1E::101 belongs to IPv6 multicast VLAN 10. IPv6 multicast VLAN 10 contains sub-VLANs VLAN 2 through VLAN 4.
  • Page 327 [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Create VLAN 20, and assign GigabitEthernet 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port gigabitethernet 1/0/2 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 1::2 64 [SwitchA-Vlan-interface20] ipv6 pim dm...
  • Page 328 # Assign GigabitEthernet 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 2 untagged [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 10 untagged [SwitchB-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 as a hybrid port, and configure VLAN 3 as the PVID of the hybrid port.
  • Page 329 (::, FF1E::101) Host slots (0 in total): Host ports (3 in total): GE1/0/2 (00:03:23) GE1/0/3 (00:04:07) GE1/0/4 (00:04:16) The output shows that MLD snooping maintains the user ports in the multicast VLAN (VLAN 10). Switch B will forward the IPv6 multicast data of VLAN 10 through these user ports.

  • Page 330: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding Overview IPv6 multicast routing and forwarding uses the following tables: • IPv6 multicast protocols' routing tables, such as the IPv6 PIM routing table. • General IPv6 multicast routing table that summarizes the multicast routing information generated by different IPv6 multicast routing protocols.
  • Page 331 the incoming interface of the (S, G) entry. After the router receives another (S, G) packet, it looks up its IPv6 multicast forwarding table for a matching (S, G) entry: • If no match is found, the router first determines the RPF route back to the packet source. Then, it creates a forwarding entry with the RPF interface as the incoming interface and performs one of the following tasks: If the receiving interface is the RPF interface, the RPF check succeeds and the router...

  • Page 332: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

    IPv6 multicast forwarding across IPv6 unicast subnets Routers forward the IPv6 multicast data from an IPv6 multicast source hop by hop along the forwarding tree, but some routers might not support IPv6 multicast protocols in a network. When the IPv6 multicast data is forwarded to a router that does not support IPv6 multicast, the forwarding path is blocked.

  • Page 333: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding Before you configure IPv6 multicast routing and forwarding, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Configure IPv6 PIM-DM or IPv6 PIM-SM. Specifying the longest prefix match principle You can enable the device to use the longest prefix match principle for RPF route selection.

  • Page 334: Enabling Ipv6 Multicast Forwarding Between Sub-Vlans Of A Super Vlan

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number ipv6 multicast boundary By default, an interface is not an { ipv6-group-address prefix-length Configure an IPv6 multicast IPv6 multicast forwarding | scope { scope-id | admin-local | forwarding boundary.
  • Page 335 Task Command Display information about the interfaces display ipv6 mrib [ vpn-instance vpn-instance-name ] maintained by the IPv6 MRIB. interface [ interface-type interface-number ] display ipv6 multicast [ vpn-instance vpn-instance-name ] boundary { group [ ipv6-group-address [ prefix-length ] ] | Display IPv6 multicast boundary scope [ scope-id ] } [ interface interface-type information.

  • Page 336: Ipv6 Multicast Routing And Forwarding Configuration Example

    Task Command ipv6-group-address } * | all } [ slot slot-number ] reset ipv6 multicast [ vpn-instance vpn-instance-name ] (In IRF mode.) Clear IPv6 multicast fast fast-forwarding cache { { ipv6-source-address | forwarding entries. ipv6-group-address } * | all } [ chassis chassis-number slot slot-number ] reset ipv6 multicast [ vpn-instance vpn-instance-name ] forwarding-table { { ipv6-source-address [ prefix-length ] |...

  • Page 337: Configuration Procedure

    Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 98. (Details not shown.) Configure OSPFv3 on the switches. Do not run OSPFv3 on VLAN-interface 100 on Switch A. (Details not shown.) Configure a GRE tunnel: # On Switch A, create service loopback group 1, and specify the unicast tunnel service for the group.

  • Page 338: Verifying The Configuration

    [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim dm [SwitchA-Vlan-interface101] quit [SwitchA] interface tunnel 1 [SwitchA-Tunnel1] ipv6 pim dm [SwitchA-Tunnel1] quit # On Switch C, enable IPv6 multicast routing. [SwitchC] ipv6 multicast routing [SwitchC-mrib6] quit # Enable MLD on the receiver-side interface (VLAN-interface 200). [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] mld enable [SwitchC-Vlan-interface200] quit...
  • Page 339 RPF prime neighbor: FE80::A01:101:1 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: pim-dm, UpTime: 00:04:25, Expires: - The output shows the following information: • Switch A is the RPF neighbor of Switch C. • IPv6 multicast data from Switch A is delivered over the GRE tunnel to Switch C.

  • Page 340: Configuring Mld

    Configuring MLD Overview Multicast Listener Discovery (MLD) establishes and maintains IPv6 multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. MLD has the following versions: • MLDv1 (defined by RFC 2710), which is derived from IGMPv2. •...
  • Page 341 Joining an IPv6 multicast group Figure 99 MLD queries and reports IPv6 network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report As shown in Figure 99, Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1.

  • Page 342: Mldv2 Enhancements

    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 IPv6 multicast addresses queried include both the destination address field and the group address field of the message.

  • Page 343: Mld Ssm Mapping

    • Filter mode—Router keeps tracing the Include or Exclude state. • List of sources—Router keeps tracing the newly added or deleted IPv6 multicast source. • Timers—Filter timers, which include the time that the router waits before switching to the Include mode after an IPv6 multicast address times out, and source timers for source recording. MLD SSM mapping An MLDv2 host can explicitly specify multicast sources in its MLDv2 reports.

  • Page 344: Mld Proxying

    MLD proxying As shown in Figure 102, in a simple tree-shaped topology, it is not necessary to configure IPv6 multicast routing protocols, such as IPv6 PIM, on edge devices. Instead, you can configure MLD proxying on these devices. With MLD proxying configured, the edge device acts as an MLD proxy: •...

  • Page 345: Mld Configuration Task List

    • RFC 3810, Multicast Listener Discovery Version 2 (MLDv2) for IPv6 MLD configuration task list Tasks at a glance Configuring basic MLD features: • (Required.) Enabling MLD • (Optional.) Specifying an MLD version • (Optional.) Configuring a static group member •...

  • Page 346: Specifying An Mld Version

    Step Command Remarks Enable MLD. mld enable By default, MLD is disabled. Specifying an MLD version For MLD to operate correctly, specify the same MLD version for all routers on the same subnet. To specify an MLD version: Step Command Remarks Enter system view.

  • Page 347: Adjusting Mld Performance

    To configure an IPv6 multicast group policy: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no IPv6 multicast mld group-policy group policy exists on an Configure an IPv6 multicast ipv6-acl-number interface. Hosts attached to the group policy.
  • Page 348 • You can configure the MLD query and response parameters globally for all interfaces in MLD view or for an interface in interface view. For an interface, the interface-specific configuration takes priority over the global configuration. • To avoid frequent MLD querier changes, set the MLD other querier present timer greater than the MLD general query interval.

  • Page 349: Enabling Fast-Leave Processing

    Step Command Remarks robustness variable. robustness variable is 2. By default, the MLD startup query Set the MLD startup query mld startup-query-interval interval equals one quarter of the interval. interval MLD general query interval. By default, the MLD startup query Set the MLD startup query mld startup-query-count count count equals the MLD querier's...

  • Page 350: Configuration Prerequisites

    Configuration prerequisites Before you configure MLD SSM mappings, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Configure basic MLD features. Configuration procedure To configure an MLD SSM mapping: Step Command Remarks...

  • Page 351: Enabling Ipv6 Multicast Forwarding On A Non-Querier Interface

    Step Command Remarks Return to system view. quit interface interface-type Enter interface view. interface-number By default, MLD proxying is Enable MLD proxying. mld proxy enable disabled. Enabling IPv6 multicast forwarding on a non-querier interface Typically, only MLD queriers can forward IPv6 multicast traffic and non-queriers cannot. This prevents IPv6 multicast data from being repeatedly forwarded.

  • Page 352: Enabling Mld Nsr

    Enabling MLD NSR This feature backs up information about MLD interfaces and MLD multicast groups to the standby process. The device recovers the information without cooperation of other devices when an active/standby switchover occurs. Use this feature to prevent an active/standby switchover from affecting the IPv6 multicast service.
  • Page 353 • OSPFv3 and IPv6 PIM-DM run on the network. • VOD streams are sent to receiver hosts in multicast. Receiver hosts of different organizations form stub networks N1 and N2. Host A and Host C are multicast receiver hosts in N1 and N2, respectively.
  • Page 354 [SwitchA-Vlan-interface101] quit # On Switch B, enable IPv6 multicast routing. <SwitchB> system-view [SwitchB] ipv6 multicast routing [SwitchB-mrib6] quit # Enable MLD on VLAN-interface 200. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] mld enable [SwitchB-Vlan-interface200] quit # Enable IPv6 PIM-DM on VLAN-interface 201. [SwitchB] interface vlan-interface 201 [SwitchB-Vlan-interface201] ipv6 pim dm [SwitchB-Vlan-interface201] quit...

  • Page 355: Mld Ssm Mapping Configuration Example

    MLD SSM mapping configuration example Network requirements As shown in Figure 104: • OSPFv3 runs on the network. • The IPv6 PIM-SM domain uses both the ASM model and SSM model for IPv6 multicast delivery. VLAN-interface 104 of Router D acts as the C-BSR and C-RP. The SSM group range is FF3E::/64.
  • Page 356 # On Switch D, enable IPv6 multicast routing. <SwitchD> system-view [SwitchD] ipv6 multicast routing [SwitchD-mrib6] quit # Enable MLDv2 on the receiver-side interface (VLAN-interface 400). [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] mld enable [SwitchD-Vlan-interface400] mld version 2 [SwitchD-Vlan-interface400] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] ipv6 pim sm [SwitchD-Vlan-interface103] quit...

  • Page 357: Mld Proxying Configuration Example

    [SwitchD-mld] ssm-mapping 1001::1 2000 [SwitchD-mld] ssm-mapping 3001::1 2000 [SwitchD-mld] quit Verifying the configuration # Display MLD SSM mappings for IPv6 multicast group FF3E::101 on Switch D. [SwitchD] display mld ssm-mapping ff3e::101 Group: FF3E::101 Source list: 1001::1 3001::1 # On Switch D, display information about MLD multicast groups that hosts have dynamically joined. [SwitchD] display mld group MLD groups in total: 1 Vlan-interface400(FE80::101):...
  • Page 358 • IPv6 PIM-DM runs on the core network. • Host A and Host C on the stub network receive VOD information destined to IPv6 multicast group FF3E::101. Configure the MLD proxying feature on Switch B so that Switch B can maintain group memberships and forward IPv6 multicast traffic without running IPv6 PIM-DM.

  • Page 359: Troubleshooting Mld

    [SwitchB-Vlan-interface200] quit Verifying the configuration # Display IPv6 multicast group membership information maintained by the MLD proxy on Switch B. [SwitchB] display mld proxy group MLD proxy group records in total: 1 Vlan-interface100(FE80::16:1): MLD proxy group records in total: 1 Group address: FF3E::101 Member state: Delay Expires: 00:00:02...

  • Page 360: Configuring Ipv6 Pim

    Configuring IPv6 PIM Overview IPv6 Protocol Independent Multicast (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, IPv6 IS-IS, or IPv6 BGP. IPv6 PIM uses the underlying IPv6 unicast routing to generate an IPv6 multicast routing table without relying on any particular IPv6 unicast routing protocol.
  • Page 361 The nodes without downstream receivers are pruned. A router that has no downstream receivers multicasts a prune message to all IPv6 PIM routers on the subnet. When the upstream node receives the prune message, it removes the receiving interface from the (S, G) entry.

  • Page 362: Ipv6 Pim-Sm Overview

    Figure 107 Assert mechanism Router A Router B Ethernet Assert message IPv6 multicast packets Receiver Router C As shown in Figure 107, 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.
  • Page 363 IMPORTANT: MLD must be enabled on the device that acts as the receiver-side DR. Otherwise, the receiver hosts attached to the DR cannot join any IPv6 multicast groups. For more information about MLD, see "Configuring MLD." Figure 108 DR election Receiver Source Receiver...
  • Page 364 As shown in Figure 109, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the IPv6 multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between IPv6 multicast groups and RPs.
  • Page 365 multicast source registers with the closest RP or a receiver-side DR joins the closest RP to implement source information synchronization. Anycast RP has the following benefits: • Optimal RP path—An IPv6 multicast source registers with the closest RP to build an optimal SPT.
  • Page 366 RPT building Figure 111 RPT building in an IPv6 PIM-SM domain Host A Source Receiver Host B Server Receiver Join message IPv6 multicast packets Host C As shown in Figure 111, the process of building an RPT is as follows: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the receiver-side DR.
  • Page 367 Figure 112 IPv6 multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C IPv6 multicast packets As shown in Figure 112, the IPv6 multicast source registers with the RP as follows: The IPv6 multicast source S sends the first multicast packet to the IPv6 multicast group G. When receiving the multicast packet, the source-side DR that directly connects to the IPv6 multicast source encapsulates the packet into a register message and unicasts the message to the RP.

  • Page 368: Ipv6 Bidir-Pim Overview

    When the RP receives the first IPv6 multicast packet, it sends an (S, G) source-specific join message toward the IPv6 multicast source. The routers along the path from the RP to the IPv6 multicast source constitute an SPT branch. The subsequent IPv6 multicast data is forwarded to the RP along the SPT without being encapsulated into register messages.
  • Page 369 DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, IPv6 BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF on each subnet. Only the DFs can forward IPv6 multicast data to the RP. DF election is not necessary for an RPL.
  • Page 370 Figure 114 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT IPv6 Multicast packets Host C As shown in Figure 114, the process for building a receiver-side RPT is the same as the process for building an RPT in IPv6 PIM-SM: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the directly connected router.

  • Page 371: Ipv6 Administrative Scoping Overview

    Figure 115 RPT building at the IPv6 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 115, the process for building a source-side RPT is relatively simple: When an IPv6 multicast source sends multicast packets to the IPv6 multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
  • Page 372 BSMs, of these IPv6 multicast groups cannot cross the boundary of the IPv6 admin-scoped zone for the group range. The IPv6 multicast group ranges to which different IPv6 admin-scoped zones are designated can have intersections. However, the IPv6 multicast groups in an IPv6 admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded as private group addresses.

  • Page 373: Ipv6 Pim-Ssm Overview

    Figure 117 IPv6 multicast address format 0xFF Flags Scope Group ID (112 bits) An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone.

  • Page 374: Relationship Among Ipv6 Pim Protocols

    SPT building The decision to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver host joins is in the IPv6 SSM group range. The IPv6 SSM group range reserved by IANA is FF3x::/32, where "x" represents any legal address scope. Figure 118 SPT building in IPv6 PIM-SSM Host A Source...

  • Page 375: Ipv6 Pim Support For Vpns

    Figure 119 Relationship among IPv6 PIM protocols A receiver joins IPv6 multicast group G. G is in the IPv6 An IPv6 multicast source is SSM group range? specified? IPv6 BIDIR-PIM is enabled? An MLD-SSM mapping is configured for G? IPv6 PIM-SM runs for G. G has an IPv6 BIDIR-PIM IPv6 PIM-SSM runs for G.

  • Page 376: Ipv6 Pim-Dm Configuration Task List

    IPv6 PIM-DM configuration task list Tasks at a glance (Required.) Enabling IPv6 PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring IPv6 PIM-DM graft retry timer (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-DM, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer.

  • Page 377: Configuring State Refresh Parameters

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the state refresh By default, the state refresh ipv6 pim state-refresh-capable feature. feature is enabled. Configuring state refresh parameters The state refresh interval determines the interval at which a router sends state refresh messages. It is configurable.

  • Page 378: Configuring Ipv6 Pim-Sm

    For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring common IPv6 PIM timers." Configuring IPv6 PIM-SM This section describes how to configure IPv6 PIM-SM. IPv6 PIM-SM configuration task list Tasks at a glance Remarks (Required.) Enabling IPv6 PIM-SM (Required.) Configuring an...

  • Page 379: Configuring An Rp

    Step Command Remarks vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM. ipv6 pim sm disabled. Configuring an RP An RP can provide services for multiple or all IPv6 multicast groups. However, only one RP at a time can forward IPv6 multicast traffic for an IPv6 multicast group.
  • Page 380 The device might use the BSR RP hash algorithm described in RFC 4601 or in RFC 2362 to calculate the RP for a multicast group. To ensure consistent group-to-RP mappings on all PIM routers in the IPv6 PIM-SM domain, specify the same BSR RP hash algorithm on the routers. To configure a C-RP: Step Command...

  • Page 381: Configuring A Bsr

    Step Command Remarks add multiple RP member addresses to an Anycast RP set. Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP. You do not need to configure a BSR when you have configured only a static RP but no C-RPs. An IPv6 PIM-SM domain can have only one BSR, but must have a minimum of one C-BSR.
  • Page 382 Step Command Remarks regarded as legal. Configuring an IPv6 PIM domain border An IPv6 PIM domain border determines the transmission boundary of bootstrap messages. Bootstrap messages cannot cross the domain border in either direction. A number of IPv6 PIM domain border interfaces partition a network into different IPv6 PIM-SM domains. To configure an IPv6 PIM domain border: Step Command...

  • Page 383: Configuring Ipv6 Multicast Source Registration

    Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] Disable the device from By default, the device forwards forwarding BSMs out of their undo bsm-reflection enable BSMs out of their incoming incoming interfaces. interfaces. Configuring IPv6 multicast source registration An IPv6 PIM register policy enables an RP to filter register messages by using an ACL that specifies the IPv6 multicast sources and groups.

  • Page 384: Configuring The Switchover To Spt

    Step Command Remarks Configure the register register-suppression-timeout The default setting is 60 seconds. suppression time. interval Configuring the switchover to SPT Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] spt-switch-threshold By default, the first IPv6 multicast Configure the switchover to { immediacy | infinity } data packet triggers the RPT to...

  • Page 385: Configuration Prerequisites

    Tasks at a glance Remarks BSMs out of their incoming interfaces (Optional.) Configuring common IPv6 PIM features (Optional.) Enabling SNMP notifications for IPv6 PIM (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 BIDIR-PIM, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer.
  • Page 386 An RP can be manually configured or dynamically elected through the BSR mechanism. For a large-scaled IPv6 PIM network, configuring static RPs is a tedious job. Generally, static RPs are backups for dynamic RPs to enhance the robustness and operational manageability on an IPv6 multicast network.

  • Page 387: Configuring A Bsr

    Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-rp ipv6-address [ advertisement-interval Configure a C-RP to provide adv-interval | { group-policy By default, no C-RPs exist. services for IPv6 BIDIR-PIM. ipv6-acl-number | scope scope-id } | holdtime hold-time | priority priority ] * bidir (Optional.) Configure the By default, the device uses the...
  • Page 388 Configuring a C-BSR IMPORTANT: Because the BSR and other devices exchange a large amount of information in the IPv6 BIDIR-PIM domain, reserve a large bandwidth between the C-BSR and other devices. A BSR policy enables the router to filter BSR messages by using an ACL that specifies the legal BSR addresses.

  • Page 389: Configuring Ipv6 Pim-Ssm

    If the IPv6 BIDIR-PIM domain contains a device that does not support this feature, you must disable BSM semantic fragmentation on all C-BSRs. If you do not disable this feature, such a device regards a BSMF as an entire BSM and updates the RP-set information each time it receives a BSMF. It learns only part of the RP-set information, which further affects the RP election.

  • Page 390: Configuration Prerequisites

    Configuration prerequisites Before you configure IPv6 PIM-SSM, configure an IPv6 unicast IPv6 routing protocol so that all devices in the domain can interoperate at the network layer. Enabling IPv6 PIM-SM Before you configure IPv6 PIM-SSM, you must enable IPv6 PIM-SM, because the implementation of the IPv6 SSM model is based on subsets of IPv6 PIM-SM.

  • Page 391: Configuring Common Ipv6 Pim Features

    Step Command Remarks Configure the IPv6 SSM The default range is FF3x::/32, ssm-policy ipv6-acl-number group range. where x can be any valid scope. Configuring common IPv6 PIM features Configuration task list Tasks at a glance (Optional.) Configuring an IPv6 multicast source policy (Optional.) Configuring an IPv6 PIM hello policy (Optional.)

  • Page 392: Configuring An Ipv6 Pim Hello Policy

    Configuring an IPv6 PIM hello policy This feature enables the device to filter IPv6 PIM hello messages by using an ACL that specifies the packet source addresses. It is used to guard against IPv6 PIM message attacks and to establish correct IPv6 PIM neighboring relationships.

  • Page 393: Configuring Common Ipv6 Pim Timers

    changed. In this case, it sends a join message to the upstream router for status update. You can configure an interface to drop hello messages without the generation ID options to promptly know the status of an upstream router. You can configure hello message options for all interfaces in IPv6 PIM view or for the current interface in interface view.
  • Page 394 The following are common timers in IPv6 PIM: • Hello interval—Interval at which an IPv6 PIM router sends hello messages to discover IPv6 PIM neighbors and maintain IPv6 PIM neighbor relationship. • Triggered hello delay—Maximum delay for sending a hello message to avoid collisions caused by simultaneous hello messages.

  • Page 395: Setting The Maximum Size Of A Join Or Prune Message

    Step Command Remarks ipv6 pim triggered-hello-delay Set the triggered hello delay. The default setting is 5 seconds. delay The default setting is 60 seconds. ipv6 pim timer join-prune Set the join/prune interval. This configuration takes effect interval after the current interval ends. Set the joined/pruned state ipv6 pim holdtime join-prune The default setting is 210...

  • Page 396: Enabling Ipv6 Pim Nsr

    Configuration restrictions and guidelines When you enable IPv6 PIM passive mode, follow these restrictions and guidelines: • This feature takes effect only when IPv6 PIM-DM or IPv6 PIM-SM is enabled on the interface. • To avoid duplicate multicast data transmission and flow loop, do not enable this feature on a shared-media LAN with multiple IPv6 PIM routers.

  • Page 397: Displaying And Maintaining Ipv6 Pim

    Displaying and maintaining IPv6 PIM Execute display commands in any view. Task Command Display register-tunnel interface display interface [ register-tunnel [ interface-number ] ] [ brief information. [ description| down ] ] Display BSR information in the display ipv6 pim [ vpn-instance vpn-instance-name ] bsr-info IPv6 PIM-SM domain.
  • Page 398 Figure 120 Network diagram Receiver Host A Switch A Vlan-int100 Host B Receiver Vlan-int300 Vlan-int101 Vlan-int200 Source Vlan-int101 Host C Switch D Switch B 4001::100/64 Vlan-int200 IPv6 PIM-DM Switch C Host D Table 26 Interface and IPv6 address assignment Device Interface IPv6 address Device...
  • Page 399 [SwitchA-Vlan-interface103] ipv6 pim dm [SwitchA-Vlan-interface103] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM on Switch B and Switch C in the same way Switch A is configured. (Details not shown.) # On Switch D, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface. <SwitchD>...

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

    (*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:01:20, Expires: - (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: Vlan-interface103 Upstream neighbor: 1002::2...
  • Page 401 • VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub networks, and a minimum of one receiver host exist in each stub network. The entire IPv6 PIM-SM domain contains only one BSR. • Host A and Host C are multicast receivers in the stub networks N1 and N2.
  • Page 402 # On Switch A, enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Enable MLD on VLAN-interface 100 (the interface that is connected to the stub network). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on other interfaces.

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

    [SwitchA] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64 Hash mask length: 126 Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64...
  • Page 404 global-scoped zone, and it is designated to the IPv6 multicast groups with the scope field value of 14. • MLDv1 runs between Switch A, Switch E, Switch I, and the receivers that directly connect to them, respectively. Figure 122 Network diagram IPv6 admin-scope 1 Vlan-int500 Receiver...
  • Page 405 Device Interface IPv6 address Device Interface IPv6 address Switch E Vlan-int400 7001::1/64 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 122. (Details not shown.) Configure OSPFv3 on all switches in the IPv6 PIM-SM domain. (Details not shown.) Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM: # On Switch A, enable IPv6 multicast routing.
  • Page 406 [SwitchB-Vlan-interface103] ipv6 multicast boundary scope 4 [SwitchB-Vlan-interface103] quit # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 as the boundaries of IPv6 admin-scoped zone 2. <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 multicast boundary scope 4 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] ipv6 multicast boundary scope 4 [SwitchC-Vlan-interface106] quit...
  • Page 407 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 1002::2 Priority: 64 Hash mask length: 126 Uptime: 00:04:54 Candidate BSR address: 1002::2 Priority: 64 Hash mask length: 126 # Display BSR information on Switch D. [SwitchD] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:25 Elected BSR address: 8001::1...
  • Page 408 Scope: 4 Group/MaskLen: FF04::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF14::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF24::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF34::/16 RP address Priority HoldTime...

  • Page 409: Ipv6 Bidir-Pim Configuration Example

    1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF04::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 # Display RP information on Switch F. [SwitchF] display ipv6 pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address Priority HoldTime Uptime Expires 8001::1 (local) 00:10:28...
  • Page 410 Device Interface IPv6 address Device Interface IPv6 address Switch B Vlan-int102 2002::1/64 Source 2 — 5001::2/64 Switch C Vlan-int102 2002::2/64 Receiver 1 — 2001::2/64 Switch C Vlan-int103 3001::1/64 Receiver 2 — 4001::2/64 Switch C Loop0 6001::1/128 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 123.
  • Page 411 <SwitchC> system-view [SwitchC] ipv6 multicast routing [SwitchC-mrib6] quit [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] ipv6 pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 pim sm [SwitchC-Vlan-interface103] quit [SwitchC] interface loopback 0 [SwitchC-LoopBack0] ipv6 pim sm [SwitchC-LoopBack0] quit [SwitchC] ipv6 pim [SwitchC-pim6] bidir-pim enable # On Switch D, enable IPv6 multicast routing.
  • Page 412 FE38:4E01 # Display IPv6 BIDIR-PIM DF information on Switch B. [SwitchB] display ipv6 pim df-info RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Vlan200 01:24:09 FE80::200:5EFF: FE71:2801 (local) Vlan101 01:24:09 FE80::20F:E2FF: FE38:4E01 (local) Vlan102 Lose 01:23:12 FE80::20F:E2FF: FE15:5601 # Display IPv6 BIDIR-PIM DF information on Switch C. [SwitchC] display ipv6 pim df-info RP address: 6001::1 Interface...

  • Page 413: Ipv6 Pim-Ssm Configuration Example

    RPF interface: Vlan-interface102 List of 2 DF interfaces: 1: Vlan-interface101 2: Vlan-interface200 # Display information about DFs for IPv6 multicast forwarding on Switch C. [SwitchC] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 6001::1 Flags: 0x0 Uptime: 00:07:21 RPF interface: LoopBack0 List of 2 DF interfaces:...
  • Page 414 Figure 124 Network diagram Receiver Host A Switch A Vlan-int100 Vlan-int102 Host B Vlan-int102 Receiver Vlan-int300 Vlan-int105 Vlan-int103 Vlan-int200 Vlan-int105 Vlan-int103 Source Vlan-int104 Switch D Switch E Switch B Host C 4001::100/64 Vlan-int104 Vlan-int200 IPv6 PIM-SSM Host D Switch C Table 30 Interface and IPv6 address assignment Device Interface...
  • Page 415 [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] ipv6 pim sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM on Switch B and Switch C in the same way Switch A is configured.

  • Page 416: Troubleshooting Ipv6 Pim

    Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF3E::101) Protocol: pim-ssm, Flag: LOC UpTime: 00:08:02 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface105 Protocol: pim-ssm, UpTime: 00:08:02, Expires: 00:03:25 The output shows that switches on the SPT path (Switch A and Switch D) have generated the correct (S, G) entries.

  • Page 417: An Rp Cannot Join An Spt In Ipv6 Pim-Sm

    Solution To resolve the problem: Use display current-configuration to verify the IPv6 multicast forwarding boundary settings. Use ipv6 multicast boundary to change the multicast forwarding boundary settings to make the IPv6 multicast packet able to cross the boundary. Use display current-configuration to verify the IPv6 multicast source policy. Change the ACL rule defined in the source-policy command so that the source/group address of the IPv6 multicast data can pass ACL filtering.

  • Page 418: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.

  • Page 419: Network Topology Icons

    Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

  • Page 420: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...

  • Page 421: Websites

    Websites Website Link Networking websites Hewlett Packard Enterprise Information Library for www.hpe.com/networking/resourcefinder Networking Hewlett Packard Enterprise Networking website www.hpe.com/info/networking Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty General websites Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs Hewlett Packard Enterprise Support Center...
  • Page 422 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 423: Index

    Index Numerics MSDP inter-AS multicast configuration (static RPF peers)(on switch), multicast inter-AS MD VPN, IGMP snooping message 802.1p priority, multicast intra-AS MD VPN configuration, MLD snooping 802.1p message priority, multicast VPN inter-AS option B, multicast VPN inter-AS option C, ASBR multicast VPN inter-AS option A, IGMP snooping policy, multicast VPN inter-AS option B,...
  • Page 424 C-RP configuration, cache MSDP SA message cache, DF election, domain border configuration, troubleshooting MSDP SA message cache entries, enable, candidate forwarding BSM out of incoming interface, bootstrap router. See C-BSR introduction, RP. See C-RP IPv6. See IPv6 BIDIR-PIM C-BSR multicast VPN default MDT establishment (BIDIR-PIM network), BIDIR-PIM C-BSR configuration, neighbor discovery,...
  • Page 425 IGMP snooping fast-leave processing, IPv6 PIM hello message options (interface), IGMP snooping general query/response IPv6 PIM hello policy, parameters, IPv6 PIM multicast source policy, IGMP snooping general query/response IPv6 PIM snooping, 301, parameters (global), IPv6 PIM snooping (VLAN), IGMP snooping group policy+simulated IPv6 PIM timer, joining (for VLAN), IPv6 PIM timer (global),...
  • Page 426 MLD snooping general query/response multicast VPN, 197, 212, parameters (VSI), multicast VPN BGP MDT, MLD snooping group policy+simulated joining multicast VPN BGP MDT peer/peer group, (for VLAN), multicast VPN BGP MDT route reflector, MLD snooping IPv6 multicast group policy, multicast VPN inter-AS option B, multicast VPN inter-AS option C, MLD snooping IPv6 multicast group policy multicast VPN MD VPN,...
  • Page 427 static multicast MAC address entry (system BIDIR-PIM configuration, view), IGMP basic configuration, sub-VLAN-based IPv6 multicast VLAN, IGMP configuration, sub-VLAN-based multicast VLAN, 60, IGMP proxying configuration, connecting IGMP SSM mapping configuration, MSDP peering connection, IGMPv3 host control, MSDP peering connection control, IPv6 BIDIR-PIM configuration, connection IPv6 multicast routing+forwarding configuration,...
  • Page 428 IPv6 PIM-SM BSM forwarding, IPv6 PIM-SM SPT switchover, IPv6 PIM-SM BSM semantic fragmentation, PIM BFD enable, PIM hello message DR_Priority, MLD snooping dynamic router port change, PIM passive mode enable, PIM-SM DR election, PIM-SM BSM semantic fragmentation, PIM-SM RPT building, discovering PIM-SM SPT switchover, BIDIR-PIM neighbor discovery,...
  • Page 429 IGMP snooping (VSI view), PIM passive mode, IGMP snooping host tracking (global), PIM SNMP notification, IGMP snooping host tracking (VLAN), PIM-DM, IGMP snooping proxying, PIM-DM state-refresh, IGMP snooping querier, PIM-SM, IGMP snooping report suppression, PIM-SM Auto-RP listening, IP multicast routing, encapsulating IPv6 BIDIR-PIM, MSDP SA message multicast data encapsulation,...
  • Page 430 MLD snooping IPv6 multicast unknown data IPv6 PIM-SM BSR, drop, IPv6 PIM-SM configuration, MLD snooping policy, IPv6 PIM-SM DR election, MLDv2 filter mode, IPv6 PIM-SM multicast source registration, 356, MSDP SA message filtering configuration, MSDP SA message policy, IPv6 PIM-SM non-scoped zone configuration, PIM hello policy, IPv6 PIM-SM RP, PIM multicast source policy,...
  • Page 431 PIM-SM zone border router, MLD snooping simulated member host port, global-scoped zone PIM-SM admin-scoped/global-scoped zone relationship, IPv6 PIM hello message Generation ID option, graft IPv6 PIM-DM, PIM hello message Generation ID option, IPv6 PIM-DM graft retry timer, IGMP PIM-DM, basic configuration, 92, PIM-DM graft retry timer, configuration, 86, 92, display,...
  • Page 432 troubleshoot no membership information on simulated member host configuration, router, static multicast MAC address entry configuration version specification, restrictions, versions, static port configuration, VPN support, static port configuration (for VLAN), IGMP snooping troubleshoot, basic configuration, troubleshoot Layer 2 multicast forwarding, troubleshoot multicast group filter, configuration, 13, 17, configuration (for VXLAN),...
  • Page 433 IP addressing IGMP snooping general query/response parameters, IGMP snooping message source IP address, IGMP snooping group policy, IP multicast address, IGMP snooping group policy+simulated joining configuration (for VLAN), IP multicast packet forwarding, IGMP snooping groups on port, IP multicast IGMP snooping last member query interval, address, IGMP snooping leave message, architecture,...
  • Page 434 IPv6 PIM protocol relationships, MLD snooping forwarding entries, MLD snooping general query/response IPv6 PIM snooping display, parameters, IPv6 PIM snooping maintain, MLD snooping group policy, IPv6 PIM timer, MLD snooping group policy+simulated joining IPv6 PIM VPN support, configuration (for VLAN), IPv6 PIM-DM, MLD snooping group replacement, IPv6 PIM-DM configuration, 365,...
  • Page 435 MSDP peering connection control, PIM-SM configuration, MSDP peer-RPF forwarding, PIM-SM DR election, MSDP protocols and standards, PIM-SM enable, MSDP RPF static peer, PIM-SM multicast source registration, MSDP SA message cache, PIM-SM neighbor discovery, MSDP SA message filtering configuration, PIM-SM non-scoped zone configuration, MSDP SA message multicast data PIM-SM RP configuration, encapsulation,...
  • Page 436 troubleshooting MLD snooping Layer 2 BSR configuration, forwarding, C-BSR configuration, troubleshooting MSDP, configuration, 374, troubleshooting PIM, C-RP, troubleshooting PIM abnormal multicast data DF election, termination, domain border configuration, troubleshooting PIM multicast distribution tree, enable, introduction, troubleshooting PIM snooping, IPv6 PIM protocol relationships, troubleshooting PIM snooping does not work, neighbor discovery, protocols and standards,...
  • Page 437 sub-VLAN-based configuration, state refresh parameters, IPv6 PIM-SM sub-VLAN-based implementation, IPv6 PIM administrative scoping, 361, BFD enable, administrative scoping zone border router, common feature configuration, admin-scoped zone configuration, configuration, 350, Anycast RP, 354, display, assert mechanism, hello message option configuration (global), BSM forwarding disable, BSM semantic fragmentation, hello message option configuration (interface),...
  • Page 438 PIM join/prune message size, static multicast MAC address entry, maintaining IGMP, Layer 2 IGMP snooping, IP multicast protocols, IPv6 multicast routing+forwarding, IPv6 PIM snooping configuration, 301, IPv6 multicast VLAN, IPv6 PIM snooping configuration (VLAN), IPv6 PIM snooping, PIM snooping configuration, 51, 52, MLD, troubleshooting IGMP snooping Layer 2 MLD snooping,...
  • Page 439 multicast VPN MDT switchover, IPv6 multicast VLAN configuration, 308, 310, member maintain, IGMP snooping router port, MLDv1. See MLDv1 IGMP snooping simulated member host, MLDv1 support, MLD snooping member port, MLDv2. See MLDv2 MLD snooping simulated member host port, MLDv2 support, NSR configuration, mesh performance adjustment,...
  • Page 440 IPv6 multicast group policy configuration MLD support, restrictions, querier election, IPv6 multicast group replacement, MLDv1 snooping version, IPv6 multicast group replacement restrictions, MLDv2 filter mode, IPv6 multicast groups on port, how it works, IPv6 multicast source port filtering, IPv6 PIM-SSM introduction, IPv6 multicast unknown data drop, MLD support, IPv6 multicast unknown data drop enable...
  • Page 441 peer-RPF forwarding, port-based multicast VLAN configuration, PIM-SM inter-domain multicast configuration, port-based multicast VLAN user port assignment, protocols and standards, port-based multicast VLAN user port assignment restrictions, RPF static peer, port-based multicast VLAN user port attribute, SA message cache, sub-VLAN-based configuration, SA message filtering configuration, sub-VLAN-based multicast VLAN configuration, SA message multicast data encapsulation,...
  • Page 442 neighbor IP multicast packet forwarding, multicast MD VPN PIM neighbor relationships, IP multicast VPN application, IP multicast VPN instance, neighbor discovery IPv6 BIDIR-PIM BSM forwarding disable, BIDIR-PIM, IPv6 BIDIR-PIM BSR, IPv6 BIDIR-PIM, IPv6 BIDIR-PIM configuration, 374, IPv6 PIM-DM, IPv6 BIDIR-PIM RP, IPv6 PIM-SM, IPv6 multicast forwarding (unicast subnet), IPv6 PIM-SSM,...
  • Page 443 MLD IPv6 multicast group policy, multicast VPN default MDT establishment (BIDIR-PIM network), MLD performance adjustment, multicast VPN default MDT establishment MLD proxying configuration, (PIM-DM network), MLD query/response parameter, multicast VPN default MDT establishment MLD snooping basic configuration, (PIM-SM network), MLD snooping configuration (for VXLAN), multicast VPN default MDT establishment MLD snooping group policy+simulated joining (PIM-SSM network),...
  • Page 444 PIM-SM zone relationships, non-scoped zone PIM-SSM configuration, IPv6 PIM-SM non-scoped zone configuration, PIM-SSM DR election, PIM-SM non-scoped zone configuration, PIM-SSM group range, notifying PIM-SSM neighbor discovery, IPv6 multicast PIM SNMP notification, PIM-SSM SPT building, PIM SNMP notification enable, port-based IPv6 multicast VLAN configuration, 错误!未定义书签。...
  • Page 445 IGMP snooping message parameters, IPv6 PIM-DM. See IPv6 PIM-DM MLD query/response parameter, IPv6 PIM-SM. See IPv6 PIM-SM MSDP SA message-related parameters, IPv6 PIM-SSM. See IPv6 PIM-SSM multicast VPN MDT switchover parameters, join/prune message size, multicast intra-AS MD VPN configuration, PIM-DM state-refresh, multicast MD VPN PIM neighbor relationships, multicast MD VPN PIM neighbor relationships, multicast source policy,...
  • Page 446 错误!未定义书签。 MSDP SA request message, PIM NSR enable, multicast routing+forwarding configuration, PIM passive mode enable, multicast source registration, 114, PIM protocol relationships, multicast VPN default MDT characteristics, PIM SNMP notification enable, multicast VPN default MDT establishment protocols and standards, (PIM-SM network), SPT building, neighbor discovery, state-refresh enable,...
  • Page 447 MLD snooping policy, MLD snooping port types, MSDP SA message policy, MLD snooping simulated member host port, port MLD snooping static port configuration, IGMP snooping basic configuration, MLD snooping static port configuration (for VLAN), IGMP snooping configuration, 13, 17, PIM snooping configuration, 51, 52, IGMP snooping configuration (for VXLAN), port-based multicast VLAN user port assignment, IGMP snooping dynamic port aging timer,...
  • Page 448 configuring IGMP snooping (for VLAN), configuring IPv6 multicast port-based VLAN, configuring IGMP snooping (for VSI), configuring IPv6 multicast port-based VLAN user port attribute, configuring IGMP snooping (for VXLAN), configuring IPv6 multicast routing+forwarding, configuring IGMP snooping basic features, 322, configuring IGMP snooping fast-leave configuring IPv6 multicast sub-VLAN-based processing configuration, VLAN,...
  • Page 449 configuring MLD query/response parameter, configuring MSDP mesh group, configuring MSDP peer description, configuring MLD query/response parameter configuring MSDP peering connection, (global), configuring MSDP PIM-SM inter-domain multicast, configuring MLD query/response parameter (on interface), configuring MSDP RPF static peer, configuring MLD snooping, configuring MSDP SA message cache, configuring MLD snooping (for VLAN), configuring MSDP SA message filtering,...
  • Page 450 configuring PIM-SM, disabling IPv6 PIM-SM BSM forwarding, configuring PIM-SM admin-scoped zone, disabling IPv6 PIM-SM BSM semantic fragmentation, configuring PIM-SM Anycast RP, disabling MLD snooping dynamic router port configuring PIM-SM BSR, change, configuring PIM-SM C-BSR, disabling PIM-SM BSM semantic fragmentation, configuring PIM-SM C-RP, configuring PIM-SM multicast source displaying IGMP, registration,...
  • Page 451 enabling IGMP snooping report suppression, enabling multicast VPN RPF vector compatibility, enabling IP multicast routing, enabling PIM BFD, 错误!未定义书签。 enabling IPv6 BIDIR-PIM, enabling PIM NSR, enabling IPv6 multicast routing, enabling PIM passive mode, enabling IPv6 multicast sub-VLAN forwarding, enabling PIM SNMP notification, enabling PIM-DM, enabling IPv6 PIM BFD, enabling PIM-DM state-refresh,...
  • Page 452 setting MLD snooping 802.1p message troubleshooting IGMP snooping multicast group priority, filter, setting MLD snooping 802.1p message troubleshooting IPv6 PIM abnormal multicast data priority (global), termination, setting MLD snooping 802.1p message troubleshooting IPv6 PIM multicast distribution priority (VLAN), tree, setting MLD snooping dynamic port aging troubleshooting IPv6 PIM-SM multicast source timers, registration failure,...
  • Page 453 IGMP proxying, reflecting IGMP proxying configuration, multicast VPN BGP MDT route reflector, IGMP snooping proxying, 16, refreshing MLD IPv6 multicast load splitting (MLD proxy), IPv6 PIM-DM state refresh enable, IPv6 PIM-DM state refresh parameters, MLD proxying, 334, PIM-DM state-refresh, MLD proxying configuration, PIM-DM state-refresh parameters, MLD snooping proxying, 265, registering...
  • Page 454 port-based multicast VLAN user port IGMP snooping group policy+simulated joining assignment, configuration (for VLAN), static multicast MAC address entry IGMP snooping last member query interval, configuration, IGMP snooping message 802.1p priority, sub-VLAN-based multicast VLAN IGMP snooping message parameters, configuration, IGMP snooping message source IP address, restrictions and guidelines IGMP snooping multicast group policy, MLD snooping, 17,...
  • Page 455 IPv6 PIM- graft retry timer, MLD MP snooping proxying, IPv6 PIM hello message options, MLD NSR, IPv6 PIM hello policy, MLD proxying, 334, IPv6 PIM join/prune message max size, MLD proxying configuration, IPv6 PIM multicast source policy, MLD query/response parameter, IPv6 PIM NSR enable, MLD snooping 802.1p message priority, IPv6 PIM protocol relationships,...
  • Page 456 multicast intra-AS MD VPN configuration, PIM-SM neighbor discovery, multicast routing, 70, See also multicast PIM-SM non-scoped zone configuration, routing+forwarding PIM-SM RP configuration, multicast VPN BGP MDT configuration, PIM-SM RP discovery, multicast VPN BGP MDT route reflector, PIM-SM RPT building, multicast VPN configuration, 197, 212, PIM-SM SPT switchover, 115, multicast VPN data-MDT to default-MDT PIM-SM static RP,...
  • Page 457 PIM-SM C-RP, PIM-SM discovery, MSDP peer-RPF forwarding, PIM-SM RPT building, MSDP SA message cache, PIM-SM SPT switchover, MSDP SA message filtering configuration, PIM-SM static RP, MSDP SA message multicast data encapsulation, troubleshooting IPv6 PIM-SM RP cannot join SPT, MSDP SA message originating RP, troubleshooting IPv6 PIM-SM RPT cannot be MSDP SA message policy, built,...
  • Page 458 MLD snooping IPv6 multicast groups on port, IPv6 PIM-DM SPT building, IPv6 PIM-SM SPT switchover, 357, multicast VLAN forwarding entries max, IPv6 PIM-SSM RPT building, PIM join/prune message size, PIM-DM SPT building, PIM-SM multicast source registration, IP multicast model, PIM-SM SPT switchover, shortest path tree.
  • Page 459 configuration, 310, IGMP snooping dynamic router port aging timer, implementation, IPv6 PIM, sub-VLAN-based multicast VLAN IPv6 PIM configuration (global), configuration, 60, 63, IPv6 PIM configuration (interface), configuration restrictions, IPv6 PIM-DM graft retry, implementation, MLD snooping dynamic port aging timers, suppressing MLDv2, IGMP snooping report suppression, PIM common,...
  • Page 460 MLD snooping, IGMPv3 snooping, MLD snooping IPv6 multicast group policy, MLD snooping specification, MLD version specification, MLD snooping Layer 2 forwarding, MLDv1, MSDP, MLDv1 snooping, MSDP peers stay in disabled state, MLDv2, MSDP RP entry exchange, MLDv2 snooping, MSDP SA message cache, VLAN multicast MD VPN default-MDT establishment, BIDIR-PIM configuration,...
  • Page 461 MLD snooping general query/response IPv6 PIM-SM administrative scoping, parameter configuration (VLAN), PIM-SM administrative scoping, MLD snooping general query/response zone parameters, border router. See MLD snooping group policy+simulated joining IPv6 admin-scoped/global-scoped zone configuration (for VLAN), relationships, MLD snooping host tracking, IPv6 PIM-SM admin-scoped zone configuration, MLD snooping message parameters, MLD snooping message source IPv6 address, IPv6 PIM-SM border router,...

Table of Contents