ZXR105900ESeries · 2016. 9. 30. · About This Manual Purpose ThismanualistheZXR105900ESeries(V3.00.11)Easy-MaintenanceMPLSRouting SwitchConfigurationGuide(Multicast),whichisapplicabletotheZXR105900E(V3

ZXR10 5900E SeriesEasy-Maintenance MPLS Routing Switch

Configuration Guide (Multicast)

Version: 3.00.11

ZTE CORPORATIONNo. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://support.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2014 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2015–01–15 First edition

Serial Number: SJ-20150114102049-007

Publishing Date: 2015-01-15 (R1.0)

SJ-20150114102049-007|2015-01-15 (R1.0) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Multicast Principle .................................................................... 1-11.1 Multicasting Overview......................................................................................... 1-1

1.2 Configuring Public IP Multicast ............................................................................ 1-3

Chapter 2 IGMP Configuration .................................................................. 2-12.1 IGMP Overview.................................................................................................. 2-1

2.2 Configuring IGMP............................................................................................... 2-2

2.3 Maintaining IGMP............................................................................................... 2-6

2.4 IGMP Configuration Examples ............................................................................ 2-8

2.4.1 IGMP Querier Election.............................................................................. 2-8

2.4.2 Joining of IGMP Dynamic Group and Static Group ................................... 2-10

2.4.3 IGMP Fast Leaving From All Groups ....................................................... 2-12

2.4.4 IGMP Fast Leaving From a Specified Group ............................................ 2-13

Chapter 3 IGMP Snooping Configuration................................................. 3-13.1 IGMP Snooping Overview................................................................................... 3-1

3.2 Configuring IGMP Snooping................................................................................ 3-1

3.3 Maintaining IGMP Snooping................................................................................ 3-7

3.4 IGMP Snooping Configuration Example ............................................................. 3-10

Chapter 4 PIM-SM Configuration .............................................................. 4-14.1 PIM-SM Overview .............................................................................................. 4-1

4.2 Configuring PIM-SM ........................................................................................... 4-3

4.3 Maintaining PIM-SM ........................................................................................... 4-7

4.4 PIM-SM Configuration Examples....................................................................... 4-14

4.4.1 Forwarding Multicast Flow through PIM-SM (Dynamic RP)........................ 4-14

4.4.2 Forwarding Multicast Flow through PIM-SM (Static RP) ............................ 4-17

4.4.3 Illegal Multicast Source Control ............................................................... 4-18

Chapter 5 PIM-SSM Configuration............................................................ 5-15.1 PIM-SSM Overview ............................................................................................ 5-1

5.2 Configuring PIM-SSM......................................................................................... 5-1

5.3 PIM-SSM Configuration Example ........................................................................ 5-2

Chapter 6 PIM-DM Configuration .............................................................. 6-16.1 PIM-DM Overview .............................................................................................. 6-1

I


6.2 Configuring PIM-DM........................................................................................... 6-1

6.3 Maintaining PIM-DM........................................................................................... 6-2

6.4 PIM-DM Configuration Example .......................................................................... 6-4

Chapter 7 PIM Snooping Configuration ................................................... 7-17.1 PIM Snooping Overview ..................................................................................... 7-1

7.2 Configuring PIM Snooping .................................................................................. 7-1

7.3 Maintaining PIM Snooping .................................................................................. 7-2

7.4 PIM Snooping Configuration Example.................................................................. 7-5

Chapter 8 PIMv6 Snooping Configuration ............................................... 8-18.1 PIMv6 Snooping Overview.................................................................................. 8-1

8.2 Configuring PIMv6 Snooping............................................................................... 8-1

8.3 Maintaining PIMv6 Snooping............................................................................... 8-2

8.4 PIMv6 Snooping Configuration Example .............................................................. 8-5

Chapter 9 MLD Snooping Configuration .................................................. 9-19.1 MLD Snooping Overview .................................................................................... 9-1

9.2 Configuring MLD Snooping ................................................................................. 9-1

9.3 Maintaining MLD Snooping ................................................................................. 9-4

9.4 MLD Snooping Configuration Example ...............................................................9-11

Chapter 10 MSDP Configuration............................................................. 10-110.1 MSDP Overview............................................................................................. 10-1

10.2 Configuring MSDP.......................................................................................... 10-2

10.3 Maintaining MSDP.......................................................................................... 10-5

10.4 MSDP Configuration Example ......................................................................... 10-8

Chapter 11 Static Multicast Configuration ............................................. 11-111.1 Static Multicast Overview .................................................................................11-1

11.2 Configuring Static Multicast ..............................................................................11-2

11.3 Static Multicast Maintenance ............................................................................11-3

11.4 Static Multicast Configuration Example .............................................................11-4

Figures............................................................................................................. I

Glossary ........................................................................................................ III

II


About This ManualPurposeThis manual is the ZXR10 5900E Series (V3.00.11) Easy-Maintenance MPLS RoutingSwitch Configuration Guide (Multicast), which is applicable to the ZXR10 5900E (V3.00.11)series switches.

Intended AudienceThis manual is intended for:

l Network planning engineerl Debugging engineerl Attendant

What Is in This ManualThis manual contains the following chapters:

Chapter 1, Multicast

Principle

Describes Multicast principle, configuration commands on the ZXR10

5900E.

Chapter 2, IGMP

Configuration

Describes IGMP technology and principle, configuration commands,

maintenance commands, and configuration examples on the ZXR10

5900E.

Chapter 3, IGMP Snooping

Configuration

Describes IGMP Snooping technology and principle, configuration

commands, maintenance commands, and configuration examples on

the ZXR10 5900E.

Chapter 4, PIM-SM

Configuration

Describes PIM-SM technology and principle, configuration commands,


5900E.

Chapter 5, PIM-SSM

Configuration

Describes PIM-SSM technology and principle, configuration commands,


5900E.

Chapter 6, PIM-DM

Configuration

Describes PIM-DM technology and principle, configuration commands,


5900E.

Chapter 7, PIM Snooping

Configuration

Describes PIM Snooping technology and principle, configuration


the ZXR10 5900E.

Chapter 8, PIMv6

Snooping Configuration

Describes PIMv6 Snooping technology and principle, configuration


the ZXR10 5900E.

I


Chapter 9, MLD Snooping

Configuration

Describes MLD technology and principle, configuration commands,


5900E.

Chapter 10, MSDP

Configuration

Describes MSDP technology and principle, configuration commands,


5900E.

Chapter 11, Static Multicast

Configuration

Describes Static Multicast technology and principle, configuration


the ZXR10 5900E.

ConventionsThis manual uses the following typographical conventions:

Italics Variables in commands. It may also refer 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.

Constant

width

Text that you type, program codes, filenames, directory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Separates individual parameter in series of parameters.

Note: provides additional information about a certain topic.

II


Chapter 1Multicast PrincipleTable of ContentsMulticasting Overview ................................................................................................1-1Configuring Public IP Multicast ...................................................................................1-3

1.1 Multicasting OverviewIP multicast is a point-to-multipoint or multipoint-to-multipoint communication mode.Multiple receivers receive the same information from the same source. Applications basedon multicast include video conferences, distance education, and software distribution.

Multicast protocols include the member management protocol and the multicast routingprotocol. The member management protocol is used to manage the joining and leavingof multicast members. The multicast routing protocol is used to construct a multicast treethrough exchanging information among switches.

Multicast AddressIn an IP multicast network, the sender sends a packet to multiple receivers in the multicastmode. The sender is called the multicast source. Multiple receivers of the same packetare identified by the same ID that is called the 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. Addresses 224.0.0.0–224.0.0.255 and addresses239.0.0.0–239.255.255.255 are used for research and management.

Multicast TreeIn a Transfer Control Protocol/Internet Protocol (TCP/IP) network, to enable multicastcommunication, the multicast source, receivers and the paths of multicast packets mustbe available. The most widely used routing method is establishing tree routes. Treeroutes 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 on the network.

A multicast tree is a set that consists of a series of ingress interfaces and egress interfaceson switches. It determines a unique forwarding path between the subnet to which themulticast source belongs and all the subnets that contain group members.

There are two types of multicast trees: source tree and shared tree.

l Source tree

1-1


ZXR10 5900E Series Configuration Guide (Multicast)

The source tree is also called the Shortest Path Tree (SPT). It constructs a spanningtree to all receivers for each source. This spanning tree uses the source as theroot node. It reaches the subnets to which the receivers belong. A multicast groupmay contain several multicast sources. Each source or each pair of (S, G) has acorresponding multicast tree.

The method to construct a source tree is called Reverse Path Forwarding (RPF). Eachswitch can find the shortest path to the source and the corresponding egress interfaceaccording to the unicast route. When a switch receives a multicast packet, it checkswhether the ingress interface that the packet reaches is the egress interface to thesource with the shortest unicast path. If it is, the switch forwards the multicast packetaccording to the multicast routes. Otherwise, the switch discards the multicast packet.

l Shared tree

The shared tree constructs a multicast route tree for each multicast group. A multicastgroup is shared by all groupmembers. That is, the tree is shared by all groupmembers(*, G) instead of a tree shared by a pair of broadcast group members (S, G). Eachmember that wants to receive multicast packets from the group should be added tothe shared tree explicitly.

A shared tree uses one or a group of switches as the center of the tree. Multicastpackets from all sources in this group to the receivers are sent to the center. Thenthese packets are forwarded in multicast mode along the tree from the center.

Multicast Routing ProtocolThe Multicast routing protocol is used for exchanging information among switches toconstruct a multicast tree. Different multicast routing protocols use different methods. Tomeet the requirements of multicast user locations in networks, multicast routing protocolis classified into two types: dense mode and sparse mode.

l Dense mode

The prerequisite for a multicast routing protocol of dense mode is that multicastusers locate in the network densely and there is sufficient bandwidth. The protocolconstructs and maintains the multicast tree by flooding the multicast packets to thenetwork periodically. That is, a switch running multicast routing protocol will flood thepackets it receives on all interfaces except the receiving interface.

When a neighbor switch of an interface reports that a group does not exist, theinterface is deleted from the group's multicast tree. This is called pruning. When theneighbor switch of an interface reports that the receiver of this group appears again,the interface is added to the multicast tree of the group. This is called graft.

Multicast routing protocols of the dense mode include the following protocols:

à Distance Vector Multicast Routing Protocol (DVMRP)

à Multicast Open Shortest Path First (MOSPF)

à Protocol Independent Multicast - Dense Mode (PIM-DM)

1-2


Chapter 1 Multicast Principle

l Sparse mode

A multicast routing protocol of sparse mode is suitable for networks where multicastreceivers locate sparsely. In such networks, if the multicast tree is constructed throughflooding (the same with dense mode), a lot of bandwidth will be wasted. In the sparsemode, if a device expects to receive multicast packets, it should make an applicationto join the multicast tree first.

Multicast routing protocols of the sparse mode include the following protocols:

à Core-Based Trees (CBT)

à Protocol Independent Multicast - Sparse Mode (PIM-SM)

1.2 Configuring Public IP MulticastTo configure public multicast on the ZXR10 5900E, perform the following steps:

Step Command Function

ZXR10(config)#ip multicast-routing Enables IP multicast function.1

ZXR10(config)#no ip multicast-routing Disables IP multicast function.

2 ZXR10(config-mcast)#router pim Enables PIM-SM.

3 ZXR10(config-mcast-pim)#no router pim Exits from PIM-SM mode.

4 ZXR10(config-mcast)#multicast-ttl <ttl-limit><interface-

name>

Configures the TTL limit for

multicast forwarding.

5 ZXR10(config-mcast)#no multicast-ttl <interface-name> Disables the TTL limit for

multicast forwarding.

6 ZXR10(config-mcast)#multipath[{s-g-hash}{basic|next

-hop-based}]

Sets the multicast load sharing

mode.

7 ZXR10(config-mcast)#no multipath Disables multicast load

sharing.

8 ZXR10#show ip mroute [vrf <vrf-name>][group<group-address>][source <source-address>][summary][iif<interface-name>][oif <interface-name>]

Displays the IP multicast

routing table.

9 ZXR10#show ip mroute nexthop [<destination-address>][vrf<vrf-name>]

Displays the next hop in the

multicast direction.

10 ZXR10#clear ip mroute [vrf <vrf-name>][group-address<group-address>[source-address <source-address>]]

Clears multicast routes.

11 ZXR10#show ip mroute summary [vrf <vrf-name>] Displays the number of

multicast routes in the IP

multicast routing tables.

12 ZXR10#show ip mroute brief [vrf <vrf-name>] Displays the brief information

of an IP multicast routing table.

1-3




13 ZXR10#mtrace <source-address>[<dest-address>][<group-

address>]

Traces the reverse path of the

source.

14 ZXR10(config-mcast)#damping-enable Enables the multicast damping

function.

15 ZXR10(config-mcast)#no damping-enable Disables the multicast damping

function.

16 ZXR10(config-mcast)#damping-threshold < threshold> Configures the threshold for

the number of times that a route

is distributed. If the number of

times that a route is distributed

exceeds the threshold, the

damping function is enabled.

The minimum wait time to

redistribute the route is 10

seconds, and the maximum

wait time is 60 seconds.

17 ZXR10(config-mcast)#no damping-threshold Restores the default damping

threshold.

18 ZXR10(config-mcast)#filter-policy monitor-interface

<interface-name>< interface-mode >< interface-type >

Configures a global filtering

interface, and the global

filtering mode (include or

exclude) and filtering type (add

or delete) of the interface. One

filtering interface is configured

once. A maximum of 20

interfaces can be configured.

The global filtering modes of

the interfaces must be the

same.

19 ZXR10(config-mcast)#no filter-policy monitor-interface

[<interface-name>]

Deletes a global filtering

interface.

20 ZXR10(config-mcast)#filter-policy monitor-mroute-inte

rface <source-address><group-address><interface-name><

interface-type >

Configures a filtering interface

for a route. The filtering types

(add or delete) of the egress

interfaces for the route are

determined by that of the

global filtering interface. One

route and filtering interface is

configured once. A maximum

of 22 filtering interfaces can be

configured for a route.

1-4




21 ZXR10(config-mcast)#no filter-policy monitor-mroute-in

terface <source-address><group-address>[<interface-name>]

Deletes a filtering interface for

a route.

22 ZXR10(config-mcast)#filter-policy monitor-mroute-mode

<source-address><group-address>< route-mode >

Configures the filtering mode

(include or exclude) for a route.

The filtering mode determines

the filtering types of the egress

interfaces for the route. Only

one filtering mode can be

configured for a route. Filtering

modes can be configured for a

maximum of 1000 routes.

23 ZXR10(config-mcast)#no filter-policy monitor-mroute-m

ode <source-address><group-address>

Deletes the filtering mode of a

route.

24 ZXR10(config-mcast)#forwarding-policy

{per-packet|per-user|per-stream}[group-list <acl-name>]Sets the multicast forwarding

policy to per-packet, per-user,

or per-stream. Default:

per-stream.

25 ZXR10(config-mcast)#no forwarding-policy Restores the default multicast

forwarding policy.

26 ZXR10(config-mcast)#monitor-interface <interface-na

me>

Configures a monitoring

interface. One monitoring

interface is configured once.

A maximum of 20 monitoring

interfaces can be configured.

27 ZXR10(config-mcast)#no monitor-interface

[<interface-name>]

Deletes a monitoring interface.

28 ZXR10(config-mcast)#monitor-mroute <source-address

><group-address>[interface <interface-name>]Configures a multicast

monitoring route. If the

interface set in this command

and themonitoring interface set

through the monitor-interface

command are the same, traffic

passing by the interface is

blocked.

It is recommended that you

configure the [interface<interface-name>] parameter.

If the parameter is not

configured, this command is

invalid, and multicast traffic

is blocked no matter whether

1-5




the monitoring interface is

configured.

29 ZXR10(config-mcast)#no monitor-mroute

<source-address><group-address>[interface<interface-name>]

Deletes a multicast monitoring

route.

30 ZXR10(config-mcast)#mroute-limit <limit> Configures the limit number

of items in the multicast

forwarding table. Default: the

maximum number supported

by the system.

31 ZXR10(config-mcast)#no mroute-limit Restores the default limit

number of items in the

multicast forwarding table.

32 ZXR10(config-mcast)#mroute-downstrem-limit <limit> Configures the limit number of

downlink nodes for the items in

the multicast forwarding table.

33 ZXR10(config-mcast)#no mroute-downstrem-limit Deletes the limit number of

downlink nodes for the items in

the multicast forwarding table.

34 ZXR10(config-mcast)#multicast-boundary

<access-list-name><interface-name>

Configures a multicast

forwarding boundary on

an interface.

35 ZXR10(config-mcast)#no multicast-boundary

[<interface-name>]

Deletes a multicast forwarding

boundary on an interface.

36 ZXR10(config-mcast)#longest-match Configures the rule of selecting

a unicast route for multicast.

The longest-match route is

selected from the MBGP

and MIGP unicast forwarding

tables.

37 ZXR10(config-mcast)#no longest-match Disables the longest match

function.

38 ZXR10(config-mcast)#nexthop < dest-address><

net-mask>< interface-name>< nexthop-address>

Configures a static multicast

next hop, and specifies the

destination address, next

hop interface, and next hop

address.

39 ZXR10(config-mcast)#no nexthop < dest-address><

net-mask>[< interface-name>< nexthop-address>]

Deletes a static multicast next

hop.

1-6




40 ZXR10(config-mcast)#set-dscp-outer < tos-value> Configures the TOS priority

of multicast protocol data

packets.

41 ZXR10(config-mcast)#no set-dscp-outer Deletes the TOS priority

of multicast protocol data

packets.

42 ZXR10(config-mcast)#reject-inbound-data

<interface-name>

Forbids the forwarding plane

to receive multicast data

packets, so that the multicast

router cannot receive multicast

packets on the specified

interface.

43 ZXR10(config-mcast)#no reject-inbound-data[<interfac

e-name>]

Disables the function of

forbidding the forwarding

plane to receive multicast data

packets.

For a description of the parameters in Step 4, refer to the following table:

Parameter Description

<interface-name> Interface name.

<ttl-limit> TTL limit.



s-g-hash Source group-based hash.

basic Default source group-based hash.

next-hop-based Next hop-based hash.



<vrf-name> VRF instance name.

<group-address> Group address, in dotted decimal notation.

<source-address> Source address, in dotted decimal notation.

summary Summary information.


For a description of the parameter in Step 9, refer to the following table:

1-7




<destination-address> Destination address.



<threshold> Damping threshold.



<interface-mode> Interface filtering mode or route filtering mode, globally unified.

<interface-type> Interface filtering type.



per-packet|per-user|per-stream Per-packet, per-user, or per-stream.

<acl-name> ACL name.



<limit> Number of routes.



<limit> Number of downlink nodes.



<dest-address> Destination IP address.

<net-mask> Destination address mask.

<interface-name> Egress interface of a next hop.

<nexthop-address> Next hop address.



<tos-value> TOS priority, range: 1–63, default: 48.

1-8


Chapter 2IGMP ConfigurationTable of Contents

IGMP Overview ..........................................................................................................2-1Configuring IGMP.......................................................................................................2-2Maintaining IGMP.......................................................................................................2-6IGMP Configuration Examples ...................................................................................2-8

2.1 IGMP OverviewIntroduction to IGMPIf a host expects to receive multicast packets from a specific group, it needs to interceptall packets sent to that group. To solve the routing problem for multicast packets on theInternet, the host is required to inform the multicast switches of the group that it joins in orleaves.

In multicast, Internet Group Management Protocol (IGMP) is used for this task. In thisway, the multicast switch knows the members of the multicast group on the network anddecides whether to forward multicast packets to the network. When a multicast switchreceives a multicast packet, it checks the multicast destination address of the packet, andthen forwards the packet to the interfaces in the group or the downstream switch.

IGMP PrincipleThe IGMP runs between a host and a switch that is connected to the host directly. Itsfunction is bidirectional.

l On the one hand, a host informs the switch through the IGMP that it expects to receivepackets from a specific multicast group.

l On the other hand, the switch checks whether the members in the Local Area Network(LAN) are in active state periodically through the IGMP. In this way, the switch collectsand maintains the relationship with the members in the segment.

Through the IGMP, a switch records whether there is a groupmember of a specificmulticastgroup in the local segment instead of the corresponding relationship between the multicastgroup and the host.

The IGMP provides information that is necessary when packets are forwarded to thedestination (the last stage). Multicast switches and hosts that receive multicast dataexchange information. The information is collected from the group members of the hoststhat are directly connected to multicast switches.

2-1



The IGMP uses two types of packets, group member query packets and group memberreport packets.

l Amulticast switch periodically sends groupmember query packets to all hosts to knowwhether specific group members exist in the connected subnets.

l The hosts returns report packets to a group member, reporting the multicast groupthat they belong to.

l When a host joins in a new group, it sends a join packet immediately instead of waitingfor a query in case that the host is the first member of that group and it fails to receiveany multicast packet.

When a host starts to receive packets as a member of a group, the multicast switch queriesthe group periodically to check whether there is any other member of the group on thenetwork. If there is, the multicast switch continues to forward data.

When the host leaves the group, the multicast switch receives a leaving packet and thenimmediately queries whether there are still active group members in the group. If thereare, the multicast switch continues to forward data. If there are not, it does not forwarddata.

At present, there are three versions for the IGMP.

l IGMPv1 (Request For Comments (RFC) 1112): It defines the basic query and reportprocedure of a group member.

l IGMPv2 (RFC 2236): It adds a leaving mechanism on the basis of IGMPv1.l IGMPv3 (RFC 3376): It enables a member to select the multicast source, which

supports the Source Specific Multicast (SSM) mode.

2.2 Configuring IGMPThe following configuration is configured on interfaces in the non-VRF mode. Theconfiguration on interfaces in the VRF mode is the same. For the configuration to enablethe VRF mode, refer to the "Configuring Public IP Multicast" section.

To configure the IGMP basic function on the ZXR10 5900E, perform the following steps:


1 ZXR10(config-mcast)#router igmp Enters IGMP configuration

mode. Use the no command

to delete all the IGMP

configurations.

2-2


Chapter 2 IGMP Configuration


ZXR10(config-mcast-igmp)#interface <interface-name> Enters IGMP interface

configuration mode, even

if IGMP is not enabled on the

interface. IGMP is triggered by

PIM on the interface.

2

ZXR10(config-mcast-igmp)#no interface

<interface-name>

Deletes the interface

configuration and restores

the default configuration.

3 ZXR10(config-mcast-igmp)#ssm-map static

{<access-list-number>|default}<source-address>

Sets SSM mapping.

ZXR10(config-mcast-igmp)#proxy-enable Enables the IGMP proxy

function.

4

ZXR10(config-mcast-igmp)#no proxy-enable Disables the IGMP proxy

function.

ZXR10(config-mcast-igmp)#require-alert-options Configures to drop the

IGMP packets whose IP

headers do not containing

Router_Alert_Options.

5

ZXR10(config-mcast-igmp)#no require-alert-options Disables the function

of dropping the IGMP

packets whose IP

headers do not containing

Router_Alert_Options.






<access-list-number> Access list name for the SSM group, with 1-31 characters.

The IGMP function of the ZXR10 5900E is based on the PIM interface. The IGMP functionis enabled automatically on interfaces on which the PIM is enabled.

Configure IGMP VersionAt present, there are IGMP v1, v2 and v3. By default, IGMP v2 is used. The version canbe adjusted using the version <version> command. For security, a switch requires that allNEs on the same segment use the same IGMP version, the IGMP v1,v2 or v3.

2-3



The configuration of the IGMP version is based on the interface. Different versions can beconfigured on different interfaces.

Configure an IGMP Group on an InterfaceTo configure an IGMP group on an interface of the ZXR10 5900E, perform the followingsteps:


1 ZXR10(config-mcast-igmp-if-interface-name)#acces

s-group <access-list-number>

Sets the range of groups that

IGMP is allowed to join.

<access-list-number>: the

standard IP access list name,

range: 1-31 characters. By

default, there is no limit about

IGMP group joining.

2 ZXR10(config-mcast-igmp-if-interface-

name)#static-group<group-address>[source

{<source-address>[{include|exclude}]|ssm-map}]

Sets a static group address on

an IGMP interface.

<group-address>: address of

the group, in the dotted decimal

notation.

<source-address>: source

address, in the dotted decimal

notation.

3 ZXR10(config-mcast-igmp-if-interface-name)#imme

diate-leave {group-list <access-list-name>|all}Sets the range of groups

allowing members to leave

immediately.

<access-list-number>: standard

IP access list name, range:

1–31 characters.

4 ZXR10(config-mcast-igmp-if-interface-name)#queri

er-election {connect|disable}

Sets querier election

restriction.

5 ZXR10(config-mcast-igmp-if-interface-name)#igmp-

proxy <interface-name>

Configure an upstream

interface of the proxy function

to send IGMP report messages

for a downstream interface

(also called a switch interface).

Use the no command to restore

the default configuration.

2-4




6 ZXR10(config-mcast-igmp-if-interface-name)#join-g

roup <group-address>

Configures a static group

member on an IGMP interface

to send report messages. Use

the no command to delete the

static group member.

7 ZXR10(config-mcast-igmp-if-interface-name)#mro

ute-proxy <interface-name>

Configures an upstream

interface of the proxy function

for a downstream interface

(also called a router interface).

The (*,G) entries of the

interface are contained on the

egress interface. IGMP report

messages can be sent on the

upstream interface. Use the no

command to restore the default

configuration.

8 ZXR10(config-mcast-igmp-if-interface-name)#prox

y-service

Configures the proxy function

at the host side. Report

messages can be sent on

the interface. Use the no


configuration.

Configure IGMP TimersAfter enabling the IGMP on the interfaces of multicast switches connecting to the sharednetwork 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 the query message, the querier waits for the member report sent from thehost that receives the query message for a period. The wait duration is the maximumresponse time carried in the query message. By default, it is 10 seconds.

After receiving the query message, a host member in the network segment reduces arandom deviation value based on the maximum response time. This result is used as theresponse time of the host member. During this period, if the querier receives a report fromanother host member, this host member cancels the report. Otherwise, the host membersends the host report when the response time expires. Therefore, prolonging themaximumresponse time will increase the waiting changes of a groupmember in the network segmentaccordingly and decrease the burst of multiple host reports in the network segment.

The timers related to the querier can be adjusted as required.

To configure IGMP timers on the ZXR10 5900E, perform the following steps:

2-5




1 ZXR10(config-mcast-igmp-if-interface-name)#quer

y-interval <seconds>

Sets the IGMP query interval.

<seconds>: range: 1-65535

seconds, default: 125

seconds.

2 ZXR10(config-mcast-igmp-if-interface-name)#query

-max-response-time <seconds>

Sets the maximum response

time contained in the query

messages.


seconds, default: 10 seconds.

3 ZXR10(config-mcast-igmp-if-interface-name)#queri

er-timeout <seconds>

Sets the IGMP querier timeout.


seconds, default: 5 * (query

interval * 2 + 5) seconds.

4 ZXR10(config-mcast-igmp-if-interface-name)#last-

member-query-interval <seconds>

Sets the IGMP query interval

of a specific group.


seconds, default: 1 second.

5 ZXR10(config-mcast-igmp-if-interface-name)#robu

stness-count <times>

Sets the allowed number of

times that packets are lost.

<times>: range: 2-7.

6 ZXR10(config-mcast-igmp-if-interface-name)#unsoli

cited-report-interval <seconds>

Configures the interval of

sending report messages at

the host side for an upstream

interface. Range: 1-25,

unit: seconds. Use the no


configuration.

7 ZXR10(config-mcast-igmp-if-interface-name)#older-

version-querier-present <seconds>

Configures the interval

of sending higher-version

report messages when

lower-version query messages

are received on an upstream

interface. Range: 60-32000,

unit: seconds. Use the no


configuration.

2.3 Maintaining IGMPTo maintain the IGMP function on the ZXR10 5900E, run the following commands.

2-6



Command Function

ZXR10#show ip igmp interface [<interface-name>] Displays the interface IGMP

configuration.

ZXR10#show ip igmp groups {[<interface-name>]|[<group-addr>]}[d

etail]

Displays the IGMP group joining

information on an interface.

ZXR10#show ip igmp packet-count [<interface-name>] Displays the statistics count of

IGMP protocol packets sending

and receiving.

ZXR10#show ip igmp groups summary Displays the summary IGMP

group numbers on an interface.

ZXR10#show ip igmp proxy groups Displays the information about

IGMP proxy group joining on

interfaces.

ZXR10#clear ip igmp packet-count [<interface-name>] Deletes the multicast groups

added dynamically.

ZXR10#clear ip igmp groups [<interface-name>] Deletes the multicast group that

joined dynamically.

For a description of the parameters, refer to the following table:



<group-addr> Group address.

The following is sample output from the show ip igmp interface command:

ZXR10#show ip igmp interface vlan10

Internet address is 102.1.1.3, subnet mask is 8

IGMP is enabled on interface

Current IGMP version is 2

IGMP query interval is 125 seconds

IGMP last member query interval is 1 seconds

IGMP query max response time is 10 seconds

IGMP querier timeout period is 251 seconds

IGMP querier is 102.1.1.3, never expire

IGMP access group is not set

IGMP immediate leave control is not set

IGMP shaping packets number is not set

IGMP maximum joins is not set

The following is sample output from the show ip igmp groups {[<interface-name>]|[<group-addr>]}[detail] command:

ZXR10#show ip igmp groups loopback3

2-7



Total: 2 groups joined in loopback3

Group addr Interface Present Expire Last Reporter

225.0.0.1 loopback3 2d20h never 200.1.1.3

226.1.1.1 loopback3 2d20h never 200.1.1.3

For a description of the parameters in the execution result, refer to the following table:


Group addr Group address.

Interface Interface.

Present Time when the group member is present.

Expire Remaining time of the time-out timer. Never means there is astatic group and the timer is not enabled.

Last Reporter Address of the host that reports the group member relation last

time.

2.4 IGMP Configuration Examples

2.4.1 IGMP Querier Election

Configuration DescriptionFigure 2-1 shows the network topology of an IGMP querier election configuration example.PIM-SM is enabled on S1 and S2. IGMPv2 is enabled to elect a querier. The switch withthe smaller IP address will be elected as the querier.

Figure 2-1 IGMP Querier Election

1. Configure the interface IP addresses in interface configuration mode. The address ofS1 is smaller than that of S2.

2. Enable IP multicast by using the ip multicast-routing command.3. Enter PIM route configuration mode and then enter the specified interface.4. Enable PIM-SM in interface configuration mode.

Configuration CommandsThe configuration commands of S1 are as follows:

S1(config)#interface vlan1

S1(config-if-vlan1)#ip address 10.0.0.1 255.255.255.0

2-8



S1(config-if-vlan1)#exit

S1(config)#ip multicast-routing

S1(config-mcast)#router pim

S1(config—mcast-pim)#interface vlan1

S1(config—mcast-pim-if-vlan1)#pimsm

The configuration commands of S2 are as follows:






S2(config—mcast-pim)#interface vlan2

S2(config—mcast-pim-if-vlan2)#pimsm

Configuration VerificationRun the show ip igmp interface command to check the configuration result on S1.

S1#show ip igmp interface vlan1

vlan1




/*IGMP version information*/


/*Query interval*/


/*The last member query interval*/


/*Maximum response time*/


/*Querier timeout*/

IGMP robustness variable is 2


/*Querier information. If this device is the querier,

the information is displayed as "never expire".*/

Inbound IGMP access group is not set




Run the show ip igmp interface command to check the configuration result on S2.


vlan2



2-9




/*IGMP version information*/


/*Query interval*/


/*Last member query interval*/


/*Maximum response time*/


/*Querier timeout*/

IGMP robustness variable is 2

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.*/





2.4.2 Joining of IGMP Dynamic Group and Static Group

Configuration DescriptionFigure 2-2 shows the network topology. PIM-SM is enabled on S1. The IGMP version isv2 by default. On S1, configure a static group to join 225.1.1.1, and configure a dynamicgroup to join 225.1.1.2 through the test host.

Figure 2-2 Joining of IGMP Dynamic Group and Static Group

Configuration Flow1. Configure the interface addresses on the switches in interface configuration mode.2. Enable IP multicast by using the ip multicast-routing command.3. Enter PIM route configuration mode and then enter the specified interface.4. Enable PIM-SM in interface configuration mode.5. In multicast mode, enter IGMP route configuration mode and then enter the specified

interface.6. Configure joining of a static group on vlan1 of S1.7. Send IGMP joining packets on the test host.

2-10









S1(config-mcast-pim)#interface vlan1

S1(config-mcast-pim-if-vlan1)#pimsm

S1(config-mcast-pim-if-vlan1)#exit

S1(config-mcast-pim)#exit

S1(config-mcast)#router igmp

S1(config-mcast-igmp)#interface vlan1

S1(config-mcast-igmp-if-vlan1)#static-group 225.1.1.1

Configuration VerificationRun the show ip igmp interface command to check IGMP interface configuration informationon S1.


vlan1








IGMP robustness variable is 2 /*IGMP version information*/






Run the show ip igmp groups detail command to check the detailed information of thegroups on the interface of S1.

S1(config-mcast-igmp-if-vlan1)#show ip igmp groups detail

Flags: S - Static Group, SSM - SSM Group, M - MDT Group

Interface: vlan1

Group: 225.1.1.1

Flags: S

Uptime: 00:05:12

Group mode: EXCLUDE (Expires: 00:03:24)

Last reporter: 100.17.21.2

2-11



Group source list is empty

2.4.3 IGMP Fast Leaving From All Groups

Configuration DescriptionFigure 2-3 shows the network topology. A switch is connected to a multicast user directly.

Figure 2-3 IGMP Fast Leaving From All Groups

Configuration Flow1. Enter multicast configuration mode and enable the interface IGMP function.2. Configure fast leaving from all groups on the interface.









S1(config-mcast-igmp-vlan1)#interface vlan1

S1(config-mcast-igmp-if-vlan1)#immediate-leave all

S1(config-mcast-igmp-if-vlan1)#version 2

S1(config-mcast-igmp-if-vlan1)#exit

S1(config-mcast-igmp)#exit

S1(config-mcast)#exit

S1(config)#

Configuration VerificationConfigure group joining and leaving on gei-0/1/1/1, and then check the configuration result.

ZXR10#show running-config multicast

! <MULTICAST>

ip multicast-routing

router pim

interface vlan1

2-12



pimsm

$

$

router igmp

interface vlan1

immediate-leave all

$

$

! </MULTICAST>

ZXR10#show ip igmp groups

Total: 1 groups


225.0.0.0 vlan1 00:00:06 00:04:14 33.33.0.12

ZXR10 PFU-0/20/0 2010-7-27 09:26:33

igmp : Receive IGMP packet from 33.33.0.12 on interface vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:26:33

igmp : Received packet is IGMP v2 leave message (225.0.0.0)

ZXR10 PFU-0/20/0 2010-7-27 09:26:33

igmp : Membership (225.0.0.0) immediately leaves on vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:26:33

igmp : Delete group 225.0.0.0 on gei-0/1/1/1


Total: 0 groups


2.4.4 IGMP Fast Leaving From a Specified Group

Configuration DescriptionFigure 2-4 shows the network topology. A switch is connected to a multicast user directly.

Figure 2-4 IGMP Fast Leaving From a Specified Group

Configuration Flow1. Configure a group filter rule.2. Enter multicast configuration mode and enable the interface IGMP function.3. Configure fast leaving from a specified group on the interface.

2-13




S1(config)#ipv4-access-list groupfilter

S1(config-ipv4-acl)#rule 1 permit 225.0.0.0

S1(config-ipv4-acl)#rule 2 deny any

S1(config-ipv4-acl)#exit




S1(config-mcast-pim-vlan1)#pimsm

S1(config-mcast-pim-vlan1)#exit




S1(config-mcast-igmp-if-valn1)#immediate-leave group-list groupfilter

S1(config-mcast-igmp-if-valn1)#version 2

S1(config-mcast-igmp-if-valn1)#exit

S1(config-mcast-igmp)#exit


S1(config)#

Configuration VerificationConfigure group joining and leaving on vlan1, and then check the configuration result.

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 pim

interface vlan1

pimsm

$

$

router igmp

interface vlan1

immediate-leave groupfilter

$

2-14



$

! </MULTICAST>

ZXR10 PFU-0/20/0 2010-7-27 09:58:18


ZXR10 PFU-0/20/0 2010-7-27 09:58:18

igmp : Received packet is IGMP v2 membership report for group 225.0.0.0

ZXR10 PFU-0/20/0 2010-7-27 09:58:18

igmp : Create group (225.0.0.0) on vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:58:18

igmp : Updating EXCLUDE group timer for 225.0.0.0 timer to 260 seconds

ZXR10 PFU-0/20/0 2010-7-27 09:58:23


ZXR10 PFU-0/20/0 2010-7-27 09:58:23

igmp : Received packet is IGMP v2 membership report for group 225.0.0.1

ZXR10 PFU-0/20/0 2010-7-27 09:58:23

igmp : Create group (225.0.0.1) on vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:58:23

igmp : Updating EXCLUDE group timer for 225.0.0.1 timer to 260 seconds


Total: 2 groups


225.0.0.0 vlan1 00:00:11 00:04:09 33.33.0.12

225.0.0.1 vlan1 00:00:06 00:04:14 33.33.0.12

ZXR10#

ZXR10 PFU-0/20/0 2010-7-27 09:58:32


ZXR10 PFU-0/20/0 2010-7-27 09:58:32


ZXR10 PFU-0/20/0 2010-7-27 09:58:32

igmp : Membership (225.0.0.0) immediately leaves on vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:58:32

igmp : Delete group 225.0.0.0 on vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:58:33


ZXR10 PFU-0/20/0 2010-7-27 09:58:33


ZXR10 PFU-0/20/0 2010-7-27 09:58:33

igmp : Send IGMPv2 specific query(225.0.0.1) on vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:58:34

igmp : Send IGMPv2 specific query(225.0.0.1) on vlan1

ZXR10 PFU-0/20/0 2010-7-27 09:58:35

igmp : Delete group 225.0.0.1 on vlan1


2-15



Total: 0 groups


ZXR10#

2-16


Chapter 3IGMP SnoopingConfigurationTable of Contents

IGMP Snooping Overview ..........................................................................................3-1Configuring IGMP Snooping .......................................................................................3-1Maintaining IGMP Snooping .......................................................................................3-7IGMP Snooping Configuration Example ...................................................................3-10

3.1 IGMP Snooping OverviewIGMP snooping detects IGMP packets. It also creates and maintains layer–2 multicastforwarding tables.

Multicast packets are broadcasted in a VPLS domain if IGMP snooping is not used. IGMPsnooping detects IGMP packets, and generates the corresponding layer–2 forwardingentities. After that, multicast packets are multicasted instead of broadcast, which reduceswaste of network bandwidths.

3.2 Configuring IGMP SnoopingTo configure the IGMP snooping function on the ZXR10 5900E, perform the following steps:


1 ZXR10(config-igmpsnoop)#igmp snooping enable Enables IGMP Snooping.

2 ZXR10(config-igmpsnoop)#vpls <vpls-name>|vlan

<vlan-id>

Enters VPLS or VLAN

configuration mode from

global configuration mode.

3 ZXR10(config-igmpsnoop)#igmp snooping packet-manage

{igmpv1 | igmpv2 | igmpv3}{accept | discard | ignore}

Sets the action on IGMP

packets of different versions

in global IGMP snooping

configuration mode.

4 ZXR10(config-igmpsnoop)#igmp snooping querier Sets a querier in global IGMP

snooping configuration mode.

3-1




5 ZXR10(config-igmpsnoop)#igmp snooping query-interval

<interval>

Sets the querier interval


configuration mode.

<interval>: interval of sending

query packets, range:

30–65535 seconds, default:

125 seconds.

6 ZXR10(config-igmpsnoop)#igmp snooping

query-response-interval <interval>

Sets the maximum response

interval on a proxy querier


configuration mode.

<interval>: maximum response

interval, range: 1–255 ticks

(1 tick = 100 milliseconds),

default: 100 ticks (10 seconds).


trans-block-port{query | report-leave}

Sets the port that passes or

blocks query packets and

leave packets in global IGMP

snooping configuration mode.


host-aging-closedown

Sets the aging time of a user


configuration mode.

9 ZXR10(config-igmpsnoop)#igmp snooping max-host-mun

{group <ip-address>| interface<port-name>|vlan<vlan-id>}[limit-num <num>]

Sets the maximum number of

hosts supported by a multicast

group under a group address

or port or VLAN in global IGMP

snooping configuration mode,

range: 1–4000.

10 ZXR10(config-igmpsnoop-vpls-zte)#igmp snooping

drop <ip-address>

Sets a dropping group

in IGMPSNOOP-VPLS

configuration mode.


dynamic-learn-closedown [interface < port-name >]Sets an NDL port in

IGMPSNOOP-VPLS

configuration mode.

< port-name >: name of a port.


fast-leave

Sets fast leaving function

in IGMPSNOOP-VPLS

configuration mode.

3-2


Chapter 3 IGMP Snooping Configuration



max-host-in-group <ip-address>limit-num <num>

Sets the maximum number of

users supported by a multicast

group in a VPLS instance

in IGMPSNOOP-VPLS

configuration mode.


mrouter interface <port-name>

Sets a route interface

in an VPLS instance

in IGMPSNOOP-VPLS

configuration mode.


mrouter-time-out <time>

Sets the aging time

of a route interface in

IGMPSNOOP-VPLS

configuration mode.

<time>: aging time of a route

interface: range 30–65535

seconds, default: 260 seconds.


prejoin<ip-address>

Sets pre-joining to a multicast

group in IGMPSNOOP-VPLS

configuration mode.


interface <port-name> enable|disable

Enters VPLS instance interface

in IGMPSNOOP-VPLS mode.


proxy-ip <ip-address>

Sets the IP address in

proxy Report packets

in a VPLS instance

in IGMPSNOOP-VPLS

configuration mode.

<ip-address>: address of a host,

in the dotted decimal notation.


query-ip <ip-address>


proxy Query packets

in a VPLS instance

in IGMPSNOOP-VPLS

configuration mode.

<ip-address>: address of a host,

in the dotted decimal notation.


static <ip-address> interface <port-name>Sets a static member

of a multicast group

in a VPLS instance

in IGMPSNOOP-VPLS

configuration mode.

3-3





host-time-out <time>

Sets the aging time of a

multicast group member

in a VPLS instance

in IGMPSNOOP-VPLS

configuration mode.

<time>: aging time, range:


260 seconds.


last-member-query-interval <interval>

Sets the interval to query the

last member in a VPLS instance

in IGMPSNOOP-VPLS

configuration mode.

<interval>: interval of querying

the last member, range: 1–25


23 ZXR10(config-igmpsnoop-vpls-zte)#igmp snooping acl

<acl-name>

Sets ACL rules for

a VPLS instance in

IGMPSNOOP-VPLS mode.


max-group-num < num >

Sets the max group number

for a VPLS instance in

IGMPSNOOP-VPLS mode.


multicast-router-guard <interface <port-name>>

enable|disable

Disables the interface to be a

route port for a VPLS instance

in IGMPSNOOP-VPLS mode.


querier

Configures a querier

in IGMPSNOOP-VPLS

configuration mode.

27 ZXR10(config-igmpsnoop-vlan1)#igmp snooping drop

<ip-address>

Sets the drop group

in IGMPSNOOP-VLAN

configuration mode.

28 ZXR10(config-igmpsnoop-vlan1)#igmp snooping

dynamic-learn-closedown [interface < port-name >]Sets the NDL interface

in IGMPSNOOP-VLAN

configuration mode.


fast-leave

Sets user fast leave function

in IGMPSNOOP-VLAN

configuration mode.

3-4





max-host-in-group <ip-address>[limit-num <num>]

Sets the maximum host number

supported by the next multicast

group in IGMPSNOOP-VLAN

configuration mode, range:

1–4000.


mrouter <interface <port-name>>

Sets the route port

for a VLAN instance

in IGMPSNOOP-VLAN

configuration mode.


mrouter-time-out <time>

Sets the aging time of a route

port in IGMPSNOOP-VLAN

configuration mode.

<time>: aging time, range:


260 seconds.


prejoin<ip-address>

Sets pre-joining a multicast

group in IGMPSNOOP-VLAN

configuration mode.

34 ZXR10(config-igmpsnoop-vlan1)#igmp snooping querier

[version <version>]

Sets the querier version for a

VLAN in IGMPSNOOP-VLAN

configuration mode.

<version>]: IGMP packet

version, IGMPv1, IGMPv2 or

IGMPv3.


proxy-ip <ip-address>


proxy report packet for a


configuration mode.

<ip-address>: host address, in

the dotted decimal notation.


query-ip <ip-address>

Sets the IP address in a

proxy query packet for a


configuration mode.

<ip-address>: host address, in

the dotted decimal notation.

37 ZXR10(config-igmpsnoop-vlan1)#igmp snooping static

<ip-address> interface<port-name>Sets a multicast static

member for a VLAN

in IGMPSNOOP-VLAN

configuration mode.

3-5





host-time-out <time>

Sets the aging time of a

multicast group member for a


configuration mode.

<time>: host aging time, range:


260 seconds.


last-member-query-interval <interval>

Sets the interval of querying

the last member in a VLAN

in IGMPSNOOP-VLAN

configuration mode.

<interval>: range: 1–65535


40 ZXR10(config-igmpsnoop-vlan1)#igmp snooping acl

<acl-name>

Sets ACL rules in

IGMPSNOOP-VLAN

configuration mode.


mode{proxy | route | transparent}

Sets the IGMP snooping

mode in IGMPSNOOP-VLAN

configuration mode.


max-group-num < num >

Sets the maximum number

of groups for a VLAN

in IGMPSNOOP-VLAN

configuration mode, range:

1–4096.


multicast-router-guard <interface <port-name>>

enable|disable

Disables the port to be a route

port in IGMPSNOOP-VLAN

configuration mode.


{enable | disable}

Enables or disables the

IGMP snooping function

in IGMPSNOOP-VPLS

configuration mode.

45 ZXR10(config-igmpsnoop-vlan1)#igmp snooping {enable

| disable}

Enables or disables the

IGMP snooping function

in IGMPSNOOP-VLAN

configuration mode.



igmpv1 | igmpv2 | igmpv3 IGMP packet version.

accept | discard | ignore Actions to the packets.

3-6





<ip-address> Group address, in the dotted decimal notation.




limit-num <num> Number of users limited in a group, determined by performance

parameters.



interface<port-name> Port name.







interface<port-name> Port name.



proxy | route | transparent Operating mode of the IGMP snooping function.

3.3 Maintaining IGMP SnoopingTo maintain the IGMP snooping function on the ZXR10 5900E, run the followingcommands.

Command Function

ZXR10(config)#show ip igmp snooping Displays all IGMP snooping

entries.

3-7



Command Function

ZXR10(config)#show ip igmp snooping vlan <vlan-id> Displays information about the

configuration and all multicast

entries of a VLAN.

ZXR10(config)#show ip igmp snooping vpls <vpls-name> Displays information about the

configuration and all multicast

entries of a VPLS.

ZXR10(config)#show ip igmp snooping group <ipv4-address>{vlan <vlan-id>|vpls <vpls-name>}

Display the configuration

information and operational

information about a group in an

instance.

ZXR10(config)#show ip igmp snooping mr-port-info Displays all IGMP snooping

routes.

ZXR10(config)#show ip igmp snooping query Displays IGMP snooping query

information.

ZXR10(config)#show ip igmp snooping ndl-port-info Displays the information of

ports where it is prohibited to

learn dynamic routes for IGMP

snooping.

ZXR10(config)#show ip igmp snooping port-info vlan <vlan-id> Displays the information about

multicast user ports of a VLAN.

ZXR10(config)#show ip igmp snooping port-info vpls

<vpls-name>

Displays the information about

multicast user ports of a VPLS.

ZXR10(config)#show ip igmp snooping port-info ip-global Displays the information about

multicast user port on a public

network.

ZXR10(config)#show ip igmp snooping summary Displays statistics of multicast

entries.

ZXR10(config)#show ip igmp snooping summary vlan <vlan-id> Displays statistics of multicast

entries in a VLAN.

ZXR10(config)#show ip igmp snooping summary vpls

<vpls-name>

Displays statistics of multicast

entries in a VPLS instance.

ZXR10(config)#show ip igmp snooping summary port-info Displays statistics of multicast

user ports.

ZXR10(config)#show ip igmp snooping summary port-info

ip-global


user ports on a public network.

ZXR10(config)#show ip igmp snooping summary port-info vlan

<vlan-id>


user ports in a VLAN.

3-8



Command Function

ZXR10(config)#show ip igmp snooping summary port-info vpls

<vpls-name>


user ports in a VPLS instance.

ZXR10(config)#show ip igmp snooping summary mr-port-info Displays statistics of routing ports.

The following is sample output from the show ip igmp snooping command:

ZXR10#show ip igmp snooping

Flags: Type--Instance Type, ID--Instance ID, Dr--Drop,

P--Prejoin, R--Remote, MH--MaxHost, S--Static, D--Dynamic

IP-G:IP-GLOBAL

Index Type ID Name Source Group Flag MH Ports

--------------------------------------------------------------------------------

1 VLAN 1 -- 0.0.0.0 225.0.0.1 -- 4000 D:gei-0/1/1/6



Index Serial number of an entry.

Type Instance type of an entry.

ID Instance ID of an entry.

Name Instance name of an entry.

Source Source address of an entry.

Group Multicast group address of an entry.

Flag Multicast group flag: drop, or prejoin.

MH The maximum number of users supported by the multicast group.

Ports User information of the multicast group.

The following is sample output from the show ip igmp snooping mr-port-info command:

ZXR10(config)#show ip igmp snooping mr-port-info

Index VLAN VPNID Port State Version Time

--------------------------------------------------------

1 1 0 gei-0/1/1/2 Static V2Query 65535

2 1 0 gei-0/1/1/1 Static V2Query 65535

ZXR10(config)#




3-9




VLAN VLAN instance ID of an entry.

VPNID VPLS instance ID of an entry.

Port Routing port.

State State of a routing port.

Version Type of IGMP packets processed by a routing port by default.

Time Aging time of a routing port.

The following is sample output from the show ip igmp snooping query command:

ZXR10(config-igmpsnoop-vlan1)#show ip igmp snooping query

IGMP snooping querier is disable.

IGMP snooping querier is not working.

IGMP snooping query interval is 125s.

IGMP snooping query response interval is 10000ms.

The following is sample output from the show ip igmp snooping ndl-port-info command:

ZXR10(config-igmpsnoop-vlan1)#show ip igmp snooping ndl-port-info

Index VLAN VPNID Port

-----------------------------

1 1 0 gei-0/1/1/1

2 1 0 gei-0/1/1/2




VLAN VLAN instance ID of an entry.

VPNID VPLS instance ID of an entry.

Port Port where it is prohibited to learn dynamic routes.

3.4 IGMP Snooping Configuration ExampleConfiguration DescriptionFigure 3-1 shows a network topology. Router A is connected to the multicast sourcethrough gei-0/1/1/1, and it is connected to switch A through gei-0/1/1/2. Router A runsIGMPv2, and switch A runs IGMPv2 snooping. Router A operates as the IGMP querier.

3-10



Figure 3-1 IGMP Snooping in a VLAN Instance

Purpose

Host A and host B can receive multicast data sent to multicast group 225.0.0.1. Whenreceiving unknown multicast data, switch A drops the data directly to prevent the datafrom being broadcast in the VLAN.

Configuration Flow1. Configure router A

Enable the IP multicast function, enable PIM-SM on the layer-3 interfaces, and enableIGMP on gei-0/1/1/2.

2. Configure switch A

a. Enable the IGMP snooping function globally.

b. Create VLAN 10, and add gei-0/1/1/1 and gei-0/1/1/4 to the VLAN. Enable theIGMP snooping function in the VLAN.

c. Simulate the hosts to join multicast group 225.0.0.1 on gei-0/1/1/2 and gei-0/1/1/4.

Configuration CommandsConfiguration of router A:

SwitchA(config)#interface gei-0/1/1/2

RouterA(config-if-gei-0/1/1/2)#ip address 10.0.0.1 255.255.255.0

RouterA(config-if-gei-0/1/1/2)#exit

RouterA(config)#ip multicast-routing

RouterA(config-mcast)#router pim

RouterA(config-mcast-pim)#interface gei-0/1/1/2

RouterA(config-mcast-pim-if-gei-0/1/1/2)#pimsm

RouterA(config-mcast-pim-if-gei-0/1/1/2)#exit

RouterA(config-mcast-pim)#exit

3-11



RouterA(config-mcast)#router igmp

RouterA(config-mcast)#router igmp

RouterA(config-mcast-igmp-gei-0/1/1/2)#interface gei-0/1/1/2

RouterA(config-mcast-igmp-if-gei-0/1/1/2)#version 2

RouterA(config-mcast-igmp-if-gei-0/1/1/2)#exit

RouterA(config-mcast-igmp)#exit

RouterA(config-mcast)#exit

RouterA(config)#

RouterA(config)#interface gei-0/1/1/1

RouterA(config-if-gei-0/1/1/1)#ip address 1.1.1.2 255.255.255.0

RouterA(config-if-gei-0/1/1/1)#exit

RouterA(config)#ip multicast-routing

RouterA(config-mcast)#router pim

RouterA(config-mcast-pim)#interface gei-0/1/1/1

RouterA(config-mcast-pim-if-gei-0/1/1/1)#pimsm

RouterA(config-mcast-pim-if-gei-0/1/1/1)#exit

RouterA(config-mcast-pim)#exit

RouterA(config-mcast)#exit

RouterA(config)#

Configuration of switch A:

SwitchA#

SwitchA#configure terminal

Enter configuration commands, one per line. End with CTRL/Z.

SwitchA(config)#switchvlan-configuration

SwitchA(config-swvlan)#vlan 10

SwitchA(config-swvlan-sub)#switchport pvid gei-0/1/1/1

SwitchA(config-swvlan-sub)#exit










SwitchA(config-swvlan)#exit

SwitchA(config)#igmpsnoop

SwitchA(config-igmpsnoop)#igmp snooping enable

SwitchA(config-igmpsnoop)#vlan 10

SwitchA(config-igmpsnoop-vlan10)#igmp snooping enable

SwitchA(config-igmpsnoop-vlan10)#end

SwitchA#

3-12



Configuration VerificationCheck the detailed information about the IGMP snooping groups in VLAN 10 on switch Aas follows:

SwitchA(config)#show ip igmp snooping port-info vlan 10

Index VLAN Source Group State Time Ports

-----------------------------------------------------------------

1 10 0.0.0.0 225.0.0.1 V2Report 998 gei-0/1/1/2

2 10 0.0.0.0 225.0.0.1 V2Report 996 gei-0/1/1/4

SwitchA(config)#

3-13



This page intentionally left blank.

3-14


Chapter 4PIM-SM ConfigurationTable of Contents

PIM-SM Overview ......................................................................................................4-1Configuring PIM-SM...................................................................................................4-3Maintaining PIM-SM...................................................................................................4-7PIM-SM Configuration Examples..............................................................................4-14

4.1 PIM-SM OverviewIntroduction to PIM-SMThe PIM-SM is mainly used in the following situations:

l Group members locate sparsely in a relatively large scale.l The network bandwidth resource is limited.

The PIM-SM does not depend on a specific unicast routing protocol. The PIM-SMassumes that all switches on a shared segment do not need to send multicast packets.The switches only can receive and send multicast packets after they request for joiningin a multicast group. The PIM-SM notifies the multicast information to all switchessupporting the PIM-SM through a Rendezvous Point (RP). In the PIM-SM, a switch joinsin or leaves the multicast group explicitly. This reduces the number of packets and thebandwidth used by the control packets.

PIM-SM PrincipleThe PIM-SM sends multicast packets by using a shared tree. A shared tree has a centerpoint that is responsible for forwarding packets for all the multicast sources in the multicastgroup. Each multicast source sends packets to the center point along the shortest path,and then the center point forwards packets to various receiving ends of the group.

The group center point of the PIM-SM is called the RP. There may be multiple RPs on anetwork, but there is only one RP operating for a multicast group.

A switch can obtain the location of the RP in two ways.

l Configure the RP manually and statically on switches running the PIM-SM.l The PIM-SMv2 obtains the location through the candidate RP advertisement. The

candidate RP with the highest priority will become the formal RP.

In the PIM-SMv2, some PIM-SM switches are manually set to operate as candidateBootstrap Routers (BSRs). The candidate BSR with the highest priority will be electedas the formal BSR.

4-1



The BSR is responsible for collecting the candidate RP information on the multicastswitches in the group to find out the candidate RPs in the multicast domain. It notifiesthe candidate RPs to all the PIM switches in the PIM domain in a unified way. The PIMswitches elect a formal RP from the candidate RP set according to rules the same asthat of RP election. Candidate RPs are configured manually.

The PIM-SM switches discover each other and maintain the neighbor relationship byexchanging Hello messages. On the multi-access network, the Hello messages alsocontain the priority information of switches. The Designate Router (DR) is electedaccording to this parameter.

After receiving a multicast packet from the direct-connected source, the multicast sourceor the first-hop switch (the DR connecting to the source directly) encapsulates the packet ina Register message, and then sends it to the RP through a unicast switch. When receivingthe Register message, the RP de-encapsulates the messages to take out the packet, andthen sends the packet to the receivers of the group along the shared multicast tree.

Each host operating as a receiver joins the multicast group through the IGMP memberreport message. The last-hop switch (or the DP on the multi-access network) sends thereceived join message to the RP level by level. After receiving the join message, theintermediate switch checks whether it has already had the routes of the group. If it has,the intermediate switch adds the downstream request switch to the shared multicast treeas a branch. If it does not, it creates a route and continues to send the join message tothe RP.

When the RP or the multicast switch connects to a receiver directly, it can switch to the SPTfrom the shared tree. When the RP receives a Register message sent from a newmulticastsource, the RP returns a joinmessage to the DR directly connecting to themulticast source.Thus, the SPT from the source to the RP is constructed.

After a DR or a switch directly connecting to multicast members receives the first multicastpacket from the multicast group, or the received packets reaches a threshold, it can switchto the SPT from the shared tree. Once the handover occurs, the switch sends a Prunemessage to the upstream neighbor and requests to leave the shared tree.

The PIM-SM has the following message types .

l Hello message: The switch interfaces on which PIM-SM runs send Hello messagesperiodically to the neighbor interfaces in the same segment to establish neighborrelationship. Hello messages are also used for switches running IGMPv1 to electthe DR.

l Register message: When receiving a multicast packet sent by a multicast source onthe local network, the DR encapsulates the packet in a Register message and sendit to the RP through unicast. The source address in the IP header of the Registermessage is the address of the DR, and the destination address is the address of theRP.

l Register-Stop message: The RP unicasts a Register-Stop message to the sender ofthe Register message to inform it stop sending Register messages.

4-2


Chapter 4 PIM-SM Configuration

l Join/Prune message: This message is forwarded in the direction to the source orthe RP. A Join message is used to construct a source tree or a shard tree. When areceiver leaves a group, it sends a Prune message to prune the source tree or theshard tree. This message contains the joining information and pruning informationof the multicast route entities. The Join message and the Prune message are in thesame packet. Either message can be null.

l Bootstrap message: A BSR generates a Bootstrap message and floods it in the entirePIM domain to advertise the information of the candidate RP set to all PIM switches.Meanwhile, BSR election is performed. All PIM switches need to forward this messageto all PIM switches after they pass through the RPF check.

l Assert message: When there are several switches on a multi-access network and amulticast group packet is received on an egress interface of a switch, it is necessaryto use the Assert message to designate a unique forwarder.

l Candidate-RP-Advertisement: A candidate RP unicastsCandidate-RP-Advertisement to the BSR periodically to advertise the set of groupaddresses served by the Candidate RP.

4.2 Configuring PIM-SMTo configure the PIM-SM function on the ZXR10 5900E, perform the following steps:


ZXR10(config-mcast)#router pim Enables PIM-SM.1

ZXR10(config-mcast)#no router pim Disables PIM-SM.

ZXR10(config-mcast-pim)#static-rp <ip-address>{[group-list <prefix-list_name>],[priority <priority>]}

Sets a static RP.

ZXR10(config-mcast-pim)#no static-rp <ip-address> Deletes a static RP.

ZXR10(config-mcast-pim)#static-rp override Sets the overriding of a static

RP.

ZXR10(config-mcast-pim)#no static-rp override Deletes the overriding of a

static RP.

ZXR10(config-mcast-pim)#interface <interface-name> Enters multicast PIM-SM

interface configuration mode.

ZXR10(config-mcast-pim)#no interface <interface-name> Deletes a PIM-SM interface.

ZXR10(config-mcast-pim)#bsr-candidate <interface-na

me>{[ hash-mask-length <hash-mask-length>],[priority<priority>]}

Sets a candidate BSR.

ZXR10(config-mcast-pim)#no bsr-candidate Deletes a candidate BSR.

ZXR10(config-mcast-pim)#rp-candidate <interface-name

>{[group-list < prefix-list-name >],[priority <priority>]}Sets a candidate RP.

2

4-3




ZXR10(config-mcast-pim)#no rp-candidate

<interface-name>

Deletes a candidate RP.

ZXR10(config-mcast-pim)#spt-threshold infinity

[group-list < access-list-name >]Sets switchover of the SPT.

The threshold is infinity.

ZXR10(config-mcast-pim)#no spt-threshold Deletes switchover from RPT

to SPT.

ZXR10(config-mcast-pim)#accept-register <

access-list-name >

Filters the multicast packets

encapsulated in Register

messages.

ZXR10(config-mcast-pim)#no accept-register Disables to filter the packets

encapsulated in Register

messages.

ZXR10(config-mcast-pim)#accept-rp <access-list-name> Filters the candidate RP

addresses advertised in the

Bootstrap messages.

ZXR10(config-mcast-pim)#no accept-rp Disables to filter the candidate

RP addresses.

ZXR10(config-mcast-pim)#anycast-rp-local

<interface-name>

Sets anycast-rp local interface.

ZXR10(config-mcast-pim)#no anycast-rp-local Deletes anycast-rp local

interface.

ZXR10(config-mcast-pim)#anycast-rp-peer <ip-address> Sets anycast-rp peer address.

ZXR10(config-mcast-pim)#no anycast-rp-peer

<ip-address>

Deletes anycast-rppeer

address.

ZXR10(config-mcast-pim)#bsm-unicast Sets unicasting BSR

messages.

ZXR10(config-mcast-pim)#no bsm-unicast Disables to unicast BSR

messages.

ZXR10(config-mcast-pim)#data-filter <access-list-name> Sets PIM source data filter.

ZXR10(config-mcast-pim)#no data-filter Deletes PIM source data filter.

ZXR10(config-mcast-pim)#rp-smart Sets smart RP switch.

ZXR10(config-mcast-pim)#no rp-smart Deletes smart RP switch.

ZXR10(config-mcast-pim)#dr-switchback-delay

<seconds>

Sets the time of recalculating

route after the DR turns into

non-DR while BFD is enabled

on the interface.

4-4




ZXR10(config-mcast-pim)#no dr-switchback-delay Sets that there is no DR

switchback delay.

ZXR10(config-mcast-pim)#join-prune-holdtime <seconds

>

Sets the holdtime of sending

Join/Prune messages.

ZXR10(config-mcast-pim)#no join-prune-holdtime Deletes the holdtime of sending

Join/Prune messages.

ZXR10(config-mcast-pimsm)#register-probe-interval

<seconds>

Sets the interval of sending

register probe packets to the

RP.

ZXR10(config-mcast-pim)#no register-probe-interval Deletes the interval of sending

register probe packets to the

RP.

ZXR10(config-mcast-pim)#register-suppression-interval

<seconds>

Sets the interval of maintaining

the register suppression state.

ZXR10(config-mcast-pim)#no register-suppression-inter

val

Deletes the interval of

maintaining the register

suppression state.

ZXR10(config-mcast-pim)#rp-proxy Enables processing Join/Prune

messages without RP

information.

ZXR10(config-mcast-pim)#no rp-proxy Enables checking RP

information before processing

of Join/Prune messages. If

RP information is not provided,

Join/Prune messages are

dropped.

ZXR10(config-mcast-pim)#register-source

<interface-name>

Configures the source address

of register messages.

ZXR10(config-mcast-pim)#no register-source Restores the default source

address of register messages,

meaning the next hop of the

unicast route to the source.

4-5




ZXR10(config-mcast-pim-if-interface-name)#pimsm Enables PIM-SM on an

interface.

ZXR10(config-mcast-pim-if-interface-name)#no

pimsm

Disables PIM-SM on an

interface.

ZXR10(config-mcast-pim-if-interface-name)#pimdm Enables PIM-DM on an

interface.


pimdm

Disables PIM-DM on an

interface.

ZXR10(config-mcast-pim-if-interface-name)#dr-pr

iority <priority>

Sets the DR priority on a PIM

interface.


dr-priority

Restores the default DR

priority.

ZXR10(config-mcast-pim-if-interface-name)#dr-ign

ore

Enables ignoring the DR.


dr-ignore

Disables ignoring the DR.

ZXR10(config-mcast-pim-if-interface-name)#bsr-b

order

Sets an interface to the border

of the PIM domain.


bsr-border

Cancels the configuration of

the PIM domain.

ZXR10(config-mcast-pim-if-interface-name)#hello-in

terval <seconds>

Sets the interval to send Hello

messages.


hello-interval

Restores the default interval to

send Hello messages.

ZXR10(config-mcast-pim-if-interface-name)#neighb

or-filter < access-list-name >

Restricts PIM-SM neighbors.


neighbor-filter

Cancels the restriction of

PIM-SM neighbors.

ZXR10(config-mcast-pim-if-interface-name)#asse

rt-disable

Disables the asserting function

on an interface.


assert-disable

Recovers the asserting function

on an interface.

ZXR10(config-mcast-pim-if-interface-name)#bfd-

enable

Enables BFD on an interface.

3


bfd-enable

Disables BFD on an interface.

Descriptions of parameters in Step 2:

4-6




<ip-address> Static RP address, in the dotted decimal notation.

<prefix-list-name> Group range in which the RP provides services.


<hash-mask-length> Hash mask length, in the range of 0-32.

<access-list-name> ACL name, with 1-31 characters.



<priority> Priority.

<seconds> The interval to send Hello messages on a PIM switch. It is in the

range of 1-65535, in the unit of second. The default value is 30

seconds.

4.3 Maintaining PIM-SMTo maintain the PIM-SM function on the ZXR10 5900E, run the following commands.

Command Function

ZXR10#show ip pim mroute [group <group-address>][source<source-address>]

Displays the PIM-SM routing table.

ZXR10#show ip pim mroute summary Displays the summary information

of the routing table.

ZXR10#show ip pim bsr Displays the information of the

BSR.

ZXR10#show ip pim rp mapping Displays all the RP mapping

information .

ZXR10#show ip pim rp hash <group-address> Displays the RP information

selected by a specific multicast

group.

ZXR10#show ip pim interface [<interface-name>] Displays the interface on which

PIM-SM is configured.

ZXR10#show ip pim neighbor [<interface-name>] Displays the neighbor information

of a PIM-SM interface.

ZXR10#show ip pim nexthop [dest-address <ip-address>] Displays the PIM-SM next hop

information.

ZXR10#show ip pim bfd [<interface-name>] Displays PIM-SM BFD information.

4-7



Command Function

ZXR10#show ip pim traffic [<interface-name>] Displays PIM-SM traffic statistic

information.

ZXR10#clear ip pim traffic [<interface-name>] Clears PIM-SM traffic statistic

information.



<group-address> Multicast group address, in the dotted decimal notation.

<source-address> Source address, in the dotted decimal notation.


The following is sample output from the show ip pim mroute command:

ZXR10#show ip pim mroute

PIM Multicast Routing Table

Flags: T- SPT-bit set,A- Forward,J- Join SPT,U- Upsend,S- PIM-SM,D- PIM-DM,

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)

(3.1.1.1, 224.1.1.1), 00:00:21/00:00:00(JOINED)/00:00:00,

Reg:NO INFO; RP:2.2.2.2; RT:NULL;

Ind:1/Exd:0/Jns:0/LAst:0/Imo:1/Ino:1

Iif:NULL; RPF nbr:0.0.0.0(S/D);

Oif:

vlan1, LocalInSG / InoSG

(*, 225.1.1.1), 00:00:21/00:00:39(JOINED), RP address: 2.2.2.2,

Ind: 1/Jns: 0/LAst: 0/Imo: 1/Lcd: 1

Iif: NULL, RPF nbr: 0.0.0.0

Oif:

vlan1, LocalIn / ImoXG



T Multicast packets from the SRT are received through the route.

A The inbound interface of the route is valid.

U Multicast packets are sent through the route.

J Data flows are switched to the SPT.

4-8




Ind Number of interfaces that joins an IGMP group and receives data

flows.

Exd Number of interfaces that joins an IGMP group but does not

receive data flows.

Jns Number of interfaces that there is a downstream device receiving

data flows.

LAst Number of interfaces that receives data flows but failed to assert.

Imo Number of interfaces that are created in accordance with route

types directly.

Ino Number of interfaces that inherits other route types.

Uptime/Expires The operating time and expiration time of an entry/outbound

interface.

RP address RP corresponding to the (*, G) entry generated by PIM-SM.

Iif Inbound interface of an entry.

RPF nbr RPF neighbor of the corresponding entry.

Oif Outbound interface list.

The following is sample output from the show ip pim mroute summary command:

ZXR10#show ip pim mroute summary

PIM Multicast Routing Table Summary

(*, G):2 , (S, G):0, (S, G, rpt):0, Register:0

(*, 225.1.1.1) (JOINED), RP: 0.0.0.0

(*, 239.255.255.250) (JOINED), RP: 0.0.0.0

The following is sample output from the show ip pim bsr command:

ZXR10#show ip pim bsr

BSR address: 1.1.1.1

Uptime: 00:00:09, BSR Priority :0, Hash mask length:30

Expires:00:00:51

This system is a candidate BSR!

candidate BSR address: 1.1.1.1(loopback1),

priority: 0,

hash mask length: 30

This system is a candidate RP!

candidate RP address: 1.1.1.1(loopback1),priority:99

4-9





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 name, priority and other information of the

RP configured locally.

The following is sample output from the show ip pim rp mapping command:

ZXR10##show ip pim rp mapping

Group(s): 224.0.0.0/4(SM)

RP: 2.2.2.2, v2, Priority:192

BSR: 2.2.2.2, via bootstrap

Uptime: 00:03:07, Expires: 00:02:14

Group(s): 224.0.0.0/4(SM)

RP: 2.2.2.2, Static, Priority:192

Group(s): 0.0.0.0/0(NOUSED)



Group(s) Address and mask of the multicast group .

RP Address, version, priority and other information of the candidate

RP advertised by the multicast group.

BSR IP address of the BSR.

uptime Uptime of the candidate RP.

expire Expiring time of the candidate RP.

Static The candidate RP is statically configured instead of advertised

by the BSR.

The following is sample output from the show ip pim rp hash command:

ZXR10#show ip pim rp hash 224.0.1.40

rp address: 1.1.1.10

4-10



For a description of the parameter in the execution result, refer to the following table:


rp address RP address selected by a specific multicast group.

The following is sample output from the show ip pim interface command:

ZXR10#show ip pim interface

Address Interface State Nbr Hello DR DR PIM Mode

Count Period Priority Silent

2.1.1.1 vlan1 Up 0 30 1 2.1.1.1 Disabled S




Address Interface address.

Interface Interface name.

Nbr-Count 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.

PIM Silent Whether the PIM Silent function is enabled on the interface.

Mode PIM-SM or PIM-DM mode on the interface.

The following is sample output from the show ip pim neighbor command:

ZXR10#show ip pim neighbor

Neighbor Address Interface DR Priority Uptime Expires Ver

1.1.1.1 vlan1 1 00:15:08 00:01:24 V2



Neighbor Address IP address of the neighbor.


DR Priority DR priority of the neighbor.

Uptime Uptime of the neighbor.

Expires Expiring time of the neighbor.

Ver Version.

The following is sample output from the show ip pim nexthop command:

4-11



ZXR10#show ip pim nexthop

PIM 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,

Dest:2.2.2.2 (00:00:56)

Type:.R. .O. .L.

Metric:0

Preference:0

Ecmp list:

Nexthop:2.2.2.2(is Local)

Port:loopback1

Dest:3.1.1.1 (00:02:46)

Type:. .S. .U. .

Metric:

Preference:

Ecmp list:


Parameter Destination

Dest Destination IP address.

Type Type of a next hop route.

Metric Metric of a next hop route.

Preference Priority of a next hop route.

Nexthop IP address of a next hop.

port Egress interface of a unicast route.

The following is sample output from the show ip pim bfd command:

ZXR10#show ip pim bfd

interface BFD Local_Addr BFD Peer_Addr State

vlan1 13.13.13.16(BDR) 13.13.13.17(DR) CONNECT



interface BFD interface name.

BFD Local_Addr BFD local address.

BFD Peer_Addr BFD peer address.

State Interface state.

The following is sample output from the show ip pim traffic command:

4-12



ZXR10#show ip pim traffic

PIM packet receive:

Interface Hel Reg Reg-st J/P Bst

Ast Grf Grf-ack C-RP-Ad Sta-ref

vlan1 0 0 0 0 0

0 0 0 0 0

PIM packet send:



vlan1 23 0 0 0 0

0 0 0 0 0

Total traffic in current PIM instance:

Summary_pkt Hel Reg Reg-st J/P Bst


RCV_type 0 0 0 0 0

0 0 0 0 0

SEND_type 894 0 0 0 0

0 0 0 0 0

pkt_rcv_all 0

pkt_rcv_error 0 pkt_rcv_ok_notpim 0

xg_Prune_rcv 0 sg_Prune_rcv 0

mgmd_xglev_rcv 0 mgmd_sginlev_rcv 0

pkt_send_all 894

data_rcv_all 0 wrong_data_rcv 0

data_send_all 0 wrong_data_send 0




Hel Number of Hello messages.

Reg Number of Register messages.

Reg-st Number of Register stop messages.

J/P Number of Join/Prune messages.

Bst Number of BSM messages.

Ast Number of Assert messages.

Grf Number of Grafting messages.

Grf-ack Number of Grafting ACK messages.

C-RP-Ad Number of CRP report messages.

Sta-ref Number of State refreshing messages.

The following is sample output from the clear ip pim traffic command:

4-13



ZXR10#clear ip pim traffic

ZXR10#show ip pim traffic

PIM packet receive:



vlan1 0 0 0 0 0

0 0 0 0 0

PIM packet send:



vlan1 0 0 0 0 0

0 0 0 0 0

Total traffic in current PIM instance:

Summary_pkt Hel Reg Reg-st J/P Bst


RCV_type 0 0 0 0 0

0 0 0 0 0

SEND_type 0 0 0 0 0

0 0 0 0 0

pkt_rcv_all 0

pkt_rcv_error 0 pkt_rcv_ok_notpim 0

xg_Prune_rcv 0 sg_Prune_rcv 0

mgmd_xglev_rcv 0 mgmd_sginlev_rcv 0

pkt_send_all 0

data_rcv_all 0 wrong_data_rcv 0

data_send_all 0 wrong_data_send 0

4.4 PIM-SM Configuration Examples

4.4.1 Forwarding Multicast Flow through PIM-SM (Dynamic RP)

Configuration DescriptionAs shown in Figure 4-1, an IGMP group connects to S2, and a multicast source connectsto S1. Configure a BSR and a candidate RP.

Figure 4-1 Forwarding Multicast Flow through PIM-SM (Dynamic RP)

4-14



Configuration Flow1. Configure corresponding interfaces.2. Enter multicast configuration mode.3. Enter PIM-SM configuration mode.4. Set the loopback5 interface of S2 to the CRP and the BSR.5. Enable PIM-SM on interfaces.6. Configure a unicast route to the RP on S1. Configure a unicast route to the multicast

source on S2 .

Configuration CommandsThe configuration of S1:







S1(config-mcast-pim-if-vlan2)#dr-priority 20


S1(config)#ip route 5.5.5.35 255.255.255.255 199.1.1.2

The configuration of S2:



S2(config-mcast-pim)#rp-candidate loopback5

S2(config-mcast-pim)#bsr-candidate loopback5








S2(config-mcast-pim)#interface loopback5

S2(config-mcast-pim-if-loopback5)#pimsm

S2(config-mcast-pim-if-loopback5)#exit



S2(config)#ip route 33.1.1.0 255.255.255.0 199.1.1.1

Configuration VerificationUse the show ip pim interface command on S1 to check the interface state, as shownbelow.

4-15



S1(config)#show ip pim interface





Use the show ip pim neighbor command on S1 to check the neighbor state, as shownbelow.

S1(config)#show ip pim neighbor


199.1.1.2 valn1 1 00:07:48 00:01:23 V2

Use the show ip pim bsr command on S1 to check the BSR state, as shown below.

S1(config)#show ip pim bsr

BSR address: 5.5.5.35

Uptime: 00:00:40, BSR Priority :0, Hash mask length:30

Expires:00:01:30

This system is a candidate BSR!

candidate BSR address: 5.5.5.35 (loopback5),

priority: 0,

hash mask length: 30

This system is a candidate RP!

candidate RP address: 5.5.5.35 (loopback5),priority:192

S1(config)#show ip pim 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


Use the show ip mroute command on S2, as shown below.S2(config)#show ip mroute

IP Multicast Routing Table

Flags:NS:SPT upsend, RT:Reg upsend, MT:tunnel, F:Forward, S:Syn mrt,

NTP:NTP join, FLT:Flt add, FD:Flt del, DPU:Damping enable, DPD:Damping del,

(*, 225.10.0.1), RP: 5.5.5.35, TYPE: DYNAMIC, FLAGS:

Incoming interface: NULL, flags:

Outgoing interface list:

vlan2, flags: F/S

(33.1.1.2, 225.10.0.1), RP: 5.5.5.35, TYPE: DYNAMIC, FLAGS:

Incoming interface: vlan1, flags:


vlan2, flags: F/S

4-16



4.4.2 Forwarding Multicast Flow through PIM-SM (Static RP)

Configuration DescriptionAs shown in Figure 4-2, an IGMP group connects to S2, and a multicast source connectsto S1. Configure PIM-SM neighbors and static RP.

Figure 4-2 Forwarding Multicast Flow through PIM-SM (Static RP)

Configuration Flow1. Enter multicast configuration mode.2. Enter PIM-SM configuration mode.3. Set 5.5.5.35 as a static RP, and configure static RP overriding.4. Enable PIM-SM on interfaces.5. Configure a unicast route to the RP on S1. Configure a unicast route to the multicast

source on S2 (In this example, static route is used).










S1(config-mcast-pim)#static-rp 5.5.5.35

S1(config-mcast-pim)#static-rp override


S1(config)#ip route 5.5.5.35 255.255.255.255 199.1.1.2




S2(config-mcast-pim)#static-rp 5.5.5.35

S2(config-mcast-pim)#static-rp override

4-17















S2(config)#ip route 33.1.1.0 255.255.255.0 199.1.1.1

Configuration VerificationUse the show ip pim interface command on S1 to check the interface state, as shownbelow.






Use the show ip pim neighbor command on S1 to check the neighbor state, as shownbelow.



199.1.1.2 valn1 1 00:07:48 00:01:23 V2

Use the show ip pim rp mapping command on S1 to check the RP state, as shown below.

S1(config)#show ip pim 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


4.4.3 Illegal Multicast Source Control

Configuration DescriptionMulticast protocol does not provide any control of the multicast source validity. Any usercan work as the multicast source to send multicast traffic to the networks. Illegal multicastsource filter can be configured to prevent unauthorized multicast sources from sendingmulticast traffic to the networks.

4-18



As shown in Figure 4-3, Source 1 sends multicast data to the user. There are another twoillegal 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.

The illegal source control policy consists of the source filter configured on the first-hoprouter and the source register filter configured on the RP. The source filter configured onthe first-hop router can prevent illegal sources from sending multicast data to the networkas early as possible. The source register filter configured on the RP can prevent illegalsources from registering on the RP. It is easy to configure and manage if the method thatconfiguring source register filter on the RP is used. However, the traffic sent by the illegalsources is still transmitted between the first-hop router and the RP, and the users on thefirst-hop router still can receive the illegal multicast data. In practical applications, the twomethods are used together, which can improve the management efficiency and networksecurity.

Figure 4-3 Illegal Multicast Source Control

Configuration Flow1. Configure source filter on the first-hop router.2. Configure source register filter on the RP.

Configuration CommandsConfigure IP addresses on the interfaces of S1 and S2 according to the following table toensure the IP connectivity on the network.

Switch Interface IP Address Mask

S1 vlan1 172.1.3.44 255.255.255.0

S1 vlan2 172.2.3.44 255.255.255.0

S1 vlan3 172.3.3.44 255.255.255.0

S1 vlan4 172.1.7.44 255.255.255.0

4-19



Switch Interface IP Address Mask

S1 loopback63 44.63.1.1 255.255.255.255

S2 vlan2 172.1.5.46 255.255.255.0

S2 vlan1 172.1.7.46 255.255.255.0

S2 loopback63 46.63.1.1 255.255.255.255

Configure a multicast protocol on S1 and S2 to establish a multicast tree from the sourceto the user. Here take PIM-SM as an example.

The configuration of S1 (enable PIM-SM on the interfaces, and configure a BSR onloopback63 interface):


















S1(config-mcast-pim)#bsr-candidate loopback63


The configuration of S2 (enable PIM-SM on the interfaces, and configure an RP onloopback63 interface):












4-20



S2(config-mcast-pim)#rp-candidate loopback63


Configure illegal source control policies on S1 and S2.

The configuration of the source S2 filter policy on S1:

S1(config)#ipv4-access-list aclUnwantedSource

S1(config-ipv4-acl)#rule deny ip 172.2.3.49 0.0.0.0 any

S1(config-ipv4-acl)#rule permit ip any any




S1(config-mcast-pim)#data-filter aclUnwantedSource

The configuration of the source S3 register filter policy on S2:

S2(config)#ipv4-access-list aclWantedSource

S2(config-ipv4-acl)#rule deny ip 172.3.3.49 0.0.0.0 any

S2(config-ipv4-acl)#rule permit ip any any




S2(config-mcast-pim)#accept-register aclWantedSource

Configuration VerificationUse the show ip mroute command on S1 and S2 to check the multicast routes. Becausecontrol policies are configured on S1 and S2, only multicast data sent by the legal sourceS1 can be forwarded to the user. The multicast traffic received by the user does not includethe data sent by the illegal sources.

According to the above configurations, there is still a route of Source 3. However, becauseillegal source register filter policy for Source 3 is configured on the S2, the multicast trafficfrom Source cannot reach the user.

The multicast routes on S1 are shown below.

S1#show ip mroute










Vlan4, flags: F/S

The multicast routes on S2 are shown below.

4-21



S2#show ip mroute







vlan2, flags: F/S




vlan2, flags: F/S




vlan2, flags: F/S




vlan2, flags: F/S

4-22


Chapter 5PIM-SSM ConfigurationTable of ContentsPIM-SSM Overview ....................................................................................................5-1Configuring PIM-SSM.................................................................................................5-1PIM-SSM Configuration Example ...............................................................................5-2

5.1 PIM-SSM OverviewThe PIM-SSM has all advantages of the PIM-SM. The PIM-SSM does not construct ashared tree. Instead, it only constructs the SPT. When receiving member relation reportmessages about a specific source and a group, the PIM-SSM constructs the SPT directly.

The PIM-SSM is a subset of the PIM-SM. The PIM-SSM is suitable for the well knownsources. It is both intra-domain and inter-domain valid. The PIM-SM uses MulticastSource Discovery Protocol (MSDP) for inter-domain multicast routing. The PIM-SSMdoes not need to use the MSDP. The multicast group address allocated for the PIM-SSMis 232.0.0.0/8. The switches 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 switchsends a (S, G) Join message to the direction of the source to construct a Shortest PathTree (SPT). The last hop switch does not send a (*, G) Join message to the direction ofRP. Once the SPT is constructed, the first-hop switch forwards packets along this tree.

5.2 Configuring PIM-SSMTo configure PIM-SSM on the ZXR10 5900E, perform the following steps:

Step Command Dunction

ZXR10(config-mcast-pim)#ssm enable Enables PIM-SSM.1

ZXR10(config-mcast-pim)#no ssm enable Disables PIM-SSM.

2 ZXR10(config-mcast-pim)#ssm range [default|group-list< access-list-name >]

Sets the address range of a

PIM-SSM group.

3 ZXR10(config-mcast-pim)#no ssm range Deletes the address range of a

PIM-SSM group.

Descriptions of parameter in Step 2:


< access-list-name > ACL name, with 1-31 characters

5-1



5.3 PIM-SSM Configuration ExampleConfiguration DescriptionFigure 5-1 shows the network topology og a PIM-SSM configuration example. PIM-SMis enabled on S1, and SSM is configured. Configure the SSM group range (by default,it is 232.0.0.0/8). In this configuration example, IGMPv3 is used. The Tester 2 sendsdynamic Join messages to the specific source. The Tester 1 sends flows to multicastgroups of multiple specific sources. Only the traffic matching both the source address andthe multicast group address is allowed to pass through.

Figure 5-1 PIM-SSM Configuration Example

Configuration Flow1. In interface configuration mode, configure IP addresses of interfaces vlan1 and vlan2

for the VLAN.2. Enable IP multicast function by using the ip multicast-routing command.3. Enter PIM-SM route configuration mode to configure the ssm enable and ssm range

default commands.4. Enter interfaces vlan1 and vlan2 to enable PIM-SM.5. Enter IGMP route configuration mode and then enter interface vlan2. Configure IGMP

v3 on the interfaces.6. Send dynamic group Join messages to the specific source on the receiving group.










S1(config-mcast-pim)#ssm enable

S1(config-mcast-pim)#ssm range default



5-2


Chapter 5 PIM-SSM Configuration


S1(config-mcast-igmp-if-vlan2)#version 3

S1(config-mcast-igmp-if-vlan2)#exit

Configuration VerificationRun the show running-config multicast command to check the configuration on S1.

S1#show running-config multicast

! <ip multicast>


router pim

ssm enable

ssm range default

interface vlan2

pimsm

$

interface vlan1

pimsm

$

$

router igmp

interface vlan2

version 3

$

$

! </ip multicast>

Run the show ip mroute command to check the result on S1.

S1#show ip mroute




(15.1.1.1, 232.0.0.1), RP: 0.0.0.0, TYPE: DYNAMIC, FLAGS: NS

Incoming interface: vlan1, flags: NS


vlan2, flags: F/S /*Generating (S,G) entity*/

5-3




5-4


Chapter 6PIM-DM ConfigurationTable of Contents

PIM-DM Overview ......................................................................................................6-1Configuring PIM-DM...................................................................................................6-1Maintaining PIM-DM...................................................................................................6-2PIM-DM Configuration Example .................................................................................6-4

6.1 PIM-DM OverviewThe PIM-DM is suitable for the dense mode, which means that the protocol is for a networkarchitecture that has multiple multicast receivers exist on the network and are located onmost network devices. Based on the above application model, the PIM-DM mechanism isrelatively simple. It uses the PUSH mode to spread the multicast traffic to all devices onthe network periodically, and then constructs and maintains the SPT.

PIM-DM is a multicast routing protocol of dense mode. It use the "PUSH" mode to forwardmulticast data. Generally, it is used in small-scale network in which the multicast groupmembers are relatively dense.

l The PIM-DM assumes that there is at least one multicast group member in eachsubnet of the network. Therefore, multicast data is spread to all nodes on the network.

l The PIM-DM prunes the branches on which there is no multicast data forwarded. Itonly keeps the branches containing receivers. The procedure "spreading-pruning"occurs periodically. The pruned branches may recover to the forwarding stateperiodically.

l When a multicast group member appears on a node on a branch that was pruned, thenode will recover to the forwarding state from the pruning state by actively sendinggraft messages to the upstream to forward multicast data.

6.2 Configuring PIM-DMTo configure the PIM-DM function on the ZXR10 5900E, perform the following steps:


ZXR10(config-mcast)#router pim Enables PIM.1

ZXR10(config-mcast)#no router pim Disables PIM.

6-1




2 ZXR10(config-mcast-pim)#interface <interface-name> Enters PIM interface

configuration mode. The

parameter <interface-name> is

the interface name.

3 ZXR10(config-mcast-pim)#no interface <interface-name> Deletes the PIM interface

configuration.

4 ZXR10(config-mcast-pim-if-interface-name)#pimdm Enables PIM on an interface.

5 ZXR10(config-mcast-pim-if-interface-name)#no

pimdm

Disables PIM on an interface.

6.3 Maintaining PIM-DMTo maintain the PIM-DM function on the ZXR10 5900E, run the following commands.

Command Function

ZXR10#show ip pim interface [<interface-name>] Displays the PIM interface

information. The parameter

<interface-name> is the interface

name.

ZXR10#show ip pim mroute [group <group-address>|[source<source-address>]]

Displays the PIM multicast routing

table.

ZXR10#show ip pim mroute summary Displays statistics of an IP

multicast PIM routing table.

ZXR10#show ip pim neighbor [<interface-name>] Displays the information of a PIM

interface neighbor.



group <group-address> Multicast group address, in dotted decimal notation.

source <source-address> Source address, in dotted decimal notation.


summary Summary information.

The following is sample output from the show ip pim interface command output is shownbelow.

ZXR10#show ip pim interface



6-2


Chapter 6 PIM-DM Configuration

1.1.1.2 vlan1 Up 0 30 1 1.1.1.2 Disabled D



Address Interface address.

Interface interface name.

Nbr Count Number of neighbors.

State Interface state, up or down.

Hello Period Interval of sending HELLO messages.

DR DR of the interface.

DR Priority DR priority of the interface.

PIM Silent Whether the PIM Silent function is enabled on the interface.

Mode PIM-SM or PIM-DM mode on the interface.

The following is sample output from the show ip pim mroute command output is shownbelow.

ZXR10#show ip pim mroute

PIM Multicast Routing Table

Flags: T- SPT-bit set,A- Forward,J- Join SPT,U- Upsend,S- PIM-SM,D- PIM-DM,

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)

(3.1.1.1, 224.1.1.1), 00:07:31/00:00:00(JOINED)/00:00:00,

Reg:NO INFO; RP:2.2.2.2; RT:NULL;

Ind:1/Exd:0/Jns:0/LAst:0/Imo:1/Ino:1

Iif:NULL; RPF nbr:0.0.0.0(S/D);

Oif:

vlan1, LocalInSG / InoSG / DenseOlist



T The route entry receives multicast packets from the SPT tree.

A The ingress interface of the route entry is valid.

U The entry forwards multicast packets.

J Switches to the SPT when data flows are received.

Ind Number of interfaces that receive IGMP Join messages.

Exd Number of interfaces that do not receive IGMP Join messages.

6-3




Jns Number of interfaces that have downstream nodes to receive

data flows.

LAst Number of interfaces that receives data flows but fails to asserts.

Imo Number of egress interfaces created based on entry types.

Ino Number of egress interfaces that inherits other entry types.

Uptime/Expires Operational time/expiring time of an entry/egress interface.

Iif Ingress interface of an entry.

RPF nbr RPF neighbor of an entry.

Oif Egress interface list.

The following is sample output from the show ip pim neighbor command output is shownbelow.

ZXR10#show ip pim neighbor


10.9.1.2 vlan1 1 00:08:52 00:01:21 V2



Neighbor Address IP address of the neighbor.


DR Priority DR priority of the neighbor.

Uptime Uptime of the neighbor.

Expires Expiring time of the neighbor.

Ver Version number.

6.4 PIM-DM Configuration ExampleConfiguration DescriptionFigure 6-1 shows the network topology of a PIM-DM configuration example. S1 and S2establishes PIM-DM neighbor relationship.

Figure 6-1 PIM-DM Configuration Example

6-4


Chapter 6 PIM-DM Configuration

Configuration Flow1. Configure the corresponding interfaces.2. Enter multicast configuration mode.3. Enter PIM interface configuration mode.4. Enable PIM-DM on the corresponding interfaces.




S1(config-if-vlan3)#no shutdown









S1(config-mcast-pim-if-vlan3)#pimdm





The configuration commands of S2 are as follows:
















S2(config-mcast-pim-if-vlan8)#end

6-5



Configuration VerificationRun the show ip pim neighbor command on S1 to check the neighbor state.



199.1.1.2 vlan3 1 00:09:14 00:01:36 V2

Run the show ip pim interface command on S1 to check interface state.






Run the show ip mroute command on S1 to check the state of the IPv4 multicast routingtable.

S1#show ip mroute


Flags:NS:SPT upsend, RT:Reg upsend, MT:Tunnel, F:Forward, S:Syn mrt,





vlan3, flags: F/S

6-6


Chapter 7PIM Snooping ConfigurationTable of Contents

PIM Snooping Overview .............................................................................................7-1Configuring PIM Snooping..........................................................................................7-1Maintaining PIM Snooping..........................................................................................7-2PIM Snooping Configuration Example ........................................................................7-5

7.1 PIM Snooping OverviewPIM snooping is to complete dynamic register of L2 multicast. It uses PIM packets. PIMsnooping maintains L2 multicast groups dynamically by detecting different types of PIMpackets transmitted between switches.

When a backbone switch connects to several switches, the switch sends multicast packetson all route interfaces even if there is no downstream receivers on some switches. Thisincrease traffic on the network and reduces network efficiency. PIM snooping can limittraffic on the network, that is, the switch only sends multicast packets on the ports thatreceive PIM-SM Join packets sent by the downstream switches. When PIM snooping isenabled, the switch learns the Hello packets to obtain the corresponding relation betweenthe IP addresses of downstream switches and ports. The switch also learns the Join/Prunepackets to obtain the multicast route ports on which packets are to be received.

7.2 Configuring PIM SnoopingTo configure the PIM snooping function on the ZXR10 5900E, perform the following steps:


1 ZXR10(config)#pimsnoop Enters PIM snooping global

configuration mode.

2 ZXR10(config-pimsnoop)#pim snooping Enables PIM snooping globally.

3 ZXR10(config-pimsnoop)#vlan <vlan-id> Enters PIM snooping VPLS

configuration mode. The

<vpls-name> parameter is with

1-4094 characters.

4 ZXR10(config-pimsnoop-vlan)#pim snooping Sets PIM snooping function in

a VLAN.

7-1




5 ZXR10(config-pimsnoop)#vpls <vpls-name> Enters PIM Snooping VPLS

configuration mode.

6 ZXR10(config-pimsnoop-vpls-zte)#pim snooping Enables the PIM snooping

function in the VPLS instance.

7.3 Maintaining PIM SnoopingTo maintain the PIM snooping function on the ZXR10 5900E, run the following commands.

Command Function

ZXR10#show ip pim snooping entry Displays the information about all

multicast entries of PIM snooping.

ZXR10#show ip pim snooping entry vlan <vlan-id> Displays the information about all

multicast entries of PIM snooping

in a VLAN.

ZXR10#show ip pim snooping entry vpls <vpls-name> Displays the information about all

multicast entries of PIM snooping

in a VPLS instance.

ZXR10#show ip pim snooping neighbor-info Displays the information about

PIM snooping neighbors.

ZXR10#show ip pim snooping port-info vlan <vlan-id> Displays the information about

PIM snooping ports in a VLAN.

ZXR10#show ip pim snooping port-info vpls <vpls-name> Displays the information about

PIM snooping ports in a VPLS

instance.

ZXR10#show ip pim snooping summary entry Displays statistics of multicast

entries of PIM snooping.

ZXR10#show ip pim snooping summary entry vlan <vlan-id> Displays statistics of multicast

entries of PIM snooping in a VLAN.

ZXR10#show ip pim snooping summary entry vpls <vpls-name> Displays statistics of multicast

entries of PIM snooping in a VPLS

instance.

ZXR10#show ip pim snooping summary neighbor-info Displays statistics of PIM snooping

neighbors.

ZXR10#show ip pim snooping summary port-info Displays statistics of all PIM

snooping multicast entries.

7-2


Chapter 7 PIM Snooping Configuration

Command Function

ZXR10#show ip pim snooping summary port-info vlan <vlan-id> Displays statistics of all PIM

snooping multicast entries in a

VLAN.

ZXR10#show ip pim snooping summary port-info vpls <vpls-name> Displays statistics of all PIM

snooping multicast entries in a

VPLS instance.

The following is sample output from the show ip pim snooping entry command:

ZXR10#show ip pim snooping entry

Index VLAN VPLS Source-IP Group-IP

-----------------------------------------------

1 1 -- 1.1.1.1 225.1.1.1




VLAN VLAN ID of a multicast group.

VPLS VPLS instance ID of a multicast group.

Source-IP Source address.

Group-IP Multicast group address.

The following is sample output from the show ip pim snooping entry vlan command:

ZXR10#show ip pim sn entry vlan 1

Index VLAN Source-ip Group-ip

------------------------------------------

1 1 1.1.1.1 225.1.1.1





Source-ip Source address.

Group-ip Multicast group address.

The following is sample output from the show ip pim snooping neighbor-info command:

ZXR10#show ip pim snooping neighbor-info

Index Port VLAN VPLS Neighbor-ip RemainTime

7-3



------------------------------------------------------------

1 gei_0/1/1/1 10 0 168.2.0.11 240




Port Neighbor port.


VPLS VPLS instance ID of a multicast entry.

Neighbor-IP Neighbor address.

RemainTime Remaining aging time of a neighbor.

The following is sample output from the show ip pim snooping port-info vlan command:

ZXR10#show ip pim snooping port-info vlan 1

PIM snooping is globally enabled.

PIM snooping is enabled in this VLAN.

Index VLAN Source-IP Group-IP Ports Time

----------------------------------------------------------

1 1 2.2.2.3 229.0.0.3 gei-0/1/1/6 2979

2 1 2.2.2.2 229.0.0.3 gei-0/1/1/6 2979

3 1 2.2.2.3 229.0.0.2 gei-0/1/1/6 2979

4 1 2.2.2.2 229.0.0.2 gei-0/1/1/6 2979

5 1 2.2.2.3 229.0.0.1 gei-0/1/1/6 2979

6 1 2.2.2.2 229.0.0.1 gei-0/1/1/6 2979




VLAN VLAN ID of a multicast member.

Source-ip Source address of a multicast member.

Group-ip Multicast group address.

Ports Multicast member port.

Time Remaining aging time of a multicast member.

The following is sample output from the show ip pim snooping summary entry command:

ZXR10#show ip pim snooping summary entry

The summary information about group entry:

Type Summary

7-4



------------------------------------------

Total 2

Source-Specific 1

Anycast-Specific 1



Type Count type.

Summary Count.

7.4 PIM Snooping Configuration ExampleConfiguration DescriptionAs shown in Figure 7-1, gei-0/1/1/2 of PE1 connects to a CE switch, and gei-0/1/1/1connects to the P router. On PE2, gei-0/1/1/2 and gei-0/1/1/3 connect to the CE switches,and gei-0/1/1/1 connects to the P router. It is required to enable PIM snooping on PE1and PE2. It is unnecessary to enable PIM snooping on the P router.

Figure 7-1 PIM Snooping Configuration Example

Configuration Flow1. Configure a VLAN to make sure PE1 and PE2 in the same VLAN.2. Enable global PIM Snooping.3. Enable PIM Snooping in the VLAN.

Configuration CommandsThe configuration of PE1:

PE1(config)#switchvlan-configuration

PE1(config-swvlan)#vlan 1

PE1(config-swvlan-sub)#switchport pvid gei-0/1/1/1

7-5



PE1(config)#pimsnoop

PE1(config-pimsnoop)#pim snooping

PE1(config-pimsnoop)#vlan 1

PE1(config-pimsnoop-vlan1#pim snooping

The configuration of PE2:




PE2(config)#pimsnoop

PE2(config-pimsnoop)#pim snooping

PE2(config-pimsnoop)#vlan 1

PE2(config-pimsnoop-vlan1#pim snooping

Configuration VerificationAfter the configurations, a VPLS PW is established successfully. CE1 and CE2 aremulticast switches and they join a group. Check the entities generated on PE1 and PE2.

l The neighbor information and the route to the groupmember on PE1 are shown below.ZXR10#show ip pim snooping neighbor-info

Index Port VLAN VPLS Neighbor-IP RemainTime

-------------------------------------------------------------------------------

1 gei-0/1/1/1 1 0 3.3.3.2 1585

ZXR10#ZXR10#show ip pim snooping port-info vlan 1




-------------------------------------------------------------------------------

1 1 2.2.2.3 229.0.0.3 gei-0/1/1/2 2979

ZXR10#

l The neighbor information and the route to the groupmember on PE2 are shown below.ZXR10#show ip pim snooping neighbor-info

Index Port VLAN VPLS Neighbor-IP RemainTime

-------------------------------------------------------------------------------

1 gei-0/1/1/1 1 0 2.2.2.1 1585

ZXR10#show ip pim snooping port-info vlan 1



7-6




-------------------------------------------------------------------------------

1 1 2.2.2.3 229.0.0.3 gei-0/1/1/3 2979

ZXR10#

7-7




7-8


Chapter 8PIMv6 SnoopingConfigurationTable of Contents

PIMv6 Snooping Overview .........................................................................................8-1Configuring PIMv6 Snooping ......................................................................................8-1Maintaining PIMv6 Snooping ......................................................................................8-2PIMv6 Snooping Configuration Example ....................................................................8-5

8.1 PIMv6 Snooping OverviewPIMv6 snooping completes dynamic layer-2 multicast registration on switches. PIMv6snooping detects different types of IPv6 PIM packets transmitted between switches tomaintain layer-2 multicast groups dynamically.

When a backbone switch is connected to multiple switches, even if some switches haveno downstream receivers, the backbone switch sends multicast packets to all ports. Thisincreases traffic on networks, and reduces network efficiency.

If the PIMv6 snooping function is used, network traffic is limited, and switches sendmulticast packets only on the ports where IPv6 PIM-SM Join messages are received fromdownstream switches. The switches obtain relationships between IP addresses and portsof downstream switches through Hello messages, and obtain the multicast routing portsthat receive packets through Join or Prune messages.

8.2 Configuring PIMv6 SnoopingTo configure the PIMv6 snooping function on the ZXR10 5900E, perform the followingsteps:


1 ZXR10(config)#pimv6snoop Enters PIMv6 snooping global configuration

mode.

2 ZXR10(config-pimv6snoop)#pimv6

snooping enable

Enables the PIMv6 snooping function

globally.

3 ZXR10(config-pimv6snoop)#vlan <vlan-id> Enters PIMv6 snooping VLAN configuration

mode.

<vlan-id>: range of 1–4094.

8-1




4 ZXR10(config-pimv6snoop-vlan1)#pimv6

snooping enable

Enables the PIMv6 snooping function in the

VLAN.

5 ZXR10(config-pimv6snoop)#vpls

<vpls-name>

Enters PIMv6 snooping VPLS configuration

mode.

6 ZXR10(config-pimv6snoop-vpls-zte)#pi

mv6 snooping enable

Enables the PIMv6 snooping function in the

VPLS instance.

8.3 Maintaining PIMv6 SnoopingTo maintain the PIMv6 snooping function on the ZXR10 5900E, run the followingcommands.

Command Function

ZXR10#show pimv6 snooping entry Displays the information about all multicast

entries of PIMv6 snooping.

ZXR10#show pimv6 snooping entry vlan <vlan-id> Displays the information about all multicast

entries of PIMv6 snooping in a VLAN.

ZXR10#show pimv6 snooping entry vpls

<vpls-name>

Displays the information about all multicast

entries of PIMv6 snooping in a VPLS instance.

ZXR10#show pimv6 snooping neighbor-info Displays the information about PIMv6 snooping

neighbors.

ZXR10#show pimv6 snooping port-info vlan

<vlan-id>

Displays the information about PIMv6 snooping

ports in a VLAN.

ZXR10#show pimv6 snooping port-info vpls

<vpls-name>

Displays the information about PIMv6 snooping

ports in a VPLS instance.

ZXR10#show pimv6 snooping summary entry Displays statistics of PIMv6 snooping multicast

entries.

ZXR10#show pimv6 snooping summary entry vlan

<vlan-id>

Displays statistics of PIMv6 snooping multicast

entries in a VLAN.

ZXR10#show pimv6 snooping summary entry vpls

<vpls-name>

Displays statistics of PIMv6 snooping multicast

entries in a VPLS instance.

ZXR10#show pimv6 snooping summary

neighbor-info

Displays statistics of PIMv6 snooping neighbors.

ZXR10#show pimv6 snooping summary port-info Displays statistics of all PIMv6 snooping multicast

ports.

ZXR10#show pimv6 snooping summary port-info

vlan <vlan-id>

Displays statistics of all PIMv6 snooping multicast

ports in a VLAN.

8-2


Chapter 8 PIMv6 Snooping Configuration

Command Function

ZXR10#show pimv6 snooping summary port-info

vpls <vpls-name>

Displays statistics of all PIMv6 snooping multicast

ports in a VPLS instance.

The following is sample output from the show pimv6 snooping entry command:

ZXR10#show pimv6 snooping entry

Index VLAN VPLS Source Group

-----------------------------------------------

1 0 1 2001::1 ff03::1

2 1 0 2011::1 ff03::1




VLAN VLAN ID of a multicast entry.


Source Source address.

Group Multicast group address.

The following is sample output from the show pimv6 snooping entry vlan command:

ZXR10#show pimv6 snooping entry vlan 2

Index VLAN Source Group

---------------------------------------

1 2 2001::1 ff03::1





Source Source address.


The following is sample output from the show pimv6 snooping neighbor-info command:

ZXR10#show pimv6 snooping neighbor-info

Index Port VLAN VPLS Neighbor RemainTime

---------------------------------------------------------------

1 gei-0/1/1/1 0 1 2001::2002 240


8-3





Port Neighbor port.



Neighbor Neighbor address.

RemainTime Remaining aging time of a neighbor.

The following is sample output from the show pimv6 snooping port-info vlan command:

ZXR10#show pimv6 snooping port-info vlan 2

PIMv6 snooping is globally enabled.

PIMv6 snooping is enabled in this VLAN.

Index VLAN Source Group Ports RemainTime

---------------------------------------------------------------

1 1 2001::1 ff03::1 gei-0/1/1/1 200




VLAN VLAN ID of a multicast member.

Source Source address of a multicast member.


Ports Multicast member port.

RemainTime Remaining aging time of a multicast member.

The following is sample output from the show pimv6 snooping summary entry command:

ZXR10#show pimv6 snooping summary entry

The summary information about group entry:

Type Summary

--------------------------------------------

Total 2

Source-Specific 1

Anycast-Specific 1



Type Count type.

Summary Count.

8-4


Chapter 8 PIMv6 Snooping Configuration

8.4 PIMv6 Snooping Configuration ExampleConfiguration DescriptionFigure 8-1 shows a network topology. Gei-0/1/1/2 of PE1 is connected to CE1, andgei-0/1/1/1 is connected to P. Gei-0/1/1/2 and gei-0/1/1/3 of PE2 are connected to CE3and CE2 respectively, and gei-0/1/1/1 is connected to P.

Figure 8-1 PIMv6 Snooping Configuration Example

Purpose

Enable the PIMv6 snooping function on PE1 and PE2, and it is unnecessary to enable thePIMv6 snooping function on P.

Configuration Flow1. Create a VLAN, and add PE1 and PE2 to the VLAN.2. Enable the PIMv6 snooping function globally.3. Enable the PIMv6 snooping function in the VLAN.

Configuration CommandsConfiguration of PE1:




PE1(config)#pimv6snoop

PE1(config-pimv6snoop)#pimv6 snooping enable

PE1(config-pimv6snoop)#vlan 1

PE1(config-pimv6snoop-vlan1)#pimv6 snooping enable

Configuration of PE2:




8-5



PE2(config)#pimv6snoop

PE2(config-pimv6snoop)#pimv6 snooping enable

PE2(config-pimv6snoop)#vlan 1

PE2(config-pimv6snoop-vlan1)#pimv6 snooping enable

Configuration VerificationCE1 and CE2 are multicast switches, and they join a multicast group. Check multicastentries on PE1 and PE2.

l Check the information about the neighbor and entry on PE1 as follows:ZXR10#show pimv6 snooping neighbor-info


-----------------------------------------------------------------------

1 gei-0/1/1/1 1 0 2003::2 1585

ZXR10#ZXR10#show pimv6 snooping port-info vlan 1




--------------------------------------------------------------------------

1 1 2002::3 ff03::3 gei-0/1/1/2 2979

ZXR10#

l Check the information about the neighbor and entry on PE2 as follows:ZXR10#show pimv6 snooping neighbor-info


--------------------------------------------------------------------------

1 gei-0/1/1/1 1 0 2002::1 1585

ZXR10#ZXR10#show pimv6 snooping port-info vlan 1




--------------------------------------------------------------------------

1 1 2002::3 229.0.0.3 gei-0/1/1/3 2979

ZXR10#

8-6


Chapter 9MLD Snooping ConfigurationTable of Contents

MLD Snooping Overview............................................................................................9-1Configuring MLD Snooping ........................................................................................9-1Maintaining MLD Snooping ........................................................................................9-4MLD Snooping Configuration Example .....................................................................9-11

9.1 MLD Snooping OverviewMLD snooping snoops MLD protocol messages. It creates and maintains layer-2 multicastforwarding tables.

If the MLD snooping function is not enabled, multicast data packets are broadcast inbroadcast domains. MLD snooping snoops MLD protocol messages, and generatesthe corresponding layer-2 forwarding entries. After that, multicast data packets aremulticasted in domains. This reduces bandwidth wastes on networks.

9.2 Configuring MLD SnoopingTo configure the MLD snooping function on the ZXR10 5900E, perform the following steps:


1 ZXR10(config-mldsnoop)#enable Enables the MLD snooping function globally.

2 ZXR10(config-mldsnoop)#disable Disables the MLD snooping function

globally.

3 ZXR10(config-mldsnoop)#vpls <vpls-name>|

vlan <vlan-id>

Enters VPLS or VLAN configuration mode.

4 ZXR10(config-mldsnoop)#query-interval

<interval>

Configures the query interval of a querier.

<interval>: query interval, meaning the

interval of sending query messages, range:

30–65535, unit: seconds, default: 125

seconds.

9-1




5 ZXR10(config-mldsnoop)#query-response-i

nterval <interval>

Configures the maximum query-response

interval of a querier.

<interval>: maximum query-response

interval, range: 1–255, unit: tick (1 tick =

100 milliseconds), default: 100 ticks (10

seconds).

6 ZXR10(config-mldsnoop-vpls-zte)#ena

ble

Enables the MLD snooping function in MLD

Snooping-VPLS configuration mode.

7 ZXR10(config-mldsnoop-vpls-zte)#disa

ble

Disables the MLD snooping function in MLD


8 ZXR10(config-mldsnoop-vpls-zte)#drop

<ipv6-address>

Configures a drop group in MLD


9 ZXR10(config-mldsnoop-vpls-zte)#fast-l

eave

Configures the fast leaving function in MLD


10 ZXR10(config-mldsnoop-vpls-zte)#m

ax-host-in-group <ipv6-address>limit-num<num>

Configures the maximum number of

users supported by a multicast group in

a VPLS instance in MLD Snooping-VPLS

configuration mode.

11 ZXR10(config-mldsnoop-vpls-zte)#mrou

ter interface <port-name>

Configures a routing port in a VPLS instance

in MLD Snooping-VPLS configuration mode.

12 ZXR10(config-mldsnoop-vpls-zte)#mro

uter-time-out <time>

Configures the time-out time of routing ports

in MLD Snooping-VPLS configuration mode.

<time>: time-out time of routing ports, range:


seconds.

13 ZXR10(config-mldsnoop-vpls-zte)#mld

snooping static <ipv6-address> interface<port-name>

Configures a static multicast group member

in a VPLS instance in MLD Snooping-VPLS

configuration mode.

14 ZXR10(config-mldsnoop-vpls-zte)#host-

time-out <time>

Configures the time-out time of multicast

group members in a VPLS instance in MLD


<time>: time-out time of multicast group

members, range: 30–65535, unit: seconds,

default: 260 seconds.

15 ZXR10(config-mldsnoop-vpls-zte)#last-

member-query-interval <interval>

Configures the interval of querying the

last member in a VPLS instance in MLD


<interval>: interval of querying the last

member, range: 1–25, unit: seconds,

default: 1 second.

9-2


Chapter 9 MLD Snooping Configuration


16 ZXR10(config-mldsnoop-vpls-zte)#acl

<acl-name>

Configures an ACL filtering rule in a

VPLS instance in MLD Snooping-VPLS

configuration mode.

17 ZXR10(config-mldsnoop-vpls-zte)#max-

group-num <num>

Configure the maximum number of groups

in a VPLS instance in MLD Snooping-VPLS

configuration mode.

18 ZXR10(config-mldsnoop-vlan1)#drop

<ipv6-address>

Configures a drop group in MLD

Snooping-VLAN configuration mode.

19 ZXR10(config-mldsnoop-vlan1)#fast-leave Configures the fast leaving function in MLD


20 ZXR10(config-mldsnoop-vlan1)#max-host

-in-group <ipv6-address>[limit-num <num>]


users supported by a multicast group in a

VLAN instance in MLD Snooping-VLAN

configuration mode.

21 ZXR10(config-mldsnoop-vlan1)#mrouter

<interface <port-name>>

Configures a routing port in a VLAN in MLD


22 ZXR10(config-mldsnoop-vlan1)#mrouter-

time-out <time>

Configures the time-out time of routing ports

in MLD Snooping-VLAN configuration mode.

<time>: time-out time of routing ports, range:


seconds.

23 ZXR10(config-mldsnoop-vlan1)#static

<ipv6-address> interface<port-name>Configures a static multicast group member

in a VLAN in MLD Snooping-VLAN

configuration mode.

24 ZXR10(config-mldsnoop-vlan1)#host-tim

e-out <time>

Configures the time-out time of multicast

group members in a VLAN in MLD


<time>: time-out time of multicast group

members, range: 30–65535, unit: seconds,

default: 260 seconds.

25 ZXR10(config-mldsnoop-vlan1)#last-mem

ber-query-interval <interval>

Configures the interval of querying the last

member in a VLAN in MLD Snooping-VLAN

configuration mode.

<interval>: interval of querying the last

member, range: 1–25, unit: seconds,

default: 1 second.

26 ZXR10(config-mldsnoop-vlan1)#acl

<acl-name>

Configures an ACL filtering rule in a VLAN in

MLD Snooping-VLAN configuration mode.

9-3




27 ZXR10(config-mldsnoop-vlan1)#mode{pr

oxy | route | transparent}

Configures the operational node in MLD


28 ZXR10(config-mldsnoop-vlan1)#max-gr

oup-num <num>


groups in a VLAN in MLD Snooping-VLAN

configuration mode.



<ipv6-address> Group address, format: X:X::X:X.

limit-num <num> Number of users in a group, determined by the performance

parameters.



interface <port-name> Port name.



<ipv6-address> Group address, format: X:X::X:X.

interface <port-name> Port name.



proxy| route| transparent Operational mode of MLD snooping.

9.3 Maintaining MLD SnoopingTomaintain the MLD snooping function on the ZXR10 5900E, run the following commands.

Command Function

show mldsnoop Displays the information about all groups and

users of MLD snooping.

show mldsnoop group <ipv6-address> vpls<vpls-name>

Displays the information about a specified group

of MLD snooping in a VPLS instance.

show mldsnoop group <ipv6-address> vlan<vlan-id>

Displays the information about a specified group

of MLD snooping in a VLAN.

9-4



Command Function

show mldsnoop mrport-info Displays the information about all routing ports

of MLD snooping.

show mldsnoop port-info ip-global Displays the information about all users in MLD

snooping public-network mode.

show mldsnoop port-info svlan Displays the information about all users in MLD

snooping SVLAN mode.

show mldsnoop port-info vbui <vbui-port> Displays the information about all users in MLD

snooping VBUI mode.

show mldsnoop port-info vlan <vlan-id> Displays the information about all users in MLD

snooping VLAN mode.

show mldsnoop port-info vpls <vpls-name> Displays the information about all users in MLD

snooping VPLS mode.

show mldsnoop query Displays the states of MLD snooping queriers.

show mldsnoop summary Displays statistics of all MLD snooping multicast

groups.

show mldsnoop summary mrport-info Displays statistics of all MLD snooping routing

ports.

show mldsnoop summary port-info Displays statistics of all MLD snooping users.

show mldsnoop summary port-info ip-global Displays statistics of all users in MLD snooping

public-network mode.

show mldsnoop summary port-info svlan Displays statistics of all users in MLD snooping

SVLAN mode.

show mldsnoop summary port-info vbui

<vbui-port>

Displays statistics of all users in MLD snooping

VBUI mode.

show mldsnoop summary port-info vpls

<vpls-name>

Displays statistics of all users in MLD snooping

VPLS mode.

show mldsnoop summary port-info vlan <vlan-id> Displays statistics of all users in MLD snooping

VLAN mode.

show mldsnoop summary vlan <vlan-id> Displays statistics of all groups in MLD snooping

VLAN mode.

show mldsnoop summary vpls <vpls-name> Displays statistics of all groups in MLD snooping

VPLS mode.

show mldsnoop vlan <vlan-id> Displays the information about configuration and

users in MLD snooping VLAN mode.

show mldsnoop vpls <vpls-name> Displays the information about configuration and

users in MLD snooping VPLS mode.

9-5



The following is sample output from the show mldsnoop command:

ZXR10#show mldsnoop

Group information:

EN: Enabled; DIS: Disabled

MHN: Max-Host-Number

(S): Static; (D): Dynamic

Instance infomation:

IP-G:IP-GLOBAL

------------------------------------------------------------------

Index Type ID Name Group Source Drop MHN Ports

------------------------------------------------------------------

1 VLAN 1 -- ff33::3 :: DIS 27 S:smartgroup

1




Type Instance type of an entry.

ID Instance ID of an entry.

Name Instance name of an entry.



Drop Whether a multicast group is set to a drop group, DIS or EN.

MHN Maximum number of users supported by a multicast group.

Ports Information about users in a multicast group.

The following is sample output from the showmldsnoop group <ipv6-address> vlan <vlan-id>command:

ZXR10#show mldsnoop group ff33::3 vlan 2

Global configration of group:

|-- VLAN ID: 2

|-- group address: ff33::3

|-- host number: 1

|-- max host number: no limit

|-- drop mode: disabled

Member infomation of group:

--------------------------------------------------------

Index Source Port State RemainTime

9-6



--------------------------------------------------------

1 :: smartgroup1 static --




Source Source address of a user.

Port Information about all users in a multicast group.

State User state.

RemainTime Remaining aging time of a user.

The following is sample output from the show mldsnoop mrport-info command:

ZXR10#show mldsnoop mrport-info

--------------------------------------------------------

Index VLAN Port State RemainTime

--------------------------------------------------------

1 2 smartgroup1 static --




VLAN VLAN ID of a routing port.

Port Routing port.

State State of a routing port.

RemainTime Remaining aging time of a routing port.

The following is sample output from the show mldsnoop port-info vlan command:

ZXR10#show mld snooping port-info vlan 1

Index VLAN Group Source State RemainTime Ports

--------------------------------------------------------------

1 1 ff33::33 11::11 Static 65535 gei-0/1/1/1




VLAN VLAN ID of a user.

Group Multicast group address of a user.

9-7




Source Source address of a user.

State User state.

RemainTime Remaining aging time of a user.

Ports Port of a user.

The following is sample output from the show mldsnoop query command:

ZXR10#show mldsnoop query

Global query configration of MLD Snooping:

|-- Querier status: disabled

|-- Query interval: 125

|-- Query response interval: 100

Instance querier infomation:

--------------------

Index VLAN Version

--------------------

1 1 2




VLAN VLAN ID of a querier.

Version Querier version.

The following is sample output from the show mldsnoop summary command:

ZXR10(config)#show mldsnoop summary

The summary information about group:

Type Summary

------------------------------------------

Total 1

Exist-host 1

Cfg-drop 0

Cfg-max-host 0

Source-Specific 0

Anycast-Specific 1



Type Statistical type.

9-8




Summary Statistical information.

The following is sample output from the show mldsnoop summary mrport-info command:

ZXR10show mldsnoop summary mrport-info

The summary information about multicast router port:

Type Summary

-------------------------------------------

Total 1

Dynamic 1

Static 0





The following is sample output from the show mldsnoop summary port-info command:

ZXR10#show mldsnoop summary port-info

The summary information about port:

Type Summary

-----------------------------------------

Total 1

Dynamic 0

Static 1





The following is sample output from the show mldsnoop summary vlan command:

ZXR10#show mldsnoop summary vlan 1

The summary information about group:

Type Summary

-----------------------------------------

Total 2

Exist-host 1

Cfg-drop 0

Cfg-max-host 1

Source-Specific 0

Anycast-Specific 2

9-9







The following is sample output from the show mldsnoop vlan command:

ZXR10#show mldsnoop vlan 2

Global configration of VLAN:

|-- fast-leave status: disabled

|-- querier: disabled

|-- last-member-query-interval: 1

|-- host-time-out: 260

|-- mrport-time-out: 260

|-- max-group-number: 1000

|-- mode: proxy

|-- ACL name: none

Group information of VLAN:

(S): Static; (D): Dynamic

---------------------------------------------------------------------

Index Group Source Drop Max-host-num Host-num

---------------------------------------------------------------------

1 ff33::3 :: disabled 0 (S)1 , (D)0

ZXR10(config-mldsnoop)#






Drop Whether a multicast group is set to a drop group.

Max-host-num Maximum number of users supported by a multicast group.

Host-num Number of users in a multicast group.

9-10



9.4 MLD Snooping Configuration ExampleConfiguration DescriptionFigure 9-1 shows a network topology. Router A is connected to the multicast sourcethrough gei-0/1/1/1, and it is connected to switch A through gei-0/1/1/2. Router A runsMLD, and switch A runs MLDv2 snooping. Router A operates as the MLD querier.

Figure 9-1 MLD Snooping in a VLAN

Purpose

Host A and host B can receive multicast data sent to multicast group FF03::1. Whenreceiving unknown multicast data, switch A drops the data directly to prevent the datafrom being broadcast in the VLAN.

Configuration Flow1. Configure router A

Enable the IP multicast function, enable IPv6 PIM-SM on the layer-3 interfaces, andenable MLD on gei-0/1/1/2.

2. Configure switch A

a. Enable the MLD snooping function globally.

b. Create VLAN 10, and add gei-0/1/1/1 and gei-0/1/1/4 to the VLAN. Enable theMLD snooping function in the VLAN.

c. Simulate the hosts to join multicast group ff03::1 on gei-0/1/1/2 and gei-0/1/1/4.

Configuration CommandsConfiguration of switch A:

SwitchA#

SwitchA#configure terminal

9-11



Enter configuration commands, one per line. End with CTRL/Z.

SwitchA(config)#switchvlan-configuration













SwitchA(config-swvlan)#exit

SwitchA(config)#mldsnoop

SwitchA(config-mldsnoop)#enable

SwitchA(config-mldsnoop)#vlan 10

SwitchA(config-mldsnoop-vlan10)#enable

SwitchA(config-mldsnoop-vlan10)#end

SwitchA#

Configuration VerificationCheck the detailed information about the MLD snooping groups in VLAN 10 on switch Aas follows:

SwitchA(config)#show mldsnoop port-info vlan 10

------------------------------------------------------------------------

Index VLAN Group Source State RemainTime Ports

------------------------------------------------------------------------

1 10 ff03::1 :: V1Report 239 gei-0/1/1/2

1 10 ff03::1 :: V1Report 236 gei-0/1/1/4

SwitchA(config)#

9-12


Chapter 10MSDP ConfigurationTable of Contents

MSDP Overview.......................................................................................................10-1Configuring MSDP....................................................................................................10-2Maintaining MSDP....................................................................................................10-5MSDP Configuration Example ..................................................................................10-8

10.1 MSDP OverviewMulticast Source Discovery Protocol (MSDP) is a mechanism to connect multiple PIM-SMdomains. It operates over the Transfer Control Protocol (TCP) and provides multicastsource information outside the PIM domains for PIM-SM.

MSDP is a mechanism that makes RPs in different PIM domains share active sourceinformation. RP knows the receiver in local domain, so RP will forward the informationto the receiver when it obtains the active source information in remote domain. In this way,multicast packets are forwarded between domains.

An MSDP speaker in a PIM-SM domain uses the TCP connection to establish MSDPneighbor session relations with other MSDP neighbors. When learning a new multicastsource in the local domain through the PIM registration mechanism, this MSDP speakergenerates a source active message, and then sends this message to all MSDP neighbors.

Each MSDP neighbor receiving the message checks the SA message through neighborRPF. 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 messageis 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 receiverexists in this domain), the RP will create a (S, G) state for the multicast source and add itinto the SPT of the multicast source.

Besides, each MSDP neighbor receives and buffers SA messages, and then creates SAcache tables. If an RP in a PIM-SM domain receives a PIM addition message from a newmulticast group G, the RP searches its SA cache table, obtains all active multicast source,and finally generates a corresponding (S,G) addition message.

Although MSDP is developed as a inter-domain multicast protocol, it has a specialapplication in a PIM-SM domain, that is, anycast RP. Anycast RP means to set two ormore RPs with the same address in the same PIM-SM domain and establish MSDP peerrelationship between these RPs. This is to realize load sharing and redundancy for theRPs in the domain.

10-1



10.2 Configuring MSDPTo configure the MSDP function on the ZXR10 5900E, run the following commands:

Command Function

ZXR10(config-mcast)#router msdp Enables the MSDP function.

ZXR10(config-mcast)#no router msdp Disables the MSDP function.

Configuring an MSDP NeighborTo configure an MSDP neighbor on the ZXR10 5900E, perform the following steps:


1 ZXR10(config-msdp)#peer <peer-address> Sets an MSDP neighbor and

enters PEER configuration

mode. The parameter

<peer-address> is the IP

address of the MSDP neighbor.

2 ZXR10(config-msdp)#default-peer <peer-address>[list<access-list-name>]

Defines a default MSDP

neighbor. The local switch will

receive all SA messages from

this neighbor. By default, there

is no default MSDP neighbor.

3 ZXR10(config-msdp-peer)#shutdown Shuts down an MSDP that has

be configured. By default, an

MSDP neighbor is not shut

down.

4 ZXR10(config-msdp-peer)#mesh-group <mesh-name> Sets 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.

Configuring MSDP Extended FunctionsTo configure MSDP extended functions on the ZXR10 5900E, perform the following steps:


1 ZXR10(config-msdp-peer)#description <peer-address><d

esc-text>

Sets a description for an MSDP

neighbor.

2 ZXR10(config-msdp)#originator-id <interface-name> Sets the IP address on a

specific interface as the RP

address in the SA messages.

10-2


Chapter 10 MSDP Configuration


3 ZXR10(config-msdp-peer)#sa-limit <peer-address><sa-

limit>

Limits the number of SA

messages from a specific

MSDP neighbor in the SA

cache table. By default, there

is no limit.

4 ZXR10(config-msdp-peer)#ttl-threshold <ttl-value> Limits the range of the

multicast packets that are

encapsulated in SA messages

sent to MSDP neighbors.

5 ZXR10(config-msdp-peer)#ttl-security-hops <ttl-value > Limits the range of packets that

can be received from MSDP

neighbors.



<peer-address> IP address of an MSDP neighbor.

<desc-text> Descriptions for an MSDP neighbor, within 80 characters.






<peer-address><sa-limit> Maximum number of SA messages that are allowed from a

specific MSDP neighbor in the SA cache table, in the range of

1–2147483646.



<ttl-value> TTL value, in the range of 0–255, with the default value 0.



<ttl-value> TTL value, in the range of 1–254.

10-3



Configuring an MSDP PolicyTo configure an MSDP policy on the ZXR10 5900E, perform the following steps:


1 ZXR10(config-msdp)#redistribute [list <access-list-name>] According to the ACL rules,

only the (S, G) multicast route

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

2 ZXR10(config-msdp-peer)#sa-filter in [list<access-list-name>]

Filters the SA messages

received from specific MSDP

neighbors. The parameter

<access-list-name> is the ACL

name, with 1-31 characters.

3 ZXR10(config-msdp-peer)#sa-filter out [list<access-list-name>]

Filters the SAmessages sent to

specific MSDP neighbors. The

parameter <access-list-name>

is the ACL name, with 1-31

characters.

4 ZXR10(config-msdp)#connect-source <interface-name> Sets 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.

5 ZXR10(config-msdp-peer)#connect-source

<interface-name>

Sets and specifies 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.

Clearing MSDP StatesTo clear MSDP states on the ZXR10 5900E, perform the following steps:

10-4




1 ZXR10#clear ip msdp peer [<peer-address>] Clears the TCP connection

established with all MSDP

neighbors or a specific MSDP

neighbor.

2 ZXR10#clear ip msdp sa-cache [<group-address>] Clears entries in the MSDP

SA cache. The parameter

<group-address> is the address

of the multicast group.

3 ZXR10#clear ip msdp statistics [<peer-address>] 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.

10.3 Maintaining MSDPTo maintain the MSDP function on theZXR10 5900E, run the following commands.

Command Function

ZXR10#show ip msdp peer [<peer-address>] Displays the detailed information

of an MSDP neighbor.

ZXR10#show ip msdp sa-cache [<group-address>[<source-address>]] Displays the (S, G) states from

different MSDP neighbors.

ZXR10#show ip msdp summary Displays the summary information

of MSDP neighbors.

ZXR10#show ip msdp count Displays the count of

sources/multicast groups

generated by SA messages

and the count of SA messages

from each MSDP neighbor in the

SA cache.



<peer-address> IP address of an MSDP neighbor

<group-address> Specific multicast group address

<source-address> Specific multicast source address

10-5



The following is sample output from the show ip msdp peer command:

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: gei-0/1/1/1 (76.1.1.33)

Uptime(Downtime): 1d10h, Messages sent/received: 22189/22236

Connection and counters cleared 16:55:21 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



MSDP Peer IP address of this MSDP neighbor.

State State of this MSDP neighbor.

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.

The following is sample output from the show ip msdp sa-cache command:

ZXR10#show ip msdp sa-cache

MSDP Source-Active Cache - 4 entries

Timers:Uptime/Expires

(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


10-6




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

The following is sample output from the show ip msdp summary command:

ZXR10#show ip msdp summary

MSDP Peer Status Summary

Peer Address State Uptime/ Reset SA

Downtime Count Count

3.3.3.3 Up 00:28:20 0 0

10.10.10.2 Up 01:08:09 0 0

*1.1.1.1 Up 04:28:29 0 0



Peer Address IP address of this MSDP neighbor.

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.

The following is sample output from the show ip msdp count command:

ZXR10#show ip msdp count

SA State per Peer Counters, <Peer>: <# SA learned>

1.1.1.1: 2

1.2.2.2: 20

1.3.3.3: 10

Total entries: 32


10-7




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

10.4 MSDP Configuration ExampleConfiguration DescriptionAs shown in Figure 10-1, S1 and S3 are in the same PIM-SM multicast domain. S2 inanother PIM-SM multicast domain. It is required to forward multicast packets between thetwo domains through MSDP.

Figure 10-1 MSDP Configuration Example

Configuration Flow1. Enable PIM-SM and configure the candidate BSR and the RP.2. Configure OSPF to make the routes between the two domains through.3. Enable MSDP and establish peer relationship.


S1(config)#interface loopback1

10-8



S1(config-if)#ip address 1.1.1.1 255.255.255.0

S1(config-if)#exit


S1(config-mcast)#router pimsm

S1(config-pimsm)#rp-candidate loopback1 priority 10

S1(config-pimsm)#bsr-candidate loopback1 hash-mask-length 10 priority 10

S1(config-pimsm)#exit




S1(config-if)#exit



S1(config-if)#exit



S1(config-if)#exit

S1(config)#router ospf 1

S1(config-ospfv2)#network 10.10.10.0 0.0.0.255 area 0




S1(config-ospfv2)#exit


S1(config-mcast)#router msdp

S1(config-msdp)#connect-source vlan20

S1(config-msdp)#peer 10.10.20.2

S1(config-msdp-peer)#exit


S1(config-pimsm)#interface vlan10

S1(config-pimsm-if)#pimsm

S1(config-pimsm-if)#exit



S1(config-pimsm-if)#bsr-border








S2(config-if)#exit


10-9










S2(config-if)#exit



S2(config-if)#exit

S2(config)#interfacevlan50


S2(config-if)#exit















S2(config-msdp)#default-peer 10.10.20.1

S2(config-msdp)#exit















10-10




S3(config-if)#exit









S3(config-if)#exit



S3(config-if)#exit














S3(config-msdp)#exit








S3(config-pimsm-if)#end

Configuration VerificationUse the show ip msdp summary command on S1 to check the establishment of MSDP peerrelationship.

S1#show ip msdp summary




10-11



10.10.20.2 up 00:05:34 0 0





*10.10.20.1 up 00:07:34 0 0

10.10.40.2 up 00:08:45 0 0





10.10.40.1 up 00:10:45 0 0

10-12


Chapter 11Static MulticastConfigurationTable of ContentsStatic Multicast Overview .........................................................................................11-1Configuring Static Multicast ......................................................................................11-2Static Multicast Maintenance ....................................................................................11-3Static Multicast Configuration Example.....................................................................11-4

11.1 Static Multicast OverviewThe static multicast route is applied when multicast is expected to forward packetsaccording to the specific path instead of the unicast optimal path.

Static multicast provides users with egress and ingress to configure the multicast routingtable directly. It forms the multicast forwarding table according to the configuration ofusers and synchronizes the multicast forwarding table with the line card. If there are staticmulticast routes and dynamic multicast routes at the same time, static multicast routesare preferred. The logical position of static multicast is equivalent to the PIM-SM and thePIM-DM, that is, static multicast can be considered as a special multicast routing protocol.According to the application environment, static multicast routesmainly have two functions.

l Changing RPF routes

Generally, the network topology of multicast is the same with that of the unicast, andthe transmission paths are also the same. Users can configure static multicast routesto change the RPF routes, thus to create a transmission path for multicast packetsthat is different from that of unicast.

l Connecting with RPF routes

When the unicast routes in the network is blocked, multicast packets cannot beforwarded as there is no RPF route. Users can configure static multicast routesto generate RPF routes, thus to create multicast route entries to forward multicastpackets.

When creating multicast route entries, multicast routing protocols use the RPF checkmechanism to ensure that multicast packets are transmitted along the correct path andprevent loops caused by different reasons.

The RPF mechanism uses the multicast source address as the destination and selects anoptimal route from the unicast routing table, the MBGP routing table and the static multicastrouting table respectively. If the longest matching rule is configured, the RPF mechanism

11-1



selects the route that meets the longest matching rule among the three routes. If the masksare the same, the RPF mechanism selects the route with the highest priority among thethree routes. If the priorities are the same, the RPF mechanism selects the route in theorder of static multicast route, MBGP route and unicast route. The selected route is usedas the RPF route, and the RPF interfaces and neighbors are selected.

11.2 Configuring Static MulticastTo configure static multicast on ZXR10 5900E, perform the following steps.


ZXR10(config-mcast)#ip multicast-static-start Enables MSTATIC.1

ZXR10(config-mcast)#no ip multicast-static-start Disables MSTATIC.

ZXR10(config-mcast)#ip multicast-static-limit xg

<xg-limit> sg <sg-limit>

Sets the number of static

multicast route entities that is

allowed.

2

ZXR10(config-mcast)#no ip multicast-static-limit Cancels the number of static

multicast route entities that is

allowed.

ZXR10(config-mcast)#ip multicast-static-route <source-a

ddress><group-address>[iif<iif-name>][oif<oif-index>]Sets a static multicast route

entity.

3

ZXR10(config-mcast)#no ip multicast-static-route

<source-address><group-address>

Deletes a static multicast route

entity.

ZXR10(config-mcast)#ip multicast-static-interface index

<index>interface < interface-name>Sets the egress set of static

multicast.

4

ZXR10(config-mcast)#no ip multicast-static-interface

index<index>[interface <interface-name>]Deletes the egress set of static

multicast.



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



<group-address> Specific multicast group address

<source-address> Specific multicast source address

11-2


Chapter 11 Static Multicast Configuration


<iif-name> Ingress interface name of the multicast routes

<oif-index> Egress set index of the multicast route entities



<index> The index of egress interface set

< interface-name> The name of the interface to join the egress interface set

11.3 Static Multicast MaintenanceZXR10 5900E provides the following commands to maintain static multicast.

Command Function

ZXR10#show ip multicast-static-interface[index<index>] Displays the interfaces that are

effective in the egress interface

set.

ZXR10#show ip multicast-static-route [group <group-address>][source <source-address>]

Displays the static multicast

routing table.

ZXR10#show ip multicast-static-route summary Displays the statistics information

of the static multicast routing table.

The following is sample output from the show ip multicast-static-interface command:

ZXR10#show ip multicast-static-interface

STATIC-MULTICAST OUT PORT INDEX 2:

Outgoing Interface: loopback1

The following is sample output from the show ip multicast-static-route command:

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


The following is sample output from the show ip multicast-static-route summary command:

ZXR10#show ip multicast-static-route summary

IP Static Multicast Routing Table Summary

(*,G): 0 routes

(S,G): 1 routes

Total: 1 routes

11-3



11.4 Static Multicast Configuration ExampleConfiguration DescriptionAs shown in Figure 11-1, a static multicast route with the source 33.1.1.2 and destination225.10.1.2 is configured to forward multicast flows properly.

Figure 11-1 Static Multicast Configuration Example

Configuration Flow1. Configure interface IP addresses2. Enter multicast mode3. Enable static multicast4. Configure the maximum number of static multicast (*, G) routes and (S, G) routes5. Configure the egress interface list of static multicast6. Configure the detail static multicast route



S1(config-mcast)#ip multicast-static-start

S1(config-mcast)#ip multicast-static-limit xg 1024 sg 1024

S1(config-mcast)#ip multicast-static-interface index 2 interface gei-0/1/1/2

S1(config-mcast)#ip multicast-static-route 33.1.1.2 225.10.1.2

iif gei-0/1/1/1 oif 2

S1(config-mcast)#end

Configuration VerificationCheck the static multicast information on S1 with the show ip multicast-static-interfacecommand, as shown below.

S1(config)#show ip multicast-static-interface

STATIC-MULTICAST OUT PORT INDEX 2:

Outgoing Interface: gei-0/1/1/2

S1(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/1/1/1 A

11-4


Chapter 11 Static Multicast Configuration

Outgoing interface list: gei-0/1/1/2 F

S1(config)#show ip mroute


(33.1.1.2, 225.10.1.2), RP: 0.0.0.0, TYPE: STATIC, FLAGS:

Incoming interface: gei-0/1/1/1, flags:

Outgoing interface list: F/S

gei-0/1/1/2, flags:

11-5




11-6


FiguresFigure 2-1 IGMP Querier Election ............................................................................. 2-8

Figure 2-2 Joining of IGMP Dynamic Group and Static Group................................. 2-10

Figure 2-3 IGMP Fast Leaving From All Groups...................................................... 2-12

Figure 2-4 IGMP Fast Leaving From a Specified Group .......................................... 2-13

Figure 3-1 IGMP Snooping in a VLAN Instance ...................................................... 3-11

Figure 4-1 Forwarding Multicast Flow through PIM-SM (Dynamic RP) .................... 4-14

Figure 4-2 Forwarding Multicast Flow through PIM-SM (Static RP) ......................... 4-17

Figure 4-3 Illegal Multicast Source Control.............................................................. 4-19

Figure 5-1 PIM-SSM Configuration Example............................................................ 5-2

Figure 6-1 PIM-DM Configuration Example............................................................... 6-4

Figure 7-1 PIM Snooping Configuration Example...................................................... 7-5

Figure 8-1 PIMv6 Snooping Configuration Example .................................................. 8-5

Figure 9-1 MLD Snooping in a VLAN ..................................................................... 9-11

Figure 10-1 MSDP Configuration Example.............................................................. 10-8

Figure 11-1 Static Multicast Configuration Example ................................................ 11-4

I


Figures


II


GlossaryACL- Access Control List

BFD- Bidirectional Forwarding Detection

BSR- Bootstrap Router

DR- Designated Router

DVMRP- Distance Vector Multicast Routing Protocol

IGMP- Internet Group Management Protocol

LAN- Local Area Network

MBGP- Multiprotocol Border Gateway Protocol

MLD- Multicast Listener Discovery

MSDP- Multicast Source Discovery Protocol

NE- Network Element

PIM- Protocol Independent Multicast

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

III



SPT- Shortest Path Tree

SSM- Source Specific Multicast

SVLAN- Selective Virtual Local Area Network

TCP- Transmission Control Protocol

TCP/IP- Transmission Control Protocol/Internet Protocol

TOS- Termination of Service

TTL- Time To Live

VLAN- Virtual Local Area Network

VPLS- Virtual Private LAN Service

VRF- Virtual Route Forwarding

IV


Documents

ZXR105900ESeries · 2016. 9. 30. · About This Manual Purpose ThismanualistheZXR105900ESeries(V3.00.11)Easy-MaintenanceMPLSRouting SwitchConfigurationGuide(Multicast),whichisapplicabletotheZXR105900E(V3