1. Manuals
  2. Brands
  3. HPE Manuals
  4. Switch
  5. FlexFabric 5800 Series
  6. Configuration manual

HPE FlexFabric 5800 Series Configuration Manual

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

Advertisement

Quick Links

Download this manual
HPE 5820X & 5800 Switch Series
IP Multicast

Configuration Guide

Part number: 5998-7383R
Software version: Release 1810
Document version: 6W100-20160129

Advertisement

Table of Contents
loading

Related Manuals for HPE FlexFabric 5800 Series

Summary of Contents for HPE FlexFabric 5800 Series

  • Page 1: Configuration Guide

    HPE 5820X & 5800 Switch Series IP Multicast Configuration Guide Part number: 5998-7383R Software version: Release 1810 Document version: 6W100-20160129...
  • 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 Information transmission techniques ·········································································································· 1 Multicast features ······································································································································· 3 Common notations in multicast ·················································································································· 4 Multicast advantages and applications ······································································································ 4 Multicast models ················································································································································ 4 Multicast architecture ········································································································································· 5 Multicast addresses ··································································································································· 5 Multicast protocols ····································································································································· 9 Multicast packet forwarding mechanism ··········································································································...
  • Page 4 Group policy and simulated joining configuration example (in a VLAN) ·················································· 36 Static port configuration example (in a VLAN) ························································································· 38 IGMP snooping querier configuration example ························································································ 41 IGMP snooping proxying configuration example ······················································································ 43 Multicast source and user control policy configuration example ······························································ 46 Troubleshooting IGMP snooping ·····················································································································...
  • Page 5 Static multicast route failure ····················································································································· 91 Multicast data fails to reach receivers ······································································································ 91 Configuring IGMP ························································································· 92 Overview ·························································································································································· 92 IGMP versions ·········································································································································· 92 IGMPv1 overview ····································································································································· 92 IGMPv2 enhancements ···························································································································· 94 IGMPv3 enhancements ···························································································································· 94 IGMP SSM mapping ································································································································ 96 IGMP proxying ·········································································································································...
  • Page 6 Configuring PIM-SM ······································································································································· 137 PIM-SM configuration task list ················································································································ 137 Configuration prerequisites ···················································································································· 138 Enabling PIM-SM ··································································································································· 138 Configuring an RP ·································································································································· 139 Configuring a BSR ································································································································· 141 Configuring administrative scoping ········································································································ 144 Configuring multicast source registration ······························································································· 146 Disabling switchover to SPT ·················································································································· 147 Configuring BIDIR-PIM ··································································································································...
  • Page 7 Displaying MBGP ··································································································································· 237 Resetting MBGP connections ················································································································ 238 Clearing MBGP information ··················································································································· 239 MBGP configuration example ························································································································ 239 Configuring multicast VPN (available only on the HPE 5800) ····················· 243 Overview ························································································································································ 243 MD-VPN overview ·································································································································· 245 Multicast across VPNs ··························································································································· 247 M6VPE ···················································································································································...
  • Page 8 How MD-VPN works ······································································································································ 250 Share-MDT establishment ····················································································································· 250 Share-MDT-based delivery ···················································································································· 253 MDT switchover ····································································································································· 257 Multi-AS MD VPN ··································································································································· 258 Multicast VPN configuration task list ·············································································································· 260 Configuring MD-VPN ····································································································································· 261 Configuration prerequisites ···················································································································· 261 Enabling IP multicast routing in a VPN instance ···················································································· 261 Configuring a share-group and an MTI binding ······················································································...
  • Page 9 Configuring an IPv6 multicast group filter ······························································································ 319 Configuring IPv6 multicast source port filtering ······················································································ 320 Enabling dropping unknown IPv6 multicast data ··················································································· 320 Enabling MLD report suppression ·········································································································· 321 Setting the maximum number of multicast groups that a port can join ·················································· 321 Enabling IPv6 multicast group replacement ···························································································...
  • Page 10 Troubleshooting IPv6 multicast policy configuration ······················································································ 373 Abnormal termination of IPv6 multicast data ·························································································· 373 Configuring MLD ························································································· 374 Overview ························································································································································ 374 MLD versions ········································································································································· 374 How MLDv1 operates ····························································································································· 374 How MLDv2 operates ····························································································································· 376 MLD message types ······························································································································ 377 MLD SSM mapping ································································································································...
  • Page 11 Configuring IPv6 PIM-SM ······························································································································ 420 IPv6 PIM-SM configuration task list ······································································································· 420 Configuration prerequisites ···················································································································· 421 Enabling IPv6 PIM-SM ··························································································································· 421 Configuring an RP ·································································································································· 422 Configuring a BSR ································································································································· 424 Configuring IPv6 administrative scoping ································································································ 427 Configuring IPv6 multicast source registration ······················································································· 428 Disabling switchover to SPT ··················································································································...
  • Page 12 Configuring IPv6 MBGP route attributes ········································································································ 483 Configuration prerequisites ···················································································································· 484 Configuring IPv6 MBGP route preferences ···························································································· 484 Configuring the default local preference ································································································ 484 Configuring the MED attribute ················································································································ 484 Configuring the NEXT_HOP attribute ···································································································· 485 Configuring the AS_PATH attribute ······································································································· 485 Tuning and optimizing IPv6 MBGP networks ·································································································...

  • Page 13: Multicast Overview

    Multicast overview As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load. Using multicast technology, a network operator can easily provide bandwidth-critical and time-critical information services.
  • Page 14 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 Figure 2, assume that only Host B, Host D, and Host E need the information. If the information is broadcast to the subnet, Host A and Host C also receive it.

  • Page 15: Multicast Features

    Figure 3 Multicast transmission As shown in Figure 3, the multicast source sends only one copy of the information to a multicast group. Host B, Host D and Host E, which are receivers of the information, must join the multicast group.

  • Page 16: Common Notations In Multicast

    Table 1 Comparing TV program transmission and multicast transmission TV 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 17: Multicast Architecture

    ASM model In the ASM model, any sender can send information to a multicast group as a multicast source. Receivers can join a multicast group (identified by a group address) and obtain multicast information addressed to that multicast group. In this model, receivers do not know the positions of the multicast sources in advance.
  • Page 18 Internet Assigned Numbers Authority (IANA) assigned the Class D address space (224.0.0.0 to 239.255.255.255) for IPv4 multicast. Table 2 Class D IP address blocks and description Address block Description Reserved permanent group addresses. The IP address 224.0.0.0 is reserved. Other IP addresses can be used by routing protocols and for topology searching, protocol maintenance, and so 224.0.0.0 to 224.0.0.255 Table 3...
  • Page 19 • IPv6 multicast addresses: Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address as shown in Figure 0xFF—The most significant eight bits are 11111111, which indicates that this address is an IPv6 multicast address. Flags—The Flags field contains four bits as shown in Figure 5 and described in...
  • Page 20 Value Meaning 6, 7, 9 through D Unassigned. Organization-local scope. Global scope. 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 A multicast MAC address identifies a group of receivers at the data link layer. •...

  • Page 21: Multicast Protocols

    Multicast protocols Multicast protocols include the following categories: • Layer 3 and Layer 2 multicast protocols: Layer 3 multicast refers to IP multicast operating at the network layer. Layer 3 multicast protocols—IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP.
  • Page 22 In the ASM model, multicast routes include intra-domain routes and inter-domain routes. An intra-domain multicast routing protocol discovers multicast sources and builds multicast distribution trees within an AS to deliver multicast data to receivers. Among a variety of mature intra-domain multicast routing protocols, Protocol Independent Multicast (PIM) is most widely used.

  • Page 23: Multicast Packet Forwarding Mechanism

    only one copy of multicast to the multicast VLAN or IPv6 multicast VLAN on the Layer 2 device. This approach avoids wasting network bandwidth and placing an extra burden on the Layer 3 device. Multicast packet forwarding mechanism In a multicast model, receiver hosts of a multicast group are usually located at different positions of the network.

  • Page 24: Multicast Application In Vpns

    Figure 10 VPN networking diagram VPN A CE a2 CE b2 CE b3 PE 2 VPN B VPN B CE b1 CE a1 CE a3 PE 1 PE 3 Public network VPN A VPN A • The provider (P) device belongs to the public network. The customer edge (CE) devices belong to their respective VPNs.

  • Page 25: Configuring Igmp Snooping

    Configuring IGMP snooping This chapter describes IGMP snooping, how to configure IGMP snooping, configuration examples, troubleshooting methods, and an appendix about processing multicast protocol messages. Overview IGMP snooping is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups.
  • Page 26 Figure 12 IGMP snooping related ports The following describes the ports involved in IGMP snooping: • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include designated routers (DRs) and IGMP queriers. In Figure 12, GigabitEthernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switch B are router ports.

  • Page 27: How Igmp Snooping Operates

    Expected message Action after Timer Description before expiration expiration port ages out. NOTE: In IGMP snooping, only dynamic ports age out. Static ports never age out. How IGMP snooping operates An IGMP snooping-enabled switch performs different actions when it receives different IGMP messages.

  • Page 28: Igmp Snooping Proxying

    removes the port from the associated forwarding entry. For a static member port, this mechanism does not take effect. When an IGMPv2 or IGMPv3 host leaves a multicast group, the host sends an IGMP leave message to the multicast router. When the switch receives an IGMP leave message on a dynamic member port, the switch first examines whether a forwarding entry matches the group address in the message:.
  • Page 29 Figure 13 Network diagram IGMP Querier IP network Router A Query from Router A Report from Switch A Query from Switch A Proxy & Querier Switch A Report from Host Host A Host C Receiver Receiver Host B As shown in Figure 13, Switch A works as an IGMP snooping proxy.

  • Page 30: Protocols And Standards

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

  • Page 31: Configuring Basic Igmp Snooping Functions

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

  • Page 32: Specifying The Version Of Igmp Snooping

    Enter IGMP-snooping view. igmp-snooping Set the maximum number of By default, the upper limit is 4000 IGMP snooping forwarding for the HPE 5800 switches, and entry-limit limit entries. 2000 for the HPE 5820X switches. NOTE: IGMP snooping forwarding entries created for multicast VLAN are not limited by this command. You can use the multicast-vlan entry-limit to limit the number of entries in the IGMP snooping forwarding table of a multicast VLAN.

  • Page 33: Configuring Static Multicast Mac Address Entries

    Configuring static multicast MAC address entries In Layer-2 multicast, a Layer 2 multicast protocol (such as IGMP snooping) can dynamically add multicast MAC address entries. Or, you can manually configure multicast MAC address entries. Configuration guidelines • You can configure a static multicast MAC address entry for any legal multicast MAC address. A multicast MAC address is a MAC address in which the least significant bit of the the most significant octet is 1.

  • Page 34: Setting Aging Timers For Dynamic Ports

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

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

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

  • Page 36: Enabling Igmp Snooping Fast-Leave Processing

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

  • Page 37: Configuring An Igmp Snooping Querier

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

  • Page 38: Configuring Parameters For Igmp Queries And Responses

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable the IGMP snooping Disabled by default. igmp-snooping querier querier in the VLAN. Configuring parameters for IGMP queries and responses CAUTION: In the configuration, make sure the IGMP general query interval is larger than the maximum response delay for IGMP general queries.

  • Page 39: Configuring The Source Ip Addresses For Igmp Queries

    Step Command Remarks query interval. last-member-query-interval interval Configuring the source IP addresses for IGMP queries IMPORTANT: Changing the source address for IGMP query messages might affect the IGMP querier election within the subnet. After a switch receives an IGMP query whose source IP address is 0.0.0.0 on a port, it does not enlist that port as a dynamic router port.

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

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

  • Page 41: Configuring Multicast Source Port Filtering

    multicast data for the multicast group is not sent to this port, and the user cannot retrieve the program. Configuration guidelines • When you configure a multicast group filter in a multicast VLAN, be sure to configure the filter in the sub-VLANs of the multicast VLAN.

  • Page 42: Enabling Dropping Unknown Multicast Data

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

  • Page 43: Enabling Igmp Report Suppression

    Step Command Remarks Enter VLAN view. vlan vlan-id Enable dropping unknown Disabled by default. igmp-snooping drop-unknown multicast data. Enabling IGMP report suppression When a Layer 2 switch receives an IGMP report from a multicast group member, the switch forwards the message to the directly connected Layer 3 device. When multiple members of a multicast group are attached to the Layer 2 switch, the Layer 3 device might receive duplicate IGMP reports for the multicast group.

  • Page 44: Enabling Multicast Group Replacement

    Set the maximum number of By default, the upper limit is 4000 igmp-snooping group-limit limit multicast groups that the port for the HPE 5800 switches, and [ vlan vlan-list ] can join. 2000 for the HPE 5820X switches. Enabling multicast group replacement...

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

    Step Command Remarks Enable multicast group igmp-snooping Disabled by default. replacement. overflow-replace [ vlan vlan-list ] Setting the 802.1p precedence for IGMP messages You can change the 802.1p precedence of IGMP messages so that they can be assigned higher forwarding priority when congestion occurs on their outgoing ports. Setting the 802.1p precedence for IGMP messages globally Step Command...

  • Page 46: Enabling The Igmp Snooping Host Tracking Function

    • After receiving an IGMP leave message from a host, the access switch matches the multicast group address and source address with the policies. If a match is found, the host is allowed to leave the group. Otherwise, the leave message is dropped by the access switch. To configure a multicast user control policy: Step Command...

  • Page 47: Displaying And Maintaining Igmp Snooping

    To set the DSCP value for IGMP messages: Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the DSCP value for By default, the DSCP value in dscp dscp-value IGMP messages IGMP messages is 48. Displaying and maintaining IGMP snooping Task Command Remarks...

  • Page 48: Group Policy And Simulated Joining Configuration Example (In A Vlan)

    Group policy and simulated joining configuration example (in a VLAN) Network requirements As shown in Figure 14, IGMPv2 runs on Router A, IGMPv2 snooping runs on Switch A, and Router A acts as the IGMP querier on the subnet. Configure a group policy and simulated joining to meet the following requirements: •...
  • Page 49 [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP snooping and the function of dropping unknown multicast traffic in the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping drop-unknown [SwitchA-vlan100] quit...

  • Page 50: Static Port Configuration Example (In A Vlan)

    MAC group address:0100-5e01-0101 Host port(s):total 2 port(s). GE1/0/3 GE1/0/4 The output shows that GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 on Switch A have joined the multicast group 224.1.1.1. Static port configuration example (in a VLAN) Network requirements As shown in Figure •...
  • Page 51 Figure 15 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 15. (Details not shown.) On Router A, enable IP multicast routing, enable IGMP on GigabitEthernet 1/0/1, and enable PIM-DM on each interface. <RouterA>...
  • Page 52 [SwitchA-GigabitEthernet1/0/3] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to this VLAN, and enable IGMP snooping in the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port gigabitethernet 1/0/1 gigabitethernet 1/0/2 [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] quit Configure Switch C:...

  • Page 53: Igmp Snooping Querier Configuration Example

    IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 1 port. GE1/0/2 (D) ( 00:03:23 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port. GE1/0/2 The output shows that GigabitEthernet 1/0/3 of Switch A has become a static router port. # Display detailed IGMP snooping group information in VLAN 100 on Switch C.
  • Page 54 • IGMPv2 runs on all receivers, and IGMPv2 snooping runs on all switches. • Switch A, which is close to the multicast sources, is chosen as the IGMP snooping querier. Perform the following tasks to meet the requirements: • To prevent flooding of unknown multicast traffic within the VLAN, be sure to configure all switches to drop unknown multicast data packets.

  • Page 55: Igmp Snooping Proxying Configuration Example

    Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable IGMP snooping and the function of dropping unknown multicast traffic in VLAN 100. [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] igmp-snooping drop-unknown [SwitchB-vlan100] quit...
  • Page 56 Figure 17 Network diagram Receiver Host A Source Receiver GE1/0/4 GE1/0/1 GE1/0/2 10.1.1.1/24 GE1/0/1 GE1/0/3 1.1.1.2/24 Switch A Host B Router A GE1/0/2 1.1.1.1/24 Proxy & Querier IGMP querier Host C VLAN 100 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 17.
  • Page 57 # Display information about the IGMP snooping groups on Switch A. [SwitchA] display igmp-snooping group Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100.

  • Page 58: Multicast Source And User Control Policy Configuration Example

    Total 1 MAC Group(s). Router port(s):total 1 port. GE1/0/1 IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Host port(s):total 1 port. GE1/0/3 MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port. GE1/0/3 Multicast source and user control policy configuration example Network requirements As shown in...
  • Page 59 <SwitchA> system-view [SwitchA] vlan 101 [SwitchA-vlan101] port gigabitethernet 1/0/1 [SwitchA-vlan101] quit [SwitchA] vlan 102 [SwitchA-vlan102] port gigabitethernet 1/0/2 [SwitchA-vlan102] quit [SwitchA] vlan 103 [SwitchA-vlan103] port gigabitethernet 1/0/3 [SwitchA-vlan103] quit [SwitchA] vlan 104 [SwitchA-vlan104] port gigabitethernet 1/0/4 [SwitchA-vlan104] quit # Enable IP multicast routing, enable PIM-DM on VLAN-interface 101, VLAN-interface 102 and VLAN-interface 104, and enable IGMP on VLAN-interface 104.
  • Page 60 [SwitchA] radius scheme scheme1 [SwitchA-radius-scheme1] server-type extended [SwitchA-radius-scheme1] primary authentication 3.1.1.1 [SwitchA-radius-scheme1] key authentication 123321 [SwitchA-radius-scheme1] primary accounting 3.1.1.1 [SwitchA-radius-scheme1] key accounting 123321 [SwitchA-radius-scheme1] user-name-format without-domain [SwitchA-radius-scheme1] quit # Create ISP domain domain1, reference scheme1 for the authentication, authorization, and accounting of LAN users, and specify domain1 as the default ISP domain.
  • Page 61 [SwitchB] radius scheme scheme2 [SwitchB-radius-scheme2] server-type extended [SwitchB-radius-scheme2] primary authentication 3.1.1.1 [SwitchB-radius-scheme2] key authentication 321123 [SwitchB-radius-scheme2] primary accounting 3.1.1.1 [SwitchB-radius-scheme2] key accounting 321123 [SwitchB-radius-scheme2] user-name-format without-domain [SwitchB-radius-scheme2] quit # Create an ISP domain domain2, reference scheme2 for the authentication, authorization, and accounting of LAN users, and specify domain2 as the default ISP domain.

  • Page 62: Troubleshooting Igmp Snooping

    GE1/0/1 (D) ( 00:01:30 ) IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Attribute: Host Port Host port(s):total 1 port(s). GE1/0/3 (D) ( 00:04:10 ) MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port(s). GE1/0/3 The output shows that GigabitEthernet 1/0/3 on Switch B has joined 224.1.1.1 but not 224.1.1.2.

  • Page 63: Configured Multicast Group Policy Fails To Take Effect

    Solution Use the display current-configuration command to display the running status of IGMP snooping. If IGMP snooping is not enabled, use the igmp-snooping command in system view to enable IGMP snooping globally. Then, use the igmp-snooping enable command in VLAN view to enable IGMP snooping for the VLAN.
  • Page 64 If PIM is enabled, the switch deletes only its dynamic member ports but not its dynamic router ports. NOTE: On a switch with Layer-3 multicast routing enabled, use the display igmp group port-info command to display Layer-2 port information. • If PIM is disabled on the switch, one of the following occurs: If IGMP is disabled, the switch deletes all its dynamic router ports.

  • Page 65: Configuring Pim Snooping

    Configuring PIM snooping This chapter describes PIM snooping, how to configure PIM snooping, configuration examples, and troubleshooting methods. Overview PIM snooping runs on Layer 2 devices. It examines the received PIM messages to determine the ports that are interested in the multicast data addressed to a multicast group , and adds the ports to the multicast forwarding entry for the multicast group, so that the multicast data can be forwarded to only the ports that are interested in the data.

  • Page 66: Configuring Pim Snooping

    Maintains the router ports according to the received PIM hello messages that PIM-capable routers send. Floods all other types of received PIM messages in the VLAN. Forwards all multicast data to all router ports in the VLAN. Each PIM-capable router in the VLAN, whether interested in the multicast data or not, can receive all multicast data and all PIM messages except PIM hello messages.

  • Page 67: Pim Snooping Configuration Example (In A Vlan)

    Task Command Remarks exclude | include } regular-expression ] display pim-snooping routing-table [ [ vlan Display PIM snooping routing vlan-id ] [ slot slot-number ] ] [ | { begin | Available in any view. entries. exclude | include } regular-expression ] Display statistics for PIM display pim-snooping statistics [ | { begin | messages learned through PIM...
  • Page 68 [RouterA] multicast routing-enable [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] pim [RouterA-pim] c-bsr gigabitethernet 1/0/2 [RouterA-pim] c-rp gigabitethernet 1/0/2 On Router B, enable IP multicast routing, and enable PIM-SM on each interface. <RouterB>...

  • Page 69: Troubleshooting Pim Snooping

    Neighbor Port Expires Option Flags 10.1.1.1 GE1/0/1 02:02:23 LAN Prune Delay 10.1.1.2 GE1/0/2 03:00:05 LAN Prune Delay 10.1.1.3 GE1/0/3 02:22:13 LAN Prune Delay 10.1.1.4 GE1/0/4 03:07:22 LAN Prune Delay The output shows that Router A, Router B, Router C, and Router D are PIM snooping neighbors. # On Switch A, display the PIM snooping routing information of VLAN 100.

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

    If PIM snooping is not enabled, enter VLAN view and use the pim-snooping enable command to enable PIM snooping for the VLAN. Some downstream PIM-capable routers cannot receive multicast data Symptom In a network with fragmented join/prune messages, some downstream PIM-capable routers cannot receive multicast data.

  • Page 71: Configuring Multicast Vlans

    Configuring multicast VLANs This chapter describes multicast VLAN, how to configure multicast VLAN, and configuration examples. Overview As shown in Figure 21, Host A, Host B, and Host C reside in different VLANs and require the same multicast programs-on-demand service. Router A (Layer 3 device) must forward a separate copy of the multicast data to Switch A (Layer 2 device).

  • Page 72: Port-Based Multicast Vlan

    Figure 22 Sub-VLAN-based multicast VLAN IGMP snooping manages router ports in the multicast VLAN and member ports in the sub-VLANs. When Router A receives the multicast data from the source, it sends only one copy of the multicast data to Switch A in the multicast VLAN. Switch A distributes a separate copy of the data to each sub-VLAN of the multicast VLAN.

  • Page 73: Multicast Vlan Configuration Task List

    the multicast data to Switch A in the multicast VLAN. Switch A distributes the data to all member ports in the multicast VLAN. For more information about IGMP snooping, router ports, and member ports, see "Configuring IGMP snooping." For more information about VLAN tags, see Layer 2—LAN Switching Configuration Guide. Multicast VLAN configuration task list Task Remarks...

  • Page 74: Configuring A Port-Based Multicast Vlan

    Step Command Remarks Enter system view. system-view Configure the specified VLAN as a multicast VLAN By default, a VLAN is not a multicast-vlan vlan-id and enter multicast VLAN multicast VLAN. view. Configure the specified By default, a multicast VLAN has VLANs as sub-VLANs of the subvlan vlan-list no sub-VLANs.

  • Page 75: Configuring Multicast Vlan Ports

    Step Command Remarks • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: interface interface-type Enter proper view. Use either command. interface-number • Enter port group view: port-group manual port-group-name Configure the user port link By default, the port link type is port link-type hybrid type as hybrid.

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

    Configure the maximum By default, the upper limit is 4000 number of forwarding entries for the HPE 5800 switches, and multicast-vlan entry-limit limit in a multicast VLAN. 2000 for the HPE 5820X switches. Displaying and maintaining a multicast VLAN...
  • Page 77 • The multicast source sends multicast data to the multicast group 224.1.1.1. Host A, Host B, Host C, and Host D are receivers of the multicast data. The hosts belong to VLAN 2 through VLAN 5 respectively. Configure the sub-VLAN-based multicast VLAN feature on Switch A to meet the following requirements: •...
  • Page 78 [SwitchA] vlan 2 to 5 # Configure GigabitEthernet 1/0/2 as a trunk port, and assign it to VLAN 2 and VLAN 3. [SwitchA] interface gigabitethernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] port link-type trunk [SwitchA-GigabitEthernet1/0/2] port trunk permit vlan 2 3 [SwitchA-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 as a trunk port, and assign it to VLAN 4 and VLAN 5. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] port link-type trunk [SwitchA-GigabitEthernet1/0/3] port trunk permit vlan 4 5...
  • Page 79 Multicast vlan 10 subvlan list: vlan 2-5 port list: no port # Display IGMP snooping multicast group information on Switch A. [SwitchA] display igmp-snooping group Total 5 IP Group(s). Total 5 IP Source(s). Total 5 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):2.

  • Page 80: Port-Based Multicast Vlan Configuration Example

    Router port(s):total 0 port(s). IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Host port(s):total 1 port(s). GE1/0/3 MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 1 port(s). GE1/0/3 Vlan(id):5. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s).
  • Page 81 • The multicast source sends multicast data to the multicast group 224.1.1.1. Host A, Host B, and Host C are receivers of the multicast data, and the hosts belong to VLAN 2 through VLAN 4 respectively. Configure the port-based multicast VLAN feature on Switch A to meet the following requirements: •...
  • Page 82 [SwitchA-vlan10] quit # Create VLAN 2, and enable IGMP snooping in the VLAN. [SwitchA] vlan 2 [SwitchA-vlan2] igmp-snooping enable [SwitchA-vlan2] quit # Create VLAN 3 and enable IGMP snooping in the VLAN. (Details not shown.) # Create VLAN 4 and enable IGMP snooping in the VLAN. (Details not shown.) # Configure GigabitEthernet 1/0/2 as a hybrid port, and configure VLAN 2 as the PVID of the hybrid port.
  • Page 83 Total 1 MAC Group(s). Router port(s):total 1 port(s). GE1/0/1 IP group(s):the following ip group(s) match to one mac group. IP group address:224.1.1.1 (0.0.0.0, 224.1.1.1): Host port(s):total 3 port(s). GE1/0/2 GE1/0/3 GE1/0/4 MAC group(s): MAC group address:0100-5e01-0101 Host port(s):total 3 port(s). GE1/0/2 GE1/0/3 GE1/0/4...

  • Page 84: Configuring Multicast Routing And Forwarding

    Configuring multicast routing and forwarding This chapter describes multicast routing and forwarding, how to configure multicast routing and forwarding, configuration examples, and troubleshooting methods. Hardware compatibility To use GRE related features on the switches, you must install SD or EB cards. Overview In multicast implementations, the following types of tables implement multicast routing and forwarding:...
  • Page 85 The specific process of RPF check is as follows: The router chooses an optimal route from the unicast routing table, the MBGP routing table, and the static multicast routing table, respectively: The router searches its unicast routing table and automatically chooses an optimal unicast route to the packet source address.

  • Page 86: Static Multicast Routes

    • If a match is found but the receiving interface is not the incoming interface of the entry, the router determines the RPF route back to the packet source. Then, it makes the following judgments: If the RPF interface of the RPF route is the incoming interface, it means that the forwarding entry is correct but the packet traveled along a wrong path.
  • Page 87 Figure 27 Changing an RPF route As shown in Figure 27, when no static multicast route is configured, Switch C's RPF neighbor on the path back to the source is Switch A. The multicast information from the source travels along the path from Switch A to Switch C, which is the unicast route between the two switches.

  • Page 88: Multicast Forwarding Across Unicast Subnets

    To make sure that the maximum transmission unit (MTU) feature operates properly in multicast forwarding through GRE tunnels, configure the same MTU value for all Tunnel interfaces on an HPE 5820X switch or HPE 5800 switch. For more information about MTU configuration on a Tunnel interface, see Layer 3—IP Services Configuration Guide.

  • Page 89: Configuration Task List

    Concepts in multicast traceroute • Last-hop router—If one of the interfaces of a router connects to the subnet that contains the given destination address, and if the router can forward multicast streams from the given multicast source onto that subnet, that router is called the "last-hop router." The given destination address and the given multicast source are specified in the mtracert command.

  • Page 90: Enabling Ip Multicast Routing

    NOTE: • The switch periodically sends a PIM hello message to PIM routers on the subnets represented by its primary address to establish and maintain PIM neighbor relationships. The hello message carries a list of secondary IP addresses, which is obtained and maintained by other PIM neighbors as next hops of multicast routes.

  • Page 91: Configuring Static Multicast Routes

    Configuring static multicast routes By configuring a static multicast route for a given multicast source, you can specify an RPF interface or an RPF neighbor for multicast traffic from that source. If you want to remove a specific static multicast route, use the undo ip rpf-route-static command. If you want to remove all static multicast routes, use the delete ip rpf-route-static command.

  • Page 92: Configuring A Multicast Forwarding Range

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

  • Page 93: Tracing A Multicast Path

    Configure the maximum multicast forwarding-table By default, the upper limit is 4000 number of entries in the route-limit limit for the HPE 5800 switches, and multicast forwarding table. 2000 for the HPE 5820X switches. Configure the maximum Optional. number of downstream...

  • Page 94: Displaying And Maintaining Multicast Routing And Forwarding

    Step Command Remarks Enable multicast By default, the multicast multicast-optimization enable optimization. optimization feature is disabled. NOTE: Enabling the multicast optimization feature reduces the efficiency of establishing multicast forwarding entries. Displaying and maintaining multicast routing and forwarding CAUTION: The reset commands might cause multicast data transmission failures. To display and maintain multicast routing and forwarding: Task Command...

  • Page 95: Multicast Routing And Forwarding Configuration Examples

    Task Command Remarks specified multicast source. [ group-address ] [ | { begin | exclude | include } regular-expression ] Available in user view. reset multicast [ all-instance | vpn-instance When a multicast vpn-instance-name ] forwarding-table Clear forwarding entries forwarding entry is { { source-address [ mask { mask | mask-length } ] | from the multicast removed, the...
  • Page 96 Figure 30 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 30. (Details not shown.) Configure OSPF on the switches in the PIM-DM domain to meet the following requirements: (Details not shown.) The switches are interoperable at the network layer.

  • Page 97: Rpf Route Creation Configuration Example

    [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit # Enable IP multicast routing and PIM-DM on Switch C in the same way Switch A is configured. (Details not shown.) Display the RPF route to Source on Switch B. [SwitchB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: Vlan-interface102, RPF neighbor: 30.1.1.2...
  • Page 98 Figure 31 Network diagram PIM-DM OSPF domain Switch A Switch B Switch C Vlan-int102 Vlan-int102 Vlan-int101 30.1.1.2/24 30.1.1.1/24 20.1.1.1/24 Vlan-int101 20.1.1.2/24 Vlan-int300 Vlan-int200 Vlan-int100 50.1.1.1/24 40.1.1.1/24 10.1.1.1/24 Source 2 Source 1 Receiver 50.1.1.100/24 40.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 31.

  • Page 99: Multicast Forwarding Over A Gre Tunnel

    [SwitchB] display multicast rpf-info 50.1.1.100 [SwitchC] display multicast rpf-info 50.1.1.100 No information is displayed, because no RPF route to the source 2 exists on Switch B or Switch Configure a static multicast route: # Configure a static multicast route on Switch B, and specify Switch A as its RPF neighbor on the route to Source 2.
  • Page 100 Figure 32 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 32. (Details not shown.) Configure a GRE tunnel: # Create service loopback group 1 on Switch A, and specify its service type as Tunnel. <SwitchA>...
  • Page 101 [SwitchC-GigabitEthernet1/0/3] undo ndp enable [SwitchC-GigabitEthernet1/0/3] undo lldp enable [SwitchC-GigabitEthernet1/0/3] port service-loopback group 1 [SwitchC-GigabitEthernet1/0/3] quit # Create interface Tunnel 0 on Switch C, configure the IP address and subnet mask for the interface, and reference service loopback group 1 on interface Tunnel 0. [SwitchC] interface tunnel 0 [SwitchC-Tunnel0] ip address 50.1.1.2 24 [SwitchC-Tunnel0] service-loopback-group 1...
  • Page 102 [SwitchA-Vlan-interface101] quit [SwitchA] interface tunnel 0 [SwitchA-Tunnel0] pim dm [SwitchA-Tunnel0] quit # On Switch C, enable multicast routing globally, enable PIM-DM on each interface, and enable IGMP on VLAN-interface 200. [SwitchC] multicast routing-enable [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] pim dm [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 102...

  • Page 103: Troubleshooting Multicast Routing And Forwarding

    The output shows that Switch A is the RPF neighbor of Switch C and the multicast data from Switch A is delivered over a GRE tunnel to Switch C. Troubleshooting multicast routing and forwarding This section describes details about troubleshooting multicast routing and forwarding. Static multicast route failure Symptom No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of...

  • Page 104: Configuring Igmp

    Configuring IGMP This chapter describes IGMP, how to configure IGMP, configuration examples, and troubleshooting methods. Overview As a TCP/IP protocol responsible for IP multicast group member management, the IGMP is used by IP hosts and adjacent multicast routers to establish and maintain their multicast group memberships. The term "interface"...
  • Page 105 Figure 33 IGMP queries and reports As shown in Figure 33, Host B and Host C are interested in multicast data addressed to multicast group G1. Host A is interested in multicast data addressed to G2. The following process describes how the hosts join the multicast groups and how the IGMP querier (Router B in the figure) maintains the multicast group memberships: The hosts send unsolicited IGMP reports to the addresses of the multicast groups that they...

  • Page 106: Igmpv2 Enhancements

    IGMPv2 enhancements Compared with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism. Querier election mechanism In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) serves as the querier among multiple routers on the same subnet. IGMPv2 introduced an independent querier election mechanism.
  • Page 107 As shown in Figure 34, the network has two multicast sources, Source 1 (S1) and Source 2 (S2). Both of them can send multicast data to multicast group G. Host B is interested in the multicast data that the source 1 sends to G but not in the data from the source 2. Figure 34 Flow paths of source-and-group-specific multicast traffic In IGMPv1 or IGMPv2, Host B cannot select multicast sources when it joins multicast group G.

  • Page 108: Igmp Ssm Mapping

    BLOCK—The Source Address fields contain a list of the sources from which the receiver no longer wants to obtain data. If the current filtering mode is Include, these sources are deleted from the multicast source list. If the current filtering mode is Exclude, these sources are added to the multicast source list.

  • Page 109: Igmp Proxying

    For more information about the SSM group range, see "Configuring PIM." IGMP proxying In some simple tree-shaped topologies, it is not necessary to configure complex multicast routing protocols, such as PIM, on the edge devices. Instead, you can configure IGMP proxying on these devices.

  • Page 110: Protocols And Standards

    runs in a VPN needs to exchange information with another multicast protocol, it passes the information only to the protocol that runs in this VPN. Protocols and standards • RFC 1112, Host Extensions for IP Multicasting • RFC 2236, Internet Group Management Protocol, Version 2 •...

  • Page 111: Configuration Prerequisites

    Configuration prerequisites Before you configure basic IGMP functions, complete the following tasks: • Configure any unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Configure PIM-DM or PIM-SM. • Determine the IGMP version. •...

  • Page 112: Specifying Igmp Versions

    Specifying IGMP versions Because the protocol packets of different IGMP versions vary in structure and type, you must configure the same IGMP version for all routers on the same subnet. Otherwise, IGMP cannot work properly. Specifying an IGMP version globally Step Command Remarks...

  • Page 113: Configuring A Multicast Group Filter

    Enter interface view. interface-number Configure the maximum By default, the upper limit is 4000 for the number of multicast groups HPE 5800 switches, and 2000 for the igmp group-limit limit that the interface can join. HPE 5820X switches. NOTE: This configuration only limits the number of multicast groups that the interface dynamically joins.

  • Page 114: Configuring Router-Alert Option Handling Methods

    • Determine the startup query interval. • Determine the startup query count. • Determine the IGMP general query interval. • Determine the IGMP querier's robustness variable. • Determine the maximum response time for IGMP general queries. • Determine the IGMP last-member query interval. •...

  • Page 115: Configuring Igmp Query And Response Parameters

    Step Command Remarks Enable insertion of the By default, IGMP messages carry Router-Alert option into igmp send-router-alert the Router-Alert option. IGMP messages. Configuring IGMP query and response parameters On startup, the IGMP querier sends IGMP general queries at the startup query interval, which is one-quarter of the IGMP general query interval.
  • Page 116 Step Command Remarks view. 2 by default. A higher robustness variable Configure the IGMP querier's robust-count robust-value makes the IGMP querier more robustness variable. robust, but results in longer multicast group timeout time. By default, the startup query Configure the startup query interval is one-quarter of the startup-query-interval interval interval.

  • Page 117: Enabling Igmp Fast-Leave Processing

    Step Command Remarks By default, the other querier present interval is [ IGMP general Configure the other querier query interval ] × [ IGMP igmp timer present interval. robustness variable ] + [ maximum other-querier-present interval response time for IGMP general queries ] / 2.

  • Page 118: Setting The Dscp Value For Igmp Messages

    Enabling the IGMP host tracking function globally Step Command Remarks Enter system view. system-view Enter public network IGMP igmp [ vpn-instance view/VPN instance IGMP vpn-instance-name ] view. Enable the IGMP host Disabled by default. host-tracking tracking function globally. Enabling the IGMP host tracking function on an interface Step Command Remarks...

  • Page 119: Enabling Ssm Mapping

    Enabling SSM mapping Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable the IGMP SSM Disabled by default. igmp ssm-mapping enable mapping feature. NOTE: To ensure SSM service for all hosts on a subnet, regardless of the IGMP version running on the hosts, enable IGMPv3 on the interface that forwards multicast traffic onto the subnet.

  • Page 120: Enabling Igmp Proxying

    Enabling IGMP proxying You can enable IGMP proxying on the interface in the direction toward the root of the multicast forwarding tree to make the device serve as an IGMP proxy. Configuration guidelines • Each device can have only one interface serving as the proxy interface. In scenarios with multiple instances, IGMP proxying is configured on only one interface per instance.

  • Page 121: Displaying And Maintaining Igmp

    Displaying and maintaining IGMP CAUTION: The reset igmp group command might cause an interruption of receivers' reception of multicast data. To display and maintain IGMP: Task Command Remarks display igmp [ all-instance | vpn-instance vpn-instance-name ] group [ group-address | interface Display IGMP group information.

  • Page 122: Igmp Configuration Examples

    Task Command Remarks display igmp [ all-instance | vpn-instance vpn-instance-name ] Display IGMP SSM mappings. Available in any view. ssm-mapping group-address [ | { begin | exclude | include } regular-expression ] display igmp [ all-instance | vpn-instance Display the multicast group vpn-instance-name ] information created from IGMPv1 ssm-mapping group...
  • Page 123 • Receivers receive VOD information through multicast. • Receivers of different organizations form stub networks N1 and N2, and Host A and Host C are receivers in N1 and N2, respectively. • Switch A in the PIM network connects to N1, and both Switch B and Switch C connect to N2. •...

  • Page 124: Ssm Mapping Configuration Example

    # On Switch B, enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on VLAN-interface 200. <SwitchB> system-view [SwitchB] multicast routing-enable [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] pim dm [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 201 [SwitchB-Vlan-interface201] pim dm [SwitchB-Vlan-interface201] quit # On Switch C, enable IP multicast routing, enable PIM-DM on each interface, and enable...
  • Page 125 • Switch D's VLAN-interface 104 serves as the C-BSR and C-RP. The SSM group range is 232.1.1.0/24. IGMPv3 runs on Switch D's VLAN-interface 400. The receiver host runs IGMPv2, and does not support IGMPv3. Therefore, the receiver host cannot specify expected multicast sources in its membership reports.
  • Page 126 # On Switch D, enable IP multicast routing, enable IGMPv3 and IGMP SSM mapping on VLAN-interface 400, and enable PIM-SM on each interface <SwitchD> system-view [SwitchD] multicast routing-enable [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] igmp enable [SwitchD-Vlan-interface400] igmp version 3 [SwitchD-Vlan-interface400] igmp ssm-mapping enable [SwitchD-Vlan-interface400] pim sm [SwitchD-Vlan-interface400] quit [SwitchD] interface vlan-interface 103...
  • Page 127 [SwitchD-igmp] ssm-mapping 232.1.1.0 24 133.133.3.1 [SwitchD-igmp] quit Verifying the configuration # Display the IGMP SSM mapping information for multicast group 232.1.1.1 on Switch D. [SwitchD] display igmp ssm-mapping 232.1.1.1 Vpn-Instance: public net Group: 232.1.1.1 Source list: 133.133.1.1 133.133.3.1 # Display information about the IGMP groups created based on the IGMP SSM mappings on Switch [SwitchD] display igmp ssm-mapping group Total 1 IGMP SSM-mapping Group(s).

  • Page 128: Igmp Proxying Configuration Example

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

  • Page 129: Troubleshooting Igmp

    [SwitchB-Vlan-interface200] quit Verifying the configuration # Display IGMP information on VLAN-interface 100 of Switch B. [SwitchB] display igmp interface vlan-interface 100 verbose Vlan-interface100(192.168.1.2): IGMP proxy is enabled Current IGMP version is 2 Multicast routing on this interface: enabled Require-router-alert: disabled Version1-querier-present-timer-expiry: 00:00:20 # Display IGMP group information on Switch A.

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

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

  • Page 131: Configuring Pim

    Configuring PIM This chapter describes PIM, how to configure PIM, configuration examples, and troubleshooting methods. Overview PIM provides IP multicast forwarding by leveraging unicast static routes or unicast routing tables generated by any unicast routing protocol, such as RIP, OSPF, IS-IS, or BGP. Independent of the unicast routing protocols running on the device, multicast routing can be implemented as long as the corresponding multicast routing entries are created through unicast routes.
  • Page 132 Neighbor discovery In a PIM domain, a PIM router discovers PIM neighbors and maintains PIM neighboring relationships with other routers. It also builds and maintains SPTs by periodically multicasting hello messages to all other PIM routers (224.0.0.13) on the local subnet. Every PIM-enabled interface on a router sends hello messages periodically, and thus learns the PIM neighboring information pertinent to the interface.

  • Page 133: Pim-Sm

    Graft A previously pruned branch might have new downstream receivers. To reduce the latency for resuming the forwarding capability of this branch, a graft mechanism is used as follows: The node that needs to receive multicast data sends a graft message toward its upstream node, as a request to join the SPT again.
  • Page 134 PIM-SM is a type of sparse mode multicast protocol. It uses the pull mode for multicast forwarding, and is suitable for large-sized and medium-sized networks with sparsely and widely distributed multicast group members. The basic implementation of PIM-SM is as follows: •...
  • Page 135 Figure 42 DR election As shown in Figure 42, the DR election process is as follows: Routers on the multi-access network send hello messages to one another. The hello messages contain the router priority for DR election. The router with the highest DR priority becomes the The router with the highest IP address wins the DR election under one of following conditions: All the routers have the same DR election priority.
  • Page 136 Figure 43 Information exchange between C-RPs and the BSR Based on the information in the RP-sets, all routers in the network can select the proper RP for a specific multicast group based on the following rules: The C-RP that is designated to the smallest multicast group range wins. If the C-RPs are designated to the same multicast group range, the C-RP with the highest priority wins.
  • Page 137 RPT building Figure 44 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 44, the process of building an RPT is as follows: When a receiver joins multicast group G, it uses an IGMP message to inform the directly connected DR.
  • Page 138 Figure 45 Multicast source registration As shown in Figure 45, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to multicast group G. When receiving the multicast packet, the DR that directly connects to the multicast source encapsulates the packet in a PIM register message.

  • Page 139: Bidir-Pim

    After receiving the first multicast packet, the RP sends an (S, G) join message hop by hop toward the multicast source to establish an SPT between the DR at the source side and the RP. Subsequent multicast data travels along the established SPT to the RP. For more information about the switchover to SPT initiated by the RP, see "Multicast source registration."...
  • Page 140 NOTE: In BIDIR-PIM, an RPF interface is the interface pointing to an RP, and an RPF neighbor is the address of the next hop to the RP. DF election On a subnet with multiple multicast routers, the same multicast packets might be forwarded to the RP repeatedly.
  • Page 141 Figure 47 RPT building at the receiver side As shown in Figure 47, the process for building a receiver-side RPT is similar to that for building an RPT in PIM-SM: When a receiver joins multicast group G, it uses an IGMP message to inform the directly connected router.

  • Page 142: Administrative Scoping

    Figure 48 RPT building at the multicast source side As shown in Figure 48, the process for building a source-side RPT is relatively simple: When a multicast source sends multicast packets to multicast group G, the DF in each network segment unconditionally forwards the packets to the RP.
  • Page 143 multicast groups within a specific range. Multicast protocol packets, such as assert messages and bootstrap messages, for a specific group range cannot cross the admin-scope zone boundary. Multicast group ranges that different admin-scope zones serve can be overlapped. A multicast group is valid only within its local admin-scope zone, and functions as a private group address.

  • Page 144: Pim-Ssm

    Figure 50 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 Figure 50, 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 145: Relationship Among Pim Protocols

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

  • Page 146: Pim Support For Vpns

    Figure 52 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 147: Pim-Dm Configuration Task List

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

  • Page 148: Enabling State-Refresh Capability

    Step Command Remarks enter VPN instance view. vpn-instance-name Configure an RD for the VPN route-distinguisher Not configured by default. instance. route-distinguisher Enable IP multicast routing. Disabled by default. multicast routing-enable interface interface-type Enter interface view. interface-number By default, an interface belongs to Bind the interface with a VPN ip binding vpn-instance the public network, and is not...

  • Page 149: Configuring Pim-Dm Graft Retry Period

    Step Command Remarks Enter system view. system-view Enter public network PIM view or pim [ vpn-instance VPN instance PIM view. vpn-instance-name ] Optional. Configure the interval between state-refresh-interval interval state-refresh messages. 60 seconds by default. Configure the time to wait before Optional.

  • Page 150: Configuration Prerequisites

    Task Remarks Configuring a PIM domain border Optional. Configuring the global C-BSR parameters Optional. Configuring C-BSR timers Optional. Disabling BSM semantic fragmentation Optional. Enabling administrative scoping Optional. Configuring an admin-scope zone boundary Optional. Configuring administrative scoping Configuring C-BSRs for each admin-scope Optional.

  • Page 151: Configuring An Rp

    Enabling PIM-SM globally on the public network Step Command Remarks Enter system view. system-view Enable IP multicast routing. Disabled by default. multicast routing-enable interface interface-type Enter interface view. interface-number Enable PIM-SM. Disabled by default. pim sm Enabling PIM-SM in a VPN instance Step Command Remarks...
  • Page 152 Step Command Remarks Enter system view. system-view Enter public network PIM pim [ vpn-instance view or VPN instance PIM vpn-instance-name ] view. Configure a static RP for static-rp rp-address [ acl-number ] No static RP exists by default. PIM-SM. [ preferred ] Configuring a C-RP In a PIM-SM domain, you can configure routers that intend to become the RP as C-RPs.

  • Page 153: Configuring A Bsr

    Configuring C-RP timers globally To enable the BSR to distribute the RP-set information within the PIM-SM domain, C-RPs must periodically send C-RP-Adv messages to the BSR. The BSR learns the RP-set information from the received messages, and encapsulates its own IP address together with the RP-set information in its bootstrap messages.
  • Page 154 hosts are outside the network. To protect a BSR against external attacks, you can enable the border routers to do the following: Perform neighbor checks and RPF checks on BSMs. Discard unwanted messages. • When an attacker controls a router on the network, the attacker can configure the router as a C-BSR to win the BSR election.
  • Page 155 Configuring the global C-BSR parameters In each PIM-SM domain, a unique BSR is elected from C-BSRs. The C-RPs in the PIM-SM domain send advertisement messages to the BSR. The BSR summarizes the advertisement messages to form an RP-set and advertises it to all routers in the PIM-SM domain. All routers use the same hash algorithm to get the RP address that corresponds to specific multicast groups.

  • Page 156: Configuring Administrative Scoping

    Step Command Remarks 130 seconds, so the default BS period is (130 – 10) / 2 = 60 (seconds). The BS period value must be smaller than the BS timeout timer. Optional. By default, the BS timeout timer is determined by the formula "BS Configure the BS timeout timeout timer = BS period ×...
  • Page 157 specific multicast group range. The global scope zone also maintains a BSR, which serves the remaining multicast groups. Enabling administrative scoping Before you configure an admin-scope zone, you must enable administrative scoping. Perform the following configuration on all routers in the PIM-SM domain. To enable administrative scoping: Step Command...

  • Page 158: Configuring Multicast Source Registration

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

  • Page 159: Disabling Switchover To Spt

    multicast data) to the RP. If the DR receives a register-stop message during the register probe time, it resets its register-stop timer. Otherwise, the DR starts sending register messages with encapsulated data again when the register-stop timer expires. The register-stop timer is set to a random value chosen uniformly from the interval (0.5 times register_suppression_time, 1.5 times register_suppression_time) minus register_probe_time.

  • Page 160: Configuring Bidir-Pim

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

  • Page 161: Enabling Pim-Sm

    Enabling PIM-SM Because BIDIR-PIM is implemented on the basis of PIM-SM, you must enable PIM-SM before enabling BIDIR-PIM. To deploy a BIDIR-PIM domain, enable PIM-SM on all non-border interfaces of the domain. Enabling PIM-SM globally for the public network Step Command Remarks Enter system view.

  • Page 162: Configuring An Rp

    Step Command Remarks view or VPN instance PIM vpn-instance-name ] view. Enable BIDIR-PIM. Disabled by default. bidir-pim enable Configuring an RP CAUTION: When both PIM-SM and BIDIR-PIM run on the PIM network, do not use the same RP to serve PIM-SM and BIDIR-PIM.
  • Page 163 Step Command Remarks Enter system view. system-view Enter public network PIM pim [ vpn-instance view or VPN instance PIM vpn-instance-name ] view. c-rp interface-type interface-number [ group-policy acl-number | priority Configure an interface to be No C-RP is configured by priority | holdtime hold-interval | a C-RP for BIDIR-PIM.

  • Page 164: Configuring A Bsr

    Configuring a BSR A BIDIR-PIM domain can have only one BSR, but must have at least one C-BSR. Any router can be configured as a C-BSR. Elected from C-BSRs, the BSR collects and advertises RP information in the BIDIR-PIM domain. Configuring a C-BSR C-BSRs must be configured on routers in the backbone network.
  • Page 165 Step Command Remarks range by default. Configuring a BIDIR-PIM domain border As the administrative core of a BIDIR-PIM domain, the BSR sends the collected RP-Set information in the form of bootstrap messages to all routers in the BIDIR-PIM domain. A BIDIR-PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope.
  • Page 166 Configuring C-BSR timers The BSR election winner multicasts its own IP address and RP-Set information through bootstrap messages within the entire zone it serves. The BSR floods bootstrap messages throughout the network at the interval of BS (BSR state) period. Any C-BSR that receives a bootstrap message retains the RP-set for the length of BS timeout timer, during which no BSR election takes place.

  • Page 167: Configuring Administrative Scoping

    The function of BSM semantic fragmentation is enabled by default. Devices not supporting this function might deem a fragment as an entire message, thus learning only part of the RP-set information. Therefore, if such devices exist in the BIDIR-PIM domain, you must disable the semantic fragmentation function on the C-BSRs.
  • Page 168 Step Command Remarks mask-length } configured. The group-address { mask | mask-length } argument can specify the multicast groups that an admin-scope zone serves, in the range of 239.0.0.0/8. Configuring C-BSRs for each admin-scope zone and the global-scope zone In a network with administrative scoping enabled, group-range-specific BSRs are elected from C-BSRs.

  • Page 169: Configuring Pim-Ssm

    Step Command Remarks view. vpn-instance-name ] Configure a C-BSR for the c-bsr global [ hash-length No C-BSRs are configured for the global-scope zone. hash-length | priority priority ] * global-scope zone by default. Configuring PIM-SSM This section describes how to configure PIM-SSM. PIM-SSM needs the support of IGMPv3.

  • Page 170: Configuring The Ssm Group Range

    IMPORTANT: All interfaces in the same VPN instance on the same device must be configured with the same PIM mode. To enable PIM-SM in a VPN instance: Step Command Remarks Enter system view. system-view Create a VPN instance and ip vpn-instance enter VPN instance view.

  • Page 171: Configuring Common Pim Features

    Step Command Remarks Enter public network PIM pim [ vpn-instance view or VPN instance PIM vpn-instance-name ] view. Optional. Configure the SSM group ssm-policy acl-number range. 232.0.0.0/8 by default. Configuring common PIM features For the configuration tasks in this section, the following rules apply: •...

  • Page 172: Configuring A Multicast Data Filter

    • Determine the assert timeout timer (global value/interface value). • Determine the join/prune interval (global value/interface level value). • Determine the join/prune timeout (global value/interface value). • Determine the multicast source lifetime. • Determine the maximum size of join/prune messages. •...

  • Page 173: Configuring Pim Hello Options

    NOTE: When the hello message filter is configured, if hello messages of an existing PIM neighbor fail to pass the filter, the PIM neighbor will be removed automatically when it times out. Configuring PIM hello options In either a PIM-DM domain or a PIM-SM domain, the hello messages sent among routers contain the following configurable options: •...

  • Page 174: Configuring The Prune Delay

    Step Command Remarks (LAN-delay). 500 milliseconds by default. Optional. Configure the prune override hello-option override-interval interval. interval 2500 milliseconds by default. Disable join suppression. Enabled by default. hello-option neighbor-tracking Configuring hello options on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 175: Configuring Common Pim Timers

    Configuring common PIM timers PIM routers discover PIM neighbors and maintain PIM neighboring relationships with other routers by periodically sending hello messages. After receiving a hello message, a PIM router waits a random period, which is smaller than the maximum delay between hello messages, before sending a hello message. This delay avoids collisions that occur when multiple PIM routers send hello messages simultaneously.

  • Page 176: Configuring Join/Prune Message Sizes

    Step Command Remarks Configure the maximum Optional. pim triggered-hello-delay delay between hello interval 5 seconds by default. messages. Optional. Configure the join/prune pim timer join-prune interval interval. 60 seconds by default. Optional. Configure the join/prune pim holdtime join-prune interval timeout timer. 210 seconds by default.

  • Page 177: Setting The Dscp Value For Pim Messages

    To enable PIM to work with BFD: Step Command Remarks Enter system view. system-view Enter interface view. interface interface-type interface-number Enable PIM to work Disabled by default. pim bfd enable with BFD. For more information about BFD, see High Availability Configuration Guide. Setting the DSCP value for PIM messages Step Command...
  • Page 178 Task Command Remarks vpn-instance-name ] df-info [ rp-address ] [ | { begin | exclude | include } regular-expression ] display pim [ all-instance | Display the information about vpn-instance unacknowledged PIM-DM graft vpn-instance-name ] grafts [ | Available in any view. messages.

  • Page 179: Pim Configuration Examples

    Task Command Remarks interface-number ] PIM configuration examples This section describes details about PIM configuration examples. PIM-DM configuration example Network requirements As shown in Figure • Receivers receive VOD information through multicast. • The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network.
  • Page 180 Device Interface IP address Device Interface IP address Switch VLAN-interface 10.110.2.2/24 VLAN-interface 192.168.3.1/24 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 53. (Details not shown.) Configure OSPF on the switches in the PIM-DM domain to make sure they are interoperable at the network layer.
  • Page 181 Vlan101 192.168.2.2 (local) Vlan102 192.168.3.2 (local) # Display the PIM neighboring relationships on Switch D. [SwitchD] display pim neighbor VPN-Instance: public net Total Number of Neighbors = 3 Neighbor Interface Uptime Expires Dr-Priority 192.168.1.1 Vlan103 00:02:22 00:01:27 1 192.168.2.1 Vlan101 00:00:22 00:01:29 3 192.168.3.1 Vlan102...

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

    (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: LOC ACT UpTime: 00:03:27 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 2 1: Vlan-interface103 Protocol: pim-dm, UpTime: 00:03:27, Expires: never 2: Vlan-interface102 Protocol: pim-dm, UpTime: 00:03:27, Expires: never PIM-SM non-scoped zone configuration example Network requirements As shown in...
  • Page 183 Figure 54 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 10.110.5.100/24 Vlan-int104 Vlan-int200 PIM-SM Host D Switch C Device Interface IP address Device...
  • Page 184 [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [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 Switch A is configured.
  • Page 185 Hash mask length: 32 State: Accept Preferred Scope: Not scoped Uptime: 00:40:40 Expires: 00:01:42 # Display information about the BSR and locally configured C-RP in effect on Switch D. [SwitchD] display pim bsr-info VPN-Instance: public net Elected BSR Address: 192.168.9.2 Priority: 20 Hash mask length: 32 State: Accept Preferred...
  • Page 186 [SwitchA] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 225.1.1.0/24 RP: 192.168.4.2 Priority: 192 HoldTime: 150 Uptime: 00:51:45 Expires: 00:02:22 RP: 192.168.9.2 Priority: 192 HoldTime: 150 Uptime: 00:51:45 Expires: 00:02:22 Assume that Host A needs to receive information addressed to the multicast group G 225.1.1.0. The RP corresponding to the multicast group G is Switch E as a result of hash calculation, so an RPT is built between Switch A and Switch E.

  • Page 187: Pim-Sm Admin-Scope Zone Configuration Example

    1: Vlan-interface100 Protocol: pim-sm, UpTime: 00:00:42, Expires: 00:03:06 The information on Switch B and Switch C is similar to that on Switch A. # Display PIM routing table information on Switch D. [SwitchD] display pim routing-table VPN-Instance: public net Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 225.1.1.0) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT LOC ACT...
  • Page 188 • VLAN-interface 101 of Switch B acts as a C-BSR and C-RP of admin-scope zone 1, which serve the multicast group range 239.0.0.0/8. VLAN-interface 104 of Switch D acts as a C-BSR and C-RP of admin-scope zone 2, which also serve the multicast group range 239.0.0.0/8. VLAN-interface 109 of Switch F acts as C-BSRs and C-RPs of the global scope zone, which serve all multicast groups other than those in the 239.0.0.0/8 range.
  • Page 189 Device Interface IP address Device Interface IP address VLAN-interface 110 10.110.10.2/24 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 55. (Details not shown.) Configure OSPF on the switches in the PIM-SM domain to make sure they are interoperable at the network layer.
  • Page 190 # On Switch B, configure VLAN-interface 102 and VLAN-interface 103 to be the boundary of admin-scope zone 1. [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] multicast boundary 239.0.0.0 8 [SwitchB-Vlan-interface102] quit [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchB-Vlan-interface103] quit # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 to be the boundary of admin-scope zone 2.
  • Page 191 [SwitchF-pim] quit Verifying the configuration # Display information about the BSR and locally configured C-RP on Switch B. [SwitchB] display pim bsr-info VPN-Instance: public net Elected BSR Address: 10.110.9.1 Priority: 64 Hash mask length: 30 State: Accept Preferred Scope: Global Uptime: 00:01:45 Expires: 00:01:25 Elected BSR Address: 10.110.1.2...
  • Page 192 Priority: 64 Hash mask length: 30 State: Elected Scope: 239.0.0.0/8 Candidate RP: 10.110.4.2(Vlan-interface104) Priority: 192 HoldTime: 150 Advertisement Interval: 60 Next advertisement scheduled at: 00:00:10 # Display information about the BSR and locally configured C-RP on Switch F. [SwitchF] display pim bsr-info VPN-Instance: public net Elected BSR Address: 10.110.9.1 Priority: 64...

  • Page 193: Bidir-Pim Configuration Example

    # Display RP information on Switch D. [SwitchD] display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 224.0.0.0/4 RP: 10.110.9.1 Priority: 192 HoldTime: 150 Uptime: 00:03:42 Expires: 00:01:48 Group/MaskLen: 239.0.0.0/8 RP: 10.110.4.2 (local) Priority: 192 HoldTime: 150 Uptime: 00:06:54 Expires: 00:02:41 # Display RP information on Switch F.
  • Page 194 Figure 56 Network diagram Loop0 Receiver 1 Receiver 2 Switch B Vlan-int200 Vlan-int102 Vlan-int102 Switch C Host A Host B Vlan-int101 Vlan-int103 BIDIR-PIM Source 1 Source 2 Vlan-int101 Vlan-int103 Vlan-int100 Vlan-int400 Switch A Switch D Device Interface IP address Device Interface IP address Switch A...
  • Page 195 [SwitchA-pim] bidir-pim enable [SwitchA-pim] quit # On Switch B, enable IP multicast routing, enable PIM-SM on each interface, enable IGMP in VLAN interface 200, and enable BIDIR-PIM. <SwitchB> system-view [SwitchB] multicast routing-enable [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] pim sm [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim sm...
  • Page 196 [SwitchD-pim] bidir-pim enable [SwitchD-pim] quit On Switch C, configure VLAN interface 102 as a C-BSR, and loopback interface 0 as a C-RP for the entire BIDIR-PIM domain. [SwitchC-pim] c-bsr vlan-interface 102 [SwitchC-pim] c-rp loopback 0 bidir [SwitchC-pim] quit Verifying the configuration # Display the DF information of BIDIR-PIM on Switch A.
  • Page 197 Total 1 RP matched 00001. RP Address: 1.1.1.1 MID: 0, Flags: 0x2100000:0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100 # Display the DF information of the multicast forwarding table on Switch B. [SwitchB] display multicast forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP Total 1 RP matched...

  • Page 198: Pim-Ssm Configuration Example

    List of 2 DF interfaces: 1: Vlan-interface300 2: Vlan-interface400 PIM-SSM configuration example Network requirements As shown in Figure • Receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire PIM domain operates in the SSM mode.
  • Page 199 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 57. (Details not shown.) Configure OSPF on the switches in the PIM-SSM domain to make sure they are interoperable at the network layer. (Details not shown.) Enable IP multicast routing, IGMP and PIM-SM: # On Switch A, enable IP multicast routing, enable IGMPv3 on VLAN-interface 100, and enable PIM-SM on each interface.

  • Page 200: Troubleshooting Pim

    # Display PIM routing table information on Switch A. [SwitchA] display pim routing-table VPN-Instance: public net Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:13:25 Upstream interface: Vlan-interface101 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100...

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

    • When PIM-SM runs on the entire network and when a router joins the SPT, the router creates (S, G) entries only if it has a route to the multicast source. If the router does not have a route to the multicast source, or if PIM-DM is not enabled on the router's RPF interface to the multicast source, the router cannot create (S, G) entries.

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

    Solution Use the display current-configuration command to verify the multicast forwarding boundary settings. Use the multicast boundary command to change the multicast forwarding boundary settings. Use the display current-configuration command to verify the multicast filter configuration. Change the ACL rule defined in the source-policy command so that the source/group address of the multicast data can pass ACL filtering.
  • Page 203 PIM-SM needs the support of the RP and BSR. Use the display pim bsr-info command to verify that the BSR information exists on each router, and then use the display pim rp-info command to verify that the RP information is correct on each router. Use the display pim neighbor command to verify that the normal PIM neighboring relationships have been established among the routers.

  • Page 204: Configuring Msdp

    Configuring MSDP This chapter describes MSDP, how to configure MSDP, configuration examples, and troubleshooting methods. Overview 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 about a domain is isolated from that of another domain.
  • Page 205 Figure 58 Where MSDP peers are in the network As shown in Figure 58, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers that assume different roles function differently. MSDP peers on RPs include the following types: Source-side MSDP peer—The MSDP peer nearest to the multicast source (Source), typically the source-side RP, like RP 1.
  • Page 206 Figure 59 Inter-domain multicast delivery through MSDP The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: When DR 1 in PIM-SM 1 receives the first multicast packet from the multicast source to multicast group G, DR 1 encapsulates the multicast data within a register message. It sends the register message to RP 1, and RP 1 obtains the information related to the multicast source.
  • Page 207 NOTE: An MSDP mesh group refers to a group of MSDP peers that have MSDP peering relationship among one another and share the same group name. RPF check rules for SA messages As shown in Figure • The autonomous systems in the network are AS 1 through AS 5. IGP is enabled on routers within each AS and BGP or MBGP as the interoperation protocol among the different ASs.
  • Page 208 When RP 6 receives the SA messages from RP 4 and RP 5 (suppose RP 5 has a higher IP address): RP 4 and RP 5 are in the same AS (AS 3) and both are MSDP peers of RP 6. RP 6 accepts only the SA message from RP 5, because RP 5 has a higher IP address.

  • Page 209: Msdp Support For Vpns

    The multicast source registers with the nearest RP. In this example, Source registers with RP 1, with its multicast data encapsulated in the register message. When the register message arrives at RP 1, RP 1 de-encapsulates the message. Receivers send join messages to the nearest RP to join in the RPT rooted as this RP. In this example, Receiver joins the RPT rooted at RP 2.

  • Page 210: Msdp Configuration Task List

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

  • Page 211: Creating An Msdp Peer Connection

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

  • Page 212: Configuring An Msdp Peer Connection

    Step Command Remarks No static RPF peer configured by static-rpf-peer peer-address Configure a static RPF peer. [ rp-policy ip-prefix-name ] default. NOTE: If only one MSDP peer is configured on a router, this MSDP will be registered as a static RPF peer. Configuring an MSDP peer connection This section describes how to configure an MSDP peer connection.

  • Page 213: Configuring Msdp Peer Connection Control

    By configuring the same mesh group name for multiple MSDP peers, you can create a mesh group that contains these MSDP peers. Before grouping multiple routers into an MSDP mesh group, make sure that these routers are interconnected with one another. To create an MSDP mesh group: Step Command...

  • Page 214: Configuring Sa Message Related Parameters

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

  • Page 215: Configuring Sa Request Messages

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

  • Page 216: Configuring The Sa Cache Mechanism

    threshold, the router encapsulates the multicast data in an SA message and sends the SA message. • After receiving an SA message with an encapsulated multicast data packet, the router decreases the TTL value of the multicast packet by 1 and then examines the TTL value. If the TTL value is less than the threshold, the router does not forward the SA message to the designated MSDP peer.

  • Page 217: Displaying And Maintaining Msdp

    Displaying and maintaining MSDP Task Command Remarks display msdp [ all-instance | vpn-instance Display the brief information of vpn-instance-name ] brief [ state { connect | Available in any view. MSDP peers. down | listen | shutdown | up } ] [ | { begin | exclude | include } regular-expression ] display msdp [ all-instance | vpn-instance Display the detailed information...
  • Page 218 Figure 62 Network diagram Device Interface IP address Device Interface IP address Switch A VLAN-interface 10.110.1.2/24 Switch VLAN-interface 10.110.4.2/24 VLAN-interface 10.110.2.1/24 VLAN-interface 10.110.5.1/24 VLAN-interface 10.110.3.1/24 Switch E VLAN-interface 10.110.6.1/24 Switch B VLAN-interface 10.110.1.1/24 VLAN-interface 192.168.3.2/24 VLAN-interface 192.168.1.1/24 Loop0 3.3.3.3/32 Loop0 1.1.1.1/32 Switch F VLAN-interface...
  • Page 219 Enable IP multicast routing, enable PIM-SM on each interface, and configure a PIM-SM domain border: # On Switch A, enable IP multicast routing, enable PIM-SM on each interface, and enable IGMP on the host-side interface VLAN-interface 200. <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim sm [SwitchA-Vlan-interface103] quit...
  • Page 220 [SwitchB-ospf-1] quit # Redistribute BGP routes into OSPF on Switch C. [SwitchB] ospf 1 [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.
  • Page 221 h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Network NextHop LocPrf PrefVal Path/Ogn * > 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 * >...

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

    Number of sent/received messages: 16/16 Number of discarded output messages: 0 Elapsed time since last connection or counters clear: 00:17:51 Information about (Source, Group)-based SA filtering policy: Import policy: none Export policy: none Information about SA-Requests: Policy to accept SA-Request messages: 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: none...
  • Page 223 Figure 63 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 224 [SwitchC-Vlan-interface102] pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] pim sm [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim sm [SwitchC-Vlan-interface104] quit # Enable IP multicast routing, PIM-SM, and IGMP on Switch A, Switch B, Switch D, Switch E, Switch F, and Switch G in the same way.
  • Page 225 [SwitchF-bgp] peer 10.110.4.1 as-number 100 [SwitchF-bgp] import-route ospf 1 [SwitchF-bgp] quit # Redistribute BGP routing information into OSPF on Switch B. [SwitchB] ospf 1 [SwitchB-ospf-1] import-route bgp [SwitchB-ospf-1] quit # Redistribute BGP routing information into OSPF on Switch D. [SwitchD] ospf 1 [SwitchD-ospf-1] import-route bgp [SwitchD-ospf-1] quit # Redistribute BGP routing information into OSPF on Switch C.

  • Page 226: Anycast Rp Configuration

    [SwitchA] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count 10.110.3.2 01:07:08 10.110.6.2 00:16:39 # Display brief MSDP peer information on Switch D. [SwitchD] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Listen...
  • Page 227 Figure 64 Network diagram Device Interface IP address Device Interface IP address Source 1 — 10.110.5.100/24 Switch VLAN-interface 192.168.1.2/24 Source 2 — 10.110.6.100/24 VLAN-interface 192.168.2.2/24 Switch A VLAN-interface 300 10.110.5.1/24 Switch VLAN-interface 10.110.3.1/24 VLAN-interface 103 10.110.2.2/24 VLAN-interface 10.110.4.1/24 Switch B VLAN-interface 100 10.110.1.1/24 VLAN-interface...
  • Page 228 [SwitchB] multicast routing-enable [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] igmp enable [SwitchB-Vlan-interface100] pim sm [SwitchB-Vlan-interface100] quit [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...
  • Page 229 Peer's Address State Up/Down time SA Count Reset Count 2.2.2.2 00:10:17 # Display brief MSDP peer information on Switch D. [SwitchD] display msdp brief MSDP Peer Brief Information of VPN-Instance: public net Configured Listen Connect Shutdown Down Peer's Address State Up/Down time SA Count Reset Count...

  • Page 230: Sa Message Filtering Configuration

    routing information displayed on Switch B with that displayed on Switch D, you can see that Switch D acts now as the RP for Source 2 and Host B. # Display PIM routing information on Switch B. [SwitchB] display pim routing-table No information is output on Switch B.
  • Page 231 • Configure SA message filtering rules so that receivers Host A and Host B can receive only the multicast data addressed to multicast groups 225.1.1.0/30 and 226.1.1.0/30, and Host can receive only the multicast data addressed to multicast groups 226.1.1.0/30 and 227.1.1.0/30. Figure 65 Network diagram PIM-SM 1 PIM-SM 2...
  • Page 232 [SwitchA-Vlan-interface100] quit [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, PIM-SM and IGMP on Switch B, Switch C and Switch D in the same way.
  • Page 233 # Configure an SA message rule on Switch C so that Switch C will not forward SA messages for (Source 1, 225.1.1.0/30) to Switch D. [SwitchC] acl number 3001 [SwitchC-acl-adv-3001] rule deny ip source 10.110.3.100 0 destination 225.1.1.0 0.0.0.3 [SwitchC-acl-adv-3001] rule permit ip source any destination any [SwitchC-acl-adv-3001] quit [SwitchC] msdp [SwitchC-msdp] peer 10.110.5.2 sa-policy export acl 3001...

  • Page 234: Troubleshooting Msdp

    Troubleshooting MSDP This section describes details about troubleshooting MSDP. MSDP peers stay in down state Symptom The configured MSDP peers stay in down state. Analysis • A TCP connection–based MSDP peering relationship is established between the local interface address and the MSDP peer after the configuration. •...
  • Page 235 Analysis • In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP peers to achieve load balancing among the RPs. • An MSDP peer address must be different from the Anycast RP address, and the C-BSR and C-RP must be configured on different devices or interfaces.

  • Page 236: Configuring Mbgp

    Configuring MBGP This chapter covers configuration tasks related to MBGP for IP multicast only. For more information about BGP, see Layer 3—IP Routing Configuration Guide. Overview BGP-4 can only carry routing information for IPv4. IETF defined Multiprotocol Border Gateway Protocol (MP-BGP) to extend BGP-4 so that BGP can carry routing information for multiple network-layer protocols.

  • Page 237: Configuring Basic Mbgp Functions

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

  • Page 238: Configuration Prerequisites

    Configuration prerequisites Configure basic MBGP functions before you configure this task. Configuring MBGP route redistribution MBGP can advertise routing information in the local AS to neighboring ASs. It redistributes such routing information from IGP into its routing table rather than learns the information by itself. The ORIGIN attribute of routes redistributed into the MBGP routing table with the import-route command is Incomplete.

  • Page 239: Configuring Mbgp Route Summarization

    Step Command Remarks route-policy route-policy-name ] The allow-direct keyword is available only when the specified routing protocol is OSPF. Enable default route redistribution into the MBGP Not enabled by default. default-route imported routing table. Configuring MBGP route summarization To reduce the routing table size on medium and large MBGP networks, you need to configure route summarization on peers.

  • Page 240: Configuring Outbound Mbgp Route Filtering

    NOTE: After you configure the peer default-route-advertise command, the router sends a default route with the next hop as itself to the specified MBGP peer or peer group, whether the default route is available or not in the routing table. Configuring outbound MBGP route filtering If several filtering policies are configured, they are applied in the following sequence: filter-policy export...

  • Page 241: Configuring Inbound Mbgp Route Filtering

    Configuring inbound MBGP route filtering By configuring MBGP route reception filtering policies, you can filter out unqualified routes from an MBGP peer or peer group. If several filtering policies are configured, they are applied in the following sequence: filter-policy import peer filter-policy import peer as-path-acl import peer ip-prefix import...

  • Page 242: Configuring Mbgp Route Dampening

    NOTE: Members of a peer group can have different route reception filtering policies from the peer group. Configuring MBGP route dampening By configuring MBGP route dampening, you can suppress unstable routes from being added to the MBGP routing table or being advertised to MBGP peers. To configure BGP route dampening: Step Command...

  • Page 243: Configuring The Default Local Preference

    Configuring the default local preference Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. Optional. Configure the default local default local-preference value preference. 100 by default. Configuring the MED attribute When other conditions of routes to a destination are identical, the route with the smallest MED is selected.

  • Page 244: Configuring The As_Path Attribute

    Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv4 MBGP address ipv4-family multicast family view. Optional. By default, MBGP specifies the local router as the next hop for routes Specify the router as the next peer { group-name | ip-address } advertised to a MBGP hop of routes sent to a peer or a...

  • Page 245: Tuning And Optimizing Mbgp Networks

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

  • Page 246: Enabling The Mbgp Orf Capability

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

  • Page 247: Configuring The Maximum Number Of Mbgp Ecmp Routes

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

  • Page 248: Configuring Mbgp Community

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

  • Page 249: Configuring An Mbgp Route Reflector

    Configuring an MBGP route reflector To guarantee the connectivity between multicast IBGP peers in an AS, you need to make them fully meshed. However, this becomes impractical when large numbers of multicast IBGP peers exist. Configuring route reflectors can solve this problem. In general, it is not required that clients of a route reflector be fully meshed.

  • Page 250: Resetting Mbgp Connections

    Task Command Remarks include } regular-expression ] display bgp multicast peer [ [ ip-address ] Display MBGP peer information or Available in any verbose ] [ | { begin | exclude | include } peer group information. view. regular-expression ] Display the prefix entries in the display bgp multicast peer ip-address received Available in any...

  • Page 251: Clearing Mbgp Information

    Task Command Remarks reset bgp ipv4 multicast { all | Reset specified MBGP as-number | ip-address | group Available in user view. connections. group-name | external | internal } Clearing MBGP information Task Command Remarks Clear dampened routing reset bgp ipv4 multicast information and release dampening [ ip-address [ mask | Available in user view.
  • Page 252 Device Interface IP address Device Interface IP address Source 10.110.1.100/24 Switch C VLAN-interface 10.110.2.1/24 Switch VLAN-interface 10.110.1.1/24 VLAN-interface 192.168.2.2/24 VLAN-interface 192.168.1.1/24 VLAN-interface 192.168.4.1/24 Loop0 1.1.1.1/32 Loop0 3.3.3.3/32 Switch VLAN-interface 192.168.1.2/24 Switch D VLAN-interface 192.168.3.2/24 VLAN-interface 192.168.2.1/24 VLAN-interface 192.168.4.2/24 VLAN-interface 192.168.3.1/24 Loop0 4.4.4.4/32 Loop0...
  • Page 253 # Configure a PIM domain border on Switch B. [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim bsr-boundary [SwitchB-Vlan-interface101] quit Configure Loopback 0 and the position of C-BSR, and C-RP: # Configure Loopback 0 and configure it as the C-BSR and C-RP on Switch A. [SwitchA] interface loopback 0 [SwitchA-LoopBack0] ip address 1.1.1.1 32 [SwitchA-LoopBack0] pim sm...
  • Page 254 [SwitchA-msdp] quit # Specify the MSDP peer on Switch B. [SwitchB] msdp [SwitchB-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 [SwitchB-msdp] quit Verify the configuration: Use the display bgp multicast peer command to display MBGP peers on a switch. For example: # Display MBGP peers on Switch B. [SwitchB] display bgp multicast peer BGP local router ID : 2.2.2.2 Local AS number : 200...

  • Page 255: Configuring Multicast Vpn (Available Only On The Hpe 5800)

    Configuring multicast VPN (available only on the HPE 5800) Overview Multicast VPN is a technique that implements multicast delivery in virtual private networks (VPNs). Figure 67 Typical VPN networking diagram VPN A VPN B Site 1 Site 2 PE 1...
  • Page 256 Figure 68 Multicast in multiple VPN instances With multicast VPN, when a multicast source in VPN A sends a multicast stream to a multicast group, of all possible receivers on the network for that group, only those that belong to VPN A, namely, in Site 1, Site 3 or Site 5, can receive the multicast stream.

  • Page 257: Md-Vpn Overview

    MD-VPN overview For more information about the concepts of Protocol Independent Multicast (PIM), bootstrap router (BSR), candidate-BSR (C-BSR), rendezvous point (RP), designated forwarder (DF), candidate-RP (C-RP), shortest path tree (SPT) and rendezvous point tree (RPT), see "Configuring PIM." Basic concepts in MD-VPN Concept Description An MD is a set of VPN instances running on PE devices that can...
  • Page 258 per-VPN-instance basis, but the public network multicast traffic between the PE devices and the P devices is transmitted through the public network. • Logically, an MD defines the transmission range of the multicast traffic of a specific VPN over the public network. Physically, an MD identifies all the PE devices that support that VPN in the public network.

  • Page 259: Multicast Across Vpns

    a. When the rate of a VPN multicast stream that entered the public network at a specific PE device exceeds the threshold, the PE device creates an MDT switchover message. The message travels to the downstream along the share-MDT. This causes a switch-MDT to be built by using the switch-group between that PE device and the remote PE devices with downstream receivers.
  • Page 260 the receivers are in different VPNs, you must configure multicast across VPNs so that the receivers can receive multicast data from the multicast source. Figure 71 Multicast across VPNs As shown in Figure 71, Source 1 is in Site 1 of VPN A, Receiver 1 is in Site 2 of VPN A, Receiver 2 is in Site 1 of VPN B.

  • Page 261: M6Vpe

    As shown in Figure 72, configure VPN instance A, create VPN instance B, and specify the share-group on PE 1. After the configuration, a share-MDT is established for VPN instance A and VPN instance B respectively on the public network. After receiving multicast packets from Source 1, PE 1 duplicates and encapsulates them, and forwards them to PE 2 and PE 3 along the share-MDT.

  • Page 262: Protocols And Standards

    To implement M6VPE, you just need to upgrade PE devices without any changes to CE devices or P devices. For carriers, M6VPE is a cost-effective solution to IPv6 multicast access services over existing IPv4 networks. Figure 74 M6VPE networking diagram As shown in Figure 74, the public network runs IPv4 protocols, and the VPN network runs IPv6...
  • Page 263 Share-MDT establishment in a PIM-DM network Figure 75 Share-MDT establishment in a PIM-DM network BGP: 11.1.3.1/24 PE 3 Share-Group: 239.1.1.1 Public network BGP peers 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 Figure 75, PIM-DM is enabled in the network and all the PE devices support VPN...
  • Page 264 As shown in Figure 76, PIM-SM is enabled in the network and all the PE devices support VPN instance A. The process of establishing a share-MDT is as follows: The public network on PE 1 initiates a join to the public network RP, with the share-group address as the multicast group address in the join message, and a (*, 239.1.1.1) state entry is created on each device along the path in the public network.

  • Page 265: Share-Mdt-Based Delivery

    Share-MDT establishment in a PIM-SSM network Figure 78 Share-MDT establishment in a PIM-SSM network BGP: 11.1.3.1/24 PE 3 Share-Group: 232.1.1.1 Public instance BGP peers SPT (11.1.1.1, 232.1.1.1) SPT (11.1.2.1, 232.1.1.1) SPT (11.1.3.1, 232.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 78, PIM-SSM is enabled in the network and all the PE devices support VPN...
  • Page 266 the share-MDT, and then de-encapsulated on the remote PE device to go into the normal protocol procedure. Finally a distribution tree is established across the public network. The following describes how multicast protocol packets are forwarded in the following circumstances: If the VPN network runs PIM-DM or PIM-SSM: Hello packets are forwarded among MTI interfaces to establish PIM neighboring relationships.
  • Page 267 Figure 79 Transmission of multicast protocol packets BGP: 11.1.3.1/24 PE 3 Source Receiver CE 1 CE 2 PE 1 PE 2 Site 1 Site 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 S: 192.1.1.1/24 Public instance BGP peers G: 225.1.1.1 VPN instance join (*, 225.1.1.1) Share-Group: 239.1.1.1 Public instance join (11.1.2.1, 239.1.1.1) The work process of multicast protocol packets is as follows:...
  • Page 268 When PIM-SM is running in the VPN: Before SPT switchover, if the multicast source and the VPN RP are in different sites, the multicast source forwards VPN multicast data to the VPN RP along the VPN SPT across the public network. If the VPN RP and the receiver are in different sites, the VPN RP forwards VPN multicast traffic to the receiver along the VPN RPT over the public network.

  • Page 269: Mdt Switchover

    to turn it back into a VPN multicast data packet, and passes it to the corresponding VPN instance. If any PE has a downstream interface for an SPT, it forwards the VPN multicast packet down the SPT. Otherwise, it discards the packet. The VPN instance on PE 2 searches the MVRF and finally delivers the VPN multicast data to Receiver.

  • Page 270: Multi-As Md Vpn

    • The traffic rate of the VPN multicast data has fallen under the switchover threshold and stayed lower than the threshold for a certain length of time (namely, the switch-holddown period). • The associated switch-group-pool is changed and the switch-group address for encapsulating the VPN multicast data is out of the new address pool.
  • Page 271 Figure 82 Multi-hop EBGP interconnectivity In the multi-hop EBGP interconnectivity approach, only one MD needs to be established for all the ASs, and public network multicast traffic between different ASs is transmitted within this MD. MD VPN inter-AS option B In MD VPN inter-AS option B, RPF vector and BGP connector are introduced: •...

  • Page 272: Multicast Vpn Configuration Task List

    Figure 83 MD VPN inter-AS option B To implement MD VPN inter-AS option B, only one MD needs to be established for the two ASs. VPN multicast data is transmitted between different ASs on the public network within this MD. NOTE: Only PIM-SSM mode is supported on the public network of MD VPN inter-AS option B.

  • Page 273: Configuring Md-Vpn

    Task Remarks Configuring a BGP MDT route reflector Optional. Specifying the source IP address for multicast across VPNs Optional. Configuring MD-VPN Configuration prerequisites Before you configure MD-VPN, complete the following tasks: • Configure any unicast routing protocol on the public network. •...

  • Page 274: Configuring Mdt Switchover Parameters

    Step Command Remarks Enter system view. system-view ip vpn-instance Enter VPN instance view. vpn-instance-name multicast-domain share-group Configure a share-group No share-group address or MTI group-address binding mtunnel address and an MTI binding. binding is configured. mtunnel-number Configuration guidelines • After a BGP peer is configured with the peer connect-interface command, the MTI interface automatically obtains the connect-interface address and uses it as its own IP address.

  • Page 275: Configuring The Rpf Vector Feature

    Step Command Remarks Configure the By default, no switch-group-pool multicast-domain switch-group-pool address is configured and multicast traffic switch-group-pool range and the switchover switch-group-pool { mask | is never switched to a criteria. mask-length } [ acl acl-number ] * switch-MDT. Optional.

  • Page 276: Configuring Bgp Mdt

    Step Command Remarks Enter system view. system-view ip vpn-instance Enter VPN instance view. vpn-instance-name Required. Enable data-group reuse multicast-domain log logging. data-group-reuse Disabled by default. Configuring BGP MDT If PIM-SSM is running in the public network, you need to configure BGP MDT. Configuration prerequisites Before you configure BGP MDT, complete the following tasks: •...

  • Page 277: Specifying The Source Ip Address For Multicast Across Vpns

    expenses. To reduce connections between them, you can configure one of them as a route reflector and specify other routers as clients. The clients establish BGP MDT connections with the route reflector, and the route reflector forwards (reflects) BGP MDT routing information between clients. In this way, the clients need not to be fully meshed.

  • Page 278: Configuration Procedure

    Configuration procedure If the receivers and the multicast source are in different VPNs, configure the IP addresses of both the multicast source and RP as the source IP address. This allows multicast across VPNs in the VPN instance views of the receivers on the receiver-side PE. Perform the following configuration on the PE.

  • Page 279: Multicast Vpn Configuration Examples

    Task Command Remarks display bgp mdt { all | route-distinguisher route-distinguisher } Display BGP MDT routing routing-table [ ip-address [ mask Available in any view. information. | mask-length ] ] [ | { begin | exclude | include } regular-expression ] reset bgp mdt { as-number | Reset a BGP MDT connection.
  • Page 280 Item Network requirements multicast groups). • Configure Loopback 2 of PE 3 as a C-BSR and a C-RP for VPN b (to work for all multicast groups). Figure 84 Network diagram VPN a Loop1 VPN b CE a2 VPN a Vlan-int30 Loop1 CE b1...
  • Page 281 # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing-enable [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls [PE1-mpls] quit [PE1] mpls ldp [PE1-mpls-ldp] quit # Create VPN instance a, configure an RD and route target attributes for it.
  • Page 282 [PE1-Vlan-interface11] ip binding vpn-instance a [PE1-Vlan-interface11] ip address 10.110.2.1 24 [PE1-Vlan-interface11] pim sm [PE1-Vlan-interface11] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [PE1] interface loopback 1 [PE1-LoopBack1] ip address 1.1.1.1 32 [PE1-LoopBack1] pim sm [PE1-LoopBack1] quit # Configure BGP.
  • Page 283 [PE2-mpls] quit [PE2] mpls ldp [PE2-mpls-ldp] quit # Create VPN instance b, configure an RD and route target attributes for it. [PE2] ip vpn-instance b [PE2-vpn-instance-b] route-distinguisher 200:1 [PE2-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE2-vpn-instance-b] vpn-target 200:1 import-extcommunity # Enable IP multicast routing in VPN instance b, configure a share-group address, and associate an MTI with the VPN instance.
  • Page 284 # Bind VLAN-interface 14 with VPN instance a, configure an IP address and enable PIM-SM on the interface. [PE2] interface vlan-interface 14 [PE2-Vlan-interface14] ip binding vpn-instance a [PE2-Vlan-interface14] ip address 10.110.4.1 24 [PE2-Vlan-interface14] pim sm [PE2-Vlan-interface14] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 1.1.1.2 32 [PE2-LoopBack1] pim sm...
  • Page 285 [PE2-rip-3] network 10.0.0.0 [PE2-rip-3] import-route bgp [PE2-rip-3] return Configure PE 3: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability. <PE3> system-view [PE3] router id 1.1.1.3 [PE3] multicast routing-enable [PE3] mpls lsr-id 1.1.1.3 [PE3] mpls...
  • Page 286 [PE3-Vlan-interface19] pim sm [PE3-Vlan-interface19] mpls [PE3-Vlan-interface19] mpls ldp [PE3-Vlan-interface19] quit # Bind VLAN-interface 17 with VPN instance a, configure an IP address and enable PIM-SM on the interface. [PE3] interface vlan-interface 17 [PE3-Vlan-interface17] ip binding vpn-instance a [PE3-Vlan-interface17] ip address 10.110.5.1 24 [PE3-Vlan-interface17] pim sm [PE3-Vlan-interface17] quit # Bind VLAN-interface 18 with VPN instance b, configure an IP address and enable PIM-SM on...
  • Page 287 [PE3-bgp-b] quit [PE3–bgp] ipv4-family vpnv4 [PE3–bgp-af-vpnv4] peer vpn-g enable [PE3-bgp-af-vpnv4] peer 1.1.1.1 group vpn-g [PE3–bgp-af-vpnv4] peer 1.1.1.2 group vpn-g [PE3–bgp-af-vpnv4] quit [PE3–bgp] quit With BGP peers configured on PE 3, the interfaces MTI 0 and MTI 1 will automatically obtain IP addresses, which are the loopback interface addresses specified in the BGP peer configuration.
  • Page 288 [P-Vlan-interface15] ip address 192.168.7.2 24 [P-Vlan-interface15] pim sm [P-Vlan-interface15] mpls [P-Vlan-interface15] mpls ldp [P-Vlan-interface15] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network interface VLAN-interface 19. [P] interface vlan-interface 19 [P-Vlan-interface19] ip address 192.168.8.2 24 [P-Vlan-interface19] pim sm [P-Vlan-interface19] mpls [P-Vlan-interface19] mpls ldp...
  • Page 289 <CEb1> system-view [CEb1] multicast routing-enable # Configure an IP address for VLAN-interface 30 and enable PIM-SM on the interface. [CEb1] interface vlan-interface 30 [CEb1-Vlan-interface30] ip address 10.110.8.1 24 [CEb1-Vlan-interface30] pim sm [CEb1-Vlan-interface30] quit # Configure an IP address for VLAN-interface 13 and enable PIM-SM on the interface. [CEb1] interface vlan-interface 13 [CEb1-Vlan-interface13] ip address 10.110.3.2 24 [CEb1-Vlan-interface13] pim sm...
  • Page 290 [CEa2] rip 2 [CEa2-rip-2] network 10.0.0.0 [CEa2-rip-2] network 22.0.0.0 Configure CE a3: # Enable IP multicast routing. <CEa3> system-view [CEa3] multicast routing-enable # Configure an IP address for VLAN-interface 50 and enable IGMP and PIM-SM 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] pim sm...

  • Page 291: Multi-As Md Vpn Configuration

    Verifying the configuration # Display the local share-group information of VPN instance a on PE 1. <PE1> display multicast-domain vpn-instance a share-group local MD local share-group information for VPN-Instance: a Share-group: 239.1.1.1 MTunnel address: 1.1.1.1 # Display the local share-group information of VPN instance a on PE 2. <PE2>...
  • Page 292 Item Network requirements MPLS respective Loopback 1 interface and exchange all VPN routes between them. • Configure MPLS separately in AS 100 and AS 200. • Enable IP multicast routing on the public network on PE 1, PE 2, PE 3 and PE 4. •...
  • Page 293 Device Interface IP address Device Interface IP address Vlan-int11 10.11.1.1/24 Vlan-int3 192.168.1.2/24 Vlan-int12 10.11.2.1/24 Loop1 1.1.1.3/32 Loop1 1.1.1.1/32 Loop2 22.22.22.22/32 PE 2 Vlan-int2 10.10.1.2/24 PE 4 Vlan-int4 10.10.2.2/24 Vlan-int3 192.168.1.1/24 Vlan-int13 10.11.3.1/24 Loop1 1.1.1.2/32 Vlan-int14 10.11.4.1/32 Loop2 11.11.11.11/32 Loop2 1.1.1.4/32 CE a1 Vlan-int10 10.11.5.1/24...
  • Page 294 # Select an available port not in use, disable spanning tree protocols, LLDP and NDP on the port, and add the port to service loopback group 1. [PE1] interface gigabitethernet1/0/3 [PE1-GigabitEthernet1/0/3] undo stp enable [PE1-GigabitEthernet1/0/3] undo ndp enable [PE1-GigabitEthernet1/0/3] undo lldp enable [PE1-GigabitEthernet1/0/3] port service-loopback group 1 [PE1-GigabitEthernet1/0/3] quit # Configure an IP address, and enable PIM-SM and LDP capability on the public network...
  • Page 295 [PE1-bgp-a] quit [PE1–bgp] ipv4-family vpn-instance b [PE1-bgp-b] import-route ospf 3 [PE1-bgp-b] import-route direct [PE1-bgp-b] quit [PE1–bgp] ipv4-family vpnv4 [PE1–bgp-af-vpnv4] peer 1.1.1.4 enable [PE1–bgp-af-vpnv4] quit [PE1–bgp] quit With BGP peers configured on PE 1, the interfaces MTI 0 and MTI 1 will automatically obtain IP addresses, which are the loopback interface addresses specified in the BGP peer configuration.
  • Page 296 [PE2-Vlan-interface2] mpls ldp [PE2-Vlan-interface2] quit # Configure an IP address, and enable PIM-SM and MPLS capability on the public network interface VLAN-interface 3. [PE2] interface vlan-interface 3 [PE2-Vlan-interface3] ip address 192.168.1.1 24 [PE2-Vlan-interface3] pim sm [PE2-Vlan-interface3] mpls [PE2-Vlan-interface3] quit # Configure an IP address for Loopback 1, and enable PIM-SM. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 1.1.1.2 32 [PE2-LoopBack1] pim sm...
  • Page 297 [PE2–bgp] quit # Configure OSPF. [PE2] ospf 1 [PE2-ospf-1] area 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0 [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.0.0 0.0.255.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # Configure a routing policy. [PE2] route-policy map1 permit node 10 [PE2-route-policy] apply mpls-label [PE2-route-policy] quit [PE2] route-policy map2 permit node 10 [PE2-route-policy] if-match mpls-label...
  • Page 298 # Configure an IP address for Loopback 2, and enable PIM-SM. [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 for the public network instance. [PE3] pim [PE3-pim] c-bsr loopback 2 [PE3-pim] c-rp loopback 2...
  • Page 299 [PE3-route-policy] if-match mpls-label [PE3-route-policy] apply mpls-label [PE3-route-policy] quit Configure PE 4: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability. <PE4> system-view [PE4] router id 1.1.1.4 [PE4] multicast routing-enable [PE4] mpls lsr-id 1.1.1.4 [PE4] mpls...
  • Page 300 [PE4-Vlan-interface4] mpls [PE4-Vlan-interface4] mpls ldp [PE4-Vlan-interface4] quit # Bind VLAN-interface 13 with VPN instance a, configure an IP address and enable PIM-SM on the interface. [PE4] interface vlan-interface 13 [PE4-Vlan-interface13] ip binding vpn-instance a [PE4-Vlan-interface13] ip address 10.11.3.1 24 [PE4-Vlan-interface13] pim sm [PE4-Vlan-interface13] quit # Bind VLAN-interface 14 with VPN instance b, configure an IP address and enable PIM-SM on the interface.
  • Page 301 # Configure OSPF. [PE4] ospf 1 [PE4-ospf-1] area 0.0.0.0 [PE4-ospf-1-area-0.0.0.0] network 1.1.1.4 0.0.0.0 [PE4-ospf-1-area-0.0.0.0] network 10.10.0.0 0.0.255.255 [PE4-ospf-1-area-0.0.0.0] quit [PE4-ospf-1] quit [PE4] ospf 2 vpn-instance a [PE4-ospf-2] import-route bgp [PE4-ospf-2] area 0.0.0.0 [PE4-ospf-2-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [PE4-ospf-2-area-0.0.0.0] quit [PE4-ospf-2] quit [PE4] ospf 3 vpn-instance b [PE4-ospf-3] import-route bgp [PE4-ospf-3] area 0.0.0.0...
  • Page 302 [CEa1-ospf-1-area-0.0.0.0] quit [CEa1-ospf-1] quit Configure CE b1: # Enable IP multicast routing. <CEb1> system-view [CEb1] multicast routing-enable # Configure an IP address for VLAN-interface 20 and enable PIM-SM on the interface. [CEb1] interface vlan-interface 20 [CEb1-Vlan-interface20] ip address 10.11.6.1 24 [CEb1-Vlan-interface20] pim sm [CEb1-Vlan-interface20] quit # Configure an IP address for VLAN-interface 12 and enable PIM-SM on the interface.
  • Page 303 [CEb2] multicast routing-enable # Configure an IP address for VLAN-interface 40 and enable IGMP and PIM-SM on the interface. [CEb2] interface vlan-interface 40 [CEb2-Vlan-interface40] ip address 10.11.8.1 24 [CEb2-Vlan-interface40] igmp enable [CEb2-Vlan-interface40] pim sm [CEb2-Vlan-interface40] quit # Configure an IP address for VLAN-interface 14 and enable PIM-SM on the interface. [CEb2] interface vlan-interface 14 [CEb2-Vlan-interface14] ip address 10.11.4.2 24 [CEb2-Vlan-interface14] pim sm...

  • Page 304: Multicast Across Vpns Configuration Example (On The Source-Side Pe)

    <PE4> display multicast-domain vpn-instance b share-group local MD local share-group information for VPN-Instance: b Share-group: 239.4.4.4 MTunnel address: 1.1.1.4 Multicast across VPNs configuration example (on the source-side PE) Network requirements As show in Figure 86, on the MPLS L3VPN network, multicast data of VPN instance a can be correctly forwarded in the VPN instance.
  • Page 305 <PE2> system-view [PE2] ip vpn-instance b # Configure the RD and route target attributes for VPN instance b. [PE2-vpn-instance-b] route-distinguisher 200:1 [PE2-vpn-instance-b] vpn-target 200:1 both # Enable IP multicast routing in VPN instance b. [PE2-vpn-instance-b] multicast routing-enable # Specify 239.2.2.2 as the share-group address for VPN instance b and associate an MTI with the VPN instance.

  • Page 306: Multicast Across Vpns Configuration Example (On The Receiver-Side Pe)

    Multicast across VPNs configuration example (on the receiver-side PE) Network requirements As show in Figure 87, on the MPLS L3VPN network, multicast data of VPN instance a can be correctly forwarded in the VPN instance. Configure multicast across VPNs on PE 2 so that R2 in VPN instance b can receive multicast data of VPN instance a.

  • Page 307: M6Vpe Configuration Example

    [PE2] ip vpn-instance b # Configure the RD and route target attributes for VPN instance b. [PE2-vpn-instance-b] route-distinguisher 200:1 [PE2-vpn-instance-b] vpn-target 200:1 both # Enable IP multicast routing in VPN instance b. [PE2-vpn-instance-b] multicast routing-enable # Specify 239.2.2.2 as the share-group address for VPN instance b and associate an MTI with the VPN instance.
  • Page 308 • IPv6 PIM-SM runs in VPN a. Loopback 0 on CE a1 acts as a C-BSR and a C-RP for all IPv6 multicast group in VPN a. The share-group address is 239.1.1.1. Figure 88 Network diagram Device Interface IP address or IPv6 Device Interface IP address or IPv6...
  • Page 309 [PE1-vpn-instance-a] quit # Create service loopback group 1 and specify its service type as multicast tunnel. [PE1] service-loopback group 1 type multicast-tunnel # Select an available port not in use (GigabitEthernet 1/0/3 in this example), disable STP, LLDP and NDP for the port, and add the port to service loopback group 1. [PE1] interface gigabitethernet1/0/3 [PE1-GigabitEthernet1/0/3] undo stp enable [PE1-GigabitEthernet1/0/3] undo ndp enable...
  • Page 310 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure RIPng. [PE1] ripng 1 vpn-instance a [PE1-ripng-1] import-route bgp4+ [PE1-ripng-1] quit [PE1] interface vlan-interface 20 [PE1-Vlan-interface20] ripng 1 enable [PE1-Vlan-interface20] quit Configure PE 2: # Configure a Router ID, enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability.
  • Page 311 [PE2] interface vlan-interface 40 [PE2-Vlan-interface40] ip address 192.168.2.2 24 [PE2-Vlan-interface40] pim sm [PE2-Vlan-interface40] mpls [PE2-Vlan-interface40] mpls ldp [PE2-Vlan-interface40] quit # Bind VLAN-interface 50 with VPN instance a, assign an IPv6 address to the interface and enable IPv6 PIM-SM. [PE2] interface vlan-interface 50 [PE2-Vlan-interface50] ip binding vpn-instance a [PE2-Vlan-interface50] ipv6 address 4001::1 64 [PE2-Vlan-interface50] pim ipv6 sm...
  • Page 312 # Enable IP multicast routing on the public network, configure an MPLS LSR ID, and enable the LDP capability. <P> system-view [P] multicast routing-enable [P] mpls lsr-id 2.2.2.2 [P] mpls [P-mpls] quit [P] mpls ldp [P-mpls-ldp] quit # Assign an IP address to VLAN-interface 30, and enable PIM-SM and LDP capability on the interface.
  • Page 313 [CEa1-Vlan-interface10] ipv6 address 1001::1 64 [CEa1-Vlan-interface10] pim ipv6 sm [CEa1-Vlan-interface10] quit # Assign an IPv6 address to VLAN-interface 20 and enable IPv6 PIM-SM on the interface. [CEa1] interface vlan-interface 20 [CEa1-Vlan-interface20] ipv6 address 2001::1 64 [CEa1-Vlan-interface20] pim ipv6 sm [CEa1-Vlan-interface20] quit # Assign an IPv6 address to Loopback 0 and enable IPv6 PIM-SM on the interface.

  • Page 314: Troubleshooting Md-Vpn Configuration

    [CEa2] ripng 1 [CEa2-ripng-1] quit [CEa2] interface vlan-interface 50 [CEa2-Vlan-interface50] ripng 1 enable [CEa2-Vlan-interface50] quit [CEa2] interface vlan-interface 60 [CEa2-Vlan-interface60] ripng 1 enable [CEa2-Vlan-interface60] quit Troubleshooting MD-VPN configuration A share-MDT cannot be established Symptom A share-MDT cannot be established. PIM adjacencies cannot be established between the same VPN instance’s interfaces on different PE devices.
  • Page 315 Analysis • If PIM-SM is running in the VPN instance, the BSR information for the VPN instance is required. Otherwise, the VPN instance’s MVRF cannot be correctly established. • If PIM-SM is running in the VPN instance, the RP information for the VPN instance is required. If a unicast route to the RP is not available, this means that a PIM adjacency has not been correctly established between the public network and the VPN instance, and thus VPN instance cannot correctly establish its MVRF.

  • Page 316: Configuring Mld Snooping

    Configuring MLD snooping This chapter describes MLD snooping, how to configure MLD snooping, configuration examples, troubleshooting methods, and an appendix about processing IPv6 multicast protocol messages. Overview MLD snooping is an IPv6 multicast constraining mechanism that runs on Layer 2 devices to manage and control IPv6 multicast groups.
  • Page 317 Figure 90 MLD snooping related ports The following describes the ports involved in MLD snooping: • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include designated routers (DRs) and MLD querier. In Figure 90, GigabitEthernet 1/0/1 of Switch A and Switch B are router ports.

  • Page 318: How Mld Snooping Operates

    NOTE: In MLD snooping, only dynamic ports age out. Static ports never age out. How MLD snooping operates An MLD snooping–enabled switch performs different actions when it receives different MLD messages. In this section, the involved ports are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports."...

  • Page 319: Mld Snooping Proxying

    • If a match is found but the receiving port is not in the forwarding entry, the switch directly discards the MLD done message. • If a match is found and the receiving port is in the forwarding entry, the switch forwards the done message to all router ports in the native VLAN.

  • Page 320: Protocols And Standards

    Table 9 MLD message processing on an MLD snooping proxy Actions message When receiving an MLD general query, the proxy forwards it to all ports but the port that General query received the query. In addition, the proxy generates a report according to the group memberships that it maintains and sends the report out of all router ports.

  • Page 321: Configuring Basic Mld Snooping Functions

    Task Remarks Setting the maximum number of MLD snooping forwarding Optional. entries Configuring IPv6 static multicast MAC address entries Optional. Configuring aging timers for dynamic ports Optional. Configuring static ports Optional. Configuring MLD Configuring a port as a simulated member host Optional.

  • Page 322: Specifying The Version Of Mld Snooping

    Configuration guidelines • Enable MLD snooping globally before you enable it for a VLAN. • After you enable MLD snooping for a VLAN, you cannot enable MLD or IPv6 PIM on the corresponding VLAN interface, and vice versa. • MLD snooping for a VLAN works only on the ports in this VLAN. Configuration procedure To enable MLD snooping: Step...

  • Page 323: Configuring Ipv6 Static Multicast Mac Address Entries

    Enter MLD-snooping view. mld-snooping Set the maximum number of By default, the upper limit is 4000 MLD snooping forwarding for the HPE 5800 switches, and entry-limit limit entries. 1000 for the HPE 5820X switches. NOTE: MLD snooping forwarding entries created for multicast VLAN are not limited by this command. You can use the multicast-vlan ipv6 entry-limit to limit the number of entries in the MLD snooping forwarding table of a multicast VLAN.

  • Page 324: Configuring Mld Snooping Port Functions

    Step Command Remarks view. the current interface. In port group interface interface-type view, the configuration is effective interface-number on all ports in the port group. • Enter port group view: port-group manual port-group-name Configure a static multicast No static multicast MAC address mac-address multicast MAC address entry.

  • Page 325: Configuring Static Ports

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

  • Page 326: Enabling Mld Snooping Fast-Leave Processing

    To avoid this situation, you can configure a port on the switch as a simulated member host for an IPv6 multicast group. When the simulated member host receives an MLD query, it gives a response. Therefore, the switch can continue receiving IPv6 multicast data. A simulated host is equivalent to a real, independent host in the following ways: •...

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

    Enabling MLD snooping fast-leave processing on a port Step Command Remarks Enter system view. system-view • Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view: Enter Layer 2 Ethernet interface view or Layer 2 interface interface-type Use either approach. aggregate interface view or interface-number enter port group view.

  • Page 328: Configuration Prerequisites

    Configuration prerequisites Before you configure an MLD snooping querier, complete the following tasks: • Enable MLD snooping in the VLAN. • Determine the interval for sending MLD general queries. • Determine the MLD last-listener query interval. • Determine the maximum response delay for MLD general queries. •...

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

    To speed up the response of hosts to MLD queries and avoid simultaneous timer expirations causing MLD report traffic bursts, set a proper value for the maximum response delay: • The maximum response delay for MLD general queries is set by the max-response-time command.

  • Page 330: Configuring Mld Snooping Proxying

    Step Command Remarks multicast-address-specific source-ip { ipv6-address | default. queries. current-interface } Configuring MLD snooping proxying This section describes how to configure MLD snooping proxying. Configuration prerequisites Before you configure MLD snooping proxying in a VLAN, complete the following tasks: •...

  • Page 331: Configuring An Mld Snooping Policy

    Configuring an MLD snooping policy This section describes how to configure an MLD snooping policy. Configuration prerequisites Before you configure an MLD snooping policy, complete the following tasks: • Enable MLD snooping for the VLAN. • Determine the IPv6 ACL for IPv6 multicast group filtering. •...

  • Page 332: Configuring Ipv6 Multicast Source Port Filtering

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

  • Page 333: Enabling Mld Report Suppression

    • When the function of dropping unknown IPv6 multicast data is disabled, the switch floods unknown IPv6 multicast data in the VLAN that the data belongs to, causing network bandwidth waste and low forwarding efficiency. • When the function of dropping unknown IPv6 multicast data is enabled, the switch forwards unknown multicast data to its router ports instead of flooding it in the VLAN.

  • Page 334: Enabling Ipv6 Multicast Group Replacement

    Set the maximum number of By default, the upper limit is 4000 mld-snooping group-limit limit IPv6 multicast groups that a for the HPE 5800 switches, and [ vlan vlan-list ] port can join. 1000 for the HPE 5820X switches. Enabling IPv6 multicast group replacement...

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

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

  • Page 336: Enabling The Mld Snooping Host Tracking Function

    match is found, the user is allowed to join the multicast group. Otherwise, the join report is dropped by the access switch. • After receiving a done message from a host, the access switch matches the IPv6 multicast group address and source address with the configured policies. If a match is found, the host is allowed to leave the group.

  • Page 337: Setting The Dscp Value For Mld Messages

    Setting the DSCP value for MLD messages This configuration applies to only the MLD messages that the local switch generates when the switch or its port acts as a member host, rather than those forwarded ones. To set the DSCP value for MLD messages: Step Command Remarks...

  • Page 338: Mld Snooping Configuration Examples

    MLD snooping configuration examples This section describes details about MLD snooping configuration examples. IPv6 group policy and simulated joining configuration example (in a VLAN) Network requirements As shown in Figure • MLDv1 runs on Router A, MLDv1 snooping runs on Switch A, and Router A acts as the MLD querier on the subnet.
  • Page 339 [RouterA-GigabitEthernet1/0/2] pim ipv6 dm [RouterA-GigabitEthernet1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable MLD snooping and the function of dropping IPv6 unknown multicast traffic in the VLAN.

  • Page 340: Static Port Configuration Example (In A Vlan)

    (::, FF1E::101): Attribute: Host Port Host port(s):total 2 port(s). GE1/0/3 (D) ( 00:03:23 ) GE1/0/4 (D) ( 00:04:10 ) MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 2 port(s). GE1/0/3 GE1/0/4 The output shows that GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 of Switch A have joined the IPv6 multicast group FF1E::101.
  • Page 341 Figure 93 Network diagram Configuration procedure Enable IPv6 forwarding and assign an IPv6 address and prefix length to each interface according to Figure On Router A, enable IPv6 multicast routing, enable MLD on GigabitEthernet 1/0/1, and enable IPv6 PIM-DM on each interface. <RouterA>...
  • Page 342 [SwitchA-GigabitEthernet1/0/3] quit Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 100, assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to this VLAN, and enable MLD snooping in the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port gigabitethernet 1/0/1 gigabitethernet 1/0/2 [SwitchB-vlan100] mld-snooping enable [SwitchB-vlan100] quit Configure Switch C:...

  • Page 343: Mld Snooping Querier Configuration Example (In A Vlan)

    IP group address:FF1E::101 (::, FF1E::101): Attribute: Host Port Host port(s):total 1 port(s). GE1/0/2 (D) ( 00:03:23 ) MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 1 port(s). GE1/0/2 The output shows that GigabitEthernet 1/0/3 of Switch A has become a static router port. # Display detailed MLD snooping group information in VLAN 100 on Switch C.
  • Page 344 • MLDv1 runs on all receivers and MLDv1 snooping runs on all switches. Switch A, which is close to the multicast sources, is chosen as the MLD snooping querier. To prevent flooding of unknown multicast traffic within the VLAN, configure all switches to drop unknown multicast data packets.

  • Page 345: Mld Snooping Proxying Configuration Example (In A Vlan)

    [SwitchB-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 # Enable the MLD snooping feature and the function of dropping unknown IPv6 multicast data packets in VLAN 100. [SwitchB-vlan100] mld-snooping enable [SwitchB-vlan100] mld-snooping drop-unknown [SwitchB-vlan100] quit Configurations of Switch C and Switch D are similar to the configuration of Switch B. Verifying the configuration When the MLD snooping querier starts to work, all switches but the querier receive MLD general queries.
  • Page 346 Figure 95 Network diagram Receiver Host A Source Receiver GE1/0/4 GE1/0/1 GE1/0/2 2001::1/64 GE1/0/1 GE1/0/3 1::2/64 Switch A Host B Router A GE1/0/2 1::1/64 Proxy & Querier MLD querier Host C VLAN 100 Configuration procedure Assign an IP address and prefix length to each interface according to Figure 95.
  • Page 347 and the display mld group command to display information about MLD snooping groups and MLD multicast groups. For example: # Display information about MLD snooping groups on Switch A. [SwitchA] display mld-snooping group Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s).

  • Page 348: Ipv6 Multicast Source And User Control Policy Configuration Example (In A Vlan)

    Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):100. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 1 port(s). GE1/0/1 IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 1 port(s). GE1/0/3 MAC group(s): MAC group address:3333-0000-0101...

  • Page 349: Configuration Procedures

    Figure 96 Network diagram Configuration procedures Enable IPv6 forwarding and assign an IP address and prefix length to each interface according Figure 96. (Details not shown.) Configure Switch A: # Create VLAN 101 through VLAN 104 and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the four VLANs respectively.
  • Page 350 [SwitchA-Vlan-interface104] quit # Create a multicast source control policy, policy1, so that multicast flows from Source 2 to FF1E::101 are blocked. [SwitchA] acl ipv6 number 3001 [SwitchA-acl6-adv-3001] rule permit udp source 2::1 128 destination ff1e::101 128 [SwitchA-acl6-adv-3001] quit [SwitchA] traffic classifier classifier1 [SwitchA-classifier-classifier1] if-match acl ipv6 3001 [SwitchA-classifier-classifier1] quit [SwitchA] traffic behavior behavior1...
  • Page 351 [SwitchA-GigabitEthernet1/0/2] quit Configure Switch B: # Globally enable MLD snooping. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 104, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to this VLAN, and enable MLD snooping in this VLAN. [SwitchB] vlan 104 [SwitchB-vlan104] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3 [SwitchB-vlan104] mld-snooping enable [SwitchB-vlan104] quit # Create a user profile profile2 and configure the user profile so that users can join or leave...
  • Page 352 [SwitchB-GigabitEthernet1/0/3] quit Configure the RADIUS server: On the RADIUS server, configure the parameters related to Switch A and Switch B. For more information, see the configuration guide of the RADIUS server. Verifying the configuration After the configurations, the two multicast sources and hosts initiate 802.1X authentication. After passing the authentication, Source 1 sends multicast flows to FF1E::101 and Source 2 sends multicast flows to FF1E::102;...

  • Page 353: Troubleshooting Mld Snooping

    List of 1 outgoing interfaces: 1: Vlan-interface104 Matched 19648 packets(20512512 bytes), Wrong If 0 packets Forwarded 19648 packets(20512512 bytes) The output shows that Switch A maintains a multicast forwarding entry for multicast packets from Source 1 to FF1E::101. No forwarding entry exists for packets from Source 2 to FF1E::101, which indicates that IPv6 multicast packets from Source 2 are blocked.

  • Page 354: Appendix

    Appendix Processing of IPv6 multicast protocol messages With Layer 3 multicast routing enabled, an MLD snooping–enabled switch processes IPv6 multicast protocol messages differently under different conditions, as follows: • If only MLD is enabled on the switch, or if both MLD and IPv6 PIM are enabled on the switch, the switch does the following: Maintains dynamic member ports or dynamic router ports according to MLD packets Maintains dynamic router ports according to IPv6 PIM hello packets...

  • Page 355: Configuring Ipv6 Pim Snooping

    Configuring IPv6 PIM snooping This chapter describes IPv6 PIM snooping, how to configure IPv6 PIM snooping, configuration examples, and troubleshooting methods. Overview IPv6 PIM snooping runs on Layer 2 devices. It determines which ports are interested in multicast data by analyzing the received IPv6 PIM messages, and adds the ports to a multicast forwarding entry to make sure multicast data can be forwarded to only the ports that are interested in the data.

  • Page 356: Configuring Ipv6 Pim Snooping

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

  • Page 357: Ipv6 Pim Snooping Configuration Example (In A Vlan)

    Task Command Remarks { begin | exclude | include } regular-expression ] display pim-snooping ipv6 routing-table Display IPv6 PIM snooping routing [ [ vlan vlan-id ] [ slot slot-number ] ] [ | Available in any view. entries. { begin | exclude | include } regular-expression ] Display statistics for IPv6 PIM display pim-snooping ipv6 statistics [ |...
  • Page 358 On Router A, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and configure interface GigabitEthernet 1/0/2 as a C-BSR and C-RP. <RouterA> system-view [RouterA] multicast ipv6 routing-enable [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim ipv6 sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim ipv6 sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] pim ipv6...

  • Page 359: Troubleshooting Ipv6 Pim Snooping

    VLAN ID: 100 Total number of neighbors: 4 Neighbor Port Expires Option Flags FE80::1 GE1/0/1 02:02:23 LAN Prune Delay FE80::2 GE1/0/2 03:00:05 LAN Prune Delay FE80::3 GE1/0/3 02:22:13 LAN Prune Delay FE80::4 GE1/0/4 03:07:22 LAN Prune Delay The output shows that Router A, Router B, Router C, and Router D are IPv6 PIM snooping neighbors.

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

    If MLD snooping is not enabled, enter system view and use the mld-snooping command to enable MLD snooping globally. Then, enter VLAN view and use the mld-snooping enable and pim-snooping ipv6 enable commands to enable MLD snooping and IPv6 PIM snooping for the VLAN.

  • Page 361: Configuring Ipv6 Multicast Vlans

    Configuring IPv6 multicast VLANs This section describes IPv6 multicast VLAN, how to configure IPv6 multicast VLANs, and configuration examples. Overview As shown in Figure 99, Host A, Host B, and Host C reside in different VLANs and require the same IPv6 multicast programs-on-demand service.
  • Page 362 Figure 100 Sub-VLAN-based IPv6 multicast VLAN MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in the sub-VLANs. When Router A receives the IPv6 multicast data from the source, it sends only one copy of the multicast traffic to Switch A in the IPv6 multicast VLAN. Switch A sends a separate copy of the data to each sub-VLAN of the IPv6 multicast VLAN.

  • Page 363: Ipv6 Multicast Vlan Configuration Task List

    For more information about MLD snooping, router ports, and member ports, see "Configuring MLD snooping." For more information about VLAN tags, see Layer 2—LAN Switching Configuration Guide. IPv6 multicast VLAN configuration task list Configuration task Remarks Configuring a sub-VLAN-based IPv6 multicast VLAN Required.

  • Page 364: Configuring A Port-Based Ipv6 Multicast Vlan

    Step Command Remarks Enter system view. system-view Configure the specified VLAN as an IPv6 multicast No IPv6 multicast VLAN multicast-vlan ipv6 vlan-id VLAN and enter IPv6 configured by default. multicast VLAN view. Configure the specified By default, an IPv6 multicast VLANs as sub-VLANs of the subvlan vlan-list VLAN has no sub-VLANs.

  • Page 365: Configuring Ipv6 Multicast Vlan Ports

    Step Command Remarks Specify the user VLAN that the current user port belongs VLAN 1 by default. port hybrid pvid vlan vlan-id to as the default VLAN. Configure the current user port to permit the specified A hybrid port permits only VLAN 1 port hybrid vlan vlan-id-list IPv6 multicast VLAN and { tagged | untagged }...

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

    Set the maximum number of By default, the upper limit is 4000 multicast-vlan ipv6 entry-limit forwarding entries for IPv6 for the HPE 5800 switches, and limit multicast VLANs. 1000 for the HPE 5820X switches. Displaying and maintaining an IPv6 multicast...
  • Page 367 • Router A sends IPv6 multicast data to Switch A through the IPv6 multicast VLAN. • Switch A forwards the traffic to the receivers that belong to different user VLANs. Figure 102 Network diagram Source MLD querier Router A GE1/0/1 1::2/64 GE1/0/2 1::1/64...
  • Page 368 [SwitchA-GigabitEthernet1/0/2] port trunk permit vlan 2 3 [SwitchA-GigabitEthernet1/0/2] quit # Configure GigabitEthernet 1/0/3 as a trunk port that permits packets from VLAN 4 and VLAN 5 to pass through. [SwitchA] interface gigabitethernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] port link-type trunk [SwitchA-GigabitEthernet1/0/3] port trunk permit vlan 4 5 [SwitchA-GigabitEthernet1/0/3] quit # Create VLAN 10, assign GigabitEthernet 1/0/1 to this VLAN and enable MLD snooping in the VLAN.
  • Page 369 subvlan list: vlan 2-5 port list: no port # Display the MLD snooping IPv6 multicast group information on Switch A. [SwitchA] display mld-snooping group Total 5 IP Group(s). Total 5 IP Source(s). Total 5 MAC Group(s). Port flags: D-Dynamic port, S-Static port, C-Copy port, P-PIM port Subvlan flags: R-Real VLAN, C-Copy VLAN Vlan(id):2.

  • Page 370: Port-Based Multicast Vlan Configuration Example

    Host port(s):total 1 port(s). GE1/0/3 MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 1 port(s). GE1/0/3 Vlan(id):5. Total 1 IP Group(s). Total 1 IP Source(s). Total 1 MAC Group(s). Router port(s):total 0 port(s). IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 1 port(s).
  • Page 371 • Router A sends IPv6 multicast data to Switch A through the IPv6 multicast VLAN. • Switch A forward the IPv6 multicast data to the receivers that belong to different user VLANs. Figure 103 Network diagram Configuration procedure Enable IPv6 forwarding on each device and assign an IPv6 address and address prefix to each interface according to Figure 103.
  • Page 372 [SwitchA-vlan2] quit # Create VLAN 3 and enable IGMP snooping in the VLAN. (Details not shown.) # Create VLAN 4 and enable IGMP snooping in the VLAN. (Details not shown.) # Configure GigabitEthernet 1/0/2 as a hybrid port. Configure VLAN 2 as the default VLAN. Configure GigabitEthernet 1/0/2 to permit packets of VLAN 2 to pass and untag the packets when forwarding them.
  • Page 373 IP group(s):the following ip group(s) match to one mac group. IP group address:FF1E::101 (::, FF1E::101): Host port(s):total 3 port(s). GE1/0/2 GE1/0/3 GE1/0/4 MAC group(s): MAC group address:3333-0000-0101 Host port(s):total 3 port(s). GE1/0/2 GE1/0/3 GE1/0/4 The output shows that MLD snooping is maintaining router ports and member ports in VLAN 10.

  • Page 374: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding This chapter describes IPv6 multicast routing and forwarding, how to configure IPv6 multicast routing and forwarding, configuration examples, and troubleshooting methods. Overview In IPv6 multicast implementations, the following types of tables implement multicast routing and forwarding: •...
  • Page 375 The router searches its IPv6 MBGP routing table and automatically selects an optimal MBGP route to the packet source address. The outgoing interface of the route is the RPF interface and the next hop is the RPF neighbor. The router selects one of the optimal routes as the RPF route according to the following principles: If the router uses the longest match principle, it selects the longest matching route as the RPF route.

  • Page 376: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

    104. The IPv6 multicast forwarding table on Router C contains the (S, G) entry, with VLAN-interface 20 as the RPF interface. Figure 104 RPF check process IPv6 Routing Table on Router C Receiver Router B Destination/Prefix Interface 2000::/16 Vlan-int20 Vlan-int10 Source Router A 2000::101/16...

  • Page 377: Configuration Task List

    To make sure the maximum transmission unit (MTU) feature works properly in multicast forwarding through GRE tunnels, configure the same MTU value for all Tunnel interfaces on an HPE 5820X switch or HPE 5800 switch. For more information about MTU configuration on a Tunnel interface, see Layer 3—IP Services Configuration Guide.

  • Page 378: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding This section describes how to configure IPv6 multicast routing and forwarding. Configuration prerequisites Before you configure IPv6 multicast routing and forwarding, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer.

  • Page 379: Configuring An Ipv6 Multicast Forwarding Range

    Configure the maximum multicast ipv6 forwarding-table By default, the upper limit is 4000 number of entries in the IPv6 route-limit limit for the HPE 5800 switches, and multicast forwarding table. 1000 for the HPE 5820X switches. Configure the maximum Optional.

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

    Configure the maximum multicast forwarding-table By default, the upper limit is 4000 number of entries in the route-limit limit for the HPE 5800 switches, and multicast forwarding table. 1000 for the HPE 5820X switches. Configure the maximum number of downstream Optional.

  • Page 381: Ipv6 Multicast Routing And Forwarding Configuration Example

    Task Command Remarks display multicast ipv6 [ all-instance | vpn-instance vpn-instance-name ] routing-table [ ipv6-source-address [ prefix-length ] | Display information about ipv6-group-address [ prefix-length ] | the IPv6 multicast routing incoming-interface { interface-type Available in any view. table. interface-number | register } | outgoing-interface { exclude | include | match } { interface-type interface-number | register } ] * [ | { begin | exclude | include } regular-expression ]...
  • Page 382 Figure 106 Network diagram Configuration procedure Enable IPv6 forwarding on each switch, and assign an IPv6 address and prefix length to each interface as shown in Figure 106. (Details not shown.) Configure a GRE tunnel: # Create service loopback group 1 on Switch A and specify its service type as Tunnel. <SwitchA>...
  • Page 383 [SwitchC-GigabitEthernet1/0/3] undo ndp enable [SwitchC-GigabitEthernet1/0/3] undo lldp enable [SwitchC-GigabitEthernet1/0/3] port service-loopback group 1 [SwitchC-GigabitEthernet1/0/3] quit # Create interface Tunnel 0 on Switch C, assign an IPv6 address and prefix length to this interface, and reference service loopback group 1 on this interface. [SwitchC] interface tunnel 0 [SwitchC-Tunnel0] ipv6 address 5001::2 64 [SwitchC-Tunnel0] service-loopback-group 1...
  • Page 384 [SwitchC-Vlan-interface102] ospfv3 1 area 0 [SwitchC-Vlan-interface102] quit [SwitchC] interface tunnel 0 [SwitchC-Tunnel0] ospfv3 1 area 0 [SwitchC-Tunnel0] quit Enable IPv6 multicast routing, IPv6 PIM-DM, and MLD: # On Switch A, enable IPv6 multicast routing globally and enable IPv6 PIM-DM on each interface.

  • Page 385: Troubleshooting Ipv6 Multicast Policy Configuration

    1: Vlan-interface200 Protocol: mld, UpTime: 00:04:25, Expires: never (1001::100, FF1E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel0 Upstream neighbor: FE80::A01:101:1 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: never The output shows that Switch A is the RPF neighbor of Switch C and the IPv6 multicast data from Switch A is delivered over a GRE tunnel to Switch C.

  • Page 386: Configuring Mld

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

  • Page 388: How Mldv2 Operates

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

  • Page 389: Mld Message Types

    MLD state A multicast router that is running MLDv2 maintains the multicast address state per multicast address per attached subnet. The multicast address state consists of the following information: • Filter mode—The router keeps tracing the Include or Exclude state. •...
  • Page 390 Table 10 MLDv2 query message field description Field Description Type = 130 Message type. For a query message, this field is set to 130. Code Initialized to zero. Checksum Standard IPv6 checksum. Maximum response delay allowed before a host sends a report Maximum Response Delay message.

  • Page 391: Mld Ssm Mapping

    Table 11 MLDv2 report message field description Field Description Type = 143 Message type. For a report message, this field is set to 143. The Reserved fields are set to 0 on transmission and ignored on Reserved reception. Checksum Standard IPv6 checksum. Number of Multicast Address This field indicates how many IPv6 multicast address records are present Records...

  • Page 392: Mld Proxying

    • If G is not in the IPv6 SSM group range, Router A cannot provide the SSM service but can provide the ASM service. • If G is in the IPv6 SSM group range but no MLD SSM mappings have been configured for the IPv6 multicast group G on Router A, Router A cannot provide SSM service and drops the packet.

  • Page 393: Mld Support For Vpns

    multicast address, filter mode, and source list. Such an entry is a collection of members in the same multicast group on each downstream interface. A proxy device performs host functions on the upstream interface based on the database. It responds to the queries according to the information in the database or sends join/leave messages when the database changes.

  • Page 394: Configuring Basic Mld Functions

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

  • Page 395: Configuring The Mld Version

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, an interface belongs to Bind the interface with a VPN ip binding vpn-instance the public network, and is not instance. vpn-instance-name bound with any VPN instance. Enable MLD. Disabled by default. mld enable For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance commands, see MPLS Command Reference.

  • Page 396: Configuring An Ipv6 Multicast Group Filter

    Enter interface view. interface-number By default, the upper limit is Configure the maximum number of 4000 for the HPE 5800 IPv6 multicast groups that the mld group-limit limit switches, and 1000 for the interface can join. HPE 5820X switches.

  • Page 397: Adjusting Mld Performance

    Adjusting MLD performance This section describes how to adjust MLD performance. Configuration prerequisites Before adjusting MLD performance, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain can be interoperable at the network layer. •...

  • Page 398: Configuring Mld Query And Response Parameters

    Step Command Remarks messages. Configuring Router-Alert option handling methods on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the interface to By default, the device does not discard any MLD message examine MLD messages for the mld require-router-alert without the Router-Alert Router-Alert option.
  • Page 399 • To avoid incorrect multicast group member removals, set the MLD query interval greater than the maximum response delay for MLD general queries. Configuration procedure To configure MLD query and response parameters globally: Step Command Remarks Enter system view. system-view Enter public network MLD mld [ vpn-instance view or VPN instance MLD...

  • Page 400: Enabling Mld Fast-Leave Processing

    Step Command Remarks By default, the startup query count Configure the startup query is the same as the MLD querier's mld startup-query-count value count. robustness variable. Configure the MLD query 125 seconds by default. mld timer query interval interval. Configure the maximum response delay for MLD 10 seconds by default.

  • Page 401: Enabling The Mld Host Tracking Function

    NOTE: The MLD fast-leave processing configuration is effective on Layer 3 interfaces other than VLAN interfaces, including Layer 3 Ethernet ports, Layer 3 aggregate interfaces, and Tunnel interfaces. Enabling the MLD host tracking function With the MLD host tracking function, the switch can record the information of the member hosts that are receiving IPv6 multicast traffic, including the host IPv6 address, running duration, and timeout time.

  • Page 402: Configuration Prerequisites

    Configuration prerequisites Before you configure the MLD SSM mapping feature, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain can be interoperable at the network layer. • Configure basic MLD functions.

  • Page 403: Enabling Mld Proxying

    • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Enable IPv6 multicast routing. Enabling MLD proxying You can enable MLD proxying on the interface in the direction toward the root of the multicast forwarding tree to make the device serve as an MLD proxy.

  • Page 404: Displaying And Maintaining Mld

    Step Command Remarks Enable IPv6 multicast forwarding on a non-querier Disabled by default. mld proxying forwarding downstream interface. Displaying and maintaining MLD CAUTION: The reset mld group command might cause an interruption of receivers' reception of multicast data. To display and maintain MLD: Task Command Remarks...

  • Page 405: Mld Configuration Examples

    Task Command Remarks [ prefix-length ] | ipv6-group-address [ prefix-length ] | flags { act | suc } ] * [ | { begin | exclude | include } regular-expression ] display mld ssm-mapping ipv6-group-address [ | { begin | Display MLD SSM mappings.
  • Page 406 • Receivers receive VOD information in the multicast mode. Receivers of different organizations form stub networks N1 and N2. Host A and Host C are multicast receivers in N1 and N2, respectively. • MLDv1 runs between Switch A and N1. MLDv1 runs between the other two switches (Switch B and Switch C) and N2.

  • Page 407: Mld Ssm Mapping Configuration Example

    <SwitchB> system-view [SwitchB] multicast ipv6 routing-enable [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] mld enable [SwitchB-Vlan-interface200] pim ipv6 dm [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 201 [SwitchB-Vlan-interface201] pim ipv6 dm [SwitchB-Vlan-interface201] quit # On Switch C, enable IPv6 multicast routing, enable IPv6 PIM-DM on each interface, and enable MLD on VLAN-interface 200.
  • Page 408 • MLDv2 runs on Switch D's VLAN-interface 400. The receiver host runs MLDv1, and does not support MLDv2. Therefore, the Receiver host cannot specify expected multicast sources in its membership reports. • Source 1, Source 2, and Source 3 send IPv6 multicast packets to multicast groups in the IPv6 SSM group range.
  • Page 409 [SwitchD-Vlan-interface400] mld ssm-mapping enable [SwitchD-Vlan-interface400] pim ipv6 sm [SwitchD-Vlan-interface400] quit [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim ipv6 sm [SwitchD-Vlan-interface103] quit [SwitchD] interface vlan-interface 104 [SwitchD-Vlan-interface104] pim ipv6 sm [SwitchD-Vlan-interface104] quit # On Switch A, enable IPv6 multicast routing, and enable IPv6 PIM-SM on each interface. <SwitchA>...

  • Page 410: Mld Proxying Configuration Example

    1001::1 3001::1 # Display the IPv6 multicast group information created based on the configured MLD SSM mappings on Switch D. [SwitchD] display mld ssm-mapping group Total 1 MLD SSM-mapping Group(s). Interface group report information Vlan-interface400 (4001::2): Total 1 MLD SSM-mapping Group reported Group Address: FF3E::101 Last Reporter: 4001::1 Uptime: 00:02:04...
  • Page 411 Figure 115 Network diagram Configuration procedure Enable IPv6 forwarding on each switch and assign an IPv6 address and prefix length to each interface according to Figure 115. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-DM, MLD, and MLD proxying: # On Switch A, enable IPv6 multicast routing, IPv6 PIM-DM on VLAN-interface 101, and MLD on VLAN-interface 100.

  • Page 412: Troubleshooting Mld

    # Display the MLD group information on Switch A. [SwitchA] display mld group Total 1 MLD Group(s). Interface group report information of VPN-Instance: public net Vlan-interface100(2001::1): Total 1 MLD Groups reported Group Address Last Reporter Uptime Expires ff3e::101 2001::2 00:02:04 00:01:15 The output shows that the MLD reports sent from the hosts are forwarded to Switch A through the proxy interface, VLAN-interface 100 of Switch B.

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

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

  • Page 414: Configuring Ipv6 Pim

    Configuring IPv6 PIM This chapter describes IPv6 PIM, how to configure IPv6 PIM, configuration examples, and troubleshooting methods. Overview IPv6 PIM provides IPv6 multicast forwarding by leveraging IPv6 unicast static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as RIPng, OSPFv3, IS-ISv6, or BGP4+.
  • Page 415 • SPT establishment • Graft • Assert Neighbor discovery In an IPv6 PIM domain, each IPv6 PIM interface periodically multicasts IPv6 PIM hello messages to all other IPv6 PIM routers on the local subnet. Through the exchanging of hello messages, all IPv6 PIM routers determine their IPv6 PIM neighbors, maintain IPv6 PIM neighboring relationships with other routers, and build and maintain SPTs.
  • Page 416 The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again when it no longer has any multicast receiver. Graft A previously pruned branch might have new downstream receivers. To reduce the latency for resuming the forwarding capability of this branch, a graft mechanism is used as follows: The node that needs to receive IPv6 multicast data sends a graft message toward its upstream node, as a request to join the SPT again.

  • Page 417: Ipv6 Pim-Sm

    IPv6 PIM-SM IPv6 PIM-DM uses the flood-and-prune principle to build SPTs for IPv6 multicast data distribution. Although an SPT has the shortest path, it is built with a low efficiency. Therefore, the PIM-DM mode is not suitable for large-sized and medium-sized networks. IPv6 PIM-SM is a type of sparse-mode IPv6 multicast protocol.
  • Page 418 A DR is elected on a multi-access subnet by means of comparison of the priorities and IPv6 link-local addresses carried in hello messages. NOTE: MLD must be enabled on a device that acts as a receiver-side DR before receivers attached to this device can join IPv6 multicast groups through this DR.
  • Page 419 NOTE: • An RP can provide services for multiple IPv6 multicast groups, but an IPv6 multicast group only uses one RP. • A device can act as a C-RP and a C-BSR at the same time. As shown in Figure 119, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR.
  • Page 420 Value Description 0x00000010. & Logical operator of "and." Logical operator of "exclusive-or." Modulo operator, which gives the remainder of an integer division. Embedded RP The embedded RP mechanism enables a router to resolve the RP address from an IPv6 multicast address so that the IPv6 multicast group is mapped to an RP.
  • Page 421 The IPv6 multicast data addressed to the IPv6 multicast group G flows through the RP, reaches the corresponding DR along the established RPT, and finally is delivered to the receiver. When a receiver is no longer interested in the IPv6 multicast data addressed to a multicast group G: The directly connected DR sends a prune message, which goes hop by hop along the RPT to the RP.

  • Page 422: Ipv6 Bidir-Pim

    NOTE: The RP is configured to initiate a switchover to SPT in the above description. Otherwise, the DR at the IPv6 multicast source side keeps encapsulating multicast data in register messages, and the registration process will not stop unless no outgoing interfaces exist in the (S, G) entry on the RP. Switchover to SPT In an IPv6 PIM-SM domain, an IPv6 multicast group corresponds to one RP and one RPT.
  • Page 423 IPv6 BIDIR-PIM is suitable for networks with dense multicast sources and dense receivers. The operating mechanism of IPv6 BIDIR-PIM is summarized as follows: • Neighbor discovery • RP discovery • DF election • Bidirectional RPT building Neighbor discovery IPv6 BIDIR-PIM uses the same neighbor discovery mechanism as IPv6 PIM-SM does. For more information, see "Neighbor discovery."...
  • Page 424 routers on the local subnet. As a result, the RP (Router E) receives duplicate multicast packets. With the DF election mechanism, once receiving the RP information, Router B and Router C initiate a DF election process for the RP: Router B and Router C multicast DF election messages to all PIM routers (224.0.0.13). The election messages carry the RP's address, and the priority and metric of the unicast route, MBGP route, or multicast static route to the RP.

  • Page 425: Ipv6 Administrative Scoping

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

  • Page 427: Ipv6 Pim-Ssm

    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. Table 13 lists the possible values of the scope field. Table 13 Values of the Scope field Value Meaning...

  • Page 428: Relationship Among Ipv6 Pim Protocols

    Figure 127 Building an SPT in IPv6 PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message IPv6 multicast packets Host C As shown in Figure 127, Hosts B and C are IPv6 multicast information receivers. They send an MLDv2 report message to the respective DRs to announce that they are interested in the information about the specific IPv6 multicast source S and that sent to the IPv6 multicast group G.

  • Page 429: Ipv6 Pim Support For Vpns

    Figure 128 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 430: Ipv6 Pim-Dm Configuration Task List

    IPv6 PIM-DM configuration task list Task Remarks Enabling IPv6 PIM-DM Required. Enabling state-refresh capability Optional. Configuring state refresh parameters Optional. Configuring IPv6 PIM-DM graft retry period Optional. Configuring common IPv6 PIM features Optional. Configuration prerequisites Before you configure IPv6 PIM-DM, complete the following tasks: •...

  • Page 431: Configuring State Refresh Parameters

    IPv6 PIM-DM domain, to refresh the prune timer state of all routers on the path. A multi-access subnet can have the state-refresh capability only if the state-refresh capability is enabled on all IPv6 PIM routers on the subnet. To enable the state-refresh capability: Step Command Remarks...

  • Page 432: Configuring Ipv6 Pim-Sm

    messages at a configurable interval (graft retry period) until it receives a graft-ack message from the upstream router. To configure the IPv6 PIM-DM graft retry period: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the graft retry pim ipv6 timer graft-retry period.

  • Page 433: Configuration Prerequisites

    Configuration prerequisites Before you configure IPv6 PIM-SM, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. • Determine the IP address of a static RP and the ACL rule defining the range of IPv6 multicast groups to be served by the static RP.

  • Page 434: Configuring An Rp

    Step Command Remarks Configure an RD for the VPN route-distinguisher Not configured by default. instance. route-distinguisher Enable IPv6 multicast Disabled by default. multicast ipv6 routing-enable routing. interface interface-type Enter interface view. interface-number By default, an interface belongs to Bind the interface with a VPN ip binding vpn-instance the public network, and is not instance.
  • Page 435 To guard against C-RP spoofing, you must configure a legal C-RP address range and the range of IPv6 multicast groups to be served on the BSR. In addition, because every C-BSR has a chance to become the BSR, you need to configure the same filtering policy on all C-BSRs in the IPv6 PIM-SM domain.

  • Page 436: Configuring A Bsr

    its bootstrap messages. The BSR then floods the bootstrap messages to all IPv6 routers in the network. Each C-RP encapsulates a timeout value in its C-RP-Adv messages. After receiving a C-RP-Adv message, the BSR obtains this timeout value and starts a C-RP timeout timer. If the BSR fails to obtain a subsequent C-RP-Adv message from the C-RP when the timer times out, the BSR assumes the C-RP to have expired or become unreachable.
  • Page 437 information. For security purposes, you can configure a legal BSR address range on all routers on the network. Therefore, all routers can discard BSMs that are out of the legal address range. These preventive measures can partially protect the security of BSRs in a network. However, if an attacker controls a legal BSR, the problem still exists.
  • Page 438 Step Command Remarks Enter public network IPv6 pim ipv6 [ vpn-instance PIM view or VPN instance vpn-instance-name ] IPv6 PIM view Optional. Configure the hash mask c-bsr hash-length hash-length length. 126 by default. Optional. Configure the C-BSR priority. c-bsr priority priority 64 by default.

  • Page 439: Configuring Ipv6 Administrative Scoping

    • After receiving a BSMF that contains the RP-set information of one group range, a non-BSR router updates corresponding RP-set information directly. • If the RP-set information of one group range is carried in multiple BSMFs, a non-BSR router updates corresponding RP-set information after receiving all these BSMFs. Because the RP-set information contained in each segment is different, loss of some IP fragments will not result in dropping of the entire message.

  • Page 440: Configuring Ipv6 Multicast Source Registration

    Perform the following configuration on routers that you want to configure as a ZBR. To configure an IPv6 admin-scope zone boundary: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number multicast ipv6 boundary { ipv6-group-address prefix-length By default, no multicast Configure an IPv6 multicast | scope { scope-id | admin-local |...

  • Page 441: Disabling Switchover To Spt

    In view of information integrity of register messages in the transmission process, you can configure the device to calculate the checksum based on the entire register messages. However, to reduce the workload of encapsulating data in register messages and for the sake of interoperability, do not use this checksum calculation method.

  • Page 442: Configuring Ipv6 Bidir-Pim

    Step Command Remarks Enter system view. system-view Enter public network IPv6 pim ipv6 [ vpn-instance PIM view or VPN instance vpn-instance-name ] IPv6 PIM view. Optional. spt-switch-threshold infinity By default, the device switches to Disable the switchover to [ group-policy acl6-number the SPT immediately after it [ order order-value ] ] receives the first IPv6 multicast...

  • Page 443: Enabling Ipv6 Pim-Sm

    • Determine the C-RP priority and the IPv6 ACL that defines the range of IPv6 multicast groups to be served by each C-RP. • Determine the legal C-RP address range and the IPv6 ACL that defines the range of IPv6 multicast groups to be served.
  • Page 444 An RP can be manually configured or dynamically elected through the BSR mechanism. For a large IPv6 PIM network, static RP configuration is a tedious job. Generally, static RP configuration is just a backup means for the dynamic RP election mechanism to enhance the robustness and operation manageability of a multicast network.

  • Page 445: Configuring A Bsr

    RP or the RP dynamically calculated based on the BSR mechanism. Thus, the DR does not need to know the RP address beforehand. Perform this configuration on all routers in the IPv6 BIDIR-PIM domain. To enable embedded RP: Step Command Remarks Enter system view.
  • Page 446 Configuring a C-BSR C-BSRs must be configured on routers on the backbone network. When configuring a router as a C-BSR, be sure to specify an IPv6 PIM-SM-enabled interface on the router. The BSR election process is as follows: • Initially, every C-BSR assumes itself to be the BSR of the IPv6 BIDIR-PIM domain, and uses its interface IPv6 address as the BSR address to send bootstrap messages.
  • Page 447 To configure an IPv6 BIDIR-PIM domain border: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure an IPv6 By default, no IPv6 BIDIR-PIM pim ipv6 bsr-boundary BIDIR-PIM domain border. domain border is configured. Configuring the global C-BSR parameters In each IPv6 BIDIR-PIM domain, a unique BSR is elected from C-BSRs.

  • Page 448: Configuring Ipv6 Administrative Scoping

    Step Command Remarks The BS period value must be smaller than the BS timeout timer. Optional. By default, the BS timeout timer is determined by the formula "BS Configure the BS timeout timeout timer = BS period × 2 + c-bsr holdtime interval timer.
  • Page 449 Perform the following configuration on all routers in the IPv6 PIM-SM domain. To enable IPv6 administrative scoping: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. pim ipv6 Enable IPv6 administrative Disabled by default. c-bsr admin-scope scoping. Configuring an IPv6 admin-scope zone boundary The boundary of each IPv6 admin-scope zone is formed by ZBRs.

  • Page 450: Configuring Ipv6 Pim-Ssm

    Step Command Remarks Enter IPv6 PIM view. pim ipv6 c-bsr scope { scope-id | admin-local | global | Configure a C-BSR for an No C-BSRs are configured for an organization-local | site-local } admin-scope zone. admin-scope zone by default. [ hash-length hash-length | priority priority ] * Configuring IPv6 PIM-SSM This section describes how to configure IPv6 PIM-SSM.

  • Page 451: Configuring The Ipv6 Ssm Group Range

    Step Command Remarks Enable IPv6 PIM-SM. Disabled by default. pim ipv6 sm Enabling IPv6 PIM-SM in a VPN instance Step Command Remarks Enter system view. system-view Create a VPN instance and ip vpn-instance enter VPN instance view. vpn-instance-name Configure an RD for the VPN route-distinguisher No RD is configured by default.

  • Page 452: Configuring Common Ipv6 Pim Features

    Configuring common IPv6 PIM features For the configuration tasks in this section, the following rules apply: • The configurations made in IPv6 PIM view are effective on all interfaces. The configurations made in interface view are effective only on the current interface. •...

  • Page 453: Configuring An Ipv6 Multicast Data Filter

    • Determine the DSCP value for PIM messages. Configuring an IPv6 multicast data filter In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, routers can examine passing-by IPv6 multicast data based on the configured filtering rules and determine whether to continue forwarding the IPv6 multicast data.

  • Page 454: Configuring Ipv6 Pim Hello Options

    Configuring IPv6 PIM hello options In both an IPv6 PIM-DM domain and an IPv6 PIM-SM domain, the hello messages sent among routers contain the following configurable options: • DR_Priority (for IPv6 PIM-SM only)—Priority for DR election. The higher the priority is, the easier it is for the router to win DR election.

  • Page 455: Configuring The Prune Delay Timer

    Step Command Remarks Disable join suppression. Enabled by default. hello-option neighbor-tracking Configuring hello options on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the priority for DR pim ipv6 hello-option dr-priority election.
  • Page 456 After receiving a hello message, an IPv6 PIM router waits a random period, which is smaller than the maximum delay between hello messages, before sending a hello message. This avoids collisions that occur when multiple IPv6 PIM routers send hello messages simultaneously. An IPv6 PIM router periodically sends join/prune messages to its upstream for state update.

  • Page 457: Configuring Join/Prune Message Sizes

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

  • Page 458: Setting The Dscp Value For Ipv6 Pim Messages

    Step Command Remarks Enter interface view. interface interface-type interface-number Enable IPv6 PIM to Disabled by default. pim ipv6 bfd enable work with BFD. For more information about BFD, see High Availability Configuration Guide. Setting the DSCP value for IPv6 PIM messages Step Command Remarks...

  • Page 459: Ipv6 Pim Configuration Examples

    Task Command Remarks about join/prune vpn-instance-name ] join-prune mode { sm [ flags messages to send. flag-value ] | ssm } [ interface interface-type interface-number | neighbor ipv6-neighbor-address ] * [ verbose ] [ | { begin | exclude | include } regular-expression ] display pim ipv6 [ all-instance | vpn-instance Display IPv6 PIM...
  • Page 460 Figure 129 Network diagram Device Interface IPv6 address Device Interface IPv6 address Switch A VLAN-interface 100 1001::1/64 Switch VLAN-interface 300 4001::1/64 VLAN-interface 103 1002::1/64 VLAN-interface 103 1002::2/64 Switch B VLAN-interface 200 2001::1/64 VLAN-interface 101 2002::2/64 VLAN-interface 101 2002::1/64 VLAN-interface 102 3001::2/64 Switch C VLAN-interface 200...
  • Page 461 # On Switch D, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface. <SwitchD> system-view [SwitchD] multicast ipv6 routing-enable [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] pim ipv6 dm [SwitchD-Vlan-interface300] quit [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim ipv6 dm [SwitchD-Vlan-interface103] quit [SwitchD] interface vlan-interface 101 [SwitchD-Vlan-interface101] pim ipv6 dm [SwitchD-Vlan-interface101] quit...

  • Page 462: 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: never (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: Vlan-interface103 Upstream neighbor: 1002::2...
  • Page 463 • VLAN-interface 105 on Switch D and VLAN-interface 102 on Switch E act as C-BSRs and C-RPs. The C-BSR on Switch E has a higher priority. The IPv6 multicast group range served by the C-RP is FF0E::101/64. Modify the hash mask length to map a certain number of consecutive IPv6 group addresses within the range to the two C-RPs.
  • Page 464 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] pim ipv6 sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim ipv6 sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim ipv6 sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD and IPv6 PIM-SM on Switch B and Switch C in the same way.
  • Page 465 Hash mask length: 128 State: Accept Preferred Uptime: 00:04:22 Expires: 00:01:46 # Display information about the BSR and locally configured C-RP in effect on Switch D. [SwitchD] display pim ipv6 bsr-info VPN-Instance: public net Elected BSR Address: 1003::2 Priority: 20 Hash mask length: 128 State: Elected Uptime: 00:05:26...
  • Page 466 Priority: 192 HoldTime: 130 Uptime: 00:05:19 Expires: 00:02:11 RP: 1003::2 Priority: 192 HoldTime: 130 Uptime: 00:05:19 Expires: 00:02:11 Assume that Host A needs to receive information addressed to the IPv6 multicast group G FF0E::100. The RP corresponding to the multicast group G is Switch E as a result of hash calculation, so an RPT is built between Switch A and Switch E.

  • Page 467: Ipv6 Pim-Sm Admin-Scope Zone Configuration Example

    Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF0E::100) RP: 1003::2 Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:14:44 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface105 Protocol: mld, UpTime: 00:14:44, Expires: 00:02:26 # Display IPv6 PIM multicast routing table information on Switch E.
  • Page 468 Figure 131 Network diagram IPv6 admin-scope 1 Vlan-int500 Receiver Switch G Host A Source 1 Vlan-int109 Source 3 Vlan-int100 Vlan-int200 Vlan-int109 Vlan-int101 Vlan-int102 Vlan-int102 Switch F Vlan-int101 Vlan-int107 Switch B Switch A Switch C Switch I Switch H Vlan-int107 Vlan-int110 Vlan-int106 Vlan-int104 Switch D...
  • Page 469 Device Interface IPv6 address Device Interface IPv6 address Switch A VLAN-interface 100 1001::1/64 Switch D VLAN-interface 3002::2/64 VLAN-interface 101 1002::1/64 VLAN-interface 6001::1/64 Switch B VLAN-interface 200 2001::1/64 VLAN-interface 6002::1/64 VLAN-interface 101 1002::2/64 Switch E VLAN-interface 7001::1/64 VLAN-interface 103 2002::1/64 VLAN-interface 3003::2/64 VLAN-interface 102 2003::1/64...
  • Page 470 # Enable IPv6 multicast routing and administrative scoping, enable IPv6 PIM-SM and MLD on Switch E and Switch I in the same way. (Details not shown.) # On Switch B, enable IPv6 multicast routing, enable IPv6 administrative scoping, and enable IPv6 PIM-SM on each interface.
  • Page 471 [SwitchB] pim ipv6 [SwitchB-pim6] c-bsr scope 4 [SwitchB-pim6] c-bsr 1002::2 [SwitchB-pim6] c-rp 1002::2 scope 4 [SwitchB-pim6] quit # On Switch D, configure the service scope of RP advertisements and configure VLAN-interface 104 as a C-BSR and C-RP of admin-scope zone 2. [SwitchD] pim ipv6 [SwitchD-pim6] c-bsr scope 4 [SwitchD-pim6] c-bsr 3002::2...
  • Page 472 # Display information about the BSR and locally configured C-RP on Switch D. [SwitchD] display pim ipv6 bsr-info VPN-Instance: public net Elected BSR Address: 8001::1 Priority: 64 Hash mask length: 126 State: Accept Preferred Scope: 14 Uptime: 00:01:45 Expires: 00:01:25 Elected BSR Address: 3002::2 Priority: 64 Hash mask length: 126...
  • Page 473 Next advertisement scheduled at: 00:00:55 # Display the RP information on Switch B. [SwitchB] display pim ipv6 rp-info VPN-Instance: public net PIM-SM BSR RP information: prefix/prefix length: FF0E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF1E::/16 RP: 8001::1 Priority: 192 HoldTime: 130...
  • Page 474 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF7E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF8E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF9E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39...
  • Page 475 prefix/prefix length: FFDE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFEE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF04::/16 RP: 1002::2 Priority: 192 HoldTime: 130...
  • Page 476 prefix/prefix length: FF44::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF54::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF64::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF74::/16 RP: 1002::2 Priority: 192 HoldTime: 130...
  • Page 477 Expires: 00:01:51 prefix/prefix length: FFB4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFC4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFD4::/16 RP: 1002::2 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFE4::/16 RP: 1002::2 Priority: 192...
  • Page 478 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF2E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF3E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF4E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39...
  • Page 479 prefix/prefix length: FF8E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FF9E::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFAE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 prefix/prefix length: FFBE::/16 RP: 8001::1 Priority: 192 HoldTime: 130...

  • Page 480: Ipv6 Bidir-Pim Configuration Example

    prefix/prefix length: FFFE::/16 RP: 8001::1 Priority: 192 HoldTime: 130 Uptime: 00:03:39 Expires: 00:01:51 IPv6 BIDIR-PIM configuration example Network requirements As shown in Figure 132: • Source 1 and Source 2 send different IPv6 multicast information to IPv6 multicast group FF14::101. Host A and Host B receive IPv6 multicast information from the two sources. •...
  • Page 481 Configure OSPFv3 on the switches in the IPv6 BIDIR-PIM domain to make sure the switches are interoperable at the network layer. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-SM, IPv6 BIDIR-PIM, and MLD: # On Switch A, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM.
  • Page 482 # On Switch D, enable IPv6 multicast routing, enable MLD in VLAN interface 300, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM. <SwitchD> system-view [SwitchD] multicast ipv6 routing-enable [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] mld enable [SwitchD-Vlan-interface300] pim ipv6 sm [SwitchD-Vlan-interface300] quit [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] pim ipv6 sm...
  • Page 483 Loop0 Vlan102 01:06:07 FE80::20F:E2FF: FE15:5601 (local) Vlan103 01:06:07 FE80::20F:E2FF: FE15:5602 (local) # Display DF information of IPv6 BIDIR-PIM on Switch D. [SwitchD] display pim ipv6 df-info VPN-Instance: public net RP Address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Vlan300 01:19:53 FE80::200:5EFF: FE71:2803 (local) Vlan400...

  • Page 484: Ipv6 Pim-Ssm Configuration Example

    Total 1 RP matched 00001. RP Address: 6001::1 MID: 0, Flags: 0x2100000:0 Uptime: 00:07:21 RPF interface: LoopBack0 List of 2 DF interfaces: 1: Vlan-interface102 2: Vlan-interface103 # Display the DF information of the IPv6 multicast forwarding table on Switch D. [SwitchD] display multicast ipv6 forwarding-table df-info Multicast DF information of VPN-Instance: public net Total 1 RP...
  • Page 485 Figure 133 Network diagram Device Interface IPv6 address Device Interface IPv6 address Switch A VLAN-interface 100 1001::1/64 Switch D VLAN-interface 300 4001::1/64 VLAN-interface 101 1002::1/64 VLAN-interface 101 1002::2/64 VLAN-interface 102 1003::1/64 VLAN-interface 105 4002::1/64 Switch B VLAN-interface 200 2001::1/64 Switch E VLAN-interface 104 3001::2/64 VLAN-interface 103...
  • Page 486 [SwitchA-Vlan-interface101] pim ipv6 sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim ipv6 sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD and IPv6 PIM-SM on Switch B and Switch C in the same way. (Details not shown.) # Enable IPv6 multicast routing and IPv6 PIM-SM on Switch D and Switch E in the same way. (Details not shown.) Configure the IPv6 SSM group range: # Configure the IPv6 SSM group range to be FF3E::/64 on Switch A.

  • Page 487: Troubleshooting Ipv6 Pim

    Protocol: mld, UpTime: 00:00:11, Expires: 00:03:25 # Display information about the IPv6 PIM multicast routing table on Switch D. [SwitchD] display pim ipv6 routing-table VPN-Instance: public net 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...

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

    Use the display pim ipv6 interface verbose command to verify that the same PIM mode is enabled on the RPF interface and the corresponding interface of the RPF neighbor router. Use the display current-configuration command to verify the IPv6 PIM mode information on each interface.

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

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

  • Page 490: Configuring Ipv6 Mbgp

    Configuring IPv6 MBGP This chapter covers configuration tasks related to MBGP for IPv6 multicast. For information about BGP and IPv6 BGP, see Layer 3—IP Routing Configuration Guide. Overview IETF defined Multiprotocol BGP (MP-BGP) to enable BGP to carry routing information for multiple network-layer protocols.

  • Page 491: Configuring Basic Ipv6 Mbgp Functions

    Task Remarks Configuring the maximum number of ECMP routes Optional Configuring an IPv6 MBGP peer group Optional Configuring a large scale IPv6 Configuring IPv6 MBGP community Optional MBGP network Configuring an IPv6 MBGP route reflector Optional Configuring basic IPv6 MBGP functions Refer to the following information for details about configuring basic IPv6 MBGP functions.

  • Page 492: Controlling Route Distribution And Reception

    To configure a preferred value for routes from a peer or a peer group: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP address ipv6-family multicast family view. Specify a preferred value for peer { ipv6-group-name | Optional.

  • Page 493: Configuring Ipv6 Mbgp Route Summarization

    Step Command Description from another routing [ process-id [ med med-value | The import-route command protocol. route-policy route-policy-name ] cannot redistribute any IGP default route if the default-route imported command is not configured. Configuring IPv6 MBGP route summarization To reduce the routing table size on medium and large BGP networks, you must configure route summarization on IPv6 MBGP routers.

  • Page 494: Configuring Inbound Ipv6 Mbgp Route Filtering

    To configure outbound IPv6 MBGP route filtering: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 MBGP ipv6-family multicast address family view. • Configure the filtering of outgoing routes: filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } Use at least one command.

  • Page 495: Configuring Ipv6 Mbgp Route Dampening

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

  • Page 496: Configuration Prerequisites

    • Default local preference attribute • MED attribute • NEXT_HOP attribute • AS_PATH attribute Configuration prerequisites Before you configure IPv6 MBGP route attributes, complete the following tasks: • Enable IPv6. • Configure basic IPv6 MBGP functions. Configuring IPv6 MBGP route preferences Step Command Remarks...

  • Page 497: Configuring The Next_Hop Attribute

    Step Command Remarks value. 0 by default. Enable the comparison of the Optional. MED for routes from different compare-different-as-med Not enabled by default. ASs. Enable the comparison of the Optional. MED for routes from each bestroute compare-med Disabled by default. Enable the comparison of the Optional.

  • Page 498: Tuning And Optimizing Ipv6 Mbgp Networks

    Step Command Remarks considering the AS path Enabled by default. during best route selection. Optional. Configure updates to a peer or a peer group to carry only peer { ipv6-group-name | Outbound IPv6 MBGP updates the public AS number in the ipv6-address } public-as-only carrying private AS numbers by AS path of routes.

  • Page 499: Enabling The Ipv6 Mbgp Orf Capability

    soft-reset IPv6 MBGP connections to refresh the IPv6 MBGP routing table and apply the new policy without terminating IPv6 MBGP connections. To perform soft reset manually: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter IPv6 address family ipv6-family view.

  • Page 500: Configuring The Maximum Number Of Ecmp Routes

    Step Command Remarks Enter IPv6 MBGP address ipv6-family multicast family view. peer { group-name | Enable the ORF IP prefix ipv6-address } negotiation capability for a Not enabled by default. capability-advertise orf BGP peer or a peer group ip-prefix { both | receive | send } Table 14 Description of the send, receive, and both parameters and the negotiation result Local parameter Peer parameter...

  • Page 501: Configuring Ipv6 Mbgp Community

    Before adding an IPv6 MBGP peer to the IPv6 MBGP peer group, you must add the corresponding IPv6 BGP unicast peer to the corresponding IPv6 BGP unicast peer group. To configure an IPv6 MBGP peer group: Step Command Remarks Enter system view. system-view Enter BGP view.

  • Page 502: Configuring An Ipv6 Mbgp Route Reflector

    Configuring an IPv6 MBGP route reflector To guarantee connectivity between IPv6 multicast IBGP peers, you must make them fully meshed. However, this becomes impractical when too many IPv6 multicast IBGP peers exist. Using route reflectors can solve the problem. The clients of a route reflector should not be fully meshed, and the route reflector reflects the routes of a client to the other clients.

  • Page 503: Resetting Ipv6 Mbgp Connections

    Task Command Remarks Display the prefix entries in the display bgp ipv6 multicast peer ipv6-address Available in ORF information of the specified received ipv6-prefix [ | { begin | exclude | include } any view. BGP peer. regular-expression ] display bgp ipv6 multicast routing-table Display IPv6 MBGP routing table Available in [ ipv6-address prefix-length ] [ | { begin | exclude |...

  • Page 504: Clearing Ipv6 Mbgp Information

    Task Command Remarks reset bgp ipv6 multicast { as-number | ipv6-address Reset the specified IPv6 MBGP [ flap-info ] | all | group Available in user view. connections. ipv6-group-name | external | internal } Clearing IPv6 MBGP information Task Command Remarks Clear dampened IPv6 MBGP routing...
  • Page 505 Device Interface IP address Device Interface IP address Source 1002::100/64 Switch C Vlan-int200 3002::1/64 Switch A Vlan-int100 1002::1/64 Vlan-int102 2001::2/64 Vlan-int101 1001::1/64 Vlan-int104 3001::1/64 Switch B Vlan-int101 1001::2/64 Switch D Vlan-int103 2002::2/64 Vlan-int102 2001::1/64 Vlan-int104 3001::2/64 Vlan-int103 2002::1/64 Configuration procedure Enable IPv6 for all the switches, and assign an IPv6 addresses and prefix length for each interface according to Figure...
  • Page 506 # Enable the imbedded RP function on Switch A. [SwitchA] pim ipv6 [SwitchA-pim6] embedded-rp [SwitchA-pim6] quit # Configure Switch B, Switch C, and Switch D in the same way. (Details not shown.) Configure BGP, specify the IPv6 MBGP peer and enable direct route redistribution: # On Switch A, configure the IPv6 MBGP peer and enable direct route redistribution.

  • Page 507: 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 Bold text represents commands and keywords that you enter literally as shown. Boldface Italic text represents arguments that you replace with actual values.

  • Page 508: 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 509: 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 510: Websites

    Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help...

  • Page 511: Index

    Index A C D E H I M N O P S T Configuring IPv6 PIM-SSM,438 Configuring MBGP route attributes,230 Accessing Hewlett Packard Enterprise Support,497 Configuring MD-VPN,261 Accessing updates,497 Configuring MLD proxying,390 Adjusting IGMP performance,101 Configuring MLD snooping port functions,312 Adjusting MLD performance,385 Configuring MLD snooping...
  • Page 512 IGMP configuration examples,110 Overview,374 IGMP configuration task list,98 Overview,349 IGMP snooping configuration examples,35 Overview,402 IGMP snooping configuration task list,18 Overview,304 IPv6 MBGP configuration example,492 Overview,53 IPv6 MBGP configuration task list,478 Overview,478 IPv6 multicast routing and forwarding configuration Overview,243 example,369 Overview,224 IPv6 multicast VLAN configuration examples,354 Overview,192...

This manual is also suitable for:

Flexfabric 5820x series

Table of Contents