HPE FlexFabric 5930 Series Ip Multicast Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. FlexFabric 5930 Series
  6. Ip multicast configuration manual

HPE FlexFabric 5930 Series Ip Multicast Configuration Manual

Hide thumbs Also See for FlexFabric 5930 Series:
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
Table of Contents

Advertisement

Quick Links

Download this manual
HPE FlexFabric 5930 Switch Series
IP Multicast

Configuration Guide

Part number: 5998-7766R
Software version: Release 242x
Document version: 6W100-20151220

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for HPE FlexFabric 5930 Series

Summary of Contents for HPE FlexFabric 5930 Series

  • Page 1: Configuration Guide

    HPE FlexFabric 5930 Switch Series IP Multicast Configuration Guide Part number: 5998-7766R Software version: Release 242x Document version: 6W100-20151220...
  • Page 2 © Copyright 2015 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Contents Multicast overview ··························································································· 1   Introduction to multicast ····································································································································· 1   Information transmission techniques ·········································································································· 1   Multicast features ······································································································································· 3   Common notations in multicast ·················································································································· 4   Multicast benefits and applications ············································································································ 4   Multicast models ················································································································································ 4  ...
  • Page 4 Configuring PIM snooping ············································································· 39   Overview ·························································································································································· 39   Configuring PIM snooping ································································································································ 40   Displaying and maintaining PIM snooping ······································································································· 40   PIM snooping configuration example ··············································································································· 41   Troubleshooting PIM snooping ························································································································ 44   PIM snooping does not work on a Layer 2 device ··················································································· 44  ...
  • Page 5 Configuring IGMP query and response parameters ················································································· 80   Enabling fast-leave processing ················································································································ 82   Configuring IGMP SSM mappings ··················································································································· 82   Configuration prerequisites ······················································································································ 82   Configuration procedure ··························································································································· 83   Enabling IGMP NSR ········································································································································ 83   Displaying and maintaining IGMP ···················································································································· 83  ...
  • Page 6 PIM configuration examples ··························································································································· 124   PIM-DM configuration example ·············································································································· 124   PIM-SM non-scoped zone configuration example ················································································· 127   PIM-SM admin-scoped zone configuration example ·············································································· 130   BIDIR-PIM configuration example ·········································································································· 135   PIM-SSM configuration example ············································································································ 139   Troubleshooting PIM ······································································································································...
  • Page 7 Configuring BGP MDT ··································································································································· 186   Configuration prerequisites ···················································································································· 186   Configuring BGP MDT peers or peer groups ························································································· 187   Configuring a BGP MDT route reflector ································································································· 187   Displaying and maintaining multicast VPN ···································································································· 188   Multicast VPN configuration examples ·········································································································· 189  ...
  • Page 8 Configuring IPv6 multicast VLANs ······························································ 249   Overview ························································································································································ 249   IPv6 multicast VLAN configuration task list ···································································································· 251   Configuring a sub-VLAN-based IPv6 multicast VLAN ··················································································· 251   Configuration prerequisites ···················································································································· 251   Configuration guidelines ························································································································· 251   Configuration procedure ························································································································· 251  ...
  • Page 9 Configuring IPv6 PIM ·················································································· 287   Overview ························································································································································ 287   IPv6 PIM-DM overview ··························································································································· 287   IPv6 PIM-SM overview ··························································································································· 289   IPv6 BIDIR-PIM overview ······················································································································· 294   IPv6 administrative scoping overview ···································································································· 297   IPv6 PIM-SSM overview ························································································································ 299  ...
  • Page 10 Document conventions and icons ······························································· 344   Conventions ··················································································································································· 344   Network topology icons ·································································································································· 345   Support and other resources ······································································ 346   Accessing Hewlett Packard Enterprise Support ···························································································· 346   Accessing updates ········································································································································· 346   Websites ················································································································································ 347  ...

  • Page 11: Multicast Overview

    Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load.
  • Page 12 Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission Figure 2, 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 13: Multicast Features

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

  • Page 14: Common Notations In Multicast

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

  • Page 15: Multicast Architecture

    ASM model In the ASM model, any multicast sources can send information to a multicast group. Receivers can join a multicast group and get multicast information addressed to that multicast group from any multicast sources. In this model, receivers do not know the positions of the multicast sources in advance.
  • Page 16 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 224.0.0.0 to 224.0.0.255 maintenance, and so on. Table 3 lists common permanent group addresses.
  • Page 17 Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 11111111. Flags—The Flags field contains four bits. Figure 5 Flags field format Table 4 Flags field description Description Reserved, set to 0. •...
  • Page 18 Value Meaning 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 • IPv4 multicast MAC addresses: As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E.

  • Page 19: Multicast Protocols

    Multicast protocols Multicast protocols include the following categories: • Layer 3 and Layer 2 multicast protocols: Layer 3 multicast refers to IP multicast working at the network layer. Layer 3 multicast protocols—IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP.
  • Page 20 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, PIM is most widely used. Based on the forwarding mechanism, PIM has dense mode (often referred to as PIM-DM) and sparse mode (often referred to as PIM-SM).

  • Page 21: Multicast Packet Forwarding Mechanism

    VLAN on the Layer 2 device. This method avoids waste of network bandwidth and extra burden on the Layer 3 device. Multicast packet forwarding mechanism In a multicast model, multicast receivers of a multicast group are usually located at different areas on the network.

  • Page 22: Multicast Application In Vpns

    • The multi-VPN-instance customer edge (MCE) device connects to the VPNs and PE devices and serves multiple VPNs. Different VPN instances for VPNs can be created on the MCE device to separately maintain their forwarding tables. • The provider edge (PE) devices connect to the public network and the VPNs and serve multiple networks.

  • Page 23: Configuring Igmp Snooping

    Configuring IGMP snooping Overview IGMP snooping runs on a Layer 2 switch as a multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from IGMP packets that are exchanged between the hosts and the router. As shown in Figure 11, when IGMP snooping is not enabled, the Layer 2 switch floods multicast...
  • Page 24 Figure 12 IGMP snooping related ports Receiver Router A Switch A FGE1/0/1 FGE1/0/2 Host A FGE1/0/3 Host B Receiver FGE1/0/1 FGE1/0/2 Source Host C Switch B Router port Member port Multicast packets Host D The following describes the ports involved in IGMP snooping: •...

  • Page 25: How Igmp Snooping Works

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

  • Page 26: Protocols And Standards

    • If no match is found, the switch discards the IGMP leave message. • If a match is found but the receiving port is not in the forwarding entry, the switch discards the IGMP leave message. • If a match is found and the receiving port is not the only outgoing interface in the forwarding entry, the switch performs the following actions: Discards the IGMP leave message.

  • Page 27: Igmp Snooping Configuration Task List

    IGMP snooping configuration task list Tasks at a glance Configuring basic IGMP snooping features: • (Required.) Enabling IGMP snooping • (Optional.) Specifying an IGMP snooping version • (Optional.) Setting the maximum number of IGMP snooping forwarding entries • (Optional.) Setting the IGMP last member query interval Configuring IGMP snooping port features: •...

  • Page 28: Specifying An Igmp Snooping Version

    • You can enable IGMP snooping for the specified VLANs in IGMP-snooping view or for a VLAN in VLAN view. For a VLAN, the configuration in VLAN view has the same priority as the configuration in IGMP-snooping view, and the most recent configuration takes effect. Enabling IGMP snooping in IGMP-snooping view Step Command...

  • Page 29: Setting The Maximum Number Of Igmp Snooping Forwarding Entries

    Step Command Remarks Specify an IGMP snooping version version-number vlan version for the specified The default setting is 2. vlan-list VLANs. Specifying an IGMP snooping version in VLAN view Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Specify an IGMP snooping igmp-snooping version The default setting is 2.

  • Page 30: Configuring Igmp Snooping Port Features

    Setting the IGMP last member query interval globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the IGMP last member The default setting is 1 last-member-query-interval interval query interval globally. second. Setting the IGMP last member query interval in a VLAN Step Command Remarks...

  • Page 31: Configuring Static Ports

    Step Command Remarks Set the aging timer for The default setting is 260 dynamic member ports host-aging-time interval seconds. globally. Setting the aging timers for dynamic ports in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the aging timer for The default setting is 260...

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

    Configuring a port as a simulated member host When a port is configured as a simulated member host, it is equivalent to an independent host in the following ways: • It sends an unsolicited IGMP report when you complete the configuration. •...

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

    Step Command Remarks Enable fast-leave igmp-snooping fast-leave [ vlan By default, fast-leave processing processing on the port. vlan-list ] is disabled for a port. Disabling a port from becoming a dynamic router port A receiver host might send IGMP general queries or PIM hello messages for testing purposes. On the Layer 2 device, the port that receives either of the messages becomes a dynamic router port.

  • Page 34: Configuring Parameters For Igmp General Queries And Responses

    Configuration guidelines When you enable the IGMP snooping querier, follow these guidelines: • Do not enable the IGMP snooping querier on a multicast network that runs IGMP. An IGMP snooping querier does not take part in IGMP querier elections. However, it might affect IGMP querier elections if it sends IGMP general queries with a low source IP address.

  • Page 35: Configuring Parameters For Igmp Messages

    Configuring parameters for IGMP general queries and responses in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the IGMP general query The default setting is 125 igmp-snooping query-interval interval interval in the VLAN. seconds.

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

    Step Command Remarks By default, if the IGMP snooping querier has received IGMP queries, the source IP address of IGMP group-specific Configure the source IP igmp-snooping queries is the source IP address of IGMP address for IGMP special-query source-ip queries. Otherwise, it is the IP address of group-specific queries.

  • Page 37: Configuring A Multicast Group Policy

    • Determine the maximum number of multicast groups that a port can join. Configuring a multicast group policy This feature enables the switch to filter IGMP reports by using an ACL that specifies multicast groups and the optional sources. It is used to control the multicast groups that receiver hosts can join. Configuration guidelines When you configure a multicast group policy, follow these guidelines: •...

  • Page 38: Enabling Dropping Unknown Multicast Data

    Configuring multicast source port filtering on a port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view. interface-number Enable multicast source port By default, multicast source port igmp-snooping source-deny filtering. filtering is disabled. Enabling dropping unknown multicast data This feature enables the switch to drop all unknown multicast data.

  • Page 39: Enabling The Multicast Group Replacement Feature

    To set the maximum number of multicast groups on a port: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Set the maximum number of The default setting is igmp-snooping group-limit limit multicast groups on a port.

  • Page 40: Igmp Snooping Configuration Examples

    Task Command Display IGMP snooping status. display igmp-snooping [ global | vlan vlan-id ] display igmp-snooping group [ group-address | Display dynamic IGMP snooping source-address ] * [ vlan vlan-id ] [ verbose ] [ slot forwarding entries. slot-number ] display igmp-snooping static-group [ group-address | Display static IGMP snooping forwarding source-address ] * [ vlan vlan-id ] [ verbose ] [ slot...
  • Page 41 Figure 13 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 13. (Details not shown.) Configure Router A: # Enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable IGMP on FortyGigE 1/0/1. [RouterA] interface fortygige 1/0/1 [RouterA-FortyGigE1/0/1] igmp enable [RouterA-FortyGigE1/0/1] quit...

  • Page 42: Static Port Configuration Example

    # Configure a multicast group policy so that hosts in VLAN 100 can join only the multicast group 224.1.1.1. [SwitchA] acl number 2001 [SwitchA-acl-basic-2001] rule permit source 224.1.1.1 0 [SwitchA-acl-basic-2001] quit [SwitchA] igmp-snooping [SwitchA-igmp-snooping] group-policy 2001 vlan 100 [SwitchA-igmp-snooping] quit Verifying the configuration # Send IGMP reports from Host A and Host B to join the multicast groups 224.1.1.1 and 224.2.2.2.
  • Page 43 For more information about the STP, see Layer 2—LAN Switching Configuration Guide. Figure 14 Network diagram Switch B Source Switch A FGE1/0/2 FGE1/0/1 1.1.1.2/24 10.1.1.1/24 FGE1/0/1 Router A 1.1.1.1/24 IGMP querier Switch C Host C Host A Receiver Receiver Host B VLAN 100 Configuration procedure Assign an IP address and subnet mask to each interface as shown in...
  • Page 44 [SwitchA-vlan100] quit # Configure FortyGigE 1/0/3 as a static router port. [SwitchA] interface fortygige 1/0/3 [SwitchA-FortyGigE1/0/3] igmp-snooping static-router-port vlan 100 [SwitchA-FortyGigE1/0/3] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, and assign FortyGigE 1/0/1 and FortyGigE 1/0/2 to the VLAN. [SwitchB] vlan 100 [SwitchB-vlan100] port fortygige 1/0/1 fortygige 1/0/2 # Enable IGMP snooping for VLAN 100.

  • Page 45: Igmp Snooping Querier Configuration Example

    Total 1 entries. VLAN 100: Total 1 entries. (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (2 in total): FGE1/0/3 FGE1/0/5 The output shows that FortyGigE 1/0/3 and FortyGigE 1/0/5 on Switch C have become static member ports of the multicast group 224.1.1.1. IGMP snooping querier configuration example Network requirements As shown in...
  • Page 46 # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign FortyGigE 1/0/1 through FortyGigE 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port fortygige 1/0/1 to fortygige 1/0/3 # Enable IGMP snooping for VLAN 100. [SwitchA-vlan100] igmp-snooping enable # Enable dropping unknown multicast packets for VLAN 100.

  • Page 47: Troubleshooting Igmp Snooping

    <SwitchD> system-view [SwitchD] igmp-snooping [SwitchD-igmp-snooping] quit # Create VLAN 100, and assign FortyGigE 1/0/1 and FortyGigE 1/0/2 to the VLAN. [SwitchD] vlan 100 [SwitchD-vlan100] port fortygige 1/0/1 to fortygige 1/0/2 # Enable IGMP snooping for VLAN 100. [SwitchD-vlan100] igmp-snooping enable # Enable dropping unknown multicast packets for VLAN 100.

  • Page 48: Multicast Group Policy Does Not Work

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

  • Page 49: Configuring Pim Snooping

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

  • Page 50: Configuring Pim Snooping

    Each PIM 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. • When the Layer 2 switch runs both IGMP snooping and PIM snooping, it performs the following actions: a.

  • Page 51: Pim Snooping Configuration Example

    Task Command display pim-snooping neighbor [ vlan vlan-id ] Display PIM snooping neighbor information. [ slot slot-number ] [ verbose ] display pim-snooping routing-table [ vlan Display PIM snooping routing entries. vlan-id ] [ slot slot-number ] [ verbose ] display pim-snooping router-port [ vlan vlan-id ] Display PIM snooping router port information.
  • Page 52 Configure Router A: # Enable IP multicast routing. <RouterA> system-view [RouterA] multicast routing [RouterA-mrib] quit # Enable PIM-SM on each interface. [RouterA] interface fortygige 1/0/1 [RouterA-FortyGigE1/0/1] pim sm [RouterA-FortyGigE1/0/1] quit [RouterA] interface fortygige 1/0/2 [RouterA-FortyGigE1/0/2] pim sm [RouterA-FortyGigE1/0/2] quit # Configure FortyGigE 1/0/2 as a C-BSR and C-RP. [RouterA] pim [RouterA-pim] c-bsr 10.1.1.1 [RouterA-pim] c-rp 10.1.1.1...
  • Page 53 # Enable IGMP on FortyGigE 1/0/1. [RouterD] interface fortygige 1/0/1 [RouterD-FortyGigE1/0/1] igmp enable [RouterD-FortyGigE1/0/1] quit # Enable PIM-SM on FortyGigE 1/0/2. [RouterD] interface fortygige 1/0/2 [RouterD-FortyGigE1/0/2] pim sm [RouterD-FortyGigE1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, assign FortyGigE 1/0/1 through FortyGigE 1/0/4 to this VLAN, and enable...

  • Page 54: Troubleshooting Pim Snooping

    VLAN 100: Total 2 entries. (*, 224.1.1.1) Upstream neighbor: 10.1.1.1 Upstream Slots (0 in total): Upstream Ports (1 in total): FGE1/0/1 Downstream Slots (0 in total): Downstream Ports (1 in total): FGE1/0/3 Expires: 00:03:01, FSM: J (*, 225.1.1.1) Upstream neighbor: 10.1.1.2 Upstream Slots (0 in total): Upstream Ports (1 in total): FGE1/0/2...

  • Page 55: Configuring Multicast Vlans

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

  • Page 57: Multicast Vlan Configuration Task List

    Multicast VLAN can be used on networks where multicast sources are connected to downstream devices of a Layer 2 device. Upon receiving multicast traffic from a downstream multicast source, the Layer 2 device changes the user VLAN of the traffic to the associated multicast VLAN. Then, it floods the traffic to the upstream Layer 3 device through the multicast VLAN.

  • Page 58: Configuring A Port-Based Multicast Vlan

    Step Command Remarks Configure a VLAN as a By default, a VLAN is not a multicast VLAN and enter its multicast-vlan vlan-id multicast VLAN. view. Assign the specified VLANs By default, a multicast VLAN does to the multicast VLAN as subvlan vlan-list not have any sub-VLANs.

  • Page 59: Assigning User Ports To A Multicast Vlan

    Assigning user ports to a multicast VLAN You can either assign the user ports to the multicast VLAN in multicast VLAN view, or assign the user ports to the multicast VLAN in interface view. When you perform this task, follow these guidelines: •...

  • Page 60: Displaying And Maintaining Multicast Vlans

    Displaying and maintaining multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about multicast display multicast-vlan [ vlan-id ] VLANs. Display information about multicast display multicast-vlan group [ source-address | group-address | groups in multicast VLANs.
  • Page 61 Figure 21 Network diagram Source FGE1/0/2 IGMP querier Vlan-int20 Switch A 1.1.1.2/24 FGE1/0/1 1.1.1.1/24 Vlan-int10 10.110.1.1/24 FGE1/0/1 Switch B FGE1/0/2 FGE1/0/4 FGE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure Switch A: # Enable IP multicast routing.
  • Page 62 Configure Switch B: # Enable IGMP snooping. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 2, assign FortyGigE 1/0/2 to the VLAN, and enable IGMP snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port fortygige 1/0/2 [SwitchB-vlan2] igmp-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign FortyGigE 1/0/3 to the VLAN, and enable IGMP snooping for the VLAN.

  • Page 63: Port-Based Multicast Vlan Configuration Example

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

  • Page 67: Configuring Multicast Routing And Forwarding

    Configuring multicast routing and forwarding Overview The following tables are involved in multicast routing and forwarding: • Multicast routing table of each multicast routing protocol, such as the PIM routing table. • General multicast routing table that summarizes multicast routing information generated by different multicast routing protocols.
  • Page 68 If the router does not use the longest prefix match principle, the route with a higher route preference becomes the RPF route. If the routes have the same preference, the unicast route becomes the RPF route. The RPF route determines the RPF interface and the RPF neighbor. If the RPF route is a unicast route, the outgoing interface of the route is the RPF interface, and the next hop is the RPF neighbor.

  • Page 69: Static Multicast Routes

    Figure 23 RPF check process IP Routing Table on Switch C Receiver Switch B Destination/Mask Interface 192.168.0.0/24 Vlan-int20 Vlan-int10 Source Switch A 192.168.0.1/24 Receiver Vlan-int10 Vlan-int20 Multicast packets Switch C As shown in Figure 23, assume that unicast routes are available in the network and no static multicast routes have been configured on Switch C.
  • Page 70 Figure 24 Changing an RPF route As shown in Figure 24, when no static multicast route is configured, Switch C's RPF neighbor on the path back to the source is Switch A. The multicast data from the source travels through Switch A to Switch C.

  • Page 71: Multicast Forwarding Across Unicast Subnets

    NOTE: A static multicast route is effective only on the multicast router on which it is configured, and will not be advertised throughout the network or redistributed to other routers. Multicast forwarding across unicast subnets Routers forward the multicast data from a multicast source hop by hop along the forwarding tree, but some routers might not support multicast protocols in a network.

  • Page 72: Enabling Ip Multicast Routing

    Enabling IP multicast routing Enable IP multicast routing before you configure any Layer 3 multicast functionality on the public network or VPN instance. To enable IP multicast routing: Step Command Remarks Enter system view. system-view Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast routing is and enter MRIB view.

  • Page 73: Specifying The Longest Prefix Match Principle

    Specifying the longest prefix match principle You can enable the multicast router to use the longest prefix match principle for RPF route selection. For more information about RPF route selection, see "RPF check process." To specify the longest prefix match principle: Step Command Remarks...

  • Page 74: Configuring Static Multicast Mac Address Entries

    Configuring static multicast MAC address entries In Layer 2 multicast, multicast MAC address entries can be dynamically created or added through Layer 2 multicast protocols (such as IGMP snooping). You can also manually configure static multicast MAC address entries by binding multicast MAC addresses and ports to control the destination ports of the multicast data.

  • Page 75: Displaying And Maintaining Multicast Routing And Forwarding

    Step Command Remarks Configure multicast By default, multicast data multicast forwarding supervlan forwarding among cannot be forwarded among community sub-VLANs of a super VLAN. sub-VLANs of a super VLAN. reset multicast [ vpn-instance vpn-instance-name ] Clear all multicast forwarding forwarding-table { { source-address entries with the super VLAN [ mask { mask-length | mask } ] | interface as the incoming...

  • Page 76: Configuration Examples

    Task Command about the multicast source. source-address [ group-address ] Clear statistics for multicast reset multicast [ vpn-instance vpn-instance-name ] forwarding event forwarding events. reset multicast [ vpn-instance vpn-instance-name ] forwarding-table Delete multicast forwarding { { source-address [ mask { mask-length | mask } ] | group-address [ mask entries.
  • Page 77 Figure 27 Network diagram Switch C Vlan-int103 Vlan-int101 40.1.1.1/24 20.1.1.2/24 PIM-DM Vlan-int103 Vlan-int101 40.1.1.2/24 20.1.1.1/24 Switch A Switch B Vlan-int102 Vlan-int102 30.1.1.2/24 30.1.1.1/24 Vlan-int200 Vlan-int100 50.1.1.1/24 10.1.1.1/24 Source Receiver 50.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 27.

  • Page 78: Creating An Rpf Route

    [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 79 Figure 28 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 28. (Details not shown.) Configure OSPF on Switch B and Switch C. (Details not shown.) Enable IP multicast routing, and enable IGMP and PIM-DM: # On Switch C, enable IP multicast routing.

  • Page 80: Multicast Forwarding Over A Gre Tunnel

    [SwitchC] display multicast rpf-info 50.1.1.100 No output is displayed, because no RPF routes to Source 2 exist on Switch B or Switch C. Configure a static multicast route: # Configure a static multicast route on Switch B, specifying Switch A as its RPF neighbor on the route to Source 2.
  • Page 81 Figure 29 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 29. (Details not shown.) Configure OSPF on all the switches. (Details not shown.) Configure a GRE tunnel: # Create service loopback group 1 on Switch A and specify the unicast tunnel service for the group <SwitchA>...
  • Page 82 [SwitchC-Tunnel0] ip address 50.1.1.2 24 [SwitchC-Tunnel0] source 30.1.1.2 [SwitchC-Tunnel0] destination 20.1.1.1 [SwitchC-Tunnel0] quit Enable IP multicast routing, PIM-DM, and IGMP: # On Switch A, enable multicast routing, and enable PIM-DM on each interface. [SwitchA] multicast routing [SwitchA-mrib] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101...

  • Page 83: Troubleshooting Multicast Routing And Forwarding

    Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.1.1.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Tunnel0 Upstream neighbor: 50.1.1.1 RPF prime neighbor: 50.1.1.1 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: pim-dm, UpTime: 00:04:25, Expires: - The output shows that Switch A is the RPF neighbor of Switch C and the multicast data from Switch...

  • Page 84: Configuring Igmp

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

  • Page 85: Igmpv2 Enhancements

    As shown in Figure 30, Host B and Host C are interested in the multicast data addressed to the multicast group G1. Host A is interested in the multicast data addressed to G2. The following process describes how the hosts join the multicast groups and how the IGMP querier (Router B in Figure maintains the multicast group memberships: The hosts send unsolicited IGMP reports to the multicast groups they want to join without...

  • Page 86: Igmpv3 Enhancements

    "Leave group" mechanism In IGMPv1, when a host leaves a multicast group, it does not send any notification to the multicast routers. The multicast routers determine whether a group has members by using the maximum response time. This adds to the leave latency. In IGMPv2, when a host is leaving a multicast group, the following process occurs: The host sends a leave message (with the destination of 224.0.0.2) to all routers on the local subnet.

  • Page 87: Igmp Support For Vpns

    In IGMPv3, Host B can explicitly express that it needs to receive the multicast data addressed to G from Source 1 but not from Source 2. As a result, Host B receives only multicast data from Source 1. Enhancements in query and report capabilities IGMPv3 introduces IGMP group-and-source queries and IGMP reports carrying group records.

  • Page 88: Igmp Configuration Task List

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

  • Page 89: Configuring A Static Group Member

    To specify an IGMP version: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Specify an IGMP version. The default setting is 2. igmp version version-number Configuring a static group member You can configure an interface as a static group member of a multicast group. The interface can always receive multicast data for the group.

  • Page 90: Adjusting Igmp Performance

    Step Command Remarks policy. Hosts attached to the interface can join any multicast groups. Adjusting IGMP performance Before adjusting IGMP performance, complete the following tasks: • Configure any unicast routing protocol so that all devices can interoperate at the network layer. •...
  • Page 91 For IGMP general queries, the maximum response time is set by the max-response-time command. For IGMP group-specific queries and IGMP group-and-source-specific queries, the maximum response time equals the IGMP last member query interval. • The following configurations take effect only on the devices that run IGMPv2 and IGMPv3: Maximum response time for IGMP general queries.

  • Page 92: Enabling Fast-Leave Processing

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

  • Page 93: Configuration Procedure

    • Configure any unicast routing protocol so that all devices in the domain can interoperate at the network layer. • Configure basic IGMP features. Configuration procedure To configure IGMP SSM mappings: Step Command Remarks Enter system view. system-view igmp [ vpn-instance Enter IGMP view.

  • Page 94: Igmp Configuration Examples

    Task Command [ source-address [ mask { mask | mask-length } ] ] } } IGMP configuration examples Basic IGMP features configuration example Network requirements As shown in Figure • OSPF and PIM-DM run on the network. • VOD streams are sent to receiver hosts in multicast. Receiver hosts of different organizations form stub networks N1 and N2.
  • Page 95 [SwitchA] multicast routing [SwitchA-mrib] quit # Enable IGMP on the receiver-side interface VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-DM on VLAN-interface 101. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim dm [SwitchA-Vlan-interface101] quit # On Switch B, enable IP multicast routing. <SwitchB>...

  • Page 96: Igmp Ssm Mapping Configuration Example

    IGMP version: 2 Query interval for IGMP: 125s Other querier present time for IGMP: 255s Maximum query response time for IGMP: 10s Querier for IGMP: 10.110.2.1 (This router) IGMP groups reported in total: 1 IGMP SSM mapping configuration example Network requirements As shown in Figure •...
  • Page 97 Device Interface IP address Device Interface IP address Switch B 192.168.2.1/24 Switch D 192.168.4.1/24 Vlan-int102 Vlan-int104 Configuration procedure Assign an IP address and subnet mask to each interface according to Table 6. (Details not shown.) Configure OSPF on the switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, PIM-SM, and IGMP: # On Switch D, enable IP multicast routing.
  • Page 98 [SwitchD-acl-basic-2000] quit [SwitchD] pim [SwitchD-pim] ssm-policy 2000 [SwitchD-pim] quit # Configure the SSM group range on Switch A, Switch B, and Switch C in the same way Switch D is configured. (Details not shown.) Configure IGMP SSM mappings on Switch D. [SwitchD] igmp [SwitchD-igmp] ssm-mapping 133.133.1.1 2000 [SwitchD-igmp] ssm-mapping 133.133.3.1 2000...

  • Page 99: Troubleshooting Igmp

    RPF prime neighbor: 192.168.3.1 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface400 Protocol: igmp, UpTime: 00:13:25, Expires: - Troubleshooting IGMP No membership information on the receiver-side router Symptom When a host sends a report for joining the multicast group G, no membership information of the multicast group G exists on the router closest to that host.
  • Page 100 • Although IGMP routers are partially compatible with hosts that separately run different versions of IGMP, all routers on the same subnet must run the same version of IGMP. Inconsistent IGMP versions running on routers on the same subnet leads to inconsistency of IGMP memberships. Solution To resolve the problem: Use the display current-configuration command to verify the IGMP information on the...

  • Page 101: Configuring Pim

    Configuring PIM Overview Protocol Independent Multicast (PIM) provides IP multicast forwarding by leveraging unicast static routes or unicast routing tables generated by any unicast routing protocol, such as RIP, OSPF, IS-IS, or BGP. PIM uses the underlying unicast routing to generate a multicast routing table without relying on any particular unicast routing protocol.
  • Page 102 The nodes without downstream receivers are pruned. A router that has no downstream receivers multicasts a prune message to all PIM routers on the subnet. When an upstream node receives the prune message, it removes the receiving interface from the (S, G) entry. In this way, the upstream stream node stops forwarding subsequent packets addressed to that multicast group down to this node.

  • Page 103: Pim-Sm Overview

    Figure 35 Assert mechanism As shown in Figure 35, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet. As a result, the downstream node Router C receives two identical multicast packets.
  • Page 104 PIM-DM does not require a DR. However, if IGMPv1 runs on any shared-media LAN in a PIM-DM domain, a DR must be elected to act as the IGMPv1 querier for the LAN. For more information about IGMP, see "Configuring IGMP." IMPORTANT: IGMP must be enabled on the device that acts as the receiver-side DR.
  • Page 105 As shown in Figure 37, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between multicast groups and RPs.
  • Page 106 As shown in Figure 38, the process of building an RPT is as follows: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR. After getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP for the multicast group.

  • Page 107: Bidir-Pim Overview

    Switchover to SPT CAUTION: If the switch is an RP, disabling switchover to SPT might cause multicast traffic forwarding failures on the source-side DR. When disabling switchover to SPT, be sure you fully understand its impact on your network. In a PIM-SM domain, only one RP and one RPT provide services for a specific multicast group. Before the switchover to SPT occurs, the source-side DR encapsulates all multicast data addressed to the multicast group in register messages and sends them to the RP.
  • Page 108 forwards the data to the receivers. Each router along the bidirectional RPT needs to maintain only one (*, G) entry, saving system resources. BIDIR-PIM is suitable for a network with dense multicast sources and receivers. Neighbor discovery BIDIR-PIM uses the same neighbor discovery mechanism as PIM-SM does. For more information, "Neighbor discovery."...
  • Page 109 Bidirectional RPT building A bidirectional RPT comprises a receiver-side RPT and a source-side RPT. The receiver-side RPT is rooted at the RP and takes the routers that directly connect to the receivers as leaves. The source-side RPT is also rooted at the RP but takes the routers that directly connect to the sources as leaves.

  • Page 110: Administrative Scoping Overview

    Figure 42 RPT building at the multicast source side As shown in Figure 42, the process for building a source-side RPT is relatively simple: When a multicast source sends multicast packets to the multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
  • Page 111 specific group range cannot cross the boundary of the admin-scoped zone for the group range. Multicast group ranges that are associated with different admin-scoped zones can have intersections. However, the multicast groups in an admin-scoped zone are valid only within the local zone, and theses multicast groups are regarded as private group addresses.

  • Page 112: Pim-Ssm Overview

    Figure 44 Relationship in view of multicast group address ranges Admin-scope 1 Admin-scope 3 G1 address G3 address Admin-scope 2 Global-scope G2 address − − G2 address As shown in Figure 44, 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 113: Relationship Among Pim Protocols

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

  • Page 114: Pim Support For Vpns

    Figure 46 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? PIM-SM runs for G. G has a BIDIR-PIM RP? PIM-SSM runs for G. BIDIR-PIM runs for G.

  • Page 115: Pim-Dm Configuration Task List

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

  • Page 116: Configuring State Refresh Parameters

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

  • Page 117: Configuring Pim-Sm

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

  • Page 118: Configuring An Rp

    Step Command Remarks Return to system view. quit interface interface-type Enter interface view. interface-number Enable PIM-SM. By default, PIM-SM is disabled. pim sm Configuring an RP An RP can provide services for multiple or all multicast groups. However, only one RP can forward multicast traffic for a multicast group at a time.

  • Page 119: Configuring A Bsr

    Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] c-rp ip-address [ advertisement-interval adv-interval | Configure a C-RP. By default, no C-RPs exist. group-policy acl-number | holdtime hold-time | priority priority ] * (Optional.) Configure a By default, no C-RP policy crp-policy acl-number C-RP policy.
  • Page 120 • When an attacker controls a router on the network, the attacker can configure the router as a C-BSR to win the BSR election. Through this router, the attacker controls the advertising of RP information. When you configure a C-BSR, follow these guidelines: •...

  • Page 121: Configuring Multicast Source Registration

    To disable BSM semantic fragmentation: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Disable BSM semantic By default, BSM semantic undo bsm-fragment enable fragmentation. fragmentation is enabled. NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. For BSMs originated due to learning of a new PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs.

  • Page 122: Configuring Bidir-Pim

    Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] By default, the device spt-switch-threshold { immediacy immediately triggers the Configure the switchover to | infinity } [ group-policy switchover to SPT after SPT. acl-number ] receiving the first multicast packet.

  • Page 123: Configuring An Rp

    Step Command Remarks Enter system view. system-view Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast routing is and enter MRIB view. vpn-instance-name ] disabled. Return to system view. quit interface interface-type Enter interface view. interface-number Enable PIM-SM. By default, PIM-SM is disabled.
  • Page 124 Configuring a C-RP IMPORTANT: When you configure a C-RP, reserve a large bandwidth between the C-RP and other devices in the BIDIR-PIM domain. In a BIDIR-PIM domain, if you want a router to become the RP, you can configure the router as a C-RP.

  • Page 125: Configuring A Bsr

    To set the maximum number of BIDIR-PIM RPs: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] Set the maximum number of By default, the maximum number bidir-rp-limit limit BIDIR-PIM RPs. of BIDIR-PIM RPs is 6. Configuring a BSR You must configure a BSR if C-RPs are configured to dynamically select the RP.
  • Page 126 Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view. vpn-instance-name ] c-bsr ip-address [ scope group-address { mask-length | By default, no C-BSR is Configure a C-BSR. mask } ] [ hash-length configured. hash-length | priority priority ] * (Optional.) Configure a BSR By default, no BSR policy exists.

  • Page 127: Configuring Pim-Ssm

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

  • Page 128: Configuring Common Pim Features

    • Configure the same SSM group range on all routers in the PIM-SSM domain. Otherwise, multicast information cannot be delivered through the SSM model. • When a member of a multicast group in the SSM group range sends an IGMPv1 or IGMPv2 report message, the device does not trigger a (*, G) join.

  • Page 129: Configuring A Pim Hello Policy

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

  • Page 131: Configuring Common Pim Timers

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

  • Page 132: Setting The Maximum Size Of Each Join Or Prune Message

    Configuring common PIM timers on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Set the hello interval. The default setting is 30 seconds. pim timer hello interval Set the triggered hello delay. The default setting is 5 seconds. pim triggered-hello-delay delay The default setting is 60 seconds.

  • Page 133: Enabling Pim Passive Mode

    Enabling PIM passive mode To guard against PIM hello spoofing, you can enable PIM passive mode on an interface which is directly connected to user hosts. The PIM passive interface cannot receive or forward PIM protocol messages (excluding register, register-stop and C-RP-Adv messages), and it acts as the DR on the subnet.

  • Page 134: Pim Configuration Examples

    Task Command display pim [ vpn-instance vpn-instance-name ] c-rp Display C-RP information in the PIM-SM domain. [ local ] display pim [ vpn-instance vpn-instance-name ] Display DF information in the BIDIR-PIM domain. df-info [ rp-address ] display pim [ vpn-instance vpn-instance-name ] Display PIM information for interfaces.
  • Page 135 Figure 47 Network diagram Receiver Host A Switch A Vlan-int100 Host B Receiver Vlan-int300 Vlan-int101 Vlan-int200 Vlan-int101 Source Host C Switch D Switch B 10.110.5.100/24 Vlan-int200 PIM-DM Switch C Host D Table 7 Interface and IP address assignment Device Interface IP address Device Interface...
  • Page 136 [SwitchA-Vlan-interface103] quit # Enable IP multicast routing, IGMP, and PIM-DM on Switch B and Switch C in the same way Switch A is configured. (Details not shown.) # On Switch D, enable IP multicast routing, and enable PIM-DM on each interface. <SwitchD>...

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

    RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.110.5.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT UpTime: 00:06:14 Upstream interface: Vlan-interface103 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-dm, UpTime: 00:04:25, Expires: -...
  • Page 138 • Specify VLAN-interface 102 on Switch E as a C-BSR and a C-RP. The C-RP is designated to the multicast group range 225.1.1.0/24. Specify VLAN-interface 101 of Switch D as the static RP on all the switches to back up the dynamic RP. •...
  • Page 139 [SwitchA-mrib] quit # Enable IGMP on the receiver-side interface VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim sm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing, IGMP, and PIM-SM on Switch B and Switch C in the same way...

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

    Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18 Candidate BSR address: 192.168.9.2 Priority: 64...
  • Page 141 Figure 49 Network diagram Table 9 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int100 192.168.1.1/24 Switch D Vlan-int105 10.110.5.2/24 Switch A Vlan-int101 10.110.1.1/24 Switch D Vlan-int108 10.110.7.1/24 Switch B Vlan-int200 192.168.2.1/24 Switch D Vlan-int107 10.110.8.1/24 Switch B...
  • Page 142 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 49. (Details not shown.) Configure OSPF on all switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, and enable IGMP and PIM-SM: # On Switch A, enable IP multicast routing.
  • Page 143 # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 as the boundaries of admin-scoped zone 2. <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 as the boundary of admin-scoped zone 2.
  • Page 144 Hash mask length: 30 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 Uptime: 00:04:54 Candidate BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 # Display BSR information on Switch D. [SwitchD] display pim bsr-info Scope: non-scoped State: Accept Preferred...

  • Page 145: Bidir-Pim Configuration Example

    Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 00:03:39 00:01:51 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.1.2 (local) 00:07:44 00:01:51 # Display RP information on Switch D. [SwitchD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address...
  • Page 146 Figure 50 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 Table 10 Interface and IP address assignment Device Interface IP address...
  • Page 147 [SwitchA] pim [SwitchA-pim] bidir-pim enable [SwitchA-pim] quit # On Switch B, enable IP multicast routing. <SwitchB> system-view [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on the receiver-side interface VLAN-interface 200. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit # Enable PIM-SM on the other interfaces.
  • Page 148 # Enable PIM-SM on the other interfaces. [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] pim sm [SwitchD-Vlan-interface400] quit [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim sm [SwitchD-Vlan-interface103] quit # Enable BIDIR-PIM. [SwitchD] pim [SwitchD-pim] bidir-pim enable [SwitchD-pim] quit On Switch C, configure VLAN interface 102 as the C-BSR, and Loopback 0 as the C-RP for the entire BIDIR-PIM domain.

  • Page 149: Pim-Ssm Configuration Example

    [SwitchA] display multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 1.1.1.1 Flags: 0x0 Uptime: 00:08:32 RPF interface: Vlan-interface101 List of 1 DF interfaces: 1: Vlan-interface100 # Display information about the DF for multicast forwarding on Switch B. [SwitchB] display multicast forwarding df-info Total 1 RP, 1 matched 00001.
  • Page 150 • The 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. • Host A and Host C are multicast receivers in two stub networks. •...
  • Page 151 <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Enable IGMPv3 on the receiver-side interface VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] igmp version 3 [SwitchA-Vlan-interface100] quit # Enable PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102...

  • Page 152: Troubleshooting Pim

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

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

    the existing unicast route and is independent of PIM. The RPF interface must be enabled with PIM, and the RPF neighbor must be a PIM neighbor. If PIM is not enabled on the RPF interface or the RPF neighbor, the multicast distribution tree cannot be built correctly. This causes incorrect multicast forwarding.

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

    If the problem persists, contact Hewlett Packard Enterprise Support. An RP cannot join an SPT in PIM-SM Symptom An RPT cannot be correctly built, or an RP cannot join the SPT toward the multicast source. Analysis Possible reasons for the problem include the following: •...
  • Page 155 Use display pim rp-info to verify that the RP information is correct on each router. Use display pim neighbor to verify that PIM neighboring relationship has been correctly established among the routers. If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 156: Configuring Msdp

    Configuring MSDP 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 in each domain is isolated.
  • Page 157 • MSDP peers created on RPs: Source-side MSDP peer—MSDP peer closest to the multicast source, such as RP 1. The source-side RP creates and sends SA messages to its remote MSDP peer to notify the MSDP peer of the locally registered multicast source information. A source-side MSDP peer must be created on the source-side RP.
  • Page 158 The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: The multicast source in PIM-SM 1 sends the first multicast packet to multicast group G. When DR 1 receives this multicast packet, it encapsulates the multicast data within a register message and sends the register message to RP 1.

  • Page 159: Msdp Support For Vpns

    As shown in Figure 54, within a PIM-SM domain, a multicast source sends multicast data to multicast group G, and the receiver joins the multicast group. To implement Anycast RP: Configure the same IP address (known as Anycast RP address, typically a private address) to an interface on Router A and Router B.

  • Page 160: Protocols And Standards

    Protocols and standards • RFC 3618, Multicast Source Discovery Protocol (MSDP) • RFC 3446, Anycast Rendezvous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) MSDP configuration task list Tasks at a glance Configuring basic MSDP functions: •...

  • Page 161: Creating An Msdp Peering Connection

    Creating an MSDP peering connection An MSDP peering relationship is identified by an address pair (the addresses of the local MSDP peer and the remote MSDP peer). To create an MSDP peering connection, you must perform the creation operation on both devices that are a pair of MSDP peers. If an MSDP peer and a BGP peer share the same interface, configure the same IP address for the MSDP peer and the BGP peer as a best practice.

  • Page 162: Configuring An Msdp Mesh Group

    Step Command Remarks Enter system view. system-view msdp [ vpn-instance Enter MSDP view. vpn-instance-name ] Configure the description for By default, an MSDP peer is not peer peer-address description an MSDP peer configured with a description. text Configuring an MSDP mesh group An AS might contain multiple MSDP peers.

  • Page 163: Configuring Sa Message-Related Parameters

    IMPORTANT: The MSDP peers involved in MD5 authentication must be configured with the same authentication method and password. Otherwise, the authentication fails and the TCP connection cannot be established. To control MSDP peering connections: Step Command Remarks Enter system view. system-view msdp [ vpn-instance Enter MSDP view.

  • Page 164: Configuring Sa Request Messages

    actual RP address. A logical RP address is the address of a logical interface on the router where the RP resides. To configure the SA message contents: Step Command Remarks Enter system view. system-view msdp [ vpn-instance Enter MSDP view. vpn-instance-name ] Enable multicast data By default, an SA message...

  • Page 165: Configuring The Sa Cache Mechanism

    • SA incoming or outgoing policy—Limits the receipt or forwarding of SA messages. This policy enables the router to receive or forward SA messages based on the used ACL that specifies the multicast sources and groups. By default, multicast data packets are encapsulated in SA messages and forwarded to MSDP peers only if the TTL values in the packets are larger than zero.

  • Page 166: Displaying And Maintaining Msdp

    Step Command Remarks Configure the maximum number of (S, G) entries The default setting is peer peer-address learned from the specified 4294967295. sa-cache-maximum sa-limit MSDP peer that the router can cache. Displaying and maintaining MSDP Execute display commands in any view and reset commands in user view. Task Command Display brief information about...
  • Page 167 Figure 55 Network diagram Table 12 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int103 10.110.1.2/24 Switch D Vlan-int104 10.110.4.2/24 Switch A Vlan-int100 10.110.2.1/24 Switch D Vlan-int300 10.110.5.1/24 Switch A Vlan-int200 10.110.3.1/24 Switch E Vlan-int105 10.110.6.1/24 Switch B...
  • Page 168 [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim sm [SwitchA-Vlan-interface103] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit # Enable IGMP on the receiver-side interface VLAN-interface 200. [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] igmp enable [SwitchA-Vlan-interface200] quit # Enable IP multicast routing and PIM-SM on Switch B, Switch C, Switch D, Switch E, and Switch F in the same way Switch A is configured.
  • Page 169 [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. [SwitchC] msdp [SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 [SwitchC-msdp] peer 192.168.3.2 connect-interface vlan-interface 102 [SwitchC-msdp] quit # Configure MSDP peers on Switch E.
  • Page 170 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 * > 192.168.1.1/32 0.0.0.0 * > 192.168.1.2/32 0.0.0.0 When Source 1 in PIM-SM 1 and Source 2 in PIM-SM 2 send multicast information, receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data.

  • Page 171: Anycast Rp Configuration

    Information about (Source, Group)-based SA filtering policy: Import policy: None Export policy: None Information about SA-Requests: Policy to accept SA-Requests: None Sending SA-Requests status: Disable Minimum TTL to forward SA with encapsulated data: 0 SAs learned from this peer: 0, SA cache maximum for the peer: 4294967295 Input queue size: 0, Output queue size: 0 Counters for MSDP messages: RPF check failure: 0...
  • Page 172 Figure 56 Network diagram Table 13 Interface and IP address assignment Device Interface IP address Device Interface IP address Source 1 — 10.110.5.100/24 Switch C Vlan-int101 192.168.1.2/24 Source 2 — 10.110.6.100/24 Switch C Vlan-int102 192.168.2.2/24 Switch A Vlan-int300 10.110.5.1/24 Switch D Vlan-int200 10.110.3.1/24 Switch A...
  • Page 173 [SwitchB-Vlan-interface100] quit # Enable PIM-SM on the other interfaces. [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] pim sm [SwitchB-Vlan-interface103] quit [SwitchB] interface Vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface loopback 0 [SwitchB-LoopBack0] pim sm [SwitchB-LoopBack0] quit [SwitchB] interface loopback 10 [SwitchB-LoopBack10] pim sm [SwitchB-LoopBack10] quit [SwitchB] interface loopback 20...
  • Page 174 # Display brief information about MSDP peers on Switch D. [SwitchD] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 1.1.1.1 Established 00:10:57 Verify that Switch B acts as the RP for Source 1 and Host A. # Send an IGMP report from Host A to join the multicast group 225.1.1.1.

  • Page 175: Sa Message Filtering Configuration

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

  • Page 178: Troubleshooting Msdp

    [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 [SwitchC-msdp] quit # Configure an SA creation policy on Switch D so that Switch D will not create SA messages for Source 2.

  • Page 179: Msdp Peers Stay In Disabled State

    MSDP peers stay in disabled state Symptom The configured MSDP peers stay in disabled state. Analysis Possible reasons for the problem include the following: • A TCP connection-based MSDP peering relationship is established between the local interface address and the MSDP peer. •...

  • Page 180: No Exchange Of Locally Registered (S, G) Entries Between Rps

    No exchange of locally registered (S, G) entries between RPs Symptom RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application. Analysis Possible reasons for the problem include the following: • In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP peers to achieve redundancy backup among the RPs.

  • Page 181: Configuring Multicast Vpn

    Configuring multicast VPN Overview Multicast VPN is a technique that implements multicast delivery in VPNs. A VPN comprises multiple sites of the customer network and the public network provided by the network service provider. The sites communicate through the public network. As shown in Figure •...

  • Page 182: Md-Vpn Overview

    Figure 59 Multicast in multiple VPN instances Through multicast VPN, multicast data of VPN A for a multicast group can arrive at only multicast receivers in Site 1, Site 3, and Site 5 of VPN A. The data is multicast in these sites and on the public network.
  • Page 183 Table 15 Basic MD-VPN concepts Concept Description An MD is a set of VPN instances running on PE devices that can Multicast domain (MD) send multicast traffic to each other. Each MD uniquely corresponds to the same set of VPN instances. An MDT is a multicast distribution tree constructed by all PE Multicast distribution tree (MDT) devices in the same VPN.
  • Page 184 • Inside an MD, all the private traffic is transmitted through the MT. The process of multicast traffic transmission through an MT is as follows: a. The local PE device encapsulates a VPN multicast packet into a public network multicast packet.

  • Page 185: Protocols And Standards

    b. After a data-delay period has passed, an MDT switchover process starts. All VPN multicast packets that have entered the public network through that PE device are not encapsulated with the default-group address. They are encapsulated into public network multicast packets with the data-group address.

  • Page 186: How Md-Vpn Works

    How MD-VPN works This section describes how the MD-VPN technology is implemented, including the default-MDT construction, multicast traffic delivery based on the default-MDT, and inter-AS MD-VPN implementation. For a VPN instance, multicast data transmission on the public network is transparent. The VPN data is exchanged between the MTIs of the local PE and the remote PE.
  • Page 187 Default-MDT establishment in a PIM-SM network Figure 63 Default-MDT establishment in a PIM-SM network As shown in Figure 63, PIM-SM is enabled in the network, and all the PE devices support VPN instance A. The process of establishing a default-MDT is as follows: The public network interface of PE 1 initiates a join to the public network RP by specifying the multicast group address as the default-group address in the join message.

  • Page 188: Default-Mdt-Based Delivery

    Default-MDT-based delivery The default-MDT delivers multicast protocol packets and multicast data packets differently. Multicast protocol packet delivery To forward the multicast protocol packets of a VPN over the public network, the local PE device encapsulates them into public network multicast data packets. These packets are transmitted along the default-MDT and are then decapsulated on the remote PE device to go into the normal protocol procedure.
  • Page 189 Figure 64 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) Default-group: 239.1.1.1 Public instance join (11.1.2.1, 239.1.1.1) The multicast protocol packet is delivered as follows:...
  • Page 190 VPN multicast data packets are forwarded across the public network differently in the following circumstances: • If PIM-DM or PIM-SSM is running in the VPN, the multicast source forwards multicast data packets to the receivers along the VPN SPT across the public network. •...

  • Page 191: Mdt Switchover

    If the outgoing interface list of the forwarding entry contains an MTI, PE 1 processes the VPN multicast data packet as described in step 3. The VPN instance on PE 1 considers the VPN multicast data packet to have been sent out of the MTI, because step 3 is transparent to it. PE 1 encapsulates the VPN multicast data packet into a public network multicast packet (11.1.1.1, 239.1.1.1) by using the GRE method.

  • Page 192: Inter-As Md-Vpn

    For a given VPN instance, the default-MDT and the data-MDT are both forwarding tunnels in the same MD. A default-MDT is uniquely identified by a default-group address, and a data-MDT is uniquely identified by a data-group address. Each default-group is uniquely associated with a data-group address range.

  • Page 193: Multicast Vpn Configuration Task List

    • PE 3 and PE 4 are interconnected through their respective public network instance and treat each other as a P device. Figure 67 Multihop EBGP interconnectivity By using this method, only one MD needs to be established for all the ASs. Public network multicast traffic between different ASs is transmitted within this MD.

  • Page 194: Configuration Prerequisites

    Configuration prerequisites Before you configure MD-VPN, complete the following tasks: • Configure a unicast routing protocol on the public network. • Configure MPLS L3VPN on the public network. • Configure PIM (PIM-DM or PIM-SM) on the public network. • Determine the VPN instance names and RDs. •...

  • Page 195: Specifying The Default-Group Address

    Step Command Remarks Create the MD for the VPN By default, the VPN instance does multicast-domain vpn-instance instance and enter MD view. not have an MD. vpn-instance-name Specifying the default-group address The MTI uses the default-group address as the destination address to encapsulate the VPN multicast packets.

  • Page 196: Enabling Data-Group Reuse Logging

    it keeps receiving multicast packets for the VPN before the timer expires, a switchover to data-MDT takes place. Otherwise, the default-MDT is still used for multicast forwarding. Perform the following configuration on the PE. To configure MDT switchover parameters: Step Command Remarks Enter system view.

  • Page 197: Configuring Bgp Mdt Peers Or Peer Groups

    • Determine the cluster IDs of the route reflectors. Configuring BGP MDT peers or peer groups Configure a BGP MDT peer or peer group on a PE router in BGP IPv4 MDT address family view. Then, the PE router can exchange MDT information with the BGP peer or peer group. MDT information includes the IP address of the PE and default-group to which the PE belongs.

  • Page 198: Displaying And Maintaining Multicast Vpn

    Step Command Remarks Enter system view. system-view Enter BGP instance view. bgp as-number Enter BGP IPv4 MDT address-family ipv4 mdt address family view. By default, neither route reflectors Configure the router as a nor clients exist. route reflector and specify a peer { group-name | ip-address For more information about this peer or peer group as its...

  • Page 199: Multicast Vpn Configuration Examples

    Multicast VPN configuration examples This section provides examples of configuring multicast VPN on switches. Intra-AS MD-VPN configuration example Network requirements Item Network requirements • In VPN instance a, S 1 is a multicast source, and R 1, R 2 and R 3 are receivers. •...
  • Page 200 Figure 68 Network diagram VPN a Loop1 VPN b CE a2 VPN a Vlan-int30 Loop1 CE b1 Vlan-int50 Loop1 Loop1 CE a3 PE 2 Vlan-int19 Vlan-int19 PE 3 Loop2 Vlan-int60 PE 1 CE a1 CE b2 Public Vlan-int10 Loop1 VPN b VPN a Table 16 Interface and IP address assignment Device...
  • Page 201 # Configure a Router ID globally, and enable IP multicast routing on the public network. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Configure an MPLS LSR ID, and enable the LDP capability. [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls ldp [PE1-ldp] quit # Create VPN instance a and configure an RD and route target attributes for it.
  • Page 202 [PE1] interface vlan-interface 11 [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 # Assign an IP address to Loopback 1, and enable PIM-SM on this interface. [PE1] interface loopback 1 [PE1-LoopBack1] ip address 1.1.1.1 32 [PE1-LoopBack1] pim sm [PE1-LoopBack1] quit # Configure BGP.
  • Page 203 # Create VPN instance b and 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 [PE2-vpn-instance-b] quit # Create service loopback group 1, and specify its type as multicast tunnel. [PE2] service-loopback group 1 type multicast-tunnel # Select an unused interface, and assign the interface to service loopback group 1.
  • Page 204 [PE2] interface vlan-interface 13 [PE2-Vlan-interface13] ip binding vpn-instance b [PE2-Vlan-interface13] ip address 10.110.3.1 24 [PE2-Vlan-interface13] pim sm [PE2-Vlan-interface13] quit # Bind VLAN-interface 14 with VPN instance a, assign an IP address to VLAN-interface 14, 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...
  • Page 205 [PE2-rip-2] network 10.0.0.0 [PE2-rip-2] import-route bgp [PE2-rip-2] quit [PE2] rip 3 vpn-instance b [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 globally, and enable IP multicast routing on the public network. <PE3> system-view [PE3] router id 1.1.1.3 [PE3] multicast routing [PE3-mrib] quit...
  • Page 206 # Create the MD for VPN instance b, and specify the default-group, MD source interface, and data-group address range for it. [PE3] multicast-domain vpn-instance b [PE3-md-b] default-group 239.2.2.2 [PE3-md-b] source loopback 1 [PE3-md-b] data-group 225.4.4.0 28 [PE3-md-b] quit # Assign an IP address to the public network interface VLAN-interface 19, and enable PIM-SM, MPLS capability, and LDP capability on it.
  • Page 207 [PE3-bgp] peer vpn-g connect-interface loopback 1 [PE3-bgp] peer 1.1.1.1 group vpn-g [PE3-bgp] peer 1.1.1.2 group vpn-g [PE3–bgp] ip vpn-instance a [PE3-bgp-a] address-family ipv4 [PE3-bgp-ipv4-a] import-route rip 2 [PE3-bgp-ipv4-a] import-route direct [PE3-bgp-ipv4-a] quit [PE3-bgp-a] quit [PE3–bgp] ip vpn-instance b [PE3-bgp-b] address-family ipv4 [PE3-bgp-ipv4-b] import-route rip 3 [PE3-bgp-ipv4-b] import-route direct [PE3-bgp-ipv4-b] quit...
  • Page 208 [P-Vlan-interface12] ip address 192.168.6.2 24 [P-Vlan-interface12] pim sm [P-Vlan-interface12] mpls enable [P-Vlan-interface12] mpls ldp enable [P-Vlan-interface12] quit # Assign an IP address to the public network interface VLAN-interface 15, and enable PIM-SM, MPLS capability, and LDP capability on it. [P] interface vlan-interface 15 [P-Vlan-interface15] ip address 192.168.7.2 24 [P-Vlan-interface15] pim sm [P-Vlan-interface15] mpls enable...
  • Page 209 [CEa1-Vlan-interface11] ip address 10.110.2.2 24 [CEa1-Vlan-interface11] pim sm [CEa1-Vlan-interface11] quit # Configure RIP. [CEa1] rip 2 [CEa1-rip-2] network 10.0.0.0 Configure CE b1: # Enable IP multicast routing. <CEb1> system-view [CEb1] multicast routing [CEb1-mrib] quit # Assign an IP address to VLAN-interface 30, and enable PIM-SM on this interface. [CEb1] interface vlan-interface 30 [CEb1-Vlan-interface30] ip address 10.110.8.1 24 [CEb1-Vlan-interface30] pim sm...
  • Page 210 [CEa2-LoopBack1] pim sm [CEa2-LoopBack1] quit # Configure Loopback 1 as a BSR and RP for VPN instance a. [CEa2] pim [CEa2-pim] c-bsr 22.22.22.22 [CEa2-pim] c-rp 22.22.22.22 [CEa2-pim] quit # Configure RIP. [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.

  • Page 211: Inter-As Md-Vpn Configuration Example

    [CEb2-Vlan-interface18] pim sm [CEb2-Vlan-interface18] quit # Configure RIP. [CEb2] rip 3 [CEb2-rip-3] network 10.0.0.0 Verifying the configuration # Display information about the default-groups in VPN instances on PE 1. [PE1] display multicast-domain default-group Group address Source address Interface VPN instance 239.1.1.1 1.1.1.1 MTunnel0...
  • Page 212 Item Network requirements • Enable IP multicast routing on CE a1, CE a2, CE b1, and CE b2. • Run IGMPv2 on VLAN-interface 30 of CE a2. IGMP • Run IGMPv2 on VLAN-interface 40 of CE b2. • Enable PIM-SM on all public network interfaces of PE 2 and PE 3. •...
  • Page 213 Devic Interface IP address Device Interface IP address PE 2 Vlan-int2 10.10.1.2/24 PE 4 Vlan-int4 10.10.2.2/24 PE 2 Vlan-int3 192.168.1.1/24 PE 4 Vlan-int13 10.11.3.1/24 PE 2 Loop1 1.1.1.2/32 PE 4 Vlan-int14 10.11.4.1/32 PE 2 Loop2 Loop2 11.11.11.11/32 PE 4 1.1.1.4/32 CE a1 Vlan-int10 10.11.5.1/24...
  • Page 214 # Create VPN instance b and configure an RD and route target attributes for it. [PE1] ip vpn-instance b [PE1-vpn-instance-b] route-distinguisher 200:1 [PE1-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE1-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE1-vpn-instance-b] quit # Enable IP multicast routing in VPN instance b. [PE1] multicast routing vpn-instance b [PE1-mrib-b] quit # Create the MD for VPN instance b, and specify the default-group, MD source interface, and...
  • Page 215 [PE1-bgp] group pe1-pe4 external [PE1-bgp] peer pe1-pe4 as-number 200 [PE1-bgp] peer pe1-pe4 ebgp-max-hop 255 [PE1-bgp] peer pe1-pe4 connect-interface loopback 1 [PE1-bgp] peer 1.1.1.4 group pe1-pe4 [PE1–bgp] ip vpn-instance a [PE1-bgp-a] address-family ipv4 [PE1-bgp-ipv4-a] import-route ospf 2 [PE1-bgp-ipv4-a] import-route direct [PE1-bgp-ipv4-a] quit [PE1-bgp-a] quit [PE1–bgp] ip vpn-instance b [PE1-bgp-b] address-family ipv4...
  • Page 216 [PE2] multicast routing [PE2-mrib] quit # Configure an MPLS LSR ID, and enable the LDP capability. [PE2] mpls lsr-id 1.1.1.2 [PE2] mpls ldp [PE2-ldp] quit # Assign an IP address to the public network interface VLAN-interface 2, and enable PIM-SM, MPLS capability, and LDP capability on it.
  • Page 217 [PE2-bgp] group pe2-pe1 internal [PE2-bgp] peer pe2-pe1 connect-interface loopback 1 [PE2-bgp] peer 1.1.1.1 group pe2-pe1 [PE2-bgp] group pe2-pe3 external [PE2-bgp] peer pe2-pe3 as-number 200 [PE2-bgp] peer pe2-pe3 connect-interface loopback 1 [PE2-bgp] peer 1.1.1.3 group pe2-pe3 [PE2-bgp] address-family ipv4 [PE2-bgp-ipv4] peer pe2-pe1 enable [PE2-bgp-ipv4] peer pe2-pe1 route-policy map2 export [PE2-bgp-ipv4] peer pe2-pe1 label-route-capability [PE2-bgp-ipv4] peer pe2-pe3 enable...
  • Page 218 [PE3-Vlan-interface4] mpls enable [PE3-Vlan-interface4] mpls ldp enable [PE3-Vlan-interface4] quit # Assign an IP address to the public network interface VLAN-interface 3, and enable PIM-SM and MPLS on it. [PE3] interface vlan-interface 3 [PE3-Vlan-interface3] ip address 192.168.1.2 24 [PE3-Vlan-interface3] pim sm [PE3-Vlan-interface3] mpls enable [PE3-Vlan-interface3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on this interface.
  • Page 219 [PE3-bgp-ipv4] peer pe3-pe2 enable [PE3-bgp-ipv4] peer pe3-pe2 route-policy map1 export [PE3-bgp-ipv4] peer pe3-pe2 label-route-capability [PE3-bgp-ipv4] import-route ospf 1 [PE3-bgp-ipv4] quit [PE3–bgp] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 22.22.22.22 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 10.10.0.0 0.0.255.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure a routing policy.
  • Page 220 # Create the MD for VPN instance a, and specify the default-group, MD source interface, and data-group address range for it. [PE4] multicast-domain vpn-instance a [PE4-md-a] default-group 239.1.1.1 [PE4-md-a] source loopback 1 [PE4-md-a] data-group 225.1.1.0 28 [PE4-md-a] quit # Create VPN instance b and configure an RD and route target attributes for it. [PE4] ip vpn-instance b [PE4-vpn-instance-b] route-distinguisher 200:1 [PE4-vpn-instance-b] vpn-target 200:1 export-extcommunity...
  • Page 221 [PE4-LoopBack1] quit # Configure BGP. [PE4] bgp 200 [PE4-bgp] group pe4-pe3 internal [PE4-bgp] peer pe4-pe3 connect-interface loopback 1 [PE4-bgp] peer 1.1.1.3 group pe4-pe3 [PE4-bgp] group pe4-pe1 external [PE4-bgp] peer pe4-pe1 as-number 100 [PE4-bgp] peer pe4-pe1 ebgp-max-hop 255 [PE4-bgp] peer pe4-pe1 connect-interface loopback 1 [PE4-bgp] peer 1.1.1.1 group pe4-pe1 [PE4–bgp] ip vpn-instance a [PE4-bgp-a] address-family ipv4...
  • Page 222 [PE4-ospf-3-area-0.0.0.0] quit [PE4-ospf-3] quit Configure CE a1: # Enable IP multicast routing. <CEa1> system-view [CEa1] multicast routing [CEa1-mrib] quit # Assign an IP address to VLAN-interface 10, and enable PIM-SM on this interface. [CEa1] interface vlan-interface 10 [CEa1-Vlan-interface10] ip address 10.11.5.1 24 [CEa1-Vlan-interface10] pim sm [CEa1-Vlan-interface10] quit # Assign an IP address to VLAN-interface 11, and enable PIM-SM on this interface.
  • Page 223 [CEb1-Vlan-interface12] pim sm [CEb1-Vlan-interface12] quit # Configure OSPF. [CEb1] ospf 1 [CEb1-ospf-1] area 0.0.0.0 [CEb1-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb1-ospf-1-area-0.0.0.0] quit [CEb1-ospf-1] quit Configure CE a2: # Enable IP multicast routing. <CEa2> system-view [CEa2] multicast routing [CEa2-mrib] quit # Assign an IP address to VLAN-interface 30, and enable IGMP on this interface. [CEa2] interface vlan-interface 30 [CEa2-Vlan-interface30] ip address 10.11.7.1 24 [CEa2-Vlan-interface30] igmp enable...

  • Page 224: Troubleshooting Md-Vpn

    [CEb2-LoopBack1] pim sm [CEb2-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP for VPN instance b. [CEb2] pim [CEb2-pim] c-bsr 3.3.3.3 [CEb2-pim] c-rp 3.3.3.3 [CEb2-pim] quit # Configure OSPF. [CEb2] ospf 1 [CEb2-ospf-1] area 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb2-ospf-1-area-0.0.0.0] quit [CEb2-ospf-1] quit...

  • Page 225: An Mvrf Cannot Be Created

    between the VPN instance on the local PE device and the same VPN instance on the remote PE device. • BGP and unicast route configurations are prerequisites for PIM to obtain correct routing information. PIM can only be enabled on the MTI interface if at least one interface of the VPN instance is enabled with PIM.

  • Page 226: Configuring Mld Snooping

    Configuring MLD snooping Overview MLD snooping runs on a Layer 2 switch as an IPv6 multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from MLD messages that are exchanged between the hosts and the router. As shown in Figure 70, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...
  • Page 227 Figure 71 MLD snooping related ports The following describes the ports involved in MLD snooping, as shown in Figure • Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include designated routers and MLD queriers. In Figure 71, FortyGigE 1/0/1 of Switch A and FortyGigE 1/0/1 of Switch B are the router ports.

  • Page 228: How Mld Snooping Works

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

  • Page 229: Protocols And Standards

    • If a match is found and the receiving port is not the only outgoing interface in the forwarding entry, the switch performs the following actions: Discards the MLD done message. Sends an MLD multicast-address-specific query to identify whether the group has active listeners attached to the receiving port.

  • Page 230: Mld Snooping Configuration Task List

    MLD snooping configuration task list Tasks at a glance Configuring basic MLD snooping features: • (Required.) Enabling MLD snooping • (Optional.) Specifying an MLD snooping version • (Optional.) Setting the maximum number of MLD snooping forwarding entries • (Optional.) Setting the MLD last listener query interval Configuring MLD snooping port features: •...

  • Page 231: Specifying An Mld Snooping Version

    You can enable MLD snooping for the specified VLANs in MLD-snooping view or for a VLAN in VLAN view. For a VLAN, the configuration in VLAN interface has the same priority as the configuration in MLD-snooping view, and the most recent configuration takes effect. Enabling MLD snooping in MLD-snooping view Step Command...

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

    Step Command Remarks Specify an MLD snooping version version-number vlan version for the specified The default setting is 1. vlan-list VLANs. Specifying an MLD snooping version in VLAN view Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Specify an MLD snooping mld-snooping version The default setting is 1.

  • Page 233: Configuring Mld Snooping Port Features

    Setting the MLD last listener query interval globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the MLD last listener The default setting is 1 last-listener-query-interval interval query interval globally. second. Setting the MLD last listener query interval in a VLAN Step Command Remarks...

  • Page 234: Configuring Static Ports

    Step Command Remarks Set the aging timer for The default setting is 260 dynamic router ports router-aging-time interval seconds. globally. Set the aging timer for The default setting is 260 dynamic member ports host-aging-time interval seconds. globally. Setting the aging timers for dynamic ports in a VLAN Step Command Remarks...

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

    Configuring a port as a simulated member host When a port is configured as a simulated member host, it is equivalent to an independent host in the following ways: • It sends an unsolicited MLD report when you complete the configuration. •...

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

    Step Command Remarks Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Enable fast-leave mld-snooping fast-leave [ vlan By default, fast-leave processing processing on the port. vlan-list ] is disabled for a port. Disabling a port from becoming a dynamic router port A receiver host might send MLD general queries or IPv6 PIM hello messages for testing purposes.

  • Page 237: Enabling The Mld Snooping Querier

    Enabling the MLD snooping querier This feature enables the switch to periodically send MLD general queries to establish and maintain multicast forwarding entries at the data link Layer. You can configure an MLD snooping querier on a network without Layer 3 multicast devices. When you enable the MLD snooping querier, follow these guidelines: •...

  • Page 238: Configuring Parameters For Mld Messages

    Configuring parameters for MLD general queries and responses in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Set the MLD general query The default setting is 125 mld-snooping query-interval interval for the VLAN. seconds. interval Set the maximum response mld-snooping...

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

    Step Command Remarks By default, if the MLD snooping querier has received MLD general queries, the source IPv6 address of MLD multicast-address-specific queries is the source IPv6 Configure the source IPv6 address of MLD general queries. address for MLD mld-snooping special-query Otherwise, it is the IPv6 link-local multicast-address-specific source-ip ipv6-address...

  • Page 240: Configuring Mld Snooping Policies

    Configuring MLD snooping policies Before you configure MLD snooping policies, complete the following tasks: • Enable MLD snooping for the VLAN. • Determine the ACL used as the IPv6 multicast group policy. • Determine the maximum number of IPv6 multicast groups that a port can join. Configuring an IPv6 multicast group policy This feature enables the switch to filter MLD reports by using an ACL that specifies IPv6 multicast groups and the optional sources.

  • Page 241: Enabling Dropping Unknown Ipv6 Multicast Data

    Enabling IPv6 multicast source port filtering globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Enable IPv6 multicast By default, IPv6 multicast source source-deny port interface-list source port filtering. port filtering is disabled. Enabling IPv6 multicast source port filtering on a port Step Command Remarks...

  • Page 242: Setting The Maximum Number Of Ipv6 Multicast Groups On A Port

    Setting the maximum number of IPv6 multicast groups on a port You can set the maximum number of IPv6 multicast groups on a port to regulate the port traffic. Configuration guidelines When you set the maximum number of IPv6 multicast groups on a port, follow these guidelines: •...

  • Page 243: Displaying And Maintaining Mld Snooping

    Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. Enable the IPv6 multicast By default, the IPv6 multicast mld-snooping overflow-replace group replacement feature group replacement feature is [ vlan vlan-list ] on the port.

  • Page 244: Mld Snooping Configuration Examples

    MLD snooping configuration examples IPv6 group policy configuration example Network requirements As shown in Figure 72, Router A runs MLDv1 and acts as the MLD querier, and Switch A runs MLDv1 snooping. Configure a group policy to meet the following requirements: •...

  • Page 245: Static Port Configuration Example

    # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, and assign FortyGigE 1/0/1 through FortyGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port fortygige 1/0/1 to fortygige 1/0/4 # Enable MLD snooping for VLAN 100. [SwitchA-vlan100] mld-snooping enable # Enable dropping IPv6 unknown multicast data for VLAN 100.
  • Page 246 • To enhance the reliability of IPv6 multicast traffic transmission, configure FortyGigE 1/0/3 and FortyGigE 1/0/5 on Switch C as static member ports for the IPv6 multicast group FF1E::101. • Suppose the STP runs on the network. To avoid data loops, the forwarding path from Switch A to Switch C is blocked under normal conditions.
  • Page 247 [RouterA-FortyGigE1/0/2] ipv6 pim dm [RouterA-FortyGigE1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, and assign FortyGigE 1/0/1 through FortyGigE 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port fortygige 1/0/1 to fortygige 1/0/3 # Enable MLD snooping for VLAN 100.

  • Page 248: Mld Snooping Querier Configuration Example

    Verifying the configuration # Display static router port information in VLAN 100 on Switch A. [SwitchA] display mld-snooping static-router-port vlan 100 VLAN 100: Router slots (1 in total): Router ports (1 in total): FGE1/0/3 The output shows that FortyGigE 1/0/3 on Switch A has become a static router port. # Display static MLD snooping forwarding entries in VLAN 100 on Switch C.
  • Page 249 Figure 74 Network diagram Source 1 Source 2 VLAN 100 1::10/64 1::20/64 Receiver Receiver FGE1/0/2 FGE1/0/2 FGE1/0/1 FGE1/0/3 FGE1/0/3 FGE1/0/1 Host A Host B FGE1/0/4 Switch A Switch B Querier Receiver Receiver FGE1/0/2 FGE1/0/1 FGE1/0/2 FGE1/0/3 FGE1/0/1 Host D Host C Switch D Switch C Configuration procedure...
  • Page 250 # Enable MLD snooping globally. <SwitchC> system-view [SwitchC] mld-snooping [SwitchC-mld-snooping] quit # Create VLAN 100, and assign FortyGigE 1/0/1 through FortyGigE 1/0/3 to the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port fortygige 1/0/1 to fortygige 1/0/3 # Enable MLD snooping for VLAN 100. [SwitchC-vlan100] mld-snooping enable # Enable dropping unknown multicast packets for VLAN 100.

  • Page 251: Troubleshooting Mld Snooping

    Troubleshooting MLD snooping Layer 2 multicast forwarding cannot function Symptom Layer 2 multicast forwarding cannot function through MLD snooping. Solution To resolve the problem: Use the display mld-snooping command to display MLD snooping status. If MLD snooping is not enabled, use the mld-snooping command in system view to enable MLD snooping globally.

  • Page 252: Configuring Ipv6 Pim Snooping

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

  • Page 253: Configuring Ipv6 Pim Snooping

    b. Broadcasts all other types of received IPv6 PIM messages except PIM hello messages in the VLAN. c. 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 254: Displaying And Maintaining Ipv6 Pim Snooping

    Displaying and maintaining IPv6 PIM snooping Execute display commands in any view and reset commands in user view. Task Command Display IPv6 PIM snooping neighbor display ipv6 pim-snooping neighbor [ vlan vlan-id ] [ slot information. slot-number ] [ verbose ] Display IPv6 PIM snooping routing display ipv6 pim-snooping routing-table [ vlan vlan-id ] [ slot entries.
  • Page 255 Configuration procedure Assign an IPv6 address and prefix length for each interface according to Figure 76. (Details not shown.) Configure OSPFv3 on all the routers. (Details not shown.) Configure Router A: # Enable IPv6 multicast routing globally. <RouterA> system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable IPv6 PIM-SM on each interface.
  • Page 256 # Enable IPv6 multicast routing globally. <RouterD> system-view [RouterD] ipv6 multicast routing [RouterD-mrib6] quit # Enable MLD on FortyGigE 1/0/1. [RouterD] interface fortygige 1/0/1 [RouterD-FortyGigE1/0/1] mld enable [RouterD-FortyGigE1/0/1] quit # Enable IPv6 PIM-SM on FortyGigE 1/0/2. [RouterD] interface fortygige 1/0/2 [RouterD-FortyGigE1/0/2] ipv6 pim sm [RouterD-FortyGigE1/0/2] quit Configure Switch A:...

  • Page 257: Troubleshooting Ipv6 Pim Snooping

    The output shows that Router A, Router B, Router C, and Router D are IPv6 PIM snooping neighbors. # On Switch A, display IPv6 PIM snooping routing entries for VLAN 100. [SwitchA] display pim-snooping ipv6 routing-table vlan 100 Total 2 entries. FSM flag: NI-no info, J-join, PP-prune pending VLAN 100: Total 2 entries.
  • Page 258 If MLD snooping is not enabled, enable MLD snooping globally, and then enable MLD snooping and IPv6 PIM snooping for the VLAN. If IPv6 PIM snooping is not enabled, enable IPv6 PIM snooping for the VLAN. If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 259: Configuring Ipv6 Multicast Vlans

    Configuring IPv6 multicast VLANs Overview As shown in Figure 77, Host A, Host B, and Host C are in different VLANs and the same IPv6 multicast group. When Switch A (Layer 3 device) receives IPv6 multicast data for that group, it sends three copies of the data to Switch B (Layer 2 device).
  • Page 260 Figure 78 Sub-VLAN-based multicast VLAN MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in each sub-VLAN. When Switch A receives IPv6 multicast data from the multicast source, it sends only one copy of the IPv6 multicast data to the IPv6 multicast VLAN on Switch B. Then, Switch B sends a separate copy to each sub-VLAN of the IPv6 multicast VLAN.

  • Page 261: Ipv6 Multicast Vlan Configuration Task List

    IPv6 multicast VLAN configuration task list Tasks at a glance (Required.) Perform one of the following tasks: • Configuring a sub-VLAN-based IPv6 multicast VLAN • Configuring a port-based IPv6 multicast VLAN Configuring user port attributes Assigning user ports to an IPv6 multicast VLAN (Optional.) Setting the maximum number of IPv6 multicast VLAN forwarding entries If you have configured both a sub-VLAN-based IPv6 multicast VLAN and a port-based IPv6 multicast...

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

    Configuring a port-based IPv6 multicast VLAN To configure a port-based IPv6 multicast VLAN, perform the following steps: Configure a VLAN as an IPv6 multicast VLAN. Configure the attributes for user ports that are connected to the multicast receivers. Assign the user ports to the IPv6 multicast VLAN. You can assign only Layer 2 Ethernet interfaces and Layer 2 aggregate interfaces as user ports to an IPv6 multicast VLAN.

  • Page 263: Setting The Maximum Number Of Ipv6 Multicast Vlan Forwarding Entries

    Assigning ports to an IPv6 multicast VLAN in IPv6 multicast VLAN view Step Command Remarks Enter system view. system-view Configure an IPv6 VLAN as By default, a VLAN is not an IPv6 an IPv6 multicast VLAN and ipv6 multicast-vlan vlan-id multicast VLAN.

  • Page 264: Ipv6 Multicast Vlan Configuration Examples

    Task Command Display information about IPv6 display ipv6 multicast-vlan [ vlan-id ] multicast VLANs. Display information about IPv6 display ipv6 multicast-vlan group [ ipv6-source-address | multicast groups in IPv6 multicast ipv6-group-address | slot slot-number | verbose | vlan vlan-id ] * VLANs.
  • Page 265 Figure 80 Network diagram Source FGE1/0/2 MLD querier Vlan-int20 Switch A 1::2/64 FGE1/0/1 1::1/64 Vlan-int10 2001::1/64 FGE1/0/1 Switch B FGE1/0/2 FGE1/0/4 FGE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure Switch A: # Enable IPv6 multicast routing globally.
  • Page 266 Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 2, assign FortyGigE 1/0/2 to the VLAN, and enable MLD snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port fortygige 1/0/2 [SwitchB-vlan2] mld-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign FortyGigE 1/0/3 to the VLAN, and enable MLD snooping for the VLAN.

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

    IPv6 multicast VLAN 10: Total 1 entries. (::, FF1E::101) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that the IPv6 multicast VLAN (VLAN 10) contains sub-VLANs VLAN 2 through VLAN 4. Switch B will replicate the IPv6 multicast data of VLAN 10 to VLAN 2 through VLAN 4. Port-based IPv6 multicast VLAN configuration example Network requirements As shown in...
  • Page 268 [SwitchA] vlan 20 [SwitchA-vlan20] port fortygige 1/0/2 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 1::2 64 [SwitchA-Vlan-interface20] ipv6 pim dm [SwitchA-Vlan-interface20] quit # Create VLAN 10, and assign FortyGigE 1/0/1 to the VLAN. [SwitchA] vlan 10 [SwitchA-vlan10] port fortygige 1/0/1 [SwitchA-vlan10] quit...
  • Page 269 [SwitchB-FortyGigE1/0/2] quit # Configure FortyGigE 1/0/3 as a hybrid port, and configure VLAN 3 as the PVID of the hybrid port. [SwitchB] interface fortygige 1/0/3 [SwitchB-FortyGigE1/0/3] port link-type hybrid [SwitchB-FortyGigE1/0/3] port hybrid pvid vlan 3 # Assign FortyGigE 1/0/3 to VLAN 3 and VLAN 10 as an untagged VLAN member. [SwitchB-FortyGigE1/0/3] port hybrid vlan 3 untagged [SwitchB-FortyGigE1/0/3] port hybrid vlan 10 untagged [SwitchB-FortyGigE1/0/3] quit...
  • Page 270 FGE1/0/2 (00:03:23) FGE1/0/3 (00:04:07) FGE1/0/4 (00:04:16) The output shows that MLD snooping maintains the user ports in VLAN 10. Switch B will forward the IPv6 multicast data of VLAN 10 through these user ports.

  • Page 271: Configuring Ipv6 Multicast Routing And Forwarding

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

  • Page 273: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

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

  • Page 274: Configuring Ipv6 Multicast Routing And Forwarding

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

  • Page 275: Configuring Ipv6 Static Multicast Mac Address Entries

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number ipv6 multicast boundary Configure the interface as By default, the interface is not { ipv6-group-address prefix-length | an IPv6 multicast configured as an IPv6 multicast scope { scope-id | admin-local | forwarding boundary for an forwarding boundary for any global | organization-local |...

  • Page 276: Configuring Ipv6 Multicast Forwarding Among Sub-Vlans Of A Super Vlan

    Configuring IPv6 multicast forwarding among sub-VLANs of a super VLAN A super VLAN is associated with multiple sub-VLANs. Sub-VLANs are isolated with each other at Layer 2. For information about the super VLAN and sub-VLANs, see Layer 2—LAN Switching Configuration Guide. To configure multicast forwarding among sub-VLANs of a super VLAN: Step Command...

  • Page 277: Configuration Examples

    Task Command ipv6-group-address [ prefix-length ] | incoming-interface interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number | slot slot-number | statistics ] * display ipv6 multicast [ vpn-instance vpn-instance-name ] Display information about the DF list in the forwarding-table df-list [ ipv6-group-address ] [ verbose ] IPv6 multicast forwarding table.
  • Page 278 Figure 84 Network diagram Configuration procedure Assign an IPv6 address and prefix length to each interface as shown in Figure 84. (Details not shown.) Configure OSPFv3 on all the switches. (Details not shown.) Configure a GRE tunnel: # Create service loopback group 1 on Switch A and specify its service type as Tunnel. <SwitchA>...
  • Page 279 [SwitchC-Tunnel0] source 3001::2 [SwitchC-Tunnel0] destination 2001::1 [SwitchC-Tunnel0] quit Enable IPv6 multicast routing, IPv6 PIM-DM, and MLD: # On Switch A, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface. [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ipv6 pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101...
  • Page 280 Protocol: mld, UpTime: 00:04:25, Expires: - (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: - 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 281: Configuring Mld

    Configuring MLD Overview Multicast Listener Discovery (MLD) establishes and maintains IPv6 multicast group memberships between a Layer 3 multicast device and hosts on the directly connected subnet. MLD has the following versions: • MLDv1 (defined by RFC 2710), which is derived from IGMPv2. •...
  • Page 282 Joining an IPv6 multicast group Figure 85 MLD queries and reports As shown in Figure 85, Host B and Host C are interested in the IPv6 multicast data addressed to IPv6 multicast group G1. Host A is interested in the IPv6 multicast data addressed to G2. The following process describes how the hosts join the IPv6 multicast groups and how the MLD querier (Router B in Figure...

  • Page 283: Mldv2 Enhancements

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

  • Page 284: Mld Support For Vpns

    • Filter mode—Router keeps tracing the Include or Exclude state. • List of sources—Router keeps tracing the newly added or deleted IPv6 multicast source. • Timers—Filter timers, which include the time that the router waits before switching to the Include mode after an IPv6 multicast address times out, and the source timer for source recording.

  • Page 285: Enabling Mld

    Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships are created and maintained. To enable MLD: Step Command Remarks Enter system view. system-view ipv6 multicast routing Enable IPv6 multicast routing By default, IPv6 multicast routing [ vpn-instance and enter IPv6 MRIB view.

  • Page 286: Configuring An Ipv6 Multicast Group Policy

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the interface is not a mld static-group Configure the interface as a ipv6-group-address [ source static member of any IPv6 static group member. ipv6-source-address ] multicast groups.
  • Page 287 interval at which a querier sends multicast-address-and-source-specific queries after receiving a report that changes IPv6 multicast source and group mappings. • MLD last listener query count—In MLDv1, it sets the number of multicast-address-specific queries that the querier sends after receiving a done message. In MLDv2, it sets the number of multicast-address-and-source-specific queries that the querier sends after receiving a report that changes IPv6 multicast group and source mappings.

  • Page 288: Enabling Fast-Leave Processing

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

  • Page 289: Configuring Mld Ssm Mappings

    Step Command Remarks Enable fast-leave mld fast-leave [ group-policy By default, fast-leave processing processing. acl6-number ] is disabled. Configuring MLD SSM mappings This feature enables the switch to provide SSM services for MLDv1 hosts. This feature does not process MLDv2 messages. As a best practice, enable MLDv2 on the receiver-side interface to ensure that MLDv2 reports can be processed.

  • Page 290: Displaying And Maintaining Mld

    Displaying and maintaining MLD CAUTION: The reset mld group command might cause IPv6 multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command display mld [ vpn-instance vpn-instance-name ] Display information about MLD groups. group [ ipv6-group-address | interface interface-type interface-number ] [ static | verbose ] display mld [ vpn-instance vpn-instance-name ]...
  • Page 291 Figure 87 Network diagram Receiver IPv6 PIM-DM Host A Vlan-int100 3000::12/64 Switch A Host B Querier Vlan-int200 3001::10/64 Receiver Host C Switch B Vlan-int200 3001::12/64 Host D Switch C Configuration procedure Assign an IPv6 address and prefix length to each interface as shown in Figure 87.

  • Page 292: Mld Ssm Mapping Configuration Example

    [SwitchB-Vlan-interface201] ipv6 pim dm [SwitchB-Vlan-interface201] quit # On Switch C, enable IPv6 multicast routing globally. <SwitchC> system-view [SwitchC] ipv6 multicast routing [SwitchC-mrib6] quit # Enable MLD on VLAN-interface 200. [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] mld enable [SwitchC-Vlan-interface200] quit # Enable IPv6 PIM-DM on VLAN-interface 202. [SwitchC] interface vlan-interface 202 [SwitchC-Vlan-interface202] ipv6 pim dm [SwitchC-Vlan-interface202] quit...
  • Page 293 Configure the MLD SSM mapping feature on Switch D so that the receiver host will receive IPv6 multicast data only from Source 1 and Source 3. Figure 88 Network diagram Source 2 Source 3 Switch B Switch C Vlan-int200 Vlan-int102 Vlan-int300 Vlan-int102 Vlan-int103...
  • Page 294 [SwitchD-Vlan-interface104] ipv6 pim sm [SwitchD-Vlan-interface104] quit # On Switch A, enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Enable IPv6 PIM-SM on each interface. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ipv6 pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 104...

  • Page 295: Troubleshooting Mld

    Vlan-interface400(FE80::101): MLD groups reported in total: 1 Group address: FF3E::101 Last reporter: FE80::1 Uptime: 00:02:04 Expires: Off # Display IPv6 PIM routing entries on Switch D. [SwitchD] display ipv6 pim routing-table Total 0 (*, G) entry; 2 (S, G) entry (1001::1, FF3E::101) RP: 1003::2 Protocol: pim-ssm, Flag:...

  • Page 296: Inconsistent Membership Information On The Routers On The Same Subnet

    • If the MLD version on the router interface is lower than that on the host, the router cannot recognize the MLD report from the host. • If the mld group-policy command has been configured on an interface, the interface cannot receive report messages that fail to pass filtering.

  • Page 297: Configuring Ipv6 Pim

    Configuring IPv6 PIM Overview IPv6 Protocol Independent Multicast (IPv6 PIM) provides IPv6 multicast forwarding by leveraging IPv6 unicast static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as RIPng, OSPFv3, IPv6 IS-IS, or IPv6 BGP. IPv6 PIM uses the underlying IPv6 unicast routing to generate an IPv6 multicast routing table without relying on any particular IPv6 unicast routing protocol.
  • Page 298 data to all downstream nodes in the network. In the flooding process, all the routers in the IPv6 PIM-DM domain create the (S, G) entry. The nodes without downstream receivers are pruned. A router that has no downstream receivers multicasts a prune message to all IPv6 PIM routers on the subnet. When the upstream node receives the prune message, it removes the receiving interface from the (S, G) entry.

  • Page 299: Ipv6 Pim-Sm Overview

    Assert On a subnet with more than one multicast router, the assert mechanism shuts off duplicate multicast flows to the network. It does this by electing a unique multicast forwarder for the subnet. Figure 90 Assert mechanism As shown in Figure 90, after Router A and Router B receive an (S, G) packet from the upstream node, they both forward the packet to the local subnet.
  • Page 300 DR election A DR is required on both the source-side network and receiver-side network. A source-side DR acts on behalf of the IPv6 multicast source to send register messages to the RP. The receiver-side DR acts on behalf of the receiver hosts to send join messages to the RP. IMPORTANT: MLD must be enabled on the device that acts as the receiver-side DR.
  • Page 301 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 92, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR.
  • Page 302 RPT building Figure 93 RPT building in an IPv6 PIM-SM domain Host A Source Receiver Host B Server Receiver Join message IPv6 multicast packets Host C As shown in Figure 93, the process of building an RPT is as follows: When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the receiver-side DR.
  • Page 303 Figure 94 IPv6 multicast source registration As shown in Figure 94, the IPv6 multicast source registers with the RP as follows: The IPv6 multicast source S sends the first multicast packet to the IPv6 multicast group G. When receiving the multicast packet, the source-side DR that directly connects to the IPv6 multicast source encapsulates the packet into an register message and unicasts the message to the RP.

  • Page 304: Ipv6 Bidir-Pim Overview

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

  • Page 307: Ipv6 Administrative Scoping Overview

    Figure 97 RPT building at the IPv6 multicast source side As shown in Figure 97, the process for building a source-side RPT is relatively simple: When an IPv6 multicast source sends multicast packets to the IPv6 multicast group G, the DF in each subnet unconditionally forwards the packets to the RP.
  • Page 308 with the same scope field value. IPv6 multicast protocol packets, such as assert messages and BSMs, of these IPv6 multicast groups cannot cross the boundary of the IPv6 admin-scoped zone for the group range. The IPv6 multicast group ranges to which different IPv6 admin-scoped zones are designated can have intersections.

  • Page 309: Ipv6 Pim-Ssm Overview

    Figure 99 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone. Table 19 lists the possible values of the scope field.

  • Page 310: Relationship Among Ipv6 Pim Protocols

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

  • Page 311: Ipv6 Pim Support For Vpns

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

  • Page 312: Ipv6 Pim-Dm Configuration Task List

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

  • Page 313: Configuring State Refresh Parameters

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

  • Page 314: Configuring Ipv6 Pim-Sm

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

  • Page 315: Configuring An Rp

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM. ipv6 pim sm disabled. Configuring an RP An RP can provide services for multiple or all IPv6 multicast groups. However, only one RP at a time can forward IPv6 multicast traffic for an IPv6 multicast group.

  • Page 316: Configuring A Bsr

    Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-rp ipv6-address [ advertisement-interval adv-interval | By default, no C-RPs Configure a C-RP. { group-policy acl6-number | scope exist. scope-id } | holdtime hold-time | priority priority ] * (Optional.) Configure a By default, no C-RP crp-policy acl6-number...
  • Page 317 Step Command Remarks ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] c-bsr ipv6-address [ scope Configure a C-BSR. scope-id ] [ hash-length hash-length By default, no C-BSRs exist. | priority priority ] * (Optional.) Configure a BSR By default, no BSR policy bsr-policy acl6-number policy.

  • Page 318: Configuring Ipv6 Multicast Source Registration

    Configuring IPv6 multicast source registration An IPv6 PIM register policy enables an RP to filter register messages by using an ACL that specifies the IPv6 multicast sources and groups. The policy limits the IPv6 multicast sources and groups to which an RP is designated. If a register message is denied by the ACL or does not match the ACL, the RP discards the register message and sends a register-stop message to the source-side DR.

  • Page 319: Ipv6 Bidir-Pim Configuration Task List

    IPv6 BIDIR-PIM configuration task list Tasks at a glance Remarks (Required.) Enabling IPv6 BIDIR-PIM (Required.) Configuring an RP: • Configuring a static RP You must configure a static RP, a C-RP, or both in an • Configuring a C-RP IPv6 BIDIR-SM domain. •...

  • Page 320: Configuring An Rp

    Configuring an RP CAUTION: When both IPv6 PIM-SM and IPv6 BIDIR-PIM run on the IPv6 PIM network, do not use the same RP to provide services for IPv6 PIM-SM and IPv6 BIDIR-PIM. Otherwise, exceptions might occur to the IPv6 PIM routing table. An RP can provide services for multiple or all IPv6 multicast groups.

  • Page 321: Configuring A Bsr

    An advertisement message contains a holdtime option, which defines the C-RP lifetime for the advertising C-RP. After the BSR receives an advertisement message from a C-RP, it starts a timer for the C-RP. If the BSR does not receive any advertisement message when the timer expires, it considers the C-RP failed or unreachable.
  • Page 322 BSR address to replace its own BSR address and no longer regards itself as the BSR. The winner retains its own BSR address and continues to regard itself as the BSR. The elected BSR distributes the RP-set information collected from C-RPs to all routers in the IPv6 BIDIR-PIM domain.

  • Page 323: Configuring Ipv6 Pim-Ssm

    a BSMF as an entire BSM and updates the RP-set information each time it receives a BSMF. It learns only part of the RP-set information, which further affects the RP election. To disable BSM semantic fragmentation: Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view.

  • Page 324: Configuring The Ipv6 Ssm Group Range

    Step Command Remarks Enter system view. system-view ipv6 multicast routing Enable IP multicast routing, By default, IPv6 multicast routing [ vpn-instance and enter MRIB view. is disabled. vpn-instance-name ] Return to system view. quit interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM.

  • Page 325: Configuration Prerequisites

    Tasks at a glance (Optional.) Enabling BFD for IPv6 PIM (Optional.) Enabling IPv6 PIM passive mode (Optional.) Enabling IPv6 PIM NSR Configuration prerequisites Before you configure common IPv6 PIM features, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer.

  • Page 326: Configuring Ipv6 Pim Hello Message Options

    Configuring IPv6 PIM hello message options In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, hello messages exchanged among routers contain the following configurable options: • DR_Priority (for IPv6 PIM-SM only)—Priority for DR election. The device with the highest priority wins the DR election.

  • Page 327: Configuring Common Ipv6 Pim Timers

    Step Command Remarks The default setting is 2500 hello-option override-interval Set the override interval. milliseconds. interval By default, neighbor tracking is Enable neighbor tracking. hello-option neighbor-tracking disabled. Configuring hello message options on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 328: Setting The Maximum Size Of Each Join Or Prune Message

    You can configure common IPv6 PIM timers for all interfaces in IPv6 PIM view or for the current interface in interface view. The configuration made in interface view takes priority over the configuration made in IPv6 PIM view. TIP: As a best practice, use the default settings for a network without special requirements. Configuring common IPv6 PIM timers globally Step Command...

  • Page 329: Enabling Bfd For Ipv6 Pim

    Step Command Remarks Enter system view. system-view ipv6 pim [ vpn-instance Enter IPv6 PIM view. vpn-instance-name ] Set the maximum size of By default, the maximum size of each join or prune a join or prune message is 8100 jp-pkt-size size message.

  • Page 330: Enabling Ipv6 Pim Nsr

    Step Command Remarks interface interface-type Enter interface view. interface-number Enable IPv6 PIM passive By default, IPv6 PIM passive ipv6 pim passive mode on the interface. mode is disabled. Enabling IPv6 PIM NSR Use this feature to avoid route flapping and forwarding interruption for IPv6 PIM when an active/standby switchover occurs.

  • Page 331: Ipv6 Pim Configuration Examples

    Task Command ipv6-source-address [ prefix-length ] | flags flag-value | fsm | incoming-interface interface-type interface-number | mode mode-type | outgoing-interface { exclude | include | match } interface-type interface-number ] * display ipv6 pim [ vpn-instance Display RP information in the IPv6 PIM-SM domain. vpn-instance-name ] rp-info [ ipv6-group-address ] Display statistics for IPv6 PIM packets.
  • Page 332 Table 20 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch C Vlan-int102 3001::1/64 Switch A Vlan-int103 1002::1/64 Switch D Vlan-int300 4001::1/64 Switch B Vlan-int200 2001::1/64 Switch D Vlan-int103 1002::2/64 Switch B Vlan-int101 2002::1/64 Switch D...
  • Page 333 [SwitchD] display ipv6 pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan300 FE80::A01:201:1 (local) Vlan103 FE80::A01:201:2 (local) Vlan101 FE80::A01:201:3 (local) Vlan102 FE80::A01:201:4 (local) # Display IPv6 PIM neighboring relationship on Switch D. [SwitchD] display ipv6 pim neighbor Total Number of Neighbors = 3 Neighbor Interface Uptime...

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

    [SwitchD] display ipv6 pim routing-table Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF0E::101) Protocol: pim-dm, Flag: LOC ACT UpTime: 00:02:19 Upstream interface: 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:02:19, Expires: - 2: Vlan-interface102...
  • Page 335 Figure 103 Network diagram Table 21 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int300 4001::1/64 Switch A Vlan-int101 1002::1/64 Switch D Vlan-int101 1002::2/64 Switch A Vlan-int102 1003::1/64 Switch D Vlan-int105 4002::1/64 Switch B...
  • Page 336 [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] ipv6 pim sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM on Switch B and Switch C in the same way Switch A is configured.

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

    Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64 Hash mask length: 126 Uptime: 00:11:18 Candidate BSR address: 1003::2 Priority: 64 Hash mask length: 126 # Display RP information on Switch A.
  • Page 338 Figure 104 Network diagram Table 22 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int105 3003::2/64 Switch A Vlan-int101 1002::1/64 Switch D Vlan-int108 6001::1/64 Switch B Vlan-int200 2001::1/64 Switch D Vlan-int107 6002::1/64 Switch B...
  • Page 339 Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 104. (Details not shown.) Configure OSPFv3 on all switches in the IPv6 PIM-SM domain. (Details not shown.) Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM: # On Switch A, enable IPv6 multicast routing globally.
  • Page 340 # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 as the boundaries of IPv6 admin-scoped zone 2. <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 multicast boundary scope 4 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] ipv6 multicast boundary scope 4 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 as the boundary of IPv6 admin-scoped zone 2.
  • Page 341 Elected BSR address: 1002::2 Priority: 64 Hash mask length: 126 Uptime: 00:04:54 Candidate BSR address: 1002::2 Priority: 64 Hash mask length: 126 # Display BSR information on Switch D. [SwitchD] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:25 Elected BSR address: 8001::1 Priority: 64 Hash mask length: 126...
  • Page 342 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF14::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF24::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF34::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local)

  • Page 343: Ipv6 Bidir-Pim Configuration Example

    RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 # Display RP information on Switch F. [SwitchF] display ipv6 pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address Priority HoldTime Uptime Expires 8001::1 (local) 00:10:28 00:02:31 IPv6 BIDIR-PIM configuration example Network requirements As shown in Figure...
  • Page 344 Device Interface IPv6 address Device Interface IPv6 address Switch C Vlan-int103 3001::1/64 Receiver 2 — 4001::2/64 Switch C Loop0 6001::1/128 Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 105. (Details not shown.) Configure OSPFv3 on the switches in the IPv6 BIDIR-PIM domain. (Details not shown.) Enable IPv6 multicast routing, IPv6 PIM-SM, IPv6 BIDIR-PIM, and MLD: # On Switch A, enable IPv6 multicast routing globally, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM.
  • Page 345 [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] ipv6 pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] ipv6 pim sm [SwitchC-Vlan-interface103] quit [SwitchC] interface loopback 0 [SwitchC-LoopBack0] ipv6 pim sm [SwitchC-LoopBack0] quit [SwitchC] ipv6 pim [SwitchC-pim6] bidir-pim enable # On Switch D, enable IPv6 multicast routing globally. <SwitchD>...
  • Page 346 RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Vlan200 01:24:09 FE80::200:5EFF: FE71:2801 (local) Vlan101 01:24:09 FE80::20F:E2FF: FE38:4E01 (local) Vlan102 Lose 01:23:12 FE80::20F:E2FF: FE15:5601 # Display the DF information of IPv6 BIDIR-PIM on Switch C. [SwitchC] display ipv6 pim df-info RP address: 6001::1 Interface State...

  • Page 347: Ipv6 Pim-Ssm Configuration Example

    2: Vlan-interface200 # Display information about the DF for IPv6 multicast forwarding on Switch C. [SwitchC] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 6001::1 Flags: 0x0 Uptime: 00:07:21 RPF interface: LoopBack0 List of 2 DF interfaces: 1: Vlan-interface102 2: Vlan-interface103 # Display information about the DF for IPv6 multicast forwarding on Switch D.
  • Page 348 Figure 106 Network diagram Table 24 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int300 4001::1/64 Switch A Vlan-int101 1002::1/64 Switch D Vlan-int101 1002::2/64 Switch A Vlan-int102 1003::1/64 Switch D Vlan-int105 4002::1/64 Switch B...
  • Page 349 [SwitchA-Vlan-interface100] mld version 2 [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim sm [SwitchA-Vlan-interface101] quit [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] ipv6 pim sm [SwitchA-Vlan-interface102] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM on Switch B and Switch C in the same way Switch A is configured.

  • Page 350: Troubleshooting Ipv6 Pim

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

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

    a router and the interface of the router's RPF neighbor operate in different IPv6 PIM modes, the multicast distribution tree cannot be correctly built. This causes abnormal multicast forwarding. • The same IPv6 PIM mode must run on the entire network. Otherwise, the multicast distribution tree cannot be correctly built, causing abnormal multicast forwarding.

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

    An RP cannot join an SPT in IPv6 PIM-SM Symptom An RPT cannot be correctly built, or an RP cannot join the SPT toward the IPv6 multicast source. Analysis Possible reasons for the problem might include the following: • RPs are the core of an IPv6 PIM-SM domain. An RP provides services for a specific IPv6 multicast group, and multiple RPs can coexist on a network.
  • Page 353 Use display ipv6 pim rp-info to verify that the RP information is correct on each router. Use display ipv6 pim neighbor to verify that IPv6 PIM neighboring relationship has been correctly established among the routers. If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 354: 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 355: 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 356: 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 357: 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 content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 358: Index

    Index multicast intra-AS MD-VPN configuration, 189 Numerics IP multicast model), 5 IGMP snooping message 802.1p priority, 26 assert MLD snooping 802.1p message priority, 229 IPv6 PIM-DM, 289 IPv6 PIM-SM, 294 PIM-DM, 92 IGMP snooping policy, 26 PIM-SM, 97 MLD snooping policy, 230 assigning address IPv6 multicast port-based VLAN user port, 252...
  • Page 359 protocols and standards, 104 RP configuration, 113 multicast MD-VPN PIM neighbor relationships, 175 RP discovery, 94 changing RP max, 114 multicast routing RPF route, 66 static RP configuration, 113 check bootstrap router. See BSR multicast RPF mechanism, 57 border checking IPv6 BIDIR-PIM domain border, 312 IPv6 multicast RPF check implementation, 261 IPv6 PIM-SM domain border, 307...
  • Page 360 IGMP snooping port feature, 20 IPv6 PIM-SM multicast source registration, 308 IGMP snooping querier, 23, 35 IPv6 PIM-SM non-scoped zone, 324 IGMP snooping simulated member host, 22 IPv6 PIM-SM RP, 305 IGMP snooping static port, 21, 32 IPv6 PIM-SM static RP, 305 IGMP SSM mapping, 82 IPv6 PIM-SM switchover to SPT, 308 IGMP SSM mapping configuration, 86...
  • Page 361 MSDP peer description, 151 PIM-SM non-scoped zone, 127 MSDP peering connection, 151 PIM-SM RP, 108 MSDP PIM-SM inter-domain multicast PIM-SM SPT switchover, 111 configuration, 156 PIM-SM static RP, 108 MSDP RPF static peer, 151 PIM-SSM, 117, 139 MSDP SA message cache, 155 PIM-SSM group range, 117 MSDP SA message content, 153 port-based IPv6 multicast VLAN, 257...
  • Page 362 troubleshooting multicast MD-VPN multicast routing, 65 default-MDT establishment, 214 multicast VLAN, 50 troubleshooting multicast VPN MVRF multicast VPN, 188 creation, 215 PIM, 123 describing PIM snooping, 40 MSDP peer description, 151 domain device IPv6 BIDIR-PIM domain border, 312 IGMPv3 host control, 76 IPv6 PIM-SM domain border, 307 multicast forwarding/GRE tunnel, 70 MSDP configuration, 146...
  • Page 363 IGMP snooping (IGMP-snooping view), 18 MLD snooping IPv6 multicast unknown data drop (VLAN), 231 IGMP snooping (VLAN view), 18 MLD snooping querier, 227 IGMP snooping drop unknown multicast data, 28 MSDP, 150 IGMP snooping drop unknown multicast data multicast routing, 62 (global), 28 multicast VPN data-group reuse logging, 186 IGMP snooping drop unknown multicast data...
  • Page 364 MLD snooping IPv6 multicast unknown data IPv6 PIM-SM multicast source drop, 231 registration, 292, 308 MLDv2 filter mode, 273 IPv6 PIM-SM non-scoped zone configuration, 324 MSDP SA message filtering configuration, 165 IPv6 PIM-SM RP, 305 PIM hello policy, 119 IPv6 PIM-SM RP discovery, 290 flooding IPv6 PIM-SM RPT building, 292 IPv6 PIM-DM SPT building, 287...
  • Page 365 PIM-DM graft retry timer, 106 IGMPv3. See IGMPv3 IP multicast VPN inter-AS MD-VPN configuration, 201 IPv6 multicast/GRE tunnel forwarding, 267 maintain, 83 multicast forwarding/GRE tunnel, 70 MLD basics configuration, 280 group MLD configuration, 271, 274, 280 IGMP snooping multicast group policy, 27 MLD SSM mapping configuration, 282 IP multicast MD-VPN default group address, 185...
  • Page 366 message 802.1p priority, 26 Group Management Protocol. Use IGMP message parameter configuration, 25 IP addressing message source IP address, 25 IGMP snooping message source IP address, 25 multicast group policy configuration, 27 IP multicast address, 5, 5 multicast group replacement, 29 IP multicast packet forwarding, 11 multicast groups on port max, 28 IP multicast...
  • Page 367 IGMP snooping report suppression, 28 MSDP peering connection, 151, 151 IGMP snooping source port filtering, 27 MSDP peering connection control, 152 IGMP snooping static port, 21 MSDP protocols and standards, 150 IGMP snooping static port configuration, 32 MSDP RPF static peer, 151 IGMP snooping version specification, 18 MSDP SA message cache, 155 IGMP SSM mapping configuration, 86...
  • Page 368 troubleshooting static route failure, 73 RP configuration, 310 unicast transmission technique, 1 RP discovery, 294 VPN application, 12 RP max, 311 VPN instance, 11 static RP, 310 VPN support, 11 zone relationships, 298 IPv4 IPv6 multicast Ethernet multicast MAC address, 8 forwarding boundary, 264 IGMP snooping multicast source port forwarding configuration, 261, 263, 264, 267...
  • Page 369 unicast subnet forwarding, 263 graft, 288 VLAN. See IPv6 multicast VLAN graft retry timer, 303 IPv6 multicast VLAN introduction, 287 configuration, 249, 251, 254 IPv6 PIM NSR enable, 320 displaying, 253 IPv6 PIM passive mode enable, 319 maintaining, 253 IPv6 PIM protocol relationships, 300 max forwarding entries, 253 neighbor discovery, 287 port -based, 250...
  • Page 370 IPv6 PIM-SM enable, 304 MAC addressing neighbor discovery, 299 Ethernet multicast MAC address, 8 protocols and standards, 301 IPv6 multicast MAC address static entry, 265 SPT building, 300 MLD snooping basic configuration, 220 IPv6 unicast MLD snooping configuration, 216, 220, 234 IPv6 multicast unicast subnet forwarding, 263 MLD snooping group policy+simulated joining configuration, 234...
  • Page 371 troubleshooting, 214 protocols and standards, 274 VPN instance IP multicast routing, 184 query/response parameter configuration, 276 member snooping. See MLD snooping IGMP snooping member port, 13 SSM mapping configuration, 279, 282 MLD snooping member port, 216 static group member configuration, 275 membership report troubleshooting, 285 IGMP snooping, 15...
  • Page 372 report suppression, 231 maintain, 156 simulated member host port, 225 mesh group, 152 static port configuration, 224, 235 peer, 146 troubleshooting, 241 peer description, 151 troubleshooting IPv6 multicast group peering connection, 151, 151 policy, 241 peering connection control, 152 troubleshooting MLD snooping Layer 2 PIM-SM inter-domain multicast configuration, 156 forwarding, 241 protocols and standards, 150...
  • Page 373 IPv6 PIM-SM, 289 PIM-SM source registration, 96 IPv6 PIM-SM administrative scoping PIM-SM SPT switchover, 97, 111 mechanism, 297 PIM-SSM, 102 IPv6 PIM-SM admin-scoped zone PIM-SSM configuration, 117, 139, 139 configuration, 327 PIM-SSM DR election, 102 IPv6 PIM-SM assert, 294 PIM-SSM group range, 117 IPv6 PIM-SM BSR, 306 PIM-SSM neighbor discovery, 102 IPv6 PIM-SM configuration, 304...
  • Page 374 static route, 59 VRF-to-VRF PE interconnectivity, 182 static route configuration, 62 multihop EBGP interconnectivity, 182 troubleshooting, 73 troubleshooting static route failure, 73 neighbor multicast VLAN multicast MD-VPN PIM neighbor configuration, 45, 47, 50 relationships, 175 displaying, 50 neighbor discovery IPv6 multicast VLAN. See IPv6 multicast BIDIR-PIM, 98 VLAN IPv6 BIDIR-PIM, 294...
  • Page 375 IPv6 multicast forwarding configuration, 264 multicast static route, 59 IPv6 multicast load splitting, 264 multicast VLAN max forwarding entries, 49 IPv6 multicast longest prefix match multicast VPN BGP MDT configuration, 186 principle, 264 multicast VPN default MDT characteristics, 177 IPv6 multicast MAC address static entry, 265 multicast VPN default MDT establishment in IPv6 multicast port-based VLAN user port PIM-DM network, 176...
  • Page 376 sub-VLAN-based multicast VLAN multicast forwarding configuration, 57, 61, 62, 66 configuration, 47 multicast forwarding/GRE tunnel, 70 network management multicast intra-AS MD-VPN configuration, 189 IGMP basic configuration, 84 multicast routing configuration, 57, 61, 62, 66 IGMP configuration, 78, 84 multicast routing RPF route change, 66 IGMP performance adjustment, 80 multicast routing RPF route creation, 68 IGMP snooping configuration, 13, 17, 30...
  • Page 377 packet common timer configuration (on interface), 122 IP multicast forwarding, 11 configuration, 91, 124 IP multicast MDT switchover, 181 display, 123 IPv6 PIM snooping DM. See PIM-DM configuration, 242, 243, 244 hello message option configuration (global), 120 multicast RPF check, 58 hello message option configuration (on multicast VPN data-MDT to default-MDT interface), 120...
  • Page 378 multicast VPN default MDT establishment in multicast VPN default MDT establishment in PIM-DM network, 176 PIM-DM network, 177 neighbor discovery, 91 neighbor discovery, 93 PIM BFD enable, 122 non-scoped zone configuration, 127 PIM configuration, 91 PIM BFD enable, 122 PIM NSR enable, 123 PIM configuration, 91 PIM passive mode enable, 123 PIM domain border, 110...
  • Page 379 IGMP snooping dynamic port aging MLD snooping static port configuration, 224, 235 timer, 14, 20 PIM snooping configuration, 39, 40, 41 IGMP snooping dynamic router port port-based multicast VLAN user port change, 23 assignment, 49 IGMP snooping fast leave processing, 22 port-based multicast VLAN user port attribute, 48 IGMP snooping group policy+simulated port-based IPv6 multicast VLAN...
  • Page 380 configuring IGMP snooping message source configuring IPv6 multicast routing, 263, 264, 267 IP address, 25 configuring IPv6 multicast sub-VLAN configuring IGMP snooping multicast group forwarding, 266 policy, 27 configuring IPv6 multicast sub-VLAN-based configuring IGMP snooping multicast group VLAN, 251 policy (global), 27 configuring IPv6 multicast VLAN, 251, 254 configuring IGMP snooping multicast group configuring IPv6 multicast/GRE tunnel...
  • Page 381 configuring MLD snooping general configuring multicast routing load splitting, 63 query/response parameters (global), 227 configuring multicast routing MAC address static configuring MLD snooping general entry, 64 query/response parameters (VLAN), 228 configuring multicast static route, 62 configuring MLD snooping group policy, 230 configuring multicast VLAN, 47, 50 configuring MLD snooping group policy configuring multicast VPN, 183, 189...
  • Page 382 configuring sub-VLAN-based multicast enabling IGMP snooping multicast group VLAN, 47, 50 replacement, 29 controlling MSDP peering connection, 152 enabling IGMP snooping multicast group replacement (global), 29 creating MD-VPN instance, 184 enabling IGMP snooping multicast group creating MSDP peering connection, 151 replacement (on port), 29 creating multicast routing RPF route, 68 enabling IGMP snooping querier, 23...
  • Page 383 enabling PIM-DM, 105 setting MLD snooping dynamic port aging timers, 223 enabling PIM-DM state-refresh, 105 setting MLD snooping dynamic port aging timers enabling PIM-SM, 107 (global), 223 enabling PIM-SSM, 107, 117 setting MLD snooping dynamic port aging timers forwarding multicast/GRE tunnel, 70 (VLAN), 224 maintaining IGMP, 83 setting MLD snooping forwarding entries...
  • Page 384 troubleshooting IPv6 PIM-SM RPT cannot be PIM join/prune message max size, 122 built, 342 PIM-DM SPT building, 91 troubleshooting MLD inconsistent member information, 286 querier troubleshooting MLD no member information, 285 IGMP snooping querier, 23 troubleshooting MLD snooping group IGMP snooping querier configuration, 35 filter, 241 IGMPv2 querier election, 75 troubleshooting MLD snooping Layer 2...
  • Page 385 router IGMP SSM mapping configuration, 86 IGMP snooping router port, 13 IGMP version specification, 78 MLD snooping router port, 216 IP multicast address, 5, 5 routing IP multicast inter-AS MD-VPN, 182 BIDIR-PIM, 97 IP multicast overview, 1 BIDIR-PIM Auto-RP listening, 114 IP multicast packet forwarding, 11 BIDIR-PIM bidirectional RPT building, 99 IP multicast transmission techniques, 1...
  • Page 386 IPv6 PIM-SM administrative scoping MSDP Anycast RP, 148 mechanism, 297 MSDP Anycast RP configuration, 161 IPv6 PIM-SM admin-scoped zone MSDP basics configuration, 150 configuration, 327 MSDP configuration, 146, 150, 156 IPv6 PIM-SM assert, 294 MSDP inter-domain multicast delivery, 147 IPv6 PIM-SM BSR, 306 MSDP mesh group, 152 IPv6 PIM-SM configuration, 304 MSDP peer, 146...
  • Page 387 PIM-SM Auto-RP listening, 109 IPv6 PIM-SM C-RP, 305 PIM-SM BSM semantic fragmentation, 110 IPv6 PIM-SM embedded RP, 291 PIM-SM BSR configuration, 109 IPv6 PIM-SM RP, 305 PIM-SM C-BSR, 109 IPv6 PIM-SM RP discovery, 290 PIM-SM configuration, 107 IPv6 PIM-SM RPT building, 292 PIM-SM C-RP, 108 IPv6 PIM-SM SPT switchover, 308 PIM-SM DR election, 93...
  • Page 388 troubleshooting IPv6 PIM-SM RPT cannot be multicast VLAN max forwarding entries, 49 built, 342 PIM join/prune message max size, 122 rule MSDP SA message policy, 154 IP multicast model, 5 shortest path tree. Use SPT snooping IGMP. See IGMP snooping MSDP SA message, 155 IPv6 PIM.
  • Page 389 MLD SSM mapping, 279 multicast forwarding across unicast subnets, 61 MLD SSM mapping configuration, 282 multicast forwarding configuration, 57, 61, 62, 66 state multicast forwarding/GRE tunnel, 70 IPv6 PIM-DM state refresh enable, 302 multicast routing configuration, 57, 61, 62, 66 IPv6 PIM-DM state refresh parameters, 303 multicast routing RPF route change, 66 MLDv2, 273...
  • Page 390 IP multicast VPN instance, 11 multicast forwarding across unicast subnets, 61 IP multicast VPN support, 11 multicast forwarding/GRE tunnel, 70 troubleshooting IGMP, 89 unicast IGMP inconsistent membership IP multicast transmission technique, 1 information, 89 multicast forwarding across unicast subnets, 61 IGMP no membership information on routing table, 57 router, 89...
  • Page 391 IGMP snooping version specification, 18 IGMP support, 77 IP multicast MLD snooping querier IP multicast application, 12 enable, 227, 227 IP multicast instance, 11 IPv6 BIDIR-PIM configuration, 333 IP multicast support, 11 IPv6 multicast super VLAN/sub-VLAN IP multicast VPN. See multicast VPN forwarding, 266 IPv6 PIM support, 301 IPv6 multicast VLAN.

Table of Contents