Page of 204
Download Table of ContentsContents Print This PagePrint Bookmark

Advertisement

HP 5920 & 5900 Switch Series
IP Multicast
Part number: 5998-3373
Software version: Release2207
Document version: 6W100-20121130

Advertisement

   Summary of Contents for HP 5920 series

  • Page 1: Configuration Guide

    HP 5920 & 5900 Switch Series IP Multicast Configuration Guide Part number: 5998-3373 Software version: Release2207 Document version: 6W100-20121130...

  • Page 2

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

  • Page 3: Table Of Contents

    Contents Multicast overview ······················································································································································· 1   Introduction to multicast ···················································································································································· 1   Information transmission techniques ······················································································································· 1   Multicast features ······················································································································································ 3   Common notations in multicast ······························································································································· 4   Multicast benefits and applications ························································································································ 4   Multicast models ································································································································································ 5  ...

  • Page 4: Table Of Contents

    Configuring the RPF route selection rule ············································································································· 37   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············································································································ 76   Configuring switchover to SPT ····························································································································· 77   Configuring common PIM features ······························································································································· 77   Configuration task list ··········································································································································· 77   Configuration prerequisites ·································································································································· 78   Configuring a multicast data filter ······················································································································· 78   Configuring a hello message filter ······················································································································ 78  ...

  • Page 6: Table Of Contents

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

  • Page 7: Table Of Contents

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

  • Page 8: Multicast Overview

    Multicast overview Introduction to multicast As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load. By using multicast technology, a network operator can easily provide 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

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

  • Page 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

    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 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 assigned 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.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 indicates that this address is an IPv6 multicast address.

  • Page 15

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

  • Page 16: Multicast Protocols

    Figure 7 An example of 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, the Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (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.

  • 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

    Configuring IGMP snooping Overview IGMP snooping enables Layer 2 switches to establish a Layer 2 multicast forwarding table instead of flooding all multicast packets. To populate the Layer 2 multicast forwarding table, IGMP snooping listens to IGMP messages exchanged between a Layer 3 multicast device and hosts. As shown in Figure 10, without IGMP snooping enabled, the Layer 2 switch floods multicast packets to...

  • 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/0/1 of Switch A and Switch B are the router ports.

  • Page 22: How Igmp Snooping Works

    NOTE: In IGMP snooping, only dynamic ports age out. Static ports never age out. How IGMP snooping works An IGMP snooping-enabled switch performs different actions when it receives different IGMP messages. The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports."...

  • Page 23: Protocols And Standards

    When receiving a leave message An IGMPv1 host silently leaves a multicast group, and the switch is not notified of the leave. However, because the host stops sending IGMP reports as soon as it leaves the multicast group, the switch removes the port that connects to the host from the forwarding entry for the multicast group when the aging timer for the port expires.

  • Page 24: Configuring Basic Igmp Snooping Functions

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

  • Page 25: Specifying The Igmp Snooping Version

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

  • Page 26: Configuring Igmp Snooping Port Functions

    To speed up the response of hosts to IGMP queries and avoid simultaneous timer expirations causing IGMP report traffic bursts, you must properly set the maximum response time. The maximum response time for IGMP general queries is set by the max-response-time command. •...

  • Page 27: Configuring Static Ports

    If the memberships of multicast groups frequently change, you can set a relatively small value for the • aging timer of the dynamic member ports. If the memberships of multicast groups rarely change, you can set a relatively large value. •...

  • Page 28: Enabling Igmp Snooping Fast-leave Processing

    To configure static ports: Step Command Remarks Enter system view. system-view Enter Ethernet interface view interface interface-type or aggregate interface view. interface-number igmp-snooping static-group Configure the port as a static By default, a port is not a static group-address [ source-ip member port.

  • Page 29: Configuring Igmp Snooping Policies

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

  • Page 30: Enabling Dropping Unknown Multicast Data

    Configuring multicast source port filtering globally Step Command Remarks Enter system view. system-view Enter IGMP-snooping view. igmp-snooping Enable multicast source port By default, multicast source port source-deny port interface-list filtering. filtering is disabled. Configuring multicast source port filtering on a port Step Command Remarks...

  • Page 31: Enabling The Multicast Group Replacement Function

    If the number of multicast groups on a port exceeds the limit, the system removes all the forwarding • entries related to that port from the IGMP snooping forwarding table. The receiver hosts attached to that port can join multicast groups again before the number of multicast groups on the port reaches the limit.

  • Page 32: Displaying And Maintaining Igmp Snooping

    Step Command Remarks Enter Ethernet interface view interface interface-type or aggregate interface view. interface-number Enable multicast group igmp-snooping overflow-replace By default, the multicast group replacement function on a [ vlan vlan-list ] replacement function is disabled. port. Displaying and maintaining IGMP snooping Execute display commands in any view and reset commands in user view.

  • Page 33

    To enable Host A and Host B to receive only the multicast data addressed to the multicast group 224.1.1.1, configure IGMP snooping on Switch A and enable the switch to drop unknown multicast data instead of flooding it in VLAN 100. Figure 12 Network diagram Receiver Host A...

  • Page 34: Static Port Configuration Example

    [SwitchA-vlan100] quit # Configure a multicast group filter so that the hosts in VLAN 100 can join only the multicast group 224.1.1.1. [SwitchA] acl number 2001 [SwitchA-acl-basic-2001] rule permit source 224.1.1.1 0 [SwitchA-acl-basic-2001] quit [SwitchA] igmp-snooping [SwitchA-igmp-snooping] group-policy 2001 vlan 100 [SwitchA-igmp-snooping] quit Verifying the configuration Assume that Host A and Host B want to join the multicast groups 224.1.1.1 and 224.2.2.2 to receive the...

  • Page 35

    For more information about the STP, see Layer 2—LAN Switching Configuration Guide. Figure 13 Network diagram Configuration procedure Assign an IP address and subnet mask to each interface as shown in Figure 13. (Details not shown.) On Router A, enable IP multicast routing globally, enable IGMP on Ten-GigabitEthernet 1/0/1, and enable PIM-DM on each interface.

  • Page 36

    # Configure Ten-GigabitEthernet 1/0/3 as a static router port. [SwitchA] interface ten-gigabitethernet 1/0/3 [SwitchA-Ten-GigabitEthernet1/0/3] igmp-snooping static-router-port vlan 100 [SwitchA-Ten-GigabitEthernet1/0/3] quit Configure Switch B: # Enable IGMP snooping globally. <SwitchB> system-view [SwitchB] igmp-snooping [SwitchB-igmp-snooping] quit # Create VLAN 100, assign Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2 to the VLAN, and enable IGMP snooping for the VLAN.

  • Page 37: Troubleshooting Igmp Snooping

    Total 1 entries. VLAN 100: Total 1 entries. (0.0.0.0, 224.1.1.1) Host slots (0 in total): Host ports (2 in total): XGE1/0/3 XGE1/0/5 The output shows that Ten-GigabitEthernet 1/0/3 and Ten-GigabitEthernet 1/0/5 on Switch C have become static member ports of the multicast group 224.1.1.1. Troubleshooting IGMP snooping Layer 2 multicast forwarding cannot function Symptom...

  • Page 38

    Use the display igmp-snooping command to verify that the function of dropping unknown multicast data is enabled. If not, use the igmp-snooping drop-unknown command to enable the function of dropping unknown multicast data.

  • Page 39: Configuring Multicast Routing And Forwarding

    Configuring multicast routing and forwarding Overview The following tables are involved in multicast routing and forwarding: Multicast routing table of each multicast routing protocol, such as the PIM routing table. • General multicast routing table that summarizes multicast routing information of different multicast •...

  • Page 40

    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. For more information about the route preference, see Layer 3—IP Routing Configuration Guide.

  • 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

    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

    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 Multicast Load Splitting

    To configure a multicast routing policy: Step Command Remarks Enter system view. system-view Configure the device to select By default, the route with the the RPF route based on the multicast longest-match highest priority is selected as the longest prefix match. RPF route.

  • Page 46: Displaying And Maintaining Multicast Routing And Forwarding

    The multicast MAC address that can be manually configured in the multicast MAC address entry • must be unused. (The least significant bit of the most significant octet is 1.) To configure a static multicast MAC address entry in system view: Step Command Remarks...

  • Page 47: Configuration Examples

    Task Command Display information about the static multicast routing display multicast routing-table static [ source-address { mask-length | mask } ] table. Display RPF route information about the display multicast rpf-info source-address [ group-address ] multicast source. Clear forwarding entries reset multicast forwarding-table { { source-address [ mask { mask-length | from the multicast mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface...

  • Page 48

    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 indicates that that no RPF routes to the 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 the 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/0/3] undo stp enable [SwitchC-Ten-GigabitEthernet1/0/3] undo lldp enable [SwitchC-Ten-GigabitEthernet1/0/3] port service-loopback group 1 [SwitchC-Ten-GigabitEthernet1/0/3] 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

    [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: never (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

    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) •...

  • Page 57: Igmpv2 Enhancements

    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. The following process describes how the hosts join the multicast groups and how the IGMP querier (Router B in Figure maintains the multicast group memberships: The hosts send unsolicited IGMP reports to the multicast groups they want to join without having to...

  • Page 58: Igmpv3 Enhancements

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

  • Page 59

    Figure 22 Flow paths of source-and-group-specific multicast traffic In IGMPv1 or IGMPv2, Host B cannot select multicast sources when it joins the multicast group G, and multicast streams from both Source 1 and Source 2 flow to Host B whether or not it needs them. When IGMPv3 runs between the hosts and routers, Host B can explicitly express that it needs to receive the multicast data that Source 1 sends to the multicast group G (denoted as (S1, G)), rather than the multicast data that Source 2 sends to multicast group G (denoted as (S2, G)).

  • Page 60

    BLOCK—The Source Address fields in this group record contain a list of the sources from which the system no longer 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 deleted from the list.

  • Page 61: Specifying The Igmp Version

    Step Command Remarks interface interface-type Enter interface view. interface-number Enable IGMP. igmp enable Disabled by default. Specifying the IGMP version Because the protocol packets of different IGMP versions vary in structure and type, specify the same IGMP version for all routers on the same subnet. Otherwise, IGMP cannot work properly. To specify an IGMP version: Step Command...

  • Page 62: Configuring A Multicast Group Filter

    Configuring a multicast group filter To restrict the hosts on the network attached to an interface from joining certain multicast groups, you can specify an ACL on the interface as a packet filter so that the interface maintains only the multicast groups that match the criteria.

  • Page 63: Displaying And Maintaining Igmp

    Step Command Remarks Enable IGMP fast-leave igmp fast-leave [ group-policy Disabled by default. processing. acl-number ] Displaying and maintaining IGMP CAUTION: The reset igmp group command might cause multicast data transmission failures. Execute display commands in any view and reset command in user view. Task Command display igmp group [ group-address | interface interface-type...

  • 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

    [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

    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

    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-set, all routers in the network can select the proper RP for a specific multicast group based on the following rules: The C-RP with the highest priority wins.

  • Page 73

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

  • Page 74

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

  • Page 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-scope zones must be geographically separated and isolated. A router cannot belong to multiple admin-scope zones. In other words, different admin-scope zones contain different routers. However, the global-scoped zone includes all routers in the PIM-SM domain.

  • Page 77: Configuring Pim-dm

    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 (Optional.) Enabling the state refresh feature (Optional.) Configuring state refresh parameters (Optional.)

  • Page 78: Configuring State Refresh Parameters

    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. A shared-media subnet can have the state refresh feature only if the state refresh feature is enabled on all PIM routers on the subnet. To enable the state refresh feature on all routers in PIM-DM domain: Step Command...

  • Page 79: Configuring Pim-sm

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

  • Page 80: Configuring An Rp

    IMPORTANT: All the interfaces on the same router must operate in the same PIM mode. To enable PIM-SM: Step Command Remarks Enter system view. system-view By default, IP multicast routing is Enable IP multicast routing. multicast routing-enable disabled. interface interface-type Enter interface view.

  • Page 81: Configuring A Bsr

    RPs for different multicast group ranges based on the RP-set information. HP recommends configuring C-RPs on backbone routers. To enable the BSR to distribute the RP-set information in the PIM-SM domain, the C-RPs must periodically send advertisement messages to the BSR. The BSR learns the C-RP information, encapsulates the C-RP information and its own IP address in a BSM, and floods the BSM to all PIM routers in the domain.

  • Page 82

    In a PIM-SM domain, the BSR collects C-RP information from the received advertisement messages from the C-RPs, encapsulates the C-RP information in the RP-set information, and distributes the RP-set information to all routers in the PIM-SM domain. All routers use the same hash algorithm to get an RP for a specific multicast group.

  • Page 83: Configuring Multicast Source Registration

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

  • Page 84: Configuring Switchover To Spt

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

  • Page 85: Configuration Prerequisites

    Task at a glance (Optional.) Setting the maximum size of each join or prune message (Optional.) Enabling PIM to work with BFD Configuration prerequisites Before you configure common PIM features, complete the following tasks: Configure any unicast routing protocol so that all devices in the domain are interoperable at the •...

  • Page 86: Configuring Pim Hello Message Options

    Step Command Remarks By default, no hello message filter exists. If a PIM neighbor's hello messages Configure a hello message pim neighbor-policy acl-number cannot pass the filter, the neighbor filter. is automatically removed when its maximum number of hello attempts is reached.

  • Page 87: Configuring Common Pim Timers

    Configuring hello message options globally Step Command Remarks Enter system view. system-view Enter PIM view. Set the DR priority. hello-option dr-priority priority By default, the DR priority is 1. By default, the neighbor lifetime is Set the neighbor lifetime. hello-option holdtime time 105 seconds.

  • Page 88

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

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

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

  • Page 90: Pim Configuration Examples

    Task Command Display PIM information on an display pim interface [ interface-type interface-number ] [ verbose ] interface. display pim neighbor [ neighbor-address | interface interface-type Display PIM neighbor information. interface-number | verbose ] * display pim routing-table [ group-address [ mask { mask-length | mask } ] | source-address [ mask { mask-length | mask } ] | flags flag-value | fsm Display PIM routing table | incoming-interface interface-type interface-number | mode mode-type...

  • Page 91

    Switch A VLAN-interface 100 10.110.1.1/24 Switch D VLAN-interface 300 10.110.5.1/24 VLAN-interface 103 192.168.1.1/24 VLAN-interface 103 192.168.1.2/24 Switch B VLAN-interface 200 10.110.2.1/24 VLAN-interface 101 192.168.2.2/24 VLAN-interface 101 192.168.2.1/24 VLAN-interface 102 192.168.3.2/24 Switch C VLAN-interface 200 10.110.2.2/24 VLAN-interface 102 192.168.3.1/24 Configuration procedure Configure the IP address and subnet mask for each interface as per Figure 32.

  • Page 92

    Vlan103 192.168.1.2 (local) Vlan101 192.168.2.2 (local) Vlan102 192.168.3.2 (local) # Display PIM neighboring relationships on Switch D. [SwitchD] display pim neighbor Total Number of Neighbors = 3 Neighbor Interface Uptime Expires Dr-Priority 192.168.1.1 Vlan103 00:02:22 00:01:27 1 192.168.2.1 Vlan101 00:00:22 00:01:29 3 192.168.3.1 Vlan102 00:00:23 00:01:31 5...

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

    Protocol: pim-dm, Flag: LOC ACT UpTime: 00:03:27 Upstream interface: Vlan-interface300 Upstream neighbor: NULL RPF prime neighbor: NULL Downstream interface(s) information: Total number of downstreams: 2 1: Vlan-interface103 Protocol: pim-dm, UpTime: 00:03:27, Expires: never 2: Vlan-interface102 Protocol: pim-dm, UpTime: 00:03:27, Expires: never PIM-SM non-scoped zone configuration example Network requirements As shown in...

  • Page 94

    Switch A Vlan-int100 10.110.1.1/24 Switch D Vlan-int300 10.110.5.1/24 Vlan-int101 192.168.1.1/24 Vlan-int101 192.168.1.2/24 Vlan-int102 192.168.9.1/24 Vlan-int105 192.168.4.2/24 Switch B Vlan-int200 10.110.2.1/24 Switch E Vlan-int104 192.168.3.2/24 Vlan-int103 192.168.2.1/24 Vlan-int103 192.168.2.2/24 Switch C Vlan-int200 10.110.2.2/24 Vlan-int102 192.168.9.2/24 Vlan-int104 192.168.3.1/24 Vlan-int105 192.168.4.1/24 Configuration procedure Assign an IP address and subnet mask to each interface according to Figure 33.

  • Page 95

    [SwitchE-acl-basic-2005] rule permit source 225.1.1.0 0.0.0.255 [SwitchE-acl-basic-2005] quit [SwitchE] pim [SwitchE-pim] c-bsr 192.168.9.2 hash-length 32 priority 20 [SwitchE-pim] c-rp 192.168.9.2 group-policy 2005 [SwitchE-pim] quit Verifying the configuration # Display PIM information on Switch A. [SwitchA] display pim interface Interface NbrCnt HelloInt DR-Pri DR-Address Vlan100...

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

    # 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 00:51:45 00:02:22 192.168.9.2 00:51:45 00:02:22 PIM-SM admin-scoped zone configuration example Network requirements As shown in Figure 34, VOD streams are sent to receiver hosts in multicast.

  • Page 97

    Figure 34 Network diagram 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 Vlan-int101 10.110.1.1/24 Vlan-int108 10.110.7.1/24 Switch B Vlan-int200 192.168.2.1/24 Vlan-int107 10.110.8.1/24 Vlan-int101 10.110.1.2/24 Switch E Vlan-int400 192.168.4.1/24 Vlan-int103 10.110.2.1/24 Vlan-int104 10.110.4.2/24 Vlan-int102 10.110.3.1/24 Vlan-int108...

  • Page 98

    # On Switch A, enable IP multicast routing globally, enable IGMP on VLAN-interface 100, and enable PIM-SM on each interface. <SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] igmp enable [SwitchA-Vlan-interface100] pim sm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 101 [SwitchA-Vlan-interface101] pim sm [SwitchA-Vlan-interface101] quit The configuration on Switch E and Switch I is similar to that on Switch A.

  • Page 99

    # On Switch D, configure VLAN-interface 107 as the boundary of admin-scoped zone 2. <SwitchD> system-view [SwitchD] interface vlan-interface 107 [SwitchD-Vlan-interface107] multicast boundary 239.0.0.0 8 [SwitchD-Vlan-interface107] quit Configure C-BSRs and C-RPs: # On Switch B, configure the service scope of RP advertisements and configure VLAN-interface 101 as a C-BSR and a C-RP for admin-scoped zone 1.

  • Page 100

    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 Bootstrap timer: 00:01:44 Elected BSR address: 10.110.9.1 Priority: 64 Hash mask length: 30 Uptime: 00:01:45 Scope: 239.0.0.0/8 State: Elected...

  • Page 101: Troubleshooting Pim

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

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

    of the router's RPF neighbor operate in different PIM modes, the multicast distribution tree cannot be built correctly, causing abnormal multicast forwarding. The same PIM mode must run on the entire network. Otherwise, the multicast distribution tree cannot • be built correctly, causing abnormal multicast forwarding. Solution Use display ip routing-table to verify that a unicast route to the multicast source or the RP is available.

  • Page 103: An Rpt Cannot Be Built Or Multicast Source Registration Fails In Pim-sm

    Analysis RPs are the core of a PIM-SM domain. An RP serves a specific multicast group, and multiple RPs can • coexist on a network. Make sure the RP information on all routers is exactly the same to map a specific multicast group to the same RP.

  • Page 104: Configuring Mld Snooping

    Configuring MLD snooping Overview MLD snooping enables Layer 2 switches to establish a Layer 2 multicast forwarding table instead of flooding all multicast packets. To populate the Layer 2 multicast forwarding table, MLD snooping listens to MLD messages exchanged between a Layer 3 multicast device and hosts. As shown in Figure 35, without MLD snooping enabled, the Layer 2 switch floods IPv6 multicast packets...

  • Page 105

    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/0/1 of Switch A and Switch B are the router ports.

  • Page 106: How Mld Snooping Works

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

  • Page 107

    determine whether the reported IPv6 multicast group still has active members attached to that port. For more information about the MLD report suppression mechanism, see "Configuring MLD." When receiving a done message When a host leaves an IPv6 multicast group, the host sends an MLD done message to the multicast routers.

  • Page 108: Configuring Basic Mld Snooping Functions

    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 (Optional.) Setting aging timers for dynamic ports...

  • Page 109: Specifying The Mld Snooping Version

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

  • Page 110: Configuring Parameters For Mld Queries And Responses

    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 111: Setting Aging Timers For Dynamic Ports

    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 • aging timer of the dynamic member ports. If the memberships of IPv6 multicast groups rarely change, you can set a relatively large value.

  • Page 112: Enabling Mld Snooping Fast-leave Processing

    A static member port does not respond to queries from the MLD querier. When you configure a port • as a static member port or cancel this configuration on the port, the port does not send unsolicited MLD reports or MLD done messages. •...

  • Page 113: Configuring Mld Snooping Policies

    Step Command Remarks 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. port. Configuring MLD snooping policies Before you configure MLD snooping policies, complete the following tasks: •...

  • Page 114: Configuring Ipv6 Multicast Source Port Filtering

    Configuring IPv6 multicast source port filtering When the IPv6 multicast source port filtering feature is enabled, the port can only connect to IPv6 multicast receivers rather than multicast sources. The port denies all IPv6 multicast data packets but it permits multicast protocol packets. If this feature is disabled, the port can connect to both multicast sources and IPv6 multicast receivers.

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

    Step Command Remarks 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. When you set the maximum number of IPv6 multicast groups on a port, follow these guidelines: •...

  • Page 116: Displaying And Maintaining Mld Snooping

    To enable the IPv6 multicast group replacement function globally: Step Command Remarks Enter system view. system-view Enter MLD-snooping view. mld-snooping Enable the IPv6 multicast By default, the IPv6 multicast group group replacement function overflow-replace [ vlan vlan-list ] replacement function is disabled. globally.

  • Page 117: Mld Snooping Configuration Examples

    Task Command Clear statistics for the MLD messages reset mld-snooping statistics learned by MLD snooping. MLD snooping configuration examples IPv6 group policy configuration example Network requirements As shown in Figure 37, Router A runs MLDv1 and serves as the MLD querier, and Switch A runs MLDv1 snooping.

  • Page 118

    [RouterA-Ten-GigabitEthernet1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, assign Ten-GigabitEthernet 1/0/1 through Ten-GigabitEthernet 1/0/4 to the VLAN, and enable MLD snooping and the function of dropping IPv6 unknown multicast data for the VLAN.

  • Page 119

    Host A and Host C are permanent receivers of the IPv6 multicast group FF1E::101. Configure Ten-GigabitEthernet 1/0/3 and Ten-GigabitEthernet 1/0/5 on Switch C as static member ports for the IPv6 multicast group FF1E::101 to enhance the reliability of IPv6 multicast traffic transmission. Suppose the STP runs on the network.

  • Page 120

    [RouterA] interface ten-gigabitethernet 1/0/2 [RouterA-Ten-GigabitEthernet1/0/2] ipv6 pim dm [RouterA-Ten-GigabitEthernet1/0/2] quit Configure Switch A: # Enable MLD snooping globally. <SwitchA> system-view [SwitchA] mld-snooping [SwitchA-mld-snooping] quit # Create VLAN 100, assign Ten-GigabitEthernet 1/0/1 through Ten-GigabitEthernet 1/0/3 to the VLAN, and enable MLD snooping for the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/3 [SwitchA-vlan100] mld-snooping enable...

  • Page 121: Troubleshooting Mld Snooping

    [SwitchC-Ten-GigabitEthernet1/0/5] mld-snooping static-group ff1e::101 vlan 100 [SwitchC-Ten-GigabitEthernet1/0/5] quit Verifying the configuration # Display information about the static router ports in VLAN 100 on Switch A. [SwitchA] display mld-snooping static-router-port vlan 100 VLAN 100: Router slots (0 in total): Router ports (1 in total): XGE1/0/3 The output shows that Ten-GigabitEthernet 1/0/3 on Switch A has become a static router port.

  • Page 122: Ipv6 Multicast Group Filter Does Not Work

    IPv6 multicast group filter does not work Symptom Hosts can receive multicast data from IPv6 multicast groups that are not permitted by the IPv6 multicast group filter. Analysis The IPv6 ACL is incorrectly configured. • The IPv6 multicast group filter is not correctly applied. •...

  • Page 123: Configuring Ipv6 Multicast Routing And Forwarding

    Configuring IPv6 multicast routing and forwarding Overview IPv6 multicast routing and forwarding uses the following tables: IPv6 multicast protocols' routing tables, such as the IPv6 PIM routing table. • • General IPv6 multicast routing table that summarizes the multicast routing information of different IPv6 multicast routing protocols.

  • Page 124

    RPF check implementation in IPv6 multicast Implementing an RPF check on each received IPv6 multicast packet would heavily burden the router. The use of an IPv6 multicast forwarding table is the solution to this issue. When the router creates an IPv6 multicast 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.

  • Page 125: Ipv6 Multicast Forwarding Across Ipv6 Unicast Subnets

    searches its IPv6 unicast routing table and finds that the outgoing interface to the source (the RPF interface) is Vlan-interface 20. This means that the (S, G) entry is correct but the packet traveled along a wrong path. The RPF check fails and the router discards the packet. IPv6 multicast forwarding across IPv6 unicast subnets Routers forward the IPv6 multicast data from an IPv6 multicast source hop by hop along the forwarding tree, but some routers might not support IPv6 multicast protocols in a network.

  • Page 126

    Step Command Remarks Enter system view. system-view 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 127: 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 128: Ipv6 Multicast Routing And Forwarding Configuration Example

    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 129

    Figure 41 Network diagram IPv6 multicast router IPv6 unicast router IPv6 multicast router Switch A Switch B Switch C Vlan-int101 Vlan-int102 Vlan-int101 Vlan-int102 2001::1/64 3001::2/64 2001::2/64 3001::1/64 XGE1/0/3 XGE1/0/3 Vlan-int100 Vlan-int200 GRE tunnel 1001::1/64 4001::1/64 Tunnel0 Tunnel0 5001::1/64 5001::2/64 Source Receiver Member port of the service loopback group...

  • Page 130

    # Disable STP and LLDP on interface Ten-GigabitEthernet 1/0/3 of Switch C, and add the interface to service loopback group 1. Ten-GigabitEthernet 1/0/3 does not belong to VLAN 200 or VLAN 102. [SwitchC] interface ten-gigabitethernet 1/0/3 [SwitchC-Ten-GigabitEthernet1/0/3] undo stp enable [SwitchC-Ten-GigabitEthernet1/0/3] undo lldp enable [SwitchC-Ten-GigabitEthernet1/0/3] port service-loopback group 1 [SwitchC-Ten-GigabitEthernet1/0/3] quit...

  • Page 131: Troubleshooting

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

  • Page 132: Configuring Mld

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

  • Page 133

    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 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, as shown in Figure 42.

  • Page 134: 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 135

    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 136: Specifying The Mld Version

    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 137: Configuring An Ipv6 Multicast Group Filter

    Step Command Remarks 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. Configuring an IPv6 multicast group filter To restrict the hosts on the network attached to an interface from joining certain IPv6 multicast groups, you can specify an IPv6 ACL on the interface as a packet filter so that the interface maintains only the IPv6 multicast groups that match the criteria.

  • Page 138: Displaying And Maintaining Mld

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable MLD fast-leave mld fast-leave [ group-policy By default, the MLD fast-leave processing. acl6-number ] processing is disabled. Displaying and maintaining MLD CAUTION: The reset mld group command might cause IPv6 multicast data transmission failures. Execute display commands in any view and reset command in user view.

  • Page 139

    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 140

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

    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 142: Configuring Ipv6 Pim

    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 143

    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. SPT building The process of building an SPT is the flood-and-prune process: In an IPv6 PIM-DM domain, when the IPv6 multicast source S sends IPv6 multicast data to the IPv6...

  • Page 144

    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 145: 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 146

    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 147

    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 that it serves. 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 148

    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 149

    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 150: 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: • When the RP receives the first multicast packet, it sends an (S, G) source-specific join message hop by hop toward the IPv6 multicast source.

  • Page 151

    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, which serves the IPv6 multicast groups with the scope field value as 14.

  • Page 152

    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 153

    Task at a glance (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. Enabling IPv6 PIM-DM Enable IPv6 multicast routing before Configuring IPv6...

  • Page 154

    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. A router might receive duplicate state refresh messages within a short time. To prevent this situation, you can configure the amount of time that the router must wait before receiving the next state refresh message.

  • Page 155: Configuring Ipv6 Pim-sm

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

  • Page 156

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

  • Page 157

    Step Command Remarks Enter system view. system-view Enter IPv6 PIM view. ipv6 pim c-rp ipv6-address [ advertisement-interval adv-interval | { group-policy Configure a C-RP. By default, no C-RP is configured. acl6-number | scope scope-id } | holdtime hold-time | priority priority ] * (Optional.) Configure a legal C-RP address range and the...

  • Page 158

    When an attacker controls a router in the network or when an illegal router is present in the network, • the attacker can configure the router as a C-BSR and make it win the BSR election to advertise RP information in the network. After a router is configured as a C-BSR, it automatically floods the network with BSMs.

  • Page 159: Configuring Ipv6 Multicast Source Registration

    If the RP-set information for an IPv6 multicast group range is carried in one BSMF, a non-BSR router • directly updates the RP-set information for the group range after receiving the BSMF. If the RP-set information for an IPv6 multicast group range is carried in multiple BSMFs, a non-BSR •...

  • Page 160

    Configuring switchover to SPT CAUTION: If the router is an RP, disabling switchover to SPT might cause multicast traffic forwarding failures on the source-side DR. When disabling switchover to SPT, be sure you fully understand its impact on your network. To configure switchover to SPT Step Command...

  • Page 161: Configuring A Hello Message Filter

    A filter can filter not only independent IPv6 multicast data but also IPv6 multicast data encapsulated in register messages. Generally, a filter nearer to the IPv6 multicast source has a better filtering effect. To configure an IPv6 multicast data filter: Step Command Remarks...

  • Page 162

    override a prune message. If the prune message delay or override interval on different IPv6 PIM routers on a shared-media LAN are different, the largest value takes effect. A router does not immediately prune an interface after it receives a prune message from the interface.

  • Page 163: Configuring Common Ipv6 Pim Timers

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

  • Page 164

    Step Command Remarks By default, the interval to send Set the interval to send timer join-prune interval join/prune messages is 60 join/prune messages. seconds. Set the joined/pruned state By default, the joined/pruned state holdtime join-prune time holdtime timer. holdtime timer is 210 seconds. Set the IPv6 multicast source By default, the IPv6 multicast source-lifetime time...

  • Page 165: Displaying And Maintaining Ipv6 Pim

    a new DR election process immediately after the original DR fails, you can enable IPv6 PIM to work with BFD on a shared-media network to detect failures of the links among IPv6 PIM neighbors. You must enable IPv6 PIM to work with BFD on all IPv6 PIM-capable routers on a shared-media network, so that the IPv6 PIM neighbors can fast detect DR failures and start a new DR election process.

  • Page 166: Ipv6 Pim Configuration Examples

    IPv6 PIM configuration examples IPv6 PIM-DM configuration example Network requirements VOD streams are sent to receiver hosts in multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire IPv6 PIM domain is operating in the dense mode.

  • Page 167

    Enable IPv6 multicast routing, MLD, and IPv6 PIM-DM: # On Switch A, enable IPv6 multicast routing, enable MLD on VLAN-interface 100, and enable IPv6 PIM-DM on each interface. <SwitchA> system-view [SwitchA] ipv6 multicast routing-enable [SwitchA] interface vlan-interface 100 [SwitchA-Vlan-interface100] mld enable [SwitchA-Vlan-interface100] ipv6 pim dm [SwitchA-Vlan-interface100] quit [SwitchA] interface vlan-interface 103...

  • Page 168

    FE80::B01:102:2 Vlan101 00:04:16 00:01:29 3 FE80::C01:103:3 Vlan102 00:03:54 00:01:17 5 Assume that Host A needs to receive the information addressed to IPv6 multicast group FF0E::101. After IPv6 multicast source 4001::100/64 sends IPv6 multicast packets to the IPv6 multicast group, an SPT is established through traffic flooding.

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

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

  • Page 170

    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 171

    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 172: 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 173

    Device Interface IPv6 address Device Interface IPv6 address Vlan-int101 1002::1/64 Vlan-int108 6001::1/64 Switch B Vlan-int200 2001::1/64 Vlan-int107 6002::1/64 Vlan-int101 1002::2/64 Switch E Vlan-int400 7001::1/64 Vlan-int103 2002::1/64 Vlan-int104 3002::2/64 Vlan-int102 2003::1/64 Vlan-int108 6001::2/64 Switch C Vlan-int300 3001::1/64 Switch F Vlan-int109 8001::1/64 Vlan-int104 3002::1/64 Vlan-int107...

  • Page 174

    [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. (Details not shown.) Configure IPv6 admin-scoped zone boundaries: # On Switch B, configure VLAN-interface 102 and VLAN-interface 103 as the boundaries of IPv6 admin-scoped zone 1.

  • Page 175

    [SwitchF-pim6] c-bsr 8001::1 [SwitchF-pim6] c-rp 8001::1 [SwitchF-pim6] quit Verifying the configuration # Display BSR information on Switch B. [SwitchB] display ipv6 pim bsr-info Scope: non-scoped State: Accept Preferred Bootstrap timer: 00:01:25 Elected BSR address: 8001::1 Priority: 64 Hash mask length: 126 Uptime: 00:01:45 Scope: 4 State: Elected...

  • Page 176

    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 # Display RP information on Switch B. [SwitchB] display ipv6 pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address...

  • Page 177: Troubleshooting Ipv6 Pim

    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) 00:02:03 00:02:56 Group/MaskLen: FFC4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local) 00:02:03 00:02:56 Group/MaskLen: FFD4::/16 RP address Priority HoldTime Uptime Expires 1002::2 (local)

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

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

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

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

  • Page 180

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

  • Page 181: Support And Other Resources

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

  • Page 182: 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 183

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

    Index abnormal multicast data termination, 171 C-BSR (PIM-SM configuration), 74 ACL, 106 changing IGMP snooping policy configuration, 22 multicast RPF route, 40 troubleshooting IGMP snooping multicast group check filter, 30 multicast RPF mechanism, 32 address configuring Ethernet multicast MAC address, 8 basic IGMP, 53 IPv4 multicast, 6 basic IGMP snooping, 17...

  • Page 185

    IPv6 PIM-SM C-BSR, 150 PIM common features, 77 IPv6 PIM-SM C-RP, 149 PIM common timers, 80 IPv6 PIM-SM domain border, 151 PIM common timers globally, 81 IPv6 PIM-SM features, 153 PIM common timers on interface, 81 IPv6 PIM-SM hello message filter, 154 PIM domain border, 75 IPv6 PIM-SM hello message options, 154 PIM hello message filter, 78...

  • Page 186

    displaying PIM, 82 MLD snooping IPv6 multicast unknown data domain border (IPv6 PIM-SM), 151 dropping globally, 107 domain border (PIM), 75 PIM to work with BFD, 82 done message (MLD snooping), 100 PIM-DM, 70 PIM-DM state-refresh feature, 70 enabling IPv6 PIM to work with BFD, 157 PIM-SM, 72 enabling PIM to work with BFD, 82 entry...

  • Page 187

    IGMP snooping drop unknown multicast data IPv6 PIM-SM hello message options configuration, enable, 23 IGMP snooping multicast group filter configuration, IPv6 PIM-SM join/prune message size configuration, 157 IGMP snooping multicast group filter global IPv6 PIM-SM multicast data filter configuration, configuration, 22 IGMP snooping multicast group filter port IPv6 PIM-SM multicast source registration, 141 configuration, 22...

  • Page 188

    IGMP snooping multicast group filter port maintaining, 25 configuration, 22 max number multicast groups on a port, 23 IGMP snooping multicast group replacement, 24 multicast group filter configuration, 22 IGMP snooping static port configuration, 27 multicast group filter global configuration, 22 IPv6 multicast MLDv2 group filtering, 127 multicast group filter port configuration, 22 MLDv1 IPv6 multicast group joining, 126...

  • Page 189

    IPv4 PIM-SM configuration, 72 configuring IGMP snooping multicast source port PIM-SM DR election, 63 filtering, 22 troubleshooting MLD snooping IPv6 multicast Ethernet multicast MAC address, 8 group filter does not work, 1 15 multicast address, 6 unicast routing table, 1 16 IPv6 unicast subnets, 1 18 basic MLD configuration, 128...

  • Page 190

    neighbor discovery, 136 IPv6 multicast forwarding configuration, 1 19 protocols and standards, 145 IPv6 multicast routing configuration, 1 19 SPT building, 136 IPv6 multicast routing enable, 1 18 IPv6 PIM-SM PIM configuration, 60, 83 administrative scoping, 143 PIM-DM configuration, 83 admin-scoped zone configuration, 165 PIM-SM admin-scoped zone configuration, 89 assert, 143...

  • Page 191

    MLD snooping basic configuration, 101 IPv6 group policy configuration, 1 10 MLD snooping configuration, 97, 100, 1 10 IPv6 multicast group filter configuration, 106 MLD snooping fast-leave processing enable, 105 IPv6 multicast group filter global configuration, MLD snooping IPv6 group policy configuration, 1 10 IPv6 multicast group filter port configuration, 106 MLD snooping static port configuration, 1 1 1...

  • Page 192

    ASM model, 5 IPv6 PIM-DM enable, 146 basic MLD configuration, 128 IPv6 PIM-DM graft, 137 broadcast transmission technique, 2 IPv6 PIM-DM graft retry timer configuration, 147 common notation, 4 IPv6 PIM-DM neighbor discovery, 136 configuring PIM-DM, 70 IPv6 PIM-DM SPT building, 136 data distribution, 4 IPv6 PIM-DM state refresh feature enable, 146 disabling PIM-SM BSM semantic fragmentation,...

  • Page 193

    MLD configuration, 125, 128, 131 PIM-SM administrative scoping, 68 MLD enable, 128 PIM-SM administrative scoping mechanism, 68 MLD fast leave processing, 130 PIM-SM admin-scoped zone configuration, 89 MLD IPv6 multicast group filter configuration, 130 PIM-SM assert, 67 MLD performance adjustment, 130 PIM-SM BSR configuration, 74 MLD snooping aging timer for dynamic port, 98 PIM-SM C-BSR configuration, 74...

  • Page 194

    troubleshooting IPv6 PIM-SM multicast source IPv6 PIM-DM graft retry timer configuration, 147 registration failure, 172 IPv6 PIM-DM state refresh feature enable, 146 troubleshooting MLD snooping IPv6 multicast IPv6 PIM-DM state refresh parameter configuration, group filter does not work, 1 15 troubleshooting MLD snooping Layer 2 multicast IPv6 PIM-SM BSM semantic fragmentation function, forwarding cannot function, 1 14...

  • Page 195

    PIM hello message filter configuration, 78 IPv6 PIM-DM configuration, 145, 159 PIM hello message options configuration, 79 IPv6 PIM-SM admin-scoped zone configuration, PIM join/prune message size, 82 PIM multicast data filter configuration, 78 IPv6 PIM-SM configuration, 148 PIM-DM assert, 62 IPv6 PIM-SM non-scoped zone configuration, 162 PIM-DM graft, 62 MLD configuration, 125, 128, 131...

  • Page 196

    enabling, 72 common timer configuration, 80 enabling PIM to work with BFD, 82 common timer global configuration, 81 introduction, 63 common timer interface configuration, 81 multicast source registration, 66 configuration, 60, 83 neighbor discovery, 63 configuring common features, 77 non-scoped zone configuration, 86 configuring hello message filter, 78 PIM domain border configuration, 75 configuring hello message options, 79...

  • Page 197

    IGMP snooping static port configuration, 20, 27 configuring IGMP snooping multicast group filter, max number IPv6 multicast groups on a port, 108 MLD snooping aging timer for dynamic port, 98 configuring IGMP snooping multicast group filter MLD snooping basic configuration, 101 globally, 22 MLD snooping configuration, 97, 100, 1 10 configuring IGMP snooping multicast group filter...

  • Page 198

    configuring IPv6 PIM-SM RP, 149 configuring PIM hello message filter, 78 configuring IPv6 PIM-SM static RP, 149 configuring PIM hello message options, 79 configuring IPv6 PIM-SM switchover to SPT, 153 configuring PIM hello message options globally, configuring IPv6 PIM-SM timer, 156 configuring IPv6 PIM-SM timer globally, 156 configuring PIM hello message options on configuring IPv6 PIM-SM timer on interface, 157...

  • Page 199

    enabling MLD snooping, 101 specifying MLD version, 129 enabling MLD snooping fast-leave processing, protocols and standards Layer 2 multicast, 10 enabling MLD snooping IPv6 multicast group Layer 3 multicast, 9 replacement function, 108 MLD, 128 enabling MLD snooping IPv6 multicast group MLDv2, 128 replacement function globally, 108 multicast, 9...

  • Page 200

    IGMP snooping drop unknown multicast data IPv6 PIM-SM configuration, 148 enable, 23 IPv6 PIM-SM C-RP configuration, 149 IGMP snooping dynamic port aging timer, 19 IPv6 PIM-SM domain border configuration, 151 IGMP snooping enable, 17 IPv6 PIM-SM DR election, 138 IGMP snooping fast leave...

  • Page 201

    MLD static member interface configuration, 129 PIM-SM multicast source registration configuration, MLD version specification, 129 MLD versions, 125 PIM-SM neighbor discovery, 63 multicast address, 6 PIM-SM non-scoped zone configuration, 86 multicast configuration, 32, 36, 37, 40 PIM-SM relationship between admin-scope and multicast forwarding across unicast subnets, 36 global scope zones, 68 multicast forwarding boundary configuration, 38...

  • Page 202

    IPv6 multicast RPF check implementation, 1 17 troubleshooting IPv6 PIM-SM multicast source IPv6 multicast RPF check mechanism, 1 16 registration failure, 172 IPv6 multicast RPF check process, 1 16 troubleshooting PIM-SM multicast source IPv6 multicast route selection rule registration failure, 96 configuration, 1 19 specifying IGMP snooping version, 18 multicast check mechanism, 32...

  • Page 203

    PIM configuration, 83 MLD snooping query/response parameter global PIM-DM configuration, 83 configuration, 103 PIM-SM admin-scoped zone configuration, 89 MLD snooping query/response parameter VLAN PIM-SM non-scoped zone configuration, 86 configuration, 103 switch (IGMP configuration), 56 PIM common timers, 80 switch configuration for IPv6 multicast forwarding PIM common timers global configuration, 81 over tunnel, 121 PIM common timers interface configuration, 81...

  • Page 204

    PIM-SM RP cannot join SPT, 95 IGMP query/response parameters (IGMP tunnel snooping), 18 IPv6 multicast forwarding over GRE tunnel IGMP snooping configuration, 13, 16, 25 configuration, 121 IGMP snooping drop unknown multicast data multicast forwarding across unicast subnets, 36 enable, 23 multicast forwarding over GRE tunnel, 44 IGMP snooping dynamic port aging timer, 19 unicast...

This manual also for:

5900 series

Comments to this Manuals

Symbols: 0
Latest comments: