SupportDocumentationRoutersCore RouterNE5000EConfiguration & CommissioningConfiguration Guide

NE5000E V800R022C00SPC500 Configuration Guide

IP Multicast Routing Management Configuration

IP Multicast Routing Management Configuration

The system synchronously maintains multiple multicast routing protocols, and controls multicast routing and forwarding by exchanging information between the control plane and forwarding plane.

Overview of IP Multicast Routing Management

Multicast routing and forwarding are implemented based multicast protocol routing and the multicast forwarding tables. Multicast routing and forwarding control are implemented based on multicast routing management.

In multicast implementation on the NE5000E, multicast routing and forwarding involve the following aspects:

  • Each multicast routing protocol has a routing table, for example, a PIM routing table.

  • Routing entries of each multicast routing protocol are directly delivered to a multicast forwarding table. The multicast forwarding table controls the forwarding of multicast data packets.

A multicast routing protocol creates multicast routing entries based on the RPF mechanism. This ensures that multicast data can be transmitted along a correct path. The system performs the RPF check based on the following types of routes:

  • Unicast routes

    A unicast routing table collects the shortest route to each destination.

  • Multicast static routes

    A multicast static routing table contains statically configured RPF routes.

Multicast route management is used to manage multicast routing tables, control the generation of multicast routes, and change multicast RPF routes.

Feature Requirements for IP Multicast Routing Management

Configuring RPF Routes

A multicast routing protocol creates multicast routing entries based on the Reverse Path Forwarding (RPF) mechanism and then establishes an MDT.

Usage Scenario

The RPF check is a basis of multicast routing. The process of performing an RPF check is as follows:

  1. Based on the source of a packet, a router searches its unicast routing table and multicast static routing table for optimal routes.

  2. The router selects a route with the highest priority from the multiple optimal routes as an RPF route. If the inbound interface of the packet is the same as the RPF interface, the packet passes the RPF check; otherwise, the packet fails the RPF check.

    If the priorities of the optimal routes are the same, the router selects the route in the sequence of the multicast static route and unicast route.

By configuring multicast static routes, you can specify an RPF interface and an RPF neighbor for the specific source of packets.

In choosing an upstream interface, a multicast router prefers the route with the highest next-hop address by default. If there are multiple equal-cost unicast routes, you can configure different policies of implementing multicast load splitting among these routes and designating different upstream interfaces for different multicast entries. In this manner, the transmission of multiple multicast data flows over a network is optimized.

Pre-configuration Tasks

Before configuring RPF routes, complete the following tasks:

  • Configure a unicast routing protocol to ensure that unicast routes are reachable.

  • Configure basic multicast functions.

Configuring Multicast Static Routes

Multicast static routes are an important basis of the Reverse Path Forwarding (RPF) check. By configuring multicast static routes, you can specify an RPF interface and an RPF neighbor for the specific source of packets.

Context

Multicast static routes implement the following functions, depending on specific applicable environments:

  • Change RPF routes.

    If the multicast topology is the same as the unicast topology, the transmission path of multicast data is the same as that of unicast data. You can configure multicast static routes on the NE5000E to change the RPF routes. Thus, a transmission path dedicated for the multicast data is established, which is different from the transmission path of unicast data.

  • Connect RPF routes.

    On the network segment where unicast routes are blocked, when multicast static routes are not configured, packets cannot be forwarded because there is no RPF route. In such a case, you can configure multicast static routes on the NE5000E. The system can then generate RPF routes, complete the RPF check, create routing entries, and guide packet forwarding.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ip rpf-route-static [ vpn-instance vpn-instance-name ] source-address { mask | mask-length } { rpf-nbr | { interface-name | interface-type interface-number } } [ preference preValue ]

    A multicast static route is configured.

    If the next-hop interface is a P2P interface, you can configure an outbound interface (RPF interface) by specifying the interface-type interface-number parameter in the command.

    If the next-hop interface is not a P2P interface, you must configure a next-hop address (IP address of the RPF neighbor) by specifying the rpf-nbr parameter in the command.

  3. (Optional) Run ip rpf-route-static frr [ vpn-instance vpn-instance-name ]

    FRR is configured for the multicast static route.

  4. Run commit

    The configuration is committed.

Follow-up Procedure

After the ip rpf-route-static command is configured, the multicast static route may not take effect. This is because the outbound interface may be unavailable for recursion or the specified interface may be Down. Therefore, after configuring the multicast static route, run the display ip routing-table table-name msr command to check whether the route is configured successfully.

Configuring Multicast Load Splitting

Multicast load splitting applies to the scenario in which multiple equal-cost unicast routes of the same type exist. In such a case, multicast load splitting can be performed based on configured policies to optimize the transmission of multiple multicast data flows.

Context

The configuration related to the VPN instance applies only to the provider edge (PE). If you want to configure multicast load splitting for a VPN instance on the PE, you must perform the configuration in the VPN instance view. In other cases, you need to perform the configuration in the public network instance view.

The Reverse Path Forwarding (RPF) check is a basis of multicast routing. Based on RPF rules, the router selects a unique route for multicast data forwarding. If multicast traffic is overloaded, network congestion may occur and the multicast service is thus interrupted.

The multicast load splitting function extends multicast routing rules, and multicast routing no long fully depends on the RPF check. If there are multiple equal-cost optimal routes, multicast traffic is load split to these equal-cost routes.

Procedure

  • Configure multicast load splitting in the public network instance.
    1. Run system-view

      The system view is displayed.

    2. Run multicast load-splitting { stable-preferred | source | group | source-group | balance-ucmp }

      Multicast load splitting is configured.

      • stable-preferred: indicates stable-preferred load splitting. This policy applies to a stable multicast networking.

        If stable-preferred is specified, the router automatically adjusts and balances the entries when equal-cost routes are added or deleted; however, the router does not automatically adjust and balance the entries when multicast routing entries are deleted.

      • group: indicates group address-based load splitting. This policy applies to the scenario of one source to multiple groups.

      • source: indicates source address-based load splitting. This policy applies to the scenario of one group to multiple sources.

      • source-group: indicates source and group addresses-based load splitting. This policy applies to the scenario of multiple sources to multiple groups.

      • balance-ucmp: Indicates link bandwidth-based load splitting. This policy is applicable to the scenario in which links have different bandwidth.

    3. Run commit

      The configuration is committed.

  • Configure multicast load splitting in a VPN instance.
    1. Run system-view

      The system view is displayed.

    2. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    3. Run multicast load-splitting { stable-preferred | source | group | source-group | balance-ucmp }

      Multicast load splitting is configured.

    4. Run commit

      The configuration is committed.

Configuring Longest Match for Multicast Route Selection

If the longest match principle is configured for route selection, an optimal intra-domain unicast route, an optimal inter-domain unicast route, and an optimal multicast static route are selected. One of them is finally selected as the multicast data forwarding path.

Context

Configurations related to VPN instances apply only to PE devices. When configuring the longest match of multicast routes for a VPN instance on a PE, perform the configuration in the VPN instance. In other cases, the longest match is configured in the public network instance.

If the longest match principle is configured for route selection, a multicast device prefers the route with the longest matched mask. If the mask lengths of multiple routes are the same, the device selects a route as the multicast data forwarding path in the order of the static multicast route, inter-domain unicast route, and intra-domain unicast route.

By default, a route with the highest priority is selected.

Perform the following steps on the multicast router:

Procedure

  • Configure longest match of multicast routes in the public network instance.
    1. Run system-view

      The system view is displayed.

    2. Run multicast longest-match

      Routes are selected based on the longest match rule.

    3. Run commit

      The configuration is committed.

  • Configure longest match of multicast routes in the VPN instance.
    1. Run system-view

      The system view is displayed.

    2. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    3. Run multicast longest-match

      Routes are selected based on the longest match rule.

    4. Run commit

      The configuration is committed.

Verifying the RPF Route Configuration

After configuring Reverse Path Forwarding (RPF) routes, verify configuration of the RPF routes.

Prerequisites

RPF routes have been configured.

Procedure

  1. Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] rpf-info source-address [ group-address ] [ rpt | spt ] command to check information about the source-specific RPF route.

Configuring Multicast Multi-Topologies

With multicast multi-topologies, multicast services can run in a specified topology, which isolates multicast services from unicast services and eliminates the configuration conflict when both multicast services and unidirectional Traffic Engineering (TE) tunnel services are deployed. In deploying multicast multi-topologies, you can specify either a multicast topology instance or a unicast topology instance for running multicast services.

Usage Scenario

  • Currently, multicast services highly depend on unicast routes. During multicast routing, a router searches a unicast routing table for an optimal route. If the unicast optimal route, shared by both multicast services and unicast services, is faulty, the multicast services and unicast services will be interrupted and users will fail to receive the multicast data. With multicast multi-topologies, multicast services can run in a specified topology, which isolates multicast services from unicast services.

  • With both multicast services and unidirectional TE tunnel services deployed, if a unidirectional TE tunnel interface is chosen during multicast routing, the multicast data will fail to pass the Reverse Path Forwarding (RPF) check. The local multicast-topology (MT) feature can address this problem. However, in this situation, a separate Multicast Interior Gateway Protocol (MIGP) routing table has to be maintained, which consumes network resources. With multicast multi-topologies, the system searches for routes only in the unicast routing table, the static multicast routing table, and the MBGP routing table specified by the multicast topology. These routing tables contain no unidirectional TE tunnel interfaces, avoiding the problem that multicast data fails to pass the RPF check when a unidirectional TE tunnel interface is chosen. In addition, no separate MIGP routing tables have to be maintained, so network resources can be properly planned.

When configuring multicast multi-topologies, you can configure a multicast topology instance or a unicast topology instance. A multicast topology can be used in both PIM-SM intra-domain and inter-domain scenarios, but a unicast topology instance can be used only in a PIM-SM intra-domain scenario.

Pre-configuration Tasks

Before configuring multicast multi-topologies, complete the following tasks:

Enabling Multicast Services to Run in a Multicast Topology Instance

Using a multicast topology instance for multicast services applies to both PIM-SM intra-domain and inter-domain scenarios.

Context

Before enabling multicast services to run in a specified multicast topology instance, you must configure the multicast topology instance in the system view.

For the configuration details, see Configuring IPv4 Multi-topology. Ensure that topology-name is multicast.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast rpf multi-topology

    Multicast services are enabled to run in a multicast topology instance.

  3. Run commit

    The configuration is committed.

Enabling Multicast Services to Run in a Unicast Topology Instance

Using a unicast topology instance for multicast services applies only to the PIM-SM intra-domain scenario.

Context

Before enabling multicast services to run in a specified unicast topology instance, you must configure a multicast topology instance and a unicast topology instance in the system view.

For the configuration details, see Configuring IPv4 Multi-topology. Ensure that one of the topology names is multicast.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast rpf multi-topology

    The multicast multi-topologies view of the public network instance is displayed.

  3. Run apply topology { base | topology-name }

    Multicast services are enabled to run in a unicast topology instance.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of Running Multicast Services in a Multicast Multi-topology Instance

After configuring multicast multi-topologies for multicast services, verify information about the current topology of the multicast network.

Prerequisites

Multicast multi-topologies have been configured.

Procedure

  • Run the display multicast rpf-info source-address [ group-address ] [ rpt | spt ] [ verbose ] command to check the current topology of the multicast network.

Controlling Multicast Forwarding Range

Multicast data for each multicast group on a network needs to be transmitted in a certain range. You can control the multicast forwarding range by setting a minimum TTL value for multicast packets or a multicast forwarding boundary.

Usage Scenario

Multicast data for each multicast group on a network needs to be transmitted in a specific range. The NE5000E supports the following methods for controlling multicast forwarding range:

  • Configure a multicast forwarding boundary on an interface to form a closed multicast forwarding area. After an interface is configured with a forwarding boundary for a specific group, the interface does not forward or receive any multicast packet for this group.

  • Set a minimum TTL value for multicast packets to restrict the transmission distance of multicast packets. The interface forwards only the multicast packets with the TTL value being greater than or equal to the minimum TTL value. If the TTL value of a packet is smaller than the minimum TTL value, the interface discards the packet.

Pre-configuration Tasks

Before controlling the multicast forwarding range, complete the following tasks:

  • Configure a unicast routing protocol to ensure that unicast routes are reachable.

  • Configure basic multicast functions.

Adjusting the Minimum TTL Value for Multicast Forwarding

Multicast information of each multicast group on a network should be transmitted within a specific range. Therefore, setting the minimum TTL value for multicast forwarding is necessary for limiting the multicast data forwarding scope.

Usage Scenario

Setting the minimum TTL value for multicast forwarding on an interface to limit the distance to which a packet is forwarded. The interface forwards only the packets (including those generated by the local device) with the TTL value being greater than or equal to the minimum TTL value. If the TTL value of a packet is smaller than the minimum TTL value, the interface discards the packet.

Pre-configuration Tasks

Before adjusting the minimum TTL value for multicast forwarding, complete the following tasks:

  • Configure a unicast routing protocol to ensure that unicast routes are reachable.

  • Configure basic multicast functions.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run multicast minimum-ttl ttl-value

    The minimum TTL value for multicast forwarding is set.

  4. Run commit

    The configuration is committed.

Checking the Configurations

Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] minimum-ttl interface-type interface-number command to check the minimum TTL value for multicast forwarding on an interface.

Configuring the Multicast Forwarding Boundary

When an interface of a multicast device is configured with a forwarding boundary for a specified group, the forwarding scope of multicast packets is restricted.

Context

By default, no multicast forwarding boundary is configured on an interface.

Perform the following steps on the multicast router:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run multicast boundary group-address { mask | mask-length }

    The multicast forwarding boundary is configured.

Checking the Configurations

Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] boundary [ group-address [ mask | mask-length ] ] [ interface interface-type interface-number ] command to check information about the multicast boundary configured on an interface.

Enabling the Function to Iterate Original Next Hops of Multicast Routes to MIGP Shortcuts

To ensure that a public network router can forward multicast traffic normally, enable the router to iterate original next hops of multicast routes to MIGP shortcuts.

Usage Scenario

If both multicast and IGP shortcut-enabled MPLS TE tunnels are configured on a network, the outbound interface of a route calculated by the IGP may not be a physical interface but a TE tunnel interface. If the original next hop of a BGP-advertised route to a multicast source is an IGP shortcut, the device sends Join messages out through a TE tunnel interface along the unicast route to the multicast source. As a result, the devices that are not on the TE tunnel will not receive the Join messages or create multicast forwarding entries.

To resolve this issue, enable the device to iterate original next hops of multicast routes to MIGP shortcuts. Physical interfaces are then used as next-hop outbound interfaces of multicast routes, and multicast forwarding entries can be created.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast recursive-lookup local-mt enable

    The function to iterate original next hops of multicast routes to MIGP shortcuts is enabled.

  3. Run commit

    The configuration is committed.

Disabling Soft Forwarding for Multicast Packets

Disabling soft forwarding for multicast packets on a multicast router prevents packet loss and disorder.

Usage Scenario

In most cases, the router forwards packets based on software before the hardware forwarding is completed. After that, the router forwards packets based on hardware.

Soft forwarding for multicast packets must be disabled on the router to prevent the low forwarding speed and first packet cache mechanism of soft forwarding from causing disorder of the first packet transmitted at a high speed.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast cpu-forward disable

    Soft forwarding is disabled for multicast packets.

  3. Run commit

    The configuration is committed.

Configuring the Maximum Number of Invalid IPv4 Multicast Protocol Packets that a Device Can Store

This section describes how to configure the maximum number of invalid ipv4 multicast protocol packets that a device can store. This configuration helps locate and rectify faults.

Usage Scenario

If multicast forwarding entries or Multicast Source Discovery Protocol (MSDP) peer relationships cannot be established on a network, you can configure the maximum number of invalid multicast protocol packets that the devices can store. Then you can check statistics and details about invalid multicast packets using related commands for troubleshooting.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast invalid-packet { igmp | mdt | msdp | pim } max-count max-number

    The maximum number of invalid multicast protocol packets that the device can store is configured.

  3. Run commit

    The configuration is committed.

Checking the Configuration

Run the display current-configuration | include multicast invalid-packet command to check the maximum number of invalid multicast protocol packets that the device can store.

<HUAWEI> display current-configuration | include multicast invalid-packet
 multicast invalid-packet igmp max-count 20

To check statistics about invalid multicast protocol packets that the device stores, perform the following operations:

  • Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] invalid-packet [ interface interface-type interface-number | message-type { leave | query | report } ] * command to check statistics about invalid Internet Group Management Protocol (IGMP) packets that the device stores.

    <HUAWEI> display igmp invalid-packet

           Statistics of invalid packets for public net:
--------------------------------------------------------------------
IGMP Query invalid packet:
Unwanted Source List    : 1000        Zero Max Resp Code      : 0
Fault Length            : 1000        Invalid Multicast Group : 0
Bad Checksum            : 0

IGMP Report invalid packet:
Fault Length            : 0           Invalid Multicast Group : 0
Invalid Multicast Source: 0           Bad Checksum            : 0
Illegal Report Type     : 0

IGMP Leave invalid packet:
Invalid Multicast Group : 0           Bad Checksum            : 0
--------------------------------------------------------------------

  • Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] invalid-packet [ peer peer-address | message-type { keepalive | notification | sa-request | sa-response | source-active } ] * command to check statistics about invalid MSDP packets that the device stores.

    <HUAWEI> display msdp invalid-packet peer 1.1.1.1

             Statistics of invalid packets for public net:                      
--------------------------------------------------------------------            
MSDP SA invalid packet:
Fault Length            : 0           Bad Length-x            : 0
Bad Sprefix             : 0           Invalid Multicast Group : 0
Invalid Multicast Source: 0           Bad Encap Data          : 0
Illegal RP Addr         : 0           RP Loop                 : 0

MSDP SA Response invalid packet:
Fault Length            : 0           Bad Length-x            : 0
Bad Sprefix             : 0           Invalid Multicast Group : 0
Invalid Multicast Source: 0           Illegal RP Addr         : 0
RP Loop                 : 0

MSDP SA Request invalid packet:
Fault Length            : 0           Invalid Multicast Group : 0

MSDP Keep Alive invalid packet:
Fault Length            : 0

MSDP Notification invalid packet:
Fault Length            : 0                         
--------------------------------------------------------------------

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] invalid-packet [ interface interface-type interface-number | message-type { hello | join-prune | assert | bsr | announcement | discovery } ] * command to check statistics about invalid Protocol Independent Multicast (PIM) packets that the device stores.

    <HUAWEI> display pim invalid-packet

             Statistics of invalid packets for public net:                      
--------------------------------------------------------------------         
PIM General invalid packet:
Invalid PIM Version     : 0           Invalid PIM Type        : 0
Fault Length            : 0           Bad Checksum            : 0

PIM Register invalid packet:
Invalid Multicast Source: 0           Invalid Multicast Group : 0
Invalid Dest Addr       : 0

PIM Register-Stop invalid packet:
Invalid Multicast Source: 0           Invalid Multicast Group : 0
Invalid Dest Addr       : 0           IP Source not RP        : 0

PIM CRP invalid packet:
Invalid Dest Addr       : 0           Invalid CRP Addr        : 0
Fault Length            : 0           CRP Adv Fault Length    : 0
Invalid Multicast Group : 0

PIM Assert invalid packet:
Invalid Dest Addr       : 0           Invalid IP Source Addr  : 0
Invalid Multicast Source: 0           Invalid Multicast Group : 0

PIM BSR invalid packet:
Bad Payload             : 0           Fault Length            : 0
Bad Scope Mask          : 0           Invalid Multicast Group : 0
Not CBSR But BSR        : 0           Invalid BSR Addr        : 0
Fault Hash Length       : 0           Invalid IP Source Addr  : 0

PIM Hello invalid packet:
Invalid Addr List       : 0           Fault Length            : 0
Bad Holdtime Length     : 0           Bad LanPruneDelay Length: 0
Bad DrPriority Length   : 0           Bad GenID Length        : 0
Invalid Dest Addr       : 0           Invalid IP Source Addr  : 0

PIM Join/Prune invalid packet:
Invalid Multicast Source: 0           Invalid Multicast Group : 0
Invalid Up Neighbor     : 0           Invalid IP Source Addr  : 0
Invalid Dest Addr       : 0           Fault Length            : 0  

PIM Graft invalid packet:
Invalid Multicast Source: 0           Invalid Multicast Group : 0
Invalid Up Neighbor     : 0           Invalid IP Source Addr  : 0
Fault Length            : 0

PIM Graft-Ack invalid packet:
Invalid Multicast Source: 0           Invalid Multicast Group : 0
Invalid Up Neighbor     : 0           Invalid IP Source Addr  : 0
Fault Length            : 0

PIM State Refresh invalid packet:
Invalid Multicast Source: 0           Invalid Multicast Group : 0
Invalid Originator Addr : 0           Fault Length            : 0
--------------------------------------------------------------------

  • Run the display multicast-domain { vpn-instance vpn-instance-name | all-instance } invalid-packet command to check statistics about invalid multicast distribution tree (MDT) switch messages that the device stores.

    <HUAWEI> display multicast-domain vpn-instance vpn1 invalid-packet
             Statistics of invalid packets for vpn1:            
--------------------------------------------------------------------            
MDT Switch invalid packet:
Fault Length            : 0           Invalid Message Type    : 0
Invalid Multicast Source: 0           Invalid Multicast Group : 0
Invalid Switch Group    : 0                 
--------------------------------------------------------------------

To check details about invalid multicast protocol packets, perform the following operations:

  • Run the display igmp invalid-packet [ packet-number ] verbose command to check details about invalid IGMP packets that the device stores.

    <HUAWEI> display igmp invalid-packet 1 verbose
       Detailed information of invalid packets
-----------------------------------------------------
Packet information (Index 6):
-----------------------------------------------------
Interface           :  GigabitEthernet1/0/1
Time                :  2010-6-9 11:03:51 UTC-08:00
Message Length      :  24
Invalid Type        :  Invalid Multicast Group
Source Address      :  10.0.3.3
0000: 16 3c 00 00 01 34 04 04
-----------------------------------------------------

  • Run the display msdp invalid-packet [ packet-number ] verbose command to check details about invalid MSDP packets that the device stores.

    <HUAWEI> display msdp invalid-packet 1 verbose
       Detailed information of invalid packets         
-----------------------------------------------------  
Packet information (Index 1):                          
-----------------------------------------------------  
Interface           :  GigabitEthernet1/0/1                   
Time                :  2010-6-9 11:25:46 UTC-08:00     
Message Length      :  22                              
Invalid Type        :  Invalid Addr List               
Peer Address         :  10.42.162.13
0000: 00 01 00 02 00 69 00 13 00 04 00 00 00 64 00 02  
0010: 00 04 81 f4 09 c4                                
-----------------------------------------------------

  • Run the display pim invalid-packet [ packet-number ] verbose command to check details about invalid PIM packets that the device stores.

    <HUAWEI> display pim invalid-packet 1 verbose
       Detailed information of invalid packets
-----------------------------------------------------
Packet information (Index 1):
-----------------------------------------------------
Interface           :  GigabitEthernet1/0/1
Time                :  2010-6-1 20:04:35 UTC-08:00
Message Length      :  26
Invalid Type        :  Invalid Multicast Source
Source Address      :  10.0.3.3
0000: 25 00 96 77 01 00 00 20 e1 01 01 01 01 00 e0 00
0010: 00 00 80 00 00 64 00 00 00 00
-----------------------------------------------------

  • Run the display multicast-domain invalid-packet [ packet-number ] verbose command to check details about invalid MDT switch messages that the device stores.

    <HUAWEI> display multicast-domain invalid-packet 1 verbose
       Detailed information of invalid packets      
-----------------------------------------------------   
Packet information (Index 1):                         
----------------------------------------------------- 
Neighbor           :  1.1.1.1
Time                :  2011-8-9 10:50:08 UTC-08:00
Message Length      :  16
Invalid Type        :  Invalid Switch Group
0000: 01 00 10 00 64 64 64 64 e8 00 00 00 0a 00 00 00 
-----------------------------------------------------

(Optional) Configuring Trunk Load Balancing Functions for Layer 3 Multicast

To implement better load balancing for Layer 3 multicast traffic on trunk member interfaces, configure optional trunk load balancing functions.

Usage Scenario

If multicast traffic is sent out through trunk interfaces, configure some optional load balancing functions to adjust load balancing on trunk member interfaces.

Pre-configuration Tasks

Before configuring optional trunk load balancing functions for Layer 3 multicast, specify outbound interfaces as trunk interfaces for multicast traffic.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run trunk multicast load-balance hash-mode multicast-member

    Multicast group- and trunk sub-interface-based multicast load balancing is enabled for hash-mode route selection.

    This configuration implements better load balancing for multicast flows that belong to the same multicast group but have different sub-interfaces of the same outbound trunk interface.

  3. Run commit

    The configuration is committed.

Maintaining IP Multicast Routing Management

Maintaining IP multicast routing management involves monitoring the running status of the IP multicast routing management.

Monitoring the Running Status of IP Multicast Routing Management

During routine maintenance of IP multicast routing management, you can run the display commands in any view to obtain the running status of the IP multicast routing management.

Context

Run the following command in any view to check the running status of IP multicast routing management.

Procedure

  • Run the display default-parameter mrm command in any view to check default configurations about multicast routing management.

Monitoring the Status of Multicast Routing

During the routine maintenance of IPv4 multicast routing management, you can run the display commands in any view to learn the running of the multicast forwarding table.

Context

In routine maintenance, you can run the following commands in any view to check the status of multicast forwarding.

Procedure

  • Run the following commands in any view to check the multicast forwarding table.

    • display multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table [ group-address | source-address | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | statistics | slot slot-number ] *

Configuration Examples for IP Multicast Routing Management

Examples for configuring multicast static routes, multicast load splitting, and multicast multi-topology are provided.

Example for Configuring Multicast Static Routes to Change RPF Routes

To change the Reverse Path Forwarding (RPF) route and create a multicast path different from the source-to-receiver unicast path, configure multicast static routes on the multicast network.

Networking Requirements

On a single NE5000E, interfaces are numbered in the format of slot number/card number/interface number. On the cluster, interfaces are numbered in the format of chassis ID/slot number/card number/interface number, in which the slot number is chassis ID/slot ID.

As shown in Figure 1-540, the network runs PIM-SM, all routers support multicast, and the receiver can receive information from the multicast source. IS-IS is run between routers. Configure a multicast static route to create a multicast path from the source to the receiver different from the unicast path from the source to the receiver.

Figure 1-540 Configuring multicast static routes to change RPF routes

Interfaces 1 through 3 in this example represent GE 1/0/0, GE 2/0/0, and GE 3/0/0, respectively.


Precautions

During the configuration, pay attention to the following points:

  • When configuring a multicast static route, if the next hop is a P2P interface, you can specify the outbound interface number. If the next hop is not a P2P interface, you must specify the next-hop address.

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure an IP address for each router interface and configure IS-IS on routers.

  2. Enable multicast routing on each router, enable PIM-SM on each interface, and enable IGMP on interfaces connecting routers to hosts.

  3. Configure Candidate-BootStrap Routers (C-BSRs) and Candidate-Rendezvous Points (C-RPs).

  4. Configure multicast static routes on Device B and specify Device C as an RPF neighbor to the source.

Data Preparation

To complete the configuration, you need the following data:

  • IP address of the source

  • Outbound interface of Device B to the source

Procedure

  1. Configure an IP address for each router interface and a unicast routing protocol. For configuration details, see Configuration Files in this section.
  2. Enable multicast routing on each router and PIM-SM on each router interface.

    # Configure Device A. The configurations of Device B, Device C, and Device D are similar to the configuration of Device A. For configuration details, see Configuration Files in this section.

    [~DeviceA] multicast routing-enable
    [*DeviceA] interface GigabitEthernet 1/0/0
    [*DeviceA-GigabitEthernet1/0/0] pim sm
    [*DeviceA-GigabitEthernet1/0/0] quit
    [*DeviceA] interface gigabitethernet 2/0/0
    [*DeviceA-GigabitEthernet2/0/0] pim sm
    [*DeviceA-GigabitEthernet2/0/0] quit
    [*DeviceA] interface GigabitEthernet 3/0/0
    [*DeviceA-GigabitEthernet3/0/0] pim sm
    [*DeviceA-GigabitEthernet3/0/0] commit
    [~DeviceA-GigabitEthernet3/0/0] quit

  3. Enable IGMP on interfaces that connect to hosts.

    # Enable IGMP on the interface connecting Device D to hosts.

    [~DeviceD] interface gigabitethernet 2/0/0
    [~DeviceD-GigabitEthernet2/0/0] igmp enable
    [*DeviceD-GigabitEthernet2/0/0] commit
    [~DeviceD-GigabitEthernet2/0/0] quit

  4. Configure C-BSRs and C-RPs.

    # Configure GE 3/0/0 on Device C as both a C-BSR and a C-RP.

    [~DeviceC] pim
    [*DeviceC] c-bsr GigabitEthernet 3/0/0
    [*DeviceC] c-rp GigabitEthernet 3/0/0
    [*DeviceC] commit
    [~DeviceC] quit

    # Run the display multicast rpf-info command on DeviceB to view the RPF route information of the source. The command output shows that the RPF route is a unicast route and the RPF neighbor is DeviceA.

    <DeviceB> display multicast rpf-info 10.5.1.2
    VPN-Instance: public net
    RPF information about source 10.5.1.2:
         RPF interface: GigabitEthernet1/0/0, RPF neighbor: 10.4.1.1
         Referenced route/mask: 10.5.1.0/24
         Referenced route type: unicast
         Route selection rule: preference-preferred
         Load splitting rule: disable

  5. Configure multicast static routes.

    # Configure a multicast static route on Device B and specify Device C as an RPF neighbor to the source.

    <DeviceB> system-view
    [~DeviceB] ip rpf-route-static 10.5.1.0 255.255.255.0 10.2.1.2
    [*DeviceB] commit
    [~DeviceB] quit

  6. Verify the configuration.

    # Run the display multicast rpf-info command on DeviceB to view the RPF route information of the source. The command output shows that the RPF route and the RPF neighbor have been updated according to the multicast static route. The command output is as follows.

    <DeviceB> display multicast rpf-info 10.5.1.2
    VPN-Instance: public net
    RPF information about source 10.5.1.2:
         RPF interface: GigabitEthernet2/0/0, RPF neighbor: 10.2.1.2
         Referenced route/mask: 10.5.1.0/24
         Referenced route type: mstatic
         Route selection rule: preference-preferred
         Load splitting rule: disable

Configuration Files

  • Device A configuration file

    #
sysname DeviceA
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0001.00
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 10.4.1.1 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 10.5.1.1 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet3/0/0
 undo shutdown
 ip address 10.3.1.1 255.255.255.0
 pim sm
 isis enable 1
#
return

  • Device B configuration file

    #
sysname DeviceB
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0002.00
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 10.4.1.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 10.2.1.1 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet3/0/0
 undo shutdown
 ip address 10.1.1.2 255.255.255.0
 pim sm
 isis enable 1
#
ip rpf-route-static 10.5.1.0 255.255.255.0 10.2.1.2
#
return

  • Device C configuration file

    #
sysname DeviceC
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0003.00
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 10.2.1.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet3/0/0
 undo shutdown
 ip address 10.3.1.2 255.255.255.0
 pim sm
 isis enable 1
#
pim
 c-bsr GigabitEthernet3/0/0
 c-rp GigabitEthernet3/0/0
#
return

  • Device D configuration file

    #
sysname DeviceD
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0004.00
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 10.6.1.1 255.255.255.0
 pim sm
 igmp enable
 isis enable 1
#
interface GigabitEthernet3/0/0
 undo shutdown
 ip address 10.1.1.1 255.255.255.0
 pim sm
 isis enable 1
#
return

Example for Configuring Multicast Static Routes to Connect RPF Routes

After multicast static routes are configured, a receiver can receive multicast data from a multicast source in another area that is unreachable with unicast routes.

Networking Requirements

On a single NE5000E, interfaces are numbered in the format of slot number/card number/interface number. On the cluster, interfaces are numbered in the format of chassis ID/slot number/card number/interface number, in which the slot number is chassis ID/slot ID.

As shown in Figure 1-541, the network runs PIM-SM, all routers support multicast, and the receiver can receive information from Source1. Device B and Device C run OSPF. There is no unicast route between Device A and Device B. To enable the receiver to receive information sent from Source 2, configure a multicast static route.

Figure 1-541 Configuring multicast static routes to connect RPF routes

Device Name

Interface

IP Address

DeviceA

GE1/0/0

10.1.5.1/24

GE3/0/0

10.1.4.2/24

DeviceB

GE1/0/0

10.1.2.2/24

GE2/0/0

10.1.3.1/24

GE3/0/0

10.1.4.1/24

DeviceC

GE1/0/0

10.1.2.1/24

GE2/0/0

10.1.1.1/24

Precautions

When configuring multicast static routes to connect RPF routes, note the following precautions:

  • When configuring a multicast static route, if the next hop is a Point-to-point (P2P) interface, you must specify the outbound interface number; if the next hop is not a P2P interface, you must specify the next-hop address.

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure an IP address for each router interface and configure OSPF on routers.

  2. Enable multicast routing on each router, enable PIM-SM on each interface, and enable IGMP on interfaces connecting routers to hosts.

  3. Configure candidate-bootstrap routers (C-BSRs) and candidate-rendezvous points (C-RPs).

  4. Configure multicast static routes on Device B and Device C.

Data Preparation

To complete the configuration, you need the following data:

  • IP address of Source 2

  • RPF interface connecting Device B to Source 2 and the RPF neighbor of Device B

  • RPF interface connecting Device C to Source 2 and the RPF neighbor of Device C

Procedure

  1. Configure an IP address for each router interface and a unicast routing protocol. For configuration details, see Configuration Files in this section.
  2. Enable multicast routing on each router and PIM-SM on each router interface.

    # Configure Device B. The configurations of Device A and Device C are similar to the configuration of Device B. For configuration details, see Configuration Files in this section.

    [~DeviceB] multicast routing-enable
    [*DeviceB] interface GigabitEthernet 1/0/0
    [*DeviceB-GigabitEthernet1/0/0] pim sm
    [*DeviceB-GigabitEthernet1/0/0] quit
    [*DeviceB] interface gigabitethernet 2/0/0
    [*DeviceB-GigabitEthernet2/0/0] pim sm
    [*DeviceB-GigabitEthernet2/0/0] quit
    [*DeviceB] interface GigabitEthernet 3/0/0
    [*DeviceB-GigabitEthernet3/0/0] pim sm
    [*DeviceB-GigabitEthernet3/0/0] commit
    [~DeviceB-GigabitEthernet3/0/0] quit

  3. Enable IGMP on interfaces that connect to hosts.

    # Enable IGMP on the interface connecting Device C to hosts.

    [~DeviceC] interface gigabitethernet 2/0/0
    [~DeviceC-GigabitEthernet2/0/0] igmp enable
    [*DeviceC-GigabitEthernet2/0/0] commit
    [~DeviceC-GigabitEthernet2/0/0] quit

  4. Configure C-BSRs and C-RPs.

    # Configure GE 1/0/0 on Device B as both a C-BSR and a C-RP.

    [~DeviceB] pim
    [*DeviceB] c-bsr GigabitEthernet 1/0/0
    [*DeviceB] c-rp GigabitEthernet 1/0/0
    [*DeviceB] commit
    [~DeviceB] quit

    Source 1 (10.1.3.2/24) and Source2 (10.1.5.2/24) both send multicast data to G (225.1.1.1). The receiver joins G and can receive multicast data sent from Source 1 and Source 2.

    # Run the display multicast rpf-info 10.1.5.2 command on Device B and Device C. There is no command output. This indicates that Devices have no RPF routes to Source 2.

  5. Configure multicast static routes.

    # Configure a multicast static route on Device B and specify Device A as an RPF neighbor to Source 2.

    <DeviceB> system-view
    [~DeviceB] ip rpf-route-static 10.1.5.0 255.255.255.0 10.1.4.2
    [*DeviceB] commit
    [~DeviceB] quit

    # Configure a multicast static route on Device C and specify Device B as an RPF neighbor to Source2.

    <DeviceC> system-view
    [~DeviceC] ip rpf-route-static 10.1.5.0 255.255.255.0 10.1.2.2
    [*DeviceC] commit
    [~DeviceC] quit

  6. Verify the configuration.

    # Run the display multicast rpf-info 10.1.5.2 command again on Device B and Device C. The command output shows RPF information of Source 2.

    <DeviceB> display multicast rpf-info 10.1.5.2
    VPN-Instance: public net
    RPF information about: 10.1.5.2
         RPF interface: GigabitEthernet3/0/0, RPF neighbor: 10.1.4.2
         Referenced route/mask: 10.1.5.0/24
         Referenced route type: mstatic
         Route selecting rule: preference-preferred
         Load splitting rule: disable 
    

    <DeviceC> display multicast rpf-info 10.1.5.2
    

    VPN-Instance: public net
    

    RPF information about source 10.1.5.2:
    

         RPF interface: GigabitEthernet1/0/0, RPF neighbor: 10.1.2.2
    

         Referenced route/mask: 10.1.5.0/24
    

         Referenced route type: mstatic
    

         Route selection rule: preference-preferred
    

         Load splitting rule: disable 
    

    # Run the display pim routing-table command on Device C to view information about PIM routing tables. Device C has multicast entries related to Source 2 and the receiver can receive multicast data from Source 2.
    

    <DeviceC> display pim routing-table
    

    VPN-Instance: public net
    

     Total 1 (*, G) entry; 2 (S, G) entries
    

    

     (*, 225.1.1.1)
    

         RP: 10.1.2.2
    

         Protocol: PIM-SM, Flag: WC
    

         UpTime: 03:54:19
    

         Upstream interface: NULL, Refresh time: 03:54:19
    

             Upstream neighbor: NULL
    

             RPF prime neighbor: NULL
    

         Downstream interface(s) information:
    

         Total number of downstreams: 1
    

             1: GigabitEthernet2/0/0
    

                 Protocol: PIM-SM, UpTime: 01:38:19, Expires: never
    

    

    (10.1.3.2, 225.1.1.1)     
    

         RP: 10.1.2.2
    

         Protocol: PIM-SM, Flag: ACT
    

         UpTime: 00:00:44
    

         Upstream interface: GigabitEthernet1/0/0, Refresh time: 00:00:44
    

             Upstream neighbor: 10.1.2.2
    

             RPF prime neighbor: 10.1.2.2
    

         Downstream interface(s) information:
    

         Total number of downstreams: 1
    

              1: GigabitEthernet2/0/0
    

                  Protocol: PIM-SM, UpTime: 00:00:44, Expires: never
    

    

    (10.1.5.2, 225.1.1.1)     
    

         RP: 10.1.2.2
    

         Protocol: PIM-SM, Flag: ACT
    

         UpTime: 00:00:44
    

         Upstream interface: GigabitEthernet1/0/0, Refresh time: 00:00:44
    

             Upstream neighbor: 10.1.2.2
    

             RPF prime neighbor: 10.1.2.2
    

         Downstream interface(s) information:
    

         Total number of downstreams: 1
    

              1: GigabitEthernet2/0/0
    

                  Protocol: PIM-SM, UpTime: 00:00:44, Expires: never
    



Configuration Files
  • Device A configuration file
    

    #
sysname DeviceA
#
multicast routing-enable
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 10.1.5.1 255.255.255.0
 pim sm
#
interface GigabitEthernet3/0/0
 undo shutdown
 ip address 10.1.4.2 255.255.255.0
 pim sm
#
ospf 1
 area 0.0.0.0
  network 10.1.5.0 0.0.0.255
   network 10.1.4.0 0.0.0.255
#
return

    

  • Device B configuration file
    

    #
sysname DeviceB
#
multicast routing-enable
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 10.1.2.2 255.255.255.0
 pim sm
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 10.1.3.1 255.255.255.0
 pim sm
#
interface GigabitEthernet3/0/0
 undo shutdown
 ip address 10.1.4.1 255.255.255.0
 pim sm
#
ospf 1
 area 0.0.0.0
  network 10.1.2.0 0.0.0.255
  network 10.1.3.0 0.0.0.255
#
pim
 c-bsr GigabitEthernet3/0/0
 c-rp GigabitEthernet3/0/0
#
ip rpf-route-static 10.1.5.0 24 10.1.4.2
#
return

    

  • Device C configuration file
    

    #
sysname DeviceC
#
multicast routing-enable
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 10.1.1.1 255.255.255.0
 pim sm
 igmp enable
#
interface GigabitEthernet3/0/0
 undo shutdown
 ip address 10.1.2.1 255.255.255.0
 pim sm
#
ospf 1
 area 0.0.0.0
  network 10.1.1.0 0.0.0.255
  network 10.1.2.0 0.0.0.255
#
ip rpf-route-static 10.1.5.0 24 10.1.2.2
#
return

    









Example for Configuring Multicast Load Splitting


On a PIM-SM network where multicast services are stable, configure the stable-preferred multicast load splitting policy so that multicast traffic can be distributed to multiple equal-cost routes for transmission.




Networking Requirements
 
On a single NE5000E, an interface is numbered in the format of slot number/card number/interface number. On an NE5000E cluster, an interface is numbered in the format of chassis ID/slot number/card number/interface number. If the slot number is specified, the chassis ID of the slot must also be specified.




As shown in Figure 1-542, there are three equal-cost routes from the device connected with Host A to Source. Host A needs to stably receive multicast data for a long term from the source. Configure a load splitting policy to distribute entries evenly to the three equal-cost routes. In this manner, load splitting among equal-cost routes is implemented.


Figure 1-542  Configuring multicast load splitting




Device



Interface



IP Address






Device A











GE 1/0/0



10.110.1.2/24





GigabitEthernet2/0/1



192.168.1.1/24





GigabitEthernet2/0/2



192.168.2.1/24





GigabitEthernet2/0/3



192.168.3.1/24





LoopBack0



1.1.1.1/32





DeviceB





GE 1/0/0



192.168.1.2/24





GigabitEthernet2/0/0



192.168.4.1/24





DeviceC





GE 1/0/0



192.168.2.2/24





GigabitEthernet2/0/0



192.168.5.1/24





DeviceD





GE 1/0/0



192.168.3.2/24





GigabitEthernet2/0/0



192.168.6.1/24





DeviceE









GE 1/0/1



192.168.4.2/24





GigabitEthernet1/0/2



192.168.5.2/24





GigabitEthernet1/0/3



192.168.6.2/24





GigabitEthernet2/0/0



192.168.7.1/24





DeviceF





GE 1/0/0



10.110.2.2/24





GigabitEthernet2/0/0



192.168.7.2/24














Precautions
When configuring multicast splitting, note the following precautions:


  • PIM-SM must be enabled before IGMP is enabled.
    

  • The five types of load splitting policies are mutually exclusive. Configure one of them as needed.
    







Configuration Roadmap
The configuration roadmap is as follows:


  1. Configure an IP address for each router interface.
    

  2. Configure IS-IS to implement communications among routers and ensure that route costs are equal.
    

  3. Enable multicast routing on all routers, enable PIM-SM on each interface, and set the loopback interface on Device A as a Rendezvous Point (RP).
    

  4. Configure stable-preferred multicast load splitting on Device E.
    

  5. Host A requires to receive data from some multicast groups for a long period. Configure the interfaces at the host side of Device F to statically join the multicast groups.
    







Data Preparation
To complete the configuration, you need the following data:


  • IP address of Source
    

  • IP address of each interface on the router
    

  • Addresses of the multicast groups that the interfaces at the host side of Device F statically join
    





Procedure


  1. Configure an IP address for each router interface. For configuration details, see Configuration Files in this section.
  2. Configure IS-IS to implement communications among routers and ensure that route costs are equal. For configuration details, see Configuration Files in this section.
  3. Enable the multicast function on all routers and enable PIM-SM on each interface.
    # Configure Device A. The configurations of Device B, Device C, Device D, Device E, and Device F are similar to those of Device A. For configuration details, see Configuration Files in this section.
    

    [~DeviceA] multicast routing-enable
[*DeviceA] interface gigabitethernet 1/0/0
[*DeviceA-GigabitEthernet1/0/0] pim sm
[*DeviceA-GigabitEthernet1/0/0] quit
[*DeviceA] interface GigabitEthernet 2/0/1
[*DeviceA-GigabitEthernet2/0/1] pim sm
[*DeviceA-GigabitEthernet2/0/1] quit
[*DeviceA] interface GigabitEthernet 2/0/2
[*DeviceA-GigabitEthernet2/0/2] pim sm
[*DeviceA-GigabitEthernet2/0/2] quit
[*DeviceA] interface GigabitEthernet 2/0/3
[*DeviceA-GigabitEthernet2/0/3] pim sm
[*DeviceA-GigabitEthernet2/0/3] quit
[*DeviceA] interface loopback 0
[*DeviceA-LoopBack0] pim sm
[*DeviceA-LoopBack0] commit
[~DeviceA-LoopBack0] quit
    

  4. Enable IGMP on interfaces that connect routers to hosts.
    # Enable IGMP on the interface connecting Device F to hosts.
    

    [~DeviceF] interface gigabitethernet 1/0/0
    

    [*DeviceF-GigabitEthernet1/0/0] igmp enable
    

    [*DeviceF-GigabitEthernet1/0/0] commit
    

    [~DeviceF-GigabitEthernet1/0/0] quit
    

  5. Configure an RP on Device A.
    # Configure loopback 0 on Device A as an RP.
    

    [~DeviceA] pim
    

    [*DeviceA-pim] c-bsr loopback 0
    

    [*DeviceA-pim] c-rp loopback 0
    

    [*DeviceA-pim] commit
    

    [~DeviceA-pim] quit
    

  6. Configure stable-preferred multicast load splitting on Device E.
    [~DeviceE] multicast load-splitting stable-preferred
    

    [*DeviceE] commit
    

  7. Configure interfaces connecting routers to hosts to statically join multicast groups.
    # Configure GE 1/0/0 on Device F to statically join the multicast groups in the range of 225.1.1.1 to 225.1.1.3.
    

    [~DeviceF] interface gigabitethernet 1/0/0
    

    [~DeviceF-GigabitEthernet1/0/0] igmp static-group 225.1.1.1
    

    [*DeviceF-GigabitEthernet1/0/0] igmp static-group 225.1.1.2
    

    [*DeviceF-GigabitEthernet1/0/0] igmp static-group 225.1.1.3
    

    [*DeviceF-GigabitEthernet1/0/0] commit
    

    [~DeviceF-GigabitEthernet1/0/0] quit
    

  8. Verify the configuration.
    # Have Source (10.110.1.1/24) send multicast data to multicast groups 225.1.1.1 to 225.1.1.3. Have Host A receive the multicast data sent from Source. On Device E, check information about PIM routing tables.
    

    <DeviceE> display pim routing-table brief
 VPN-Instance: public net
 Total 3 (*, G) entries; 3 (S, G) entries

 Entries                                Upstream interface       NDwnstrms
 (*, 225.1.1.1)                         GigabitEthernet1/0/3                 1
 (10.110.1.1, 225.1.1.1)                GigabitEthernet1/0/3                 1
 (*, 225.1.1.2)                         GigabitEthernet1/0/2                 1
 (10.110.1.1, 225.1.1.2)                GigabitEthernet1/0/2                 1
 (*, 225.1.1.3)                         GigabitEthernet1/0/1                 1
 (10.110.1.1, 225.1.1.3)                GigabitEthernet1/0/1                 1

    

    (*, G) and (S, G) entries are evenly distributed to the three equal-cost routes, with the upstream interfaces being GE 1/0/3, GE 1/0/2, and GE 1/0/1.
    

     
    The load splitting algorithm processes (*, G) and (S, G) entries separately but the process rules are the same.
    

    



Configuration Files
  • Device A configuration file
    

    #
sysname DeviceA
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0001.00
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 10.110.1.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/1
 undo shutdown
 ip address 192.168.1.1 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/2
 undo shutdown
 ip address 192.168.2.1 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/3
 undo shutdown
 ip address 192.168.3.1 255.255.255.0
 pim sm
 isis enable 1
#
interface Loopback0
 ip address 1.1.1.1 255.255.255.255
 pim sm
 isis enable 1
#
pim
 c-bsr LoopBack0
 c-rp LoopBack0
#
return

    

  • Device B configuration file
    

    #
sysname DeviceB
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0002.00
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 192.168.1.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 192.168.4.1 255.255.255.0
 pim sm
 isis enable 1
#
return

    

  • Device C configuration file
    

    #
sysname DeviceC
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0003.00
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 192.168.2.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 192.168.5.1 255.255.255.0
 pim sm
 isis enable 1
#
return

    

  • Device D configuration file
    

    #
sysname DeviceD
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0004.00
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 192.168.3.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 192.168.6.1 255.255.255.0
 pim sm
 isis enable 1
#
return

    

  • Device E configuration file
    

    #
sysname DeviceE
#
multicast routing-enable
multicast load-splitting stable-preferred
#
isis 1
 network-entity 10.0000.0000.0005.00
#
interface GigabitEthernet1/0/1
 undo shutdown
 ip address 192.168.4.2 255.255.255.0
 isis enable 1
 pim sm
#
interface GigabitEthernet1/0/2
 undo shutdown
 ip address 192.168.5.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet1/0/3
 undo shutdown
 ip address 192.168.6.2 255.255.255.0
 pim sm
 isis enable 1
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 192.168.7.1 255.255.255.0
 pim sm
 isis enable 1
#
return

    

  • Device F configuration file
    

    #
sysname DeviceF
#
multicast routing-enable
#
isis 1
 network-entity 10.0000.0000.0006.00
#
interface GigabitEthernet1/0/0
 undo shutdown
 ip address 10.110.2.2 255.255.255.0
 pim sm
 igmp enable
 isis enable 1
#
interface GigabitEthernet2/0/0
 undo shutdown
 ip address 192.168.7.2 255.255.255.0
 pim sm
 isis enable 1
#
return

    
















Translation
Favorite
Download
Update Date：2023-11-24
Document ID：EDOC1100278760
Views：228486
Downloads：1072
Average rating：5.0Points
Related Documents
Digital Signature File
digtal sigature tool