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

Advertising

   Also See for HP FlexFabric 5950 series

   Summary of Contents for HP FlexFabric 5950 series

  • Page 1

    HPE FlexFabric 5950 Switch Series IP Multicast Configuration Guide Part number: 5200-2212a Software version: Release 6123 and later Document version: 6W101-20170120...

  • Page 2

    © Copyright 2017 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 IP multicast architecture ·············································································································· 5 Multicast addresses ·············································································································...

  • Page 4: Table Of Contents

    IGMP snooping querier configuration example (for VLANs) ························································ 39 IGMP snooping proxying configuration example (for VLANs) ······················································ 42 IGMP snooping configuration example (for VSIs) ····································································· 43 IGMP snooping configuration example (for VXLANs) ································································ 49 Troubleshooting IGMP snooping ································································································· 54 Layer 2 multicast forwarding cannot function ··········································································· 54 Multicast group policy does not work ·····················································································...

  • Page 5: Table Of Contents

    IGMP SSM mapping ·········································································································· 94 IGMP proxying ·················································································································· 95 IGMP support for VPNs ······································································································ 96 Protocols and standards ····································································································· 96 IGMP configuration task list ········································································································ 97 Configuring basic IGMP features ································································································· 97 Enabling IGMP ················································································································· 97 Specifying an IGMP version ································································································· 98 Configuring a static group member ························································································...

  • Page 6: Table Of Contents

    Configuring PIM-SSM ············································································································· 143 PIM-SSM configuration task list ·························································································· 143 Configuration prerequisites ································································································ 143 Enabling PIM-SM ············································································································ 143 Configuring the SSM group range ······················································································· 143 Configuring common PIM features ····························································································· 144 Configuration task list ······································································································· 144 Configuration prerequisites ································································································ 144 Configuring a multicast source policy ···················································································...

  • Page 7: Table Of Contents

    MSDP peers stay in disabled state ······················································································ 201 No SA entries exist in the router's SA message cache ····························································· 201 No exchange of locally registered (S, G) entries between RPs ·················································· 202 Configuring multicast VPN ····························································· 203 Overview ······························································································································ 203 MD VPN overview ···········································································································...

  • Page 8: Table Of Contents

    Enabling the MLD snooping querier ····················································································· 298 Configuring parameters for MLD general queries and responses ··············································· 298 Enabling MLD snooping proxying ······························································································ 299 Configuring parameters for MLD messages ················································································· 299 Configuration prerequisites ································································································ 299 Configuring source IPv6 addresses for MLD messages ··························································· 300 Setting the 802.1p priority for MLD messages ········································································...

  • Page 9: Table Of Contents

    Specifying the longest prefix match principle ········································································· 350 Configuring IPv6 multicast load splitting ··············································································· 350 Configuring an IPv6 multicast forwarding boundary ································································· 350 Enabling IPv6 multicast forwarding between sub-VLANs of a super VLAN ··································· 351 Displaying and maintaining IPv6 multicast routing and forwarding ···················································· 351 IPv6 multicast routing and forwarding configuration examples ·························································...

  • Page 10: Table Of Contents

    Configuration prerequisites ································································································ 394 Enabling IPv6 PIM-SM ····································································································· 394 Configuring an RP ··········································································································· 395 Configuring a BSR ··········································································································· 397 Configuring IPv6 multicast source registration ······································································· 399 Configuring the switchover to SPT ······················································································ 400 Configuring IPv6 BIDIR-PIM ····································································································· 400 IPv6 BIDIR-PIM configuration task list ·················································································· 400 Configuration prerequisites ································································································...

  • Page 11: Multicast Overview

    Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load.

  • Page 12

    Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission Host A Receiver Host B Source Host C Receiver Host D A network segment Receiver Packets for all hosts Host E...

  • Page 13: Multicast Features

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

  • Page 14: Common Notations In Multicast

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

  • Page 15: Ip Multicast Architecture

    multicast sources. In this model, receivers do not know the positions of the multicast sources in advance. SFM model The SFM model is derived from the ASM model. To a multicast source, the two models appear to have the same multicast membership architecture. The SFM model functionally extends the ASM model.

  • Page 16

    group addresses. A packet destined for an address in this block will not be forwarded beyond the local subnet regardless of the TTL value in the IP header. Globally scoped group addresses. This block includes the following types of designated group addresses: 224.0.1.0 to 238.255.255.255 •...

  • Page 17

    Figure 4 IPv6 multicast format 0xFF Flags Scope Group ID (112 bits) The following describes the fields of an IPv6 multicast address: 0xFF—The most significant eight bits are 11111111.  Flags—The Flags field contains four bits.  Figure 5 Flags field format 0 R P T Table 4 Flags field description Description...

  • Page 18: Multicast Protocols

    Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast  group in the scope that the Scope field defines. Ethernet multicast MAC addresses • IPv4 multicast MAC addresses: As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E.

  • Page 19

    Layer 2 multicast protocols—IGMP snooping, MLD snooping, PIM snooping, IPv6 PIM snooping, multicast VLAN, and IPv6 multicast VLAN. • IPv4 and IPv6 multicast protocols: For IPv4 networks—IGMP snooping, PIM snooping, multicast VLAN, IGMP, PIM, MSDP,  and MBGP. For IPv6 networks—MLD snooping, IPv6 PIM snooping, IPv6 multicast VLAN, MLD, IPv6 ...

  • Page 20: Multicast Packet Forwarding Mechanism

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

  • Page 21: Multicast Support For Vpns

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

  • Page 22: Multicast Application In Vpns

    Multicast application in VPNs A PE device that supports multicast for VPNs performs the following operations: • Maintains an independent set of multicast forwarding mechanisms for each VPN, including the multicast protocols, PIM neighbor information, and multicast routing table. In a VPN, the device forwards multicast data based on the forwarding table or routing table for that VPN.

  • Page 23: Configuring Igmp Snooping

    Configuring IGMP snooping Overview IGMP snooping runs on a Layer 2 device as a multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from IGMP packets that are exchanged between the hosts and the router. As shown in Figure 11, when IGMP snooping is not enabled, the Layer 2 switch floods multicast...

  • Page 24

    Figure 12 IGMP snooping ports Receiver Router A Switch A HGE1/0/1 HGE1/0/2 Host A HGE1/0/3 Host B Receiver HGE1/0/1 Source HGE1/0/2 Host C Switch B Router port Member port Multicast packets Host D Router ports On an IGMP snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.

  • Page 25: How Igmp Snooping Works

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

  • Page 26: Igmp Snooping Proxying

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

  • Page 27: Protocols And Standards

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

  • Page 28: Igmp Configuration Task List For Vsis

    Configuring the IGMP snooping querier: • (Optional.) Enabling the IGMP snooping querier • (Optional.) Configuring parameters for IGMP general queries and responses (Optional.) Enabling IGMP snooping proxying Configuring parameters for IGMP messages: • (Optional.) Configuring source IP addresses for IGMP messages •...

  • Page 29: Configuring Basic Igmp Snooping Features

    Configuring basic IGMP snooping features Before you configure basic IGMP snooping features, complete the following tasks: • Configure VLANs or VSIs. • Determine the IGMP snooping version. • Determine the maximum number of IGMP snooping forwarding entries. • Determine the IGMP last member query interval. Enabling IGMP snooping When you enable IGMP snooping, follow these restrictions and guidelines: •...

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

    • IGMPv3 snooping processes IGMPv1, IGMPv2, and IGMPv3 messages. If you change IGMPv3 snooping to IGMPv2 snooping, the device performs the following actions: • Clears all IGMP snooping forwarding entries that are dynamically added. • Keeps static IGMPv3 snooping forwarding entries (*, G). •...

  • Page 31: Configuring Static Multicast Mac Address Entries

    Configuring static multicast MAC address entries In Layer 2 multicast, multicast MAC address entries can be dynamically created through Layer 2 multicast protocols (such as IGMP snooping). 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 32: Configuring Igmp Snooping Port Features

    VSI-specific configuration takes priority over the global configuration. For a VLAN, the VLAN-specific configuration takes priority over the global configuration. 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 last-member-query-interval interva The default setting is 1 query interval globally.

  • Page 33: Configuring Static Ports

    Setting the aging timers for dynamic ports globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the aging timer for The default setting is 260 dynamic router ports router-aging-time seconds seconds. globally. Set the global aging timer for The default setting is 260 dynamic member ports host-aging-time seconds...

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

    igmp-snooping static-router-port vlan vlan 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 35: Disabling A Port From Becoming A Dynamic Router Port

    Enabling fast-leave processing on a port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface- interface view or Layer 2 number aggregate interface view. Enable fast-leave processing igmp-snooping fast-leave [ By default, fast-leave processing on the port. vlan vlan-list ] is disabled on a port.

  • Page 36: Enabling The Igmp Snooping Querier

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

  • Page 37: Enabling Igmp Snooping Proxying

    Configuring parameters for IGMP general queries and responses globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Set the maximum response time for IGMP general max-response-time seconds The default setting is 10 seconds. queries. Configuring parameters for IGMP general queries and responses in a VLAN or VSI Step Command Remarks...

  • Page 38: Configuring Source Ip Addresses For Igmp Messages

    • Determine the 802.1p priority of IGMP messages. Configuring source IP addresses for IGMP messages The IGMP snooping querier might send IGMP general queries with the source IP address 0.0.0.0. The port that receives such queries will not be maintained as a dynamic router port. This might prevent the associated dynamic IGMP snooping forwarding entry from being correctly created at the data link layer and eventually cause multicast traffic forwarding failures.

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

    Configuring the source IP address for IGMP messages in a VSI Step Command Remarks Enter system view. system-view Enter VSI view. vsi vsi-name By default, the source IP address of IGMP general queries is the IP Configure the source IP igmp-snooping address of the gateway interface for a address for IGMP general...

  • Page 40: Configuring Igmp Snooping Policies

    For IGMP packets created by the device, the 802.1p priority is 0. For IGMP packets to be forwarded, the device does not change the 802.1p priority. Setting the 802.1p priority for IGMP messages in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view.

  • Page 41: Enabling Multicast Source Port Filtering

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

  • Page 42: Enabling Igmp Report Suppression

    • Enter VLAN view: vlan vlan-id Enter VLAN view or VSI • view. Enter VSI view: vsi vsi-name By default, dropping unknown Enable dropping unknown multicast data is disabled, and multicast data for the VLAN igmp-snooping drop-unknown unknown multicast data is or VSI.

  • Page 43: Enabling Multicast Group Replacement

    Enabling multicast group replacement This feature enables the device to replace an existing group with a newly joined group when the number of groups exceeds the upper limit. This feature is typically used in the channel switching application. Without this feature, the device discards IGMP reports for new groups, and the user cannot change to the new channel.

  • Page 44: Displaying And Maintaining Igmp Snooping

    Enter VLAN view. vlan vlan-id Enable host tracking for the By default, host tracking is igmp-snooping host-tracking VLAN. disabled for a VLAN. Displaying and maintaining IGMP snooping Execute display commands in any view and reset commands in user view. Task Command display igmp-snooping [ global | vlan vlan-id | vsi vsi-name ] Display IGMP snooping status.

  • Page 45: Igmp Snooping Configuration Examples

    IGMP snooping. IGMP snooping configuration examples Group policy and simulated joining configuration example(for VLANs) Network requirements As shown in Figure 14, Router A runs IGMPv2 and acts as the IGMP querier. Switch A runs IGMPv2 snooping. Configure a multicast group policy and simulated joining to meet the following requirements: •...

  • Page 46

    [RouterA] interface hundredgige 1/0/2 [RouterA-HundredGigE1/0/2] pim dm [RouterA-HundredGigE1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100.

  • Page 47: Static Port Configuration Example (for Vlans)

    Static port configuration example (for VLANs) Network requirements As shown in Figure • Router A runs IGMPv2 and acts as the IGMP querier. Switch A, Switch B, and Switch C run IGMPv2 snooping. • Host A and host C are permanent receivers of multicast group 224.1.1.1. Configure static ports to meet the following requirements: •...

  • Page 48

    [RouterA-HundredGigE1/0/1] igmp enable [RouterA-HundredGigE1/0/1] quit # Enable PIM-DM on HundredGigE 1/0/2. [RouterA] interface hundredgige 1/0/2 [RouterA-HundredGigE1/0/2] pim dm [RouterA-HundredGigE1/0/2] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/3 # Enable IGMP snooping for VLAN 100.

  • Page 49: Igmp Snooping Querier Configuration Example (for Vlans)

    [SwitchC-HundredGigE1/0/3] quit [SwitchC] interface hundredgige 1/0/5 [SwitchC-HundredGigE1/0/5] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-HundredGigE1/0/5] quit Verifying the configuration # Display static router port information for VLAN 100 on Switch A. [SwitchA] display igmp-snooping static-router-port vlan 100 VLAN 100: Router ports (1 in total): HGE1/0/3 The output shows that HundredGigE 1/0/3 on Switch A has become a static router port.

  • Page 50

    Figure 16 Network diagram Source 1 Source 2 VLAN 100 192.168.1.10/24 192.168.1.20/24 Receiver Receiver HGE1/0/2 HGE1/0/2 HGE1/0/1 HGE1/0/3 HGE1/0/3 HGE1/0/1 Host A Host B HGE1/0/4 Switch A Switch B Querier Receiver Receiver HGE1/0/2 HGE1/0/1 HGE1/0/2 HGE1/0/3 HGE1/0/1 Host D Host C Switch D Switch C Configuration procedure...

  • Page 51

    [SwitchB-vlan100] igmp-snooping enable [SwitchB-vlan100] igmp-snooping drop-unknown [SwitchB-vlan100] quit Configure Switch C: # Enable IGMP snooping globally. <SwitchC> system-view [SwitchC] igmp-snooping [SwitchC-igmp-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/3 to the VLAN. [SwitchC] vlan 100 [SwitchC-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/3 # Enable IGMP snooping, and enable dropping unknown multicast data for VLAN 100.

  • Page 52: Igmp Snooping Proxying Configuration Example (for Vlans)

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

  • Page 53: Igmp Snooping Configuration Example (for Vsis)

    # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable IGMP snooping and IGMP snooping proxying for the VLAN. [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] igmp-snooping proxy enable [SwitchA-vlan100] quit Verifying the configuration # Send an IGMP report to join multicast group 224.1.1.1 from Host A and Host B.

  • Page 54

    • In VLAN 100, Source in Site 1, Host A in Site 2, and Host B in Site 3 communicate with CE 1, CE 2, and CE 3, respectively. Configure the devices so that Host A and Host B can receive multicast data from Source. Figure 18 Network diagram Loop0 Site 2 of VPN a...

  • Page 55

    [CE1-HundredGigE1/0/1] quit # In VLAN 100, enable the IGMP snooping querier. [CE1-vlan100] igmp-snooping querier # In VLAN 100, specify 192.168.1.100 as the source IP address of IGMP general queries and IGMP group-specific queries. [CE1-vlan100] igmp-snooping general-query source-ip 192.168.1.100 [CE1-vlan100] igmp-snooping special-query source-ip 192.168.1.100 Configure CE 2: # Enable IGMP snooping globally.

  • Page 56

    [PE1] interface vlan-interface 101 [PE1-Vlan-interface101] mpls enable [PE1-Vlan-interface101] mpls ldp enable [PE1-Vlan-interface101] quit # Enable MPLS and LDP on VLAN-interface 102. [PE1] interface vlan-interface 102 [PE1-Vlan-interface102] mpls enable [PE1-Vlan-interface102] mpls ldp enable [PE1-Vlan-interface102] quit # Create a VSI named aaa, and specify the VSI to establish PWs statically. [PE1] vsi aaa [PE1-vsi-aaa] pwsignaling static # Configure PWs for VSI aaa.

  • Page 57

    [PE2] interface vlan-interface 103 [PE2-Vlan-interface103] mpls enable [PE2-Vlan-interface103] mpls ldp enable [PE2-Vlan-interface103] quit # Create a VSI named aaa, and specify the VSI to establish PWs statically. [PE2] vsi aaa [PE2-vsi-aaa] pwsignaling static # Configure PWs for VSI aaa. [PE2-vsi-aaa-static] peer 1.1.1.1 pw-id 3 in-label 100 out-label 100 [PE2-vsi-aaa-static-1.1.1.1-3] quit [PE2-vsi-aaa-static] peer 3.3.3.3 pw-id 3 in-label 300 out-label 300 [PE2-vsi-aaa-static-3.3.3.3-3] quit...

  • Page 58

    [PE3] vsi aaa [PE3-vsi-aaa] pwsignaling static # Configure PWs for VSI aaa. [PE3-vsi-aaa-static] peer 1.1.1.1 pw-id 3 in-label 200 out-label 200 [PE3-vsi-aaa-static-1.1.1.1-3] quit [PE3-vsi-aaa-static] peer 2.2.2.2 pw-id 3 in-label 300 out-label 300 [PE3-vsi-aaa-static-2.2.2.2-3] quit [PE3-vsi-aaa-static] quit [PE3-vsi-aaa] quit # Bind HundredGigE 1/0/1 to VSI aaa. [PE3] interface hundredgige 1/0/1 [PE3-HundredGigE1/0/1] service-instance 1 [PE3-HundredGigE1/0/1-srv1] encapsulation s-vid 5...

  • Page 59: Igmp Snooping Configuration Example (for Vxlans)

    [PE2] display igmp-snooping group vsi aaa verbose Total 1 entries. VSI aaa: Total 1 entries. (0.0.0.0, 225.0.0.1) Attribute: global port FSM information: normal Host slots (0 in total): Host ports (1 in total): NPW (Link ID 8) (00:02:07) VLAN pairs (1 in total): Outer VLAN 100 Inner VLAN 0 (00:02:07)

  • Page 60

    • VXLAN 10 uses the unicast mode for flood traffic. Configure IGMP snooping on the switches to implement Layer 2 multicast forwarding and reduce the burden of replicating known multicast traffic for VTEPs in VXLAN 10. Figure 19 Network diagram Loop0 Loop0 Transport network...

  • Page 61

    [SwitchA] vsi vpna [SwitchA-vsi-vpna] igmp-snooping enable [SwitchA-vsi-vpna] igmp-snooping drop-unknown [SwitchA-vsi-vpna] quit # Assign an IP address to Loopback 0. This IP address will be used as the source address of the VXLAN tunnels to Switch B and Switch C. [SwitchA] interface loopback 0 [SwitchA-Loopback0] ip address 1.1.1.1 255.255.255.255 [SwitchA-Loopback0] quit # Create a VXLAN tunnel to Switch B.

  • Page 62

    [SwitchB] vsi vpna [SwitchB-vsi-vpna] vxlan 10 [SwitchB-vsi-vpna-vxlan-10] quit [SwitchB-vsi-vpna] quit # Enable IGMP snooping globally. [SwitchB] igmp-snooping [SwitchB -igmp-snooping] quit # Enable IGMP snooping and dropping unknown multicast data packets for VSI vpna. [SwitchB] vsi vpna [SwitchB-vsi-vpna] igmp-snooping enable [SwitchB-vsi-vpna] igmp-snooping drop-unknown [SwitchB-vsi-vpna] quit # Assign an IP address to Loopback 0.

  • Page 63

    Configure Switch C: # Enable L2VPN. <SwitchC> system-view [SwitchC] l2vpn enable # Enable Layer 2 forwarding for VXLANs. [SwitchC] undo vxlan ip-forwarding # Create a VSI named vpna, and create VXLAN 10. [SwitchC] vsi vpna [SwitchC-vsi-vpna] vxlan 10 [SwitchC-vsi-vpna-vxlan-10] quit [SwitchC-vsi-vpna] quit # Enable IGMP snooping globally.

  • Page 64: Troubleshooting Igmp Snooping

    [SwitchC-vsi-vpna] vxlan 10 [SwitchC-vsi-vpna-vxlan-10] tunnel 1 [SwitchC-vsi-vpna-vxlan-10] tunnel 3 [SwitchC-vsi-vpna-vxlan-10] quit [SwitchC-vsi-vpna] quit # On HundredGigE 1/0/1, create Ethernet service instance 1000 to match VLAN 2. [SwitchC] interface hundredgige 1/0/1 [SwitchC-HundredGigE1/0/1] service-instance 1000 [SwitchC-HundredGigE1/0/1-srv1000] encapsulation s-vid 2 # Map Ethernet service instance 1000 to VSI vpna. [SwitchC-HundredGigE1/0/1-srv1000] xconnect vsi vpna [SwitchC-HundredGigE1/0/1-srv1000] quit [SwitchC-HundredGigE1/0/1] quit...

  • Page 65: Multicast Group Policy Does Not Work

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

  • Page 66: 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 20 Multicast packet transmission without or with PIM snooping Multicast packet transmission Multicast packet transmission when...

  • Page 67

    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: d.

  • Page 68: Displaying And Maintaining Pim Snooping

    switchover. The default setting is 210 seconds. (Optional.) Set the aging time for global downstream A global downstream port or a global pim-snooping ports and global router ports router port is a Layer 2 aggregate graceful-restart on the master device after a interface, AC, N-PW, or U-PW that join-aging-time seconds master/subordinate...

  • Page 69: Configuration Procedure

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

  • Page 70

    [RouterB-HundredGigE1/0/1] pim sm [RouterB-HundredGigE1/0/1] quit [RouterB] interface hundredgige 1/0/2 [RouterB-HundredGigE1/0/2] pim sm [RouterB-HundredGigE1/0/2] quit # Set the maximum size of a join or prune message to 1400 bytes. [RouterB] pim [RouterB-pim] jp-pkt-size 1400 Configure Router C: # Enable IP multicast routing. <RouterC>...

  • Page 71: Verifying The Configuration

    [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable IGMP snooping and PIM snooping for VLAN 100. [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] pim-snooping enable [SwitchA-vlan100] quit Verifying the configuration # On Switch A, display PIM snooping neighbor information for VLAN 100. [SwitchA] display pim-snooping neighbor vlan 100 Total 4 neighbors.

  • Page 72: Troubleshooting Pim Snooping

    • Switch A will forward the multicast data intended for multicast group 224.1.1.1 only to Router C. • Switch A will forward the multicast data intended for multicast group 225.1.1.1 only to Router D. Troubleshooting PIM snooping PIM snooping does not work on a Layer 2 device Symptom PIM snooping does not work on a Layer 2 device.

  • Page 73: Configuring Multicast Vlans

    Configuring multicast VLANs Overview As shown in Figure 22, Host A, Host B, and Host C are in three different VLANs and the same multicast group. When Switch A (Layer 3 device) receives multicast data for that group, it sends three copies of the multicast data to Switch B (Layer 2 device).

  • Page 74

    Figure 23 Sub-VLAN-based multicast VLAN Multicast packets VLAN 10 (Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Source Switch A Switch B IGMP querier VLAN 4 Receiver Host C IGMP snooping manages router ports in the multicast VLAN and member ports in each sub-VLAN. When Switch A receives multicast data from the multicast source, it sends only one copy of the multicast data to the multicast VLAN on Switch B.

  • Page 75: Multicast Vlan Configuration Task List

    Forward transmission and reverse transmission The device supports both forward transmission and reverse transmission for multicast VLAN. In forward transmission, multicast receivers are connected to downstream devices of a Layer 2 device. The Layer 2 device forwards multicast traffic only from the upstream Layer 3 device to downstream devices that are in sub-VLANs or have member ports.

  • Page 76

    • Make sure that no trunk port exists both in a multicast VLAN and a sub-VLAN of the multicast VLAN. Configuration procedure To configure a sub-VLAN-based multicast VLAN: Step Command Remarks Enter system view. system-view Configure a VLAN as a By default, a VLAN is not a multicast VLAN and enter its multicast-vlan vlan-id...

  • Page 77: Assigning User Ports To A Multicast Vlan

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

  • Page 78: Displaying And Maintaining Multicast Vlans

    Set the maximum number of By default, the maximum number multicast VLAN forwarding multicast-vlan entry-limit limit of multicast VLAN forwarding entries. entries is 4000. Displaying and maintaining multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about multicast...

  • Page 79

    Figure 25 Network diagram Source IGMP querier HGE1/0/2 Vlan-int20 Switch A 1.1.1.2/24 HGE1/0/1 1.1.1.1/24 Vlan-int10 10.110.1.1/24 HGE1/0/1 Switch B HGE1/0/2 HGE1/0/4 HGE1/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 80

    Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 2, assign HundredGigE 1/0/2 to the VLAN, and enable IGMP snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port hundredgige 1/0/2 [SwitchB-vlan2] igmp-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign HundredGigE 1/0/3 to the VLAN, and enable IGMP snooping in the VLAN.

  • Page 81: Port-based Multicast Vlan Configuration Example

    [SwitchB] display multicast-vlan group Total 1 entries. Multicast VLAN 10: Total 1 entries. (0.0.0.0, 224.1.1.1) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that multicast group 224.1.1.1 belongs to multicast VLAN 10. Multicast VLAN 10 contains sub-VLANs VLAN 2 through VLAN 4.

  • Page 82

    [SwitchA] multicast routing [SwitchA-mrib] quit # Create VLAN 20, and assign HundredGigE 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port hundredgige 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 83

    # Assign HundredGigE 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-HundredGigE1/0/2] port hybrid vlan 2 untagged [SwitchB-HundredGigE1/0/2] port hybrid vlan 10 untagged [SwitchB-HundredGigE1/0/2] quit # Configure HundredGigE 1/0/3 as a hybrid port, and configure VLAN 3 as the PVID of the hybrid port.

  • Page 84

    (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (3 in total): HGE1/0/2 (00:03:23) HGE1/0/3 (00:04:07) HGE1/0/4 (00:04:16) The output shows that IGMP snooping maintains the user ports in the multicast VLAN (VLAN 10). Switch B will forward the multicast data of VLAN 10 through these user ports.

  • Page 85: 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 86

    RPF check implementation in multicast Implementing an RPF check on each received multicast packet brings a big burden to the router. The use of a multicast forwarding table is the solution to this issue. When the router creates a multicast forwarding entry for an (S, G) packet, it sets the RPF interface of the packet as the incoming interface of the (S, G) entry.

  • Page 87: Static Multicast Routes

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

  • Page 88: Multicast Forwarding Across Unicast Subnets

    Figure 29 Creating an RPF route Static multicast routing table on Device C OSPF domain Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 Vlan-int10 1.1.1.1/24 Receiver Device D Static multicast routing table on Device D Vlan-int20 Source/Mask Interface RPF neighbor/Mask 2.2.2.1/24 192.168.0.0/24 Vlan-int20 2.2.2.2/24 Source RIP domain...

  • Page 89: Configuration Task List

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

  • Page 90

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

  • Page 91: Configuring Multicast Load Splitting

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

  • Page 92: Displaying And Maintaining Multicast Routing And Forwarding

    interface view. Enable By default, multicast multicast data forwarding cannot be between forwarded sub-VLANs multicast forwarding supervlan community between that are sub-VLANs that associated are associated with a super with a super VLAN. VLAN. Clear all multicast forwarding reset entries with multicast [ vpn-instance vpn-instance-name ] forwarding-table the super { { source-address [ mask { mask-length | mask } ] | group-address...

  • Page 93: Configuration Examples

    display multicast Display information about the DF list in [ vpn-instance vpn-instance-name ] forwarding-table df-list the multicast forwarding table. [ group-address ] [ verbose ] [ slot slot-number ] display multicast [ vpn-instance vpn-instance-name ] routing-table [ source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] Display multicast routing entries.

  • Page 94

    Figure 31 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 Static multicast route Configuration procedure Assign an IP address and subnet mask for each interface, as shown in Figure 31.

  • Page 95: Creating An Rpf Route

    [SwitchA-Vlan-interface200] quit [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 RPF information for Source on Switch B.

  • Page 96

    Figure 32 Network diagram PIM-DM OSPF domain Switch A Switch B Switch C Vlan-int102 Vlan-int102 Vlan-int101 30.1.1.2/24 30.1.1.1/24 20.1.1.1/24 Vlan-int101 20.1.1.2/24 Vlan-int300 Vlan-int200 Vlan-int100 50.1.1.1/24 40.1.1.1/24 10.1.1.1/24 Source 2 Source 1 Receiver 50.1.1.100/24 40.1.1.100/24 10.1.1.100/24 Static multicast route Configuration procedure Assign an IP address and subnet mask for each interface, as shown in Figure 32.

  • Page 97: Multicast Forwarding Over A Gre Tunnel

    [SwitchB] display multicast rpf-info 50.1.1.100 [SwitchC] display multicast rpf-info 50.1.1.100 No 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 and specify Switch A as its RPF neighbor on the route to Source 2.

  • Page 98

    Figure 33 Network diagram Multicast router Unicast router Multicast router Switch A Switch B Switch C Vlan-int101 Vlan-int101 Vlan-int102 Vlan-int102 20.1.1.1/24 20.1.1.2/24 30.1.1.1/24 30.1.1.2/24 HGE1/0/3 HGE1/0/3 Vlan-int100 Vlan-int200 GRE tunnel 10.1.1.1/24 40.1.1.1/24 Tunnel2 Tunnel2 50.1.1.1/24 50.1.1.2/24 Source Receiver Member port of a service loopback group 10.1.1.100/24 40.1.1.100/24 Configuration procedure...

  • Page 99

    [SwitchC-Tunnel2] destination 20.1.1.1 [SwitchC-Tunnel2] quit Enable IP multicast routing, PIM-DM, and IGMP: # On Switch A, enable multicast routing. [SwitchA] multicast routing [SwitchA-mrib] quit # Enable PIM-DM on each interface. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim dm [SwitchA-Vlan-interface101] quit [SwitchA] interface tunnel 2...

  • Page 100: 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: Tunnel2 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 101: Configuring Igmp

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

  • Page 102: Igmpv2 Enhancements

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

  • Page 103: Igmpv3 Enhancements

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

  • Page 104: Igmp Ssm Mapping

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

  • Page 105: Igmp Proxying

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

  • Page 106: Igmp Support For Vpns

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

  • Page 107: 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 108: Specifying An Igmp Version

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

  • Page 109: Adjusting Igmp Performance

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no IGMP multicast igmp group policy exists on an Configure a multicast group group-policy ipv4-acl-number [ v interface. Hosts attached to the policy. ersion-number ] interface can join any multicast groups.

  • Page 110

    • To avoid frequent IGMP querier changes, set the IGMP other querier present timer greater than the IGMP general query interval. In addition, configure the same IGMP other querier present timer for all IGMP routers on the same subnet. • To avoid mistakenly deleting multicast receivers, set the IGMP general query interval greater than the maximum response time for IGMP general queries.

  • Page 111: Enabling Fast-leave Processing

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

  • Page 112: Configuring Igmp Ssm Mappings

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

  • Page 113: Enabling Multicast Forwarding On A Non-querier Interface

    you must enable multicast forwarding on the interface. For more information, see "Enabling multicast forwarding on a non-querier interface." To enable IGMP proxying: Step Command Remarks Enter system view. system-view multicast routing Enable IP multicast routing By default, IP multicast routing is [ vpn-instance vpn-instance-nam and enter MRIB view.

  • Page 114: Enabling Igmp Nsr

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

  • Page 115: Igmp Configuration Examples

    IGMP configuration examples This section provides examples of configuring IGMP on switches. 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 116

    # Enable IGMP on VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] quit # Enable PIM-DM on VLAN-interface 101. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim dm [SwitchA-Vlan-interface101] quit # On Switch B, enable IP multicast routing. <SwitchB> system-view [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on VLAN-interface 200.

  • Page 117: Igmp Ssm Mapping Configuration Example

    Other querier present time for IGMP: 255s Maximum query response time for IGMP: 10s Querier for IGMP: 10.110.2.1 (This router) IGMP groups reported in total: 1 IGMP SSM mapping configuration example Network requirements As shown in Figure • OSPF runs on the network. •...

  • Page 118

    Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 39. (Details not shown.) Configure OSPF on the switches in the PIM-SM domain. (Details not shown.) Enable IP multicast routing, PIM-SM, and IGMP: # On Switch D, enable IP multicast routing. <SwitchD>...

  • Page 119

    [SwitchD-pim] ssm-policy 2000 [SwitchD-pim] quit # Configure the SSM group range on Switch A, Switch B, and Switch C in the same way Switch D is configured. (Details not shown.) Configure IGMP SSM mappings on Switch D. [SwitchD] igmp [SwitchD-igmp] ssm-mapping 133.133.1.1 2000 [SwitchD-igmp] ssm-mapping 133.133.3.1 2000 [SwitchD-igmp] quit Verifying the configuration...

  • Page 120: Igmp Proxying Configuration Example

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

  • Page 121: Troubleshooting Igmp

    [SwitchB-mrib] quit # Enable IGMP proxying on VLAN-interface 100. [SwitchB] interface vlan-interface 100 [SwitchB-Vlan-interface100] igmp proxy enable [SwitchB-Vlan-interface100] quit # Enable IGMP on VLAN-interface 200. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit Verifying the configuration # Display multicast group membership information maintained by the IGMP proxy on Switch B. [SwitchB] display igmp proxy group IGMP proxy group records in total: 1 Vlan-interface100(192.168.1.2):...

  • Page 122

    Use the display current-configuration command to verify the IGMP information on the interfaces. Make sure the routers on the subnet have the same IGMP settings on their interfaces. Use the display igmp interface command on all routers on the same subnet to verify the IGMP-related timer settings.

  • Page 123: 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 124

    this way, the upstream stream node stops forwarding subsequent packets addressed to that multicast group down to this node. NOTE: An (S, G) entry contains a multicast source address S, a multicast group address G, an outgoing interface list, and an incoming interface. A prune process is initiated by a leaf router.

  • Page 125: Pim-sm Overview

    Figure 42 Assert mechanism Router A Router B Ethernet Assert message Multicast packets Receiver Router C As shown in Figure 42, 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 126

    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 127

    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. The BSR encapsulates the RP-set information in the bootstrap messages (BSMs) and floods the BSMs to the entire PIM-SM domain.

  • Page 128

    Anycast RP member address—IP address of each Anycast RP member for  communication among the RP members. Anycast RP address—IP address of the Anycast RP set for communication within the  PIM-SM domain. It is also known as RPA. As shown in Figure 45, RP 1, RP 2, and RP 3 are members of an Anycast RP set.

  • Page 129

    RPT building Figure 46 RPT building in a PIM-SM domain Host A Source Receiver Host B Server Receiver Join message Multicast packets Host C As shown in Figure 46, the process of building an RPT is as follows: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR.

  • Page 130

    Figure 47 Multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C Multicast packets As shown in Figure 47, the multicast source registers with the RP as follows: The multicast source S sends the first multicast packet to the multicast group G. When receiving the multicast packet, the source-side DR encapsulates the packet into a PIM register message and unicasts the message to the RP.

  • Page 131: Bidir-pim Overview

    When the RP receives multicast traffic, it sends an (S, G) source-specific join message toward the multicast source. The routers along the path from the RP to the multicast source constitute an SPT. The subsequent multicast data is forwarded to the RP along the SPT without being encapsulated into register messages.

  • Page 132

    DF election On a subnet with multiple multicast routers, duplicate multicast packets might be forwarded to the RP. To address this issue, BIDIR-PIM uses a designated forwarder (DF) election mechanism to elect a unique DF for each RP on a subnet. Only the DFs can forward multicast data to the RP. DF election is not necessary for an RPL.

  • Page 133

    Figure 49 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT Multicast packets Host C As shown in Figure 49, the process for building a receiver-side RPT is the same as the process for building an RPT in PIM-SM: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the directly connected router.

  • Page 134: Administrative Scoping Overview

    Figure 50 RPT building at the multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT Multicast packets Host C As shown in Figure 50, 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 135

    Multicast group ranges that are associated with different admin-scoped zones can have intersections. However, the multicast groups in an admin-scoped zone are valid only within the local zone, and theses multicast groups are regarded as private group addresses. The global-scoped zone maintains a BSR for the multicast groups that do not belong to any admin-scoped zones.

  • Page 136: Pim-ssm Overview

    Figure 52 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 52, 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 137: Relationship Among Pim Protocols

    Figure 53 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 53, 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 138: Pim Support For Vpns

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

  • Page 139: 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 the PIM-DM graft retry timer (Optional.) Configuring common PIM features Configuration prerequisites Before you configure PIM-DM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.

  • Page 140: 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 141: 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, •...

  • Page 142: Configuring An Rp

    and enter MRIB view. [ vpn-instance vpn-instance-name ] disabled. Return to system view. quit interface interface-type Enter interface view. interface-number Enable PIM-SM. pim sm By default, PIM-SM is disabled. Configuring an RP An RP can provide services for multiple or all multicast groups. However, only one RP can forward multicast traffic for a multicast group at a time.

  • Page 143

    A C-RP policy enables the BSR to filter C-RP advertisement messages by using an ACL that specifies the packet source address range and multicast groups. It is used to guard against C-RP spoofing. You must configure the same C-RP policy on all C-BSRs in the PIM-SM domain. To configure a C-RP: Step Command...

  • Page 144: Configuring A Bsr

    Step Command Remarks Enter system view. system-view Enter PIM view. [ vpn-instance vpn-instance-name ] By default, Anycast RP is not configured. anycast-rp anycast-rp-address You can repeat this command to Configure Anycast RP. member-rp-address add multiple RP member addresses to the Anycast RP set.

  • Page 145

    To configure a C-BSR: Step Command Remarks Enter system view. system-view Enter PIM view. [ vpn-instance vpn-instance-name ] c-bsr ip-address [ scope group-address Configure a C-BSR. { mask-length | mask } ] By default, no C-BSRs exist. [ hash-length hash-length | priority priority ] * By default, no BSR policy exists, (Optional.) Configure a BSR...

  • Page 146: Configuring Multicast Source Registration

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

  • Page 147: Configuring The Switchover To Spt

    Step Command Remarks Enter system view. system-view Enter PIM view. [ vpn-instance vpn-instance-nam By default, no PIM register policy Configure a PIM register register-policy ipv4-acl-number exists, and all PIM register policy. messages are regarded as legal. Configure the device to By default, the device calculates calculate the checksum register-whole-checksum...

  • Page 148: Configuration Prerequisites

    • (Required.) Configuring a C-BSR • (Optional.) Configuring a PIM domain border • (Optional.) Disabling BSM semantic fragmentation • (Optional.) Disabling the device from forwarding BSMs out of their incoming interfaces (Optional.) Configuring common PIM features Configuration prerequisites Before you configure BIDIR-PIM, configure a unicast routing protocol so that all devices in the domain can interoperate at the network layer.

  • Page 149

    An RP can be manually configured or dynamically elected through the BSR mechanism. For a large-scaled PIM network, configuring static RPs is a tedious job. Generally, static RPs are backups for dynamic RPs to enhance the robustness and operational manageability on a multicast network. Configuring a static RP If only one dynamic RP exists on a network, you can configure a static RP to avoid communication interruption caused by single-point failures.

  • Page 150

    Step Command Remarks Enter system view. system-view Enter PIM view. pim [ vpn-instance vpn-instance-name ] Configure a C-RP to c-rp ip-address [ advertisement-interval adv-interval By default, no C-RPs provide services for | group-policy ipv4-acl-number | holdtime hold-time exist. BIDIR-PIM. | priority priority ] * bidir Enabling Auto-RP listening This feature enables the device to receive Auto-RP announcement and discovery messages and learn RP information.

  • Page 151

    domain, reserve a large bandwidth between the C-BSR and other devices. The BSR election process is summarized as follows: Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain. When a C-BSR receives the BSM from another C-BSR, it compares its own priority with the priority carried in the message.

  • Page 152

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

  • Page 153: 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 154: Configuring Common Pim Features

    Configuration restrictions and guidelines When you configure the SSM group range, follow these restrictions and guidelines: • Configure the same SSM group range on all routers in the entire PIM-SSM domain. Otherwise, multicast information cannot be delivered through the SSM model. •...

  • Page 155: Configuring A Multicast Source Policy

    Configuring a multicast source policy This feature enables the device to filter multicast data by using an ACL that specifies the multicast sources and the optional groups. It filters not only data packets but also register messages with multicast data encapsulated. It controls the information available to downstream receivers. To configure a multicast source policy: Step Command...

  • Page 156

    On the shared-media LAN, the propagation delay and override interval are used as follows: If a router receives a prune message on its upstream interface, it means that there are  downstream routers on the shared-media LAN. If this router still needs to receive multicast data, it must send a join message to override the prune message within the override interval.

  • Page 157: Configuring Common Pim Timers

    Set the PIM message The default setting is 500 pim hello-option lan-delay delay propagation delay. milliseconds. pim hello-option The default setting is 2500 Set the override interval. override-interval interval milliseconds. pim hello-option By default, neighbor tracking is Enable neighbor tracking. neighbor-tracking disabled.

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

    Set the joined/pruned The default setting is 210 holdtime join-prune time state holdtime. seconds. Set the multicast source The default setting is 210 source-lifetime time lifetime. seconds. Configuring common PIM timers on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 159: Enabling Pim Passive Mode

    interface-number By default, BFD is disabled for Enable BFD for PIM. pim bfd enable PIM. Enabling PIM passive mode To guard against PIM hello spoofing, you can enable PIM passive mode on a receiver-side interface. 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 160: Setting A Dscp Value For Outgoing Pim Messages

    Step Command Remarks Enter system view. system-view snmp-agent trap enable pim Enable SNMP notifications [ candidate-bsr-win-election By default, SNMP notifications for for PIM. | elected-bsr-lost-election PIM are enabled. | neighbor-loss ] * Setting a DSCP value for outgoing PIM messages To control the transmission preference of outgoing PIM messages, set a DSCP value for outgoing PIM messages.

  • Page 161: Pim Configuration Examples

    PIM-SM domain. [ group-address ] display pim statistics Display statistics for PIM packets. PIM configuration examples PIM-DM configuration example Network requirements As shown in Figure • OSPF runs on the network. • VOD streams are sent to receiver hosts in multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist on each stub network.

  • Page 162

    Configuration procedure Assign an IP address and subnet mask for each interface, as shown in Figure 55. (Details not shown.) Configure OSPF on the switches in the PIM-DM domain. (Details not shown.) Enable IP multicast routing, IGMP, and PIM-DM: # On Switch A, enable IP multicast routing. <SwitchA>...

  • Page 163

    Neighbor Interface Uptime Expires Dr-Priority Mode 192.168.1.1 Vlan103 00:02:22 00:01:27 1 192.168.2.1 Vlan101 00:00:22 00:01:29 3 192.168.3.1 Vlan102 00:00:23 00:01:31 5 # Send an IGMP report from Host A to join multicast group 225.1.1.1. (Details not shown.) # Send multicast data from multicast source 10.110.5.100/24 to multicast group 225.1.1.1. (Details not shown.) # Display PIM routing entries on Switch A.

  • Page 164: Pim-sm Non-scoped Zone Configuration Example

    The output shows the following information: • Switches on the SPT path (Switch A and Switch D) have the correct (S, G) entries. • Switch A has the correct (*, G) entry. PIM-SM non-scoped zone configuration example Network requirements As shown in Figure •...

  • Page 165

    Switch B Vlan-int200 10.110.2.1/24 Switch E Vlan-int104 192.168.3.2/24 Switch B Vlan-int103 192.168.2.1/24 Switch E Vlan-int103 192.168.2.2/24 Switch C Vlan-int200 10.110.2.2/24 Switch E Vlan-int102 192.168.9.2/24 Switch C Vlan-int104 192.168.3.1/24 Switch E Vlan-int105 192.168.4.1/24 Configuration procedure Assign an IP address and subnet mask to each interface, as shown in Figure 56.

  • Page 166: Pim-sm Admin-scoped Zone Configuration Example

    # Configure the static RP on Switch B, Switch C, and Switch D in the same way Switch A is configured. (Details not shown.) Verifying the configuration # Display PIM information on Switch A. [SwitchA] display pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan100...

  • Page 167

    • VOD streams are sent to receiver hosts in multicast. The entire PIM-SM domain is divided into admin-scoped zone 1, admin-scoped zone 2, and the global-scoped zone. Switch B, Switch C, and Switch D are ZBRs of the three zones, respectively. •...

  • Page 168

    Switch C Vlan-int104 10.110.4.1/24 Switch F Vlan-int107 10.110.8.2/24 Switch C Vlan-int105 10.110.5.1/24 Switch F Vlan-int102 10.110.3.2/24 Switch C Vlan-int103 10.110.2.2/24 Switch G Vlan-int500 192.168.5.1/24 Switch C Vlan-int106 10.110.6.1/24 Switch G Vlan-int109 10.110.9.2/24 Switch H Vlan-int110 10.110.10.1/24 Source 1 — 192.168.2.10/24 Switch H Vlan-int106 10.110.6.2/24...

  • Page 169

    Configure admin-scoped zone boundaries: # On Switch B, configure VLAN-interface 102 and VLAN-interface 103 as the boundaries of admin-scoped zone 1. [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] multicast boundary 239.0.0.0 8 [SwitchB-Vlan-interface102] quit [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchB-Vlan-interface103] quit # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 as the boundaries of admin-scoped zone 2.

  • Page 170

    [SwitchF-pim] quit Verifying the configuration # Display BSR information on Switch B. [SwitchB] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 10.110.9.1 Priority: 64 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...

  • Page 171: Bidir-pim Configuration Example

    Elected BSR address: 10.110.9.1 Priority: 64 Hash mask length: 30 Uptime: 00:11:11 Candidate BSR address: 10.110.9.1 Priority: 64 Hash mask length: 30 # Display RP information on Switch B. [SwitchB] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime...

  • Page 172

    • IGMPv2 runs between Switch B and Host A, and between Switch D and Host B. Figure 58 Network diagram Receiver 1 Loop0 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...

  • Page 173

    [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 174

    [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 a C-BSR, and Loopback 0 as a C-RP for the entire BIDIR-PIM domain.

  • Page 175: Pim-ssm Configuration Example

    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 DFs for multicast forwarding on Switch B. [SwitchB] display multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 1.1.1.1 Flags: 0x0 Uptime: 00:06:24 RPF interface: Vlan-interface102...

  • Page 176

    • The entire PIM domain operates in the SSM mode. • Host A and Host C are multicast receivers on two stub networks. • The SSM group range is 232.1.1.0/24. • IGMPv3 runs between Switch A and N1, and between Switch B, Switch C, and N2. Figure 59 Network diagram Receiver Host A...

  • Page 177

    [SwitchA-mrib] quit # Enable IGMPv3 on VLAN-interface 100 (the interface that connects to the stub network). [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 178: Troubleshooting Pim

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

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

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

  • Page 180

    If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 181: Configuring Msdp

    Configuring MSDP Overview Multicast Source Discovery Protocol (MSDP) is an inter-domain multicast solution that addresses the interconnection of PIM-SM domains. It discovers multicast source information in other PIM-SM domains. In the basic PIM-SM mode, a multicast source registers only with the RP in the local PIM-SM domain, and the multicast source information in each domain is isolated.

  • Page 182

    As shown in Figure 60, an MSDP peer can be created on any PIM-SM router. MSDP peers created on PIM-SM routers that assume different roles function differently. • MSDP peers created on RPs: Source-side MSDP peer—MSDP peer closest to the multicast source, such as RP 1. The ...

  • Page 183

    Figure 61 Inter-domain multicast delivery through MSDP Receiver DR 2 MSDP peers Multicast packets SA message RP 2 Join message PIM-SM 2 Register message DR 1 Source PIM-SM 4 RP 1 RP 3 PIM-SM 1 PIM-SM 3 The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: When the multicast source in PIM-SM 1 sends the first multicast packet to multicast group G, DR 1 encapsulates the data within a register message.

  • Page 184

    determines whether to initiate an RPT-to-SPT switchover process based on its configuration. If no receivers exist in the domain, RP 2 neither creates an (S, G) entry nor sends a join  message toward the multicast source. In inter-domain multicasting using MSDP, once an RP gets information about a multicast source in another PIM-SM domain, it no longer relies on RPs in other PIM-SM domains.

  • Page 185

    Figure 62 Anycast RP through MSDP RP 1 RP 2 Router A Router B PIM-SM Source Receiver MSDP peers SA message The following describes how Anycast RP through MSDP is implemented: a. After receiving the multicast data from Source, the source-side DR registers with the closest RP (RP 1 in this example).

  • Page 186: Msdp Support For Vpns

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

  • Page 187: Msdp Configuration Task List

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

  • Page 188: Specifying An Msdp Peer

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

  • Page 189: Configuring An Msdp Mesh Group

    To configure a description for an MSDP peer: Step Command Remarks Enter system view. system-view Enter MSDP view. msdp [ vpn-instance vpn-instance-name ] Configure a description By default, no description for peer peer-address description text for an MSDP peer. an MSDP peer exists. Configuring an MSDP mesh group This feature avoids SA message flooding among MSDP peers within an AS.

  • Page 190: Configuring Sa Message-related Parameters

    You can change the MSDP connection retry interval to adjust the interval between MSDP peering connection attempts. To enhance MSDP security, enable MD5 authentication for both MSDP peers to establish a TCP connection. If the MD5 authentication fails, the TCP connection cannot be established. IMPORTANT: The MSDP peers involved in MD5 authentication must be configured with the same authentication method and key.

  • Page 191: Configuring The Originating Rp Of Sa Messages

    the source-side DR and builds an SPT. Because the (S, G) entries have timed out, remote receivers can never receive the multicast data from the multicast source. To avoid this problem, you can enable the source-side RP to encapsulate multicast data in SA messages.

  • Page 192: Configuring Sa Message Policies

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

  • Page 193: Configuring The Sa Cache Mechanism

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

  • Page 194: Msdp Configuration Examples

    Task Command display msdp [ vpn-instance vpn-instance-name ] brief Display brief information about MSDP peers. [ state { connect | disabled | established | listen | shutdown } ] Display MSDP NSR status information. display msdp non-stop-routing status display Display detailed status of MSDP peers. msdp [ vpn-instance vpn-instance-name ] peer-st atus [ peer-address ] display...

  • Page 195

    Figure 64 Network diagram AS 100 AS 200 Receiver Receiver Loop0 Switch F Switch E Vlan-int105 Source 1 Vlan-int105 Vlan-int102 Vlan-int100 PIM-SM 3 Switch A PIM-SM 2 Vlan-int102 Switch B Vlan-int101 Vlan-int104 Vlan-int101 Vlan-int104 Switch C Switch D Loop0 Loop0 Source 2 PIM-SM 1 MSDP peers...

  • Page 196

    [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 197

    [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 198

    * > 1.1.1.1/32 192.168.1.1 100? * >i 2.2.2.2/32 0.0.0.0 * > 192.168.1.0 0.0.0.0 * > 192.168.1.1/32 0.0.0.0 * > 192.168.1.2/32 0.0.0.0 # Verify that hosts in PIM-SM 1 and PIM-SM 3 can receive the multicast data from Source 1 in PIM-SM 1 and Source 2 in PIM-SM 2.

  • Page 199: Inter-as Multicast Configuration By Leveraging Static Rpf Peers

    Import policy: None Export policy: None Information about SA-Requests: Policy to accept SA-Requests: None Sending SA-Requests status: Disable Minimum TTL to forward SA with encapsulated data: 0 SAs learned from this peer: 0, SA cache maximum for the peer: 4294967295 Input queue size: 0, Output queue size: 0 Counters for MSDP messages: RPF check failure: 0...

  • Page 200

    Figure 65 Network diagram AS 100 AS 200 PIM-SM 3 Receiver Switch G Vlan-int106 Vlan-int106 Switch F Loop0 Loop0 Receiver Vlan-int102 Vlan-int102 Switch A Switch C PIM-SM 2 Switch D Switch E Vlan-int103 Vlan-int105 Vlan-int103 Vlan-int105 Vlan-int100 Switch B Source 1 Loop0 Source 2 PIM-SM 1...

  • Page 201

    # Enable PIM-SM on each interface, and enable IGMP on the receiver-side interface (VLAN-interface 200). [SwitchC] interface vlan-interface 102 [SwitchC-Vlan-interface102] pim sm [SwitchC-Vlan-interface102] quit [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim sm [SwitchC-Vlan-interface104] quit # Configure Switch A, Switch B, Switch D, Switch E, Switch F, and Switch G in the same way Switch C is configured.

  • Page 202

    [SwitchC] bgp 100 [SwitchC-bgp] router-id 1.1.1.3 [SwitchC-bgp] peer 10.110.4.2 as-number 200 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] peer 10.110.4.2 enable [SwitchC-bgp-ipv4] import-route ospf 1 [SwitchC-bgp-ipv4]quit [SwitchC-bgp] quit # On Switch F, configure an EBGP peer, and redistribute OSPF routing information. [SwitchF] bgp 200 [SwitchF-bgp] router-id 3.3.3.1 [SwitchF-bgp] peer 10.110.4.1 as-number 100 [SwitchF-bgp] address-family ipv4 unicast...

  • Page 203: Anycast Rp Configuration

    # On Switch G, configure Switch A as the MSDP peer and static RPF peer. [SwitchG] ip prefix-list list-a permit 10.110.0.0 16 greater-equal 16 less-equal 32 [SwitchG] msdp [SwitchG-msdp] peer 10.110.2.1 connect-interface vlan-interface 106 [SwitchG-msdp] static-rpf-peer 10.110.2.1 rp-policy list-a [SwitchG-msdp] quit Verifying the configuration # Display the BGP peering relationships on Switch A.

  • Page 204

    Figure 66 Network diagram Source 1 Source 2 Switch A Switch C Switch E Vlan-int300 Vlan-int400 Receiver Receiver Switch B Switch D Vlan-int100 Vlan-int200 Host A Host B Loop10 Loop10 PIM-SM MSDP peers Table 16 Interface and IP address assignment Device Interface IP address...

  • Page 205

    [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 206

    [SwitchD] display msdp brief Configured Established Listen Connect Shutdown Disabled Peer address State Up/Down time SA count Reset count 1.1.1.1 Established 00:10:57 # Send an IGMP report from Host A to join multicast group 225.1.1.1. (Details not shown.) # Send multicast data from Source 1 to multicast group 225.1.1.1. (Details not shown.) # Display the PIM routing table on Switch D.

  • Page 207: 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 208

    Figure 67 Network diagram PIM-SM 1 PIM-SM 2 PIM-SM 3 Loop0 Source 2 Vlan-int100 Switch A Receiver Loop0 Host A Vlan-int400 Switch C Vlan-int104 Vlan-int104 Switch D Vlan-int300 Vlan-int500 Source 1 Vlan-int200 Switch B Receiver Receiver Host B Host C MSDP peers Table 17 Interface and IP address assignment Device...

  • Page 209

    [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 210: Troubleshooting Msdp

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

  • Page 211: 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 might include the following: • A TCP connection-based MSDP peering relationship is established between the local interface address and the MSDP peer. •...

  • Page 212: 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 might 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 213: Configuring Multicast Vpn

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

  • Page 214: Md Vpn Overview

    Figure 69 Multicast in multiple VPN instances PE 1" PE 2" Site 3 MD A Site 1 Site 5 PE 3" VPN instance A PE 1' PE 2' PE 3' Public instance Site 4 PE 1"' MD B PE 2"' Site 2 Site 6 PE 3"'...

  • Page 215

    Table 18 Basic MD VPN concepts Concept Description An MD is a set of PE devices that are in the same VPN instance. Multicast domain (MD) Each MD uniquely corresponds to a VPN instance. An MDT is a multicast distribution tree constructed by all PE devices Multicast distribution tree (MDT) in the same VPN.

  • Page 216

    b. The encapsulated multicast packet is sent by the PE device and travels over the public network. c. After receiving the multicast packet, the remote PE device decapsulates the multicast packet to get the original VPN multicast packet. • The local PE device sends VPN data out of the MTI. The remote PE devices receive the private data from their MTI interfaces.

  • Page 217

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

  • Page 218: Default-mdt Establishment

    For a VPN instance, multicast data transmission on the public network is transparent. The VPN data is exchanged between the MTIs of the local PE and the remote PE. This implements the seamless transmission of the VPN data over the public network. However, the multicast data transmission process (the MDT transmission process) over the public network is very complicated.

  • Page 219

    Default-MDT establishment in a PIM-SM network Figure 73 Default-MDT establishment in a PIM-SM network BGP: 11.1.3.1/24 PE 3 Default-group: 239.1.1.1 Public instance BGP peers RPT (*, 239.1.1.1) SPT (11.1.1.1, 239.1.1.1) SPT (11.1.2.1, 239.1.1.1) SPT (11.1.3.1, 239.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in...

  • Page 220

    Default-MDT establishment in a BIDIR-PIM network Figure 74 Default-MDT establishment in a BIDIR-PIM network BGP: 11.1.3.1/24 PE 3 Default-Group: 239.1.1.1 Public instance BGP peers Receiver-side RPT (*, 239.1.1.1) Source-side RPT (*, 239.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 74, BIDIR-PIM runs on the network, and all the PE devices support VPN instance...

  • Page 221: Default-mdt-based Delivery

    Default-MDT establishment in a PIM-SSM network Figure 75 Default-MDT establishment in a PIM-SSM network BGP: 11.1.3.1/24 PE 3 Default-Group: 232.1.1.1 Public instance BGP peers SPT (11.1.1.1, 232.1.1.1) SPT (11.1.2.1, 232.1.1.1) SPT (11.1.3.1, 232.1.1.1) PE 1 PE 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 As shown in Figure 75, PIM-SSM runs on the network, and all the PE devices support VPN instance...

  • Page 222

    A flood-prune process (in PIM-DM) or a join process (in PIM-SSM) is initiated across the  public network to establish an SPT across the public network. • If the VPN network runs PIM-SM: Hello packets are forwarded through MTI interfaces to establish PIM neighboring ...

  • Page 223

    After receiving the join message from CE 2, the VPN instance on PE 2 creates a state entry (*, 225.1.1.1) and specifies the MTI interface as the upstream interface. The VPN instance on PE 2 considers the join message to have been sent out of the MTI interface, because step 3 is transparent to the VPN instance.

  • Page 224: Mdt Switchover

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

  • Page 225: Inter-as Md Vpn

    connect VPN multicast receivers and multicast sources. When specific network criteria are met, a switchover from the default-MDT to the data-MDT occurs to forward VPN multicast traffic to receivers. The process of default-MDT to data-MDT switchover is as follows: The source-side PE device (PE 1, for example) periodically examines the forwarded VPN multicast traffic.

  • Page 226

    Based on these solutions, there are three ways to implement inter-AS MD VPN: • MD VPN inter-AS option A • MD VPN inter-AS option B • MD VPN inter-AS option C MD VPN inter-AS option A As shown in Figure •...

  • Page 227

    route. In this way, the PIM message can be forwarded across the ASs and an MDT is established. • BGP connector—Attribute shared by BGP peers when they exchange VPNv4 routes. It is the IP address of the remote PE device. The local PE device fills the upstream neighbor address field with the BGP connector in a join message.

  • Page 228: M6vpe

    • A VPN network involves AS 1 and AS 2. • PE 3 and PE 4 are the ASBRs for AS 1 and AS 2, respectively. • PE 3 and PE 4 are interconnected through MP-EBGP and treat each other as a P device. •...

  • Page 229: Multicast Vpn Configuration Task List

    Figure 81 M6VPE network Public network PE 1 PE 2 CE 1 CE 2 VPN A VPN A Site 1 Site 2 IPv6 multicast traffic forwarding over the IPv4 public network is as follows: CE 1 forwards an IPv6 multicast packet for VPN instance VPN A to PE 1. PE 1 encapsulates the IPv6 multicast packet with an IPv4 packet header and transmits the IPv4 packet in the IPv4 backbone network.

  • Page 230: Configuring Md Vpn

    Configuring MD VPN This section describes how to configure MD VPN. 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. •...

  • Page 231: Creating An Md For A Vpn Instance

    Creating an MD for a VPN instance To provide multicast services for a VPN instance, you must create an MD for the VPN instance on PE devices that belong to the VPN instance. After the MD is created, the system automatically creates MTIs and binds them with the VPN instance.

  • Page 232: Specifying The Md Source Interface

    Step Command Remarks Enter system view. system-view multicast-domain Enter MD view. vpn-instance vpn-instance-name • Enter MD IPv4 address family view: address-family ipv4 Enter MD address family • view. Enter MD IPv6 address family view: address-family ipv6 By default, no default-group Specify the default-group.

  • Page 233: Configuring The Rpf Vector Feature

    • Perform this task on PE devices. • On a PE, the data-group range for an MD cannot include the default-group or data-groups of any other MD. • For an MD that transmits both IPv4 and IPv6 multicast packets, the data-group range in MD IPv4 and IPv6 address family views cannot overlap.

  • Page 234: Enabling Data-group Reuse Logging

    Step Command Remarks Enter system view. system-view Enable RPF vector multicast rpf-proxy-vector By default, RPF vector compatibility. compatible compatibility is disabled. Enabling data-group reuse logging For a given VPN, the number of VPN multicast streams to be switched to data-MDTs might exceed the number of addresses in the data-group range.

  • Page 235: Configuring Bgp Mdt Peers Or Peer Groups

    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 236: Displaying And Maintaining Multicast Vpn

    Step Command Remarks Enter system view. system-view bgp as-number [ instance Enter BGP instance view. instance-name ] Enter BGP IPv4 MDT address-family ipv4 mdt address family view. Configure the device as a peer { group-name | route reflector and specify its By default, neither route reflectors ip-address [ mask-length ] } peers or peer groups as...

  • Page 237: Multicast Vpn Configuration Examples

    Display information about display multicast-domain vpn-instance vpn-instance-name ipv6 data-grou data-groups for IPv6 multicast transmission that are sent in a p send [ group group-address | reuse interval | vpn-source-address VPN instance. [ mask-length ] | vpn-group-address [ mask-length ] ] * Display information about display multicast-domain default-groups for IPv4 multicast...

  • Page 238

    • Enable IGMPv2 on VLAN-interface 40 of CE a2, VLAN-interface 50 of CE a3, and VLAN-interface 60 of CE b2. Enable PIM-SM on the public network and for VPN instances a and b: • Enable PIM-SM on all interfaces of the P device. •...

  • Page 239

    Loop1 2.2.2.2/32 CE a2 Vlan-int16 10.110.12.1/24 Loop1 PE 1 Vlan-int12 192.168.6.1/24 CE a2 22.22.22.22/32 PE 1 Vlan-int20 10.110.1.1/24 CE a3 Vlan-int50 10.110.10.1/24 PE 1 Vlan-int11 10.110.2.1/24 CE a3 Vlan-int17 10.110.5.2/24 PE 1 Loop1 1.1.1.1/32 CE a3 Vlan-int16 10.110.12.2/24 PE 2 Vlan-int15 192.168.7.1/24 CE b1...

  • Page 240

    [PE1-md-a-ipv4] quit [PE1-md-a] quit # Assign an IP address to VLAN-interface 12. [PE1] interface vlan-interface 12 [PE1-Vlan-interface12] ip address 192.168.6.1 24 #Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 12. [PE1-Vlan-interface12] pim sm [PE1-Vlan-interface12] mpls enable [PE1-Vlan-interface12] mpls ldp enable [PE1-Vlan-interface12] quit # Associate VLAN-interface 20 with VPN instance a.

  • Page 241

    [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 192.168.6.0 0.0.0.255 [PE1-ospf-1-area-0.0.0.0] quit [PE1-ospf-1] quit # Configure RIP. [PE1] rip 2 vpn-instance a [PE1-rip-2] network 10.110.1.0 0.0.0.255 [PE1-rip-2] network 10.110.2.0 0.0.0.255 [PE1-rip-2] import-route bgp [PE1-rip-2] return Configure PE 2: # Configure a global router ID, and enable IP multicast routing on the public network. <PE2>...

  • Page 242

    # Create a VPN instance named a, and configure an RD and route targets for VPN instance. [PE2] ip vpn-instance a [PE2-vpn-instance-a] route-distinguisher 100:1 [PE2-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE2-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE2-vpn-instance-a] quit # Enable IP multicast routing for VPN instance a. [PE2] multicast routing vpn-instance a [PE2-mrib-a] quit # Create an MD for VPN instance a.

  • Page 243

    [PE2] bgp 100 [PE2-bgp-default] group vpn-g internal [PE2-bgp-default] peer vpn-g connect-interface loopback 1 [PE2-bgp-default] peer 1.1.1.1 group vpn-g [PE2-bgp-default] peer 1.1.1.3 group vpn-g [PE2–bgp-default] ip vpn-instance a [PE2-bgp-default-a] address-family ipv4 [PE2-bgp-default-ipv4-a] import-route rip 2 [PE2-bgp-default-ipv4-a] import-route direct [PE2-bgp-default-ipv4-a] quit [PE2-bgp-default-a] quit [PE2–bgp-default] ip vpn-instance b [PE2-bgp-default-b] address-family ipv4 [PE2-bgp-default-ipv4-b] import-route rip 3...

  • Page 244

    [PE3-HundredGigE1/0/4] port service-loopback group 1 [PE3-HundredGigE1/0/4] quit # Configure an LSR ID, and enable LDP globally. [PE3] mpls lsr-id 1.1.1.3 [PE3] mpls ldp [PE3-ldp] quit # Create a VPN instance named a, and configure an RD and route targets for the VPN instance. [PE3] ip vpn-instance a [PE3-vpn-instance-a] route-distinguisher 100:1 [PE3-vpn-instance-a] vpn-target 100:1 export-extcommunity...

  • Page 245

    [PE3-Vlan-interface19] ip address 192.168.8.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 19. [PE3-Vlan-interface19] pim sm [PE3-Vlan-interface19] mpls enable [PE3-Vlan-interface19] mpls ldp enable [PE3-Vlan-interface19] quit # Associate VLAN-interface 17 with VPN instance a. [PE3] interface vlan-interface 17 [PE3-Vlan-interface17] ip binding vpn-instance a # Assign an IP address to VLAN-interface 17, and enable PIM-SM on the interface.

  • Page 246

    [PE3-bgp-default-ipv4-a] quit [PE3-bgp-default-a] quit [PE3–bgp-default] ip vpn-instance b [PE3-bgp-default-b] address-family ipv4 [PE3-bgp-default-ipv4-b] import-route rip 3 [PE3-bgp-default-ipv4-b] import-route direct [PE3-bgp-default-ipv4-b] quit [PE3-bgp-default-b] quit [PE3–bgp-default] address-family vpnv4 [PE3–bgp-default-vpnv4] peer vpn-g enable [PE3–bgp-default-vpnv4] quit [PE3–bgp-default] quit # Configure OSPF. [PE3] ospf 1 [PE3-ospf-1] area 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255 [PE3-ospf-1-area-0.0.0.0] quit...

  • Page 247

    [P-Vlan-interface15] ip address 192.168.7.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 15. [P-Vlan-interface15] pim sm [P-Vlan-interface15] mpls enable [P-Vlan-interface15] mpls ldp enable [P-Vlan-interface15] quit # Assign an IP address to VLAN-interface 19. [P] interface vlan-interface 19 [P-Vlan-interface19] ip address 192.168.8.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 19.

  • Page 248

    [CEa1] rip 2 [CEa1-rip-2] network 10.110.2.0 0.0.0.255 [CEa1-rip-2] network 10.110.7.0 0.0.0.255 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 the interface. [CEb1] interface vlan-interface 30 [CEb1-Vlan-interface30] ip address 10.110.8.1 24 [CEb1-Vlan-interface30] pim sm...

  • Page 249

    # Configure Loopback 1 as a C-BSR and a C-RP. [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.110.4.0 0.0.0.255 [CEa2-rip-2] network 10.110.9.0 0.0.0.255 [CEa2-rip-2] network 10.110.12.0 0.0.0.255 [CEa2-rip-2] network 22.22.22.22 0.0.0.0 Configure CE a3: # Enable IP multicast routing.

  • Page 250: Intra-as M6vpe Configuration Example

    [CEb2] interface vlan-interface 18 [CEb2-Vlan-interface18] ip address 10.110.6.2 24 [CEb2-Vlan-interface18] pim sm [CEb2-Vlan-interface18] quit # Configure RIP. [CEb2] rip 3 [CEb2-rip-3] network 10.110.6.0 0.0.0.255 [CEb2-rip-3] network 10.110.11.0 0.0.0.255 Verifying the configuration # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 1.

  • Page 251

    belong to the public network. • PE 3: VLAN-interface 17 belongs to VPN instance a. VLAN-interface 18 and Loopback 2 belongs to VPN instance b. VLAN-interface 19 and Loopback 1 belong to the public network. • Configure OSPF on the public network, and configure OSPFv3 between the PE devices and the CE devices.

  • Page 252

    Figure 83 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 20 Interface and IP address assignment IPv4/IPv6...

  • Page 253

    Configuration procedure Configure PE 1: # Configure a global router ID, and enable IP multicast routing on the public network. <PE1> system-view [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE1] service-loopback group 1 type multicast-tunnel # Assign HundredGigE 1/0/4 to service loopback group 1.

  • Page 254

    # Associate VLAN-interface 20 with VPN instance a, and assign an IPv6 address to the interface. [PE1] interface vlan-interface 20 [PE1-Vlan-interface20] ip binding vpn-instance a [PE1-Vlan-interface20] ipv6 address 10:110:1::1 64 # Configure VLAN-interface 20 to run OSPFv3 process 2 in Area 0, and enable MLD on the interface.

  • Page 255

    # Configure OSPFv3. [PE1] ospfv3 2 vpn-instance a [PE1-ospfv3-2] router-id 1.1.1.1 [PE1-ospfv3-2] import-route bgp4+ [PE1-ospfv3-2] import-route direct [PE1-ospfv3-2] area 0 [PE1-ospfv3-2-area-0.0.0.0] return Configure PE 2: # Configure a global RD, and enable IP multicast routing on the public network. <PE2> system-view [PE2] router id 1.1.1.2 [PE2] multicast routing [PE2-mrib] quit...

  • Page 256

    [PE2-vpn-instance-a] route-distinguisher 100:1 [PE2-vpn-instance-a] vpn-target 100:1 export-extcommunity [PE2-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE2-vpn-instance-a] quit # Enable IPv6 multicast routing for VPN instance a. [PE2] ipv6 multicast routing vpn-instance a [PE2-mrib6-a] quit # Create an MD for VPN instance a. [PE2] multicast-domain vpn-instance a # Create an MD IPv6 address family for VPN instance a.

  • Page 257

    [PE2-LoopBack1] ip address 1.1.1.2 32 [PE2-LoopBack1] pim sm [PE2-LoopBack1] quit # Configure BGP. [PE2] bgp 100 [PE2-bgp-default] group vpn-g internal [PE2-bgp-default] peer vpn-g connect-interface loopback 1 [PE2-bgp-default] peer 1.1.1.1 group vpn-g [PE2-bgp-default] peer 1.1.1.3 group vpn-g [PE2–bgp-default] ip vpn-instance a [PE2-bgp-default-a] address-family ipv6 [PE2-bgp-default-ipv6-a] import-route ospfv3 2 [PE2-bgp-default-ipv6-a] import-route direct...

  • Page 258

    [PE3] multicast routing [PE3-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE3] service-loopback group 1 type multicast-tunnel # Assign HundredGigE 1/0/4 to service loopback group 1. The interface does not belong to VLAN 17, VLAN 18, or VLAN 19.

  • Page 259

    # Specify the default-group, the MD source interface, and the data-group range for VPN instance b. [PE3-md-b-ipv6] default-group 239.2.2.2 [PE3-md-b-ipv6] source loopback 1 [PE3-md-b-ipv6] data-group 225.4.4.0 28 [PE3-md-b-ipv6] quit [PE3-md-b] quit # Assign an IP address to VLAN-interface 19. [PE3] interface vlan-interface 19 [PE3-Vlan-interface19] ip address 192.168.8.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 19.

  • Page 260

    # Configure Loopback 2 as a C-BSR and a C-RP. [PE3] ipv6 pim vpn-instance b [PE3-pim6-b] c-bsr 33:33:33::33 [PE3-pim6-b] c-rp 33:33:33::33 [PE3-pim6-b] quit # Configure BGP. [PE3] bgp 100 [PE3-bgp-default] group vpn-g internal [PE3-bgp-default] peer vpn-g connect-interface loopback 1 [PE3-bgp-default] peer 1.1.1.1 group vpn-g [PE3-bgp-default] peer 1.1.1.2 group vpn-g [PE3–bgp-default] ip vpn-instance a [PE3-bgp-default-a] address-family ipv6...

  • Page 261

    <P> system-view [P] multicast routing [P-mrib] quit # Configure an LSR ID, and enable LDP globally. [P] mpls lsr-id 2.2.2.2 [P] mpls ldp [P-ldp] quit # Assign an IP address to VLAN-interface 12. [P] interface vlan-interface 12 [P-Vlan-interface12] ip address 192.168.6.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 12.

  • Page 262

    [P-ospf-1-area-0.0.0.0] network 192.168.8.0 0.0.0.255 Configure CE a1: # Enable IPv6 multicast routing. <CEa1> system-view [CEa1] ipv6 multicast routing [CEa1-mrib6] quit # Assign an IPv6 address to VLAN-interface 10. [CEa1] interface vlan-interface 10 [CEa1-Vlan-interface10] ipv6 address 10:110:7::1 64 # Configure VLAN-interface 10 to run OSPFv3 process 2 in Area 0, and enable IPv6 PIM-SM on the interface.

  • Page 263

    # Configure OSPFv3. [CEb1] ospfv3 3 [CEb1-ospfv3-3] router-id 7.7.7.7 [CEb1-ospfv3-3] area 0 [CEb1-ospfv3-3-area-0.0.0.0] quit Configure CE a2: # Enable IPv6 multicast routing. <CEa2> system-view [CEa2] ipv6 multicast routing [CEa2-mrib6] quit # Assign an IPv6 address to VLAN-interface 40. [CEa2] interface vlan-interface 40 [CEa2-Vlan-interface40] ipv6 address 10:110:9::1 64 # Configure VLAN-interface 40 to run OSPFv3 process 2 in Area 0, and enable MLD on the interface.

  • Page 264

    [CEa2] ospfv3 2 [CEa2-ospfv3-2] router-id 8.8.8.8 [CEa2-ospfv3-2] area 0 [CEa2-ospfv3-2-area-0.0.0.0] quit Configure CE a3: # Enable IPv6 multicast routing. <CEa3> system-view [CEa3] ipv6 multicast routing [CEa3-mrib6] quit # Assign an IPv6 address to VLAN-interface 50. [CEa3] interface vlan-interface 50 [CEa3-Vlan-interface50] ipv6 address 10:110:10::1 64 # Configure VLAN-interface 50 to run OSPFv3 process 2 in Area 0, and enable MLD on the interface.

  • Page 265: Md Vpn Inter-as Option B Configuration Example

    [CEb2-Vlan-interface60] ospfv3 3 area 0.0.0.0 [CEb2-Vlan-interface60] mld enable [CEb2-Vlan-interface60] quit # Assign an IPv6 address to VLAN-interface 18. [CEb2] interface vlan-interface 18 [CEb2-Vlan-interface18] ipv6 address 10:110:6::2 64 # Configure VLAN-interface 18 to run OSPFv3 process 3 in Area 0, and enable IPv6 PIM-SM on the interface.

  • Page 266

    • For VPN instance b, the default-group is 232.3.3.3, and the data-group range is 232.4.4.0 to 232.4.4.15. They are in the SSM group range. • PE 1: VLAN-interface 11 belongs to VPN instance a. VLAN-interface 12 belongs to VPN instance b. VLAN-interface 2 and Loopback 1 belong to the public network instance.

  • Page 267

    Figure 84 Network diagram CE a1 CE b2 Vlan-int21 Vlan-int24 VPN a VPN b Loop1 Loop1 Loop1 Loop1 Vlan-int2 Vlan-int4 Vlan-int3 Vlan-int5 Vlan-int6 Vlan-int4 Vlan-int2 Vlan-int3 Vlan-int5 Vlan-int6 PE 1 PE 4 PE 2 PE 3 ASBR ASBR AS 100 AS 200 Vlan-int22 Vlan-int23...

  • Page 268

    [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE1] service-loopback group 1 type multicast-tunnel # Assign HundredGigE 1/0/4 to service loopback group 1. The interface does not belong to VLAN 2, VLAN 11, or VLAN 12.

  • Page 269

    # Create an MD for VPN instance b. [PE1] multicast-domain vpn-instance b # Create an MD IPv4 address family for VPN instance b. [PE1-md-b] address-family ipv4 # Specify the default-group, the MD source interface, and the data-group range for VPN instance b.

  • Page 270

    [PE1–bgp-default] ip vpn-instance b [PE1-bgp-default-b] address-family ipv4 [PE1-bgp-default-ipv4-b] import-route ospf 3 [PE1-bgp-default-ipv4-b] import-route direct [PE1-bgp-default-ipv4-b] quit [PE1-bgp-default-b] quit [PE1–bgp-default] address-family vpnv4 [PE1–bgp-default-vpnv4] peer 2.2.2.2 enable [PE1–bgp-default-vpnv4] quit [PE1-bgp-default] address-family ipv4 mdt [PE1-bgp-default-mdt] peer 2.2.2.2 enable [PE1-bgp-default-mdt] quit [PE1–bgp-default] quit # Configure OSPF. [PE1] ospf 1 [PE1-ospf-1] area 0.0.0.0 [PE1-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0...

  • Page 271

    # Assign an IP address to VLAN-interface 4. [PE2] interface vlan-interface 4 [PE2-Vlan-interface4] ip address 10.3.1.1 24 # Enable PIM-SM and MPLS on VLAN-interface 4. [PE2-Vlan-interface4] pim sm [PE2-Vlan-interface4] mpls enable [PE2-Vlan-interface4] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [PE2] interface loopback 1 [PE2-LoopBack1] ip address 2.2.2.2 32 [PE2-LoopBack1] pim sm...

  • Page 272

    [PE3-Vlan-interface5] pim sm [PE3-Vlan-interface5] mpls enable [PE3-Vlan-interface5] mpls ldp enable [PE3-Vlan-interface5] quit # Assign an IP address to VLAN-interface 4. [PE3] interface vlan-interface 4 [PE3-Vlan-interface4] ip address 10.3.1.2 24 # Enable PIM-SM and MPLS on VLAN-interface 4. [PE3-Vlan-interface4] pim sm [PE3-Vlan-interface4] mpls enable [PE3-Vlan-interface4] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

  • Page 273

    [PE4] interface hundredgige 1/0/4 [PE4-HundredGigE1/0/4] port service-loopback group 1 [PE4-HundredGigE1/0/4] quit # Configure an LSR ID, and enable LDP globally. [PE4] mpls lsr-id 4.4.4.4 [PE4] mpls ldp [PE4-ldp] quit # Create a VPN instance named a, and configure the RD and route targets for the VPN instance.

  • Page 274

    [PE4-md-b-ipv4] default-group 232.3.3.3 [PE4-md-b-ipv4] source loopback 1 [PE4-md-b-ipv4] data-group 232.4.4.0 28 [PE4-md-b-ipv4] quit [PE4-md-b] quit # Assign an IP address to VLAN-interface 6. [PE4] interface vlan-interface 6 [PE4-Vlan-interface6] ip address 10.5.1.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 6. [PE4-Vlan-interface6] pim sm [PE4-Vlan-interface6] mpls enable [PE4-Vlan-interface6] mpls ldp enable...

  • Page 275

    [PE4–bgp-default] address-family vpnv4 [PE4–bgp-default-vpnv4] peer 3.3.3.3 enable [PE4–bgp-default-vpnv4] quit [PE4-bgp-default] address-family ipv4 mdt [PE4-bgp-default-mdt] peer 3.3.3.3 enable [PE4-bgp-default-mdt] quit [PE4–bgp-default] quit # Configure OSPF. [PE4] ospf 1 [PE4-ospf-1] area 0.0.0.0 [PE4-ospf-1-area-0.0.0.0] network 4.4.4.4 0.0.0.0 [PE4-ospf-1-area-0.0.0.0] network 10.5.1.0 0.0.0.255 [PE4-ospf-1-area-0.0.0.0] quit [PE4-ospf-1] quit [PE4] ospf 2 vpn-instance a [PE4-ospf-2] area 0.0.0.0...

  • Page 276

    [P1-Vlan-interface3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [P1] interface loopback 1 [P1-LoopBack1] ip address 5.5.5.5 32 [P1-LoopBack1] pim sm [P1-LoopBack1] quit # Configure OSPF. [P1] ospf 1 [P1-ospf-1] area 0.0.0.0 [P1-ospf-1-area-0.0.0.0] network 5.5.5.5 0.0.0.0 [P1-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 [P1-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 Configure P 2:...

  • Page 277

    [P2-ospf-1-area-0.0.0.0] network 10.5.1.0 0.0.0.255 Configure CE a1: # Enable IP multicast routing. <CEa1> system-view [CEa1] multicast routing [CEa1-mrib] quit # Assign an IP address to VLAN-interface 21, and enable PIM-SM on the interface. [CEa1] interface vlan-interface 21 [CEa1-Vlan-interface21] ip address 12.1.1.1 24 [CEa1-Vlan-interface21] pim sm [CEa1-Vlan-interface21] quit # Assign an IP address to VLAN-interface 11, and enable PIM-SM on the interface.

  • Page 278

    [CEb1-pim] quit # Configure OSPF. [CEb1] ospf 1 [CEb1-ospf-1] area 0.0.0.0 [CEb1-ospf-1-area-0.0.0.0] network 12.2.1.0 0.0.0.255 [CEb1-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.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 23, and enable IGMP on the interface. [CEa2] interface vlan-interface 23 [CEa2-Vlan-interface23] ip address 12.3.1.1 24 [CEa2-Vlan-interface23] igmp enable...

  • Page 279: Md Vpn Inter-as Option C Configuration Example

    [CEb2-ospf-1] area 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 12.4.1.0 0.0.0.255 [CEb2-ospf-1-area-0.0.0.0] network 11.4.1.0 0.0.0.255 [CEb2-ospf-1-area-0.0.0.0] quit [CEb2-ospf-1] quit Verifying the configuration # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 1. [PE1] display multicast-domain default-group local MD local default-group information: Group address Source address...

  • Page 280

    which PE devices to VPN instance a. VLAN-interface 2 and Loopback 1 belong to the public belong network instance. • PE 2: VLAN-interface 2, VLAN-interface 3, Loopback 1, and Loopback 2 belong to the public network instance. • PE 3: VLAN-interface 3, VLAN-interface 4, Loopback 1, and Loopback 2 belong to the public network instance.

  • Page 281

    Figure 85 Network diagram Loop0 Loop0 CE a1 CE b2 Vlan-int10 Vlan-int40 VPN a VPN b Vlan-int2 Vlan-int4 Vlan-int3 Vlan-int3 PE 1 PE 4 Vlan-int2 Vlan-int4 PE 2 PE 3 ASBR ASBR AS 100 AS 200 Vlan-int20 Vlan-int30 CE b1 CE a2 VPN b VPN a...

  • Page 282

    [PE1] router id 1.1.1.1 [PE1] multicast routing [PE1-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE1] service-loopback group 1 type multicast-tunnel # Assign HundredGigE 1/0/4 to service loopback group 1. The interface does not belong to VLAN 2, VLAN 11, or VLAN 12.

  • Page 283

    # Specify the default-group, the MD source interface, and the data-group range for VPN instance b. [PE1-md-b-ipv4] default-group 239.4.4.4 [PE1-md-b-ipv4] source loopback 1 [PE1-md-b-ivp4] data-group 225.4.4.0 28 [PE1-md-b-ipv4] quit [PE1-md-b] quit # Assign an IP address to VLAN-interface 2. [PE1] interface vlan-interface 2 [PE1-Vlan-interface2] ip address 10.10.1.1 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 2.

  • Page 284

    [PE1-bgp-default-ipv4-a] quit [PE1-bgp-default-a] quit [PE1–bgp-default] ip vpn-instance b [PE1-bgp-default-b] address-family ipv4 [PE1-bgp-default-ipv4-b] import-route ospf 3 [PE1-bgp-default-ipv4-b] import-route direct [PE1-bgp-default-ipv4-b] quit [PE1-bgp-default-b] quit [PE1–bgp-default] address-family ipv4 [PE1-bgp-default-ipv4] peer pe1-pe2 enable [PE1-bgp-default-ipv4] peer pe1-pe2 label-route-capability [PE1-bgp-default-ipv4] quit [PE1–bgp-default] address-family vpnv4 [PE1–bgp-default-vpnv4] peer pe1-pe4 enable [PE1–bgp-default-vpnv4] quit [PE1–bgp-default] quit # Configure OSPF.

  • Page 285

    # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 2. [PE2-Vlan-interface2] pim sm [PE2-Vlan-interface2] mpls enable [PE2-Vlan-interface2] mpls ldp enable [PE2-Vlan-interface2] quit # Assign an IP address to VLAN-interface 3. [PE2] interface vlan-interface 3 [PE2-Vlan-interface3] ip address 192.168.1.1 24 # Enable PIM-SM and MPLS on VLAN-interface 3. [PE2-Vlan-interface3] pim sm [PE2-Vlan-interface3] mpls enable [PE2-Vlan-interface3] quit...

  • Page 286

    [PE2-bgp-default-ipv4] peer pe2-pe1 label-route-capability [PE2-bgp-default-ipv4] peer pe2-pe3 enable [PE2-bgp-default-ipv4] peer pe2-pe3 route-policy map1 export [PE2-bgp-default-ipv4] peer pe2-pe3 label-route-capability [PE2-bgp-default-ipv4] import-route ospf 1 [PE2-bgp-default-ipv4] quit [PE2–bgp-default] quit # Configure OSPF. [PE2] ospf 1 [PE2-ospf-1] area 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 11.11.11.11 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 10.10.1.0 0.0.0.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit...

  • Page 287

    [PE3-LoopBack2] ip address 22.22.22.22 32 [PE3-LoopBack2] pim sm [PE3-LoopBack2] quit # Configure Loopback 2 as a C-BSR and a C-RP. [PE3] pim [PE3-pim] c-bsr 22.22.22.22 [PE3-pim] c-rp 22.22.22.22 [PE3-pim] quit # Configure VLAN-interface 3 as a PIM-SM domain border. [PE3] interface vlan-interface 3 [PE3-Vlan-interface3] pim bsr-boundary [PE3-Vlan-interface3] quit # Establish an MSDP peering relationship.

  • Page 288

    [PE4] multicast routing [PE4-mrib] quit # Create service loopback group 1, and specify the multicast tunnel service for the group. [PE4] service-loopback group 1 type multicast-tunnel # Assign HundredGigE 1/0/4 to service loopback group 1. The interface does not belong to VLAN 4, VLAN 13, or VLAN 14.

  • Page 289

    [PE4-md-b-ipv4] default-group 239.4.4.4 [PE4-md-b-ipv4] source loopback 1 [PE4-md-b-ivp4] data-group 225.4.4.0 28 [PE4-md-b-ipv4] quit [PE4-md-b] quit # Assign an IP address to VLAN-interface 4. [PE4] interface vlan-interface 4 [PE4-Vlan-interface4] ip address 10.10.2.2 24 # Enable PIM-SM, MPLS, and IPv4 LDP on VLAN-interface 4. [PE4-Vlan-interface4] pim sm [PE4-Vlan-interface4] mpls enable [PE4-Vlan-interface4] mpls ldp enable...

  • Page 290

    [PE4–bgp-default] ip vpn-instance b [PE4-bgp-default-b] address-family ipv4 [PE4-bgp-default-ipv4-b] import-route ospf 3 [PE4-bgp-default-ipv4-b] import-route direct [PE4-bgp-default-ipv4-b] quit [PE4-bgp-default-b] quit [PE4–bgp-default] address-family ipv4 [PE4-bgp-default-ipv4] peer pe4-pe3 enable [PE4-bgp-default-ipv4] peer pe4-pe3 label-route-capability [PE4-bgp-default-ipv4] quit [PE4–bgp-default] address-family vpnv4 [PE4–bgp-default-vpnv4] peer pe4-pe1 enable [PE4–bgp-default-vpnv4] quit [PE4–bgp-default] quit # Configure OSPF.

  • Page 291

    # Assign an IP address to Loopback 1, and enable PIM-SM on the interface. [CEa1] interface loopback 1 [CEa1-LoopBack1] ip address 2.2.2.2 32 [CEa1-LoopBack1] pim sm [CEa1-LoopBack1] quit # Configure Loopback 1 as a C-BSR and a C-RP. [CEa1] pim [CEa1-pim] c-bsr 2.2.2.2 [CEa1-pim] c-rp 2.2.2.2 [CEa1-pim] quit...

  • Page 292

    [CEa2-Vlan-interface30] ip address 10.11.7.1 24 [CEa2-Vlan-interface30] igmp enable [CEa2-Vlan-interface30] quit # Assign an IP address to VLAN-interface 13, and enable PIM-SM on the interface. [CEa2] interface vlan-interface 13 [CEa2-Vlan-interface13] ip address 10.11.3.2 24 [CEa2-Vlan-interface13] pim sm [CEa2-Vlan-interface13] quit # Configure OSPF. [CEa2] ospf 1 [CEa2-ospf-1] area 0.0.0.0 [CEa2-ospf-1-area-0.0.0.0] network 10.11.3.0 0.0.0.255...

  • Page 293: Troubleshooting Md Vpn

    [CEb2-ospf-1] quit Verifying the configuration # Display information about the local default-group for IPv4 multicast transmission in each VPN instance on PE 1. [PE1] display multicast-domain default-group local MD local default-group information: Group address Source address Interface VPN instance 239.1.1.1 1.1.1.1 MTunnel0 239.4.4.4...

  • Page 294

    Solution To resolve the problem: Use the display pim bsr-info command to verify that the BSR information exists on the public network and VPN instance. If it does not, verify that a unicast route exists to the BSR. Use the display pim rp-info command to examine the RP information. If no RP information is available, verify that a unicast route exists to the RP.

  • Page 295: Configuring Mld Snooping

    Configuring MLD snooping Overview MLD snooping runs on a Layer 2 device as an IPv6 multicast constraining mechanism to improve multicast forwarding efficiency. It creates Layer 2 multicast forwarding entries from MLD messages that are exchanged between the hosts and the router. As shown in Figure 86, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...

  • Page 296

    Figure 87 MLD snooping ports Receiver Router A Switch A HGE1/0/1 HGE1/0/2 Host A HGE1/0/3 Host B Receiver HGE1/0/1 Source HGE1/0/2 Host C Switch B Router port Member port IPv6 multicast packets Host D Router ports On an MLD snooping Layer 2 device, the ports toward Layer 3 multicast devices are called router ports.

  • Page 297: How Mld Snooping Works

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

  • Page 298: Mld Snooping Proxying

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

  • Page 299

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

  • Page 300: Mld Snooping Configuration Task List For Vsis

    • (Optional.) Enabling fast-leave processing • (Optional.) Disabling a port from becoming a dynamic router port Configuring the MLD snooping querier: • (Optional.) Enabling the MLD snooping querier • (Optional.) Configuring parameters for MLD general queries and responses (Optional.) Enabling MLD snooping proxying Configuring parameters for MLD messages: •...

  • Page 301: Configuring Basic Mld Snooping Features

    Configuring basic MLD snooping features Before you configure basic MLD snooping features, complete the following tasks: • Configure VLANs or VSIs. • Determine the MLD snooping version. • Determine the maximum number of MLD snooping forwarding entries. • Determine the MLD last listener query interval. Enabling MLD snooping When you enable MLD snooping, follow these restrictions and guidelines: •...

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

    • MLDv2 snooping can process MLDv1 and MLDv2 messages. If you change MLDv2 snooping to MLDv1 snooping, the system performs the following actions: • Clears all MLD snooping forwarding entries that are dynamically created. • Keeps static MLDv2 snooping forwarding entries (*, G). •...

  • Page 303: Configuring Static Ipv6 Multicast Mac Address Entries

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

  • Page 304: Configuring Mld Snooping Port Features

    Configuration restrictions and guidelines When you set the MLD last listener query interval, follow these restrictions and guidelines: • The Layer 2 device does not send an MLD multicast-address-specific query if it receives an MLD done message from a port enabled with fast-leave processing. •...

  • Page 305

    setting the MLD last listener query interval on the Layer 2 device, see "Setting the MLD last listener query interval." • You can set the timers globally for all VLANs and VSIs in MLD-snooping view, for a VSI in VSI view, or for a VLAN in VLAN view.

  • Page 306

    port. member port: member port or a static router mld-snooping port. static-group ipv6-group-add ress [ source-ip ipv6-source -address ] vlan vlan-id • Configure the port as a static router port: mld-snooping static-router-port vlan vlan 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: •...

  • Page 307

    Enable fast-leave processing By default, fast-leave processing fast-leave [ vlan vlan-list ] globally. is disabled globally. Enabling fast-leave processing on a port Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface- interface view or Layer 2 number aggregate interface view.

  • Page 308: Enabling The Mld Snooping Querier

    • Determine the MLD general query interval. • Determine the maximum response time for MLD general queries. Enabling the MLD snooping querier This feature enables the device 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.

  • Page 309: Enabling Mld Snooping Proxying

    configuration takes priority over the global configuration. For a VLAN, the VLAN-specific configuration takes priority over the global configuration. Configuring parameters for MLD general queries and responses globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the maximum response time for MLD general max-response-time seconds The default setting is 10 seconds.

  • Page 310: Configuring Source Ipv6 Addresses For Mld Messages

    • Determine the source IPv6 address of MLD reports. • Determine the source IPv6 address of MLD done messages. • Determine the 802.1p priority of MLD messages. Configuring source IPv6 addresses for MLD messages You can change the source IPv6 address of the MLD queries sent by an MLD snooping querier. This configuration might affect MLD querier election within the subnet.

  • Page 311

    current VLAN interface does not have an IPv6 link-local address, the source IPv6 address is FE80::02FF:FFFF:FE00:0001. Configuring the source IPv6 address for MLD messages in a VSI Step Command Remarks Enter system view. system-view Enter VLAN view. vsi vsi-name By default, the source IPv6 address of MLD general queries is the IPv6 link-local address of the Configure the source IPv6...

  • Page 312: Setting The 802.1p Priority For Mld Messages

    Setting the 802.1p priority for MLD messages When congestion occurs on outgoing ports of the Layer 2 device, it forwards MLD messages in their 802.1p priority order, from highest to lowest. You can assign a higher 802.1p priority to MLD messages that are created or forwarded by the device.

  • Page 313: Enabling Ipv6 Multicast Source Port Filtering

    • You can configure an IPv6 multicast group policy globally for all ports in MLD-snooping view or for a port in interface view. For a port, the port-specific configuration takes priority over the global configuration. Configuring an IPv6 multicast group policy globally Step Command Remarks...

  • Page 314: Enabling Dropping Unknown Ipv6 Multicast Data

    Enabling dropping unknown IPv6 multicast data Unknown IPv6 multicast data refers to IPv6 multicast data for which no forwarding entries exist in the MLD snooping forwarding table. This feature enables the device only to forward unknown IPv6 multicast data to the router port. If the device does not have a router port, unknown IPv6 multicast data will be dropped.

  • Page 315: Enabling Ipv6 Multicast Group Replacement

    Configuration procedure To set the maximum number of IPv6 multicast groups on a port: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface- interface view or Layer 2 number aggregate interface view. Set the maximum number of By default, no limit is placed on mld-snooping group-limit limit IPv6 multicast groups on the...

  • Page 316: Displaying And Maintaining Mld Snooping

    Enabling host tracking globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Enable host tracking By default, host tracking is host-tracking globally. disabled globally. Enabling host tracking in a VLAN Step Command Remarks Enter system view. system-view Enter VLAN view.

  • Page 317: Mld Snooping Configuration Examples

    Display statistics for the MLD messages and IPv6 PIM hello display mld-snooping statistics messages learned through MLD snooping. reset ipv6 l2-multicast fast-forwarding cache [ vlan vlan-id ] Clear Layer 2 IPv6 multicast fast { { ipv6-source-address | ipv6-group-address } * | all } forwarding entries.

  • Page 318

    Figure 89 Network diagram Receiver Host A Source Receiver HGE1/0/4 HGE1/0/1 HGE1/0/2 HGE1/0/1 HGE1/0/3 1::2/64 2001::1/64 Switch A Host B HGE1/0/2 Router A 1::1/64 MLD querier Host C VLAN 100 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 89.

  • Page 319

    [SwitchA] acl ipv6 basic 2001 [SwitchA-acl-ipv6-basic-2001] rule permit source ff1e::101 128 [SwitchA-acl-ipv6-basic-2001] quit [SwitchA] mld-snooping [SwitchA–mld-snooping] group-policy 2001 vlan 100 [SwitchA–mld-snooping] quit # Configure HundredGigE 1/0/3 and HundredGigE 1/0/4 as simulated member hosts to join IPv6 multicast group FF1E::101. [SwitchA] interface hundredgige 1/0/3 [SwitchA-HundredGigE1/0/3] mld-snooping host-join ff1e::101 vlan 100 [SwitchA-HundredGigE1/0/3] quit [SwitchA] interface hundredgige 1/0/4...

  • Page 320

    the process. For more information about the STP, see Layer 2—LAN Switching Configuration Guide. Configure HundredGigE 1/0/3 on Switch A as a static router port. Then, IPv6 multicast data can flow to the receivers nearly uninterrupted along the path of Switch A—Switch C when the path of Switch A—Switch B—Switch C is blocked.

  • Page 321

    [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/3 # Enable MLD snooping for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] quit # Configure HundredGigE 1/0/3 as a static router port. [SwitchA] interface hundredgige 1/0/3 [SwitchA-HundredGigE1/0/3] mld-snooping static-router-port vlan 100 [SwitchA-HundredGigE1/0/3] quit Configure Switch B: # Enable MLD snooping globally.

  • Page 322: Mld Snooping Querier Configuration Example (for Vlans)

    # Display brief information about static MLD snooping group entries in VLAN 100 on Switch C. [SwitchC] display mld-snooping static-group vlan 100 Total 1 entries). VLAN 100: Total 1 entries). (::, FF1E::101) Host ports (2 in total): HGE1/0/3 HGE1/0/5 The output shows that HundredGigE 1/0/3 and HundredGigE 1/0/5 on Switch C have become static member ports of IPv6 multicast group FF1E::101.

  • Page 323

    [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/3 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/3 # Enable MLD snooping, and enable dropping unknown IPv6 multicast data for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] mld-snooping drop-unknown # Configure Switch A as the MLD snooping querier.

  • Page 324: Mld Snooping Proxying Configuration Example (for Vlans)

    Verifying the configuration # Display statistics for MLD messages and IPv6 PIM hello messages learned through MLD snooping on Switch B. [SwitchB] display mld-snooping statistics Received MLD general queries: Received MLDv1 specific queries: Received MLDv1 reports: Received MLD dones: Sent MLDv1 specific queries: Received MLDv2 reports: Received MLDv2 reports with right and wrong records:...

  • Page 325

    Configuration procedure Assign an IPv6 address and subnet mask to each interface, as shown in Figure 92. (Details not shown.) Configure Router A: # Enable IPv6 multicast routing. <RouterA> system-view [RouterA] ipv6 multicast routing [RouterA-mrib6] quit # Enable MLD and IPv6 PIM-DM on HundredGigE 1/0/1. [RouterA] interface hundredgige 1/0/1 [RouterA-HundredGigE1/0/1] mld enable [RouterA-HundredGigE1/0/1] ipv6 pim dm...

  • Page 326: Mld Snooping Configuration Example (for Vsis)

    Last reporter: FE80::2FF:FFFF:FE00:1 Uptime: 00:00:31 Expires: 00:03:48 # Display brief information about dynamic MLD snooping group entries on Switch A. [SwitchA] display mld-snooping group Total 1 entries. VLAN 100: Total 1 entries. (::, FF1E::101) Host ports (1 in total): HGE1/0/3 ( 00:01:23 ) The output shows that HundredGigE 1/0/4 (connected to Host A) has been deleted from the entry of IPv6 multicast groups (FF1E::101).

  • Page 327

    Configuration procedure Assign an IP address and subnet mask to each interface on the VPLS network, as shown Table 23. (Details not shown.) Configure OSPF on the switches on the VPLS network. (Details not shown.) Configure CE 1: # Enable MLD snooping globally. <CE1>...

  • Page 328

    [CE3-vlan100] mld-snooping enable [CE3-vlan100] mld-snooping drop-unknown # Configure HundredGigE 1/0/1 as a trunk port, and assign it to VLAN 100. [CE3] interface hundredgige 1/0/1 [CE3-HundredGigE1/0/1] port link-type trunk [CE3-HundredGigE1/0/1] port trunk permit vlan 100 [CE3-HundredGigE1/0/1] quit Configure PE 1: # Configure the LSR ID as 1.1.1.1 for the local node, and enable L2VPN and LDP. <PE1>...

  • Page 329

    Configure PE 2: # Configure the LSR ID as 2.2.2.2 for the local node, and enable L2VPN and LDP. <PE2> system-view [PE2] mpls lsr-id 2.2.2.2 [PE2] l2vpn enable [PE2] mpls ldp [PE2-ldp] quit # Enable MPLS and LDP on VLAN-interface 101 and VLAN-interface 103. [PE2] interface vlan-interface 101 [PE2-Vlan-interface101] mpls enable [PE2-Vlan-interface101] mpls ldp enable...

  • Page 330

    [PE3] interface vlan-interface 102 [PE3-Vlan-interface102] mpls enable [PE3-Vlan-interface102] mpls ldp enable [PE3-Vlan-interface102] quit [PE3] interface vlan-interface 103 [PE3-Vlan-interface103] mpls enable [PE3-Vlan-interface103] mpls ldp enable [PE3-Vlan-interface103] quit # Create a VSI named aaa, specify the VSI to establish PWs statically, and configure PWs for it. [PE3] vsi aaa [PE3-vsi-aaa] pwsignaling static [PE3-vsi-aaa-static] peer 1.1.1.1 pw-id 3 in-label 200 out-label 200...

  • Page 331

    [PE1] display mld-snooping router-port vsi aaa verbose VSI aaa: Router slots (0 in total): Router ports (1 in total): GE1/0/1 ( Link ID 0) (00:01:46) VLAN pairs (1 in total): Outer VLAN 100 Inner VLAN 0 (00:01:46) # Display detailed information about dynamic MLD snooping group entries for VSI aaa on PE 2. [PE2] display mld-snooping group vsi aaa verbose Total 1 entries.

  • Page 332: Mld Snooping Configuration Example (for Vxlans)

    VLAN pairs (1 in total): Outer VLAN 100 Inner VLAN 0 (00:01:24) MLD snooping configuration example (for VXLANs) Network requirements As shown in Figure • VXLAN 10 provides Layer 2 connectivity for VM 1, VM 2, and VM 3 across the network sites. •...

  • Page 333

    [SwitchA] vsi vpna [SwitchA-vsi-vpna] vxlan 10 [SwitchA-vsi-vpna-vxlan-10] quit [SwitchA-vsi-vpna] quit # Enable MLD snooping globally. [SwitchA] mld-snooping [SwitchA -mld-snooping] quit # Enable MLD snooping and dropping unknown IPv6 multicast data packets for VSI vpna. [SwitchA] vsi vpna [SwitchA-vsi-vpna] mld-snooping enable [SwitchA-vsi-vpna] mld-snooping drop-unknown [SwitchA-vsi-vpna] quit # Assign an IP address to Loopback 0.

  • Page 334

    Configure Switch B: # Enable L2VPN. <SwitchB> system-view [SwitchB] l2vpn enable # Enable Layer 2 forwarding for VXLANs. [SwitchB] undo vxlan ip-forwarding # Create a VSI named vpna, and create VXLAN 10. [SwitchB] vsi vpna [SwitchB-vsi-vpna] vxlan 10 [SwitchB-vsi-vpna-vxlan-10] quit [SwitchB-vsi-vpna] quit # Enable MLD snooping globally.

  • Page 335

    [SwitchB] interface hundredgige 1/0/1 [SwitchB-HundredGigE1/0/1] service-instance 1000 [SwitchB-HundredGigE1/0/1-srv1000] encapsulation s-vid 2 # Map Ethernet service instance 1000 to VSI vpna. [SwitchB-HundredGigE1/0/1-srv1000] xconnect vsi vpna [SwitchB-HundredGigE1/0/1-srv1000] quit [SwitchB-HundredGigE1/0/1] quit Configure Switch C: # Enable L2VPN. <SwitchC> system-view [SwitchC] l2vpn enable # Enable Layer 2 forwarding for VXLANs. [SwitchC] undo vxlan ip-forwarding # Create a VSI named vpna, and create VXLAN 10.

  • Page 336: Troubleshooting Mld Snooping

    The source address and destination address of the tunnel interface are 3.3.3.3 and 2.2.2.2,  respectively. [SwitchC] interface tunnel 3 mode vxlan [SwitchC-Tunnel3] source 3.3.3.3 [SwitchC-Tunnel3] destination 2.2.2.2 [SwitchC-Tunnel3] quit # Assign Tunnel 1 and Tunnel 3 to VXLAN 10. [SwitchC] vsi vpna [SwitchC-vsi-vpna] vxlan 10 [SwitchC-vsi-vpna-vxlan-10] tunnel 1...

  • Page 337: Ipv6 Multicast Group Policy Does Not Work

    If MLD snooping is not enabled, use the mld-snooping command in system view to enable MLD snooping globally. Then, use the mld-snooping enable command in VLAN view or VSI view to enable MLD snooping for the VLAN or VSI. If MLD snooping is enabled globally but not enabled for the VLAN or VSI, use the mld-snooping enable command in VLAN view or VSI view to enable MLD snooping for the VLAN or VSI.

  • Page 338: 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 339

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

  • Page 340: Displaying And Maintaining Ipv6 Pim Snooping

    The default setting is 105 (Optional.) Set the aging seconds. time for global neighbor ipv6 pim-snooping A global neighbor port is a Layer ports on the new master graceful-restart 2 aggregate interface, AC device after a neighbor-aging-time seconds interface, N-PW interface, or master/subordinate U-PW interface that acts as a switchover.

  • Page 341

    To make sure Switch A forwards IPv6 PIM protocol packets and IPv6 multicast data packets only to routers that are connected to receivers, perform the following tasks: • On Switch A, configure MLD snooping and IPv6 PIM snooping. • On all IPv6 PIM routers connected to Switch A, set the maximum size of a join or prune message to 1400 bytes, which is less than the path MTU.

  • Page 342

    <RouterB> system-view [RouterB] ipv6 multicast routing [RouterB-mrib6] quit # Enable IPv6 PIM-SM on each interface. [RouterB] interface hundredgige 1/0/1 [RouterB-HundredGigE1/0/1] ipv6 pim sm [RouterB-HundredGigE1/0/1] quit [RouterB] interface hundredgige 1/0/2 [RouterB-HundredGigE1/0/2] ipv6 pim sm [RouterB-HundredGigE1/0/2] quit # Set the maximum size of a join or prune message to 1400 bytes. [RouterB] ipv6 pim [RouterB-pim6] jp-pkt-size 1400 Configure Router C:...

  • Page 343

    <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, and assign HundredGigE 1/0/1 through HundredGigE 1/0/4 to the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port hundredgige 1/0/1 to hundredgige 1/0/4 # Enable MLD snooping and IPv6 PIM snooping for VLAN 100. [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] ipv6 pim-snooping enable [SwitchA-vlan100] quit...

  • Page 344: Troubleshooting Ipv6 Pim Snooping

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

  • Page 345: Configuring Ipv6 Multicast Vlans

    Configuring IPv6 multicast VLANs Overview As shown in Figure 97, Host A, Host B, and Host C are in different VLANs and the same IPv6 multicast group. When Switch A (Layer 3 device) receives IPv6 multicast data for that group, it forwards three copies of the data to Switch B (Layer 2 device).

  • Page 346

    Figure 98 Sub-VLAN-based multicast VLAN IPv6 Multicast packets VLAN 10 (IPv6 Multicast VLAN) VLAN 2 VLAN 2 Receiver VLAN 3 Host A VLAN 4 VLAN 3 Receiver Host B Source Switch A Switch B MLD querier VLAN 4 Receiver Host C MLD snooping manages router ports in the IPv6 multicast VLAN and member ports in each sub-VLAN.

  • Page 347: Ipv6 Multicast Vlan Configuration Task List

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

  • Page 348: Configuring A Port-based Ipv6 Multicast Vlan

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

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

    Configuration restrictions and guidelines When you perform this task, follow these restrictions and guidelines: • The VLAN to be configured as an IPv6 multicast VLAN must exist. • A port can belong to only one IPv6 multicast VLAN. Configuration procedure To assign user ports to an IPv6 multicast VLAN in IPv6 multicast VLAN view: Step Command...

  • Page 350: Displaying And Maintaining Ipv6 Multicast Vlans

    Displaying and maintaining IPv6 multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about IPv6 display ipv6 multicast-vlan [ vlan-id ] multicast VLANs. Display information about information display ipv6 multicast-vlan group [ ipv6-source-address about IPv6 multicast group entries in | ipv6-group-address | slot slot-number | verbose | vlan vlan-id ] * IPv6 multicast VLANs.

  • Page 351

    Figure 100 Network diagram Source MLD querier HGE1/0/2 Vlan-int20 Switch A 1::2/64 HGE1/0/1 1::1/64 Vlan-int10 2001::1/64 HGE1/0/1 Switch B HGE1/0/2 HGE1/0/4 HGE1/0/3 Receiver Receiver Receiver Host A Host B Host C VLAN 2 VLAN 3 VLAN 4 Configuration procedure Configure Switch A: # Enable IPv6 multicast routing.

  • Page 352

    Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 2, assign HundredGigE 1/0/2 to the VLAN, and enable MLD snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port hundredgige 1/0/2 [SwitchB-vlan2] mld-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign HundredGigE 1/0/3 to the VLAN, and enable MLD snooping for the VLAN.

  • Page 353: Port-based Ipv6 Multicast Vlan Configuration Example

    [SwitchB] display ipv6 multicast-vlan group Total 1 entries. IPv6 multicast VLAN 10: Total 1 entries. (::, FF1E::101) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that IPv6 multicast group FF1E::101 belongs to IPv6 multicast VLAN 10. IPv6 multicast VLAN 10 contains sub-VLANs VLAN 2 through VLAN 4.

  • Page 354

    [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Create VLAN 20, and assign HundredGigE 1/0/2 to the VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port hundredgige 1/0/2 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM on the interface. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 1::2 64 [SwitchA-Vlan-interface20] ipv6 pim dm...

  • Page 355

    # Assign HundredGigE 1/0/2 to VLAN 2 and VLAN 10 as an untagged VLAN member. [SwitchB-HundredGigE1/0/2] port hybrid vlan 2 untagged [SwitchB-HundredGigE1/0/2] port hybrid vlan 10 untagged [SwitchB-HundredGigE1/0/2] quit # Configure HundredGigE 1/0/3 as a hybrid port, and configure VLAN 3 as the PVID of the hybrid port.

  • Page 356

    (::, FF1E::101) Host slots (0 in total): Host ports (3 in total): HGE1/0/2 (00:03:23) HGE1/0/3 (00:04:07) HGE1/0/4 (00:04:16) The output shows that MLD snooping maintains the user ports in the multicast VLAN (VLAN 10). Switch B will forward the IPv6 multicast data of VLAN 10 through these user ports.

  • Page 357: 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 358

    packet as the incoming interface of the (S, G) entry. After the router receives another (S, G) packet, it looks up its IPv6 multicast forwarding table for a matching (S, G) entry: • If no match is found, the router first determines the RPF route back to the packet source. Then, it creates a forwarding entry with the RPF interface as the incoming interface and performs one of the following tasks: If the receiving interface is the RPF interface, the RPF check succeeds and the router...

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

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

  • Page 361: Enabling Ipv6 Multicast Forwarding Between Sub-vlans Of A Super Vlan

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

  • Page 362

    information. oup [ ipv6-group-address [ prefix-length ] ] | scope [ scope-id ] } [ interface interface-type interface-number ] display ipv6 multicast Display IPv6 multicast fast forwarding [ vpn-instance vpn-instance-name ] fast-forwarding entries. cache [ ipv6-source-address | ipv6-group-address ] * [ slot slot-number ] display ipv6 multicast Display DF information.

  • Page 363: Ipv6 Multicast Routing And Forwarding Configuration Examples

    IPv6 multicast routing and forwarding configuration examples IPv6 multicast forwarding over a GRE tunnel Network requirements As shown in Figure 104: • IPv6 multicast routing and IPv6 PIM-DM are enabled on Switch A and Switch C. • Switch B does not support IPv6 multicast. •...

  • Page 364

    [SwitchA-Tunnel2] source 2001::1 [SwitchA-Tunnel2] destination 3001::2 [SwitchA-Tunnel2] quit # On Switch C, create service loopback group 1, and specify the unicast tunnel service for the group. <SwitchC> system-view [SwitchC] service-loopback group 1 type tunnel # Assign HundredGigE 1/0/3 to service loopback group 1. (HundredGigE 1/0/3 does not belong to VLAN 200 or VLAN 102.) [SwitchC] interface hundredgige 1/0/3 [SwitchC-HundredGigE1/0/3] port service-loopback group 1...

  • Page 365

    On Switch C, configure a static IPv6 route with the destination address 1001::1/64 and the outgoing interface Tunnel 2. [SwitchC] ipv6 route-static 1001::1 64 tunnel 2 Verifying the configuration # Send an MLD report from Receiver to join the IPv6 multicast group FF1E::101. (Details not shown.) # Send IPv6 multicast data from Source to the IPv6 multicast group FF1E::101.

  • Page 366: Configuring Mld

    Configuring MLD Overview Multicast Listener Discovery (MLD) establishes and maintains IPv6 multicast group memberships between a Layer 3 multicast device and the hosts on the directly connected subnet. MLD has the following versions: • MLDv1 (defined by RFC 2710), which is derived from IGMPv2. •...

  • Page 367

    Joining an IPv6 multicast group Figure 105 MLD queries and reports IPv6 network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report As shown in Figure 105, Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1.

  • Page 368: 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 369: Mld Ssm Mapping

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

  • Page 370: Mld Proxying

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

  • Page 371: Mld Configuration Task List

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

  • Page 372: Specifying An Mld Version

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

  • Page 373: Adjusting Mld Performance

    To configure an IPv6 multicast group policy: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, no IPv6 multicast group policy exists on an Configure an IPv6 multicast group-policy ipv6-acl-number [ v interface. Hosts attached to the group policy on the interface.

  • Page 374

    • You can configure the MLD query and response parameters globally for all interfaces in MLD view or for an interface in interface view. For an interface, the interface-specific configuration takes priority over the global configuration. • To avoid frequent MLD querier changes, set the MLD other querier present timer greater than the MLD general query interval.

  • Page 375

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

  • Page 376

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

  • Page 377: Enabling Ipv6 Multicast Forwarding On A Non-querier Interface

    interface interface-type Enter interface view. interface-number By default, MLD proxying is Enable MLD proxying. mld proxy enable disabled. Enabling IPv6 multicast forwarding on a non-querier interface Typically, only MLD queriers can forward IPv6 multicast traffic and non-queriers cannot. This prevents IPv6 multicast data from being repeatedly forwarded. If a router interface on the MLD proxy failed the querier election, enable IPv6 multicast forwarding on the interface to forward IPv6 multicast data to downstream receivers.

  • Page 378: Displaying And Maintaining Mld

    active/standby switchover occurs. Use this feature to prevent an active/standby switchover from affecting the IPv6 multicast service. To enable MLD NSR: Step Command Remarks Enter system view. system-view By default, MLD NSR is Enable MLD NSR. mld non-stop-routing disabled. Displaying and maintaining MLD CAUTION: The reset mld group command might cause IPv6 multicast data transmission failures.

  • Page 379

    • VOD streams are sent to receiver hosts in multicast. Receiver hosts of different organizations form stub networks N1 and N2. Host A and Host C are multicast receiver hosts in N1 and N2, respectively. • MLDv1 runs between Switch A and N1, and between the other two switches (Switch B and Switch C) and N2.

  • Page 380

    # On Switch B, enable IPv6 multicast routing. <SwitchB> system-view [SwitchB] ipv6 multicast routing [SwitchB-mrib6] quit # Enable MLD on VLAN-interface 200. [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] mld enable [SwitchB-Vlan-interface200] quit # Enable IPv6 PIM-DM on VLAN-interface 201. [SwitchB] interface vlan-interface 201 [SwitchB-Vlan-interface201] ipv6 pim dm [SwitchB-Vlan-interface201] quit # On Switch C, enable IPv6 multicast routing.

  • Page 381: Mld Ssm Mapping Configuration Example

    MLD SSM mapping configuration example Network requirements As shown in Figure 110: • OSPFv3 runs on the network. • The IPv6 PIM-SM domain uses both the ASM model and SSM model for IPv6 multicast delivery. VLAN-interface 104 of Router D acts as the C-BSR and C-RP. The SSM group range is FF3E::/64.

  • Page 382

    # On Switch D, enable IPv6 multicast routing. <SwitchD> system-view [SwitchD] ipv6 multicast routing [SwitchD-mrib6] quit # Enable MLDv2 on the receiver-side interface (VLAN-interface 400). [SwitchD] interface vlan-interface 400 [SwitchD-Vlan-interface400] mld enable [SwitchD-Vlan-interface400] mld version 2 [SwitchD-Vlan-interface400] quit # Enable IPv6 PIM-SM on the other interfaces. [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] ipv6 pim sm [SwitchD-Vlan-interface103] quit...

  • Page 383: Mld Proxying Configuration Example

    [SwitchD-mld] ssm-mapping 1001::1 2000 [SwitchD-mld] ssm-mapping 3001::1 2000 [SwitchD-mld] quit Verifying the configuration # Display MLD SSM mappings for IPv6 multicast group FF3E::101 on Switch D. [SwitchD] display mld ssm-mapping ff3e::101 Group: FF3E::101 Source list: 1001::1 3001::1 # On Switch D, display information about MLD multicast groups that hosts have dynamically joined. [SwitchD] display mld group MLD groups in total: 1 Vlan-interface400(FE80::101):...

  • Page 384

    • IPv6 PIM-DM runs on the core network. • Host A and Host C on the stub network receive VOD information destined to IPv6 multicast group FF3E::101. Configure the MLD proxying feature on Switch B so that Switch B can maintain group memberships and forward IPv6 multicast traffic without running IPv6 PIM-DM.

  • Page 385: Troubleshooting Mld

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

  • Page 386: 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 387

    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 388: Ipv6 Pim-sm Overview

    Figure 113 Assert mechanism Router A Router B Ethernet Assert message IPv6 multicast packets Receiver Router C As shown in Figure 113, 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 389

    IMPORTANT: MLD must be enabled on the device that acts as the receiver-side DR. Otherwise, the receiver hosts attached to the DR cannot join any IPv6 multicast groups. For more information about MLD, see "Configuring MLD." Figure 114 DR election Receiver Source Receiver...

  • Page 390

    As shown in Figure 115, each C-RP periodically unicasts its advertisement messages (C-RP-Adv messages) to the BSR. An advertisement message contains the address of the advertising C-RP and the IPv6 multicast group range to which it is designated. The BSR collects these advertisement messages and organizes the C-RP information into an RP-set, which is a database of mappings between IPv6 multicast groups and RPs.

  • Page 391

    multicast source registers with the closest RP or a receiver-side DR joins the closest RP to implement source information synchronization. Anycast RP has the following benefits: • Optimal RP path—An IPv6 multicast source registers with the closest RP to build an optimal SPT.

  • Page 392

    RPT building Figure 117 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 117, 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 393

    Figure 118 IPv6 multicast source registration Host A Source Receiver Host B Server Receiver Join message Register message Host C IPv6 multicast packets As shown in Figure 118, the IPv6 multicast source registers with the RP as follows: The IPv6 multicast source S sends the first multicast packet to the IPv6 multicast group G. When receiving the multicast packet, the source-side DR that directly connects to the IPv6 multicast source encapsulates the packet into a register message and unicasts the message to the RP.

  • Page 394: Ipv6 Bidir-pim Overview

    If the RP receives IPv6 multicast traffic, it sends an (S, G) source-specific join message toward the IPv6 multicast source. The routers along the path from the RP to the IPv6 multicast source constitute an SPT branch. The subsequent IPv6 multicast data is forwarded to the RP along the SPT without being encapsulated into register messages.

  • Page 395

    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 396

    Figure 120 RPT building at the receiver side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Join message Receiver-side RPT IPv6 Multicast packets Host C As shown in Figure 120, 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 397: Ipv6 Administrative Scoping Overview

    Figure 121 RPT building at the IPv6 multicast source side Source Receiver Host A Server B Source Receiver Host B Server A Receiver Source-side RPT IPv6 Multicast packets Host C As shown in Figure 121, 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 398

    BSMs, of these IPv6 multicast groups cannot cross the boundary of the IPv6 admin-scoped zone for the group range. The IPv6 multicast group ranges to which different IPv6 admin-scoped zones are designated can have intersections. However, the IPv6 multicast groups in an IPv6 admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded as private group addresses.

  • Page 399: Ipv6 Pim-ssm Overview

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

  • Page 400: Relationship Among Ipv6 Pim Protocols

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

  • Page 401: Ipv6 Pim Support For Vpns

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

  • Page 402: Ipv6 Pim-dm Configuration Task List

    IPv6 PIM-DM configuration task list Tasks at a glance (Required.) Enabling IPv6 PIM-DM (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.) Configuring the 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 403

    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 404: 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 405

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

  • Page 406

    same C-RP policy on all C-BSRs in the IPv6 PIM-SM domain because every C-BSR might become the BSR. When you configure a C-RP, reserve a relatively large bandwidth between the C-RP and the other devices in the IPv6 PIM-SM domain. The device might use the BSR RP hash algorithm described in RFC 4601 or in RFC 2362 to calculate the RP for a multicast group.

  • Page 407

    Step Command Remarks Enter system view. system-view ipv6 pim Enter IPv6 PIM view. [ vpn-instance vpn-instance-name ] By default, Anycast RP is not configured. anycast-rp ipv6-anycast-rp-address Configure Anycast RP. You can repeat this command to ipv6-member-address add multiple RP member addresses to an Anycast RP set.

  • Page 408

    ipv6 pim Enter IPv6 PIM view. [ vpn-instance vpn-instance-name ] c-bsr ipv6-address [ scope scope-id ] Configure a C-BSR. By default, no C-BSRs exist. [ hash-length hash-length | priority priority ] * By default, no BSR policy exists, (Optional.) Configure a BSR bsr-policy ipv6-acl-number and all bootstrap messages are policy.

  • Page 409: Configuring Ipv6 Multicast Source Registration

    duplicated traffic. If all the devices have consistent routing information, you can disable the device from forwarding BSMs out of their incoming interfaces to reduce the duplicated traffic. To disable the device from forwarding BSMs out of their incoming interfaces: Step Command Remarks...

  • Page 410

    By default, no IPv6 register policy Configure an IPv6 PIM register-policy ipv6-acl-number exists, and all IPv6 register register policy. messages are regarded as legal. Configure the device to By default, the device calculates calculate the checksum register-whole-checksum the checksum based on the based on the entire register header of a register message.

  • Page 411

    (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 BIDIR-PIM, configure an IPv6 unicast routing protocol so that all devices in the domain can interoperate at the network layer. Enabling IPv6 BIDIR-PIM Because IPv6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM, you must enable IPv6 PIM-SM before enabling IPv6 BIDIR-PIM.

  • Page 412

    Configuring a static RP If only one dynamic RP exists on a network, you can configure a static RP to avoid communication interruption caused by single-point failures. The static RP can also avoid bandwidth waste due to frequent message exchange between C-RPs and the BSR. In IPv6 BIDIR-PIM, a static RP can be specified with an unassigned IPv6 address.

  • Page 413

    Step Command Remarks Enter system view. system-view Enter IPv6 PIM ipv6 pim [ vpn-instance vpn-instance-name ] view. Configure a C-RP c-rp ipv6-address [ advertisement-interval adv-interval to provide services By default, no C-RPs | { group-policy ipv6-acl-number | scope scope-id } for IPv6 exist.

  • Page 414

    Configuring a C-BSR IMPORTANT: Because the BSR and other devices exchange a large amount of information in the IPv6 BIDIR-PIM domain, reserve a large bandwidth between the C-BSR and other devices. A BSR policy enables the router to filter BSR messages by using an ACL that specifies the legal BSR addresses.

  • Page 415: Configuring Ipv6 Pim-ssm

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

  • Page 416

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

  • Page 417: Configuring Common Ipv6 Pim Features

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

  • Page 418: Configuring An Ipv6 Pim Hello Policy

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

  • Page 419: Configuring Common Ipv6 Pim Timers

    the upstream router has changed, it considers that the status of the upstream router has changed. In this case, it sends a join message to the upstream router for status update. You can configure an interface to drop hello messages without the generation ID options to promptly know the status of an upstream router.

  • Page 420

    join/prune messages to be less than the joined/pruned state holdtime timer. The following are common timers in IPv6 PIM: • Hello interval—Interval at which an IPv6 PIM router sends hello messages to discover IPv6 PIM neighbors and maintain IPv6 PIM neighbor relationship. •...

  • Page 421

    interface-number Set the hello interval. ipv6 pim timer hello interval The default setting is 30 seconds. ipv6 pim Set the triggered hello delay. The default setting is 5 seconds. triggered-hello-delay delay The default setting is 60 seconds. ipv6 pim timer Set the join/prune interval.

  • Page 422: Enabling Ipv6 Pim Nsr

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

  • Page 423: Displaying And Maintaining Ipv6 Pim

    Displaying and maintaining IPv6 PIM Execute display commands in any view. Task Command Display register-tunnel interface display interface [ register-tunnel [ interface-number ] ] [ brief information. [ description| down ] ] Display BSR information in the display ipv6 pim [ vpn-instance vpn-instance-name ] bsr-info IPv6 PIM-SM domain.

  • Page 424

    Figure 126 Network diagram Receiver Host A Switch A Vlan-int100 Host B Receiver Vlan-int300 Vlan-int101 Vlan-int200 Source Vlan-int101 Host C Switch D Switch B 4001::100/64 Vlan-int200 IPv6 PIM-DM Switch C Host D Table 27 Interface and IPv6 address assignment Device Interface IPv6 address Device...

  • Page 425

    [SwitchA-Vlan-interface103] ipv6 pim dm [SwitchA-Vlan-interface103] quit # Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM on Switch B and Switch C in the same way Switch A is configured. (Details not shown.) # On Switch D, enable IPv6 multicast routing, and enable IPv6 PIM-DM on each interface. <SwitchD>...

  • Page 426: Ipv6 Pim-sm Non-scoped Zone Configuration Example

    (*, FF0E::101) Protocol: pim-dm, Flag: WC UpTime: 00:01:24 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:01:20, Expires: - (4001::100, FF0E::101) Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: Vlan-interface103 Upstream neighbor: 1002::2...

  • Page 427

    • VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub networks, and a minimum of one receiver host exist in each stub network. The entire IPv6 PIM-SM domain contains only one BSR. • Host A and Host C are multicast receivers in the stub networks N1 and N2.

  • Page 428

    # On Switch A, enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Enable MLD on VLAN-interface 100 (the interface that is connected to the stub network). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-SM on other interfaces.

  • Page 429: Ipv6 Pim-sm Admin-scoped Zone Configuration Example

    [SwitchA] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64 Hash mask length: 126 Uptime: 00:11:18 # Display BSR information on Switch E. [SwitchE] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:01:44 Elected BSR address: 1003::2 Priority: 64...

  • Page 430

    global-scoped zone, and it is designated to the IPv6 multicast groups with the scope field value of 14. • MLDv1 runs between Switch A, Switch E, Switch I, and the receivers that directly connect to them, respectively. Figure 128 Network diagram IPv6 admin-scope 1 Receiver Vlan-int500...

  • Page 431

    Switch E Vlan-int400 7001::1/64 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 128. (Details not shown.) Configure OSPFv3 on all switches in the IPv6 PIM-SM domain. (Details not shown.) Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM: # On Switch A, enable IPv6 multicast routing.

  • Page 432

    # 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 433

    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 434

    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 435: 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 436

    Switch C Vlan-int102 2002::2/64 Receiver 1 — 2001::2/64 Switch C Vlan-int103 3001::1/64 Receiver 2 — 4001::2/64 Switch C Loop0 6001::1/128 Configuration procedure Assign an IPv6 address and prefix length to each interface, as shown in Figure 129. (Details not shown.) Configure OSPFv3 on the switches in the IPv6 BIDIR-PIM domain.

  • Page 437

    [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. <SwitchD>...

  • Page 438

    RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Vlan200 01:24:09 FE80::200:5EFF: FE71:2801 (local) Vlan101 01:24:09 FE80::20F:E2FF: FE38:4E01 (local) Vlan102 Lose 01:23:12 FE80::20F:E2FF: FE15:5601 # Display IPv6 BIDIR-PIM DF information on Switch C. [SwitchC] display ipv6 pim df-info RP address: 6001::1 Interface State DF-Pref...

  • Page 439: Ipv6 Pim-ssm Configuration Example

    2: Vlan-interface200 # Display information about DFs for IPv6 multicast forwarding on Switch C. [SwitchC] display ipv6 multicast forwarding df-info Total 1 RP, 1 matched 00001. RP address: 6001::1 Flags: 0x0 Uptime: 00:07:21 RPF interface: LoopBack0 List of 2 DF interfaces: 1: Vlan-interface102 2: Vlan-interface103 # Display information about DFs for IPv6 multicast forwarding on Switch D.

  • Page 440

    Figure 130 Network diagram Receiver Host A Switch A Vlan-int100 Vlan-int102 Host B Vlan-int102 Receiver Vlan-int300 Vlan-int105 Vlan-int103 Vlan-int200 Vlan-int105 Vlan-int103 Source Vlan-int104 Switch D Switch E Switch B Host C 4001::100/64 Vlan-int104 Vlan-int200 IPv6 PIM-SSM Host D Switch C Table 31 Interface and IPv6 address assignment Device Interface...

  • Page 441

    [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 442: Troubleshooting Ipv6 Pim

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

  • Page 443: An Rp Cannot Join An Spt In Ipv6 Pim-sm

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

  • Page 444: Document Conventions And Icons

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

  • Page 445: 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 446: Support And Other Resources

    Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements. Websites Website Link...

  • Page 447: Customer Self Repair

    Hewlett Packard Enterprise Information Library for www.hpe.com/networking/resourcefinder Networking Hewlett Packard Enterprise Networking website www.hpe.com/info/networking Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty General websites Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc...

  • Page 448: Index

    Index MSDP inter-AS multicast configuration (static Numerics RPF peers)(on switch), multicast inter-AS MD VPN, IGMP snooping message 802.1p priority, multicast intra-AS MD VPN configuration, MLD snooping 802.1p message priority, multicast VPN inter-AS option B, multicast VPN inter-AS option C, ASBR multicast VPN inter-AS option A, IGMP snooping policy, multicast VPN inter-AS option B,...

  • Page 449

    C-BSR configuration, IPv6 PIM-SM, configuration, 137, 161 IPv6 PIM-SM administrative scoping zone border router, C-RP configuration, IPv6 PIM-SM C-BSR, DF election, PIM-SM administrative scoping zones, domain border configuration, PIM-SM BSR configuration, enable, PIM-SM C-BSR configuration, introduction, PIM-SM RP discovery, IPv6. See IPv6 BIDIR-PIM multicast VPN default MDT establishment (BIDIR-PIM network),...

  • Page 450

    IGMP performance adjustment, IPv6 multicast port-based VLAN, IGMP proxying, 102, 110 IPv6 multicast port-based VLAN user port attribute, IGMP query/response parameter (global), IPv6 multicast routing+forwarding, 347, 349, 350, IGMP query/response parameter (interface), IPv6 multicast sub-VLAN-based VLAN, IGMP snooping, 13, 17, 35 IPv6 multicast VLAN, 335, 337, 340 IGMP snooping (for VLAN),...

  • Page 451

    MLD snooping (for VLAN), multicast forwarding boundary, MLD snooping (for VSI), 290, 316 multicast forwarding/GRE tunnel, MLD snooping (for VXLAN), multicast group policy (global), MLD snooping basic features, multicast intra-AS MD VPN, MLD snooping general query/response multicast routing load splitting, parameters, multicast routing longest prefix match MLD snooping general query/response...

  • Page 452

    port-based multicast VLAN, 66, 71 multicast VPN default-MDT characteristics, port-based multicast VLAN user port multicast VPN default-MDT establishment attribute, (BIDIR-PIM network), source IP address for IGMP message multicast VPN default-MDT establishment (VLAN), (PIM-DM network), source IP address for IGMP message multicast VPN default-MDT establishment (VSI), (PIM-SM network),...

  • Page 453

    multicast VPN inter-AS option C multicast VPN, configuration, PIM, PIM configuration, PIM snooping, PIM-DM configuration, domain PIM-SM admin-scoped zone BIDIR-PIM domain border configuration, configuration, IPv6 BIDIR-PIM domain border, PIM-SM non-scoped zone configuration, IPv6 PIM-SM domain border, PIM-SSM configuration, MSDP configuration, DF election MSDP inter-domain multicast delivery, BIDIR-PIM,...

  • Page 454

    embedded RP (IPv6 PIM-SM), MLD snooping proxying, enabling MLD snooping querier, BIDIR-PIM, MSDP, BIDIR-PIM Auto-RP listening, MSDP NSR, fast-leave processing (global), MSDP SA message multicast data encapsulation, fast-leave processing (port), multicast forwarding sub-VLANs, IGMP, multicast group replacement (global), IGMP fast-leave processing, multicast group replacement (port), IGMP forwarding (non-querier interface), multicast MD VPN RPF vector,...

  • Page 455

    IPv6 PIM administrative scoping, IPv6 PIM common feature, fast IPv6 PIM configuration, 376, 413 IGMP fast-leave processing, IPv6 PIM multicast source policy, IGMP snooping fast-leave processing, IPv6 PIM protocol relationships, fast-leave processing IPv6 PIM snooping configuration, 328, 329 MLD, IPv6 PIM snooping configuration (for VLAN), MLD snooping, IPv6 PIM timer, filtering...

  • Page 456

    multicast VPN MDT switchover, IPv6 PIM hello message options, PIM configuration, 113, 151 IPv6 PIM policy, PIM snooping configuration, 56, 57 PIM common timer configuration (global), PIM snooping configuration (for VLAN), PIM common timer configuration (on interface), PIM VPN support, PIM hello message option configuration PIM-DM, (global),...

  • Page 457

    protocols and standards, multicast group policy configuration, proxying, multicast group policy configuration restrictions, proxying configuration, 102, 110 multicast group replacement, proxying enable, multicast group replacement restrictions, query/response parameter configuration, multicast groups on port, query/response parameter configuration restrictions, multicast groups on port restrictions, snooping.

  • Page 458

    implementing IGMP protocols and standards, IPv6 multicast RPF check, IGMP proxying, 95, 102 inconsistent membership information (IGMP), IGMP proxying configuration, instance IGMP proxying enable, multicast VPN MD for VPN instance, IGMP query/response parameters, inter-AS IGMP snooping basic configuration, multicast MD VPN, IGMP snooping configuration, 13, 17, 35 Internet...

  • Page 459

    IGMPv1, 91, 91 MLD display, IGMPv2, MLD fast-leave processing, IGMPv3, MLD maintain, IPv6 administrative scoping, MLD performance adjustment, IPv6 BIDIR-PIM, MLD proxying, IPv6 BIDIR-PIM bidirectional RPT MLD proxying configuration, building, MLD proxying enable, IPv6 BIDIR-PIM BSR, MLD snooping 802.1p message priority, IPv6 BIDIR-PIM configuration, 400, 425 MLD snooping basic configuration,...

  • Page 460

    MLD VPN support, PIM-DM configuration, 128, 151 models, PIM-DM enable, MSDP Anycast RP, PIM-DM graft, MSDP Anycast RP configuration, PIM-DM graft retry timer, MSDP basics configuration, PIM-DM neighbor discovery, MSDP configuration, 171, 177, 184 PIM-DM SPT building, MSDP display, PIM-DM state-refresh, MSDP inter-domain multicast delivery, PIM-DM state-refresh parameters, MSDP maintain,...

  • Page 461

    troubleshooting IPv6 PIM snooping on Layer 2 PIM. See IPv6 PIM device, PIM snooping. See troubleshooting IPv6 PIM-SM multicast PIM-DM. See source registration failure, PIM-DM configuration, troubleshooting IPv6 PIM-SM RP cannot join PIM-SM. See SPT, PIM-SM DR election, troubleshooting MLD, PIM-SSM.

  • Page 462

    static MAC address entry configuration, troubleshoot IPv6 PIM snooping on Layer 2 device, sub-VLAN forwarding, IPv6 PIM-DM VLAN. See assert, IPv6 multicast VLAN configuration, 391, 413 configuration, 335, 337, 340 enable, display, graft, forwarding entries max, graft retry timer, maintain, introduction, port –based implementation, IPv6 PIM NSR enable,...

  • Page 463

    IPv6 PIM-SSM IGMPv2 leave group mechanism, configuration, 405, 429 MLDv1 IPv6 group leave, DR election, load splitting group range configuration, IGMP multicast load splitting (IGMP proxy), group range configuration restrictions, IPv6 multicast configuration, introduction, MLD IPv6 multicast load splitting (MLD proxy), IPv6 PIM protocol relationships, multicast routing configuration,...

  • Page 464

    how it works, MSDP SA message filtering configuration, inter-AS option B configuration, MSDP SA message multicast data encapsulation, inter-AS option C configuration, MSDP SA message originating RP, intra-AS M6VPE configuration, MSDP SA message policy, intra-AS MD VPN configuration, MSDP SA message-related parameters, MD address family creation, MSDP SA request message, MD for VPN instance,...

  • Page 465

    VPN support, proxying configuration (for VLAN), MLD snooping querier configuration, 802.1p message priority, querier configuration (for VLAN), basic configuration, querier enable, configuration, 285, 289, 307 querier enable restrictions, configuration (for VSI), report suppression, configuration (for VXLAN), simulated member host port, display, static port configuration, done message,...

  • Page 466

    multicast VPN inter-AS option C forwarding/GRE tunnel configuration, configuration, IP multicast routing enable, multicast VPN MD VPN configuration, load splitting configuration, MSDP longest prefix match principle, Anycast RP, maintain, Anycast RP configuration, RPF check mechanism, basics configuration, RPF route change, 77, 83 configuration, 171, 177, 184...

  • Page 467

    inter-AS option B, BIDIR-PIM RP configuration, inter-AS option B configuration, BIDIR-PIM RP discovery, inter-AS option C, BIDIR-PIM RP max, inter-AS option C configuration, BIDIR-PIM static RP configuration, intra-AS M6VPE configuration, IGMP basic configuration, 97, 105 intra-AS MD VPN configuration, IGMP fast-leave processing, maintain, IGMP multicast group policy, MD address family creation,...

  • Page 468

    IPv6 multicast sub-VLAN-based VLAN MLD static group member, configuration, MLD version specification, IPv6 PIM BFD enable, MSDP Anycast RP configuration, IPv6 PIM common feature, MSDP basics configuration, IPv6 PIM hello message options, MSDP configuration, IPv6 PIM hello policy, MSDP inter-AS multicast configuration (static IPv6 PIM join/prune message max size, RPF peers)(on switch), IPv6 PIM multicast source policy,...

  • Page 469

    PIM multicast source policy, sub-VLAN-based multicast VLAN configuration, 65, 68 PIM NSR enable, network management PIM passive mode enable, BIDIR-PIM, PIM SNMP notification enable, IGMP configuration, 91, 97, 105 PIM-DM assert, IGMP performance adjustment, PIM-DM configuration, IGMP snooping configuration, 13, 17, 35 PIM-DM graft, IP multicast overview, PIM-DM graft retry timer,...

  • Page 470

    IPv6 PIM hello message Generation ID, MSDP Anycast RP, IPv6 PIM hello message holdtime, MSDP inter-AS multicast configuration (static RPF peers)(on switch), IPv6 PIM hello message LAN_Prune_Delay, MSDP inter-domain multicast delivery, IPv6 PIM hello message options, MSDP intermediate, IPv6 PIM hello message options configuration MSDP NSR enable, (global), MSDP peer,...

  • Page 471

    multicast VPN RPF vector, Anycast RP configuration, multicast VPN RPF vector configuration, assert, nonstop routing (NSR) enable, Auto-RP listening configuration, outgoing packet DSCP value, BSM forwarding disable, passive mode enable, BSM semantic fragmentation, passive mode enable restrictions, BSR configuration, protocol relationships, C-BSR configuration, protocols and standards, configuration,...

  • Page 472

    protocols and standards, IGMP snooping multicast group replacement, RP configuration, IGMP snooping multicast groups on port, RP discovery, IGMP snooping multicast source port filtering, RPT building, IGMP snooping port, SPT switchover, IGMP snooping port feature, SPT switchover configuration, IGMP snooping simulated member host, static RP configuration, IGMP snooping static port, troubleshoot multicast source registration...

  • Page 473

    configuration, 66, 68, 71 configuring IGMP snooping multicast group policy, implementation, configuring IGMP snooping multicast group policy user port assignment, (port), user port assignment restrictions, configuring IGMP snooping multicast source port user port attribute, filtering (IGMP-snooping view), prefix configuring IGMP snooping multicast source port IPv6 multicast longest prefix match filtering (interface view), principle,...

  • Page 474

    configuring IPv6 PIM multicast source configuring MLD snooping general policy, query/response parameters, configuring IPv6 PIM snooping, configuring MLD snooping general query/response parameters (global), configuring IPv6 PIM snooping (for VLAN), configuring MLD snooping general query/response parameters (VLAN), configuring IPv6 PIM timer, configuring MLD snooping general configuring IPv6 PIM timer (global), query/response parameters (VSI),...

  • Page 475

    configuring MSDP SA message-related configuring PIM-SM C-BSR, parameters, configuring PIM-SM C-RP, configuring MSDP SA request message, configuring PIM-SM multicast source configuring multicast forwarding boundary, registration, configuring multicast forwarding/GRE configuring PIM-SM non-scoped zone, tunnel, configuring PIM-SM RP, configuring multicast group policy (global), configuring PIM-SM SPT switchover, configuring multicast intra-AS M6VPE, configuring PIM-SM static RP,...

  • Page 476

    disabling PIM-SM BSM semantic enabling MD VPN instance IP multicast fragmentation, routing, displaying IGMP, enabling MLD, displaying IGMP snooping, enabling MLD fast-leave processing, displaying IPv6 multicast enabling MLD NSR, routing+forwarding, enabling MLD proxying, displaying IPv6 multicast VLAN, enabling MLD snooping, displaying IPv6 PIM, enabling MLD snooping (MLD-snooping displaying IPv6 PIM snooping,...

  • Page 477

    maintaining MLD snooping, setting multicast VLAN forwarding entries max, maintaining MSDP, setting PIM join/prune message size, maintaining multicast routing+forwarding, specifying IGMP snooping version, 19, 19 maintaining multicast VLAN, specifying IGMP snooping version (IGMP-snooping view), maintaining multicast VPN, specifying IGMP snooping version (VLAN maintaining PIM snooping, view), setting IGMP last member query interval...

  • Page 478

    troubleshooting multicast MD VPN PIM hello message LAN_Prune_Delay default-MDT establishment, option, troubleshooting multicast VPN MVRF PIM join/prune message size, creation, PIM-DM SPT building, troubleshooting PIM abnormal multicast data termination, querier troubleshooting PIM multicast distribution tree, IGMP snooping querier, 25, 26 troubleshooting PIM RP cannot join SPT, IGMP snooping querier configuration (for VLAN),...

  • Page 479

    IGMP snooping report suppression, IGMP snooping router port, IGMPv3 report capability), MLD snooping router port, MLD snooping membership report, routing MLD snooping report suppression, BIDIR-PIM, restrictions BIDIR-PIM Auto-RP listening, IGMP last member query interval BIDIR-PIM bidirectional RPT building, configuration, BIDIR-PIM BSM forwarding disable, IGMP multicast forwarding enable, BIDIR-PIM BSM semantic fragmentation, IGMP query/response parameter...

  • Page 480

    IGMP snooping static port, IPv6 PIM-DM, IGMP snooping static port configuration (for IPv6 PIM-DM assert, VLAN), IPv6 PIM-DM configuration, 391, 413 IGMP snooping version, IPv6 PIM-DM graft, IGMP SSM mapping, 94, 102 IPv6 PIM-DM neighbor discovery, IGMP SSM mapping configuration, IPv6 PIM-DM SPT building, IGMP version specification, IPv6 PIM-DM state refresh enable,...

  • Page 481

    MLD snooping forwarding entries, multicast VPN default-MDT to data-MDT switch, MLD snooping general query/response parameters, multicast VPN default-MDT-based delivery, MLD snooping group policy+simulated joining multicast VPN inter-AS option B configuration (for VLAN), configuration, MLD snooping last member query multicast VPN inter-AS option C interval, configuration, MLD snooping message parameters,...

  • Page 482

    PIM-SSM group range, troubleshooting PIM-SM RP cannot be built, PIM-SSM neighbor discovery, troubleshooting PIM-SM RP cannot join SPT, PIM-SSM SPT building, routing table IPv6 multicast check mechanism, IPv6 multicast forwarding (unicast IPv6 multicast longest prefix match principle, subnet), IPv6 multicast RPF check implementation, multicast RPF check mechanism, IPv6 multicast RPF check process, longest prefix match principle,...

  • Page 483

    IPv6 PIM-SM BSM, IGMP snooping host tracking, PIM-SM BSM, IPv6 PIM snooping, setting IPv6 PIM snooping configuration, IGMP last member query interval, IPv6 PIM snooping configuration (for VLAN), IGMP last member query interval (global), MLD snooping, IGMP last member query interval (VLAN), PIM snooping configuration, 56, 57 IGMP last member query interval (VSI),...

  • Page 484

    MLD mapping, IP multicast VPN application, MLD SSM mapping, IP multicast VPN instance, MLD SSM mapping configuration, IP multicast VPN support, state MSDP inter-AS multicast configuration (static RPF peers)(on switch), IPv6 PIM-DM state refresh enable, MSDP PIM-SM inter-domain multicast IPv6 PIM-DM state refresh parameters, configuration, MLDv2, multicast forwarding across unicast subnets,...

  • Page 485

    traffic multicast VPN MVRF creation, IPv6 multicast load splitting, PIM, multicast routing load splitting, PIM abnormal multicast data termination, transmitting PIM multicast distribution tree, IP multicast, PIM snooping, IP multicast broadcast, PIM snooping does not work, IP multicast overview, PIM-SM multicast source registration failure, IP multicast transmission techniques, PIM-SM RP cannot be built, IP multicast unicast,...

  • Page 486

    IGMP snooping general query/response MLD snooping version, parameters, multicast forwarding sub-VLANs, IGMP snooping message 802.1p priority, multicast VLAN configuration, 63, 65, 68 IGMP snooping message parameters, PIM configuration, 113, 151 IGMP snooping message source IP PIM snooping configuration, address, PIM-DM configuration, IGMP snooping multicast group PIM-SM admin-scoped zone configuration, replacement,...

  • Page 487

    MLD snooping query/response parameter configuration (VSI), MLD snooping version, IPv6 PIM-SM administrative scoping, PIM-SM administrative scoping, zone border router. See IPv6 admin-scoped/global-scoped zone relationships, IPv6 PIM-SM admin-scoped zone configuration, IPv6 PIM-SM border router, IPv6 PIM-SM non-scoped zone configuration, PIM-SM admin-scoped zone configuration, PIM-SM admin-scoped/global-scoped zone relationship,...

Comments to this Manuals

Symbols: 0
Latest comments: