ZXR10 M6000 (V1.00.30) Carrier-Class Router Configuration Guide (IPv4 Multicast)

ZXR10 M6000
Carrier-Class Router
Configuration Guide (IPv4 Munticast)

Version: V1.00.30
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R2.1
2011-05-10
Third release, The follwoing chapters are modified.

l
PIM-SM Configuration
MSDP Configuration
R2.0
2011-01-15
Second release, the document architecture is changed.
R1.0
2010-09-30
First release
Serial Number: SJ-20110504161056-014

Publishing Date: 2010-05-10 (R2.1)
Contents
About This Manual ......................................................................................... I
Chapter 1 Safety Instruction...................................................................... 1-1
1.1 Safety Instruction ............................................................................................... 1-1
1.2 Safety Signs ...................................................................................................... 1-1
Chapter 2 IP Multicast Principle................................................................ 2-1

2.1 IP Multicasting Overview..................................................................................... 2-1
2.1.1 IP Multicast Address................................................................................. 2-1
2.1.2 Multicast Tree .......................................................................................... 2-1
2.1.3 Multicast Routing Protocol ........................................................................ 2-2
2.2 Configuring Public IP Multicast ............................................................................ 2-3
Chapter 3 IGMP Configuration .................................................................. 3-1

3.1 IGMP Overview.................................................................................................. 3-1
3.2 IGMP Principle ................................................................................................... 3-1
3.3 Configuring IGMP............................................................................................... 3-2
3.3.1 Configuring IGMP Version......................................................................... 3-3
3.3.2 Configuring an IGMP Group on an Interface............................................... 3-3
3.3.3 Configuring IGMP Timers.......................................................................... 3-4
3.4 IGMP Maintenance............................................................................................. 3-6
3.5 IGMP Configuration Examples ............................................................................ 3-7
3.5.1 IGMP Querier Election.............................................................................. 3-7
3.5.2 Joining of IGMP Dynamic Group and Static Group ..................................... 3-9
3.5.3 IGMP Fast Leaving Form All Groups ........................................................3-11
3.5.4 IGMP Fast Leaving Form a Specified Group ............................................ 3-14
3.6 IGMP Fault Handling ........................................................................................ 3-17
3.6.1 Network Topology................................................................................... 3-17
3.6.2 Fault Analysis ........................................................................................ 3-17
3.6.3 Handling Flow ........................................................................................ 3-17
3.6.4 Handling Procedure................................................................................ 3-18
Chapter 4 PIM-DM Configuration .............................................................. 4-1

4.1 PIM-DM Overview .............................................................................................. 4-1
4.2 PIM-DM Principle ............................................................................................... 4-1
4.3 Configuring PIM-DM ........................................................................................... 4-1
4.4 PIM-DM Maintenance ......................................................................................... 4-2
I
4.5 PIM-DM Configuration Example .......................................................................... 4-4

4.6 PIM-DM Fault Handling ...................................................................................... 4-5
4.6.1 Network Topology..................................................................................... 4-5
4.6.2 Fault Analysis .......................................................................................... 4-6
4.6.3 Handling Flow .......................................................................................... 4-6
4.6.4 Handling Procedure.................................................................................. 4-6
Chapter 5 PIM-SM Configuration .............................................................. 5-1

5.1 PIM-SM Overview .............................................................................................. 5-1
5.2 PIM-SM Principle ............................................................................................... 5-1
5.3 Configuring PIM-SM ........................................................................................... 5-3
5.4 PIM-SM Maintenance ......................................................................................... 5-5
5.5 PIM-SM Configuration Examples........................................................................5-11
5.5.1 Forwarding Multicast Flow through PIM-SM (Dynamic RP).........................5-11
5.5.2 Forwarding Multicast Flow through PIM-SM (Static RP) ............................ 5-13
5.5.3 Illegal Multicast Source Control ............................................................... 5-15
5.5.4 Anycast-RP Configuration Example ......................................................... 5-18
5.6 PIM-SM Fault Handling..................................................................................... 5-20
5.6.2 Fault Analysis ........................................................................................ 5-21
5.6.3 Handling Flow ........................................................................................ 5-21
Chapter 6 PIM-SSM Configuration ............................................................ 6-1

6.1 PIM-SSM Overview ............................................................................................ 6-1
6.2 PIM-SSM Principle ............................................................................................. 6-1
6.3 Configuring PIM-SSM ......................................................................................... 6-1
6.4 PIM-SSM Configuration Example ........................................................................ 6-2
6.5 PIM-SSM Fault Handling .................................................................................... 6-4
6.5.2 Fault Analysis .......................................................................................... 6-4
6.5.3 Handling Flow .......................................................................................... 6-4
Chapter 7 Multicast Load Sharing Configuration.................................... 7-1

7.1 Multicast Load Sharing Overview ........................................................................ 7-1
7.2 Multicast Load Sharing Principle.......................................................................... 7-1
7.3 Configuring Multicast Load Sharing ..................................................................... 7-2
7.4 Multicast Load Sharing Maintenance ................................................................... 7-2
7.5 Multicast Load Sharing Configuration Example..................................................... 7-3
II
7.6 Multicast Load Sharing Fault Handling................................................................. 7-6

7.6.2 Fault Analysis .......................................................................................... 7-6
7.6.3 Handling Flow .......................................................................................... 7-6
Chapter 8 Static Multicast Configuration ................................................. 8-1

8.1 Static Multicast Overview .................................................................................... 8-1
8.2 Static Multicast Principle ..................................................................................... 8-1
8.3 Configuring Static Multicast................................................................................. 8-2
8.4 Static Multicast Maintenance............................................................................... 8-3
8.5 Static Multicast Configuration Example ................................................................ 8-4
8.6 Static Fault Malfunction Handling ........................................................................ 8-5
8.6.2 Fault Analysis .......................................................................................... 8-5
8.6.3 Handling Flow .......................................................................................... 8-5
Chapter 9 MSDP Configuration ................................................................. 9-1

9.1 MSDP Overview................................................................................................. 9-1
9.2 MSDP Principle.................................................................................................. 9-1
9.3 Configuring MSDP.............................................................................................. 9-2
9.3.1 Configuring an MSDP Neighbor ................................................................ 9-2
9.3.2 Configuring MSDP Extended Functions ..................................................... 9-2
9.3.3 Configuring an MSDP Policy ..................................................................... 9-3
9.3.4 Clearing MSDP States.............................................................................. 9-4
9.4 MSDP Maintenance ........................................................................................... 9-5
9.5 MSDP Configuration Examples ........................................................................... 9-7
9.5.1 MSDP Basic Configuration Example.......................................................... 9-7
9.5.2 Anycast-RP Accomplished Through MSDP .............................................. 9-12
9.6 MSDP Fault Handling ....................................................................................... 9-14
9.6.2 Fault Analysis ........................................................................................ 9-15
9.6.3 Handling Flow ........................................................................................ 9-15
Chapter 10 IGMP Snooping Configuration............................................. 10-1

10.1 IGMP Snooping Overview ............................................................................... 10-1
10.2 IGMP Snooping Principle ................................................................................ 10-1
10.3 Configuring IGMP Snooping............................................................................ 10-1
III
10.4 IGMP Snooping Maintenance.......................................................................... 10-5

10.5 IGMP Snooping Configuration Example ........................................................... 10-6
10.6 IGMP Snooping Fault Handling ....................................................................... 10-9
10.6.1 Network Topology................................................................................. 10-9
10.6.2 Fault Analysis......................................................................................10-10
10.6.3 Handling Flow .....................................................................................10-10
10.6.4 Handling Procedure.............................................................................10-10
Chapter 11 PIM Snooping Configuration................................................ 11-1

11.1 PIM Snooping Overview...................................................................................11-1
11.2 PIM Snooping Principle ....................................................................................11-1
11.3 Configuring PIM Snooping................................................................................11-1
11.4 PIM Snooping Maintenance..............................................................................11-2
11.5 PIM Snooping Configuration Example ...............................................................11-2
11.6 PIM Snooping Fault Handling ...........................................................................11-6
11.6.1 Network Topology ..................................................................................11-6
11.6.2 Fault Analysis........................................................................................11-6
11.6.3 Handling Flow .......................................................................................11-6
11.6.4 Handling Procedure ...............................................................................11-7
Figures............................................................................................................. I
Glossary ........................................................................................................ III
IV
About This Manual

Purpose
At first, thank you for choosing ZXR10 routers of ZTE Corporation!
This manual describes the principle, configuration commands, maintenance commands,
configuration examples and fault handling about IPv4 multicast function of ZXR10 M6000.
Intended Audience
This manual is intended for the following engineers:
l
l
l
On-site maintenance engineers

Network monitor engineers
System operation and maintenance engineer
What Is in This Manual

This manual contains the following contents:
Chapter
Summary
Chapter 1 Safety Instruction
Introduces safety instruction and symbol description for device

installation, operation and maintenance.
Chapter 2 IP Multicast Principle
Describes the multicast principle, include multicast address,

multicast tree, multicast route protocol and the command of
configuring public IP multicast.
Chapter 3 IGMP Configuration
Describes the IGMP principle, configuration commands,

maintenance commands, configuration examples and fault
handling.
Chapter 4 PIM-DM Configuration
Describes the PIM-DM principle, configuration commands,

handling.
Chapter 5 PIM-SM Configuration
Describes the PIM-SM principle, configuration commands,

handling.
Chapter 6 PIM-SSM Configuration
Describes the PIM-SSM principle, configuration commands,

handling.
Chapter 7 Multicast Load Sharing
Describes the Multicast Load Sharing principle, configuration
Configuration
commands, maintenance commands, configuration examples

and fault handling.
Chapter
Summary
Chapter 8 Static Multicast
Describes the Static Multicast principle, configuration commands,
Configuration

handling.
Chapter 9 MSDP Configuration
Describes the MSDP principle, configuration commands,

handling.
Chapter 10 IGMP Snooping
Describes the IGMP Snooping principle, configuration
Configuration
commands, maintenance commands, configuration examples

and fault handling.
Chapter 11 PIM Snooping
Describes the PIM Snooping principle, configuration commands,
Configuration

handling.
Conventions
ZTE documents employ the following typographical conventions.
Typeface
Meaning
Italics
Variables in commands. It may also refers to other related manuals and documents.
Bold
Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters and commands.
CAPS
Keys on the keyboard and buttons on screens and company name.
Constant
Text that you type, program codes, filenames, directory names, function names.
width
[]
Optional parameters.
{}
Mandatory parameters.
Separates individual parameter in series of parameters.
Danger: Indicates an imminently hazardous situation, which if not avoided, will result in
death or serious injury.
Warning: Indicates a hazard that, if not avoided, could result in serious injuries,
equipment damages or interruptions of major services.
Caution: Indicates a potential hazard that, if not avoided, could result in moderate
injuries, equipment damages or partial service interruption.
Note: Provides additional information about a certain topic.
II
Typeface
Meaning
Checkpoint: Indicates that a particular step needs to be checked before proceeding
further.
Tip: Indicates a suggestion or hint to make things easier or more productive for the
reader.
III
IV
Chapter 1
Safety Instruction
Table of Contents
Safety Instruction .......................................................................................................1-1
Safety Signs ...............................................................................................................1-1
1.1 Safety Instruction

Only duly trained and qualified personnel can install, operate and maintain the devices.
During the device installation, operation and maintenance, please abide by the local
safety specifications and related operation instructions, otherwise physical injury may
occur or devices may be broken. The safety precautions mentioned in this manual are
only supplement of local safety specifications.
The debug commands on the devices will affect the performance of the devices, which
may bring serious consequences. So take care to use debug commands. Especially, the
debug all command will open all debug processes, so this command must not be used on
the devices with services. It is not recommended to use the debug commands when the
user networks are in normal state.
ZTE Corporation will assume no responsibility for consequences resulting from violation
of general specifications for safety operations or of safety rules for design, production and
use of the devices.
1.2 Safety Signs

The information that users should pay attention to when they install, operate and maintain
devices are explained in the following formats:
Warning!
Indicates the matters needing close attention. If this is ignored, serious injury accidents
may happen or devices may be damaged.
Caution!
Indicates the matters needing attention during configuration.
1-1
SJ-20110504161056-014|2010-05-10 (R2.1)
ZTE Proprietary and Confidential
ZXR10 M6000 Configuration Guide (IPv4 Munticast)
Note:
Indicates the description, hint, tip, and so on for configuration operations.
1-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 2
IP Multicast Principle
Table of Contents
IP Multicasting Overview ............................................................................................2-1
Configuring Public IP Multicast ...................................................................................2-3
2.1 IP Multicasting Overview

Internet Protocol (IP) multicast is a point to multipoint or multipoint to multipoint
communication mode, that is, several receivers receive the same information from a
source. IP multicast can be applied to video conference, distance education, software
distribution, and so on.
Multicasting protocol includes member management protocol and multicast routing
protocol. The member management protocol is used to manage the joining and leaving
of multicasting members. The multicast routing protocol is used to construct a multicast
tree by interacting with information among routers.
2.1.1 IP Multicast Address

In an IP multicast network, the sender sends a packet to multiple receivers in multicasting
mode. The sender is called multicast source. Multiple receivers of the same packet
are identified by the same ID. This is called multicast group address. In the IP address
allocation scheme, IP addresses of Class D (224.0.0.0~239.255.255.255) are the
IP multicast addresses. The addresses 224.0.0.0~224.0.0.255 and the addresses
239.0.0.0~239.255.255.255 are used for research and management.
2.1.2 Multicast Tree

In Transfer Control Protocol/Internet Protocol (TCP/IP) network, to enable multicast
communication, the multicast source, receivers and the paths of multicast packets should
be available. The most widely used routing method is to establish tree routes. Tree routes
have the following two advantages:
1. Packets are sent to different receivers along the tree branches in parallel.
2. Packets are copied only on crotches, which minimizes the number of packets
transmitted in the network.
A multicast tree is a set that comprises a series of ingress interfaces and egress interfaces
on routers. It determines a unique forwarding path between the subnet to which the
multicast source belongs and all the subnets that contain the group members.
2-1
SJ-20110504161056-014|2010-05-10 (R2.1)
There are two types of multicast trees, source tree and shared tree.
1. Source tree
The source tree is also called the Shortest Path Tree (SPT). It constructs a spanning
tree to all receivers for each source. This spanning tree takes the source as the
root node. It reaches the subnets to which the receivers belong. A multicast group
may contain several multicast sources. Each source or each pair of (S, G) has a
corresponding multicast tree.
The method to construct a source tree is Reverse Path Forwarding (RPF). Each
router can find the shortest path to the source and the corresponding egress interface
according to unicast route. When a router receives a multicast packet, it checks
whether the ingress interface that the packet reaches is the egress interface to the
source with the shortest unicast path. If it is, the router forwards the multicast packet
according to the multicast routes. Otherwise, the router discards the multicast packet.
The ingress interface from which the router receives the multicast packets is called a
parent link. The egress interface on which the router sends the multicast packets is
called a child link.
2. Shared tree
The shared tree constructs a multicast route tree for each multicast group. A multicast
group is shared by all group members. That is, the tree is shared by the group (*,
G) instead of every pair of (S, G). Each member that wants to receive the multicast
packets from the group should be added to the shared tree explicitly.
A shared tree uses one or a group of routers as the center of the tree. Multicast
packets from all sources in this group to the receivers are sent to the center. Then
these packets are forwarded in multicasting mode along the tree from the center.
2.1.3 Multicast Routing Protocol

Multicast routing protocol is responsible for interacting with information among routers
to construct a multicast tree. Different multicast routing protocol use different methods.
To meet the requirements of multicast user locations in the networks, multicast routing
protocol is classified into two types, dense mode and sparse mode.
1. Dense mode
The prerequisite if a multicast routing protocol of dense mode is that multicast
users locate in the network densely and there is plenty of bandwidth. The protocol
constructs and maintains the multicast tree by flooding the multicast packets to the
network periodically. That is, a router running multicast routing protocol will flood the
packets it receives on all interfaces except the receiving interface.
When a neighbor router of an interface reports that some group does not exist, the
interface will be deleted from the multicast tree of the group. This is called pruning.
When the neighbor router of an interface reports that the receiver of this group appears
again, the interface will be added to the multicast tree of the group. This is called graft.
2-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 2 IP Multicast Principle
There are the following multicast routing protocols of dense mode:

l Distance Vector Multicast Routing Protocol (DVMRP)
l Multicast Open Shortest Path First (MOSPF)
l Protocol Independent Multicast - Dense Mode (PIM-DM)
2. Sparse mode
A multicast routing protocol of sparse mode is suitable for the networks where
the multicast receivers locate sparsely. In such networks, if the multicast tree is
constructed through flooding (the same with dense mode), a lot of bandwidth will be
wasted. In sparse mode, if a device expects to receive multicast packets, it should
make an application to join the multicast tree first.
There are the following multicast routing protocols of sparse mode:
l
l
Core-Based Trees (CBT)

Protocol Independent Multicast - Sparse Mode (PIM-SM)
2.2 Configuring Public IP Multicast

To configure public IP multicast on ZXR10 M6000, perform the following steps.
Step
Command
Function
ZXR10(config)#ip multicast-routing
This enables IP multicast function.
ZXR10(config)#no ip multicast-routing
This disables IP multicast function.
ZXR10(config-mcast)#router pimsm
This enables PIM-SM.
ZXR10(config-pimsm)#exit
This exit from PIM-SM mode.
ZXR10(config-mcast)#vrf < vrf-name>
This enters multicast Virtual Route

Forwarding (VRF) mode. It is
necessary to enable PIM-SM first.
ZXR10(config-mcast-vrf)#mtunnel < intf_name>
This configures an interface to an

mtunnel interface.
ZXR10(config-mcast-vrf)#mdt default < group-address>
This configures the mdt default

group of an instance.
ZXR10(config-mcast-vrf)#mdt data < group-address> <
This configures the mdt data group
group_mask> [ < acl-name> ]
of an instance.
ZXR10#show ip mroute [ < vrf-name> ] [ group < group-address> ] [
This shows the IP multicast routing
source < source-address> ]
table.
ZXR10#show ip rpf < source-address>
This shows the RPF information.

The RPF information which PIM has
not paid attention to is not displayed.
10
ZXR10#clear ip mroute [ < vrf-name> ] [ group-address <
This clears multicast routes.
group-address> ] [ source-address < source-address> ]
2-3
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
11
ZXR10#show ip mdt
This shows the multicast MDT

information.
12
ZXR10#show ip mroute summary [ < vrf-name> ]
This shows the number of multicast

routes in the IP multicast routing
tables.
13
ZXR10#show ip mroute brief [ < vrf-name> ]
This shows the detailed information

of an IP multicast routing table.
Descriptions of the parameter in Step 4:

Parameter
Description
< vrf-name>
VRF name

Parameter
Description
< intf_name>
Interface name

Parameter
Description
< group-address>
The address of an mdt data group in a VRF instance
2-4
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 3
IGMP Configuration
Table of Contents
IGMP Overview ..........................................................................................................3-1
IGMP Principle ...........................................................................................................3-1
Configuring IGMP.......................................................................................................3-2
IGMP Maintenance.....................................................................................................3-6
IGMP Configuration Examples ...................................................................................3-7
IGMP Fault Handling ................................................................................................3-17
3.1 IGMP Overview

If a host expects to receive the multicast packets from a specific group, it needs to detect
all packets sent to that group. To solve the routing problem of multicast packets on the
Internet, it is necessary for the host to join or leave a group by informing the multicast
routers on the network.
In multicast, Internet Group Management Protocol (IGMP) is used to execute this task. In
this way, the multicast router knows the members of the multicast group on the network and
decides whether to forward the multicast packets to the network. When a multicast router
receives a multicast packet, it checks the multicast destination address of the packet. Then
it forwards the packet to the interfaces in the group or the downstream router.
3.2 IGMP Principle

IGMP is run between hosts and the routers connecting to the host directly. Its function is
bidirectional. On one hand, a host informs the router through IGMP about the information
of a specific multicast group that it expects to receive. On the other hand, the router
checks whether the members in the Local Area Network (LAN) are in active state
periodically through IGMP. In this way, the router collects and maintains the relationship
with the members in the segment. Through IGMP, a router records whether there
is a group member of a specific multicast group in the local segment instead of the
corresponding relationship between the multicast group and the host.
IGMP provides information that is necessary when packets are forwarded to the destination
(the last stage). The multicast routers and the hosts that receive multicast data exchange
information. The information is collected from the group members of the hosts that are
directly connected to the multicast routers.
IGMP employs two kinds of packets, group member query packets and group member
report packets. A multicast router periodically sends group member query packets to all
3-1
SJ-20110504161056-014|2010-05-10 (R2.1)
hosts to know which specific group members exist in the connected subnets. The hosts
returns group member report packets, reporting the multicast group which they belong to.
When a host joins a new group, it will send a Join packet immediately instead of waiting
for a query in case that the host is the first member of that group and it fails to receive any
multicast packet.
When a host starts to receive packets as a member of a group, the multicast router will
query the group periodically to check whether there is any other member of the group on
the network. If there is any, the multicast router continues to forward data.
When the host leaves the group, the multicast router will receive a leaving packet and then
it will immediately query whether there are still active group members in the group. If there
is any, the multicast router will continue to forward data. If there is no member, it will not
forward data.
At present, there are three versions of IGMP.
l
l
l
IGMPv1 (Request For Comments (RFC) 1112) defines basic query and report
procedure of a group member.
IGMPv2 (RFC 2236) adds the mechanisms group member leaving, on the basis of
IGMPv1.
IGMPv3 (RFC 3376) adds the ability of a member to select the multicast source. This
is to support Source Specific Multicast (SSM).
3.3 Configuring IGMP

The following configuration is configured on interfaces in non-VRF mode.
The
configuration on interfaces in VRF mode is the same. For the configuration to enable
VRF mode, please refer to the Configuring Public IP Multicast topic.
To configure IGMP on ZXR10 M6000, perform the following steps.
Step
Command
Function
ZXR10(config-mcast)#router igmp
This enters IGMP configuration

mode.
This deletes all IGMP configuration
ZXR10(config-mcast)#no router igmp
and restores the default

configuration.
2
ZXR10(config-igmp)#interface < interface-name>
This enters IGMP interface

configuration mode.
ZXR10(config-igmp)#no interface < interface-name>
This deletes the interface

configuration and restores the
default configuration.
ZXR10(config-igmp)#ssm-map static < access- list-number> <
This configures SSM mapping.
source-address>
3-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-igmp-if)#immediate-leave { < access-list-name> | all}
This configures the range of groups

in which members are allowed to
leave immediately.
This deletes the configuration of
ZXR10(config-igmp-if)#no immediate-leave
immediate leave.

Parameter
Description
< interface-name>
Interface name

Parameter
Description
< access-list-number>
Access list name for the SSM group, with 1-31 characters
Descriptions of the parameters in Step 4:

Parameter
Description
< access- list-number>
Access list name of an SSM group, with 1-31 chatacters
all
All multicast groups
The IGMP function of ZXR10 M6000 is on the base of PIM interface. IGMP function is
enabled automatically on the interfaces on which PIM is enabled.
3.3.1 Configuring IGMP Version

At present, there are IGMPv1, v2 and v3. By default, it is IGMPv3. The version can be
adjusted according to situations with version < version> command. Considering security, a
router requires all Network Elements (NEs) on the same segment to use the same IGMP
version.
The configuration of IGMP version is on the base of interface. Different versions can be
configured on different interfaces.
3.3.2 Configuring an IGMP Group on an Interface

To configure an IGMP group on an interface on ZXR10 M6000, perform the following steps.
3-3
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-igmp-if)#access-group < access-list-number>
This configures the range of groups

allowing the IGMP to join. The
parameter < access-list-number> Is
the standard IP access list name,
with 1-31 characters. By default,
there is no limit about IGMP group
joining.
ZXR10(config-igmp-if)#static-group < group-address>
This configures a static group

address on an IGMP interface. The
parameter < group-address> is the
address of the group, in the dotted
decimal notation.
ZXR10(config-igmp-if)#immediate-leave [ group-list <
This configures the range of
access-list-number> ]
groups allowing members to leave

immediately. The parameter <
access-list-number> Is the standard
IP access list name, with 1-31
characters.
3.3.3 Configuring IGMP Timers

After enabling IGMP on the interfaces of multicast routers connecting to the shared network
segment, select the optimum interface as the querier of this network segment. The querier
sends query messages to obtain the information of the group members.
After sending query message, the querier will wait for the member report sent from the host
that receives the query message for a period. The wait duration is the maximum response
time carried in the query message. By default, it is 10 seconds.
After receiving the query message, a host member in the network segment will reduce
a random deviation value based on the maximum response time. This result will be
used as the response time of the host member its own. During this period, if the querier
receives a report from another host member, this host member will cancel the report.
Otherwise, the host member will send the host report when the response time expires.
Therefore, prolonging the maximum response time will increase the waiting changes of
a group member in the network segment accordingly and decrease the burst of multiple
host reports in the network segment.
The timers related to the querier can be adjusted according to actual requirements.
To configure IGMP timers on ZXR10 M6000, perform the following steps.
3-4
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-igmp-if)#query-interval < seconds>
This configures the IGMP query

interval. The parameter < seconds>
is the interval. It is in the range of
1-65535, in the unit of second. The
default value is 125 seconds.
ZXR10(config-igmp-if)#query-max-response-time < seconds>
This configures the maximum

response time contained in the
query messages. This command is
only valid on IGMPv2 and IGMPv3
interfaces. The parameter < seconds>
is the time value. It is in the range
of 1-25, in the unit of second. The
default value is 10 seconds.
ZXR10(config-igmp-if)#querier-timeout < seconds>
This configures the IGMP querier

time-out. The parameter <
seconds> is the time-out. It is in
the range of 60-300, in the unit
of second. The default value is
<query-interval> *< robustness-count>
+< query-max-response-time> /2
seconds. The < robustness-count>
parameter is the robustness count
of the querier.
ZXR10(config-igmp-if)#last-member-query-interval < seconds>
This configures the IGMP query

interval of a specific group. This
command is only valid on IGMPv2
interfaces. The parameter < seconds>
is the query interval. It is in the range
of 1-25, in the unit of second. The
default value is 1 second.
ZXR10(config-igmp-if)#robusrness-count < times>
This configures the robusrness count

of the IGMP querier, that is, the
number of attempts to send query
packets. The parameter < times> is
the number of queries. It is in the
range of 2-7.
3-5
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-igmp-if)#shaping-packets-number < number>
This configures the number of

packets allowed to be forwarded
on the interface. The parameter <
number> is the number of packets.
The range is from 1 to the maximum
number that is allowed on the
interface.
3.4 IGMP Maintenance

ZXR10 M6000 provides the following commands to maintain IGMP.
Command
Function
ZXR10#show ip igmp interface [ < interface-name> ]
This shows the interface IGMP

configuration.
ZXR10#show ip igmp groups [ vrf < vrf-name> ] [ summary vrf < vrf-name>
This shows the IGMP group joining
] [ < interface-name> ] [ < group-addr> ] [ deatil]
information on an interface.
ZXR10#show ip igmp packet-count [ < interface-name> ]
This shows the statistics count of IGMP

protocol packets sending and receiving.
This shows the summary IGMP
ZXR10#show ip igmp group summary
information on an interface.
ZXR10#clear ip igmp groups [ < interface-name> ]
This deletes the multicast groups added

dynamically.
This clears the the statistics count of
ZXR10#clear ip igmp packet-count
IGMP protocol packets sending and

receiving.
Parameter descriptions:
Parameter
Description
< interface-name>
Interface name
An example of the ZXR10#show ip igmp interface command output is shown below.

ZXR10#show ip igmp interface
fei-0/1/0/1
Internet address is 102.1.1.3, subnet mask is 255.0.0.0
IGMP is enabled on interface
Current IGMP version is 2
IGMP query interval is 125 seconds
IGMP last member query interval is 1 seconds
3-6
SJ-20110504161056-014|2010-05-10 (R2.1)

IGMP query max response time is 10 seconds
IGMP querier timeout period is 255 seconds
IGMP querier is 102.1.1.3, never expire
Inbound IGMP access group is not set
IGMP immediate leave control is not set
An example of the ZXR10#show ip igmp groups [ vrf < vrf-name> ] [ < interface-name> ] [ <
group-addr> ] [ deatil] command output is shown below.
ZXR10#show ip igmp groups fei-0/1/0/3
IGMP Connected Group Membership
Group addr
Interface
Present
Expire
Last Reporter
233.1.1.4
fei-0/1/0/3
01:07:49
never
30.1.1.43
233.1.1.147
fei-0/1/0/3
01:07:49
00:03:05
30.1.1.42
233.1.4.21
fei-0/1/0/3
01:07:49
00:03:05
30.1.1.42
Descriptions of the command output:

Command Output
Description
Group addr
Group address
Interface
Interface
Present
The time when the group member is present
Expire
The remaining time of the time-out timer. Never means there is a static
group and the timer is not enabled.
Last Reporter
The address of the host that reports the group member relation last time
3.5 IGMP Configuration Examples

3.5.1 IGMP Querier Election
Configuration Description
As shown in Figure 3-1, PIM-SM is enabled on R1 and R2. IGMPv2 is enabled to elect a
querier. The IGMPv3 router with the smallest IP address will be elected as the querier.
Figure 3-1 IGMP Querier Election
3-7
SJ-20110504161056-014|2010-05-10 (R2.1)
Configuration Thought
1. Configure the interface IP addresses in interface configuration mode. The address of
R1 is smaller than that of R2.
2. Configure ip multicast-routing to enable IP multicast.
3. Enter PIM-SM route configuration mode and then enter the specific interface.
4. Enable PIM-SM in interface configuration mode.
Configuration Commands
The configuration of R1:
R1(config)#interface fei-0/1/0/1
R1(config-if)#ip address 10.0.0.1 255.255.255.0
R1(config-if)#exit
R1(config)#ip multicast-routing
R1(config-mcast)#router pimsm
R1(config-pimsm)#interface fei-0/1/0/1
R1(config-pimsm-if)#pimsm

R2(config-if)#exit
Configuration Verification
Check the configuration result on R1, as shown below.
R1#show ip igmp interface fei-0/1/0/1
fei-0/1/0/1
/*IGMP version information*/
/*Query interval*/
/*The last member query interval*/
/*Maximum response time*/
/*Querier time-out*/
IGMP robustness variable is 2
3-8
SJ-20110504161056-014|2010-05-10 (R2.1)

/*Querier information. If this device is the querier,
the information is displayed as "never expire".*/
IGMP shaping packets number is not set
IGMP maximum joins is not set
Check the configuration result on R2, as shown below.

fei-0/1/0/2
/*Query interval*/
/*Last member query interval*/
/*Maximum response time*/
/*Querier time-out*/
IGMP querier is 10.0.0.1, expire timer: 00:04:06
/*Querier information. If this device is not the querier,
the information displayed is the remaining expiration time
of the querier. Here "00:04:06" means that the querier will
expire in four minutes and six seconds.*/
3.5.2 Joining of IGMP Dynamic Group and Static Group

As shown in Figure 3-2, PIM-SM is enabled on R1. The IGMP version is v2 by default.
On R1, configure a static group to join 225.1.1.1, and configure a dynamic group to join
225.1.1.2 through the test host.
3-9
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 3-2 Joining of IGMP Dynamic Group and Static Group
1.
2.
3.
4.
5.
Configure the interface address on the router in interface configuration mode.

Configure ip multicast-routing to enable IP multicast.
Enter PIM-SM route configuration mode and then enter the specific interface.
Enable PIM-SM in interface configuration mode.
In multicast mode, enter IGMP route configuration mode and then enter the specific
interface.
6. Configure joining of a static group on fei-0/1/0/1 of R1.
7. Send IGMP joining packets on the test host.
R1(config-if)#exit
R1(config-pimsm)# interface fei-0/1/0/1
R1(config-pimsm-if)#exit
R1(config-pimsm)#exit
R1(config-mcast)#router igmp
R1(config-igmp)#interface fei-0/1/0/1
R1(config-igmp-if)#static-group 225.1.1.1 source 20.1.1.1
Check IGMP interface configuration information on R1, as shown below.
fei-0/1/0/1
3-10
SJ-20110504161056-014|2010-05-10 (R2.1)


Check the detailed information of the groups on the interface of R1, as shown below.
R1(config-igmp-if)#show ip igmp groups fei-0/1/0/1 detail
Flags: S - Static Group, SSM - SSM Group, M - MDT Group
Interface:
Group:
fei-0/1/0/1
225.1.1.1
Flags:
Uptime:
00:05:12
Group mode:
EXCLUDE (Expires: 00:03:24)
/*Time-out of the dynamic group*/

Last reporter:
100.17.21.2
Group source list is empty

Interface:
fei-0/1/0/1
Group:
225.1.1.2
Flags:
Uptime:
00:01:16
Group mode:
INCLUDE
Last reporter:
10.0.0.1
/*Flag of the static group*/
Group source list is empty
3.5.3 IGMP Fast Leaving Form All Groups

As shown in Figure 3-3, a router connects to a multicast user directly.
3-11
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 3-3 IGMP Fast Leave Form All Groups
1. Enter multicast configuration mode and enable interface IGMP function.
2. Configure fast leaving from all groups on the interface.
R1(config-igmp-if)#immediate-leave all
R1(config-igmp-if)#version 2
R1(config-igmp-if)#exit
R1(config-igmp)#exit
R1(config-mcast)#exit
R1(config)#
Configure group joining and leaving on fei-0/1/0/1. Then check the configuration result, as
shown below.
ZXR10#show running-config multicast
! <MULTICAST>
ip multicast-routing
router pimsm
3-12
SJ-20110504161056-014|2010-05-10 (R2.1)

interface fei-0/1/0/1
pimsm
$
$
router igmp
immediate-leave
all
version 2
$
$
! </MULTICAST>
ZXR10#debug ip igmp fei-0/1/0/1

IGMP permit interface (fei-0/1/0/1) debugging is on
ZXR10#terminal monitor
ZXR10 0/20/CPU0 2010-7-27 09:26:24
igmp : Receive IGMP packet from 33.33.0.12 on interface
fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:26:24
igmp : Received packet is IGMP v2 membership report for
group 225.0.0.0
ZXR10 0/20/CPU0 2010-7-27 09:26:24
igmp : Create group (225.0.0.0) on fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:26:24
igmp : Updating EXCLUDE group timer for 225.0.0.0 timer
to 260 seconds
ZXR10#show ip igmp group

Total: 1 groups
Group addr
Interface
Present
Expire
Last Reporter
225.0.0.0
fei-0/1/0/1
00:00:06
00:04:14
33.33.0.12
ZXR10 0/20/CPU0 2010-7-27 09:26:33

fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:26:33
igmp : Received packet is IGMP v2 leave message (225.0.0.0)
ZXR10 0/20/CPU0 2010-7-27 09:26:33
igmp : Membership (225.0.0.0) immediately leaves on fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:26:33
igmp : Delete group 225.0.0.0 on fei-0/1/0/1
Total: 0 groups
Group addr
Interface
Present
Expire
Last Reporter
3-13
SJ-20110504161056-014|2010-05-10 (R2.1)
3.5.4 IGMP Fast Leaving Form a Specified Group

As shown in Figure 3-4, a router connects to a multicast user directly.
Figure 3-4 IGMP Fast Leaving Form a Specified Group
1. Configure a group filter rule
2. Enter multicast configuration mode and enable interface IGMP function.
3. Configure fast leaving from a specified group on the interface.
R1(config)#ipv4-access-list groupfilter
R1(config-ipv4-acl)#rule 1 permit 225.0.0.0
R1(config-ipv4-acl)#rule 2 deny any
R1(config-ipv4-acl)#exit
R1(config-igmp-if)#immediate-leave groupfilter
R1(config-igmp-if)#exit
R1(config-igmp)#exit
3-14
SJ-20110504161056-014|2010-05-10 (R2.1)

R1(config)#
Configure group joining and leaving on fei-0/1/0/1. Then check the configuration result, as
shown below.
ZXR10(config)#show running-config ipv4-acl
! <ACL>
ipv4-access-list groupfilter
rule 1 permit 225.0.0.0 0.0.0.0
rule 2 deny any
$
! </ACL>
ZXR10(config)#show running-config multicast

! <MULTICAST>
router pimsm
pimsm
$
$
router igmp
immediate-leave groupfilter
version 2
$
$
! </MULTICAST>
ZXR10 0/20/CPU0 2010-7-27 09:58:18
fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:58:18
igmp : Received packet is IGMP v2 membership report for
group 225.0.0.0
ZXR10 0/20/CPU0 2010-7-27 09:58:18
ZXR10 0/20/CPU0 2010-7-27 09:58:18
to 260 seconds
ZXR10#
ZXR10 0/20/CPU0 2010-7-27 09:58:23
fei-0/1/0/1
3-15
SJ-20110504161056-014|2010-05-10 (R2.1)

ZXR10 0/20/CPU0 2010-7-27 09:58:23
igmp : Received packet is IGMP v2 membership report for g
roup 225.0.0.1
ZXR10 0/20/CPU0 2010-7-27 09:58:23
ZXR10 0/20/CPU0 2010-7-27 09:58:23
to 260 seconds

Total: 2 groups
Group addr
Interface
Present
Expire
Last Reporter
225.0.0.0
fei-0/1/0/1
00:00:11
00:04:09
33.33.0.12
225.0.0.1
fei-0/1/0/1
00:00:06
00:04:14
33.33.0.12
ZXR10#
ZXR10 0/20/CPU0 2010-7-27 09:58:32
fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:58:32
ZXR10 0/20/CPU0 2010-7-27 09:58:32
igmp : Membership (225.0.0.0) immediately leaves on
fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:58:32
ZXR10 0/20/CPU0 2010-7-27 09:58:33
fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:58:33
ZXR10 0/20/CPU0 2010-7-27 09:58:33
igmp : Send IGMPv2 specific query(225.0.0.1) on fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:58:34
igmp : Send IGMPv2 specific query(225.0.0.1) on fei-0/1/0/1
ZXR10 0/20/CPU0 2010-7-27 09:58:35

Total: 0 groups
Group addr
Interface
Present
Expire
Last Reporter
ZXR10#
3-16
SJ-20110504161056-014|2010-05-10 (R2.1)
3.6 IGMP Fault Handling

3.6.1 Network Topology
The network topology of an IGMP fault is shown in Figure 3-5.
Figure 3-5 Network Topology of an IGMP Fault
3.6.2 Fault Analysis

Symptom: IGMPv2 is enabled. A tester simulates a host to join a group dynamically. The
range of the dynamic group is 225.1.1.1225.1.1.10. However, there is no information
about the group that the tester joins on the router.
Possible causes:
1. Interface fault
2. Configuration problem on the router
3. Configuration problem on the tester
3.6.3 Handling Flow

The flow to handle an IGMP fault is shown in Figure 3-6.
3-17
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 3-6 Flow to Handle an IGMP Fault
3.6.4 Handling Procedure

The procedure to handle an IGMP fault is described below.
1. Check whether the physical link is up. Change the cables and optical modules if
necessary. If the fault is still not solved, change the line card or the interface board.
2. Check whether the IP addresses are configured correctly. Check whether the router
and the tester can ping each other successfully.
3. Check whether PIM-SM is enabled on the corresponding interface, and whether the
IGMP interface information can be viewed.
4. Check whether the related configuration (such as interface information and joining
information) on the host is correct.
5. Use the debug ip pimsm command to analyze the fault.
If the fault cannot be solved according to the steps above, please ask for technical support.
3-18
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 4
PIM-DM Configuration
Table of Contents
PIM-DM Overview ......................................................................................................4-1
PIM-DM Principle .......................................................................................................4-1
Configuring PIM-DM...................................................................................................4-1
PIM-DM Maintenance.................................................................................................4-2
PIM-DM Configuration Example .................................................................................4-4
PIM-DM Fault Handling ..............................................................................................4-5
4.1 PIM-DM Overview

PIM-DM is suitable for dense mode. That is, assume that there are many multicast
receivers locating on most network devices in the network. On the base of such
application modules, the PIM-DM mechanism is relatively easy. It uses the PUSH mode
to spread the multicast traffic to all devices in the network periodically, and then constructs
and maintains the SPT.
4.2 PIM-DM Principle

PIM-DM is a multicast routing protocol of dense mode. It use the PUSH mode to forward
multicast data. Generally, it is used in small-scale network in which the multicast group
members are relatively dense.
PIM-DM assumes that there is at least one multicast group member in each subnet of the
network. Therefore, multicast data will be spread to all nodes in the network. After that,
PIM-DM prunes the branches on which there is no multicast data forwarded. It only keeps
the branches containing receivers. The procedure spreading-pruning occurs periodically.
The pruned branches may recover to forwarding state periodically. When a multicast
group member appears on a node on a branch that was pruned, the node will recover
to forwarding state from pruning state by sending graft messages to the upstream on its
own initiative to forward multicast data.
4.3 Configuring PIM-DM

To configure PIM-DM on ZXR10 M6000, perform the following steps.
4-1
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-mcast)#router pimdm
This enables PIM-DM.
ZXR10(config-mcast)#no router pimdm
This disables PIM-DM.
ZXR10(config-mcast)#interface < interface-name>
This enters PIM-DM interface
configuration mode. The parameter

< interface-name> is the interface
name.
3
This enables PIM-DM on an
ZXR10(config-pimdm-if)#pimdm
interface.
4.4 PIM-DM Maintenance

ZXR10 M6000 provides the following commands to maintain PIM-DM.
Command
Function
ZXR10#show ip pimdm interface[ < interface-name> ]
This views the PIM-DM interface

information. The parameter <
interface-name> is the interface name.
ZXR10#show ip pimdm mroute [ [ group < group-address> [ source <
This views the PIM-DM multicast
source-address> ] ] | [ source < source-address> ] | [ summary] ]
routing table.
ZXR10#show ip pimdm neighbor [ < interface-name> ]
This views the information of a PIM-DM

interface neighbor.
Parameter
Description
group < group-address>
multicast group address, in the dotted decimal notation
source < source-address>
Source address, in the dotted decimal notation
summary
Summary information
An example of the show ip pimdm interface command output is shown below.

ZXR10#show ip pimdm interface
Address
Interface
State Nbr
1.1.1.2
fei-0/1/0/1
Up
Coun
0
Query
DR
Intvl
30
DR
Priority
1.1.1.2

Command Output
Description
Address
Interface address
Interface
Interface name
4-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Command Output
Description
NbrCount
Number of neighbors
State
Interface state, up or down
QueryIntvl
The interval to send Hello messages
DR Priority
DR priority of the interface
An example of the show ip pimdm mroute command output is shown below.

ZXR10#show ip pimdm mroute
PIMDM Multicast Routing Table
Flags:C -Connected,F -Forward,P -Pruned, * -Assert flag
Timers:Uptime/Expires
Interface state:Interface,Next-Hop or VCD,State/Mode

Command Output
Description
Connected
Indicates that there is a member of this multicast group or this interface
Pruned
Indicates that the egress of the route entities is null
Forward
Indicates that this entity has forwarding function
Uptime/Expires
Uptime or expiring time of the entity/egress interface
flag
The state of multicast route entities
Incoming interface
Incoming interface
RPF nbr
RPF neighbor of corresponding entity
Outgoing interface list
Assert flag
An example of the show ip pimdm neighbor command output is shown below.

ZXR10#show ip pimdm neighbor
Neighbor Address
Interface
DR Priority
Uptime
Expires
Ver

Command Output
Description
Neighbor Address
IP address of the neighbor
Interface
Interface name
DR Priority
DR priority of the neighbor
Uptime
Uptime of the neighbor
Expires
Expiring time of the neighbor
4-3
SJ-20110504161056-014|2010-05-10 (R2.1)
4.5 PIM-DM Configuration Example

As shown in Figure 4-1, R1 and R2 establishes PIM-DM neighbor relationship.
Figure 4-1 PIM-DM Configuration Example
Configuration thought
1.
2.
3.
4.
Configure corresponding interfaces.

Enter multicast configuration mode.
Enter PIM-DM configuration mode.
Enable PIM-DM on corresponding interfaces.
R1(config)#interface gei-0/2/0/3
R1(config-if)#exit
R1(config-if)#ip address 33.1.1.1
255.255.255.0
R1(config-if)#exit
R1(config-mcast)#router pimdm
R1(config-pimdm)#interface gei-0/2/0/3
R1(config-pimdm-if)#pimdm

R2(config-if)#exit
R2(config-if)#exit
R2(config-mcast)#router pimdm
4-4
SJ-20110504161056-014|2010-05-10 (R2.1)

Use the show ip pimdm neighbor command on R1 to check the neighbor state, as shown
below.
R1(config)#show ip pimdm neighbor
Neighbor
Interface
DR
Address
199.1.1.2
Uptime
Expires
Ver
00:09:14
00:01:36
V2
Priority
gei-0/2/0/3
Use the show ip pimdm interface command on R1 to check interface state, as shown below.
R1(config)#show ip pimdm interface
Address
Interface
State
Nbr
Query
Count
Intvl
DR
DR
Priority
199.1.1.1
gei-0/2/0/3
Up
30
199.1.1.2
33.1.1.1
gei-0/2/0/4
Up
30
33.1.1.1
Use the show ip mroute command on R1 to check the state of the IP multicast routing table,
as shown below.
R1#show ip mroute
IP Multicast Routing Table
(33.1.1.2, 225.10.0.1), RP: 0.0.0.0, TYPE: DYNAMIC, FLAGS:
Incoming interface: gei-0/2/0/4, flags:
Outgoing interface list:
gei-0/2/0/3, flags:
4.6 PIM-DM Fault Handling

The network topology of a PIM-DM fault is shown in Figure 4-2.
Figure 4-2 Network Topology of a PIM-DM Fault
4-5
SJ-20110504161056-014|2010-05-10 (R2.1)

After PIM-DM is configured, the multicast source sends flows to the group. If the path is
not through, analyze the fault in hardware and software aspects. In the hardware aspect,
check the network wires, optical modules, line cards, and so on. If it is certain that the
hardware has no problem, analyze the fault in the aspect of configuration and software,
such as whether PIM-DM is enabled correctly, and so on.
4.6.3 Handling Flow

The flow to handle a PIM-DM fault is shown in Figure 4-3.
Figure 4-3 Flow to Handle a PIM-DM Fault

The procedure to handle a PIM-DM fault is described below.
1. Check whether the physical links are up. Change the cables and optical modules if
necessary. If the fault is not solved, change the line card or the interface board. If the
fault is still not solved, please consult the hardware development engineers.
2. Check whether the IP addresses are configured correctly, and whether the addresses
can be pinged successfully.
3. Check whether PIM-DM is enabled on corresponding interfaces, and whether PIM-DM
neighbor relationship can be established properly.
4-6
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 5
PIM-SM Configuration
Table of Contents
PIM-SM Overview ......................................................................................................5-1
PIM-SM Principle .......................................................................................................5-1
Configuring PIM-SM ...................................................................................................5-3
PIM-SM Maintenance .................................................................................................5-5
PIM-SM Configuration Examples..............................................................................5-11
PIM-SM Fault Handling ............................................................................................5-20
5.1 PIM-SM Overview

PIM-SM is mainly used in the following situations:
l
l
Group members locate sparsely in a relatively large scale.

The network bandwidth resource is limited.
PIM-SM does not depend on a specific unicast routing protocol. PIM-SM assumes that all
routers on a shared segment do not need to send multicast packets. The routers only can
receive and send multicast packets after they request to join a multicast group on their own
initiative. PIM-SM advertises the multicast information to all routers supporting PIM-SM
through a Rendezvous Point (RP). In PIM-SM, a router joins or leaves the multicast group
explicitly. This reduces the number of packets and the bandwidth used by the control
packets.
5.2 PIM-SM Principle

PIM-SM sends multicast packets by using a shared tree. A shared tree has a center point
that is responsible for forwarding packets for all the multicast sources in the multicast
group. Each multicast source sends packets to the center point along the shortest path,
and then the center point forwards the packets to various receiving ends of the group.
The group center point of the PIM-SM is called the RP. There may be several RPs on a
network, but there is only one RP serving for a multicast group.
A router can obtain the location of the RP in two ways.
1. Configure the RP manually and statically on the routers running PIM-SM.
2. PIM-SMv2 obtains the location through the candidate RP advertisement.
candidate RP with the highest priority will become formal RPs.
The
5-1
SJ-20110504161056-014|2010-05-10 (R2.1)
In PIM-SMv2, some PIM-SM routers are manually set to work as candidate Bootstrap
Routers (BSRs). The candidate BSR with the highest priority will be elected as the formal
BSR.
The BSR is responsible for collecting the candidate RP information on the multicast routers
in the group to find out the candidate RPs in the multicast domain. It notifies the candidate
RPs to all the PIM routers in the PIM domain in a unified way. The PIM routers elect a
formal RP from the candidate RP set according to rule the same as that of RP election.
Candidate RPs are configured manually.
The PIM-SM routers discover each other and maintain the neighbor relationship by
exchanging Hello messages. On the multi-access network, the Hello messages also
contain the priority information of routers. The Designate Router (DR) is elected according
to this parameter.
After receiving a multicast packet from the direct-connected source, the multicast source
or the first-hop router (the DR connecting to the source directly) encapsulates the packet in
a Register message, and then sends it to the RP through a unicast router. When receiving
the Register message, the RP de-encapsulates the messages to take out the packet, and
then sends the packet to the receivers of the group along the shared multicast tree.
Each host acting as a receiver joins the multicast group through the IGMP member report
message. The last-hop router (or the DP on the multi-access network) sends the received
Join message to the RP level by level. After receiving the Join message, the intermediate
router checks whether it has already had the routes of the group. If it has, the intermediate
router adds the downstream request router to the shared multicast tree as a branch. If it
does not, it creates a route and continues to send the Join message to the RP.
When the RP or the multicast router connects to a receiver directly, it can switch to the
SPT from the shared tree. When the RP receives a Register message sent from a new
multicast source, the RP will return a Join message to the DR directly connecting to the
multicast source. Thus, the SPT from the source to the RP is constructed.
After a DR or a router directly connecting to multicast members receives the first multicast
packet from the multicast group, or the received packets reaches a threshold, it can switch
to the SPT from the shared tree. Once the handover occurs, the router will send a Prune
message to the upstream neighbor and request to leave the shared tree.
In PIM-SM, there are the following types of messages.
l
Hello message: The router interfaces on which PIM-SM runs send Hello messages
periodically to the neighbor interfaces in the same segment to establish neighbor
relationship. Hello messages are also used for routers running IGMPv1 to elect the
DR.
Register message: When receiving a multicast packet sent by a multicast source on
the local network, the DR will encapsulate the packet in a Register message and send
it to the RP through unicast. The source address in the IP header of the Register
message is the address of the DR, and the destination address is the address of the
RP.
5-2
SJ-20110504161056-014|2010-05-10 (R2.1)
l
l
Register-Stop message: The RP unicasts a Register-Stop message to the sender of

the Register message to inform it stop sending Register messages.
Join/Prune message: This message is forwarded in the direction to the source or
the RP. A Join message is used to construct a source tree or a shard tree. When a
receiver leaves a group, it sends a Prune message to prune the source tree or the
shard tree. This message contains the joining information and pruning information
of the multicast route entities. The Join message and the Prune message are in the
same packet. Either message can be null.
Bootstrap message: A BSR generates a Bootstrap message and floods it in the whole
PIM domain to advertise the information of the candidate RP set to all PIM routers.
Meanwhile, BSR election is performed. All PIM routers need to forward this message
to all PIM routers after they pass through the RPF check.
Assert message: When there are several routers on a multi-access network and a
multicast group packet is received on an egress interface of a router, it is necessary
to use the Assert message to designate a unique forwarder.
Candidate-RP-Advertisement:
A
candidate
RP
unicasts
Candidate-RP-Advertisement to the BSR periodically to advertise the set of group
addresses served by the Candidate RP.
5.3 Configuring PIM-SM

To configure PIM-SM on ZXR10 M6000, perform the following steps.
Step
Command
Function
This enables PIM-SM.
ZXR10(config-mcast)#no router pimsm
This disables PIM-SM.
ZXR10(config-pimsm)#static-rp < ip-address> [ group-list <
This configures a static RP.
prifix-list-name> ] [ priority < priority> ]

This deletes a static RP.
ZXR10(config-pimsm)#no static-rp
This configures the overriding of a
ZXR10(config-pimsm)#static-rp override
static RP.
This deletes the overriding of a static
ZXR10(config-pimsm)#no static-rp override
RP.
ZXR10(config-pimsm)#interface < interface-name>
This enters multicast interface

configuration mode.
ZXR10(config-pimsm)#no interface < interface-name>
This disables PIM-SM on an

interface.
ZXR10(config-pimsm)#bsr-candidate < interface-name> [ <
This configures a candidate BSR.
hash-mask-length> ] [ < priority> ]

This deletes a candidate BSR.
ZXR10(config-pimsm)#no bsr-candidate
5-3
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-pimsm)#rp-candidate < interface-name> [ group-list
This configures a candidate RP.
< prefix-list_name > ] [ priority < priority> ]

ZXR10(config-pimsm)#no rp-candidate < interface-name>
This deletes a candidate RP.
ZXR10(config-pimsm)#spt-threshold infinity [ group-list <
This configures handover of the SPT.
prefix-list-name > ]
ZXR10(config-pimsm)#accept-register < access-list-name >
This configures the filter policy of

Register messages.
This disables the filter policy of
ZXR10(config-pimsm)#no accept-register
Register messages.
ZXR10(config-pimsm)#accept-rp < access-list-name>
This filters the candidate RP

addresses advertised in the
Bootstrap messages.
This disables to filter the candidate
ZXR10(config-pimsm)#no accept-rp
RP addresses.
ZXR10(config-pimsm)#dr-switchback-delay < seconds>
This configures the delay for route

calculation when the DR becomes
non-DR after BFD is enabled on an
interface.
This configures to calculate route
ZXR10(config-pimsm)#no dr-switchback-delay
immediately after the DR is changed.

3
This enables PIM-SM on an
ZXR10(config-pimsm-if)#pimsm
interface.
This disables PIM-SM on an
ZXR10(config-pimsm-if)#no pimsm
interface.
ZXR10(config-pimsm-if)#dr-priority < priority>
This configures the DR priority on a

PIM interface.
ZXR10(config-pimsm-if)#no dr-priority
This restores the default DR priority.
ZXR10(config-pimsm-if)#bsr-border
This sets an interface to the border

of the PIM domain.
This cancel the configuration of the
ZXR10(config-pimsm-if)#no bsr-border
PIM domain.
ZXR10(config-pimsm-if)#hello-interval < seconds>
This configures the interval to send

Hello messages.
This restores the default interval to
ZXR10(config-pimsm-if)#no hello-interval
send Hello messages.

ZXR10(config-pimsm-if)#neighbor-filter < access-list-name >
This restricts PIM-SM neighbors.
5-4
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-pimsm-if)#no neighbor-filter
This cancels the restriction of

PIM-SM neighbors.
This disables the asserting function
ZXR10(config-pimsm-if)#assert-disable
on an interface.
This recovers the asserting function
ZXR10(config-pimsm-if)#no assert-disable
on an interface.
ZXR10(config-pimsm-if)#bfd-enable
This enables BFD on an interface.
ZXR10(config-pimsm-if)#no bfd-enable
This disables BFD on an interface.
ZXR10(config-pimsm)#data-filter[ < access-list-name > ]
This enables source address filter.
ZXR10(config-pimsm)#no data-filter[ < access-list-name > ]
This disables source address filter.

Parameter
Description
< ip-address>
Static RP address, in the dotted decimal notation
< prifix-list-name>
Group range in which the RP provides services
< hash-mask-length>
Hash mask length, in the range of 032
< access-list-name>
ACL name, with 131 characters

Parameter
Description
< seconds>
The interval to send Hello messages on a PIM router. It is in the range of

165535, in the unit of second. The default value is 30 seconds.
5.4 PIM-SM Maintenance

ZXR10 M6000 provides the following commands to maintain PIM-SM.
Command
Function
ZXR10#show ip pimsm mroute [ group < group-address> ] [ source <
This shows the PIM-SM routing table.
source-address> ]
This shows the summary information of
ZXR10#show ip mroute summary
the routing table.

ZXR10#show ip pimsm bsr
This shows the information of the BSR.
ZXR10#show ip pimsm rp mapping
This shows the RP mapping information

advertised by the BSR.
5-5
SJ-20110504161056-014|2010-05-10 (R2.1)
Command
Function
ZXR10#show ip pimsm rp hash < group-address>
This shows the RP information selected

by a specific multicast group.
ZXR10#show ip pimsm interface [ < interface-name> ]
This shows the interface on which

PIM-SM is configured.
ZXR10#show ip pimsm neighbor [ < interface-name> ]
This shows the neighbor information of

a PIM-SM interface.
This shows the PIM-SM next hop
ZXR10#show ip pimsm nexthop
information.
ZXR10#show ip pimsm rpf < source-address>
This shows the PIM-SM RPF

information.
Parameter
Description
< group-address>
Multicast group address, in the dotted decimal notation
< source-address>
Source address, in the dotted decimal notation
< interface-name>
Interface name
An example of the show ip pimsm mroute command output is shown below.

ZXR10#show ip pimsm mroute
PIMSM Multicast Routing Table
Flags: T- SPT-bit set,A- Forward,J- Join SPT,U- Upsend ,
Macro state: Ind- Pim Include Macro,Exd- Pim Exclude Macro,
Jns- Pim Joins Macro,LAst- Pim Lost_assert Macro,
Imo- Pim Immediate_olist Macro,Ino- Pim Inherited_olist Macro,
Lcd- Pim Local_receiver_include Macro
Timers:Uptime/Expires(Upstream State)
(*, 224.0.1.40), 00:01:18/00:00:00(JOINED), RP address: 0.0.0.0,
Ind: 1/Jns: 0/LAst: 0/Imo: 1/Lcd: 1
Iif: NULL, RPF nbr: 0.0.0.0
Oif:
fei-0/1/0/1,
LocalIn
ImoXG

Oif:
fei-0/1/0/2,
LocalIn
ImoXG

Oif:
5-6
SJ-20110504161056-014|2010-05-10 (R2.1)

fei-0/1/0/2,
LocalIn
ImoXG

Command Output
Description
Connected
Indicates that there is a member of this multicast group or this interface
Pruned
Indicates that the egress of the route entities is null
RP-bit set
Indicates that this (S, G) is on the shared tree
Register flag
Indicates that Register messages connecting to the source directly can

be sent through this entity
SPT-bit set
Indicates that this route entity receives multicast packets from the SPT
Up Send
Indicates that multicast packets are sent to this entity
Join SPT
Indicates that traffic received is handed over to the SPT
Uptime/Expires
Uptime or expiring time of the entity/egress interface
RP
The RP corresponding to *, G generated by PIM-SM
flag
The state of multicast route entities
Incoming interface
Incoming interface
RPF nbr
RPF neighbor of corresponding entity
An example of the show ip mroute summary command output is shown below.

ZXR10#show ip pimsm mroute summary
PIMSM Multicast Routing Table Summary
(*, G):3 , (S, G):0, (S, G, rpt):0, Register:0
(*, 224.0.1.40) (JOINED), RP: 1.1.1.10
(*, 224.1.1.1) (JOINED), RP: 1.1.1.10
(*, 224.1.1.2) (JOINED), RP: 1.1.1.10
An example of the show ip pimsm bsr command output is shown below.

ZXR10#show ip pimsm bsr
BSR address: 1.1.1.10

Uptime: 00:08:32, BSR Priority :0, Hash mask length:30
Expires:00:00:28
This system is a candidate BSR!

candidate BSR address: 1.1.1.10(fei-0/1/0/1),
priority: 0,
hash mask length: 30
5-7
SJ-20110504161056-014|2010-05-10 (R2.1)
This system is a candidate RP!

candidate RP address: 1.1.1.10(fei-0/1/0/1),priority:192

Command Output
Description
BSR address
IP address of the BSR
Uptime
Uptime of the BSR
BSR Priority
Priority of the BSR
Hash mask length
Mask length of the BSR
Expires
Expiring time of the BSR or of the BSR message
candidate BSR address
IP address of the candidate BSR configured locally
Priority
Priority of the candidate BSR configured locally
hash mask length
Mask length of the candidate BSR configured locally
CRP
IP address, interface number, priority and other information of the RP

configured locally
An example of the show ip pimsm rp mapping command output is shown below.

ZXR10#show ip pimsm rp mapping
Group(s): 224.0.0.0/4(SM)
RP: 1.1.1.10, v2, Priority:192
BSR: 1.1.1.10, via bootstrap
Uptime: 00:09:11, expires: 00:01:42
Group(s): 0.0.0.0/0(NOUSED)

Command Output
Description
Group
Address and mask of the multicast group advertised by the BSR
RP address
Address, version, priority and other information of the candidate RP

advertised by the multicast group
BSR address
IP address of the BSR
uptime
Uptime of the candidate RP
expire
Expiring time of the candidate RP
An example of the show ip pimsm rp hash command output is shown below.

ZXR10#show ip pimsm rp hash 224.0.1.40
rp address: 1.1.1.10
5-8
SJ-20110504161056-014|2010-05-10 (R2.1)

Command Output
Description
RP address
RP address selected by a specific multicast group
An example of the show ip pimsm interface command output is shown below.

ZXR10#show ip pimsm interface
Address
Interface
State Nbr
Hello
Count
Period
DR
DR
Priority
1.1.1.10
fei-0/1/0/1
Up
30
1.1.1.10
2.2.2.10
fei-0/1/0/2
Up
30
2.2.2.10

Command Output
Description
Address
Interface address
Interface
Interface name
NbrCount
Number of neighbors
State
Interface state
Hello Period
Interval to send Hello messages
DR Priority
DR priority of this interface
DR
The DR of the interface
An example of the show ip pimsm neighbor command output is shown below.

ZXR10#show ip pimsm neighbor
Neighbor Address
Interface
DR
Uptime
Expires
Ver
00:15:08
00:01:24
V2
Priority
1.1.1.1
fei-0/1/0/1

Command Output
Description
Neighbor Address
IP address of the neighbor
Interface
Interface name
DR Priority
DR priority of the neighbor
Uptime
Uptime of the neighbor
Expires
Expiring time of the neighbor
Ver
Version
An example of the show ip pimsm nexthop command output is shown below.

5-9
SJ-20110504161056-014|2010-05-10 (R2.1)

ZXR10#show ip pimsm nexthop
PIMSM Nexthop Table
Nexthop state: R- Nexthop to RP,S- Nexthop to Source,
O- Related with Unicast,U- No Unicast Route,
L- Local Route,C- Connect to Dest,
Nexthop:1.1.1.10
(00:02:59)
Type:.R. .O. .L.

Metric:0
Preference:0
Nexthop address:1.1.1.10(is Local)
Nexthop port:fei-0/1/0/1
Nexthop:1.1.2.1
(00:03:27)
Type:. . . .U. .
Metric:
Preference:
Nexthop address:
Nexthop port:

Command Output
Description
Next-hop Address
IP address of the next hop
Type
Type of the next hop route
Metric
Route metric of the next hop
Preference
Route priority of the next hop
Next-hop port
Port number of the next hop
An example of the show ip pimsm rpf command output is shown below.

ZXR10#show ip pimsm rpf 1.1.1.10
RPF information:
RPF interface is fei-0/1/0/1(pimsm)
RPF neighbor is 1.1.1.10(local)
RPF metric preference is 0
RPF metric value is 0

Command Output
Description
RPF interface
RFP interface to the source address
RPF neighbor
RFP neighbor to the source address
RPF metic preference
Route priority to the source address
RPF metric
Route metric to the source address

5-10
SJ-20110504161056-014|2010-05-10 (R2.1)
5.5 PIM-SM Configuration Examples

5.5.1 Forwarding Multicast Flow through PIM-SM (Dynamic RP)
As shown in Figure 5-1, an IGMP group connects to R2, and a multicast source connects
to R1. Configure a BSR and a candidate RP.
Figure 5-1 Forwarding Multicast Flow through PIM-SM (Dynamic RP)
1.
2.
3.
4.
5.
6.
Configure corresponding interfaces.

Enter PIM-SM configuration mode.
Set the loopback5 interface of R2 to the CRP and the BSR.
Enable PIM-SM on interfaces.
Configure a unicast route to the RP on R1. Configure a unicast route to the multicast
source on R2 (In this example, static route is used. IGP can also be configured to
make the path through).
R1(config-if)#exit
R1(config-if)#exit
R1(config-pimsm)#interface gei-0/2/0/3
R1(config-pimsm-if)#dr-priority 20
R1(config)#ip route 5.5.5.35 255.255.255.255 199.1.1.2
5-11
SJ-20110504161056-014|2010-05-10 (R2.1)

R2(config-if)#exit
R2(config-if)#exit
R2(config-pimsm)#rp-candidate loopback5
R2(config-pimsm)#bsr-candidate loopback5
R2(config)#ip route 33.1.1.0/24 255.255.255.0 199.1.1.1
R2(config-pimsm)#show ip mroute
(*, 225.10.0.1), RP: 6.6.6.35, TYPE: DYNAMIC, FLAGS:
Incoming interface: NULL, flags:
gei-0/3/0/7, flags: F
gei-0/3/0/7, flags:
Use the show ip pimsm interface command on R1 to check the interface state, as shown
below.
R1(config)#show ip pimsm interface
Address
Interface
State
Nbr
Hello
Count
Period
DR
DR
Priority
33.1.1.1
gei-0/2/0/7
Up
30
20
33.1..1.1
199.1.1.1
gei-0/2/0/3
Up
30
199.1.1.2
Use the show ip pimsm neighbor command on R1 to check the neighbor state, as shown
below.
R1(config)#show ip pimsm neighbor
Neighbor Address
Interface
DR
Uptime
Expires
Ver
00:01:23
V2
Priority
199.1.1.2
gei-0/2/0/3
00:07:48
Use the show ip pimsm bsr command on R1 to check the BSR state, as shown below.
5-12
SJ-20110504161056-014|2010-05-10 (R2.1)

R1(config)#show ip pimsm bsr
BSR address: 5.5.5.35
Uptime: 00:00:40, BSR Priority :0, Hash mask length:30
Expires:00:01:30
No candidate RP information!
R1(config)#show ip pimsm rp mapping
Group(s): 224.0.0.0/4(SM)
RP: 5.5.5.35, v2, Priority:192
BSR: 5.5.5.35, via bootstrap
Uptime: 00:00:43, expires: 00:01:47
5.5.2 Forwarding Multicast Flow through PIM-SM (Static RP)

As shown in Figure 5-2, an IGMP group connects to R2, and a multicast source connects
to R1. Configure PIM-SM neighbors and static RP.
Figure 5-2 Forwarding Multicast Flow through PIM-SM (Static RP)
1.
2.
3.
4.
5.

Enter PIM-SM configuration mode.
Set 5.5.5.35 as a static RP, and configure static RP overriding.
Enable PIM-SM on interfaces.
Configure a unicast route to the RP on R1. Configure a unicast route to the multicast
source on R2 (In this example, static route is used).
R1(config-if)#exit
R1(config-if)#exit
5-13
SJ-20110504161056-014|2010-05-10 (R2.1)

R1(config-pimsm)#static-rp 5.5.5.35
R1(config-pimsm)#static-rp overrid
R1(config)#ip route 5.5.5.35 255.255.255.255 199.1.1.2

R2(config-if)#exit
R2(config-if)#exit
R2(config-pimsm)#static-rp 5.5.5.35
R2(config-pimsm)#static-rp overrid
R2(config)#ip route 33.1.1.0/24 255.255.255.0 199.1.1.1
Use the show ip pimsm interface command on R1 to check the interface state, as shown
below.
R1(config)#show ip pimsm interface

Address
Interface
State
33.1.1.1
gei-0/2/0/7
Up
199.1.1.1
gei-0/2/0/3
Up
Nbr
Hello
DR
DR
Count
Period
Priority
30
20
33.1..1.1
30
199.1.1.2
Use the show ip pimsm neighbor command on R1 to check the neighbor state, as shown
below.
R1(config)#show ip pimsm neighbor
Neighbor Address
Interface
DR
Uptime
Expires
Ver
5-14
SJ-20110504161056-014|2010-05-10 (R2.1)

Priority
199.1.1.2
gei-0/2/0/3
00:07:48
00:01:23
V2
Use the show ip pimsm rp mapping command on R1 to check the RP state, as shown
below.
R1(config)#show ip pimsm rp mapping
Static RP is overriding in group-set!
Group(s): 224.0.0.0/4(SM)
RP: 5.5.5.35, Static, Priority:192
5.5.3 Illegal Multicast Source Control

Multicast protocol does not provide any control of the multicast source validity. Any user
can work as the multicast source to send multicast traffic to the networks. Illegal multicast
source filter can be configured to prevent unauthorized multicast sources from sending
multicast traffic to the networks.
As shown in Figure 5-3, Source 1 sends multicast data to the user. There are another two
illegal multicast sources (Source 2 and Source 3) sending multicast data to the network.
To prevent the data sent by Source 2 and Source 3 from being transmitted on the network,
it is necessary to configure illegal source control policies on the first-hop router and the RP.
Figure 5-3 Illegal Multicast Source Control
1. Configure source filter on the first-hop router.
2. Configure source register filter on the RP.
5-15
SJ-20110504161056-014|2010-05-10 (R2.1)
Note:
The illegal source control policy consists of the source filter configured on the first-hop
router and the source register filter configured on the RP. The source filter configured on
the first-hop router can prevent illegal sources from sending multicast data to the network
as early as possible. The source register filter configured on the RP can prevent illegal
sources from registering on the RP. It is easy to configure and manage if the method that
configuring source register filter on the RP is used. However, the traffic sent by the illegal
sources is still transmitted between the first-hop router and the RP, and the users on the
first-hop router still can receive the illegal multicast data. In practical applications, the two
methods are used together, which can improve the management efficiency and network
security.
Configure IP addresses on the interfaces of R1 and R2 according to the following table to
ensure the IP connectivity on the network.
Router
Interface
IP Address
Mask
R1
gei-0/15/0/1
172.1.3.44
255.255.255.0
R1
gei-0/15/0/2
172.2.3.44
255.255.255.0
R1
gei-0/15/0/3
172.3.3.44
255.255.255.0
R1
gei-0/15/1/3
172.1.7.44
255.255.255.0
R1
loopback63
44.63.1.1
255.255.255.255
R2
gei-0/3/1/8
172.1.5.46
255.255.255.0
R2
gei-0/6/0/2
172.1.7.46
255.255.255.0
R2
loopback63
46.63.1.1
255.255.255.255
Configure a multicast protocol on R1 and R2 to establish a multicast tree from the source
to the user. Here take PIM-SM as an example.
The configuration of R1 (enable PIM-SM on the interfaces, and configure a BSR on
loopback63 interface):
5-16
SJ-20110504161056-014|2010-05-10 (R2.1)

The configuration of R2 (enable PIM-SM on the interfaces, and configure an RP on

Configure illegal source control policies on R1 and R2.

The configuration of the source filter policy on R1:
R1(config)#ipv4-access-list aclUnwantedSource
R1(config-ipv4-acl)#rule deny ip 172.2.3.44 0.0.0.0 any
R1(config-ipv4-acl)#rule permit ip any any
R1(config-pimsm)#data-filter aclUnwantedSource
The configuration of the source register filter policy on R2:

R2(config)#ipv4-access-list aclWantedSource
R2(config-ipv4-acl)#rule deny ip 172.3.3.44 0.0.0.0 any
R2(config-ipv4-acl)#rule permit ip any any
R2(config-pimsm)#accept-register aclWantedSource
Use the show ip mroute command on R1 and R2 to check the multicast routes. Because
control policies are configured on R1 and R2, only multicast data sent by the legal source
can be forwarded to the user. The multicast traffic received by the user does not include
the data sent by the illegal sources.
According to the above configurations, there is still a route of Source 3. However, because
illegal source register filter policy for Source 3 is configured on the RP, the multicast traffic
from Source cannot reach the user.
5-17
SJ-20110504161056-014|2010-05-10 (R2.1)
The multicast routes on R1 are shown below.

R1#show ip mroute
The multicast routes on R2 are shown below.

R2#show ip mroute
gei-0/3/1/8, flags:
5.5.4 Anycast-RP Configuration Example

As shown in Figure 5-4, it is required to run OSPF on RA, RB and RC, and it is required
to configure an anycast-RP.
5-18
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 5-4 Anycast-RP Configuration Example
1. Configure OSPF on RA, RB and RC. RA and RB can communicate through unicast
routes. RA and RC can communicate through unicast routes.
2. Configure PIMSM on RB and RC, and configure an anycast-RP.
The configuration of RB:
ZXR10(config)#interface gei-0/0/0/1
ZXR10(config-if)#ip address 11.1.1.2 255.255.255.0
ZXR10(config)#router ospf 1
ZXR10(config-ospfv2)#network 11.1.1.0 0.0.0.255 area 0
ZXR10(config)#interface loopback64
ZXR10(config-pimsm)#rp-candidate loopback64
ZXR10(config-pimsm)#bsr-candidate loopback64
ZXR10(config-pimsm)#anycast-rp-local loopback64
/*Configure an anycast-RP*/
ZXR10(config-pimsm)#anycast-rp-peer 64.1.1.1
5-19
SJ-20110504161056-014|2010-05-10 (R2.1)

ZXR10(config-pimsm)#anycast-rp-peer 64.1.1.1
ZXR10(config-pimsm)#interface gei_0/0/0/2
The configuration of RC:

ZXR10(config)#interface gei_0/0/0/1
ZXR10(config)#interface gei_0/0/0/2
ZXR10(config-pimsm)#bsr-candidate loopback64
ZXR10(config-pimsm)#anycast-rp-local loopback64
ZXR10(config-pimsm)#anycast-rp-peer 64.1.1.1 /*Configure an Anycast-RP*/
For the configuration of the switch, please refer to the configuration of RB and RC. It is
necessary to enable PIM-SM.
The receiver joins the IP multicast group. An RP is chosen randomly between RB and
RC to forward the Register message. If the chosen link is down, traffic will be forwarded
through the other link.
5.6 PIM-SM Fault Handling

The network topology of a PIM-SM fault is shown in Figure 5-5.
5-20
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 5-5 Network Topology of a PIM-SM Fault

After PIM-SM is configured, the multicast source sends flows to the joining group. If the
path is not through, analyze the fault in hardware and software aspects. In the hardware
aspect, check the network wires, optical modules, line cards, and so on. If it is certain that
the hardware has no problem, analyze the fault in the aspect of configuration and software.
Check the PIM-SM configuration, unicast route configuration, BSR, RP, the first-hop router,
the last-hop router, and so on.
5.6.3 Handling Flow

The flow to handle a PIM-SM fault is shown in Figure 5-6.
5-21
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 5-6 Flow to Handle a PIM-SM Fault

The procedure to handle a PIM-SM fault is described below.
5-22
SJ-20110504161056-014|2010-05-10 (R2.1)
1. Check whether the physical links are up. Change the cables and optical modules if
3. Check whether PIM-SM is enabled on corresponding interfaces, and whether PIM-SM
neighbor relationship can be established properly.
4. Check whether the BSR and the candidate RP are configured correctly. If static RP
is used, check whether it is configured on each router and whether static-override is
configured.
5. Use the show ip pimsm nexthop command to check whether the unicast routes are
configured correctly, including the unicast routes to the multicast source, RP, BSR,
and so on.
6. Check whether the first-hop and the last-hop routers are DRs. If they are not, modify
the DR priorities to make the DR as the first-hop and the last-hop routers.
7. Check whether filter is configured on interfaces and in multicast configuration. If it is
configured, modify the filter conditions or delete the filter configuration.
8. Use the debug ip pimsm command to analyze the fault.
5-23
SJ-20110504161056-014|2010-05-10 (R2.1)
This page intentionally left blank.
5-24
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 6
PIM-SSM Configuration
Table of Contents
PIM-SSM Overview ....................................................................................................6-1
PIM-SSM Principle .....................................................................................................6-1
Configuring PIM-SSM.................................................................................................6-1
PIM-SSM Configuration Example ...............................................................................6-2
PIM-SSM Fault Handling ............................................................................................6-4
6.1 PIM-SSM Overview

PIM-SSM has all advantages of PIM-SM. PIM-SSM does not construct a shared tree.
Instead, it only constructs the SPT. When receiving the member relation report messages
about a specific source and a group, PIM-SSM will construct the SPT directly.
6.2 PIM-SSM Principle

PIM-SSM is a subset of PIM-SM. PIM-SSM is suitable for the well known sources. It
is both intra-domain and inter-domain valid. PIM-SM uses Multicast Source Discovery
Protocol (MSDP) for inter-domain multicast routing. PIM-SSM does not need to use MSDP.
The multicast group address allocated for PIM-SSM is 232.0.0.0/8. The routers will not
construct a shared tree for this group address.
After a host sends a Join message from a specific source to a group, the last hop router
will send a (S, G) Join message to the direction of the source to construct a SPT. The last
hop router will not send a (*, G) Join message to the direction of RP. Once the SPT is
constructed, the first-hop router will forward packets along this tree.
6.3 Configuring PIM-SSM

To configure PIM-SSM on ZXR10 M6000, perform the following steps.
Step
Command
Dunction
ZXR10(config-pimsm)#ssm enable
This enables PIM-SSM.
ZXR10(config-pimsm)#no ssm enable
This disables PIM-SSM.
ZXR10(config-pimsm)#ssm range [ group-list < access-list-name > ]
This configures the address range of

PIM-SSM group.

6-1
SJ-20110504161056-014|2010-05-10 (R2.1)
Parameter
Description
< access-list-name >
ACL name, with 131 characters
6.4 PIM-SSM Configuration Example

As shown in Figure 6-1, PIM-SM is enabled on R1, and SSM is configured. Configure
the SSM group range (by default, it is 232.0.0.0/8). IGMP version is v3. The Tester 2
sends dynamic Join messages to the specific source. The Tester 1 sends flows to multicast
groups of multiple specific sources. Only the traffic matching both the source address and
the multicast group address is allowed to pass through.
Figure 6-1 PIM-SSM Configuration Example
1. In interface configuration mode, configure interface addresses on gei-0/1/0/1 and
gei-0/1/0/2 of R1.
2. Enable IP multicast function with ip multicast-routing command.
3. Enter PIM-SM route configuration mode to configure ssm enable and ssm range default.
4. Enter the interfaces gei-0/1/0/1 and gei-0/1/0/2 to enable PIM-SM.
5. Enter IGMP route configuration mode and then enter the corresponding interfaces.
Configure IGMP v3 on the interfaces.
6. Send dynamic group Join messages to specific source on the receiving group.
7. Configure a static route on the router. The destination of the route is the source
address gateway, and the next hop is the address of the interface connecting to
gei-0/1/0/2 directly on the receiving group.
R1(config-if)#exit
6-2
SJ-20110504161056-014|2010-05-10 (R2.1)

R1(config-if)#exit
R1(config-pimsm)#intererface gei-0/1/0/1
R1(config-pimsm)#ssm enable
R1(config-pimsm)#ssm range default
R1(config-igmp)#interface gei-0/1/0/2
R1(config)#ip route 15.1.1.0 255.255.255.0 30.0.0.2
Check the configuration on R1, as shown below.
R1#show running-config multicast
! <MULTICAST>
router pimsm
ssm enable
ssm range default
interface gei-0/1/0/2
pimsm
$
pimsm
$
$
router igmp
version 3
$
$
! </MULTICAST>
Check the result on R1, as shown below.

R1#show ip mroute
(15.1.1.1, 232.0.0.1), RP: 0.0.0.0, TYPE: DYNAMIC, FLAGS: NS
Incoming interface: int2, flags: NS
int1, flags: F
/*Generating (S,G) entity*/
6-3
SJ-20110504161056-014|2010-05-10 (R2.1)
6.5 PIM-SSM Fault Handling

The network topology of a PIM-SSM fault is shown in Figure 6-2.
Figure 6-2 Network Topology of a PIM-SSM Fault

Symptom: IGMPv3 is configured. SSM static group joining is configured on the interfaces.
The data source sends flows to the static group. The receiver cannot receive flows
properly.
6.5.3 Handling Flow

The flow to handle a PIM-SSM fault is shown in Figure 6-3.
6-4
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 6-3 Flow to Handle a PIM-SSM Fault

The procedure to handle a PIM-SSM fault is described below.
1. Check whether PIM-SM is enabled on the interfaces.
2. Check whether PIM-SSM is enabled in PIM-SM configuration mode.
3. Check whether the SSM range is configured in PIM-SM configuration mode (by default,
the group range is 232.0.0.0/8).
4. Check whether the source is configured for the static group on IGMP interface.
5. Check whether the data source and the designated source are consistent.
6-5
SJ-20110504161056-014|2010-05-10 (R2.1)
6-6
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 7
Multicast Load Sharing

Configuration
Table of Contents
Multicast Load Sharing Overview ...............................................................................7-1
Multicast Load Sharing Principle.................................................................................7-1
Configuring Multicast Load Sharing ............................................................................7-2
Multicast Load Sharing Maintenance ..........................................................................7-2
Multicast Load Sharing Configuration Example...........................................................7-3
Multicast Load Sharing Fault Handling .......................................................................7-6
7.1 Multicast Load Sharing Overview

A router forwards IP packets according to the IP routing table. In a routing table, when
there are several paths to the same destination prefix, the priorities of the paths may be
the same or different. A router always selects the routes with the highest priority as the
action path. When there are several path with the same highest priority, the router can
share the traffic to the destination prefix on the paths to perform load sharing.
7.2 Multicast Load Sharing Principle

In multicast applications, there may be a network structure that is shown in Figure 7-1.
On this network, the RPF routes from Router 2 to Source 1 and Source 2 are Equal-Cost
Muti-Path routing (ECMP) corresponding to egress I0 and I1 respectively. When multicast
finds the route to Source 1, it may select an equal-cost route (assume that the egress is
I0), and then this routes is recorded. The next time when the protocol triggers to search
for the routes to Source 1, PIM searches the route among the unicast routes recorded
locally. In this way, each time the egress is I0 and all traffic goes through the same route.
However, the other routes is idle.
7-1
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 7-1 Multicast Load Sharing Principle
To solve the problem described above, L3 multicast load sharing solution is introduced.
7.3 Configuring Multicast Load Sharing

To configure multicast load sharing on ZXR10 M6000, use the following commands.
Command
Function
ZXR10(config-mcast)#multipath
This enables load sharing according to

the Hash algorithm based on source
address.
ZXR10(config-mcast)#multipath s-g-hash basic

address and multicast address.
ZXR10(config-mcast)#multipath s-g-hash next-hop-based

address, multicast address and next
hop.
This disables multicast load sharing.
ZXR10(config-mcast)#no mulpath
7.4 Multicast Load Sharing Maintenance

ZXR10 M6000 provides the following command to maintain multicast load sharing.
Command
Function
ZXR10#show ip mroute nexthop [ < destination-address> ] [ vrf< vrf-name> ]
This shows the information of multicast

next hop and ECMP.
Parameter
Description
< destination-address>
Destination address, in the dotted decimal notation
vrf< vrf-name>
VRF name, with 1-32 characters

7-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 7 Multicast Load Sharing Configuration
An example of the show ip mroute nexthop command output is shown below.

ZXR10(config)#show ip mroute nexthop
IP Multicast Nexthop Table
FLAG of ECMP: L:Local, C:Connect, S:Static
U:Unicast, UR:Unicast unreachable, UG:Unicast no response
SUR:Static unreachable, SNR:Static nexthop should be replaced
Dest address: 10.40.50.24
Owner: /PIMDM
Flag : /U/UR/UG
Metric: 4294967295, Preference: 255

Ecmp list:
Owner: /PIMDM
Flag : /U
Ecmp list:
Nexthop: 1.1.1.4, Oif: fei-0/1/0/1
Nexthop: 123.1.1.2, Oif: fei-0/1/0/1.1
Nexthop: 123.2.1.2, Oif: fei-0/1/0/1.2
Nexthop: 123.3.1.2, Oif: fei-0/1/0/1.3

Command Output
Description
FLAG of ECMP
ECMP identifier. L: local; C: connection; S: static; U: unicast; UR:

unreachable unicast; UG: no response to unicast; SUR: static unreachable;
SNR: static next hop should be replaced.
7.5 Multicast Load Sharing Configuration Example

When there are multiple equal-cost routes from the source to the last hop router, multicast
load sharing can be configured to make traffic reach the user along different paths. As
shown in Figure 7-2, the source sends several groups of multicast traffic. There are two
paths form the last-hop router R2 to the source.
Figure 7-2 Multicast Load Sharing Configuration Example
Assume that the two routes are equal-cost for R2, that is, the two routes are equal-cost
routes between R2 and the source. Multicast load sharing can be configured on R2 to
make the multicast traffic reach the user along the two paths.
7-3
SJ-20110504161056-014|2010-05-10 (R2.1)
1. Configure PIM-SM, BSR and RP on the routers to make the user can receive the
multicast traffic sent by the source properly.
2. Configure multicast load sharing on the downstream router.
Router
Interface
IP Address
Mask
R1
gei-0/15/0/1
172.1.3.44
255.255.255.0
R1
gei-0/15/1/3
172.1.7.44
255.255.255.0
R1
gei-0/15/1/10
172.1.13.44
255.255.255.0
R1
loopback63
44.63.1.1
255.255.255.255
R2
gei-0/3/1/2
172.1.13.46
255.255.255.0
R2
gei-0/3/1/8
172.1.5.46
255.255.255.0
R2
gei-0/6/0/2
172.1.7.46
255.255.255.0
Configure multicast protocol on R and R2 to create a multicast tree. Here take PIM-SM as
an example.
The configuration of R1 (enable PIM-SM on the interfaces, and configure BSR and RP on
The configuration of R2 (Enable PIM-SM on the interfaces. Configure routes to BSR

and RP so that R2 can receive BSR packets properly and multicast routing table can be
created. Configure routes to the source, and make sure that there are two equal-cast
routes between R2 and the source):
7-4
SJ-20110504161056-014|2010-05-10 (R2.1)

R2(config)#ip route 44.63.1.1 255.255.255.255 172.1.7.44
R2(config)#ip route 172.1.3.0 255.255.255.0 172.1.7.44
R2(config)#ip route 172.1.3.0 255.255.255.0 172.1.13.44
Enable load sharing on R2, here take s-g-hash as an example.

R2(config-mcast)#multipath s-g-hash basic
When the user starts to receive the multicast traffic sent from the source, check the routing
tables on R1 and R2. Pay attention to the ingress and egress of the routes.
The multicast routing table on R1 is shown below:
R1#show ip mroute
gei-0/15/1/10, flags: F
The multicast routing table on R2 is shown below:

R2#show ip mroute
(*, 238.255.255.0), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS: NS
Incoming interface: gei-0/6/0/2, flags: NS
7-5
SJ-20110504161056-014|2010-05-10 (R2.1)

(*, 238.255.255.1), RP: 44.63.1.1, TYPE: DYNAMIC, FLAGS: NS
Incoming interface: gei-0/6/0/2, flags: NS
gei-0/3/1/8, flags:
7.6 Multicast Load Sharing Fault Handling

The network topology of a multicast load sharing fault is shown in Figure 7-3.
Figure 7-3 Network Topology of a Multicast Load Sharing Fault

After load sharing is configured on the downstream router R2, the traffic of different
groups is not shared on the links. Check whether multicast load sharing is configured
first. And then check whether the multicast routing protocol is configured correctly and
whether the multicast routing table is created properly. That the multicast routing protocol
works properly is the prerequisite to realize multicast load sharing.
If the multicast routing protocol works properly, check whether there are several equal-cost
routes between the source and the last-hop router. That there are several equal-cost
routes between the source and the last-hop router is the necessary condition to realize
multicast load sharing. A valid path means that the routers along this path work properly
and they can forward traffic properly.
If none of the fault mentioned above occurs, please ask for technical support.
7.6.3 Handling Flow

The flow to handle a multicast load sharing fault is shown in Figure 7-4.
7-6
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 7-4 Flow to Handle a Multicast Load Sharing Fault

The procedure to handle a multicast load sharing fault is described below.
1. Execute the show running-config multicast command to check whether multicast load
sharing is configured on the downstream router R2.
R2(config)#show running-config multicast
! <MULTICAST>
router pimsm
pimsm
$
pimsm
$
pimsm
$
$
router igmp
$
7-7
SJ-20110504161056-014|2010-05-10 (R2.1)

$
multipath s-g-hash basic /*multicast load sharing configuration*/
! </MULTICAST>
2. Execute the show running-config multicast command to check multicast configuration.

Check whether the protocol works properly, including whether the neighbor
relationship is established properly between routers, whether RP information is learnt,
whether there are unicast routes to the BSR and the RP, and whether multicast route
entities are formed.
3. Check whether there are equal-cost routes between the source and the last-hop router.
Execute the show ip mroute nexthop command on the last-hop router to check the
equal-cost route list to the source. If equal-cost routes exist but multicast traffic is not
shared, check whether the link is valid, that is, whether the multicast protocol on the
routers along the path works properly.
R2#show ip mroute nexthop
IP Multicast Nexthop Table
FLAG of ECMP: L:Local, C:Connect, S:Static
U:Unicast, UR:Unicast unreachable, UG:Unicast no response
SUR:Static unreachable, SNR:Static nexthop should be replaced
Owner: PIMSM
Flag : /U
Ecmp list:
Nexthop: 172.1.7.44, Oif: gei-0/6/0/2
Nexthop: 172.234.7.44, Oif: gei-0/6/0/2.3962
Owner: PIMSM
Flag : /U
Ecmp list:
Nexthop: 172.1.7.44, Oif: gei-0/6/0/2
Nexthop: 172.1.13.44, Oif: gei-0/3/1
7-8
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 8
Static Multicast
Configuration
Table of Contents
Static Multicast Overview ...........................................................................................8-1
Static Multicast Principle.............................................................................................8-1
Configuring Static Multicast ........................................................................................8-2
Static Multicast Maintenance ......................................................................................8-3
Static Multicast Configuration Example.......................................................................8-4
Static Fault Malfunction Handling ...............................................................................8-5
8.1 Static Multicast Overview

Static multicast route is applied when multicast is excepted to forward packets according
to the specific path instead of the unicast optimal path.
8.2 Static Multicast Principle

Static multicast provides egress and ingress for users to configure the multicast routing
table directly. It forms the multicast forwarding table according to the configuration of
users and synchronizes the multicast forwarding table with the line card. If there are static
multicast routes and dynamic multicast routes at the same time, static multicast routes are
preferred. The logical position of static multicast is equivalent to PIM-SM and PIM-DM, that
is, static multicast can be considered as a special multicast routing protocol. According to
the application environment, static multicast routes mainly has two functions.
1. Changing RPF routes
Generally, the network topology of multicast is the same with that of unicast, and the
transmission paths are also the same. Users can configure static multicast routes to
change the RPF routes, thus to create a transmission path for multicast packets that
is different from that of unicast.
2. Connecting with RPF routes
When the unicast routes in the network is blocked, multicast packets cannot be
forwarded as there is no RPF route. Users can configure static multicast routes
to generate RPF routes, thus to create multicast route entities to forward multicast
packets.
8-1
SJ-20110504161056-014|2010-05-10 (R2.1)
When creating multicast route entities, multicast routing protocols use RPF check
mechanism to make sure that multicast packets are transmitted along the correct path and
prevent loops caused by different reasons. RPF mechanism uses the multicast source
address as the destination and selects an optimal route from the unicast routing table,
the MBGP routing table and the static multicast routing table respectively. If the longest
matching rule is configured, RPF mechanism will select the route that meets the longest
matching rule among the three routes. If the masks are the same, RPF mechanism will
select the route with the highest priority among the three routes. If the priorities are the
same, RPF mechanism will select the route in the order of static multicast route, MBGP
route and unicast route. The selected route is used as the RPF route, and RPF interfaces
and neighbors will be selected.
8.3 Configuring Static Multicast

To configure static multicast on ZXR10 M6000, perform the following steps.
Step
Command
Function
ZXR10(config-mcast)#ip multicast-static-start
This enables MSTATIC.
ZXR10(config-mcast)#no ip multicast-static-start
This disables MSTATIC.
ZXR10(config-mcast)#ip multicast-static-limit xg < xg-limit> sg
< sg-limit>
number of static multicast route
entities.
ZXR10(config-mcast)#no ip multicast-static-limit
This cancels the maximum number

of static multicast route entities.
ZXR10(config-mcast)#ip multicast-static-route < source-address> <
This configures a static multicast
group-address> [ iif< iif-name> ] [ oif< oif-index> ]
route entity.
ZXR10(config-mcast)#no ip multicast-static-route < source-address>
This deletes a static multicast route
< group-address> [ iif< iif-name> ] [ oif< oif-index> ]
entity.
ZXR10(config-mcast)#ip multicast-mstatic-interface index < index>
This configures the egress set of
[ interface < interface-name> ]
static multicast.
ZXR10(config-mcast)#no ip multicast-mstatic-interface index<
This deletes the egress set of static
index> [ interface < interface-name> ]
multicast.

Parameter
Description
< xg-limit>
The number of static multicast (*, G) route entities that is allowed. By

default, the number is 0.
< sg-limit>
The number of static multicast (S, G) route entities that is allowed. By

default, the number is 0.

8-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 8 Static Multicast Configuration
Parameter
Description
< group-address>
Specific multicast group address
< source-address>
Specific multicast source address
< iif-name>
Ingress interface name of the multicast routes
< oif-index>
Egress set index of the multicast route entities

Parameter
Description
< index>
The index of egress interface set
< interface-name>
The name of the interface to join the egress interface set
8.4 Static Multicast Maintenance

ZXR10 M6000 provides the following commands to maintain static multicast.
Command
Function
ZXR10#show ip multicast-static-interface [ index < index> ]
This shows the interfaces that are

effective in the egress interface set.
ZXR10#show ip multicast-static-route [ group < group-address> ] [ source
This shows the static multicast routing
< source-address> ]
table.
ZXR10#show ip multicast-static-route summary
This shows the statistics information of

the static multicast routing table.
An example of the show ip multicast-static-interface command output is shown below.

ZXR10#show ip multicast-static-interface
STATIC-MULTICAST OUT PORT INDEX 2:
Outgoing Interface: NULL
An example of the show ip multicast-static-route command output is shown below.

ZXR10#show ip multicast-static-route
The Capability of Static Multicast Route
(*, g) 10, (s, g) 10
(101.1.1.1, 224.1.1.1)
Incoming interface: NULL
An example of the show ip multicast-static-route summary command output is shown below.

ZXR10#show ip multicast-static-route summary
IP Static Multicast Routing Table Summary
(*,G): 0 routes
8-3
SJ-20110504161056-014|2010-05-10 (R2.1)

(S,G): 1 routes
Total: 1 routes
8.5 Static Multicast Configuration Example

As shown in Figure 8-1, a static multicast route with the source 33.1.1.2 and destination
225.10.0.1 is configured to forward multicast flows properly.
Figure 8-1 Static Multicast Configuration Example
1.
2.
3.
4.
5.
6.
Configure interface IP addresses

Enter multicast mode
Enable static multicast
Configure the maximum number of static multicast (*, G) routes and (S, G) routes
Configure the egress interface list of static multicast
Configure the detail static multicast route
R1(config-mcast)#ip multicast-static-start
R1(config-mcast)#ip multicast-static-limit xg 1024 sg 1024
R1(config-mcast)#ip multicast-static-interface index 2 interface
gei-0/3/0/6
R1(config-mcast)#ip multicast-static-route 33.1.1.2 225.10.1.2
iif gei-0/3/0/7 oif 2
Check the static multicast information on R1 with the show ip multicast-static-interface
command, as shown below.
R1(config)#show ip multicast-static-interface
STATIC-MULTICAST OUT PORT INDEX 100:
Outgoing Interface:
gei-0/3/0/6
8-4
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 8 Static Multicast Configuration

R1 (config)#show ip multicast-static-route
The Capability of Static Multicast Route
(*, g) 1024, (s, g) 1024
(33.1.1.2, 225.10.1.2)
Incoming interface: gei-0/3/0/7

gei-0/3/0/6
R1(config)#show ip mroute
(33.1.1.2, 225.10.1.2), RP: 0.0.0.0, TYPE: STATIC, FLAGS:
gei-0/3/0/6, flags:
8.6 Static Fault Malfunction Handling

The network topology of a static multicast fault is shown in Figure 8-2.
Figure 8-2 Network Topology of a Static Multicast Fault

After static multicast is configured, the multicast source sends flows to the group. If the
path is not through, analyze the fault in hardware and software aspects. In the hardware
aspect, check the network wires, optical modules, line cards, and so on. If it is certain that
the hardware has no problem, analyze the fault in the aspect of configuration and software.
8.6.3 Handling Flow

The flow to handle a static multicast fault is shown in Figure 8-3.
8-5
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 8-3 Flow to Handle a Static Multicast Fault

The procedure to handle a static multicast fault is described below.
1. Check whether physical links are up. Change the cables and optical modules if
3. Check whether the ingress interface and the egress interface are configured correctly.
8-6
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 9
MSDP Configuration
Table of Contents
MSDP Overview.........................................................................................................9-1
MSDP Principle ..........................................................................................................9-1
Configuring MSDP......................................................................................................9-2
MSDP Maintenance ...................................................................................................9-5
MSDP Configuration Examples ..................................................................................9-7
MSDP Fault Handling ...............................................................................................9-14
9.1 MSDP Overview

Multicast Source Discovery Protocol (MSDP) is a mechanism to connect multiple PIM-SM
domains. It works over the Transfer Control Protocol (TCP) and provides multicast source
information outside the PIM domains for PIM-SM.
9.2 MSDP Principle

MSDP is a mechanism that makes RPs in different PIM domains share active source
information. RP knows the receiver in local domain, so RP will forward the information
to the receiver when it obtains the active source information in remote domain. In this way,
multicast packets are forwarded between domains.
The MSDP speaker in a PIM-SM domain establishes MSDP neighbor sessions with
other MSDP neighbors through TCP connection. When the MSDP speaker learns a new
multicast source in its domain (through PIM Register mechanism), it generates and sends
a Source Active (SA) message to all MSDP neighbors.
Each MSDP neighbor receiving the message checks the SA message through neighbor
RPF. The MSDP neighbor only forwards SA message received on the correct interface.
Other SA messages will be discarded. If the MSDP neighbor receiving the SA message
is the RP in the local domain, and the egress interface on the RP corresponding to the (*,
G) entity in the multicast group contained in the SA message is not null (that is, a receiver
exists in this domain), the RP will create a (S, G) state for the multicast source and add it
into the SPT of the multicast source.
In Addition, each MSDP neighbor caches the received SA messages to establish an SA
cache table. If the RP in a PIM-SM domain receives the PIM Join message from a new
multicast group G, the RP will search its SA cache table to get all active multicast sources
and generate the corresponding (S,G) Join message.
9-1
SJ-20110504161056-014|2010-05-10 (R2.1)
Although MSDP is developed as a inter-domain multicast protocol, it has a special

application in a PIM-SM domain, that is, anycast RP. Anycast RP means to set two or
more RPs with the same address in the same PIM-SM domain and establish MSDP peer
relationship between these RPs. This is to realize load sharing and redundancy for the
RPs in the domain.
9.3 Configuring MSDP

To configure MSDP on ZXR10 M6000, use the following commands.
Command
Function
ZXR10(config-mcast)#router msdp
This enables MSDP.
ZXR10(config-mcast)#no router msdp
This disables MSDP.
9.3.1 Configuring an MSDP Neighbor

To configure an MSDP neighbor on ZXR10 M6000, perform the following steps.
Step
Command
ZXR10(config-msdp)#peer < peer-address>
Function
This configures an MSDP neighbor
and enters PEER configuration
mode. The parameter <
peer-address> is the IP address
of the MSDP neighbor.
ZXR10(config-msdp)#default-peer < peer-address> [ list <
This defines a default MSDP
access-list-name> ]
neighbor. The local router will

receive all SA messages from this
neighbor.
This shut down an MSDP that has
ZXR10(config-msdp-peer)#shutdown
be configured. By default, an MSDP

neighbor is not shut down.
4
ZXR10(config-msdp-peer)#mesh-group < mesh-name>
This set a specific MSDP neighbor

to a mesh group member. The
parameter < mesh-name> is the
name of the mesh group, within 32
characters. By default, an MSDP
neighbor does not belong to any
mesh group.
9.3.2 Configuring MSDP Extended Functions

To configure MSDP extended functions on ZXR10 M6000, perform the following steps.
9-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-msdp-peer)#description < peer-address> < desc-text>
This configures description for an

MSDP neighbor.
ZXR10(config-msdp)#originator-id < interface-name>
This sets the IP address on a specific

interface as the RP address in the
SA messages.
ZXR10(config-msdp-peer)#sa-limit < peer-address> < sa-limit>
This limits the number of SA

messages from a specific MSDP
neighbor in the SA cache table. By
default, there is no limit.
ZXR10(config-msdp-peer)#ttl-threshold < ttl-value>
This limits the range of the multicast

packets that are encapsulated in SA
messages sent to MSDP neighbors.

Parameter
Description
< peer-address>
IP address of an MSDP neighbor
< desc-text>
Description for an MSDP neighbor, within 80 characters

Parameter
Description
< interface-name>
Interface name

Parameter
Description
< peer-address> < sa-limit>
The maximum number of SA messages that are allowed from a specific

MSDP neighbor in the SA cache table, in the range of 1-2147483646

Parameter
Description
< ttl-value>
TTL value, in the range of 0-255, with the default value 0
9.3.3 Configuring an MSDP Policy

To configure an MSDP policy on ZXR10 M6000, perform the following steps.
9-3
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-msdp)#redistribute [ list < access-list-name> ]
This configures an ACL. Only the

(S, G) multicast route entities that
meet the rules will appear in the
SA messages generated by an
MSDP neighbor. The parameter <
access-list-name> is the ACL name,
with 1-31 characters.
ZXR10(config-msdp-peer)#sa-filter in [ list < access-list-name> ]
This filters the SA messages

received from specific MSDP
neighbors. The parameter <
access-list-name> is the ACL name,
with 1-31 characters.
ZXR10(config-msdp-peer)#sa-filter out [ list < access-list-name> ]
This filters the SA messages sent

to specific MSDP neighbors. The
parameter < access-list-name> is the
ACL name, with 1-31 characters.
ZXR10(config-msdp)#connect-source < interface-name>
This configures the source IP

address of TCP connections. The
parameter < interface-name> is the
interface name. The address of the
interface will used as the source IP
address of the TCP connections.
9.3.4 Clearing MSDP States

To configure clear MSDP states on ZXR10 M6000, perform the following steps.
Step
Command
Function
ZXR10#clear ip msdp peer [ < peer-address> ]
This clears the TCP connection

established with all MSDP neighbors
or a specific MSDP neighbor.
ZXR10#clear ip msdp sa-cache [ < group-address> ]
This clears entities in the MSDP

SA cache. The parameter <
group-address> is the address of the
multicast group.
ZXR10#clear ip msdp statistics [ < peer-address> ]
This clears the statistics information

of an MSDP neighbor but does
not resets the MSDP session. The
parameter < peer-address> is the IP
address of the MSDP neighbor.
9-4
SJ-20110504161056-014|2010-05-10 (R2.1)
9.4 MSDP Maintenance

ZXR10 M6000 provides the following commands to maintain MSDP.
Command
Function
ZXR10#show ip msdp peer [ < peer-address> ]
This shows the detailed information of

an MSDP neighbor.
ZXR10#show ip msdp sa-cache [ < group-address> [ < source-address> ] ]
This shows the (S, G) states from

different MSDP neighbors.
This shows the summary information of
ZXR10#show ip msdp summary
MSDP neighbors.
This the count of sources/multicast
ZXR10#show ip msdp count
groups generated by SA messages and

the count of SA messages from each
MSDP neighbor in the SA cache.
Parameter
Description
< peer-address>
IP address of an MSDP neighbor
< group-address>
< source-address>
An example of the show ip msdp peer command output is shown below.

ZXR10#show ip msdp peer 101.1.1.1
MSDP Peer 101.1.1.1
Description: zte router 1
Connection status:
State: Up, Resets: 9, Connection source: pvc1 (101.1.1.2)
Uptime(Downtime): 1d10h, Messages sent/received: 22189/22236
Connection and counters cleared 1w2d ago
Peer is member of mesh-group zte1
SA Filtering:
Input (S,G) filter: everything
Output (S,G) filter: none
Peer ttl threshold: 0
SAs learned from this peer: 2, SAs limit: 500

Command Output
Description
MSDP Peer
IP address of this MSDP neighbor
State
State of this MSDP neighbor

9-5
SJ-20110504161056-014|2010-05-10 (R2.1)
Command Output
Description
Connection source
The interface that provides an IP address as the local TCP connection

address
Uptime(Downtime)
The uptime (downtime) of this MSDP neighbor. If this time is less than 24
hours, it is displayed in the format of hour: minute: second.
Messages sent/received
The count of SA messages that are sent to or received from this MSDP
neighbor
SA Filtering
Filter information about the input or output SA messages
SAs learned from this peer
The count of SA messages that are received from this MSDP neighbor
in the SA cache
SAs limit
SA message limit of this MSDP neighbor
An example of the show ip msdp sa-cache command output is shown below.

ZXR10#show ip msdp sa-cache
MSDP Source-Active Cache - 4 entries
(101.101.101.101, 224.1.1.1), RP 49.4.4.4, 00:21:45/ 00:05:57
(101.101.101.101, 224.1.1.2), RP 49.4.4.4, 00:21:45/ 00:05:57
(101.101.101.101, 226.1.1.1), RP 50.4.4.4, 00:09:04/ 00:04:57
(101.101.101.101, 226.1.1.2), RP 50.4.4.4, 00:09:04/ 00:04:57

Command Output
Description
(101.101.101.101, 224.1.1.1)
The packets sent to the second address (the multicast group) by the first
address (the source)
RP 49.4.4.4
The address of the RP first to generate SA messages in the domain
00:21:45/ 00:05:57
This cache has been established by this router for 21 minutes 45 seconds.
If this SA message has not been received until 5 minutes 57 seconds, the
cache will be deleted.
An example of the show ip msdp summary command output is shown below.

ZXR10#show ip msdp summary
MSDP Peer Status Summary
Peer Address
Downtime
101.1.1.1
102.2.2.2
103.3.3.3
State
Count
Uptime/
Reset
SA
Count
Up
1d10h
Up
Up
14:24:00
12:36:17
20
10

Command Output
Description
Peer Address
IP address of this MSDP neighbor

9-6
SJ-20110504161056-014|2010-05-10 (R2.1)
Command Output
Description
State
State of this MSDP neighbor
Uptime/Downtime
The uptime (downtime) of this MSDP neighbor. If this time is less than 24
hours, it is displayed in the format of hour: minute: second.
Reset Count
Count of reset. The TCP connection may be disconnected.
SA Count
The count of SA messages that are received from this MSDP neighbor
in the SA cache
An example of the show ip msdp count command output is shown below.

ZXR10#show ip msdp count
SA State per Peer Counters, <Peer>: <# SA learned>
101.1.1.1: 2
102.2.2.2: 20
103.3.3.3: 10
Total entries: 32

Command Output
Description
101.1.1.1: 2
The IP address means the MSDP neighbor with this address. The count
of SA messages that are received from this MSDP neighbor in the SA
cache is 2.
Total entries 32
The count of SA messages that are received from all MSDP neighbors in
the SA cache is 32.
9.5 MSDP Configuration Examples

9.5.1 MSDP Basic Configuration Example
As shown in Figure 9-1, R1 and R3 are in the same PIM-SM multicast domain. R2 is in
another PIM-SM multicast domain. It is required to forward multicast packets between the
two domains through MSDP.
9-7
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 9-1 MSDP Basic Configuration Example
1. Enable PIM-SM and configure the candidate BSR and the RP.
2. Configure OSPF to make provide the routes between the two domains.
3. Enable MSDP and establish peer relationship. The multicast source sends multicast
flows. When the multicast receiver sends a multicast group Join message, the
multicast source and the multicast receiver can communicate with each other.
R1(config)#interface loopback1
R1(config-if)#exit
R1(config-pimsm)#rp-candidate loopback1 priority 10
R1(config-pimsm)#bsr-candidate loopback1 10 10
R1(config-if)#exit
R1(config-if)#exit
9-8
SJ-20110504161056-014|2010-05-10 (R2.1)

R1(config-if)#exit
R1(config)#router ospf 1
R1(config-ospfv2)#network 10.10.10.0 0.0.0.255 area 0
R1(config-ospfv2)#exit
R1(config-mcast)#router msdp
R1(config-msdp)#connect-source gei-0/1/0/2
R1(config-msdp)#peer 10.10.20.2
R1(config-msdp-peer)#exit
R1(config-pimsm-if)#bsr-border

R2(config-if)#exit
R2(config-if)#exit
9-9
SJ-20110504161056-014|2010-05-10 (R2.1)

R2(config-if)#exit
R2(config-if)#exit
R2(config-msdp)#default-peer 10.10.20.1
R2(config-msdp)#exit

R3(config-if)#exit
9-10
SJ-20110504161056-014|2010-05-10 (R2.1)

R3(config-if)#exit
R3(config-if)#exit
R3(config-msdp)#exit
R3(config-pimsm-if)#end
Execute the show ip msdp summary command on R1 to check the establishment of MSDP
peer relationship.
R1#show ip msdp summary
Peer Address
State
Uptime/
Reset
Downtime
Count
SA
Count
9-11
SJ-20110504161056-014|2010-05-10 (R2.1)

10.10.20.2
up
00:05:34
10.10.30.2
up
00:06:45

Peer Address
State
Uptime/
Reset
*10.10.20.1
up
10.10.40.2
up
00:08:45
SA
Downtime
Count
00:07:34
Count

Peer Address
State
Uptime/
Reset
Downtime
Count
SA
Count
10.10.30.1
up
00:09:34
10.10.40.1
up
00:10:45
9.5.2 Anycast-RP Accomplished Through MSDP

As shown in Figure 9-2, it is required to accomplish anycast-RP by configuring MSDP on
RB and RC.
Figure 9-2 Anycast-RP Accomplished Through MSDP
9-12
SJ-20110504161056-014|2010-05-10 (R2.1)
1.
2.
3.
4.
Configure OSPF to provides routes between RA and RB and between RA and RC.
Enable PIM-SM and configure an RP.
Configure MSDP between RB and RC.
The receiver joins the multicast group. The multicast source sends flows.
The configuration of RB:
ZXR10(config)interface gei-0/0/0/1
ZXR10(config-if)#exit
ZXR10(config-ospfv2)#exit
/*Loopback1 works as an RP.*/
ZXR10(config-msdp)#originator-id loopback2
ZXR10(config-msdp)#peer 10.0.0.3
ZXR10(config-msdp-peer)#connect-source loopback2
/*Configure MSDP*/
The configuration of RC:

9-13
SJ-20110504161056-014|2010-05-10 (R2.1)

ZXR10(config-ospfv2)#exit
/*Loopback1 works as an RP. The address is the same as that on RA.*/
ZXR10(config-msdp)#originator-id loopback2
ZXR10(config-msdp)#peer 10.0.0.2
ZXR10(config-msdp-peer)#connect-source loopback2
/*Configure MSDP*/
The receiver joins the IP multicast group. An RP is chosen randomly between RB and
RC to forward the Register message. If the chosen link is down, traffic will be forwarded
through the other link.
9.6 MSDP Fault Handling

The network topology of an MSDP fault is shown in Figure 9-3.
9-14
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 9-3 Network Topology of an MSDP Fault

Assume that the multicast source uses 10.10.10.2 as the source address. 226.1.1.1 is the
multicast address of the multicast packets. The receiver does not receive the packets.
9.6.3 Handling Flow

The flow to handle an MSDP fault is shown in Figure 9-4.
9-15
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 9-4 Flow to Handle an MSDP Fault

The procedure to handle an MSDP fault is described below.
1. Use the show ip interface brief command to check whether the interface state and
address are correct. Use the show running-config multicast command (on an interface)
to check whether the services are correct. Use the show running-config-interface gei0/1/0/1 command (on an interface) to check the services on the interface.
2. Use the show ip pimsm neighbor command to check whether the PIM-SM neighbor
relationship is established. Use the show ip pimsm bsr command to check the RP information and the election of BSR. Use the show ip mroute command to check whether
the forwarding routing table is normal.
3. Use the show ip msdp summary command to check the peer establishment and SA
filter condition.
4. Check whether the receiving group address is 226.1.1.1.
9-16
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 10
IGMP Snooping
Configuration
Table of Contents
IGMP Snooping Overview ........................................................................................10-1
IGMP Snooping Principle .........................................................................................10-1
Configuring IGMP Snooping .....................................................................................10-1
IGMP Snooping Maintenance...................................................................................10-5
IGMP Snooping Configuration Example ...................................................................10-6
IGMP Snooping Fault Handling ................................................................................10-9
10.1 IGMP Snooping Overview

In a Virtual Private LAN Service (VPLS) broadcast domain, IGMP snooping is responsible
for detecting IGMP packets. It also creates and maintains the L2 multicast forwarding
table.
10.2 IGMP Snooping Principle

Multicast packets will be broadcasted in a VPLS domain without IGMP snooping. IGMP
snooping is responsible for detecting IGMP packets, and generating corresponding L2
forwarding entities. After that, multicast packets are multicasted instead of broadcasted,
which reduces waste of network bandwidths.
10.3 Configuring IGMP Snooping

To configure IGMP snooping on ZXR10 M6000, perform the following steps.
Step
Command
Function
ZXR10(config-igmpsnoop)#igmp snooping
This enables IGMP snooping.
ZXR10(config-igmpsnoop)#igmp snooping mode { proxy | route |
This configures the working mode
transparent} vpls< word >
of a VPLS instance in global IGMP

snooping configuration mode.
ZXR10(config-igmpsnoop)#igmp snooping packet-manage { igmpv1
This configures the action on IGMP
| igmpv2 | igmpv3} { accept | discard | ignore}
packets of different versions in global

IGMP snooping configuration mode.
10-1
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-igmpsnoop)#igmp snooping querier
This configures a querier in global

IGMP snooping configuration mode.
ZXR10(config-igmpsnoop)#igmp snooping query-interval < interval>
This configures the querier interval in

global IGMP snooping configuration
mode. The < interval> parameter
is the querier interval, that is, the
interval to send query packets. It is
in the unit of second, in the range of
30-65535, with the default value of
125 seconds.
ZXR10(config-igmpsnoop)#igmp snooping query-response-interval
< interval>
response interval on a proxy

querier in global IGMP snooping
configuration mode. The < interval>
parameter is the maximum response
interval, in the unit of tick (1 tick =
100 milliseconds), in the range of
1-255, with the default value of 100
ticks (10 seconds).
ZXR10(config-igmpsnoop-vfi)#igmp snooping drop < ip-address> [
This configures a dropping group
number < num> ]
in IGMPSNOOP-VFI configuration
mode.
ZXR10(config-igmpsnoop-vfi)#igmp snooping dynamic-learn-close
This configures an NDL port in
down [ interface < port-name > ]
IGMPSNOOP-VFI configuration
mode. The < port-name > parameter
is the name of a port.
ZXR10(config-igmpsnoop-vfi)#igmp snooping fast-leave
This configures fast leaving function

mode.
10
ZXR10(config-igmpsnoop-vfi)#igmp snooping max-host-in-group
< ip-address> [ limit-num < num> ]

number of users supported by a
multicast group in a VPLS instance
mode.
11
ZXR10(config-igmpsnoop-vfi)#igmp snooping mrouter interface <
This configures a route interface in an

VPLS instance in IGMPSNOOP-VFI
port-name>
configuration mode.
10-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 10 IGMP Snooping Configuration
Step
Command
Function
12
ZXR10(config-igmpsnoop-vfi)#igmp snooping mrouter-time-out
This configures the aging time of a
< time>
route interface in IGMPSNOOP-VFI

configuration mode. The < time>
parameter is the aging time of a route
interface. It is in the unit of second,
in the range of 30-65535, with the
default value of 260 seconds.
13
ZXR10(config-igmpsnoop-vfi)#igmp snooping prejoin< ip-address>
This configures pre-joining to a
[ number < number> ]
multicast group in IGMPSNOOP-VFI

configuration mode.
14
ZXR10(config-igmpsnoop-vfi)#igmp snooping querier [ version
This configures the version of
< version> ]
the querier in a VPLS instance in

IGMPSNOOP-VFI configuration
mode. The version can be IGMPv1,
IGMPv2 or IGMPv3.
15
ZXR10(config-igmpsnoop-vfi)#igmp snooping proxy-ip <
This configures the IP address in
ip-address>
proxy Report packets in a VPLS

instance in IGMPSNOOP-VFI
configuration mode. The <
ip-address> parameter is the address
of a host, in the dotted decimal
notation.
16
ZXR10(config-igmpsnoop-vfi)#igmp snooping query-ip <
This configures the IP address in
ip-address>
proxy Query packets in a VPLS

instance in IGMPSNOOP-VFI
ip-address> parameter is the address
of a host, in the dotted decimal
notation.
17
ZXR10(config-igmpsnoop-vfi)#igmp snooping static < ip-address>
[ < ip-address> ] interface < port-name>
This configures a member of a

multicast group in a VPLS instance
mode.
18
ZXR10(config-igmpsnoop-vfi)#igmp snooping host-time-out <
This configures the aging time of
time>
a multicast group member in a

VPLS instance in IGMPSNOOP-VFI
configuration mode. The < time>
parameter is the aging time, in
the unit of second, in the range of
30-65535, with the default value of
260 seconds.
10-3
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
19
ZXR10(config-igmpsnoop-vfi)#igmp snooping last-member-query-
This configures the interval to query
interval < interval>
the last member in a VPLS instance

mode. The < interval> parameter is
the interval to query the last member,
in the unit of second, in the range
of 1-25, with the default value of 1
second.

Parameter
Description
proxy | route | transparent
IGMP snooping working mode

Parameter
Description
igmpv1 | igmpv2 | igmpv3
IGMP packet version
accept | discard | ignore
Actions to the packets

Parameter
Description
< ip-address>
Group address, in the dotted decimal notation
< num>
The number of continuous groups to be dropped, in the range of 1-1024

Parameter
Description
< ip-address>
limit-num < num>
Number of users limited in a group, in the range of 1-4096

Parameter
Description
interface< port-name>
Port name

Parameter
Description
< ip-address>
number< number>
The number of continuous groups to pre-join, in the range of 1-1024

10-4
SJ-20110504161056-014|2010-05-10 (R2.1)

Parameter
Description
< ip-address>
interface< port-name>
Port name
10.4 IGMP Snooping Maintenance

ZXR10 M6000 provides the following command to maintain IGMP snooping.
Command
Function
ZXR10#show ip igmp snooping
This shows all IGMP snooping entities.
An example of the show ip igmp snooping command output is shown below.

ZXR10(config)#show ip ig snooping
Host-time-out is 260.
Last-member-query-interval is 1.
Total-group-num is 9.
Max-group-num is 1024.
Exist-host-group-num is 9.
Cfg-drop-group-num is 0.
Cfg-prejoin-group-num is 0.
Cfg-max-host-group-num is 0.
S = Static; D = Dynamic.
Index VpnId VLAN VBUI
Group
Drop Prejoin MaxHost Ports
-------------------------------------------------------------------1
vbui1
225.1.1.9
D:fei-0/1/0/1
vbui1
225.1.1.8
D:fei-0/1/0/1
vbui1
225.1.1.7
D:fei-0/1/0/1
vbui1
225.1.1.6
D:fei-0/1/0/1
vbui1
225.1.1.5
D:fei-0/1/0/1
vbui1
225.1.1.4
D:fei-0/1/0/1
vbui1
225.1.1.3
D:fei-0/1/0/1
vbui1
225.1.1.2
D:fei-0/1/0/1
vbui1
225.1.1.1
D:fei-0/1/0/1
ZXR10(config)#

Command Output
Description
Index
The number of entities
VpnId
The ID of a VPN where an entity locates. If there is no VPNID, the system

displays 0.
10-5
SJ-20110504161056-014|2010-05-10 (R2.1)
Command Output
Description
VLAN
The ID of a VLAN where an entity locates. If there is no VLANID, the

system displays 0.
VBUI
The name of a VBUI interface where an entity locates
Group
Multicast group address of an entity
Drop
Whether the multicast group is a dropping group
Prejoin
Whether the multicast group is a pre-joining group
MaxHost
The maximum number of users supported by the multicast group
Ports
User information of the multicast group
10.5 IGMP Snooping Configuration Example

As shown in Figure 10-1, gei-0/1/0/2 of PE1 connects to a CE router, and gei-0/1/0/1
connects to the P router. On PE2, gei-0/3/0/2 and gei-0/3/0/3 connect to the CE routers,
and gei-0/3/0/1 connects to the P router. It is required to enable IGMP snooping on PE1
and PE2. It is unnecessary to enable IGMP snooping on the P router.
Figure 10-1 IGMP Snooping Configuration Example
1.
2.
3.
4.
Configure interface addresses on the routers to make PE1 connect to PE2.

Configure loopback interface addresses to working as LDP Router-IDs.
Configure OSPF to advertisement loopback interface addresses to each other
Configure LDP instances. For a direct connection, it is unnecessary to establish a
target session.
5. Configure L2 VPN instances.
6. Enable IGMP snooping.
7. Enable IGMP snooping in VPLS.
10-6
SJ-20110504161056-014|2010-05-10 (R2.1)
The configuration of PE1:
PE1(config)#interface gei-0/1/0/1
PE1(config-if)#ip address 2.2.2.1 255.255.255.0
PE1(config-if)#no shutdown
PE1(config-if)#exit
PE1(config)#interface loopback1
PE1(config-if)#exit
PE1(config)#router ospf 200
PE1(config-ospfv2)#network 2.2.2.0 0.0.0.255 area 0.0.0.0
PE1(config-ospfv2)#exit
PE1(config)#mpls ldp instance 100
PE1(config-ldp)#router-id loopback1
PE1(config-ldp)#interface gei-0/1/0/1
PE1(config-ldp-if)#exit
PE1(config-ldp)#exit
PE1(config)#sdu sdu3
PE1(config)#mpls l2vpn enable
PE1(config)#vpls vpls_zte2
PE1(config-vpls)#sdu sdu3
PE1(config-vpls-sdu)#neighbour 1.1.1.3 40
PE1(config-vpls-sdu-pw)#control-word unused
PE1(config-vpls-sdu-pw)#signal dynamic
PE1(config-vpls-sdu-pw)#encapsulation raw
PE1(config-vpls-sdu-pw)#tunnel-policy auto
PE1(config-vpls-sdu-pw)#exit
PE1(config-vpls-sdu)#exit
PE1(config-vpls)#sac gei-0/1/0/2
PE1(config-vpls-sac)#service-define ethernet
PE1(config-vpls-sac-sd)#exit
PE1(config-vpls-sac)#exit
PE1(config-vpls)#exit
PE1(config)#igmpsnoop
PE1(config-igmpsnoop)#igmp snooping
PE1(config-igmpsnoop)#vpls zte2
PE1(config-igmpsnoop-vfi)#igmp snooping
PE1(config-igmpsnoop-vfi)#exit
PE1(config-igmpsnoop)#exit

10-7
SJ-20110504161056-014|2010-05-10 (R2.1)

PE2(config-if)#exit
PE2(config-if)#ip addr 1.1.1.3 255.255.255.255
PE2(config-if)#exit
PE2(config-vpls)# sdu sdu3
PE2(config-vpls-sac-sd)# exit
PE2(config)#igmpsnoop
PE2(config-igmpsnoop)#igmp snooping
PE2(config-igmpsnoop)#vpls zte2
PE2(config-igmpsnoop-vfi)#igmp snooping
PE2(config-igmpsnoop-vfi)#exit
PE2(config-igmpsnoop)#exit
After the configurations, a VPLS PW is established successfully. CE1 joins a group. Check
the entities generated on PE1 and PE2.
l
The entities on PE1 are shown below.

PE1(config)#show l2vpn summary
10-8
SJ-20110504161056-014|2010-05-10 (R2.1)

The summary information about configured L2VPN:
vpn type
configure/maximum
VPLS
1/8000
VPWS
0/8000
MSPW
0/8000
VLSS
0/8000
PE1(config)#show ip igmp snooping

Flags: ID--Index, Dr--Drop, P--Prejoin, MH--MaxHost,
S--Static, D--Dynamic
ID VPN VLAN VBUI
Source
Group
Dr P MH
Ports
------------------------------------------------------------1
NULL
0.0.0.0
225.1.1.1
0 0
D:gei-0/1/0/2
The entities on PE2 are shown below.

Flags: ID--Index, Dr--Drop, P--Prejoin, MH--MaxHost,
S--Static, D--Dynamic
ID VPN VLAN VBUI
Source
Group
Dr P MH
Ports
------------------------------------------------------------1
NULL
0.0.0.0
225.1.1.1
0 0
D:sdu100
10.6 IGMP Snooping Fault Handling

In practical applications, the main IGMP snooping faults are that multicast traffic is
broadcast in VPLS domain instead of forwarded to the interfaces on which users join the
group. The network topology of an IGMP snooping fault is shown in Figure 10-2.
10-9
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 10-2 Network Topology of an IGMP Snooping Fault

By default, the dropping function is not enabled, and traffic is broadcast in the VPLS
domain. It is necessary to enable the dropping function, so that the traffic will not be
forwarded to the groups without receivers.
10.6.3 Handling Flow

The flow to handle an IGMP snooping fault is shown in Figure 10-3.
Figure 10-3 Flow to Handle an IGMP Snooping Fault

The procedure to handle an IGMP snooping fault is described below.
1. Check whether the dropping function is enabled.
2. Configure the dropping function correctly.
10-10
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 11
PIM Snooping Configuration

Table of Contents
PIM Snooping Overview ...........................................................................................11-1
PIM Snooping Principle ............................................................................................11-1
Configuring PIM Snooping........................................................................................11-1
PIM Snooping Maintenance......................................................................................11-2
PIM Snooping Configuration Example ......................................................................11-2
PIM Snooping Fault Handling ...................................................................................11-6
11.1 PIM Snooping Overview

In a VPLS broadcast domain, the PIM Snooping module is responsible for detecting the
PIM protocol packets to complete Layer 2 multicast dynamic registration.
11.2 PIM Snooping Principle

VPLS is the simulation of Layer 2 network. When multicast traffic passes by a VPLS
network, the traffic is broadcast on the network. As a result, all CEs on the VPLS network
will receive the multicast traffic. This wastes bandwidths. After PIM snooping is enabled
on the VPLS network, a router obtains the relations between IP addresses and ports of
round routers through Hello packets. The router also obtains the multicast route ports on
which packets are to be received by learning the Join/Prune packets. After that, the router
only sends multicast packets to all multicast route ports, which avoids waste of bandwidth.
11.3 Configuring PIM Snooping

To configure PIM snooping on ZXR10 M6000, perform the following steps.
Step
Command
ZXR10(config)#pimsnoop
Function
This enters PIM snooping global
configuration mode.
ZXR10(config-pimsnoop)#pim snooping
This enables PIM snooping globally.
ZXR10(config-pimsnoop)#vpls < vpls-name>
This enters PIM snooping VPLS

vpls-name> parameter is with 1-32
characters.
11-1
SJ-20110504161056-014|2010-05-10 (R2.1)
Step
Command
Function
ZXR10(config-pimsnoop-vfi)#pim snooping
This configures PIM snooping

function in a VPLS instance.
11.4 PIM Snooping Maintenance

ZXR10 M6000 provides the following command to maintain PIM snooping.
Command
Function
ZXR10#show ip pim snooping port-info vpls < vpls-name>
This shows all entities in a PIM

snooping VPLS instance.
An example of the show ip pim snooping port-info vpls zte command output is shown below.
ZXR10#show ip pim snooping port-info vpls zte
PIM Snooping is globally enabled.
PIM Snooping is enabled in this VPLS.
Index
VPLS
Source-ip
Group-ip
Ports
RemainTime
--------------------------------------------------------------1
192.168.100.111
224.1.1.1
fei-0/1/0/1
207
ZXR10#

Command Output
Description
Index
The number of entities
VPLS
The ID of a VPN where an entity locates
Source-ip
The source address of a multicast member
Group-ip
Multicast group address
Ports
Multicast member port
RemainTime
The remained aging time of a multicast member
11.5 PIM Snooping Configuration Example

As shown in Figure 11-1, gei-0/1/0/2 of PE1 connects to a CE router, and gei-0/1/0/1
connects to the P router. On PE2, gei-0/3/0/2 and gei-0/3/0/3 connect to the CE routers,
and gei-0/3/0/1 connects to the P router. It is required to enable PIM snooping on PE1 and
PE2. It is unnecessary to enable PIM snooping on the P router.
11-2
SJ-20110504161056-014|2010-05-10 (R2.1)
Chapter 11 PIM Snooping Configuration
Figure 11-1 PIM Snooping Configuration Example
1.
2.
3.
4.
Configure interface addresses on the routers to make PE1 connect to PE2.

Configure loopback interface addresses to working as LDP Router-IDs.
Configure OSPF to advertisement loopback interface addresses to each other
Configure LDP instances. For a direct connection, it is unnecessary to establish a
target session.
5. Configure L2 VPN instances.
6. Enable PIM snooping.
7. Enable PIM snooping in VPLS.
PE1(config-if)#exit
PE1(config-if)#exit
11-3
SJ-20110504161056-014|2010-05-10 (R2.1)

PE1(config-vpls)#sdu sdu3
PE1(config-vpls-sac-sd)#exit
PE1(config)#pimsnoop
PE1(config-pimsnoop)#pim snooping
PE1(config-pimsnoop)#vpls zte2
PE1(config-pimsnoop-vfi)#pim snooping
PE1(config-pimsnoop-vfi)#exit
PE1(config-pimsnoop)#exit

PE2(config-if)#exit
PE2(config-if)#ip addr 1.1.1.3 255.255.255.255
PE2(config-if)#exit
PE2(config-vpls)# sdu sdu3
11-4
SJ-20110504161056-014|2010-05-10 (R2.1)

PE2(config-vpls-sac-sd)# exit
PE2(config)#pimsnoop
PE2(config-pimsnoop)#pim snooping
PE2(config-pimsnoop)#vpls zte2
PE2(config-pimsnoop-vfi)#pim snooping
PE2(config-pimsnoop-vfi)#exit
PE2(config-pimsnoop)#exit
After the configurations, a VPLS PW is established successfully. CE1 is a multicast router
and it joins a group. Check the entities generated on PE1 and PE2.
l
The neighbor information and the route to the group member on PE1 are shown below.
PE1(config)#show l2vpn summary
The summary information about configured L2VPN:
vpn type
configure/maximum
VPLS
1/8000
VPWS
0/8000
MSPW
0/8000
VLSS
0/8000
PE1(config)#show ip pim snooping neighbor-info

Index
Port
VLAN
VPLS
Neighbor-ip
RemainTime
-----------------------------------------------------------1
gei-0/1/0/2
35.35.0.12
PE1(config)#show ip pim snooping port-info vpls
102
zte

Index
VPLS
Source-ip
Group-ip
Ports
RemainTime
-------------------------------------------------------------1
1.2.3.4
227.0.0.4
gei-0/1/0/2
146
The neighbor information and the route to the group member on PE2 are shown below.
PE2(config)#show ip pim snooping neighbor-info
Index
Port
VLAN
VPLS
Neighbor-ip
RemainTime
--------------------------------------------------------1
sdu100
ZXR10(config)#show ip
35.35.0.12
170
pim snooping port-info vpls zte
11-5
SJ-20110504161056-014|2010-05-10 (R2.1)

Index
VPLS
Source-ip
Group-ip
Ports
RemainTime
--------------------------------------------------------------1
1.2.3.4
227.0.0.4
sdu100
232
11.6 PIM Snooping Fault Handling

In practical applications, the main PIM snooping faults are that multicast route neighbors
and group Join packets cannot be detected. The network topology of a PIM snooping fault
is shown in Figure 11-2.
Figure 11-2 Network Topology of a PIM Snooping Fault

By default, PIM snooping is not enabled globally or in a VPLS instance, so multicast route
neighbors and group Join packets cannot be learnt.
11.6.3 Handling Flow

The flow to handle a PIM snooping fault is shown in Figure 11-3.
11-6
SJ-20110504161056-014|2010-05-10 (R2.1)
Figure 11-3 Flow to Handle a PIM Snooping Fault

The procedure to handle a PIM snooping fault is described below.
1. Check whether the PIM snooping function is enabled.
2. Enable PIM snooping globally and in a VPLS instance respectively.
11-7
SJ-20110504161056-014|2010-05-10 (R2.1)
11-8
SJ-20110504161056-014|2010-05-10 (R2.1)
Figures
Figure 3-1 IGMP Querier Election ............................................................................. 3-7
Figure 3-2 Joining of IGMP Dynamic Group and Static Group................................. 3-10
Figure 3-3 IGMP Fast Leave Form All Groups ........................................................ 3-12
Figure 3-4 IGMP Fast Leaving Form a Specified Group .......................................... 3-14
Figure 3-5 Network Topology of an IGMP Fault....................................................... 3-17
Figure 3-6 Flow to Handle an IGMP Fault ............................................................... 3-18
Figure 4-1 PIM-DM Configuration Example............................................................... 4-4
Figure 4-2 Network Topology of a PIM-DM Fault ....................................................... 4-5
Figure 4-3 Flow to Handle a PIM-DM Fault ............................................................... 4-6
Figure 5-1 Forwarding Multicast Flow through PIM-SM (Dynamic RP) .................... 5-11
Figure 5-2 Forwarding Multicast Flow through PIM-SM (Static RP) ......................... 5-13
Figure 5-3 Illegal Multicast Source Control.............................................................. 5-15
Figure 5-4 Anycast-RP Configuration Example ....................................................... 5-19
Figure 5-5 Network Topology of a PIM-SM Fault ..................................................... 5-21
Figure 5-6 Flow to Handle a PIM-SM Fault ............................................................. 5-22
Figure 6-1
PIM-SSM Configuration Example............................................................ 6-2
Figure 6-2 Network Topology of a PIM-SSM Fault..................................................... 6-4

Figure 6-3 Flow to Handle a PIM-SSM Fault ............................................................. 6-5
Figure 7-1 Multicast Load Sharing Principle .............................................................. 7-2
Figure 7-2 Multicast Load Sharing Configuration Example ........................................ 7-3
Figure 7-3 Network Topology of a Multicast Load Sharing Fault ................................ 7-6
Figure 7-4 Flow to Handle a Multicast Load Sharing Fault ........................................ 7-7
Figure 8-1 Static Multicast Configuration Example .................................................... 8-4
Figure 8-2 Network Topology of a Static Multicast Fault ............................................ 8-5
Figure 8-3 Flow to Handle a Static Multicast Fault..................................................... 8-6
Figure 9-1 MSDP Basic Configuration Example ........................................................ 9-8
Figure 9-2 Anycast-RP Accomplished Through MSDP............................................ 9-12
Figure 9-3 Network Topology of an MSDP Fault...................................................... 9-15
Figure 9-4 Flow to Handle an MSDP Fault .............................................................. 9-16
Figure 10-1 IGMP Snooping Configuration Example ............................................... 10-6
Figure 10-2 Network Topology of an IGMP Snooping Fault ................................... 10-10
Figure 10-3 Flow to Handle an IGMP Snooping Fault ........................................... 10-10
I
Figure 11-1 PIM Snooping Configuration Example .................................................. 11-3

Figure 11-2 Network Topology of a PIM Snooping Fault .......................................... 11-6
Figure 11-3 Flow to Handle a PIM Snooping Fault .................................................. 11-7
II
Glossary
BSR
- Bootstrap Router
DR
- Designate Router
DVMRP
- Distance Vector Multicast Routing Protocol
ECMP
- Equal-Cost Muti-Path routing
IGMP
- Internet Group Management Protocol
IP
- Internet Protocol
LAN
- Local Area Network
MSDP
- Multicast Source Discovery Protocol
NE
- Network Element
PIM-DM
- Protocol Independent Multicast - Dense Mode
PIM-SM
- Protocol Independent Multicast - Sparse Mode
RFC
- Request For Comments
RP
- Rendezvous Point
RPF
- Reverse Path Forwarding
SA
- Source Active
SPT
- Shortest Path Tree
SSM
- Source Specific Multicast
III
TCP
- Transfer Control Protocol
TCP/IP
- Transfer Control Protocol/Internet Protocol
VPLS
- Virtual Private LAN Service
VRF
- Virtual Route Forwarding
IV

ZXR10 M6000 (V1.00.30) Carrier-Class Router Configuration Guide (IPv4 Multicast)

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ZXR10 M6000 (V1.00.30) Carrier-Class Router Configuration Guide (IPv4 Multicast)

Transféré par

Droits d'auteur :

Formats disponibles

ZXR10 M6000

Configuration Guide (IPv4 Munticast)

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Third release, The follwoing chapters are modified.

Second release, the document architecture is changed.

Serial Number: SJ-20110504161056-014

Chapter 2 IP Multicast Principle................................................................ 2-1

Chapter 3 IGMP Configuration .................................................................. 3-1

Chapter 4 PIM-DM Configuration .............................................................. 4-1

4.5 PIM-DM Configuration Example .......................................................................... 4-4

Chapter 5 PIM-SM Configuration .............................................................. 5-1

Chapter 6 PIM-SSM Configuration ............................................................ 6-1

Chapter 7 Multicast Load Sharing Configuration.................................... 7-1

7.6 Multicast Load Sharing Fault Handling................................................................. 7-6

Chapter 8 Static Multicast Configuration ................................................. 8-1

Chapter 9 MSDP Configuration ................................................................. 9-1

Chapter 10 IGMP Snooping Configuration............................................. 10-1

10.4 IGMP Snooping Maintenance.......................................................................... 10-5

Chapter 11 PIM Snooping Configuration................................................ 11-1

About This Manual

On-site maintenance engineers

What Is in This Manual

Chapter 1 Safety Instruction

Introduces safety instruction and symbol description for device

Chapter 2 IP Multicast Principle

Describes the multicast principle, include multicast address,

Chapter 3 IGMP Configuration

Describes the IGMP principle, configuration commands,

Chapter 4 PIM-DM Configuration

Describes the PIM-DM principle, configuration commands,

Chapter 5 PIM-SM Configuration

Describes the PIM-SM principle, configuration commands,

Chapter 6 PIM-SSM Configuration

Describes the PIM-SSM principle, configuration commands,

Chapter 7 Multicast Load Sharing

Describes the Multicast Load Sharing principle, configuration

commands, maintenance commands, configuration examples

Chapter 8 Static Multicast

Describes the Static Multicast principle, configuration commands,

maintenance commands, configuration examples and fault

Chapter 9 MSDP Configuration

Describes the MSDP principle, configuration commands,

Chapter 10 IGMP Snooping

Describes the IGMP Snooping principle, configuration

commands, maintenance commands, configuration examples

Chapter 11 PIM Snooping

Describes the PIM Snooping principle, configuration commands,

maintenance commands, configuration examples and fault

Keys on the keyboard and buttons on screens and company name.

Separates individual parameter in series of parameters.

1.1 Safety Instruction

1.2 Safety Signs

ZTE Proprietary and Confidential

ZXR10 M6000 Configuration Guide (IPv4 Munticast)

ZTE Proprietary and Confidential

2.1 IP Multicasting Overview

2.1.1 IP Multicast Address

2.1.2 Multicast Tree

ZTE Proprietary and Confidential

ZXR10 M6000 Configuration Guide (IPv4 Munticast)

2.1.3 Multicast Routing Protocol

ZTE Proprietary and Confidential

Chapter 2 IP Multicast Principle