S1720, S2700, S5700, and S6720 Series Ethernet

Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

9 IPv4 Multicast Route Management

Configuration

About This Chapter

This chapter explains the multicast protocols that a switch can use to control
multicast routing and forwarding, by exchanging messages between the control
plane and the forwarding plane.

NOTE

In this chapter, the word "router" and the router icon used in figures refer to a conventional
router or Layer 3 switch.

9.1 Overview
9.2 Principles
9.3 Configuration Task Summary
9.4 Licensing Requirements and Limitations for IPv4 Multicast Route Management
9.5 Default Configuration
9.6 Configuring RPF Check Policies
9.7 Configuring a Multicast Boundary
9.8 Disabling Software Forwarding for Multicast Packets
9.9 Configuring Parameters for Controlling the MFIB
9.10 Maintaining Multicast Routes
9.11 Configuration Examples
9.12 Common Misconfigurations

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 545

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

9.1 Overview
Definition
Multicast route management refers to the control of multicast packet forwarding
by creating or changing multicast routes, as well as checking and maintaining
multicast forwarding paths.

Purpose
Multicast route management ensures that multicast packets are forwarded
efficiently through the correct paths.

In multicast routing and forwarding, each multicast routing protocol creates and
maintains its own routing table. The routing information from these tables is then
used to create a general multicast routing table. Multicast routers use this general
multicast routing table to determine optimal routes, according to multicast
routing and forwarding policies. The optimal route information is then delivered to
the multicast forwarding information base (MFIB), where multicast data
forwarding is controlled.

The MFIBs of network devices maintain a point-to-multipoint forwarding tree for

the entire network, with a multicast source as the root and group members as
leaves. Table 9-1 describes functions of multicast route management.

Table 9-1 Multicast route management functions

Function Description

Reverse Path Forwarding (RPF) check Ensures that multicast data is

forwarded through correct paths.

Multicast static route Changes or connects multicast RPF

routes.

Multicast load splitting Distributes multicast data to multiple

equal-cost routes to reduce the load on
individual paths.

Multicast ping Detects members of reserved groups

on the network.

Multicast traceroute Tracks the path to a multicast receiver

along a multicast forwarding tree.

9.2 Principles

9.2.1 Multicast Routing and Forwarding

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 546

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Devices performing different roles on a multicast network maintain different

multicast tables, including the Internet Group Management Protocol (IGMP)
group table, IGMP routing table, multicast protocol routing table, multicast
routing table, and multicast forwarding information base (MFIB). The following
sections describe the functions of these tables in multicast route management.

IGMP Group and Routing Tables

A multicast router creates an IGMP group entry when it receives an IGMP Join
message from a host. The router maintains group memberships in IGMP group
entries and instructs a multicast routing protocol, usually the Protocol
Independent Multicast (PIM) protocol, to create corresponding (*, G) entries. The
router maintains an IGMP group entry for each interface provided that the
interfaces have IGMP enabled and have received IGMP Join messages.

The following is an example of a group entry on an interface:

<HUAWEI> display igmp group
Interface group report information
Vlanif100(10.1.6.2):
Total 1 IGMP Group reported
Group Address Last Reporter Uptime Expires
225.1.1.2 10.1.6.10 00:02:04 00:01:17

Table 9-2 explains the fields of this IGMP group entry.

Table 9-2 Description of fields in the IGMP group entry

Field Description

Group Address Indicates the address of the group that an

interface has joined.

Last Reporter Indicates the IP address of the last user that

sent an IGMP Join message to the group.

Uptime Indicates the time elapsed since the group was

created.

Expires Indicates the time remaining before the group

will be aged out.

IGMP also maintains an IGMP routing table. An interface is included in an IGMP

routing entry only when PIM is not enabled on the interface. The IGMP routing
table increases the number of available outbound interfaces for multicast routing
entries. The following is an example of an IGMP routing entry:
<HUAWEI> display igmp routing-table
Routing table
Total 1 entries

00001. (*, 225.1.1.1)

List of 1 downstream interface
Vlanif100 (10.20.20.1)
Protocol: IGMP

Table 9-3 explains the fields in this IGMP routing entry.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 547

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Table 9-3 Description of fields in the IGMP routing entry

Field Description

00001. (*, 225.1.1.1) 00001 is the entry number, and (*, 225.1.1.1) is
an (*, G) entry, where * indicates any source
and G indicates a group address.

List of 1 downstream Indicates the downstream interfaces toward

interface receivers.

Protocol: IGMP Indicates the protocol that generates the

downstream interfaces.

According to the command output, the downstream interface is generated by

IGMP, indicating that PIM is not enabled on the interface. If PIM is enabled on an
interface, the routing entries of the interface are maintained by PIM.

Multicast Protocol Routing Table

Multicast routing protocols maintain their own routing tables to guide multicast
route management. PIM is the most widely used multicast routing protocol. The
following is an example of a PIM routing table:
<HUAWEI> display pim routing-table
VPN-Instance: public net
Total 0 (*, G) entry; 1 (S, G) entry

(192.168.0.12, 227.0.0.1)
RP: 10.2.2.2
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 02:54:43
Upstream interface: Vlanif 10
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlanif 20
Protocol: pim-sm, UpTime: 02:54:43, Expires: 00:02:47

Table 9-4 explains the fields in this PIM routing entry.

Table 9-4 Description of fields in the PIM routing entry

Field Description

(192.168.0.12, 227.0.0.1) (S, G) entry, where 192.168.0.12 is the source

address and 227.0.0.1 is the group address.

RP: 10.2.2.2 Indicates the rendezvous point (RP) IP address,

which is displayed only when the protocol type
is PIM-SM.

Protocol: pim-sm The first Protocol field in an entry indicates the

protocol that generates the entry, and the
second Protocol field indicates the protocol that
generates the downstream interfaces.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 548

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Field Description

Flag: SPT LOC ACT Indicates the flag of the PIM routing entry.

UpTime: 02:54:43 The first UpTime field in an entry indicates how

long the entry has existed, and the second
UpTime field indicates how long a downstream
interface has existed.

Upstream interface: Vlanif 10 Indicates the upstream interface pointing to the

multicast source.

Upstream neighbor: NULL NULL indicates that no upstream neighbor is

available.

RPF prime neighbor: NULL NULL indicates that no reverse path check
(RPF) neighbor is available.

Downstream interface(s) Indicates information about downstream

information: interfaces toward receivers.

Total number of Indicates the number of downstream interfaces.

downstreams: 1

Expires: 00:02:47 Indicates the aging time of a downstream

interface.

For details about PIM routing entries, see 5.2.1 Concepts in the PIM feature
description.

Multicast Routing Table

A multicast routing table is generated and maintained by the multicast route
management module of a router. If a router supports multiple multicast protocols,
its multicast routing table contains the optimal routes selected from the routing
tables of these protocols.

In unicast routing, routing tables of various routing protocols, such as Open

Shortest Path First (OSPF), Routing Information Protocol (RIP), and Border
Gateway Protocol (BGP), constitute an IP routing table. Similarly, routing tables of
different multicast protocols constitute a multicast table. Routers deliver multicast
routing entries to their MFIBs to guide multicast data forwarding. The following is
an example of a multicast routing table:
<HUAWEI> display multicast routing-table
Multicast routing table
Total 1 entry
00001. (192.168.0.2, 227.0.0.1)
Uptime: 00:00:28
Upstream Interface: Vlanif10
List of 2 downstream interfaces
1: Vlanif20
2: Vlanif30

Table 9-5 explains the fields in this multicast routing entry.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 549

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Table 9-5 Description of fields in the multicast routing entry

Field Description

00001. (192.168.0.2, 00001 is the entry number, and (FC00::2,

227.0.0.1) FFE3::1) is an (S, G) entry, where S indicates a
source address and G indicates a group address.

Uptime: 00:00:28 Indicates the time elapsed since the multicast

routing entry was updated.

Upstream Interface: Indicates the upstream interface pointing to the

VlanifIndicates the 10 multicast source.

List of 2 downstream Indicates the downstream interfaces toward

interfaces receivers.

MFIB
An MFIB is created and maintained by the route management module of a router
according to multicast routing information. Routers forward multicast data
according to their MFIBs. You can use the display multicast forwarding-table
command to view entries in an MFIB. An MFIB has the same functions as a unicast
FIB. The following is an example of an MFIB.
<HUAWEI> display multicast forwarding-table
Multicast Forwarding Table
Total 1 entry, 1 matched

00001. (10.10.10.2, 225.0.0.1)

MID: 10, Flags: ACT
Uptime: 00:08:32, Timeout in: 00:03:26
Incoming interface: Vlanif10
List of 1 outgoing interfaces:
1: Vlanif20
Activetime: 00:23:15
Matched 38264 packets(1071392 bytes), Wrong If 0 packets
Forwarded 38264 packets(1071392 bytes)

Table 9-6 explains the fields in this multicast forwarding entry.

Table 9-6 Description of fields in the multicast forwarding entry

Field Description

00001. (10.10.10.2, 225.0.0.1) 00001 is the entry number, and (10.10.10.2,

225.0.0.1) is an (S, G) entry, where S indicates a
source address and G indicates a group address.

MID: 10 Indicates the unique identifier of the multicast

forwarding entry in the MFIB. It is used to
rapidly search the MFIB.

Flags: ACT Indicates the flag of the multicast forwarding

entry.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 550

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Field Description

Uptime: 00:08:32 Indicates how long the multicast forwarding

entry has existed.

Timeout in: 00:03:26 Indicates how soon the multicast forwarding

entry will time out.

Incoming interface: Vlanif10 Indicates the inbound interface in the multicast

forwarding entry.

List of 1 outgoing interfaces: Lists the outbound interfaces toward receivers.

Activetime: 00:23:15 Indicates how long an outbound interface has

existed.

Activetime: 00:23:15 Indicates how long an outbound interface has

existed.

Matched 38264 Indicates the number of packets that match the

packets(1071392 bytes) multicast forwarding entry.

Wrong If 0 packets Indicates the number of packets that arrive on

the incorrect inbound interfaces.

Forwarded 38264 Indicates the number of forwarded packets.

packets(1071392 bytes)

The preceding information shows that multicast data is forwarded according to

the MFIB. Each multicast forwarding entry records statistics about packets that are
forwarded according to the entry.

9.2.2 RPF Check

RPF Check Basics

In unicast routing and forwarding, unicast packets are transmitted along a point-
to-point path. Routers only need to know the destination address of a packet to
find the outbound interface. In multicast routing and forwarding, however, routers
cannot know the location of a specific receiver because the destination address of
a multicast packet identifies a group of receivers. Because routers can find out the
source of a multicast packet based on the source address, they can check the
source addresses of multicast packets to ensure correct forwarding paths. The
process of checking the forwarding path based on the source address is a reverse
path forwarding (RPF) check.
When a router receives a multicast packet, it searches the unicast routing table for
the route to the source address of the packet. After finding the route, the router
checks whether the outbound interface for the route is the same as the inbound
interface of the multicast packet. If they are the same, the router considers that
the multicast packet has been received from a correct interface. This ensures
correct forwarding paths for multicast packets.
The correct interface is called an RPF interface.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 551

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

RPF Check Process

In addition to unicast routes, RPF checks can also be performed using
Multiprotocol Border Gateway Protocol (MBGP) routes and static multicast routes.
If a router has all these routes, it performs an RPF check on a multicast packet in
the following way:

1. The router selects an optimal route from each of the unicast routing table,
MBGP routing table, and multicast static routing table according to the source
address of the multicast packet. The outbound interfaces of the unicast and
MBGP routes are RPF interfaces, and the next hops of those routes are the
RPF neighbors. The RPF interface and RPF neighbor of the multicast static
route have been specified when the route is manually configured.
2. The router selects one of the three routes as the RPF route according to the
following rules:
– If the longest match rule is configured, the router selects the route with
the longest mask. If more than one route has the longest mask, the
router selects the one with the highest preference. If more than one route
has the highest preference, the router uses the following order of priority:
multicast static route, MBGP route, and unicast route.
– If the longest match rule is not configured, the router selects the route
with the highest preference. If more than one route has the highest
preference, the router uses the following order of priority: multicast static
route, MBGP route, and unicast route.
3. The router compares the inbound interface of the packet with the RPF
interface of the selected RPF route. If the inbound interface is the same as the
RPF interface, the router considers that the packet has arrived on the correct
path from the source and forwards the packet downstream. If the inbound
interface is different from the RPF interface, the packet fails the RPF check.
The router considers that the packet is received from an incorrect interface
and drops the packet.

In Figure 9-1, a multicast stream sent from source 10.10.2.2 arrives at interface
Int1 of the router. The router checks the routing table and finds that the multicast
stream from this source should arrive at interface Int0. The RPF check fails, and
the router drops the multicast stream.

Figure 9-1 RPF check fails

IP Routing Table
Network Interface
Multicast stream
10.10.0.0/16 Int0 from source
192.168.1.0/24 Int1 10.10.2.2
192.168.2.0/24 Int2

Int1
Int0 Int2

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 552

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

In Figure 9-2, a multicast stream sent from the source 10.10.2.2 arrives at
interface Int0 of the router. The router checks the routing table and finds that the
RPF interface is also Int0. The RPF check succeeds, and the multicast stream is
correctly forwarded.

Figure 9-2 RPF check succeeds

IP Routing Table
Network Interface
10.10.0.0/16 Int0
192.168.1.0/24 Int1
192.168.2.0/24 Int2

Multicast stream Int1

from source Int0 Int2
10.10.2.2

RPF Check in Multicast Data Forwarding

Multicast routing protocols determine upstream and downstream neighbors and
create multicast routing entries based on unicast routes, MBGP routes, and
multicast static routes. The RPF check mechanism enables multicast data streams
to be transmitted along the multicast distribution tree and prevents loops on
forwarding paths.

If a router searches the unicast routing table to perform an RPF check on every
multicast data packet received, many system resources are consumed. To save
system resources, a router first searches for the matching (S, G) entry after
receiving a data packet sent from a source to a group.

● If no matching (S, G) entry is found, the router performs an RPF check to find
the RPF interface for the packet. The router then creates a multicast route
with the RPF interface as the upstream interface and delivers the route to the
multicast forwarding information base (MFIB). If the RPF check succeeds, the
inbound interface of the packet is the RPF interface, and the router forwards
the packet to all the downstream interfaces in the forwarding entry. If the RPF
check fails, the packet has been forwarded along an incorrect path, so the
router drops the packet.
● If a matching (S, G) entry is found and the inbound interface of the packet is
the same as the upstream interface in the entry, the router replicates the
packet to all downstream interfaces specified in the entry.
● If a matching (S, G) entry is found but the inbound interface of the packet is
different from the upstream interface in the entry, the router performs an RPF
check on the packet. Based on the RPF check result, the router processes the
packet as follows:
– If the RPF interface is the same as the upstream interface in the entry,
the (S, G) entry is correct and the packet has been forwarded along an
incorrect path. The router drops the packet.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 553

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

– If the RPF interface is different from the upstream interface in the entry,
the (S, G) entry is outdated, and the router changes the upstream
interface in the entry to be the same as the RPF interface. The router
then compares the RPF interface with the inbound interface of the
packet. If the inbound interface is the RPF interface, the router replicates
the packet to all downstream interfaces specified in the (S, G) entry. If
the inbound interface is different from the RPF interface, the router drops
the packet.

9.2.3 Multicast Static Route

RPF checks can be performed using multicast static routes. Multicast static routes
can be used to change and connect RPF routes.

Changing RPF Routes

You can change RPF routes on a network by configuring multicast static routes.
Multicast data can then be transmitted along a different path from unicast data.

In Figure 9-3, RouterA is the RPF neighbor of RouterC towards the multicast
source (Source). Multicast packets sent from Source are transmitted along the
path Source → RouterA → RouterC. If you configure a multicast static route on
RouterC and specify RouterB as the RPF neighbor, the transmission path of
multicast packets sent from Source changes to Source → RouterA → RouterB →
RouterC. In this way, the multicast path diverges from the unicast path.

Figure 9-3 Configuring a multicast static route to change the RPF route
Multicast Routing Table on RouterC
Source/Mask Interface RPF Neighbor/Mask
192.168.1.1/24 Int0 10.2.2.1/24

Receiver
RouterB

Int0
10.2.2.1/24
Source Int0 Receiver
10.2.2.2/24

Int1
192.168.1.1/24 RouterA
RouterC

Multicast stream
Multicast static route

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 554

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Connecting RPF Routes

When unicast routes on a multicast network are incomplete, multicast packets
cannot be forwarded due to a lack of an RPF route. In this case, multicast static
routes can be configured on the network to generate new RPF routes. Multicast
routers then create new multicast forwarding entries to guide multicast data
forwarding.
In Figure 9-4, Domain1 and Domain2 are routing domains (RIP and OSPF
domains for example). The domains have no unicast route to each other, so
receivers in Domain2 cannot receive data from the multicast source in Domain1.
To enable receivers to receive data from the multicast source, configure multicast
static routes on RouterC and RouterD in Domain2. On RouterC, specify RouterB as
the RPF neighbor. On RouterD, specify RouterC as the RPF neighbor.

Figure 9-4 Configuring multicast static routes to connect RPF routes

Multicast Routing Table on RouterC
Source/Mask Interface RPF Neighbor/Mask
192.168.1.1/24 Int1 10.3.3.1/24

Multicast Routing Table On RouterD Domain2

Source/Mask Interface RPF Neighbor/Mask
RouterD Receiver
192.168.1.1/24 Int0 10.2.2.2/24

Int0
10.2.2.1/24
Domain1
Source Int0 Receiver
10.3.3.1/24 10.3.3.2/24 10.2.2.2/24
Int0 Int1

192.168.1.1/24 RouterA RouterB RouterC

Multicast stream
Multicast static route

NOTE

Multicast static routes are local to the router where they are configured and are not
advertised or redistributed to any other router.

9.2.4 Multicast Load Splitting

Load splitting is different from load balancing. Load splitting provides a way to
distribute data streams destined for the same destination to multiple equal-cost
paths, which may not result in a balanced traffic load on the paths. Load
balancing is a special form of load splitting and distributes even data traffic loads
on multiple equal-cost paths.

Implementation
By default, a router selects an RPF route from multiple equal-cost optimal routes
to forward multicast packets according to the following RPF check policy:

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 555

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

● If the equal-cost routes are in the same routing table, for example, a unicast
routing table, multicast static routing table, or MBGP routing table, the router
selects the route with the largest next-hop address as the RPF route.
● If the equal-cost routes are in different routing tables, the router selects the
route with the highest preference. If multiple routes have the highest
preference, the router selects the route with the longest mask length. If
multiple routes have the longest mask length, the router uses an algorithm to
select a route as the RPF route.
In this default configuration, the router selects only one route as the RPF route,
regardless of which condition is met.
Multicast load splitting enables a router to distribute multicast traffic to multiple
equal-cost routes, instead of selecting only one route based on the RPF check
policy.
As shown in Figure 9-5, the multicast source (Source) sends multicast streams to
group G. RouterA and RouterD run an Interior Gateway Protocol (IGP), OSPF for
example, to implement IP interworking. Two equal-cost paths are available:
RouterA → RouterB → RouterD and RouterA → RouterC → RouterD. Based on the
default RPF check policy, multicast streams are forwarded through interface Int0
of RouterA because Int0 has a larger IP address than Int1. After multicast load
splitting is configured on RouterA, RouterA does not select forwarding paths by
comparing the next-hop IP addresses. Instead, multicast streams are forwarded
along both of the two equal-cost paths.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 556

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Figure 9-5 Multicast forwarding without and with multicast load splitting

Multicast network without load splitting

RouterB

Source Receiver
Int0 10.1.2.1
RouterD
Int1 10.1.1.1
RouterA

RouterC

Multicast network with load splitting

RouterB

Source Receiver
Int0 10.1.2.1
RouterD
Int1 10.1.1.1
RouterA

RouterC
Multicast Packets

Multicast Load Splitting Modes

Various methods are available to split (*, G) and (S, G) data streams in different
scenarios.
● Load splitting by group address
In Figure 9-6, the source sends data streams to different multicast groups (G1
to G10). Router7, Router6, and Router5 each have two equal-cost paths to
the source. These routers use route selection algorithms to select an optimal
path for data sent to each group. In this load splitting mode, streams
transmitted on different paths are sent to different groups.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 557

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Figure 9-6 Load splitting by group address

Router1

Router5 Receiver

Router2
(S, G1)
(S, G2) Source
Router7
.
. Router3
.
(S, G10) Router6
Router4

● Load splitting by source address

In Figure 9-7, different sources (S1 to S10) send data streams to the same
group. Router7, Router6, and Router5 each have two equal-cost paths to the
sources. These routers use route selection algorithms to select an optimal
path for data from each source. In this load splitting mode, streams
transmitted on different paths are sent from different sources.

Figure 9-7 Load splitting by source address

Router1
Source Router5 Receiver
(S1, G) Router2

Router7
.
. Router3
.
Router6
Router4
(S10, G)

Source10

● Load splitting by source address and group address

In Figure 9-8, different sources (S1 to S10) send data streams to different
groups (G1 to G10). Router7, Router6, and Router5 each have two equal-cost
paths to the sources. These routers use route selection algorithms to select an
optimal path for each (S, G) stream. In this load splitting mode, streams
transmitted on different paths have different source and group addresses.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 558

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Figure 9-8 Load splitting by source address and group address

Router1
Source Router5 Receiver
(S1, G) Router2

Router7
.
. Router3
.
Router6
Router4
(S10, G10)

Source10

● Other load splitting methods

Figure 9-9 Load splitting network

Router1
Source Router5 Receiver

Router2

Router7
Router3

Router6
Router4

The following load balancing methods can also be used on the network
shown in Figure 9-9:
– Stable-preferred load splitting
When route flapping occurs on a multicast network, frequent changes of
multicast traffic distribution on equal-cost paths will worsen route
flapping. Stable-preferred load splitting can be configured to solve this
problem. When route flapping occurs, a router with stable-preferred load
splitting adjusts traffic distribution on equal-cost paths until route
flapping ends. When the network topology becomes stable, the router
evenly distributes (S, G) streams from the same source to equal-cost
paths.
– Balance-preferred load splitting
Balance-preferred load splitting enables routers to immediately adjust
traffic distribution among equal-cost paths when route flapping occurs
on a multicast network. When the network topology becomes stable, the
router evenly distributes (S, G) streams from the same source to equal-
cost paths.
– Unbalanced load splitting

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 559

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Unbalanced load splitting is a supplement to stable-preferred and

balance-preferred load splitting and does not change their behavior. In
unbalanced load splitting mode, (S, G) streams are distributed to equal-
cost paths in proportion to the weights of the paths. As transmission
paths on a network have different capabilities, load on some paths may
need to be adjusted manually. In this case, load splitting weights can be
configured on upstream interfaces of a router to implement unbalanced
load splitting. A larger weight allows the corresponding path to transmit
more (*, G) and (S, G) streams.

9.2.5 Multicast Ping and Multicast Tracert

Introduction to Multicast Ping and Multicast Tracert

As the Internet develops, more and more data, voice, and video service
information is exchanged across networks, and multicast services are rapidly
developing to meet this need. Multicast ping (MPing) and multicast tracert
(MTrace) have been developed to provide users with the multicast service
detection and fault diagnosis functions. They are described as follows:

● MPing: a tool for detecting multicast services. MPing sends Internet Control
Message Protocol (ICMP) Echo Request messages to trigger the setup of the
multicast forwarding tree and detect members of reserved multicast groups
on the network.
NOTE

Reserved multicast group addresses range from 224.0.0.0 to 224.0.0.255. For example, 224.0.0.5
is reserved for the OSPF multicast group, and 224.0.0.13 is reserved for the PIM multicast group.
● MTrace: a tool for tracing multicast forwarding paths. MTrace traces the path
from a receiver to a multicast source along the multicast forwarding tree.

MPing
MPing uses standard ICMP messages to detect the connectivity of a multicast
path. MPing constructs an ICMP Echo Request message with the encapsulated
destination address being a multicast address (either a multicast address for the
reserved multicast group or a common multicast group address).

● If the encapsulated destination address of an ICMP Echo Request message is

the address of a reserved multicast group, the querier must specify the
outbound interface of the message. Upon receiving such an ICMP Echo
Request message, the member of the reserved multicast group responds with
an ICMP Echo Reply packet. Therefore, you can ping the address of the
reserved multicast group to detect the members in the reserved multicast
group.
● If the encapsulated destination address of an ICMP Echo Request message is
the address of a common multicast group, the querier cannot specify the
outbound interface of the message. The ICMP Echo Request message is
forwarded on the multicast network, which triggers the setup of multicast
routing entries. The querier collects statistics on ICMP Echo Reply packets
received from the destination host and calculates the TTL and response time
from the multicast source to a group member.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 560

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

MTrace
MTrace complies with the protocol draft draft-fenner-traceroute-ipm-01.txt
defined by the Internet Engineering Task Force (IETF).
This draft describes a mechanism to trace the path along which multicast data is
forwarded from the multicast source to the designated receiver. Figure 9-10
shows message exchanges in an MTrace process.

Figure 9-10 MTrace message exchange

Source First-hop route

Receiver

Querier Last-hop route

IGMP Tracert Query

IGMP Tracert Repuest
IGMP Tracert Response

MTrace takes effect only on a network where a multicast protocol (such as PIM-
SM) is enabled and the multicast distribution tree is established. MTrace detects
the multicast forwarding path by sending query messages. Query messages
include IGMP Tracert Query messages, IGMP Tracert Request messages, and IGMP
Tracert Response messages.
MTrace is implemented as follows:
1. The querier sends an IGMP Tracert Query message to the last-hop device
connected to the destination host.
2. After receiving the IGMP Tracert Query message, the last-hop device adds a
response data block containing information about the interface that received
the IGMP Tracert Query message, and sends an IGMP Tracert Request
message to the previous-hop device.
3. Devices of each hop add a response data block to the IGMP Tracert Request
message and send the message upstream.
4. When the first-hop device connected to the multicast source receives the
IGMP Tracert Request message, it adds a response data block and sends the
IGMP Tracert Response message to the querier.
5. The querier analyzes the IGMP Tracert Response message and obtains
information about the forwarding path from the multicast source to the
destination host.
6. If the IGMP Tracert Request message cannot reach the first-hop device due to
an error, the IGMP Tracert Response message is directly sent to the querier.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 561

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

The querier then analyzes the data block information for locating and
monitoring the faulty node.

9.3 Configuration Task Summary

Table 9-7 lists IPv4 multicast route management configuration tasks.

Table 9-7 IPv4 multicast route management configuration tasks

Task Description

9.6 Configuring RPF Check Policies Applies different route selection

policies to adapt to different multicast
service scenarios.

9.7 Configuring a Multicast Restricts the scope of multicast

Boundary forwarding.

9.9 Configuring Parameters for Allows you to adjust the number of

Controlling the MFIB multicast forwarding entries and the
number of downstream nodes.

9.10.1 Using MPing to Check Triggers creation of a multicast tree

Multicast Service Performance and detects members of reserved
multicast groups on the network.

9.10.2 Using Tracert to Check Tracks the path to a multicast receiver

Multicast Service Performance along a multicast forwarding tree.

9.4 Licensing Requirements and Limitations for IPv4

Multicast Route Management

Involved Network Elements

An IPv4 multicast network consists of the following network elements:
● Multicast source
A device that sends multicast data to receiver hosts. For example, a video
server is a multicast source.
● IPv4 Protocol Independent Multicast (PIM) device
A device that uses the IPv4 PIM protocol to generate and maintain multicast
routing entries and forwards multicast data based on multicast routing
entries. On an IPv4 multicast network, all Layer 3 devices must run IPv4 PIM;
otherwise, multicast forwarding paths cannot be established.
● Multicast Source Discovery Protocol (MSDP) device
A device that forwards multicast data from one PIM network to another. For
example, if multicast data needs to be transmitted between two autonomous
systems (ASs), the devices at the border of the ASs must run the MSDP
protocol.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 562

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

● Multicast VPN device

Multicast VPN enables multicast data of a private network to be transmitted
over a public network. Multicast VPN devices are used on VPN networks. For
example, if two sites of a VPN network need to exchange multicast data
across a public network, multicast VPN needs to be configured on the PE
devices.
● IGMP querier
A device that exchanges IGMP messages with receiver hosts to create and
maintain group memberships. On a multicast network, Layer 3 devices
connected to network segments of receivers must run the IGMP protocol or
be configured with static IGMP groups. Otherwise, upstream PIM devices
cannot know the multicast groups that users want to join, and therefore
cannot establish multicast forwarding paths.
● IGMP snooping device
A device that listens on IGMP messages exchanged between upstream Layer 3
multicast devices and receiver hosts to create and maintain Layer 2 multicast
forwarding entries, which are used for accurate multicast data forwarding on
a Layer 2 network. To prevent broadcasting of multicast packets on a Layer 2
network and conserve network bandwidth, it is recommended that you
configure IGMP snooping on Layer 2 devices.
● Receiver
A multicast user that receives multicast data. A receiver can be a PC, a set top
box, or any device with multicast client installed.

Generally, IPv4 multicast route management is configured on a device running

IPv4 PIM to monitor and maintain multicast forwarding paths.

Licensing Requirements
IPv4 multicast route management is a basic feature of a switch and is not under
license control.

Version Requirements

Table 9-8 Products and versions supporting IPv4 multicast route management

Product Product Software Version

Model

S1700 S1720GFR, Not supported

S1720GW-
E, and
S1720GWR
-E

S1720GW, Not supported

S1720GWR

S1720X, Not supported

S1720X-E

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 563

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Product Product Software Version

Model

Other Models that cannot be configured using commands.

S1700 For details about features and versions, see S1700
models Documentation Bookshelf.

S2700 S2700SI, Not supported

S2710SI,
S2700EI,
S2720EI,
and
S2750EI

S3700 S3700SI Not supported

S3700EI V100R005C01, V100R006(C00&C01&C03&C05)

S3700HI V100R006C01, V200R001C00

S5700 S5700S-LI, Not supported

S5700LI,
S5710-C-LI,
S5710-X-LI,
and
S5700SI

S5720LI V200R011C10
and
S5720S-LI

S5720S-SI V200R008C00, V200R009C00, V200R010C00,

and V200R011C00, V200R011C10
S5720SI

S5730SI V200R011C10

S5730S-EI V200R011C10

S5700EI V100R005C01, V100R006(C00&C01),

V200R001(C00&C01), V200R002C00, V200R003C00,
V200R005(C00&C01&C02&C03)

S5710EI V200R002C00, V200R003C00, and

V200R005(C00&C02)

S5700HI V100R006C01, V200R001(C00&C01), V200R002C00,

V200R003C00, V200R005(C00SPC500&C01&C02)

S5710HI V200R003C00, V200R005(C00&C02&C03)

S5720EI V200R007C00, V200R008C00, V200R009C00,

V200R010C00, V200R011C00, V200R011C10

S5720HI V200R006C00, V200R007(C00&C10), V200R008C00,

V200R009C00, V200R010C00, V200R011C00,
V200R011C10

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 564

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Product Product Software Version

Model

S6700 S6700EI V100R006C00, V200R001(C00&C01), V200R002C00,

V200R003C00, V200R005(C00&C01&C02)

S6720EI V200R008C00, V200R009C00, V200R010C00,

V200R011C00, V200R011C10

S6720S-EI V200R009C00, V200R010C00, V200R011C00,

V200R011C10

S6720LI V200R011C10
and
S6720S-LI

S6720SI V200R011C00, V200R011C10

and
S6720S-SI

NOTE
To know details about software mappings, see Hardware Query Tool.

Feature Limitations
● IPv4 multicast route management-capable switches support IPv4 multicast
route management configuration on physical interfaces that have been
switched to Layer 3 mode using the undo portswitch command since
V200R005. This configuration, however, is not supported on the S6720SI,
S6720S-SI, S6720LI, S6720S-LI, S5720LI, S5720S-LI, S5720SI, S5730SI, S5730S-
EI, and S5720S-SI.
● Only the following products and versions support configuration of IPv4
multicast route management in a VPN instance:
– V200R005C01: S6700EI and S5700HI
– V200R005C02: S6700EI, S5700HI, and S5710HI
– V200R005C03: S5710HI
– V200R010 and later versions: S5720EI, S5720HI, S6720EI, and S6720S-EI
● When configuring IPv4 multicast route management in a VPN instance,
ensure that the VPN instance is not bound to a physical interface that has
been switched to Layer 3 mode using the undo portswitch command.

9.5 Default Configuration

Table 9-9 lists the default configuration of multicast route management.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 565

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Table 9-9 Default configuration of IPv4 multicast route management

Parameter Default Setting

Longest match rule for Not configured. The reverse path forwarding (RPF)
multicast route route is selected based on router preference during an
selection RPF check.

Multicast load splitting Disabled. Only one route is selected to forward

multicast packets.

Multicast boundary Not configured.

9.6 Configuring RPF Check Policies

Pre-configuration Tasks
Before configuring an RPF check policy, complete the following tasks:
● Configure a unicast routing protocol to ensure normal unicast routing on the
network.
● Run the multicast routing-enable command in the system view to enable
Layer 3 multicast routing globally.

Configuration Process
The following configuration tasks can be performed in any sequence.

9.6.1 Configuring a Multicast Static Route

Context
A multicast static route specifies a reverse path forwarding (RPF) interface or RPF
neighbor for multicast packets from a specified multicast source. Configure a
multicast static route to:
● Change an RPF route.
If you want an interface to receive multicast data packets from a specified
multicast source but the interface is not the RPF interface for that multicast
source, configure a multicast static route to specify this interface as the RPF
interface for the multicast source. When the switch receives multicast data
packets from the multicast source, it performs an RPF check using the
configured RPF route. Packets sent from the source to the switch through
other interfaces fail the RPF check.
● Connect RPF routes.
If the unicast route on a network segment is incomplete, multicast packets
cannot be forwarded because there is no RPF route. For example, when two
adjacent devices run different routing protocols but the routing protocols do
not import routes from each other, packets cannot be forwarded between the
two devices. In this case, you can configure RPF static routes on the devices.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 566

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

The devices can perform an RPF check using the specified RPF interfaces so
that multicast packets can be forwarded successfully.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
ip rpf-route-static source-address { mask | mask-length } [ isis process-id | ospf process-id | rip process-id |
bgp | static ] [ route-policy route-policy-name ] { gateway-address | interface-type interface-number }
[ preference preference ] [ order order-number ]

A multicast static route is configured.

If the next-hop interface of a multicast static route is a P2P interface, select the
interface-type interface-number parameter from gateway-address | interface-type
interface-number to specify the outbound interface. If the next-hop interface is a
P2MP interface, select the gateway-address parameter to specify the next-hop IP
address.

----End

9.6.2 Configuring Longest Match for Multicast Route Selection

Context
By default, a switch selects reverse path forwarding (RPF) routes based on route
preference. If you change the RPF check policy to longest match, the switch
compares mask lengths of routes to select an RPF route, and compares route
preference when multiple routes have the longest mask length.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
multicast longest-match

The longest match rule is applied for route selection.

----End

9.6.3 Configuring Multicast Load Splitting

Context
By default, if there are multiple equal-cost routes to a multicast source, a switch
applies the following route selection rules during a reverse path forwarding (RPF)
check:

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 567

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

● If the equal-cost routes are in the same routing table, for example, a unicast
routing table, multicast static routing table, or Multiprotocol Border Gateway
Protocol (MBGP) routing table, the switch selects the route with the largest
next-hop address as the RPF route.
● If the equal-cost routes are in different routing tables, the switch selects the
route with the highest preference. If multiple routes have the highest
preference, the switch selects the route with the longest mask length. If
multiple routes have the longest preference, the switch uses an algorithm to
select an RPF route.
In this default configuration, the switch selects only one route as the RPF route,
regardless of which condition is met. Multicast load splitting enables the switch to
distribute multicast data among multiple equal-cost paths based on a specific load
splitting policy. This function improves quality of multicast forwarding.

NOTE

● It is recommended that you use a fixed load splitting policy that best suits your network.
The stable-preferred or balance-preferred load splitting policy is recommended.
● The load splitting timer and load splitting weights can be configured when the stable-
preferred or balance-preferred load splitting policy is used.
● If Protocol Independent Multicast Dense Mode (PIM-DM) is enabled on the current
switch, the stable-preferred or balance-preferred policy cannot be used.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
multicast load-splitting { balance-preferred | stable-preferred | source | group | source-group }

Multicast load splitting is configured.

The keywords in the command specify different multicast load splitting policies:
● balance-preferred: ensures even load distribution among forwarding paths.
Use this policy in scenarios where users frequently join and leave multicast
groups. It enables traffic distribution to automatically adapt to frequent
changes in group memberships.
If this load splitting policy is used, the switch automatically adjusts traffic on
equal-cost routes when equal-cost routes are added or deleted, multicast
routing entries are deleted, or load splitting weights on interfaces are
changed.
● stable-preferred: ensures stable multicast forwarding. Use this policy on a
network with stable multicast services.
If this load splitting policy is used, the switch automatically adjusts traffic on
equal-cost routes when equal-cost routes are added or deleted. However,
when multicast routing entries are deleted or load splitting weights on
interfaces are changed, the switch does not automatically adjust the traffic on
the equal-cost routes.
● group: load splitting by group address. Use this policy in scenarios where one
multicast source sends data to multiple groups.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 568

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

● source: load splitting by source address. Use this policy in scenarios where
one group receives data from multiple sources.
● source-group: load splitting by source address and group address. Use this
policy in scenarios where multiple sources send data to multiple groups.
Step 3 (Optional) Run:
multicast load-splitting-timer interval

The multicast load splitting timer is set.

By default, the value of a load splitting timer is 1800 seconds.
Step 4 (Optional) Set the load splitting weight of an interface.
1. Run:
interface interface-type interface-number

The interface view is displayed.

2. (Optional) On an Ethernet interface, run undo portswitch
The interface is switched to Layer 3 mode.
By default, an Ethernet interface works in Layer 2 mode.
NOTE

Only the S5720HI, S5720EI, S6720EI, and S6720S-EI support switching between Layer
2 and Layer 3 modes.
3. Run:
multicast load-splitting weight weight-value

Load splitting weight is set for the interface.

By default, the multicast load splitting weight of an interface is 1.

----End

9.6.4 Checking the Configuration

Context
After changing the reverse path forwarding (RPF) check policy, check the multicast
static routing table, multicast routing table, and RPF routing table to verify that
the multicast network can operate normally.

Procedure
● Run the display multicast routing-table [ vpn-instance vpn-instance-
name ] static [ config ] [ source-address { mask | mask-length } ] command
to check the multicast static routing table.
● Run either of the following commands to check the multicast routing table:
– display multicast [ vpn-instance vpn-instance-name | all-instance ]
routing-table [ group-address [ mask { group-mask | group-mask-
length } ] | source-address [ mask { source-mask | source-mask-length } ]
| incoming-interface { interface-type interface-number | register } |
outgoing-interface { include | exclude | match } { interface-type

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 569

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

interface-number | register | none } ] * [ outgoing-interface-number

[ number ] ]
● Run the display multicast [ vpn-instance vpn-instance-name | all-instance ]
rpf-info source-address [ group-address ] [ rpt | spt ] command to check the
RPF route to a specified multicast source.
----End

9.7 Configuring a Multicast Boundary

Pre-configuration Tasks
Before configuring the multicast boundary, complete the following tasks:
● Configure a unicast routing protocol to ensure normal unicast routing on the
network.
● Run the multicast routing-enable command in the system view to enable
Layer 3 multicast routing globally.

Context
To restrict forwarding of multicast packets sent to a multicast group within a
range, configure a multicast boundary on interfaces. Once the multicast boundary
is configured on an interface, multicast packets sent to the group cannot be
forwarded through the interface.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
interface interface-type interface-number

The interface view is displayed.

Step 3 (Optional) On an Ethernet interface, run undo portswitch
The interface is switched to Layer 3 mode.
By default, an Ethernet interface works in Layer 2 mode.
NOTE

Only the S5720HI, S5720EI, S6720EI, and S6720S-EI support switching between Layer 2 and
Layer 3 modes.

Step 4 Run:
multicast boundary group-address { mask | mask-length }

A multicast boundary is configured on the interface.

----End

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 570

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Checking the Configuration

After configuring a multicast boundary on interfaces, check the multicast routing
table and information about the multicast boundary on the interfaces to verify
that the multicast network can operate normally.

● Run either of the following commands to check the multicast routing table:
– display multicast routing-table [ group-address [ mask { group-mask |
group-mask-length } ] | source-address [ mask { source-mask | source-
mask-length } ] | incoming-interface { interface-type interface-number |
register } | outgoing-interface { include | exclude | match } { interface-
type interface-number | register | none } ] * [ outgoing-interface-
number [ number ] ]
● Run the display multicast boundary [ group-address [ mask | mask-
length ] ] [ interface interface-type interface-number ] command to check
information about the multicast boundary configured on an interface.

9.8 Disabling Software Forwarding for Multicast

Packets

Pre-configuration Tasks
Before disabling software forwarding for multicast packets, complete the following
tasks:

● Configure a unicast routing protocol to ensure normal unicast routing on the

network.
● Run the multicast routing-enable command in the system view to enable
Layer 3 multicast routing globally.

Context
In most cases, a switch performs software forwarding before hardware forwarding
entries are generated. After hardware forwarding entries are generated, the switch
performs hardware forwarding. Software forwarding for multicast packets must be
disabled on the switch to prevent packet loss and mis-sequencing caused by the
low forwarding speed and first packet cache mechanism of software forwarding.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
multicast cpu-forward disable

Soft forwarding is disabled for multicast packets.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 571

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

By default, software forwarding for multicast packets is enabled.

----End

9.9 Configuring Parameters for Controlling the MFIB

Context
The multicast forwarding information base (MFIB) of a device controls forwarding
of multicast packets. You can control forwarding of multicast packets by
configuring the parameters for controlling the MFIB.

Pre-configuration Tasks
Before configuring the parameters for controlling the multicast forwarding table,
complete the following tasks:
● Configure a unicast routing protocol to ensure normal unicast routing on the
network.
● Run the multicast routing-enable command in the system view to enable
Layer 3 multicast routing globally.

Configuration Process
The following configuration tasks can be performed in any sequence.

9.9.1 Restricting the Number of Multicast Forwarding Entries

Context
Excessive multicast forwarding entries will exhaust the memory of the switch. To
prevent this problem, set a limit on the number of entries in the MFIB.

Default Configuration
By default, a maximum of 1024 entries are allowed in the MFIB of the S5720SI
and S5720S-SI and a maximum of 4096 entries are allowed in the MFIB of the
S5720EI, S5720HI, S6720EI, and S6720S-EI.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
multicast forwarding-table route-limit limit

A limit is configured for the number of entries in the MFIB.

----End

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 572

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

9.9.2 Configuring the Maximum Number of Downstream

Nodes in a Multicast Forwarding Entry

Context
When the switch receives a multicast packet, it copies the packet for each
downstream node in the matching multicast forwarding entry. If there are too
many downstream nodes, the switch is overloaded. To reduce the load on the
switch, limit the number of downstream nodes in each multicast forwarding entry.

Default Configuration
By default, a multicast forwarding entry can contain a maximum of 128
downstream nodes.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
multicast forwarding-table downstream-limit limit

The maximum number of downstream nodes in a multicast forwarding entry is

configured.

----End

9.9.3 Configuring the Multicast Hash Algorithm

Context
To improve multicast forwarding performance, the switch uses a hash algorithm to
learn multicast addresses. When a large number of multicast hash collisions occur,
the switch will fail to learn some multicast addresses. If this occurs, you can
change the multicast hash algorithm to reduce hash collisions.

NOTICE

MAC addresses are randomly distributed on a network, so the best hash algorithm
cannot be determined. The default hash algorithm is the best algorithm in most
cases, so changing the hash algorithm is not recommended.
After changing the hash algorithm, restart the switch for the configuration to take
effect.

Product Support

S1720GFR Not supported

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 573

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Product Support

S2720, S2750 Not supported

S5700 Supported only by the S5720EI

S6720EI, S6720S-EI Supported

Default Configuration
The default multicast hash algorithm is crc-32-lower.

Procedure
Step 1 Run:
system-view

The system view is displayed.

Step 2 Run:
set multicast-hash-mode { crc-32-upper | crc-32-lower | lsb | crc-16-upper | crc-16-lower }

The multicast hash algorithm is specified.

----End

9.9.4 Checking the Configuration

Context
After configuring parameters for controlling the MFIB, check the MFIB to verify
that the multicast network is operating properly.

Procedure
● Run the display multicast forwarding-table [ group-address [ mask
{ group-mask | group-mask-length } ] | source-address [ mask { source-mask |
source-mask-length } ] | incoming-interface { interface-type interface-
number | register } | outgoing-interface { include | exclude | match }
{ interface-type interface-number | register | none } | { statistics | verbose } ]
* command to check the multicast forwarding table.

----End

9.10 Maintaining Multicast Routes

Context
You can check multicast service performance using multicast ping (MPing) and
multicast traceroute (MTrace) functions, delete multicast forwarding and routing
entries, and monitor multicast routing and forwarding.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 574

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

9.10.1 Using MPing to Check Multicast Service Performance

Context
Multicast devices need to support not only multicast forwarding and multicast
routing protocols but also multicast diagnostic tools.

Multicast ping (MPing) is a diagnostic tool that can be used to:

● Ping a common group address.

● Check the multicast routing table on the switch to determine the protocol
operating status and the establishment of the multicast distribution tree.
● Collect statistics on received Internet Control Message Protocol (ICMP) Echo
Reply packets from the destination host and calculate the TTL and response
time from the ping initiator to the group member.
● Calculate the network delay and route jitter by performing MPing tests
continuously.
● Ping a reserved group address to check reserved group members on the
network.

Procedure
Step 1 Run the ping multicast [ -c count | -h ttl-value | -i interface-type interface-
number | -m time | -p pattern | -q | -s packetsize | -t timeout | -tos tos-value | -v ]
* host command to monitor multicast service performance.

By specifying a reserved group address, you can check whether the switch
interface connected to the specified interface is running the corresponding
protocol and has joined the reserved group.

NOTE

When the destination address is a reserved group address, you must specify the parameter -i.
When the destination is not a reserved group address, you cannot specify the parameter -i.

----End

9.10.2 Using Tracert to Check Multicast Service Performance

Context
During multicast service troubleshooting and routine maintenance, run the
mtrace command to collect traffic information, which helps you locate the failure
points and reduce configuration errors. You can also perform tracert tests multiple
times to figure out rates of multicast flows.

Procedure
● Run the mtrace [ -l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr | -ur
resp-dest ] | -q nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-
name | -w timeout ] * source source-address command to trace the reverse
path forwarding (RPF) path from a multicast source to the querier.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 575

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

● Run the mtrace -g group [ -l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr

| -ur resp-dest ] | -q nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-
name | -w timeout ] * source source-address command to trace the multicast
path from a multicast source to the querier.
● Run the mtrace { -gw last-hop-router | -d } -r receiver [ -a source-ip-address |
-l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr | -ur resp-dest ] | -q
nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-name | -w timeout ]
* source source-address command to trace the RPF path from a multicast

source to a destination host.

● Run the mtrace { -gw last-hop-router | -b | -d } -r receiver -g group [ -a
source-ip-address | -l [ stat-times ] [ -st stat-int ] | -m max-ttl | [ -mr | -ur
resp-dest ] | -q nqueries | -tr ttl | -ts ttl | -v | -vpn-instance vpn-instance-
name | -w timeout ] * source source-address command to trace the multicast
path from a multicast source to a destination host.

----End

Follow-up Procedure
Run the display mtrace statistics command to display statistics about an mtrace
test instance. After multiple MTrace tests are performed, the accumulated
statistics make the analysis result inaccurate. In this case, run the reset mtrace
statistics command to reset MTrace statistics.

9.10.3 Deleting Multicast Forwarding Entries and Routing

Entries

Context
After confirming that multicast forwarding entries and routing entries can be
deleted, run the reset commands in the user view to delete the entries.

NOTICE

Deleting multicast forwarding entries or routing entries may cause interruption of

multicast data transmission. When you delete entries from the multicast routing
table, multicast forwarding entries are also deleted.

Procedure
● Run either of the following commands in the user view to delete multicast
forwarding entries:
– reset multicast [ vpn-instance vpn-instance-name | all-instance ]
forwarding-table all
– reset multicast [ vpn-instance vpn-instance-name | all-instance ]
forwarding-table { group-address [ mask { group-mask | group-mask-
length } ] | source-address [ mask { source-mask | source-mask-length } ]
| incoming-interface { interface-type interface-number | register } } *

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 576

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

● Run either of the following commands in the user view to delete multicast
routing entries:
– reset multicast [ vpn-instance vpn-instance-name | all-instance ]
routing-table all
– reset multicast [ vpn-instance vpn-instance-name | all-instance ]
routing-table { group-address [ mask { group-mask | group-mask-
length } ] | source-address [ mask { source-mask | source-mask-length } ]
| incoming-interface { interface-type interface-number | register } } *

----End

9.10.4 Monitoring Multicast Routing and Forwarding

Context
During routine maintenance, run the following commands in any view to check
the running status of the multicast forwarding and routing tables.

Procedure
● 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 the multicast boundary configured on
an interface.
● Run the display multicast[ vpn-instance vpn-instance-name | all-instance ]
forwarding-table [ group-address [ mask { group-mask | group-mask-
length } ] | source-address [ mask { source-mask | source-mask-length } ] |
incoming-interface { interface-type interface-number | register } | outgoing-
interface { include | exclude | match } { interface-type interface-number |
register | none } | { statistics | verbose } ] * command to check the MFIB.
● Run the display multicast routing-table [ vpn-instance vpn-instance-
name ] static [ config ] [ source-address { mask-length | mask } ] command
to check the multicast static routing table.
● Run either of the following commands to check the multicast routing table:
– display multicast { vpn-instance vpn-instance-name | all-instance }
routing-table [ group-address [ mask { group-mask | group-mask-
length } ] | source-address [ mask { source-mask | source-mask-length } ]
| incoming-interface { interface-type interface-number | register } |
outgoing-interface { include | exclude | match } { interface-type
interface-number | register | none } ] * [ outgoing-interface-number
[ number ] ]
● Run the display multicast [ vpn-instance vpn-instance-name | all-instance ]
rpf-info source-address [ group-address ] [ rpt | spt ] command to check the
reverse path forwarding (RPF) route.

----End

9.10.5 Configuring the Maximum Number of Invalid IPv4

Multicast Protocol Packets that a Switch Can Store

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 577

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Context
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 switch can store.
Then check statistics and details about invalid multicast packets for
troubleshooting.

Procedure
Step 1 Run the system-view command to enter the system view.
Step 2 Run the multicast invalid-packet { igmp | msdp | pim } max-count max-number
command to set the maximum number of invalid multicast protocol packets that
the switch can store.
By default, a switch can store a maximum of 10 invalid packets for each multicast
protocol.

NOTE

Only the following versions and products support the mdt keyword.

----End

Checking the Configuration

After completing the configuration, run the following commands to check the
maximum number of invalid IPv4 multicast protocol packets that can be saved
and statistics about invalid multicast protocol packets:
● Run the display current-configuration | include multicast invalid-packet
command to check the maximum number of invalid multicast protocol
packets that the switch can store.
● Run the following commands to check the statistics about various invalid
multicast protocol packets saved on the switch:
– 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 saved on
the switch.
– 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 saved on the switch.
– Run the display pim [ vpn-instance vpn-instance-name | all-instance ]
invalid-packet [ interface interface-type interface-number | message-
type { assert | bsr | hello | join-prune | graft | graft-ack | state-
refresh } ] * command or display pim invalid-packet message-type
{ crp | register | register-stop } command to check statistics about
invalid Protocol Independent Multicast (PIM) packets saved on the
switch.
● Run the following commands to check detailed information about a specified
number of latest invalid multicast protocol packets received by the switch:

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 578

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

– Run the display igmp invalid-packet [ packet-number ] verbose

command to check details information about a specified number of latest
invalid IGMP packets received by the switch.
– Run the display msdp invalid-packet [ packet-number ] verbose
command to check details information about a specified number of latest
invalid MSDP packets received by the switch.
– Run the display pim invalid-packet [ packet-number ] verbose
command to check details information about a specified number of latest
invalid PIM packets received by the switch.

9.11 Configuration Examples

9.11.1 Example for Configuring a Multicast Static Route to

Change the RPF Route

Networking Requirements
In Figure 9-11, SwitchA, SwitchB, and SwitchC run Open Shortest Path First
(OSPF) to implement IP interworking, and their interfaces use Protocol
Independent Multicast Sparse Mode (PIM-SM) to provide multicast services. Data
sent from the multicast source (Source) is forwarded to the receiver host
(Receiver) through SwitchA and SwitchB. The link between SwitchA and SwitchB
transmits unicast and multicast services simultaneously. To reduce load on this
link, multicast data needs to be transmitted along the path SwitchA → SwitchC →
SwitchB.

NOTE

In this scenario, to avoid loops, ensure that all connected interfaces have STP disabled and
connected interfaces are removed from VLAN 1. If STP is enabled and VLANIF interfaces of
switches are used to construct a Layer 3 ring network, an interface on the network will be
blocked. As a result, Layer 3 services on the network cannot run normally.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 579

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Figure 9-11 Configuring a static route to change the RPF route

SwitchC

GE0/0/3 GE0/0/2
VLANIF30 VLANIF40
10.1.12.2/24 10.1.13.2/24

10.1.12.1/24 10.1.13.1/24
VLANIF30 PIM-SM VLANIF40
GE0/0/3 GE0/0/2

SwitchA SwitchB
GE0/0/1 GE0/0/1
GE0/0/2 VLANIF10 VLANIF10
10.1.9.1/24 10.1.9.2/24 GE0/0/3
VLANIF20 VLANIF50
10.1.8.1/24 10.1.7.1/24

10.1.8.2/24 10.1.7.2/24
Source Receiver

Multicast static route

Configuration Roadmap
By configuring a multicast static route, you can change the reverse path
forwarding (RPF) interface used to receive multicast data, so that multicast and
unicast services are transmitted through different links to reduce load on a single
link. The configuration roadmap is as follows:

1. Configure IP addresses for interfaces and configure a unicast routing protocol

(OSPF in this example) on each switch. Multicast routing protocols depend on
unicast routing protocols.
2. Enable multicast routing on all switches and PIM-SM on all Layer 3 interfaces.
Configure a static rendezvous point (RP) and specify the static RP address on
all switches. Enable Internet Group Management Protocol (IGMP) on the
interface connected to the network segment of the receiver host. After these
basic multicast functions are configured, the switches can establish a
multicast distribution tree using default parameter settings. Multicast data
can then be forwarded to Receiver along the multicast distribution tree.
3. Configure a multicast RPF static route on SwitchB and specify SwitchC as the
RPF neighbor.

Procedure
Step 1 Configure IP addresses for interfaces and configure OSPF on each switch. SwitchB
is used as an example in the following operations. Configurations of the other
switches are similar.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 580

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

# Create VLANs and add Layer 2 physical interfaces to the VLANs.

<HUAWEI> system-view
[HUAWEI] sysname SwitchB
[SwitchB] vlan batch 10 40 50
[SwitchB] interface gigabitethernet0/0/1
[SwitchB-GigabitEthernet0/0/1] port link-type trunk
[SwitchB-GigabitEthernet0/0/1] port trunk allow-pass vlan 10
[SwitchB-GigabitEthernet0/0/1] quit
[SwitchB] interface gigabitethernet0/0/2
[SwitchB-GigabitEthernet0/0/2] port link-type trunk
[SwitchB-GigabitEthernet0/0/2] port trunk allow-pass vlan 40
[SwitchB-GigabitEthernet0/0/2] quit
[SwitchB] interface gigabitethernet0/0/3
[SwitchB-GigabitEthernet0/0/3] port link-type trunk
[SwitchB-GigabitEthernet0/0/3] port trunk allow-pass vlan 50
[SwitchB-GigabitEthernet0/0/3] quit

# Configure IP addresses and masks for Layer 3 VLANIF interfaces.

[SwitchB] interface vlanif 10
[SwitchB-Vlanif10] ip address 10.1.9.2 24
[SwitchB-Vlanif10] quit
[SwitchB] interface vlanif 40
[SwitchB-Vlanif40] ip address 10.1.13.1 24
[SwitchB-Vlanif40] quit
[SwitchB] interface vlanif 50
[SwitchB-Vlanif50] ip address 10.1.7.1 24
[SwitchB-Vlanif50] quit

# Configure OSPF.
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.7.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.9.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.13.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit

Step 2 Enable multicast routing on all switches and enable PIM-SM on all Layer 3
interfaces.
# Enable multicast routing globally, PIM-SM on all Layer 3 interfaces, and IGMP
on the interface connected to the network segment of the receiver host. (The
configurations on the other switches are similar to the configuration on SwitchB.)
[SwitchB] multicast routing-enable
[SwitchB] interface vlanif 10
[SwitchB-Vlanif10] pim sm
[SwitchB-Vlanif10] quit
[SwitchB] interface vlanif 40
[SwitchB-Vlanif40] pim sm
[SwitchB-Vlanif40] quit
[SwitchB] interface vlanif 50
[SwitchB-Vlanif50] pim sm
[SwitchB-Vlanif50] igmp enable
[SwitchB-Vlanif50] quit

# Configure the IP address of VLANIF30 on SwitchC as a static RP address. (The

configurations on the other switches are similar to the configuration on SwitchC.)
[SwitchC] pim
[SwitchC-pim] static-rp 10.1.12.2
[SwitchC-pim] quit

# Run the display multicast rpf-info command on SwitchB to check the RPF
route to Source. The following command output shows that the RPF route
originates from a unicast routing protocol, and the RPF neighbor is SwitchA.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 581

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

[SwitchB] display multicast rpf-info 10.1.8.2

VPN-Instance: public net
RPF information about source: 10.1.8.2
RPF interface: Vlanif10, RPF neighbor: 10.1.9.1
Referenced route/mask: 10.1.8.0/24
Referenced route type: unicast
Route selection rule: preference-preferred
Load splitting rule: disable

Step 3 Configure a multicast static route.

# Configure a multicast RPF static route to Source on SwitchB, and configure
SwitchC as the RPF neighbor.
[SwitchB] ip rpf-route-static 10.1.8.0 255.255.255.0 10.1.13.2

Step 4 Verify the configuration.

# Run the display multicast rpf-info command on SwitchB to check the RPF
route to Source. The command output shows that the unicast RPF route has been
replaced with the multicast static route and the RPF neighbor has changed to
SwitchC.
[SwitchB] display multicast rpf-info 10.1.8.2
VPN-Instance: public net
RPF information about source: 10.1.8.2
RPF interface: Vlanif40, RPF neighbor: 10.1.13.2
Referenced route/mask: 10.1.8.0/24
Referenced route type: mstatic
Route selection rule: preference-preferred
Load splitting rule: disable

----End

Configuration Files
● SwitchA configuration file
#
sysname SwitchA
#
vlan batch 10 20 30
#
multicast routing-enable
#
interface Vlanif10
ip address 10.1.9.1 255.255.255.0
pim sm
#
interface Vlanif20
ip address 10.1.8.1 255.255.255.0
pim sm
#
interface Vlanif30
ip address 10.1.12.1 255.255.255.0
pim sm
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 10
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 20
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk allow-pass vlan 30

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 582

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

#
ospf 1
area 0.0.0.0
network 10.1.8.0 0.0.0.255
network 10.1.9.0 0.0.0.255
network 10.1.12.0 0.0.0.255
#
pim
static-rp 10.1.12.2
#
return
● SwitchB configuration file
#
sysname SwitchB
#
vlan batch 10 40 50
#
multicast routing-enable
#
interface Vlanif10
ip address 10.1.9.2 255.255.255.0
pim sm
#
interface Vlanif40
ip address 10.1.13.1 255.255.255.0
pim sm
#
interface Vlanif50
ip address 10.1.7.1 255.255.255.0
pim sm
igmp enable
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 10
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 40
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk allow-pass vlan 50
#
ospf 1
area 0.0.0.0
network 10.1.7.0 0.0.0.255
network 10.1.9.0 0.0.0.255
network 10.1.13.0 0.0.0.255
#
pim
static-rp 10.1.12.2
#
ip rpf-route-static 10.1.8.0 24 10.1.13.2
#
return
● SwitchC configuration file
#
sysname SwitchC
#
vlan batch 30 40
#
multicast routing-enable
#
interface Vlanif30
ip address 10.1.12.2 255.255.255.0
pim sm
#

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 583

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

interface Vlanif40
ip address 10.1.13.2 255.255.255.0
pim sm
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 40
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk allow-pass vlan 30
#
ospf 1
area 0.0.0.0
network 10.1.12.0 0.0.0.255
network 10.1.13.0 0.0.0.255
#
pim
static-rp 10.1.12.2
#
return

9.11.2 Example for Configuring Multicast Static Routes to

Connect RPF Routes

Networking Requirements
In Figure 9-12, SwitchB and SwitchC run Open Shortest Path First (OSPF) to
implement IP interworking, but they have no unicast route to SwitchA. Switch
interfaces must run Protocol Independent Multicast Sparse Mode (PIM-SM) to
provide multicast services. The receiver host (Receiver) can receive data from
Source1 and also needs to receive data from Source2.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 584

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Figure 9-12 Configuring multicast static routes to connect RPF routes

Source1
10.1.3.2/24

10.1.3.1/24 10.1.4.1/24
VLANIF13 VLANIF40
GE0/0/2 GE0/0/3 SwitchA
SwitchB
GE0/0/3
GE0/0/1 VLANIF40
PIM-SM 10.1.4.2/24 GE0/0/1
VLANIF20
VLANIF11
10.1.2.2/24
10.1.2.1/24 10.1.5.1/24
VLANIF20
OSPF GE0/0/1
SwitchC

GE0/0/2
VLANIF12
10.1.1.1/24

Source2
10.1.5.2/24
Receiver

Multicast static route

Configuration Roadmap
An RPF route to Source2 can be established on the path SwitchC → SwitchB →
SwitchA by configuring multicast static routes on SwitchB and SwitchC. The
configuration roadmap is as follows:

1. Configure IP addresses for interfaces of the switches. Configure OSPF on

SwitchB and SwitchC but not on SwitchA, so that SwitchB and SwitchC have
no unicast route to SwitchA.
2. Enable multicast routing on all switches and PIM-SM on all Layer 3 interfaces.
Configure a static RP and specify the static rendezvous point (RP) address on
all switches. Enable Internet Group Management Protocol (IGMP) on the
interface connected to the network segment of the receiver host. After these
basic multicast functions are configured, the switches can establish a
multicast distribution tree using default parameter settings. Multicast data
can then be forwarded to Receiver along the multicast distribution tree.
3. Configure multicast static routes to Source2 on SwitchB and SwitchC.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 585

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Procedure
Step 1 Configure IP addresses for interfaces and configure OSPF on each switch. SwitchB
is used as an example in the following operations. Configurations of the other
switches are similar.
# Create VLANs and add Layer 2 physical interfaces to the VLANs on the switches.
<HUAWEI> system-view
[HUAWEI] sysname SwitchB
[SwitchB] vlan batch 13 20 40
[SwitchB] interface gigabitethernet0/0/1
[SwitchB-GigabitEthernet0/0/1] port link-type trunk
[SwitchB-GigabitEthernet0/0/1] port trunk allow-pass vlan 20
[SwitchB-GigabitEthernet0/0/1] quit
[SwitchB] interface gigabitethernet0/0/2
[SwitchB-GigabitEthernet0/0/2] port link-type trunk
[SwitchB-GigabitEthernet0/0/2] port trunk allow-pass vlan 13
[SwitchB-GigabitEthernet0/0/2] quit
[SwitchB] interface gigabitethernet0/0/3
[SwitchB-GigabitEthernet0/0/3] port link-type trunk
[SwitchB-GigabitEthernet0/0/3] port trunk allow-pass vlan 40
[SwitchB-GigabitEthernet0/0/3] quit

# Configure IP addresses and masks for Layer 3 VLANIF interfaces on the switches.
[SwitchB] interface vlanif 13
[SwitchB-Vlanif13] ip address 10.1.3.1 24
[SwitchB-Vlanif13] quit
[SwitchB] interface vlanif 20
[SwitchB-Vlanif20] ip address 10.1.2.2 24
[SwitchB-Vlanif20] quit
[SwitchB] interface vlanif 40
[SwitchB-Vlanif40] ip address 10.1.4.1 24
[SwitchB-Vlanif40] quit

# Configure OSPF on SwitchB and SwitchC.

[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.2.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.3.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit

Step 2 Enable multicast routing on all switches and enable PIM-SM on all Layer 3
interfaces.
# Enable multicast routing globally, PIM-SM on all Layer 3 interfaces, and IGMP
on the interface connected to the network segment of the receiver host.
Configure SwitchA.
[SwitchA] multicast routing-enable
[SwitchA] interface vlanif11
[SwitchA-Vlanif11] pim sm
[SwitchA-Vlanif11] quit
[SwitchA] interface vlanif 40
[SwitchA-Vlanif40] pim sm
[SwitchA-Vlanif40] quit

Configure SwitchB.
[SwitchB] multicast routing-enable
[SwitchB] interface vlanif 20
[SwitchB-Vlanif20] pim sm
[SwitchB-Vlanif20] quit
[SwitchB] interface vlanif 13

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 586

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

[SwitchB-Vlanif13] pim sm
[SwitchB-Vlanif13] quit
[SwitchB] interface vlanif 40
[SwitchB-Vlanif40] pim sm
[SwitchB-Vlanif40] quit

Configure SwitchC.
[SwitchC] multicast routing-enable
[SwitchC] interface vlanif 20
[SwitchC-Vlanif20] pim sm
[SwitchC-Vlanif20] quit
[SwitchC] interface vlanif 12
[SwitchC-Vlanif12] pim sm
[SwitchC-Vlanif12] igmp enable
[SwitchC-Vlanif12] quit

# Configure the IP address of VLANIF20 on SwitchB as a static RP address. (The

configurations on the other switches are similar to the configuration on SwitchB.)
[SwitchB] pim
[SwitchB-pim] static-rp 10.1.2.2
[SwitchB-pim] quit

# Source1 (10.1.3.2/24) and Source2 (10.1.5.2/24) send multicast data to group G

(225.1.1.1). After Receiver joins group G, it receives the multicast data sent by
Source1 but cannot receive the multicast data sent by Source2.
# Run the display multicast rpf-info 10.1.5.2 command on SwitchB and SwitchC.
No information is displayed, indicating that SwitchB and SwitchC have no RPF
route to Source2.
Step 3 Configure multicast static routes.
# On SwitchA, configure a static route to the RP to enable Source2 to register on
the RP.
[SwitchA] ip route-static 10.1.2.2 32 10.1.4.1

# Configure a multicast RPF static route to Source2 on SwitchB, and configure

SwitchA as the RPF neighbor.
[SwitchB] ip rpf-route-static 10.1.5.0 255.255.255.0 10.1.4.2

# Configure a multicast RPF static route to Source2 on SwitchC, and configure

SwitchB as the RPF neighbor.
[SwitchC] ip rpf-route-static 10.1.5.0 255.255.255.0 10.1.2.2

Step 4 Verify the configuration.

# Run the display multicast rpf-info 10.1.5.2 command on SwitchB and SwitchC
to check the RPF route to Source2. The following information is displayed:
[SwitchB] display multicast rpf-info 10.1.5.2
VPN-Instance: public net
RPF information about source: 10.1.5.2
RPF interface: Vlanif40, RPF neighbor: 10.1.4.2
Referenced route/mask: 10.1.5.0/24
Referenced route type: mstatic
Route selection rule: preference-preferred
Load splitting rule: disable
[SwitchC] display multicast rpf-info 10.1.5.2
VPN-Instance: public net
RPF information about source: 10.1.5.2
RPF interface: Vlanif20, RPF neighbor: 10.1.2.2
Referenced route/mask: 10.1.5.0/24

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 587

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Referenced route type: mstatic

Route selection rule: preference-preferred
Load splitting rule: disable

# Run the display pim routing-table command on SwitchC to check the PIM
routing table. SwitchC has multicast entries for Source2, indicating that Receiver
can now receive multicast data from Source2.
[SwitchC] 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: Vlanif20
Upstream neighbor: 10.1.2.2
RPF prime neighbor: 10.1.2.2
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlanif12
Protocol: igmp, UpTime: 01:38:19, Expires: -

(10.1.3.2, 225.1.1.1)
RP: 10.1.2.2
Protocol: pim-sm, Flag: SPT ACT
UpTime: 00:00:44
Upstream interface: Vlanif20
Upstream neighbor: 10.1.2.2
RPF prime neighbor: 10.1.2.2
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlanif12
Protocol: pim-sm, UpTime: 00:00:44, Expires: -

(10.1.5.2, 225.1.1.1)
RP: 10.1.2.2
Protocol: pim-sm, Flag: SPT ACT
UpTime: 00:00:44
Upstream interface: Vlanif20
Upstream neighbor: 10.1.2.2
RPF prime neighbor: 10.1.2.2
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlanif12
Protocol: pim-sm, UpTime: 00:00:44, Expires: -

----End

Configuration Files
● SwitchA configuration file
#
sysname SwitchA
#
vlan batch 11 40
#
multicast routing-enable
#
interface Vlanif11
ip address 10.1.5.1 255.255.255.0
pim sm
#
interface Vlanif40
ip address 10.1.4.2 255.255.255.0
pim sm
#

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 588

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 11
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk allow-pass vlan 40
#
pim
static-rp 10.1.2.2
#
ip route-static 10.1.2.2 255.255.255.255 10.1.4.1
#
return
● SwitchB configuration file
#
sysname SwitchB
#
vlan batch 13 20 40
#
multicast routing-enable
#
interface Vlanif13
ip address 10.1.3.1 255.255.255.0
pim sm
#
interface Vlanif20
ip address 10.1.2.2 255.255.255.0
pim sm
#
interface Vlanif40
ip address 10.1.4.1 255.255.255.0
pim sm
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 20
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 13
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk allow-pass vlan 40
#
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
static-rp 10.1.2.2
#
ip rpf-route-static 10.1.5.0 24 10.1.4.2
#
return
● SwitchC configuration file
#
sysname SwitchC
#
vlan batch 12 20
#
multicast routing-enable
#
interface Vlanif12
ip address 10.1.1.1 255.255.255.0
pim sm

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 589

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

igmp enable
#
interface Vlanif20
ip address 10.1.2.1 255.255.255.0
pim sm
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 20
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 12
#
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
#
pim
static-rp 10.1.2.2
#
ip rpf-route-static 10.1.5.0 24 10.1.2.2
#
return

9.11.3 Example for Configuring Multicast Load Splitting

Networking Requirements
In Figure 9-13, SwitchE connects to HostA and has three equal-cost routes to the
multicast source (Source). According to the default reverse path forwarding (RPF)
check policy, SwitchE will select one of these equal-cost routes to transmit
multicast data. When the rate of multicast traffic is high, the network will become
congested, lowering the quality of multicast services. To ensure the quality of
multicast services, multicast load splitting needs to be configured so that multicast
data can be transmitted through multiple equal-cost routes.

NOTE

In this scenario, to avoid loops, ensure that all connected interfaces have STP disabled and
connected interfaces are removed from VLAN 1. If STP is enabled and VLANIF interfaces of
switches are used to construct a Layer 3 ring network, an interface on the network will be
blocked. As a result, Layer 3 services on the network cannot run normally.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 590

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Figure 9-13 Networking diagram of multicast load splitting

Source
24 19
.2/ V 2.16
6 8.1 IF201 GELANI 8.4.1
2.1 AN 0/ 0/0 F6 /2
19 VL GE0/ /2 0 4
SwitchB
4 19
1/2 2.1
8 .1. 68
6 VL .4.2
2.1 20 PIM-SM
19 NIF 1 GE ANIF /24
A 0/0 60
10.110.1.2/24 VL 0/0/ /1
VLANIF10 GE 192.168.2.1/24 SwitchC
192.168.5.2/24
GE0/0/4 SwitchE
VLANIF30 VLANIF80
GE0/0/2 GE0/0/2
SwitchA
GE0/0/1 GE0/0/2
VLANIF30 VLANIF80 GE0/0/4
GE 3
0 192.168.2.2/24 192.168.5.1/24 /0/00 10.110.2.2/24
VL /0/3 0
GE IF1 4 VLANIF140
19 ANI AN 2/2
2.1 F4 V 8.6.
L
68 0 6
.3. 2 .1
1/2 19
Loopback0 4
GE /2 00 24
10.1.1.1/32 19 0
2.1 VLAN /0/1 0/0 IF1 /
68 GE LAN 8.6.1
.3. IF40 V .16
2/2 2
4 19

SwitchD
HostA

Configuration Roadmap
The configuration roadmap is as follows:
1. Configure IP addresses for interfaces on the switches.
2. Configure a unicast routing protocol, Intermediate System-Intermediate
System (IS-IS) in this example, to implement interworking among all switches
and ensure that route costs are the same.
3. Enable multicast routing on all switches and enable PIM-SM on all Layer 3
interfaces. Configure the loopback interface on SwitchA as a candidate
bootstrap router (C-BSR) and candidate rendezvous point (C-RP).
4. On SwitchE, configure stable-preferred multicast load splitting to ensure
stable transmission of multicast services.
5. On SwitchE, configure static multicast groups on the interface connected to
the network segment of HostA, because HostA needs to receive data of these
groups for a long time.
6. On SwitchE, configure different multicast load splitting weights for the
interfaces connected to the upstream switches to implement unbalanced load
splitting, because HostA needs to receive multicast data of new groups.

Procedure
Step 1 Configure IP addresses for interfaces on the switches. SwitchA is used as an
example in the following operations. Configurations of the other switches are
similar.
# Create VLANs and add Layer 2 physical interfaces to the VLANs.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 591

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

<HUAWEI> system-view
[HUAWEI] sysname SwitchA
[SwitchA] vlan batch 10 20 30 40
[SwitchA] interface gigabitethernet0/0/4
[SwitchA-GigabitEthernet0/0/4] port link-type trunk
[SwitchA-GigabitEthernet0/0/4] port trunk allow-pass vlan 10
[SwitchA-GigabitEthernet0/0/4] quit
[SwitchA] interface gigabitethernet0/0/1
[SwitchA-GigabitEthernet0/0/1] port link-type trunk
[SwitchA-GigabitEthernet0/0/1] port trunk allow-pass vlan 20
[SwitchA-GigabitEthernet0/0/1] quit
[SwitchA] interface gigabitethernet0/0/2
[SwitchA-GigabitEthernet0/0/2] port link-type trunk
[SwitchA-GigabitEthernet0/0/2] port trunk allow-pass vlan 30
[SwitchA-GigabitEthernet0/0/2] quit
[SwitchA] interface gigabitethernet0/0/3
[SwitchA-GigabitEthernet0/0/3] port link-type trunk
[SwitchA-GigabitEthernet0/0/3] port trunk allow-pass vlan 40
[SwitchA-GigabitEthernet0/0/3] quit

# Configure IP addresses and masks for Layer 3 interfaces.

[SwitchA] interface vlanif 10
[SwitchA-Vlanif10] ip address 10.110.1.2 24
[SwitchA-Vlanif10] quit
[SwitchA] interface vlanif 20
[SwitchA-Vlanif20] ip address 192.168.1.1 24
[SwitchA-Vlanif20] quit
[SwitchA] interface vlanif 30
[SwitchA-Vlanif30] ip address 192.168.2.1 24
[SwitchA-Vlanif30] quit
[SwitchA] interface vlanif 40
[SwitchA-Vlanif40] ip address 192.168.3.1 24
[SwitchA-Vlanif40] quit
[SwitchA] interface loopback0
[SwitchA-LoopBack0] ip address 10.1.1.1 32
[SwitchA-LoopBack0] quit

Step 2 Configure IS-IS to implement interworking among all switches and ensure that
route costs are the same (SwitchA as an example).
[SwitchA] isis 1
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] quit
[SwitchA] interface vlanif 10
[SwitchA-Vlanif10] isis enable 1
[SwitchA-Vlanif10] quit
[SwitchA] interface vlanif 20
[SwitchA-Vlanif20] isis enable 1
[SwitchA-Vlanif20] quit
[SwitchA] interface vlanif 30
[SwitchA-Vlanif30] isis enable 1
[SwitchA-Vlanif30] quit
[SwitchA] interface vlanif 40
[SwitchA-Vlanif40] isis enable 1
[SwitchA-Vlanif40] quit
[SwitchA] interface loopback0
[SwitchA-LoopBack0] isis enable 1
[SwitchA-LoopBack0] quit

Step 3 Enable multicast routing on all switches and enable Protocol Independent
Multicast Sparse Mode (PIM-SM) on all Layer 3 interfaces (SwitchA as an
example).
[SwitchA] multicast routing-enable
[SwitchA] interface vlanif 10
[SwitchA-Vlanif10] pim sm
[SwitchA-Vlanif10] quit
[SwitchA] interface vlanif 20
[SwitchA-Vlanif20] pim sm

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 592

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

[SwitchA-Vlanif20] quit
[SwitchA] interface vlanif 30
[SwitchA-Vlanif30] pim sm
[SwitchA-Vlanif30] quit
[SwitchA] interface vlanif 40
[SwitchA-Vlanif40] pim sm
[SwitchA-Vlanif40] quit
[SwitchA] interface loopback 0
[SwitchA-LoopBack0] pim sm
[SwitchA-LoopBack0] quit

Step 4 On all switches, specify the IP address of Loopback0 on SwitchA as a static RP

address (SwitchA as an example).
[SwitchA] pim
[SwitchA-pim] static-rp 10.1.1.1
[SwitchA-pim] quit

Step 5 Configure stable-preferred multicast load splitting on SwitchE.

[SwitchE] multicast load-splitting stable-preferred

Step 6 Configure static multicast groups on the interface of SwitchE connected to the
network segment of HostA.
# Configure static multicast groups 225.1.1.1 to 225.1.1.3 on VLANIF 140.
[SwitchE] interface Vlanif140
[SwitchE-Vlanif140] igmp static-group 225.1.1.1 inc-step-mask 32 number 3
[SwitchE-Vlanif140] quit

Step 7 Verify the configuration of stable-preferred multicast load splitting.

# Source (10.110.1.1/24) sends multicast data to multicast groups 225.1.1.1 to
225.1.1.3. HostA can receive multicast data from Source. Brief information about
the PIM routing table on SwitchE is as follows:
[SwitchE] display pim routing-table brief
VPN-Instance: public net
Total 3 (*, G) entries; 3 (S, G) entries

00001.(*, 225.1.1.1)
Upstream interface:Vlanif100
Number of downstream:1
00002.(10.110.1.1, 225.1.1.1)
Upstream interface:Vlanif100
Number of downstream:1
00003.(*, 225.1.1.2)
Upstream interface:Vlanif80
Number of downstream:1
00004.(10.110.1.1, 225.1.1.2)
Upstream interface:Vlanif80
Number of downstream:1
00005.(*, 225.1.1.3)
Upstream interface:Vlanif60
Number of downstream:1
00006.(10.110.1.1, 225.1.1.3)
Upstream interface:Vlanif60
Number of downstream:1

(*, G) and (S, G) entries are evenly distributed on the three equal-cost routes. The
upstream interfaces of the routes are VLANIF 100, VLANIF 80, and VLANIF 60,
respectively.

NOTE

The load splitting algorithm processes (*, G) and (S, G) entries separately using the same
rule.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 593

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Step 8 Set different multicast load splitting weights for upstream interfaces of SwitchE to
implement uneven multicast load splitting.
# Set the multicast load splitting weight of VLANIF 60 to 3.
[SwitchE] interface Vlanif60
[SwitchE-Vlanif60] multicast load-splitting weight 3
[SwitchE-Vlanif60] quit

# Set the multicast load splitting weight of VLANIF 80 to 2.

[SwitchE] interface Vlanif80
[SwitchE-Vlanif80] multicast load-splitting weight 2
[SwitchE-Vlanif80] quit

Step 9 Configure new static multicast groups on the interface of SwitchE connected to
the network segment of HostA.
# Configure static multicast groups 225.1.1.4 to 225.1.1.6 on VLANIF 140.
[SwitchE] interface Vlanif140
[SwitchE-Vlanif140] igmp static-group 225.1.1.4 inc-step-mask 32 number 3
[SwitchE-Vlanif140] quit

Step 10 Verify the configuration of uneven multicast load splitting.

# Source (10.110.1.1/24) sends multicast data to multicast groups 225.1.1.1 to
225.1.1.6. HostA can receive multicast data from Source. Brief information about
the PIM routing table on SwitchE is as follows:
[SwitchE] display pim routing-table brief
VPN-Instance: public net
Total 6 (*, G) entries; 6 (S, G) entries

00001.(*, 225.1.1.1)
Upstream interface:Vlanif60
Number of downstream:1
00002.(10.110.1.1, 225.1.1.1)
Upstream interface:Vlanif60
Number of downstream:1
00003.(*, 225.1.1.2)
Upstream interface:Vlanif80
Number of downstream:1
00004.(10.110.1.1, 225.1.1.2)
Upstream interface:Vlanif80
Number of downstream:1
00005.(*, 225.1.1.3)
Upstream interface:Vlanif100
Number of downstream:1
00006.(10.110.1.1, 225.1.1.3)
Upstream interface:Vlanif100
Number of downstream:1
00007.(*, 225.1.1.4)
Upstream interface:Vlanif60
Number of downstream:1
00008.(10.110.1.1, 225.1.1.4)
Upstream interface:Vlanif60
Number of downstream:1
00009.(*, 225.1.1.5)
Upstream interface:Vlanif60
Number of downstream:1
00010.(10.110.1.1, 225.1.1.5)
Upstream interface:Vlanif60
Number of downstream:1
00011.(*, 225.1.1.6)
Upstream interface:Vlanif80
Number of downstream:1
00012.(10.110.1.1, 225.1.1.6)

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 594

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Upstream interface:Vlanif80
Number of downstream:1

The upstream interfaces of existing (*, G) and (S, G) entries remain unchanged.
VLANIF 60 has a larger multicast load splitting weight (3) than VLANIF 80 (2).
Therefore, more new (*, G) and (S, G) entries are distributed to the route with
VLANIF 60 as the upstream interface. The multicast load splitting weight of
VLANIF 100 is 1 (default value), smaller than the weights of VLANIF60 and
VLANIF80. Therefore, the route with VLANIF 100 as the upstream interface does
not have new entries.

----End

Configuration Files
● SwitchA configuration file
#
sysname SwitchA
#
vlan batch 10 20 30 40
#
multicast routing-enable
#
isis 1
network-entity 10.0000.0000.0001.00
#
interface Vlanif10
ip address 10.110.1.2 255.255.255.0
isis enable 1
pim sm
#
interface Vlanif20
ip address 192.168.1.1 255.255.255.0
isis enable 1
pim sm
#
interface Vlanif30
ip address 192.168.2.1 255.255.255.0
isis enable 1
pim sm
#
interface Vlanif40
ip address 192.168.3.1 255.255.255.0
isis enable 1
pim sm
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 20
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 30
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk allow-pass vlan 40
#
interface GigabitEthernet0/0/4
port link-type trunk
port trunk allow-pass vlan 10
#
interface LoopBack0
ip address 10.1.1.1 255.255.255.255
isis enable 1
pim sm

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 595

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

#
pim
static-rp 10.1.1.1
#
return
● SwitchB configuration file
#
sysname SwitchB
#
vlan batch 20 60
#
multicast routing-enable
#
isis 1
network-entity 10.0000.0000.0002.00
#
interface Vlanif20
ip address 192.168.1.2 255.255.255.0
isis enable 1
pim sm
#
interface Vlanif60
ip address 192.168.4.1 255.255.255.0
isis enable 1
pim sm
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 20
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 60
#
pim
static-rp 10.1.1.1
#
return
● SwitchC configuration file
#
sysname SwitchC
#
vlan batch 30 80
#
multicast routing-enable
#
isis 1
network-entity 10.0000.0000.0003.00
#
interface Vlanif30
ip address 192.168.2.2 255.255.255.0
isis enable 1
pim sm
#
interface Vlanif80
ip address 192.168.5.1 255.255.255.0
isis enable 1
pim sm
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 30
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 80
#
pim

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 596

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

static-rp 10.1.1.1
#
return
● SwitchD configuration file
#
sysname SwitchD
#
vlan batch 40 100
#
multicast routing-enable
#
isis 1
network-entity 10.0000.0000.0004.00
#
interface Vlanif40
ip address 192.168.3.2 255.255.255.0
isis enable 1
pim sm
#
interface Vlanif100
ip address 192.168.6.1 255.255.255.0
isis enable 1
pim sm
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 40
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 100
#
pim
static-rp 10.1.1.1
#
return
● SwitchE configuration file
#
sysname SwitchE
#
vlan batch 60 80 100 140
#
multicast routing-enable
multicast load-splitting stable-preferred
#
isis 1
network-entity 10.0000.0000.0005.00
#
interface Vlanif60
ip address 192.168.4.2 255.255.255.0
isis enable 1
pim sm
multicast load-splitting weight 3
#
interface Vlanif80
ip address 192.168.5.2 255.255.255.0
isis enable 1
pim sm
multicast load-splitting weight 2
#
interface Vlanif100
ip address 192.168.6.2 255.255.255.0
isis enable 1
pim sm
#
interface Vlanif140
ip address 10.110.2.2 255.255.255.0
isis enable 1

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 597

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

pim sm
igmp static-group 225.1.1.1 inc-step-mask 0.0.0.1 number 3
igmp static-group 225.1.1.4 inc-step-mask 0.0.0.1 number 3
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 60
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk allow-pass vlan 80
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk allow-pass vlan 100
#
interface GigabitEthernet0/0/4
port link-type trunk
port trunk allow-pass vlan 140
#
pim
static-rp 10.1.1.1
#
return

9.12 Common Misconfigurations

9.12.1 Multicast Static Route Fails to Take Effect

Fault Description
A device does not run any dynamic routing protocols, and a multicast static route
is configured on the device. Multicast data cannot be forwarded to user hosts
through this multicast static route even though the physical status and link-layer
protocol status of the interface are both Up.

Procedure
Step 1 Check whether the multicast static route is configured correctly and has been
added to the multicast routing table.
Run the display multicast routing-table static command to check whether the
multicast static route is configured correctly.
If the multicast static route is not configured correctly or does not match the
network topology because the topology has changed, the multicast routing table
will not contain the routing entry or configuration of the multicast static route. In
this case, run the ip rpf-route-static command to configure a multicast static
route that matches the current network topology.
Step 2 Check whether the multicast static route has been added to the routing table of
the specified routing protocol.
If a routing protocol has been specified for the multicast static route, run the
display ip routing-table command to check whether this route has been added
to the routing table of the protocol. If not, configure a matching unicast route for
the routing protocol.

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 598

S1720, S2700, S5700, and S6720 Series Ethernet
Switches
Configuration Guide - IP Multicast 9 IPv4 Multicast Route Management Configuration

Step 3 Check whether the multicast static route matches the specified routing policy.
If a routing protocol has been specified for the multicast static route, run the
display route-policy command to check whether the source address of the
multicast static route matches the routing policy. If not, run the route-policy
command to change the matching rule of the routing policy. Ensure that the
multicast static route matches the routing policy and can be added to the routing
table.

----End

9.12.2 Upstream Interface in Multicast Forwarding Entries Is

Incorrect

Fault Description
After multicast routing configuration is complete, Protocol Independent Multicast
(PIM) routing entries are created. However, the upstream interface in multicast
forwarding entries is incorrect, and multicast data cannot be sent to user network
segments.

Procedure
Step 1 Run the display multicast forwarding-table command to check whether the
upstream interface in multicast forwarding entries is a loopback interface.
If the upstream interface is a loopback interface, a possible reason is that the
source IP address of multicast data packets is the same as a VLANIF interface
address on the device. In this case, change the multicast source address or the
VLANIF interface address. Ensure that the two IP addresses are different but
remain on the same network segment.

----End

Issue 14 (2020-11-30) Copyright © Huawei Technologies Co., Ltd. 599