Page of 383
Download Table of ContentsContents Print This PagePrint Bookmark
HP 6125XLG Blade Switch
IP Multicast
Part number: 5998-5364a
Software version: Release 240x
Document version: 6W101-20150515

Advertising

   Related Manuals for HP 6125XLG

   Summary of Contents for HP 6125XLG

  • Page 1: Configuration Guide

    HP 6125XLG Blade Switch IP Multicast Configuration Guide Part number: 5998-5364a Software version: Release 240x Document version: 6W101-20150515...

  • Page 2

    The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.

  • Page 3: 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 ································································································································································ 5  ...

  • Page 4: Table Of Contents

    Troubleshooting PIM snooping ····································································································································· 39   PIM snooping does not work on a Layer 2 device ···························································································· 39   Configuring multicast VLANs ····································································································································· 41   Overview ········································································································································································· 41   Multicast VLAN configuration task list ························································································································· 43   Configuring a sub-VLAN-based multicast VLAN ········································································································· 43  ...

  • Page 5: Table Of Contents

    Enabling IGMP fast-leave processing ·················································································································· 76   Displaying and maintaining IGMP ······························································································································· 77   IGMP configuration examples ······································································································································ 77   Network requirements ··········································································································································· 77   Configuration procedure ······································································································································ 78   Verifying the configuration ··································································································································· 79   Troubleshooting IGMP ··················································································································································· 80  ...

  • Page 6: Table Of Contents

    Displaying and maintaining PIM ································································································································ 116   PIM configuration examples ······································································································································· 117   PIM-DM configuration example ························································································································· 117   PIM-SM non-scoped zone configuration example ··························································································· 120   PIM-SM admin-scoped zone configuration example ······················································································· 123   BIDIR-PIM configuration example ······················································································································· 129  ...

  • Page 7: Table Of Contents

    Configuring MD-VPN ··················································································································································· 181   Configuration prerequisites ································································································································ 181   Enabling IP multicast routing in a VPN instance ······························································································ 181   Creating the MD for a VPN instance ················································································································ 182   Specifying the default-group address ················································································································ 182   Specifying the MD source interface ·················································································································· 183  ...

  • Page 8: Table Of Contents

    IPv6 multicast VLAN configuration task list ··············································································································· 243   Configuring a sub-VLAN-based IPv6 multicast VLAN ······························································································ 243   Configuration prerequisites ································································································································ 243   Configuration guidelines ···································································································································· 243   Configuration procedure ···································································································································· 243   Configuring a port-based IPv6 multicast VLAN ········································································································ 244  ...

  • Page 9: Table Of Contents

    IPv6 PIM-DM overview ········································································································································ 274   IPv6 PIM-SM overview ········································································································································ 277   IPv6 BIDIR-PIM overview ····································································································································· 282   IPv6 administrative scoping overview ··············································································································· 285   IPv6 PIM-SSM overview ······································································································································ 287   Relationship among IPv6 PIM protocols ············································································································ 288   IPv6 PIM support for VPNs ································································································································· 289  ...

  • Page 10: Table Of Contents

    An RPT cannot be built or IPv6 multicast source registration fails in IPv6 PIM-SM ······································· 333   Support and other resources ·································································································································· 335   Contacting HP ······························································································································································ 335   Subscription service ············································································································································ 335   Related information ······················································································································································ 335   Documents ···························································································································································· 335  ...

  • 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. By using multicast technology, a network operator can easily provide bandwidth-critical and time-critical information services.

  • Page 12

    Unicast is not suitable for batch transmission of information. Broadcast In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission Figure 2, assume that only Host B, Host D, and Host E need the information. If the information is broadcast to the subnet, Host A and Host C also receive it.

  • Page 13: Multicast Features

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

  • Page 14: Common Notations In Multicast

    For a better understanding of the multicast concept, you can compare multicast transmission to the transmission of TV programs. 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.

  • Page 15: Multicast Models

    Multicast models Based on how the receivers treat the multicast sources, the multicast models include any-source multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM). ASM model In the ASM model, any sender can send information to a multicast group as a multicast source. Receivers can join a multicast group identified by a group address and get multicast information addressed to that multicast group.

  • Page 16: Multicast Addresses

    Multicast addresses IP multicast addresses • IPv4 multicast addresses: IANA assigns the Class D address block (224.0.0.0 to 239.255.255.255) to IPv4 multicast. Table 2 Class D IP address blocks and description Address block Description Reserved permanent group addresses. The IP address 224.0.0.0 is reserved.

  • Page 17

    Address Description 224.0.0.13 All Protocol Independent Multicast (PIM) routers. 224.0.0.14 RSVP encapsulation. 224.0.0.15 All Core-Based Tree (CBT) routers. 224.0.0.16 Designated SBM. 224.0.0.17 All SBMs. 224.0.0.18 VRRP. • IPv6 multicast addresses: Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address: 0xFF—If the most significant eight bits are 1 1 1 1 1 1 1 1, this address is an IPv6 multicast address.

  • Page 18

    Table 5 Values of the Scope field Value Meaning 0, F Reserved. Interface-local scope. Link-local scope. Subnet-local scope. Admin-local scope. Site-local scope. 6, 7, 9 through D Unassigned. Organization-local scope. Global scope. Group ID—The Group ID field contains 1 12 bits. It uniquely identifies an IPv6 multicast group in the scope that the Scope field defines.

  • Page 19: Multicast Protocols

    Figure 7 IPv6-to-MAC address mapping IMPORTANT: Because of the duplicate mapping from multicast IP address to multicast MAC address, the device might inadvertently send multicast protocol packets as multicast data in Layer 2 forwarding. To avoid this, do not use the IP multicast addresses that are mapped to multicast MAC addresses 0100-5E00-00xx and 3333-0000-00xx (where "x"...

  • Page 20

    Figure 8 Positions of Layer 3 multicast protocols Multicast group management protocols: • Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) protocol are multicast group management protocols. Typically, they run between hosts and Layer 3 multicast devices that directly connect to the hosts to establish and maintain the multicast group memberships.

  • Page 21: Multicast Packet Forwarding Mechanism

    Figure 9 Positions of Layer 2 multicast protocols IGMP snooping and MLD snooping: • IGMP snooping and MLD snooping run on Layer 2 devices as multicast constraining mechanisms to improve multicast forwarding efficiency. They generate Layer 2 multicast forwarding tables by listening to IGMP or MLD messages exchanged between the hosts and Layer 3 multicast devices.

  • Page 22: Multicast Support For Vpns

    To process the same multicast information from different peers received on different interfaces of the • same device, the multicast device performs an RPF check on each multicast packet. The RPF check result determines whether the packet will be forwarded or discarded. The RPF check mechanism is the basis for most multicast routing protocols to implement multicast forwarding.

  • Page 23

    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 24: Configuring Igmp Snooping

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

  • Page 25

    Figure 12 IGMP snooping related ports The following describes the ports involved in IGMP snooping: Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include DRs and IGMP • queriers. In Figure 12, Ten-GigabitEthernet 1/1/5 of Switch A and Ten-GigabitEthernet 1/1/5 of Switch B are the router ports.

  • Page 26: How Igmp Snooping Works

    NOTE: In IGMP snooping, only dynamic ports age out. Static ports never age out. 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.

  • Page 27: Protocols And Standards

    cannot determine whether the reported multicast group still has active members attached to that port. For more information about the IGMP report suppression mechanism, see "Configuring IGMP." Leave message An IGMPv1 host does not send any leave messages when it leaves a multicast group. The Layer 2 device cannot immediately update the status of the port that connects to the receiver host.

  • Page 28: Configuring Basic Igmp Snooping Functions

    Task at a glance Configuring IGMP snooping port functions: • (Optional.) Setting aging timers for dynamic ports • (Optional.) Configuring static ports • (Optional.) Enabling IGMP snooping fast-leave processing Configuring IGMP snooping policies: • (Optional.) Configuring a multicast group filter •...

  • Page 29: Specifying The Igmp Snooping Version

    Step Command Remarks Enter system view. system-view Enable IGMP snooping By default, IGMP snooping is globally and enter igmp-snooping disabled. IGMP-snooping view. Return to system view. quit Enter VLAN view. vlan vlan-id Enable IGMP snooping for the By default, IGMP snooping is igmp-snooping enable VLAN.

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

    In this case, HP recommends that you manually remove the extra entries.

  • Page 31: Configuring Igmp Snooping Port Functions

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

  • Page 32: Configuring Static Ports

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

  • Page 33: Configuring Igmp Snooping Policies

    it immediately removes that port from the forwarding entry for the multicast group. Then, when the switch receives IGMP group specific queries for that multicast group, it does not forward them to that port. When you enable the IGMP snooping fast-leave processing feature, follow these guidelines: In a VLAN, you can enable IGMP snooping fast-leave processing on ports that have only one •...

  • Page 34: Configuring Multicast Source Port Filtering

    You can configure a multicast filter either for the current port in interface view or globally for all • ports in IGMP-snooping view. If the configurations are made in both interface view and IGMP-snooping view, the configuration made in interface view takes priority. Configuring a multicast group filter globally Step Command...

  • Page 35: Enabling Dropping Unknown Multicast Data

    Step Command Remarks Enter Layer 2 Ethernet interface interface-type interface view. interface-number Enable multicast source port By default, the multicast source port igmp-snooping source-deny filtering. filtering is disabled. Enabling dropping unknown multicast data Unknown multicast data refers to multicast data for which no forwarding entries exist in the IGMP snooping forwarding table.

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

    Setting the maximum number of multicast groups on a port You can set the maximum number of multicast groups on a port to regulate the port traffic. When you set the maximum number of multicast groups on a port, follow these guidelines: This configuration is effective on the multicast groups that a port dynamically joins.

  • Page 37: Displaying And Maintaining Igmp Snooping

    Step Command Remarks Enable the multicast group By default, the multicast group overflow-replace [ vlan vlan-list ] replacement function globally. replacement function is disabled. To enable the multicast group replacement function on a port: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type...

  • Page 38: Igmp Snooping Configuration Examples

    Task Command Clear statistics for the IGMP messages reset igmp-snooping statistics learned by IGMP snooping. IGMP snooping configuration examples Group policy configuration example Network requirements As shown in Figure 13, Router A runs IGMPv2 and acts as the IGMP querier. Switch A runs IGMPv2 snooping.

  • Page 39

    [RouterA-Ten-GigabitEthernet1/1/5] quit # Enable PIM-DM on Ten-GigabitEthernet 1/1/6. [RouterA] interface ten-gigabitethernet 1/1/6 [RouterA-Ten-GigabitEthernet1/1/6] pim dm [RouterA-Ten-GigabitEthernet1/1/6] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA> system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit # Create VLAN 100, and assign Ten-GigabitEthernet 1/1/5 through Ten-GigabitEthernet 1/1/8 to the VLAN.

  • Page 40: Static Port Configuration Example

    Static port configuration example Network requirements As shown in Figure Router A runs IGMPv2 and serves 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 •...

  • Page 41

    [RouterA-mrib] quit # Enable IGMP on Ten-GigabitEthernet 1/1/5. [RouterA] interface ten-gigabitethernet 1/1/5 [RouterA-Ten-GigabitEthernet1/1/5] igmp enable [RouterA-Ten-GigabitEthernet1/1/5] quit # Enable PIM-DM on Ten-GigabitEthernet 1/1/6. [RouterA] interface ten-gigabitethernet 1/1/6 [RouterA-Ten-GigabitEthernet1/1/6] pim dm [RouterA-Ten-GigabitEthernet1/1/6] quit Configure Switch A: # Enable IGMP snooping globally. <SwitchA>...

  • Page 42: Troubleshooting Igmp Snooping

    # Configure Ten-GigabitEthernet 1/1/7 and Ten-GigabitEthernet 1/1/9 as static member ports for multicast group 224.1.1.1. [SwitchC] interface ten-gigabitethernet 1/1/7 [SwitchC-Ten-GigabitEthernet1/1/7] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-Ten-GigabitEthernet1/1/7] quit [SwitchC] interface ten-gigabitethernet 1/1/9 [SwitchC-Ten-GigabitEthernet1/1/9] igmp-snooping static-group 224.1.1.1 vlan 100 [SwitchC-Ten-GigabitEthernet1/1/9] quit Verifying the configuration # Display information about the static router ports in VLAN 100 on Switch A.

  • Page 43: Multicast Group Filter Does Not Work

    If IGMP snooping is enabled globally but not enabled for the VLAN, use the igmp-snooping enable command in VLAN view to enable IGMP snooping for the VLAN. Multicast group filter does not work Symptom Hosts can receive multicast data from multicast groups that are not permitted by the multicast group filter. Analysis The ACL is incorrectly configured.

  • Page 44: 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.

  • Page 45

    Forwards all multicast data to all router ports in the VLAN. 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 •...

  • Page 46: Displaying And Maintaining Pim Snooping

    Displaying and maintaining PIM snooping Execute display commands in any view and reset commands in user view. Task Command display pim-snooping neighbor [ vlan vlan-id ] [ slot Display information about PIM snooping neighbors. slot-number ] [ verbose ] display pim-snooping routing-table [ vlan vlan-id ] Display PIM snooping routing entries.

  • Page 47

    Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 16. (Details not shown.) Configure OSPF on the routers to make sure the following conditions are met: (Details not shown.) The routers are interoperable at the network layer. The routers can dynamically update their routing information.

  • Page 48

    [RouterC] interface ten-gigabitethernet 1/1/6 [RouterC-Ten-GigabitEthernet1/1/6] pim sm [RouterC-Ten-GigabitEthernet1/1/6] quit Configure Router D: # Enable IP multicast routing. <RouterD> system-view [RouterD] multicast routing [RouterD-mrib] quit # Enable IGMP on Ten-GigabitEthernet 1/1/5. [RouterD] interface ten-gigabitethernet 1/1/5 [RouterD-Ten-GigabitEthernet1/1/5] igmp enable [RouterD-Ten-GigabitEthernet1/1/5] quit # Enable PIM-SM on Ten-GigabitEthernet 1/1/6. [RouterD] interface ten-gigabitethernet 1/1/6 [RouterD-Ten-GigabitEthernet1/1/6] pim sm [RouterD-Ten-GigabitEthernet1/1/6] quit...

  • Page 49: Troubleshooting Pim Snooping

    10.1.1.4 Slots (0 in total): Ports (1 in total): XGE1/1/8 (00:32:43) The output shows that Router A, Router B, Router C, and Router D are PIM snooping neighbors. # On Switch A, display information about PIM snooping routing entries for VLAN 100. [SwitchA] display pim-snooping routing-table vlan 100 Total 2 entries.

  • Page 50

    If IGMP snooping is not enabled, enable IGMP snooping globally, and then enable IGMP snooping and PIM snooping for the VLAN. If PIM snooping is not enabled, enable PIM snooping for the VLAN.

  • Page 51: Configuring Multicast Vlans

    Configuring multicast VLANs Overview As shown in Figure 17, Host A, Host B, and Host C reside in different VLANs and join 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 52

    Figure 18 Sub-VLAN-based multicast VLAN IGMP snooping manages router ports in the multicast VLAN and user ports in each sub-VLAN. Switch A forwards only one copy of the received multicast data to the multicast VLAN on Switch B. Switch B replicates the multicast data and sends the copy to each sub-VLAN of the multicast VLAN.

  • Page 53: Multicast Vlan Configuration Task List

    If you have configured both a sub-VLAN-based multicast VLAN and a port-based multicast VLAN on a device, the port-based multicast VLAN configuration takes effect. HP recommends that you not configure multicast VLANs on a device that is enabled with IP multicast •...

  • Page 54: Configuring A Port-based Multicast Vlan

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

  • Page 55: Assigning User Ports To A Multicast Vlan

    If the total number of the entries exceeds the upper limit value that you are setting, the system does not automatically remove existing entries or create new entries. In this case, HP recommends that you remove extra entries manually.

  • Page 56: Displaying And Maintaining Multicast Vlans

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

  • Page 57

    Figure 20 Network diagram Configuration procedure Configure Switch A: # Enable IP multicast routing. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Create VLAN 20, and assign Ten-GigabitEthernet 1/1/6 to this VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port ten-gigabitethernet 1/1/6 [SwitchA-vlan20] quit # Assign an IP address to VLAN-interface 20, and enable PIM-DM on the interface.

  • Page 58

    [SwitchA-Vlan-interface10] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 2, assign Ten-GigabitEthernet 1/1/6 to the VLAN, and enable IGMP snooping for the VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port ten-gigabitethernet 1/1/6 [SwitchB-vlan2] igmp-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign Ten-GigabitEthernet 1/1/7 to the VLAN, and enable IGMP snooping for...

  • Page 59: Port-based Multicast Vlan Configuration Example

    Port list(0 in total): # Display information about the multicast VLAN forwarding entries on Switch B. [SwitchB] display multicast-vlan group Total 1 entries. Multicast VLAN 10: Total 1 entries. (0.0.0.0, 224.1.1.1) Sub-VLANs (3 in total): VLAN 2 VLAN 3 VLAN 4 The output shows that the multicast VLAN (VLAN 10) is maintaining the sub-VLANs (VLAN 2 through VLAN 4).

  • Page 60

    Configuration procedure Configure Switch A: # Enable IP multicast routing. <SwitchA> system-view [SwitchA] multicast routing [SwitchA-mrib] quit # Create VLAN 20, and assign Ten-GigabitEthernet 1/1/6 to this VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port ten-gigabitethernet 1/1/6 [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...

  • Page 61

    [SwitchB-vlan3] quit # Create VLAN 4, and enable IGMP snooping for the VLAN. [SwitchB] vlan 4 [SwitchB-vlan4] igmp-snooping enable [SwitchB-vlan4] quit # Configure Ten-GigabitEthernet 1/1/6 as a hybrid port, and configure VLAN 2 as the PVID of the hybrid port. [SwitchB] interface ten-gigabitethernet 1/1/6 [SwitchB-Ten-GigabitEthernet1/1/6] port link-type hybrid [SwitchB-Ten-GigabitEthernet1/1/6] port hybrid pvid vlan 2...

  • Page 62

    Multicast VLAN 10: Sub-VLAN list(0 in total): Port list(0 in total): XGE1/1/6 XGE1/1/7 XGE1/1/8 # Display information about IGMP snooping forwarding entries for the dynamic multicast groups on Switch B. [SwitchB] display igmp-snooping group Total 1 entries. VLAN 2: Total 1 entries. (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (3 in total):...

  • Page 63: 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 •...

  • Page 64

    For more information about the route preference, see Layer 3—IP Routing Configuration Guide. If the router does not use the longest prefix match principle, the router selects the route that has the highest priority as the RPF route. If the routes have the same priority, the router selects a route as the RPF route in the order of static multicast route and unicast route.

  • Page 65: Static Multicast Routes

    Figure 22 RPF check process IP Routing Table on Switch C Receiver Switch B Destination/Mask Interface 192.168.0.0/24 Vlan-int20 Vlan-int10 Source Switch A 192.168.0.1/24 Receiver Vlan-int10 Vlan-int20 Multicast packets Switch C As shown in Figure 22, assume that unicast routes are available in the network and no static multicast routes have been configured on Switch C.

  • Page 66

    Figure 23 Changing an RPF route As shown in Figure 23, when no static multicast route is configured, Switch C's RPF neighbor on the path back to the source is Switch A. The multicast data from the source travels through Switch A to Switch C. You can configure a static multicast route on Switch C and specify Switch B as its RPF neighbor on the path back to the source.

  • Page 67: Multicast Forwarding Across Unicast Subnets

    C and Switch D, and specify Switch B and Switch C as the RPF neighbors of Switch C and Switch D, respectively. Then, the receiver hosts can receive the multicast data from the multicast source. NOTE: A static multicast route is effective only on the multicast router on which it is configured, and will not be advertised throughout the network or redistributed to other routers.

  • Page 68: Enabling Ip Multicast Routing

    NOTE: The device can route and forward multicast data only through the primary IP addresses of interfaces, rather than their secondary addresses or unnumbered IP addresses. For more information about primary Layer 3—IP Services Configuration Guide and secondary IP addresses, and IP unnumbered, see Enabling IP multicast routing Enable IP multicast routing before you configure any Layer 3 multicast functionality on the public network or VPN instance.

  • Page 69: Configuring The Rpf Route Selection Rule

    Configuring the RPF route selection rule You can configure the router to select the RPF route based on the longest prefix match principle. For more information about RPF route selection, see "RPF check process." To configure a multicast routing policy: Step Command Remarks...

  • Page 70: Configuring Static Multicast Mac Address Entries

    Step Command Remarks Configure a multicast multicast boundary group-address By default, no forwarding forwarding boundary. { mask-length | mask } boundary is configured. Configuring static multicast MAC address entries In Layer 2 multicast, multicast MAC address entries can be dynamically created or added through Layer 2 multicast protocols (such as IGMP snooping).

  • Page 71: Displaying And Maintaining Multicast Routing And Forwarding

    To configure multicast forwarding between sub-VLANs of a super VLAN: Step Command Remarks Enter system view. system-view Enter VLAN interface view. interface vlan-interface interface-number By default, multicast data Configure multicast cannot be forwarded forwarding between multicast forwarding supervlan community between sub-VLANs of a sub-VLANs of a super VLAN.

  • Page 72: Configuration Examples

    Task Command display multicast [ vpn-instance vpn-instance-name ] routing-table [ source-address [ mask { mask-length | mask } ] | group-address [ mask Display information about the { mask-length | mask } ] | incoming-interface interface-type interface-number multicast routing table. | outgoing-interface { exclude | include | match } interface-type interface-number ] * Display information about the...

  • Page 73

    Figure 26 Network diagram Switch C Vlan-int103 Vlan-int101 40.1.1.1/24 20.1.1.2/24 PIM-DM Vlan-int103 Vlan-int101 40.1.1.2/24 20.1.1.1/24 Switch A Switch B Vlan-int102 Vlan-int102 30.1.1.2/24 30.1.1.1/24 Vlan-int200 Vlan-int100 50.1.1.1/24 10.1.1.1/24 Source Receiver 50.1.1.100/24 10.1.1.100/24 Multicast static route Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 26.

  • Page 74: Creating An Rpf Route

    [SwitchA-mrib] quit [SwitchA] interface vlan-interface 200 [SwitchA-Vlan-interface200] pim dm [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 the RPF route to Source on Switch B.

  • Page 75

    Configure the switches so that the receiver host receives multicast data from the Source 2, which is outside the OSPF domain. Figure 27 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 27.

  • Page 76: Multicast Forwarding Over A Gre Tunnel

    [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit # Enable IP multicast routing and PIM-DM on Switch B in the same way Switch A is configured. (Details not shown.) Display information about their RPF routes to Source 2 on Switch B and Switch C. [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 the source 2 exist on Switch B or Switch C.

  • Page 77

    Figure 28 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 28. (Details not shown.) Configure OSPF on switches to meet the following requirements: (Details not shown.) The switches are interoperable at the network layer. The switches can dynamically update their routing information.

  • Page 78

    # Assign an IP address to interface Tunnel 0, and specify its source and destination addresses. [SwitchC-Tunnel0] ip address 50.1.1.2 24 [SwitchC-Tunnel0] source 30.1.1.2 [SwitchC-Tunnel0] destination 20.1.1.1 [SwitchC-Tunnel0] quit Enable IP multicast routing, PIM-DM, and IGMP: # On Switch A, enable multicast routing, and enable PIM-DM on each interface. [SwitchA] multicast routing [SwitchA-mrib] quit [SwitchA] interface vlan-interface 100...

  • Page 79: Troubleshooting Multicast Routing And Forwarding

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

  • Page 80: Configuring Igmp

    Configuring IGMP Overview Internet Group Management Protocol (IGMP) establishes and maintains the multicast group memberships between a Layer 3 multicast device and its directly connected hosts. IGMP has three versions: IGMPv1 (defined by RFC 1 1 12) • • IGMPv2 (defined by RFC 2236) IGMPv3 (defined by RFC 3376) •...

  • Page 81

    Figure 29 IGMP queries and reports IP network Router A Router B Ethernet Host A Host B Host C (G2) (G1) (G1) Query Report As shown in Figure 29, Host B and Host C are interested in the multicast data addressed to the multicast group G1.

  • Page 82: Igmpv2 Enhancements

    IGMPv2 enhancements Backwards-compatible with IGMPv1, IGMPv2 has introduced a querier election mechanism and a leave-group mechanism. Querier election mechanism In IGMPv1, the DR elected by the Layer 3 multicast routing protocol (such as PIM) serves as the querier among multiple routers that run IGMP on the same subnet. IGMPv2 introduced an independent querier election mechanism.

  • Page 83

    If the host expects to receive multicast data from specific sources like S1, S2, …, it sends a report • with the Filter-Mode denoted as "Include Sources (S1, S2, …)." If the host expects to reject multicast data from specific sources like S1, S2, …, it sends a report with •...

  • Page 84: Igmp Support For Vpns

    TO_IN—The filtering mode has changed from Exclude to Include. TO_EX—The filtering mode has changed from Include to Exclude. ALLOW—The Source Address fields contain a list of additional sources from which the receiver wants to obtain data. If the current filtering mode is Include, these sources are added to the INCLUDE source address list.

  • Page 85: Enabling Igmp

    Enabling IGMP To configure IGMP, enable IGMP on the interface where the multicast group memberships are established and maintained. To enable IGMP: Step Command Remarks Enter system view. system-view Enable IP multicast routing multicast routing [ vpn-instance By default, IP multicast is disabled. and enter MRIB view.

  • Page 86: Configuring A Multicast Group Filter

    Configuration procedure To configure an interface as a static member interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, an interface is not a Configure the interface as a igmp static-group group-address static member of any multicast static member interface.

  • Page 87: Displaying And Maintaining Igmp

    With this feature enabled, after receiving an IGMP leave message, the IGMP querier does not send IGMP group specific queries or IGMP group and source specific queries. Instead, it directly sends a leave notification to the upstream. This reduces leave latency and preserves the network bandwidth. The IGMP fast-leave processing configuration is effective only if the device is running IGMPv2 or IGMPv3.

  • Page 88: Configuration Procedure

    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 receiver hosts in N1 and N2, respectively. IGMPv2 runs between Switch A and N1, and between the other two switches and N2. Switch A •...

  • Page 89: Verifying The Configuration

    [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 (the interface that connects to the stub network). [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit # Enable PIM-DM on VLAN-interface 201.

  • Page 90: Troubleshooting Igmp

    IGMP groups reported in total: 1 Troubleshooting IGMP No membership information on the receiver-side router Symptom When a host sends a report for joining the multicast group G, no membership information of the multicast group G exists on the router closest to that host. Analysis •...

  • Page 91

    Although IGMP routers are partially compatible with hosts that run different IGMP versions, all • routers on the same subnet must run the same IGMP version. Inconsistent IGMP versions running on routers on the same subnet leads to inconsistency of IGMP memberships. Solution Use the display current-configuration command to verify the IGMP information on the interfaces.

  • Page 92: 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 is not dependent on any particular unicast routing protocol, and it uses the underlying unicast routing to generate a routing table with routes.

  • Page 93

    Neighbor discovery In a PIM domain, each interface that runs PIM on a router periodically multicasts PIM hello messages to all other PIM routers (identified by the address 224.0.0.13) on the local subnet. Through the exchanging of hello messages, all PIM routers discover PIM neighbors, maintain PIM neighboring relationship with other routers, and build and maintain SPTs.

  • Page 94

    Graft A previously pruned branch might have new downstream receivers. To reduce the latency for resuming the forwarding capability of this branch, a graft mechanism is used as follows: The node that needs to receive the multicast data sends a graft message to its upstream node, telling it to rejoin the SPT.

  • Page 95: Pim-sm Overview

    PIM-SM overview PIM-DM uses the flood-and-prune cycles to build SPTs for multicast data forwarding. Although an SPT has the shortest paths from the multicast source to the receivers, it is built with a low efficiency and is not suitable for large- and medium-sized networks. PIM-SM uses the pull mode for multicast forwarding, and it is suitable for large- and medium-sized networks with sparsely and widely distributed multicast group members.

  • Page 96

    Figure 34 DR election As shown in Figure 34, the DR election process is as follows: The routers on the shared-media LAN send hello messages to one another. The hello messages contain the priority for DR election. The router with the highest DR priority is elected as the DR. The router with the highest IP address wins the DR election under one of following conditions: All the routers have the same DR election priority.

  • Page 97

    Figure 35 Information exchange between C-RPs and BSR Based on the information in the RP-set, all routers in the network can select an RP for a specific multicast group based on the following rules: The C-RP that is designated to a smallest group range wins. If the C-RPs are designated to the same group range, the C-RP with the highest priority wins.

  • Page 98

    After getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP for the multicast group. The routers along the path from the DR to the RP form an RPT branch. Each router on this branch adds to its forwarding table a (*, G) entry, where the asterisk (*) represents any multicast source.

  • Page 99: Bidir-pim Overview

    Switchover to SPT CAUTION: If the switch is an RP, disabling switchover to SPT might cause multicast traffic forwarding failures on the source-side DR. When disabling switchover to SPT, be sure you fully understand its impact on your network. In a PIM-SM domain, only one RP and one RPT provide services for a specific multicast group. Before the switchover to SPT occurs, the source-side DR encapsulates all multicast data addressed to the multicast group in register messages and sends them to the RP.

  • Page 100

    BIDIR-PIM addresses the problem. Derived from PIM-SM, BIDIR-PIM builds and maintains a bidirectional RPT, which is rooted at the RP and connects the multicast sources and the receivers. Along the bidirectional RPT, the multicast sources send multicast data to the RP, and the RP forwards the data to the receivers.

  • Page 101

    Router B and Router C multicast a DF election message to all PIM routers (224.0.0.13). The election message carries the RP's address, and the priority and metric of the unicast route or static multicast route to the RP. The router with a route of the higher priority becomes the DF. In the case of a tie in the priority, the router with the route with the lower metric wins the DF election.

  • Page 102: Administrative Scoping Overview

    Figure 40 RPT building at the multicast source side As shown in Figure 40, 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 103

    Admin-scoped zones are divided for multicast groups. Zone border routers (ZBRs) form the boundary of an admin-scoped zone. Each admin-scoped zone maintains one BSR for multicast groups within a specific range. Multicast protocol packets, such as assert messages and BSMs, for a specific group range cannot cross the boundary of the admin-scoped zone for the group range.

  • Page 104: Pim-ssm Overview

    Figure 42 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 42, 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 105: Relationship Among Pim Protocols

    Figure 43 SPT building in PIM-SSM Host A Source Receiver Host B Server Receiver Subscribe message Multicast packets Host C As shown in Figure 43, 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 After receiving a report message, the DR first checks whether the group address in this message is in the SSM group range and does the following:...

  • Page 106: Pim Support For Vpns

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

  • Page 107: Pim-dm Configuration Task List

    Enable IP multicast routing before you configure PIM. With PIM-DM enabled on interfaces, routers can establish PIM neighbor relationship and process PIM messages from their PIM neighbors. When you deploy a PIM-DM domain, HP recommends that you enable PIM-DM on all non-border interfaces of the routers.

  • Page 108: Configuring State Refresh Parameters

    To enable the state refresh feature on all routers in PIM-DM domain: 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 router that directly connects to the multicast source periodically sends state refresh messages.

  • Page 109: Configuring Pim-sm

    Enable IP multicast routing before you configure PIM. With PIM-SM enabled on interfaces, routers can establish PIM neighbor relationship and process PIM messages from their PIM neighbors. When you deploy a PIM-SM domain, HP recommends that you enable PIM-SM on all non-border interfaces.

  • Page 110: Configuring An Rp

    When you configure a C-RP, reserve a relatively large bandwidth between the C-RP and other devices in the PIM-SM domain. In a PIM-SM domain, if you want a router to become the RP, you can configure the router as a C-RP. HP recommends that you configure C-RPs on backbone routers.

  • Page 111: Configuring A Bsr

    The C-RPs periodically send advertisement messages to the BSR, which collects RP set information. You can configure the interval for sending the advertisement messages. The holdtime option in C-RP advertisement messages defines the C-RP lifetime for the advertising C-RP. The BSR starts a holdtime timer for a C-RP after the BSR receives an advertisement message. If the BSR does not receive any advertisement message when the timer expires, it regards the C-RP failed or unreachable.

  • Page 112

    All routers use the same hash algorithm to get an RP for a specific multicast group. Configuring a legal BSR address range enables filtering of BSMs based on the address range, which prevents a maliciously configured host from masquerading as a BSR. The same configuration must be made on all routers in the PIM-SM domain.

  • Page 113: Configuring Multicast Source Registration

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure a PIM domain By default, no PIM domain border pim bsr-boundary border. is configured. Disabling the BSM semantic fragmentation function Generally, a BSR periodically advertises the RP-set information in BSMs within the PIM-SM domain. It encapsulates a BSM in an IP datagram.

  • Page 114: Configuring Switchover To Spt

    In view of information integrity of a register message in the transmission process, you can configure the device to calculate the checksum based on the entire register message. If a device that does not support this function is present on the network, you can configure the device to calculate the checksum based on the register message header.

  • Page 115: Configuration Prerequisites

    Enabling BIDIR-PIM Because BIDIR-PIM is implemented on the basis of PIM-SM, you must enable PIM-SM before you enable BIDIR-PIM. When you deploy a BIDIR-PIM domain, HP recommends that you enable PIM-SM on all non-border interfaces of the domain. IMPORTANT: All interfaces on a device must be enabled with the same PIM mode.

  • Page 116

    Then, it organizes the C-RP information into the RP-set information, which is flooded throughout the entire network. Then, the other routers in the network can determine the RPs for different multicast group ranges based on the RP-set information. HP recommends that you configure C-RPs on backbone routers.

  • Page 117

    In a BIDIR-PIM domain, one DF election per RP is implemented on all PIM-enabled interfaces. To avoid unnecessary DF elections, HP recommends not configuring multiple RPs for BIDIR-PIM. This configuration sets a limit on the number of BIDIR-PIM RPs. If the number of RPs exceeds the limit, excess RPs do not take effect and can be used only for DF election rather than multicast data forwarding.

  • Page 118

    Initially, each C-BSR regards itself as the BSR of the BIDIR-PIM domain and sends BSMs to other routers in the domain. When a C-BSR receives the BSM from another C-BSR, it compares its own priority with the priority carried in the message. The C-BSR with a higher priority wins the BSR election. If a tie exists in the priority, the C-BSR with a higher IP address wins.

  • Page 119

    A PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope. A number of PIM domain border interfaces partition a network into different BIDIR-PIM domains. Bootstrap messages cannot cross a domain border in either direction. Perform the following configuration on routers that you want to configure as a PIM domain border.

  • Page 120: 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 Task (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 are interoperable at the network layer.

  • Page 121: Configuring Common Pim Features

    Configuration guidelines Perform the following configuration on all routers in the PIM-SSM domain. • • Make sure the same SSM group range is configured on all routers in the entire domain. Otherwise, multicast information cannot be delivered through the SSM model. When a member of a multicast group in the SSM group range sends an IGMPv1 or IGMPv2 report •...

  • Page 122: Configuring A Hello Message Filter

    A filter can filter not only independent multicast data but also multicast data encapsulated in register messages. Generally, a filter nearer to the multicast source has a better filtering effect. To configure a multicast data filter: Step Command Remarks Enter system view. system-view pim [ vpn-instance Enter PIM view.

  • Page 123

    The LAN delay defines the PIM message propagation delay. The override interval defines a period for a router to override a prune message. If the propagation delay or override interval on different PIM routers on a shared-media LAN are different, the largest ones apply. 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.

  • Page 124: Configuring Common Pim Timers

    If you configure common PIM timers in both PIM view and interface view, the configuration in interface view always takes precedence. TIP: For a network without special requirements, HP recommends using the defaults. Configuring common PIM timers globally Step...

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

    Step Command Remarks pim [ vpn-instance Enter PIM view. vpn-instance-name ] Set the interval to send hello timer hello interval The default setting is 30 seconds. messages. The default setting is 60 seconds. Set the interval to send NOTE: timer join-prune interval join/prune messages.

  • Page 126: Enabling Bfd For Pim

    Enabling BFD for PIM PIM uses hello messages to elect a DR for a shared-media network. The elected DR is the only multicast forwarder on the shared-media network. If the DR fails, a new DR election process will start after the DR ages out. However, it might take a long period of time before other routers detect the link failures and trigger a new DR election.

  • Page 127: Pim Configuration Examples

    Task Command display pim [ vpn-instance vpn-instance-name ] routing-table [ group-address [ mask { mask-length | mask } ] | source-address [ mask Display PIM routing table { mask-length | mask } ] | flags flag-value | fsm | incoming-interface information.

  • Page 128

    Table 6 Interface and IP address assignment Device Interface IP address Switch A VLAN-interface 100 10.110.1.1/24 Switch A VLAN-interface 103 192.168.1.1/24 Switch B VLAN-interface 200 10.110.2.1/24 Switch B VLAN-interface 101 192.168.2.1/24 Switch C VLAN-interface 200 10.110.2.2/24 Switch C VLAN-interface 102 192.168.3.1/24 Switch D VLAN-interface 300...

  • Page 129

    [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim dm [SwitchD-Vlan-interface103] quit [SwitchD] interface vlan-interface 101 [SwitchD-Vlan-interface101] pim dm [SwitchD-Vlan-interface101] quit [SwitchD] interface vlan-interface 102 [SwitchD-Vlan-interface102] pim dm [SwitchD-Vlan-interface102] quit Verifying the configuration # Display PIM information on Switch D. [SwitchD] display pim interface Interface NbrCnt HelloInt DR-Pri...

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

    Upstream interface: Vlan-interface103 Upstream neighbor: 192.168.1.2 RPF prime neighbor: 192.168.1.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-dm, UpTime: 00:04:25, Expires: - # Display the PIM routing table information on Switch D. [SwitchD] display pim routing-table Total 0 (*, G) entry;...

  • Page 131

    Figure 46 Network diagram Receiver Host A Switch A Vlan-int100 Vlan-int102 Host B Vlan-int102 Receiver Vlan-int300 Vlan-int105 Vlan-int103 Vlan-int200 Vlan-int105 Vlan-int103 Source Vlan-int104 Switch D Switch E Switch B Host C 10.110.5.100/24 Vlan-int104 Vlan-int200 PIM-SM Host D Switch C Table 7 Interface and IP address assignment Device Interface IP address...

  • Page 132

    Configure OSPF on all switches on the PIM-SM network to meet the following requirements: (Details not shown.) The switches are interoperable at the network layer. The switches can dynamically update their routing information. Enable IP multicast routing, and enable IGMP and PIM-SM: # On Switch A, enable IP multicast routing.

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

    [SwitchA] display pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan100 10.110.1.1 (local) Vlan101 192.168.1.2 Vlan102 192.168.9.2 # Display BSR information on Switch A. [SwitchA] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 Elected BSR address: 192.168.9.2 Priority: 64 Hash mask length: 30 Uptime: 00:11:18 # Display BSR information on Switch E.

  • Page 134

    Source 1 and Source 2 send different multicast data to the multicast group 239.1.1.1. Host A receives • the multicast data only from Source 1, and Host B receives the multicast data only from Source 2. Source 3 sends multicast data to the multicast group 224.1.1.1. Host C is a multicast receiver for the multicast group 224.1.1.1.

  • Page 135

    Device Interface IP address Switch C VLAN-interface 105 10.110.5.1/24 Switch C VLAN-interface 103 10.110.2.2/24 Switch C VLAN-interface 106 10.110.6.1/24 Switch D VLAN-interface 105 10.110.5.2/24 Switch D VLAN-interface 108 10.110.7.1/24 Switch D VLAN-interface 107 10.110.8.1/24 Switch E VLAN-interface 400 192.168.4.1/24 Switch E VLAN-interface 104 10.110.4.2/24 Switch E...

  • Page 136

    # Enable PIM-SM on VLAN-interface 101. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit # Enable IP multicast routing, IGMP, and PIM-SM on Switch E and Switch I in the same way Switch A is configured. (Details not shown.) # On Switch B, enable IP multicast routing.

  • Page 137

    [SwitchD-Vlan-interface107] quit Configure C-BSRs and C-RPs: # On Switch B, configure the service scope of RP advertisements. [SwitchB] acl number 2001 [SwitchB-acl-basic-2001] rule permit source 239.0.0.0 0.255.255.255 [SwitchB-acl-basic-2001] quit # Configure VLAN-interface 101 as a C-BSR and a C-RP for admin-scoped zone 1. [SwitchB] pim [SwitchB-pim] c-bsr 10.110.1.2 scope 239.0.0.0 8 [SwitchB-pim] c-rp 10.110.1.2 group-policy 2001...

  • Page 138

    Hash mask length: 30 # Display BSR information on Switch D. [SwitchD] display pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:44 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:01:12 Elected BSR address: 10.110.5.2 Priority: 64 Hash mask length: 30...

  • Page 139: Bidir-pim Configuration Example

    Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 00:03:42 00:01:48 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.5.2 (local) 00:06:54 00:02:41 # Display RP information on Switch F. [SwitchF] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address...

  • Page 140

    Device Interface IP address Switch A VLAN-interface 101 10.110.1.1/24 Switch B VLAN-interface 200 192.168.2.1/24 Switch B VLAN-interface 101 10.110.1.2/24 Switch B VLAN-interface 102 10.110.2.1/24 Switch C VLAN-interface 102 10.110.2.2/24 Switch C VLAN-interface 103 10.110.3.1/24 Switch C Loopback 0 1.1.1.1/32 Switch D VLAN-interface 300 192.168.3.1/24 Switch D...

  • Page 141

    [SwitchB] multicast routing [SwitchB-mrib] quit # Enable IGMP on VLAN-interface 200 (the interface that connects to the receiver host). [SwitchB] interface vlan-interface 200 [SwitchB-Vlan-interface200] igmp enable [SwitchB-Vlan-interface200] quit # Enable PIM-SM on the other interfaces. [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] pim sm...

  • Page 142

    [SwitchD] interface vlan-interface 103 [SwitchD-Vlan-interface103] pim sm [SwitchD-Vlan-interface103] quit # Enable BIDIR-PIM. [SwitchD] pim [SwitchD-pim] bidir-pim enable [SwitchD-pim] quit On Switch C, configure VLAN interface 102 as the C-BSR, and Loopback 0 as the C-RP for the entire BIDIR-PIM domain. [SwitchC-pim] c-bsr 10.110.2.2 [SwitchC-pim] c-rp 1.1.1.1 bidir [SwitchC-pim] quit...

  • Page 143: 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 the DF for multicast forwarding on Switch B. [SwitchB] display multicast forwarding df-info Total 1 RP, 1 matched 00001.

  • Page 144

    Host A and Host C are multicast receivers in 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 49 Network diagram Receiver Host A Switch A...

  • Page 145

    Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 49. (Details not shown.) Configure OSPF on the switches in the PIM-SSM domain to meet the following requirements: (Details not shown.) The switches are interoperable at the network layer. The switches can dynamically update their routing information.

  • Page 146: Troubleshooting Pim

    # Send an IGMPv3 report from Host A to join the multicast source and group (10.1 10.5.100/24, 232.1.1.1). (Details not shown.) # Display PIM routing table information on Switch A. [SwitchA] display pim routing-table Total 0 (*, G) entry; 1 (S, G) entry (10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:13:25...

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

    the router does not have a route to the multicast source, or if PIM-DM is not enabled on the RPF interface toward the multicast source, the router cannot create an (S, G) entry. On a PIM-SM network, when a router wants to join the SPT, the router will create an (S, G) entry. The •...

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

    If an ACL is defined by the source-policy command, and the multicast packets cannot match the • ACL rule, PIM cannot create the routing entries for the packets. Solution Use display current-configuration to verify the multicast forwarding boundary settings. Use multicast boundary to change the multicast forwarding boundary settings to make the multicast packet able to cross the boundary.

  • Page 149

    Solution Use display ip routing-table to verify that unicast routes to the C-RPs and the BSR are available on each router and that a route is available between each C-RP and the BSR. Make sure each C-RP has a unicast route to the BSR, the BSR has a unicast route to each C-RP, and each router on the network has unicast routes to the C-RPs.

  • Page 150: Configuring Msdp

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

  • Page 151

    Figure 50 MSDP peer locations in the network As shown in Figure 50, 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: •...

  • Page 152

    Figure 51 Inter-domain multicast delivery through MSDP The process of implementing PIM-SM inter-domain multicast delivery by leveraging MSDP peers is as follows: The multicast source in PIM-SM 1 sends the first multicast packet to multicast group G. When DR 1 receives the multicast packet, it encapsulates the multicast data within a register message and sends the register message to RP 1.

  • Page 153

    By now, the subsequent multicast data flows to RP 2 along the SPT, and then from RP 2 to the receiver-side DR along the RPT. After receiving the multicast data, the receiver-side DR 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.

  • Page 154: Msdp Support For Vpns

    Figure 52 Intra-domain Anycast RP through MSDP The operating process of Anycast RP through MSDP is as follows: After receiving the multicast data from Source, the source-side DR registers with the closest RP (RP 1 in this example). After receiving the IGMP report message from the receiver, the receiver-side DR sends a join message toward the closest RP (RP 2 in this example).

  • Page 155: Msdp Configuration Task List

    MSDP configuration task list Task at a glance Configuring basic MSDP functions: • (Required.) Enabling MSDP • (Required.) Creating an MSDP peering connection • (Optional.) Configuring a static RPF peer Configuring an MSDP peering connection: • (Optional.) Configuring the description for an MSDP peer •...

  • Page 156: Creating An Msdp Peering Connection

    MSDP peers. If an MSDP peer and a BGP peer share an interface at the same time, HP recommends that you configure the same IP address for the MSDP peer and the BGP peer.

  • Page 157

    Configuration prerequisites Before you configure an MSDP peering connection, complete the following tasks: • Configure a unicast routing protocol so that all devices in the domain are interoperable at the network layer. Configure basic MSDP functions. • Configuring the description for an MSDP peer MSDP peer descriptions help administrators easily distinguish between different MSDP peers and better manage them.

  • Page 158: Controlling Msdp Peering Connections

    Controlling MSDP peering connections MSDP peers are interconnected over TCP (port number 639). You can tear down or re-establish MSDP peering connections to control SA message exchange between the MSDP peers. When the connection between two MSDP peers is torn down, SA messages are no longer delivered between them, and the TCP connection is closed without any connection setup attempt.

  • Page 159: Configuring Sa Message Contents

    Configure basic MSDP functions. • Configuring SA message contents Some multicast sources send multicast data at an interval longer than the aging time of (S, G) entries. In this case, the source-side DR must encapsulate multicast data packet-by-packet in register messages and send them to the source-side RP.

  • Page 160: Configuring Sa Message Filtering Rules

    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 Enable the device to send send an SA request message to peer peer-address request-sa-enable SA request messages.

  • Page 161: Configuring The Sa Message Cache

    Step Command Remarks Configure the lower TTL threshold for multicast data peer peer-address minimum-ttl The default setting is 0. packets encapsulated in SA ttl-value messages. Configuring the SA message cache To reduce the time spent in obtaining the multicast information, enable the SA message cache mechanism to locally cache (S, G) entries contained in SA messages on the router.

  • Page 162: Msdp Configuration Examples

    Task Command Display brief information about display msdp [ vpn-instance vpn-instance-name ] brief [ state { connect | MSDP peers. disabled | established | listen | shutdown } ] Display detailed information about display msdp [ vpn-instance vpn-instance-name ] peer-status the MSDP peer status.

  • Page 163

    Figure 53 Network diagram Table 11 Interface and IP address assignment Device Interface IP address Switch A VLAN-interface 103 10.110.1.2/24 Switch A VLAN-interface 100 10.110.2.1/24 Switch A VLAN-interface 200 10.110.3.1/24 Switch B VLAN-interface 103 10.110.1.1/24 Switch B VLAN-interface 101 192.168.1.1/24 Switch B Loopback 0 1.1.1.1/32...

  • Page 164

    Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 53. (Details not shown.) Configure OSPF on the switches to meet the following requirements: (Details not shown.) The switches in each AS are interoperable at the network layer. The switches can dynamically update routing information.

  • Page 165

    [SwitchB-bgp] address-family ipv4 unicast [SwitchB-bgp-ipv4] import-route ospf 1 [SwitchB-bgp-ipv4] peer 192.168.1.2 enable [SwitchB-bgp-ipv4] quit # On Switch C, configure an eBGP peer, and redistribute OSPF routes. [SwitchC] bgp 200 [SwitchC-bgp] router-id 2.2.2.2 [SwitchC-bgp] peer 192.168.1.1 as-number 100 [SwitchC-bgp] address-family ipv4 unicast [SwitchC-bgp-ipv4] import-route ospf 1 [SwitchC-bgp-ipv4] peer 192.168.1.1 enable [SwitchC-bgp-ipv4] quit...

  • Page 166

    [SwitchC] display bgp peer ipv4 BGP local router ID: 2.2.2.2 Local AS number: 1 Total number of peers: 1 Peers in established state: 1 Peer MsgRcvd MsgSent OutQ PrefRcv Up/Down State 192.168.1.1 100 18 00:20:07 Established # Display the BGP routing table on Switch C. [SwitchC] display bgp routing-table ipv4 Total number of routes: 5 BGP local router ID is 2.2.2.2...

  • Page 167: Anycast Rp Configuration

    Peer address State Up/Down time SA count Reset count 192.168.3.1 Established 01:07:57 # Display detailed MSDP peer information on Switch B. [SwitchB] display msdp peer-status MSDP Peer 192.168.1.2; AS 200 Description: Information about connection status: State: Established Up/down time: 00:15:47 Resets: 0 Connection interface: Vlan-interface101 (192.168.1.1) Received/sent messages: 16/16...

  • Page 168

    Figure 54 Network diagram Table 12 Interface and IP address assignment Device Interface IP address Source 1 — 10.110.5.100/24 Source 2 — 10.110.6.100/24 Switch A VLAN-interface 300 10.110.5.1/24 Switch A VLAN-interface 103 10.110.2.2/24 Switch B VLAN-interface 100 10.110.1.1/24 Switch B VLAN-interface 103 10.110.2.1/24 Switch B...

  • Page 169

    Device Interface IP address Switch E VLAN-interface 104 10.110.4.2/24 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 54. (Details not shown.) Configure OSPF on the switches to meet the following requirements: (Details not shown.) The switches are interoperable at the network layer.

  • Page 170

    # Configure an MSDP peer on Loopback 0 of Switch B. [SwitchB] msdp [SwitchB-msdp] originating-rp loopback 0 [SwitchB-msdp] peer 2.2.2.2 connect-interface loopback 0 [SwitchB-msdp] quit # Configure an MSDP peer on Loopback 0 of Switch D. [SwitchD] msdp [SwitchD-msdp] originating-rp loopback 0 [SwitchD-msdp] peer 1.1.1.1 connect-interface loopback 0 [SwitchD-msdp] quit Verifying the configuration...

  • Page 171

    Protocol: igmp, UpTime: 00:15:04, Expires: - (10.110.5.100, 225.1.1.1) RP: 10.1.1.1 (local) Protocol: pim-sm, Flag: SPT 2MSDP ACT UpTime: 00:46:28 Upstream interface: Vlan-interface103 Upstream neighbor: 10.110.2.2 RPF prime neighbor: 10.110.2.2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-sm, UpTime: - , Expires: The output shows that Switch B now acts as the RP for Source 1 and Host A.

  • Page 172: Sa Message Filtering Configuration

    Protocol: pim-sm, UpTime: - , Expires: The output shows that Switch D now acts as the RP for Source 2 and Host B. SA message filtering configuration Network requirements As shown in Figure 55, OSPF runs within and among the PIM-SM domains to provide unicast routing. Set up an MSDP peering relationship between Switch A and Switch C and between Switch C and Switch Source 1 sends multicast data to multicast groups 225.1.1.0/30 and 226.1.1.0/30, and Source 2 sends multicast data to the multicast group 227.1.1.0/30.

  • Page 173

    Device Interface IP address Switch B VLAN-interface 200 10.110.3.1/24 Switch B VLAN-interface 102 10.110.2.2/24 Switch B VLAN-interface 103 192.168.2.1/24 Switch C VLAN-interface 300 10.110.4.1/24 Switch C VLAN-interface 104 10.110.5.1/24 Switch C VLAN-interface 101 192.168.1.2/24 Switch C VLAN-interface 103 192.168.2.2/24 Switch C Loopback 0 2.2.2.2/32 Switch D...

  • Page 174

    # Configure a PIM domain border on Switch C. [SwitchC] interface vlan-interface 101 [SwitchC-Vlan-interface101] pim bsr-boundary [SwitchC-Vlan-interface101] quit [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] pim bsr-boundary [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 104 [SwitchC-Vlan-interface104] pim bsr-boundary [SwitchC-Vlan-interface104] quit # Configure PIM domain borders on Switch A, Switch B, and Switch D in the same way Switch C is configured.

  • Page 175: Troubleshooting Msdp

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

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

    The TCP connection setup fails if the local interface address is not consistent with the MSDP peer • address configured on the peer router. If no route is available between the MSDP peers, the TCP connection setup fails. • Solution Use the display ip routing-table command to verify that the unicast route between the routers is reachable.

  • Page 177

    When an MSDP peer receives an SA message, it performs an RPF check on the message. If the • MSDP peer finds that the remote RP address is the local RP address, it discards the SA message. Solution Use the display ip routing-table command to verify that the unicast route between the routers is reachable.

  • Page 178: Configuring Multicast Vpn

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

  • Page 179

    can consider these instances on PE 1 to be independent virtual devices, which are PE 1', PE 1", and PE 1'". Each virtual device works on a plane, as shown in Figure Figure 57 Multicast in multiple VPN instances Through multicast VPN, multicast data of VPN A for a multicast group can arrive at only multicast receivers in Site 1, Site 3, and Site 5 of VPN A.

  • Page 180: Md-vpn Overview

    MD-VPN overview The basic MD-VPN concepts are described in Table Table 14 Basic MD-VPN concepts Concept Description An MD is a set of VPN instances running on PE devices that can send multicast traffic to each other. Each MD uniquely corresponds to the Multicast domain (MD) same set of VPN instances.

  • Page 181

    An MD logically defines the transmission boundary of the multicast traffic of a specific VPN over the • public network. It also physically identifies all the PE devices that support that VPN instance on the public network. Different VPN instances correspond to different MDs. As shown in Figure 57, the ellipse area in the center of each VPN instance plane represents an MD...

  • Page 182

    An MD is assigned a unique data-group address range for MDT switchover. When a PE device • keeps receiving a VPN multicast stream that entered the public network for a period of time, the PE does the following: Selects an address that is least referenced from the data-group address range. Uses the address to encapsulate the multicast packets for that VPN.

  • Page 183

    PE-PE PIM neighboring relationship—Established between PE devices that are in the same VPN • instance after they receive the PIM hello packets. PE-CE PIM neighboring relationship—Established between a PE interface that is bound with the • VPN instance and the peer interface on the CE device over the link. Protocols and standards RFC 6037, Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs How MD-VPN works...

  • Page 184

    Encapsulates the PIM protocol packet of the private network into a public network multicast data packet. PE 1 does this by specifying the source address as the IP address of the MD source interface and the multicast group address as the default-group address. Sends the multicast data packet to the public network.

  • Page 185: Default-mdt-based Delivery

    The public network interface of PE 1 registers the multicast source with the public network RP, and the public network RP initiates a join to PE 1. A (11.1.1.1, 239.1.1.1) state entry is created on each device along the path on the public network. At the same time, PE 2 and PE 3 separately initiate a similar register process.

  • Page 186

    Figure 62 Transmission of multicast protocol packets BGP: 11.1.3.1/24 PE 3 Source Receiver CE 1 CE 2 PE 1 PE 2 Site 1 Site 2 BGP: 11.1.1.1/24 BGP: 11.1.2.1/24 S: 192.1.1.1/24 Public instance BGP peers G: 225.1.1.1 VPN instance join (*, 225.1.1.1) Default-group: 239.1.1.1 Public instance join (11.1.2.1, 239.1.1.1) The multicast protocol packet is delivered as follows:...

  • Page 187

    VPN multicast data packets are forwarded across the public network differently in the following circumstances: If PIM-DM or PIM-SSM is running in the VPN, the multicast source forwards multicast data packets • to the receivers along the VPN SPT across the public network. When PIM-SM is running in the VPN: •...

  • Page 188: Mdt Switchover

    CE 1 forwards the VPN multicast data packet along an SPT to PE 1, and the VPN instance on PE 1 examines the MVRF. If the outgoing interface list of the forwarding entry contains an MTI, PE 1 processes the VPN multicast data packet as described in step 3.

  • Page 189: Inter-as Md Vpn

    After sending the MDT switchover message, PE 1 waits a certain length of time (known as the data-delay period). After this period of time, PE 1 starts using the default-group address to encapsulate the VPN multicast data. The multicast data is then forwarded down the data-MDT. After the multicast traffic is switched from the default-MDT to the data-MDT, PE 1 continues sending MDT switchover messages periodically.

  • Page 190: Multicast Vpn Configuration Task List

    Figure 64 VPN instance-VPN instance interconnectivity By using this method, a separate MD must be established within each AS. VPN multicast data traffic between different ASs is transmitted between the two MDs. Because only VPN multicast data traffic is forwarded between ASBRs, different PIM modes can run within different ASs.

  • Page 191: Configuring Md-vpn

    Task at a glance (Required.) Creating the MD for a VPN instance (Required.) Specifying the default-group address (Required.) Specifying the MD source interface (Optional.) Configuring MDT switchover parameters (Optional.) Enabling data-group reuse logging The MTI interfaces are automatically created and bound with the VPN instance when you create the MD for the VPN instance.

  • Page 192: Creating The Md For A Vpn Instance

    Step Command Remarks Enter system view. system-view By default, no VPN instance exists on the device. Create a VPN instance and ip vpn-instance vpn-instance-name For more information about this enter VPN instance view. command, see MPLS Command Reference. By default, no RD is configured for a VPN instance.

  • Page 193: Specifying The Md Source Interface

    Step Command Remarks Enter system view. system-view multicast-domain vpn-instance Enter MD view. vpn-instance-name Specify default-group By default, no default-group default-group group-address address. address is specified. Specifying the MD source interface The MTI uses the IP address of the MD source interface as the source address to encapsulate the VPN multicast packets.

  • Page 194: Enabling Data-group Reuse Logging

    Step Command Remarks By default, no data-group address Configure data-group data-group group-address range is configured and multicast address range { mask-length | mask } [ acl traffic never switches to a switchover criteria. acl-number ] data-MDT. Optional. Configure data-delay data-delay delay period.

  • Page 195: Multicast Vpn Configuration Examples

    Task Command Display the default-group display multicast-domain [ vpn-instance vpn-instance-name ] information. default-group Multicast VPN configuration examples This section provides examples of configuring multicast VPN on switches. Intra-AS MD VPN configuration example Network requirements Item Network requirements • In VPN instance a, S 1 is a multicast source, and R 1, R 2 and R 3 are receivers. •...

  • Page 196

    Item Network requirements • Enable PIM-SM on all interfaces of the P device. • Enable PIM-SM on all public and private network interfaces that do not have attached receiver hosts on PE 1, PE 2, and PE 3. • Enable PIM-SM on all interfaces that do not have attached receiver hosts on CE a1, CE a2, CE a3, CE b1, and CE b2.

  • Page 197

    Device Interface IP address Device Interface IP address VLAN-interface 19 192.168.8.2/24 CE a2 VLAN-interface 14 10.110.4.2/24 Loopback 1 2.2.2.2/32 CE a2 VLAN-interface 16 10.110.12.1/24 PE 1 VLAN-interface 12 192.168.6.1/24 CE a2 Loopback 1 22.22.22.22/32 PE 1 VLAN-interface 20 10.110.1.1/24 CE a3 VLAN-interface 50 10.110.10.1/24 PE 1...

  • Page 198

    [PE1-md-a] data-group 225.2.2.0 28 [PE1-md-a] quit # Assign an IP address to the public network interface VLAN-interface 12, and enable PIM-SM, MPLS, and LDP on it. [PE1] interface vlan-interface 12 [PE1-Vlan-interface12] ip address 192.168.6.1 24 [PE1-Vlan-interface12] pim sm [PE1-Vlan-interface12] mpls enable [PE1-Vlan-interface12] mpls ldp enable [PE1-Vlan-interface12] quit # Bind VLAN-interface 20 with VPN instance a, assign an IP address to VLAN-interface 20, and...

  • Page 199

    [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.0.0 0.0.255.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.0.0.0 [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 200

    [PE2-vpn-instance-a] vpn-target 100:1 import-extcommunity [PE2-vpn-instance-a] quit # Enable IP multicast routing in VPN instance a. [PE2] multicast routing vpn-instance a [PE2-mrib-a] quit # Create the MD for VPN instance a, and specify the default-group, MD source interface, and data-group address range for it. [PE2] multicast-domain vpn-instance a [PE2-md-a] default-group 239.1.1.1 [PE2-md-a] source loopback 1...

  • Page 201

    [PE2-bgp-ipv4-a] import-route rip 2 [PE2-bgp-ipv4-a] import-route direct [PE2-bgp-ipv4-a] quit [PE2-bgp-a] quit [PE2–bgp] ip vpn-instance b [PE2-bgp-b] address-family ipv4 [PE2-bgp-ipv4-b] import-route rip 3 [PE2-bgp-ipv4-b] import-route direct [PE2-bgp-ipv4-b] quit [PE2-bgp-b] quit [PE2–bgp] address-family vpnv4 [PE2–bgp-vpnv4] peer vpn-g enable [PE2–bgp-vpnv4] quit [PE2–bgp] quit # Configure OSPF.

  • Page 202

    [PE3] multicast routing vpn-instance a [PE3-mrib-a] quit # Create the MD for VPN instance a, and specify the default-group, MD source interface, and data-group address range for it. [PE3] multicast-domain vpn-instance a [PE3-md-a] default-group 239.1.1.1 [PE3-md-a] source loopback 1 [PE3-md-a] data-group 225.2.2.0 28 [PE3-md-a] quit # Create VPN instance b, and configure an RD and route target attributes for it.

  • Page 203

    # Bind VLAN-interface 18 with VPN instance b, assign an IP address to VLAN-interface 18, and enable PIM-SM on the interface. [PE3] interface vlan-interface 18 [PE3-Vlan-interface18] ip binding vpn-instance b [PE3-Vlan-interface18] ip address 10.110.6.1 24 [PE3-Vlan-interface18] pim sm [PE3-Vlan-interface18] quit # Assign an IP address to Loopback 1, and enable PIM-SM on the interface.

  • Page 204

    [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.0.0 0.0.255.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure RIP. [PE3] rip 2 vpn-instance a [PE3-rip-2] network 10.0.0.0 [PE3-rip-2] import-route bgp [PE3-rip-2] quit [PE3] rip 3 vpn-instance b [PE3-rip-3] network 10.0.0.0 [PE3-rip-3] network 33.0.0.0 [PE3-rip-3] import-route bgp [PE3-rip-3] return...

  • Page 205

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

  • Page 206

    [CEb1] interface vlan-interface 13 [CEb1-Vlan-interface13] ip address 10.110.3.2 24 [CEb1-Vlan-interface13] pim sm [CEb1-Vlan-interface13] quit # Configure RIP. [CEb1] rip 3 [CEb1-rip-3] network 10.0.0.0 Configure CE a2: # Configure CE a2: <CEa2> system-view [CEa2] multicast routing [CEa2-mrib] quit # Assign an IP address to VLAN-interface 40, and enable IGMP on this interface. [CEa2] interface vlan-interface 40 [CEa2-Vlan-interface40] ip address 10.110.9.1 24 [CEa2-Vlan-interface40] igmp enable...

  • Page 207

    # Assign an IP address to VLAN-interface 50, and enable IGMP on the interface. [CEa3] interface vlan-interface 50 [CEa3-Vlan-interface50] ip address 10.110.10.1 24 [CEa3-Vlan-interface50] igmp enable [CEa3-Vlan-interface50] quit # Assign an IP address to VLAN-interface 17, and enable PIM-SM on the interface. [CEa3] interface vlan-interface 17 [CEa3-Vlan-interface17] ip address 10.110.5.2 24 [CEa3-Vlan-interface17] pim sm...

  • Page 208: Inter-as Md Vpn Configuration Example

    239.1.1.1 1.1.1.2 MTunnel1 # Display information about the default-groups in VPN instances on PE 3. [PE3] display multicast-domain default-group Group address Source address Interface VPN instance 239.1.1.1 1.1.1.3 MTunnel0 239.2.2.2 1.1.1.3 MTunnel1 Inter-AS MD VPN configuration example Network requirements Item Network requirements •...

  • Page 209

    Item Network requirements MSDP Establish an MSDP peering relationship between PE 2 and PE 3 on their Loopback 1. Figure 67 Network diagram Table 16 Interface and IP address assignment Device Interface IP address Device Interface IP address — 10.11.5.2/24 —...

  • Page 210

    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 # Configure an MPLS LSR ID, and enable LDP. [PE1] mpls lsr-id 1.1.1.1 [PE1] mpls ldp [PE1-ldp] quit...

  • Page 211

    [PE1-md-b] source loopback 1 [PE1-md-b] data-group 225.4.4.0 28 [PE1-md-b] quit # Assign an IP address to the public network interface VLAN-interface 2, and enable PIM-SM, MPLS, and LDP on it. [PE1] interface vlan-interface 2 [PE1-Vlan-interface2] ip address 10.10.1.1 24 [PE1-Vlan-interface2] pim sm [PE1-Vlan-interface2] mpls enable [PE1-Vlan-interface2] mpls ldp enable [PE1-Vlan-interface2] quit...

  • Page 212

    [PE1-bgp-ipv4-b] import-route ospf 3 [PE1-bgp-ipv4-b] import-route direct [PE1-bgp-ipv4-b] quit [PE1-bgp-b] quit [PE1–bgp] address-family ipv4 [PE1-bgp-ipv4] peer pe1-pe2 enable [PE1-bgp-ipv4] peer pe1-pe2 label-route-capability [PE1-bgp-ipv4] quit [PE1–bgp] address-family vpnv4 [PE1–bgp-vpnv4] peer pe1-pe4 enable [PE1–bgp-vpnv4] quit [PE1–bgp] 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 [PE1-ospf-1-area-0.0.0.0] network 10.10.0.0 0.0.255.255...

  • Page 213

    [PE2-Vlan-interface2] mpls ldp enable [PE2-Vlan-interface2] quit # Assign an IP address to the public network interface VLAN-interface 3, and enable PIM-SM and MPLS on it. [PE2] interface vlan-interface 3 [PE2-Vlan-interface3] ip address 192.168.1.1 24 [PE2-Vlan-interface3] pim sm [PE2-Vlan-interface3] mpls enable [PE2-Vlan-interface3] quit # Assign an IP address to Loopback 1, and enable PIM-SM on this interface.

  • Page 214

    [PE2-bgp-ipv4] peer pe2-pe3 enable [PE2-bgp-ipv4] peer pe2-pe3 route-policy map1 export [PE2-bgp-ipv4] peer pe2-pe3 label-route-capability [PE2-bgp-ipv4] import-route ospf 1 [PE2-bgp-ipv4] quit [PE2–bgp] quit # Configure OSPF. [PE2] ospf 1 [PE2-ospf-1] area 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 11.11.11.11 0.0.0.0 [PE2-ospf-1-area-0.0.0.0] network 10.10.0.0 0.0.255.255 [PE2-ospf-1-area-0.0.0.0] quit [PE2-ospf-1] quit # Configure a routing policy.

  • Page 215

    # Assign an IP address to Loopback 1, and enable PIM-SM on this interface. [PE3] interface loopback 1 [PE3-LoopBack1] ip address 1.1.1.3 32 [PE3-LoopBack1] pim sm [PE3-LoopBack1] quit # Assign an IP address to Loopback 2, and enable PIM-SM on this interface. [PE3] interface loopback 2 [PE3-LoopBack2] ip address 22.22.22.22 32 [PE3-LoopBack2] pim sm...

  • Page 216

    [PE3-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 22.22.22.22 0.0.0.0 [PE3-ospf-1-area-0.0.0.0] network 10.10.0.0 0.0.255.255 [PE3-ospf-1-area-0.0.0.0] quit [PE3-ospf-1] quit # Configure a routing policy. [PE3] route-policy map1 permit node 10 [PE3-route-policy-map1-10] apply mpls-label [PE3-route-policy-map1-10] quit [PE3] route-policy map2 permit node 10 [PE3-route-policy-map2-10] if-match mpls-label [PE3-route-policy-map2-10] apply mpls-label [PE3-route-policy-map2-10] quit Configure PE 4:...

  • Page 217

    [PE4] ip vpn-instance b [PE4-vpn-instance-b] route-distinguisher 200:1 [PE4-vpn-instance-b] vpn-target 200:1 export-extcommunity [PE4-vpn-instance-b] vpn-target 200:1 import-extcommunity [PE4-vpn-instance-b] quit # Enable IP multicast routing in VPN instance b. [PE4] multicast routing vpn-instance b [PE4-mrib-b] quit # Create the MD for VPN instance b, and specify the default-group, MD source interface, and data-group address range for it.

  • Page 218

    [PE4-bgp] group pe4-pe1 external [PE4-bgp] peer pe4-pe1 as-number 100 [PE4-bgp] peer pe4-pe1 ebgp-max-hop 255 [PE4-bgp] peer pe4-pe1 connect-interface loopback 1 [PE4-bgp] peer 1.1.1.1 group pe4-pe1 [PE4–bgp] ip vpn-instance a [PE4-bgp-a] address-family ipv4 [PE4-bgp-ipv4-a] import-route ospf 2 [PE4-bgp-ipv4-a] import-route direct [PE4-bgp-ipv4-a] quit [PE4-bgp-a] quit [PE4–bgp] ip vpn-instance b [PE4-bgp-b] address-family ipv4...

  • Page 219

    [CEa1-mrib] quit # Assign an IP address to VLAN-interface 10, and enable PIM-SM on this interface. [CEa1] interface vlan-interface 10 [CEa1-Vlan-interface10] ip address 10.11.5.1 24 [CEa1-Vlan-interface10] pim sm [CEa1-Vlan-interface10] quit # Assign an IP address to VLAN-interface 11, and enable PIM-SM on this interface. [CEa1] interface vlan-interface 11 [CEa1-Vlan-interface11] ip address 10.11.1.2 24 [CEa1-Vlan-interface11] pim sm...

  • Page 220

    [CEb1-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb1-ospf-1-area-0.0.0.0] quit [CEb1-ospf-1] quit Configure CE a2: # Enable IP multicast routing. <CEa2> system-view [CEa2] multicast routing [CEa2-mrib] quit # Assign an IP address to VLAN-interface 30, and enable IGMP on this interface. [CEa2] interface vlan-interface 30 [CEa2-Vlan-interface30] ip address 10.11.7.1 24 [CEa2-Vlan-interface30] igmp enable [CEa2-Vlan-interface30] quit...

  • Page 221: Troubleshooting Md-vpn

    [CEb2-pim] c-bsr 3.3.3.3 [CEb2-pim] c-rp 3.3.3.3 [CEb2-pim] quit # Configure OSPF. [CEb2] ospf 1 [CEb2-ospf-1] area 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0 [CEb2-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255 [CEb2-ospf-1-area-0.0.0.0] quit [CEb2-ospf-1] quit Verifying the configuration # Display information about the default-groups in VPN instances on PE 1. [PE1] display multicast-domain default-group Group address Source address...

  • Page 222: An Mvrf Cannot Be Created

    instance on different PE devices only after the MTI interface obtains an IP address and becomes PIM-enabled. Solution Use the display interface command to examine the MTI interface state and address encapsulation on the MTI. Use the display multicast-domain default-group command to verify that the same default-group address has been configured for the same VPN instance on different PE devices.

  • Page 223: Configuring Mld Snooping

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

  • Page 224

    Figure 69 MLD snooping related ports The following describes the ports involved in MLD snooping, as shown in Figure Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include DRs and MLD • queriers. In Figure 69, Ten-GigabitEthernet 1/1/5 of Switch A and Ten-GigabitEthernet 1/1/5 of Switch B are the router ports.

  • Page 225: How Mld Snooping Works

    NOTE: In MLD snooping, only dynamic ports age out. Static ports never age out. 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.

  • Page 226

    receiver members will receive the report and suppress their own reports. In this case, the switch cannot determine whether the reported IPv6 multicast group still has active members attached to that port. For more information about the MLD report suppression mechanism, see "Configuring MLD."...

  • Page 227: Mld Snooping Configuration Task List

    MLD snooping configuration task list Task at a glance Configuring basic MLD snooping functions: • (Required.) Enabling MLD snooping • (Optional.) Specifying the MLD snooping version • (Optional.) Setting the maximum number of MLD snooping forwarding entries • (Optional.) Configuring parameters for MLD queries and responses Configuring MLD snooping port functions: •...

  • Page 228: Specifying The Mld Snooping Version

    Step Command Remarks Enter system view. system-view Enable MLD snooping By default, MLD snooping is globally and enter mld-snooping disabled. MLD-snooping view. Enable MLD snooping for the By default, MLD snooping is enable vlan vlan-list specified VLANs. disabled for a VLAN. To enable MLD snooping for a VLAN in VLAN view: Step Command...

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

    You can modify the maximum number of MLD snooping forwarding entries. When the number of forwarding entries on the device reaches the upper limit, the device does not automatically remove any existing entries or create new entries. In this case, HP recommends that you manually remove extra entries.

  • Page 230: Configuring Mld Snooping Port Functions

    Configuring parameters for MLD queries and responses globally Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Set the maximum response delay for MLD general max-response-time interval The default setting is 10 seconds. queries. Set the MLD last-listener query last-listener-query-interval interval The default setting is 1 second.

  • Page 231

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

  • Page 232: Enabling Mld Snooping Fast-leave Processing

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

  • Page 233: Configuring Mld Snooping Policies

    Configuring MLD snooping policies Before you configure MLD snooping policies, complete the following tasks: • Enable MLD snooping for the VLAN. Determine the ACL used as the IPv6 multicast group filter. • Determine the maximum number of IPv6 multicast groups that a port can join. •...

  • Page 234: Enabling Dropping Unknown Ipv6 Multicast Data

    You can enable multicast source port filtering either for the specified ports in MLD-snooping view or for the current port in interface view. These configurations have the same priority level. Configuring IPv6 multicast source port filtering globally Step Command Remarks Enter system view.

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

    When the MLD report suppression function is enabled, the Layer 2 switch within a query interval forwards only the first MLD report for the IPv6 multicast group to the Layer 3 device. It does not forward subsequent MLD reports for the same IPv6 multicast group to the Layer 3 device, which reduces the number of packets being transmitted over the network.

  • Page 236: Displaying And Maintaining Mld Snooping

    replacement must also be enabled so a user can switch from the current IPv6 multicast group to a new one. When you enable the IPv6 multicast group replacement function, follow these guidelines: This configuration takes effect on the multicast groups that the port dynamically joins. If you •...

  • Page 237: Mld Snooping Configuration Examples

    Task Command Display information about dynamic display mld-snooping group [ ipv6-group-address | MLD snooping forwarding entries. ipv6-source-address ] * [ vlan vlan-id ] [ verbose ] [ slot slot-number ] Display information about static MLD display mld-snooping static-group [ ipv6-group-address | snooping forwarding entries.

  • Page 238

    Figure 70 Network diagram Receiver Host A Source Receiver XGE1/1/8 XGE1/1/6 XGE1/1/5 XGE1/1/5 XGE1/1/7 1::2/64 2001::1/64 Switch A Host B XGE1/1/6 1::1/64 Router A MLD querier Host C VLAN 100 Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 70.

  • Page 239

    [SwitchA-vlan100] quit # Configure an IPv6 multicast group filter so that the hosts in VLAN 100 can join only the IPv6 multicast group FF1E::101. [SwitchA] acl ipv6 number 2001 [SwitchA-acl6-basic-2001] rule permit source ff1e::101 128 [SwitchA-acl6-basic-2001] quit [SwitchA] mld-snooping [SwitchA–mld-snooping] group-policy 2001 vlan 100 [SwitchA–mld-snooping] quit Verifying the configuration # Send MLD reports from Host A and Host B to join the IPv6 multicast groups FF1E::101 and FF1E::202.

  • Page 240

    Configure Ten-GigabitEthernet 1/1/7 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. Figure 71 Network diagram Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure...

  • Page 241

    [SwitchA] vlan 100 [SwitchA-vlan100] port ten-gigabitethernet 1/1/5 to ten-gigabitethernet 1/1/7 [SwitchA-vlan100] mld-snooping enable [SwitchA-vlan100] quit # Configure Ten-GigabitEthernet 1/1/7 as a static router port. [SwitchA] interface ten-gigabitethernet 1/1/7 [SwitchA-Ten-GigabitEthernet1/1/7] mld-snooping static-router-port vlan 100 [SwitchA-Ten-GigabitEthernet1/1/7] quit Configure Switch B: # Enable MLD snooping globally. <SwitchB>...

  • Page 242: Troubleshooting Mld Snooping

    The output shows that Ten-GigabitEthernet 1/1/7 on Switch A has become a static router port. # Display information about the static MLD snooping forwarding entries in VLAN 100 on Switch C. [SwitchC] display mld-snooping static-group vlan 100 Total 1 entries). VLAN 100: Total 1 entries).

  • Page 243

    Solution Use the display acl ipv6 command to verify that the configured IPv6 ACL meets the IPv6 multicast group filter requirements. Use the display this command in MLD-snooping view or in a corresponding interface view to verify that the correct IPv6 multicast group filter has been applied. If not, use the group-policy or mld-snooping group-policy command to apply the correct IPv6 multicast group filter.

  • Page 244: 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.

  • Page 245

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

  • Page 246: Displaying And Maintaining Ipv6 Pim Snooping

    Step Command Remarks (Optional.) Set the aging The default setting is 210. time for the IPv6 PIM snooping global A global downstream port or a ipv6 pim-snooping graceful-restart downstream ports and global router port is a Layer 2 join-aging-time interval global router ports on the aggregate interface that acts as a new master device in IRF...

  • Page 247

    Figure 73 Network diagram Configuration procedure Assign an IPv6 address and prefix length for each interface according to Figure 73. (Details not shown.) Configure OSPFv3 on the routers to meet the following requirements: (Details not shown.) The switches are interoperable at the network layer. The switches can dynamically update their routing information.

  • Page 248

    [RouterB] interface ten-gigabitethernet 1/1/5 [RouterB-Ten-GigabitEthernet1/1/5] ipv6 pim sm [RouterB-Ten-GigabitEthernet1/1/5] quit [RouterB] interface ten-gigabitethernet 1/1/6 [RouterB-Ten-GigabitEthernet1/1/6] ipv6 pim sm [RouterB-Ten-GigabitEthernet1/1/6] quit Configure Router C: # Enable IPv6 multicast routing. <RouterC> system-view [RouterC] ipv6 multicast routing [RouterC-mrib6] quit # Enable MLD on Ten-GigabitEthernet 1/1/5. [RouterC] interface ten-gigabitethernet 1/1/5 [RouterC-Ten-GigabitEthernet1/1/5] mld enable [RouterC-Ten-GigabitEthernet1/1/5] quit...

  • Page 249

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

  • Page 250: Troubleshooting Ipv6 Pim Snooping

    The output shows the following: • Switch A will forward the multicast data intended for IPv6 multicast group FF1E::101 to only Router Switch A will forward the multicast data intended for IPv6 multicast group FF2E::101 to only Router • Troubleshooting IPv6 PIM snooping This section describes common IPv6 PIM snooping problems and how to troubleshoot them.

  • Page 251: Configuring Ipv6 Multicast Vlans

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

  • Page 252

    Figure 75 Sub-VLAN-based multicast VLAN MLD snooping manages router ports in the IPv6 multicast VLAN and user ports in each sub-VLAN. Switch A sends only one copy of the received IPv6 multicast data to the IPv6 multicast VLAN on Switch B. Switch B replicates the IPv6 multicast data and sends a separate copy to each sub-VLAN of the IPv6 multicast VLAN.

  • Page 253: Ipv6 Multicast Vlan Configuration Task List

    If you have configured both a sub-VLAN-based IPv6 multicast VLAN and a port-based IPv6 • multicast VLAN on a device, the port-based IPv6 multicast VLAN configuration takes effect. HP recommends that you not configure IPv6 multicast VLANs on a device with IP multicast routing • enabled.

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

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

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

    If the total number of the entries exceeds the upper limit value that you are setting, the system does not automatically remove existing entries or create new entries. In this case, HP recommends that you remove extra entries manually.

  • Page 256: Displaying And Maintaining Ipv6 Multicast Vlans

    Step Command Remarks Enter system view. system-view Set the maximum number of IPv6 multicast VLAN ipv6 multicast-vlan entry-limit limit The default setting is 4000. forwarding entries. Displaying and maintaining IPv6 multicast VLANs Execute display commands in any view and reset commands in user view. Task Command Display information about IPv6...

  • Page 257

    Figure 77 Network diagram Configuration procedure Configure Switch A: # Enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Create VLAN 20, and assign Ten-GigabitEthernet 1/1/6 to this VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port ten-gigabitethernet 1/1/6 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM.

  • Page 258

    [SwitchA-Vlan-interface10] quit Configure Switch B: # Enable MLD snooping globally. <SwitchB> system-view [SwitchB] mld-snooping [SwitchB-mld-snooping] quit # Create VLAN 2, assign Ten-GigabitEthernet 1/1/6 to this VLAN, and enable MLD snooping for this VLAN. [SwitchB] vlan 2 [SwitchB-vlan2] port ten-gigabitethernet 1/1/6 [SwitchB-vlan2] mld-snooping enable [SwitchB-vlan2] quit # Create VLAN 3, assign Ten-GigabitEthernet 1/1/7 to this VLAN, and enable MLD snooping for...

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

    Port list(0 in total): # Display information about the IPv6 multicast VLAN forwarding entries on Switch B. [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 the IPv6 multicast VLAN (VLAN 10) is maintaining the sub-VLANs (VLAN 2 through...

  • Page 260

    Configuration procedure Configure Switch A: # Enable IPv6 multicast routing. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Create VLAN 20, and assign Ten-GigabitEthernet 1/1/6 to this VLAN. [SwitchA] vlan 20 [SwitchA-vlan20] port ten-gigabitethernet 1/1/6 [SwitchA-vlan20] quit # Assign an IPv6 address to VLAN-interface 20, and enable IPv6 PIM-DM. [SwitchA] interface vlan-interface 20 [SwitchA-Vlan-interface20] ipv6 address 1::2 64 [SwitchA-Vlan-interface20] ipv6 pim dm...

  • Page 261

    [SwitchB-vlan3] quit # Create VLAN 4, and enable MLD snooping for the VLAN. [SwitchB] vlan 4 [SwitchB-vlan4] mld-snooping enable [SwitchB-vlan4] quit # Configure Ten-GigabitEthernet 1/1/6 as a hybrid port, and configure VLAN 2 as the PVID of the hybrid port. [SwitchB] interface ten-gigabitethernet 1/1/6 [SwitchB-Ten-GigabitEthernet1/1/6] port link-type hybrid [SwitchB-Ten-GigabitEthernet1/1/6] port hybrid pvid vlan 2...

  • Page 262

    IPv6 multicast VLAN 10: Sub-VLAN list(0 in total): Port list(0 in total): XGE1/1/6 XGE1/1/7 XGE1/1/8 # Display information about MLD snooping forwarding entries for the dynamic IPv6 multicast groups on Switch B. [SwitchB] display mld-snooping group Total 1 entries. VLAN 2: Total 1 entries. (::, FF1E::101) Host slots (0 in total): Host ports (3 in total):...

  • Page 263: 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 •...

  • Page 264

    RPF check implementation in IPv6 multicast Implementing an RPF check on each received IPv6 multicast packet would heavily burden the router. The use of an IPv6 multicast forwarding table is the solution to this issue. When the router creates an IPv6 multicast forwarding entry for an IPv6 multicast packet, it sets the RPF interface of the packet as the incoming interface of the forwarding entry.

  • Page 265: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

    interface to the source (the RPF interface) is VLAN-interface 20. This means that the (S, G) entry is correct but the packet traveled along a wrong path. The packet fails the RPF check and Switch C discards the packet. 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.

  • Page 266

    To enable IPv6 multicast routing: Step Command Remarks Enter system view. system-view Enable IPv6 multicast routing ipv6 multicast routing By default, IPv6 multicast routing is and enter IPv6 MRIB view. [ vpn-instance vpn-instance-name ] disabled. 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 are interoperable at the •...

  • Page 267: Configuring An Ipv6 Multicast Forwarding Boundary

    Configuring an IPv6 multicast forwarding boundary Instead of traveling infinitely in a network, the IPv6 multicast data of each IPv6 multicast group travels within a definite scope. A multicast forwarding boundary sets the boundary condition for the IPv6 multicast groups in the specified range. If the destination address of an IPv6 multicast packet matches the set boundary condition, the packet is not forwarded.

  • Page 268: Configuring Ipv6 Multicast Forwarding Between Sub-vlans Of A Super Vlan

    Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface/Layer 2 aggregate interface-number interface view. Configure a static multicast mac-address multicast By default, no static multicast MAC MAC address entry. mac-address vlan vlan-id address entries exist. Configuring IPv6 multicast forwarding between sub-VLANs of a super VLAN A super VLAN is associated with multiple sub-VLANs.

  • Page 269

    Task Command Display information about IPv6 static display mac-address [ mac-address [ vlan vlan-id ] | [ multicast ] multicast MAC address table. [ vlan vlan-id ] [ count ] ] Display information about the interfaces display ipv6 mrib [ vpn-instance vpn-instance-name ] interface maintained by the IPv6 MRIB.

  • Page 270

    Configuration examples IPv6 multicast forwarding over a GRE tunnel Network requirements As shown in Figure 81, IPv6 multicast routing and IPv6 PIM-DM are enabled on Switch A and Switch C. Switch B does not support IPv6 multicast. OSPFv3 is running on Switch A, Switch B, and Switch C. Configure the switches so that the receiver host can receive the IPv6 multicast data from the source.

  • Page 271

    # On Switch C, create service loopback group 1, and specify its service type as Tunnel. <SwitchC> system-view [SwitchC] service-loopback group 1 type tunnel # Add Ten-GigabitEthernet 1/1/7 to service loopback group 1. Ten-GigabitEthernet 1/1/7 does not belong to VLAN 200 or VLAN 102. [SwitchC] interface ten-gigabitethernet 1/1/7 [SwitchC-Ten-GigabitEthernet1/1/7] port service-loopback group 1 [SwitchC-Ten-GigabitEthernet1/1/7] quit...

  • Page 272

    # Display IPv6 PIM routing table information on Switch C. [SwitchC] display ipv6 pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, FF1E::101) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200...

  • Page 273: Configuring Mld

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

  • Page 274

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

  • Page 275: Mldv2 Enhancements

    The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::2. After receiving the MLD done message, the querier sends a configurable number of multicast address specific queries to the group that the host is leaving. The IPv6 multicast addresses queried include both the destination address field and the group address field of the message.

  • Page 276: Mld Support For Vpns

    When MLDv2 runs on the hosts and routers, Host B can explicitly express its interest in the IPv6 multicast data that Source 1 sends to G (denoted as (S1, G)). It can also explicitly express that it does not want to receive the IPv6 multicast data that Source 2 sends to G (denoted as (S2, G)).

  • Page 277: Enabling Mld

    Determine the IPv6 multicast group address and IPv6 multicast source address for static group • member configuration. Determine the ACL rule for IPv6 multicast group filtering. • Enabling MLD Enable MLD on the interface on which IPv6 multicast group memberships are created and maintained. To enable MLD: Step Command...

  • Page 278: Configuring An Ipv6 Multicast Group Filter

    A static member interface does not respond to queries from the MLD querier. When you configure • an interface as a static member interface or cancel this configuration, the interface does not send any MLD report or an MLD done message. This is because the interface is not a real member of the IPv6 multicast group or the IPv6 multicast source and group.

  • Page 279: Enabling Mld Fast-leave Processing

    Enabling MLD fast-leave processing In some applications, such as ADSL dial-up networking, only one multicast receiver host is attached to an interface of the MLD querier. The receiver host might switch frequently from one IPv6 multicast group to another. To allow fast response to the MLD done messages of the host when it switches frequently from one IPv6 multicast group to another, you can enable fast-leave processing on the MLD querier.

  • Page 280: Mld Configuration Examples

    MLD configuration examples Network requirements As shown in Figure VOD streams are sent to receiver hosts in multicast. Receiver hosts of different organizations form • stub networks N1 and N2. Host A and Host C are multicast receiver hosts in N1 and N2, respectively.

  • Page 281

    <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit # Enable MLD on VLAN-interface 100. [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-DM on VLAN-interface 101. [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] ipv6 pim dm [SwitchA-Vlan-interface101] quit # On Switch B, enable IPv6 multicast routing.

  • Page 282

    Verifying the configuration # Display MLD information on VLAN-interface 200 of Switch B. [SwitchB] display mld interface vlan-interface 200 Vlan-interface200(FE80::200:5EFF:FE66:5100): MLD is enabled. MLD version: 1 Query interval for MLD: 125s Other querier present time for MLD: 255s Maximum query response time for MLD: 10s Querier for MLD: FE80::200:5EFF:FE66:5100 (This router) MLD groups reported in total: 1 Troubleshooting MLD...

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

    Inconsistent membership information on the routers on the same subnet Symptom Different memberships are maintained on different MLD routers on the same subnet. Analysis A router running MLD maintains multiple parameters for each interface. Inconsistent MLD interface • parameter configurations for routers on the same subnet result in inconsistent MLD memberships. •...

  • Page 284: 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 is not dependent on any particular IPv6 unicast routing protocol, and it uses the underlying IPv6 unicast routing to generate a routing table with routes.

  • Page 285

    Neighbor discovery In an IPv6 PIM domain, each IPv6 PIM interface periodically multicasts IPv6 PIM hello messages to all other IPv6 PIM routers on the local subnet. Through the exchanging of hello messages, all IPv6 PIM routers discover IPv6 PIM neighbors, maintain IPv6 PIM neighboring relationship with other routers, and build and maintain SPTs.

  • Page 286

    Graft A previously pruned branch might have new downstream receivers. To reduce the latency for resuming the forwarding capability of this branch, a graft mechanism is used as follows: The node that needs to receive the IPv6 multicast data sends a graft message to its upstream node, telling it to rejoin the SPT.

  • Page 287: Ipv6 Pim-sm Overview

    IPv6 PIM-SM overview IPv6 PIM-DM uses the flood-and-prune cycles to build SPTs for IPv6 multicast data forwarding. Although an SPT has the shortest paths from the IPv6 multicast source to the receivers, it is built with a low efficiency. IPv6 PIM-DM is not suitable for large- and medium-sized networks. IPv6 PIM-SM uses the pull mode for IPv6 multicast forwarding, and it is suitable for large-sized and medium-sized networks with sparsely and widely distributed IPv6 multicast group members.

  • Page 288

    Figure 87 DR election As shown in Figure 87, the DR election process is as follows: The routers on the shared-media LAN send hello messages to one another. The hello messages contain the priority for DR election. The router with the highest DR priority is elected as the DR. The router with the highest IPv6 link-local address wins the DR election under one of the following conditions: All the routers have the same DR election priority.

  • Page 289

    The BSR encapsulates the RP-set information in the bootstrap messages (BSMs) and floods the BSMs to the entire IPv6 PIM-SM domain. Figure 88 Information exchange between C-RPs and BSR Based on the information in the RP-set, all routers in the network can select an RP for a specific IPv6 multicast group based on the following rules: The C-RP that is designated to a smallest IPv6 multicast group range wins.

  • Page 290

    RPT building Figure 89 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 89, 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 291

    Figure 90 IPv6 multicast source registration As shown in Figure 90, the IPv6 multicast source registers with the RP as follows: The IPv6 multicast source S sends the first multicast packet to the IPv6 multicast group G. When receiving the multicast packet, the source-side DR that directly connects to the IPv6 multicast source encapsulates the packet into an register message and unicasts the message to the RP.

  • Page 292: Ipv6 Bidir-pim Overview

    To eliminate these weaknesses, IPv6 PIM-SM allows an RP or the receiver-side DR to initiate a switchover to SPT: The RP initiates a switchover to SPT: • After receiving the first (S, G) multicast packet, the RP immediately sends an (S, G) source-specific join message toward the IPv6 multicast source.

  • Page 293

    In IPv6 PIM-SM, an RP must be specified with a real IPv6 address. In IPv6 BIDIR-PIM, an RP can be specified with a virtual IPv6 address, which is called the "rendezvous point address (RPA)." The link corresponding to the RPA's subnet is called the "rendezvous point link (RPL)." All interfaces connected to the RPL can act as the RPs, and they back up one another.

  • Page 294

    Figure 92 RPT building at the receiver side As shown in Figure 92, the process for building a receiver-side RPT is similar to that 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 295: Ipv6 Administrative Scoping Overview

    Figure 93 RPT building at the IPv6 multicast source side As shown in Figure 93, 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 296

    An IPv6 admin-scoped zone is designated to particular IPv6 multicast groups with the same scope field value in their group addresses. Zone border routers (ZBRs) form the boundary of an IPv6 admin-scoped zone. Each IPv6 admin-scoped zone maintains one BSR for IPv6 multicast groups with the same scope field value.

  • Page 297: Ipv6 Pim-ssm Overview

    Figure 95 IPv6 multicast address format An IPv6 admin-scoped zone with a larger scope field value contains an IPv6 admin-scoped zone with a smaller scope field value. The zone with the scope field value of E is the IPv6 global-scoped zone.

  • Page 298: Relationship Among Ipv6 Pim Protocols

    SPT building The decision to build an RPT for IPv6 PIM-SM or an SPT for IPv6 PIM-SSM depends on whether the IPv6 multicast group that the receiver joins is in the IPv6 SSM group range. The IPv6 SSM group range reserved by IANA is FF3x::/32, where "x"...

  • Page 299: Ipv6 Pim Support For Vpns

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

  • Page 300: Ipv6 Pim-dm Configuration Task List

    With IPv6 PIM-DM enabled on interfaces, routers can establish IPv6 PIM neighbor relationship and process IPv6 PIM messages from their IPv6 PIM neighbors. When you deploy an IPv6 PIM-DM domain, HP recommends that you enable IPv6 PIM-DM on all non-border interfaces of routers. IMPORTANT: All the interfaces on a device must operate in the same IPv6 PIM mode in the public network or the same VPN instance.

  • Page 301

    domain to refresh the prune timer state of all the routers on the path. A shared-media subnet can have the state refresh feature only if the state refresh feature is enabled on all IPv6 PIM routers on the subnet. To enable the state refresh feature on all routers in IPv6 PIM-DM domain: Step Command Remarks...

  • Page 302: Configuring Ipv6 Pim-sm

    For more information about the configuration of other timers in IPv6 PIM-DM, see "Configuring common IPv6 PIM timers." To configure the IPv6 PIM-DM graft retry timer: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the graft retry timer is 3 Configure the graft retry timer.

  • Page 303

    With IPv6 PIM-SM enabled on interfaces, routers can establish IPv6 PIM neighbor relationship and process IPv6 PIM messages from their IPv6 PIM neighbors. When you deploy an IPv6 PIM-SM domain, HP recommends that you enable IPv6 PIM-SM on all non-border interfaces. IMPORTANT: All the interfaces on the same router must operate in the same IPv6 PIM mode in the public network or the same VPN instance.

  • Page 304

    The C-RPs periodically send advertisement messages to the BSR, which collects RP set information for the RP election. You can configure the interval for sending the advertisement messages. The holdtime option in C-RP advertisement messages defines the C-RP lifetime for the advertising C-RP. The BSR starts a holdtime timer for a C-RP after it receives an advertisement message from a C-RP.

  • Page 305

    Collects C-RP information from the received advertisement messages from the C-RPs. • • Encapsulates the C-RP information in the RP-set information. Distributes the RP-set information to all routers in the IPv6 PIM-SM domain. • All routers use the same hash algorithm to get an RP for a specific IPv6 multicast group. Configuring a legal BSR address range enables filtering of BSMs based on the address range which prevents a maliciously configured host from masquerading as a BSR.

  • Page 306: Configuring Ipv6 Multicast Source Registration

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configuring an IPv6 PIM By default, no IPv6 PIM domain ipv6 pim bsr-boundary domain border. border is configured. Disabling the BSM semantic fragmentation function Generally, a BSR periodically advertises the RP-set information in BSMs within the IPv6 PIM-SM domain. It encapsulates a BSM in an IPv6 datagram.

  • Page 307

    The ACL does not define a deny or permit action for a matching register message. • In view of information integrity of a register message in the transmission process, you can configure the device to calculate the checksum based on the entire register message. If a device that does not support this function is present on the network, you can configure the device to calculate the checksum based on the register message header.

  • Page 308

    Because IPv6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM, you must enable IPv6 PIM-SM before enabling IPv6 BIDIR-PIM. When you deploy an IPv6 BIDIR-PIM domain, HP recommends that you enable IPv6 PIM-SM on all non-border interfaces of the domain.

  • Page 309

    When you configure a C-RP, reserve a large bandwidth between the C-RP and other devices in the IPv6 • BIDIR-PIM domain. HP recommends that you configure C-RPs on backbone routers. • In an IPv6 BIDIR-PIM domain, if you want a router to become the RP, you can configure the router as a C-RP.

  • Page 310

    In an IPv6 BIDIR-PIM domain, one DF election per RP is implemented on all IPv6 PIM-enabled interfaces. To avoid unnecessary DF elections, HP recommends not configuring multiple RPs for BIDIR-PIM. This configuration sets a limit on the number of IPv6 BIDIR-PIM RPs. If the number of RPs exceeds the limit, excess RPs do not take effect and can be used only for DF election rather than IPv6 multicast data forwarding.

  • Page 311

    Initially, each C-BSR regards itself as the BSR of the IPv6 BIDIR-PIM domain and sends BSMs to other routers in the domain. When a C-BSR receives the BSM from another C-BSR, it compares its own priority with the priority carried in the message. The C-BSR with a higher priority wins the BSR election. If a tie exists in the priority, the C-BSR with a higher IPv6 address wins.

  • Page 312

    An IPv6 PIM domain border is a bootstrap message boundary. Each BSR has its specific service scope. IPv6 PIM domain border interfaces partition a network into different IPv6 BIDIR-PIM domains. Bootstrap messages cannot cross a domain border in either direction. Perform the following configuration on routers that you want to configure as an IPv6 PIM domain border.

  • Page 313: Configuring Ipv6 Pim-ssm

    Configuring IPv6 PIM-SSM IPv6 PIM-SSM requires MLDv2 support. Enable MLDv2 on IPv6 PIM routers that connect to multicast receivers. IPv6 PIM-SSM configuration task list Task (Required.) Enabling IPv6 PIM-SM (Optional.) Configuring the IPv6 SSM group range (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-SSM, configure an IPv6 unicast IPv6 routing protocol so that all devices in the domain are interoperable at the network layer.

  • Page 314: Configuring The Ipv6 Ssm Group Range

    Configuring the IPv6 SSM group range When an IPv6 PIM-SM enabled interface receives an IPv6 multicast packet, it checks whether the Ipv6 multicast group address of the packet is in the IPv6 SSM group range. If the IPv6 multicast group address is in this range, the IPv6 PIM mode for this packet is IPv6 PIM-SSM.

  • Page 315: Configuring An Ipv6 Multicast Data Filter

    Configuring an IPv6 multicast data filter To control the IPv6 multicast traffic and the information available to downstream receivers, you can configure an IPv6 PIM router as an IPv6 multicast data filter. Then, the router will check passing-by IPv6 packets and determine to forward or discard the packets. A filter can filter not only independent IPv6 multicast data but also IPv6 multicast data encapsulated in register messages.

  • Page 316

    Holdtime—IPv6 PIM neighbor lifetime. If a router receives no hello message from a neighbor when • the neighbor lifetime expires, it regards the neighbor failed or unreachable. LAN_Prune_Delay—Delay of pruning a downstream interface on a shared-media LAN. This option • consists of LAN delay, override interval, and neighbor tracking support (namely, the capability to disable join message suppression).

  • Page 317: Configuring Common Ipv6 Pim Timers

    Step Command Remarks Enable the neighbor tracking By default, the neighbor tracking hello-option neighbor-tracking function. function is disabled. Configuring hello message options on an interface Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number ipv6 pim hello-option dr-priority Set the DR priority.

  • Page 318

    If you configure hello message options in both IPv6 PIM view and interface view, the configuration in interface view always takes precedence. TIP: For a network without special requirements, HP recommends using the defaults. Configuring common IPv6 PIM timers globally Step...

  • Page 319

    Setting the maximum size of each join or prune message The loss of an oversized join or prune message might result in loss of massive information. You can set a small value for the size of each join or prune message to reduce the impact. To set the maximum size of each join or prune message: Step Command...

  • Page 320: Ipv6 Pim Configuration Examples

    Task Command Display BSR information in the IPv6 display ipv6 pim [ vpn-instance vpn-instance-name ] bsr-info PIM-SM domain. Display information about the display ipv6 pim [ vpn-instance vpn-instance-name ] claimed-route routes used by IPv6 PIM. [ ipv6-source-address ] Display C-RP information in the IPv6 display ipv6 pim [ vpn-instance vpn-instance-name ] c-rp [ local ] PIM-SM domain.

  • Page 321

    Figure 98 Network diagram Table 18 Interface and IPv6 address assignment Device Interface IPv6 address Switch A VLAN-interface 100 1001::1/64 Switch A VLAN-interface 103 1002::1/64 Switch B VLAN-interface 200 2001::1/64 Switch B VLAN-interface 101 2002::1/64 Switch C VLAN-interface 200 2001::2/64 Switch C VLAN-interface 102 3001::1/64...

  • Page 322

    # 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 connects to the stub network). [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] quit # Enable IPv6 PIM-DM on VLAN-interface 103. [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] ipv6 pim dm [SwitchA-Vlan-interface103] quit...

  • Page 323

    Neighbor Interface Uptime Expires Dr-Priority FE80::A01:101:1 Vlan103 00:04:00 00:01:29 1 FE80::B01:102:2 Vlan101 00:04:16 00:01:29 3 FE80::C01:103:3 Vlan102 00:03:54 00:01:17 5 # Send an MLD report from Host A to join the IPv6 multicast group FF0E::101. (Details not shown.) # Send IPv6 multicast data from the IPv6 multicast source 4001::100/64 to the IPv6 multicast group FF0E::101.

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

    Protocol: pim-dm, UpTime: 00:02:19, Expires: - IPv6 PIM-SM non-scoped zone configuration example Network requirements As shown in Figure VOD streams are sent to receiver hosts in multicast. The receivers of different subnets form stub • networks, and at least one receiver host exist in each stub network. The entire IPv6 PIM-SM domain contains only one BSR.

  • Page 325

    Device Interface IPv6 address Switch C VLAN-interface 200 2001::2/64 Switch C VLAN-interface 104 192.168.3.1/24 Switch D VLAN-interface 300 4001::1/64 Switch D VLAN-interface 101 1002::2/64 Switch D VLAN-interface 105 4002::1/64 Switch E VLAN-interface 104 3001::2/64 Switch E VLAN-interface 103 2002::2/64 Switch E VLAN-interface 102 1003::2/64 Switch E...

  • Page 326

    [SwitchE-acl6-basic-2005] rule permit source ff0e::101 64 [SwitchE-acl6-basic-2005] quit # Configure VLAN-interface 102 as a C-BSR and a C-RP, and configure VLAN-interface 101 of Switch D as the static RP. [SwitchE] ipv6 pim [SwitchE-pim6] c-bsr 1003::2 [SwitchE-pim6] c-rp 1003::2 group-policy 2005 [SwitchE-pim6] static-rp 1002::2 [SwitchE-pim6] quit # On Switch A, configure VLAN-interface 101 of Switch D as the static RP...

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

    BSR RP information: Scope: non-scoped Group/MaskLen: FF0E::101/64 RP address Priority HoldTime Uptime Expires 1003::2 00:05:19 00:02:11 Static RP information: RP address Mode Preferred 1002::2 ---- pim-sm IPv6 PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 100: VOD streams are sent to receiver hosts in multicast. The entire IPv6 PIM-SM domain is divided into •...

  • Page 328

    Figure 100 Network diagram Table 20 Interface and IPv6 address assignment Device Interface IPv6 address Switch A VLAN-interface 100 1001::1/64 Switch A VLAN-interface 101 1002::1/64 Switch B VLAN-interface 200 2001::1/64 Switch B VLAN-interface 101 1002::2/64 Switch B VLAN-interface 103 2002::1/64 Switch B VLAN-interface 102 2003::1/64...

  • Page 329

    Device Interface IPv6 address Switch E VLAN-interface 108 6001::2/64 Switch F VLAN-interface 109 8001::1/64 Switch F VLAN-interface 107 6002::2/64 Switch F VLAN-interface 102 2003::2/64 Switch G VLAN-interface 500 9001::1/64 Switch G VLAN-interface 109 8001::2/64 Switch H VLAN-interface 110 4001::1/64 Switch H VLAN-interface 106 3004::2/64 Switch I...

  • Page 330

    [SwitchB-Vlan-interface200] ipv6 pim sm [SwitchB-Vlan-interface200] quit [SwitchB] interface vlan-interface 101 [SwitchB-Vlan-interface101] ipv6 pim sm [SwitchB-Vlan-interface101] quit [SwitchB] interface vlan-interface 102 [SwitchB-Vlan-interface102] ipv6 pim sm [SwitchB-Vlan-interface102] quit [SwitchB] interface vlan-interface 103 [SwitchB-Vlan-interface103] ipv6 pim sm [SwitchB-Vlan-interface103] quit # Enable IPv6 multicast routing and IPv6 PIM-SM on Switch C, Switch D, Switch F, Switch G, and Switch H in the same way Switch B is configured.

  • Page 331

    [SwitchD-pim6] c-rp 3003::2 scope 4 [SwitchD-pim6] quit # On Switch F, configure VLAN-interface 109 as a C-BSR and a C-RP for the IPv6 global-scoped zone. <SwitchF> system-view [SwitchF] ipv6 pim [SwitchF-pim6] c-bsr 8001::1 [SwitchF-pim6] c-rp 8001::1 [SwitchF-pim6] quit Verifying the configuration # Display BSR information on Switch B.

  • Page 332

    Candidate BSR address: 3003::2 Priority: 64 Hash mask length: 126 # Display BSR information on Switch F. [SwitchF] display ipv6 pim bsr-info Scope: non-scoped State: Elected Bootstrap timer: 00:00:49 Elected BSR address: 8001::1 Priority: 64 Hash mask length: 126 Uptime: 00:01:11 Candidate BSR address: 8001::1 Priority: 64 Hash mask length: 126...

  • Page 333: Ipv6 Bidir-pim Configuration Example

    RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FF94::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFA4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFB4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local)

  • Page 334

    Figure 101 Network diagram Loop0 Receiver 1 Receiver 2 Switch B Vlan-int200 Vlan-int102 Vlan-int102 Switch C Host A Host B Vlan-int101 Vlan-int103 IPv6 BIDIR-PIM Source 1 Source 2 Vlan-int101 Vlan-int103 Vlan-int100 Vlan-int400 Switch A Switch D Table 21 Interface and IPv6 address assignment Device Interface IPv6 address...

  • Page 335

    Enable IPv6 multicast routing, IPv6 PIM-SM, IPv6 BIDIR-PIM, and MLD: # On Switch A, enable IPv6 multicast routing, enable IPv6 PIM-SM on each interface, and enable IPv6 BIDIR-PIM. <SwitchA> system-view [SwitchA] ipv6 multicast routing [SwitchA-mrib6] quit [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] ipv6 pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101...

  • Page 336

    [SwitchC-LoopBack0] quit [SwitchC] ipv6 pim [SwitchC-pim6] bidir-pim enable # On Switch D, enable IPv6 multicast routing. <SwitchD> system-view [SwitchD] ipv6 multicast routing [SwitchD-mrib6] quit # Enable MLD in VLAN interface 300 (the interface that connects to the receiver host). [SwitchD] interface vlan-interface 300 [SwitchD-Vlan-interface300] mld enable [SwitchD-Vlan-interface300] quit # Enable IPv6 PIM-SM on the other interfaces.

  • Page 337

    FE15:5601 # Display the DF information of IPv6 BIDIR-PIM on Switch C. [SwitchC] display ipv6 pim df-info RP address: 6001::1 Interface State DF-Pref DF-Metric DF-Uptime DF-Address Loop0 Vlan102 01:06:07 FE80::20F:E2FF: FE15:5601 (local) Vlan103 01:06:07 FE80::20F:E2FF: FE15:5602 (local) # Display the DF information of IPv6 BIDIR-PIM on Switch D. [SwitchD] display ipv6 pim df-info RP address: 6001::1 Interface...

  • Page 338: Ipv6 Pim-ssm Configuration Example

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

  • Page 339

    Figure 102 Network diagram Table 22 Interface and IPv6 address assignment Device Interface IPv6 address Switch A VLAN-interface 100 1001::1/64 Switch A VLAN-interface 101 1002::1/64 Switch A VLAN-interface 102 1003::1/64 Switch B VLAN-interface 200 2001::1/64 Switch B VLAN-interface 103 2002::1/64 Switch C VLAN-interface 200 2001::2/64...

  • Page 340

    Configure OSPFv3 on the switches in the IPv6 PIM-SSM domain to meet the following requirements: (Details not shown.) The switches are interoperable at the network layer. The switches can dynamically update their routing information. Enable IPv6 multicast routing, MLD, and IPv6 PIM-SM: # On Switch A, enable IPv6 multicast routing.

  • Page 341: Troubleshooting Ipv6 Pim

    [SwitchA] display ipv6 pim routing-table Total 0 (*, G) entry; 1 (S, G) entry (4001::100, FF3E::101) Protocol: pim-ssm, Flag: UpTime: 00:00:11 Upstream interface: Vlan-interface101 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: mld, UpTime: 00:00:11, Expires: 00:03:25 # Display IPv6 PIM multicast routing table information on Switch B.

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

    The router does not have a route to the IPv6 multicast source. IPv6 PIM-SM is not enabled on the RPF interface toward the IPv6 multicast source. When a multicast router receives an IPv6 multicast packet, it looks up the existing IPv6 unicast •...

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

    Solution 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 data filter. 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 344

    Solution Use display ipv6 routing-table to verify that the IPv6 unicast routes to the C-RPs and the BSR are available on each router and that a route is available between each C-RP and the BSR. Make sure each C-RP has an IPv6 unicast route to the BSR, the BSR has an IPv6 unicast route to each C-RP, and each router on the network has IPv6 unicast routes to the C-RPs.

  • Page 345: Support And Other Resources

    Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...

  • Page 346: Conventions

    Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...

  • Page 347

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

  • Page 348: Index

    Index IP multicast inter-AS MD VPN, IP multicast VPN inter-AS MD-VPN abnormal multicast data termination configuration, IP multicast PIM, IP multicast VPN intra-AS MD-VPN IPv6 PIM, configuration, IP multicast IGMP snooping policy IP multicast model), configuration, assert IPv6 multicast MLD snooping policy, IP multicast PIM-DM, address IP multicast PIM-SM,...

  • Page 349

    administrative scoping, IP multicast PIM-SM C-BSR configuration, bidirectional RPT building, IP multicast PIM-SM RP discovery, BSM semantic fragmentation, IPv6 BIDIR-PIM C-BSR configuration, BSR configuration, IPv6 BIDIR-PIM configuration, C-BSR configuration, IPv6 PIM-SM administrative scoping zone border router, configuration, 104, IPv6 PIM-SM C-BSR configuration, C-RP configuration, IPv6 PIM-SM configuration, DF election,...

  • Page 350

    IP multicast IGMP performance adjustment, IP multicast PIM-DM graft retry timer, IP multicast IGMP snooping, 14, 17, IP multicast PIM-DM state-refresh parameter, IP multicast IGMP snooping basic functions, IP multicast PIM-SM, IP multicast IGMP snooping fast leave IP multicast PIM-SM admin-scoped zone, processing, IP multicast PIM-SM BSR, IP multicast IGMP snooping group policy,...

  • Page 351

    IPv6 multicast MLD snooping group policy, IPv6 PIM-SM domain border, IPv6 multicast MLD snooping IPv6 multicast IPv6 PIM-SM multicast source registration, group filter, IPv6 PIM-SM non-scoped zone, IPv6 multicast MLD snooping IPv6 multicast IPv6 PIM-SM RP, group filter globally, IPv6 PIM-SM static RP, IPv6 multicast MLD snooping IPv6 multicast IPv6 PIM-SM switchover to SPT, group filter on port,...

  • Page 352

    creating IP multicast PIM-SM BSM semantic fragmentation, IP multicast MD-VPN MD for VPN instance, disabling IPv6 BIDIR-PIM BSM semantic fragmentation MSDP peering connection, function, multicast routing RPF route, disabling IPv6 PIM-SM BSM semantic fragmentation C-RP function, IP multicast BIDIR-PIM configuration, discovering IP multicast PIM-SM configuration, IP multicast BIDIR-PIM neighbor discovery,...

  • Page 353

    IP multicast PIM hello message DR_Priority, 1 12 IP multicast MD-VPN routing in VPN instance, IP multicast PIM/BFD enable, 1 16 IP multicast MLD, IP multicast PIM-SM DR election, IP multicast MLD fast leave processing, IP multicast PIM-SM RPT building, IP multicast PIM/BFD, 1 16 IP multicast PIM-SM SPT switchover...

  • Page 354

    IP multicast PIM-SM non-scoped zone IP multicast PIM-DM SPT building, configuration, IPv6 PIM-DM SPT building, IP multicast PIM-SSM configuration, forwarding IP multicast VPN application, IP multicast BIDIR-PIM configuration, IP multicast VPN instance, IP multicast IGMP snooping max number IP multicast VPN support, forwarding entries, IPv6 BIDIR-PIM configuration, IP multicast inter-AS MD VPN,...

  • Page 355

    IPv6 multicast sub-VLAN forwarding, IP multicast PIM-SM admin-scoped/global-scoped zone relationship, IPv6 multicast unicast subnet forwarding, graft IPv6 multicast VLAN max number of forwarding entries, IP multicast PIM-DM, IPv6 PIM configuration, 274, IP multicast PIM-DM graft retry timer, IPv6 PIM feature configuration, IPv6 PIM-DM, IPv6 PIM multicast data filter, IPv6 PIM-DM graft retry timer,...

  • Page 356

    enable, multicast group filter configuration, fast leave processing, multicast group replacement, IP multicast IGMPv1. See IGMPv1 multicast groups max number on port, IP multicast IGMPv2. See IGMPv2 multicast source port filtering, IP multicast IGMPv3. See IGMPv3 policy configuration, IP multicast MLD basic configuration, port function configuration, IP multicast MLD configuration, 263, 266, protocols and standards,...

  • Page 357

    IGMP snooping query/response parameters, multicast. See IP multicast IGMP snooping report suppression, IP addressing IGMP snooping source port filtering, IP multicast address, 6, IGMP snooping static port, IP multicast packet forwarding, IGMP snooping static port configuration, IP multicast IGMP static member interface configuration, address, IGMP version specification, architecture,...

  • Page 358

    MSDP RPF static peer, troubleshooting IGMP inconsistent membership information, MSDP SA message cache, troubleshooting IGMP no membership information MSDP SA message content, on router, MSDP SA message filtering configuration, troubleshooting IGMP snooping, MSDP SA message filtering rule, troubleshooting IGMP snooping Layer 2 multicast MSDP SA message related parameters, forwarding, MSDP SA request message,...

  • Page 359

    multicast MLD multicast group filter, MLD snooping dynamic port aging timers, multicast MLD performance adjustment, MLD snooping fast-leave processing enable, multicast MLDv1 IPv6 group joining, MLD snooping group filter, multicast MLDv1 IPv6 group leaving, MLD snooping group policy configuration, multicast VLAN. See IPv6 multicast VLAN MLD snooping group replacement, PIM.

  • Page 360

    hello message option global configuration, C-BSR configuration, hello message option interface configuration, configuration, C-RP configuration, hello message options, domain border configuration, join/prune message size, DR election, multicast data filter configuration, embedded RP, protocol relationships, enabling, protocols and standards, introduction, timer configuration, IPv6 BIDIR-PIM, timer global configuration, IPv6 PIM protocol relationships,...

  • Page 361

    IP multicast protocols and standards, multicast routing static multicast MAC address entry, IPv6 PIM snooping configuration, 234, 235, maintaining multicast routing MAC address static entry, IP multicast IGMP, Layer 3 IP multicast IGMP snooping, IP multicast BIDIR-PIM configuration, IP multicast MLD, IP multicast PIM configuration, 82, 1 17 IP multicast PIM snooping,...

  • Page 362

    message aging timer for dynamic port, IP multicast IGMP snooping leave, basic concepts, IP multicast PIM hello message filter, 1 12 basic configuration, IP multicast PIM hello message options, 1 12 configuration, 213, 217, IP multicast PIM join/prune message size, 1 15 displaying, IPv6 multicast MLD snooping basic...

  • Page 363

    IPv6 PIM-SSM introduction, troubleshooting locally registered (S, G) entries between RPs, MLD support, troubleshooting no SA entries in message source list, cache, timers, troubleshooting peers stay in disabled state, MLDv2 snooping version specification, VPN support, model multicast IP multicast, BIDIR-PIM, IP multicast ASM, BIDIR-PIM bidirectional RPT building, IP multicast SFM,...

  • Page 364

    IPv6 PIM-SM SPT switchover, troubleshooting IPv6 PIM-SM multicast source registration failure, IPv6 PIM-SM SPT switchover configuration, 297, troubleshooting IPv6 PIM-SM RP cannot join SPT, IPv6 PIM-SSM configuration, 303, troubleshooting PIM abnormal multicast data IPv6 PIM-SSM group range, termination, IPv6 PIM-SSM introduction, troubleshooting PIM multicast distribution tree, IPv6 zone relationships, troubleshooting PIM-SM multicast source...

  • Page 365

    port-based VLAN user port attribute IPv6 PIM-DM, configuration, IPv6 PIM-SM, sub-VLAN-based, IPv6 PIM-SSM, sub-VLAN-based configuration, network multicast VPN BIDIR-PIM RP maximum number configuration, configuration, 168, 180, Ethernet multicast MAC address, data-group reuse logging, IP multicast address, 6, data-MDT to default-MDT switch, IP multicast architecture, default-MDT establishment, IP multicast BIDIR-PIM bidirectional RPT building,...

  • Page 366

    IP multicast PIM-DM SPT building, IPv6 multicast forwarding boundary, IP multicast PIM-DM state-refresh feature, IPv6 multicast forwarding configuration, IP multicast PIM-DM state-refresh parameters, IPv6 multicast load splitting, IP multicast PIM-SM administrative scoping, IPv6 multicast MAC address static entry, IP multicast PIM-SM assert, IPv6 multicast MLD group filter, IP multicast PIM-SM BSM semantic IPv6 multicast MLD snooping IPv6 multicast source...

  • Page 367

    IP multicast IGMP configuration, 74, IPv6 multicast MLD snooping configuration, 213, 217, IP multicast IGMP performance adjustment, IPv6 multicast MLD snooping group policy IP multicast IGMP snooping basic configuration, configuration, IPv6 multicast MLD snooping static port IP multicast IGMP snooping configuration, configuration, 14, 17, IPv6 multicast port-based VLAN configuration,...

  • Page 368

    IPv6 PIM hello message LAN_Prune_Delay troubleshooting MSDP peer stays in disabled option, state, IPv6 PIM hello message options, IPv6 PIM hello message options global BFD enable, 1 16 configuration, BIDIR. See BIDIR-PIM IPv6 PIM hello message options interface common feature configuration, 1 1 1 configuration, common timer configuration,...

  • Page 369

    maintaining, IP multicast VPN default MDT establishment in PIM-DM network, troubleshooting, IPv6. See IPv6 PIM-SM troubleshooting PIM snooping does not work, IPv6 PIM/BFD enable, PIM-DM MSDP Anycast RP, assert, MSDP Anycast RP configuration, configuration, 96, 1 17 MSDP configuration, 140, 145, enable, MSDP enable, graft,...

  • Page 370

    neighbor discovery, IPv6 multicast MLD snooping aging timer for dynamic port, protocols and standards, IPv6 multicast MLD snooping basic SPT building, configuration, policy IPv6 multicast MLD snooping IP multicast IGMP snooping configuration, configuration, 213, 217, IP multicast IGMP snooping group policy IPv6 multicast MLD snooping dynamic port aging configuration, timers,...

  • Page 371

    assigning IP multicast port-based VLAN user configuring IP multicast IGMP snooping policy, port (VLAN view), configuring IP multicast IGMP snooping port assigning IPv6 multicast port-based VLAN user function, port, configuring IP multicast IGMP snooping assigning IPv6 multicast port-based VLAN user query/response parameters, port (interface view), configuring IP multicast IGMP snooping...

  • Page 372

    configuring IP multicast PIM-SSM, configuring IPv6 multicast MLD snooping group filter, configuring IP multicast PIM-SSM group range, 1 10 configuring IPv6 multicast MLD snooping group filter globally, configuring IP multicast port-based multicast VLAN, configuring IPv6 multicast MLD snooping group filter on port, configuring IP multicast port-based VLAN, configuring IPv6 multicast MLD snooping group configuring IP multicast port-based VLAN user...

  • Page 373

    configuring IPv6 PIM timer on interface, configuring multicast routing MAC address static entry, configuring IPv6 PIM-DM, 289, configuring multicast routing RPF route selection configuring IPv6 PIM-DM graft retry timer, rule, configuring IPv6 PIM-DM state refresh configuring multicast static route, parameter, configuring PIM, 1 17 configuring IPv6 PIM-SM,...

  • Page 374

    enabling IP multicast IGMP fast leave enabling PIM-SM, processing, forwarding multicast over GRE tunnel, enabling IP multicast IGMP snooping drop maintaining IP multicast IGMP, unknown multicast data, maintaining IP multicast IGMP snooping, enabling IP multicast IGMP snooping fast-leave maintaining IP multicast MLD, processing globally, maintaining IP multicast PIM snooping, enabling IP multicast IGMP snooping fast-leave...

  • Page 375

    specifying MLD version, IP multicast MLD, troubleshooting IP multicast IGMP snooping IP multicast MLDv2, Layer 2 forwarding, IP multicast PIM, troubleshooting IP multicast IGMP snooping IP multicast PIM protocol relationships, multicast group filter, IP multicast VPN, troubleshooting IP multicast MD-VPN IPv6 multicast MLD snooping, default-MDT establishment, 21 1...

  • Page 376

    IPv6 multicast MLD snooping membership IP multicast IGMP snooping max number report, forwarding entries, IPv6 multicast MLD snooping report IP multicast IGMP snooping multicast group filter, suppression, IP multicast IGMP snooping multicast source port reverse path forwarding. Use filtering, route IP multicast IGMP snooping policy configuration, IPv6 multicast RPF route selection rule, IP multicast IGMP snooping port function...

  • Page 377

    IP multicast PIM-SM C-RP configuration, IP multicast VPN MD-VPN configuration, IP multicast PIM-SM DR election, IP multicast VPN support, IP multicast PIM-SM multicast source IPv6 administrative scoping, registration, 88, IPv6 BIDIR-PIM, IP multicast PIM-SM neighbor discovery, IPv6 BIDIR-PIM bidirectional RPT building, IP multicast PIM-SM non-scoped zone IPv6 BIDIR-PIM BSR configuration, configuration,...

  • Page 378

    IPv6 PIM-DM graft, MSDP SA message related parameters, IPv6 PIM-DM neighbor discovery, MSDP SA request message, IPv6 PIM-DM SPT building, multicast routing. See multicast routing IPv6 PIM-DM state refresh enable, PIM-SM MSDP inter-domain multicast configuration, IPv6 PIM-DM state refresh parameters, port-based IPv6 multicast VLAN configuration, IPv6 PIM-SM, sub-VLAN-based IPv6 multicast VLAN...

  • Page 379

    IPv6 PIM-SM static RP configuration, IPv6 multicast RPF route selection rule, MSDP Anycast RP, semantic fragmentation MSDP RPF static peer, IP multicast BIDIR-PIM BSM, troubleshooting IP multicast PIM-SM RP cannot IP multicast PIM-SM BSM, be built, IPv6 BIDIR-PIM BSM, troubleshooting IPv6 PIM-SM RP cannot join IPv6 PIM-SM BSM, SPT, setting...

  • Page 380

    troubleshooting IP multicast PIM-SM multicast IPv6 BIDIR-PIM RP, source registration failure, IPv6 multicast MAC address entry, troubleshooting IPv6 PIM-SM multicast source IPv6 multicast MLD snooping static port registration failure, configuration, specifying IPv6 PIM-SM RP, IP multicast IGMP snooping version, static route IP multicast IGMP version, multicast routing configuration, IP multicast MD-VPN default group address,...

  • Page 381

    port-based IPv6 multicast VLAN IP multicast VPN support, configuration, techniques, sub-VLAN-based IPv6 multicast VLAN unicast, configuration, troubleshooting transmission techniques, IP multicast IGMP, switchover IP multicast IGMP inconsistent membership IP multicast PIM-SM switchover to SPT, information, IPv6 PIM-SM SPT switchover configuration, IP multicast IGMP no membership information on IPv6 PIM-SM switchover to SPT, router,...

  • Page 382

    MSDP locally registered (S, G) entries between IP multicast IGMP snooping group policy RPs, configuration, MSDP peers stay in disabled state, IP multicast IGMP snooping max number multicast groups on port, multicast forwarding, IP multicast IGMP snooping multicast group multicast routing, replacement, multicast static route failure, IP multicast IGMP snooping policy configuration,...

  • Page 383

    IP multicast IGMP support, IP multicast instance, IP multicast MLD support, IP multicast PIM support, IP multicast support, IP multicast VPN. See multicast VPN IPv6 PIM support, MSDP support, VRF-to-VRF PE interconnectivity, IP multicast PIM-SM administrative scoping, IPv6 PIM-SM, zone border router.

Comments to this Manuals

Symbols: 0
Latest comments: