Page of 211
Download Table of ContentsContents Print This PagePrint Bookmark

HP 6125XLG Configuration Manual

R2306-hp 6125xlg blade switch ip multicast configuration guide.
Hide thumbs
HP 6125XLG Blade Switch
IP Multicast
Part number: 5998-3720
Software version: Release 2306
Document version: 6W100-20130912

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-3720 Software version: Release 2306 Document version: 6W100-20130912...

  • Page 2

    HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

  • 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

    Configuring the RPF route selection rule ············································································································· 38   Configuring multicast load splitting ····················································································································· 38   Configuring a multicast forwarding boundary ··································································································· 38   Configuring static multicast MAC address entries ····························································································· 38   Displaying and maintaining multicast routing and forwarding ················································································· 39  ...

  • Page 5: Table Of Contents

    Configuring multicast source registration············································································································ 77   Configuring switchover to SPT ····························································································································· 77   Configuring common PIM features ······························································································································· 78   Configuration task list ··········································································································································· 78   Configuration prerequisites ·································································································································· 78   Configuring a multicast data filter ······················································································································· 78   Configuring a hello message filter ······················································································································ 78  ...

  • Page 6: Table Of Contents

    Configuration task list ·················································································································································· 120   Enabling IPv6 multicast routing ··································································································································· 120   Configuring IPv6 multicast routing and forwarding ································································································· 121   Configuring the RPF route selection rule ··········································································································· 121   Configuring IPv6 multicast load splitting··········································································································· 121   Configuring an IPv6 multicast forwarding boundary ······················································································ 121  ...

  • Page 7: Table Of Contents

    Configuring a BSR ··············································································································································· 153   Configuring IPv6 multicast source registration ································································································· 155   Configuring switchover to SPT ··························································································································· 156   Configuring common IPv6 PIM features ···················································································································· 156   Configuration task list ········································································································································· 156   Configuration prerequisites ································································································································ 157   Configuring an IPv6 multicast data filter ···········································································································...

  • Page 8: Multicast Overview, Introduction To Multicast, Information Transmission Techniques

    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 new value-added services, such as live webcasting, Web TV, distance learning, telemedicine, Web radio, real-time video conferencing, and other bandwidth-critical and time-critical information services.

  • Page 9

    a separate copy of the same information to each of these hosts. Sending many copies can place a tremendous pressure on the information source and the network bandwidth. 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.

  • Page 10: 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 11: Common Notations In Multicast, Multicast Benefits And Applications

    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 12: Multicast Models, Multicast Architecture

    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, and receivers can join a multicast group identified by a group address and get multicast information addressed to that multicast group.

  • Page 13: 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 14

    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—The most significant eight bits are 1 1 1 1 1 1 1 1, which means that this address is an IPv6 multicast address.

  • Page 15

    Scope—The Scope field contains four bits, which indicate the scope of the IPv6 internetwork for which the multicast traffic is intended. 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.

  • Page 16: 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 17

    Figure 8 Positions of Layer 3 multicast protocols Multicast group management protocols: • Typically, IGMP or MLD protocol is used between hosts and Layer 3 multicast devices that directly connect to the hosts to define how to establish and maintain their multicast group memberships. Multicast routing protocols: •...

  • Page 18: Multicast Packet Forwarding Mechanism

    Figure 9 Positions of Layer 2 multicast protocols IGMP snooping and MLD snooping: • IGMP snooping and MLD snooping are multicast constraining mechanisms that run on Layer 2 devices. They manage and control multicast groups by monitoring and analyzing IGMP or MLD messages exchanged between the hosts and Layer 3 multicast devices, effectively controlling the flooding of multicast data in a Layer 2 network.

  • Page 19

    incoming interface. 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. For more information about the RPF mechanism, see "Configuring multicast routing and forwarding"...

  • Page 20: Configuring Igmp Snooping, Overview, Basic Igmp Snooping Concepts

    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 10, when IGMP snooping is not enabled, the Layer 2 switch floods multicast packets...

  • Page 21

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

  • Page 22: How Igmp Snooping Works

    Message received before Action after the timer Timer Description the timer expires expires When a port dynamically joins a The switch removes the Dynamic multicast group, the switch starts or port from the IGMP member port resets an aging timer for the port. IGMP membership report.

  • Page 23: Protocols And Standards

    switch resolves the multicast group address in the report and looks up the ACL. If a match is found to permit the port that received the report to join the multicast group, the switch creates an IGMP snooping forwarding entry for the multicast group and adds the port to the forwarding entry. Otherwise, the switch drops this report, in which case the multicast data for the multicast group is not sent to this port, and the user cannot retrieve the program.

  • Page 24: Igmp Snooping Configuration Task List, Configuring Basic Igmp Snooping Functions, Enabling Igmp Snooping

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

  • Page 25: Specifying The Igmp Snooping Version, Setting The Maximum Number Of Igmp Snooping Forwarding Entries

    Step Command Remarks 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 for a igmp-snooping enable VLAN.

  • Page 26: Configuring Parameters For Igmp Queries And Responses

    Step Command Remarks Set the maximum number of The default setting is IGMP snooping forwarding entry-limit limit 4294967295. entries. Configuring parameters for IGMP queries and responses When a multicast listening host receives an IGMP query (general query or group-specific query), it starts a delay timer for each multicast group that it has joined.

  • Page 27: Configuring Igmp Snooping Port Functions, Setting Aging Timers For Dynamic Ports

    Configuring IGMP snooping port functions Before you configure IGMP snooping port functions, complete the following tasks: • Enable IGMP snooping for the VLAN. Determine the aging timer for dynamic router ports. • Determine the aging timer for dynamic member ports. •...

  • Page 28: Configuring Static Ports, Enabling Igmp Snooping Fast-leave Processing

    Configuring static ports If all hosts attached to a port are interested in the multicast data addressed to a particular multicast group or the multicast data that a particular multicast source sends to a particular group, you can configure the port as a static member port for the specified multicast group or the specified multicast source and group.

  • Page 29: Configuring Igmp Snooping Policies, Configuring A Multicast Group Filter

    Step Command Remarks Enter IGMP-snooping view. igmp-snooping Enable IGMP snooping By default, fast-leave processing is fast-leave [ vlan vlan-list ] fast-leave processing globally. disabled. To enable IGMP snooping fast-leave processing on a port: Step Command Remarks Enter system view. system-view Enter Ethernet interface view interface interface-type or aggregate interface view.

  • Page 30: Configuring Multicast Source Port Filtering, Enabling Dropping Unknown Multicast Data

    Configuring a multicast group filter on a port Step Command Remarks Enter system view. system-view Enter Ethernet interface view interface interface-type or aggregate interface view. interface-number By default, no multicast group filter Configure a multicast group igmp-snooping group-policy is configured on a port, which filter on a port.

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

    When dropping unknown multicast data is enabled, the switch forwards unknown multicast data to • other router ports instead of flooding it in the VLAN. If no other router ports exist, the switch drops the unknown multicast data. To enable dropping unknown multicast data for a VLAN: Step Command Remarks...

  • Page 32: Displaying And Maintaining Igmp Snooping

    This configuration is effective for the multicast groups that a port dynamically joins. If you configure • the port as a static member port for a multicast group, this configuration is not effective for the multicast group. • You can enable the multicast group replacement function either for the current port in proper interface view or globally for all ports in IGMP-snooping view.

  • Page 33: Igmp Snooping Configuration Examples, Group Policy Configuration Example

    Task Command Display information about MAC address display l2-multicast mac-forwarding-table [ mac-address ] [ vlan multicast forwarding entries. vlan-id ] [ slot slot-number ] Remove the dynamic IGMP snooping reset igmp-snooping group { group-address [ source-address ] | forwarding entries for the specified all } [ vlan vlan-id ] multicast groups.

  • Page 34: Verifying The Configuration

    [RouterA] multicast routing-enable [RouterA] interface ten-gigabitethernet 1/1/5 [RouterA-Ten-GigabitEthernet1/1/5] igmp enable [RouterA-Ten-GigabitEthernet1/1/5] pim dm [RouterA-Ten-GigabitEthernet1/1/5] quit [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, assign Ten-GigabitEthernet 1/1/5 through Ten-GigabitEthernet 1/1/8 to the VLAN, and enable IGMP snooping and the function of dropping unknown multicast data for the VLAN.

  • Page 35: Static Port Configuration Example

    Static port configuration example Network requirements As shown in Figure 13, Router A runs IGMPv2 and serves as the IGMP querier, and 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 Ten-GigabitEthernet 1/1/7 and Ten-GigabitEthernet 1/1/9 on Switch C as static member ports for multicast group 224.1.1.1 to enhance the reliability of multicast traffic transmission.

  • Page 36

    On Router A, enable IP multicast routing globally, enable IGMP on Ten-GigabitEthernet 1/1/5, and enable PIM-DM on each interface. <RouterA> system-view [RouterA] multicast routing-enable [RouterA] interface ten-gigabitethernet 1/1/5 [RouterA-Ten-GigabitEthernet1/1/5] igmp enable [RouterA-Ten-GigabitEthernet1/1/5] pim dm [RouterA-Ten-GigabitEthernet1/1/5] quit [RouterA] interface ten-gigabitethernet 1/1/6 [RouterA-Ten-GigabitEthernet1/1/6] pim dm [RouterA-Ten-GigabitEthernet1/1/6] quit Configure Switch A:...

  • Page 37: Troubleshooting Igmp Snooping, Layer 2 Multicast Forwarding Cannot Function

    [SwitchC-vlan100] igmp-snooping enable [SwitchC-vlan100] quit # 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 38: Multicast Group Filter Does Not Work

    If IGMP snooping is not enabled, use the igmp-snooping command in system view to enable IGMP snooping globally, and then use the igmp-snooping enable command in VLAN view to enable IGMP snooping for the VLAN. 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.

  • Page 39: Configuring Multicast Routing And Forwarding, Overview, Rpf Check Mechanism

    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 40

    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, it 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 41: Static Multicast Routes

    Figure 14 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 14, assume that unicast routes are available in the network, and no static multicast routes have been configured on Switch C.

  • Page 42

    Figure 15 Changing an RPF route As shown in Figure 15, when no static multicast route is configured, Switch C's RPF neighbor on the path back to the source is Switch A, and the multicast data from the source travels through Switch A to Switch C.

  • Page 43: Multicast Forwarding Across Unicast Subnets, Configuration Task List

    and Switch D, specifying Switch B as the RPF neighbor of Switch C and Switch C as the RPF neighbor of Switch D, 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 44: Enabling Ip Multicast Routing, Configuring Multicast Routing And Forwarding, Configuring Static Multicast Routes

    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 Before you configure any Layer 3 multicast functionality, you must enable IP multicast routing.

  • Page 45: Configuring The Rpf Route Selection Rule, Configuring Multicast Load Splitting, Configuring A Multicast Forwarding Boundary

    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 46: Displaying And Maintaining Multicast Routing And Forwarding

    address entries to bind multicast MAC addresses and ports to control the destination ports of the multicast data. When you configure static multicast MAC address entries, follow these guidelines: You can configure static multicast MAC address entries on the specified interface in system view, or •...

  • Page 47: Configuration Examples, Changing An Rpf Route

    Task Command display multicast forwarding-table [ source-address [ mask { mask-length | Display multicast mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface forwarding table interface-type interface-number | outgoing-interface { exclude | include | information.

  • Page 48: Configuration Procedure

    Figure 18 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 Configure the IP address and subnet mask for each interface as shown in Figure 18.

  • Page 49: Creating An Rpf Route

    [SwitchA] interface vlan-interface 102 [SwitchA-Vlan-interface102] pim dm [SwitchA-Vlan-interface102] quit [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit # Enable IP multicast routing and PIM-DM on Switch C in the same way. (Details not shown.) # Use the display multicast rpf-info command to display the RPF route to the source on Switch B. [SwitchB] display multicast rpf-info 50.1.1.100 RPF information about source 50.1.1.100: RPF interface: Vlan-interface102, RPF neighbor: 30.1.1.2...

  • Page 50

    Figure 19 Network diagram Configuration procedure Configure the IP address and subnet mask for each interface as shown in Figure 19. (Details not shown.) Enable OSPF on Switch B and Switch C to make sure the network-layer on the PIM-DM network is interoperable and the routing information among the switches can be dynamically updated.

  • Page 51: Multicast Forwarding Over A Gre Tunnel

    [SwitchB] display multicast rpf-info 50.1.1.100 [SwitchC] display multicast rpf-info 50.1.1.100 No output is displayed. It means that that no RPF routes to Source 2 exist on Switch B or Switch C. Configure a static multicast route: # Configure a static multicast route on Switch B, specifying Switch A as its RPF neighbor on the route to Source 2.

  • Page 52

    Figure 20 Network diagram Configuration procedure Configure the IP address and subnet mask for each interface as shown in Figure 20. (Details not shown.) Enable OSPF on switches to make sure the network-layer among the switches is interoperable and the routing information among the switches can be dynamically updated. (Details not shown.) Configure a GRE tunnel: # Create service loopback group 1 on Switch A and specify its service type as Tunnel.

  • Page 53

    [SwitchC-Ten-GigabitEthernet1/1/7] undo stp enable [SwitchC-Ten-GigabitEthernet1/1/7] undo lldp enable [SwitchC-Ten-GigabitEthernet1/1/7] port service-loopback group 1 [SwitchC-Ten-GigabitEthernet1/1/7] quit # Create interface Tunnel 0 on Switch C and specify the tunnel encapsulation mode as GRE over IPv4. [SwitchC] interface tunnel 0 mode gre # Configure the IP address for interface Tunnel 0 on Switch C and specify its source and destination addresses.

  • Page 54: Troubleshooting Multicast Routing And Forwarding, Static Multicast Route Failure

    [SwitchC] display pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25 Upstream interface: NULL Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface200 Protocol: igmp, UpTime: 00:04:25, Expires: - (10.1.1.100, 225.1.1.1) Protocol: pim-dm, Flag: ACT...

  • Page 55: Multicast Data Fails To Reach Receivers

    Multicast data fails to reach receivers Symptom No multicast packets can cross a multicast boundary set with the multicast boundary command. Analysis If you have configured a multicast forwarding boundary by using the multicast boundary command, any multicast packet will be kept from crossing the boundary. Solution Use the display pim routing-table command to verify that the corresponding (S, G) entries exist on each router.

  • Page 56: Configuring Igmp, Overview, Igmpv1 Overview

    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 57

    Figure 21 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 21, Host B and Host C are interested in the multicast data addressed to the multicast group G1, and Host A is interested in the multicast data addressed to G2.

  • Page 58: Igmpv2 Enhancements, Igmpv3 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 59

    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 60: Igmp Configuration Task List, Protocols And Standards, Configuring Basic Igmp Functions

    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 in this group record contain a list of the additional sources from which the system wants to obtain data for packets sent to the specified multicast address. If the change was to an Include source list, these sources are the addresses that were added to the list.

  • Page 61: Enabling Igmp, Specifying The Igmp Version, Configuring An Interface As A Static Member Interface

    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. Disabled by default. multicast routing-enable interface interface-type Enter interface view.

  • Page 62: Configuring A Multicast Group Filter, Adjusting Igmp Performance, Enabling Igmp Fast-leave Processing

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number An interface is not a static member Configure the interface as a igmp static-group group-address of any multicast group or multicast static member interface. [ source source-address ] source and group by default.

  • Page 63: Displaying And Maintaining Igmp, Igmp Configuration Examples, Network Requirements

    The IGMP fast-leave processing configuration is effective only if the device is running IGMPv2 or IGMPv3. To enable IGMP fast-leave processing: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable IGMP fast-leave igmp fast-leave [ group-policy Disabled by default.

  • Page 64: Configuration Procedure

    Figure 23 Network diagram Receiver PIM network Host A Vlan-int100 10.110.1.1/24 Switch A Host B Querier Vlan-int200 10.110.2.1/24 Receiver Host C Switch B Vlan-int200 10.110.2.2/24 Host D Switch C Configuration procedure Assign the IP address and subnet mask to each interface as shown in Figure 23.

  • Page 65: Verifying The Configuration, Troubleshooting Igmp, No Membership Information On The Receiver-side Router

    [SwitchB] interface vlan-interface 201 [SwitchB-Vlan-interface201] pim dm [SwitchB-Vlan-interface201] quit # On Switch C, enable IP multicast routing globally, enable IGMP on VLAN-interface 200, and enable PIM-DM on each interface. <SwitchC> system-view [SwitchC] multicast routing-enable [SwitchC] interface vlan-interface 200 [SwitchC-Vlan-interface200] igmp enable [SwitchC-Vlan-interface200] pim dm [SwitchC-Vlan-interface200] quit [SwitchC] interface vlan-interface 202...

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

    Analysis The correctness of networking and interface connections and whether the protocol layer of the • interface is up directly affect the generation of group membership information. • Multicast routing must be enabled on the router. IGMP must be enabled on the interface that connects to the host.

  • Page 67: Configuring Pim, Overview, Pim-dm Overview

    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 68

    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 to discover PIM neighbors, maintain PIM neighboring relationship with other routers, and build and maintain SPTs. SPT building The process of building an SPT is the flood-and-prune process: In a PIM-DM domain, when the multicast source S sends multicast data to the multicast group G,...

  • Page 69

    Graft To reduce the join latency when a new receiver on a previously pruned branch joins a multicast group, PIM-DM uses a graft mechanism to turn the pruned branch into a forwarding branch, 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 70: 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 71

    IMPORTANT: IGMP must be enabled on the device that acts as the receiver-side DR. Otherwise, the receiver hosts attached to the DR cannot join any multicast groups. Figure 26 DR election As shown in Figure 26, the DR election process is as follows: The routers on the shared-media LAN send hello messages to one another.

  • Page 72

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

  • Page 73

    As shown in Figure 28, the process of building an RPT is as follows: When a receiver wants to join the multicast group G, it uses an IGMP message to inform the receiver-side DR. After getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP that provides services for the multicast group.

  • Page 74

    multicast data reaches the RP along the SPT, the RP unicasts a register-stop message to the source-side DR to prevent the DR from unnecessarily encapsulating the data. 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.

  • Page 75: Administrative Scoping Overview

    Administrative scoping overview Typically, a PIM-SM domain contains only one BSR, which is responsible for advertising RP-set information within the entire PIM-SM domain. The information about all multicast groups is forwarded within the network that the BSR administers. This is called the "non-scoped BSR mechanism." To implement refined management, you can divide a PIM-SM domain into a global-scoped zone and multiple administratively-scoped zones (admin-scoped zones).

  • Page 76

    Figure 30 Relationship in view of geographical locations As shown in Figure 30, for the multicast groups in a specific group address range, the admin-scoped zones must be geographically separated and isolated. A router cannot belong to multiple admin-scoped zones. An admin-scoped zone contains routers that are different from other admin-scoped zones.

  • Page 77: Configuring Pim-dm, Protocols And Standards, Pim-dm Configuration Task List, Configuration Prerequisites, Enabling Pim-dm

    Protocols and standards RFC 3973, Protocol Independent Multicast-Dense Mode (PIM-DM): Protocol Specification(Revised) • • RFC 4601, Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification (Revised) RFC 5059, Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM) • Configuring PIM-DM PIM-DM configuration task list Task at a glance (Required.) Enabling PIM-DM...

  • Page 78: Enabling The State Refresh Feature, Configuring State Refresh Parameters

    Enabling the state refresh feature Pruned interfaces resume multicast forwarding when the pruned state times out. To prevent this, the router with the multicast source attached periodically sends an (S, G) state refresh message, which is forwarded hop by hop along the initial multicast flooding path of the PIM-DM domain, to refresh the prune timer state of all the routers on the path.

  • Page 79: Configuring Pim-dm Graft Retry Timer, Configuring Pim-sm, Pim-sm Configuration Task List, Configuration Prerequisites

    Configuring PIM-DM graft retry timer In PIM-DM, graft is the only type of message that uses the acknowledgment mechanism. In a PIM-DM domain, if a router does not receive a graft-ack message from the upstream router within the specified time after it sends a graft message, the router keeps sending new graft messages at a configurable interval known as graft retry timer, until it receives a graft-ack message from the upstream router.

  • Page 80: Enabling Pim-sm, Configuring An Rp

    Enabling 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. IMPORTANT: All the interfaces on the same router must operate in the same PIM mode.

  • Page 81: Configuring A Bsr

    Configuring a C-RP IMPORTANT: When you configure a C-RP, reserve a relatively large bandwidth between the C-RP and the 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. The BSR collects the C-RP information according to the received advertisement messages from C-RPs or the auto-RP announcements from other routers.

  • Page 82

    Configuring a C-BSR C-BSRs should be configured on routers on the backbone network. The BSR election process is summarized as follows: • Initially, each C-BSR regards itself as the BSR of the PIM-SM 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 •...

  • Page 83

    Step Command Remarks (Optional.) Configure a legal By default, no restrictions are bsr-policy acl-number BSR address range. defined. Configuring a PIM domain border As the administrative core of a PIM-SM domain, the BSR sends the collected RP-set information in the form of bootstrap messages to all routers in the PIM-SM domain.

  • Page 84: Configuring Multicast Source Registration, Configuring Switchover To Spt

    NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. However, for BSMs originated due to learning of a new PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs. Configuring multicast source registration In a PIM-SM domain, the source-side DR sends register messages to the RP, and these register messages have different multicast source or group addresses.

  • Page 85: Configuring Common Pim Features, Configuration Task List, Configuration Prerequisites, Configuring A Multicast Data Filter

    Configuring common PIM features Configuration task list Task at a glance (Optional.) Configuring a multicast data filter (Optional.) Configuring a hello message filter (Optional.) Configuring PIM hello message options (Optional.) Configuring common PIM timers (Optional.) Setting the maximum size of each join or prune message (Optional.) Enabling PIM to work with BFD Configuration prerequisites...

  • Page 86: Configuring Pim Hello Message Options

    To guard against PIM message attacks, you can configure a legal source address range for hello messages on interfaces of routers to ensure the correct PIM neighboring relationships. To configure a hello message filter: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 87: Configuring Common Pim Timers

    drop hello messages without the generation ID options to promptly know the status of an upstream router. You can configure hello message options in PIM view or interface view. The configurations made in PIM view are effective on all interfaces and the configurations made in interface view are effective on only the current interface.

  • Page 88

    After receiving a hello message, a PIM router waits for a random time period before sending a hello message. This random time period is smaller than the maximum delay for sending hello messages, and it can avoid collisions that might occur when multiple PIM routers send hello messages simultaneously. A PIM router periodically sends join/prune messages to its upstream routers for state update.

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

    Step Command Remarks Set the joined/pruned state By default, the joined/pruned state pim holdtime join-prune time holdtime timer. holdtime timer is 210 seconds. 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.

  • Page 90: Pim Configuration Examples, Pim-dm Configuration Example

    Task Command Display BSR information in the display pim bsr-info PIM-SM domain. Display information about the display pim claimed-route [ source-address ] routes used by PIM. Display C-RP information in the display pim c-rp [ local ] PIM-SM domain. Display PIM information on an display pim interface [ interface-type interface-number ] [ verbose ] interface.

  • Page 91

    Figure 32 Network diagram Receiver Host A Switch A Vlan-int100 Host B Receiver Vlan-int300 Vlan-int101 Vlan-int200 Vlan-int101 Source Host C Switch D Switch B 10.110.5.100/24 Vlan-int200 PIM-DM Switch C Host D Table 6 shows the interface and IP address assignment, and network topology scheme. Table 6 Interface and IP address assignment Device Interface...

  • Page 92

    <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 103 [SwitchA-Vlan-interface103] pim dm [SwitchA-Vlan-interface103] quit # Enable IP multicast routing, IGMP, and PIM-DM on Switch B and Switch C in the same way. (Details not shown.) # On Switch D, enable IP multicast routing, and enable PIM-DM on each interface.

  • Page 93

    Switch A. You can use the display pim routing-table command to display the PIM routing table information on each switch. For example: # Display the PIM routing table information on Switch A. [SwitchA] display pim routing-table Total 1 (*, G) entry; 1 (S, G) entry (*, 225.1.1.1) Protocol: pim-dm, Flag: WC UpTime: 00:04:25...

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

    PIM-SM non-scoped zone configuration example Network requirements As shown in Figure 33, 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 PIM-SM domain contains only one BSR.

  • Page 95

    Device Interface IP address Switch C VLAN-interface 104 192.168.3.1/24 Switch D VLAN-interface 300 10.110.5.1/24 Switch D VLAN-interface 101 192.168.1.2/24 Switch D VLAN-interface 105 192.168.4.2/24 Switch E VLAN-interface 104 192.168.3.2/24 Switch E VLAN-interface 103 192.168.2.2/24 Switch E VLAN-interface 102 192.168.9.2/24 Switch E VLAN-interface 105 192.168.4.1/24 Configuration procedure...

  • Page 96

    [SwitchD-pim] c-rp 192.168.4.2 group-policy 2005 [SwitchD-pim] quit # On Switch E, configure the service scope of RP advertisements, configure VLAN-interface 102 as a C-BSR and a C-RP, and set the hash mask length to 32 and the priority of the C-BSR to 20. <SwitchE>...

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

    Priority: 20 Hash mask length: 32 Uptime: 00:01:18 Candidate BSR address: 192.168.9.2 Priority: 20 Hash mask length: 32 # Display RP information on Switch A. [SwitchA] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 225.1.1.0/24 RP address Priority HoldTime Uptime Expires 192.168.4.2...

  • Page 98

    Figure 34 Network diagram Table 8 shows the interface and IP address assignment, and network topology scheme. Table 8 Interface and IP address assignment Device Interface IP address Device Interface IP address Switch A Vlan-int100 192.168.1.1/24 Switch D Vlan-int105 10.110.5.2/24 Switch A Vlan-int101 10.110.1.1/24...

  • Page 99

    Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 34. (Details not shown.) Enable OSPF on all switches on the PIM-SM network to make sure the network-layer on the PIM-SM network is interoperable and the routing information among the switches can be dynamically updated.

  • Page 100

    # On Switch C, configure VLAN-interface 103 and VLAN-interface 106 as the boundaries of admin-scoped zone 2. <SwitchC> system-view [SwitchC] interface vlan-interface 103 [SwitchC-Vlan-interface103] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface103] quit [SwitchC] interface vlan-interface 106 [SwitchC-Vlan-interface106] multicast boundary 239.0.0.0 8 [SwitchC-Vlan-interface106] quit # On Switch D, configure VLAN-interface 107 as the boundary of admin-scoped zone 2.

  • Page 101

    Hash mask length: 30 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected Bootstrap timer: 00:00:06 Elected BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 Uptime: 00:04:54 Candidate BSR address: 10.110.1.2 Priority: 64 Hash mask length: 30 # Display BSR information on Switch D. [SwitchD] display pim bsr-info Scope: non-scoped State: Accept Preferred...

  • Page 102: Troubleshooting Pim, A Multicast Distribution Tree Cannot Be Correctly Built

    BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4 RP address Priority HoldTime Uptime Expires 10.110.9.1 00:03:39 00:01:51 Scope: 239.0.0.0/8 Group/MaskLen: 239.0.0.0/8 RP address Priority HoldTime Uptime Expires 10.110.1.2 (local) 00:07:44 00:01:51 # Display RP information on Switch D. [SwitchD] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: 224.0.0.0/4...

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

    source, or if PIM-SM is not enabled on the RPF interface toward the multicast source, the router cannot create an (S, G) entries. When a multicast router receives a multicast packet, it looks up the existing unicast routing table for •...

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

    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. Use display current-configuration to verify the multicast data filter. Change the ACL rule defined in the source-policy command so that the source/group address of the multicast data can pass ACL filtering.

  • Page 105

    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 106: Configuring Mld Snooping, Overview, Basic Mld Snooping Concepts

    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 35, when MLD snooping is not enabled, the Layer 2 switch floods IPv6 multicast...

  • Page 107

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

  • Page 108: How Mld Snooping Works

    Message received Action after the timer Timer Description before the timer expires expires When a port dynamically joins a The switch removes the Dynamic multicast group, the switch starts or port from the MLD member port resets an aging timer for the port. MLD report message.

  • Page 109

    report message, the switch resolves the IPv6 multicast group address in the report and looks up the ACL. If a match is found to permit the port that received the report to join the IPv6 multicast group, the switch creates an MLD snooping forwarding entry for the IPv6 multicast group and adds the port to the forwarding entry.

  • Page 110: Mld Snooping Configuration Task List, Configuring Basic Mld Snooping Functions, Enabling Mld Snooping

    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 111: Specifying The Mld Snooping Version, Setting The Maximum Number Of Mld Snooping Forwarding Entries

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

  • Page 112: Configuring Parameters For Mld Queries And Responses, Configuring Mld Snooping Port Functions

    Step Command Remarks Set the maximum number of The default setting is MLD snooping forwarding entry-limit limit 4294967295. entries. Configuring parameters for MLD queries and responses When a multicast listening host receives an MLD query (general query or multicast-address-specific query), it starts a timer for each IPv6 multicast group that it has joined. This timer is initialized to a random value in the range of 0 to the maximum response delay advertised in the MLD query message.

  • Page 113: Setting Aging Timers For Dynamic Ports, Configuring Static Ports

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

  • Page 114: Enabling Mld Snooping Fast-leave Processing

    multicast group, you can configure the port as a static member port for the specified IPv6 multicast group or the specified IPv6 multicast source and group. You can also configure a port as a static router port, through which the switch can forward all IPv6 multicast traffic it receives.

  • Page 115: Configuring Mld Snooping Policies, Configuring An Ipv6 Multicast Group Filter

    To enable MLD snooping fast-leave processing on a port: Step Command Remarks Enter system view. system-view Enter Ethernet interface view interface interface-type or aggregate interface view. interface-number Enable MLD snooping mld-snooping fast-leave [ vlan By default, MLD snooping fast-leave processing on the vlan-list ] fast-leave processing is disabled.

  • Page 116: Configuring Ipv6 Multicast Source Port Filtering, Enabling Dropping Unknown Ipv6 Multicast Data

    Step Command Remarks By default, no IPv6 multicast group Configure an IPv6 multicast mld-snooping group-policy filter is configured for the port. The group filter for the port. acl6-number [ vlan vlan-list ] hosts on this port can join any valid IPv6 multicast group.

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

    Step Command Remarks Enter system view. system-view Enter VLAN view. vlan vlan-id Enable dropping unknown By default, this function is disabled. IPv6 multicast data for the mld-snooping drop-unknown Unknown IPv6 multicast data is VLAN flooded. Setting the maximum number of IPv6 multicast groups on a port You can set the maximum number of IPv6 multicast groups on a port to regulate the port traffic.

  • Page 118: Displaying And Maintaining Mld Snooping

    You can enable the multicast group replacement function either for the current port in proper • interface view or globally for all ports in MLD-snooping view. If the configurations are made in both interface view and MLD-snooping view, the configuration made in interface view takes priority. To enable the IPv6 multicast group replacement function globally: Step Command...

  • Page 119: Mld Snooping Configuration Examples, Ipv6 Group Policy Configuration Example

    Task Command Remove the dynamic MLD snooping reset mld-snooping group { ipv6-group-address forwarding entries for the specified [ ipv6-source-address ] | all } [ vlan vlan-id ] multicast groups. Remove dynamic router ports. reset mld-snooping router-port { all | vlan vlan-id } Clear statistics for the MLD messages reset mld-snooping statistics learned by MLD snooping.

  • Page 120

    [RouterA-Ten-GigabitEthernet1/1/5] mld enable [RouterA-Ten-GigabitEthernet1/1/5] ipv6 pim dm [RouterA-Ten-GigabitEthernet1/1/5] quit [RouterA] interface ten-gigabitethernet 1/1/6 [RouterA-Ten-GigabitEthernet1/1/6] ipv6 pim dm [RouterA-Ten-GigabitEthernet1/1/6] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, assign Ten-GigabitEthernet 1/1/5 through Ten-GigabitEthernet 1/1/8 to the VLAN, and enable MLD snooping and the function of dropping IPv6 unknown multicast data for the VLAN.

  • Page 121

    Static port configuration example Network requirements As shown in Figure 38, Router A runs MLDv1 and serves as the MLD querier, and Switch A, Switch B, and Switch C run MLDv1 snooping. Host A and Host C are permanent receivers of the IPv6 multicast group FF1E::101. Configure Ten-GigabitEthernet 1/1/7 and Ten-GigabitEthernet 1/1/9 on Switch C as static member ports for the IPv6 multicast group FF1E::101 to enhance the reliability of IPv6 multicast traffic transmission.

  • Page 122

    On Router A, enable IPv6 multicast routing, enable MLD on Ten-GigabitEthernet 1/1/5, and enable IPv6 PIM-DM on each interface. <RouterA> system-view [RouterA] ipv6 multicast routing-enable [RouterA] interface ten-gigabitethernet 1/1/5 [RouterA-Ten-GigabitEthernet1/1/5] mld enable [RouterA-Ten-GigabitEthernet1/1/5] ipv6 pim dm [RouterA-Ten-GigabitEthernet1/1/5] quit [RouterA] interface ten-gigabitethernet 1/1/6 [RouterA-Ten-GigabitEthernet1/1/6] ipv6 pim dm [RouterA-Ten-GigabitEthernet1/1/6] quit Configure Switch A:...

  • Page 123: Troubleshooting Mld Snooping, Layer 2 Multicast Forwarding Cannot Function

    [SwitchC-vlan100] mld-snooping enable [SwitchC-vlan100] quit # Configure Ten-GigabitEthernet 1/1/7 and Ten-GigabitEthernet 1/1/9 as static member ports for the IPv6 multicast group FF1E::101. [SwitchC] interface ten-gigabitethernet 1/1/7 [SwitchC-Ten-GigabitEthernet1/1/7] mld-snooping static-group ff1e::101 vlan 100 [SwitchC-Ten-GigabitEthernet1/1/7] quit [SwitchC] interface ten-gigabitethernet 1/1/9 [SwitchC-Ten-GigabitEthernet1/1/9] mld-snooping static-group ff1e::101 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 124: Ipv6 Multicast Group Filter Does Not Work

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

  • Page 125: Configuring Ipv6 Multicast Routing And Forwarding, Overview, Rpf Check Mechanism

    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 126

    multicast routing entry and 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. After the router receives an IPv6 multicast packet, it searches its IPv6 multicast forwarding table: •...

  • Page 127: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets, Configuration Task List, Enabling Ipv6 Multicast Routing

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

  • Page 128: Configuring Ipv6 Multicast Load Splitting, Configuring Ipv6 Multicast Routing And Forwarding

    Step Command Remarks By default, IPv6 multicast routing is Enable IPv6 multicast routing. ipv6 multicast routing-enable 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 129: Configuring Ipv6 Static Multicast Mac Address Entries

    To configure an IPv6 multicast forwarding boundary: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number ipv6 multicast boundary { ipv6-group-address prefix-length Configure an IPv6 multicast By default, no forwarding | scope { scope-id | admin-local | forwarding boundary.

  • Page 130: Displaying And Maintaining Ipv6 Multicast Routing And Forwarding, Ipv6 Multicast Routing And Forwarding Configuration Example

    Displaying and maintaining IPv6 multicast routing and forwarding CAUTION: The reset commands might cause IPv6 multicast data transmission failures. Execute display commands in any view and reset commands in user view. Task Command Display information about IPv6 static display mac-address [ mac-address [ vlan vlan-id ] | [ multicast ] multicast MAC address table.

  • Page 131: Network Requirements, Configuration Procedure

    Network requirements As shown in Figure 41, 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. Perform the configuration so that the receiver host can receive the IPv6 multicast data from the source. Figure 41 Network diagram IPv6 multicast router IPv6 unicast router...

  • Page 132

    [SwitchA-Tunnel0] quit # Create service loopback group 1 on Switch C and specify its service type as Tunnel. <SwitchC> system-view [SwitchC] service-loopback group 1 type tunnel # Disable STP and LLDP on interface Ten-GigabitEthernet 1/1/7 of Switch C, and add the interface to service loopback group 1.

  • Page 133: Troubleshooting, Verifying The Configuration, Ipv6 Multicast Data Fails To Reach Receivers

    Verifying the configuration The source sends the IPv6 multicast data to the multicast group FF1E::101 and the receiver host can receive the IPv6 multicast data after joining the IPv6 multicast group. You can use the display ipv6 pim routing-table command to display IPv6 PIM routing table information. For example: # Display IPv6 PIM routing table information on Switch C.

  • Page 134

    Solution Use the display ipv6 pim routing-table command to verify that the corresponding (S, G) entries exist on each router. If so, routers have received the IPv6 multicast data. Otherwise, routers have not received the IPv6 multicast data. Use the display ipv6 multicast boundary command to display the multicast boundary information on the interfaces.

  • Page 135: Configuring Mld, Overview, How Mldv1 Works

    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 136

    Joining an IPv6 multicast group Figure 42 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 42, assume that Host B and Host C want to receive the IPv6 multicast data addressed to IPv6 multicast group G1, and Host A wants to receive the IPv6 multicast data addressed to G2.

  • Page 137: 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 138: Mld Configuration Task List, Protocols And Standards, Configuring Basic Mld Functions, Enabling Mld

    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)), rather than the IPv6 multicast data that Source 2 sends to G (denoted as (S2, G)). Only IPv6 multicast data from Source 1 is delivered to Host B. Enhancement in MLD state A multicast router that is running MLDv2 maintains the multicast address state for each multicast address on each attached subnet.

  • Page 139: Specifying The Mld Version, Configuring An Interface As A Static Member Interface

    To enable MLD: Step Command Remarks Enter system view. system-view Enable IPv6 multicast ipv6 multicast routing-enable Disable by default. routing. Enter interface view. interface interface-type interface-number Enable MLD. mld enable Disabled by default. Specifying the MLD version Because MLD message types and formats vary with MLD versions, configure the same MLD version for all routers on the same subnet.

  • Page 140: Configuring An Ipv6 Multicast Group Filter, Adjusting Mld Performance, Enabling Mld Fast-leave Processing

    Step Command Remarks interface interface-type Enter interface view. interface-number By default, an interface is not a mld static-group Configure the interface as a static member of any IPv6 multicast ipv6-group-address [ source static member interface. group or IPv6 multicast source and ipv6-source-address ] group.

  • Page 141: Displaying And Maintaining Mld, Mld Configuration Examples, Network Requirements

    With MLD fast-leave processing enabled, after receiving an MLD done message from a host, the MLD querier sends a leave notification to the upstream immediately without first sending MLD multicast-address-specific queries. This reduces leave latency and preserves the network bandwidth. To enable MLD fast-leave processing: Step Command...

  • Page 142

    Figure 44 Network diagram Receiver IPv6 PIM network Host A Vlan-int100 3000::12/64 Switch A Host B Querier Vlan-int200 3001::10/64 Receiver Host C Switch B Vlan-int200 3001::12/64 Host D Switch C Configuration procedure Assign an IP address and prefix length to each interface as shown in Figure 44.

  • Page 143: Troubleshooting Mld, Verifying The Configuration, No Member Information Exists On The Receiver-side Router

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

  • Page 144

    Analysis The correctness of networking and interface connections and whether the protocol layer of the • interface is up directly affect the generation of IPv6 group member information. • IPv6 multicast routing must be enabled on the router. MLD must be enabled on the interface connecting to the host.

  • Page 145: Configuring Ipv6 Pim, Pim Overview, Ipv6 Pim-dm Overview

    Configuring IPv6 PIM PIM overview Protocol Independent Multicast for IPv6 (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 146

    Assert • Neighbor discovery In an IPv6 PIM domain, each interface that runs IPv6 PIM on a router periodically multicasts IPv6 PIM hello messages to all other IPv6 PIM routers on the local subnet to discover IPv6 PIM neighbors, maintain IPv6 PIM neighboring relationship with other routers, and build and maintain SPTs.

  • Page 147

    Graft To reduce the join latency when a new receiver on a previously pruned branch joins an IPv6 multicast group, IPv6 PIM-DM uses a graft mechanism to turn the pruned branch into a forwarding branch, 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 148: 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 and 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 149

    IMPORTANT: MLD must be enabled on the device that acts as the receiver-side DR. Otherwise, the receiver hosts attached to the DR cannot join any IPv6 multicast groups. For more information about MLD, see "Configuring MLD." Figure 47 DR election As shown in Figure 47, the DR election process is as follows:...

  • Page 150

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

  • Page 151

    RPT building Figure 49 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 49, 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 152

    Figure 50 IPv6 multicast source registration As shown in Figure 50, 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 in an register message and unicasts the message to the RP.

  • Page 153: Ipv6 Administrative Scoping 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 hop by hop toward the IPv6 multicast source.

  • Page 154

    admin-scoped zones are designated can have intersections, but the IPv6 multicast groups in an IPv6 admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded as private group addresses. The IPv6 global-scoped zone can be regarded as a special IPv6 admin-scoped zone, and it maintains a BSR to provide services for the IPv6 multicast groups with the scope field value as 14.

  • Page 155: Configuring Ipv6 Pim-dm, Protocols And Standards, Ipv6 Pim-dm Configuration Task List

    Figure 52 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 156: Configuration Prerequisites, Enabling Ipv6 Pim-dm, Enabling The State Refresh Feature

    Task at a glance (Optional.) Configuring state refresh parameters (Optional.) Configuring IPv6 PIM-DM graft retry timer (Optional.) Configuring common IPv6 PIM features Configuration prerequisites Before you configure IPv6 PIM-DM, configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer.

  • Page 157: Configuring State Refresh Parameters, Configuring Ipv6 Pim-dm Graft Retry Timer

    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 feature ipv6 pim state-refresh-capable feature. is enabled. Configuring state refresh parameters The router directly connected with the IPv6 multicast source periodically sends state refresh messages. You can configure the interval for sending such messages on that router.

  • Page 158: Configuring Ipv6 Pim-sm, Ipv6 Pim-sm Configuration Task List, Configuration Prerequisites, Enabling Ipv6 Pim-sm

    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. ipv6 pim timer graft-retry interval seconds. Configuring IPv6 PIM-SM IPv6 PIM-SM configuration task list Task at a glance (Required.) Enabling IPv6 PIM-SM...

  • Page 159: Configuring An Rp

    To enable IPv6 PIM-SM: Step Command Remarks Enter system view. system-view By default, IPv6 multicast routing is Enable IPv6 multicast routing. ipv6 multicast routing-enable disabled. interface interface-type Enter interface view. interface-number By default, IPv6 PIM-SM is Enable IPv6 PIM-SM. ipv6 pim sm disabled.

  • Page 160

    does not receive any advertisement message when the timer expires, it regards the C-RP failed or unreachable. To guard against C-RP spoofing, you must configure a legal C-RP address range and the multicast group range to which the C-RP is designated on the BSR. In addition, because every C-BSR might become the BSR, you must configure the same filtering policy on all C-BSRs in the IPv6 PIM-SM domain.

  • Page 161

    Configuring a legal BSR address range enables filtering of BSMs based on the address range, thereby preventing a maliciously configured host from masquerading as a BSR. The same configuration must be made on all routers in the IPv6 PIM-SM domain. The following describes the typical BSR spoofing cases and the corresponding preventive measures: •...

  • Page 162: Configuring Ipv6 Multicast Source Registration

    Step Command Remarks 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 and might fragment the datagram if the message exceeds the MTU.

  • Page 163: Configuring Switchover To Spt, Configuring Common Ipv6 Pim Features, Configuration Task List

    To configure IPv6 multicast source registration: Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. ipv6 pim Configure a filtering rule for By default, no register filtering rule register-policy acl6-number register messages. exists. Configure the device to By default, the device calculates calculate the checksum based register-whole-checksum the checksum based on the header...

  • Page 164: Configuring An Ipv6 Multicast Data Filter, Configuration Prerequisites, Configuring A Hello Message Filter

    Configuration prerequisites Before you configure common IPv6 PIM features, complete the following tasks: • Configure an IPv6 unicast routing protocol so that all devices in the domain are interoperable at the network layer. Configure IPv6 PIM-DM or IPv6 PIM-SM. • Configuring an IPv6 multicast data filter In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, routers can check passing-by IPv6 multicast data and determine whether to continue forwarding the IPv6 multicast data based on the configured...

  • Page 165: Configuring Ipv6 Pim Hello Message Options

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

  • Page 166: Configuring Common Ipv6 Pim Timers

    Step Command Remarks By default, the prune message Set the prune message delay. hello-option lan-delay delay delay is 500 milliseconds. hello-option override-interval By default, the override interval is Set the override interval. interval 2500 milliseconds. Enable the neighbor tracking By default, the neighbor tracking hello-option neighbor-tracking function.

  • Page 167

    on only the current interface. 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 Command Remarks...

  • Page 168: Enabling Ipv6 Pim To Work With Bfd, Displaying And Maintaining Ipv6 Pim

    Step Command Remarks Enter IPv6 PIM view. ipv6 pim By default, the maximum size of a Set the maximum size of each jp-pkt-size size join or prune message is 8100 join or prune message. bytes. Enabling IPv6 PIM to work with BFD IPv6 PIM uses hello messages to elect a DR for a shared-media network.

  • Page 169: Ipv6 Pim Configuration Examples, Ipv6 Pim-dm Configuration Example

    Task Command display ipv6 pim routing-table [ ipv6-group-address [ prefix-length ] | ipv6-source-address [ prefix-length ] | flags flag-value | fsm | Display IPv6 PIM routing table incoming-interface interface-type interface-number | mode mode-type | information. outgoing-interface { exclude | include | match } interface-type interface-number ] * Display RP information in the IPv6 display ipv6 pim rp-info [ ipv6-group-address ]...

  • Page 170

    Table 10 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 Switch D VLAN-interface 300...

  • Page 171

    [SwitchD-Vlan-interface101] ipv6 pim dm [SwitchD-Vlan-interface101] quit [SwitchD] interface vlan-interface 102 [SwitchD-Vlan-interface102] ipv6 pim dm [SwitchD-Vlan-interface102] quit Verifying the configuration # Display IPv6 PIM information on Switch D. [SwitchD] display ipv6 pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan300 FE80::A01:201:1 (local) Vlan103 FE80::A01:201:2 (local)

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

    Protocol: pim-dm, Flag: ACT UpTime: 00:01:20 Upstream interface: Vlan-interface103 Upstream neighbor: 1002::2 RPF prime neighbor: 1002::2 Downstream interface(s) information: Total number of downstreams: 1 1: Vlan-interface100 Protocol: pim-dm, UpTime: 00:01:20, Expires: - # Display IPv6 PIM multicast routing table information on Switch D. [SwitchD] display ipv6 pim routing-table Total 0 (*, G) entry;...

  • Page 173

    Figure 54 Network diagram Table 1 1 shows the interface and IPv6 address assignment, and network topology scheme. Table 11 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...

  • Page 174

    Configuration procedure Assign an IPv6 address and prefix length to each interface according to Figure 54. (Details not shown.) Enable OSPFv3 on all switches on the IPv6 PIM-SM network to make sure the network-layer on the IPv6 PIM-SM network is interoperable and the routing information among the switches can be dynamically updated.

  • Page 175

    Verifying the configuration # Display IPv6 PIM information on Switch A. [SwitchA] display ipv6 pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan100 FE80::A01:201:1 (local) Vlan101 FE80::A01:201:2 Vlan102 FE80::A01:201:3 # Display BSR information on Switch A. [SwitchA] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:46...

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

    RP address Priority HoldTime Uptime Expires 1003::2 00:05:19 00:02:11 4002::1 00:05:19 00:02:11 IPv6 PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 55, VOD streams are sent to receiver hosts in multicast. The entire IPv6 PIM-SM domain is divided into IPv6 admin-scoped zone 1, IPv6 admin-scoped zone 2, and the IPv6 global-scoped zone.

  • Page 177

    Table 12 Interface and IPv6 address assignment Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int105 3003::2/64 Switch A Vlan-int101 1002::1/64 Switch D Vlan-int108 6001::1/64 Switch B Vlan-int200 2001::1/64 Switch D Vlan-int107 6002::1/64 Switch B Vlan-int101 1002::2/64 Switch E...

  • Page 178

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

  • Page 179

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

    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 181: Troubleshooting Ipv6 Pim, A Multicast Distribution Tree Cannot Be Correctly Built

    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 182: Ipv6 Multicast Data Is Abnormally Terminated On An Intermediate Router

    the IPv6 multicast source. If the router does not have a route to the IPv6 multicast source, or if IPv6 PIM-DM is not enabled on the RPF interface toward the IPv6 multicast source, the router cannot create an (S, G) entry. •...

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

    If an ACL is defined by the source-policy command, and the IPv6 multicast packets cannot match • the ACL rules, IPv6 PIM cannot create the routing entries for the packets. 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.

  • Page 184

    RPs are the core of an IPv6 PIM-SM domain. Make sure the RP information on all routers is exactly • the same to map a specific IPv6 multicast group to the same RP, and that an IPv6 unicast route to the RP are available on the routers.

  • Page 185: Support And Other Resources, Contacting Hp, Subscription Service, Related Information, Documents, Websites

    Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers • Technical support registration number (if applicable) • • Product serial numbers Error messages •...

  • Page 186: 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 187

    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 188: Index

    Index IPv6 PIM-SM C-BSR configuration, abnormal multicast data termination, IPv6 PIM-SM configuration, ACL, PIM-SM administrative scoping zone border IGMP snooping policy configuration, router, troubleshooting IGMP snooping multicast group PIM-SM BSR configuration, filter, PIM-SM C-BSR configuration, address Ethernet multicast MAC address, IPv4 multicast, C-BSR (IPv6 PIM-SM), IPv6 multicast,...

  • Page 189

    IPv6 multicast MLD snooping IPv6 multicast group filter, forwarding, 18, 120, 120, 121, MLD snooping IPv6 multicast group filter IPv6 multicast forwarding boundary, globally, IPv6 multicast forwarding over GRE tunnel, MLD snooping IPv6 multicast group filter on port, IPv6 multicast load splitting, MLD snooping IPv6 multicast source port IPv6 multicast routing, 18, 120, 121,...

  • Page 190

    PIM-SM static RP, creating embedded RP (IPv6 PIM-SM), multicast RPF route, enabling multicast RPF routes, IGMP, C-RP (IPv6 PIM-SM), IGMP fast leave processing, C-RP (PIM-SM configuration), IGMP snooping, IGMP snooping drop unknown multicast data function, data filter (IPv6 PIM-SM multicast), IGMP snooping multicast group replacement, device max number forwarding entries, IP multicast routing,...

  • Page 191

    PIM-SM non-scoped zone configuration, MLDv2 filter mode, PIM hello message filter configuration, PIM multicast data filter configuration, fast leave processing, filtering IPv6 multicast source port, fast leave processing (IGMP snooping), forwarding fast-leave processing (MLD snooping), IPv6 administrative scoping, feature (multicast), IPv6 multicast.

  • Page 192

    IPv6 PIM-SM multicast source registration IGMP snooping multicast group filter global configuration, configuration, IPv6 PIM-SM neighbor discovery, IGMP snooping multicast group filter port configuration, IPv6 PIM-SM non-scoped zone configuration, IGMP snooping multicast group replacement, IPv6 PIM-SM RP configuration, IGMP snooping static port configuration, IPv6 PIM-SM RP discovery, IPv6 multicast MLDv2 group filtering, IPv6 PIM-SM RPT building,...

  • Page 193

    drop unknown multicast data enable, query capability, enabling, report capability, fast leave processing configuration, IGMPv3 snooping version specification, general query, implementing IPv6 multicast RPF check, 1 18 group policy configuration, implementing multicast RPF check, how it works, inconsistent membership information received (IGMP troubleshooting), IGMP query/response parameter configuration,...

  • Page 194

    MLD snooping multicast group filter static multicast MAC address entry configuration, configuration, MLD snooping multicast group filter global troubleshooting, configuration, troubleshooting data fails to reach receiver, MLD snooping multicast group filter port VLAN. See IPv6 multicast VLAN configuration, IPv6 PIM MLD snooping multicast unknown data drop configuration, 138, enable,...

  • Page 195

    enabling PIM to work with BFD, PIM-SM admin-scoped zone configuration, feature configuration, PIM-SM non-scoped zone configuration, hello message filter configuration, Layer 3 IP multicast routing enable, hello message options configuration, Layer 3 multicast protocols, hello message options global leave group mechanism (IGMPv2), configuration, leave message (IGMP snooping), hello message options interface...

  • Page 196

    MLD snooping basic configuration, done message, MLD snooping configuration, 99, 103, 1 12 dynamic port aging timers, MLD snooping fast-leave processing dynamic port aging timers global setting, enable, dynamic port aging timers VLAN setting, MLD snooping IPv6 group policy enabling, configuration, 1 12 fast-leave processing enable,...

  • Page 197

    IPv6 multicast group filtering, IGMP snooping group filter port configuration, MLD support, IGMP snooping max number groups joined on a port, source list, IGMP snooping multicast group replacement, timers, IGMP snooping policy configuration, MLDv2 version specification, IGMP static member interface configuration, model IGMP version specification, ASM (multicast),...

  • Page 198

    IPv6 PIM-SM hello message options MLD snooping IPv6 group filter global configuration, 158, configuration, IPv6 PIM-SM join/prune message size MLD snooping IPv6 group filter port configuration, configuration, IPv6 PIM-SM multicast data filter MLD snooping IPv6 multicast group replacement configuration, 157, function, 1 10 IPv6 PIM-SM multicast source registration,...

  • Page 199

    PIM-SM C-BSR configuration, troubleshooting IPv6 PIM-SM multicast source registration failure, PIM-SM configuration, troubleshooting MLD snooping IPv6 multicast group PIM-SM C-RP configuration, filter does not work, 1 17 PIM-SM DR election, troubleshooting MLD snooping Layer 2 multicast PIM-SM enable, forwarding cannot function, 1 16 PIM-SM multicast source registration troubleshooting PIM abnormal multicast data...

  • Page 200

    IPv6 multicast forwarding boundary MLD snooping related port, configuration, MLD snooping version specification, IPv6 multicast load splitting configuration, MLD static member interface configuration, IPv6 multicast routing enable, MLD version specification, IPv6 multicast RPF route selection rule multicast address, configuration, multicast architecture, IPv6 PIM-DM enable, multicast forwarding across unicast subnets, IPv6 PIM-DM graft retry timer configuration,...

  • Page 201

    network management transmission techniques, basic MLD configuration, no membership information received (IGMP troubleshooting), how MLD snooping works, notation (multicast), IGMP basic configuration, IGMP basic snooping configuration, IGMP configuration, 49, 53, option IGMP fast leave processing enable, PIM hello message options configuration, IGMP multicast group filter configuration, PIM hello message options global configuration, IGMP performance adjustment,...

  • Page 202

    maintaining, RPT building, PIM-DM. See PIM-DM SPT switchover, PIM-SM. See PIM-SM SPT switchover configuration, protocols and standards, static RP configuration, troubleshooting, troubleshooting multicast source registration failure, troubleshooting abnormal multicast data termination, troubleshooting RP cannot be built, troubleshooting multicast distribution tree, troubleshooting RP cannot join SPT, PIM-DM policy...

  • Page 203

    MLD snooping dynamic port aging timers VLAN configuring IGMP snooping multicast group filter setting, globally, MLD snooping enable, configuring IGMP snooping multicast group filter port, MLD snooping fast-leave processing enable, configuring IGMP snooping multicast source port filtering, MLD snooping IPv6 group policy configuration, 1 12 configuring IGMP snooping multicast source port...

  • Page 204

    configuring IPv6 PIM-SM multicast source configuring multicast RPF route selection rule, registration, configuring multicast static multicast MAC address configuring IPv6 PIM-SM non-scoped zone, entries, configuring IPv6 PIM-SM RP, configuring multicast static route, configuring IPv6 PIM-SM static RP, configuring PIM, configuring IPv6 PIM-SM switchover to SPT, configuring PIM common features, configuring IPv6 PIM-SM timer, configuring PIM common timers,...

  • Page 205

    enabling IGMP fast leave processing, setting IGMP snooping dynamic port aging timer globally, enabling IGMP snooping, setting IGMP snooping dynamic port aging timer in enabling IGMP snooping drop unknown VLAN, multicast data function, setting IGMP snooping max number forwarding enabling IGMP snooping multicast group entries, replacement, setting max number IPv6 multicast groups on a...

  • Page 206

    IGMP snooping port function configuration, IGMP snooping related ports, reporting (IGMPv3 enhanced capability), IGMP snooping static port configuration, 21, reporting IGMP snooping membership, IGMP snooping version specification, reverse path forwarding. Use IGMP static member interface configuration, route selection rule, IGMP version specification, router port (IGMP snooping), IGMPv2, router port (MLD snooping),...

  • Page 207

    IPv6 PIM-SM multicast data filter multicast address, configuration, multicast configuration, 32, 36, 37, IPv6 PIM-SM multicast source registration, multicast forwarding across unicast subnets, IPv6 PIM-SM multicast source registration multicast forwarding boundary configuration, configuration, multicast forwarding configuration, 32, 36, 37, IPv6 PIM-SM neighbor discovery, multicast forwarding over GRE tunnel, IPv6 PIM-SM non-scoped zone multicast load splitting configuration,...

  • Page 208

    PIM-SM enable, troubleshooting IPv6 PIM-SM RP cannot join SPT, PIM-SM multicast source registration, troubleshooting IPv6 PIM-SM RPT cannot be PIM-SM multicast source registration built, configuration, troubleshooting PIM-SM RP cannot be built, PIM-SM neighbor discovery, troubleshooting PIM-SM RP cannot join SPT, PIM-SM non-scoped zone configuration, PIM-SM relationship between admin-scoped and global-scoped zones,...

  • Page 209

    MLD snooping dynamic port aging timers in static PIM-SM static RP configuration, VLAN, static port (IGMP snooping), 21, MLD snooping max number forwarding static route entries, multicast, setting PIM join/prune message max size, multicast routing table, SFM model (multicast), RPF route change, snooping RPF route creation, IGMP.

  • Page 210

    IPv6 PIM-SM configuration, IPv6 PIM-SM multicast source registration failure, IPv6 PIM-SM global configuration, IPv6 PIM-SM RP cannot join SPT, IPv6 PIM-SM interface configuration, IPv6 PIM-SM RPT cannot be built, MLD snooping aging timer for dynamic port, MLD, MLD snooping dynamic port aging timers, MLD inconsistent member information, MLD snooping dynamic port aging timers MLD no member information,...

  • Page 211

    version MLD snooping static port configuration, IGMP snooping specification, PIM configuration, 60, IGMP specification, PIM-DM configuration, IGMPv1, PIM-SM admin-scoped zone configuration, IGMPv1 snooping, PIM-SM non-scoped zone configuration, IGMPv2, IGMPv2 leave group mechanism, zone IGMPv2 querier election mechanism, border router, IGMPv2 snooping, IPv6 PIM-SM admin-scoped zone IGMPv3, configuration,...

Comments to this Manuals

Symbols: 0
Latest comments: