Configuration Guide - IP Multicast (V600R001C00 - 04) - NE80E40E

HUAWEI NetEngine80E/40E Router
V600R001C00
Configuration Guide - IP Multicast
Issue 04
Date 2010-08-31
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 04 (2010-08-31) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide - IP Multicast About This Document
About This Document
Purpose
The document describes the configuration methods of IP multicast network in terms of basic
principles, implementation of protocols, configuration procedures and configuration examples
for the IP multicast of the NE80E/40E.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
HUAWEI NetEngine80E/40E V600R001C00

Router
Intended Audience
The intended audience of this document is:
l Commissioning Engineer
l Data Configuration Engineer
l Network Monitoring Engineer
l System Maintenance Engineer
Organization
This document is organized as follows.
Chapter Describes
1 IP Multicast This chapter describes IP multicast fundamentals,

Configuration Guide classifications, framework and packet forwarding
mechanism.
Issue 04 (2010-08-31) Huawei Proprietary and Confidential iii

About This Document Configuration Guide - IP Multicast
Chapter Describes
2 IGMP Configuration This chapter describes the IGMP fundamentals and

configuration steps and maintenance for IGMP functions,
along with typical examples.
3 Layer 2 Multicast This chapter describes the Layer 2 Multicas fundamentals

Configuration and configuration steps and maintenance for Layer 2
Multicas functions, along with typical examples.
4 PIM-DM (IPv4) This chapter describes the PIM-DM (IPv4) fundamentals and
Configuration configuration steps and maintenance for PIM-DM functions,
5 PIM-SM (IPv4) This chapter describes the PIM-SM (IPv4) and SSM
Configuration fundamentals and configuration steps and maintenance for
PIM-SM functions, along with typical examples.
6 MSDP Configuration This chapter describes the MSDP fundamentals and

configuration steps and maintenance for MSDP functions,
7 MBGP Configuration This chapter describes the MBGP fundamentals and

configuration steps and maintenance for MBGP functions,
8 IPv4 Multicast VPN This chapter describes the MD VPN fundamentals and
Configuration configuration steps and maintenance for MD VPN functions,
9 IPv4 Multicast CAC This chapter describes the configurations and maintenance of
Configuration IPv4 multicast CAC, and provides configuration examples.
10 IPv4 Multicast Routing This chapter describes the RPF fundamentals and
Management configuration steps and maintenance for RPF functions,
along with typical examples and troubleshooting cases.
11 MLD Configuration This chapter describes the MLD fundamentals and

configuration steps and maintenance for MLD functions,
12 PIM-DM (IPv6) This chapter describes the PIM-DM (IPv6) fundamentals and
Configuration configuration steps and maintenance for PIM-DM functions,
13 PIM-SM (IPv6) This chapter describes the PIM-SM (IPv6) and SSM
Configuration fundamentals and configuration steps and maintenance for
PIM-SM functions, along with typical examples.
14 IPv6 Multicast Routing This chapter describes the RPF fundamentals and
Management configuration steps and maintenance for RPF functions,
along with typical examples and troubleshooting cases of
IPv6 multicast.
15 Multicast Network This chapter describes the configuration methods and

Management maintenance of the multicast network management function.
iv Huawei Proprietary and Confidential Issue 04 (2010-08-31)

Chapter Describes
A Glossary This appendix collates frequently used glossaries in this

document.
B Acronyms and This appendix collates frequently used acronyms and

Abbreviations abbreviations in this document.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save

time.
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.
Issue 04 (2010-08-31) Huawei Proprietary and Confidential v

About This Document Configuration Guide - IP Multicast
Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
vi Huawei Proprietary and Confidential Issue 04 (2010-08-31)

Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 04 (2010-08-31)

The fourth commercial release.

The third commercial release.

The second commercial release.

Initial field trial release.
Issue 04 (2010-08-31) Huawei Proprietary and Confidential vii

Configuration Guide - IP Multicast Contents
Contents
About This Document...................................................................................................................iii

1 IP Multicast Configuration Guide..........................................................................................1-1
1.1 IP Multicast Introduction................................................................................................................................ 1-2
1.1.1 IP Multicast Overview........................................................................................................................... 1-2
1.1.2 IP Multicast Features Supported by the NE80E/40E.............................................................................1-2
1.2 IPv4 Multicast Configuration Guide...............................................................................................................1-2
1.2.1 IPv4 Multicast Addresses.......................................................................................................................1-2
1.2.2 IPv4 Multicast Protocols........................................................................................................................1-3
1.2.3 Typical Configuration Solution..............................................................................................................1-4
1.2.4 Controlling Multicast Forwarding..........................................................................................................1-5
1.3 IPv6 Multicast Configuration Guide...............................................................................................................1-5
1.3.1 IPv6 Multicast Addresses.......................................................................................................................1-6
1.3.2 IPv6 Multicast Protocols........................................................................................................................1-8
1.3.3 Typical Configuration Solution..............................................................................................................1-9
1.3.4 Controlling Multicast Forwarding........................................................................................................1-10
2 IGMP Configuration.................................................................................................................2-1
2.1 IGMP Introduction..........................................................................................................................................2-2
2.1.1 IGMP Overview.....................................................................................................................................2-2
2.1.2 IGMP Features Supported by the NE80E/40E.......................................................................................2-2
2.2 Configuring Basic IGMP Functions................................................................................................................2-3
2.2.1 Establishing the Configuration Task......................................................................................................2-4
2.2.2 Enabling IP Multicast Routing...............................................................................................................2-5
2.2.3 Enabling Basic IGMP Functions............................................................................................................2-5
2.2.4 Configuring IGMP Version....................................................................................................................2-6
2.2.5 Configuring a Static IGMP Group.........................................................................................................2-6
2.2.6 (Optional) Configuring an Interface to Join a Multicast Group in a Certain Range..............................2-7
2.2.7 Checking the Configuration...................................................................................................................2-8
2.3 Configuring Options of an IGMP Packet........................................................................................................2-8
2.3.2 Configuring a Router to Reject IGMP Packets Without the Router-Alert Option.................................2-9
2.3.3 Configuring a Router to Send IGMP Packets Without the Router-Alert Option.................................2-10
2.3.4 Configuring Host Address-based IGMP Report Message Filtering.....................................................2-11
Issue 04 (2010-08-31) Huawei Proprietary and Confidential ix

Contents Configuration Guide - IP Multicast
2.3.5 Checking the Configuration.................................................................................................................2-12

2.4 Configuring IGMP Query Control................................................................................................................2-12
2.4.1 Establishing the Configuration Task....................................................................................................2-12
2.4.2 Configuring an IGMPv1 Querier.........................................................................................................2-13
2.4.3 Configure an IGMPv2/v3 Querier........................................................................................................2-14
2.5 Configuring SSM Mapping...........................................................................................................................2-17
2.5.2 Enabling SSM Mapping.......................................................................................................................2-18
2.5.3 Configuring a Static SSM Mapping Policy..........................................................................................2-18
2.6 Configuration IGMP Limit Function............................................................................................................2-19
2.6.2 (Optional) Configuring the Maximum Number of Global IGMP Group Memberships......................2-20
2.6.3 (Optional) Configuring the Maximum Number of Global IGMP Entries in a Single Instance...........2-21
2.6.4 (Optional) Configuring the Maximum Number of IGMP Group Memberships on an Interface.........2-21
2.6.5 (Optional) Configuring the Interface-based Rate Limit for the IGMP Packets to Be Sent to the CPU
.......................................................................................................................................................................2-22
2.7 Maintaining IGMP........................................................................................................................................2-24
2.7.1 Clearing IGMP Group Information......................................................................................................2-24
2.7.2 Monitoring the Running Status of IGMP.............................................................................................2-24
2.8 Configuration Examples................................................................................................................................2-25
2.8.1 Example for Configuring Basic IGMP Functions................................................................................2-25
2.8.2 Example for Configuring SSM Mapping.............................................................................................2-28
2.8.3 Example for Configuring IGMP Limit.................................................................................................2-33
2.8.4 Example for Configuring Sub-interface for QinQ Termination to Statically Join Multicast Group. . .2-37
3 Layer 2 Multicast Configuration.............................................................................................3-1

3.1 Layer 2 Multicast Introduction........................................................................................................................3-3
3.1.1 IGMP Snooping......................................................................................................................................3-3
3.1.2 Replication of the Multicast VLAN.......................................................................................................3-4
3.1.3 1+1 Protection of Multicast VLANs......................................................................................................3-4
3.1.4 Static Layer 2 Multicast.........................................................................................................................3-5
3.1.5 Layer 2 Multicast CAC..........................................................................................................................3-5
3.2 Configuring IGMP Snooping for a VSI..........................................................................................................3-8
3.2.2 Configuring Basic IGMP Snooping Functions for a VSI......................................................................3-9
3.2.3 Configuring a Static Router Port for a VSI..........................................................................................3-10
3.2.4 Configuring the Dynamic Learning of Router Ports for a VSI............................................................3-11
3.2.5 Configuring the IGMP Snooping Querier for a VSI............................................................................3-12
3.2.6 Configuring Parameters for the IGMP Snooping Querier for a VSI....................................................3-13
3.2.7 Configuring the Multicast Policy for a VSI.........................................................................................3-14
x Huawei Proprietary and Confidential Issue 04 (2010-08-31)

3.2.8 Configuring Prompt Leave for Ports for a VSI....................................................................................3-15

3.2.9 Configuring IGMP Proxy for a VSI.....................................................................................................3-16
3.2.10 Configuring the IGMP Fast Join Function for a VSI.........................................................................3-16
3.2.11 Checking the Configuration...............................................................................................................3-17
3.3 Configuring IGMP Snooping for a VLAN...................................................................................................3-18
3.3.2 Enable IGMP Snooping for a VLAN...................................................................................................3-20
3.3.3 Configuring a Static Router Port for a VLAN.....................................................................................3-21
3.3.4 Configuring the Dynamic Learning of Router Ports in the VLAN......................................................3-21
3.3.5 Configuring the IGMP Snooping Querier for a VLAN.......................................................................3-22
3.3.6 Configuring Parameters of the IGMP Snooping Querier for a VLAN................................................3-23
3.3.7 Configuring the Multicast Policy for a VLAN.....................................................................................3-24
3.3.8 Configuring Prompt Leave for Ports in a VLAN.................................................................................3-25
3.3.9 Configuring IGMP Proxy for a VLAN................................................................................................3-26
3.3.10 Configuring the IGMP Fast Join Function for a VLAN....................................................................3-26
3.4 Configuring Trunk Load Balancing for Layer 2 Multicast...........................................................................3-28
3.4.2 Configuring VLAN-based Trunk Load Balancing for Layer 2 Multicast............................................3-29
3.4.3 Configuring VSI-based Trunk Load Balancing for Layer 2 Multicast................................................3-29
3.5 Configuring Replication of the Multicast VLAN.........................................................................................3-31
3.5.2 Configuring a Multicast VLAN...........................................................................................................3-33
3.5.3 Adding an Interface to a VLAN...........................................................................................................3-34
3.5.4 Configuring the Mapping Relationship Between the Multicast VLAN and the User VLAN.............3-34
3.5.5 (Optional) Enabling the Querier Election for User VLANs.................................................................3-35
3.6 Configuring 1+1 Protection of Multicast VLANs.........................................................................................3-36
3.6.2 Configuring a Multicast VLAN...........................................................................................................3-38
3.6.3 Configuring a Protection Group...........................................................................................................3-39
3.6.4 Configuring the Delay for the Switchover of a Protection Group.......................................................3-39
3.6.5 Configuring the Recovery Mode and the WRT of a Protection Group................................................3-40
3.6.6 Configuring Fault Detection on the Working VLAN and the Protection VLAN................................3-40
3.6.7 Configuring the Switchover Status of a Protection Group...................................................................3-41
3.7 Configuring Static Layer 2 Multicast............................................................................................................3-42
3.7.2 Configuring Static Layer 2 Multicast for a VSI...................................................................................3-43
3.7.3 Configuring Static Layer 2 Multicast for a VLAN..............................................................................3-44
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xi

3.8 Configuring the Network Management Function for Layer 2 Multicast......................................................3-46

3.8.1 Enabling the Alarm Function for Layer 2 Multicast............................................................................3-46
3.9 Configuring Layer 2 Multicast SSM Mapping.............................................................................................3-47
3.9.2 (Optional) Configuring a Layer 2 Multicast SSM Policy....................................................................3-48
3.9.3 Configuring Layer 2 Multicast SSM Mapping....................................................................................3-49
3.10 Configuring Layer 2 Multicast CAC for a VLAN, a Layer 2 Interface, or the Interface in a Specified VLAN
.............................................................................................................................................................................3-50
3.10.1 Establishing the Configuration Task..................................................................................................3-51
3.10.2 Configuring Restriction on the Number of Multicast Group Members of a VLAN, a Layer 2 Interface,
or the Interface in a Specified VLAN...........................................................................................................3-52
3.10.3 Configuring Restriction on the Bandwidth of Multicast Groups of a VLAN, a Layer 2 Interface, or the
Interface in a Specified VLAN......................................................................................................................3-53
3.10.4 Configuring Restriction on the Number of Channels of a VLAN, a Layer 2 Interface, or the Interface in
a Specified VLAN.........................................................................................................................................3-53
3.10.5 Configuring Restriction on the Bandwidth of Channels of a VLAN, a Layer 2 Interface, or the Interface
in a Specified VLAN.....................................................................................................................................3-54
3.10.6 Configuring Channels for a VLAN....................................................................................................3-55
3.11 Configuring Layer 2 Multicast CAC for a VSI...........................................................................................3-58
3.11.2 Configuring Restriction on the Number of Multicast Group Members of a VSI...............................3-59
3.11.3 Configuring Restriction on the Bandwidth of Multicast Groups of a VSI.........................................3-59
3.11.4 Configuring Restriction on the Number of Channels of a VSI..........................................................3-60
3.11.5 Configuring Restriction on the Bandwidth of Channels of a VSI......................................................3-60
3.11.6 Configuring Channels for a VSI.........................................................................................................3-61
3.12 Configuring Layer 2 Multicast CAC for a Sub-interface............................................................................3-63
3.12.2 Configuring Restriction on the Number of Multicast Group Members of a Sub-interface...............3-64
3.12.3 Configuring Restriction on the Bandwidth of Multicast Groups of a Sub-interface..........................3-65
3.12.4 Configuring Restriction on the Number of Channels of a Sub-interface...........................................3-66
3.12.5 Configuring Restriction on the Bandwidth of Channels of a Sub-interface.......................................3-66
3.13 Configuring Layer 2 Multicast CAC for a PW...........................................................................................3-68
3.13.2 Configuring Restriction on the Number of Multicast Group Members of a PW...............................3-70
3.13.3 Configuring Restriction on the Bandwidth of Multicast Groups of a PW.........................................3-71
3.13.4 Configuring Restriction on the Number of Channels of a PW..........................................................3-71
3.13.5 Configuring Restriction on the Bandwidth of Channels of a PW......................................................3-71
3.14 Maintaining Static Layer 2 Multicast..........................................................................................................3-74
xii Huawei Proprietary and Confidential Issue 04 (2010-08-31)

3.14.1 Clearing the Dynamic Port in the Outbound Port Information..........................................................3-74

3.14.2 Clearing the Statistics of IGMP Snooping.........................................................................................3-74
3.14.3 Monitoring the Running Status of IGMP Snooping...........................................................................3-75
3.14.4 Maintaining Layer 2 Multicast CAC..................................................................................................3-75
3.15 Configuration Examples..............................................................................................................................3-76
3.15.1 Example for Configuring IGMP Snooping for a VSI........................................................................3-76
3.15.2 Example for Configuring IGMP Snooping for a VLAN....................................................................3-83
3.15.3 Example for Configuring Replication of the Multicast VLAN..........................................................3-86
3.15.4 Example for Configuring 1+1 Protection of Multicast VLANs.........................................................3-88
3.15.5 Example for Adding an Interface to a Multicast Group Statically.....................................................3-94
3.15.6 Example for Configuring Layer 2 Multicast CAC for a VLAN........................................................3-96
3.15.7 Example for Configuring Layer 2 Multicast CAC for a VSI...........................................................3-100
3.15.8 Example for Configuring Layer 2 Multicast CAC for a PW...........................................................3-107
3.15.9 Example for Configuring Layer 2 Multicast SSM Mapping............................................................3-113
3.15.10 Example for Configuring Multicast CAC on a Sub-interface for VLAN Tag Termination..........3-116
4 PIM-DM (IPv4) Configuration................................................................................................4-1

4.1 PIM-DM (IPv4) Introduction..........................................................................................................................4-2
4.1.1 PIM-DM Overview................................................................................................................................4-2
4.1.2 PIM-DM Features Supported by the NE80E/40E..................................................................................4-3
4.2 Configuring Basic PIM-DM Functions...........................................................................................................4-4
4.2.2 Enabling IPv4 Multicast Routing...........................................................................................................4-5
4.2.3 Enabling PIM-DM..................................................................................................................................4-5
4.3 Adjusting Control Parameters of a Multicast Source......................................................................................4-7
4.3.2 Configuring the Lifetime of a Source....................................................................................................4-8
4.3.3 Configuring Filtering Rules Based on Source Addresses......................................................................4-9
4.4 Adjusting Control Parameters for Maintaining Neighbor Relationships......................................................4-10
4.4.2 Configuring the Interval for Sending Hello Messages.........................................................................4-11
4.4.3 Configuring the Timeout Period of a Neighbor...................................................................................4-12
4.4.4 Refusing to Receive the Hello Message Without the Generation ID Option.......................................4-13
4.4.5 Configuring PIM Neighbor Filtering...................................................................................................4-13
4.5 Adjusting Control Parameters for Prune.......................................................................................................4-14
4.5.2 Configuring the Period for an Interface to Keep the Prune State.........................................................4-15
4.5.3 Configuring the Delay for Transmitting Prune Messages in a LAN....................................................4-16
4.5.4 Configuring the Interval for Overriding the Prune Action...................................................................4-17
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xiii

4.6 Adjusting Control Parameters for State-Refresh...........................................................................................4-18

4.6.2 Disabling State-Refresh........................................................................................................................4-19
4.6.3 Configuring the Interval for Sending State-Refresh Messages............................................................4-20
4.6.4 Configuring the Period for Receiving the Next State-Refresh Message..............................................4-20
4.6.5 Configuring the TTL Value Carried in a State-Refresh Message........................................................4-21
4.7 Adjusting Control Parameters for Graft........................................................................................................4-22
4.7.2 Configuring the Interval for Retransmitting Graft Messages...............................................................4-23
4.8 Adjusting Control Parameters for Assert......................................................................................................4-24
4.8.2 Configuring the Period for Keeping the Assert State...........................................................................4-25
4.9 Configuring PIM Silent.................................................................................................................................4-26
4.9.2 Configuring PIM Silent........................................................................................................................4-27
4.10 Maintaining PIM.........................................................................................................................................4-29
4.10.1 Clearing Statistics of PIM Control Messages.................................................................................... 4-29
4.10.2 Monitoring the Running Status of PIM..............................................................................................4-29
4.11 Configuration Example...............................................................................................................................4-30
4.11.1 Example for Configuring Basic PIM-DM Functions.........................................................................4-30
5 PIM-SM (IPv4) Configuration.................................................................................................5-1

5.1 PIM-SM (IPv4) Introduction...........................................................................................................................5-3
5.1.1 PIM-SM Overview.................................................................................................................................5-3
5.1.2 PIM-SM Features Supported by the NE80E/40E..................................................................................5-4
5.2 Configuring Basic PIM-SM Functions...........................................................................................................5-6
5.2.3 Enabling Basic PIM-SM Functions........................................................................................................5-8
5.2.4 (Optional) Configuring a Static RP........................................................................................................5-9
5.2.5 (Optional) Configuring a Dynamic RP................................................................................................ 5-10
5.2.6 (Optional) Configuring the SSM Group Address Range.....................................................................5-11
5.3 Adjusting Control Parameters for a Multicast Source.................................................................................. 5-12
5.3.2 Configuring the Lifetime of a Source.................................................................................................. 5-13
5.3.3 Configuring Filtering Rules Based on Source Addresses....................................................................5-14
5.4 Adjusting Control Parameters of the C-RP and C-BSR................................................................................5-15
xiv Huawei Proprietary and Confidential Issue 04 (2010-08-31)


5.4.2 Adjusting C-RP Parameters.................................................................................................................5-16
5.4.3 Adjusting C-BSR Parameters...............................................................................................................5-17
5.4.4 Configuring the BSR Boundary...........................................................................................................5-18
5.4.5 (Optional) Configuring the BSR Address Range.................................................................................5-18
5.4.6 (Optional) Configuring the Range of Valid C-RP Addresses..............................................................5-19
5.5 Configuring a BSR Administrative Domain.................................................................................................5-20
5.5.2 Enabling a BSR Administrative Domain.............................................................................................5-21
5.5.3 Configuring the Boundary of a BSR Administrative Domain.............................................................5-21
5.5.4 Adjusting C-BSR Parameters...............................................................................................................5-22
5.6 Adjusting Control Parameters for Establishing the Neighbor Relationship.................................................5-23
5.6.2 Configuring Control Parameters for Establishing the Neighbor Relationship.....................................5-24
5.6.3 Configuring Control Parameters for Electing a DR.............................................................................5-26
5.6.4 Enabling the Function of Tracking a Downstream Neighbor..............................................................5-27
5.6.5 Configuring PIM Neighbor Filtering...................................................................................................5-28
5.7 Adjusting Control Parameters for Source Registering..................................................................................5-29
5.7.2 Configuring PIM-SM Register Messages............................................................................................5-30
5.7.3 Configuring PIM-SM Register Suppression........................................................................................5-31
5.8 Adjusting Control Parameters for Forwarding..............................................................................................5-31
5.8.2 Configuring Control Parameters for Keeping the Forwarding State....................................................5-32
5.8.3 Configuring Control Parameters for Prune..........................................................................................5-34
5.8.4 Configuring Join Information Filtering................................................................................................5-35
5.8.5 Configuring Neighbor Check...............................................................................................................5-35
5.9 Adjusting Control Parameters for Assert......................................................................................................5-37
5.9.2 Configuring the Period for Keeping the Assert State...........................................................................5-37
5.10 Configuring the SPT Switchover................................................................................................................5-39
5.10.2 (Optional) Configuring the Interval for Checking the Forwarding Rate of Multicast Data...............5-40
5.11 Configuring PIM BFD................................................................................................................................5-41
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xv

5.11.2 Configuring PIM BFD.......................................................................................................................5-42

5.11.3 (Optional) Adjusting BFD Parameters...............................................................................................5-43
5.12 Configuring PIM GR...................................................................................................................................5-44
5.12.2 Configuring PIM GR..........................................................................................................................5-45
5.13 Configuring PIM Silent...............................................................................................................................5-46
5.13.2 Configuring PIM Silent......................................................................................................................5-47
5.14 Maintaining PIM.........................................................................................................................................5-48
5.14.1 Clearing Statistics of PIM Control Messages.................................................................................... 5-49
5.14.2 Clearing the PIM Status of the Specified Downstream Interfaces of PIM Entries............................5-49
5.14.3 Monitoring the Running Status of PIM-SM.......................................................................................5-50
5.15.1 Example for Configuring a PIM-SM Network.................................................................................. 5-51
5.15.2 Example for Configuring the SPT Switchover in a PIM-SM Domain.............................................. 5-59
5.15.3 Example for Configuring PIM BFD on Routers in Ethernet............................................................. 5-64
5.15.4 Example for Configuring PIM GR.....................................................................................................5-67
6 MSDP Configuration.................................................................................................................6-1
6.1 MSDP Introduction.........................................................................................................................................6-3
6.1.1 MSDP Overview....................................................................................................................................6-3
6.1.2 MSDP Features Supported by the NE80E/40E......................................................................................6-3
6.2 Configuring PIM-SM Inter-domain Multicast................................................................................................6-5
6.2.2 Configuring Intra-AS MSDP Peers........................................................................................................6-6
6.2.3 Configuring Inter-AS MSDP Peers on MBGP Peers.............................................................................6-8
6.2.4 Configuring Static RPF Peers................................................................................................................6-9
6.3 Configuring an Anycast RP in a PIM-SM Domain.......................................................................................6-10
6.3.2 Configuring the Interface Address of an RP........................................................................................6-11
6.3.3 Configuring a C-RP..............................................................................................................................6-12
6.3.4 Statically Configuring an RP................................................................................................................6-13
6.3.5 Configuring an MSDP Peer..................................................................................................................6-13
6.3.6 Specifying the Logical RP Address for an SA Message......................................................................6-14
6.4 Managing MSDP Peer Connections..............................................................................................................6-16
6.4.2 Controlling the Sessions Between MSDP Peers..................................................................................6-17
6.4.3 Adjusting the interval for Retrying Setting up an MSDP Peer Connection.........................................6-17
xvi Huawei Proprietary and Confidential Issue 04 (2010-08-31)


6.5 Configuring SA Cache..................................................................................................................................6-18
6.5.2 Configuring the Maximum Number of (S, G) Entries in the Cache....................................................6-19
6.5.3 Disabling the SA Cache Function........................................................................................................6-20
6.6 Configuring the SA Request.........................................................................................................................6-21
6.6.2 Configuring "Sending SA Request Messages" on the Local Router....................................................6-22
6.6.3 (Optional) Configuring the Filtering Rules for Receiving SA Request Messages..............................6-23
6.6.4 Check the Configuration......................................................................................................................6-23
6.7 Transmitting Burst Multicast Data Between Domains.................................................................................6-24
6.7.2 Encapsulating a Multicast Data Packet in an SA message...................................................................6-25
6.7.3 (Optional) Setting the TTL Threshold for Forwarding an SA Message Containing a Multicast Data Packet
.......................................................................................................................................................................6-26
6.8 Configuring the Filtering Rules for SA Messages........................................................................................6-28
6.8.2 Setting Rules for Creating an SA Message..........................................................................................6-29
6.8.3 Setting Rules for Receiving an SA Message........................................................................................6-29
6.8.4 Setting Rules for Forwarding an SA Message.....................................................................................6-30
6.9 Configuring MSDP Authentication...............................................................................................................6-32
6.9.2 Configuring MSDP MD5 Authentication............................................................................................6-33
6.9.3 Configuring MSDP Key-Chain Authentication...................................................................................6-33
6.10 Maintaining MSDP.....................................................................................................................................6-35
6.10.1 Clearing Statistics of MSDP Peers.....................................................................................................6-35
6.10.2 Clearing (S, G) Information in SA Cache..........................................................................................6-36
6.10.3 Monitoring the Running Status of MSDP..........................................................................................6-36
6.11.1 Example for Configuring PIM-SM Inter-Domain Multicast.............................................................6-37
6.11.2 Example for Configuring Inter-AS Multicast by Using Static RPF Peers.........................................6-44
6.11.3 Example for Configuring Anycast RP...............................................................................................6-48
7 MBGP Configuration................................................................................................................7-1
7.1 MBGP Introduction.........................................................................................................................................7-2
7.1.1 MBGP Overview....................................................................................................................................7-2
7.1.2 MBGP Features Supported by the NE80E/40E.....................................................................................7-2
7.2 Configuring Basic MBGP Functions..............................................................................................................7-2
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xvii

7.2.2 Configuring a BGP Peer.........................................................................................................................7-3

7.2.3 Configuring an MBGP Peer...................................................................................................................7-4
7.2.4 Configuring an MBGP Route Reflector.................................................................................................7-5
7.2.5 Configuring MBGP to Import Local Routes..........................................................................................7-6
7.3 Configuring the Policy for Advertising MBGP Routes..................................................................................7-8
7.3.2 Configuring the Next Hop of a Route as the Local Address..................................................................7-9
7.3.3 Configuring the Aggregation of Local MBGP Routes...........................................................................7-9
7.3.4 Configuring the Local Peer to Advertise Default Routes.....................................................................7-10
7.3.5 Configuring the Local Peer to Advertise Community Attribute and Extended Community Attribute
.......................................................................................................................................................................7-11
7.3.6 Configuring Update Packets not to Carry Private AS Number............................................................7-12
7.4 Configuring the Policy for Exchanging Routes Between MBGP Peers.......................................................7-13
7.4.2 Configuring the Route Filtering Policy Globally.................................................................................7-14
7.4.3 Configuring the Route Filtering Policy Based on Route-policy..........................................................7-15
7.4.4 Configuring the Route Filtering Policy Based on ACL.......................................................................7-16
7.4.5 Configuring the Route Filtering Policy Based on AS-Path List..........................................................7-17
7.4.6 Configuring the Route Filtering Policy Based on IP Prefix.................................................................7-18
7.4.7 Configuring the Maximum Number of Routes Received from Peers..................................................7-19
7.5 Configuring MBGP Route Attributes...........................................................................................................7-20
7.5.2 Setting Preferred Values of Routes Learned from Peers......................................................................7-21
7.5.3 Configuring the Preference of an MBGP Route..................................................................................7-22
7.5.4 Configuring the Local-Pref of an MBGP Route..................................................................................7-22
7.5.5 Configuring the MED Attribute of an MBGP Route...........................................................................7-23
7.5.6 Configuring Next_Hop.........................................................................................................................7-24
7.6 Configuring MBGP Route Dampening.........................................................................................................7-25
7.6.2 Setting Dampening Parameters of an MBGP Route............................................................................7-26
7.7 Maintaining MBGP.......................................................................................................................................7-27
7.7.1 Resetting MBGP Connection...............................................................................................................7-27
7.7.2 Clearing MBGP Statistics....................................................................................................................7-28
7.8.1 Example for Configuring Basic MBGP Functions..............................................................................7-28
8 IPv4 Multicast VPN Configuration........................................................................................8-1

8.1 IPv4 Multicast VPN Introduction...................................................................................................................8-2
xviii Huawei Proprietary and Confidential Issue 04 (2010-08-31)

8.1.1 Overview of IPv4 Multicast VPN..........................................................................................................8-2

8.1.2 IPv4 Multicast VPN Supported by the NE80E/40E...............................................................................8-3
8.2 Configuring Basic MD VPN Functions..........................................................................................................8-4
8.2.2 Enabling IP Multicast VPN....................................................................................................................8-5
8.2.4 Configuring Share-Group and Binding an MTI.....................................................................................8-6
8.2.5 Configuring an MTI...............................................................................................................................8-6
8.3 Configuring Switch-MDT Switchover............................................................................................................8-8
8.3.2 (Optional) Setting Switching Parameters of Switch-MDT....................................................................8-9
8.4 Maintaining IPv4 Multicast VPN..................................................................................................................8-10
8.4.1 Monitoring the Running Status of IPv4 Multicast VPN......................................................................8-10
8.4.2 Controlling the Output of Logs............................................................................................................8-11
8.5.1 Example for Configuring Single-AS MD VPN................................................................................... 8-12
8.5.2 Example for Configuring Inter-AS MD VPN......................................................................................8-31
9 IPv4 Multicast CAC Configuration........................................................................................9-1

9.1 IPv4 Multicast CAC Introduction...................................................................................................................9-2
9.1.1 Multicast CAC Overview.......................................................................................................................9-2
9.1.2 Multicast CAC Features Supported by the NE80E/40E........................................................................9-4
9.2 Configuring Multicast CAC............................................................................................................................9-4
9.2.2 Configuring a Channel...........................................................................................................................9-6
9.2.3 (Optional) Configuring the Maximum Number of PIM Routing Entries in a Single Instance..............9-6
9.2.4 (Optional) Configuring the Maximum Number of PIM Routing Entries in a Channel.........................9-7
9.2.5 (Optional) Configuring the Maximum Number of Outgoing Interface Lists to Which an Interface Is Added
and Bandwidth Limit.......................................................................................................................................9-8
9.3 Maintaining Multicast CAC............................................................................................................................9-9
9.3.1 Monitoring the Running Status of Multicast CAC.................................................................................9-9
9.4 Configuration Examples..................................................................................................................................9-9
9.4.1 Example for Configuring Multicast CAC..............................................................................................9-9
10 IPv4 Multicast Routing Management................................................................................10-1

10.1 IPv4 Multicast Routing Management Introduction.....................................................................................10-2
10.1.1 Overview of IPv4 Multicast Routing Management........................................................................... 10-2
10.1.2 IPv4 Multicast Routing Management Features Supported by the NE80E/40E.................................10-3
10.2 Configuring a Static Multicast Route..........................................................................................................10-5
10.2.2 Configuring a Static Multicast Route.................................................................................................10-5
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xix


10.3 Configuring the Multicast Routing Policy..................................................................................................10-7
10.3.2 Configuring Longest Match of Multicast Route................................................................................10-7
10.3.3 Configuring Multicast Load Splitting................................................................................................10-8
10.3.4 Configuring a Multicast Load Splitting Weight...............................................................................10-10
10.3.5 Checking the Configuration.............................................................................................................10-10
10.4 Configuring the Multicast Forwarding Scope...........................................................................................10-11
10.4.1 Establish the Configuration Task.....................................................................................................10-11
10.4.2 Configuring the Multicast Forwarding Boundary............................................................................10-12
10.4.3 Configuring the TTL Threshold of Multicast Forwarding...............................................................10-12
10.5 Configuring Control Parameters of the Multicast Forwarding Table.......................................................10-13
10.5.1 Establishing the Configuration Task................................................................................................10-14
10.5.2 Setting the Maximum Number of Entries in Multicast Forwarding Table......................................10-14
10.5.3 Setting the Maximum Number of Downstream Nodes of Multicast Forwarding Entry..................10-15
10.6 Maintaining the Multicast Policy..............................................................................................................10-17
10.6.1 Testing Multicast Routing................................................................................................................10-17
10.6.2 Check RPF Paths and Multicast Paths.............................................................................................10-18
10.6.3 Clearing Multicast Routing and Forwarding Entries.......................................................................10-18
10.6.4 Monitoring the Status of Multicast Routing and Forwarding..........................................................10-19
10.7 Configuration Examples............................................................................................................................10-20
10.7.1 Example for Changing Static Multicast Routes to RPF Routes.......................................................10-20
10.7.2 Example for Connecting the RPF Route Through a Static Multicast Route....................................10-23
10.7.3 Example for Implementing Multicast Through a Static Multicast Routed Tunnel..........................10-28
10.7.4 Example for Configuring Multicast Load Splitting.........................................................................10-31
10.8 Troubleshooting of Static Multicast Routes..............................................................................................10-38
11 MLD Configuration...............................................................................................................11-1
11.1 MLD Introduction.......................................................................................................................................11-2
11.1.1 MLD Overview..................................................................................................................................11-2
11.1.2 MLD Features Supported by the NE80E/40E....................................................................................11-2
11.2 Configuring Basic MLD Functions.............................................................................................................11-3
11.2.2 Enabling IPv6 Multicast Routing.......................................................................................................11-4
11.2.3 Enabling MLD....................................................................................................................................11-4
11.2.4 (Optional) Configuring the MLD Version.........................................................................................11-5
11.2.5 (Optional) Configuring an Interface to Statically Join a Group.........................................................11-5
11.2.6 (Optional) Configuring the Range of Groups an Interface Can Join.................................................11-6
11.3 Configuring Options of an MLD Packet.....................................................................................................11-7
xx Huawei Proprietary and Confidential Issue 04 (2010-08-31)

11.3.2 Configuring the Router-Alert Option of an MLD Packet..................................................................11-7

11.4 Configuring MLD Query Control...............................................................................................................11-9
11.4.2 (Optional) Configuring MLD Query and Response.........................................................................11-10
11.5 Configuring SSM Mapping.......................................................................................................................11-12
11.5.2 Enabling SSM Mapping...................................................................................................................11-13
11.5.3 Configuring the Static SSM Mapping Policy...................................................................................11-14
11.6 Configuration MLD Limit Function.........................................................................................................11-15
11.6.2 Configuring the Maximum Number of Global MLD Group Memberships.....................................11-16
11.6.3 Configuring the Maximum Number of Global MLD Entries in a Single Instance..........................11-16
11.6.4 Configuring the Maximum Number of MLD Group Memberships on an Interface........................11-17
11.7 Maintaining MLD.....................................................................................................................................11-18
11.7.1 Clearing Information about MLD Groups.......................................................................................11-18
11.7.2 Monitoring the Running Status of MLD..........................................................................................11-19
11.8 Configuration Example.............................................................................................................................11-20
11.8.1 Example for Configuring Basic MLD functions..............................................................................11-20
11.8.2 Example for Configuring MLD Limit..............................................................................................11-22
12 PIM-DM (IPv6) Configuration............................................................................................12-1

12.1 PIM-IPv6 Introduction................................................................................................................................12-3
12.1.1 PIM-IPv6 Overview...........................................................................................................................12-3
12.1.2 PIM-DM Features Supported by the NE80E/40E..............................................................................12-3
12.2 Configuring Basic PIM-DM (IPv6) Functions............................................................................................12-4
12.2.3 Enabling Basic PIM-DM (IPv6) Functions........................................................................................12-5
12.3 Adjusting Control Parameters of a Source..................................................................................................12-6
12.3.2 Configuring the Keepalive Period of a Source...................................................................................12-7
12.3.3 Configuring Filtering Rules Based on Source Addresses..................................................................12-8
12.4 Adjusting Control Parameters for Maintaining Neighbors.........................................................................12-9
12.4.2 Configuring the Interval for Sending Hello Messages.....................................................................12-10
12.4.3 Configuring the Timeout Period of a Neighbor...............................................................................12-11
12.4.4 Refusing to Receive the Hello Message Without the Generation ID Option...................................12-12
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xxi

12.4.5 Configuring PIM Neighbor Filtering...............................................................................................12-12

12.5 Adjusting Control Parameters for Prune...................................................................................................12-13
12.5.2 Configuring the Period for an Interface to Keep the Prune State.....................................................12-14
12.5.3 Configuring the Delay for Transmitting Prune Messages in a LAN................................................12-15
12.5.4 Configuring the Interval for Overriding the Prune Action...............................................................12-16
12.6 Adjusting Control Parameters for State-Refresh.......................................................................................12-17
12.6.1 Estalishing the Configuration Task..................................................................................................12-18
12.6.2 Disabling State-Refresh....................................................................................................................12-18
12.6.3 Configuring the Interval for Sending State-Refresh Messages........................................................12-19
12.6.4 Configuring the Period for Receiving the Next State-Refresh Message..........................................12-20
12.6.5 Configuring the TTL Value of a State-Refresh Message.................................................................12-20
12.7 Adjusting Control Messages for Graft......................................................................................................12-21
12.7.2 Setting the Interval for Retransmitting Graft Messages...................................................................12-22
12.8 Adjusting Control Messages for Assert....................................................................................................12-23
12.8.2 Configuring the Period for Keeping the Assert State.......................................................................12-24
12.9 Configuring PIM-IPv6 Silent....................................................................................................................12-25
12.9.2 Configuring PIM-IPv6 Silent...........................................................................................................12-26
12.10 Maintaining PIM-DM.............................................................................................................................12-27
12.10.1 Clearing Statistics of PIM Control Messages................................................................................12-27
12.10.2 Monitoring Running Status of PIM-DM........................................................................................12-28
12.11 Configuration Example...........................................................................................................................12-28
12.11.1 Example for Configuring Basic PIM-DM Functions.....................................................................12-28
13 PIM-SM (IPv6) Configuration.............................................................................................13-1

13.1 PIM-SM (IPv6) Introduction.......................................................................................................................13-3
13.1.1 PIM-IPv6 Overview...........................................................................................................................13-3
13.1.2 PIM-SM Features Supported by the NE80E/40E..............................................................................13-3
13.2 Configuring Basic PIM-SM (IPv6) Functions............................................................................................13-5
13.2.3 Enabling Basic PIM-SM (IPv6) Functions........................................................................................13-7
13.2.4 (Optional) Configuring an Embedded-RP..........................................................................................13-8
13.2.5 (Optional) Configuring a Static RP....................................................................................................13-9
xxii Huawei Proprietary and Confidential Issue 04 (2010-08-31)

13.2.6 (Optional) Configuring a Dynamic RP............................................................................................13-10

13.2.7 (Optional) Configuring the SSM Group Address Range.................................................................13-11
13.3 Adjusting Control Parameters of a Source................................................................................................13-12
13.3.2 Configuring the Keepalive Period of a Source.................................................................................13-13
13.3.3 Configuring Filtering Rules Based on Source Addresses................................................................13-13
13.4 Adjusting Control Parameters of a C-RP and a C-BSR............................................................................13-14
13.4.2 Adjusting Control Parameters of a C-RP.........................................................................................13-15
13.4.3 Adjusting Control Parameters of a C-BSR......................................................................................13-16
13.4.4 Configuring the BSR Service Boundary..........................................................................................13-17
13.4.5 (Optional) Configuring the Range of Legal BSR addresses............................................................13-18
13.4.6 (Optional) Configuring the Range of Legal C-RP Addresses..........................................................13-19
13.5 Adjusting Control Parameters for Maintaining Neighbors.......................................................................13-19
13.5.2 Configuring Control Parameters for Maintaining PIM Neighbors..................................................13-21
13.5.3 Configuring Control Parameters for Electing a DR.........................................................................13-22
13.5.4 Enabling the Function of Tracking a Downstream Neighbor..........................................................13-23
13.5.5 Configuring PIM Neighbor Filtering...............................................................................................13-24
13.6 Adjusting Control Parameters of Source Registering...............................................................................13-25
13.6.2 Configuring Rules for Filtering PIM-SM (IPv6) Register Messages..............................................13-26
13.6.3 Configuring PIM-SM (IPv6) Registering Suppression....................................................................13-26
13.7 Adjusting Control Parameters for Forwarding..........................................................................................13-27
13.7.2 Configuring Control Parameters for Keeping the Forwarding Relationship...................................13-28
13.7.3 Configuring Control Parameters for Prune......................................................................................13-30
13.7.4 Configuring Join Information Filtering............................................................................................13-31
13.7.5 Configuring Neighbor Check...........................................................................................................13-31
13.8 Configuring Control Parameters for Assert..............................................................................................13-33
13.8.2 Configuring the Period for Keeping the Assert State.......................................................................13-33
13.9 Adjusting Control Parameters for the SPT Switchover............................................................................13-35
13.9.2 (Optional) Configuring the Interval for Checking the Forwarding Rate of Multicast Data.............13-36
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xxiii

13.9.3 (Optional) Adjusting Conditions of the SPT Switchover.................................................................13-37

13.10 Configuring PIM GR (IPv6)................................................................................................................... 13-38
13.10.1 Establishing the Configuration Task..............................................................................................13-38
13.10.2 Configuring PIM GR (IPv6).......................................................................................................... 13-39
13.10.3 Checking the Configuration...........................................................................................................13-39
13.11 Configuring PIM-IPv6 Silent..................................................................................................................13-40
13.11.1 Establishing the Configuration Task..............................................................................................13-40
13.11.2 Configuring PIM-IPv6 Silent.........................................................................................................13-41
13.11.3 Checking the Configuration...........................................................................................................13-41
13.12 Maintaining PIM-SM..............................................................................................................................13-42
13.12.1 Clearing Statistics of PIM-IPv6 Control Messages........................................................................13-42
13.12.2 Clearing the PIM Status of the Specified Downstream Interfaces of PIM Entries........................13-42
13.12.3 Monitoring the Running Status of PIM-SM...................................................................................13-43
13.13 Configuration Example...........................................................................................................................13-44
13.13.1 Example for Configuring Basic PIM-SM functions...................................................................... 13-44
13.13.2 Example for Configuring PIM GR (IPv6)......................................................................................13-51
14 IPv6 Multicast Routing Management................................................................................14-1

14.1 IPv6 Multicast Routing Management Introduction.....................................................................................14-2
14.1.1 Overview of IPv6 Multicast Routing Management...........................................................................14-2
14.1.2 IPv6 Multicast Routing Management Features Supported by the NE80E/40E.................................14-2
14.2 Configuring the IPv6 Multicast Routing Policy..........................................................................................14-3
14.2.2 Configuring IPv6 Multicast Load Splitting........................................................................................14-4
14.2.3 Configuring an IPv6 Multicast Load Splitting Weight......................................................................14-5
14.3 Limiting the Range of Multicast Forwarding..............................................................................................14-6
14.3.2 Configuring the IPv6 Multicast Forwarding Boundary on an Interface............................................14-7
14.3.3 Configuring the TTL Threshold for IPv6 Multicast Forwarding.......................................................14-7
14.4 Configuring Control Parameters of the IPv6 Multicast Forwarding Table.................................................14-8
14.4.2 Configuring the Maximum Number of Entries in the IPv6 Multicast Forwarding Table..................14-9
14.4.3 Configuring the Maximum Number of Downstream Nodes of a Single Forwarding Entry............14-10
14.5 Maintaining IPv6 Multicast Routing Management...................................................................................14-10
14.5.1 Clearing IPv6 Multicast Forwarding Entries and Routing Entries.................................................. 14-11
14.5.2 Monitoring the Running Status of IPv6 Multicast Forwarding and Routing...................................14-11
14.6 Configuration Examples............................................................................................................................14-12
14.6.1 Example for Configuring IPv6 Multicast Load Splitting.................................................................14-12
15 Multicast Network Management........................................................................................15-1
xxiv Huawei Proprietary and Confidential Issue 04 (2010-08-31)

15.1 Multicast Network Management Introduction............................................................................................15-2

15.1.1 Overview of Multicast Network Management...................................................................................15-2
15.1.2 Multicast Network Management Features Supported by the NE80E/40E.........................................15-2
15.2 Configuring Multicast Network Management............................................................................................15-2
15.2.2 Enabling Multicast Network Management........................................................................................15-3
15.2.3 Binding Multicast MIB to an Instance...............................................................................................15-4
15.2.4 Enabling the Trap Function for IGMP...............................................................................................15-4
15.2.5 Enabling the Trap Function for MLD................................................................................................15-5
15.2.6 Enabling the Trap Function for MRM...............................................................................................15-5
15.2.7 Enabling the MSDP Trap Function....................................................................................................15-5
15.2.8 Enable the PIM Trap Function...........................................................................................................15-6
15.2.9 Enabling the Trap Function for Layer 2 Multicast.............................................................................15-6
15.3 Adjusting the Frequency for Multicast Protocols to Send Trap Messages.................................................15-7
15.3.2 Adjusting the Frequency for IGMP or MLD to Send Trap Messages...............................................15-8
15.3.3 Adjusting the Interval for PIM to Send Trap Messages.....................................................................15-9
15.3.4 Adjusting the Interval for Sending Trap Messages About Join Failure due to Multicast CAC.........15-9
A Glossary.....................................................................................................................................A-1
B Acronyms and Abbreviations.................................................................................................B-1
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xxv

Configuration Guide - IP Multicast Figures
Figures
Figure 1-1 Location of each IPv4 multicast protocol...........................................................................................1-3

Figure 1-2 Format of an IPv6 multicast address..................................................................................................1-6
Figure 1-3 Location of each IPv6 multicast protocol...........................................................................................1-8
Figure 2-1 Networking diagram of configuring basic IGMP functions.............................................................2-26
Figure 2-2 SSM mapping network.....................................................................................................................2-29
Figure 2-3 Networking diagram of configuring IGMP Limit............................................................................2-34
Figure 2-4 Networking diagram of sub-interface for QinQ termination to statically join multicast group
.............................................................................................................................................................................2-37
Figure 3-1 Networking diagram of Layer 2 multicast CAC.................................................................................3-6
Figure 3-2 Application on replication of the multicast VLAN..........................................................................3-32
Figure 3-3 Application of 1+1 protection of multicast VLANs.........................................................................3-37
Figure 3-4 Networking diagram of H-VPLS......................................................................................................3-69
Figure 3-5 Networking diagram of configuring IGMP snooping for a VSI.......................................................3-77
Figure 3-6 Example for configuring IGMP Snooping for a VLAN...................................................................3-83
Figure 3-7 Networking diagram of configuring replication of the multicast VLAN on Router A....................3-86
Figure 3-8 Networking diagram of configuring 1+1 protection of multicast VLANs.......................................3-89
Figure 3-9 Networking diagram of adding an interface to a multicast group statically.....................................3-94
Figure 3-10 Networking diagram of Layer 2 multicast CAC for a VLAN........................................................3-96
Figure 3-11 Networking diagram of Layer 2 multicast CAC for a VSI...........................................................3-100
Figure 3-12 Networking diagram of Layer 2 multicast CAC for a PW...........................................................3-107
Figure 3-13 Networking diagram of Layer 2 multicast SSM mapping............................................................3-113
Figure 3-14 Networking diagram of multicast CAC on a sub-interface for VLAN tag termination...............3-117
Figure 4-1 Location of PIM-DM in the multicast network..................................................................................4-2
Figure 4-2 Networking diagram for configuring basic PIM-DM functions.......................................................4-31
Figure 5-1 Application of PIM-SM a the multicast network...............................................................................5-3
Figure 5-2 Networking diagram for configuring PIM-SM multicast network...................................................5-51
Figure 5-3 Networking diagram for performing SPT switchover in a PIM-SM domain...................................5-60
Figure 5-4 Networking diagram of applying PIM BFD on a multi-router network segment............................5-64
Figure 5-5 Networking diagram of PIM GR......................................................................................................5-68
Figure 6-1 Networking diagram of configuring PIM-SM inter-domain multicast.............................................6-37
Figure 6-2 Networking diagram of configuring inter-AS multicast by using static RPF peers.........................6-44
Figure 6-3 Networking diagram of configuring anycast RP..............................................................................6-48
Figure 7-1 MBGP path selection networking diagram......................................................................................7-29
Figure 8-1 Multicast VPN based on multi-instance.............................................................................................8-2
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xxvii

Figures Configuration Guide - IP Multicast
Figure 8-2 Networking diagram of configuring single-AS MD VPN................................................................8-12

Figure 8-3 Networking diagram of configuring inter-AS MD VPN..................................................................8-31
Figure 9-1 Typical Applications of Multicast CAC.............................................................................................9-3
Figure 9-2 Networking diagram of configuring multicast CAC........................................................................9-10
Figure 10-1 Networking diagram for changing static multicast routes to RPF routes.....................................10-21
Figure 10-2 Networking diagram for connecting the RPF route through static multicast routes....................10-24
Figure 10-3 Networking diagram of implementing multicast through a static multicast routed tunnel..........10-28
Figure 10-4 Networking diagram of configuring multicast load splitting.......................................................10-33
Figure 11-1 Networking diagram of configuring basic MLD functions..........................................................11-20
Figure 11-2 Networking diagram of configuring MLD Limit.........................................................................11-23
Figure 12-1 Networking diagram of configuring basic PIM-DM functions....................................................12-29
Figure 13-1 Networking diagram of configuring basic PIM-SM functions.....................................................13-44
Figure 13-2 Networking diagram of PIM GR..................................................................................................13-52
Figure 14-1 Networking diagram of configuring IPv6 multicast load splitting...............................................14-13
xxviii Huawei Proprietary and Confidential Issue 04 (2010-08-31)

Configuration Guide - IP Multicast Tables
Tables
Table 1-1 Class D addresses.................................................................................................................................1-3

Table 1-2 Multicast protocols...............................................................................................................................1-4
Table 1-3 Description of IPv6 Multicast Addresses.............................................................................................1-7
Table 1-4 Description of commonly-used IPv6 multicast Addresses..................................................................1-7
Table 1-5 IPv6 multicast protocols.......................................................................................................................1-9
Table 8-1 Configuration information about interfaces.......................................................................................8-12
Table 8-2 Networking requirements of Single-AS MD VPN solution..............................................................8-14
Table 8-3 Configuration of router interface........................................................................................................8-32
Table 8-4 Networking requirements of inter-AS MD VPN...............................................................................8-33
Issue 04 (2010-08-31) Huawei Proprietary and Confidential xxix

Configuration Guide - IP Multicast 1 IP Multicast Configuration Guide
1 IP Multicast Configuration Guide
About This Chapter
This chapter describes IP multicast fundamentals, classifications, framework, and packet

forwarding mechanism.
1.1 IP Multicast Introduction
This section describes applications and functions of IP multicast.
1.2 IPv4 Multicast Configuration Guide
This section describes multicast addresses, protocols, and typical configuration solutions in IPv4
networks.
This section describes multicast addresses, protocols, and typical configuration solutions in an
the IPv6 network.
Issue 04 (2010-08-31) Huawei Proprietary and Confidential 1-1

1 IP Multicast Configuration Guide Configuration Guide - IP Multicast
1.1 IP Multicast Introduction

This section describes applications and functions of IP multicast.
1.1.1 IP Multicast Overview

1.1.2 IP Multicast Features Supported by the NE80E/40E
1.1.1 IP Multicast Overview

Multicast is a Point to Multi-Point (P2MP) data transmission mode. During data transmission,
multicast can ensure the security of information. Multicast consumes limited network
bandwidth.
The multicast technology applied to IPv4 and IPv6 is called IP multicast.
The Internet services implemented through IP multicast include IPTV, Video and Audio
Conferences, e-learning, and remote medicine.
1.1.2 IP Multicast Features Supported by the NE80E/40E

In the NE80E/40E, IPv4 networks and IPv6 networks can support multicast services, but
networks that runs IPv4 and IPv6 simultaneously cannot support multicast services.

This section describes multicast addresses, protocols, and typical configuration solutions in IPv4
networks.
1.2.1 IPv4 Multicast Addresses
1.2.2 IPv4 Multicast Protocols
1.2.3 Typical Configuration Solution
1.2.4 Controlling Multicast Forwarding

The IPv4 multicast address ranges from 224.0.0.0 to 239.255.255.255. Table 1-1 shows
description of IPv4 multicast addresses.
The multicast group address available for multicast data services ranges from 224.0.1.0 to
239.255.255.255. Any host (or other receiving device) that joins a multicast group within this
range becomes a member of the group, and can identify and receive IP packets with the IP
multicast address as the destination address. The members of a group can be distributed at any
position in the network. The hosts can join or leave a multicast group at any time.
1-2 Huawei Proprietary and Confidential Issue 04 (2010-08-31)

Table 1-1 Class D addresses

Class D Address Range Description
224.0.0.0 to 224.0.0.255 Indicates the reserved group addresses for local links. The
addresses are reserved by Internet Assigned Number
Authority (IANA) for routing protocols, and are called
permanent multicast group addresses. The addresses are
used to identify a group of specific network devices rather
than being used for multicast forwarding.
224.0.1.0 to 231.255.255.255 Indicates Any-Source Multicast (ASM) addresses. The

233.0.0.0 to 238.255.255.255 addresses are valid in the entire network.
232.0.0.0 to 232.255.255.255 Indicates Source-Specific Multicast (SSM) addresses.

This is the default SSM group address scope, and is valid
in the entire network.
239.0.0.0 to 239.255.255.255 Indicates administration multicast addresses. The default

range of BSR administrative domain group addresses is
valid only in the local BSR administration domain. The
addresses are private addresses. You can configure the
same address in different BSR administration domains.

To implement a complete set of IPv4 multicast services, various multicast protocols deployed
in the network need to cooperate with each other, as shown in Figure 1-1.
Figure 1-1 Location of each IPv4 multicast protocol
IPv4 Network IPv4 Network

AS1 AS2
Source
PIM PIM
MSDP
IGMP IGMP
User User

Table 1-2 Multicast protocols

Applied Objectives Multicast Protocol
Location
Between hosts Connecting hosts to a multicast network: Internet Group Management

and multicast l Ensure that the members can Protocol (IGMP)
routers dynamically join and leave a group at
the host side.
l Manage and maintain the member
relationship at the router side and
exchange information with the upper-
layer multicast routing protocols.
Between intra- Multicast routing and forwarding: Protocol Independent

domain l Create multicast routes on demand. Multicast (PIM), including
multicast Protocol Independent
routers l Respond to the changes of the network Multicast - Dense Mode (PIM-
topology and maintain the multicast DM) and Protocol
routing table. Independent Multicast -
l Forward packets according to the Sparse Mode (PIM-SM)
routing table.
Between inter- Sharing information about inter-domain Multicast Source Discovery

domain multicast sources: Protocol (MSDP)
multicast l routers in the domain where the source
routers resides transmit the local source
information to routers in other
domains.
l routers in different domains transmit
the source information.
CAUTION
Customize configuration solutions according to the actual network conditions and service
requirements. The configuration solution in this section functions only as a reference.
The network environments are classified into two types, which need different configuration
solutions. For details, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide -
IP Multicast.
NOTE
Ensure that unicast routes work normally in the network before configuring IP multicast.

Small-Scale Network
A small-scale network, such as a test network, is suitable to implement multicast data
transmission in a Local Area Network (LAN), and does not interconnect with the Internet.
Perform the following configurations:
1. Enable multicast on all routers in the network.

2. Enable PIM-DM on all interfaces of the routers.
3. Enable IGMP on the router interface connected to hosts.
4. If multicast needs to be deployed in a VPN, perform the preceding configurations in the
private network and public network respectively, and configure the Multicast Domain
(MD) on PEs.
Large-Scale Network
A large-scale network is suitable to bear multicast services on an ISP network, and interconnects
with the Internet.

2. Enable PIM-SM on all interfaces of the routers.
3. Enable IGMP on the router interface connected to hosts.
4. Configure an RP, specify a static RP, or elect an RP from C-RPs.
5. Divide a network into PIM-SM domains.
6. Configure MSDP in the PIM-SM domain and implement the anycast RP.
7. Configure MSDP between PIM-SM domains. Generally, MSDP cooperates with MBGP.
8. If multicast needs to be deployed in a VPN, perform the preceding configurations in the
private network and public network respectively, and configure MD on PEs.

IP multicast guides the forwarding of multicast packets by using the multicast routing table and
forwarding table. You can adjust the transmission path of multicast data by configuring the
Reverse Path Forwarding (RPF) routing policy, and limit multicast forwarding by configuring
the forwarding policy and the capacity of the forwarding table.
For details, refer to the chapter IPv4 Multicast Routing Management in the HUAWEI
NetEngine80E/40E Router Configuration Guide - IP Multicast.

This section describes multicast addresses, protocols, and typical configuration solutions in an
the IPv6 network.


Figure 1-2 shows the format of an IPv6 multicast address.
Figure 1-2 Format of an IPv6 multicast address

0 7 11 15 31
FF flags scope
reserved (80bit)
group ID (32bit)
The meaning of each field is as follows:

l The IPv6 multicast address begins with FF.
l Flags (four-bit): The meaning of the last bit is as follows:
– 0: indicates that the address is a well-known multicast address defined by IANA.
– 1 or 2: indicates multicast addresses within the ASM group address range.
– 3: indicates multicast addresses within the SSM group address range.
– Other: indicates unallocated ones. It can also indicate the multicast addresses within the
ASM group address range.
l Scope (four-bit): indicates that the multicast group contains only the nodes of the same
local network, the same site, and the same organization. The meaning of each field is as
follows:
– 0: reserved
– 1: node/interface-local scope
– 2: link-local scope
– 3: reserved
– 4: admin-local scope
– 5: site-local scope
– 8: organization-local scope
– E: global scope
– F: reserved
– Other: unassigned
Table 1-3 shows the scopes and meanings of fixed IPv6 multicast addresses.

Table 1-3 Description of IPv6 Multicast Addresses

Scope Description
FF0x::/32 Indicates the well-known multicast addresses defined by

the IANA. For details, see Table 1-4.
FF1x::/32 (x cannot be 1 or 2) Indicates ASM addresses. The addresses are valid in the
FF2x::/32 (x cannot be 1 or 2) entire network.
FF3x::/32 (x cannot be 1 or 2) Indicates SSM addresses. This is the default SSM group
address scope, and is valid in the entire network.
Table 1-4 Description of commonly-used IPv6 multicast Addresses

Scope IPv6 Multicast Description
Address
Node/interface-local FF01:0:0:0:0:0:0:1 Indicates all node (interface) addresses.

scope
FF01:0:0:0:0:0:0:2 Indicates all router addresses.
Link-local scope FF02:0:0:0:0:0:0:1 Indicates all node addresses.
FF02:0:0:0:0:0:0:2 Indicates all router addresses.
FF02:0:0:0:0:0:0:3 Indicates the undefined address.
FF02:0:0:0:0:0:0:4 Indicates the Distance Vector Multicast

Routing Protocol (DVMRP) Routers.
FF02:0:0:0:0:0:0:5 Indicates OSPF IGP routers.
FF02:0:0:0:0:0:0:6 Indicates OSPF IGP designated routers.
FF02:0:0:0:0:0:0:7 Indicates ST routers.
FF02:0:0:0:0:0:0:8 Indicates ST hosts.
FF02:0:0:0:0:0:0:9 Indicates RIP routers.
FF02:0:0:0:0:0:0:A Indicates EIGRP routers.
FF02:0:0:0:0:0:0:B Indicates mobile agents.
FF02:0:0:0:0:0:0:D Indicates all PIM routers.
FF02:0:0:0:0:0:0:E Indicates RSVP encapsulation.
FF02:0:0:0:0:0:1:1 Indicates the link name.
FF02:0:0:0:0:0:1:2 Indicates all DHCP agents.
FF02:0:0:0:0:1:FFXX:X Indicates the solicited node address.

XXX XX:XXXX indicates the last 24 bits of
the IPv6 address of a node.

Scope IPv6 Multicast Description

Address
Site-local scope FF05:0:0:0:0:0:0:2 Indicates all router addresses.
FF05:0:0:0:0:0:1:3 Indicates all DHCP severs.
FF05:0:0:0:0:0:1:4 Indicates all DHCP relays.
FF05:0:0:0:0:0:1:1000 to Indicates the service location.

FF05:0:0:0:0:0:1:13FF

To implement a complete set of IPv6 multicast services, various multicast protocols deployed
in a network need to cooperate with each other, as shown in Figure 1-3.
Figure 1-3 Location of each IPv6 multicast protocol
MLD Receiver
IPv6 Network UserA
PIM
Source
Receiver
Multicast UserB
PIM
Server
PIM
MLD Receiver
UserC
UserD

Table 1-5 IPv6 multicast protocols
Location Objectives Multicast Protocol
Between hosts Connecting hosts to a multicast network: Multicast Listener Discovery

and multicast l Implement the dynamic join and (MLD)
routers leaving of members at the host side.
l Manage and maintain the member
relationship at the router side and
exchange information with the upper-
layer multicast routing protocols.
Between Multicast routing and forwarding: PIM-IPv6, including the PIM-

multicast l Create multicast routes on demand. DM and PIM-SM modes
routers
l Dynamically respond to the changes of
the network topology and maintain the
multicast routing table.
l Forward packets according to the
routing table.
CAUTION
Customize the configuration solutions according to the actual network conditions and service
requirements. The configuration solution in this section functions only as a reference.
The network environments are classified into two types, which are suitable for different
configuration solutions. For details, refer to the HUAWEI NetEngine80E/40E Router
Configuration Guide - IP Multicast.
NOTE
Ensure that IPv6 unicast routes work normally in the network before configuring IP multicast.
Small-Scale Network
A small-scale network, such as the test network, is suitable to implement multicast data
transmission in a Local Area Network (LAN), and does not interconnect with the Internet.

2. Enable PIM-IPv6-DM on all router interfaces.
3. Enable MLD on router interfaces connected to hosts.

Large-Scale Network
A large-scale network is suitable to carry multicast services on an ISP network, and interconnects
with the Internet.
2. Enable PIM-IPv6-SM on all router interfaces.
3. Enable MLD on router interfaces connected to hosts.
4. Configure an RP. You can configure an embedded RP, a static RP, or a BSR-RP.

IP multicast guides the forwarding of multicast packets by using the multicast routing table and
forwarding table. You can adjust the transmission path of multicast data by configuring the RPF
routing policy, and limit multicast forwarding by configuring the forwarding policy and the
capacity of the forwarding table.
For details, refer to the chapter IPv6 Multicast Routing Management in the HUAWEI

Configuration Guide - IP Multicast 2 IGMP Configuration
2 IGMP Configuration
About This Chapter
This chapter describes the IGMP fundamentals and configuration steps, and maintenance
commands for IGMP functions, along with typical examples.
2.1 IGMP Introduction
This section describes the basic principle of IGMP and IGMP features supported by the NE80E/
40E.
2.2 Configuring Basic IGMP Functions
This section describes the applications of IGMP and how to configure basic IGMP functions.
2.3 Configuring Options of an IGMP Packet
This section describes how to configure IGMP packet options.
2.4 Configuring IGMP Query Control
This section describes how to configure IGMPv1 and IGMPv2/v3 queriers.
2.5 Configuring SSM Mapping
This section describes how to configure SSM mapping.
2.6 Configuration IGMP Limit Function
This section describes how to configure the IGMP limit function.
2.7 Maintaining IGMP
This section describes how to clear the statistics of IGMP and monitor the running status of
IGMP.
2.8 Configuration Examples
This section provides several configuration examples of IGMP.

2 IGMP Configuration Configuration Guide - IP Multicast
2.1 IGMP Introduction

This section describes the basic principle of IGMP and IGMP features supported by the NE80E/
40E.
2.1.1 IGMP Overview

2.1.2 IGMP Features Supported by the NE80E/40E
2.1.1 IGMP Overview
With the wide applications of multicast, increasingly more hosts join the related multicast
groups. Managing multicast groups and related members on routers becomes an important issue.
In the TCP/IP suite, the Internet Group Management Protocol (IGMP) manages IPv4 multicast
members. It establishes and maintains the relationship between IP hosts and routers that are
directly connected to the IP hosts.
IGMP is a signaling mechanism of hosts towards routers on the leaf network of IP multicast.
IGMP can be divided into two functional parts: at the host side and at the router side.
NOTE
The Operating System (OS) of a host determines which version of IGMP is supported by the host.
l All hosts that participate in multicast transmission must be enabled with IGMP. Hosts can
randomly join or leave the related multicast groups, and the number of hosts is not limited.
l Through IGMP, a multicast router can know whether there is a member of a certain group
in the network segment to which each interface of the router is connected. Hosts store
information only about the multicast groups they join.
At present, IGMP has three versions, that is, IGMPv1 (defined in RFC 1112), IGMPv2 (defined
in RFC 2236), and IGMPv3 (defined in RFC 3376). All IGMP versions support the Any-Source
Multicast (ASM) model. IGMPv3 can be directly applied to the Source-Specific Multicast
(SSM) model, whereas IGMPv1 and IGMPv2 require the technical support of SSM mapping
when they are applied to the SSM model.
2.1.2 IGMP Features Supported by the NE80E/40E
Basic Functions of IGMP

The basic IGMP functions supported by the NE80E/40E are as follows:
l Supporting IGMPv1, IGMPv2, and IGMPv3. The IGMP version can be configured.
l Supporting static IGMP.
l Configuring the range of multicast groups that an interface can join.
Currently, IGMPv3 supported by the NE80E/40E can process the packets matching the
following situations:
l The group address is within the SSM group address range.

l The group address is within the ASM group address range, the mode of Group Record is
MODE_IS_EXCLUDE or CHANGE_TO_EXCLUDE_MODE, and the source address list
is null.
All the packets that do not match these conditions are not processed.
Router-Alert
Through Router-Alert, IGMP sends the messages related to the group that the local device does
not join to the upper protocol for processing.
According to requirements, users can determine whether to set Router-Alert in IGMP packets
to be sent, and whether to require that the received IGMP packets contain Router-Alert.
IGMP Query Controller

For IGMPv1, users can set the interval for sending general query messages and the robustness
variable.
For IGMPv2, users can configure the interval for sending general query messages, robustness
variables, the maximum response time of IGMP query packets, and IGMP fast leave.
For IGMPv3, users can configure the interval for sending general query messages, robustness
variables, and the maximum response time of IGMP query packets.
SSM-Mapping
You can configure SSM mapping on routers to provide SSM services for hosts that run IGMPv1
or IGMPv2.
Limiting the Number of IGMP Group Memberships

l Limiting the total number of IGMP group memberships on a router: The total number of
IGMP group memberships created by a router cannot exceed the limit value. When the total
number of IGMP group memberships created by a router exceeds the limit value, no IGMP
entry can be created.
l Limiting the total number of IGMP group memberships in a single instance: The total
number of IGMP group memberships related to an instance cannot exceed the limit value.
When the total number of IGMP group memberships related to an instance reaches the limit
value, no IGMP entry can be created.
l Limiting the total number of IGMP group memberships on an interface: The total number
of IGMP group memberships created on an interface cannot exceed the limit value. When
the total number of IGMP group memberships created on an interface reaches the limit
value, no IGMP entry can be created.
Host Addresses-based IGMP Report Messages Filtering

Through certain filtering rules, you can filter IGMP Report messages based on host addresses.
2.2 Configuring Basic IGMP Functions

This section describes the applications of IGMP and how to configure basic IGMP functions.
2.2.1 Establishing the Configuration Task

2.2.2 Enabling IP Multicast Routing

2.2.3 Enabling Basic IGMP Functions
2.2.4 Configuring IGMP Version
2.2.5 Configuring a Static IGMP Group
2.2.6 (Optional) Configuring an Interface to Join a Multicast Group in a Certain Range
2.2.7 Checking the Configuration
Applicable Environment
IGMP is applicable to the network segment where routers are connected to hosts. routers and
hosts need to run IGMP. This section only describes how to configure IGMP on routers.
Before configuring IGMP, enable IP multicast routing. IP multicast routing is the precondition
for configuring all multicast functions. If IP multicast routing is disabled, the configurations
related to multicast are deleted.
You need to enable IGMP on the interface connected to hosts. Because the packet formats of
IGMPv1, IGMPv2, and IGMPv3 are different, you need to specify the IGMP version for
routers and hosts first (the later version at the router side is compatible with the earlier version
at the host side). After this, you can perform other IGMP configurations.
You can set an ACL rule so that the host joins specified multicast groups and receive packets
from these groups. This ACL rule serves as a filter on the associated interface and limits the
range of groups that an interface joins.
Pre-configuration Tasks
Before configuring basic IGMP functions, complete the following tasks:
l Configuring the link layer protocol parameters and an IP address for each interface to make
the link protocol of the interface Up
l Configuring a unicast routing protocol to make IP routes between nodes reachable
Data Preparation
To configure basic IGMP functions, you need the following data.
No. Data
1 IGMP version
2 Group address and source address used to configure multicast static routes
3 (Optional) ACL rules defined to filter multicast group addresses

NOTE
l The configuration in the IGMP view is globally effective, whereas the configuration in the interface
view is effective only on the interface.
l When the command is not used in the interface view, the global values set in the IGMP view are used.
When the command is used in both views, the values set in the interface view are preferred.
Context
Do as follows on the router connected to hosts:
Procedure
Step 1 Run:
system-view
The system view is displayed.
Step 2 Run:
multicast routing-enable
IP multicast routing is enabled in the public network instance.
By default, IPv4 multicast routing is not enabled in the public network instance.
CAUTION
Configurations related to VPN instances are applicable only to PE routers. On the PE, if the
VPN instance interface is connected to hosts, you need to perform Step 3 and Step 4.
Step 3 (Optional) Run:

ip vpn-instance vpn-instance-name
The VPN instance view is displayed.

IP multicast routing is enabled in the VPN instance.
----End
2.2.3 Enabling Basic IGMP Functions
Context
Do as follows on the router connecting the host:

Procedure
Step 1 Run:
system-view

Step 2 Run:
interface interface-type interface-number
The interface view is displayed.

interface-type interface-number specified the interface connecting the host.
Step 3 Run:
igmp enable
IGMP is enabled.
By default, IGMP is not enabled on the interface.
----End
2.2.4 Configuring IGMP Version
Context
CAUTION
All the routers on the same subnet must be configured with the same IGMP version. By default,
IGMPv2 is adopted.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
igmp version { 1 | 2 | 3 }
The IGMP version is set for the interface.
----End
2.2.5 Configuring a Static IGMP Group

Context
The configuration is optional. By default, the interface does not statically join any multicast
group.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Choose one of the following configures to configure an interface to statically join one or more
multicast groups
l To configure an interface to statically join one or multiple multicast groups, run:
igmp static-group group-address [ inc-step-mask { group-mask | group-mask-
length } number group-number ] [ source source-address ]
l To configure sub-interface for QinQ termination or Dot1q termination to statically join one
or multiple multicast groups, run:
igmp static-group group-address [ inc-step-mask { group-mask | group-mask-
length } number group-number ] { qinq pe-vid pe-vid ce-vid low-ce-vid [ to high-
ce-vid ] | dot1q vid low-pe-vid [ to high-pe-vid ] }
NOTE
The static group with VLAN tag can be configured only on the sub-interface for QinQ termination or
the sub-interface for Dot1q termination.
After the interface joins the multicast groups, the router considers that the members of the
multicast groups exist on the network segment where the interface resides.
----End
2.2.6 (Optional) Configuring an Interface to Join a Multicast Group

in a Certain Range
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
igmp group-policy { acl-number | acl-name acl-name } [ 1 | 2 | 3 ]
The range of multicast groups that the interface is allowed to join is configured.
----End
Procedure
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] interface
[ interface-type interface-number | up | down ] [ verbose ] command to check the
configuration and running of IGMP on an interface.
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] group [ group-
address | interface interface-type interface-number ] * static command to check the
members of static IGMP multicast groups.
address | interface interface-type interface-number ] * verbose command to check the
members of an IGMP multicast group.
----End
2.3 Configuring Options of an IGMP Packet

This section describes how to configure IGMP packet options.
2.3.2 Configuring a Router to Reject IGMP Packets Without the Router-Alert Option
2.3.3 Configuring a Router to Send IGMP Packets Without the Router-Alert Option
2.3.4 Configuring Host Address-based IGMP Report Message Filtering
The Router-Alert option is used to send the IGMPmessages of which the multicast group is not
specified by the upper-layer protocol of the IP layer to the upper-layer protocol for processing.
For details of Route-Alert, refer to RFC 2113.
By checking host addresses in the IP headers encapsulating IGMP Report messages, IGMP
Report message filtering is achieved.
Before configuring options of an IGMP message, complete the following task:

l Configuring a unicast routing protocol

l Configuring basic IGMP functions
Data Preparation
To configure options of an IGMP message, you need the following data.
No. Data
1 Whether a packet should contain the Router-Alert option
2 Type and number of the interface on which IGMP Report messages need to be filtered
2.3.2 Configuring a Router to Reject IGMP Packets Without the

Router-Alert Option
Context
By default, routers do not check the Router-Alert option contained in IGMP packets. That is,
routers process all the received IGMP packets, including the IGMP packets without the Router-
Alert option.
When a user does not want to receive the IGMP packets without Router-Alert option, do as
follows on the router connected to the user:
NOTE
The configuration involves the following cases:

l Global configuration: It is valid on all interfaces.
l Configuration on an interface: The configuration on an interface takes precedence over the global
configuration. If the configuration on an interface is not done, the global configuration is used.
Procedure
l Global Configuration
1. Run:
system-view

2. Run:
igmp [ vpn-instance vpn-instance-name ]
The IGMP view is displayed.

3. Run:
require-router-alert
The router is configured to receive only the IGMP packets with the Router-Alert
option.
The IGMP packets without the Router-Alert option are discarded.

l Configuration on an Interface
1. Run:
system-view

2. Run:
The interface is connected to hosts or a switch.

3. Run:
igmp require-router-alert
The router is configured to receive only the IGMP packets with the Router-Alert
option.
The IGMP packets without the Router-Alert option are discarded.
----End
2.3.3 Configuring a Router to Send IGMP Packets Without the

Router-Alert Option
Context
By default, the IGMP packets sent by routers contain the Router-Alert option.
To configure a router to send the IGMP packets without the Router-Alert option, do as follows
on the router connected to hosts:
NOTE

Procedure
1. Run:
system-view

2. Run:

3. Run:
undo send-router-alert
The header of a sent IGMP packet does not contain the Router-Alert option.

1. Run:
system-view

2. Run:

The interface is connected to hosts or a switch.
3. Run:
undo igmp send-router-alert
The header of a sent IGMP packet does not contain the Router-Alert option.
----End
2.3.4 Configuring Host Address-based IGMP Report Message

Filtering
Context
By default, the router does not filter the received IGMP Report messages based on host addresses.
The rules for filtering IGMP Report messages based on host addresses are as follows:
l Processing the IGMP Report messages whose host addresses are at the same network
segment with the addresses of the inbound interfaces of the IGMP Report messages or
processing the IGMP Report messages whose host addresses are 0.0.0.0
l Discarding the IGMP Report messages if the host addresses in the IP headers are at different
network segments from the addresses of the inbound interfaces of the IGMP Report
messages
When you need to filter IGMP Report messages based on host addresses, do as follows on the
interface of the router connected with the host:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
igmp ip-source-policy
Filtering IGMP Report messages based on host addresses is configured.
----End

Procedure
address | interface interface-type interface-number ] * [ static ] [ verbose ] command to
check information about the members of an IGMP group.
----End
2.4 Configuring IGMP Query Control

This section describes how to configure IGMPv1 and IGMPv2/v3 queriers.
2.4.2 Configuring an IGMPv1 Querier
2.4.3 Configure an IGMPv2/v3 Querier
CAUTION
A great many of IGMP interfaces exist on the network and the IGMP interfaces are mutually
restricted. Therefore, ensure that all the IGMP parameter values of all the IGMP router interfaces
on the same network segment are identical. Otherwise, the network may be faulty.
The querier periodically sends IGMP query messages on a shared network connected to
receivers. When receiving a Report message from a member, the querier refreshes information
about the members.
If non-queriers do not receive any general query message within the Keepalive period of other
IGMP queriers, the querier is considered faulty, and a new round of querier election is triggered
automatically.
In ADSL dial-up access, the querier corresponds to only one host because a single host
corresponds to one port. When a receiver frequently joins or leaves multiple multicast groups,
like switchover among TV channels, you can enable the mechanism of fast leave on the querier.
Before configuring IGMP query control, complete the following tasks:

l Configuring a unicast routing protocol to interconnect the entire multicast domain

l Configuring Basic IGMP Functions
Data Preparation
To configure IGMP query control, you need the following data.
No. Data
1 Interval for sending IGMP general query messages
2 Robustness variable
3 Maximum response time of IGMP query messages
4 Keepalive time of other IGMP queriers
5 Interval for sending IGMP last member query messages
6 ACL list used to control the application range of fast leave
2.4.2 Configuring an IGMPv1 Querier
Context
CAUTION
This configuration is applicable only to IGMPv1.
This configuration is optional. Do as follows on the router connected to hosts.
NOTE

Procedure
1. Run:
system-view

2. Run:

3. Run:
timer query interval
The interval for sending general query messages is set.
By default, the interval for sending general query messages is 60 seconds.

4. Run:
robust-count robust-value
The robustness variable is set.
By default, the IGMP robustness variable is 2.

1. Run:
system-view

2. Run:

3. Run:
igmp timer query interval

4. Run:
igmp robust-count robust-value
----End
2.4.3 Configure an IGMPv2/v3 Querier
Context
CAUTION
This configuration is applicable only to IGMPv2 and IGMPv3. In actual configuration, ensure
that the interval for sending general query messages is greater than the maximum response time
but is smaller than the Keepalive time of other IGMP queriers.
This configuration is optional. Do as follows on the router connected to hosts.
NOTE


Procedure
1. Run:
system-view

2. Run:

3. Run:

By default, the interval for sending general query messages is 60 seconds.
4. Run:

By default, the robustness variable is 2.
When a router starts, the router sends general query messages for the number of robust-
value times. The sending interval is 1/4 of the interval for sending IGMP general query
messages. When a router receives a Leave message,
– For IGMPv2, the router sends group-specific query messages for the number of
robust-value times. The sending interval is the interval for sending IGMP group-
specific query messages.
– For IGMPv3, the router sends group-and-source-specific query messages for the
number of robust-value times. The sending interval is the interval for sending
IGMP group-and-source-specific query messages.
The greater the robustness variable is, the more robust the IGMP router is. However,
the timeout period of the group is longer.
5. Run:
max-response-time interval
The maximum response time is set for the Query messages on the IGMP router.
By default, the maximum IGMP response time is 10 seconds.
6. Run:
timer other-querier-present interval
The Keepalive time of other IGMP queriers is set.

By default, the Keepalive time of other IGMP queriers is obtained through the formula,
that is, the Keepalive time of other IGMP queriers = robustness variable x the interval
for sending general query messages + 1/2 x the maximum response time. When the
default values of the robustness variable, the interval for sending general query
messages, and the maximum response time are used, the Keepalive time of other IGMP
queriers is 125 seconds.
7. Run:
lastmember-queryinterval interval

The interval for sending IGMP last member query messages is set.
The shorter the interval is, the more flexible the querier is.
By default, the interval for sending IGMP last member query messages is 1 second.
1. Run:
system-view

2. Run:

3. Run:
igmp timer query interval

4. Run:
igmp max-response-time interval
The maximum response time to IGMP query messages is set.

5. Run:
igmp timer other-querier-present interval
The Keepalive time of other IGMP queriers is set.

6. Run:
igmp robust-count robust-value
The IGMP robustness variable is set.

7. Run:
igmp lastmember-queryinterval interval
The interval for sending IGMP group-specific messages is set.

8. Run:
igmp on-demand
The group membership on the interface is configured not to time out.

The interface does not send any IGMP query message outside.
By default, the interface takes part in the querier election and sends query messages.
NOTE
This command is valid to IGMPv2 and IGMPv3.

9. Run:
igmp prompt-leave [ group-policy { acl-number | acl-name acl-name } ]
IGMP fast leave is configured.

After receiving a Leave message from a host, the interface does not send the last
member query message, and deletes group membership on the interface immediately.
By default, IGMP sends the last member query message after receiving a Leave
message from a host.

This command is valid only to IGMPv2.
----End
Procedure
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] routing-table
[ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask
{ source-mask | source-mask-length } ] ] * [ static ] [ outgoing-interface-number
[ number ] ] command to check the IGMP routing table.
NOTE
IGMP routing entries are generated on an interface only when the interface is configured with IGMP
but not PIM and the interface functions as an IGMP querier. You can run the display igmp routing-
table command to view IGMP routing entries.
----End

2.5.2 Enabling SSM Mapping
2.5.3 Configuring a Static SSM Mapping Policy
In the network segment where multicast services are provided in the SSM mode, certain hosts
must run IGMPv1/v2 due to various limitations. To provide SSM services for the hosts, you
need to configure static SSM mapping on the router.
To configure SSM mapping, complete the following task:

l Enabling IP Multicast Routing
Data Preparation
To configure SSM mapping, you need the following data.

No. Data
1 Interfaces that need to be configured with SSM mapping
2 Multicast group address and mask, and multicast source address and mask
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
igmp enable
IGMP is enabled.
Step 4 Run:
igmp version 3
IGMPv3 is configured.
To ensure that hosts that run any IGMP version on the network segment can obtain SSM services,
you are recommended to configure IGMPv3 on the interface.
Step 5 Run:
igmp ssm-mapping enable
SSM Mapping is enabled.
----End
2.5.3 Configuring a Static SSM Mapping Policy
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ssm-mapping group-address { mask | mask-length } source-address
The mapping from a multicast group to the source is configured.

You can run the command for many times to configure the mapping from a group to multiple
multicast sources.
l group-address { mask | mask-length }: specifies the group address and the mask.
l source-address: specifies the address of the source that sets up the mapping with the group.
----End

Procedure
address | interface interface-type interface-number ] * ssm-mapping [ verbose ] command
to check information about groups involved in SSM mapping.
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] ssm-mapping
group [ group-address ] command to check SSM mapping rules of a specified group
address.
interface [ interface-type interface-number ] command to check whether SSM mapping is
enabled on an interface.
----End
2.6 Configuration IGMP Limit Function

This section describes how to configure the IGMP limit function.
2.6.2 (Optional) Configuring the Maximum Number of Global IGMP Group Memberships
2.6.3 (Optional) Configuring the Maximum Number of Global IGMP Entries in a Single Instance
2.6.4 (Optional) Configuring the Maximum Number of IGMP Group Memberships on an
Interface
2.6.5 (Optional) Configuring the Interface-based Rate Limit for the IGMP Packets to Be Sent
to the CPU

The function of IGMP Limit is applicable to IPv4 PIM-SM and IPv4 PIM-DM networks.
To limit IPTV ICPs and the number of users accessing IP core networks, you can configure the
IGMP limit function.
The IGMP limit function is configured on the last-hop router connected to users. You can
perform the following configurations as required:
l Configure the maximum number of global IGMP group memberships on a router.

l Configure the maximum number of IGMP entries in a single instance.
l Configure the maximum number of IGMP group memberships on an interface.
NOTE
If the IGMP limit function is required to be configured globally, for a single instance, and for an interface
on the same router, it is recommended that the limits on the number of global IGMP group memberships,
the number of IGMP group memberships in the single instance, and the number of IGMP group
memberships on the interface should be in descending order.
Before configuring the IGMP limit function, complete the following task:

l Configuring Basic IGMP Functions
Data Preparation
To configure the IGMP limit function, you need the following data.
No. Data
1 Maximum number of global IGMP group memberships
2 Maximum number of IGMP group memberships in a single instance
3 Maximum number of IGMP group memberships on an interface
2.6.2 (Optional) Configuring the Maximum Number of Global

IGMP Group Memberships
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:
igmp global limit number
The maximum number of global IGMP entries of all instances is set.
----End
2.6.3 (Optional) Configuring the Maximum Number of Global

IGMP Entries in a Single Instance
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
limit number
The maximum number of global IGMP entries in a single instance is set.
----End
2.6.4 (Optional) Configuring the Maximum Number of IGMP

Group Memberships on an Interface
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The IGMP interface view is displayed.

Step 3 Run:
igmp limit number [ except { acl-number | acl-name acl-name } ]
The maximum number of IGMP group memberships is set on the interface.
NOTE
If except is not set in the command, the router is limited by the maximum number of IGMP entries when
creating the entries for all the groups or source/groups.
Before setting except, you need to configure the related ACL. The interface then filters the received IGMP
Join messages according to the ACL. The number of entries specified to be filtered by the ACL is not
limited by the maximum number of IGMP entries.
----End
2.6.5 (Optional) Configuring the Interface-based Rate Limit for the

IGMP Packets to Be Sent to the CPU
Context
Do as follows on the router:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run the following commands according to the interface type:
l In the case of an Ethernet sub-interface, GE sub-interface, or Eth-Trunk sub-interface, run
the cp-rate-limit igmp cir cir-value [ cbs cbs-value ] command to set the rate of the IGMP
packets to be sent to the CPU.
l In the case of a Layer 2 Ethernet interface, Layer 2 GE interface, Layer 2 Eth-Trunk interface,
dot1q terminating sub-interface, or QinQ stacking sub-interface, run the cp-rate-limit
igmp cir cir-value [ cbs cbs-value ] vlan vlan-id1 [ to vlan-id2 ] command to set the rate of
the IGMP packets to be sent to the CPU.
l In the case of a QinQ terminating sub-interface, run the cp-rate-limit igmp cir cir-value
[ cbs cbs-value ] pe-vid pe-vid ce-vid begin-vid [ to end-vid ] command to set the rate of the
IGMP packets to be sent to the CPU.
For the detailed configurations of QinQ interfaces, refer to the Configuration Guide - LAN Access
and MAN Access.
----End


Procedure
l Run the following commands to check information about the members of an IGMP
multicast group.
– display igmp [ vpn-instance vpn-instance-name | all-instance ] group [ group-
address | interface interface-type interface-number ] [ verbose ]
– display igmpdisplay igmp [ vpn-instance vpn-instance-name | all-instance ] group
[ group-address | interface interface-type interface-number ] ssm-mapping
[ verbose ]
l Run the display cp-rate-limit [ slot slot-id ] [ verbose ] command to check the
configuration about all the users that use IGMP packets to launch attacks.
l Run the display cp-rate-limit interface interface-type interface-number [ vlan vlan-id ]
[ verbose ] command to check the configuration about the attackers on a specified interface.
l Run the display cp-rate-limit interface interface-type interface-number pe-vid pe-vid ce-
vid ce-vid [ verbose ] command to check the configuration about the attackers on a QinQ
interface.
----End
Example
# Run the display igmp interface command to view the configuration and running status of
IGMP on the router interface. The display information is as follows:
<RouterA> display igmp interface gigabitethernet 1/0/0
Ethernet0/0/0(10.2.1.1):
IGMP is enabled
Current IGMP version is 2
IGMP state: up
IGMP group policy: none
IGMP limit: 40
Value of query interval for IGMP (negotiated): -
Value of query interval for IGMP (configured): 60 s
Value of other querier timeout for IGMP: 0 s
Value of maximum query response time for IGMP: 10 s
Querier for IGMP: 10.2.1.1 (this router)
Total 1 IGMP Group reported
From the display, you can see the maximum number of IGMP group members on GE1/0/0 of
Router A.
# Display information about the attackers on all LPUs.
<HUAWEI> display cp-rate-limit verbose
[Slot 2]
Interface: GigabitEthernet1/8/0/2.1
PeVid: 0
CeVid: 0
PassBytes(byte): 1391816
PassByteRate(kbps): 200
DropBytes(byte): 5827014740
DropByteRate(kbps): 838529
PassPackets(packet): 13384

PassPacketRate(pps): 240
DropPackets(packet): 56028990
DropPacketRate(pps): 1007848
2.7 Maintaining IGMP

This section describes how to clear the statistics of IGMP and monitor the running status of
IGMP.
2.7.1 Clearing IGMP Group Information
2.7.2 Monitoring the Running Status of IGMP
2.7.1 Clearing IGMP Group Information
Context
CAUTION
The IGMP groups that an interface dynamically joins are deleted after you run the reset igmp
group or the reset igmp group ssm-mapping command. Therefore, receivers cannot receive
multicast information normally. So, confirm the action before you run the command.
Procedure
l Run the reset igmp [ vpn-instance vpn-instance-name | all-instance ] group { all |
interface interface-type interface-number { all | group-address [ mask { group-mask |
group-mask-length } ] [ source-address [ mask { source-mask | source-mask-length } ] ] } }
command in the user view to clear the statistics of the IGMP groups that an interface
dynamically joins.
----End
2.7.2 Monitoring the Running Status of IGMP
Context
In routine maintenance, you can run the following commands in any view to check the running
status of IGMP.
Procedure
address | interface interface-type interface-number ] * [ static ] [ verbose ] command in
any view to check information about IGMP groups.
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] group ssm-
mapping [ group-address | interface interface-type interface-number ] [ verbose ]
command in any view to check information about multicast groups involved in SSM
mapping.


[ interface-type interface-number ] [ verbose ] command in any view to check the
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] routing-table
[ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask
{ source-mask | source-mask-length } ] ] * [ static ] [ outgoing-interface-number
[ number ] ] command in any view to check the IGMP routing table.
group [ group-address ] command in any view to check SSM mapping of a source/group-
specific address.
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] explicit-
tracking [ interface interface-type interface-number [ host-address host-address |
group group-address source source-address ] ] command in any view to check tracking
information about the IGMPv3 hosts that join the specific source and group in Include
mode.
l Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] control-message
counters [ interface interface-type interface-number ] [ message-type { query |
report } ] command in any view to check the statistics of IGMP messages received by
interfaces.
----End

This section provides several configuration examples of IGMP.
2.8.1 Example for Configuring Basic IGMP Functions

2.8.2 Example for Configuring SSM Mapping
2.8.3 Example for Configuring IGMP Limit
2.8.4 Example for Configuring Sub-interface for QinQ Termination to Statically Join Multicast
Group
2.8.1 Example for Configuring Basic IGMP Functions
Networking Requirements
In the IPv4 network shown in Figure 2-1, unicast routes are normal. It is required to implement
multicast in the network to enable hosts to receive the Video On Demand (VOD) information.
When the host connected to a certain interface of a router needs to receive a very popular program
for a long time, you can add the interface to a multicast group statically. As shown in the
following network, if Host A and Host B need to receive the multicast data of multicast group
225.1.1.1 for a long time, add GE 1/0/0 of the routers to multicast group 225.1.1.1 statically.

Figure 2-1 Networking diagram of configuring basic IGMP functions
Ethernet
HostA
RouterA Receiver
POS2/0/0 N1
192.168.1.1/24 GE1/0/0
HostB
10.110.1.1/24
RouterB
POS2/0/0 GE1/0/0
192.168.2.1/24 10.110.2.1/24 Leaf network
HostC
PIM network
RouterC GE1/0/0 Receiver
N2
10.110.2.2/24
POS2/0/0 HostD
192.168.3.1/24
Ethernet
Configuration Roadmap
The configuration roadmap is as follows:
1. Enable multicast on all routers because multicast is a prerequisite to IGMP.

2. Enable PIM-SM on all interfaces.
3. Enable IGMP on the interface connected to hosts.
4. Add GE 1/0/0 on Router A to multicast group 225.1.1.1 statically. In this manner, hosts
can steadily receive the multicast data of multicast group 225.1.1.1 for a long time.
Data Preparation
To complete the configuration, you need the following data:
l Version number of IGMP run on routers and hosts

l Static multicast group address that is 225.1.1.1
Procedure
Step 1 Enable multicast on each router, and configure IGMP and PIM-SM on the interface connected
to hosts.
# Enable multicast on Router A; enable IGMP and PIM-SM on Gigabit Ethernet 1/0/0; configure
the IGMP version to 2.
The configurations of Router B and Router C are the same as the configuration of Router A, and
are not mentioned here.
[RouterA] multicast routing-enable
[RouterA] interface gigabitethernet 1/0/0
[RouterA-GigabitEthernet1/0/0] pim sm
[RouterA-GigabitEthernet1/0/0] igmp enable

[RouterA-GigabitEthernet1/0/0] quit
Step 2 Add GE 1/0/0 on Router A to multicast group 225.1.1.1 statically. In this manner, the hosts
connected to GE 1/0/0 can steadily receive the multicast data sent to multicast group 225.1.1.1.
[RouterA-GigabitEthernet1/0/0] igmp static-group 225.1.1.1
Step 3 Verify the configuration.

IGMP on the interfaces of each router. Take the display on GE 1/0/0 of Router B as an example.
<RouterB> display igmp interface gigabitethernet 1/0/0
Interface information of VPN-Instance: public net
GigabitEthernet1/0/0(10.110.2.1):
IGMP is enabled
IGMP state: up
IGMP limit: -
Value of query interval for IGMP(in seconds): 60 s
Value of other querier timeout for IGMP(in seconds): 0 s
Value of maximum query response time for IGMP(in seconds): 10 s
# Run the display pim routing-table command on Router A to check whether GE 1/0/0 is added
to multicast group 225.1.1.1 statically. If (*, 225.1.1.1) entry is generated on Router A, the
downstream interface is GE 1/0/0, and the protocol type is set to static, it indicates that GE 1/0/0
is successfully added to multicast group 225.1.1.1.
<RouterA> display pim routing-table
VPN-Instance: public net
Total 1 (*, G) entry; 0 (S, G) entry
(*, 225.1.1.1)
RP: 192.168.4.1
Protocol: pim-sm, Flag: WC
UpTime: 00:12:17
Upstream interface: Pos2/0/0
Upstream neighbor: 192.168.1.1
RPF prime neighbor: 192.168.1.1
Downstream interface(s) information:
Total number of downstreams: 1
1: GigabitEthernet1/0/0
Protocol: static, UpTime: 00:12:17, Expires: -
----End
Configuration Files
l Configuration file of Router A
#
sysname RouterA
#
#
interface GigabitEthernet1/0/0
undo shutdown
ip address 10.110.1.1 255.255.255.0
pim sm
igmp enable
igmp static-group 225.1.1.1
#
interface Pos2/0/0
undo shutdown
link-protocol ppp

ip address 192.168.1.1 255.255.255.0

pim sm
#
ospf 1
area 0.0.0.0
network 10.110.1.0 0.0.0.255
network 192.168.1.0 0.0.0.255
#
return
l Configuration file of Router B

#
sysname RouterB
#
#
undo shutdown
ip address 10.110.2.1 255.255.255.0
pim sm
igmp enable
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 192.168.2.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#
return
l Configuration file of Router C

#
sysname RouterC
#
#
undo shutdown
ip address 10.110.2.2 255.255.255.0
pim sm
igmp enable
#
interface Pos2/0/0
link-protocol ppp
ip address 192.168.3.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.3.0 0.0.0.255
#
return
2.8.2 Example for Configuring SSM Mapping
In the multicast network shown in Figure 2-2, PIM-SM is run in the network, and the ASM and
SSM models are used to provide multicast services. The interface connected to the receiver runs
IGMPv3. The IGMP version on the receiver is IGMPv2 and cannot be upgraded to IGMPv3.

The SSM group address range in the network is 232.1.1.0/24. Source 1, Source 2, and Source 3
send multicast data to the multicast groups in this range. It is required that the receiver receive
the multicast data only from Source 1 and Source 3.
Solution: Configure SSM mapping on Router D.
Figure 2-2 SSM mapping network
Source 2 Source 3
133.133.2.1/24 133.133.3.1/24
RouterB RouterC
GE1/0/0 GE3/0/0 GE3/0/0 GE1/0/0
GE2/0/0 GE2/0/0
Leaf network Leaf network

Source 1 PIM-SM
133.133.1.1/24 GE2/0/0 GE2/0/0 DSLAM
GE1/0/0 GE1/0/0
GE3/0/0 GE3/0/0
RouterA RouterD
Leaf network
Receiver
133.133.4.1/24
router Interface IP address router Interface IP address

Router A GE 1/0/0 133.133.1.2/24 Router C GE 1/0/0 133.133.3.2/24
GE 2/0/0 192.168.1.1/24 GE 2/0/0 192.168.3.1/24
GE 3/0/0 192.168.4.2/24 GE 3/0/0 192.168.2.2/24
Router B GE 1/0/0 133.133.2.2/24 Router D GE 1/0/0 133.133.4.2/24
GE 2/0/0 192.168.1.2/24 GE 2/0/0 192.168.3.2/24
GE 3/0/0 192.168.2.1/24 GE 3/0/0 192.168.4.1/24
1. Enable SSM Mapping on the multicast router interface connected to hosts.

2. Configure the SSM group address range on all the multicast routers in the PIM-SM domain.
3. Configure the static SSM mapping rules on the routers that are enabled with SSM Mapping.
Data Preparation
To complete this configuration, you need the following data:
l SSM group address range

l IP addresses of Source 1 and Source 3

Procedure
Step 1 Configure an IP address for each interface and a unicast routing protocol on each router. The
configuration details are not mentioned here.
Step 2 Enable IGMP and SSM mapping on the interface connected to hosts.
[RouterD] multicast routing-enable
[RouterD] interface gigabitethernet 1/0/0
[RouterD-GigabitEthernet1/0/0] igmp enable
[RouterD-GigabitEthernet1/0/0] igmp version 3
[RouterD-GigabitEthernet1/0/0] igmp ssm-mapping enable
[RouterD-GigabitEthernet1/0/0] quit
Step 3 Configure the SSM group address range.

# Configure the SSM group address range to 232.1.1.0/24 on all routers. The configurations on
Router B, Router C, and Router D are similar to those on Router A, and the detailed
configurations are not mentioned here.
[RouterA] acl number 2000
[RouterA-acl-basic-2000] rule permit source 232.1.1.0 0.0.0.255
[RouterA-acl-basic-2000] quit
[RouterA] pim
[RouterA-pim] ssm-policy 2000
Step 4 Configure the static SSM mapping rules on the router connected to hosts.
# Map the multicast groups within the 232.1.1.0/24 range to Source 1 and Source 3.
[RouterD] igmp
[RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.1.1
[RouterD-igmp] ssm-mapping 232.1.1.0 24 133.133.3.1
# View SSM mapping of the source/group-specific address on the router.

<RouterD> display igmp ssm-mapping group
IGMP SSM-Mapping conversion table of VPN-Instance: public net
Total 2 entries Total 2 entries matched
Total 2 entries 2 entries matched
00001. (133.133.1.1, 232.1.1.0)
00002. (133.133.3.1, 232.1.1.0)
Total 2 entries matched

# Configure the receiver to join group 232.1.1.1.
# Run the display igmp group ssm-mapping command to check information about a specified
source/group address. The information about the specified source or group address on Router
D is displayed as follows:
<RouterD> display igmp group ssm-mapping
IGMP SSM mapping interface group report information of VPN-Instance: public net
GigabitEthernet1/0/0 (133.133.4.2):
Total 1 IGMP SSM-Mapping Group reported
Group Address Last Reporter Uptime Expires
232.1.1.1 133.133.4.1 00:01:44 00:00:26
<RouterD> display igmp group ssm-mapping verbose
Interface group report information of VPN-Instance: public net
Limited entry of this VPN-Instance: -
GigabitEthernet1/0/0 (133.133.4.2):
Total entry on this interface: 1
Limited entry on this interface: -
Total 1 IGMP SSM-Mapping Group reported
Group: 232.1.1.1
Uptime: 00:01:52
Expires: 00:00:18

Last reporter: 133.133.4.1

Last-member-query-counter: 0
Last-member-query-timer-expiry: off
Group mode: exclude
Version1-host-present-timer-expiry: off
Version2-host-present-timer-expiry: 00:00:17
# Run the display pim routing-table command to view the PIM-SM routing table on a router.
The PIM-SM routing table on Router D is as follows:
<RouterD> display pim routing-table
Total 0 (*, G) entry; 2 (S, G) entries
(133.133.1.1, 232.1.1.1)
Protocol: pim-ssm, Flag:SG_RCVR
UpTime: 00:11:25
Upstream interface: GigabitEthernet3/0/0
Protocol: ssm-map, UpTime: 00:11:25, Expires:-
(133.133.3.1, 232.1.1.1)
Protocol: pim-ssm, Flag:SG_RCVR
UpTime: 00:11:25
Protocol: ssm-map, UpTime: 00:11:25, Expires:-
----End
Configuration Files
#
sysname RouterA
#
#
acl number 2000
rule 5 permit source 232.1.1.0 0.0.0.255
#
undo shutdown
ip address 133.133.1.2 255.255.255.0
pim sm
#
undo shutdown
ip address 192.168.1.1 255.255.255.0
pim sm
#
undo shutdown
ip address 192.168.4.2 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 133.133.1.0 0.0.0.255
network 192.168.1.0 0.0.0.255
network 192.168.4.0 0.0.0.255
#

pim
ssm-policy 2000
#
return
#
sysname RouterB
#
#
acl number 2000
#
undo shutdown
ip address 133.133.2.2 255.255.255.0
pim sm
#
undo shutdown
ip address 192.168.1.2 255.255.255.0
pim sm
#
undo shutdown
ip address 192.168.2.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 133.133.2.0 0.0.0.255
network 192.168.1.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#
pim
ssm-policy 2000
#
return
#
sysname RouterC
#
#
acl number 2000
#
undo shutdown
ip address 133.133.3.2 255.255.255.0
pim sm
#
undo shutdown
ip address 192.168.3.1 255.255.255.0
pim sm
#
undo shutdown
ip address 192.168.2.2 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 133.133.3.0 0.0.0.255
network 192.168.3.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#

pim
ssm-policy 2000
#
return
l Configuration file of Router D

#
#
acl number 2000
#
undo shutdown
ip address 133.133.4.2 255.255.255.0
pim sm
igmp enable
igmp version 3
igmp ssm-mapping enable
#
undo shutdown
ip address 192.168.3.2 255.255.255.0
pim sm
#
undo shutdown
ip address 192.168.4.1 255.255.255.0
pim sm
#
igmp
ssm-mapping 232.1.1.0 255.255.255.0 133.133.1.1
ssm-mapping 232.1.1.0 255.255.255.0 133.133.3.1
#
pim
ssm-policy 2000
#
return
2.8.3 Example for Configuring IGMP Limit
When a large number of users watch multiple programs simultaneously, great bandwidth of
devices is consumed, which degrades the performance of the devices and lowers the stability of
receiving multicast data.
The existing multicast technologies control multicast networks by limiting the number of
multicast forwarding entries or the number of outgoing interfaces of an entry, which cannot meet
the requirements of operators for real-time video services on IPTV networks and flexible
management of network resources.
Configuring IGMP limit can enable operators to properly plan network resources and flexibly
control the number of multicast groups that hosts can join. In the network shown in Figure
2-3, multicast services are deployed. The global IGMP limit, instance-based IGMP limit, and
interface-based IGMP limit are configured on Router A, Router B, and Router C connected to
hosts to limit the number of multicast groups that the hosts can join. When the number of
multicast groups that hosts can join reaches the limit, the devices are not allowed to create new
IGMP entries. This ensures that the users that join related multicast groups more clearly and
stably watch related programs.

Figure 2-3 Networking diagram of configuring IGMP Limit
Ethernet
HostA
RouterA Receiver
POS2/0/0 N1
192.168.1.1/24 GE1/0/0
HostB
10.110.1.1/24
RouterB
POS2/0/0 GE1/0/0
192.168.2.1/24 10.110.2.1/24 Leaf network
HostC
PIM network
RouterC GE1/0/0 Receiver
N2
10.110.2.2/24
POS2/0/0 HostD
192.168.3.1/24
Ethernet
1. Enable multicast on all routers because multicast is a prerequisite to IGMP.
2. Enable PIM-SM on all interfaces.
3. Enable IGMP on the interface connected to hosts.
4. Add GE 1/0/0 on Router A to multicast group 225.1.1.1 statically. In this manner, hosts
can steadily receive the multicast data of multicast group 225.1.1.1 for a long time.
5. Limit the number of IGMP group memberships on Router A.
Data Preparation
l Version number of IGMP run on routers and hosts
l Static multicast group address that is 225.1.1.1
l The maximum number of IGMP group memberships.
Procedure
Step 1 Enable multicast on each router, and configure IGMP and PIM-SM on the interface connected
to hosts.
# Enable multicast on Router A; enable IGMP and PIM-SM on Gigabit Ethernet 1/0/0; configure
the IGMP version to 2. Configurations of Router B and Router C are similar to those of Router
A, and are not mentioned here.


[RouterA] interface pos 2/0/0
[RouterA-Pos2/0/0] pim sm
[RouterA-Pos2/0/0] quit
Step 2 Add GE 1/0/0 on Router A to multicast group 225.1.1.1 statically. In this manner, the hosts
connected to GE 1/0/0 can steadily receive the multicast data sent to multicast group 225.1.1.1.
[RouterA-GigabitEthernet1/0/0] igmp static-group 225.1.1.1
Step 3 Limit the number of IGMP group memberships on the last-hop router connected to users.
# Configure the maximum number of IGMP group memberships to 50 on Router A.
[RouterA] igmp global limit 50
# Configure the maximum number of IGMP group memberships to 40 in the public network
instance.
[RouterA] igmp
[RouterA-igmp] limit 40
[RouterA-igmp] quit
# Configure the maximum number of IGMP group relationships to 30 on GE 1/0/0.

[RouterA-GigabitEthernet1/0/0] igmp limit 30
# Configurations of Router B and Router C are similar to those of Router A, and are not
mentioned here.
IGMP on the interfaces of each router. Take the display on GE 1/0/0 of Router A as an example.
<RouterA> display igmp interface gigabitethernet 1/0/0
GigabitEthernet1/0/0(10.110.1.1):
IGMP is enabled
IGMP state: up
IGMP limit: 30
Value of query interval for IGMP (configured): 60 s
Value of other querier timeout for IGMP: 0 s
Value of maximum query response time for IGMP: 10 s
From the display, you can see that the maximum number of IGMP group members that the
GE1/0/0 of Router A can create is 30.
----End
Configuration Files
#
sysname RouterA
#
igmp global limit 50
#

#
undo shutdown
ip address 10.110.1.1 255.255.255.0
pim sm
igmp enable
igmp limit 30
igmp static-group 225.1.1.1
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.1.0 0.0.0.255
network 192.168.1.0 0.0.0.255
#
igmp
limit 40
#
return
#
sysname RouterB
#
#
#
undo shutdown
ip address 10.110.2.1 255.255.255.0
pim sm
igmp enable
igmp limit 30
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#
igmp
limit 40
#
return
#
sysname RouterC
#
#
#
undo shutdown
ip address 10.110.2.2 255.255.255.0
pim sm
igmp enable
igmp limit 30

#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.3.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.3.0 0.0.0.255
#
igmp
limit 40
#
return
2.8.4 Example for Configuring Sub-interface for QinQ Termination

to Statically Join Multicast Group
As shown in Figure 2-4, configure sub-interface for QinQ termination to statically join multicast
groups, to make the Receiver receive multicast data sent from the Source.
Figure 2-4 Networking diagram of sub-interface for QinQ termination to statically join multicast
group
vpna
Source
Loopback1
GE1/0/0 2.2.2.9/32
10.1.1.2/24 GE1/0/0 GE2/0/0 PE2
PE1
Loopback1 172.1.1.2/24 172.2.1.1/24 Loopback1
1.1.1.9/32 GE3/0/0 GE3/0/0 3.3.3.9/32
172.1.1.1/24 172.2.1.2/24
GE2/0/0.10 P GE1/0/0
10.2.1.2/24 MPLSbackbone 10.3.1.2/24
AS: 100
Access vpna
network
Receiver

1. Configure OSPF on the backbone network to implement interworking between PEs.
2. Configure the basic MPLS functions and MPLS LDP on the PEs and establish the MPLS
LSPs between the PEs.
3. Configure the VPN instance on the PE and bind VPN instance with the interface to Source
and the interface to Receiver.
4. Configure MP IBGP to exchange the VPN routing information between the PEs.
5. Configuring sub-interface for QinQ termination to statically join multicast groups
Data Preparation
To configuring sub-interface for QinQ termination to statically join multicast groups, you need
the following data:
l MPLS LSR-IDs on the PEs and the Ps
l VPN instance name, RD, VPN-Target
l ID of the outer QinQ VLAN tag, value range of the inner QinQ VLAN tag
Procedure
Step 1 Configure basic BGP/MPLS IP VPN.
The specific configuration procedures are omitted here.
Step 2 Configure VPN instance on PE, configure sub-interface for QinQ termination and bind the
interface with the VPN instance.
# Configure PE1.
# Configure VPN instance.
[PE1] ip vpn-instance vpna
[PE1-vpn-instance-vpna] route-distinguisher 100:1
[PE1-vpn-instance-vpna] vpn-target 111:1 both
[PE1-vpn-instance-vpna] quit
# Bind the VPN instance with the interface to the Source.

[PE1] interface gigabitethernet 1/0/0
[PE1-GigabitEthernet1/0/0] ip binding vpn-instance vpna
[PE1-GigabitEthernet1/0/0] ip address 10.1.1.2 24
[PE1-GigabitEthernet1/0/0] quit
# Bind the VPN instance with the interface to the Receiver.

# Configure the interface to the Receiver as the user termination mode.

[PE1-GigabitEthernet2/0/0] mode user-termination

# Create a sub-interface for QinQ termination and configure VLAN ID.

[PE1] interface gigabitethernet 2/0/0.10
[PE1-GigabitEthernet2/0/0.10] control-vid 10 qinq-termination
[PE1-GigabitEthernet2/0/0.10] qinq termination pe-vid 1 ce-vid 1 to 2
[PE1-GigabitEthernet2/0/0.10] ip address 10.2.1.2 24
[PE1-GigabitEthernet2/0/0.10] quit
# Configure PE2.
# Configure VPN instance.

[PE2] ip vpn-instance vpna
[PE2-vpn-instance-vpna] route-distinguisher 100:2
[PE2-vpn-instance-vpna] vpn-target 111:1 both
[PE2-vpn-instance-vpna] quit
# Bind the VPN instance with the GE1/0/0 of PE2.

[PE2-GigabitEthernet1/0/0] ip address 10.3.1.2 24
Step 3 Add the route of the Source and the route of the Receiver to VPN routing-table.
# Configure PE1.
[PE1] bgp 100
[PE1-bgp] ipv4-family vpn-instance vpna
[PE1-bgp-vpna] import-route direct
[PE1-bgp-vpna] quit
# Configure PE2.
[PE2] bgp 100
[PE2-bgp] ipv4-family vpn-instance vpna
[PE2-bgp-vpna] import-route direct
[PE2-bgp-vpna] quit
After the configuration above, run the display ip routing-table vpn-instance command on PE1.
The route of the Source and the route of the Receiver are added to VPN routing-table.
[PE1] display ip routing-table vpn-instance vpna
Route Flags: R - relied, D - download to fib
------------------------------------------------------------------------------
Routing Tables: vpna
Destinations : 5 Routes : 5
Destination/Mask Proto Pre Cost Flags NextHop Interface
10.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet1/0/0
10.1.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0
10.2.1.0/24 Direct 0 0 D 10.2.1.2 GigabitEthernet2/0/0
10.3.1.0/24 BGP 255 0 RD 3.3.3.9 GigabitEthernet3/0/0
Step 4 Configure multicast routing-enable in the public instance on PE1, P and PE2.
# Configure PE1.
[PE1] multicast routing-enable
# Configure P.
[P] multicast routing-enable
# Configure PE2.
[PE2] multicast routing-enable

Step 5 Configure multicast basic function.

# Configure PIM-SM in the public network.
# Configure PE1.
[PE1-GigabitEthernet3/0/0] pim sm
[PE1] interface loopback 1
[PE1-LoopBack1] pim sm
[PE1-LoopBack1] quit
# Configure P.
[P] interface gigabitethernet 1/0/0
[P-GigabitEthernet1/0/0] pim sm
[P-GigabitEthernet1/0/0] quit
[P-GigabitEthernet2/0/0] quit
[P] interface loopback 1
[P-LoopBack1] pim sm
[P-LoopBack1] quit
# Configure PE2.
[PE2-GigabitEthernet3/0/0] pim sm
[PE2] interface loopback 1
[PE2-LoopBack1] pim sm
[PE2-LoopBack1] quit
# Configure RP in the public instance.

[P] pim
[P] c-bsr loopback 1
[P] c-rp loopback 1
# Configure IGMP on the main interface to the Receiver.

[PE1-GigabitEthernet2/0/0] igmp enable
Step 6 Configuring sub-interface for QinQ termination to statically join multicast groups.
[PE1] interface gigabitethernet 2/0/0.10
[PE2-GigabitEthernet2/0/0.10] igmp static-group 225.0.0.1 inc-step-mask 0.0.0.1
number 17 qinq pe-vid 1 ce-vid 1 to 2

After the configuration, run the display pim vpn-instance vpna routing-table command on
PE1 to check the multicast routing-table information.
Run the display igmp-snooping qinq-port-info interface gigabitethernet 2/0/0.10 to check
the multicast group information on the sub-interface for QinQ termination.
<PE1> display igmp-snooping qinq-port-info interface gigabitethernet 2/0/0.10
Interface GigabitEthernet2/0/0.10, 17 Group(s)
(Source,Group) PE-VID/CE-VID LiveTime Flag
-----------------------------------------------------------------------
( *,225.0.0.1 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.2 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.3 ) 1/1 -------- S-
1/2 -------- S-

( *,225.0.0.4 ) 1/1 -------- S-

1/2 -------- S-
( *,225.0.0.5 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.6 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.7 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.8 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.9 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.10 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.11 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.12 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.13 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.14 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.15 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.16 ) 1/1 -------- S-
1/2 -------- S-
( *,225.0.0.17 ) 1/1 -------- S-
1/2 -------- S-
----End
Configuration Files
l Configuration file of PE1
#
sysname PE1
#
router id 1.1.1.9
#
#
mpls lsr-id 1.1.1.9
mpls
#
mpls ldp
#
ip vpn-instance vpna
route-distinguisher 100:1
vpn-target 111:1 export-extcommunity
vpn-target 111:1 import-extcommunity
#
undo shutdown
ip binding vpn-instance vpna
ip address 10.1.1.2 255.255.255.0
pim sm
#
undo shutdown
mode user-termination
pim sm
igmp enable
#
interface gigabitethernet 2/0/0.10
control-vid 10 qinq-termination
qinq termination pe-vid 1 ce-vid 1 to 2

ip address 10.2.1.2 255.255.255.0

igmp static-group 225.0.0.1 inc-step-mask 0.0.0.1 number 17 qinq pe-vid 1 ce-
vid 1 to 2
#
undo shutdown
ip address 172.1.1.1 255.255.255.0
pim sm
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.9 255.255.255.255
pim sm
#
bgp 100
peer 3.3.3.9 as-number 100
peer 3.3.3.9 connect-interface LoopBack1
#
ipv4-family unicast
undo synchronization
peer 3.3.3.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 3.3.3.9 enable
#
ipv4-family vpn-instance vpna
import-route direct
#
ospf 1
area 0.0.0.0
network 172.1.1.0 0.0.0.255
network 1.1.1.9 0.0.0.0
#
return
l Configuration file of P
#
sysname P
#
router id 2.2.2.9
#
#
mpls lsr-id 2.2.2.9
mpls
#
mpls ldp
#
undo shutdown
ip address 172.1.1.2 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 172.2.1.1 255.255.255.0
pim sm
mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.9 255.255.255.255
pim sm
#
pim
c-bsr LoopBack1

c-rp LoopBack1
#
ospf 1
area 0.0.0.0
network 172.1.1.0 0.0.0.255
network 172.2.1.0 0.0.0.255
network 2.2.2.9 0.0.0.0
#
return

#
sysname PE2
#
router id 3.3.3.9
#
#
mpls lsr-id 3.3.3.9
mpls
#
mpls ldp
#
ip vpn-instance vpna
#
undo shutdown
ip address 10.3.1.2 255.255.255.0
pim sm
#
undo shutdown
ip address 172.2.1.2 255.255.255.0
pim sm
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.9 255.255.255.255
pim sm
#
bgp 100
#
ipv4-family unicast
peer 1.1.1.9 enable
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.9 enable
#
ipv4-family vpn-instance vpna
import-route direct
#
ospf 1
area 0.0.0.0
network 172.2.1.0 0.0.0.255
network 3.3.3.9 0.0.0.0
#
return

Configuration Guide - IP Multicast 3 Layer 2 Multicast Configuration
3 Layer 2 Multicast Configuration
About This Chapter
This chapter describes the Layer 2 Multicas fundamentals and configuration steps and
maintenance for Layer 2 Multicas functions, along with typical examples.
3.1 Layer 2 Multicast Introduction

This section describes the principle and concepts of Layer 2 multicast.
3.2 Configuring IGMP Snooping for a VSI
This section describes how to configure IGMP snooping in the VPLS network.
3.3 Configuring IGMP Snooping for a VLAN
This section describes how to configure IGMP snooping for a VLAN.
3.4 Configuring Trunk Load Balancing for Layer 2 Multicast
This section describes how to configure trunk load balancing for Layer 2 multicast.
3.5 Configuring Replication of the Multicast VLAN
This section describes how to configure replication of the multicast VLAN.
3.6 Configuring 1+1 Protection of Multicast VLANs
This section describes how to configure the multicast 1+1 protection.
3.7 Configuring Static Layer 2 Multicast
This section describes how to configure static Layer 2 multicast.
3.8 Configuring the Network Management Function for Layer 2 Multicast
This section describes how to configure the network management function for Layer 2 multicast.
3.9 Configuring Layer 2 Multicast SSM Mapping
This section describes how to configure the Layer 2 multicast SSM mapping function.
3.10 Configuring Layer 2 Multicast CAC for a VLAN, a Layer 2 Interface, or the Interface in a
Specified VLAN
This section describes how to configure Layer 2 Multicast CAC for a VLAN, a Layer 2 Interface,
or the Interface in a Specified VLAN.
3.11 Configuring Layer 2 Multicast CAC for a VSI
This section describes how to configure Layer 2 Multicast CAC for a VSI.

3 Layer 2 Multicast Configuration Configuration Guide - IP Multicast
3.12 Configuring Layer 2 Multicast CAC for a Sub-interface

This section describes how to configure Layer 2 Multicast CAC for a Sub-interface.
3.13 Configuring Layer 2 Multicast CAC for a PW
This section describes how to configure Layer 2 Multicast CAC for a PW.
3.14 Maintaining Static Layer 2 Multicast
This section describes how to clear the IGMP snooping statistics.
This section provides several configuration examples of Layer 2 multicast.

3.1 Layer 2 Multicast Introduction

This section describes the principle and concepts of Layer 2 multicast.
3.1.1 IGMP Snooping

3.1.2 Replication of the Multicast VLAN
3.1.3 1+1 Protection of Multicast VLANs
3.1.4 Static Layer 2 Multicast
3.1.5 Layer 2 Multicast CAC
Layer 2 multicast CAC is involved in the IPTV multicast scheme and is mainly used to control
the number and bandwidth of IPTV channels in the Layer 2 multicast scenario, thereby
preventing users from requesting additional channels or bandwidth and ensuring high service
qualities for existing users.
3.1.1 IGMP Snooping

Internet Group Management Protocol (IGMP) snooping runs on Layer 2 routers. In the
implementation of Layer 2 multicast, IGMP snooping manages and controls the forwarding of
multicast packets by maintaining information about the outbound port of multicast packets. It
maintains the outbound port information by detecting the multicast protocol packets exchanged
between the upstream router and hosts.
The router supports IGMP snooping for the VLAN.
When the Virtual Private LAN Service (VPLS) network is deployed at the network convergence
layer, the router also supports IGMP snooping for its Virtual Switching Instances (VSIs). In
addition, IGMP snooping is supported by the router in the VPLS over Traffic Engineering (TE)
network.
NOTE
For details about VPLS, refer to the HUAWEI NetEngine80E/40E Router Feature Description - VPN.
Router Port
A router port refers to a port connected to the upstream multicast router. The router port is
classified into the following types:
l Dynamic router port
– A dynamic router port is the port that can receive the IGMP Query message with the
source address that is not 0.0.0.0 or the Protocol Independent Multicast (PIM) Hello
message. The dynamic router port is dynamically maintained through protocol packets
exchanged between routers and hosts.
– Each dynamic router port starts a timer. The timeout period of the timer is the aging
time of the router port. The port is no longer a router port, if the port does not receive
any IGMP Query message with the source address being not 0.0.0.0 or the PIM Hello
message before the timer times out.
l Static router port
– The static router port is specified by using commands and does not age.

Multicast Group Policy

You can configure the multicast group policy and the Source-Specific Multicast (SSM) group
policy by using related commands. The ports in a VLAN or VSI can only be dynamically added
to the group matching Access Control List (ACL) rules.
Prompt Leave
When receiving an IGMP Leave message through a member port, the router immediately deletes
the member port regardless of whether the aging timer times out. The member port thus becomes
invalid and stops receiving multicast packets. This is called prompt leave of member ports.
On the router, if all ports in a VLAN are connected to only one multicast receiver, you can
configure ports in the VLAN to promptly leave some or all multicast groups. This saves the
network bandwidth.
Suppression of IGMP Report Messages

To respond to the IGMP query messages, only one IGMP Report message is sent to the upstream
multicast router, no matter how many hosts in the VLAN or VSI want to join the same multicast
group. This saves the bandwidth at the network side.
IGMP Snooping Querier

A router port is the inbound port of IGMP Query messages on a router. The router sends the
Report and Leave messages of hosts to an upstream router through the router port. By configuring
a querier on the router, you can save the bandwidth between the upstream router and the local
router, because the querier replaces the upstream router to send IGMP Query messages. At the
same time, you can also configure parameters for the IGMP snooping querier based on different
networking requirements.
3.1.2 Replication of the Multicast VLAN

In the traditional multicast on demand mode, Layer 3 devices are required to replicate and send
multicast packets for each Virtual Local Area Network (VLAN), when multicast on demand is
performed for hosts that are connected to Layer 2 devices and that belong to different VLANs.
This wastes the bandwidth and imposes extra burden on Layer 3 devices.
After replication of the multicast VLAN is configured, you can configure different VLANs as
user VLANs of one multicast VLAN on Layer 2 devices, when multicast on demand is performed
for hosts that are connected to Layer 2 devices and that belong to different VLANs. You only
need to enable the Layer 2 multicast function in the multicast VLAN. In this manner, Layer 3
devices only send multicast packets to the multicast VLAN, and are not required to replicate
multicast packets for each VLAN.
By using replication of the multicast VLAN, you can send multicast packets in different VLANs.
Thus, you can easily manage and control the multicast source and the multicast group members
to reduce the waste on bandwidth.
3.1.3 1+1 Protection of Multicast VLANs

To improve the reliability of multicast services, 1+1 protection of multicast VLANs is
implemented on replication of the multicast VLANs for the router.
That is, 1+1 protection of multicast VLANs implements 1+1 backup of multicast packets through
the working VLAN and the protection VLAN. The selection about multicast packets of the

working VLAN or the protection VLAN is determined by the Ethernet Operations,

Administration, and Maintenance (Ethernet OAM) mechanism on the inbound port of multicast
packets. The Continuity Check Message (CCM) detection packets are bound to the working
VLAN and the protection VLAN. If the CCM packets are normal, it indicates that the multicast
packets of the VLAN are normal; otherwise, the multicast packets of the VLAN are abnormal.
In normal situations, multicast packets of the working VLAN are received and multicast packets
of the protection VLAN are discarded directly.
3.1.4 Static Layer 2 Multicast

In static Layer 2 multicast mode, multicast packets are forwarded to only hosts that require the
multicast packets for a long time based on the forwarding table that is configured manually. The
static Layer 2 multicast mode has the following advantages:
l Avoids flood of protocol packets.
l Reduces the network delay by directly searching the multicast forwarding table to transmit
multicast packets.
l Improves the information security and implements the payment provision mechanism for
services by preventing unregistered hosts from receiving the multicast traffic.
3.1.5 Layer 2 Multicast CAC

Layer 2 multicast CAC is involved in the IPTV multicast scheme and is mainly used to control
the number and bandwidth of IPTV channels in the Layer 2 multicast scenario, thereby
preventing users from requesting additional channels or bandwidth and ensuring high service
qualities for existing users.
Configuration Perspective of CAC

As shown in Figure 3-1, IGMP snooping-based Layer 2 multicast CAC is configured on the
UPE to restrict the number or bandwidth of IPTV channels, thereby preventing subscribers from
requesting additional channels or bandwidth and ensuring high service quality for existing
viewers.

Figure 3-1 Networking diagram of Layer 2 multicast CAC
BTV
NPE
IP/MPLS
UPE DSLAM
CE
IGMP snooping-based Layer 2 multicast CAC can be configured differently, depending on the
networks that deliver multicast services:
l Global Layer 2 multicast CAC
l Layer 2 multicast CAC for a VLAN
l Layer 2 multicast CAC for a VSI
l Multicast CAC for a Layer 2 interface or Layer 2 multicast CAC for an interface in the
specified VALN
l Layer 2 multicast CAC for a sub-interface
l Layer 2 multicast CAC for a PW
Objects Restricted by CAC

Layer 2 multicast CAC can restrict the following aspects:
l Number of multicast group members
l Bandwidth of multicast groups
l Number of channels
l Bandwidth of channels
Working Process of CAC

In practice, CAC can be implemented in two areas: VLAN areaWhen the router receives Report
messages from a user, the system performs CAC over these Report messages from perspectives
of port and VLAN, port, VLAN, and global configuration in sequence to respectively check the

number of multicast group members, bandwidth of multicast group members, number of

channels, and bandwidth of channels. If all the checked items are within the limit, the system
creates a forwarding entry for the user; if any checked item exceeds the limit, the system does
not create the forwarding entry for the user. VSI area Interfaces are bound to the VSI.When the
router receives Report messages from a user, the system performs CAC over these Report
messages from perspectives of subinterface, VSI, and global configuration in sequence to check
the number of multicast group members, bandwidth of multicast group members, number of
channels, and bandwidth of channels respectively. If all the checked items are within the limit,
the system creates a forwarding entry for the user; if any checked item exceeds the limit, the
system does not create the forwarding entry for the user. A PW accesses the VSI.When the router
receives Report messages from a user, the system performs CAC over these Report messages
from perspectives of PW, VSI, and global configuration in sequence to check the number of
multicast group members, bandwidth of multicast group members, number of channels, and
bandwidth of channels respectively. If all the checked items are within the limit, the system
creates a forwarding entry for the user; if any checked item exceeds the limit, the system does
not create the forwarding entry for the user. Interfaces that can be bound to a VSI are VLANIF
interfaces, sub-interfaces for QinQ VLAN tag termination, sub-interfaces for dot1q VLAN tag
termination, and common sub-interfaces.
Counting Rules of CAC

When referring to configuring multicast CAC bandwidth limit, it does not mean the manual
allocation of the bandwidth. Instead, the bandwidth is configured for multicast groups from
different perspectives. It is required that all the bandwidth configured for multicast groups be
smaller than the bandwidth that has been configured for channels in the VLAN or VSI so that
the number of entries on the device can be limited.
When configuring channel-based CAC in IGMPv3, you need to set the channel type to ASM or
SSM. If the channel type is ASM, the system counts and processes (*, G) and (S, G) entries; if
the channel type is SSM, the system counts and processes (S, G) entries.
NOTE
When configuring an SSM channel, you must run the command to create the source IP address to be
mapped; when configuring an ASM channel, you need not configure the source IP address to be mapped.
You can run the igmp-snooping ssm-policy command to change the multicast address range of
the ASM and SSM channels rather than the counting rules of CAC. You are recommended to
run the igmp-snooping ssm-policy command prior to setting the channel type to SSM. In this
case, the multicast group address range of the SSM and ASM channels is consistent with that
configured through the igmp-snooping ssm-policy command.
CAC over Static Entries and Fast-Channel Entries

CAC over Static Entries and Fast-Channel Entries as follows:
l The number of static entries is not limited and counted.
l The number of fast-channel entries is not limited but counted. For example, if the CAC
limit set for VLAN10 is 100 and there have been 80 fast-channel entries, the system can
add a maximum of 20 entries. If there have been 100 or more than 100 fast-channel entries,
the system can no longer add entries. Fast-channel entries can be configured only in the
VLAN and VSI views, and therefore only fast-channel entries in the VLAN and VSI are
counted.

NOTE
The system use the multicast CAC bandwidth limit to process the entries triggered by multicast streams
the same as fast-channel entries.
3.2 Configuring IGMP Snooping for a VSI

This section describes how to configure IGMP snooping in the VPLS network.

3.2.2 Configuring Basic IGMP Snooping Functions for a VSI
3.2.3 Configuring a Static Router Port for a VSI
3.2.4 Configuring the Dynamic Learning of Router Ports for a VSI
3.2.5 Configuring the IGMP Snooping Querier for a VSI
3.2.6 Configuring Parameters for the IGMP Snooping Querier for a VSI
3.2.7 Configuring the Multicast Policy for a VSI
3.2.8 Configuring Prompt Leave for Ports for a VSI
3.2.9 Configuring IGMP Proxy for a VSI
3.2.10 Configuring the IGMP Fast Join Function for a VSI
In a VPLS network, the multicast traffic is broadcast in the VSI if IGMP snooping is not enabled
on PE devices. To prevent the multicast traffic from being transmitted on the PW on which no
receiver exists, you need to configure IGMP snooping for the VSI.
In the network, concepts related to IGMP snooping are as follows:
l Static router port: When the network topology is stable, you can configure router ports on
the router as static router ports.
l IGMP snooping querier: To save the bandwidth between the upstream router and the local
router, you can configure the querier on the local router. The querier replaces the upstream
router to send IGMP Query messages. You can also configure parameters for the IGMP
snooping querier as required.
l Multicast policy: You can configure the multicast policy for a VSI, when you need to
specify the range of multicast groups that hosts in a certain VSI can access.
l Prompt response to changes in the Layer 2 link: When the Layer 2 link changes, the
router must rapidly update information about the ports so that the multicast traffic can be
forwarded without interruptions.
l After the igmp-snooping send-query enable command is used, the router sends the IGMP
General Query message with the source IP address being not 0.0.0.0 when Layer 2 links

change. In this manner, other routers can rapidly update their router port. The port link
change event is received by the ports in the VSI.
l For the MSTP port link change event, the Query message is sent to all non-router ports in
the VSI.
l For the RRPP and RPR port link change events, the Query message is sent to only the ports
that receive the event.
l Prompt leave: When only one host exists for all ports in a VSI, you can configure prompt
leave for the ports to save the network bandwidth.
l Suppression for IGMP messages: After the igmp-snooping proxy command is used, IGMP
proxy provides two functions: querier and message suppression. Through the querier
function, a switch can replace the upstream router to send IGMP Query messages; through
the message suppression function, the switch can replace the upstream router to receive
IGMP Report and Leave messages. Therefore, after IGMP proxy is enabled on the local
router, bandwidth of the link between the upstream router and local router can be saved.
Before configuring IGMP snooping for a VSI, complete the following tasks:
l Connecting interfaces and setting physical parameters for the interfaces so that the physical
layer of the interfaces is Up
l Configuring basic VPLS functions
l Creating the VSI
NOTE
For details about creating the VSI, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide
- VPN.
Data Preparation
To configure IGMP snooping for a VSI, you need the following data.
No. Data
1 Name of the VSI enabled with IGMP snooping
2 ACL rules that the multicast policy is applied to
3 Source IP address of the IGMP General Query message
4 Parameters of the querier, including the interval for sending the IGMP General Query
message, the robustness variable, the maximum response time, and the interval for
sending the Last Member Query message
3.2.2 Configuring Basic IGMP Snooping Functions for a VSI
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:
igmp-snooping enable
IGMP snooping is enabled on the router. By default, IGMP snooping is disabled on the router.
Step 3 Run:
vsi vsi-name
The VSI view is displayed.

l2-multicast forwarding-mode { mac | ip }
The forwarding mode is configured. By default, the forwarding mode is based on the IP address.
You are recommended to use the default values. The LPUB supports only the forwarding based
on MAC addresses.
Step 5 Run:
IGMP snooping is enabled in the VPLS network. By default, IGMP snooping is disabled in the
VPLS network.
Step 6 Run:
igmp-snooping version { 1 | 2 | 3 }
The version of IGMP packets that can be processed is configured for the router enabled with
IGMP snooping. By default, the versions of IGMP packets that can be processed through IGMP
snooping of the router is IGMPv2.
The versions of IGMP packets that can be processed through IGMP snooping of the router are
IGMPv1, IGMPv2 or IGMPv3
To enable IGMP snooping for multiple VSIs, you can perform Step 3 to Step 6 repeatedly as
required.
----End
3.2.3 Configuring a Static Router Port for a VSI

Context
In a network with stable topology, you can configure the PWs and sub-interfaces on the router
as static router ports.
Procedure
l Configuring a PW as a Static Router Port
1. Run:
system-view


2. Run:
vsi vsi-name

3. Run:
igmp-snooping static-router-port remote-peer ip-address [ negotiation-vc-
id vc-id ]
The PW is configured as a static router port. The statically configured router port does
not age and can only be deleted by using commands.
When the LDP is used as the signaling negotiation protocol for a PW, you can use the
igmp-snooping static-router-port remote-peer ip-address [ negotiation-vc-id vc-
id ] command to configure the PW as a static router port in the VSI. If no IP address
is assigned to the remote peer, you can also configure the PW as a static router port
in the VSI. The configuration, however, takes effect only after an IP address is assigned
to the remote peer.
l Adding a Sub-interface to the Static Router Port
1. Run:
system-view

2. Run:
interface interface-type interface-number.subnumber
The Ethernet sub-interface view is displayed.
The static routing interfaces support the following sub-interfaces:
– Common sub-interface
– Dot1q termination sub-interfaces
– QinQ termination sub-interfaces
For configuration of sub-interfaces, refer to the HUAWEI NetEngine80E/40E Router

Configuration Guide - LAN Access and WAN Access.
3. Run:
l2 binding vsi vsi-name
The Ethernet sub-interface is bound to a VSI.

4. Run:
igmp-snooping static-router-port vsi vsi-name
The interface is configured as a static route port.
----End
3.2.4 Configuring the Dynamic Learning of Router Ports for a VSI
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:
vsi vsi-name

Step 3 Run:
igmp-snooping router-learning
The dynamic learning of router ports is enabled. By default, the dynamic learning of router ports
is enabled.
igmp-snooping router-aging-time router-aging-time
The default aging time of the routing interface learnt from IGMP packets is 180 seconds. The
default aging time of the routing interface learnt from PIM Hello packets is the Holdtime carried
in PIM Hello packets.
An aging time is set for the router port. If the router port does not receive the IGMP Query
message with the source address not being 0.0.0.0 or the PIM Hello message within the aging
time, the router considers the router port as an invalid port.
----End
3.2.5 Configuring the IGMP Snooping Querier for a VSI

Context
To save the bandwidth between an upstream multicast router and the local router, you need to
configure the IGMP snooping querier on the local router. The querier replaces the upstream
router to send IGMP Query messages.
Procedure
Step 1 Run:
system-view

igmp-snooping send-query enable
The router is enabled to send the IGMP General Query message with the source address not
being 0.0.0.0.
routers can swiftly update the outbound port information and the multicast data received by user
hosts is not interrupted when the topology changes because of a link fault.

igmp-snooping send-query source-address ip-address
The source address of the IGMP General Query message is configured.
By default, the source address is 192.168.0.1. When 192.168.0.1 is used by other devices in the
network, you can run the igmp-snooping send-query source-address command to change the
source IP address of the IGMP General Query message sent by the IGMP snooping module.
Step 4 Run:
vsi vsi-name
Step 5 Run:
igmp-snooping querier enable
The IGMP snooping querier is enabled.
----End
3.2.6 Configuring Parameters for the IGMP Snooping Querier for a

VSI
Context
Steps 3 to 8 are optional and can be selected as required. The default values are recommended
in most cases.
NOTE
For details of parameters of the querier, refer to the chapter "IGMP Configuration."
Procedure
Step 1 Run:
system-view
Step 2 Run:
vsi vsi-name
Step 3 Run:
igmp-snooping query-interval query-interval
The interval for the querier to send IGMP General Query messages is set.
Step 4 Run:
igmp-snooping robust-count robust-count
The robustness variable of the querier is set.
Step 5 Run:
igmp-snooping max-response-time max-response-time

The maximum response time of the querier is set.

Step 6 Run:
igmp-snooping lastmember-queryinterval lastmember-queryinterval
The interval for the querier to send the Last Member Query message is set.
Step 7 Run:
igmp-snooping require-router-alert
The router is configured to receive IGMP packets that must contain the Router Alert option in
the IP header. The router does not process the packet but discard the packet directly.
Step 8 Run:
igmp-snooping send-router-alert
The router is configured to contain the RouterAlert option in the IP header of the sent IGMP
packets.
----End
3.2.7 Configuring the Multicast Policy for a VSI

Context
NOTE
l To specify the range of multicast groups that hosts in a certain VSI can access, you can configure the
multicast policy for the VSI.
l After the multicast policy is configured, hosts in the VSI cannot join multicast groups that are not that
are not in the range specified by the policy.
Procedure
l Configuring the Multicast Group Policy
1. Run:
system-view

2. Run:
vsi vsi-name

3. Run:
igmp-snooping group-policy acl-number [ version number ]
The multicast group policy is configured for the VSI. In this manner, ports in the VSI
can only dynamically join the multicast group matching ACL rules. By default, no
multicast group policy is configured for the VSI.
4. Run:
quit
Return to the system view.

5. Run:

interface { ethernet | gigabitethernet |eth-trunk } interface-

number.subnumber
The sub-interface view for a VSI is displayed.

6. Run:
igmp-snooping group-policy acl-number [ version number ] { vlan vlan-id1
[ to vlan-id2 ] | qinq pe-vid pe-vid ce-vid ce-id1 [ to ce-id2 ] |
dot1q vid vid1 [ to vid2 ] }
The multicast group policy is configured for the sub-interface. By default, no multicast
group policy is configured for the sub-interface.
l Configuring the SSM Group Policy
1. Run:
system-view

2. Run:
vsi vsi-name

3. Run:
igmp-snooping ssm-policy basic-acl-number
The SSM group policy is configured. By default, the SSM group policy ranges from
232.0.0.0 to 232.255.255.255.
----End
3.2.8 Configuring Prompt Leave for Ports for a VSI
Context
After prompt leave is enabled for IGMP snooping, the router deletes a port from the forwarding
table without waiting for the Report message when receiving the Leave message from the port.
Therefore, the aging timer need not be enabled.
Prompt leave is applied when only one host is connected to the port. In addition, prompt leave
for the port takes effect only when IGMPv2 packets can be processed in the VSI.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vsi vsi-name
Step 3 Run:
igmp-snooping prompt-leave [ group-policy acl-number ]

Prompt leave is configured for ports in the VSI. By default, ports are not allowed to promptly
leave a multicast group.
group-policy acl-number specifies the range of multicast groups that ports can promptly leave.
If no group-policy acl-number is specified, ports promptly leave a multicast group after the
router receives the Leave message from the VSI.
----End
3.2.9 Configuring IGMP Proxy for a VSI

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
vsi vsi-name

Step 3 Run:
igmp-snooping proxy
IGMP proxy is enabled.

Step 4 Run:
igmp-snooping proxy querier-disable
The querier function of IGMP proxy is disabled in the VSI.

IGMP proxy provides two functions: querier and message suppression. Through the querier
function, a switch can replace the upstream router to send IGMP Query messages; through the
message suppression function, the switch can replace the upstream router to receive IGMP
Report and Leave messages. Therefore, after IGMP proxy is enabled on the local router,
bandwidth of the link between the upstream router and local router can be saved.
----End
3.2.10 Configuring the IGMP Fast Join Function for a VSI
Context
When the router receives IGMP Report messages from a multicast group, it needs to apply for
resources for the multicast group before generating the forwarding entry, which slows down the
speed at which a member joins a multicast group.
After the fast join function is enabled through the l2-multicast fast-channel command, the
router applies for resources for multicast groups in advance. When the router receives IGMP
Report messages from a multicast group, it can immediately generate the forwarding entry for

the multicast group, thus improving the speed at which the member joins a multicast group and
reducing the response delay of the router.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vsi vsi-name

Step 3 Run:
l2-multicast fast-channel { source-address source-address { mask | mask-length } |
group-address group-address { mask | mask-length } }
A member promptly joins a specific multicast group.
----End

Prerequisite
The configurations of the IGMP Snooping for a VSI function are complete.
Procedure
l Run the display igmp-snooping [vsi [ vsi-name ] ] [ configuration ] command to check
all parameters of IGMP Snooping in the VSI.
l Run the display igmp-snooping router-port { vlan vlan-id | vsi vsi-name } command to
check the information in the router interface.
l Run the display l2-multicast forwarding-mode vsi vsi-name command to check the
forwarding mode for a VSI.
l Run the display l2-multicast forwarding-table vsi vsi-name [ group-address group-
address [ source-address source-address ] | [ | count ] [ | { begin | include | exclude }
regular-expression ] ] command to check the Layer 2 multicast forwarding table.
----End
Example
Run the display igmp-snooping vsi vsi-name configuration command. If the IGMP snooping
parameters configured for the VSI are displayed, it means that the configuration succeeds.
<HUAWEI> display igmp-snooping vsi v123 configuration
IGMP Snooping Configuration for Vsi v123
igmp-snooping version 1
igmp-snooping query-interval 200
igmp-snooping router-aging-time 300

Run the display l2-multicast forwarding-mode vsi command. If the Layer 2 multicast
forwarding mode of all VSIs is displayed, it means that the configuration succeeds.
<HUAWEI> display l2-multicast forwarding-mode vsi
VSI Fowarding-mode
-----------------------------------------------
Vsi1 IP
Run the display l2-multicast forwarding-table vsi vsi-name command. If the Layer 2 multicast
forwarding mode of the VSI is displayed, it means that the configuration succeeds.
<HUAWEI> display l2-multicast forwarding-table vsi vsi123
VSI Name : vsi123, Forwarding Mode : IP,
-------------------------------------------------------------------,
(Source, Group) Status Age Index Port-cnt,
--------------------------------------------------------------------,
Router-port Ok No 0 1 ,
(192.168.0.7, 232.0.0.1) Ok No 1 2 ,
--------------------------------------------------------------------,
Total Entry(s) : 2
3.3 Configuring IGMP Snooping for a VLAN

This section describes how to configure IGMP snooping for a VLAN.

3.3.2 Enable IGMP Snooping for a VLAN
3.3.3 Configuring a Static Router Port for a VLAN
3.3.4 Configuring the Dynamic Learning of Router Ports in the VLAN
3.3.5 Configuring the IGMP Snooping Querier for a VLAN
3.3.6 Configuring Parameters of the IGMP Snooping Querier for a VLAN
3.3.7 Configuring the Multicast Policy for a VLAN
3.3.8 Configuring Prompt Leave for Ports in a VLAN
3.3.9 Configuring IGMP Proxy for a VLAN
3.3.10 Configuring the IGMP Fast Join Function for a VLAN

NOTE
For the VLAN bound to a VSI, you need to enable IGMP snooping in the VSI view.
IGMP snooping for a VLAN runs on Layer 2 of routers. In the implementation of Layer 2
multicast, IGMP snooping manages and controls the forwarding of multicast packets by
maintaining information about the outbound port of multicast packets. It maintains the outbound
port information by detecting the multicast protocol packets exchanged between the upstream
router and hosts.
In the network, functions related to IGMP snooping are as follows:

l Static router port: When the network topology is stable, you can configure router ports on
the router as static router ports.
l Static member port: If hosts connected to a certain port need to receive the multicast traffic
of a certain multicast group for a long time, you can add the port to the multicast group. In
this manner, the port becomes a static member port.
l IGMP snooping querier: To save the bandwidth between the upstream router and the local
router, you can configure the querier on the local router. The querier replaces the upstream
router to send IGMP Query messages. You can also configure parameters for the IGMP
snooping querier based on different networking requirements
l Multicast policy: You can configure the multicast policy for a VLAN, when you need to
specify the range of multicast groups that hosts in a certain VLAN can access.
l Rapid response to changes in the Layer 2 link: When the Layer 2 link changes, the router
must rapidly update information about the ports so that the multicast traffic can be
forwarded without interruptions.
l After the igmp-snooping send-query enable command is used, the router sends the IGMP
General Query message with source IP address being not 0.0.0.0 when Layer 2 links change.
The port link change event is received by the ports in the VLAN.
l For the MSTP port link change event, the Query message is sent to all non-router ports in
the VLAN.
l For the RRPP and RPR port link change events, the Query message is sent to only the ports
that receive the event.
l Prompt leave: When only one host exists for all ports in a VLAN, you can configure prompt
leave for the ports to save the network bandwidth.
l Suppression for IGMP messages: After the igmp-snooping proxy command is used, IGMP
proxy provides two functions: querier and message suppression. Through the querier
function, a switch can replace the upstream router to send IGMP Query messages; through
the message suppression function, the switch can replace the upstream router to receive
IGMP Report and Leave messages. Therefore, after IGMP proxy is enabled on the local
router, bandwidth of the link between the upstream router and local router can be saved.
Before configuring IGMP snooping for a VLAN, complete the following tasks:
l Creating a VLAN
l Adding ports to the VLAN
Data Preparation
To configure IGMP snooping for a VLAN, you need the following data.
No. Data
1 ID of the VLAN to be enabled with IGMP snooping
2 ACL rules that the multicast policy is applied to
3 Source IP address of the IGMP General Query message

No. Data
4 Parameters of the querier, including the interval for sending the IGMP General Query
message, the robustness variable, the maximum response time, and the interval for
sending the Last Member Query message
3.3.2 Enable IGMP Snooping for a VLAN
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
IGMP snooping is enabled on the router. By default, IGMP snooping is disabled on the router.
Step 3 Run:
vlan vlan-id
The VLAN view is displayed.
Step 4 (Optional)Run:
l2-multicast forwarding-mode { mac | ip }
The forwarding mode is configured for static Layer 2 multicast. By default, the forwarding mode
is based on the IP address.
You are recommended to use the default values. The LPUB supports only the forwarding based
on MAC addresses.
Step 5 Run:
IGMP snooping is enabled for the VLAN. By default, IGMP snooping is disabled for the VLAN.
Step 6 Run:
The version of IGMP packets that can be processed is configured for the router enabled with
IGMP snooping. By default, the version of IGMP packets that can be processed through IGMP
snooping of the router is IGMPv2.
The versions of IGMP packets that can be processed through IGMP snooping of the router are
IGMPv1, IGMPv2 or IGMPv3

To enable IGMP snooping for multiple VLANs, you can perform Step 3 to Step 6 repeatedly as
required.
----End
3.3.3 Configuring a Static Router Port for a VLAN
Context
Procedure
Step 1 Run:
system-view
Step 2 Perform the following as required.

l Run:
The view of the Ethernet interface connected to the router or the virtual Ethernet interface is
displayed.
l Run:
interface eth-trunk trunk-id
The view of the Ethernet trunk interface connected to the router is displayed.
Step 3 Run:
portswitch
The interface is switched to a Layer 2 port.
Step 4 Run:
igmp-snooping static-router-port vlan vlan-id
The interface in the VLAN is configured as a static router port. The statically configured router
port does not age and can only be deleted by using commands.
Before using the igmp-snooping static-router-port command, ensure that the interface is added
to the VLAN specified by vlan-id; otherwise, the configuration fails. If the VLAN that the current
interface belongs to is bound to a VSI, you can configure the current interface as a router port
in the VSI.
----End
3.3.4 Configuring the Dynamic Learning of Router Ports in the

VLAN
Context

Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
igmp-snooping router-learning
The dynamic learning of router ports is enabled.
By default, the dynamic learning of router ports is enabled.
Step 4 Run:
igmp-snooping router-aging-time router-aging-time
The default aging time of the routing interface learnt from IGMP packets is 180 seconds. The
default aging time of the routing interface learnt from PIM Hello packets is the Holdtime carried
in PIM Hello packets.
An aging time is set for the router port. If the router port does not receive the IGMP Query
message with the source address not being 0.0.0.0 or the PIM Hello message before the aging
time, the router considers the router port as invalid.
----End
3.3.5 Configuring the IGMP Snooping Querier for a VLAN
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The router is enabled to send the IGMP General Query message with the source address not
being 0.0.0.0.

igmp-snooping send-query source-address ip-address
The source address of the IGMP General Query message is configured.

By default, the source address is 192.168.0.1. When 192.168.0.1 is used by other devices in the
network, you can run the igmp-snooping send-query source-address command to change the
source IP address of the IGMP General Query message.
Step 4 Run:
vlan vlan-id
Step 5 Run:
The IGMP snooping querier is enabled.
----End
3.3.6 Configuring Parameters of the IGMP Snooping Querier for a

VLAN
Context
Steps 3 to 8 are optional and can be selected as required.
NOTE
For details of parameters of the querier, refer to the chapter "IGMP Configuration."
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
igmp-snooping query-interval query-interval
The interval for the querier to send IGMP General Query messages is set.
Step 4 Run:
igmp-snooping robust-count robust-count
The robustness variable of the querier is set.
Step 5 Run:
igmp-snooping max-response-time max-response-time
The maximum response time of the querier is set.
Step 6 Run:
igmp-snooping lastmember-queryinterval lastmember-queryinterval

The interval for the querier to send the Last Member Query message is set.
Step 7 Run:
igmp-snooping require-router-alert
The router is configured to receive IGMP packets that must contain the Router Alert option in
the IP header. The router does not process the packet but discard the packet directly.
Step 8 Run:
igmp-snooping send-router-alert
The router is configured to contain the Router Alert option in the IP header of the sent IGMP
packets. You can run the undo igmp-snooping send-router-alert command to set the IP header
of the sent IGMP packet not to contain the Router-Alert option.
----End
3.3.7 Configuring the Multicast Policy for a VLAN
Context
NOTE
l To specify the range of multicast groups that hosts in a certain VLAN can access, you can configure
the multicast policy for the VLAN.
l After the multicast policy is configured, hosts in the VLAN cannot join multicast groups that are not
specified in the policy.
Procedure
l Configuring the Multicast Group Policy
1. Run:
system-view

2. Run:
vlan vlan-id

3. Run:
igmp-snooping group-policy acl-number [ version number ]
The multicast group policy is configured for the VLAN. After that, ports in the VLAN
can only dynamically join the multicast group matching ACL rules.
4. Run:
quit
Return to the system view.

5. Run:
interface { ethernet | gigabitethernet |eth-trunk } interface-number
The interface view for a VLAN is displayed.

6. Run:

igmp-snooping group-policy acl-number [ version number ] { vlan vlan-id1

[ to vlan-id2 ] }
The multicast group policy is configured for the interface. By default, no multicast
group policy is configured for the interface.
l Configuring the SSM Group Policy
1. Run:
system-view

2. Run:
vlan vlan-id

3. Run:
The SSM group policy is configured.
By default, the SSM group policy ranges from 232.0.0.0 to 232.255.255.255.
----End
3.3.8 Configuring Prompt Leave for Ports in a VLAN
Context
When only one host exists for all ports in a VLAN, you can configure prompt leave for the ports
to save the network bandwidth. In addition, prompt leave for the ports takes effect only when
IGMPv2 packets can be processed in the VLAN.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
igmp-snooping prompt-leave [ group-policy acl-number ]
Prompt leave is configured for the port. By default, ports are not allowed to promptly leave a
multicast group.
group-policy acl-number specifies the range of multicast groups that ports can promptly leave.
If no group-policy acl-number is specified, the port promptly leaves a multicast group after
receiving the Leave message from a member port in a VLAN.
----End

3.3.9 Configuring IGMP Proxy for a VLAN

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id

Step 3 Run:
igmp-snooping proxy
IGMP proxy is enabled.

Step 4 Run:
The querier function of IGMP proxy is disabled in the VSI.

IGMP proxy provides two functions: querier and message suppression. Through the querier
function, a switch can replace the upstream router to send IGMP Query messages; through the
message suppression function, the switch can replace the upstream router to receive IGMP
Report and Leave messages. Therefore, after IGMP proxy is enabled on the local router,
bandwidth of the link between the upstream router and local router can be saved.
----End
3.3.10 Configuring the IGMP Fast Join Function for a VLAN
Context
When the router receives IGMP Report messages from a multicast group, it needs to apply for
resources for the multicast group before generating the forwarding entry, which slows down the
speed at which a member is added to a multicast group.
After the fast join function is enabled through the l2-multicast fast-channel command, the
router applies for resources for multicast groups in advance. When the router receives IGMP
Report messages from a multicast group, it can immediately generate the forwarding entry for
the multicast group, thus improving the speed at which the member joins a multicast group and
reducing the response delay of the router.
Procedure
Step 1 Run:

system-view

Step 2 Run:
vlan vlan-id
The multicast VLAN view is displayed.

Step 3 Run:
l2-multicast fast-channel { source-address source-address { mask | mask-length } |
group-address group-address { mask | mask-length } }
A member promptly joins a specific multicast group.
----End

Prerequisite
The configurations of the IGMP Snooping for a VLAN function are complete.
Procedure
l Run the display igmp-snooping [ vlan [ vlan-id ] ] [ configuration ] command to check
the parameters of IGMP snooping for a VLAN.
l Run the display igmp-snooping router-port vlan vlan-id command to check information
about the router port.
l Run the display l2-multicast forwarding-mode vlan [ vlan-id ] command to check the
forwarding mode for a VLAN.
l Run the display l2-multicast forwarding-table { vlan vlan-id | vsi vsi-name} [ group-
address group-address [ source-address source-address ] | [ | count ] [ | { begin |
include | exclude } regular-expression ] ] command to check the layer 2 multicast
forwarding table.
l Run the display igmp-snooping port-info [ vlan vlan-id [ group-address group-
address ] ] [ verbose ] command to check information about ports in a VLAN.
----End
Example
# Check all configurations of IGMP snooping for VLAN 10.
<HUAWEI> display igmp-snooping vlan 10 configuration
IGMP Snooping Configuration for Vlan 10
igmp-snooping lastmember-queryinterval 5
igmp-snooping max-response-time 6
igmp-snooping group-policy 2001 2
# In VLAN 10,run the display igmp-snooping port-info [ vlan vlan-id [ group-address group-
address ] ] [ verbose ] to check information about the outbound port that joins multicast group
225.1.1.1.
<HUAWEI> display igmp-snooping port-info
-----------------------------------------------------------------------
(Source, Group) Port Flag

-----------------------------------------------------------------------
VLAN 10, 3 Entry(s)
(10.1.1.2, 224.1.1.1) GE1/0/1 --M
1 port(s)
(10.1.1.3, 224.1.1.1) GE1/0/1 --M
1 port(s)
(10.1.1.4, 224.1.1.1) GE1/0/1 --M
1 port(s)
-----------------------------------------------------------------------
# Check the Layer 2 forwarding mode of VLAN 10.

<HUAWEI> display l2-multicast forwarding-mode vlan 10
VLAN Fowarding-mode
-----------------------------------------------
10 IP
3.4 Configuring Trunk Load Balancing for Layer 2 Multicast

This section describes how to configure trunk load balancing for Layer 2 multicast.
3.4.2 Configuring VLAN-based Trunk Load Balancing for Layer 2 Multicast
3.4.3 Configuring VSI-based Trunk Load Balancing for Layer 2 Multicast
In the scenario where IGMP snooping is not enabled in the VLAN or VSI, multicast traffic needs
to be load balanced among trunk member interfaces.
Trunk load balancing for Layer 2 multicast is applicable to the following networkings:
l VLAN, VPLS, H-VPLS

l Sub-interface for QinQ VLAN tag termination accessing the VPLS
l IGMP snooping enabled in different VLANs or VSIs
Before configuring trunk load balancing for Layer 2 multicast, complete the following tasks:
l Connecting interfaces and configuring physical parameters of the interfaces to ensure that
the physical status of the interfaces is Up
l Creating a VLAN
l Creating a VSI
Data Preparation
To configure trunk load balancing for Layer 2 multicast, you need the following data.

No. Data
1 ID of the VLAN to be configured with trunk load balancing for Layer 2 multicast
2 Name of the VSI to be configured with trunk load balancing for Layer 2 multicast
3.4.2 Configuring VLAN-based Trunk Load Balancing for Layer 2

Multicast
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id

Step 3 Run:
trunk multicast load-balance enable
VLAN-based trunk load balancing is enabled for Layer 2 multicast.
----End
3.4.3 Configuring VSI-based Trunk Load Balancing for Layer 2

Multicast
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
vsi vsi-name [ auto | static ]

Step 3 Run:
trunk multicast load-balance enable
VSI-based trunk load balancing is enabled for Layer 2 multicast.
----End

Prerequisite
Configurations about VLAN-based or VSI-based trunk load balancing for Layer 2 multicast are
complete.
Procedure
Step 1 Run the display interface [ interface-type [ interface-number ] ] [ | { begin | exclude |
include } regular-expression ] command to check the number of multicast packets received or
sent on each trunk member interface.
----End
Example
Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ]
command, and you can view configurations about Eth-Trunk 1 in the VLAN. For example:
<HUAWEI> display eth-trunk 1
Eth-Trunk1's state information is:
WorkingMode: NORMAL Hash arithmetic: According to flow
Least Active-linknumber: 1 Max Bandwidth-affected-linknumber: 16
Operate status: up Number Of Up Port In Trunk: 2
--------------------------------------------------------------------------------
PortName Status Weight
GigabitEthernet4/0/0 Up 1
GigabitEthernet4/0/5 Up 1
Run the display interface [ interface-type [ interface-number ] ] [ | { begin | exclude |

include } regular-expression ] command, and you can find that all member interfaces of Eth-
Trunk 1 in the VLAN have statistics about multicast traffic, that is, they share the forwarding
of multicast traffic. For example:
<HUAWEI> display interface GigabitEthernet 4/0/0
GigabitEthernet4/0/0 current state : UP
Line protocol current state : DOWN
Description: GigabitEthernet4/0/0 Interface
Route Port,The Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc8b-93fa
The Vendor Name is FINISAR CORP. , The Vendor PN is FTLF8519P2BNL-HW
Transceiver BW: 1G, Transceiver Mode: Multi Mode
WaveLength: 850nm, Transmission Distance: 500m
Rx Optical Power: NaNdBm, Tx Optical Power: NaNdBm
Loopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive
Enable and Send Enable
Last physical up time : -
Last physical down time : 2009-03-28 12:33:13
Statistics last cleared:2009-03-28 12:33:31
Last 300 seconds input rate: 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bits/sec, 0 packets/sec
Input: 0 bytes, 0 packets
Output: 1260258 bytes, 12327 packets
Input:

Unicast: 0 packets, Multicast: 0 packets

Broadcast: 0 packets, JumboOctets: 0 packets
CRC: 0 packets, Symbol: 0 packets
Overrun: 0 packets, InRangeLength: 0 packets
LongPacket: 0 packets, Jabber: 0 packets, Alignment: 0 packets
Fragment: 0 packets, Undersized Frame: 0 packets
RxPause: 0 packets
Output:
Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets
System: 0 packets, Overruns: 0 packets
TxPause: 0 packets
Unknown Vlan: 0 packets
<HUAWEI> display interface GigabitEthernet 4/0/5
GigabitEthernet4/0/5 current state : UP
Line protocol current state : DOWN
Description: GigabitEthernet4/0/5 Interface
Route Port,The Maximum Transmit Unit is 1500
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc8b-93ff
The Vendor Name is AGILENT , The Vendor PN is HFCT-5710L
Transceiver BW: 1G, Transceiver Mode: Single Mode
WaveLength: 1310nm, Transmission Distance: 10km
Loopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive
Enable and Send Enable
Last physical up time : -
Last physical down time : 2009-03-28 12:33:13
Statistics last cleared:2009-03-28 12:33:32
Last 300 seconds input rate: 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bits/sec, 0 packets/sec
Input: 0 bytes, 0 packets
Output: 9039146 bytes, 86932 packets
Input:
CRC: 0 packets, Symbol: 0 packets
Overrun: 0 packets, InRangeLength: 0 packets
LongPacket: 0 packets, Jabber: 0 packets, Alignment: 0 packets
Fragment: 0 packets, Undersized Frame: 0 packets
RxPause: 0 packets
Output:
Unicast: 0 packets, Multicast: 12327 packet
Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets
System: 0 packets, Overruns: 0 packets
TxPause: 0 packets
Unknown Vlan: 0 packets
3.5 Configuring Replication of the Multicast VLAN

This section describes how to configure replication of the multicast VLAN.

3.5.2 Configuring a Multicast VLAN
3.5.3 Adding an Interface to a VLAN
3.5.4 Configuring the Mapping Relationship Between the Multicast VLAN and the User VLAN
3.5.5 (Optional) Enabling the Querier Election for User VLANs

When hosts in different VLANs need to receive the same multicast traffic, you can configure
replication of the multicast VLAN. By configuring replication of the multicast VLAN, you can
manage and control the multicast source and the multicast group members. You can also reduce
wastes on the bandwidth.
In the implementation, VLANs are classified into the multicast VLAN and the user VLAN:
l A multicast VLAN is the VLAN that the interface connecting the router to the multicast
source belongs to. The multicast VLAN is used to converge the multicast traffic. The
router supports a maximum of 16 multicast VLANs.
l A user VLAN is the VLAN that member hosts of a multicast group belong to. The user
VLAN is used to receive the data from the multicast VLAN.
l You can bind multiple user VLANs to one multicast VLAN. A maximum of 512 user
VLANs can be bound to each multicast VLAN.
As shown in Figure 3-2, Router A is connected to Router B at the side of the multicast source.
It is required that Router A replicate the data flow from the multicast VLAN 10 to the user VLAN
100 and the user VLAN 200.
NOTE
As shown inFigure 3-2, Router A is equivalent to a Layer 2 switch.
Figure 3-2 Application on replication of the multicast VLAN
Source Router B
Internet/
Intranet
VLAN 10
Router A
VLAN100 VLAN200
Before configuring replication of the multicast VLAN, complete the following tasks:

status of the interfaces is Up
l Enabling IGMP snooping globally
l Creating a user VLAN and adding the interfaces that are connected to a switch to the user
VLAN as shown in Figure 3-2
Data Preparation
To configure replication of the multicast VLAN, you need the following data.
No. Data
1 ID of the multicast VLAN
2 ID of the user VLAN
3 Number of the interface

Context
Do as follows on Router A:
Procedure
Step 1 Run:
system-view

Step 2 Run:
The global IGMP snooping is enabled.

Step 3 Run:
vlan vlan-id

Step 4 Run:
IGMP snooping is enabled for the multicast VLAN.

Step 5 Run:
multicast-vlan enable
Replication of the multicast VLAN is enabled.

By default, replication of the multicast VLAN is not enabled.
----End

3.5.3 Adding an Interface to a VLAN
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The view of the specified interface is displayed.
Here, the interface refers to an interface that connects Router A to the upstream router.
Step 3 Run:
portswitch
The interface is changed to a Layer 2 port.

l Run:
port default vlan vlan-id
The port is added to a multicast VLAN in default mode.

l Run:
port trunk allow-pass vlan vlan-id
The port is added to a multicast VLAN in trunk mode.
----End
3.5.4 Configuring the Mapping Relationship Between the Multicast

VLAN and the User VLAN
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id

Step 3 Run:
multicast-vlan user-vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> }
The matching relationship between the multicast VLAN and the user VLAN is configured.
vlan-id1 and vlan-id2 are IDs of user VLANs.
One multicast VLAN can be mapped to multiple user VLANs, but one user VLAN can be
mapped to only one multicast VLAN.
----End
3.5.5 (Optional) Enabling the Querier Election for User VLANs

Context
To prevent hosts from receiving two multicast flows in the replication of inter-VLANs, you must
enable the querier election for user VLANs. If a user VLAN receives two Query messages that
have different source addresses, you need to enable the querier election to prohibit the upstream
routers from sending Query messages.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id

Step 3 Run:
multicast-vlan igmp-querier-election user-vlan { { vlan-id [ to vlan-id ] }
&<1-10> }
The querier election is enabled for user VLANs.
----End

Prerequisite
The configurations of the Replication of the Multicast VLAN function are complete.
Procedure
l Run the display user-vlan vlan [ vlan-id ] command to check the configuration on the user
VLAN.
l Run the display multicast-vlan vlan [ vlan-id ] command to check the configuration on
the multicast VLAN.
----End

Example
Run the display multicast-vlan vlan command. If you can view the IDs of all configured
multicast VLANs, the number of user VLANs mapped to the multicast VLAN, and the IGMP
snooping status of the multicast VLAN, it means that the configuration succeeds.
<HUAWEI> display multicast-vlan vlan
Total multicast vlan 2
multicast-vlan user-vlan snooping-state
--------------------------------------------------
2 1 Enable
80 0 Enable
Run the display user-vlan vlan command. If the configurations on all configured user VLANs
are displayed, it means that the configuration succeeds.
<HUAWEI> display user-vlan vlan
Total user vlan 6
user-vlan snooping-state multicast-vlan snooping-state
---------------------------------------------------------
3 Enable 2 Enable
223 Enable 222 Enable
3.6 Configuring 1+1 Protection of Multicast VLANs

This section describes how to configure the multicast 1+1 protection.

3.6.3 Configuring a Protection Group
3.6.4 Configuring the Delay for the Switchover of a Protection Group
3.6.5 Configuring the Recovery Mode and the WRT of a Protection Group
3.6.6 Configuring Fault Detection on the Working VLAN and the Protection VLAN
3.6.7 Configuring the Switchover Status of a Protection Group

To ensure the receiving of multicast traffic in a steady and effective manner, you can configure
1+1 protection of multicast VLANs.
As shown in Figure 3-3, Router A and Router B are Huawei devices. The Continuity Check
(CC) mechanism of the Ethernet Connectivity Fault Management (CFM) is applied to the two
devices.
NOTE
Router A and Router B can be a switch or router that supports the 1+1 protection of multicast VLANs.

On Router A, VLAN 3 is the multicast VLAN; VLAN 4 and VLAN 5 are user VLANs. On
Router B, VLAN 4 functions as a multicast VLAN; VLAN 100 and VLAN 200 function as its
user VLANs. VLAN 5 functions as the protection VLAN of VLAN 4. It is not required to
configure VLAN 5 as a multicast VLAN or enable IGMP snooping.
It is required that Router A should forward the traffic of the multicast VLAN 3 to user VLAN
4 and user VLAN 5. According to the detection results of the CCM, Router B selects the multicast
traffic from one of the two VLANs, and then forwards the valid multicast traffic to user VLAN
100 and user VLAN 200.
Figure 3-3 Application of 1+1 protection of multicast VLANs
DHCP Source
server
IP/MPLS
core
VLAN3
RouterA
VLAN4 VLAN5
CCM
VLAN4 VLAN5
RouterB
VLAN100 VLAN200
Multicast flow
CCM Data Flow
Multicast flow of the working VLAN
Multicast flow of the protection VLAN

Before configuring 1+1 protection of multicast VLANs, complete the following tasks:
l Configuring replication of the multicast VLAN
l Configuring the Ethernet OAM fault detection mechanism on Router A and Router B
Data Preparation
To configure 1+1 protection multicast VLANs, you need the following data.
No. Data
1 ID of the working VLAN and ID of the protection VLAN
2 Number of the interface that needs to be added to the VLAN
3 Name of the Maintenance Domain (MD) and the Maintenance Alliance (MA), and
number of the Remote Maintenance End Point (RMEP)
Context
Do as follows on Router A and Router B:
Procedure
Step 1 Run:
system-view
Step 2 Run:
IGMP snooping is enabled globally.
Step 3 Run:
vlan vlan-id
The first multicast VLAN is created. The value of vlan-id can be any integer that ranges from 1
to 4094.
Step 4 Run:
Step 5 Run:

Replication of the multicast VLAN is enabled.
----End
3.6.3 Configuring a Protection Group

Context
Do as follows on Router B:
Do not run the igmp-snooping enable command and the multicast-vlan enable command for
a protection VLAN.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id

Step 3 Run:
l2-multicast protection protect-vlan vlan-id
The protection VLAN is configured for the multicast VLAN.
----End
3.6.4 Configuring the Delay for the Switchover of a Protection

Group
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id
The working VLAN view is displayed.

Step 3 Run:
l2-multicast protection protect-vlan vlan-id hold-off milliseconds
The delay for the switchover of the protection group that the working VLAN belongs to is
configured.

By default, the switchover delay is 0.
----End
3.6.5 Configuring the Recovery Mode and the WRT of a Protection

Group
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id

Step 3 Run:
l2-multicast protection protect-vlan vlan-id restore { non-revertive | revertive
[ wtr minutes] }
The recovery mode and the Wait to Restore Time (WRT) of the protection group that the working
VLAN belongs to are configured.
By default, the protection group works in revertive mode and the WRT is 5 minutes.
----End
3.6.6 Configuring Fault Detection on the Working VLAN and the

Protection VLAN
Context
Do as follows on Router A and Router B:
NOTE
In the following commands, the name of the Maintenance Domain (MD) and the Maintenance Association
(MA), and the number of the Remote Maintenance End Point (RMEP) should be defined before the Ethernet
OAM detection mechanism is configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id

Step 3 Run:
l2-multicast protection oam-bind cfm md md-name ma ma-name remote-mep mep-id
The OAM fault detection mechanism is bound to the working VLAN.
Step 4 Run:
quit
Exit from the VLAN view.
Step 5 Run:
vlan vlan-id
The protection VLAN view is displayed.
Step 6 Run:
l2-multicast protection oam-bind cfm md md-name ma ma-name remote-mep mep-id
The OAM fault detection mechanism is bound to the protection VLAN.
----End
3.6.7 Configuring the Switchover Status of a Protection Group
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
l2-multicast protection switch { clear | lock | force | manual }
The switchover status of the protection group that the working VLAN belongs to is configured.
----End
Prerequisite
The configurations of the 1+1 Protection of Multicast VLANs function are complete.

Procedure
Step 1 Run the display l2-multicast protection vlan [ vlan-id ] command to check the configuration
on multicast VLAN 1+1 protection.
----End
Example
Run the display l2-multicast protection vlan command. If the configuration on multicast
VLAN 1+1 protection is displayed, it means that the configuration succeeds. For example:
<HUAWEI> display l2-multicast protection vlan
Total protection groups 1:
PG Main Prot Rest Wtr Hold Main Prot Proto FM Swith Group
indx vlan vlan mode time time stat stat enable Board cmd state
------------------------------------------------------------------------
0 2 3 Rev 5 0 OK OK Yes 3 none normal
3.7 Configuring Static Layer 2 Multicast

This section describes how to configure static Layer 2 multicast.

3.7.2 Configuring Static Layer 2 Multicast for a VSI
3.7.3 Configuring Static Layer 2 Multicast for a VLAN

In the metro Ethernet, when hosts attached to the Digital Subscriber Line Access Multiplexer
(DSLAM) need to receive the multicast traffic of a certain group for a long time, the multicast
traffic should be directly sent to the DSLAM. After static Layer 2 multicast is configured, the
hosts can receive the multicast traffic of the registered multicast group in a steady and timely
manner for a long time. In addition, attacks of network protocols can be avoided. In a VPLS
network, you need to configure static Layer 2 multicast on the Underlayer Provider Edge (UPE)
device and the PE-Aggregation (PE-AGG) device.
Before configuring static Layer 2 multicast, complete the following tasks:
l Configuring basic VPLS functions
l Enabling IGMP snooping globally
Data Preparation
To configure static Layer 2 multicast, you need the following data.

No. Data
1 IP address of the multicast group that hosts join statically
2 Pseudo Wire (PW), sub-interface, and interface of the multicast group that hosts join
statically
3.7.2 Configuring Static Layer 2 Multicast for a VSI

Context
NOTE
l A sub-interface not bound to a VSI cannot be added to a static multicast group. In addition, when the
binding relationship between the sub-interface and the VSI is configured, the configurations of all static
multicast groups and router ports on the sub-interface are deleted.
l One sub-interface can be added to only one VSI. In addition, one sub-interface can be configured with
multiple static groups in only one VSI.
Procedure
l Adding a PW to a Static Layer 2 Multicast Group
1. Run:
system-view

2. Run:
vsi vsi-name

3. Run:
l2-multicast static-group [ source source-ip-address ] group-address
group-address remote-peer ip-address [ negotiation-vc-id vc-id ]
A PW is added to a Layer 2 multicast group in the VSI statically.

When the Label Distribution Protocol (LDP) is used as the signaling negotiation
protocol for a PW, run the l2-multicast static-group [ source source-ip-address ]
group-address group-address remote-peer ip-address [ negotiation-vc-id vc-id ]
command. If no IP address is assigned to the remote peer, you can also add the PW
to the Layer 2 multicast group in the VSI. The configuration, however, takes effect
only after an IP address is assigned to the remote peer.
l Adding a Sub-interface to a Static Layer 2 Multicast Group
Do as follows on the router.

NOTE
l A sub-interface not bound to a VSI cannot be added to a static multicast group. In addition, when
the binding relationship between the sub-interface and the VSI is removed, the configurations of
all static multicast groups and router ports on the sub-interface are deleted.
l One sub-interface can be added to only one VSI. In addition, one sub-interface can be configured
with multiple static groups in only one VSI.
1. Run:
system-view

2. Run:
interface interface-type interface-number.subnumber
The sub-interface view is displayed.

The static routing interfaces support the following sub-interfaces:
– Common sub-interface
– Dot1q termination sub-interfaces
– QinQ termination sub-interfaces
For configuration of sub-interfaces, refer to the HUAWEI NetEngine80E/40E Router

Configuration Guide - LAN Access and WAN Access.
3. Run:
l2 binding vsi vsi-name
The Ethernet sub-interface is bound to a VSI.

4. Run:
l2-multicast static-group { [ source source-ip-address ] | group-address
group-address } vsi vsi-name
The sub-interface is added to a Layer 2 multicast group in the VSI statically.

----End
3.7.3 Configuring Static Layer 2 Multicast for a VLAN

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
vlan vlan-id
The VLAN is created.

Step 3 Run:

The IGMP snooping function is enabled

Step 4 Run:
The version of IGMP Snooping is configured

Step 5 Run:
quit
Exit from the VLAN view.

l Run:
The Ethernet interface view is displayed.

l Run:
interface eth-trunk trunk-id
The Ethernet trunk interface view is displayed.

The interface should be connected to the host that is added to the multicast group statically.
Step 7 Run:
portswitch
The interface is changed to a Layer 2 port.

l Run:
port default vlan vlan-id
The port is added to a VLAN in default mode.

l Run:
port trunk allow-pass vlan vlan-id
The port is added to a VLAN in trunk mode.

Step 9 Run:
l2-multicast static-group { source source-ip-address | group-address group-
address } vlan { { vlan-id1 [ to vlan-id2 ] } & <1-10> }
An interface in the VLAN is added to the multicast group statically.
----End

Prerequisite
The configurations of the Static Layer 2 Multicast function are complete.
Procedure
Step 1 Run the display igmp-snooping port-info [ vlan vlan-id ] [ group-address group-address ] ]
[ verbose ] command to check information about ports on the router.
----End

Example
Run the display igmp-snooping port-info command. You can view whether the configuration
of the static multicast takes effect. If the bolded S is displayed, it indicates that the port is a static
router port. That means the configuration succeeds.
-----------------------------------------------------------------------
-----------------------------------------------------------------------
VLAN 10, 3 Entry(s)
(10.1.1.2, 224.1.1.1) GE1/0/1 S--
1 port(s)
(10.1.1.3, 224.1.1.1) GE1/0/1 S--
1 port(s)
(10.1.1.4, 224.1.1.1) GE1/0/1 S--
1 port(s)
-----------------------------------------------------------------------
3.8 Configuring the Network Management Function for

Layer 2 Multicast
This section describes how to configure the network management function for Layer 2 multicast.
3.8.1 Enabling the Alarm Function for Layer 2 Multicast

3.8.1 Enabling the Alarm Function for Layer 2 Multicast
Procedure
Step 1 Run:
system-view
Step 2 Run:
snmp-agent trap enable feature-name l2-multicast { non-excessive all | trap-name
trap-name }
The alarm function is enabled for Layer 2 multicast.
By default, the alarm function is disabled for Layer 2 multicast.
----End
Prerequisite
The configurations of the the Network Management Function for Layer 2 Multicast function are
complete.

Procedure
Step 1 Run the display current-configuration configuration | include l2-multicast command to
check the Layer 2 alarm function.
----End
Example
Run the display current-configuration configuration | include l2-multicast command. If the
bolded information as shown in the following output is displayed, it means that the configuration
succeeds.
<HUAWEI> display current-configuration configuration | include l2-multicast
snmp-agent trap enable l2-multicast
3.9 Configuring Layer 2 Multicast SSM Mapping

This section describes how to configure the Layer 2 multicast SSM mapping function.
3.9.2 (Optional) Configuring a Layer 2 Multicast SSM Policy
3.9.3 Configuring Layer 2 Multicast SSM Mapping
If a router connected with the host is configured with IGMPv3, SSM mapping is required for
the device to map the multicast group addresses of the received multicast packets with no source
addresses to specific sources.
Though the router enabled with IGMPv3 receives an IGMPv2 packet whose group address is
within the SSM group range, SSM mapping is still required to implement automatic source
mapping.
Before configuring Layer 2 multicast SSM mapping, complete the following tasks:
l Enabling global IGMP snooping
Data Preparation
To configure Layer 2 multicast SSM mapping, you need the following data.
No. Data
1 (Optional) ACL rule

No. Data
2 (Optional) SSM policy
3 Source addresses mapped to the multicast group address
3.9.2 (Optional) Configuring a Layer 2 Multicast SSM Policy
Context
If the specified multicast group address is in the ASM group address range, you are required to
configure an SSM policy on the router and add the multicast address to the SSM group address
range.
Do as follows on the router connected with the host:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
acl number basic-acl-number
The ACL view is displayed.

Step 4 Run:
rule permit source source-ip-address source-wildcard
A basic ACL rule is created.

rule deny source any
The multicast packet whose group address is beyond the range defined in the ACL rule is
discarded.
Step 6 Run:
vlan vlan-id

Step 7 Run:
The specified multicast address is specified to be in the SSM group address range.
----End

3.9.3 Configuring Layer 2 Multicast SSM Mapping
Context
Do as follows on the router connected with the host:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 (Optional)Run:
The version of IGMP Snooping is configured.
Step 4 Run:
vlan vlan-id
Step 5 Run:
Step 6 Run:
igmp-snooping ssm-mapping enable
SSM mapping is enabled for the multicast VLAN.
By default, SSM mapping is disabled for the multicast VPN.
Step 7 Run:
igmp-snooping ssm-mapping ip-group-address { ip-group-mask | mask-length } ip-
source-address
The multicast address in the specified range is mapped to the source address.
The specified multicast address must be within the SSM group address range.
----End
Prerequisite
Configurations about Layer 2 multicast SSM mapping are complete.

Procedure
l Run the display igmp-snooping port-info command to check entries on the interface.
----End
Example
Run the display igmp-snooping port-info command, and you can view entries on the
corresponding interface. For example:
-----------------------------------------------------------------------
-----------------------------------------------------------------------
VLAN 10, 3 Entry(s)
(10.1.1.2, 224.1.1.1) GE1/0/1 --M
1 port(s)
(10.1.1.3, 224.1.1.1) GE1/0/1 --M
1 port(s)
(10.1.1.4, 224.1.1.1) GE1/0/1 --M
1 port(s)
-----------------------------------------------------------------------
3.10 Configuring Layer 2 Multicast CAC for a VLAN, a Layer

2 Interface, or the Interface in a Specified VLAN
This section describes how to configure Layer 2 Multicast CAC for a VLAN, a Layer 2 Interface,
or the Interface in a Specified VLAN.
As shown in Figure 3-1, UPEs are connected with access devices (DSLAMs or switches)
through VLANs. IGMP snooping and multicast CAC are deployed on UPEs. Therefore, when
receiving IGMP Report messages, UPEs check the messages based on the configured CAC limit,
thereby controlling the number of IPTV channels or bandwidth of each channel requested by
the access devices attached to UPEs.
NOTE
You can choose to configure multicast CAC for a VLAN, a Layer 2 interface, or the interface in a specified
VLAN, or you can configure multicast CAC for all of them simultaneously.

3.10.2 Configuring Restriction on the Number of Multicast Group Members of a VLAN, a Layer
2 Interface, or the Interface in a Specified VLAN
3.10.3 Configuring Restriction on the Bandwidth of Multicast Groups of a VLAN, a Layer 2
Interface, or the Interface in a Specified VLAN
3.10.4 Configuring Restriction on the Number of Channels of a VLAN, a Layer 2 Interface, or
the Interface in a Specified VLAN
3.10.5 Configuring Restriction on the Bandwidth of Channels of a VLAN, a Layer 2 Interface,
or the Interface in a Specified VLAN
3.10.6 Configuring Channels for a VLAN


UPEs can work in either of the following scenarios to provide multicast services based on
VLANs:
l Static multicast groups are configured on NPEs and UPEs are configured to be queriers. In
this situation, UPEs do not process Query messages from NPEs. Instead, UPEs learn the
Report messages sent from the user side and generate corresponding multicast forwarding
entries.
NPEs send general Query messages periodically. If receiving no Report messages sent from
the user side, NPEs age the multicast forwarding entries at a certain interval. If receiving
Leave messages, NPEs send group-specific Query messages. You can also configure static
multicast groups on UPEs.
l IGMP snooping is enabled on UPEs. When receiving Query messages from NPEs, UPEs
forward the Query messages to all members of a VLAN. After receiving Report messages
from the user side, UPEs create corresponding multicast forwarding entries. If the later
received Query messages are from the same group and the corresponding multicast
forwarding entries do not reach the timeout period, UPEs directly send Report messages
to NPEs.
NOTE
In this section, the scenario where IGMP snooping is deployed on UPEs is described.
Before configuring Layer 2 multicast CAC for a VLAN, a Layer 2 interface, or the interface in
a specified VLAN, complete the following tasks:
l Connecting interfaces of the routers in the network correctly
l Configuring interfaces on the routers to ensure that the status of the link layer protocol
between the routers is Up
Data Preparation
To configure Layer 2 multicast CAC for a VLAN, a Layer 2 interface, or the interface in a
specified VLAN, you need the following data.
No. Data
1 Name of channels
2 Number of multicast groups
3 Bandwidth of multicast groups
4 Number of channels
5 Bandwidth of channels
6 ID of the VLAN or the type and number of the interface where Layer 2 multicast
CAC should be configured

3.10.2 Configuring Restriction on the Number of Multicast Group

Members of a VLAN, a Layer 2 Interface, or the Interface in a
Specified VLAN
Context
Do as follows on a UPE:
Procedure
Step 1 Run:
system-view
Step 2 Run:
l2-multicast limit max-entry count [ except acl-number ]
Restriction on the number of global multicast group members is configured.
Step 3 Run:
l2-multicast limit max-entry count vlan { { vlan-id [ to vlan-id ] } &<1-10> }
[ except acl-number ]
Restriction on the number of multicast group members is configured for a VLAN.
Step 4 Run:
The Ethernet interface view, Gigabit Ethernet interface view, or Eth-Trunk interface view is
displayed.
Step 5 Run:
portswitch
The Layer 3 interface is switched to a Layer 2 interface.
Step 6 Run:
l2-multicast limit max-entry count[ except acl-number ]
Restriction on the number of multicast group members is configured for the Layer 2 interface.
Step 7 Run:
l2-multicast limit max-entry count [ vlan { { vlan-id [ to vlan-id ] } &<1-10> } ]
Restriction on the number of multicast group members is configured for the interface in a
specified VLAN.
NOTE
The parameter except is used to exclude the multicast groups that need not be restricted.
----End

3.10.3 Configuring Restriction on the Bandwidth of Multicast

Groups of a VLAN, a Layer 2 Interface, or the Interface in a
Specified VLAN
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
l2-multicast limit bandwidth bandwidth
Restriction on the bandwidth of global multicast groups is configured.
Step 3 Run:
l2-multicast limit bandwidth bandwidth vlan { { vlan-id [ to vlan-id ] } &<1-10>
}
Restriction on the bandwidth of the multicast groups is configured for a VLAN.
Step 4 Run:
displayed.
Step 5 Run:
portswitch
Step 6 Run:
Restriction on the bandwidth of the multicast groups on the Layer 2 interface is configured.
Step 7 Run:
l2-multicast limit bandwidth bandwidth [ vlan { { vlan-id [ to vlan-id ] }
&<1-10> } ]
Restriction on the bandwidth of the multicast groups is configured for the interface in a specified
VLAN.
----End
3.10.4 Configuring Restriction on the Number of Channels of a

VLAN, a Layer 2 Interface, or the Interface in a Specified VLAN

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
l2-multicast limit channel channel-name { max-entry count } [ vlan { { vlan-id
[ to vlan-id ] } &<1-10> } ]
Restriction on the number of global channels or the number of channels in a VLAN is configured.
Step 3 Run:
displayed.
Step 4 Run:
portswitch

Step 5 Run:
l2-multicast limit channel channel-name { max-entry count }
Restriction on the number of channels is configured for the Layer 2 interface.

Step 6 Run:
l2-multicast limit channel channel-name { max-entry count } [ vlan { { vlan-id
[ to vlan-id ] } &<1-10> } ]
Restriction on the number of channels is configured for the interface in a specified VLAN.
----End
3.10.5 Configuring Restriction on the Bandwidth of Channels of a

VLAN, a Layer 2 Interface, or the Interface in a Specified VLAN
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
l2-multicast limit channel channel-name { bandwidth bandwidth } [ vlan { { vlan-id
[ to vlan-id ] } &<1-10> } ]

Restriction on the bandwidth of global channels or the bandwidth of the channels in a VLAN is
configured.
Step 3 Run:
displayed.
Step 4 Run:
portswitch
Step 5 Run:
l2-multicast limit channel channel-name { bandwidth bandwidth }
Restriction on the bandwidth of the channels is configured for the Layer 2 interface.
Step 6 Run:
l2-multicast limit channel channel-name { bandwidth bandwidth } [ vlan { { vlan-id
[ to vlan-id ] } &<1-10> } ]
Restriction on the bandwidth of the channels is configured for the interface in a specified VLAN.
----End
3.10.6 Configuring Channels for a VLAN
Context
Procedure
Step 1 Run:
system-view
Step 2 (Optional) Perform the following steps to configure global channels.

l To enter the global channel view, run the l2-multicast-channel command.
l To create a global channel and enter the channel view, run the channel channel-name
command.
l To configure member multicast groups in the global channel and set bandwidth for each
member multicast group, run the group group-address { group-mask-length | group-mask }
[ per-bandwidth bandwidth ] command. If the bandwidth is not configured, the value is 0.
Step 3 Run:
l2-multicast-channel vlan vlan-id
The VLAN channel view is displayed.
The VLAN specified in this command must not a VLAN that is bound to a VSI and must not
be a user VLAN or a protection VLAN. Otherwise, you cannot configure channels for the VLAN.

Step 4 Run:
channel channel-name [ type [ asm | ssm ] ]
A channel is set for the VLAN.
The name specified in this command must not be the same as the name of the global channel,
otherwise, the channel cannot be created for the VLAN.
Step 5 Run:
group group-address { group-mask-length | group-mask } [ per-bandwidth bandwidth ]
The member multicast groups of the channel in the VLAN are configured and bandwidth of each
member multicast group is set.
The addresses of member multicast groups in the global channel, the channels in a VLAN, and
the channels in a VSI cannot be the same.
Step 6 Run:
displayed.

unspecified-channel deny
The method for the channel in the VLAN to process the Join messages for an unknown member
multicast group is configured.
After this command is run, the Join messages for an unknown member multicast group are
denied; if the undo unspecified-channel deny command is run, the Join messages for an
unknown member multicast group are permitted.
----End
Prerequisite
The configurations of layer 2 Multicast CAC for a VLAN, a Layer 2 Interface, or the Interface
in a Specified VLAN function are complete.
Procedure
l Run the display l2-multicast limit configuration command to check configurations of
Layer 2 multicast CAC.
l Run the display l2-multicast limit configuration vlan [ vlanid ] command to check
configurations of Layer 2 multicast CAC for a VLAN.
l Run the display l2-multicast limit vlan [ vlanid ] [ channel channel-name ] command to
check configurations and statistics of restriction on the channels in a VLAN.
l Run the display l2-multicast limit interface interface-type interface-number command to
check configurations and statistics of Layer 2 multicast CAC for an interface.
l Run the display l2-multicast limit channel channel-name command to check
configurations and statistics of Layer 2 multicast CAC for a channel.

l Run the display l2-multicast-channel channel-name command to check configurations of

a channel.
----End
Example
Run the display l2-multicast limit configuration command to check configurations of Layer
2 multicast CAC.
<HUAWEI> display l2-multicast limit configuration
L2-multicast limit information, The unit of bandwidth is kbits/sec
---------------------------------------------------------------------
ConfigEntries ConfigBandwidth
CurrentEntries CurrentBandwidth
---------------------------------------------------------------------
Global limit information:
---------------------------------------------------------------------
100 2000
---- ----------
VLAN 20 limit information:
---------------------------------------------------------------------
50 1000
---- ----------
VLAN 20 channel limit information:
---------------------------------------------------------------------
bjtv 15 60
---- ----------
interface GigabitEthernet1/0/1 VLAN 10 channel limit information:
---------------------------------------------------------------------
cctv 20 300
---- ----------
Run the display l2-multicast-channel vlan 10 command to check configurations of the channel
in VLAN 10.
<HUAWEI> display l2-multicast-channel vlan 10
Channel information on VLAN 10
ChannelName GroupAddress Mask Bandwidth
---------------------------------------------------------------------
njtv 226.1.1.0 255.255.255.0 4
226.1.2.0 255.255.255.0 6
226.1.3.0 255.255.255.0 5
---------------------------------------------------------------------
njtv1 226.2.1.0 255.255.255.0 4
226.2.2.0 255.255.255.0 2
Run the display l2-multicast limit vlan 20 command to check configurations and statistics of
multicast CAC for the channels in VLAN 20.
<HUAWEI> display l2-multicast limit vlan 20
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
50 1000
0 0
---------------------------------------------------------------------
bjtv 15 60
0
Run the display l2-multicast limit vlan 10 command to check configurations and statistics of
multicast CAC on the interface in VLAN 10.

<HUAWEI> display l2-multicast limit vlan 10 interface gigabitethernet 1/0/1

---------------------------------------------------------------------
---------------------------------------------------------------------
interface GigabitEthernet1/0/1 VLAN 10 channel limit information:
---------------------------------------------------------------------
cctv 20 300
20 450
3.11 Configuring Layer 2 Multicast CAC for a VSI

This section describes how to configure Layer 2 Multicast CAC for a VSI.
3.11.2 Configuring Restriction on the Number of Multicast Group Members of a VSI
3.11.3 Configuring Restriction on the Bandwidth of Multicast Groups of a VSI
3.11.4 Configuring Restriction on the Number of Channels of a VSI
3.11.5 Configuring Restriction on the Bandwidth of Channels of a VSI
3.11.6 Configuring Channels for a VSI

In the scenario where UPEs provide Layer 2 multicast services through VSIs, you can deploy
Layer 2 multicast CAC on UPEs to restrict the number or bandwidth of multicast groups, thereby
saving network bandwidth and preventing unnecessary multicast data from occupying network
resources.
Before configuring Layer 2 multicast CAC for a VSI, complete the following tasks:
l Connecting interfaces of the routers in the network correctly
Data Preparation
To configure Layer 2 multicast CAC for a VSI, you need the following data.
No. Data
1 Name and ID of the VSI, and the interface to which the VSI is bound
2 Name of the channels created for the VSI

No. Data

Members of a VSI
Context
Procedure
Step 1 Run:
system-view

Restriction on the number of global multicast group members is configured.

Step 3 Run:
vsi vsi-name

Step 4 Run:
Restriction on the number of multicast group members is configured for a VSI. You can specify
the parameter except to exclude the multicast groups that need not be restricted.
----End

Groups of a VSI
Context
Procedure
Step 1 Run:
system-view


Restriction on the bandwidth of global multicast groups is configured.

Step 3 Run:
vsi vsi-name

Step 4 Run:
Restriction on the bandwidth of the multicast groups is configured for a VSI.
----End
3.11.4 Configuring Restriction on the Number of Channels of a VSI
Context
Procedure
Step 1 Run:
system-view

l2-multicast limit channel channel-name max-entry count
Restriction on the number of global channels is configured.

Step 3 Run:
vsi vsi-name

Step 4 Run:
Restriction on the number of channels is configured for a VSI.
----End

VSI
Context

Procedure
Step 1 Run:
system-view

l2-multicast limit channel channel-name bandwidth bandwidth
Restriction on the bandwidth of global channels is configured.

Step 3 Run:
vsi vsi-name

Step 4 Run:
Restriction on the bandwidth of the channels is configured for a VSI.
----End
3.11.6 Configuring Channels for a VSI
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
l2-multicast-channel vsi vsi-name
The VSI channel view is displayed.

The method for the channel in the VSI to process the Join messages for an unknown member
multicast group is configured.
After this command is run, the Join messages for an unknown member multicast group are
denied; if the unspecified-channel deny command is run, the Join messages for an unknown
member multicast group are permitted.
For the procedure for configuring a global channel, see "Configuring Channels for a
VLAN."
Step 4 Run:
channel channel-name [ type [ asm | ssm ] ]
A channel is configured for the VSI and the channel view is displayed.

The name specified in this command must not be the same as the name of the global channel,
otherwise, the channel cannot be created for the VSI.
Step 5 Run:
group group-address { group-mask-length | group-mask } [ per-bandwidth bandwidth ]
The member multicast groups in the channel are configured and the bandwidth of each member
multicast group is set.
If the bandwidth is not configured, the value is 0.
----End

Prerequisite
The configurations of layer 2 Multicast CAC for a VSI function are complete.
Procedure
l Run the display l2-multicast limit configuration vsi vsi-name command to check
configurations of Layer 2 multicast CAC for a VSI.
l Run the display l2-multicast limit vsi [ vsi-name ] [ channel channel-name ] command
to check configurations and statistics of restriction on the channels in a VSI.
a channel.
----End
Example
Run the display l2-multicast limit configuration command to check configurations about
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
1000 4000
---- --------
VSI a limit information:
---------------------------------------------------------------------
1000 4000
---- --------
interface GigabitEthernet1/0/0.1 channel limit information:
---------------------------------------------------------------------
bjtv 100 1000

---- --------
---------------------------------------------------------------------
cctv 120 2500
---- --------
---------------------------------------------------------------------
njtv 50 450
---- --------
---------------------------------------------------------------------
bjtv 100 1000
---- --------
---------------------------------------------------------------------
cctv 120 2500
---- --------
---------------------------------------------------------------------
njtv 50 450
---- ----------
Run the display l2-multicast-channel vsi a command to check configurations and statistics of
restriction on the channels in VSI a.
<HUAWEI> display l2-multicast-channel vsi a
Channel information on VSI a
---------------------------------------------------------------------
bjtv 226.1.2.0 255.255.255.0 4
---------------------------------------------------------------------
cctv 226.1.3.0 255.255.255.0 6
---------------------------------------------------------------------
njtv 226.1.1.0 255.255.255.0 3
Run the display l2-multicast limit configuration vsi vsi-name command to check
configurations of Layer 2 multicast CAC on the sub-interface bound with the VSI.
<HUAWEI> display l2-multicast limit configuration vsi a interface Ethernet 1/0/1.1
------------------------------------------------------------------------------
------------------------------------------------------------------------------
interface Ethernet1/0/1.1 limit information:
------------------------------------------------------------------------------
200 500
---- ----------
3.12 Configuring Layer 2 Multicast CAC for a Sub-interface

This section describes how to configure Layer 2 Multicast CAC for a Sub-interface.
3.12.2 Configuring Restriction on the Number of Multicast Group Members of a Sub-interface
3.12.3 Configuring Restriction on the Bandwidth of Multicast Groups of a Sub-interface
3.12.4 Configuring Restriction on the Number of Channels of a Sub-interface
3.12.5 Configuring Restriction on the Bandwidth of Channels of a Sub-interface

In the scenario where UPEs provide multicast services through VSIs and VSIs are bound to
Ethernet sub-interfaces, you can configure Layer 2 multicast CAC on sub-interfaces to ensure
the quality of the IPTV service.
Before configuring Layer 2 multicast CAC for a sub-interface, complete the following tasks:
l Connecting interfaces on network devices correctly

Data Preparation
To configure Layer 2 multicast CAC for a sub-interface, you need the following data.
No. Data
1 Name and ID of the VSI and the number of sub-interface bound to the VSI
2 Name of the channels created for the VSI

Members of a Sub-interface
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface { ethernet | gigabitethernet | eth-trunk} interface-number.subnumber

Step 3 Run:
Restriction on the number of multicast group members is configured for a sub-interface. You
can specify the parameter except to exclude the multicast groups that need not be restricted.
Step 4 Run:
l2-multicast limit max-entry count dot1q vid { { vid1 [ to vid2 ] } & <1-10> }
Restriction on the number of the multicast group members on a sub-interface for dot1q VLAN
tag termination is configured. You can specify the parameter except to exclude the multicast
groups that need not be restricted.
Step 5 Run:
l2-multicast limit max-entry count qinq pe-vid pe-vid ce-vid { { ce-id1 [ to ce-
id2 ] } & <1-10> } [ except acl-number ]
Restriction on the number of the multicast group members on a sub-interface for QinQ VLAN
tag termination is configured. You can specify the parameter except to exclude the multicast
groups that need not be restricted.
NOTE
For details on the procedure for configuring the sub-interface for dot1q or QinQ VLAN tag termination,
refer to the HUAWEI NetEngine80E/40E Configuration Guide - LAN Access and MAN Access.
----End

Groups of a Sub-interface
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface { ethernet | gigabitethernet | eth-trunk} interface-number.subnumber
Step 3 Run:
Restriction on the bandwidth of the multicast groups of a sub-interface is configured.
Step 4 Run:
l2-multicast limit bandwidth bandwidth dot1q vid { { vid1 [ to vid2 ] } & <1-10> }

Restriction on the bandwidth of the multicast groups of a sub-interface for dot1q VLAN tag
termination is configured.
Step 5 Run:
l2-multicast limit bandwidth bandwidth qinq pe-vid pe-vid ce-vid { { ce-id1 [ to
ce-id2 ] } & <1-10> }
Restriction on the bandwidth of the multicast groups of a sub-interface for QinQ VLAN tag
termination is configured.
NOTE
For details on the procedure for configuring the sub-interface for dot1q or QinQ VLAN tag termination,
refer to the HUAWEI NetEngine80E/40E Configuration Guide - LAN Access and MAN Access.
----End
3.12.4 Configuring Restriction on the Number of Channels of a Sub-

interface
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface { ethernet | gigabitethernet | eth-trunk } interface-number.subnumber

Step 3 Run:
Restriction on the number of channels is configured for a sub-interface.
----End

Sub-interface
Context
Procedure
Step 1 Run:
system-view


Step 2 Run:
interface { ethernet | gigabitethernet | eth-trunk } interface-number.subnumber

Step 3 Run:
Restriction on the bandwidth of channels is configured for a sub-interface.
----End

Prerequisite
The configurations of layer 2 Multicast CAC for a Sub-interface function are complete.
Procedure
l Run the display l2-multicast limit configuration vsi [vsi-name] interface { interface-
type interface-number.subnumber } command to check configurations of Layer 2 multicast
CAC for a sub-interface.
a channel.
----End
Example
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
1000 4000
---- --------
---------------------------------------------------------------------
1000 4000
---- --------
---------------------------------------------------------------------
bjtv 100 1000
---- --------


---------------------------------------------------------------------
cctv 120 2500
---- --------
---------------------------------------------------------------------
njtv 50 450
---- --------
---------------------------------------------------------------------
bjtv 100 1000
---- --------
---------------------------------------------------------------------
cctv 120 2500
---- --------
---------------------------------------------------------------------
njtv 50 450
---- ----------
Run the display l2-multicast limit configuration vsi [vsi-name [ interface { interface-type
interface-number } ] ] command to check configurations and statistics of Layer 2 multicast CAC
on the sub-interface bound with the VSI.
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
200 500
---- ----------
Run the display l2-multicast limit interface command to check configurations and statistics of
Layer 2 multicast CAC on an interface.
<HUAWEI> display l2-multicast limit interface Ethernet 1/0/0
------------------------------------------------------------------------------
------------------------------------------------------------------------------
interface Ethernet1/0/0 limit information:
------------------------------------------------------------------------------
500 1000
0 0
Run the display l2-multicast-channel command to check configurations of a global channel.

<HUAWEI>display l2-multicast-channel channel cnn
Channel information on global channel
----------------------------------------------------------------------
cnn 225.1.0.0 255.255.255.0 3
225.0.0.0 255.255.255.0 3
225.2.0.0 255.255.255.0 3
----------------------------------------------------------------------
3.13 Configuring Layer 2 Multicast CAC for a PW

This section describes how to configure Layer 2 Multicast CAC for a PW.

3.13.2 Configuring Restriction on the Number of Multicast Group Members of a PW

3.13.3 Configuring Restriction on the Bandwidth of Multicast Groups of a PW
3.13.4 Configuring Restriction on the Number of Channels of a PW
3.13.5 Configuring Restriction on the Bandwidth of Channels of a PW
In a ring network, UPEs are connected as shown in Figure 3-4 and H-VPLS is deployed in the
network to reduce the replicated multicast traffic between UPEs.
Figure 3-4 Networking diagram of H-VPLS
BTV SERVER
NPE1 NPE2
BFD FOR PIM OVER

VPLS
UPE1 H-VPLS UPE4
UPE3
UPE2
DSLAM1 DSLAN2

In the H-VPLS networking, IGMP Report messages received from downstream UPEs are
forwarding through PWs and the outgoing interface in the multicast forwarding table can also
be a PW.
Therefore, you are recommended to configure Layer 2 multicast CAC for the PW.
NOTE
You must first configure a VSI or PW. When configure the PW, you should specify the signaling protocol,
LDP or BGP, adopted by the PW.
Before configuring Layer 2 multicast CAC for a PW, complete the following tasks:
l Connecting interfaces on network devices correctly
Data Preparation
To configure Layer 2 multicast CAC for a PW, you need the following data.
No. Data
1 Name of the channels created for the PW

Members of a PW
Context
Do as follows on the UPE and SPE:
Procedure
Step 1 Run:
pwsignal { ldp | bgp }
The signaling protocol (LDP or BGP) used by the PW is configured and the VSI-LDP or VSI-
BGP view is displayed.
Step 2 Run:
l2-multicast limit max-entry count [ except acl-number ] {remote-peer ip-address
[ negotiation-vc-id vc-id ]| remote-site remote-site-id}

Restriction on the number of multicast group members is configured for a PW. You can specify
the parameter except to exclude the multicast groups that need not be restricted.
----End

Groups of a PW
Context
Procedure
Step 1 Run:
Step 2 Run:
l2-multicast limit bandwidth bandwidth {remote-peer ip-address [ negotiation-vc-id
vc-id ]| remote-site remote-site-id}
Restriction on the bandwidth of the multicast groups is configured for a PW.
----End
3.13.4 Configuring Restriction on the Number of Channels of a PW
Context
Procedure
Step 1 Run:
Step 2 Run:
l2-multicast limit channel channel-name max-entry count { remote-peer ip-address
[ negotiation-vc-id vc-id ]| remote-site remote-site-id}
Restriction on the number of channels is configured for a PW.
----End

PW

Context
Procedure
Step 1 Run:
Step 2 Run:
l2-multicast limit channel channel-name bandwidth traffic-rate {remote-peer ip-
address [ negotiation-vc-id vc-id ]| remote-site remote-site-id}
Restriction on the bandwidth of the channels is configured for a PW.
----End

Prerequisite
The configurations of layer 2 Multicast CAC for a PW function are complete.
Procedure
l Run the display vpls connection [ ldp | bgp | vsi vsi-name ] [ down | up ] [ verbose ]
command to check information about the VPLS connection.
l Run the display vsi remote ldp [ router-id ip-address ] [ pw-id pw-id ] command to check
information about the remote VSI.
l Run the display l2-multicast limit configuration vsi vsi-name command to check
configurations of Layer 2 multicast CAC for a VSI.
l Run the display l2-multicast limit vsi [vsi-name [ interface { interface-type interface-
number } ] ] |remote-peer ip-address [ negotiation-vc-id vc-id ] | [ channel channel-
name ] command to check configurations and statistics of restriction on the channels of a
peer.
a channel.
----End
Example


---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
1000 4000
---- --------
---------------------------------------------------------------------
1000 4000
---- --------
---------------------------------------------------------------------
bjtv 100 1000
---- --------
---------------------------------------------------------------------
cctv 120 2500
---- --------
---------------------------------------------------------------------
njtv 50 450
---- --------
---------------------------------------------------------------------
bjtv 100 1000
---- --------
---------------------------------------------------------------------
cctv 120 2500
---- --------
---------------------------------------------------------------------
njtv 50 450
---- ----------
Run the display l2-multicast-channel vsi a command to check configurations of restriction on

the channels in the VSI.
<HUAWEI> display l2-multicast-channel vsi a
---------------------------------------------------------------------
bjtv 226.1.2.0 255.255.255.0 4
---------------------------------------------------------------------
cctv 226.1.3.0 255.255.255.0 6
---------------------------------------------------------------------
njtv 226.1.1.0 255.255.255.0 3
Run the display l2-multicast limit configuration vsi vsi-name command to check
configurations and statistics of Layer 2 multicast CAC on the sub-interface bound with the VSI.
------------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------------
200 500
---- ----------

3.14 Maintaining Static Layer 2 Multicast

This section describes how to clear the IGMP snooping statistics.
3.14.1 Clearing the Dynamic Port in the Outbound Port Information

3.14.2 Clearing the Statistics of IGMP Snooping
3.14.3 Monitoring the Running Status of IGMP Snooping
3.14.4 Maintaining Layer 2 Multicast CAC
3.14.1 Clearing the Dynamic Port in the Outbound Port Information
Context
CAUTION
After you clear the dynamic port in the outbound port information, the hosts in the VLAN or
VSI are disabled from receiving multicast flows provisionally until the router regenerates the
outbound port information. So, confirm before you use the command.
Procedure
Step 1 Run the reset igmp-snooping group { vlan { vlan-id | all } | vsi { vsi-name | all } | all } command
in the user view to clear the Dynamic Port in the Outbound Port Information statistics.
----End
3.14.2 Clearing the Statistics of IGMP Snooping
Context
CAUTION
If the statistics of IGMP snooping are cleared, the previous statistics cannot be restored. So,
confirm the action before you use the command.
Procedure
Step 1 Run the reset igmp-snooping statistics { vlan { vlan-id | all } | vsi { vsi-name | all} | all }
command in the user view to clear the Statistics of IGMP Snooping statistics.
----End

3.14.3 Monitoring the Running Status of IGMP Snooping
Context
In routine maintenance, you can run the following command in any view to check the operation
of he Running Status of IGMP Snooping.
Procedure
l Run the display igmp-snooping [ vlan [ vlan-id ] | vsi [ vsi-name ] ] [ configuration ]
command in any view to check the operation of all the configurations of IGMP snooping.
l Run the display igmp-snooping port-info [ vlan vlan-id [ group-address group-
address ] ] [ verbose ] command in any view to check the operation of information about
ports on the router.
l Run the display igmp-snooping router-port { vlan vlan-id | vsi vsi-name } command in
any view to check the operation of information about the router port.
l Run the display igmp-snooping statistics { vlan [ vlan-id ] | vsi [ vsi-name ] } command
in any view to check the operation of the statistics of IGMP snooping.
l Run the display { multicast-vlan | user-vlan } vlan [ vlan-id ] command in any view to
check the operation of information about the multicast VLAN or the user VLAN.
l Run the display igmp-snooping querier { vlan [ vlan-id ] | vsi [ vsi-name ] } command
in any view to check the operation of information about the IGMP snooping querier.
l Run the display l2-multicast forwarding-mode { vlan [ vlan-id ] | vsi [ vsi-name ] }
command in any view to check the operation of the forwarding mode of Layer 2 multicast.
l Run the display l2-multicast forwarding-table {vlan vlan-id | vsi vsi-name } [ group-
address group-address | router-group ] command in any view to check the operation of
the Layer 2 multicast forwarding table.
l Run the display l2-multicast protection [ vlan vlan-id ] command in any view to check
the operation of detailed information about the protection group.
----End
3.14.4 Maintaining Layer 2 Multicast CAC
CAUTION
Debugging affects the performance of the system. So, after debugging, run the undo debugging
all command to disable it immediately.
When a fault occurs, run the debugging command to debug CAC and locate the fault. For the
procedure for displaying the debugging information, refer to the HUAWEI NetEngine80E/
40E Router Configuration Guide - System Management.
Action Command
Enable the debugging of Layer 2 debugging l2-multicast limit { all | check |

multicast CAC. configuration | event }


This section provides several configuration examples of Layer 2 multicast.
3.15.1 Example for Configuring IGMP Snooping for a VSI

3.15.2 Example for Configuring IGMP Snooping for a VLAN
3.15.3 Example for Configuring Replication of the Multicast VLAN
3.15.4 Example for Configuring 1+1 Protection of Multicast VLANs
3.15.5 Example for Adding an Interface to a Multicast Group Statically
3.15.6 Example for Configuring Layer 2 Multicast CAC for a VLAN
This section provides a typical VLAN networking and a specific configuration example for
describing configurations about multicast CAC in a VLAN in details.
3.15.7 Example for Configuring Layer 2 Multicast CAC for a VSI
This section provides a typical VSI networking and a specific configuration example for
describing configurations about multicast CAC in a VSI in details.
3.15.8 Example for Configuring Layer 2 Multicast CAC for a PW
This section provides a typical PW networking and a specific configuration example for
describing configurations about multicast CAC on a PW in details.
3.15.9 Example for Configuring Layer 2 Multicast SSM Mapping
3.15.10 Example for Configuring Multicast CAC on a Sub-interface for VLAN Tag Termination
3.15.1 Example for Configuring IGMP Snooping for a VSI

As shown in Figure 3-5, PE1 serves as the Superstratum Provider Edge (SPE) device, and PE2
and PE3 serve as the UPE devices in the VPLS network. When Hierarchical VPLS (HVPLS) is
deployed, the multicast data is broadcasted to all PWs if IGMP snooping is not supported on
PE1. This wastes the network resources.
After IGMP snooping is configured for the VSI, however, the multicast data is sent to only access
devices of multicast receivers. In a network with a stable topology, configure GE 1/0/0 on PE1
as a static router port and the PW on PE2 as a static router port in the VSI. In this manner,
receivers can steadily receive the multicast data. To reduce the number of IGMP Query packets
from the upstream router, you are recommended to configure PE1 as a querier. This further saves
the bandwidth.

Figure 3-5 Networking diagram of configuring IGMP snooping for a VSI
VPLS Loopback1
CE3
POS2/0/0 GE1/0/0
Ethernet GE1/0/0
Loopback1 PE3
CE1
POS3/0/0
GE1/0/0
GE1/0/0
GE2/0/0 PE1 POS2/0/0 Ethernet
PE2 CE2
Source GE1/0/0
POS2/0/0 GE1/0/0
GE2/0/0
Receiver
Loopback1
router Interface IP address

PE1 POS 2/0/0 10.1.1.1/30
POS 3/0/0 20.1.1.1/30
Loopback1 1.1.1.1/32
PE2 POS 2/0/0 10.1.1.2/30
PE3 POS 2/0/0 20.1.1.2/30
CE1 GE 1/0/0 100.1.1.1/30
CE2 GE 1/0/0 100.1.1.2/30
CE3 GE 1/0/0 100.1.1.3/30
1. Configure basic VPLS functions.

2. Enable IGMP snooping globally and for the VSI.
3. Configure static router ports and configure PE1 as a querier.
Data Preparation
l ID of the VSI and VSI name

Procedure
Step 1 Enable Open Shortest Path First (OSPF) to advertise the network segment of each interface and
ID of the Label Switch Router(LSR).
The configurations are not mentioned here.
Step 2 Configure basic MPLS functions and the Label Distribution Path (LDP).
# Configure PE1.
<PE1> system-view
[PE1] mpls lsr-id 1.1.1.1
[PE1] mpls
[PE1-mpls] quit
[PE1] mpls ldp
[PE1-mpls-ldp] quit
[PE1] interface pos 2/0/0
[PE1-Pos2/0/0] mpls
[PE1-Pos2/0/0] mpls ldp
[PE1-Pos2/0/0]quit
[PE1-Pos3/0/0] mpls
[PE1-Pos3/0/0] quit
# Configure PE2.
<PE2> system-view
[PE2] mpls
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2-Pos2/0/0] mpls
[PE2-Pos2/0/0] quit
# Configure PE3.
<PE3> system-view
[PE3] mpls
[PE3-mpls] quit
[PE3] mpls ldp
[PE3-mpls-ldp] quit
[PE3-Pos2/0/0] mpls
[PE3-Pos2/0/0] quit
Step 3 Enable MPLS L2VPN and configure a VSI.

# Configure PE1.
<PE1> system-view
[PE1] mpls l2vpn
[PE1-l2vpn] quit
[PE1] vsi v123 static
[PE1-vsi-v123] pwsignal ldp
[PE1-vsi-v123-ldp] vsi-id 123
[PE1-vsi-v123-ldp] peer 2.2.2.2 upe
[PE1-vsi-v123-ldp] peer 3.3.3.3 upe
[PE1-vsi-v123-ldp] quit
[PE1-vsi-v123] quit
# Configure PE2.

<PE2> system-view
[PE2] mpls l2vpn
[PE2-l2vpn] quit
[PE2-vsi-v123-ldp] peer 1.1.1.1
[PE2-vsi-v123] quit
# Configure PE3.
<PE3> system-view
[PE3] mpls l2vpn
[PE3-l2vpn] quit
[PE3-vsi-v123-ldp] peer 1.1.1.1
[PE3-vsi-v123] quit
Step 4 Bind the VSI on the PE devices to interfaces.
# Configure PE1. The configurations of PE2 and PE3 are similar to those of PE1 and are not
mentioned here.
[PE1] vlan 10
[PE1-vlan10] quit
[PE1-GigabitEthernet1/0/0] portswitch
[PE1-GigabitEthernet1/0/0] port link-type access
[PE1-GigabitEthernet1/0/0] port default vlan 10
[PE1-GigabitEthernet1/0/0] undo shutdown
[PE1] interface vlanif 10
[PE1-Vlanif10] l2 binding vsi v123
[PE1-Vlanif10] quit
Step 5 Enable IGMP snooping globally and for the VSI on the PE devices.
# Configure PE1. The configurations of PE2 and PE3 are similar to those of PE1 and are not
mentioned here.
[PE1] igmp-snooping enable
[PE1] vsi v123
[PE1-vsi-v123] igmp-snooping enable
Step 6 Configure GE 1/0/0 on PE1 as a static router port and the PW on PE2 as a static router port in
VLAN 10, and configure the querier on PE1. The default values are used for the querier and
thus no special configuration is required.
# Configure PE1.
<PE1> system-view
[PE1] igmp-snooping send-query enable
[PE1] vsi v123
[PE1-vsi-v123] igmp-snooping querier enable
[PE1-vsi-v123] quit
[PE1-GigabitEthernet1/0/0] igmp-snooping static-router-port vlan 10
# Configure PE2.
<PE2> system-view
[PE2] vsi v123
[PE2-vsi-v123] igmp-snooping static-router-port remote-peer 1.1.1.1


# Run the display igmp-snooping querier vsi command on PE1. You can check whether the
configuration of the querier succeeds. If the Enable state is displayed as shown in the following
output, it indicates that the querier is enabled for VSI v123.
<PE1> display igmp-snooping querier vsi v123
VSI Querier-state
-----------------------------------------------
v123 Enable
-----------------------------------------------
total entry 1
# Run the display igmp-snooping router-port vlan command on PE1. You can check whether
the configuration of the static router port succeeds. If STATIC is displayed as shown in the
following output, it indicates that GE 1/0/0 is already configured as a static router port in VLAN
10.
<PE1> display igmp-snooping router-port vlan 10
Port Name UpTime Expires Flags
---------------------------------------------------------------------
VLAN 10, 1 router-port(s)
GigabitEthernet1/0/0 00:00:16 -- STATIC
# Run the display igmp-snooping router-port vsi command on PE2. You can check whether
the configuration of the static router port succeeds. If STATIC is displayed as shown in the
following output, it indicates that PW (1.1.1.1/123) is already configured as a static router port.
<PE2> display igmp-snooping router-port vsi v123
---------------------------------------------------------------------
VSI v123, 1 router-port(s)
PW(1.1.1.1/123) 00:05:16 -- STATIC
----End
Configuration Files
#
sysname PE1
#
vlan batch 10
#
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi v123 static
pwsignal ldp
vsi-id 123
peer 2.2.2.2 upe
peer 3.3.3.3 upe
#
mpls ldp
#
interface Vlanif10
l2 binding vsi v123
#

undo shutdown
portswitch
port link-type access
port default vlan 10
igmp-snooping static-router-port vlan 10
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 20.1.1.1 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 10.1.1.0 0.0.0.3
network 20.1.1.0 0.0.0.3
#
return
#
sysname PE2
#
vlan batch 10
#
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi v123 static
pwsignal ldp
vsi-id 123
peer 1.1.1.1
igmp-snooping static-router-port remote-peer 1.1.1.1
#
mpls ldp
#
interface Vlanif10
l2 binding vsi v123
#
undo shutdown
portswitch
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 10.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1

ip address 2.2.2.2 255.255.255.255

#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 10.1.1.0 0.0.0.3
#
return
#
sysname PE3
#
vlan batch 10
#
#
mpls lsr-id 3.3.3.3
mpls
#
mpls l2vpn
#
vsi v123 static
pwsignal ldp
vsi-id 123
peer 1.1.1.1
#
mpls ldp
#
interface Vlanif10
l2 binding vsi v123
#
undo shutdown
portswitch
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 20.1.1.2 255.255.255.252
mpls
mpls ldp
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
#
ospf 1
area 0.0.0.0
network 3.3.3.3 0.0.0.0
network 20.1.1.0 0.0.0.3
#
return
l Configuration file of CE1
#
sysname CE1
#
#
interface GigabitEthernet 1/0/0
undo shutdown
ip address 100.1.1.1 255.255.255.252
igmp enable
#
ospf 1
area 0.0.0.0
network 100.1.1.1 0.0.0.3

#
return
3.15.2 Example for Configuring IGMP Snooping for a VLAN

A shown in Figure 3-6, GE 1/0/0 on Router A is connected to an upstream multicast router,
Router B. Router A is also connected downstream to Switch-A and Switch-B, which belong to
VLAN 3 and VLAN 2 respectively.
To save the bandwidth and system resources between Router A and Router B, you can configure
Router A as a querier to send IGMP Query messages instead of Router B.
When hosts connected to Switch-A need to receive the multicast data for a long time, you can
configure the interface that connects Router A to Router B as a static router port.
If only one host connected to Switch-B needs to receive the multicast data, you can configure
prompt leave for GE 1/0/2 that connects Router A to Switch-B. In this manner, after the IGMP
Leave message is received, GE 1/0/2 becomes invalid immediately without waiting for the
timeout period of the aging timer. This saves the bandwidth and system resources.
Figure 3-6 Example for configuring IGMP Snooping for a VLAN
Source RouterB
Internet/
Intranet
GE1/0/0
GE1/0/1 GE1/0/2
RouterA
VLAN 3 VLAN2
SwitchA SwitchB
1. Configure VLANs.
2. Configuring basic IGMP snooping functions.
3. Configure Router A as the querier for VLAN 3.
4. Configure GE 1/0/0 on Router A as a static router port.
5. Configure prompt leave for GE 1/0/2 on Router A.

Data Preparation
l GE 1/0/0 is configured as the static router port.
l GE 1/0/2 is configured with prompt leave.
l Switch-A and the switches connected to Switch-A belong to VLAN 3; Switch-B and the
switches connected to Switch-B belong to VLAN 2.
Procedure
Step 1 Configure VLANs.
<RouterA> system-view
[RouterA-GigabitEthernet1/0/1] portswitch
[RouterA-GigabitEthernet1/0/1] undo shutdown
[RouterA] vlan 3
[RouterA-vlan3] port gigabitethernet 1/0/1
[RouterA-vlan3] quit
[RouterA] vlan 2
[RouterA-vlan2] port gigabitethernet 1/0/2
Step 2 Enable IGMP snooping on the router.

# Enable global IGMP snooping on Router A.
[RouterA] igmp-snooping enable
# On Router A, enable global IGMP snooping for VLAN 3 and VLAN 2.

[RouterA] vlan 3
[RouterA-vlan3] igmp-snooping enable
[RouterA] vlan 2
Step 3 Configure Router A as the querier for VLAN 3 and allow Router A to send IGMP General Query
messages.
[RouterA] vlan 3
[RouterA-vlan3] igmp-snooping querier enable
[RouterA] igmp-snooping send-query enable
Step 4 Configure GE 1/0/0 on Router A as a static router port.

[RouterA-GigabitEthernet1/0/0] igmp-snooping static-router-port vlan 3
Step 5 On Router A, configure prompt leave for ports in VLAN 2.

[RouterA] vlan 2
[RouterA-vlan2] igmp-snooping prompt-leave

# Run the display igmp-snooping command on Router A.

<RouterA> display igmp-snooping vlan configuration

igmp-snooping prompt-leave
# Run the display igmp-snooping router-port vlan 3 command on Router A. As shown in the
following output, it indicates that GE 1/0/0 is configured as a static router port.
<RouterA> display igmp-snooping router-port vlan 3
---------------------------------------------------------------------
VLAN 3, 1 router-port(s)
GigabitEthernet1/0/1 00:01:02 -- STATIC
# Run the display igmp-snooping querier vlan 3 command on Router A. You can check
whether the configuration of the querier succeeds.
<RouterA> display igmp-snooping querier vlan 3
VLAN Querier-state
-----------------------------------------------
3 Enable
----End
Configuration Files
#
sysname RouterA
#
vlan batch 2 3
#
#
vlan 2
#
vlan 3
#
undo shutdown
portswitch
#
undo shutdown
portswitch
port default vlan 3
#
undo shutdown
portswitch
port default vlan 2
#
return

3.15.3 Example for Configuring Replication of the Multicast VLAN
As shown in Figure 3-7, GE 1/0/1 that connects Router A to Router B is added to VLAN 10.
GE 1/0/2 and GE 1/0/3 that connect Router A to switches are added to VLAN 100 and VLAN
200 respectively. It is required that the four hosts connected to Router A should receive the
multicast packets from the multicast group with the address ranges from 225.0.0.1 to 225.0.0.3.
VLAN 10 is a multicast VLAN, VLAN 100 and VLAN 200 are user VLANs.
Figure 3-7 Networking diagram of configuring replication of the multicast VLAN on Router
A
Source RouterB
Internet/
Intranet
VLAN 10 GE1/0/1
GE1/0/2 GE1/0/3
RouterA
VLAN100 VLAN200
1. Create a multicast VLAN and user VLANs.

2. Enable replication of the multicast VLAN.
3. Set the mapping relationship between the multicast VLAN and the user VLANs.
4. Configure the VLAN that the interface of Router A belongs to and static multicast entries.
Data Preparation
l Interface connected to Router B and the VLAN that the interface belongs to
l Interfaces connected to hosts and the VLANs that the interfaces belong to
l Group addresses of entries in the static multicast VLAN

Procedure
Step 1 Create a multicast VLAN and user VLANs.
# Create a multicast VLAN.
[RouterA] vlan 10
# Create user VLANs.

[RouterA] vlan batch 100 200
Step 2 Enable replication of the multicast VLAN.

[RouterA] igmp-snooping version 3
[RouterA] vlan 10
[RouterA-vlan10] multicast-vlan enable
Step 3 Set the mapping relationship between the multicast VLAN and the user VLANs.
[RouterA-vlan10] multicast user-vlan 100
[RouterA-vlan10] multicast user-vlan 200
Step 4 Configure the VLAN that the interface of Router A belongs to and static multicast entries.
# Configure GE 1/0/1 to allow data frames from VLAN 10 to pass through.
[RouterA-GigabitEthernet1/0/1] port trunk allow-pass vlan 10
# Add GE 1/0/2 to VLAN 100, and add the interface to the multicast group statically.
[RouterA-GigabitEthernet1/0/2] l2-multicast static-group group-address 225.0.0.1
vlan 100
vlan 100
vlan 100
# Add GE 1/0/3 to VLAN 200, and add the interface to the multicast group statically.
vlan 200
vlan 200
vlan 200

After the static Layer 2 multicast is configured for the user VLAN, run the display l2-multicast
forwarding-table command. You can view information about entries of the multicast VLAN.

According to the following output, the forwarding table is created for the multicast VLAN and
the forwarding mode of the table is based on MAC addresses.
The static multicast group 225.0.0.1 is mapped to the MAC multicast address 0100-5e00-0001;
the static multicast group 225.0.0.2 is mapped to the MAC multicast address 0100-5e00-0002;
the static multicast group 225.0.0.3 is mapped to the MAC multicast address 0100-5e00-0003.
<RouterA> display l2-multicast forwarding-table vlan 10
VLAN ID : 10, Forwarding Mode : IP,
--------------------------------------------------------------------
(Source, Group) Status Age Index Port-cnt
--------------------------------------------------------------------
(*, 225.0.0.1) Ok No 0 1
(*, 225.0.0.2) Ok No 0 2
(*, 225.0.0.3) Ok No 0 2
--------------------------------------------------------------------
Total Entry(s) : 3
----End
Configuration Files
#
sysname RouterA
#
vlan batch 10 100 200
#
#
vlan 10
multicast user-vlan 100
multicast user-vlan 200
#
undo shutdown
portswitch
port trunk allow-pass vlan 10
#
undo shutdown
portswitch
l2-multicast static-group group-address 225.0.0.1 vlan 100
#
undo shutdown
portswitch
#
return
3.15.4 Example for Configuring 1+1 Protection of Multicast VLANs

As shown in Figure 3-8, Router A is responsible for receiving multicast packets from the
multicast source. In addition, Router A replicates multicast packets of VLAN 10 and sends them

to VLAN 2 and VLAN 3. GE 1/0/1 on Router A belongs to VLAN 2 and GE 1/0/2 belongs to
VLAN 3. Router B selects the multicast traffic from VLAN 2 and VLAN 3 and performs the
switchover of traffic in the case of VLAN failure. In this manner, Router B steadily and
effectively sends multicast packets to hosts within VLAN 100 and VLAN 200.
Figure 3-8 Networking diagram of configuring 1+1 protection of multicast VLANs
DHCP Source
Server
IP/MPLS
core
VLAN10 GE1/0/3
RouterA
GE1/0/1 GE1/0/2
VLAN2 VLAN3
MAN MAN
VLAN2 VLAN3
GE2/0/1 GE2/0/2
GE2/0/3 GE2/0/4
RouterB
VLAN100 VLAN200
1. Enable replication of the multicast VLAN.

2. Configure the multicast VLAN 1+1 protection group.
3. Configure OAM fault detection for the multicast VLAN.
Data Preparation

l ID of the working VLAN and ID of the protection VLAN

l Number of the interface that needs to be added to the VLAN
l Names of the MD and the MA, and number of the RMEP
Procedure
Step 1 Enable replication of the multicast VLAN.
# Enable replication of the multicast VLAN on Router A, and add GE 1/0/1 and GE 1/0/2 to the
multicast VLAN.
[RouterA] vlan batch 2 3 10
[RouterA] vlan 10
[RouterA-vlan10] multicast-vlan enable
[RouterA-vlan10] multicast-vlan user-vlan 2 to 3
[RouterA] interface gigabitethernet1/0/3
vlan 2
vlan 3
# Enable replication of the multicast VLAN on Router B, and add GE 2/0/1, GE 2/0/2, GE 2/0/3,
and GE 2/0/4 to the multicast VLAN.
<RouterB> system-view
[RouterB] vlan batch 2 3 100 200
[RouterB] igmp-snooping enable
[RouterB] vlan 2
[RouterB-vlan2] igmp-snooping enable
[RouterB-vlan2] multicast-vlan enable
[RouterB-vlan2] multicast-vlan user-vlan 100 200
[RouterB-vlan2] quit
[RouterB] interface gigabitethernet2/0/1
[RouterB-GigabitEthernet2/0/1] undo shutdown
[RouterB-GigabitEthernet2/0/1] portswitch
[RouterB-GigabitEthernet2/0/1] port trunk allow-pass vlan 2
[RouterB-GigabitEthernet2/0/1] quit
[RouterB-GigabitEthernet2/0/3] l2-multicast static-group group-address 225.0.0.1
vlan 100

[RouterB-GigabitEthernet2/0/4] l2-multicast static-group group-address 225.0.0.1
vlan 200
Step 2 Configure the 1+1 protection group of multicast VLANs.

[RouterB] vlan 2
[RouterB-vlan2] l2-multicast protection protect-vlan 3
Step 3 Configure OAM fault detection for the multicast VLAN.
# On Router A, configure OAM fault detection for the multicast VLAN.

[RouterA] cfm enable
[RouterA] cfm md test
[RouterA-md-test] ma test2
[RouterA-md-test-ma-test2] map vlan 2
[RouterA-md-test-ma-test2] mep mep-id 2 vlan
[RouterA-md-test-ma-test2] mep ccm-send mep-id 2 enable
[RouterA-md-test-ma-test2] quit
[RouterA-md-test] ma test3
[RouterA-md-test-ma-test3] map vlan 3
[RouterA-md-test-ma-test3] mep mep-id 3 vlan
[RouterA-md-test-ma-test3] mep ccm-send mep-id 3 enable
[RouterA-md-test-ma-test3] quit
# On Router B, configure OAM fault detection for the multicast VLAN.

[RouterB] cfm enable
[RouterB] cfm md test
[RouterB-md-test] ma test2
[RouterB-md-test-ma-test2] map vlan 2
[RouterB-md-test-ma-test2] mep mep-id 102 interface gigabitethernet2/0/1 outward
[RouterB-md-test-ma-test2] remote-mep mep-id 2
[RouterB-md-test-ma-test2] remote-mep ccm-receive mep-id 2 enable
[RouterB-md-test-ma-test2] quit
[RouterB-md-test] ma test3
[RouterB-md-test-ma-test3] map vlan 3
[RouterB-md-test-ma-test3] mep mep-id 103 interface gigabitethernet2/0/2 outward
[RouterB-md-test-ma-test3] remote-mep mep-id 3
[RouterB-md-test-ma-test3] remote-mep ccm-receive mep-id 3 enable
[RouterB-md-test-ma-test3] quit
[RouterB-md-test] quit
[RouterB] vlan 2
[RouterB-vlan2] l2-multicast protection oam-bind cfm md test ma test2 remote-mep 2
[RouterB] vlan 3
[RouterB-vlan3] l2-multicast protection oam-bind cfm md test ma test3 remote-mep 3
# The following output shows the configurations about the multicast VLAN on Router B. You
can check whether the configurations are correct.
<RouterB> display multicast-vlan vlan 2
Multicast-vlan : 2
User-vlan : 2
IGMP snooping state : Enable
User-vlan Snooping-state
-------------------------------------
100 Enable
200 Enable

# Run the display l2-multicast protection vlan 2 command on Router B to check information
about the multicast protection group.
<RouterB> display l2-multicast protection vlan 2
PG main-vlan 2, protect-vlan 3, work-vlan 2.
PG main-vlan state OK, protect-vlan state OK.
PG revertive-mode Revertive, wtr-time 5s
PG hold-off time 0(100ms)
PG protocol-enable is Yes, switch command is none
PG state is normal
Vlan 2 bind md is test, ma is test2, remote-mep is 2
# Run the shutdown command on GE 2/0/1 on Router B and then run the display l2-multicast
protection vlan command to check information about the protection group. You can view that
VLAN 3 serves as the working VLAN. This indicates that the switchover is performed and
Router B now receives the multicast data from the protection VLAN.
<RouterB> display l2-multicast protection vlan 2
PG main-vlan 2, protect-vlan 3, work-vlan 3.
PG main-vlan state DE, protect-vlan state OK.
PG revertive-mode Revertive, wtr-time 5s
PG hold-off time 0(100ms)
PG protocol-enable is Yes, switch command is none
PG state is sf_w
Vlan 2 bind md is test, ma is test2, remote-mep is 2
----End
Configuration Files
#
sysname RouterA
#
vlan batch 2 3 10
#
#
vlan 10
multicast-vlan user-vlan 2 to 3
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
cfm enable
cfm md test
ma test2
map vlan 2
mep mep-id 2 vlan
mep ccm-send mep-id 2 enable
ma test3

map vlan 3
mep mep-id 3 vlan
mep ccm-send mep-id 3 enable
#
return

#
sysname RouterB
#
vlan batch 2 3 100 200
#
#
vlan 2
multicast-vlan user-vlan 100 200
l2-multicast protection protect-vlan 3
l2-multicast protection oam-bind cfm md test ma test2 remote-mep 2
#
vlan 3
l2-multicast protection oam-bind cfm md test ma test3 remote-mep 3
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
undo shutdown
portswitch
#
cfm md test
ma test2
map vlan 2
mep mep-id 102 interface GigabitEthernet2/0/1 outward
remote-mep mep-id 2
remote-mep ccm-receive mep-id 2 enable
ma test3
map vlan 3
mep mep-id 103 interface GigabitEthernet2/0/2 outward
remote-mep mep-id 3
remote-mep ccm-receive mep-id 3 enable
#
return

3.15.5 Example for Adding an Interface to a Multicast Group

Statically
As shown in Figure 3-9, GE 1/0/1 on Router A is connected to a router, and GE 1/0/2 on the
Router A is connected to a switch. It is required that all the hosts in VLAN 3 should receive the
multicast packets from the multicast group 225.0.0.1.
Figure 3-9 Networking diagram of adding an interface to a multicast group statically

Source
DHCP
server
IP/MPLS
Core
RouterB
VLAN 3 GE1/0/1
RouterA
GE1/0/2
Host3 Host4 Host5
1. Create a VLAN.
2. Add interfaces to the VLAN.
3. Add interfaces to the multicast group statically.
Data Preparation
l Address of the multicast group

l ID of the VLAN and numbers of interfaces

Procedure
Step 1 Create a VLAN.
# Create VLAN 3 on Router A.
[RouterA] vlan 3
Step 2 Add interfaces to the VLAN.

# Configure GE 1/0/2 on Router A to allow data frames from VLAN 3 to pass through.
# Configure GE 1/0/1 on Router A to allow data frames from VLAN 3 to pass through.
Step 3 Create GE 1/0/2 on Router A and add it to the multicast group 225.0.0.1 statically.
vlan 3

Run the display l2-multicast forwarding table command on Router A. You can view
information about the outbound interface of the multicast group 225.0.0.1.
VLAN ID : 3, Forwarding Mode : MAC, Total Entry Count : 1
Group-Address Status Age Index Port-cnt add del update
------------------------------------------------------------------------------
0100-5e01-0101 : 225.0.0.1 NoChg No 0 1 0 0 0
<HUAWEI> display l2-multicast forwarding-table vlan 3
VLAN ID : 3, Forwarding Mode : IP,
--------------------------------------------------------------------
--------------------------------------------------------------------
( *, 225.225.225.225) Ok No 0 1
--------------------------------------------------------------------
Total Entry(s) : 1
----End
Configuration Files
#
sysname RouterA
#
vlan batch 3
#
#
undo shutdown
portswitch

#
undo shutdown
portswitch
#
return
3.15.6 Example for Configuring Layer 2 Multicast CAC for a VLAN

This section provides a typical VLAN networking and a specific configuration example for
describing configurations about multicast CAC in a VLAN in details.
As shown in Figure 3-10, Switch and Router A are connected through VLAN 20. Router A
accesses the upper layer network (IPTV server in the diagram) through Router B. The multicast
CAC bandwidth limit is set on both the switch and Router A. This relieves the burden of
bandwidth on a physical link between the switch and Router A, and ensures that high-quality
IPTV services reach downstream users connected to the switch.
Layer 2 multicast CAC for the VLAN is required on GE 1/0/0 on Router A. The maximum
number of multicast group members allowed in VLAN 20 is restricted to 50 and the bandwidth
of the multicast groups is 1000 kbit/s; the maximum number of member multicast groups of the
BJTV channel in VLAN 20 is restricted to 15 and the bandwidth of the BJTV channel is 60 kbit/
s. Gobal Layer 2 multicast CAC on Router A needs to be configured to restrict the number of
multicast group members on Router A to 100 and the bandwidth of multicast groups to 2000
kbit/s.
The Layer 2 multicast CAC limit for VLAN 20 is set on the switch. The maximum number of
multicast group members allowed in VLAN 20 is restricted to 40 and the bandwidth of the
multicast groups is 100 kbit/s; the maximum number of member multicast groups of the BJTV
channel in VLAN 20 is restricted to 3 and the bandwidth of the BJTV channel is 30 kbit/s; the
maximum number of global multicast groups is 50 and the bandwidth of the multicast groups is
1000 kbit/s.
The channel named bjtv of the ASM type is configured. The multicast address of the member
multicast group is 226.1.1.0/24 and the bandwidth of each membe multicast group is 4 kbit/s;
the multicast address of the member multicast group 2 is 226.1.2.0/24, and the bandwidth of
each member multicast group is 5 kbit/s;the multicast address of the member multicast group 3
is 226.1.3.0/24, and the bandwidth of each member multicast group is 6 kbit/s.
The multicast policy is configured for VLAN 20 by using the unspecified-channel deny
command, disabling the switch and router from creating entries for multicast groups whose
addresses are not in the address range allowed by the configured channel.
Figure 3-10 Networking diagram of Layer 2 multicast CAC for a VLAN
VLAN20 RouterA
GE1/0/0 MPLS/ Internet

VPLS
GE1/0/1
Switch RouterB TV Server

l Configure VLAN 20 on Switch and Router A.
l Enable global IGMP snooping.
l Configure global Layer 2 multicast CAC and Layer 2 multicast CAC for VLAN 20.
Data Preparation
l ID of the VLAN to which Router A and Switch belong
l Parameters related to Layer 2 multicast CAC, including the number of multicast group
members and channels and bandwidth of multicast groups and channels
Procedure
Step 1 Configure VLAN 20 on Router A and the switch.
# Configure the switch.
[Switch] vlan 20
[Switch-vlan20] quit
[Switch] interface gigabitethernet 1/0/1
[Switch-GigabitEthernet1/0/1] portswitch
[Switch-GigabitEthernet1/0/1] port trunk allow-pass vlan 20
# Configure Router A.
Step 2 Enable global IGMP snooping.

# Configure Router A. Configurations on the switch are the same as the configurations on
Router A.
Step 3 Enable IGMP snooping in VLAN 20.

# Configure Router A. Configurations on the switch are the same as the configurations on
Router A.
[RouterA] vlan 20
Step 4 Configure the channel attributes in VLAN 20.

[Switch] l2-multicast-channel vlan 20
[Switch-l2-channel-vlan20] channel bjtv type asm
[Switch-l2-channel-vlan20-bjtv] group 226.1.1.0 255.255.255.0 per-bandwidth 4
[Switch-l2-channel-vlan20-bjtv] quit

[Switch-l2-channel-vlan20] unspecified-channel deny
[RouterA] l2-multicast-channel vlan 20
[RouterA-l2-channel-vlan20] channel bjtv type asm
[RouterA-l2-channel-vlan20-bjtv] group 226.1.1.0 255.255.255.0 per-bandwidth 4
[RouterA-l2-channel-vlan20-bjtv] quit
[RouterA-l2-channel-vlan20] unspecified-channel deny
Step 5 Configure global Layer 2 multicast CAC and Layer 2 multicast CAC for VLAN 20.
[RouterA] l2-multicast limit max-entry 100
[RouterA] l2-multicast limit bandwidth 2000
[RouterA] l2-multicast limit max-entry 50 vlan 20
[RouterA] l2-multicast limit bandwidth 1000 vlan 20
[RouterA] l2-multicast limit channel bjtv max-entry 15 vlan 20
[RouterA] l2-multicast limit channel bjtv bandwidth 60 vlan 20

[Switch] l2-multicast limit max-entry 50
[Switch] l2-multicast limit bandwidth 1000
[Switch] l2-multicast limit max-entry 40 vlan 20
[Switch] l2-multicast limit bandwidth 100 vlan 20
[Switch] l2-multicast limit channel bjtv max-entry 3 vlan 20
[Switch] l2-multicast limit channel bjtv bandwidth 30 vlan 20
Run the display l2-multicast limit configuration command. You can view configurations of
Take the display on Router A as an example:

[RouterA] display l2-multicast limit configuration
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
100 2000
---- ----------
---------------------------------------------------------------------
50 1000
---- ----------
---------------------------------------------------------------------
bjtv 15 60
---- ----------
Run the display l2-multicast-channel vlan 20 command. You can view configurations of the
channels in VLAN 20.
Take the display on the switch as an example:

[Switch] display l2-multicast-channel vlan 20
Channel information on VLAN 20
ChannelName Group/Mask Source/Mask Bandwidth
-------------------------------------------------------------------------------
bjtv 226.1.1.0/24 * 4

226.1.2.0/24 * 6
226.1.3.0/24 * 5
Run the display l2-multicast limit vlan 20 command. You can view configurations of Layer 2
multicast CAC for VLAN 20.
[RouterA] display l2-multicast limit vlan 20
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
50 1000
0 0
---------------------------------------------------------------------
bjtv 15 60
0
----End
Configuration Files
#
sysname RouterA
#
vlan 20
#
l2-multicast limit max-entry 100
l2-multicast limit bandwidth 2000
l2-multicast limit max-entry 50 vlan 20
l2-multicast limit bandwidth 1000 vlan 20
l2-multicast limit channel bjtv max-entry 15 vlan 20
l2-multicast limit channel bjtv bandwidth 60 vlan 20
#
vlan 20
#
undo shutdown
portswitch
#
l2-multicast-channel vlan 20
channel bjtv type asm
group 226.1.1.0 255.255.255.0 per-bandwidth 4
#
return
l Configuration file of the switch

#
sysname Switch
#
vlan 20
#
l2-multicast limit max-entry 40 vlan 20

l2-multicast limit bandwidth 100 vlan 20

#
vlan 20
#
undo shutdown
portswitch
#
l2-multicast-channel vlan 20
#
return
3.15.7 Example for Configuring Layer 2 Multicast CAC for a VSI

This section provides a typical VSI networking and a specific configuration example for
describing configurations about multicast CAC in a VSI in details.
As shown in Figure 3-11, Router A and Router B are connected a VSI network. Layer 2 multicast
CAC for the VSI is required on GE 1/0/2 on Router B. The number of the multicast group
members in the VSI should be restricted to 1000 and the bandwidth reserved for multicast groups
should be 4000 kbit/s. In addition, you are required to configure Layer 2 multicast CAC for the
channels on the sub-interface, with the number of member multicast groups in the BJTV, NJTV,
and CCTV channels being restricted to 100, 50, and 120 respectively, and bandwidth reserved
for the three channels being 1000 kbit/s, 450 kbit/s, and 2500 kbit/s respectively.
l Channel 1: NJTV, with the multicast group address being 226.1.1.0/24, the channel type
being ASM, and bandwidth reserved for each member multicast group being 3 kbit/s
l Channel 2: BJTV, with the multicast group address being 226.1.2.0/24, the channel type
l Channel 3: CCTV, with the multicast group address being 226.1.3.0/24, the channel type
The sub-interface, GE 1/0/0 on Router A and GE 1/0/2 on Router B, are bound with VSIs
respectively.
Figure 3-11 Networking diagram of Layer 2 multicast CAC for a VSI

GE1/0/1 Loopback 2:2.2.2.2/32
Loopback 1:1.1.1.1/32
192.168.10.2/24 TV Server
GE1/0/2
GE1/0/0
MPLS/
VPLS Internet
GE1/0/1
Switch RouterA RouterB
GE1/0/1
192.168.10.1/24

l Configure the VSI network between Router A and Router B.
l Configure Layer 2 multicast CAC on Router B.
l Configure Layer 2 multicast CAC on Router A.
Data Preparation
l Numbers of the interfaces that bound with the VSIs
l Name of a VSI
Procedure
Step 1 Enable basic MPLS capabilities and LDP on the MPLS backbone network and enable L2VPN.
[RouterA] interface loopback 1
[RouterA-LoopBack1] ip address 1.1.1.1 32
[RouterA-LoopBack1] quit
[RouterA] mpls lsr-id 1.1.1.1
[RouterA] mpls
[RouterA-mpls] mpls ldp
[RouterA-mpls-ldp] quit
[RouterA-mpls] mpls l2vpn
[RouterA-l2vpn] quit
# Configure Router B.
[RouterB] interface loopback 2
[RouterB-LoopBack2] ip address 2.2.2.2 32
[RouterB-LoopBack2] quit
[RouterB] mpls lsr-id 2.2.2.2
[RouterB] mpls
[RouterB-mpls] mpls ldp
[RouterB-mpls-ldp] quit
[RouterB-mpls] mpls l2vpn
[RouterB-l2vpn] quit
Step 2 Create VSIs and specify LDP as the signaling protocol of VSIs.
[RouterA] vsi a static
[RouterA-vsi-a] pwsignal ldp
[RouterA-vsi-a-ldp] vsi-id 1
[RouterA-vsi-a-ldp] peer 2.2.2.2
[RouterA-vsi-a-ldp] quit
[RouterA-vsi-a] quit
[RouterB] vsi a static
[RouterB-vsi-a] pwsignal ldp
[RouterB-vsi-a-ldp] vsi-id 1

[RouterB-vsi-a-ldp] peer 1.1.1.1

[RouterB-vsi-a-ldp] quit
[RouterB-vsi-a] quit
Step 3 Configure IP addresses for GE 1/0/1 on Router A and Router B and enable MPLS on GE 1/0/1.
[RouterA-GigabitEthernet1/0/1] ip address 192.168.10.1 24
[RouterA-GigabitEthernet1/0/1] mpls
[RouterA-GigabitEthernet1/0/1] mpls ldp
[RouterB-GigabitEthernet1/0/1] ip address 192.168.10.2 24
[RouterB-GigabitEthernet1/0/1] mpls
[RouterB-GigabitEthernet1/0/1] mpls ldp
Step 4 Configure OSPF for route advertisement.

[RouterA-ospf-1] a 0
[RouterA-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0
[RouterA-ospf-1-area-0.0.0.0] quit
[RouterB-ospf-1] a 0
[RouterB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[RouterB-ospf-1-area-0.0.0.0] quit
Step 5 Configure sub-interfaces on Routers and bind the sub-interfaces to the VSIs.
[RouterA] interface gigabitethernet 1/0/0.1
[RouterA-GigabitEthernet1/0/0.1] vlan-type dot1q 1
[RouterA-GigabitEthernet1/0/0.1] l2 binding vsi a
[RouterA-GigabitEthernet1/0/0.1] undo shutdown
[RouterA-GigabitEthernet1/0/0.1] quit
[RouterA] interface gigabitethernet 1/0/0.2
[RouterB] interface gigabitethernet 1/0/2.1
[RouterB-GigabitEthernet1/0/2.1] vlan-type dot1q 1
[RouterB-GigabitEthernet1/0/2.1] l2 binding vsi a
[RouterB-GigabitEthernet1/0/2.1] undo shutdown
[RouterB-GigabitEthernet1/0/2.1] quit

# Configure Router A. The configurations on Router B are the same as the configurations on
Router A.


[RouterA] vsi a
[RouterA-vsi-a] igmp-snooping enable
Step 7 Configure Layer 2 multicast CAC for the VSI on Router B.

[RouterB] vsi a
[RouterB-vsi-a] l2-multicast limit max-entry 1000
[RouterB-vsi-a] l2-multicast limit bandwidth 4000
Step 8 Configure restriction on the number and bandwidth of the channels in the VSI.
[RouterA] l2-multicast-channel vsi a
[RouterA-l2-channel-vsi-a] channel njtv type asm
[RouterA-l2-channel-vsi-a-njtv] group 226.1.1.0 255.255.255.0 per-bandwidth 3
[RouterA-l2-channel-vsi-a-njtv] quit
[RouterA-l2-channel-vsi-a] channel bjtv type asm
[RouterA-l2-channel-vsi-a-bjtv] group 226.1.2.0 255.255.255.0 per-bandwidth 4
[RouterA-l2-channel-vsi-a-bjtv] quit
[RouterA-l2-channel-vsi-a] channel cctv type asm
[RouterA-l2-channel-vsi-a-cctv] group 226.1.3.0 255.255.255.0 per-bandwidth 6
[RouterA-l2-channel-vsi-a-cctv] quit
Step 9 Configure Layer 2 multicast CAC on the sub-interface on Router B.

[RouterB-GigabitEthernet1/0/2.1] l2-multicast limit channel bjtv max-entry 100
[RouterB-GigabitEthernet1/0/2.1] l2-multicast limit channel bjtv bandwidth 1000
[RouterB-GigabitEthernet1/0/2.1] l2-multicast limit channel njtv max-entry 50
[RouterB-GigabitEthernet1/0/2.1] l2-multicast limit channel njtv bandwidth 450
[RouterB-GigabitEthernet1/0/2.1] l2-multicast limit channel cctv max-entr 120
[RouterB-GigabitEthernet1/0/2.1] l2-multicast limit channel cctv bandwidth 2500

Run the display ospf peer command, and you can find that OSPF neighbor relationship is set
up.
[RouterA] display ospf peer
OSPF Process 1 with Router ID 1.1.1.1

Neighbors
Area 0.0.0.0 interface 192.168.10.1(GigabitEthernet1/0/1)'s neighbors

Router ID: 2.2.2.2 Address: 192.168.10.2
State: Full Mode:Nbr is Master Priority: 1
DR: 192.168.10.1 BDR: 192.168.10.2 MTU: 0
Dead timer due in 30 sec
Neighbor is up for 00:19:44
Authentication Sequence: [ 0 ]
Run the display vsi name a verbose command and find that the VSI status is Up.
Take the display on Router A as an example.
[RouterA] display vsi name a verbose
***VSI Name : a
Administrator VSI : no
Isolate Spoken : disable
VSI Index : 0
PW Signaling : ldp

Member Discovery Style : static

PW MAC Learn Style : unqualify
Encapsulation Type : vlan
MTU : 1500
Diffserv Mode : uniform
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1
*Peer Router ID : 2.2.2.2
VC Label : 23552
Peer Type : dynamic
Session : up
Tunnel ID : 0x802000
Interface Name : GigabitEthernet1/0/0.2

State : up
State : up
**PW Information:
*Peer Ip Address : 2.2.2.2

PW State : up
Local VC Label : 23552
Remote VC Label : 23552
PW Type : label
FIB Link-ID : 1
2 multicast CAC.
Take the display on Router B as an example:
[RouterB] display l2-multicast limit configuration
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
1000 4000
---- --------
---------------------------------------------------------------------
1000 4000
---- --------
---------------------------------------------------------------------
bjtv 100 1000
---- --------
---------------------------------------------------------------------
cctv 120 2500
---- --------
---------------------------------------------------------------------
njtv 50 450
---- --------
Run the display l2-multicast-channel vsi a command to check configurations of restriction on

the channels in VSI a.

[RouterB] display l2-multicast-channel vsi a

ChannelName Group/Mask Source/Mask Bandwidth
-------------------------------------------------------------------------------
bjtv 226.1.2.0/24 * 4
-------------------------------------------------------------------------------
cctv 226.1.3.0/24 * 6
-------------------------------------------------------------------------------
njtv 226.1.1.0/24 * 3
----End
Configuration Files
#
sysname RouterA
#
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi a static
pwsignal ldp
vsi-id 1
peer 2.2.2.2
#
mpls ldp
#
undo shutdown
#
interface GigabitEthernet1/0/0.1
undo shutdown
vlan-type dot1q 1
l2 binding vsi a
#
undo shutdown
vlan-type dot1q 2
l2 binding vsi a
#
undo shutdown
ip address 192.168.10.1 255.255.255.0
mpls
mpls ldp
interface NULL0
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 192.168.10.0 0.0.0.255
#
l2-multicast-channel vsi a
channel bjtv
channel cctv
channel njtv

#
return
#
sysname RouterB
#
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi a static
pwsignal ldp
vsi-id 1
peer 1.1.1.1
#
mpls ldp
#
undo shutdown
ip address 192.168.10.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
mpls
mpls ldp
#
undo shutdown
vlan-type dot1q 1
l2 binding vsi a
l2-multicast limit channel bjtv max-entry 100
l2-multicast limit channel bjtv bandwidth 1000
l2-multicast limit channel njtv max-entry 50
l2-multicast limit channel njtv bandwidth 450
l2-multicast limit channel cctv max-entr 120
l2-multicast limit channel cctv bandwidth 2500
#
undo shutdown
vlan-type dot1q 2
l2 binding vsi a
#
interface NULL0
#
interface LoopBack2
ip address 2.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 192.168.10.0 0.0.0.255
#
l2-multicast-channel
#
channel cctv type asm
channel njtv type asm

#
return
3.15.8 Example for Configuring Layer 2 Multicast CAC for a PW

This section provides a typical PW networking and a specific configuration example for
describing configurations about multicast CAC on a PW in details.
As shown in Figure 3-12, Router A and Router B are connected through a PW and LDP is set
to be the signaling protocol used by the PW. To save network bandwidth between Routers and
ensure the quality of the IPTV service, you are recommended to configure global Layer 2
multicast CAC on Router B, with the number of multicast group members being restricted to
650 and bandwidth reserved for multicast groups being 3000 kbit/s.
A channel SHTV is configured in the VSI, with the multicast address being 225.0.0.1, the channel
type being ASM, and the bandwidth configured for each multicast group member of the channel
being 3 kbit/s. The maximum number of multicast groups on a PW is 650, the bandwidth for the
multicast group is 3000 kbit/s, the number of multicast groups in the channel SHTV is 50, and
the bandwidth for the multicast group in the channel SHTV is 300 kbit/s.
The interval for sending the same multicast CAC-related trap message is set to 40 seconds.
Figure 3-12 Networking diagram of Layer 2 multicast CAC for a PW
Loopback 1:1.1.1.1/32 Loopback 2:2.2.2.2/32 TV Server

GE1/0/1
RouterB GE1/0/2
192.168.10.1/24
RouterA PW Tunnel Internet
GE1/0/0
GE1/0/1
192.168.10.2/24
Switch
l Establish a PW between Router A and Router B.
l Configure Layer 2 multicast CAC on Router B.
l Configure Layer 2 multicast CAC for the PW.

Data Preparation
l Numbers and IP addresses of the two ends of the PW connecting Router A and Router B
l Name of a VSI
Procedure
Step 1 Configure an IP address for each interface.
On Router A and Router B, create loopback interfaces respectively on Router A and Router B
and configure an IP address for each interface. The detailed configuration is not mentioned here.
Step 2 Configure IP addresses for GE 1/0/1 on Router A and Router B and enable MPLS on GE 1/0/1.
[RouterA-GigabitEthernet1/0/1] ip address 192.168.10.1 24
[RouterA-GigabitEthernet1/0/1] mpls
[RouterA-GigabitEthernet1/0/1] mpls ldp
[RouterB-GigabitEthernet1/0/1] ip address 192.168.10.2 24
[RouterB-GigabitEthernet1/0/1] mpls
[RouterB-GigabitEthernet1/0/1] mpls ldp
Step 3 Configure OSPF.

Enable OSPF to advertise routes in each network segment. Run the display ip routing-table
command and you can view that Router A and Router B have learnt addresses of loopback
interfaces from each other. For details, see configuration files.
# Take the display on Router A as an example:
[RouterA] display ip routing-table
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 6 Routes : 6
Destination/Mask Proto Pre Cost Flags NextHop Interface

2.2.2.2/32 OSPF 10 1 D 192.168.10.2
GigabitEthernet1/0/1
192.168.10.0/24 Direct 0 0 D 192.168.10.1
Step 4 Configure MPLS networks on Router A and Router B, set up a PW between Router A and
Router B, with LDP being the signaling protocol, and enable MPLS L2VPN.

[RouterA] mpls lsr-id 1.1.1.1

[RouterA] mpls
[RouterA-mpls] mpls ldp
[RouterA-mpls-ldp] quit
[RouterA-mpls] mpls l2vpn
[RouterA-l2vpn] quit
[RouterB] mpls lsr-id 2.2.2.2
[RouterB] mpls
[RouterB-mpls] mpls ldp
[RouterB-mpls-ldp] quit
[RouterB-mpls] mpls l2vpn
[RouterB-l2vpn] quit
Step 5 Configure VSIs.

[RouterA] vsi a static
[RouterA-vsi-a] pwsignal ldp
[RouterA-vsi-a-ldp] vsi-id 1
[RouterA-vsi-a-ldp] peer 2.2.2.2
[RouterA-vsi-a-ldp] quit
[RouterA-vsi-a] quit
[RouterB-vsi-a-ldp] vsi-id 1
[RouterB-vsi-a-ldp] peer 1.1.1.1
[RouterB-vsi-a-ldp] quit
[RouterB-vsi-a] quit
Step 6 Bind VSIs and sub-interfaces on Router A and Router B.

[RouterA] interface gigabitethernet1/0/0.1
[RouterB] interface gigabitethernet1/0/2.1

# Configure Router A. The configurations on Router B are the same as the configurations on
Router A.
[RouterA] vsi a
[RouterA-vsi-a] igmp-snooping enable
Step 8 Configure global Layer 2 multicast CAC on Router B.

[RouterB] l2-multicast limit max-entry 650

[RouterB] l2-multicast limit bandwidth 3000
Step 9 Configure restriction on the number and bandwidth of the channel SHTV in the VSI.
[RouterB] l2-multicast-channel vsi a
[RouterB-l2-channel-vsi-a] channel shtv type asm
[RouterB-l2-channel-vsi-a-njtv] group 225.0.0.1 255.255.255.0 per-bandwidth 3
[RouterB-l2-channel-vsi-a-njtv] quit
Step 10 Configure Layer 2 multicast CAC for the PW.

[RouterB-vsi-a-ldp] l2-multicast limit max-entry 650 remote-peer 1.1.1.1
[RouterB-vsi-a-ldp] l2-multicast limit bandwidth 3000 remote-peer 1.1.1.1
[RouterB-vsi-a-ldp] l2-multicast limit channel shtv max-entry 50 remote-peer
1.1.1.1
[RouterB-vsi-a-ldp] l2-multicast limit channel shtv bandwidth 300 remote-peer
1.1.1.1
Step 11 On Router A, set the interval for sending the same multicast CAC-related trap message to 40
seconds.
[RouterA] l2-multicast limit trap-interval 40

Run the display vsi name a verbose command and you can view that the VSI named a is Up
and the corresponding PW is also Up.
[RouterB] display vsi name a verbose
***VSI Name : a
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
VSI State : up
VSI ID : 1
VC Label : 23552
Peer Type : dynamic
Session : up
State : up
**PW Information:
*Peer Ip Address : 1.1.1.1
PW State : up
Local VC Label : 23552
Remote VC Label : 23552
PW Type : label

Run the display mpls ldp session command, and you can find that peer relationship is set up.
[RouterA] display mpls ldp session
LDP Session(s) in Public Network
------------------------------------------------------------------------------
Peer-ID Status LAM SsnRole SsnAge KA-Sent/Rcv
------------------------------------------------------------------------------
2.2.2.2:0 Operational DU Passive 000:00:00 1/1
------------------------------------------------------------------------------
TOTAL: 1 session(s) Found.
LAM : Label Advertisement Mode SsnAge Unit : DDD:HH:MM
2 multicast CAC.
[RouterB] display l2-multicast limit configuration
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
650 3000
---- ----------
PW(Peer:1.1.1.1, VCID:1) limit information:
----------------------------------------------------------------------------
650 3000
---- ----------
PW(Peer:1.1.1.1, VCID:1) channel limit information:
------------------------------------------------------------------------------
shtv 50 300
---- ----------
----End
Configuration Files
#
sysname RouterA
#
l2-multicast limit trap-interval 40
#
mpls lsr-id 1.1.1.1
mpls
#
mpls l2vpn
#
vsi a static
pwsignal ldp
vsi-id 1
peer 2.2.2.2
#
mpls ldp
#
interface Ethernet1/0/0
undo shutdown
#
vlan-type dot1q 1
undo shutdown

l2 binding vsi a
#
undo shutdown
ip address 192.168.10.1 255.255.255.0
mpls
mpls ldp
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 192.168.10.0 0.0.0.255
#
return
#
sysname RouterB
#
#
mpls lsr-id 2.2.2.2
mpls
#
mpls l2vpn
#
vsi a static
pwsignal ldp
vsi-id 1
peer 1.1.1.1
l2-multicast limit max-entry 650 remote-peer 1.1.1.1
l2-multicast limit bandwidth 3000 remote-peer 1.1.1.1
l2-multicast limit channel shtv max-entry 50 remote-peer 1.1.1.1
l2-multicast limit channel shtv bandwidth 300 remote-peer 1.1.1.1
#
mpls ldp
#
undo shutdown
ip address 192.168.10.2 255.255.255.0
mpls
mpls ldp
#
undo shutdown
#
undo shutdown
vlan-type dot1q 1
l2 binding vsi a
#
interface LoopBack2
ip address 2.2.2.2 255.255.255.255
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 192.168.10.0 0.0.0.255
#
l2-multicast-channel
#
channel shtv type asm

#
return
3.15.9 Example for Configuring Layer 2 Multicast SSM Mapping
As shown in Figure 3-13, PE1 is connected to PE2 through GE 1/0/0. They both belong to
VLAN 10. GE 1/0/0 on PE2 is a static router port and statically joins the multicast group
224.1.1.1.
IGMPv3 is run on PE1 while IGMPv2 is run on PE2.
Then, SSM mapping needs to be configured on PE1 so that PE1 can map the multicast group
addresses of the received packets with no source addresses to specific sources. In addition, the
querier function is required for VLAN 10 on PE1 to enable PE1 to send Query messages
periodically to PE2.
Figure 3-13 Networking diagram of Layer 2 multicast SSM mapping
VLAN10
PE1 PE2
GE1/0/0 GE1/0/0
SSM Mapping
1. Create VLANs and enable basic IGMP snooping functions.
2. Configure the versions of IGMP snooping running on PE1 and PE2.
3. Enable the querier function for VLAN 10 on PE1.
4. Configure GE 1/0/0 on PE2 as a static router port and statically add GE 1/0/0 to the multicast
group 224.1.1.1.
5. Configure an IGMP snooping SSM policy.
Data Preparation
l VLAN ID

l IGMP snooping version number

l Static multicast group address
Procedure
Step 1 Create VLANs.
# Configure PE1.
<HUAWEI> system-view
[HUAWEI] sysname PE1
[PE1] interface gigabitethernet1/0/0
[PE1] vlan 10
[PE1-vlan10] port gigabitethernet 1/0/0
[PE1-vlan10] quit
# Configure PE2.
[HUAWEI] sysname PE2
[PE2] vlan 10
[PE2-vlan10] port gigabitethernet 1/0/0
[PE2-vlan10] quit
Step 2 Enable global IGMP snooping and IGMP snooping in a VLAN.
# Configure PE1.
[PE1] vlan 10
[PE1-vlan10]igmp-snooping enable
# Configure PE2.
[PE2] vlan 10
[PE2-vlan10]igmp-snooping enable
[PE2-vlan10]igmp-snooping proxy enable
Step 3 Configure the versions of IGMP snooping running on PE1 and PE2.
# Configure PE1.
[PE1-vlan10] igmp-snooping version 3
# Configure PE2.
[PE2-vlan10] igmp-snooping version 2
Step 4 Enable the querier function for VLAN 10 on PE1 so that PE1 can send general Query messages
to PE2.
[PE1] igmp-snooping send-query enable
[PE1] vlan 10
[PE1-vlan10] igmp-snooping querier enable
[PE1-vlan10] quit
Step 5 Statically add GE 1/0/0 on PE2 to the multicast group with the source address being 10.1.1.1
and group address being 224.1.1.1.

[PE2-GigabitEthernet1/0/0] igmp-snooping static-router-port vlan 10

[PE2-GigabitEthernet1/0/0] l2-multicast static-group group-addre
ss 224.1.1.1 vlan 10
Step 6 Configure an IGMP snooping SSM policy.

[PE1] acl number 2008
[PE1-acl-basic-2008] rule 5 permit source 224.1.1.1 0
[PE1-acl-basic-2008] quit
[PE1] vlan 10
[PE1-vlan10] igmp-snooping ssm-policy 2008
[PE1-vlan10] igmp-snooping ssm-mapping enable
[PE1-vlan10] igmp-snooping ssm-mapping 224.1.1.1 24 10.1.1.2

# On PE1, run the display igmp-snooping vlan configuration command to check
configurations about the VLAN.
[PE1] display igmp-snooping vlan configuration
IGMP Snooping Configuration for VLAN 10
IGMP Querier Enable
igmp-snooping ssm-policy 2008
igmp-snooping ssm-mapping 224.1.1.0 255.255.255.0 10.1.1.2
# After PE1 receives a Report message, run the display igmp-snooping port-info command to
check configurations about the interface.
[PE1] display igmp-snooping port-info
-----------------------------------------------------------------------
-----------------------------------------------------------------------
VLAN 10, 3 Entry(s)
(10.1.1.2, 224.1.1.1) GE1/0/0 --M
1 port(s)
(10.1.1.3, 224.1.1.1) GE1/0/0 --M
1 port(s)
(10.1.1.4, 224.1.1.1) GE1/0/0 --M
1 port(s)
-----------------------------------------------------------------------
# On PE2, run the display l2-multicast forwarding-table command to check information on

the multicast forwarding table.
[PE2] display l2-multicast forwarding-table vlan 10
VLAN ID : 10, Forwarding Mode : IP
--------------------------------------------------------------------
--------------------------------------------------------------------
Router-port Ok No 0 1
(*, 224.1.1.1) Ok No 1 2
--------------------------------------------------------------------
Total Entry(s) : 2
----End
Configuration Files
#
sysname PE1

#
vlan batch 10
#
#
vlan 10
igmp-snooping ssm-policy 2008
#
acl number 2008
rule 5 permit source 224.1.1.1 0
#
undo shutdown
portswitch
#
return

#
sysname PE2
#
vlan batch 10
#
#
vlan 10
igmp-snooping proxy enable
#
undo shutdown
portswitch
#
return
3.15.10 Example for Configuring Multicast CAC on a Sub-interface

for VLAN Tag Termination
As shown in Figure 3-14, PE accesses the upper network through a VSI.
QinQ VLAN tag termination is configured on GE 1/0/0.1 of PE. Then, multicast CAC needs to
be configured in the sub-interface view, with the number of multicast groups being limited to
650 and bandwidth of the multicast groups being limited to 3000.
Dot1q VLAN tag termination is configured on GE1/0/0.2 of PE and a global channel CCTV is
created, adopting the SSM model. Then, channel-based multicast CAC needs to be configured
in the sub-interface view, with the number of member multicast groups in the CCTV channel
being limited to 50 and bandwidth of the channel being limited to 300.

Figure 3-14 Networking diagram of multicast CAC on a sub-interface for VLAN tag termination
PE
Internet/
Intranet
GE1/0/0.2
Dot1q termination GE1/0/0.1
QinQ termination
CE
Group Number
1. Enable global IGMP snooping.
2. Configure basic MPLS functions on PE and bind the sub-interfaces on PE to the VSI.
3. Enable IGMP snooping in the VSI and configure the IGMP snooping version number.
4. Configure the QinQ VLAN tag termination mode on GE 1/0/0.1.
5. Configure global multicast CAC on GE 1/0/0.1.
6. Configure the dot1q VLAN tag termination mode on GE 1/0/0.2.
7. Configure channel-based multicast CAC on GE 1/0/0.2.
Data Preparation
l Version of IGMP snooping running on PE
l VSI name and the numbers of the sub-interfaces to which the VSI is bound
l VLAN ID terminated by GE 1/0/0.1
l VLAN ID terminated by GE 1/0/0.2
l Parameters related to multicast CAC, including the number of multicast groups, bandwidth
of multicast groups, number of member multicast groups in the channel, and bandwidth of
the channel
Procedure

[HUAWEI] sysname PE
[PE] igmp-snooping enable
Step 2 Configure basic MPLS functions.

[PE] mpls lsr-id 1.1.1.1
[PE] mpls
[PE-mpls] quit
[PE] mpls ldp
[PE-mpls-ldp] quit
[PE] interface gigabitethernet 1/0/1
[PE-GigabitEthernet1/0/1] mpls
[PE-GigabitEthernet1/0/1] mpls ldp
[PE-GigabitEthernet1/0/1] quit
[PE] mpls l2vpn
[PE-l2vpn] quit
[PE] vsi a static
[PE-vsi-a] pwsignal ldp
[PE-vsi-a-ldp] vsi-id 2
[PE-vsi-a-ldp] peer 2.2.2.2
[PE-vsi-a-ldp] quit
[PE-vsi-a] quit
Step 3 Enable basic IGMP snooping functions in the VSI and configure the IGMP snooping version
number.
[PE] vsi a static
[PE-vsi-a] igmp-snooping enable
[PE-vsi-a] igmp-snooping version 3
Step 4 Configure the QinQ VLAN tag termination mode on GE 1/0/0.1 and bind GE 1/0/0.1 to the VSI.
[PE] interface gigabitethernet 1/0/0
[PE-GigabitEthernet1/0/0] mode user-termination
[PE-GigabitEthernet1/0/0] quit
[PE] interface gigabitethernet 1/0/0.1
[PE-GigabitEthernet1/0/0.1] control-vid 1 qinq-termination
[PE-GigabitEthernet1/0/0.1] qinq termination pe-vid 10 ce-vid 100 to 200
[PE-GigabitEthernet1/0/0.1] l2 binding vsi a
[PE-GigabitEthernet1/0/0.1] undo shutdown
[PE-GigabitEthernet1/0/0.1] quit
Step 5 Configure the dot1q VLAN tag termination mode on GE 1/0/0.2 and bind GE 1/0/0.2 to the VSI.
[PE-GigabitEthernet1/0/0.2] control-vid 2 dot1q-termination
[PE-GigabitEthernet1/0/0.2] dot1q termination vid 50 to 90
[PE-GigabitEthernet1/0/0.2] l2 binding vsi a
[PE-GigabitEthernet1/0/0.2] undo shutdown
[PE-GigabitEthernet1/0/0.2] quit
Step 6 Configure multicast CAC on the two sub-interfaces for VLAN tag termination.
# Configure the sub-interface for QinQ VLAN tag termination.
[PE-GigabitEthernet1/0/0.1] l2-multicast limit max-entry 650 qinq pe-vid 10 ce-vid
100 to 102
[PE-GigabitEthernet1/0/0.1] l2-multicast limit bandwidth 3000 qinq pe-vid 10 ce-vid
100 to 102
# Configure the sub-interface for dot1q VLAN tag termination.

[PE] l2-multicast-channel
[PE-l2-channel-glb] channel cctv type ssm
[PE-l2-channel-glb-cctv] group 232.0.0.0 255.255.255.0 source 10.1.1.0
255.255.255.0 per-bandwidth 20
[PE-l2-channel-glb-cctv] quit
[PE-l2-channel-glb] quit
[PE-GigabitEthernet1/0/0.2] l2-multicast limit channel cctv max-entry 50 dot1q vid
50 to 52

[PE-GigabitEthernet1/0/0.2] l2-multicast limit channel cctv bandwidth 300 dot1q

vid 50 to 52

# Run the display vsi name a verbose command, and you can view that the VSI named a is Up.
[PE-GigabitEthernet1/0/0.2] display vsi name a verbose
***VSI Name : a
VSI Index : 0
PW Signaling : ldp
MTU : 1500
Service Class : --
Color : --
DomainId : 255
Domain Name :
Create Time : 0 days, 6 hours, 42 minutes, 26 seconds
VSI State : up
VSI ID : 2
VC Label : 162816
Peer Type : dynamic
Session : down
Tunnel ID :

State : up
Last Up Time : 2009/03/18 11:06:06
Total Up Time : 0 days, 5 hours, 2 minutes, 47 seconds
State : up
Last Up Time : 2009/03/18 11:07:44
Total Up Time : 0 days, 5 hours, 1 minutes, 9 seconds
# After PE receives a Report message, run the display igmp-snooping port-info command to
check configurations about the interface.
[PE] display igmp-snooping port-info
-----------------------------------------------------------------------
-----------------------------------------------------------------------
VSI a, 3 Entry(s)
(10.1.1.2, 232.0.0.1) GE1/0/0.2(PE:50) -D-
1 port(s)
(10.1.1.3, 232.0.0.1) GE1/0/0.2(PE:51) -D-
1 port(s)
(10.1.1.1, 232.1.1.1) GE1/0/0.1(PE:10/CE:100) -D-
1 port(s)
-----------------------------------------------------------------------
# Run the display l2-multicast limit configuration command to check configurations and
statistics about multicast CAC.
[PE] display l2-multicast limit
L2-multicast limit information, The unit of bandwidth is Kbits/sec
------------------------------------------------------------------------------
------------------------------------------------------------------------------
interface GigabitEthernet1/0/0.1 qinq pe-vid 10 ce-vid 100 limit information:
------------------------------------------------------------------------------
650 3000

1 0
------------------------------------------------------------------------------
650 3000
0 0
------------------------------------------------------------------------------
650 3000
0 0
interface GigabitEthernet1/0/0.2 dot1q vid 50 channel limit information:
------------------------------------------------------------------------------
cctv 50 300
1 20
------------------------------------------------------------------------------
cctv 50 300
1 20
------------------------------------------------------------------------------
cctv 50 300
0 0
----End
Configuration Files
l Configuration file of PE
#
sysname
PE
#
igmp-snooping
enable
#
mpls lsr-id
1.1.1.1
mpls
#
mpls
l2vpn
#
vsi a
static
pwsignal
ldp
vsi-id
2
peer
2.2.2.2
igmp-snooping
enable
igmp-snooping version
3
#
mpls
ldp
#
interface
undo
shutdown
mode user-
termination
#
interface
GigabitEthernet1/0/0.1
control-vid 1 qinq-

termination
qinq termination pe-vid 10 ce-vid 100 to
200
l2 binding vsi
a
l2-multicast limit max-entry 650 qinq pe-vid 10 ce-vid 100 to
102
l2-multicast limit bandwidth 3000 qinq pe-vid 10 ce-vid 100 to
102
#
interface
GigabitEthernet1/0/0.2
control-vid 2 dot1q-
termination
dot1q termination vid 50 to
90
l2 binding vsi
a
l2-multicast limit channel cctv max-entry 50 dot1q vid 50 to
52
l2-multicast limit channel cctv bandwidth 300 dot1q vid 50 to
52
#
interface
undo
shutdown
ip address 200.1.1.1
255.255.255.252
mpls
mpls
ldp
#
interface
LoopBack1
ip address 1.1.1.1
255.255.255.255
#
ospf
1
area
0.0.0.0
network 1.1.1.1
0.0.0.0
network 200.1.1.0
0.0.0.3
#
l2-multicast-
channel
channel cctv type
ssm
group 232.0.0.0 255.255.255.0 source 10.1.1.0 255.255.255.0 per-bandwidth
20
#
return

Configuration Guide - IP Multicast 4 PIM-DM (IPv4) Configuration
4 PIM-DM (IPv4) Configuration
About This Chapter
This chapter describes the PIM-DM (IPv4) fundamentals, configuration steps, and maintenance
for PIM-DM functions, along with typical examples.
4.1 PIM-DM (IPv4) Introduction
This section describes basic principles of PIM-DM.
4.2 Configuring Basic PIM-DM Functions
This section describes how to configure basic PIM-DM functions.
4.3 Adjusting Control Parameters of a Multicast Source
This section describes how to control the forwarding of multicast data based on the multicast
source in a PIM network.
4.4 Adjusting Control Parameters for Maintaining Neighbor Relationships
This section describes how to configure control parameters of a PIM-DM Hello message.
4.5 Adjusting Control Parameters for Prune
This section describes how to configure control parameters of a PIM-DM Join/Prune message.
4.6 Adjusting Control Parameters for State-Refresh
This section describes how to configure control parameters of a PIM-DM State-Refresh message.
4.7 Adjusting Control Parameters for Graft
This section describes how to configure control parameters of a PIM-DM Graft message.
4.8 Adjusting Control Parameters for Assert
This section describes how to configure control parameters of a PIM-DM Assert message.
4.9 Configuring PIM Silent
This section describes how to configure PIM silent to prevent the attack of a malicious host.
4.10 Maintaining PIM
This section describes how to clear the statistics of PIM-DM and monitor the running status of
PIM-DM.
4.11 Configuration Example
This section provides several configuration examples of PIM-DM.

4 PIM-DM (IPv4) Configuration Configuration Guide - IP Multicast
4.1 PIM-DM (IPv4) Introduction

This section describes basic principles of PIM-DM.
4.1.1 PIM-DM Overview
4.1.2 PIM-DM Features Supported by the NE80E/40E
4.1.1 PIM-DM Overview
CAUTION
This chapter is concerned only about the PIM-DM configuration in an IPv4 network.
The Protocol Independent Multicast (PIM) is a multicast protocol that is independent of unicast
routing protocol such as static route, RIP, OSPF, IS-IS, and BGP. Multicast routing is
independent of unicast routing protocols, except that unicast routing protocols are used to
generate related multicast routing entries.
Based on the Reverse Path Forwarding (RPF), PIM transmits multicast data across a network.
RPF constructs a multicast forwarding tree by using the existing unicast routing information.
When a multicast packet reaches a router, the router performs the RPF check first. If the packet
does not pass the RPF check, the router directly discards the packet.
NOTE
For more details of RPF, refer to the chapter IPv4 Multicast Routing Management in the HUAWEI
The Protocol Independent Multicast-Dense Mode (PIM-DM) is a multicast routing protocol of

dense node. It is applicable to a small-scale network with densely-distributed members.
The functions and location of PIM-DM in a multicast network are shown in Figure 4-1.
Figure 4-1 Location of PIM-DM in the multicast network
IGMP
Receiver
UserA
PIM-DM
Source
Receiver
UserB
Multicast
PIM-DM
Server
PIM-DM IGMP
Receiver
UserC
UserD

The Protocol Independent Multicast-Sparse Mode (PIM-SM) is applicable to a large-scale

network with sparsely-distributed members. For details of PIM-SM, refer to the chapter PIM-
SM (IPv4) Configuration in the HUAWEI NetEngine80E/40E Router Configuration Guide -
IP Multicast.
Controlling the Forwarding of a Multicast Source

You can configure the Keepalive period of a multicast source and the filtering rules based on
multicast sources.
Adjusting Control Parameters for Setting Up Neighbor Relationship

You can set the following control parameters:
l The interval for sending Hello messages
l The period for keeping neighbors reachable
l Whether the Hello messages without the Generation ID option are received
l The maximum delay for triggering Hello messages
l Neighbor filtering function: An interface sets up neighbor relationships with only the
addresses matching the filtering rules and deletes the neighbors unmatched with the filtering
rules.
Adjusting Control Parameters for Pruning

You can adjust the following control parameters for pruning:
l The interval for keeping the Prune state of the downstream interface
l The delay from the time when the current router receives a Prune message from a
downstream router to the time when the current router performs the prune action in the
LAN
l The period for overriding the prune action
Adjusting Control Parameters for State-Refresh

You can enable or disable State-Refresh, set the interval for sending PIM State-Refresh
messages, set the minimum interval for receiving the next State-Refresh message, and set the
TTL value for forwarding State-Refresh messages on the router directly connected to the source.
Adjusting Control Parameters for Graft

You can set the interval for retransmitting Graft messages.
Adjusting Control Parameters for Assert

You can set the period for a router to retain the Assert state. The router that fails in the election
prevents the downstream interface from forwarding multicast data during this period. After the
period expires, the downstream interface continues to forward multicast data.

Configuring PIM Silent

On the access layer, the router interface directly connected to hosts needs to be enabled with
PIM. You can establish a PIM neighbor on the router interface to process various PIM packets.
The configuration, however, has the security vulnerability. When a host maliciously generates
PIM Hello packets and sends the packets in large quantity, the router may break down.
To prevent the preceding case, you can set the status of the router interface to PIM silent. When
the interface is in the PIM silent state, the interface is prohibited from receiving and forwarding
any PIM packet. Then all PIM neighbors and PIM state machines on the interface are deleted.
The interface acts as the static DR and immediately takes effect. At the same time, IGMP on the
interface are not affected.
PIM Multi-instance
In multi-instance applications, multicast routers need to maintain the PIM neighbor list and
multicast routing table for different VPN instances and keep the information independent among
multiple instances.
When a router receives a multicast data packet, the router needs to distinguish the VPN instance
to which the packet belongs and forward the packet based on the multicast routing table of the
specific VPN instance, or create a PIM multicast routing entry of the VPN instance.
4.2 Configuring Basic PIM-DM Functions

This section describes how to configure basic PIM-DM functions.
4.2.2 Enabling IPv4 Multicast Routing
4.2.3 Enabling PIM-DM
PIM-DM is applicable to a small-scale network, and most network segments of the network have
receivers.
Before configuring basic PIM-DM functions, complete the following configuration tasks:
l Configuring an IPv4 unicast routing protocol
Data Preparation
To configure basic PIM-DM functions, you need the following data.

No. Data
1 Type and number of an interface
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
IPv4 multicast routing is enabled in the public network.
CAUTION
The configuration related to the VPN instance is applicable only to the PE router. If the interface
of the VPN instance connects to hosts, run the commands in Step 3 and Step 4.


IPv4 multicast routing is enabled in the VPN instance.
----End
4.2.3 Enabling PIM-DM
Context
NOTE
PIM-SM and PIM-DM cannot be enabled on an interface at the same time. The PIM mode must be the
same on all the interfaces of the same instance. When routers are distributed in different PIM-DM domains,
enable PIM-SM on all non-boundary interfaces.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim dm
PIM-DM is enabled.
After PIM-DM is enabled on the interface and the PIM neighbor relationship is set up between
routers, the protocol packets sent by the PIM neighbors can be processed. You can run the undo
pim dm command to disable PIM-DM on the interface.
----End
Procedure
l Run the command display pim [ vpn-instance vpn-instance-name | all-instance ]
interface [ interface-type interface-number | up | down ] [ verbose ] to check PIM on
interfaces of the public network, VPN instance, or all instances.
neighbor [ neighbor-address | interface interface-type interface-number | verbose ] * to
check PIM neighbors of the public network, VPN instance, or all instances.
l Run the following commands to check the PIM routing table of the public network, VPN
instance, or all instances.
– display pim { vpn-instance vpn-instance-name | all-instance } routing-table [ group-
address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-
mask-length | source-mask } ] | incoming-interface { interface-type interface-
number | register } | outgoing-interface { include | exclude | match } { interface-type
interface-number | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ]
* [ outgoing-interface-number [ number ] ]
– display pim routing-table [ group-address [ mask { group-mask-length | group-

mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-
interface { interface-type interface-number | register } | outgoing-interface
{ include | exclude | match } { interface-type interface-number | vpn-instance vpn-
instance-name | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ] *
[ outgoing-interface-number [ number ] ]
– display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table brief
[ group-address [ mask { group-mask-length | group-mask } ] | source-address
[ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type
interface-number | register } ] *
----End

Example
Run the display pim interface verbose command, and you can view the detailed information
about PIM on the interface in the public network instance.
<HUAWEI> display pim interface verbose
Interface: Ethernet2/0/12, 12.40.41.2
PIM version: 2
PIM mode: Dense
PIM state: up
PIM DR: 12.40.41.2 (local)
PIM DR Priority (configured): 1
PIM neighbor count: 1
PIM hello interval: 120 s
PIM LAN delay (negotiated): 500 ms
PIM LAN delay (configured): 100 ms
PIM hello override interval (negotiated): 2500 ms
PIM hello override interval (configured): 2500 ms
PIM Silent: enabled
PIM neighbor tracking (negotiated): disabled
PIM neighbor tracking (configured): disabled
PIM generation ID: 0XC34B2FCD
PIM require-GenID: disabled
PIM hello hold interval: 60 s
PIM hello assert interval: 180 s
PIM triggered hello delay: 5 s
PIM J/P interval: 60 s
PIM J/P hold interval: 200 s
PIM state-refresh processing: enabled
PIM state-refresh interval: 60 s
PIM graft retry interval: 3 s
PIM state-refresh capability on link: capable
PIM dr-switch-delay timer : not configured
Number of routers on network not using DR priority: 0
Number of routers on network not using LAN delay: 0
Number of routers on link not using neighbor tracking: 1
Run the display pim neighbor verbose command, and you can view the detailed information
about PIM neighbors in the public network instance.
<HUAWEI> display pim neighbor verbose
Total Number of Neighbors = 1
Neighbor: 12.40.41.1
Interface: Ethernet2/0/12
Uptime: 00:20:19
Expiry time: 00:01:27
DR Priority: 1
Generation ID: 0XB3DDAD78
Holdtime: 105 s
LAN delay: 500 ms
Override interval: 2500 ms
State refresh interval: 60 s
Neighbor tracking: Disabled
4.3 Adjusting Control Parameters of a Multicast Source

This section describes how to control the forwarding of multicast data based on the multicast
source in a PIM network.
4.3.2 Configuring the Lifetime of a Source
4.3.3 Configuring Filtering Rules Based on Source Addresses


This configuration is applicable to all PIM-DM networks.
A PIM router checks the passing multicast data. By checking whether the data matches the
filtering rule, the router determines whether to forward the data. In this case, you can regard the
router as the filter of the multicast data. The filter helps to control the data flow and limit the
information that downstream receivers can obtain. Network security is thus ensured.
Before configuring control parameters of a multicast source, complete the following tasks:
l Configuring Basic PIM-DM Functions
Data Preparation
To configure control parameters of a multicast source, you need the following data.
No. Data
1 Keepalive period of a multicast source
2 Filtering rules of multicast source addresses
Context
Do as follows on the first next hop router connected to the source:
NOTE
If there is no special requirement, default values are recommended.
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim [ vpn-instance vpn-instance-name ]
The PIM view is displayed.

Step 3 Run:
source-lifetime interval

The lifetime of a source is set.

If a router does not receive any (S, G) packet in the lifetime of the source, the router considers
that the source stops sending multicast data to G and the (S, G) entry becomes invalid.
When State-Refresh is enabled, the lifetime of the multicast source is prolonged to about the
value of interval.
----End
Context
Do as follows on the PIM router:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
source-policy { acl-number | acl-name acl-name }
The filter is configured.

The effect of the filtering is more obvious if the filter is closer to the source.
If the basic ACL is configured, only the packets with the source addresses that pass the filtering
are forwarded.
If the advanced ACL is configured, only the packets with the source addresses and group
addresses that pass the filtering are forwarded.
NOTE
l If acl-number | acl-name acl-name is specified in the source-policy command and ACL rules are
created, only the multicast packets whose source addresses match the ACL rules are permitted.
l If acl-number | acl-name acl-name is specified in the source-policy command and no ACL rule is
created, the multicast packets with any source addresses are not forwarded.
l The source-policy command does not filter the static (S, G) entries and the PIM entries of the Join
messages received from private networks.
----End

Procedure
l Run the following commands to check the PIM routing table.


number | register } | outgoing-interface { include | exclude | match } { interface-type
interface-number | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ]
* [ outgoing-interface-number [ number ] ]

----End
4.4 Adjusting Control Parameters for Maintaining Neighbor

Relationships
This section describes how to configure control parameters of a PIM-DM Hello message.
4.4.2 Configuring the Interval for Sending Hello Messages
4.4.3 Configuring the Timeout Period of a Neighbor
4.4.4 Refusing to Receive the Hello Message Without the Generation ID Option
4.4.5 Configuring PIM Neighbor Filtering

PIM routers exchange Hello messages to set up neighbor relationships and negotiate various
control parameters.
The Router under the control of default values can work normally. In the NE80E/40E, users can
adjust related parameters according to the specific network environment.
NOTE
Before adjusting control parameters for maintaining neighbor relationships, complete the
following tasks:


Data Preparation
To adjust control parameters for maintaining neighbor relationships, you need the following
data.
No. Data
1 Timeout period of the neighbor
2 Interval for sending Hello messages
3 Maximum delay for triggering Hello messages
4 Number or name of the ACL used to filter PIM neighbors
Context
Do as follows on the PIM-DM router:
NOTE

l Global configuration: It is valid on each interface.
Procedure
1. Run:
system-view

2. Run:

3. Run:
timer hello interval
The interval for sending Hello messages is set.

1. Run:
system-view

2. Run:

3. Run:
pim timer hello interval

4. Run:
pim triggered-hello-delay interval
The maximum delay for triggering Hello messages is set.

After the maximum delay is set, the conflict caused by multiple PIM routers sending
Hello messages simultaneously is prevented.
----End
Context
NOTE
The configuration involves the following two cases:

Procedure
1. Run:
system-view

2. Run:

3. Run:
hello-option holdtime interval
The timeout period during which the neighbor is reachable is set.

If no Hello message is received from a neighbor in the timeout period, the neighbor
is considered unreachable.
1. Run:
system-view

2. Run:

3. Run:
pim hello-option holdtime interval
The timeout period during which the neighbor is reachable is set.

If no Hello message is received from a neighbor in the timeout period, the neighbor
is considered unreachable.
----End
4.4.4 Refusing to Receive the Hello Message Without the

Generation ID Option
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim require-genid
The Generation ID option is set in a Hello message.

The Hello message without the Generation ID option is rejected.
When the Generation ID option in the Hello message received from an upstream neighbor
changes, it indicates that the upstream neighbor restarts. If a router does not want to receive data
from an upstream neighbor, the router sends a Prune message after receiving a data packet from
the upstream neighbor.
----End
Context
To prevent some router from being involved in PIM, filtering PIM neighbors is required.
Do as follows on the router running PIM-DM:
Procedure
Step 1 Run:
system-view


Step 2 Run:

Step 3 Run:
pim neighbor-policy { basic-acl-number | acl-name acl-name }
PIM neighbor filtering is configured.

An interface sets up neighbor relationships with only the addresses matching the filtering rules
and deletes the neighbors unmatching the filtering rules.
NOTE
When configuring the neighbor filtering function on the interface, you must also configure the neighbor
filtering function correspondingly on the router that sets up the neighbor relationship with the interface.
----End

Procedure
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface
[ interface-type interface-number | up | down ] [ verbose ] command to check PIM on an
interface.
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] neighbor
[ neighbor-address | interface interface-type interface-number | verbose ] * command to
check information about a PIM neighbor.
----End

This section describes how to configure control parameters of a PIM-DM Join/Prune message.
4.5.2 Configuring the Period for an Interface to Keep the Prune State
4.5.3 Configuring the Delay for Transmitting Prune Messages in a LAN
4.5.4 Configuring the Interval for Overriding the Prune Action

When the last member leaves its group, the router sends a Prune message through an upstream
interface. After receiving the Prune message, the upstream router performs the prune action and
stops sending multicast packets to this network segment. If other downstream routers exist in
the network, the routers need to send a Join message to override the prune action.

Routers can work normally under the control of the default parameter values. Users can adjust
related parameters according to the specific network environment.
NOTE

Before adjusting control parameters for prune, complete the following tasks:

Data Preparation
To adjust control parameters for prune, you need the following data.
No. Data
1 Timeout period of the Prune state
2 Delay for transmitting Prune messages
3 Period for overriding the prune action
Context
Procedure
1. Run:
system-view

2. Run:

3. Run:
holdtime join-prune interval
The period during which the downstream interface is in the Prune state is set.

After the period expires, the pruned interface starts to forward packets again. Before
the period expires, the router refreshes the Prune state when receiving a State-Refresh
message.
1. Run:
system-view

2. Run:

3. Run:
pim holdtime join-prune interval
After the period is expired, the pruned interface starts to forward packets again.
Before the period expires, the router refreshes the Prune state when receiving a State-
Refresh message.
----End
4.5.3 Configuring the Delay for Transmitting Prune Messages in a

LAN
Context
Procedure
1. Run:
system-view

2. Run:

3. Run:
hello-option lan-delay interval
The delay for transmitting messages in a LAN is set.

1. Run:
system-view

2. Run:


3. Run:
pim hello-option lan-delay interval
----End
Context
Procedure
1. Run:
system-view

2. Run:

3. Run:
hello-option override-interval interval
The interval for overriding the prune action is set.
When a router receives a Prune message from an upstream interface, it indicates that
another downstream router exists in the LAN. If the router still requests the multicast
data, it needs to send a Join message to the upstream router in the override-interval
period.
1. Run:
system-view

2. Run:

3. Run:
pim hello-option override-interval interval
----End


Procedure
[ interface-type interface-number | up | down ] [ verbose ] command to check information
about PIM on an interface.
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] control-message
counters interface interface-type interface-number [ message-type { assert | graft | graft-
ack | hello | join-prune | state-refresh | bsr } ] command to check the number of sent or
received PIM control packets.
number | register } | outgoing-interface { include | exclude | match } { interface-
type interface-number | register | none } | mode { dm | sm | ssm } | flags flag-value |
fsm ] * [ outgoing-interface-number [ number ] ]
----End

This section describes how to configure control parameters of a PIM-DM State-Refresh message.
4.6.2 Disabling State-Refresh
4.6.3 Configuring the Interval for Sending State-Refresh Messages
4.6.4 Configuring the Period for Receiving the Next State-Refresh Message
4.6.5 Configuring the TTL Value Carried in a State-Refresh Message

In a PIM-DM network, periodical flooding-prune wastes a lot of network resources. To prevent
a pruned interface from forwarding packets, you can enable the State-Refresh function.

Router periodically send State-Refresh messages to refresh the prune state of interfaces and
maintain the SPT.
NOTE
If there is no specific requirement, default values are recommended.
Before adjusting control parameters for State-Refresh, complete the following tasks:
Data Preparation
To adjust control parameters for State-Refresh, you need the following data.
No. Data
1 Interval for sending PIM State-Refresh messages
2 Period for waiting to receive the next State-Refresh message
3 TTL value for forwarding State-Refresh messages
Context
Do as follows on all the routers in the PIM-DM domain.
NOTE
By default, PIM-DM State-Refresh is enabled on the interface.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
undo pim state-refresh-capable
PIM-DM State-Refresh is disabled.

The interface on which PIM-DM State-Refresh is disabled cannot forward any State-Refresh
message.
NOTE
You can run the pim state-refresh-capable command to re-enable PIM-DM State-Refresh on the interface.
----End
Context
Do as follows on all the routers in the PIM-DM domain:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
state-refresh-interval interval
The interval for sending PIM State-Refresh messages is set.
NOTE
l This command is applicable to the first-hop router connecting with the multicast source.
l The interval for sending PIM State-Refresh messages should be shorter than the timeout period for
keeping the Prune state.
l You can run the holdtime join-prune command to set the timeout period for keeping the Prune state.
----End
4.6.4 Configuring the Period for Receiving the Next State-Refresh

Message
Context
Do as follows on all the PIM-DM routers in the PIM-DM domain:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
state-refresh-rate-limit interval
The period for waiting to receive the next State-Refresh message is set.
----End
4.6.5 Configuring the TTL Value Carried in a State-Refresh

Message
Context
Do as follows on all the PIM-DM routers in the PIM-DM domain:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
state-refresh-ttl ttl-value
The TTL value carried in the State-Refresh message is set.

NOTE
This command is valid only on the router directly connected to the source.
----End

Procedure
interface.
received PIM control messages.


----End
4.7 Adjusting Control Parameters for Graft

This section describes how to configure control parameters of a PIM-DM Graft message.
4.7.2 Configuring the Interval for Retransmitting Graft Messages
In a PIM-DM network, if State-Refresh is not enabled, a pruned interface can forward packets
after the Prune state times out. If State-Refresh is enabled, the pruned interface may never
forward packets.
To enable new members in the network to receive multicast data quickly, a PIM-DM router
sends a Graft message through an upstream interface. After receiving the Graft message, the
upstream router responds immediately with a Graft-Ack message and enables the interface that
receives the Graft message to forward packets.
the related parameters according to the specific network environment.
NOTE
Pre-configuration Task
Before configuring control parameters for graft, complete the following tasks:


Data Preparation
To configure control parameters for graft, you need the following data.
No. Data
1 Interval for retransmitting Graft messages
4.7.2 Configuring the Interval for Retransmitting Graft Messages
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim timer graft-retry interval
The interval for retransmitting Graft messages is set.

If the local router does not receive any Graft-Ack message from the upstream router in a specified
period, it resends a Graft message.
----End

Procedure
interface.
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] grafts command
to check an unacknowledged PIM-DM graft.
ack | hello | join-prune | state-refresh | bsr } ] command to check the number of the sent
or received PIM control messages.


----End

This section describes how to configure control parameters of a PIM-DM Assert message.
4.8.2 Configuring the Period for Keeping the Assert State
When a PIM-DM router receives multicast data through a downstream interface, it indicates that
other upstream routers exist in the network segment. The router sends Assert messages through
the interface to elect the unique upstream router.
NOTE
Before adjusting control parameters for Assert, complete the following tasks:

Data Preparation
To adjust control parameters for Assert, you need the following data.

No. Data
1 Period for keeping the Assert state
Context
NOTE

Procedure
1. Run:
system-view

2. Run:

3. Run:
holdtime assert interval
The period for holding the Assert state is set.

The router that fails in the election prevents its downstream interface from forwarding
multicast data.
After the Holdtime of the Assert state expires, the downstream interface can forward
packets.
1. Run:
system-view

2. Run:

3. Run:
pim holdtime assert interval
The period for holding the Assert state is set.

The router that fails in the election prevents its downstream interface from forwarding
multicast data.
After the Holdtime period of the Assert state expires, the downstream interface can
forward packets.
----End

Procedure
interface.
----End

4.9.2 Configuring PIM Silent

On the access layer, the interface directly connected to hosts needs to be enabled with PIM. You
can set up the PIM neighbor relationship on the interface to process various PIM packets. The
configuration, however, has the security vulnerability. When a host maliciously generates PIM
Hello messages and sends many packets to a router, the router may fail.
To prevent the preceding case, you can set the status of the interface to PIM silent. When the
interface is in the PIM silent state, the interface is prevented from receiving and forwarding any
PIM packet. All PIM neighbor relationships and PIM state machines on the interface are deleted.
At the same time, IGMP and MLD on the interface are not affected.
To enable PIM silent, the network environment must meet the following conditions:
l The network supports IPv4 and IPv6 simultaneously.

l PIM silent is applicable only to the interface directly connected to the host network segment
that is connected only to this router.
CAUTION
If PIM silent is enabled on the interface connected to a router, the PIM neighbor relationship
cannot be established and a multicast fault may occur.
If the host network segment is connected to multiple routers and PIM silent is enabled on multiple
interfaces of the routers, these interfaces do not send Assert messages. Therefore, multiple
interfaces that forward multicast data exist in the user network segment. A multicast fault thus
occurs.
Before configuring PIM silent, complete the following tasks:
l Configuring a unicast routing protocol to make the network reachable

l Configuring PIM-DM
l Configuring IGMP
Data Preparation
To configure PIM silent, you need the following data.
No. Data
1 Number of the interface connected to hosts

Context
Do as follows on the interface connected to the host network segment:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim silent
PIM silent is enabled.

After PIM silent is enabled, the Hello message attack of malicious hosts is effectively prevented,
and the router is protected.
----End

Prerequisite
All the configurations of PIM silent are complete.
Procedure
interface.
----End
Example
Run the display pim interface verbose command, and you can find that the configuration is
complete.
<HUAWEI> display pim interface gigabitethernet 6/0/0 verbose
Interface: GigabitEthernet6/0/0, 10.1.2.1
PIM version: 2
PIM mode: Dense
PIM state: up
PIM DR: 10.1.2.1 (local)
PIM Silent: enabled


PIM generation ID: 0X36E8D01B
PIM assert hold interval: 180 s
PIM state-refresh processing: enabled
PIM state-refresh interval: 60 s
PIM graft retry interval: 3 s
PIM state-refresh capability on link: capable
Number of routers on link not using DR priority: 0
Number of routers on link not using LAN delay: 0

This section describes how to clear the statistics of PIM-DM and monitor the running status of
PIM-DM.
4.10.1 Clearing Statistics of PIM Control Messages
4.10.2 Monitoring the Running Status of PIM

Context
CAUTION
The statistics of the PIM control messages on the interface cannot be restored after you reset
them. Confirm the action before you run the command.
Procedure
l Run the reset pim [ vpn-instance vpn-instance-name | all-instance ] control-message
counters [ interface interface-type interface-number ] command in the user view to clear
the statistics of the PIM control messages on an interface.
----End
4.10.2 Monitoring the Running Status of PIM

Context
status of PIM.

Procedure
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] claimed-route
[ source-address ] command in any view to check the unicast routes used by PIM.
ack | hello | join-prune | state-refresh | bsr } ] command in any view to check the number
of sent or received PIM control messages.
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] grafts command
in any view to check unacknowledged PIM-DM Graft messages.
[ interface-type interface-number | up | down ] [ verbose ] command to check information
about PIM on an interface.
check information about a PIM neighbor.
----End

This section provides several configuration examples of PIM-DM.
4.11.1 Example for Configuring Basic PIM-DM Functions
In the test network shown in Figure 4-2, multicast and an IGP are deployed, and the unicast
routes work normally. It is required to configure routers correctly in the network to enable hosts
to receive the Video On Demand (VOD) information in multicast mode.

Figure 4-2 Networking diagram for configuring basic PIM-DM functions

RouterA Ethernet
GE2/0/0 Receiver
Ethernet HostA
POS1/0/0
N1
PIM-DM
Source POS3/0/0 Leaf network
GE4/0/0
POS1/0/0 GE2/0/0
RouterD
POS2/0/0
POS1/0/0 N2
RouterB
POS1/0/0
Receiver
HostB
GE2/0/0
RouterC Ethernet
router Interface IP address router Interface IP address

Router A POS 1/0/0 192.168.1.1/24 Router D POS 1/0/0 192.168.2.2/24
GE 2/0/0 10.110.1.1/24 POS 2/0/0 192.168.3.2/24
Router B POS 1/0/0 192.168.2.1/24 POS 3/0/0 192.168.1.2/24
GE 2/0/0 10.110.2.1/24 GE 4/0/0 10.110.5.1/24
Router C POS 1/0/0 192.168.3.1/24
GE 2/0/0 10.110.2.2/24
The network is a small-scale experiment network. Therefore, PIM-DM is adopted. Enable PIM
silent on Router A to prevent Hello message attack. The configuration roadmap is as follows:
1. Enable multicast on each router.
2. Enable PIM-DM on each interface.
3. Enable PIM silent on the interface connected to hosts, and configure IGMP.
Data Preparation
l Address of multicast group G is 225.1.1.1/24.
l Address of multicast source S is 10.110.5.100/24.
l Version of IGMP running on routers and hosts is IGMPv2.
Procedure
Step 1 Enable multicast on each router and PIM-DM on each interface.
# Enable multicast on Router A and enable PIM-DM on each interface. The configuration
procedures on Router B, Router C, and Router D are similar to those on Router A, and are not
mentioned here.


[RouterA-GigabitEthernet2/0/0] pim dm
[RouterA-Pos1/0/0] pim dm
Step 2 Enable PIM silent on the interface connected to hosts, and configure IGMP on the interface.
# On Router A, enable PIM silent on the interface connected to hosts, and configure IGMP on
the interface.
[RouterA-GigabitEthernet2/0/0] pim silent
# On Router B, configure IGMP on the interface. The configurations of Router C are the same
as that of Router B, and are not mentioned here.
[RouterB] interface gigabitethernet 2/0/0
[RouterB-GigabitEthernet2/0/0] igmp enable

# Run the display pim interface command to view the configuration and the running of PIM
on the interface of the router. Take the PIM configuration on Router D as an example:
<RouterD> display pim interface
Interface State NbrCnt HelloInt DR-Pri DR-Address
Eth1/3/1 up 0 30 1 172.168.0.2 (local)
GE4/0/0 up 0 30 1 10.110.5.1 (local)
Pos3/0/0 up 1 30 1 192.168.1.2 (local)
Pos1/0/0 up 1 30 1 192.168.2.2 (local)
Pos2/0/0 up 1 30 1 192.168.3.2 (local)
# Run the display pim neighbor command to view the PIM neighbor relationship between
routers. Take the PIM neighbor relationship on Router D as an example:
<RouterD> display pim neighbor
Neighbor Interface Uptime Expires Dr-Priority BFD-Session
192.168.1.1 Pos3/0/0 00:02:22 00:01:27 1 N
192.168.2.1 Pos1/0/0 00:00:22 00:01:29 1 N
192.168.3.1 Pos2/0/0 00:00:23 00:01:31 1 N
# Run the display pim routing-table command, and you can view the PIM routing table. Assume
that Host A requests the information of group G (225.1.1.1). After multicast source S
(10.110.5.100) sends multicast packets to multicast group G (255.1.1.1), the MDT (Multicast
Distribution Tree) is established be means of flooding. All PIM multicast routers (including
Router A and Router D) on the MDT have the (S, G) entry. Host A joins G, and Router A
generates an (*, G) entry. The display information on Router B and Router C is similar to that
on Router A.
(*, 225.1.1.1)
Protocol: pim-dm, Flag: WC
UpTime: 03:54:19
Upstream interface: NULL
Upstream neighbor: NULL
RPF prime neighbor: NULL


Protocol: igmp, UpTime: 01:38:19, Expires: never
(10.110.5.100, 225.1.1.1)
Protocol: pim-dm, Flag: ACT
UpTime: 00:00:44
Protocol: pim-dm, UpTime: 00:00:44, Expires: never
(10.110.5.100, 225.1.1.1)
Protocol: pim-dm, Flag: LOC ACT
UpTime: 01:35:25
1: Pos3/0/0
2: Pos1/0/0
3: Pos2/0/0
----End
Configuration Files
#
sysname RouterA
#
#
undo shutdown
ip address 10.110.1.1 255.255.255.0
pim dm
pim silent
igmp enable
#
interface POS1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.1.1 255.255.255.0
pim dm
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 10.110.1.0 0.0.0.255
#
return

#
sysname RouterB
#
#

undo shutdown
ip address 10.110.2.1 255.255.255.0
pim dm
igmp enable
#
interface POS1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.2.1 255.255.255.0
pim dm
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 10.110.2.0 0.0.0.255
#
return
#
sysname RouterC
#
#
undo shutdown
ip address 10.110.2.2 255.255.255.0
pim dm
igmp enable
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.3.1 255.255.255.0
pim dm
#
ospf 1
area 0.0.0.0
network 192.168.3.0 0.0.0.255
network 10.110.2.0 0.0.0.255
#
return
#
sysname RouterD
#
#
undo shutdown
ip address 10.110.5.1 255.255.255.0
pim dm
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.2.2 255.255.255.0
pim dm
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 192.168.3.2 255.255.255.0
pim dm
#
interface Pos3/0/0
undo shutdown
link-protocol ppp
ip address 192.168.1.2 255.255.255.0

pim dm
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 192.168.3.0 0.0.0.255
network 192.168.1.0 0.0.0.255
network 10.110.5.0 0.0.0.255
#
return

Configuration Guide - IP Multicast 5 PIM-SM (IPv4) Configuration
5 PIM-SM (IPv4) Configuration
About This Chapter
This chapter describes the PIM-SM (IPv4) and SSM fundamentals, configuration steps, and
maintenance for PIM-SM functions, along with typical examples.
5.1 PIM-SM (IPv4) Introduction
This section describes the PIM-SM overview and PIM-SM features supported by the NE80E/
40E.
5.2 Configuring Basic PIM-SM Functions
This section describes how to configure PIM-SM to implement ASM and SSM models.
5.3 Adjusting Control Parameters for a Multicast Source
This section describes how to control the forwarding of multicast data according to the multicast
source in the PIM network.
5.4 Adjusting Control Parameters of the C-RP and C-BSR
This section describes how to configure control parameters of the C-RP, advertisement
messages, C-BSR, and Bootstrap messages.
5.5 Configuring a BSR Administrative Domain
This section describes how to configure a PIM-SM administrative domain.
5.6 Adjusting Control Parameters for Establishing the Neighbor Relationship
This section describes how to configure control parameters of PIM-SM Hello messages.
5.7 Adjusting Control Parameters for Source Registering
This section describes how to configure control parameters of PIM-SM Register messages.
5.8 Adjusting Control Parameters for Forwarding
This section describes how to configure control parameters of PIM-SM Join/Prune messages.
This section describes how to configure control parameters of PIM-SM Assert messages.
5.10 Configuring the SPT Switchover
This section describes how to configure the PIM-SM SPT switchover.
5.11 Configuring PIM BFD
This section describes how to configure PIM BFD in a shared network segment.

5 PIM-SM (IPv4) Configuration Configuration Guide - IP Multicast
5.12 Configuring PIM GR

This section describes how to configure PIM GR.
This section describes how to clear the statistics of PIM-SM and monitor the running status of
PIM-SM.
This section provides several configuration examples of PIM-SM.


This section describes the PIM-SM overview and PIM-SM features supported by the NE80E/
40E.
5.1.1 PIM-SM Overview
5.1.2 PIM-SM Features Supported by the NE80E/40E
5.1.1 PIM-SM Overview

The Protocol Independent Multicast (PIM) indicates that any unicast routing protocol, such as
static route, RIP, OSPF, IS-IS, or BGP, can provide the routing information for IP multicast.
multicast routing is independent of unicast routing protocols, except that the unicast routing table
is used to generated multicast routing entries.
PIM forwards multicast packets by using the Reverse Path Forwarding (RPF) mechanism. The
RPF mechanism is used to create the multicast forwarding tree through the existing unicast
routing information. When a multicast packet arrives at a router, the router performs the RPF
check on the packet. If the RPF check succeeds, a multicast routing entry is created for
forwarding the multicast packet. If the RPF check fails, the packet is discarded.
NOTE
For details of RPF, refer to the chapter IPv4 Multicast Routing Management in the NE80E/40E Router
Configuration Guide - IP Multicast.
The working process of the Protocol Independent Multicast-Sparse Mode (PIM-SM) consists
of neighbor discovery, assert, DR election, RP discovery, join, prune, register, and SPT
switchover.
As shown in Figure 5-1, PIM-SM is used in a large-scale network with sparsely distributed
group members.
Figure 5-1 Application of PIM-SM a the multicast network

Receiver
UserA
IGMP
PIM-SM Receiver
PIM-SM IGMP
Source PIM-SM
UserB
Multicast PIM-SM PIM-SM
Receiver
Server PIM-SM IGMP
PIM-SM
UserC

NOTE
l The Protocol Independent Multicast Dense Mode (PIM-DM) is applicable to a small-scale network
with densely distributed members.
l PIM-SM can be used to construct the Any-Source Multicast (ASM) and Source-Specific Multicast
(SSM) models.
Basic PIM-SM Functions

PIM-SM supports the ASM and SSM models. You can set the range of ASM group addresses
or the range of SSM group addresses.
Static RP
You can specify a static RP on all the routers in a PIM-SM domain. When a dynamic RP exists
in the domain, the dynamic RP is preferred by default, but you can configure the static RP to be
preferred.
Dynamic RP
You can configure C-RPs and C-BSRs in a PIM-SM domain and set the unified rules used to
dynamically generated the BSR and the RP. You can adjust the priority for C-RP election, adjust
the lifetime of the advertisement message on the BSR received from the C-RP, adjust the interval
for the C-RP to send advertisement messages, and specify an Access Control List (ACL) to limit
the range of the multicast groups served by the C-RP.
BSR
You can specify the C-BSR in the BSR domain, adjust the hash length used by the RP for C-RP
election, adjust the priority used for BSR election, and adjust the legal BSR address range. To
limit the transmission of BSR messages, you can configure the BSR service boundary on an
interface of the router on the boundary of the BSR domain.
Filtering Policy Based on Source Addresses

You can configure filtering rules of the multicast source address to control multicast sources.
You can configure the policy to filter Register messages, and suppress PIM-SM Register
messages.
BSR Administrative Domain

You can configure the service boundary of the BSR administrative domain and the boundary of
the administrative domain by using the related commands.
Adjusting Parameters for Maintaining PIM-SM Neighbors

You can adjust the following parameters about PIM-SM neighbors, including:
l Interval for sending Hello messages

l Time period for the neighbor to hold the reachable state

l Whether to receive the Hello messages with Generation IDs
l Maximum delay in triggering the Hello messages
l Priority for DR election
l DR switching delay
rules.
Configuring Control Parameters for Multicast Forwarding

You can adjust control parameters for multicast forwarding, including:
l Interval for sending Join messages
l Time period for the downstream interface to keep the forwarding state
l Time for overriding the prune action
l Filtering join information in the Join/Prune messages
l Neighbor check function: checks whether the Join/Prune and Assert messages are sent to
or received from a PIM neighbor. If not, these messages are not sent.
Configuring Control Parameters for Assert

You can configure the period for retaining the Assert state of the router interface.
Adjusting Control Parameters for SPT Switchover

You can adjust conditions of the SPT switchover and the interval for checking the forwarding
rate of multicast data.
PIM BFD
In the NE80E/40E, you can dynamically set up the BFD session to detect the status of the link
between PIM neighbors. Once a fault occurs on the link, BFD reports the fault to PIM.
PIM GR
The NE80E/40E supports the PIM GR function on the router with double MPUs. PIM GR
ensures normal multicast data forwarding during master-slave switchover of the router.

The interface acts as the static DR and immediately takes effect. At the same time, IGMP on the

Multi-Instance PIM
In multi-instance applications, a multicast router needs to maintain the PIM neighbor list,
multicast routing table, BSR information, and RP-Set information for different VPN instances
and keep the information independent between the instances. The router functions as multiple
multicast routers running PIM independently.
When a router receives a data packet, it needs to differentiate which VPN instance the packet
belongs to and forward it based on the multicast routing table of that VPN instance, or create
PIM-related multicast routing entries in that VPN instance.
5.2 Configuring Basic PIM-SM Functions

5.2.3 Enabling Basic PIM-SM Functions
5.2.4 (Optional) Configuring a Static RP
5.2.5 (Optional) Configuring a Dynamic RP
5.2.6 (Optional) Configuring the SSM Group Address Range
A PIM-SM network can adopt the ASM and SSM models to provide multicast services for user
hosts. The integrated components (including the RP) of the ASM model must be configured in
the network first. The SSM group address range is then adjusted as required.
NOTE
The SSM model is only supported in IGMPv3. If user hosts must run IGMPv1 or IGMPv2, configure IGMP
SSM mapping on router interfaces.
Through IGMP, a router knows the multicast group G that a user wants to join.
l If G is in the SSM group address range and the source S is specified when the user joins G
through IGMPv3, the SSM model is used to provide multicast services.
l If G is in the SSM group address range and the router is configured with the (S, G) SSM
mapping rules, the SSM model is used to provide multicast services.
l If G is not in the SSM group address range, the ASM model is used to provide multicast
services.
In the PIM-SM network, the ASM model supports the following methods to obtain an RP. You
can select the method as required.
l dynamic RP: To obtain the dynamic RP, select several routers in the PIM-SM domain and
configure them as C-RPs and C-BSRs, and then configure the BSR boundary on the

interface on the boundary of the domain. Each router in the PIM-SM domain can then
automatically obtain the RP.
l Static RP: To obtain a static RP, manually configure RP on each router in the PIM-SM
domain. For the large-scale PIM network, configuring the static RP is complicated. To
enhance the robustness and the operating management of the multicast network, the static
RP is usually used as the backup of the BSR-RP.
A multicast group may be in the service range of the dynamic RP and the static RP
simultaneously. By default, The router prefers the dynamic RP. If the static RP precedence is
configured, the static RP is preferred.
Different multicast groups correspond to different RPs. Compared with all groups corresponding
to an RP, this can reduce the burden of an RP and enhance the robustness of the network.
Before configuring basic PIM-SM functions, complete the following tasks:
Data Preparation
To configure basic PIM-SM functions, you need the following data.
No. Data
1 Static RP address
2 ACL rule indicating the service scope of static RP
3 C-RP priority
4 ACL rule indicating the service scope of C-RP
5 Interval for C-RP sending Advertisement message
6 Timeout of the period during which BSR waits to receive the Advertisement message
from C-RP.
7 C-BSR Hash mask length
8 C-BSR priority
9 SSM group address range

Context
CAUTION
The configuration related to the VPN instance is applicable only to the PE router. If the interface
of the VPN instance connects to the host, run the commands in step 3 and step 4.
Procedure
Step 1 Run:
system-view

Step 2 Run:


IP multicast routing is enabled is enabled in the VPN instance.
----End
5.2.3 Enabling Basic PIM-SM Functions
Context
NOTE
PIM-SM and PIM-DM cannot be enabled on an interface at the same time. The PIM mode on all interfaces
that belong to the same instance must be consistent. When the router is distributed in the PIM-SM domain,
enable PIM-SM on all non-boundary interfaces.
Procedure
Step 1 Run:
system-view

Step 2 Run:


Step 3 Run:
pim sm
PIM SM is enabled.
After PIM SM is enabled on the interface and PIM neighbor relationships are set up between
routers, the packets from the PIM neighbors can be processed.
----End

Context
CAUTION
When the static RP and the dynamicRP are configured in the PIM-SM at the same time, faults
may occur in the network. So, confirm the action before you run the command. If you want to
use only the dynamicRP in the PIM-SM network, skip the configuration.
Do as follows on all routers in the PIM-SM area:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
static-rp rp-address [ basic-acl-number | acl-name acl-name ] [ preferred ]
The static RP is specified.

You can run the command repeatedly to configure multiple static RPs for the router.
NOTE
All routers in the PIM-SM area must be configured with the same static-rp command.
l rp-address: specifies the static RP address.
l basic-acl-number | acl-name acl-name: specifies the ACL. The ACL defines the range of
the multicast group served by the static RP. When the range of multicast groups that multiple
static RPs serve overlaps, the static RP with the largest IP address functions as the RP.
l preferred: indicates the preference of the static RP. If the C-RP is configured in the network
at the same time, the router prefers the RP statically specified after preferred is used.
Otherwise, C-RP is preferred.
----End


Context
CAUTION
The configuration is applicable only to the dynamic RP. If you want to use the static RP in the
network, skip the configuration.
Do as follows on the router that may become RP in the PIM-SM area:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
c-rp interface-type interface-number [ group-policy { basic-acl-number | acl-name
acl-name } | priority priority | holdtime hold-interval | advertisement-interval
adv-interval ] *
The C-RP is configured.

l interface-type interface-number: specifies the interface where the C-RP resides. The
interface must be configured with PIM-SM.
l group-policy { basic-acl-number | acl-name acl-name }: specifies the multicast group
permitted by ACL and served by the C-RP. By default, C-RP serves all multicast groups.
l priority priority: specifies the priority for electing C-RP. The greater is the value, the lower
is the priority. By default, it is 0.
In the RP election, the C-RP with the highest priority wins. In case of the same priority, the
hash function is used and the C-RP with the greatest hash value wins. In case of the same
priority and the same hash value, the C-RP with the highest IP address wins.
NOTE
It is recommended to configure the loopback interfaces as RPs.

If the address borrowing is configured, it is not recommended to configure C-RP on the interfaces that
have the same addresses. If the priorities of the interfaces are different, the BSR considers that the C-
RP configuration is repeatedly modified.
l holdtime hold-interval: specifies the interval during which the BSR waits for the
Advertisement message from the C-RP. By default, the interval is 150 seconds.
l advertisement-interval adv-interval: specifies the interval during which the C-RP sends the
Advertisement message. By default, the interval is 60 seconds.
Step 4 Run:
c-bsr interface-type interface-number [ hash-length [ priority ] ]

The C-BSR is configured.
l interface-type interface-number: specifies the interface where the C-BSR resides. The
interface must be configured with the PIM-SM.
l hash-length: specifies the length of the hash. According to the G, C-RP address, and the value
of hash-length, routers calculate the C-RPs that have the same priority and require to serve
G by operating hash functions, and compare the calculation results. The C-RP with the
greatest calculated value functions as the RP that serves G.
l priority: specifies the priority used by routers to join the BSR election. The greater is the
value, the higher is the priority. By default, it is 0.
In the BSR election, the C-BSR with the highest priority wins. In the case of the same priority,
the C-BSR with the largest IP address wins.

auto-rp listening enable
The Auto-RP listening is enabled.
When the router interworks with a router supporting auto-RP, this command needs to be
configured on the router.
----End
Context
This configuration is optional. By default, the SSM group address range is 232.0.0.0/8.
Do as follows on all routers in the PIM-SM domain:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
ssm-policy { basic-acl-number | acl-name acl-name }
The SSM group address range is configured.
NOTE
Ensure that the SSM group address range of all routers in the network is consistent.
----End


Procedure
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] bsr-info command
to check the BSR in a PIM-SM domain.
interface.
check a PIM neighbor.
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] rp-info [ group-
address ] command to check the RP in a PIM-SM domain.
----End
5.3 Adjusting Control Parameters for a Multicast Source

source in the PIM network.


All the configurations in this section are applicable to the ASM and SSM models.
PIM routers check the multicast data that passes by. By checking whether the data matches the
filtering rule, the routers determine whether to forward the data. That is, the routers in the PIM
domain function as filters. The filters help to control the data flow, and to limit the information
that the downstream receiver can obtain.
Routers can work normally under the control of default values. The NE80E/40E allows users to
adjust the parameters as required.
NOTE
Before adjusting control parameters for a multicast source, complete the following tasks:
l Configuring a certain unicast routing protocol
l Configuring Basic PIM-SM Functions
Data Preparation
To adjust control parameters for a multicast source, you need the following data.
No. Data
1 Lifetime of a multicast source
2 Filtering rules based on multicast source addresses
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
The lifetime of a source is configured.

If the lifetime of the source expires, the (S, G) entry becomes invalid.
----End
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
source-policy { acl-number | acl-name acl-name }
A filter is configured.
are forwarded.
NOTE
l If acl-number | acl-name acl-name is specified in the source-policy command and ACL rules are
l If acl-number | acl-name acl-name is specified in the source-policy command and no ACL rule is
l The source-policy command does not filter the static (S, G) entries and the PIM entries of the Join
messages received from private networks.
----End

Procedure


----End
5.4 Adjusting Control Parameters of the C-RP and C-BSR

5.4.2 Adjusting C-RP Parameters
5.4.3 Adjusting C-BSR Parameters
5.4.4 Configuring the BSR Boundary
5.4.5 (Optional) Configuring the BSR Address Range
5.4.6 (Optional) Configuring the Range of Valid C-RP Addresses

This section describes how to adjust the control parameters of the C-RP and the C-BSR through
commands in the ASM model.
NOTE
The configuration is applicable only to a BSR-RP. If you want to use only a static RP in the network, skip
the configuration.
The router can work normally under the control of default values. The NE80E/40E allows users
to adjust the parameters as required.
NOTE
Before adjusting control parameters of the C-RP and C-BSR, complete the following tasks:


Data Preparation
To adjust various control parameters of the C-RP and C-BSR, you need the following data.
No. Data
1 RP priority
2 Interval for a C-RP to send Advertisement messages
3 Timeout of the period during which a BSR waits to receive Advertisement messages
from a C-RP
4 Hash mask length of a C-BSR
5 Priority of a C-BSR
6 Interval for a C-BSR to send Bootstrap messages
7 Time of holding the Bootstrap message received from a BSR
8 ACL defining the legal BSR address scope
5.4.2 Adjusting C-RP Parameters
Context
Do as follows on the router configured with the C-RP:
NOTE
You can re-set various parameters of a C-RP. This configuration is optional. If there is no specific
requirement, default values of parameters are recommended.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
c-rp priority priority
The C-RP priority is set.

Step 4 Run:
c-rp advertisement-interval interval
The interval during which the C-RP sends Advertisement messages is set.
Step 5 Run:
c-rp holdtime interval
The time for holding the Advertisement message from a C-RP is set. The value must be greater
than the interval for a C-RP to send advertisement messages.
The C-RP periodically sends advertisement messages to the BSR. After receiving the
advertisement messages, the BSR obtains the Holdtime of the C-RP from the message. During
the Holdtime, the C-RP is valid. When the Holdtime expires, the C-RP ages out.
----End
Context
Do as follows on the router configured with the C-BSR:
NOTE
You can re-set various parameters of a C-BSR. This configuration is optional. If there is no specific
requirement, the default values of parameters are recommended.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
c-bsr hash-length hash-length
The hash mask length of a C-BSR is set.

Step 4 Run:
c-bsr priority priority
The priority of the C-BSR is set.

Step 5 Run:
c-bsr interval interval
The interval for the C-BSR to send Bootstrap messages is set.

Step 6 Run:
c-bsr holdtime interval
The time of holding the Bootstrap message received from a BSR is set.

The BSR periodically sends a Bootstrap message to the network. After receiving the Bootstrap
message, the routers keep the message for a certain time. During the period, the BSR election
stops temporarily. If the Holdtime timer times out, a new round of BSR election is triggered
among C-BSRs.
NOTE
Ensure that the value of c-bsr holdtime is greater than the value of c-bsr interval. Otherwise, the winner
of BSR election cannot be fixed.
----End
5.4.4 Configuring the BSR Boundary
Context
Do as follows on the router that may become the BSR boundary:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim bsr-boundary
The BSR boundary is configured. Bootstrap messages cannot pass the BSR boundary.
By default, all the PIM-SM routers on the network can receive Bootstrap messages.
NOTE
Routers outside the BSR boundary cannot participate in multicast forwarding in this PIM-SM domain.
----End
5.4.5 (Optional) Configuring the BSR Address Range
Context
NOTE
By default, all BSR packets are received without the BSR source address check.
Procedure
Step 1 Run:
system-view


Step 2 Run:

Step 3 Run:
bsr-policy { basic-acl-number | acl-name acl-name }
The legal range of BSR addresses is set.

After receiving a BSR message, the router checks the source address of the message. If the source
address is not within the range of legal addresses, the message is discarded. BSR spoofing is
thus prevented.
{ basic-acl-number | acl-name acl-name } specifies the basic ACL. The ACL defines the
filtering policy for the source address range of the BSR messages.
----End
5.4.6 (Optional) Configuring the Range of Valid C-RP Addresses
Context
Do as follows on all the C-BSRs in the PIM-SM domain:
NOTE
This configuration is optional. By default, a router does not check the C-RP address and the group address
contained in a received Advertisement message and adds them to the RP-set.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
crp-policy { advanced-acl-number | acl-name acl-name }
The range of the valid C-RP addresses and the range of the multicast group addresses that a
router serves are specified. When receiving an Advertisement message, the router checks the C-
RP address and the addresses of the groups that the C-RP serves in the message. The C-RP
address and the addresses of the groups that the C-RP serves are added to the RP-Set only when
they are in the valid address range. The C-RP spoofing can thus be prevented.
{ advanced-acl-number | acl-name acl-name }: specifies the advanced ACL. The ACL defines
the filtering policy for the C-RP address range and the address range of the groups that a C-RP
serves.
----End


Procedure
----End
5.5 Configuring a BSR Administrative Domain

This section describes how to configure a PIM-SM administrative domain.
5.5.2 Enabling a BSR Administrative Domain
5.5.3 Configuring the Boundary of a BSR Administrative Domain

This section describes how to configure a BSR administrative domain in the ASM model through
commands.
In the traditional mode, a PIM-SM network maintains only one BSR and all multicast groups in
the network are in the administrative range of the BSR. To better manage the domains, the PIM-
SM network is divided into multiple BSR administrative domains. Each BSR administrative
domain maintains only one BSR that serves specified multicast groups. BSR administrative
domains are geographically isolated. Multicast packets of a BSR administrative domain cannot
pass the border of the domain.
The address of a multicast group served by a BSR administrative domain is valid only in the
BSR administrative domain. The addresses of multicast groups served by different BSR
administrative domains can be identical and these addresses are equal to private multicast group
addresses.
Multicast groups that do not belong to any BSR administrative domain are served by the global
domain. Global domain maintains only one BSR that serves the remaining multicast groups.
Dividing a PIM-SM network into multiple BSR administrative domains and a global domain
effectively reduces the load of a single BSR, and provides a special service for specific multicast
groups.
NOTE
It is recommended to adopt default values if there is no special requirement.

Before configuring a BSR administrative domain, complete the following tasks:
Data Preparation
To configure a BSR administrative domain, you need the following data.
No. Data
1 Priority and hash mask length for electing a BSR in a BSR domain
2 Priority and hash mask length of electing the global domain BSR
5.5.2 Enabling a BSR Administrative Domain
Context
Do as follows on all routers in the PIM-SM network:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
c-bsr admin-scope
The division of BSR administrative domains is enabled in a PIM-SM network.
----End
5.5.3 Configuring the Boundary of a BSR Administrative Domain
Context
Do as follows on all routers at the boundary of a BSR administrative domain:
NOTE
The routers outside the BSR administrative domain cannot forward the multicast packets of the BSR
administrative domain.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
multicast boundary group-address { mask | mask-length }
The BSR administrative domain boundary is configured. Multicast packets that belong to the
BSR administrative domain cannot traverse the boundary.
----End
Context
Do as follows on all C-BSRs:
NOTE
The C-BSR configuration involves three cases:

l Global configuration: For global configuration, see Adjusting Control Parameters of the C-RP and
C-BSR. It is valid in the global domain and each BSR administrative domain.
l Configuration in a BSR administrative domain: Because the configuration in a BSR administrative
domain takes precedence over the global configuration, the global configuration is used when the
configuration in a BSR administrative domain is not done.
l Configuration in the global domain: Because the configuration in the global domain takes precedence
over the global configuration, the global configuration is used when the configuration in the global
domain is not done.
Procedure
l Configuration in a BSR Administrative Domain
1. Run:
system-view

2. Run:

3. Run:
c-bsr group group-address { mask | mask-length } [ hash-length hash-
length | priority priority ] *
The C-BSR parameters are configured.

– group-address { mask | mask-length }: specifies the range of the multicast groups

served by a C-BSR.
– hash-length hash-length: specifies the hash mask length of a C-BSR.
– priority priority: specifies the priority of a C-BSR.
l Configuration in the Global Domain
1. Run:
system-view

2. Run:

3. Run:
c-bsr global [ hash-length hash-length | priority priority ] *
The C-BSR parameters are configured.
– hash-length hash-length: specifies the hash mask length of a C-BSR.

– priority priority: specifies the priority of a C-BSR.
----End
Procedure
----End
5.6 Adjusting Control Parameters for Establishing the

Neighbor Relationship
This section describes how to configure control parameters of PIM-SM Hello messages.
5.6.2 Configuring Control Parameters for Establishing the Neighbor Relationship
5.6.3 Configuring Control Parameters for Electing a DR
5.6.4 Enabling the Function of Tracking a Downstream Neighbor

The configuration in this section is applicable to both the ASM model and the SSM model.
The PIM routers send Hello messages to each other to establish the neighbor relationship,
negotiate the control parameters, and elect a DR.
The router can work normally by default. The NE80E/40E allows the users to adjust the
parameters as required.
NOTE
It is recommended to adopt the default value if there is no special requirement.
Before configuring control parameters for establishing the neighbor relationship, complete the
following tasks:
l Configuring unicast routing protocol

Data Preparation
To adjust the control parameters for establishing the neighbor relationship, you need the
following data.
No. Data
1 Priority of the DR that is elected
2 Timeout period for waiting for Hello messages from a neighbor
5 DR switchover delay, that is, the period during which the original entries are still
valid when the interface changes from a DR to a non-DR.
5.6.2 Configuring Control Parameters for Establishing the

Neighbor Relationship
Context
Do as follows on the PIM-SM router.

NOTE

l Global configuration: It is valid on all the interfaces.
Procedure
1. Run:
system-view

2. Run:

3. Run:

4. Run:
The timeout period of holding the reachable state of a neighbor is set.
If no Hello message is received after the interval expires, the neighbor is considered
unreachable.
1. Run:
system-view

2. Run:

3. Run:
pim timer hello interval

4. Run:
pim triggered-hello-delay interval
This can prevent the conflict of Hello messages sent by multiple PIM routers at the
same time.
5. Run:
pim hello-option holdtime interval
The timeout period of holding the reachable state of a neighbor is set.

If no Hello message is received after the interval expires, the neighbor is considered
unreachable.
6. Run:
pim require-genid
The Generation ID option is contained in a received Hello message. The Hello message
without the Generation ID option is rejected.
By default, the router handles the Hello message without the Generation option.
----End
Context
Do as follows on the PIM-SM router:
NOTE

Procedure
1. Run:
system-view

2. Run:

3. Run:
hello-option dr-priority priority
The DR priority is set.
On a shared network segment where all PIM routers support the DR priority, the
interface with the highest priority acts as the DR. In the case of the same priority, the
interface with the largest IP address acts as the DR. If a minimum of one PIM router
does not support the DR priority, the interface with the largest IP address acts as the
DR.
1. Run:
system-view

2. Run:


3. Run:
pim hello-option dr-priority priority
The DR priority is set.

On a shared network segment where all PIM routers support the DR priority, the
interface with the highest priority acts as the DR. In the case of the same priority, the
interface with the largest IP address acts as the DR. If a minimum of one PIM router
does not support the DR priority, the interface with the largest IP address acts as the
DR.
4. Run:
pim timer dr-switch-delay interval
The DR switchover delay is configured and the delay is specified.

When an interface changes from a DR to a non-DR, the original entries are valid till
the delay expires.
By default, once an interface changes from a DR to a non-DR, the original entries are
deleted immediately.
----End
Context
NOTE

l Configuration on the interface: The configuration on an interface takes precedence over the global
Procedure
l Global configuration
1. Run:
system-view

2. Run:

3. Run:
hello-option neighbor-tracking
The function of tracking a downstream neighbor is enabled.

After this function is enabled, information about the downstream neighbor who has
sent a Join message and whose Join state does not times out is recorded.

NOTE
The function of tracking downstream neighbors cannot be implemented unless all the PIM
routers in the shared network segment are enabled with this function.
l Configuration on an interface
1. Run:
system-view

2. Run:

3. Run:
pim hello-option neighbor-tracking
The function of tracking a downstream neighbor is enabled.
NOTE
The function of tracking downstream neighbors cannot be implemented unless all PIM
routers in the shared network segment are enabled with this function.
----End
Context
To prevent some router from being involved in the PIM protocol and prevent the router from
becoming the DR, filtering PIM neighbors is required.
Do as follows on the router enabled with PIM-SM:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim neighbor-policy { basic-acl-number | acl-name acl-name }

NOTE
When configuring the PIM neighbor filtering function on the interface, you must also configure the
neighbor filtering function correspondingly on the router that sets up the neighbor relationship with the
interface.
----End
Procedure
interface.
check a PIM neighbor.
----End
5.7 Adjusting Control Parameters for Source Registering

This section describes how to configure control parameters of PIM-SM Register messages.
5.7.2 Configuring PIM-SM Register Messages
5.7.3 Configuring PIM-SM Register Suppression
This section describes how to configure the control parameters of the source registering through
commands.
In a PIM-SM network, the DR directly connected to the source S encapsulates multicast data in
a Register message and sends it to the RP in unicast mode. The RP then decapsulates the message,
and forwards it along the RPT.
After the SPT switchover on the RP is complete, the multicast data reaches the RP along the
source tress in the multicast mode. The RP sends a Register-stop message to the DR at the source
side. The DR stops sending Register messages and enters the suppressed state. During the register
suppression, the DR periodically sends null packets to inform that the source is still in the active
state. After the timeout of the register suppression, the DR starts to send Register message again.
The router can work normally under the control of default values. The NE80E/40E allows the
users to adjust the parameters as required.
NOTE

Before adjusting control parameters for source registering, complete the following tasks:
Data Preparation
To adjust control parameters for source registering, you need the following data.
No. Data
1 ACL rules used by the RP to filter Register messages
2 Whether the checksum is calculated only according to the header of a Register

message
3 Timeout for keeping the suppressed state of registering
4 Interval for sending null Register messages to the RP
5.7.2 Configuring PIM-SM Register Messages
Context
Do as follows on all routers that may become an RP:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
register-policy { advanced-acl-number | acl-name acl-name }
The policy for filtering Register messages is set.

The RP applies the policy to filter received and rejected Register messages.
Step 4 Run:
register-header-checksum
The checksum is calculated only according to the header of a Register message.

By default, the checksum is calculated according to the entire message.
----End

5.7.3 Configuring PIM-SM Register Suppression
Context
Do as follows on all the routers that may become the DR at the multicast source side:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
register-suppression-timeout interval
The timeout for keeping the suppressed state of registering is set.
Step 4 Run:
probe-interval interval
The interval for sending null Register messages is set.
----End
Procedure
interface.
----End

This section describes how to configure control parameters of PIM-SM Join/Prune messages.
5.8.2 Configuring Control Parameters for Keeping the Forwarding State
5.8.3 Configuring Control Parameters for Prune
5.8.4 Configuring Join Information Filtering
5.8.5 Configuring Neighbor Check


The configurations in this section are applicable to the ASM model and the SSM model.
When the first member of a group appears in the network segment, the router sends a Join
message through an upstream interface, requiring the upstream router to forward packets to the
network segment.
When the last member of the group leaves, the router sends a Prune message through an upstream
interface, requiring the upstream router to perform the Prune action and to stop forwarding
packets to this network segment. If other downstream routers in this network segment still want
to receive data of this group, they must send a Join message to override the Prune action.
In the ASM model, a router periodically sends Join messages to the RP to prevent RPT branches
from being deleted due to timeout.
NOTE
Before adjusting control parameters for forwarding, complete the following tasks:
Data Preparation
To adjust control parameters for forwarding, you need the following data.
No. Data
2 Period of overriding the Prune action
4 Interval for sending Join messages
5 Number or name of the ACL used to filter join information in the Join/Prune messages
6 Whether neighbor check needs to be performed after Join/Prune message and Assert
messages are sent or received
5.8.2 Configuring Control Parameters for Keeping the Forwarding

State

Context
NOTE

Procedure
1. Run:
system-view

2. Run:

3. Run:
timer join-prune interval
The interval for sending Join/Prune messages is set.

4. Run:
The interval for holding the forwarding state of a downstream interface is set.
1. Run:
system-view

2. Run:

3. Run:

4. Run:
pim holdtime join-prune interval
The interval for holding the forwarding state of a downstream interface is set.
5. Run:
pim require-genid
The Generation ID option is contained in a received Hello message. The Hello message
without the Generation ID option is rejected.
By default, the router handles the Hello message without the Generation option.

The change of the Generation ID in the Hello message received from an upstream
neighbor indicates that the upstream neighbor is lost or the status of the upstream
neighbor has changed. The router immediately sends the Join/Prune message to the
upstream router to refresh the status.
----End
Context
NOTE

l Global Configuration: It is valid on all the interfaces.
Procedure
1. Run:
system-view

2. Run:

3. Run:

A Hello message carries lan-delay and override-interval . PPT indicates the delay
from the time when a router receives the Prune message from a downstream interface
to the time when the router performs the prune action to suppress the forwarding of
the downstream interface. The PPT is obtained by the lan-delay plus override-interval.
If the router receives a Join message from a downstream router within the PPT, the
router does not perform the prune action.
4. Run:
The interval for overriding the Prune action is set.

If a router receives the Prune message through an upstream interface, this indicates
that other downstream routers exist in this LAN. If the router still needs to receive
multicast data of the group, the router must send a Join message to the upstream
router within the override-interval.
1. Run:
system-view


2. Run:

3. Run:
pim hello-option lan-delay interval

4. Run:
pim hello-option override-interval interval
The interval for overriding the Prune action is set.

----End
Context
A Join/Prune message received by an interface may contain both join information and prune
information. You can configure the router to filter join information based on ACL rules. The
router then creates PIM entries for only the join information matching ACL rules, which can
avoid access of illegal users.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim join-policy { asm { basic-acl-number | acl-name acl-name } | ssm { advanced-acl-
number | acl-name acl-name } }
Join information filtering is configured.
----End
Context
By default, checking whether the Join/Prune message and Assert messages are sent to or received
from a PIM neighbor is not enabled.
If PIM neighbor checking is required, it is recommended to configure the neighbor checking
function on the devices connected with user devices rather than on the internal devices of the

network. Then, the router checks whether the Join/Prune and Assert messages are sent to or
received from a PIM neighbor. If not, the router drops the messages.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
neighbor-check { receive | send }
The neighbor check function is configured.
You can specify both receive and send to enable the PIM neighbor check function for the
received and sent Join/Prune and Assert messages.
----End
Procedure
interface.


----End

This section describes how to configure control parameters of PIM-SM Assert messages.

The configurations in this section ares applicable to the ASM model and the SSM model.
If a PIM-SM router receives multicast data through a downstream interface, it indicates that
other upstream routers exist in this network segment. routers send Assert messages to elect the
unique upstream router.
NOTE
Before adjusting control parameters for assert, complete the following tasks:
Data Preparation
To adjust control parameters for assert, you need the following data.
No. Data
1 Interval for holding the Assert state
Context
Do as follows on all the routers in the PIM-SM domain:

NOTE

Procedure
1. Run:
system-view

2. Run:

3. Run:
The interval for holding the Assert state is set.

The router that fails in the election prevents the downstream interface from forwarding
multicast packets within the interval. After the interval expires, the downstream
interface starts to forward multicast packets.
l Configuration on the Interface
1. Run:
system-view

2. Run:

3. Run:
pim holdtime assert interval
The interval for holding the Assert state is configured.

The router that fails in the election prohibits the downstream interface from forwarding
multicast packets within this interval. After the interval expires, the downstream
interface starts to forward multicast packets.
----End

Procedure
interface.

----End
5.10 Configuring the SPT Switchover

This section describes how to configure the PIM-SM SPT switchover.
5.10.2 (Optional) Configuring the Interval for Checking the Forwarding Rate of Multicast Data
This section describes how to configure the control parameters of the SPT switchover through
commands.
In a PIM-SM network, each multicast group corresponds to an RPT. At first, all multicast sources
encapsulate data in Register messages, and send them to the RP in the unicast mode. The RP
decapsulates the messages and forwards them along the RPT.
Forwarding multicast data by using the RPT has the following defects:
l The DR at the source side and the RP need to encapsulate and decapsulate packets.
l Forwarding path may not be the shortest path from the source to receivers.
l Large-volume data flow increases the load of the RP, and may cause a fault.
The solution to the preceding defects is that:

l SPT switchover triggered by the RP: The RP sends a Join message to the source, and
establishes a multicast route along the shortest path from the source to the RP. The
subsequent packets are forwarded along the path.
l SPT switchover triggered by the DR at the member side: The DR at the member side checks
the forwarding rate of multicast data. If the DR finds that the rate exceeds the threshold,
the DR tiggers the SPT switchover immediately. The DR sends a Join message to the source,
and establishes a multicast route along the shortest path from the source to the DR. The
subsequent packets are forwarded along the path.
Routers can work normally under the control of default values. The NE80E/40E allows users to
adjust the parameters as required.
NOTE
Before configuring the SPT switchover, complete the following tasks:

Data Preparation
To configure the SPT switchover, you need the following data.
No. Data
1 Rate threshold that a leaf PIM router switches packets from the RPT to the SPT
2 Group filtering policy and sequence policy for the switchover from the RPT to the
SPT
3 Interval for checking the rate threshold of multicast data before the RPT-to-SPT
switchover
5.10.2 (Optional) Configuring the Interval for Checking the

Forwarding Rate of Multicast Data
Context
Do as follows on all the routers that may become a DR at the member side:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
spt-switch-threshold { traffic-rate | infinity } [ group-policy { basic-acl-number
| acl-name acl-name } [ order order-value ] ]
The SPT switchover condition is set.

l traffic-rate: specifies the rate threshold of the SPT switchover.
l infinity: indicates that the SPT switchover is not triggered forever.
l group-policy { basic-acl-number | acl-name acl-name } [ order order-value]: specifies the
range of the multicast groups that use the threshold. By default, the threshold is applicable
to all multicast groups.
Step 4 Run:
timer spt-switch interval
The interval for checking the forwarding rate of multicast data is set.
----End

Procedure
----End
5.11 Configuring PIM BFD

This section describes how to configure PIM BFD in a shared network segment.
5.11.2 Configuring PIM BFD

5.11.3 (Optional) Adjusting BFD Parameters


Generally, if the current DR in a shared network segment is faulty, other PIM neighbors triggers
a new round of DR election only after the neighbor relationship times out. The duration that data
transmission is interrupted is not shorter than the timeout period of the neighbor relationship.
Generally, it is of second level.
BFD features fast detection of faults, and is up to the millisecond level. BFD can detect statuses
of PIM neighbors in the shared network segment. When BFD detects that a peer is faulty, BFD
immediately reports it to PIM. PIM then triggers a new round of DR election without waiting
for the timeout of the neighbor relationship. This shortens the duration of interruption of data
transmission and enhances the reliability of the network.
PIM BFD is also applicable to the assert election in a shared network segment. It can fast respond
to the fault of the interface that wins the assert election.
Before configuring PIM BFD, complete the following task:
Data Preparation
To configure PIM BFD, you need the following data.
No. Data
1 Minimum intervals for sending and receiving BFD detection messages, and local
detection multiple
5.11.2 Configuring PIM BFD
Context
NOTE
This function is applicable to NBMA interfaces and broadcast interfaces rather than MTunnel interfaces.
Do as follows on PIM routers that set up the neighbor relationship:
Procedure
Step 1 Run:

system-view

Step 2 Run:

Step 3 Run:
pim bfd enable
PIM BFD is enabled.

By default, PIM BFD is disabled.
----End
5.11.3 (Optional) Adjusting BFD Parameters
Context
Do as follows on two PIM routers that set up the neighbor relationship:
Procedure
Step 1 Run:
system-view

Step 2 Run:
The interface view is displayed

Step 3 Run:
pim bfd { min-tx-interval tx-value | min-rx-interval rx-value | detect-multiplier
multiplier-value }*
PIM BFD parameters are adjusted.

PIM BFD parameters include the minimum interval for sending PIM BFD messages, the
minimum interval for receiving PIM BFD messages, and the local detection multiple.
If this command is not used, the default values of these parameters are used. When the BFD
parameters configured for other protocols are the same as those configured for PIM, the
configurations of the PIM BFD parameters are affected.
----End

Procedure
l Run the following commands to check information about a PIM BFD session.
– display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session statistics

– display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session

[ interface interface-type interface-number | neighbor neighbor-address ] *
----End
5.12 Configuring PIM GR

This section describes how to configure PIM GR.
5.12.2 Configuring PIM GR
In some multicast applications, the router may need to perform active/standby switchover. After
active/standby switchover, the new active main control board deletes the forwarding entries on
the interface board and re-learns the PIM routing table and multicast routing table. During this
process, multicast traffic is interrupted.
In the PIM-SM/SSM network, PIM Graceful Restart (GR) can be applied to the router with dual
main control boards to ensure normal multicast traffic forwarding during active/standby
switchover.
The active main control board of the router backs up PIM routing entries and Join/Prune
information to be sent upstream to the standby main control board. The interface board maintains
forwarding entries. Therefore, after active/standby switchover, the router can actively and fast
send Join messages upstream to maintain the Join state of the upstream. In addition, the PIM
protocol sends Hello message carrying new Generation ID to all routers enabled with PIM-SM.
When the downstream router finds that the Generation ID of its neighbor changes, it sends a
Join/Prune message to the neighbor for re-creating routing entires, thereby ensuring non-stop
forwarding of multicast data on the forwarding plane.
If a dynamic RP is used on the network, after receiving a Hello message with the Generation ID
being changed, the DR or candidate DR unicasts a BSM message to the router performing active/
standby switchover and the router learns and restores RP information based on the received BSM
message. If the router has not leant any RP information from the BSM messages, it obtains the
RP information from the Join/Prune message received from the downstream router and re-creates
NOTE
PIM GR is applicable to PIM-SM/SSM networks.
Before enabling PIM GR, complete the following task:
l Configuring a unicast routing protocol and enabling unicast GR


Data Preparation
To enable PIM GR, you need the following data.
No. Data
1 Unicast GR period
2 PIM GR period
5.12.2 Configuring PIM GR
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
graceful-restart
PIM GR is enabled.

graceful-restart period period
The PIM GR period is set.
By default, the PIM GR period is 120 seconds.
----End
Procedure
Step 1 Run the following commands to check PIM routing table.
l display pim { vpn-instance vpn-instance-name | all-instance } routing-table [ group-
mask-length | source-mask } ] | incoming-interface { interface-type interface-number |
register } | outgoing-interface { include | exclude | match } { interface-type interface-

number | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ] * [ outgoing-

interface-number [ number ] ]
l display pim routing-table [ group-address [ mask { group-mask-length | group-mask } ] |
source-address [ mask { source-mask-length | source-mask } ] | incoming-interface
{ interface-type interface-number | register } | outgoing-interface { include | exclude |
match } { interface-type interface-number | vpn-instance vpn-instance-name | register |
none } | mode { dm | sm | ssm } | flags flag-value | fsm ] * [ outgoing-interface-number
[ number ] ]
l display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table brief [ group-
mask-length | source-mask } ] | incoming-interface { interface-type interface-number |
register } ] *
----End


On the access layer, the interface directly connected to hosts needs to be enabled with PIM. You
can establish the PIM neighbor relationship on the interface to process various PIM packets. The
configuration, however, has security vulnerability. When a host maliciously generates PIM Hello
packets and sends the packets in large quantity, the router may fail.
To prevent the preceding case, you can set the status of the interface to PIM silent. When the
interface is in the PIM silent state, the interface is prevented from receiving and forwarding any
PIM packet. All PIM neighbors and PIM state machines on the interface are deleted. The
interface acts as the static DR and immediately takes effect. At the same time, IGMP and MLD
on the interface are not affected.
PIM silent is applicable only to the interface directly connected to the host network segment that
is connected only to this router.
CAUTION
If PIM silent is enabled on the interface connected to a router, the PIM neighbor relationship
cannot be set up and a multicast fault may occur.
If the host network segment is connected to multiple routers and PIM silent is enabled on multiple
interfaces, the interfaces become static DRs. Therefore, multiple DRs exist in this network
segment, and a fault occurs.

Before configuring PIM silent, complete the following tasks:
l Configuring a unicast routing protocol to make the network layer reachable

l Configuring PIM-SM
l Configuring IGMP
Data Preparation
To configure PIM silent, you need the following data.
No. Data
1 The number of the interface connected to hosts
Context
Do as follows on the interface connected to the host network segment:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim silent
PIM silent is enabled.
After PIM silent is enabled, the Hello packet attack of malicious hosts is effectively prevented
and the router is protected.
----End
Prerequisite

Procedure
interface.
----End
Example
Run the display pim interface verbose command, and you can find that the configuration is
complete.
<RouterA> display pim interface verbose
PIM version: 2
PIM mode: Sparse
PIM DR: 2.2.2.2 (local)
PIM Silent: enabled
PIM generation ID: 0X2649E5DA
PIM require-genid: disabled
PIM hello assert interval: 180 s
PIM state-refresh capability on link: non-capable
PIM BSR domain border: disabled
Number of routers on link not using DR priority: 0
Number of routers on link not using LAN delay: 0

This section describes how to clear the statistics of PIM-SM and monitor the running status of
PIM-SM.
5.14.2 Clearing the PIM Status of the Specified Downstream Interfaces of PIM Entries
5.14.3 Monitoring the Running Status of PIM-SM

Context
CAUTION
The statistics of PIM control messages on an interface cannot be restored after you clear it. So,
confirm the action before you use the command.
Procedure
l Run the reset pim [ vpn-instance vpn-instance-name | all-instance ] control-message
counters [ interface interface-type interface-number ] command in the user view to clear
the statistics of PIM control messages on an interface.
----End
5.14.2 Clearing the PIM Status of the Specified Downstream

Interfaces of PIM Entries
Context
CAUTION
Clearing PIM status of the downstream interfaces may trigger the sending of corresponding Join/
Prune messages, which affects multicast services.
Using the following command can clear join information about illegal users, and clear the PIM
status of the specified interface in a specified entry, such as PIM Join/Prune status and Assert
status.
The command cannot be used to clear the IGMP or static group join status on a specified
interface.
Procedure
Step 1 After confirming that PIM status of the specified downstream interfaces of the specified PIM
entry need to be cleared, run the reset pim [ vpn-instance vpn-instance-name ] routing-table
group group-address mask { group-mask-length | group-mask } source source-address
interface interface-type interface-number command in the user view.
----End

Context
status of PIM-SM.
Procedure
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] claimed-route
[ source-address ] command in any view to check the unicast routes used by PIM.
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session
[ interface interface-type interface-number | neighbor neighbor-address ] * command in
any view to check information about a PIM BFD session.
in any view to check information about the BSR in a PIM-SM domain.
ack | hello | join-prune | state-refresh | bsr } ] command in any view to check the number
of sent or received PIM control messages.
[ interface-type interface-number | up | down ] [ verbose ] command in any view to check
PIM on an interface.
neighbor [ neighbor-address | interface interface-type interface-number | verbose ] * to
check PIM neighbors.
l Run the following commands in any view to check the PIM routing table.
address ] command in any view to check information about the RP to which a multicast
group corresponds.
----End


This section provides several configuration examples of PIM-SM.
5.15.1 Example for Configuring a PIM-SM Network

5.15.2 Example for Configuring the SPT Switchover in a PIM-SM Domain
5.15.3 Example for Configuring PIM BFD on Routers in Ethernet
5.15.4 Example for Configuring PIM GR
5.15.1 Example for Configuring a PIM-SM Network
As shown in Figure 5-2, multicast is deployed in the Internet Service Provider (ISP) network.
An integrated Interior Gateway Protocol (IGP) is deployed in the network. Unicast routes work
normally and are connected to the Internet. It is required to perform proper configuration on
routers in the network to enable hosts to receive the Video On Demand (VOD) information in
multicast mode.
Figure 5-2 Networking diagram for configuring PIM-SM multicast network

RouterA Ethernet
N1
POS3/0/0
GE2/0/0
Ethernet
Receiver
POS1/0/0 HostA
POS2/0/0 PIM-SM
Source RouterE POS3/0/0 Leaf networks
GE3/0/0 POS1/0/0
POS4/0/0 POS2/0/0 GE2/0/0
POS4/0/0 POS1/0/0 Receiver
RouterD POS1/0/0
RouterB HostB
RouterC POS2/0/0
N2
GE1/0/0 Ethernet
router Interface IP Address

Router A POS 1/0/0 192.168.9.1/24
POS 3/0/0 192.168.1.1/24
GE 2/0/0 10.110.1.1/24
Router B POS 1/0/0 192.168.2.1/24
GE 2/0/0 10.110.2.1/24
Router C POS 2/0/0 192.168.3.1/24
GE 1/0/0 10.110.2.2/24
Router D POS 1/0/0 192.168.4.2/24
POS 2/0/0 192.168.1.2/24
POS 4/0/0 10.110.4.1/24

GE 3/0/0 10.110.5.1/24
Router E POS 1/0/0 192.168.3.2/24
POS 2/0/0 192.168.2.2/24
POS 3/0/0 192.168.9.2/24
POS 4/0/0 192.168.4.1/24
The ISP network is accessed to the Internet. To expand services, PIM-SM is adopted to configure
multicast functions, and ASM and SSM models are used to provide multicast services.
1. Configure an IP address for each interface on routers and a unicast routing protocol. PIM,
an intra-domain multicast routing protocol, depends on unicast routing protocols. The
multicast routing protocol can work normally only when unicast routing protocols work
normally.
2. Enable the multicast function on all the routers providing multicast services. PIM-SM can
be configured only after multicast is enabled.
3. Enable PIM-SM on all interfaces of the multicast routers. Other PIM-SM functions can be
configured only after PIM-SM is enabled.
NOTE
If IGMP needs to be configured on this interface, PIM-SM must be enabled before IGMP is enabled.
The configuration order cannot be reversed; otherwise, the configuration of PIM-SM fails.
4. Enable IGMP on the interface connected to user hosts. A receiver can join and leave a
multicast group freely by sending IGMP messages. Leaf routers maintain the member
relationship through IGMP.
5. Enable PIM silent on the router interface connected to hosts to prevent malicious hosts
from attacking the router by simulating and sending PIM Hello packets; therefore, the
security of multicast routers can be ensured.
NOTE
PIM silent is applicable only to the router interface directly connected to the host network segment
that is connected only to this router.
6. Configure an RP. The RP is a root node of an RPT tree in a PIM-SM network. It is
recommended to configure the RP on a router through which many multicast flows pass,
such as Router E in the figure.
NOTE
l After creating an (*, G) entry according to the new multicast member relationship, the DR on
the user side sends Join/Prune messages to the RP, updating the shared tree.
l When a multicast data source starts to send data to groups, the DR unicasts a Register message
to the RP. After receiving the Register message, the RP decapsulates it and then forwards it to
other multicast members along the shared tree. At the same time, the RP sends a Register-Stop
message to the DR on the multicast source side. After the Register-Stop message is received by
the DR, the traffic can be switched from RPT to the SPT.
7. (Optional) Configure the BSR boundary on the interface connected to the Internet.
Bootstrap messages cannot pass through the BSR boundary; therefore, the BSR serves this
PIM-SM domain only. In this manner, multicast services can be controlled effectively.

8. (Optional) Configure the SSM group address range on each router. Ensure that multicast
routers in the PIM-SM domain provide services only for multicast groups in the SSM group
address range. In this manner, multicast services can be controlled effectively.
Data Preparation
l Address of multicast group G is 225.1.1.1.
l Source address is 10.110.5.100/24.
l Version number of IGMP running between the interface and hosts is 3.
l SSM group address range is 232.1.1.0/24.
Procedure
Step 1 Configure an IP address and a unicast routing protocol on each interface.
Step 2 Enable multicast on all routers and PIM-SM on all interfaces.
# Enable multicast on all routers and PIM-SM on all interfaces. The configurations of Router
B, Router C, Router D, and Router E are the same as the configuration of Router A, and are not
mentioned here.
Step 3 Enable IGMP on the interface connected to hosts.

# On Router A, enable IGMP on the interface connected to hosts. The configurations of Router
B and Router C are the same as the configuration of Router A, and are not mentioned here.
[RouterA-GigabitEthernet2/0/0] igmp version 3
Step 4 Enable PIM silent on an interface of Router A.

[RouterA-GigabitEthernet2/0/0] pim silent
Step 5 Configure a C-RP.

NOTE
l RPs are classified into two types, that is, the static RP and the dynamic RP. You can configure the static
RP and the dynamic at the same time or just configure one of them.
l When the static RP and the dynamic RP are configured simultaneously, you can adjust parameters to
specify the preferred RP.
This example shows how to configure the static RP and the dynamic RP, to prefer the dynamic
RP, and specify the static RP as the standby RP by configuring the parameters.
# Configure the dynamic RP on one or more routers in the PIM-SM domain. Set the service
range of the RP advertisement and configure the C-BSR and the C-RP on Router E.

[RouterE] acl number 2005

[RouterE-acl-basic-2005] rule permit source 225.1.1.0 0.0.0.255
[RouterE-acl-basic-2005] quit
[RouterE] pim
[RouterE-pim] c-bsr pos 3/0/0
[RouterE-pim] c-rp pos 3/0/0 group-policy 2005 priority 0
# Configure the static RP on all multicast routers. Configure Router A, Router B, Router C,
Router D, and Router E. The configurations on Router B, Router C, Router D, and Router E are
similar to those on Router A. The detailed configurations are not mentioned here.
NOTE
If preferred is set in the static-rp x.x.x.x command, the static RP is preferred as the RP in the PIM-SM
domain.
[RouterA] pim
[RouterA-pim] static-rp 192.168.2.2
Step 6 On Router D, configure the BSR boundary on the interface connected to the Internet.
[RouterD] interface pos 4/0/0
[RouterD-Pos4/0/0] pim bsr-boundary
[RouterD-Pos4/0/0] quit
Step 7 Configure the SSM group address range.

# Set the SSM group address range to 232.1.1.0/24 on all routers. The configurations of Router
B, Router C, Router D, and Router E are the same as the configuration of Router A, and are not
mentioned here.
[RouterA] acl number 2000
[RouterA-acl-basic-2000] rule permit source 232.1.1.0 0.0.0.255
[RouterA-acl-basic-2000] quit
[RouterA] pim
[RouterA-pim] ssm-policy 2000

# Run the display pim interface command to view the configuration and running of PIM on an
interface. The display of PIM on Router C is as follows:
<RouterC> display pim interface
GE1/0/0 up 0 30 1 10.110.2.2 (local)
Pos2/0/0 up 1 30 1 192.168.3.1
# Run the display pim bsr-info command to view the BSR election on a router. For example,
the BSR information on Router A and Router E (including the C-BSR information on Router
E) is as follows:
<RouterA> display pim bsr-info
Elected AdminScoped BSR Count: 0
Elected BSR Address: 192.168.9.2
Priority: 0
Hash mask length: 30
State: Accept Preferred
Scope: Not scoped
Uptime: 01:40:40
Expires: 00:01:42
C-RP Count: 1
<RouterE> display pim bsr-info
Elected BSR Address: 192.168.9.2
Priority: 0


State: Elected
Scope: Not scoped
Uptime: 00:00:18
Next BSR message scheduled at :00:01:42
C-RP Count: 1
Candidate AdminScoped BSR Count: 0
Candidate BSR Address is: 192.168.9.2
Priority: 0
State:Elected
Scope: Not scoped
Wait to be BSR: 0
# Run the display pim rp-info command to view the RP information obtained by a router. For
example, the RP information on Router A is as follows:
<RouterA> display pim rp-info
PIM-SM BSR RP information:
Group/MaskLen: 225.1.1.0/24
RP: 192.168.9.2
Priority: 0
Uptime: 00:51:45
Expires: 00:02:22
PIM SM static RP information:
Static RP: 192.168.2.2
# Run the display pim routing-table command to view the PIM multicast routing table on a
router. Host A needs to receive the information about group 225.1.1.1/24, and Host B needs to
receive the information sent by source 10.110.5.100/24 to group 232.1.1.1/24. The display is as
follows:
(*, 225.1.1.1)
RP: 192.168.9.2
UpTime: 00:13:46
Upstream interface: Pos1/0/0,
RPF neighbor: 192.168.9.2
1: GigabitEthernet2/0/0,
Protocol: igmp, UpTime: 00:13:46, Expires:-
(10.110.5.100, 225.1.1.1)
RP: 192.168.9.2
Protocol: pim-sm, Flag: SPT ACT
UpTime: 00:00:42
Protocol: pim-sm, UpTime: 00:00:42, Expires:-
(10.110.5.100, 225.1.1.1)
RP: 192.168.9.2
UpTime: 00:00:42


1: Pos2/0/0
(10.110.5.100, 232.1.1.1)
Protocol: pim-ssm, Flag:
UpTime: 00:01:20
1: Pos1/0/0
Protocol: pim-ssm, UpTime: 00:01:20, Expires:-
<RouterE> display pim routing-table
(*, 225.1.1.1)
RP: 192.168.9.2 (local)
UpTime: 00:13:16
Upstream interface: Register
1: Pos3/0/0
Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22
(10.110.5.100, 232.1.1.1)
UpTime: 00:01:22
1: Pos1/0/0
Protocol: pim-ssm, UpTime: 00:01:22, Expires:-
<RouterC> display pim routing-table
Total 1 (S, G) entry
(10.110.5.100, 232.1.1.1)
UpTime: 00:01:25
----End
Configuration Files
#
sysname RouterA
#
#
acl number 2000
#
undo shutdown
ip address 10.110.1.1 255.255.255.0
pim sm

igmp enable
igmp version 3
pim silent
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.1 255.255.255.0
pim sm
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.9.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.1.0 0.0.0.255
network 192.168.1.0 0.0.0.255
network 192.168.9.0 0.0.0.255
#
pim
static-rp 192.168.2.2
ssm-policy 2000
#
return
#
sysname RouterB
#
#
acl number 2000
#
undo shutdown
ip address 10.110.2.1 255.255.255.0
pim sm
igmp enable
igmp version 3
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#
Pim
static-rp 192.168.2.2
ssm-policy 2000
#
return
#
sysname RouterC
#
#
acl number 2000
#

undo shutdown
ip address 10.110.2.2 255.255.255.0
pim sm
igmp enable
igmp version 3
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.3.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.3.0 0.0.0.255
#
pim
static-rp 192.168.2.2
ssm-policy 2000
#
return

#
sysname RouterD
#
#
acl number 2000
#
undo shutdown
ip address 10.110.5.1 255.255.255.0
pim sm
#
interface Pos4/0/0
link-protocol ppp
undo shutdown
ip address 10.110.4.1 255.255.255.0
pim sm
pim bsr-boundary
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.2 255.255.255.0
pim sm
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.4.2 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.4.0 0.0.0.255
network 10.110.5.0 0.0.0.255
network 192.168.1.0 0.0.0.255
network 192.168.4.0 0.0.0.255
#
pim
static-rp 192.168.2.2
ssm-policy 2000
#
return

l Configuration file of Router E

#
sysname RouterE
#
#
acl number 2000
#
acl number 2005
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.3.2 255.255.255.0
pim sm
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.2 255.255.255.0
pim sm
#
interface Pos3/0/0
link-protocol ppp
undo shutdown
ip address 192.168.9.2 255.255.255.0
pim sm
#
interface Pos4/0/0
link-protocol ppp
undo shutdown
ip address 192.168.4.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 192.168.3.0 0.0.0.255
network 192.168.2.0 0.0.0.255
network 192.168.9.0 0.0.0.255
network 192.168.4.0 0.0.0.255
#
pim
c-bsr Pos3/0/0
c-rp Pos3/0/0 group-policy 2005 priority 0
static-rp 192.168.2.2
ssm-policy 2000
#
return
5.15.2 Example for Configuring the SPT Switchover in a PIM-SM

Domain
Receivers can receive the Video On Demand (VOD) information in multicast mode. The SM-
single BSR administrative domain is adopted in the entire PIM network. By default, the DR at
the receiver side and the RP perform the SPT switchover immediately after receiving the first
multicast data packet, and choose the optimal path to receive information from the source. If a
receiver wants to perform the SPT switchover after the traffic reaches the threshold, you need
to configure the SPT switchover.

As shown in Figure 5-3, it is required to perform proper configuration on routers. Host A on

the leaf network can receive multicast data from the RP (POS 1/0/0 of Router A). When the rate
for forwarding multicast data reaches 1024 kbit/s, the SPT switchover is performed (After SPT
switchover, the path used by Host A to receive multicast data is Source-Router B-Router C-Host
A).
Figure 5-3 Networking diagram for performing SPT switchover in a PIM-SM domain
RouterA
POS2/0/0
Ethernet
POS1/0/0
POS2/0/0 Leaf
POS1/0/0 networks
Source POS1/0/0
GE3/0/0
POS3/0/0 GE2/0/0
RouterB RouterC
PIM-SM Receiver
HostA
Ethernet
router Interface IP address

Router A POS 1/0/0 192.168.1.1/24
POS 2/0/0 192.168.3.1/24
Router B POS 1/0/0 192.168.2.1/24
POS 2/0/0 192.168.3.2/24
GE 3/0/0 10.110.5.1/24
Router C POS 1/0/0 192.168.1.2/24
POS 3/0/0 192.168.2.2/24
GE 2/0/0 10.110.2.1/24
1. Configure an IP address and a unicast routing protocol for each interface.

2. Enable multicast on each router, PIM-SM on each interface, and IGMP on the interface at
the host side.
3. Configure POS 1/0/0 of Router A as the C-BSR and C-RP.
4. Perform the SPT switchover on Router C.
Data Preparation
l Multicast source address is 10.110.5.100/24.

l Group address is 225.1.1.1/24.

l The number of IGMP version running between Router C and the leaf network is 2.
Procedure
Step 1 Configure an IP address and a unicast routing protocol on each interface.
# Based on Figure 5-3, configure an IP address and mask of each interface, interconnect
routers through OSPF, ensure that Router A, Router B, and Router C can interconnect at the
network layer, and configure the three routers to dynamically update routes through a unicast
routing protocol. The configuration details are not mentioned here.
Step 2 Enable multicast on each router, PIM-SM on each interface, and IGMP on the interface at the
host side.
# Enable multicast on each router, PIM-SM on each interface, and IGMP on the interfaces
through which Router C is connected to the leaf network. The configurations of Router A and
Router B are the same as the configuration of Router C, and are not mentioned here.
[RouterC] multicast routing-enable
[RouterC] interface gigabitethernet 2/0/0
[RouterC-GigabitEthernet2/0/0] pim sm
[RouterC-GigabitEthernet2/0/0] igmp enable
[RouterC-GigabitEthernet2/0/0] igmp version 2
[RouterC-GigabitEthernet2/0/0] quit
[RouterC] interface pos 3/0/0
[RouterC-Pos2/0/0] pim sm
[RouterC-Pos2/0/0] quit
Step 3 Configure a static RP.

# Configure the static RP on Router A, Router B, and Router C. The configurations on Router
B and Router C are similar to those on Router A. The detailed configurations are not mentioned
here.
[RouterA] pim
Step 4 Configure the threshold of the SPT switchover.

# Perform the SPT switchover on Router C when the rate of multicast data packets reaches 1024
kbit/s.
[RouterC] pim
[RouterC-pim] spt-switch-threshold 1024
[RouterC-pim] quit

# The multicast source starts to send data to the group, and Host A can receive the data from the
source. When the rate is smaller than 1024 kbit/s, run the display pim routing-table command
to view the PIM multicast routing table on the router. You can find that the upstream neighbor
is Router A. The display is as follows:
(*, 225.1.1.1)
RP: 192.168.1.1

UpTime: 00:13:46
(10.110.5.100, 225.1.1.1)
RP: 192.168.1.1
Protocol: pim-sm, Flag: ACT
UpTime: 00:00:42
# When the rate is greater than 1024 kbit/s, run the display pim routing-table command to view
the PIM multicast routing table on the router. You can find that the upstream neighbor is Router
B. The display is as follows:
(*, 225.1.1.1)
RP: 192.168.1.1
UpTime: 00:13:46
(10.110.5.100, 225.1.1.1)
RP: 192.168.1.1
Protocol: pim-sm, Flag:RPT SPT ACT
UpTime: 00:00:42
----End
Configuration Files
#
sysname RouterA
#
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.1 255.255.255.0
pim sm
#
interface Pos2/0/0
link-protocol ppp

undo shutdown
ip address 192.168.3.1 255.255.255.0
pim sm
#
pim
static-rp 192.168.1.1
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 192.168.3.0 0.0.0.255
#
return
#
sysname RouterB
#
#
undo shutdown
ip address 10.110.5.1 255.255.255.0
pim sm
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
pim sm
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.3.2 255.255.255.0
pim sm
#
pim
static-rp 192.168.1.1
#
ospf 1
area 0.0.0.0
network 10.110.5.0 0.0.0.255
network 192.168.2.0 0.0.0.255
network 192.168.3.0 0.0.0.255
#
return
#
sysname RouterC
#
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.2 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.2.1 255.255.255.0
pim sm
igmp enable
igmp version 2
#
interface Pos3/0/0
link-protocol ppp
undo shutdown

ip address 192.168.2.2 255.255.255.0

pim sm
#
pim
spt-switch-threshold 1024
static-rp 192.168.1.1
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.1.0 0.0.0.255
network 192.168.2.0 0.0.0.255
#
return
5.15.3 Example for Configuring PIM BFD on Routers in Ethernet
In the multicast network shown in Figure 5-4, PIM-SM is run on routers, hosts normally receive
the VOD information from the multicast source, and Router B and Router C are connected to
the host network segment. When the DR changes, other routers in the network segment can
detect the change of the DR quickly.
Set up the BFD session on the host network segment to quickly respond to the changes of the
DR, and configure the delay of the DR switchover. In this case, when a router is added to the
network segment and may become a DR, the multicast routing table of the original DR is reserved
till the entries of the new DR are created. The packet loss due to the delay for creating multicast
entries is thus prevented.
NOTE
After the delay of the PIM DR switchover is set, downstream receivers may receive two copies of the same
data during the DR switchover, and trigger the assert mechanism. If you do not tend to trigger the assert
mechanism, you need not configure the DR switchover delay.
Figure 5-4 Networking diagram of applying PIM BFD on a multi-router network segment
RouterA
Source
10.1.7.1/24 PIM-SM
RouterC
GE2/0/0
10.1.1.2/24
RouterB
GE2/0/0
10.1.1.1/24
User1 User2

1. Configure PIM BFD on the interface that is connected to the host network segment.
2. Configure the PIM DR switching delay on the interface that is connected to the host network
segment.
Data Preparation
l Parameters of a PIM BFD session
l PIM DR switching delay
Procedure
Step 1 Configure an IP address for each interface and a unicast routing protocol.
Step 2 Enable BFD globally and configure PIM BFD on an interface.
# Enable BFD globally on Router B and Router C, enable PIM BFD on the interface that is
connected to the host network segment, and configure PIM BFD parameters. Configuration
procedures of Router C are similar to those of Router B, and are not mentioned here.
[RouterB] bfd
[RouterB-bfd] quit
[RouterB-GigabitEthernet2/0/0] pim bfd enable
[RouterB-GigabitEthernet2/0/0] pim bfd min-tx-interval 100 min-rx-interval 100
detect-multiplier 3
Step 3 Configure the PIM DR switching delay

# Configure the PIM DR switching delay on Router B and Router C. The configuration
procedures of Router C are similar to those of Router B, and are not mentioned here.
[RouterB-GigabitEthernet2/0/0] pim timer dr-switch-delay 20
[RouterB] quit
Step 4 Verify the configuration

# Run the display pim interface verbose command, and you can view detailed information
about the PIM interface. The information about the PIM interface on Router B indicates that the
DR on the host network segment is Router C, and the interface is enabled with PIM BFD and
configured with the switching delay.
<RouterB> display pim interface GigabitEthernet2/0/0 verbose
PIM version: 2
PIM mode: Sparse
PIM state: up
PIM DR: 10.1.1.2
PIM Hello interval: 30 s
PIM Hello override interval (negotiated): 2500 ms
PIM Hello override interval (configured): 2500 ms

PIM Silent: disabled

PIM generation ID: 0XF5712241
PIM Hello hold interval: 105 s
PIM Hello assert interval: 180 s
PIM triggered Hello delay: 5 s
PIM state-refresh capability on link: non-capable
PIM BSR domain border: disabled
PIM BFD: enable
PIM BFD min-tx-interval: 100 ms
PIM BFD min-rx-interval: 100 ms
PIM BFD detect-multiplier: 3
PIM dr-switch-delay timer : 20 s
Number of routers on network not using DR priority: 0
Number of routers on network not using LAN delay: 0
# Run the display pim bfd session command to display the BFD session on each router, and
you can check whether the BFD session on each router is set up.
<RouterB> display pim bfd session
Total 1 BFD session Created
GigabitEthernet2/0/0 (10.1.1.1): Total 1 BFD session Created
Neighbor ActTx(ms) ActRx(ms) ActMulti Local/Remote State
10.1.1.2 100 100 3 8192/8192 Up
# Run the display pim routing-table command to view the PIM routing table. Router C acts as
the DR. (S, G) and (*, G) entries exist. The display is as follows:
(*, 225.1.1.1)
RP: 10.1.5.2
UpTime: 00:13:46
(10.1.7.1, 225.1.1.1)
RP: 10.1.5.2
UpTime: 00:00:42
----End
Configuration Files
Router A needs to be configured only with basic PIM-SM functions that are not most of concern
in this example. Therefore, the configuration file of Router A is not mentioned here.

The configuration file of Router B is as follows. The configuration file of Router C is similar to
that of Router B and is not mentioned here.
#
sysname RouterB
#
#
bfd
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 10.1.2.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
pim sm
igmp enable
pim bfd enable
pim bfd min-tx-interval 100 min-rx-interval 100 detect-multiplier 3
pim timer dr-switch-delay 20
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
return
5.15.4 Example for Configuring PIM GR
In multicast applications, if a device performs the active/standby switchover, the new main
control board deletes the multicast forwarding entries on the interface board and rebuilds the
PIM routing table and PIM forwarding table. During this process, multicast traffic of users is
interrupted.
Deploying PIM GR on an IPTV network protects the core devices and edge devices. When a
device on the IPTV network performs the active/standby switchover, the interface board can
maintain the normal forwarding of multicast data, which increases the fault tolerance capacity
of the devices on the network.
In the network shown in Figure 5-5, multicast services are deployed and PIM GR is configured
on Router C. During the process that Router C forwards multicast data to receiver, the active
main control board backs up the PIM routing entries and Join/Prune messages that need to be
sent to upstream device to the standby main control board. When Router C performs the active/
standby switchover, the interface board maintains the original forwarding entries, which ensures
the smooth forwarding of multicast data. Therefore, the receiver can normally receive multicast
data from the multicast source when the device performs the active/standby switchover.

Figure 5-5 Networking diagram of PIM GR
Ethernet
Leaf networks
RouterA
POS1/0/0 POS2/0/0
Source
GE2/0/0 POS1/0/0 POS1/0/0 GE2/0/0
Router B RouterC
Receiver
PIM-SM HostA
Ethernet
Device Interface IP Address

RouterA POS1/0/0 192.168.2.1/24
GE2/0/0 10.110.1.1/24
RouterB POS1/0/0 192.168.2.2/24
POS2/0/0 192.168.4.1/24
RouterC POS1/0/0 192.168.4.2/24
GE2/0/0 10.110.2.1/24
1. Configure IP addresses for the interfaces and a unicast routing protocol on each router.
2. Enable unicast GR on each router and set unicast GR period.
3. Enable the multicast function, enable PIM-SM on the interfaces of routers, and enable
IGMP on the interface connecting router to the host.
4. Configure a RP. Configure a same static RP on routers.
5. On Router C, enable PIM GR and set the GR period.
Data Preparation
l Multicast source address (in this example, S is 10.110.1.100)

l Multicast group address (in this example, G is 225.1.1.1)
l Unicast GR period
l PIM GR period

Procedure
Step 1 Configure IP addresses for the interfaces and a unicast routing protocol on each router.
# Based on Figure 5-5, configure IP addresses and masks for the interfaces on each router.
Configure OSPF as the unicast routing protocol running between routers to ensure IP
interworking between Router A, Router B, and Router C. The detailed configuration is not
mentioned here.
Step 2 Enable unicast GR and set the GR period.
# Enable unicast GR and set the GR period to 200 seconds on each router. The configurations
on Router A and Router B are similar to those on Router C. The detailed configuration procedures
[RouterC] ospf 1
[RouterC-ospf-1] opaque-capability enable
[RouterC-ospf-1] graceful-restart
[RouterC-ospf-1] graceful-restart period 200
[RouterC-ospf-1] quit
Step 3 Enable the multicast function, enable PIM-SM on the interfaces of routers, and enable IGMP
on the interface connecting router and the host.
# Enable the multicast function on all routers, and enable PIM-SM on the interfaces of the
routers, and enable IGMP on the interface connecting Router C to the host. The configurations
# Create a loopback interface on Router A and enable PIM-SM on the interface.

[RouterA-Loopback0] ip address 1.1.1.1 255.255.255.255
[RouterA-Loopback0] pim sm
[RouterA-Loopback0] quit
# Configure a same static RP on each router. The configurations on Router B and Router C are
similar to those on Router A. The detailed configuration procedures are not mentioned here.
[RouterA] pim
[RouterA-pim] quit
Step 5 Enable PIM GR and set the PIM GR period.
# On Router C, enable PIM GR and set the PIM GR period to 300 seconds.
[RouterC] pim
[RouterC-pim] graceful-restart
[RouterC-pim] graceful-restart period 300
[RouterC-pim] quit

# The multicast source (10.110.1.100) sends data to the multicast group (225.1.1.1). Host A
sends IGMP Report message to join multicast group and can receive the data from the multiast
source. Before Router C performs active/standby switchover, run the display pim routing-
table command on Router B and Router C to view PIM routing table. The command output are
as follows:
<RouterB> display pim routing-table
(*, 225.1.1.1)
RP: 1.1.1.1
UpTime: 01:52:38
1: Pos2/0/0
(10.110.1.100, 225.1.1.1)
RP: 1.1.1.1
UpTime: 01:52:38
1: Pos2/0/0
(*, 225.1.1.1)
RP: 1.1.1.1
UpTime: 01:51:24
Protocol: igmp, UpTime: 01:51:24, Expires: -
(10.110.1.100, 225.1.1.1)
RP: 1.1.1.1
UpTime: 01:51:24
Protocol: pim-sm, UpTime: 01:51:24, Expires: -
# run the active/standby switchover command on Router C:

[RouterC] slave switchover
After Router C performs active/standby switchover, during PIM GR, run the display pim
routing-table command on Router B and Router C to view PIM routing table. The command
output are as follows:


(*, 225.1.1.1)
RP: 1.1.1.1
UpTime: 02:52:38
1: Pos2/0/0
(10.110.1.100, 225.1.1.1)
RP: 1.1.1.1
UpTime: 02:52:38
1: Pos2/0/0
(*, 225.1.1.1)
RP: 1.1.1.1
UpTime: 02:51:24
Protocol: igmp, UpTime: 02:51:24, Expires: -
(10.110.1.100, 225.1.1.1)
RP: 1.1.1.1
UpTime: 02:51:24
In a normal multicast network, the downstream router periodically sends Join/Prune messages
upstream to refresh the timeout period of PIM routing entries on the upstream, thereby ensuring
normal multicast data forwarding.
If the GR function is not configured on Router C, the new active main control board deletes the
multicast forwarding entries on the interface board, receives IGMP Report messages from the
host again, and re-creates PIM routing entries. During this process, multicast traffic is
interrupted.
From the preceding command output, it can be found that after Router C performs active/standby
switchover, the downstream interface of Router B remains unchanged. That is, after Router C
performs active/standby switchover, Router C sends the backed up Join messages upstream. In

this way, multicast forwarding entries can be maintained during GR to ensure non-stop multicast
data forwarding.
During the process of restoring multicast routing entries on Router C after active/standby
switchover, users can receive multicast data normally and services are not interrupted.
----End
Configuration Files
#
sysname RouterA
#
#
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.1.1 255.255.255.0
pim sm
#
interface Loopback0
ip address 1.1.1.1 255.255.255.255
pim sm
#
ospf 1
opaque-capability enable
graceful-restart period 200
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 10.110.1.0 0.0.0.255
network 1.1.1.1 0.0.0.0
#
pim
static-rp 1.1.1.1
#
return

#
sysname RouterB
#
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.2 255.255.255.0
pim sm
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.4.1 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0

network 192.168.2.0 0.0.0.255

network 192.168.4.0 0.0.0.255
#
pim
static-rp 1.1.1.1
#
return

#
sysname RouterC
#
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.4.2 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.2.1 255.255.255.0
pim sm
igmp enable
#
ospf 1
area 0.0.0.0
network 10.110.2.0 0.0.0.255
network 192.168.4.0 0.0.0.255
#
pim
static-rp 1.1.1.1
graceful-restart
#
return

Configuration Guide - IP Multicast 6 MSDP Configuration
6 MSDP Configuration
About This Chapter
This chapter describes the MSDP fundamentals and configuration steps, and maintenance for
MSDP functions, along with typical examples.
6.1 MSDP Introduction
This section describes basic MSDP functions and MSDP features supported by the NE80E/
40E.
6.2 Configuring PIM-SM Inter-domain Multicast
This section describes how to configure PIM-SM inter-domain MSDP peers in an AS.
6.3 Configuring an Anycast RP in a PIM-SM Domain
This section describes how to configure an anycast RP.
6.4 Managing MSDP Peer Connections
This section describes how to manage MSDP peers connections.
6.5 Configuring SA Cache
This section describes how to configure SA Cache.
6.6 Configuring the SA Request
This section describes how to configure an SA request.
6.7 Transmitting Burst Multicast Data Between Domains
This section describes how to transmit burst multicast data between domains.
6.8 Configuring the Filtering Rules for SA Messages
This section describes how to configure the filtering rules for SA messages.
6.9 Configuring MSDP Authentication
This section describes how to configure MSDP MD5 authentication and Key-Chain
authentication to enhance the security of the connections between MSDP peers.
6.10 Maintaining MSDP
This section describes how to clear MSDP statistics, reset connections between MSDP peers,
and monitor the running status of MSDP.

6 MSDP Configuration Configuration Guide - IP Multicast
This section provides several configuration examples of MSDP.

6.1 MSDP Introduction

This section describes basic MSDP functions and MSDP features supported by the NE80E/
40E.
6.1.1 MSDP Overview

6.1.2 MSDP Features Supported by the NE80E/40E
6.1.1 MSDP Overview
In the general PIM-SM mode, a multicast source registers only with the local rendezvous point
(RP). The information on the inter-domain multicast sources is isolated. The RP knows only the
source in its domain, establishes a multicast distribution tree (MDT) in its domain, and distributes
the data sent by the source to the local users.
A type of mechanism is required to enable the local RP to share the information on the multicast
sources of other domains. By means of the mechanism, the local RP can send Join messages to
the multicast sources of other domains and establish MDTs. Multicast packets can thus be
transmitted across domains.
The Multicast Source Discovery Protocol (MSDP) is an inter-area multicast solution based on
multiple interconnected PIM-SM domains, and can solve the preceding problem.
MSDP achieves this objective by setting up the MSDP peer relationship between RPs of different
domains. MSDP peers share the information on multicast sources by sending Source Active
(SA) messages. They transmit the (S, G) information from the RP that the source S registers
with to other RPs connected to members of G.
MSDP peers are connected through the TCP connection. MSDP peers perform the RPF check
on received SA messages.
NOTE
MSDP is applicable only to PIM-SM domains, and useful only for the Any-Source Multicast (ASM) mode.
6.1.2 MSDP Features Supported by the NE80E/40E
PIM-SM Inter-Domain Multicast

When a multicast network is divided into multiple PIM-SM domains, MSDP is used to connect
RPs in each domain to share the multicast source information. In this manner, hosts in a domain
can receive multicast data sent by multicast sources in other domains.
You can configure intra-AS MSDP peers, inter-AS MSDP peers, and static RPF peers.
PIM-SM Intra-domain Anycast RP

After an anycast RP is applied to a PIM-SM domain, the multicast source registers with the
nearest RP and receivers send Join messages to the nearest RP. This reduces the burden of a
single RP, implements RP backup, and optimizes the forwarding path.

You can use a loopback interface as a C-RP or a static RP and specify the logical RP address
for an SA message.
Configuring Control Parameters for Maintaining MSDP Peer Connections

In the NE80E/40E, you can set up and tear down an MSDP session, and configure the period
for retrying to send TCP connection requests to the remote MSDP peers.
Configuring SA Cache
By default, SA-Cache is enabled on routers. Therefore, routers can locally store the (S, G)
information carried in SA messages. When required to receive the multicast data, the routers
can obtain the (S, G) information from the SA-Cache.
You can set the maximum number of cached (S, G) entries, which can effectively prevent the
Denial of Service (DoS) attack.
You can disable SA-Cache on a router. After the SA-Cache on a router is disabled, the router
does not locally store the (S, G) information carried in SA messages. When the router needs to
receive multicast data, it needs to wait for the SA message to be sent by its MSDP peer in the
next period. This causes a delay for receivers to obtain multicast source information.
Controlling SA Requests
Certain routers cannot be enabled with SA Cache or the capacity of SA Cache on these routers
is too small. When these routers need to receive multicast data, they cannot immediately obtain
the valid (S, G) information but need to wait for the SA message to be sent by their MSDP peers
in the next period.
If SA Cache is enabled on the remote MSDP peer and the capacity of the SA Cache is large, you
can configure "sending SA request messages" on the local router to reduce the period during
which receivers obtain multicast source information.
At the same time, you can also configure the filtering rules for receiving SA request messages
on the remote MSDP peers.
Transmitting Burst Multicast Data

When the interval for a certain multicast source to send multicast data is longer than the timeout
period of an (S, G) entry, the source DR can only encapsulate burst multicast data in Register
messages and send them to the source RP. The source RP uses SA messages to transmit (S, G)
information to the remote RP. The remote RP then sends an (S, G) Join message towards the
multicast source to create an SPT. Because of the timeout of the (S, G) entry, the remote user
cannot receive the multicast data sent by S.
The NE80E/40E supports the transmission of burst multicast data. You can enable the function
of encapsulating a multicast data packet in an SA message on the source RP. The source RP can
then encapsulate multicast data in an SA message and send the message out. After receiving the
SA message, the remote RP decapsulates the message, and then forwards multicast data to hosts
in the domain along the RPT.
Setting the TTL threshold can limit the transmission scope of a multicast data packet contained
in an SA message. After receiving an SA message containing a multicast data packet, an MSDP
peer checks the TTL value in the IP header of the multicast packet. If the TTL value is equal to
or smaller than the threshold, the MSDP peer does not forward the SA message to the specific

remote peers. If the TTL value is greater than the threshold, the MSDP peer reduces the TTL
value in the IP header of the multicast packet by 1, and then encapsulates the multicast packet
in an SA message and sends the message out.
Rules for Creating, Receiving, and Forwarding SA Messages

By default, MSDP routers receive all SA messages that pass the RPF check and forward them
to all MSDP peers.
To control the transmission of SA messages between MSDP peers, you can configure filtering
rules by using the following methods:
l Setting rules for filtering SA messages based on multicast sources on the source RP
The source RP filters active multicast sources that register with the local router, and then
determines whether to send (S, G) entries based on the rules.
l Setting rules for filtering SA messages received from remote MSDP peers
When an SA message sent by a remote MSDP peer reaches the local router, the router
determines whether to receive the message based on the rules.
l Setting rules for filtering SA messages forwarded to remote MSDP peers
Before forwarding an SA message to a remote MSDP peer, the local router determines
whether to forward it based on the rules.
Multi-Instance MSDP
MSDP peer relationships can be set up between interfaces on multicast routers that belong to
the same instance (including the public instance and VPN instance). MSDP peers exchange SA
message with each other. The inter-domain VPN multicast is thus implemented.
Multicast routers on which multi-instance is applied maintain a set of MSDP mechanisms for
each instance. Multicast routers also guarantee the information separation among different
instances; therefore, only MSDP and PIM-SM that belong to the same instance can interact.
By applying multi-instance, the NE80E/40E implements inter-domain VPN multicast.
NOTE
For details of inter-domain VPN multicast, refer to the chapter "Multicast VPN Configuration" in the
HUAWEI NetEngine80E/40E Router Configuration Guide - IP Multicast.
MSDP Authentication
Configuring MSDP MD5 or Key-Chain authentication can improve the security of TCP
connections set up between MSDP peers. Note that the MSDP peers must be configured with
the same authentication password; otherwise, the TCP connection cannot be set up between
MSDP peers and MSDP messages cannot be transmitted.
6.2 Configuring PIM-SM Inter-domain Multicast

This section describes how to configure PIM-SM inter-domain MSDP peers in an AS.
6.2.2 Configuring Intra-AS MSDP Peers
6.2.3 Configuring Inter-AS MSDP Peers on MBGP Peers

6.2.4 Configuring Static RPF Peers

When a large multicast network is divided into multiple PIM-SM domains, MSDP is used to
connect RPs of various domains to share the source information. In this manner, hosts in a domain
can receive multicast data sent by multicast sources in other domains.
To ensure that all RPs in the network can share the source information, reduce the scale of an
MSDP connected graph. It is recommended to configure MSDP peer relationships between all
RPs, including static RPs and C-RPs, in the network.
To ensure that SA messages transmitted between MSDP peers are not interrupted by RPF rules
and to reduce redundant traffic, the following solutions are recommended:
l Configuring all MSDP peers in an AS to join the same mesh group

l Using the same interface address to set up MBGP peer relationships between inter-AS
MSDP peers or specifying inter-AS MSDP peers as RPF peers of each other
NOTE
Both BGP and MBGP can be used to set up inter-AS EBGP peer relationships. MBGP is recommended
because MBGP does not affect the unicast topology of a network.
Before configuring PIM-SM inter-domain multicast, complete the following tasks:
l Configuring a unicast routing protocol to enable interworking at the network layer

l Enabling IP multicast
l Configuring a PIM-SM domain to implement intra-domain multicast
Data Preparation
To configure PIM-SM inter-domain multicast, you need the following data.
No. Data
1 Address of a remote MSDP peer
2 Type and number of the local interface connected to MSDP peers
3 Description of an MSDP peer
4 Name of a mesh group
6.2.2 Configuring Intra-AS MSDP Peers

Context
Do as follows on the RPs of all PIM-SM domains that belong to the same AS:
Procedure
Step 1 Run:
system-view
The system is displayed.

Step 2 Run:
msdp [ vpn-instance vpn-instance-name ]
MSDP is enabled in the public network instance or VPN instances and the MSDP view is
displayed.
Step 3 Run:
peer peer-address connect-interface interface-type interface-number
An MSDP peer connection is configured

The parameters of the command are explained as follows:
l peer-address: specifies the address of a remote MSDP peer.
l interface-type interface-number: specifies the local interface connected to the remote MSDP
peer.
NOTE
The system does not advertise routes on MTIs to VPNs; therefore, it is not allowed to use MTIs to set up
an MSDP peer connection.

peer peer-address description text
The description of a remote MSDP peer is added.

This configuration helps to differentiate remote MSDP peers and manage the connections with
the remote MSDP peers.
l peer-address specifies the address of a remote MSDP peer.
l text: specifies the description text. The text is a string of 80 characters.
Step 5 Run:
peer peer-address mesh-group name
A remote MSDP peer is configured to join a mesh group.

That is, the remote MSDP peer is acknowledged as a member of the mesh group.
The parameters of this command are explained as follows:
l name: specifies the name of a mesh group. The members of the same mesh group use the
same mesh group name.
Note the following:

l MSDP peer connections must be set up between all members of the same mesh group.
l All members of the mesh group must acknowledge each other as a member of the group.
l An MSDP peer can belong to only one mesh group. If an MSDP peer is configured to join
different mesh groups for multiple times, only the latest configuration is valid.
----End
6.2.3 Configuring Inter-AS MSDP Peers on MBGP Peers
Context
Establish the MBGP peer relationship between two RPs of different ASs and do as follows on
the MBGP peers:
NOTE
If the two RPs set up the BGP peer relationship, it is not necessary to set up the MBGP peer relationship
between them.
For details of the configuration of MBGP peers, refer to the chapter MBGP Configuration in the HUAWEI
Procedure
Step 1 Run:
system-view
Step 2 Run:
MSDP is enabled in the public network instance or VPN instance, and the MSDP view is
displayed.
Step 3 Run:
An MSDP peer connection is configured.
l peer-address: specifies the address of a remote MSDP peer. The address is the same as that
of the remote BGP or MBGP peer.
peer. The interface is the same as the local BGP or MBGP interface.

The description of the MSDP peer is added.
The configuration helps to distinguish the remote MSDP peers and manage the connections with


----End
6.2.4 Configuring Static RPF Peers
Context
NOTE
If Configuring Inter-AS MSDP Peers on MBGP Peers is complete, skip the configuration.
Do as follows on two RPs of different ASs:
Procedure
Step 1 Run:
system-view
Step 2 Run:
MSDP is enabled in the public network instance or VPN instance, and the MSDP view is
displayed.
Step 3 Run:
An MSDP peer connection is configured.

peer.

The description of a remote MSDP peer is added.
The configuration helps to distinguish remote MSDP peers and manage the connections with

l text: specifies the description text. The text is a string of up to 80 characters.
Step 5 Run:
static-rpf-peer peer-address
A remote MSDP peer is statically specified as an RPF peer.

peer-address specifies the address of a remote MSDP peer.
----End

Procedure
l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] brief command
to check the brief information about the statuses of all remote peers that establish MSDP
peer relationships with the local host.
l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] peer-status
[ peer-address ] to check the detailed information about the statuses of the specified remote
peers that establish the MSDP peer relationships with the local host.
----End
Example
<HUAWEI> display msdp brief
MSDP Peer Brief Information of VPN-Instance: public net
Configured Up Listen Connect Shutdown Down
2 2 0 0 0 0
Peer's Address State Up/Down time AS SA Count Reset Count

192.168.2.1 UP 01:07:08 200 8 0
192.168.4.2 UP 00:06:39 100 13 0
6.3 Configuring an Anycast RP in a PIM-SM Domain

This section describes how to configure an anycast RP.
6.3.2 Configuring the Interface Address of an RP
6.3.3 Configuring a C-RP
6.3.4 Statically Configuring an RP
6.3.5 Configuring an MSDP Peer
6.3.6 Specifying the Logical RP Address for an SA Message

In a traditional PIM-SM domain, each multicast group can be mapped to only one RP. When
the network is overloaded or the traffic is too concentrated, many network problems are caused.
For example, the pressure of the RP is too heavy, routers converge slowly after the RP fails, and
the multicast forwarding path is not optimal.
After anycast RPs are applied in a PIM-SM domain, the source registers with the nearest RP and
hosts sends Join messages to the nearest RP. That is, the load of a single RP is abated, the RP
backup is implemented, and the forwarding path is optimized.

The recommended configuration solutions are as follows:

l Configure loopback interfaces on multiple routers in the PIM-SM domain respectively,
assign the same IP address to the loopback interfaces, and advertise the IP address by using
unicast routes.
l Configure the loopback interfaces on the routers as C-RPs or configure the address of the
loopback interface as a static RP on all routers in the PIM-SM domain.
l Set up the MSDP peer relationship between the routers. If the number of routers is greater
than three, it is recommended to set up the MSDP peer relationship between the routers
and configure them to join the same mesh group.
l Specify the logical RP address to transmit SA messages between the MSDP peers.
Before configuring an anycast RP in a PIM-SM domain, complete the following tasks:
l Configuring a unicast routing protocol to implement interconnection at the network layer
l Configuring a PIM-SM domain without any RP
Data Preparation
To configure an anycast RP in a PIM-SM domain, you need the following data.
No. Data
1 RP address
2 Interface and address of the local MSDP peer
3 Interface and address of the remote MSDP peer
4 Description of an MSDP peer
6.3.2 Configuring the Interface Address of an RP
Context
Use a unicast routing protocol in the current network to advertise the address of the newly
configured RP interface. Ensure that all routers in the network have a route to the RP.
In the PIM-SM domain, do as follows on multiple routers on which the anycast RP is to be
configured:
Procedure
Step 1 Run:
system-view

Step 2 Run:
interface loopback interface-number
The loopback interface view is displayed.

Multiple RPs can use the same IP address in a network. The RPs, therefore, are configured on
the loopback interface.
Step 3 Run:
ip address ip-address { mask | mask-length }
The address of the loopback interface is configured.

l ip-address: specifies the address of an RP. The RPs configured on multiple devices uses the
same IP address.
l mask | mask-length: specifies the address mask of the loopback interface.
Step 4 Run:
pim sm
PIM-SM is enabled for the RP interface.
NOTE
Before configuring a dynamic RP, you need to run this command. This command is not required when you
configure a static RP.
----End
6.3.3 Configuring a C-RP
Context
NOTE
l If the PIM-SM network uses a static RP, the configuration is not necessary.
l If the PIM-SM network uses a BSR-RP, the configuration is mandatory. Before configuring a C-RP,
configure a BSR and BSP boundary. The BSR address cannot be the same as the C-RP address.
Do as follows on multiple routers on which an anycast RP is to be configured in the PIM-SM

domain:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
c-rp loopback interface-number

An interface is specified as RP.
----End
6.3.4 Statically Configuring an RP
Context
NOTE
l When the PIM-SM network uses a BSR-RP, the configuration is not necessary.
l When the PIM-SM network uses a static RP, the configuration is mandatory.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
static-rp rp-address
The RP address is configured.

rp-address specifies the IP address of the static RP.
----End
6.3.5 Configuring an MSDP Peer
Context
Do as follows on multiple routers on which an anycast RP is to be created:
NOTE
If the number of routers configured with the RPs that have the same IP address exceeds two, ensure the
interconnection between the routers that set up MSDP peer relationship.
Procedure
Step 1 Run:
system-view

Step 2 Run:

MSDP is enabled in the public network instance or the VPN instance, and the MSDP view is
displayed.
Step 3 Run:
An MSDP peer connection is created.

l interface-type interface-number: specifies the local interface.

The description of the MSDP peer is added.
This configuration helps to differentiate remote MSDP peers and manage the connection with


peer peer-address mesh-group name
A remote MSDP peer is configured to join a mesh group.
That is, the remote MSDP peer is acknowledged as a member of the mesh group.
If only two routers are configured with the anycast-RP, this configuration is not necessary.

l name: specifies the name of a mesh group. The members of the same mesh group use the
same mesh group name.
Note the following:
l MSDP peer connections must be set up between all members of the mesh group.
l All members of the mesh group must acknowledge each other as the member of the mesh
group.
l An MSDP peer belongs to only one mesh group. If an MSDP peer is configured to join
different mesh groups for many times, only the last configuration is valid.
----End
6.3.6 Specifying the Logical RP Address for an SA Message

Context
After receiving an SA message, an MSDP peer performs the RPF check on the message. If the
remote RP address carried in the SA message is the same as the local RP address, the SA message
is discarded.
Do as follows on the routers on which the anycast RP is to be configured:
Procedure
Step 1 Run:
system-view

Step 2 Run:
The MSDP view is displayed.

Step 3 Run:
originating-rp interface-type interface-number
The logical RP interface is configured. The logical RP interface cannot be the same as the actual
RP interface. It is recommended to configure the logical interface as the MSDP peer interface.
After the originating-rp command is used, the logical RP address carried in the SA message
sent by the router replaces the RP address in the IP header of the SA message, and the SA message
can pass the RPF check after reaching the remote router.
NOTE
The system does not advertise routes on the MTIs to VPNs; therefore, the MTIs cannot be used as logical
RPs.
----End

Procedure
to check the the brief information of the MSDP peer status.
l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table
command to check the information about the RP corresponding to the PIM routing table.
----End
Example
Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] brief command. If the
brief information about the remote MSDP peer status is displayed, it means that the configuration
succeeds. For example:
1 1 0 0 0 0


2.2.2.2 UP 00:10:17 ? 0 0
Run the display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table

command. If the RP information corresponding to the routing table is displayed, it means that
the configuration succeeds. For example:
<HUAWEI> display pim routing-table
(10.11.1.2, 225.1.1.1)
RP: 7.7.7.7 (local)
UpTime: 00:01:57
Protocol: pim-sm, UpTime: - , Expires: -
6.4 Managing MSDP Peer Connections

This section describes how to manage MSDP peers connections.
6.4.2 Controlling the Sessions Between MSDP Peers
6.4.3 Adjusting the interval for Retrying Setting up an MSDP Peer Connection
MSDP peers are connected by the TCP connection (the port number is 639). Users can close or
reestablish a TCP connection, and flexibly control the sessions set up between MSDP peers.
When a new MSDP peer is created, or when a closed MSDP peer connection is restarted, or
when a faulty MSDP peer tries recovering, the TCP connection needs to be immediately set up
between MSDP peers. Users can flexibly adjust the interval for retrying setting up an MSDP
peer connection.
Before managing MSDP peer connections, complete the following tasks:

l Configuring PIM-SM Inter-domain Multicast or Configuring an Anycast RP in a
PIM-SM Domain

Data Preparation
To manage MSDP peer connections, you need the following data.
No. Data
2 Interface type and interface number of the local router
6.4.2 Controlling the Sessions Between MSDP Peers
Context
Do as follows on the router on which the MSDP peer is created:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
shutdown peer-address
A session with the remote MSDP peer is closed.

l After the session with the remote MSDP peer is closed, the TCP connection is closed, the
peers no longer transmit SA messages, and the peers do not re-try setting up the connection.
The configuration, however, is saved.
l You can run the undo shutdown peer-address command to open the session with the remote
MSDP peer, and reestablish the TCP connection.
----End
6.4.3 Adjusting the interval for Retrying Setting up an MSDP Peer

Connection
Context
Do as follows on the router on which the MSDP peer is created:

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
timer retry interval
The period for retrying sending the TCP connection request to the remote MSDP peer is set
----End
Procedure
to check the brief information about the statuses of all remote peers that establish MSDP
peer relationships with the local host.
[ peer-address ] to check the detailed information about the statuses of the specified remote
peers that establish the MSDP peer relationships with the local host.
----End
Example
2 2 0 0 0 0

192.168.2.1 UP 01:07:08 200 8 0
192.168.4.2 UP 00:06:39 100 13 0
6.5 Configuring SA Cache

This section describes how to configure SA Cache.
6.5.2 Configuring the Maximum Number of (S, G) Entries in the Cache
6.5.3 Disabling the SA Cache Function


By default, SA Cache is enabled on routers on which MSDP peers are configured. The routers
can locally store the (S, G) information carried in SA messages. When the routers need to receive
(S, G) information, the routers can obtain the (S, G) information from the SA Cache.
Setting the maximum number of (S, G) entries can prevent the Denial of Service (DoS) attack.
Users can disable the SA Cache of a router. After the SA Cache of a router is disabled, the
router does not locally store the (S, G) information carried in SA messages. When a router wants
to receive (S, G) data, it needs to waits for the SA message to be sent by its MSDP peer in the
next period. This delays receivers from obtaining multicast data.
Before configuring SA Cache, complete the following tasks:
PIM-SM Domain
Data Preparation
To configure SA Cache, you need the following data.
No. Data
1 Maximum number of (S, G) entries in the SA Cache
6.5.2 Configuring the Maximum Number of (S, G) Entries in the

Cache
Context
Do as follows on the router on which the MSDP peer is configured:
NOTE
If the configuration is not done, default values are used.
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
peer peer-address sa-cache-maximum sa-limit
The maximum number of (S, G) entries is set.

l sa-limit: specifies the maximum number of cached (S, G) entries. The value of configuration
is valid when it is less than the specification of cache. Contrarily, specification of cache is
valid.
----End
6.5.3 Disabling the SA Cache Function
Context
Do as follows on the router on which the MSDP peer is configured:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
undo cache-sa-enable
The SA Cache function is disabled.
NOTE
To reenable SA Cache, run the cache-sa-enable command in the MSDP view.
----End
Procedure
l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] sa-cache [ group-
address | source-address | { 2-byte-as-number | 4-byte-as-number } ] * command to check
(S, G) entries in the SA Cache of the public network instance, VPN instance or all instances.

l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] sa-count [ 2-

byte-as-number | 4-byte-as-number ] command to check the number of (S, G) entries in the
SA Cache of the public network instance, VPN instance or all instances.
----End
Example
Run the display msdp sa-cache command to check (S, G) entries in SA Cache.
<HUAWEI> display msdp sa-cache
MSDP Source-Active Cache Information of VPN-Instance: public net
MSDP Total Source-Active Cache - 3 entries
MSDP matched 3 entries
(8.8.8.8, 225.0.0.200)
Origin RP: 4.4.4.4
Pro: BGP, AS: 10
Uptime: 00:00:33, Expires: 00:05:27
(8.8.8.8, 225.0.0.201)
Origin RP: 4.4.4.4
Pro: BGP, AS: 1.0
Uptime: 00:00:33, Expires: 00:05:27
(8.8.8.8, 225.0.0.202)
Origin RP: 4.4.4.4
Pro: BGP, AS: 65535.65535
Uptime: 00:00:33, Expires: 00:05:27
Run the display msdp sa-count command to check the number of (S, G) entries in SA Cache.
<HUAWEI> display msdp sa-count
MSDP Source-Active Count Information of VPN-Instance: public net
Number of cached Source-Active entries, counted by Peer
Peer's Address Number of SA
10.10.10.10 5
Number of source and group, counted by AS
AS Number of source Number of group
? 3 3
Total 5 Source-Active entries matched
6.6 Configuring the SA Request

This section describes how to configure an SA request.
6.6.2 Configuring "Sending SA Request Messages" on the Local Router
6.6.3 (Optional) Configuring the Filtering Rules for Receiving SA Request Messages
6.6.4 Check the Configuration
The capacity of SA Cache on certain routers is small. When these routers need to receive
multicast data, they cannot immediately obtain the valid (S, G) information and need to wait for
the SA message sent by their MSDP peers in the next period.

If SA Cache is enabled on the remote MSDP peer and the capacity of the SA Cache is large,
configuring "sending SA Request message" on the local router can shorten the period during
which receivers obtain multicast source information.
l When the local router wants to receive (S, G) information, it sends an SA Request message
to a specified remote MSDP peer.
l On receiving the SA Request message, the MSDP peer responds to the SA Request message
with the required (S, G) information. If the "filtering rule of SA Request message" is
configured on the remote MSDP peer, it checks the SA Request messages received from a
specified peers and determines whether to respond according to the checking results.
Before configuring an SA request, complete the following tasks:

PIM-SM Domain
Data Preparation
To configure an SA request, you need the following data.
No. Data
2 Filtering list for receiving SA request messages
6.6.2 Configuring "Sending SA Request Messages" on the Local

Router
Context
Do as follows on the local router:
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
peer peer-address request-sa-enable
Sending SA Request message is configured.

peer-address specifies the address of a remote MSDP peer. When the local router receives a
new Join message from a group, it sends an SA Request message only to peer-address.
----End
6.6.3 (Optional) Configuring the Filtering Rules for Receiving SA

Request Messages
Context
Do as follows on the remote MSDP peer specified by using the peer peer-address request-sa-
enable command. If the configuration is not done, once an SA message reaches, the router
immediately responds to it with an SA message containing the required (S, G) information.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
peer peer-address sa-request-policy [ acl { basic-acl-number | acl-name } ]
The filtering rules for receiving SA Request messages are set.

l peer-address: specifies the address of an MSDP peer that sends the SA Request message.
l acl: specifies the filtering policy. If the ACL is not specified, all SA messages sent by a peer
are ignored. If the ACL is specified, only the SA messages that match the ACL are received
and other SA messages are discarded.
----End
6.6.4 Check the Configuration

Procedure
[ peer-address ] command to check detailed information about the MSDP peer status.
SA Cache of the public network instance, VPN instance, or all instances.
----End

Example
Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] peer-status [ peer-
address ] command, and you can view the SA-Requests field and check whether the
configuration is valid. For example:
<HUAWEI> display msdp peer-status
MSDP Peer Information of VPN-Instance: public net
MSDP Peer 172.40.41.1, AS ?
Description:
Information about connection status:
State: Up
Up/down time: 00:26:41
Resets: 0
Connection interface: GigabitEthernet2/0/14 (172.40.41.2)
Number of sent/received messages: 27/28
Number of discarded output messages: 0
Elapsed time since last connection or counters clear: 00:26:56
Information about (Source, Group)-based SA filtering policy:
Import policy: none
Export policy: none
Information about SA-Requests:
Policy to accept SA-Request messages: 2000
Sending SA-Requests status: enable
Minimum TTL to forward SA with encapsulated data: 0
SAs learned from this peer: 0, SA Cache maximum for the peer: none
Input queue size: 0, Output queue size: 0
Counters for MSDP message:
Count of RPF check failure: 0
Incoming/outgoing SA messages: 16/0
Incoming/outgoing SA requests: 0/0
Incoming/outgoing SA responses: 0/0
Incoming/outgoing data packets: 0/0
Peer authentication: configured
Peer authentication type: Key-Chain
6.7 Transmitting Burst Multicast Data Between Domains

This section describes how to transmit burst multicast data between domains.
6.7.2 Encapsulating a Multicast Data Packet in an SA message
6.7.3 (Optional) Setting the TTL Threshold for Forwarding an SA Message Containing a
Multicast Data Packet

The time during which certain multicast sources send multicast data is long, and is longer than
the timeout of an (S, G) entry. In this case, the source DR encapsulates multicast data packets
in Register messages one by one, and sends the messages to the source RP. The source RP then
uses SA messages to forward (S, G) entries to the remote RP.
The remote RP then sends a Join message to the source DR. An SPT is thus set up. Because of
the timeout of the (S, G) entry, remote users cannot receive multicast data sent by S.
After the function of encapsulating a multicast packet in an SA message is enabled on the source
RP, the source RP encapsulates multicast data in SA messages and sends them out. After

receiving an SA message, a remote RP decapsulates the message and forwards the multicast data
to users in the domain along the RPT.
Setting the TTL threshold can limit the transmission scope of a multicast packet contained in an
SA message. After receiving an SA message containing a multicast packet, an MSDP peer checks
the TTL value in the IP header of the multicast packet. If the TTL value is smaller than or equal
to the threshold, the MSDP peer does not forward the SA message to a specific remote peers. If
the TTL value is greater than the threshold, the MSDP peer reduces the TTL value in the IP
header of the multicast packet by 1, and then encapsulates the multicast packet in an SA message
and sends it out.
Before transmitting burst multicast data between domains, complete the following tasks:
PIM-SM Domain
Data Preparation
To transmit burst multicast data between domains, you need the following data.
No. Data
1 TTL threshold for forwarding an SA message containing a multicast data packet
6.7.2 Encapsulating a Multicast Data Packet in an SA message
Context
Do as follows on the source RP configured with an MSDP peer:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
encap-data-enable

A multicast data packet is encapsulated in an SA message.
By default, the SA message contains only (S, G) information, and does not contain a multicast
data packet.
----End
6.7.3 (Optional) Setting the TTL Threshold for Forwarding an SA

Message Containing a Multicast Data Packet
Context
Do as follows on the router configured with an MSDP peer:
NOTE
If the configuration is not done, default values are used.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
peer peer-address minimum-ttl ttl
The TTL threshold of a multicast data packet is set.
After receiving an SA massage containing a multicast data packet, an MSDP peer forwards the
SA message to a specified remote MSDP peers only when the TTL value of the multicast packet
is greater than the threshold.

l ttl: specifies the value of the TTL threshold. By default, the value is 0.
----End
Procedure


----End
Example
address ] command, and you can view the minimum TTL for forwarding an SA messages
containing a data packet and check whether the configuration is valid. For example:
MSDP Peer 172.40.41.1, AS ?
Description:
State: Up
Resets: 0
Import policy: none
Export policy: none
Run the display msdp sa-cache command to check the information about (S, G) entries in SA
Cache.
l If group-address is specified, the (S, G) entry to which a specified group corresponds is
displayed.
l If source-address is specified, the (S, G) entry to which a specified source corresponds is
displayed.
l If 2-byte-as-number or 4-byte-as-number is specified, the (S, G) entry whose Origin RP
attribute belongs to a specified AS is displayed.
(8.8.8.8, 225.0.0.200)
Origin RP: 4.4.4.4
Pro: BGP, AS: 10
Uptime: 00:00:33, Expires: 00:05:27
(8.8.8.8, 225.0.0.201)
Origin RP: 4.4.4.4
Pro: BGP, AS: 1.0
Uptime: 00:00:33, Expires: 00:05:27
(8.8.8.8, 225.0.0.202)

Origin RP: 4.4.4.4

Pro: BGP, AS: 65535.65535
Uptime: 00:00:33, Expires: 00:05:27
6.8 Configuring the Filtering Rules for SA Messages

This section describes how to configure the filtering rules for SA messages.
6.8.2 Setting Rules for Creating an SA Message
6.8.3 Setting Rules for Receiving an SA Message
6.8.4 Setting Rules for Forwarding an SA Message

By default, MSDP routers receive all SA messages that pass the RPF check and forward them
to all MSDP peers. To control of the transmission of SA messages among MSDP peers, users
can configure various filtering rules by using the following methods:
l Setting the rules for filtering the multicast source of an SA message on the source RP. The
source RP filters active multicast sources that register with the local router, and determines
the (S, G) entries to be sent according to the rules.
l Setting the rules for filtering an SA message received from a remote MSDP peer. When an
SA message sent by a remote MSDP peer reaches a router, the router determines whether
to receive the message based on the rules.
l Setting the rules for filtering an SA message forwarded to a remote MSDP peer. Before
forwarding the SA message to the remote MSDP peer, the router determines whether to
forward it based on the rules.
Before configuring the filtering rules for SA messages, complete the following tasks:
PIM-SM Domain
Data Preparation
To configure the filtering rules for SA messages, you need the following data.
No. Data
1 Filtering list for creating SA messages

No. Data
2 Filtering list for receiving SA messages
3 Filtering list for forwarding SA messages
6.8.2 Setting Rules for Creating an SA Message
Context
Do as follows on the source RP configured with an MSDP peer:
NOTE
If the configuration is not done, an SA message created by the source RP contains the information of all
local active sources.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
import-source [ acl { acl-number | acl-name } ]
The rules for filtering the multicast source of an SA message are set.
l acl: specifies the filtering list based on multicast sources. The SA message created by an
MSDP peer contains the local source information that match the filtering rules. The MSDP
peer can thus control the local (S, G) information.
l If the import-source command with acl is used, the SA message does not advertise any
information about the local active source.
----End
6.8.3 Setting Rules for Receiving an SA Message
Context
Do as follows on the router configured with MSDP:

NOTE
If the configuration is not done, the router receives all SA messages that pass the RPF check.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
peer peer-address sa-policy import [ acl { advanced-acl-number | acl-name } ]
The rules for filtering an SA message received from a remote MSDP peer are set.
l acl: specifies the advanced filtering list. Only the (S, G) information that passes the filtering
of the ACL is received. The (S, G) information is contained in an SA message sent by the
peer specified by peer-address .
l If the peer peer-address sa-policy import command without acl is used, the router does not
receive any (S, G) information from the peer specified by peer-address.
----End
6.8.4 Setting Rules for Forwarding an SA Message
Context
Do as follows on the router enabled with MSDP:
NOTE
If the configuration is not done, the router forwards all SA messages that pass the RPF check.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
peer peer-address sa-policy export [ acl { advanced-acl-number | acl-name } ]
The rules for filtering an SA message forwarded to a remote MSDP peer is set.


l acl: specifies the advanced filtering list. Only the (S, G) information that matches the ACL
rule is forwarded to the peer specified by peer-address.
l If the peer peer-address sa-policy export command without acl is used, the router does not
forward any (S, G) information to the peer specified by peer-address.
----End
Procedure
----End
Example
address ] command, and you can view information about the (Source, Group)-based SA filtering
policy field and check whether the configuration is valid. For example:
MSDP Peer 172.40.41.1, AS ?
Description:
State: Up
Resets: 0
Import policy: 3000
Export policy: 3002
Run the display msdp sa-cache command to check the information about (S, G) entries in SA
Cache.

l If group-address is specified, the (S, G) entry to which a specified group corresponds is

displayed.
l If source-address is specified, the (S, G) entry to which a specified source corresponds is
displayed.
l If 2-byte-as-number or 4-byte-as-number is specified, the (S, G) entry whose Origin RP
attribute belongs to a specified AS is displayed.
(8.8.8.8, 225.0.0.200)
Origin RP: 4.4.4.4
Pro: BGP, AS: 10
Uptime: 00:00:33, Expires: 00:05:27
(8.8.8.8, 225.0.0.201)
Origin RP: 4.4.4.4
Pro: BGP, AS: 1.0
Uptime: 00:00:33, Expires: 00:05:27
(8.8.8.8, 225.0.0.202)
Origin RP: 4.4.4.4
Pro: BGP, AS: 65535.65535
Uptime: 00:00:33, Expires: 00:05:27
6.9 Configuring MSDP Authentication

This section describes how to configure MSDP MD5 authentication and Key-Chain
authentication to enhance the security of the connections between MSDP peers.
6.9.2 Configuring MSDP MD5 Authentication
6.9.3 Configuring MSDP Key-Chain Authentication
Configuring MSDP authentication can enhance the security of the TCP connections between
MSDP peers.
Before configuring MSDP authentication, complete the following tasks:
l Configuring a unicast routing protocol to implement IP interworking between domains

l Configuring PIM-SM domains to implement intra-domain multicast
PIM-SM Domain

Data Preparation
Before configuring MSDP authentication, prepare the following data:
No. Data
1 IP address of the peer to be configured with MSDP authentication
2 Password for MSDP MD5 authentication
3 Key-Chain name for MSDP Key-Chain authentication
6.9.2 Configuring MSDP MD5 Authentication
Context
By default, MSDP MD5 authentication is not configured.
Do as follows on the router configured with MSDP peers:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
peer peer-address password { cipher cipher-password | simple simple-password }
MSDP MD5 authentication is configured.
The MSDP MD5 authentication password is case sensitive and cannot contain any space.
The MSDP peers must be configured with the same authentication password; otherwise, the TCP
connection cannot be set up between MSDP peers and MSDP messages cannot be transmitted.
The authentication password on peers can be in different forms, that is, the password on one end
can be in the cipher text while the password on the peer can be in the plain text.
NOTE
MSDP MD5 authentication and MSDP Key-Chain authentication are mutually exclusive.
The MD5 authentication password that starts and ends with $@$@ is invalid, because $@$@ is used to
distinguish old and new passwords.
----End
6.9.3 Configuring MSDP Key-Chain Authentication

Context
By default, MSDP Key-Chain authentication is not configured.
Do as follows on the router configured with MSDP peers:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
peer peer-address keychain keychain-name
MSDP Key-Chain authentication is configured.

You must configure Key-Chain authentication on both MSDP peers. Encryption algorithms and
passwords configured for Key-Chain authentication on both peers must be the same; otherwise,
the TCP connection cannot be set up between MSDP peers and MSDP messages cannot be
transmitted.
Before configuring MSDP Key-Chain authentication, configure a Key-Chain in accordance with
the configured keychain-name; otherwise, the TCP connection cannot be set up.
NOTE
MSDP MD5 authentication and MSDP Key-Chain authentication are mutually exclusive.
----End

Procedure
to check brief information about MSDP peers.
[ peer-address ] command to check detailed information about MSDP peers.
----End
Example
address ] command, and you can find the Peer authentication and Peer authentication type
fields in the command output. For example:
MSDP Peer 172.40.41.1, AS ?
Description:

State: Up
Resets: 0
Import policy: 3000
Export policy: 3002
SAs learned from this peer: 0, SA-cache maximum for the peer: none
Peer authentication: configured
Peer authentication type: Key-Chain
6.10 Maintaining MSDP

This section describes how to clear MSDP statistics, reset connections between MSDP peers,
and monitor the running status of MSDP.
6.10.1 Clearing Statistics of MSDP Peers
6.10.2 Clearing (S, G) Information in SA Cache
6.10.3 Monitoring the Running Status of MSDP
6.10.1 Clearing Statistics of MSDP Peers
Context
CAUTION
The statistics of MSDP peers cannot be restored after you clear it. So, confirm the action before
you use the command.
Procedure
l Run the reset msdp [ vpn-instance vpn-instance-name | all-instance ] peer [ peer-
address ] command in the user view to clear the TCP connection with a specified MSDP
peer and all statistics of the specified MSDP peer.
l Run the reset msdp [ vpn-instance vpn-instance-name | all-instance ] statistics [ peer-
address ] command in the user view to clear the statistics of an MSDP peer or multiple
MSDP peers of the public network instance, VPN instance, or all instances, if MSDP peers
are not reset.

l Run the reset msdp [ vpn-instance vpn-instance-name | all-instance ] control-message

counters [ peer peer-address ] command in the user view to clear the statistics about the
received, sent, and discarded MSDP messages.
----End
6.10.2 Clearing (S, G) Information in SA Cache

Context
CAUTION
The (S, G) information in SA Cache cannot be restored after you clear it. So, confirm the action
before you use the command.
Procedure
l Run the reset msdp [ vpn-instance vpn-instance-name | all-instance ] sa-cache [ group-
address ] command in the user view to clear the entries in MSDP SA Cache.
----End
6.10.3 Monitoring the Running Status of MSDP

Context
status of MSDP.
Procedure
l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] brief [ state
{ connect | down | listen | shutdown | up } ] command in any view to check brief
information about the MSDP peer status.
[ peer-address ] command in any view to check detailed information about the status of an
MSDP peer of the public network instance, VPN instance, or all instances.
address | source-address | { 2-byte-as-number | 4-byte-as-number } ] * command in any
view to check the (S, G) information in SA Cache.
l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] sa-count [ 2-
byte-as-number | 4-byte-as-number ] command in any view to check the number of (S, G)
entries in MSDP Cache.
l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] control-
message counters [ peer peer-address | message-type { source-active | sa-request | sa-
response | keepalive | notification | traceroute-request | traceroute-reply | data-
packets | unknown-type } ] * command in any view to check statistics about the received,
sent, and discarded MSDP messages.
----End


This section provides several configuration examples of MSDP.
6.11.1 Example for Configuring PIM-SM Inter-Domain Multicast

6.11.2 Example for Configuring Inter-AS Multicast by Using Static RPF Peers
6.11.3 Example for Configuring Anycast RP
6.11.1 Example for Configuring PIM-SM Inter-Domain Multicast
As shown in Figure 6-1, there are two ASs in the network. Each AS contains one or more PIM-
SM domains. The receivers in PIM-SM2 domain are required to receive multicast data sent by
S3 in PIM-SM3 domain and multicast data sent by S1 in PIM-SM1 domain.
Figure 6-1 Networking diagram of configuring PIM-SM inter-domain multicast
AS100 AS200
Loopback0
Loopback0 2.2.2.2/32 Receiver
1.1.1.1/32
PIM-SM2
RouterA
RouterC GE1/0/0
POS2/0/0 POS1/0/0 POS1/0/0 POS2/0/0
POS2/0/0 POS2/0/0
GE1/0/0 RouterB POS3/0/0 RouterD
PIM-SM1
S1 POS3/0/0 RouterF
POS2/0/0
POS2/0/0
RouterE GE1/0/0
PIM-SM3
S3
Loopback0
3.3.3.3/32
MSDP peer
router Interface IP Address router Interface IP Address

RouterA GE1/0/0 10.110.1.1/24 RouterD GE1/0/0 10.110.2.1/24
POS2/0/0 192.168.1.1/24 POS2/0/0 192.168.3.2/24
RouterB POS1/0/0 192.168.2.1/24 RouterE POS2/0/0 192.168.5.1/24
POS2/0/0 192.168.1.2/24 POS3/0/0 192.168.4.2/24

RouterC POS1/0/0 192.168.2.2/24 RouterF GE1/0/0 10.110.3.1/24

POS2/0/0 192.168.3.1/24 POS2/0/0 192.168.5.2/24
POS3/0/0 192.168.4.1/24
Solution: configure MSDP peer relationships between RPs of each PIM-SM domain. The
configuration roadmap is as follows:
1. Configure IP addresses of interfaces on each router, and configure OSPF in the ASs to
ensure that unicast routes are reachable in the ASs.
2. Configure EBGP peers between ASs and configure BGP and OSPF to import routes to each
other to ensure that unicast routes are reachable.
3. Enable multicast and PIM-SM on each interface, configure the boundary of a domain, and
enable IGMP on the interface connected to hosts.
4. Configure a C-BSR and a C-RP. Configure the RPs of PIM-SM1 and PIM-SM2 on ASBRs.
5. Establish the MSDP peer relationship between RPs of each domain. MSDP peers and EBGP
peers between ASs use the same interface address. According to RPF rules, routers receive
SA messages forwarded by the next hop of the route to the source RP.
Data Preparation
l Address of multicast group G: 225.1.1.1/24.
l The AS number of Router A and Router B is 100. Router ID of Router B is 1.1.1.1.
l The AS number of Router C and Router D is 200. Router ID of Router C is 2.2.2.2.
l The AS number of Router E and Router F is 200.
Procedure
Step 1 Configure an IP address and a unicast routing protocol on each router.
# Configure an IP address and mask on each interface as shown in Figure 6-1. Configure OSPF
in the AS. Ensure that the communication between routers is normal at the network layer. Ensure
dynamic routing updates between routers with the help of the unicast routing protocol. The
procedures are not mentioned here.
Step 2 Configure BGP between ASs and configure BGP and OSPF to import routes each other.
# Configure EBGP on Router B and import OSPF routes.
[RouterB] bgp 100
[RouterB-bgp] router-id 1.1.1.1
[RouterB-bgp] peer 192.168.2.2 as-number 200
[RouterB-bgp] import-route ospf 1
[RouterB-bgp] quit
# Configure EBGP on Router C, and then import OSPF routes.

[RouterC] bgp 200
[RouterC-bgp] router-id 2.2.2.2
[RouterC-bgp] peer 192.168.2.1 as-number 100

[RouterC-bgp] import-route ospf 1

[RouterC-bgp] quit
# Import BGP routes to OSPF on Router B. The configuration of Router C is similar to that of
Router B, and is not mentioned here.
[RouterB] ospf 1
[RouterB-ospf-1] import-route bgp
[RouterB-ospf-1] quit
Step 3 Enable multicast on each router and enable PIM-SM on each interface, configure the boundary
of a domain and enable IGMP on the interface connected to hosts.
# Enable multicast on Router B, and enable PIM-SM on each interface. The configurations of
other routers are similar to that of Router B, and are not mentioned here.
[RouterB] multicast routing-enable
[RouterB] interface pos 2/0/0
[RouterB-Pos2/0/0] pim sm
[RouterB-Pos2/0/0] quit
# Configure the BSR boundary on POS 1/0/0 of Router B.

[RouterB-Pos1/0/0] pim bsr-boundary
Configure the domain boundary on POS 1/0/0 and POS 3/0/0 of Router C and the BSR service
boundary on POS 3/0/0 of Router E. The configurations of Router C and Router E are similar
to that of Router B, and are not mentioned here.
# Enable IGMP on interface through which Router D is connected to the leaf network.
[RouterD] interface gigabitethernet 1/0/0
[RouterD-GigabitEthernet1/0/0] igmp enable
Step 4 Configure a C-BSR and a C-RP.

# Configure Loopback 0 interfaces and C-BSRs and C-RPs on Router B. The configurations of
Router C and Router E are similar to those of Router B, and are not mentioned here.
[RouterB-LoopBack0] ip address 1.1.1.1 255.255.255.255
[RouterB-LoopBack0] pim sm
[RouterB] pim
[RouterB-pim] c-bsr loopback 0
[RouterB-pim] c-rp loopback 0
[RouterB-pim] quit
Step 5 Configure MSDP peers.

# Configure MSDP peers on Router B.
[RouterB] msdp
[RouterB-msdp] peer 192.168.2.2 connect-interface pos1/0/0
[RouterB-msdp] quit
# Configure MSDP peers on Router C.

[RouterC] msdp
[RouterC-msdp] peer 192.168.2.1 connect-interface pos1/0/0
[RouterC-msdp] peer 192.168.4.2 connect-interface pos3/0/0
[RouterC-msdp] quit
# Configure MSDP peers on Router E.

[RouterE] msdp
[RouterE-msdp] peer 192.168.4.1 connect-interface pos3/0/0
[RouterE-msdp] quit

# Run the display bgp peer command. You can view BGP peer relationships between routers.
For example, the BGP peer relationship between Router B and Router C is as follows:
<RouterB> display bgp peer
BGP local router ID : 1.1.1.1
Local AS number : 100
Total number of peers : 1 Peers in established state : 1
Peer V AS MsgRcvd MsgSent OutQ Up/Down State
PrefRcv
192.168.2.2 4 200 24 21 0 00:13:09 Established 6
<RouterC> display bgp peer
Peer V AS MsgRcvd MsgSent OutQ Up/Down State
PrefRcv
192.168.2.1 4 100 18 16 0 00:12:04 Established 1
# Run the display bgp routing-table command. You can view the BGP routing table on a
router. For example, the BGP routing table on Router C is as follows:
<RouterC> display bgp routing-table
Total Number of Routes: 5
BGP Local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 1.1.1.1/32 192.168.2.1 0 0 100?
*>i 2.2.2.2/32 0.0.0.0 0 0 ?
*> 192.168.2.0 0.0.0.0 0 0 ?
*> 192.168.2.1/32 0.0.0.0 0 0 ?
*> 192.168.2.2/32 0.0.0.0 0 0 ?
# Run the display msdp brief command. You can view MSDP peer relationships between
routers. The brief information about MSDP peer relationships between Router B, Router C, and
Router E is as follows:
<RouterB> display msdp brief
1 1 0 0 0 0
192.168.2.2 UP 00:12:27 200 13 0
<RouterC> display msdp brief
2 2 0 0 0 0
192.168.2.1 UP 01:07:08 100 8 0
192.168.4.2 UP 00:06:39 200 13 0
<RouterE> display msdp brief
1 1 0 0 0 0
192.168.4.1 UP 00:15:32 200 8 0
# Run the display msdp peer-status command. You can view the detailed information about
the MSDP peers. The detailed information about MSDP peers on Router B is as follows:
<RouterB> display msdp peer-status


MSDP Peer 192.168.2.2, AS 200
Description:
State: Up
Resets: 0
Connection interface: Pos1/0/0 (192.168.2.1)
Import policy: none
Export policy: none
Policy to accept SA-Request messages: none
Sending SA-Requests status: disable
Peer authentication: not configured
Peer authentication type: none
# Run the display pim routing-table command. You can view the PIM routing table on a
router. When S1 (10.110.1.2/24) in PIM-SM1 domain and S3 (10.110.3.2/24) in PIM-SM3
domain send multicast data to G (225.1.1.1/24), Receiver (10.110.2.2/24) in PIM-SM2 domian
can receive the multicast data. The information about the PIM routing tables on Router B and
Router C is as follows:
(10.110.1.2, 225.1.1.1)
RP: 1.1.1.1(local)
Protocol: pim-sm, Flag: SPT EXT ACT
UpTime: 00:00:42
1: Pos1/0/0
(*, 225.1.1.1)
RP: 2.2.2.2(local)
Protocol: pim-sm, Flag: WC RPT
UpTime: 00:13:46
Upstream interface: NULL,
1: Pos2/0/0,
(10.110.1.2, 225.1.1.1)
RP: 2.2.2.2
Protocol: pim-sm, Flag: SPT MSDP ACT
UpTime: 00:00:42


1: Pos2/0/0
(10.110.3.2, 225.1.1.1)
RP: 2.2.2.2
Protocol: pim-sm, Flag: SPT MSDP ACT
UpTime: 00:00:42
1: Pos2/0/0
----End
Configuration Files
#
sysname RouterB
#
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 192.168.1.2 255.255.255.0
pim sm
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.2.1 255.255.255.0
pim sm
pim bsr-boundary
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
pim sm
#
bgp 100
router-id 1.1.1.1
import-route ospf 1
#
ospf 1
import-route bgp
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 1.1.1.1 0.0.0.0
#
pim
c-bsr LoopBack0
c-rp LoopBack0
#
msdp
peer 192.168.2.2 connect-interface Pos1/0/0
#
return

#
sysname RouterC
#

#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.2.2 255.255.255.0
pim sm
pim bsr-boundary
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 192.168.3.1 255.255.255.0
pim sm
#
interface Pos3/0/0
undo shutdown
link-protocol ppp
ip address 192.168.4.1 255.255.255.0
pim sm
pim bsr-boundary
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.255
pim sm
#
bgp 200
router-id 2.2.2.2
import-route ospf 1
#
ospf 1
import-route bgp
area 0.0.0.0
network 192.168.3.0 0.0.0.255
network 192.168.4.0 0.0.0.255
network 2.2.2.2 0.0.0.0
#
pim
c-bsr LoopBack0
c-rp LoopBack0
#
msdp
#
return
#
sysname RouterE
#
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 192.168.5.1 255.255.255.0
pim sm
#
interface Pos3/0/0
undo shutdown
link-protocol ppp
ip address 192.168.4.2 255.255.255.0
pim sm
pim bsr-boundary
#
interface LoopBack0
ip address 3.3.3.3 255.255.255.255
pim sm

#
ospf 1
area 0.0.0.0
network 192.168.4.0 0.0.0.255
network 192.168.5.0 0.0.0.255
network 3.3.3.3 0.0.0.0
#
pim
c-bsr LoopBack0
c-rp LoopBack0
#
msdp
#
return
6.11.2 Example for Configuring Inter-AS Multicast by Using Static

RPF Peers
As shown in Figure 6-2, there are two ASs in the network. Each AS contains one or more PIM-
SM domains; and each PIM-SM domain has 0 or 1 multicast source or receiver. MSDP peer
relationships are required to be set up between PIM-SM domains to share the information about
multicast sources.
Figure 6-2 Networking diagram of configuring inter-AS multicast by using static RPF peers
AS100 AS200
Loopback0
RouterE
POS2/0/0 POS1/0/0
Loopback0
RouterD
RouterC POS2/0/0 PIM-SM2
POS1/0/0
Receiver
100
Receiver
POS2/0/0 PIM-SM1 RouterB Loopback0
RouterG
POS1/0/0
S1
POS1/0/0
RouterA RouterF
PIM-SM3
S2
BGP peers


Router B POS 2/0/0 192.168.2.2/24 Loopback 0 2.2.2.2/32

Router C POS 1/0/0 192.168.1.1/24 Router E POS 2/0/0 192.168.2.1/24
POS 2/0/0 192.168.4.1/24 Router F POS 1/0/0 192.168.5.1/24
Loopback 0 1.1.1.1/32 Loopback 0 3.3.3.3/32
Solution: set up an MSDP peer on RP in each PIM-SM domain. Set up static RPF peer among
MSDP peers. Thus the transmission of source information across sources is implemented without
changing unicast topology. The steps are as follows:
1. Configure an IP address for each interface, configure OSPF in the ASs, configure EBGP
between ASs, and configure BGP and OSPF to import routes into each other.
2. Enable multicast on each router and PIM-SM on each interface, enable IGMP on the
interface connected to hosts, and configure the positions of Loopback 0 interfaces, the C-
BSR, and the C-RP. The Loopback 0 interfaces on Router C, Router D, and Router F act
as C-BSRs and C-RPs of their PIM-SM domains.
3. Set up MSDP peer relationships between RPs in each domain, and the MSDP peer
relationship between Router C and Router D and between Router C and Router F.
4. Specify a static RPF peer for an MSDP peer. The static RPF peers of Router C are Router
D and Router F. Router D and Router F has only one static RPF peer, that is, Router C.
According to RPF rules, routers receive SA messages from static RPF peers.
Data Preparation
l The AS number of Router A, Router B and Router C is 100. The router IDs of the three
routers are 1.1.1.3, 1.1.1.2 and 1.1.1.1 respectively.
l The AS number of Router D and Router E is 200. The router IDs of the two routers are
2.2.2.2 and 2.2.2.1 respectively.
l The AS number of Router F and Router G is 200. The router ID of Router F is 3.3.3.3.
l The name of policy adopted by Router C in filtering the SA message from Router D and
Router F is list-df.
l The name of policy adopted by Router D and Router F in filtering the SA message from
Router C is list-c.
Procedure
Step 1 Configure an IP address for each interface and a unicast routing protocol.
# As shown in Figure 6-2, configure an IP address and mask for each interface. Configure OSPF
in the AS. Configure EBGP between Router A and Router F, Router B, and Router E. Configure
BGP and OSPF to import routes into each other. Ensure the normal communication between
routers on the network layer. Ensure dynamic routing updates between routers through the
unicast routing protocol. The procedures are not mentioned here.
Step 2 Enable multicast on each router and PIM-SM on each interface.

# Enable multicast on each router and enable PIM-SM on each interface. The configurations of
the other routers are similar to that of Router C, and are not mentioned here.
# Configure the BSR boundary on POS 1/0/0 of Router A, POS 2/0/0 of Router B, POS 2/0/0
of Router E and POS 1/0/0 of Router F. The configurations of Router B, Router E, and Router
F are similar to that of Router A, and are not mentioned here.
[RouterA-Pos1/0/0] pim bsr-boundary
Step 3 Configure the Loopback 0 interface, C-BSR, and C-RP.

# Configure Loopback 0 interfaces and positions of the C-BSR and C-RP on Router C, Router
D, and Router F. The configurations of Router D and Router F are similar to that of Router C,
and are not mentioned here.
[RouterC] interface loopback 0
[RouterC-LoopBack0] ip address 1.1.1.1 255.255.255.255
[RouterC-LoopBack0] pim sm
[RouterC-LoopBack0] quit
[RouterC] pim
[RouterC-pim] c-bsr loopback 0
[RouterC-pim] c-rp loopback 0
[RouterC-pim] quit
Step 4 Configure static RPF peers.

# Configure Router D and Router F as static RPF peers of Router C.
[RouterC] ip ip-prefix list-df permit 192.168.0.0 16 greater-equal 16 less-equal 32
[RouterC] msdp
[RouterC-msdp] peer 192.168.3.2 connect-interface pos 1/0/0
[RouterC-msdp] peer 192.168.5.1 connect-interface pos 2/0/0
[RouterC-msdp] static-rpf-peer 192.168.3.2 rp-policy list-df
[RouterC-msdp] static-rpf-peer 192.168.5.1 rp-policy list-df
[RouterC-msdp] quit
# Configure Router C as the static RPF peer of Router D and Router F. The configurations of
Router F are similar to that of Router D, and are not mentioned here.
[RouterD] ip ip-prefix list-c permit 192.168.0.0 16 greater-equal 16 less-equal 32
[RouterD] msdp
[RouterD-msdp] peer 192.168.1.1 connect-interface pos 1/0/0
[RouterD-msdp] static-rpf-peer 192.168.1.1 rp-policy list-c

# Run the display bgp peer command. You can view the BGP peer relationship between
routers. If there is no output information on Router C, it indicates that the BGP peer relationship
is not set up between Router C and Router D, and between Router C and Router F.
# Run the display msdp brief command. You can view the MSDP peer relationship between
routers. When S1 in PIM-SM1 domain sends a multicast packet, the receivers in PIM-SM2 and
PIM-SM3 domains can receive it. For example, information about MSDP peers on Router C,
Router D, and Router F is as follows:
<RouterC> display msdp brief


2 2 0 0 0 0
192.168.3.2 UP 01:07:08 ? 8 0
192.168.5.1 UP 00:16:39 ? 13 0
<RouterD> display msdp brief
1 1 0 0 0 0
192.168.1.1 UP 01:07:09 ? 8 0
<RouterF> display msdp brief
1 1 0 0 0 0
192.168.4.1 UP 00:16:40 ? 13 0
----End
Configuration Files
Configuration file of Router C is as follows:
#
sysname RouterC
#
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.1.1 255.255.255.0
pim sm
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 192.168.4.1 255.255.255.0
pim sm
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
pim sm
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 192.168.4.0 0.0.0.255
network 1.1.1.1 0.0.0.0
#
pim
c-bsr LoopBack0
c-rp LoopBack0
#
ip ip-prefix list-df permit 192.168.0.0 16 greater-equal 16 less-equal 32
#
msdp
peer 192.168.3.2 connect-interface pos 1/0/0
peer 192.168.5.1 connect-interface pos 2/0/0
static-rpf-peer 192.168.3.2 rp-policy list-df
static-rpf-peer 192.168.5.1 rp-policy list-df
#
return
The configuration fiiles of Router D and Router F are similar to the files mentioned previously,

6.11.3 Example for Configuring Anycast RP
As shown in Figure 6-3, the PIM-SM domain has multiple multicast sources and receivers. It
is required to set up MSDP peers in the PIM-SM domain to implement RP load balancing.
Figure 6-3 Networking diagram of configuring anycast RP
Receiver
user2 RouterB
GE2/0/0
Loopback10
PIM-SM GE1/0/0
Source GE3/0/0 GE2/0/0
S1 RouterD
Loopback1
POS1/0/0 Source
GE1/0/0
S2
RouterA Loopback0
GE2/0/0 Loopback0
POS1/0/0
GE2/0/0
POS1/0/0
Loopback1
GE3/0/0 POS2/0/0
RouterC RouterE
Receiver
Loopback10 user1
MSDP peers

Router A GE 1/0/0 10.110.5.1/24 Router D POS 1/0/0 192.168.3.1/24
GE 2/0/0 10.110.1.2/24 GE 2/0/0 10.110.2.1/24
Router B GE 1/0/0 10.110.6.1/24 GE 3/0/0 10.110.3.1/24
GE 2/0/0 10.110.2.2/24 Loopback 0 2.2.2.2/32
Router C POS 1/0/0 192.168.1.1/24 Loopback 1 4.4.4.4/32
GE 2/0/0 10.110.1.1/24 Loopback 10 10.1.1.1/32
GE 3/0/0 10.110.4.1/24 Router E POS 1/0/0 192.168.3.2/24
Loopback 0 1.1.1.1/32 POS 2/0/0 192.168.1.2/24
Loopback 1 3.3.3.3/32
Loopback 10 10.1.1.1/32

Solution: Configure an anycast RP. The receiver sends a Join message to the RP closest to the
topology. The source sends a Register message to the RP closest to the topology. The steps are
as follows:
1. Configure an IP address for each interface and configure OSPF in the PIM-SM area.
2. Enable multicast on each router and PIM-SM on each interface and enable IGMP on the
interface connected to hosts.
3. Configure the same loopback interface address for Router C and Router D. Configure the
C-BSR on Loopback 1 interfaces and the C-RP on Loopback 10 interfaces.
4. Configure MSDP peers on Loopback 0 interfaces of Router C and Router D. According to
RPF rules, routers receive SA messages from the source RP.
Data Preparation
l Address of group G is 225.1.1.1/24.
l Router ID of Router C is 1.1.1.1.
l Router ID of Router D is 2.2.2.2.
Procedure
Step 1 Configure an IP address on each interface and a unicast routing protocol.
#Configure an IP address and mask to each interface according to Figure 6-3. Configure OSPF.
Ensure the communication between routers on the network layer. Ensure dynamic routing
updates between routers by means of the unicast routing protocol. The procedures are not
mentioned here.
Step 2 Enable multicast on each router and configure PIM-SM on each interface.
# Enable multicast on each router, and enable PIM-SM on each interface. Enable IGMP on the
interface connected to hosts. The configurations of other routers are similar to that of Router C,
Step 3 Configure Loopback 1 and Loopback 10 interfaces, and the C-BSR and C-RP.
# Configure the address of Loopback 1 interface and the address of Loopback 10 interface on
Router C and Router D respectively. Configure the C-BSP on Loopback 1 and the C-RP on
Loopback 10. The configurations of Router D are similar to that of Router C, and are not
mentioned here.

[RouterC] pim
[RouterC-pim] c-bsr loopback 1
[RouterC-pim] c-rp loopback 10
[RouterC-pim] quit
Step 4 Configure Loopback 0 interfaces and MSDP peers.

# Configure MSDP peers on the Loopback 0 interfaces of Router C.
[RouterC] msdp
[RouterC-msdp] originating-rp loopback0
[RouterC-msdp] peer 2.2.2.2 connect-interface loopback0
[RouterC-msdp] quit
# Configure MSDP peers on the Loopback 0 interfaces of Router D.

[RouterD] interface loopback 0
[RouterD-LoopBack0] ip address 2.2.2.2 255.255.255.255
[RouterD-LoopBack0] pim sm
[RouterD-LoopBack0] quit
[RouterD] msdp
[RouterD-msdp] originating-rp loopback0
[RouterD-msdp] peer 1.1.1.1 connect-interface loopback0
[RouterD-msdp] quit

# Run the display msdp brief command. You can view the MSDP peer relationships between
routers. The MSDP peer relationship between Router C and Router D is as follows:
[RouterC] display msdp brief
1 1 0 0 0 0
2.2.2.2 Up 00:10:17 ? 0 0
[RouterD] display msdp brief
1 1 0 0 0 0
1.1.1.1 Up 00:10:18 ? 0 0
# Run the display pim routing-table command. You can view PIM routes on a router. In the
PIM-SM domain, S1 (10.110.5.100/24) sends multicast information to G (225.1.1.1). User 1
that joins G receives the multicast data sent to G. Comparing with the display of PIM routes on
Router C and Router D, you can find that the valid RP is Router C. That is, S1 registers with
Router C, and User 1 sends Join messages to Router C.
(*, 225.1.1.1)
RP: 10.1.1.1 (local)
UpTime: 00:28:49


Protocol: static, UpTime: 00:28:49, Expires: -
(10.110.5.1, 225.1.1.1)
RP: 10.1.1.1 (local)
Protocol: pim-sm, Flag: SPT 2MSDP ACT
UpTime: 00:02:26
There is no display.
# User 1 leaves G, and S1 stops sending multicast data to G. You can run the reset multicast
routing-table all and reset multicast forwarding-table all commands to clear the multicast
routing entries and multicast forwarding entries on Router C.
# User 2 joins G, and S2 (10.110.6.100/24) sends multicast data to G. Comparing with the display
of PIM routes on Router C and Router D, you can find that the valid RP is Router D. That is, S2
registers with Router D, and User 2 sends Join messages to Router D.
<RouterC> reset multicast routing-table all
<RouterC> reset multicast forwarding-table all
There is no display.
(*, 225.1.1.1)
RP: 10.1.1.1 (local)
Protocol: pim-sm, Flag: WC RPT
UpTime: 00:07:23
Upstream interface: NULL,
(10.110.6.100, 225.1.1.1)
RP: 10.1.1.1 (local)
Protocol: pim-sm, Flag: SPT 2MSDP ACT
UpTime: 00:10:20
----End
Configuration Files
Configuration file of Router C is as follows.
#
sysname RouterC

#
#
undo shutdown
ip address 10.110.4.1 255.255.255.0
igmp enable
pim sm
#
undo shutdown
ip address 10.110.1.1 255.255.255.0
pim sm
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.168.1.1 255.255.255.0
pim sm
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255
pim sm
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
pim sm
#
interface LoopBack10
ip address 10.1.1.1 255.255.255.255
pim sm
#
ospf 1
area 0.0.0.0
network 10.110.1.0 0.0.0.255
network 10.110.4.0 0.0.0.255
network 1.1.1.1 0.0.0.0
network 3.3.3.3 0.0.0.0
network 10.1.1.1 0.0.0.0
network 192.168.1.0 0.0.0.255
#
pim
c-bsr LoopBack1
c-rp LoopBack10
#
msdp
originating-rp LoopBack0
#
return
The configuration of Router D is similar to that of Router C, and is not mentioned here.

Configuration Guide - IP Multicast 7 MBGP Configuration
7 MBGP Configuration
About This Chapter
This chapter describes the MBGP fundamentals and configuration steps and maintenance for
MBGP functions, along with typical examples.
7.1 MBGP Introduction
This section describes the principle and the concepts of Multicast BGP (MBGP).
7.2 Configuring Basic MBGP Functions
This section describes how to configure basic MBGP functions.
7.3 Configuring the Policy for Advertising MBGP Routes
This section describes how to configure the policy for advertising MBGP routes.
7.4 Configuring the Policy for Exchanging Routes Between MBGP Peers
This section describes how to configure the policy for filtering the routes between MBGP peers.
7.5 Configuring MBGP Route Attributes
This section describes how to configure MBGP route attributes.
7.6 Configuring MBGP Route Dampening
This section describes how to configure MBGP route dampening.
7.7 Maintaining MBGP
This section describes how to clear MBGP statistics and reset connections between MBGP peers.
This section provides the configuration example of MBGP.

7 MBGP Configuration Configuration Guide - IP Multicast
7.1 MBGP Introduction

This section describes the principle and the concepts of Multicast BGP (MBGP).
7.1.1 MBGP Overview

7.1.2 MBGP Features Supported by the NE80E/40E
7.1.1 MBGP Overview

When a multicast source and its receivers are distributed in different Autonomous Systems
(ASs), a forwarding tree needs to be set up across ASs. The Multiprotocol Border Gateway
Protocol (MP-BGP) specially transfers routes between ASs for multicast.
MP-BGP is the multiprotocol extension of the Border Gateway Protocol (BGP). At present,
BGP4 is applied only to unicast. MP-BGP, based on BGP4, supports multiple routing protocols,
including multicast.
l MP-BGP maintains routes for unicast and multicast at the same time, stores them in
different routing tables, and keeps the routing information of unicast and multicast separate
from each other.
l MP-BGP builds different network topologies for unicast and multicast at the same time.
l Most of unicast routing policies and configuration methods supported by BGP4 can be
applied to multicast. MP-BGP maintains different routes for unicast and multicast
according to routing policies.
When MP-BGP is applied to multicast, it is called Multicast BGP (MBGP).
NOTE
This chapter describes the configuration of MP-BGP applied to multicast, that is, MBGP configuration.
For the details of MP-BGP, refer to the chapter "BGP Configuration" in the HUAWEI NetEngine80E/
40E Router Configuration Guide - IP Routing.
7.1.2 MBGP Features Supported by the NE80E/40E

For details, refer to the chapter BGP Configuration in the HUAWEI NetEngine80E/40E Router
Configuration Guide IP Routing.
7.2 Configuring Basic MBGP Functions

This section describes how to configure basic MBGP functions.
7.2.2 Configuring a BGP Peer
7.2.3 Configuring an MBGP Peer
7.2.4 Configuring an MBGP Route Reflector
7.2.5 Configuring MBGP to Import Local Routes

Perform the Reverse Path Forwarding (RPF) check on multicast packets according to the
following factors:
l Static multicast route

l Unicast route
l MBGP route
Setting up MBGP connections in the multicast address family view can provide routing
information for RPF check.
Before configuring basic MBGP functions, you need to configure basic Multicast functions.
Data Preparation
To configure basic MBGP functions, you need the following data.
No. Data
1 Local AS number and router ID
2 IPv4 addresses and AS numbers of peers
3 Interface originating the Update message
7.2.2 Configuring a BGP Peer
Context
CAUTION
If the two routers that plan to set up the MBGP peer relationship have set up a BGP connection,
skip the section.
Do as follows on the two routers between which the MBGP peer relationship needs to be set up.
Procedure
Step 1 Run:
system-view


Step 2 Run:
bgp as-number
BGP is enabled, the local AS number is set, and the BGP view is displayed.
router-id ipv4-address
The ID of a BGP router is set.

Step 4 Run:
peer ip-address as-number as-number
The IP address and AS number of a remote peer are specified.

peer { ipv4-address | group-name } connect-interface interface-type interface-
number [ ipv4-source-address ]
The local interface and the source address used to set up a BGP connection are specified.
If the BGP connection is set up through a Loopback interface or a sub-interface, the command
is required.
peer { ip-address | group-name } ebgp-max-hop [ number ]
The maximum number of hops of an EBGP connection is set.

The command is valid only for EBGP peers.
If the EBGP connection is set up through a Loopback interface, the command is required.
NOTE
For details of BGP peers, refer to the HUAWEI NetEngine80E/40E Router Configuration Guide - IP
Routing.
----End
7.2.3 Configuring an MBGP Peer
Context
Do as follows on the router configured with a BGP peer:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number
The BGP view is displayed.

Step 3 Run:
ipv4-family multicast
The BGP-IPv4 multicast address family view is displayed.

Step 4 Run:
peer { peer-address | group-name } enable
MBGP is enabled on the original BGP peer or peer group. The original BGP peer becomes an
MBGP peer.
l group-name: specifies the original BGP peer group.
l peer-address: specifies the IP address of the original remote BGP peer.
----End
7.2.4 Configuring an MBGP Route Reflector
Context
CAUTION
A Route reflector is valid only for IBGP peers. Before performing the configuration, you must
establish the IBGP peer relationships between MBGP route reflector and clients.
The configuration is optional. By default, the route reflector is not configured.

Do as follows on the router that is to become an MBGP route reflector:
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
peer { group-name | peer-address } reflect-client
The local host is configured as a route reflector, and the peer (group) is specified as a client of
the route reflector.

l group-name: specifies the name of an MBGP peer group.

l peer-address: specifies the IP address of a remote MBGP peer.

reflector cluster-id { decimal-value | ipv4-address }
The cluster ID of the route reflector is configured.
By default, the route reflector uses its router ID as the cluster ID.
l decimal-value: specifies the value of a cluster ID in the form of an integer.

l ipv4-address: specifies the value of a cluster ID in the form of an IPv4 address.
----End
7.2.5 Configuring MBGP to Import Local Routes
Context
CAUTION
MBGP routes are originated from the following:
l Routes statically imported by using the network command.
l Routes imported by using the import-route command.
Users can import at least one type of local routes as required.
Do as follows on the router configured with an MBGP peer:
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number
Step 3 Run:
Step 4 Run:
network network-address [ mask-length | mask ] [ route-policy route-policy-name ]
The routes of the local network segment are advertised.

l network-address [ mask-length | mask ]: specifies the routes to be advertised.

l route-policy route-policy-name: specifies the name of the routing policy that controls the
routes to be advertised.
Step 5 Run:
import-route protocol [ process-id ] [ med med-value | route-policy route-policy-
name ] *
IGP routes are imported to MBGP.
l protocol [ process-id ]: specifies the routing protocol and the process ID of the routing
protocol from which routes are imported. The routing protocol contains direct, static, rip,
isis and ospf. When the routing protocol is isis, ospf or rip, the process ID must be specified.
l med med-value: specifies the MED value assigned to an imported route.
l route-policy route-policy-name: specifies the route filtering policy. Only the route that
passes the filtering of the policy is imported.

default-route imported
Default routes are imported to the MBGP routing table.
By default, no default route is imported to the MBGP routing table.
The default-route imported command needs to work with the import-route command to
import default routes. The default routes cannot be imported by using only the import-route
command. The default-route imported command is used to import the default routes that exist
in the local routing table.
----End
Prerequisite
The configurations of basic MBGP functions are complete.
Procedure
l Run the display bgp multicast peer [ [ peer-address ] verbose ] command to check
information about an MBGP peer.
l Run the display bgp multicast group [ group-name ] command to check information about
an MBGP peer group.
l Run the display bgp multicast network command to check the routing information
advertised by MBGP.
l Run the display bgp multicast routing-table [ network-address [ mask-length [ longer-
prefixes ] | mask [ longer-prefixes ] ] ] command to check the MBGP routing table.
----End

7.3 Configuring the Policy for Advertising MBGP Routes

This section describes how to configure the policy for advertising MBGP routes.
7.3.2 Configuring the Next Hop of a Route as the Local Address
7.3.3 Configuring the Aggregation of Local MBGP Routes
7.3.4 Configuring the Local Peer to Advertise Default Routes
7.3.5 Configuring the Local Peer to Advertise Community Attribute and Extended Community
Attribute
7.3.6 Configuring Update Packets not to Carry Private AS Number
A router configured with the MBGP peer advertises the local routing information to a remote
peer. Based on the actual networking, users can adopt the following policies as required:
l Whether MBGP changes the next hop when advertising a route to IBGP peers
l Whether MBGP advertises all local routes or only the locally aggregated routes
l Whether MBGP advertises default routes
l Whether MBGP advertises community attributes or extended community attributes
l Whether a BGP Update message sent by an MBGP peer carries the private AS number
Before configuring the policy for advertising MBGP routes, complete the task of Configuring
Basic MBGP Functions.
Data Preparation
To configure the policy for advertising MBGP routes, you need the following data.
No. Data
1 AS number
2 Address of a remote peer or the name of a peer group
3 Name of the routing policy
4 Addresses and masks of the local routes that need to be aggregated

7.3.2 Configuring the Next Hop of a Route as the Local Address
Context
Do as follows on the router configured with an MBGP peer.
NOTE
The configuration is optional, and is valid only for an IBGP peer or peer group.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
peer { group-name | peer-address } next-hop-local
The local address is configured as the next hop of routes, when MBGP advertises routes to an
MBGP peer or peer group.
l group-name: specifies an MBGP peer group.
----End
7.3.3 Configuring the Aggregation of Local MBGP Routes
Context
NOTE
The configuration is optional. By default, MBGP does not aggregate local routes.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
summary automatic
The automatic aggregation of the subnet routes is configured.

Step 5 Run:
aggregate ip-address { mask | mask-length } [ as-set | attribute-policy route-
policy-name1 | detail-suppressed | origin-policy route-policy-name2 | suppress-
policy route-policy-name3 ] *
The local route aggregation is configured.

MBGP advertises the aggregated route.
MBGP supports the following two ways of local route aggregation:
l Automatic aggregation: aggregates the routes imported by MBGP locally.
l Manual aggregation: aggregates routes in the local MBGP routing table. Manual aggregation
takes precedence over automatic aggregation.
----End
7.3.4 Configuring the Local Peer to Advertise Default Routes
Context
NOTE
The configuration is optional. By default, no default route is advertised.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
peer { group-name | peer-address } default-route-advertise [ route-policy route-
policy-name ]
A default route is advertised to a remote MBGP peer or peer group.

l route-policy route-policy-name: specifies the routing policy that controls all advertised
routes.
----End
7.3.5 Configuring the Local Peer to Advertise Community Attribute

and Extended Community Attribute
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

peer { group-name | peer-address } advertise-community
The local peer is configured to advertise the community attribute to an MBGP peer group or a
remote MBGP peer.
By default, the local peer does not advertise the community attribute.
l peer-address: specifies the IP address for a remote MBGP peer.
l advertise-community: advertises the community attribute.

peer { group-name | peer-address } advertise-ext-community

The local peer is configured to advertise the extended community attribute to an MBGP peer
group or a remote MBGP peer.
By default, the local peer does not advertise the extended community attribute.

l peer-address: specifies the IP address for a remote MBGP peer.
l advertise-ext-community: advertises the extended community attribute.
----End
7.3.6 Configuring Update Packets not to Carry Private AS Number
Context
NOTE
The configuration is applicable only to an EBGP peer. By default, an update message can carries private
AS number.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number
Step 3 Run:
Step 4 Run:
peer { group-name | peer-address } public-as-only
A BGP update message sent to an MBGP peer group or a remote MBGP peer is configured not
to carry private AS number. The public AS number can be directly used on the Internet. The
private AS number cannot be advertised to the Internet, and is used only in domains.

----End

Prerequisite
The configurations of the policy for advertising MBGP routes are complete.
Procedure
l Run the display bgp multicast routing-table community [ aa:nn ] & <0-13> [ no-
advertise | no-export | no-export-subconfed ] * [ whole-match ] command to check the
routing information of a specified MBGP community.
l Run the display bgp multicast routing-table community-filter { { community-filter-
name | basic-community-filter-number } [ whole-match ] | advanced-community-filter-
number } command to check the routes that match a specified MBGP community attribute
filter.
advertised by MBGP.
l Run the display bgp multicast routing-table [ network-address [ mask-length [ longer-
prefixes ] | mask [ longer-prefixes ] ] ] command to check the MBGP routing table.
l Run the display bgp multicast routing-table cidr command to check CIDR routes.
l Run the display bgp multicast routing-table statistics command to check the statistics
of the MBGP routing table.
----End
7.4 Configuring the Policy for Exchanging Routes Between

MBGP Peers
This section describes how to configure the policy for filtering the routes between MBGP peers.
7.4.2 Configuring the Route Filtering Policy Globally
7.4.3 Configuring the Route Filtering Policy Based on Route-policy
7.4.4 Configuring the Route Filtering Policy Based on ACL
7.4.5 Configuring the Route Filtering Policy Based on AS-Path List
7.4.6 Configuring the Route Filtering Policy Based on IP Prefix
7.4.7 Configuring the Maximum Number of Routes Received from Peers
Based on the actual network, users can configure the related route exchange polices to control
the routing information transmitted between MBGP peers.

For a router configured with MBGP, the routes exchanged between peers are classified into the
following types:
l import: filters the routes sent by a specified peer. Only the routes that pass the filtering are
received.
l export: filters the routes sent to a specified peer or peer group. Only the routes that pass
the filtering are sent.
Pre-configuration Task
Before configuring the route filtering policy between MBGP peers, complete the following task:
l Configuring Basic MBGP Functions
Data Preparation
To configure the route filtering policy between MBGP peers, you need the following data.
No. Data
1 Number of the AS where the peer resides
2 Address of a peer or name of a peer group
3 Name of the routing policy, sequence number of the node, and matching rule
4 ID of the ACL
5 AS-Path filter
6 IP-Prefix
7 The threshold of the route-limit
7.4.2 Configuring the Route Filtering Policy Globally
Context
NOTE
The configuration is optional and is applicable to the route exchange with any peer.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number


Step 3 Run:

Step 4 Run:
filter-policy { basic-acl-number | acl-name acl-name | ip-prefix ip-prefix-name }
import
MBGP routing policy is configured to control the route exchange with any MBGP peer.
l basic-acl-number and acl-name acl-name: specifies the address filtering table.
l ip-prefix-name: specifies the address prefix list.
l import: filters the routes sent by any MBGP peer. Only the routes that pass the filtering are
received.
Step 5 Run:
filter-policy { basic-acl-number | acl-name acl-name | ip-prefix ip-prefix-name }
export [ protocol [ process-id ] ]
MBGP routing policy is configured to control the route exchange with any MBGP peer.
l basic-acl-number and acl-name acl-name: specifies the address filtering table.
l ip-prefix-name: specifies the address prefix list.
l export [ protocol [ process-id ] ]: filters the routes sent to any MBGP peer. In fact, the filtering
is performed when the local routes are imported to the MBGP routing table. This command
is used to import the local routes that pass the filtering to the MBGP routing table, and then
advertise the routing information in the MBGP routing table.
----End
7.4.3 Configuring the Route Filtering Policy Based on Route-policy
Context
NOTE
The configuration is optional. By default, the route filtering policy based on route-policy is not configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number


Step 3 Run:

Step 4 Run:
peer { group-name | peer-address } route-policy route-policy-name { import |
export }
The MBGP routing policy based on route-policy is configured to control the route exchange
with a specified remote MBGP peer.
l group-name specifies an MBGP peer group.
l peer-address: specifies the IP address of the remote MBGP peer.
l route-policy-name: specifies the routing policy.
l import: filters the routes sent by a specified remote MBGP peer or peer group. Only the
routes that pass the filtering are received.
l export: filters the routes sent to a specified remote MBGP peer or peer group. Only the routes
that pass the filtering are sent.
----End
7.4.4 Configuring the Route Filtering Policy Based on ACL
Context
NOTE
The configuration is optional. By default, the route filtering policy based on the ACL is not configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
peer { group-name | peer-address } filter-policy { basic-acl-number | acl-name acl-
name } { import | export }

The MBGP routing policy based on the ACL is configured to control the route exchange with
a specified remote MBGP peer.

l basic-acl-number and acl-name acl-name: specifies the routing policy.
----End
7.4.5 Configuring the Route Filtering Policy Based on AS-Path List
Context
NOTE
The configuration is optional. By default, the route filtering policy based on the AS-Path list is not
configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number
Step 3 Run:
Step 4 Run:
peer { group-name | peer-address } as-path-filter filter-number { import | export }
The MBGP routing policy based on the AS-Path list is configured to control the route exchange
with a specified remote MBGP route.

l filter-number: specifies the routing policy.

----End
7.4.6 Configuring the Route Filtering Policy Based on IP Prefix
Context
NOTE
The configuration is optional. By default, the route filtering policy based on the IP prefix list is not
configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number
Step 3 Run:
Step 4 Run:
peer { group-name | peer-address } ip-prefix prefix-name { import | export }
The MBGP routing policy based on the IP prefix list is configured to control the route exchange
with a specified remote MBGP peer.

l prefix-name: specifies the routing policy.
----End

7.4.7 Configuring the Maximum Number of Routes Received from

Peers
Context
NOTE
The configuration is optional. By default, the maximum number of routes received from peers is not
configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
peer { group-name | peer-address } route-limit maximum-limit [ threshold ] [ alert-
only | idle-forever | idle-timeout value ]
The number of routes received from an MBGP peer or peer group is limited.
The command can be used to control the peer to receive routes. You can configure specific
parameters as required to control BGP after the number of the routes received from a peer exceeds
the threshold.
l alert-only: indicates that only an alarm is generated when the number of routes exceeds the
limit.
l idle-forever: indicates that when the number of routes exceeds the limit, the connection is
not automatically set up until the reset bgp command is used.
l idle-timeout value: indicates the timeout timer for reestablishing the connection
automatically after the number of routes exceeds the limit. value specifies the value of the
timer.
l If the three parameters are not set, the peer relationship is disconnected. The router retries
setting up a connection after 30 seconds. An alarm is generated and recorded in the log.
----End

Prerequisite
The configurations of the policy for exchanging routes between MBGP peers are complete.

Procedure
l Run the display bgp multicast routing-table different-origin-as command to check the
routes different from the original AS.
l Run the display bgp multicast routing-table regular-expression [ as-regular-
expression ] command to check the routing information that matches the AS regular
expression.
l Run the display bgp multicast paths [ as-regular-expression ] command to check the
information about the AS paths.
l Run the display bgp multicast routing-table as-path-filter as-path-filter-number
command to check the routing information that matches the filtering list.
l Run the display bgp multicast routing-table community-filter { { community-filter-
name | basic-community-filter-number } [ whole-match ] | advanced-community-filter-
number } command to check the routes that match the MBGP community list.
l Run the display bgp multicast routing-table peer peer-address { advertised-routes |
received-routes } [ statistics ] command to check the routing information receive form or
sent to a specified MBGP peer.
advertised by MBGP.
----End
7.5 Configuring MBGP Route Attributes

This section describes how to configure MBGP route attributes.
7.5.2 Setting Preferred Values of Routes Learned from Peers
7.5.3 Configuring the Preference of an MBGP Route
7.5.4 Configuring the Local-Pref of an MBGP Route
7.5.5 Configuring the MED Attribute of an MBGP Route
7.5.6 Configuring Next_Hop
MBGP has many route attributes. You can change the optimal route selection by using the
following attributes.
l Preferred values of MBGP routes

l Preferences of MBGP routes
l Local_Pref
l MED of MBGP routes

Before configuring the policy for MBGP route selection, complete the task of Configuring Basic
MBGP Functions.
Data Preparation
To configure the policy for MBGP route selection, you need the following data.
No. Data
1 AS number
2 Protocol preference of MBGP
3 Preferred value
4 Local_Pref
5 MED of MBGP routes
7.5.2 Setting Preferred Values of Routes Learned from Peers
Context
NOTE
The configuration is optional. By default, the preferred value is 0.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
peer { group-name |peer-address } preferred-value preference-value
The preferred value is set for a route learnt from an MBGP peer group or a remote MBGP peer.
The route with the greatest preferred value is selected as the route to a specified network.


----End
7.5.3 Configuring the Preference of an MBGP Route
Context
NOTE
The configuration is optional. By default, the default preferences of EBGP routes, IBGP routes, and local
routes are 255.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
preference { external-preference internal-preference local-preference | route-
policy route-policy-name }
The preferences of internal, external and local routes are set.

l external-preference: specifies the preference of the route learned from an EBGP peer.
l internal-preference: specifies the preference of the route learned from an IBGP peer.
l local-preference: specifies the preference of the local originated route.
l route-policy route-policy-name: specifies the routing policy. The configuration is applicable
to the specific routes that meet certain matching conditions.
----End
7.5.4 Configuring the Local-Pref of an MBGP Route
Context

NOTE
The configuration is optional. By default, the Local_Pref value of the MBGP route is 100.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number
Step 3 Run:
Step 4 Run:
default local-preference preference
Local-Pref of the local host is configured.
When a BGP router obtains multiple routes with the same destination but different next hops
from different IBGP peers, the route with the greatest Local_Pref value is preferred.
----End
7.5.5 Configuring the MED Attribute of an MBGP Route
Context
NOTE
The configuration is optional. When a BGP router obtains multiple routes with the same destination but
different next hops from different EBGP peers, the route with the smallest MED value is preferred if other
conditions of these routes are the same.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number
Step 3 Run:

Step 4 Run:
default med med
The default MED value of the local host is configured.
Step 5 Run:
compare-different-as-med
MED values of routes from different ASs are compared.
By default, the BGP router compares only the MED values of the routes from the same AS.
Step 6 Run:
deterministic-med
Deterministic-MED is enabled.
If this command is not configured, when an optimal route is to be selected from among routes
which are received from different ASs and which carry the same prefix, the sequence in which
routes are received is relevant to the result of route selection. After the command is configured,
however, when an optimal route is to be selected from among routes which are received from
different ASs and which carry the same prefix, routes are first grouped according to the leftmost
AS in the AS_Path. Routes with the same leftmost AS are grouped together, and after
comparison, an optimal route is selected for the group. The group optimal route is then compared
with optimal routes from other groups to determine the final optimal route. This mode of route
selection ensures that the sequence in which routes are received is no longer relevant to the result
of route selection.
Step 7 Run:
bestroute med-none-as-maximum
When the MED value of a route is lost, the route is configured with the maximum MED value.
By default, the MED value of the route is 0.
Step 8 Run:
bestroute med-confederation
MED values of routes in the same confederation are compared.
By default, the BGP router compares the MED values of routes in the same AS.
----End
7.5.6 Configuring Next_Hop
Context
Do as follows on the router configured with the MBGP peer:
Procedure
Step 1 Run:
system-view


Step 2 Run:
bgp as-number

Step 3 Run:

Step 4 Run:
nexthop recursive-lookup route-policy route-policy-name
The next-hop iteration based on the specified routing policy is enabled.

By default, the next-hop iteration based on the specified routing policy is disabled.
The next-hop iteration based on the specified routing policy can control the iterated route
according to certain conditions. The route that fails to pass the policy is ignored.
----End

Prerequisite
The configurations of the policy for MBGP route selection are complete.
Procedure
l Run the display bgp multicast routing-table command to check the routes of the MBGP
routing table.
l Run the display bgp multicast routing-table statistics command to check the statistics
of the MBGP routing table.
----End
7.6 Configuring MBGP Route Dampening

This section describes how to configure MBGP route dampening.
7.6.2 Setting Dampening Parameters of an MBGP Route

Configuring MBGP dampening can suppress the unstable routing information. After MBGP
dampening is configured, the unstable routing information is not added to the MBGP routing
table, or advertised to other MBGP peers.

Before configuring MBGP route dampening, complete the following task:
l Configuring Basic MBGP Functions
Data Preparation
To configure MBGP route dampening, you need the following data.
No. Data
1 Dampening parameters, including the half-life and threshold
7.6.2 Setting Dampening Parameters of an MBGP Route
Context
NOTE
The configuration is valid only for EBGP routes. By default, the default values of dampening parameters
are used.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bgp as-number
Step 3 Run:
Step 4 Run:
dampening [ half-life-reach reuse suppress ceiling | route-policy route-policy-
name ] *
The dampening parameters of an MBGP route are configured.
l half-life-reach: specifies the half-life of a reachable route.

l reuse: specifies the threshold for releasing routes from being suppressed. When the penalty
is smaller than the threshold, the suppressed routes are reused.

l suppress: specifies the threshold for suppressing routes. The value must be greater than the
value of reuse. When the penalty is greater than the threshold, the routes are suppressed.
l ceiling: specifies the ceiling value of the threshold. The value must be greater than the value
of suppress.
l route-policy route-policy-name: specifies the routing policy. The configuration is applicable
to the routes that meet certain matching conditions.
----End

Prerequisite
The configurations of MBGP route dampening are complete.
Procedure
l Run the display bgp multicast routing-table dampened command to check MBGP
dampened routes.
l Run the display bgp multicast routing-table dampening parameter command to check
MBGP route dampening parameters.
l Run the display bgp multicast routing-table flap-info [ network-address [ mask [ longer-
match ] | mask-length [ longer-match ] ] | as-path-filter as-path-filter-number | regular-
expression as-regular-expression ] command to check the statistics of MBGP route
flapping.
----End
7.7 Maintaining MBGP

This section describes how to clear MBGP statistics and reset connections between MBGP peers.
7.7.1 Resetting MBGP Connection
7.7.2 Clearing MBGP Statistics
7.7.1 Resetting MBGP Connection

Context
CAUTION
The MBGP peer relationship is deleted after you reset MBGP connections with the reset bgp
multicast command. So, confirm the action before you use the command.
Procedure
l Run the reset bgp multicast peer-address command in the user view to reset the MBGP
connection between specified peers.

l Run the reset bgp multicast all command in the user view to reset all MBGP connections.
l Run the reset bgp multicast group group-name command in the user view to reset the
MBGP connections between all peers in the peer group.
l Run the reset bgp multicast external command in the user view to reset external
connections.
l Run the reset bgp multicast internal command in the user view to reset internal
connections.
----End
7.7.2 Clearing MBGP Statistics
Context
CAUTION
The MBGP statistics cannot be restored after you clear them. So, confirm the action before you
use the command.
Procedure
l Run the reset bgp multicast dampening [ network-address [ mask | mask-length ] ]
command in the user view to clear the MBGP routing information.
l Run the reset bgp multicast flap-info [ network-address [ mask-length | mask ] | as-path-
filter as-path-list-number | regrexp regrexp ] command in the user view to clear the
information about the MBGP route flapping.
----End

This section provides the configuration example of MBGP.
7.8.1 Example for Configuring Basic MBGP Functions
7.8.1 Example for Configuring Basic MBGP Functions
As shown in Figure 7-1, the receiver receives information in multicast mode. The receiver and
the source reside in different ASs. The MBGP peer relationship is established between ASs to
transmit multicast routing information.

Figure 7-1 MBGP path selection networking diagram
AS100 AS200
RouterD
Loopback0
POS2/0/0
POS1/0/0
Source RouterA POS2/0/0

RouterB
GE2/0/0 POS1/0/0
POS1/0/0 POS3/0/0
Loopback0 Loopback0
POS3/0/0 POS1/0/0
RouterC Loopback0
GE2/0/0
Receiver
MBGP peers
Device Interface IP address Device Interface IP address

Router A POS 1/0/0 192.1.1.1/24 Router C POS 1/0/0 195.1.1.1/24
GE 2/0/0 10.10.10.1/24 GE 2/0/0 22.22.22.1/24
Loopback 0 1.1.1.1/32 POS 3/0/0 193.1.1.1/24
Loopback 0 3.3.3.3/32
Router B POS 1/0/0 192.1.1.2/24 Router D POS 1/0/0 195.1.1.2/24
POS 2/0/0 194.1.1.2/24 POS 2/0/0 194.1.1.1/24
POS 3/0/0 193.1.1.2/24 Loopback 0 4.4.4.4/32
Loopback 0 2.2.2.2/32
1. Configure an address for each interface to ensure internetworking within the AS in unicast
mode.
2. Configure the MBGP peer relationship and set up inter-AS multicast routes.
3. Configure the MBGP routes to be advertised.
5. Configure basic PIM-SM functions in each AS and enable IGMP on the interface connected
to hosts.

6. Configure the BSR boundary on interfaces that connect two ASs.

7. Configure MSDP peers to transfer inter-domain multicast source information.
8. Verify the configuration.
Data Preparation
l AS number of Router A is 100.
l Router B, Router C, and Router D belong to AS 200.
l Multicast group address is 225.1.1.1 and source address is 10.10.10.10/24.
Procedure
Step 1 Configure an IP address for each interface and OSPF in an AS.
# Configure an IP address and mask for each interface and the OSPF protocol in the AS shown
in Figure 7-1. Enable that Router B, Router C, Router D, and Receiver in AS 200 can
interconnect at the network layer. Ensure that the routers can learn routes to the loopback
interfaces. Ensure the dynamic routing updates between routers by means of the unicast routing
protocol. The process 1 of OSPF is adopted in the configuration, and the detailed process is not
mentioned here.
Step 2 Configure BGP, enable MBGP, and configure an MBGP peer.
# Enable BGP and configure an MBGP peer on Router A.
[RouterA] bgp 100
[RouterA-bgp] peer 192.1.1.2 as-number 200
[RouterA-bgp] ipv4-family multicast
[RouterA-bgp-af-multicast] peer 192.1.1.2 enable
[RouterA-bgp-af-multicast] quit
[RouterA-bgp] quit
# Enable BGP and configure an MBGP peer on Router B.

[RouterB] bgp 200
[RouterB-bgp] ipv4-family multicast
[RouterB-bgp-af-multicast] peer 192.1.1.1 enable
[RouterB-bgp-af-multicast] quit
[RouterB-bgp] quit
# Enable BGP and configure an MBGP peer on Router C.

[RouterC] bgp 200
[RouterC-bgp] ipv4-family multicast
[RouterC-bgp-af-multicast] peer 193.1.1.2 enable
[RouterC-bgp-af-multicast] peer 195.1.1.2 enable
[RouterC-bgp-af-multicast] quit
[RouterC-bgp] quit
# Enable BGP and configure an MBGP peer on Router D.

[RouterD] bgp 200
[RouterD-bgp] peer 194.1.1.2 as-number 200

[RouterD-bgp] peer 195.1.1.1 as-number 200

[RouterD-bgp] ipv4-family multicast
[RouterD-bgp-af-multicast] peer 194.1.1.2 enable
[RouterD-bgp-af-multicast] peer 195.1.1.1 enable
[RouterD-bgp-af-multicast] quit
[RouterD-bgp] quit
Step 3 Configure the routes to be advertised.
# Configure the routes to be advertised on Router A.

[RouterA] bgp 100
[RouterA-bgp] import-route direct
[RouterA-bgp] ipv4-family multicast
[RouterA-bgp-af-multicast] import-route direct
[RouterA-bgp-af-multicast] quit
[RouterA-bgp] quit
# Configure the routes to be advertised on Router B.

[RouterB] bgp 200
[RouterB-bgp] import-route direct
[RouterB-bgp] ipv4-family multicast
[RouterB-bgp-af-multicast] import-route direct
[RouterB-bgp-af-multicast] quit
[RouterB-bgp] quit
# Configure the routes to be advertised on Router C.

[RouterC] bgp 200
[RouterC-bgp] import-route direct
[RouterC-bgp] ipv4-family multicast
[RouterC-bgp-af-multicast] import-route direct
[RouterC-bgp-af-multicast] quit
[RouterC-bgp] quit
# Configure the routes to be advertised on Router D.

[RouterD] bgp 200
[RouterD-bgp] import-route direct
[RouterD-bgp] ipv4-family multicast
[RouterD-bgp-af-multicast] import-route direct
[RouterD-bgp-af-multicast] quit
[RouterD-bgp] quit
Step 4 Enable multicast on each router.
[RouterA] interface Pos1/0/0
[RouterA] interface GigabitEthernet2/0/0
[RouterB] interface Pos1/0/0

# Configure Router C.
[RouterC] interface Pos1/0/0
[RouterC] interface GigabitEthernet2/0/0
[RouterC] interface Pos3/0/0
# Configure Router D.
[RouterD] interface Pos1/0/0
[RouterD-Pos1/0/0] pim sm
[RouterD] interface Pos2/0/0
Step 5 Configure a BSR and an RP in an AS.

[RouterA-LoopBack0] ip address 1.1.1.1 255.255.255.255
[RouterA-LoopBack0] pim sm
[RouterA] pim
[RouterA-pim] c-bsr loopback 0
[RouterA-pim] c-rp loopback 0
[RouterA-pim] quit
[RouterB-LoopBack0] ip address 2.2.2.2 255.255.255.255
[RouterB-LoopBack0] pim sm
[RouterB] pim
[RouterB-pim] c-bsr loopback 0
[RouterB-pim] c-rp loopback 0
[RouterB] quit
Step 6 Configure the BSR service boundary on inter-AS interfaces.

[RouterA] interface Pos1/0/0
[RouterA-Pos1/0/0] pim bsr-boundary
[RouterB-Pos1/0/0] pim bsr-boundary
Step 7 Configure an MSDP peer.

[RouterA] msdp
[RouterA-msdp] peer 192.1.1.2 connect-interface Pos 1/0/0
[RouterA-msdp] quit

[RouterB] msdp
[RouterB-msdp] peer 192.1.1.1 connect-interface Pos 1/0/0
[RouterB-msdp] quit

# Run the display bgp multicast peer command to check the MBGP peer relationship between
routers. For example, the MBGP peer relationship on Router A is displayed as follows:
[RouterA] display bgp multicast peer
Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
192.1.1.2 4 200 82 75 0 00:30:29 Established 17
# Run the display msdp brief command to check the MSDP peer relationship between
routers. For example, the brief information about the MSDP peer relationship on Router B is
displayed as follows:
[RouterB] display msdp brief
1 1 0 0 0 0
192.1.1.1 Up 00:07:17 100 1 0
----End
Configuration Files
#
sysname RouterA
#
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.1.1.1 255.255.255.0
pim bsr-boundary
pim sm
#
undo shutdown
ip address 10.10.10.1 255.255.255.0
pim sm
#
interface loopback0
ip address 1.1.1.1 255.255.255.255
pim sm
#
pim
c-bsr loopback 0
c-rp loopback 0
#
bgp 100
#
ipv4-family unicast
import-route direct
peer 192.1.1.2 enable
#

import-route direct
#
msdp
#
return
#
sysname RouterB
#
#
interface pos1/0/0
undo shutdown
link-protocol ppp
ip address 192.1.1.2 255.255.255.0
pim bsr-boundary
pim sm
#
interface pos2/0/0
undo shutdown
link-protocol ppp
ip address 194.1.1.2 255.255.255.0
pim sm
#
interface pos3/0/0
undo shutdown
link-protocol ppp
ip address 193.1.1.2 255.255.255.0
pim sm
#
interface loopback 0
ip address 2.2.2.2 255.255.255.255
pim sm
#
pim
c-bsr loopback 0
c-rp loopback 0
#
ospf 1
area 0.0.0.0
network 193.1.1.0 0.0.0.255
network 194.1.1.0 0.0.0.255
network 2.2.2.2 0.0.0.0
#
bgp 200
#
ipv4-family unicast
import-route direct
#
import-route direct
#
msdp
peer 192.1.1.1 connect-interface Pos 1/0/0

#
return
#
sysname RouterC
#
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 195.1.1.1 255.255.255.0
pim sm
#
undo shutdown
ip address 22.22.22.1 255.255.255.0
igmp enable
pim sm
#
interface pos3/0/0
undo shutdown
link-protocol ppp
ip address 193.1.1.1 255.255.255.0
pim sm
#
interface loopback0
ip address 3.3.3.3 255.255.255.255
pim sm
#
ospf 1
area 0.0.0.0
network 193.1.1.0 0.0.0.255
network 195.1.1.0 0.0.0.255
network 22.22.22.0 0.0.0.255
network 3.3.3.3 0.0.0.0
#
bgp 200
#
ipv4-family unicast
import-route direct
#
import-route direct
#
return
#
sysname RouterD
#
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 195.1.1.2 255.255.255.0
pim sm
#
interface Pos2/0/0
undo shutdown

link-protocol ppp
ip address 194.1.1.1 255.255.255.0
pim sm
#
ip address 4.4.4.4 255.255.255.255
pim sm
#
ospf 1
area 0.0.0.0
network 194.1.1.0 0.0.0.255
network 195.1.1.0 0.0.0.255
network 4.4.4.4 0.0.0.0
#
bgp 200
#
ipv4-family unicast
import-route direct
#
import-route direct
#
return

Configuration Guide - IP Multicast 8 IPv4 Multicast VPN Configuration
8 IPv4 Multicast VPN Configuration
About This Chapter
This chapter describes the MD VPN fundamentals and configuration steps and maintenance for
MD VPN functions, along with typical examples.
8.1 IPv4 Multicast VPN Introduction
This section describes the principle and concepts of MD VPN.
8.2 Configuring Basic MD VPN Functions
This section describes how to configure basic MD VPN functions.
8.3 Configuring Switch-MDT Switchover
This section describes how to configure Switch-MDT switchover.
8.4 Maintaining IPv4 Multicast VPN
This section describes how to monitor the running status of MSDP and control the output of
logs.
This section provides several configuration examples of MD VPN.

8 IPv4 Multicast VPN Configuration Configuration Guide - IP Multicast
8.1 IPv4 Multicast VPN Introduction

This section describes the principle and concepts of MD VPN.
8.1.1 Overview of IPv4 Multicast VPN

8.1.2 IPv4 Multicast VPN Supported by the NE80E/40E
8.1.1 Overview of IPv4 Multicast VPN

TheNE80E/40E implements multicast data transmission based on MPLS/BGP VPN.
As shown in Figure 8-1, when multicast VPN is deployed in the network, the network carries
three separate multicast services at the same time, that is, VPN A instance, VPN B instance, and
the public network instance. A multicast router PE at the edge of the public network supports
multi-instance. The PE acts as multiple multicast routers that run separately. Each instance
corresponds to a plane. The three planes are isolated.
Figure 8-1 Multicast VPN based on multi-instance
site4 PE2
site6
MD B
site5 PE1
VPN instance B
P
PE2
PE1
PIM
PE3
Public instance
site2
site1 MD A PE2
PE1
site3
VPN instance A PE3
The following takes VPN A instance as an example to explain multicast VPN.
l S1 belongs to VPN A. S1 sends multicast data to G, a multicast group.

l Among all possible data receivers, only members of VPN A (Site 1, Site 2, and Site 3) can
receive multicast data from S1.

l Multicast data is transmitted among sites in the public network and each site in multicast
mode.
To implement multicast VPN, the following network conditions need to be met:
l Each site supports multicast based on VPN instances.

l Public network supports multicast based on the public network instance.
l PE device supports multi-instance multicast:
– Connecting sites through a VPN instance, and supporting multicast based on the VPN
instance
– Connecting the public network through the public instance, and supporting multicast
based on the public network instance
– Supporting information communication and data switching between the public network
instance and the VPN instance
8.1.2 IPv4 Multicast VPN Supported by the NE80E/40E
MD VPN
The NE80E/40E applies Multicast Domain (MD) to implement multicast VPN, which is called
MD VPN. In an MD, VPN data is transmitted through the Multicast Tunnel (MT).
The greatest advantage of the MD solution is that only PEs are required to support multi-instance.
MD neither needs to upgrade CEs and Ps, nor modify the previous Protocol Independent
Multicast (PIM) configuration on CEs and Ps. That is, the MD solution is transparent to CEs
and Ps.
Users can bind Share-Group to Multicast Tunnel Interfaces (MTIs), and set MTI parameters.
Share-Multicast Distribution Tree

For a VPN instance, data transmission in the public network is transparent. The VPN data is
seamlessly connected at MTIs on PEs: The VPN instance only knows that after it sends the VPN
data through an MTI on local PE, and the remote PE can receive the data through an MTI.
Actually, the data experiences the complex public network transmission process, that is,
multicast distribution tree (MDT) transmission.
The MDT that takes the address of Share-group as the group address is called Share-MDT. VPNs
use Share-Group to uniquely identify a Share-MDT.
Multicast can be enabled in a PIM-SM network or a PIM-DM network. In the two different
modes, the process of setting up a Share-MDT is different.
Switch-MDT Switchover
When multicast data is forwarded through a Share-MDT in the public network, the multicast
data is forwarded to all PEs that support the same VPN instance, regardless of whether there is
a receiver in the site connected to PEs. When the rate of VPN multicast data is higher, it may
lead to data flooding, which wastes the network bandwidth and adds load to PEs.
The NE80E/40E optimizes the MD. Special Switch-MDTs is set up between PEs connected to
VPN receivers and PEs connected to the VPN multicast source for VPN multicast data of a high

rate flowing to the public network. The multicast data flow is then switched from the Share-
MDT to the Switch-MDT. Multicast data can thus be transmitted on demand.
Users can configure the switching conditions of a Switch-MDT.
MD VPN across Multi-AS

When a VPN covers multiple ASs, it is necessary to connect VPN nodes among different ASs.
The following lists methods used by MD VPN to realize inter-AS multicast:
l VPN instance-to-VPN Instance connection method
l Multi-hop EBGP connection method
NOTE
For detailed implementation process, refer to the chapter "Multicast VPN" in the HUAWEI NetEngine80E/
40E Router Feature Description - IP Multicast.
Processing Modes of the Multicast VPN Service

The devices support the following two processing modes of the multicast VPN service:
distributed mode and integrated mode.
l Distributed mode
The LPUF-20/21 and LPUF-40 support a complete multicast VPN function and therefore
can independently implement multicast packet forwarding among VPNs.
l Integrated mode
For the LPUs that do not support the multicast VPN function, they only send packets to the
SPUC for integrated processing.
8.2 Configuring Basic MD VPN Functions

This section describes how to configure basic MD VPN functions.
8.2.2 Enabling IP Multicast VPN
8.2.4 Configuring Share-Group and Binding an MTI
8.2.5 Configuring an MTI

To implement multicast transmission in a VPN network, ensure that the VPN network works
normally. To enable a PE to receive information from multiple VPNs, the PE needs to
simultaneously support the public network instance and the VPN instance. The public network
is responsible for communicating with Ps, and each VPN instance is responsible for
communicating with each CE.

Configure multicast VPN by using the MD solution. Set up Share-MDT to forward multicast
packets. When the multicast forwarding rate exceeds the threshold, Share-MDT is switched to
Switch-MDT.
Before configuring basic MD VPN functions, complete the following tasks:

l Configuring MPLS/BGP VPN
l Configuring public network multicast
Data Preparation
To configure basic MD VPN functions, you need the following data.
No. Data
1 VPN instance name and RD
2 Share-Group address
3 Address and MTU of MTI
8.2.2 Enabling IP Multicast VPN
Context
Do as follows on the PE router:
Procedure
Step 1 Run:
set board-type slot slot-id { tunnel | netstream }
Set the service mode of the SPUC to be Tunnel mode.
Step 2 Run:
system-view
Step 3 Run:
multicast-vpn slot slot-id
The board is specified to support multicast VPN.
----End

Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
Step 4 Run:
IP multicast routing is enabled in the VPN instance.
----End
8.2.4 Configuring Share-Group and Binding an MTI
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
multicast-domain share-group group-address binding mtunnel number
A share group is configured. The system automatically creates an MTI, and then binds the share
group to the MTI and binds the MTI to the VPN instance.
----End
8.2.5 Configuring an MTI

Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface mtunnel number
The MTI interface view is displayed.
Step 3 Run:
pim sm
or run:
pim dm
PIM is enabled on the MTI.
The PIM mode is the same as the PIM mode of the VPN that the MTI belongs to.
Step 4 Run:
ip address ip-address { mask | mask-length }
The address of the MTI is configured.
NOTE
The MTI address must be the same as the IP address that is used to set up the IBGP peer relationship on
the PE in the public network. Otherwise, the VPN multicast packets received on the MTI cannot pass the
RPF check.

mtu mti-mtu
The MTU value of the MTI is configured.
By default, the MTU value of the MTI is 1472 bytes.
When multicast packets are transmitted between the VPN instance and the public network
instance, these packets are encapsulated and decapsulated in the GRE mode. If the size of a VPN
multicast packet is equal or close to the Maximum Transmission Unit (MTU) of the outgoing
interface of the public network instance, the size of a new multicast packet after GRE
encapsulation exceeds the MTU of that outgoing interface. In this case, the multicast packet
needs to be fragmented when it is sent out through the outgoing interface of the public network
instance. This creates a difficulty of re-forming the fragments to the remote receiving interface.
Therefore, you can configure a smaller MTU for the MTI to enable the fragmentation of multicast
packet prior to the process of GRE encapsulation. This method prevents re-forming on the remote
receiving interface, and improves the efficiency greatly.
----End

Procedure
l Run the display multicast-domain vpn-instance vpn-instance-name share-group
[ local | remote ] command to check Share-Group information of a specified VPN instance
in an MD.
l Run the display pim vpn-instance vpn-instance-name interface mtunnel [ number ]
[ verbose ] command to check information about an MTI.
----End
8.3 Configuring Switch-MDT Switchover

This section describes how to configure Switch-MDT switchover.
8.3.2 (Optional) Setting Switching Parameters of Switch-MDT
When multicast data packets are forwarded through the share-MDT in the public network, the
packets are forwarded to all PEs that support the same VPN instance, regardless of whether there
is a receiver in the site to which a PE is connected. When the rate for forwarding VPN multicast
data packets is high, the packets may be flooded in the public network. This wastes network
bandwidth and increases the load of PEs.
In the NE80E/40E, you can determine whether to perform Switch-MDT switchover. If Switch-
MDT switchover is not configured, MDs use Share-MDT to transmit VPN multicast data forever.
l When the rate of the VPN multicast data entering the public network exceeds the threshold,
the VPN multicast data can be switched from Share-MDT to a specified Switch-MDT. On-
demand multicast is thus implemented.
l After the VPN multicast data is switched to the switch-MDT, the switchover conditions
may not be met. In this case, the VPN multicast data can be reversely switched from Switch-
MDT to Share-MDT.
Before configuring Switch-MDT switchover, complete the task of Configuring Basic MD VPN
Functions.
Data Preparation
To configure Switch-MDT switchover, you need the following data.

No. Data
1 VPN instance name
2 The address range and mask of the switch-group-pool of Switch-MDT
3 Switching threshold
4 Delay for switching from Share-MDT to Switch-MDT
5 Delay for switching from Switch-MDT to Share-MDT
8.3.2 (Optional) Setting Switching Parameters of Switch-MDT
Context
NOTE
This configuration is optional. If this configuration is not done, Switch-MDT switchover cannot be
performed and Share-MDT is always used to transmit VPN multicast data.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
multicast-domain switch-group-pool switch-group-pool { network-mask | network-mask-
length } [ threshold threshold-value | acl { advanced-acl-number | acl-name } ] *
The switch-group-pools of Switch-MDT and switch conditions are configured.
l switch-group-pool: specifies a switch-group-pool. It's suggested that the same VPN instance
on different PEs are configured with the same switch-group-pool. On a PE, the Switch-Group
address ranges to which different VPNs correspond cannot overlap.
l threshold-value: Specifies the threshed. By default, it is 0 kbit/s.
l { advanced-acl-number | acl-name }: specifies the advanced ACL filtering rules. By default,
packets are not filtered.

multicast-domain switch-delay switch-delay
The delay for switching to Switch-MDT is configured.

By default, the delay is 5 seconds.

multicast-domain holddown-time interval
The duration for keeping the rate of VPN multicast data lower than the threshold before reversely
switching from Switch-MDT to Share-MDT is set.
By default, the delay for switching from Switch-MDT to Share-MDT is 60 seconds.
----End
Procedure
l Run the following commands to check Switch-Group information received by a specified
VPN instance in the MD.
– display multicast-domain vpn-instance vpn-instance-name switch-group receive
brief
[ active | group group-address | sender source-address | vpn-source-address [ mask
{ source-mask-length | source-mask } ] | vpn-group-address [ mask { group-mask-
length | group-mask } ] ] *
l Run the display multicast-domain vpn-instance vpn-instance-name switch-group
send [ group group-address | reuse interval | vpn-source-address [ mask { source-mask-
length | source-mask } ] | vpn-group-address [ mask { group-mask-length | group-
mask } ] ] * command to check Switch-Group information sent by a specified VPN instance
in the MD.
----End
8.4 Maintaining IPv4 Multicast VPN

This section describes how to monitor the running status of MSDP and control the output of
logs.
8.4.1 Monitoring the Running Status of IPv4 Multicast VPN
8.4.2 Controlling the Output of Logs
8.4.1 Monitoring the Running Status of IPv4 Multicast VPN
Context
status of IPv4 Multicast VPN.
Procedure
l Run the display multicast-domain vpn-instance vpn-instance-name share-group
[ local | remote ] command in any view to check information about Share-Group of a
specified VPN instance in an MD.

l Run the following commands in any view to check information about Switch-Group
received by a specified VPN instance in an MD.
brief
[ active | group group-address | sender source-address | vpn-source-address [ mask
{ source-mask-length | source-mask } ] | vpn-group-address [ mask { group-mask-
length | group-mask } ] ] *
l Run the display multicast-domain vpn-instance vpn-instance-name switch-group
send [ group group-address | reuse interval | vpn-source-address [ mask { source-mask-
length | source-mask } ] | vpn-group-address [ mask { group-mask-length | group-
mask } ] ] * command in any view to check information about the Switch-Group sent to a
specified VPN instance in an MD.
----End
8.4.2 Controlling the Output of Logs
Context
In the VPN instance on the source PE, if the number of VPN multicast data flows that need to
be switched is more than the number of group addresses in the switch-group-pool of Switch-
MDT, the group addresses in the switch-group-pool can be used repeatedly.
By default, the logs of the reused Switch-Group addresses are not recorded.
To know the running status of the system or locate a fault through logs, do as follows on the PE:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
multicast-domain log switch-group-reuse
The logs of the reused Switch-Group addresses are recorded.
----End

This section provides several configuration examples of MD VPN.
8.5.1 Example for Configuring Single-AS MD VPN

8.5.2 Example for Configuring Inter-AS MD VPN

8.5.1 Example for Configuring Single-AS MD VPN
In the single-AS MPLS/BGP VPN shown in Figure 8-2, the MD solution is used to deploy
multicast services.
Figure 8-2 Networking diagram of configuring single-AS MD VPN
PC2
VPN
RED
Source2 GE1
CE-Rb
GE2 GE3
PC3
GE1 Loopback1
VPN Loopback1
BLUE GE3 GE3 GE1
GE2 VPN
Loopback1 RED
CE-Bb Public
GE2 GE2
PE-B GE1 P PE-C CE-Rc
GE2 GE3 GE2
Loopback2
GE1
Source1 GE1
GE3
CE-Ra
GE1Loopback1 GE2
GE1 GE3 VPN
CE-Bc BLUE
GE2
VPN GE2 GE1
RED PE-A
PC4
PC1 Loopback1
NOTE
In Figure 8-2, GE1 stands for GigabitEthernet 1/0/0, GE2 stands for GigabitEthernet 2/0/0, and GE3 stands
for GigabitEthernet 3/0/0. The IP address of each interface is shown in the following table.
The devices support two processing modes of the multicast VPN service: distributed mode and integrated
mode. In distributed mode, you must run the multicast-vpn slot command to specify the slot that supports
multicast VPN. In integrated mode, you must run the set board-type slot and multicast-vpn slot
commands to set the service mode of the SPUC to be Tunnel mode and enable multicast VPN on an SPUC
separately. The following configuration example use the distributed mode to cofigure the multicast VPN
service.
Table 8-1 Configuration information about interfaces
Device IP Address of Interface Remarks
P GE1: 192.168.6.2/24 -
GE2: 192.168.7.2/24 -
GE3: 192.168.8.2/24 -

Loopback1: 2.2.2.2/32 Acts as C-RP of the public network
PE-A GE1: 192.168.6.1/24 Public network instance
GE2: 10.110.1.1/24 VPN-RED instance
Loopback1: 1.1.1.1/32 Public network instance

Loopback 1 interfaces of PE-A, PE-B,
and PE-C set up IBGP peer
relationships.
PE-B GE1: 192.168.7.1/24 Public network instance
GE2: 10.110.3.1/24 VPN-BLUE instance

relationships.
PE-C GE1: 192.168.8.1/24 Public network instance
GE3: 10.110.6.1/24 VPN-BLUE instance

relationships.
Loopback2: 33.33.33.33/32 VPN-BLUE instance

Acts as C-RP of VPN-BLUE
CE-Ra GE1: 10.110.7.1/24 -
GE2: 10.110.2.2/24 -
CE-Bb GE1: 10.110.8.1/24 -
GE2: 10.110.3.2/24 -
CE-Rb GE1: 10.110.9.1/24 -
GE2: 10.110.4.2/24 -
GE3: 10.110.12.1/24 -
Loopback1: 22.22.22.22/32 VPN-RED instance

Acts as C-RP of VPN-RED instance
CE-Rc GE1: 10.110.10.1/24 -

GE2: 10.110.5.2/24 -
GE3: 10.110.12.2/24 -
CE-Bc GE1: 10.110.11.1/24 -
GE2: 10.110.6.2/24 -
Source1 10.110.7.2/24 Multicast source in the VPN-RED
Source2 10.110.8.2/24 Multicast source in the VPN-BLUE
PC1 10.110.1.2/32 Multicast receiver in the VPN-RED
PC4 10.110.11.2/32 Multicast receiver in the VPN-BLUE
Table 8-2 Networking requirements of Single-AS MD VPN solution

Item Networking Requirements
Multicast Multicast source of VPN RED is Source1. The receivers include PC1, PC2, and
source/ PC3. Multicast source of VPN BLUE is Source2. The receiver is PC4. In VPN
receiver RED, Share-Group address is 239.1.1.1 and Switch-Group address pool ranges
from 225.2.2.1 to 225.2.2.16. In VPN BLUE, Share-Group address is 239.2.2.2
and Switch-Group address pool ranges from 225.4.4.1 to 225.4.4.16.
VPN On PE-A, GE2 and GE3 belong to VPN-RED instance, and GE1 and
instance Loopback1 belong to the public network instance. On PE-B, GE2 belongs to
which the VPN-BLUE instance, GE3 belongs to VPN-RED instance, and GE1 and
interfaces Loopback1 belong to the public network instance. On PE-C, GE2 belongs to
on PEs VPN-RED instance, GE3 and Loopback2 belong to VPN-BLUE instance, and
belong to GE1 and Loopback1 belong to the public network instance.
Routing Configure OSPF on the public network. Enable RIP on PE and CE routers.
protocol Establish a BGP peer connection and transmit all VPN routes between
and MPLS Loopback1 interfaces on PE-A, PE-B, and PE-C. Enable MPLS forwarding on
the public network.
Multicast Enable multicast on P. Enable multicast on the public network instance on PE-
function A, PE-B, and PE-C. Enable multicast on VPN-RED instance on PE-A, PE-B,
and PE-C. Enable multicast on VPN-BLUE instance on PE-B and PE-C. Enable
multicast on CE-Ra, CE-Rb, CE-Rc, CE-Bb, and CE-Bc.
IGMP Enable IGMP on GE2 of PE-A.Enable IGMP on GE1 of CE-Rb, GE1 of CE-
function Rc, and GE1 of CE-Bc.

PIM Enable PIM-SM on all the VPN interfaces in VPN-RED instance. Enable PIM-
function SM on all the VPN interfaces in VPN-BLUE instance. Enable PIM-SM on all
the interfaces of P and CEs, as well as public network instance interfaces of
PEs. Configure Loopback1 of P as the C-BSR and C-RP of public network
(serving all multicast groups). Configure Loopback1 of CE-Rb as the C-BSR
and C-RP of VPN-RED (serving all multicast groups). Configure Loopback2
of PE-C as the C-BSR and C-RP of VPN-BLUE (serving all multicast groups).
1. Configure MPLS/BGP VPN to ensure that the VPN network works normally and unicast
routes are reachable.
2. Enable multicast VPN services of integrated mode.
3. Enable multicast and PIM in the entire network. Enable multicast of public network on PEs
and Ps, and enable multicast of the VPN instances on PEs and CEs.
4. Configure the same Share-group address, the same MTI, and the same switch-group-pool
for the same VPN instance on each PE.
5. Configure the MTI address of each PE as the IBGP peer interface address in the public
network, and enable PIM on the MTI.
Data Preparation
See Table 8-2.
Procedure
Step 1 Configure PE-A.
# Configure an ID for PE-A, enable IP multicast routing in the public network, configure MPLS
LSR-ID, and enable LDP.
[PE-A] router id 1.1.1.1
[PE-A] multicast routing-enable
[PE-A] mpls lsr-id 1.1.1.1
[PE-A] mpls
[PE-A-mpls] quit
[PE-A] mpls ldp
[PE-A-mpls-ldp] quit
# Set the service mode of the SPUC to be Tunnel mode.Enable multicast VPN services on the
SPUC of the PE. Suppose that the SPUC is in slot 4, the configuration is as follows:
[PE-A] quit
<PE-A> set board-type slot 4 tunnel
<PE-A> system-view
[PE-A] multicast-vpn slot 4
# Create VPN RED instance and enter the VPN instance view. Configure the VPN IPv4 prefix
and create egress and ingress routes for the instance. Enable IP multicast and configure Share-
Group. Specify an MTI bound to the VPN instance and the range of the switch-address-pool.

[PE-A] ip vpn-instance RED

[PE-A-vpn-instance-RED] route-distinguisher 100:1
[PE-A-vpn-instance-RED] vpn-target 100:1 export-extcommunity
[PE-A-vpn-instance-RED] vpn-target 100:1 import-extcommunity
[PE-A-vpn-instance-RED] multicast routing-enable
[PE-A-vpn-instance-RED] multicast-domain share-group 239.1.1.1 binding mtunnel 0
[PE-A-vpn-instance-RED] multicast-domain switch-group-pool 225.2.2.1 28
[PE-A-vpn-instance-RED] quit
# Enable LDP and PIM-SM on the interface GigabitEthernet 1/0/0 in the public network.
[PE-A] interface gigabitethernet 1/0/0
[PE-A-GigabitEthernet1/0/0] ip address 192.168.6.1 24
[PE-A-GigabitEthernet1/0/0] pim sm
[PE-A-GigabitEthernet1/0/0] mpls
[PE-A-GigabitEthernet1/0/0] mpls ldp
# Bind the interface GigabitEthernet 2/0/0 to VPN RED instance, and enable IGMP and PIM-
SM.
[PE-A-GigabitEthernet2/0/0] ip binding vpn-instance RED
[PE-A-GigabitEthernet2/0/0] igmp enable
# Bind GigabitEthernet 3/0/0 to VPN RED instance and enable PIM-SM.

# Assign an IP address for the interface Loopback1 and enable PIM-SM.

[PE-A] interface loopback 1
[PE-A-LoopBack1] ip address 1.1.1.1 32
[PE-A-LoopBack1] pim sm
[PE-A-LoopBack1] quit
# Assign an IP address for the interface MTI0. The address of MTI0 is same as the that of the
interface Loopback0. The system then automatically binds MTI0 to VPN RED instance. Enable
PIM-SM on the interface.
[PE-A] interface MTunnel 0
[PE-A-MTunnel0] ip address 1.1.1.1 32
[PE-A-MTunnel0] pim sm
[PE-A-MTunnel0] quit
# Configure BGP, OSPF, and RIP.

[PE-A] bgp 100
[PE-A-bgp] group VPN-G internal
[PE-A-bgp] peer VPN-G connect-interface LoopBack1
[PE-A-bgp] peer 1.1.1.2 group VPN-G
[PE-A-bgp] peer 1.1.1.3 group VPN-G
[PE-A-bgp] ipv4-family vpn-instance RED
[PE-A-bgp-RED] import-route rip 2
[PE-A-bgp-RED] import-route direct
[PE-A-bgp-RED] quit
[PE-A-bgp] ipv4-family vpnv4
[PE-A-bgp-af-vpnv4] peer VPN-G enable
[PE-A-bgp-af-vpnv4] peer 1.1.1.2 group VPN-G
[PE-A-bgp-af-vpnv4] peer 1.1.1.3 group VPN-G
[PE-A-bgp-af-vpnv4] quit
[PE-A-bgp] quit
[PE-A] ospf 1
[PE-A-ospf-1] area 0.0.0.0
[PE-A-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0


[PE-A-ospf-1-area-0.0.0.0] quit
[PE-A-ospf-1] quit
[PE-A] rip 2 vpn-instance RED
[PE-A-rip-2] network 10.0.0.0
[PE-A-rip-2] import-route bgp cost 3
Step 2 Configure PE-B.

# Configure an ID for PE-B, enable multicast in the public network, configure MPLS LSR-ID,
and enable LDP.
[PE-B] router id 1.1.1.2
[PE-B] multicast routing-enable
[PE-B] mpls lsr-id 1.1.1.2
[PE-B] mpls
[PE-B-mpls] quit
[PE-B] mpls ldp
[PE-B-mpls-ldp] quit
[PE-B] quit
<PE-B> set board-type slot 4 tunnel
<PE-B> system-view
[PE-B] multicast-vpn slot 4
# Create VPN BLUE instance and enter the VPN instance view. Configure VPN IPv4 prefix
and create the egress and ingress routes for the instance. Enable IP multicast and configure Share-
[PE-B] ip vpn-instance BLUE
[PE-B-vpn-instance-BLUE] route-distinguisher 200:1
[PE-B-vpn-instance-BLUE] vpn-target 200:1 export-extcommunity
[PE-B-vpn-instance-BLUE] vpn-target 200:1 import-extcommunity
[PE-B-vpn-instance-BLUE] multicast routing-enable
[PE-B-vpn-instance-BLUE] multicast-domain share-group 239.2.2.2 binding mtunnel 1
[PE-B-vpn-instance-BLUE] multicast-domain switch-group-pool 225.4.4.1 28
# Create VPN RED instance and enter the VPN instance view. Configure VPN IPv4 prefix and
create egress and ingress routes for the instance. Enable IP multicast and configure Share-Group.
Specify an MTI bound to the VPN instance and the range of the switch-address-pool.
[PE-B] ip vpn-instance RED
[PE-B-vpn-instance-RED] route-distinguisher 100:1
[PE-B-vpn-instance-RED] vpn-target 100:1 export-extcommunity
[PE-B-vpn-instance-RED] vpn-target 100:1 import-extcommunity
[PE-B-vpn-instance-RED] multicast routing-enable
[PE-B-vpn-instance-RED] multicast-domain share-group 239.1.1.1 binding mtunnel 0
[PE-B-vpn-instance-RED] multicast-domain switch-group-pool 225.2.2.1 28
[PE-B] interface gigabitethernet 1/0/0
[PE-B-GigabitEthernet1/0/0] ip address 192.168.7.1 24
[PE-B-GigabitEthernet1/0/0] pim sm
[PE-B-GigabitEthernet1/0/0] mpls
[PE-B-GigabitEthernet1/0/0] mpls ldp
# Bind the interface GigabitEthernet 2/0/0 to VPN BLUE instance, and enable PIM-SM.
[PE-B-GigabitEthernet2/0/0] ip binding vpn-instance BLUE
# Bind the interface GigabitEthernet 3/0/0 to VPN RED instance, and enable PIM-SM.


[PE-B-GigabitEthernet3/0/0] ip binding vpn-instance RED
# Assign an IP address for the interface Loopback1, and enable PIM-SM.

[PE-B] interface loopback 1
[PE-B-LoopBack1] ip address 1.1.1.2 32
[PE-B-LoopBack1] pim sm
[PE-B-LoopBack1] quit
# Assign an IP address for the interface MTI0. The address of MTI0 is same as the that of the
interface Loopback1. Enable PIM-SM on the interface.
[PE-B] interface MTunnel 0
[PE-B-MTunnel0] ip address 1.1.1.2 32
[PE-B-MTunnel0] pim sm
# Assign an IP address for MTI1. The address of MTI1 is the same as that of the interface
Loopback1. Enable PIM-SM on the interface.
[PE-B] interface MTunnel 1
[PE-B-MTunnel1] ip address 1.1.1.2 32
[PE-B-MTunnel1] pim sm

[PE-B] bgp 100
[PE-B-bgp] group VPN-G internal
[PE-B-bgp] peer VPN-G connect-interface LoopBack1
[PE-B-bgp] peer 1.1.1.1 group VPN-G
[PE-B-bgp] peer 1.1.1.3 group VPN-G
[PE-B-bgp] ipv4-family vpn-instance RED
[PE-B-bgp-RED] import-route rip 2
[PE-B-bgp-RED] import-route direct
[PE-B-bgp-RED] quit
[PE-B-bgp] ipv4-family vpn-instance BLUE
[PE-B-bgp-BLUE] import-route rip 3
[PE-B-bgp-BLUE] import-route direct
[PE-B-bgp-BLUE] quit
[PE-B-bgp] ipv4-family vpnv4
[PE-B-bgp-af-vpnv4] peer VPN-G enable
[PE-B-bgp-af-vpnv4] peer 1.1.1.1 group VPN-G
[PE-B-bgp-af-vpnv4] peer 1.1.1.3 group VPN-G
[PE-B-bgp-af-vpnv4] quit
[PE-B-bgp] quit
[PE-B] ospf 1
[PE-B-ospf-1] area 0.0.0.0
[PE-B-ospf-1-area-0.0.0.0] network 1.1.1.2 0.0.0.0
[PE-B-ospf-1-area-0.0.0.0] quit
[PE-B-ospf-1] quit
[PE-B] rip 2 vpn-instance RED
[PE-B-rip-2] network 10.0.0.0
[PE-B-rip-2] import-route bgp cost 3
[PE-B-rip-2] quit
[PE-B] rip 3 vpn-instance BLUE
[PE-B-rip-3] network 10.0.0.0
[PE-B-rip-3] import-route bgp cost 3
Step 3 Configure PE-C.

# Configure an ID for PE-C, enable IP multicast of the public network, configure MPLS LSR-
ID, and enable LDP.
[PE-C] router id 1.1.1.3
[PE-C] multicast routing-enable
[PE-C] mpls lsr-id 1.1.1.3

[PE-C] mpls
[PE-C-mpls] quit
[PE-C] mpls ldp
[PE-C-mpls-ldp] quit
[PE-C] quit
<PE-C> set board-type slot 4 tunnel
<PE-C> system-view
[PE-C] multicast-vpn slot 4
Specify an MTI bound to the VPN instance and the range of the switch-addres-pool.
[PE-C] ip vpn-instance RED
[PE-C-vpn-instance-RED] route-distinguisher 100:1
[PE-C-vpn-instance-RED] vpn-target 100:1 export-extcommunity
[PE-C-vpn-instance-RED] vpn-target 100:1 import-extcommunity
[PE-C-vpn-instance-RED] multicast routing-enable
[PE-C-vpn-instance-RED] multicast-domain share-group 239.1.1.1 binding mtunnel 0
[PE-C-vpn-instance-RED] multicast-domain switch-group-pool 225.2.2.1 28
# Create VPN BLUE instance and enter the VPN instance view. Configure the VPN IPv4 prefix
[PE-C] ip vpn-instance BLUE
[PE-C-vpn-instance-BLUE] route-distinguisher 200:1
[PE-C-vpn-instance-BLUE] vpn-target 200:1 export-extcommunity
[PE-C-vpn-instance-BLUE] vpn-target 200:1 import-extcommunity
[PE-C-vpn-instance-BLUE] multicast routing-enable
[PE-C-vpn-instance-BLUE] multicast-domain share-group 239.2.2.2 binding mtunnel 1
[PE-C-vpn-instance-BLUE] multicast-domain switch-group-pool 225.4.4.1 28
# Enable LDP and PIM-SM on the interface GigabitEthernet1/0/0 in the public network.
[PE-C] interface gigabitethernet 1/0/0
[PE-C-GigabitEthernet1/0/0] ip address 192.168.8.1 24
[PE-C-GigabitEthernet1/0/0] pim sm
[PE-C-GigabitEthernet1/0/0] mpls
[PE-C-GigabitEthernet1/0/0] mpls ldp
# Bind the interface GigabitEthernet2/0/0 to VPN RED instance, and enable PIM-SM.
[PE-C-GigabitEthernet2/0/0] ip binding vpn-instance RED
# Bind the interface GigabitEthernet3/0/0 to VPN BLUE instance, and enable PIM-SM.
[PE-C-GigabitEthernet3/0/0] ip binding vpn-instance BLUE
# Assign an IP address for the interface Loopback1, and enable PIM-SM.

[PE-C] interface loopback 1
[PE-C-LoopBack1] ip address 1.1.1.3 32
[PE-C-LoopBack1] pim sm
[PE-C-LoopBack1] quit
# Assign the an IP address for the interface MTI0. The address of MTI0 is the same as that of
the interface Loopback1. Enable PIM-SM on the interface.

[PE-C] interface MTunnel 0

[PE-C-MTunnel0] ip address 1.1.1.3 32
[PE-C-MTunnel0] pim sm
# Assign the an IP address for MTI1. The address of MTI1 is the same as that of the interface
Loopback1. Enable PIM-SM on the interface.
[PE-C] interface MTunnel 1
[PE-C-MTunnel1] ip address 1.1.1.3 32
[PE-C-MTunnel1] pim sm
# Bind the interface Loopback2 to VPN BLUE instance, and enable PIM-SM.
[PE-C-LoopBack2] ip binding vpn-instance BLUE
# Configure the interface Loopback2 as the C-BSR and the C-RP of VPN-BLUE.
[PE-C] pim vpn-instance BLUE
[PE-C-pim-blue] c-bsr Loopback2
[PE-C-pim-blue] c-rp Loopback2
[PE-C-pim-blue] quit

[PE-C] bgp 100
[PE-C-bgp] group VPN-G internal
[PE-C-bgp] peer VPN-G connect-interface LoopBack1
[PE-C-bgp] peer 1.1.1.1 group VPN-G
[PE-C-bgp] peer 1.1.1.2 group VPN-G
[PE-C-bgp] ipv4-family vpn-instance RED
[PE-C-bgp-RED] import-route rip 2
[PE-C-bgp-RED] import-route direct
[PE-C-bgp-RED] quit
[PE-C-bgp] ipv4-family vpn-instance BLUE
[PE-C-bgp-BLUE] import-route rip 3
[PE-C-bgp-BLUE] import-route direct
[PE-C-bgp-BLUE] quit
[PE-C-bgp] ipv4-family vpnv4
[PE-C-bgp-af-vpnv4] peer VPN-G enable
[PE-C-bgp-af-vpnv4] peer 1.1.1.1 group VPN-G
[PE-C-bgp-af-vpnv4] peer 1.1.1.2 group VPN-G
[PE-C-bgp-af-vpnv4] quit
[PE-C-bgp] quit
[PE-C] ospf 1
[PE-C-ospf-1] area 0.0.0.0
[PE-C-ospf-1-area-0.0.0.0] network 1.1.1.3 0.0.0.0
[PE-C-ospf-1-area-0.0.0.0] quit
[PE-C-ospf-1] quit
[PE-C] rip 2 vpn-instance RED
[PE-C-rip] network 10.0.0.0
[PE-C-rip] import-route bgp cost 3
[PE-C-rip] quit
[PE-C] rip 3 vpn-instance BLUE
[PE-C-rip] network 10.0.0.0
[PE-C-rip] import-route bgp cost 3
Step 4 Configure P.
# Enable multicast in the public network, configure MPLS LSR-ID, and enable LDP.
[P] multicast routing-enable
[P] mpls lsr-id 2.2.2.2
[P] mpls
[P-mpls] quit
[P] mpls ldp

[P-mpls-ldp] quit
[P-GigabitEthernet1/0/0] ip address 192.168.6.2 24
[P-GigabitEthernet1/0/0] mpls
[P-GigabitEthernet1/0/0] mpls ldp

[P] interface loopback 1
[P-LoopBack1] ip address 2.2.2.2 32
[P-LoopBack1] pim sm
[P-LoopBack1] quit
# Configure the interface Loopback1 as the C-BSR and C-RP of the public network instance.
[P] pim
[P-pim] c-bsr Loopback1
[P-pim] c-rp Loopback1
# Configure OSPF.
[P] ospf 1
[P-ospf-1] area 0.0.0.0
[P-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[P-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.255.255
[P-ospf-1-area-0.0.0.0] quit
Step 5 Configure CE-Ra.

# Enable multicast.
[CE-Ra] multicast routing-enable
# Enable PIM-SM on the interface GigabitEthernet 1/0/0 in the VPN.

[CE-Ra] interface gigabitethernet 1/0/0
[CE-Ra-GigabitEthernet1/0/0] ip address 10.110.7.1 24
[CE-Ra-GigabitEthernet1/0/0] pim sm

[CE-Ra] interface gigabitethernet 2/0/0
[CE-Ra-GigabitEthernet2/0/0] ip address 10.110.2.2 24
[CE-Ra-GigabitEthernet2/0/0] pim sm
# Configure RIP.
[CE-Ra] rip 2
[CE-Ra-rip-2] network 10.0.0.0
[CE-Ra-rip-2] import-route direct

Step 6 Configure CE-Bb.

# Enable multicast.
[CE-Bb] multicast routing-enable
# Enable PIM-SM on the interface GigabitEthernet 1/0/0.

[CE-Bb] interface gigabitethernet 1/0/0
[CE-Bb-GigabitEthernet1/0/0] ip address 10.110.8.1 24
[CE-Bb-GigabitEthernet1/0/0] pim sm

[CE-Bb] interface gigabitethernet 2/0/0
[CE-Bb-GigabitEthernet2/0/0] ip address 10.110.3.2 24
[CE-Bb-GigabitEthernet2/0/0] pim sm
# Configure RIP.
[CE-Bb] rip 3
[CE-Bb-rip-3] network 10.0.0.0
[CE-Bb-rip-3] import-route direct
Step 7 Configure CE-Rb.

# Enable multicast.
[CE-Rb] multicast routing-enable
# Enable PIM-SM and IGMP on the interface GigabitEthernet 1/0/0.

[CE-Rb] interface gigabitethernet 1/0/0
[CE-Rb-GigabitEthernet1/0/0] ip address 10.110.9.1 24
[CE-Rb-GigabitEthernet1/0/0] pim sm
[CE-Rb-GigabitEthernet1/0/0] igmp enable



[CE-Rb] interface loopback 1
[CE-Rb-LoopBack1] ip address 22.22.22.22 32
[CE-Rb-LoopBack1] pim sm
[CE-Rb-LoopBack1] quit
# Configure the interface Loopback1 as the BSR and RP of VPN-RED

[CE-Rb] pim vpn-instance RED
[CE-Rb-pim] c-bsr Loopback1
[CE-Rb-pim] c-rp Loopback1
[CE-Rb-pim] quit
# Configure RIP.
[CE-Rb] rip 2
[CE-Rb-rip-2] network 10.0.0.0
[CE-Rb-rip-2] network 22.0.0.0
[CE-Rb-rip-2] import-route direct

Step 8 Configure CE-Rc.

# Enable IP multicast.
[CE-Rc] multicast routing-enable
# Enable PIM-SM and IGMP on the interface GigabitEthernet 1/0/0 in the VPN.
[CE-Rc] interface gigabitethernet 1/0/0
[CE-Rc-GigabitEthernet1/0/0] ip address 10.110.10.1 24
[CE-Rc-GigabitEthernet1/0/0] pim sm
[CE-Rc-GigabitEthernet1/0/0] igmp enable


# Configure RIP.
[CE-Rc] rip 2
[CE-Rc-rip-2] network 10.0.0.0
[CE-Rc-rip-2] import-route direct
Step 9 Configure CE-Bc.

# Enable IP multicast.
[CE-Bc] multicast routing-enable
# Enable PIM-SM and IGMP on the interface GigabitEthernet 1/0/0 in the VPN.
[CE-Bc] interface gigabitethernet 1/0/0
[CE-Bc-GigabitEthernet1/0/0] ip address 10.110.11.1 24
[CE-Bc-GigabitEthernet1/0/0] pim sm
[CE-Bc-GigabitEthernet1/0/0] igmp enable

[CE-Bc] interface gigabitethernet 2/0/0
[CE-Bc-GigabitEthernet2/0/0] ip address 10.110.6.2 24
[CE-Bc-GigabitEthernet2/0/0] pim sm
# Configure RIP.
[CE-Bc] rip 3
[CE-Bc-rip-3] network 10.0.0.0
[CE-Bc-rip-3] import-route direct

After the preceding configurations are complete, PC1, PC2, and PC3 can receive multicast
information from Source1, and PC4 can receive multicast information from Source2.
----End
Configuration Files
l Configuration file of PE-A
#
sysname PE-A

#
router id 1.1.1.1
#
#
multicast-vpn slot 4
#
mpls lsr-id 1.1.1.1
mpls
#
mpls ldp
#
ip vpn-instance RED
multicast-domain share-group 239.1.1.1 binding MTunnel 0
multicast-domain switch-group-pool 225.2.2.0 255.255.255.240
#
undo shutdown
ip address 192.168.6.1 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip binding vpn-instance RED
ip address 10.110.1.1 255.255.255.0
pim sm
igmp enable
#
undo shutdown
ip address 10.110.2.1 255.255.255.0
pim sm
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
pim sm
#
interface MTunnel0
ip address 1.1.1.1 255.255.255.255
pim sm
#
bgp 100
group VPN-G internal
peer VPN-G connect-interface LoopBack1
peer 1.1.1.2 group VPN-G
#
ipv4-family unicast
peer VPN-G enable
peer 1.1.1.2 enable
peer 1.1.1.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer VPN-G enable
peer 1.1.1.2 enable


peer 1.1.1.3 enable
#
ipv4-family vpn-instance RED
import-route rip 2
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.1 0.0.0.0
network 192.168.0.0 0.0.255.255
#
rip 2 vpn-instance RED
network 10.0.0.0
import-route bgp cost 3
#
return
l Configuration file of PE-B
#
sysname PE-B
#
router id 1.1.1.2
#
#
#
mpls lsr-id 1.1.1.2
mpls
#
mpls ldp
#
ip vpn-instance BLUE
#
ip vpn-instance RED
#
undo shutdown
ip address 192.168.7.1 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip binding vpn-instance BLUE
ip address 10.110.3.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.4.1 255.255.255.0
pim sm
#
interface LoopBack1

ip address 1.1.1.2 255.255.255.255

pim sm
#
interface MTunnel0
ip address 1.1.1.2 255.255.255.255
pim sm
#
interface MTunnel1
ip address 1.1.1.2 255.255.255.255
pim sm
#
bgp 100
#
ipv4-family unicast
peer VPN-G enable
peer 1.1.1.1 enable
peer 1.1.1.3 enable
#
ipv4-family vpnv4
policy vpn-target
peer VPN-G enable
peer 1.1.1.1 enable
peer 1.1.1.3 enable
#
import-route rip 2
import-route direct
#
ipv4-family vpn-instance BLUE
import-route rip 3
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.2 0.0.0.0
network 192.168.0.0 0.0.255.255
#
network 10.0.0.0
#
rip 3 vpn-instance blue
network 10.0.0.0
#
return
l Configuration file of PE-C
#
sysname PE-C
#
router id 1.1.1.3
#
#
#

mpls lsr-id 1.1.1.3

mpls
#
mpls ldp
#
ip vpn-instance RED
#
#
undo shutdown
ip address 192.168.8.1 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 10.110.5.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.6.1 255.255.255.0
pim sm
#
interface LoopBack1
ip address 1.1.1.3 255.255.255.255
pim sm
#
interface LoopBack2
ip address 33.33.33.33 255.255.255.255
pim sm
#
pim vpn-instance BLUE
c-bsr LoopBack2
c-rp LoopBack2
#
interface MTunnel0
ip address 1.1.1.3 255.255.255.255
pim sm
#
interface MTunnel1
ip address 1.1.1.3 255.255.255.255
pim sm
#
bgp 100


#
ipv4-family unicast
peer VPN-G enable
peer 1.1.1.1 enable
peer 1.1.1.2 enable
#
ipv4-family vpnv4
policy vpn-target
peer VPN-G enable
peer 1.1.1.1 enable
peer 1.1.1.2 enable
#
import-route rip 2
import-route direct
#
import-route rip 3
import-route direct
#
ospf 1
area 0.0.0.0
network 1.1.1.3 0.0.0.0
network 192.168.0.0 0.0.255.255
#
network 10.0.0.0
#
rip 3 vpn-instance BLUE
network 10.0.0.0
#
return
l Configuration file of P
#
sysname P
#
#
mpls lsr-id 2.2.2.2
mpls
#
mpls ldp
#
undo shutdown
ip address 192.168.6.2 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 192.168.7.2 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 192.168.8.2 255.255.255.0
pim sm

mpls
mpls ldp
#
interface LoopBack1
ip address 2.2.2.2 255.255.255.255
pim sm
#
pim
c-bsr Loopback1
c-rp Loopback1
#
ospf 1
area 0.0.0.0
network 2.2.2.2 0.0.0.0
network 192.168.0.0 0.0.255.255
#
return
l Configuration file of CE-Ra
#
sysname CE-Ra
#
#
undo shutdown
ip address 10.110.7.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.2.2 255.255.255.0
pim sm
#
rip 2
network 10.0.0.0
import-route direct
#
return
l Configuration file of CE-Bb
#
sysname CE-Bb
#
#
undo shutdown
ip address 10.110.8.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.3.2 255.255.255.0
pim sm
#
rip 3
network 10.0.0.0
import-route direct
#
return
l Configuration file of CE-Rb
#
sysname CE-Rb
#
#
undo shutdown

ip address 10.110.9.1 255.255.255.0

pim sm
igmp enable
#
undo shutdown
ip address 10.110.4.2 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.12.1 255.255.255.0
pim sm
#
ip address 22.22.22.22 32
pim sm
#
pim
c-bsr Loopback1
c-rp Loopback1
#
rip 2
network 10.0.0.0
network 22.0.0.0
import-route direct
#
return
l Configuration file of CE-Rc
#
sysname CE-Rc
#
#
undo shutdown
ip address 10.110.10.1 255.255.255.0
pim sm
igmp enable
#
undo shutdown
ip address 10.110.5.2 255.255.255.0
pim sm
#
undo shutdown
ip address 10.110.12.2 255.255.255.0
pim sm
#
rip 2
network 10.0.0.0
import-route direct
#
return
l Configuration file of CE-Bc
#
sysname CE-Bc
#
#
undo shutdown
ip address 10.110.11.1 255.255.255.0
pim sm
igmp enable
#

undo shutdown
ip address 10.110.6.2 255.255.255.0
pim sm
#
rip 3
network 10.0.0.0
import-route direct
#
return
8.5.2 Example for Configuring Inter-AS MD VPN
In the inter-AS MPLS/BGP VPN (VPN-Option C mode) shown in Figure 8-3, the MD solution
is used to deploy multicast services.
Figure 8-3 Networking diagram of configuring inter-AS MD VPN
Source2 PC1
VPN VPN
BLUE RED
GE1 GE1
Loopback0 Loopback0
Loopback1 Loopback1
CE-B GE2 GE2 CE-C
AS 100 AS 200
GE3 GE2
GE1 GE2 GE1
Loopback1 Loopback1
GE1 GE2 GE1
GE2 PE-A PE-B PE-C PE-D GE3
CE-A GE2 GE2 CE-D
Loopback2 Loopback2
GE1
GE1 VPN VPN
RED BLUE
PC2
Source1
NOTE
GE1 stands for GigabitEthernet 1/0/0, GE2 stands for GigabitEthernet 2/0/0, and GE3 stands for
GigabitEthernet 3/0/0. The IP address of each interface is listed as follows:
The devices support two processing modes of the multicast VPN service: distributed mode and integrated
mode. In distributed mode, you must run the multicast-vpn slot command to specify the slot that supports
multicast VPN. In integrated mode, you must run the set board-type slot and multicast-vpn slot
commands to set the service mode of the SPUC to be Tunnel mode and enable multicast VPN on an SPUC
separately. The following configuration example use the distributed mode to cofigure the multicast VPN
service.

Table 8-3 Configuration of router interface

PE-A GE1: 10.10.1.1/24 Public instance
GE2: 10.111.1.1/24 VPN-RED
GE3: 10.111.2.1/24 VPN-BLUE
Loopback1: 1.1.1.1/32 Public instance

It sets up IBGP peer relationship with Loopback1
interface of PE-B, and sets up the EBGP peer
relationship with Loopback1 interface of PE-D.
PE-B GE1: 10.10.1.2/24 Public instance
GE2: 192.168.1.1/24 Public instance

GE2 is the BSR boundary.

This interface is used to set up BGP peer
relationships and MSDP peer relationships. This
interface sets up the IBGP peer relationship with
Loopback1 interface of PE-A and the EBGP peer
relationship with Loopback1 interface of PE-C.

It acts as the C-BSR and C-RP of the PIM domain
in AS 100
PE-C GE1: 10.10.2.1/24 Public instance
GE2: 192.168.1.2/24 Public instance

GE2 is the BSR boundary.
Loopback1: 1.1.1.3/32 Public instance.

This interface is used to set up BGP peer
relationships and MSDP peer relationships. This
interface sets up the the IBGP peer relationship
with Loopback1 interface of PE-D and the EBGP
peer relationship with Loopback1 interface of
PE-B.

Ths interface acts as the C-BSR and C-RP of the
PIM domain in AS 200
PE-D GE1: 10.10.2.2/24 Public instance
GE2: 10.111.3.1/24 VPN-RED
GE3: 10.111.4.1/24 VPN-BLUE


This interface sets up the IBGP peer relationship
with Loopback1 interface of PE-C and the EBGP
peer relationship with Loopback1 interface of
PE-A.
CE-A GE1: 10.111.5.1/24 -
GE2: 10.111.1.2/24 -
CE-B GE1: 10.111.6.1/24 -
GE2: 10.111.2.2/24 -
Loopback0: 2.2.2.2/32 It acts as the C-BSR and C-RP of the PIM domain
in VPN-BLUE
CE-C GE1: 10.111.7.1/24 -
GE2: 10.111.3.2/24 -
Loopback0: 3.3.3.3/24 It acts as the C-BSR and C-RP of the PIM domain
in VPN-RED
CE-D GE1: 10.111.8.1/24 -
GE2: 10.111.4.2/24 -
Source1 10.111.5.2./24 Multicast source in VPN-RED
Source2 10.111.6.2/24 Multicast source in VPN-BLUE
PC1 10.111.7.2/24 Multicast receiver in VPN-RED
PC2 10.111.8.2/24 Multicast receiver in VPN-BLUE
Table 8-4 Networking requirements of inter-AS MD VPN

Multicast source Multicast source of VPN RED is Source1 and the multicast receiver is
and multicast PC1.
receiver Multicast source of VPN BLUE is Source2 and the multicast receiver
is PC2.
In VPN RED, Share-Group address is 239.1.1.1 and Switch-Group
address pool ranges from 225.1.1.1 to 225.1.1.16.
In VPN BLUE, Share-Group address is 239.4.4.4 and Switch-Group
address pool ranges from 225.4.4.1 to 225.4.4.16.

VPN instance On PE-A, GE1 and Loopback1 belong to the public network instance,
which the GE2 belongs to VPN-RED, and GE3 belongs to VPN-BLUE.
interfaces on PEs On PE-B, GE1, GE2, Loopback1, and Loopback2 belong to the public
belong to network instance.
On PE-C, GE1, GE2, Loopback1, and Loopback2 belong to the public
network instance.
On PE-D, GE1 and Loopback1 belong to the public network instance,
GE2 belongs to VPN-RED, and GE3 belongs to VPN-BLUE.
Routing protocol Configure OSPF in AS 100 and AS 200. Enable OSPF on PE and CE
and MPLS routers. Configure BGP peers and transmit all VPN routes between
Loopback1 interfaces of PE-A, PE-B, PE-C and PE-D. Enable MPLS
in AS 100 and AS 200.
Multicast Enable multicast on the public network instance on PE-A, PE-B, PE-C,
functions and PE-D. Enable multicast on VPN-RED and VPN-BLUE on PE-A
and PE-D. Enable multicast on CE-A, CE-B, CE-C, and CE-D.
IGMP functions Enable IGMP on GE1 on CE-C. Enable IGMP on GE1 on CE-D.
PIM functions Enable PIM-SM on all the public network instance interfaces on PE-A,
PE-B, PE-C, and PE-D. Enable PIM-SM on the interfaces of VPN-RED
instance and VPN-BLUE instance on PE-A and PE-D. Set Loopback2
interfaces of PE-B and PE-C as the C-BSR and C-RP of the public
network instance in the AS which they belong to (serving all multicast
groups). Set Loopback0 interface of CE-B as the C-BSR and C-RP of
VPN-BLUE (serving all multicast groups). Set Loopback0 interface of
CE-C as the C-BSR and C-RP of VPN-RED (serving all multicast
groups).
MSDP functions Establish MSDP peer relationships on Loopback1 interfaces of PE-B

and PE-C.
1. Configure MPLS/BGP VPN to ensure that the VPN network works normally and unicast
routes are reachable.
2. Enable the SPUC to support the multicast VPN service of integrated mode. In this manner,
multicast packets are encapsulated and decapsulated in GRE mode during the transmission
between the VPN instance and the public network instance.
NOTE
In VPN-OptionC mode, multicast packets on the ASBR-PE (PE-B and PE-C in Figure 8-3) do not
require the GRE encapsulation and decapsulation. As a result, the SPUC is not enabled to support
the multicast VPN service.
3. Enable multicast and PIM in the entire network, enable multicast on the PEs and PEs in
the public network, and enable multicast on PEs and CEs in the VPNs.
4. Configure MSDP peers on EBGP peers of PE-B and PE-C.

5. Configure the same Share-Group address, the same MTI, and the same Switch-MDT switch
for a VPN instance on PE-A and PE-D.
6. Configure the MTI address as the IBGP peer interface address of the public network on
PE-A and PE-D, and enable PIM on the MTI.
Data Preparation
See Table 8-4 for information about data preparation.
Procedure
Step 1 Configuring PE-A
# Configure an ID for PE-A, enable multicast in the public network, configure an ID for an
MPLS LSR, and enable LDP.
[PE-A] router id 1.1.1.1
[PE-A] multicast routing-enable
[PE-A] mpls lsr-id 1.1.1.1
[PE-A] mpls
[PE-A-mpls] quit
[PE-A] mpls ldp
[PE-A-mpls-ldp] quit
[PE-A] quit
<PE-A> system-view
[PE-A] ip vpn-instance RED
[PE-A-vpn-instance-RED] route-distinguisher 100:1
[PE-A-vpn-instance-RED] vpn-target 100:1 export-extcommunity
[PE-A-vpn-instance-RED] vpn-target 100:1 import-extcommunity
[PE-A-vpn-instance-RED] multicast routing-enable
[PE-A-vpn-instance-RED] multicast-domain share-group 239.1.1.1 binding mtunnel 0
[PE-A-vpn-instance-RED] multicast-domain switch-group-pool 225.1.1.1 28
[PE-A-vpn-instance-RED] quit
[PE-A] ip vpn-instance BLUE
[PE-A-vpn-instance-BLUE] route-distinguisher 200:1
[PE-A-vpn-instance-BLUE] vpn-target 200:1 export-extcommunity
[PE-A-vpn-instance-BLUE] vpn-target 200:1 import-extcommunity
[PE-A-vpn-instance-BLUE] multicast routing-enable
[PE-A-vpn-instance-BLUE] multicast-domain share-group 239.4.4.4 binding mtunnel 1
[PE-A-vpn-instance-BLUE] multicast-domain switch-group-pool 225.4.4.1 28
[PE-A-vpn-instance-BLUE] quit
# Enable LDP and PIM-SM on GigabitEthernet 1/0/0 in the public network.

[PE-A-GigabitEthernet1/0/0] mpls

[PE-A-GigabitEthernet1/0/0] mpls ldp

# Bind GigabitEthernet 3/0/0 to VPN BLUE instance and enable PIM-SM.

[PE-A-GigabitEthernet3/0/0] ip binding vpn-instance BLUE
# Configure an IP address for Loopback 1 interface and enable PIM-SM.

[PE-A] interface loopback 1
[PE-A-LoopBack1] ip address 1.1.1.1 32
[PE-A-LoopBack1] pim sm
[PE-A-LoopBack1] quit
# Configure an IP address (the same as that of Loopback 1 interface) for MTI0 and enable PIM-
SM.
SM.
# Configure BGP and OSPF.

[PE-A] bgp 100
[PE-A-bgp] group pea-peb internal
[PE-A-bgp] peer pea-peb label-route-capability
[PE-A-bgp] peer pea-peb connect-interface LoopBack1
[PE-A-bgp] peer 1.1.1.2 group pea-peb
[PE-A-bgp] group pea-ped external
[PE-A-bgp] peer pea-ped as-number 200
[PE-A-bgp] peer pea-ped ebgp-max-hop 255
[PE-A-bgp] peer 1.1.1.4 group pea-ped
[PE-A-bgp] peer 1.1.1.4 connect-interface Loopback1
[PE-A-bgp] ipv4-family vpn-instance RED
[PE-A-bgp-RED] import-route ospf 2
[PE-A-bgp-RED] import-route direct
[PE-A-bgp-RED] quit
[PE-A-bgp] ipv4-family vpn-instance BLUE
[PE-A-bgp-BLUE] import-route ospf 3
[PE-A-bgp-BLUE] import-route direct
[PE-A-bgp-BLUE] quit
[PE-A-bgp] ipv4-family vpnv4
[PE-A-bgp-af-vpnv4] peer 1.1.1.4 enable
[PE-A-bgp-af-vpnv4] quit
[PE-A] ospf 1
[PE-A-ospf-1] quit
[PE-A] ospf 2 vpn-instance RED
[PE-A-ospf-2] import-route bgp


[PE-A] ospf 3 vpn-instance BLUE
[PE-A-ospf-3] import-route bgp
Step 2 Configuring PE-B

# Configure an ID for PE-B, enable multicast in the public network, configure an ID for an
[PE-B] router id 1.1.1.2
[PE-B] multicast routing-enable
[PE-B] mpls lsr-id 1.1.1.2
[PE-B] mpls
[PE-B-mpls] quit
[PE-B] mpls ldp
[PE-B-mpls-ldp] quit

[PE-B-GigabitEthernet1/0/0] mpls ldp
[PE-B-GigabitEthernet1/0/0] quit
# Enable PIM-SM and MPLS on GigabitEthernet 2/0/0 in the public network.

# Configure an IP address for Loopback1 interface and enable PIM-SM.

# Configure an IP address for Loopback2 interface and enable PIM-SM.

# Configure static routes, BGP, and OSPF.

[PE-B] ip route-static 1.1.1.3 32 gigabitethernet 2/0/0 192.168.1.2
[PE-B] bgp 100
[PE-B-bgp] import-route ospf 1
[PE-B-bgp] group peb-pea internal
[PE-B-bgp] peer peb-pea route-policy map2 export
[PE-B-bgp] peer peb-pea label-route-capability
[PE-B-bgp] peer peb-pea connect-interface LoopBack1
[PE-B-bgp] peer 1.1.1.1 group peb-pea
[PE-B-bgp] group peb-pec external
[PE-B-bgp] peer peb-pec as-number 200
[PE-B-bgp] peer peb-pec ebgp-max-hop 255
[PE-B-bgp] peer peb-pec route-policy map1 export
[PE-B-bgp] peer peb-pec label-route-capability
[PE-B-bgp] peer peb-pec connect-interface Loopback1
[PE-B-bgp] peer 1.1.1.3 group peb-pec
[PE-B] ospf 1

[PE-B-ospf-1] area 0.0.0.0

[PE-B-ospf-1-area-0.0.0.0] quit
[PE-B-ospf-1] quit
# Configure a routing policy.

[PE-B] route-policy map1 permit node 10
[PE-B-route-policy] apply mpls-label
[PE-B-route-policy] quit
[PE-B] route-policy map2 permit node 10
[PE-B-route-policy] if-match mpls-label
[PE-B-route-policy] apply mpls-label
# Configure a C-BSR and a C-RP.

[PE-B] pim
[PE-B-pim] c-bsr loopback 2
[PE-B-pim] c-rp loopback 2
[PE-B-pim] quit
# Configure the BSR boundary.

[PE-B-GigabitEthernet2/0/0] pim bsr-boundary
# Set up the MSDP peer relationship.

[PE-B] msdp
[PE-B-msdp] encap-data-enable
[PE-B-msdp] peer 1.1.1.3 connect-interface Loopback1
Step 3 Configure PE-C.

# Configure an ID for PE-C, enable multicast in the public network, configure an ID for an
[PE-C] router id 1.1.1.3
[PE-C] multicast routing-enable
[PE-C] mpls lsr-id 1.1.1.3
[PE-C] mpls
[PE-C-mpls] quit
[PE-C] mpls ldp
[PE-C-mpls-ldp] quit
# Enable MPLS LDP and PIM-SM on GigabitEthernet 1/0/0 in the public network.
[PE-C-GigabitEthernet1/0/0] mpls ldp
[PE-C-GigabitEthernet1/0/0] quit
# Enable PIM-SM and MPLS on GigabitEthernet 2/0/0 in the public network.

# Configure an IP address for Loopback1 and enable PIM-SM.


# Configure an IP address for Loopback2 and enable PIM-SM.

# Configure static route, BGP, and OSPF.

[PE-C] ip route-static 1.1.1.2 32 gigabitethernet 2/0/0 192.168.1.1
[PE-C] bgp 200
[PE-C-bgp] import-route ospf 1
[PE-C-bgp] group pec-ped internal
[PE-C-bgp] peer pec-ped route-policy map2 export
[PE-C-bgp] peer pec-ped label-route-capability
[PE-C-bgp] peer pec-ped connect-interface LoopBack1
[PE-C-bgp] peer 1.1.1.4 group pec-ped
[PE-C-bgp] group pec-peb external
[PE-C-bgp] peer pec-peb as-number 100
[PE-C-bgp] peer pec-peb ebgp-max-hop 255
[PE-C-bgp] peer pec-peb route-policy map1 export
[PE-C-bgp] peer pec-peb label-route-capability
[PE-C-bgp] peer pec-peb connect-interface Loopback1
[PE-C-bgp] peer 1.1.1.2 group pec-peb
[PE-C] ospf 1
[PE-C-ospf-1] area 0.0.0.0
[PE-C-ospf-1-area-0.0.0.0] quit
[PE-C-ospf-1] quit
# Configure a routing policy.

[PE-C] route-policy map1 permit node 10
[PE-C-route-policy] apply mpls-label
[PE-C-route-policy] quit
[PE-C] route-policy map2 permit node 10
[PE-C-route-policy] if-match mpls-label
[PE-C-route-policy] apply mpls-label
# Configure a C-BSR and a C-RP.

[PE-C] pim
[PE-C-pim] c-bsr loopback 2
[PE-C-pim] c-rp loopback 2
[PE-C-pim] quit
# Configure the PIM BSR boundary.

[PE-C-GigabitEthernet2/0/0] pim bsr-boundary
# Set up the MSDP peer relationship.

[PE-C] msdp
[PE-C-msdp] encap-data-enable
[PE-C-msdp] peer 1.1.1.2 connect-interface Loopback1
[PE-C-msdp] quit
Step 4 Configure PE-D.

# Configure an ID for PE-D, enable multicast in the public network, configure an ID for an
[PE-D] router id 1.1.1.4
[PE-D] multicast routing-enable

[PE-D] mpls lsr-id 1.1.1.4

[PE-D] mpls
[PE-D-mpls] quit
[PE-D] mpls ldp
[PE-D-mpls-ldp] quit
[PE-A] quit
<PE-A> system-view
[PE-D] ip vpn-instance RED
[PE-D-vpn-instance-RED] route-distinguisher 100:1
[PE-D-vpn-instance-RED] vpn-target 100:1 export-extcommunity
[PE-D-vpn-instance-RED] vpn-target 100:1 import-extcommunity
[PE-D-vpn-instance-RED] multicast routing-enable
[PE-D-vpn-instance-RED] multicast-domain share-group 239.1.1.1 binding mtunnel 0
[PE-D-vpn-instance-RED] multicast-domain switch-group-pool 225.1.1.1 28
[PE-D-vpn-instance-RED] quit
[PE-D] ip vpn-instance BLUE
[PE-D-vpn-instance-BLUE] route-distinguisher 200:1
[PE-D-vpn-instance-BLUE] vpn-target 200:1 export-extcommunity
[PE-D-vpn-instance-BLUE] vpn-target 200:1 import-extcommunity
[PE-D-vpn-instance-BLUE] multicast routing-enable
[PE-D-vpn-instance-BLUE] multicast-domain share-group 239.4.4.4 binding mtunnel 1
[PE-D-vpn-instance-BLUE] multicast-domain switch-group-pool 225.4.4.1 28
[PE-D-vpn-instance-BLUE] quit

[PE-D] interface gigabitethernet 1/0/0
[PE-D-GigabitEthernet1/0/0] ip address 10.10.2.2 24
[PE-D-GigabitEthernet1/0/0] pim sm
[PE-D-GigabitEthernet1/0/0] mpls
[PE-D-GigabitEthernet1/0/0] mpls ldp

[PE-D-GigabitEthernet2/0/0] ip binding vpn-instance RED
# Bind GigabitEthernet 3/0/0 to VPN BLUE instance and enable PIM-SM.

[PE-D-GigabitEthernet3/0/0] ip binding vpn-instance BLUE
# Assign an IP address for Loopback1 interface and enable PIM-SM.

[PE-D] interface loopback 1
[PE-D-LoopBack1] ip address 1.1.1.4 32
[PE-D-LoopBack1] pim sm
[PE-D-LoopBack1] quit

# Configure an IP address (the same as that of Loopback1 interface) for MTI0 and enable PIM-
SM.
[PE-D] interface MTunnel 0
[PE-D-MTunnel1] ip address 1.1.1.4 32
[PE-D-MTunnel1] pim sm
SM.
[PE-D] interface MTunnel 1
[PE-D-MTunnel1] ip address 1.1.1.4 32
[PE-D-MTunnel1] pim sm
# Configure BGP and OSPF.

[PE-D] bgp 200
[PE-D-bgp] group ped-pec internal
[PE-D-bgp] peer ped-pec label-route-capability
[PE-D-bgp] peer ped-pec connect-interface LoopBack1
[PE-D-bgp] peer 1.1.1.3 group ped-pec
[PE-D-bgp] group ped-pea external
[PE-D-bgp] peer ped-pea as-number 100
[PE-D-bgp] peer ped-pea ebgp-max-hop 255
[PE-D-bgp] peer 1.1.1.1 group ped-pea
[PE-D-bgp] peer 1.1.1.1 connect-interface Loopback1
[PE-D-bgp] ipv4-family vpn-instance RED
[PE-D-bgp-RED] import-route ospf 2
[PE-D-bgp-RED] import-route direct
[PE-D-bgp-RED] quit
[PE-D-bgp] ipv4-family vpn-instance BLUE
[PE-D-bgp-BLUE] import-route ospf 3
[PE-D-bgp-BLUE] import-route direct
[PE-D-bgp-BLUE] quit
[PE-D-bgp] ipv4-family vpnv4
[PE-D-bgp-af-vpnv4] peer 1.1.1.1 enable
[PE-D-bgp-af-vpnv4] quit
[PE-D] ospf 1
[PE-D-ospf-1] area 0.0.0.0
[PE-D-ospf-1-area-0.0.0.0] network 1.1.1.4 0.0.0.0
[PE-D-ospf-1-area-0.0.0.0] quit
[PE-D-ospf-1] quit
[PE-D] ospf 2 vpn-instance RED
[PE-D-ospf-2] import-route bgp
[PE-D] ospf 3 vpn-instance BLUE
[PE-D-ospf-3] import-route bgp
Step 5 Configure CE-A.

# Enable multicast.
[CE-A] multicast routing-enable
# Enable PIM-SM on GigabitEthernet 1/0/0.

[CE-A] interface gigabitethernet 1/0/0
[CE-A-GigabitEthernet1/0/0] ip address 10.111.5.1 24
[CE-A-GigabitEthernet1/0/0] pim sm

[CE-A] interface gigabitethernet 2/0/0

[CE-A-GigabitEthernet2/0/0] ip address 10.111.1.2 24

[CE-A-GigabitEthernet2/0/0] pim sm
# Configure OSPF.
[CE-A] ospf 1
[CE-A-ospf-1] area 0.0.0.0
[CE-A-ospf-1-area-0.0.0.0] network 10.111.0.0 0.0.255.255
[CE-A-ospf-1-area-0.0.0.0] quit
Step 6 Configure CE-B.

# Enable multicast.
[CE-B] multicast routing-enable

[CE-B] interface gigabitethernet 1/0/0
[CE-B-GigabitEthernet1/0/0] ip address 10.111.6.1 24
[CE-B-GigabitEthernet1/0/0] pim sm

[CE-B] interface gigabitethernet 2/0/0
[CE-B-GigabitEthernet2/0/0] ip address 10.111.2.2 24
[CE-B-GigabitEthernet2/0/0] pim sm
# Assign an IP address for Loopback0 and enable PIM-SM.

[CE-B] interface loopback 0
[CE-B-LoopBack0] ip address 2.2.2.2 32
[CE-B-LoopBack0] pim sm
[CE-B-LoopBack0] quit
# Configure Loopback0 interface as the BSR and RP of VPN BLUE instance.

[CE-B] pim
[CE-B-pim] c-bsr Loopback 0
[CE-B-pim] c-rp Loopback 0
# Configure OSPF.
[CE-B] ospf 1
[CE-B-ospf-1] area 0.0.0.0
[CE-B-ospf-1-area-0.0.0.0] network 10.111.0.0 0.0.255.255
[CE-B-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[CE-B-ospf-1-area-0.0.0.0] quit
Step 7 Configure CE-C.

# Enable multicast.
[CE-C] multicast routing-enable
# Enable PIM-SM and IGMP on GigabitEthernet 1/0/0.

[CE-C] interface gigabitethernet 1/0/0
[CE-C-GigabitEthernet1/0/0] ip address 10.111.7.1 24
[CE-C-GigabitEthernet1/0/0] pim sm
[CE-C-GigabitEthernet1/0/0] igmp enable

[CE-C] interface gigabitethernet 2/0/0
[CE-C-GigabitEthernet2/0/0] ip address 10.111.3.2 24
[CE-C-GigabitEthernet2/0/0] pim sm
# Assign an IP address for Loopback0 interfance, and enable PIM-SM.

[CE-C] interface loopback0

[CE-C-LoopBack0] ip address 3.3.3.3 32
[CE-C-LoopBack0] pim sm
[CE-C-LoopBack0] quit
# Set Loopback0 interface as the BSR and RP of VPN RED instance.

[CE-C] pim
[CE-C-pim] c-bsr Loopback0
[CE-C-pim] c-rp Loopback0
# Configure OSPF.
[CE-C] ospf 1
[CE-C-ospf-1] area 0.0.0.0
[CE-C-ospf-1-area-0.0.0.0] network 10.111.0.0 0.0.255.255
[CE-C-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0
[CE-C-ospf-1-area-0.0.0.0] quit
Step 8 Configure CE-D.

# Enable multicast.
[CE-D] multicast routing-enable

[CE-D] interface gigabitethernet 1/0/0
[CE-D-GigabitEthernet1/0/0] ip address 10.111.8.1 24
[CE-D-GigabitEthernet1/0/0] pim sm
[CE-D-GigabitEthernet1/0/0] igmp enable

[CE-D] interface gigabitethernet 2/0/0
[CE-D-GigabitEthernet2/0/0] ip address 10.111.4.2 24
[CE-D-GigabitEthernet2/0/0] pim sm
# Configure OSPF.
[CE-D] ospf 1
[CE-D-ospf-1] area 0.0.0.0
[CE-D-ospf-1-area-0.0.0.0] network 10.111.0.0 0.0.255.255
[CE-D-ospf-1-area-0.0.0.0] quit

After the preceding configurations are complete, PC1 can receive multicast information from
Source1, and PC2 can receive multicast information from Source2.
----End
Configuration Files
l Configuration file of PE-A
#
sysname PE-A
#
#
#
ip vpn-instance RED
multicast-domain share-group 239.1.1.1 binding mtunnel 0


#
#
mpls lsr-id 1.1.1.1
mpls
#
mpls ldp
#
undo shutdown
ip address 10.10.1.1 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 10.111.1.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.111.2.1 255.255.255.0
pim sm
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
pim sm
#
interface MTunnel0
ip address 1.1.1.1 255.255.255.255
pim sm
#
interface MTunnel1
ip address 1.1.1.1 255.255.255.255
pim sm
#
bgp 100
group pea-peb internal
peer pea-peb connect-interface LoopBack1
peer 1.1.1.2 group pea-peb
group pea-ped external
peer pea-ped as-number 200
peer pea-ped ebgp-max-hop 255
peer 1.1.1.4 group pea-ped
#
ipv4-family unicast
peer pea-peb enable
peer pea-peb label-route-capability
peer 1.1.1.2 enable
peer 1.1.1.2 group pea-peb
peer pea-ped enable
peer 1.1.1.4 enable
peer 1.1.1.4 group pea-ped
#

import-route direct
import-route ospf 2
#
import-route direct
import-route ospf 3
#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.4 enable
#
ospf 1
area 0.0.0.0
network 10.10.0.0 0.0.255.255
network 1.1.1.1 0.0.0.0
#
ospf 2 vpn-instance RED
import-route bgp
area 0.0.0.0
network 10.111.0.0 0.0.255.255
#
ospf 3 vpn-instance BLUE
import-route bgp
area 0.0.0.0
network 10.111.0.0 0.0.255.255
#
return
l Configuration file of PE-B
#
sysname PE-B
#
#
mpls lsr-id 1.1.1.2
mpls
#
mpls ldp
#
undo shutdown
ip address 10.10.1.2 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 192.168.1.1 255.255.255.0
pim sm
pim bsr-boundary
mpls
#
interface LoopBack1
ip address 1.1.1.2 255.255.255.255
pim sm
#
interface LoopBack2
ip address 11.11.11.11 255.255.255.255
pim sm
#
ip route-static 1.1.1.3 255.255.255.255 GigabitEthernet2/0/0 192.168.1.2
#
bgp 100
group peb-pea internal
peer peb-pea connect-interface LoopBack1
peer 1.1.1.1 group peb-pea
group peb-pec external
peer peb-pec as-number 200
peer peb-pec ebgp-max-hop 255

peer peb-pec connect-interface LoopBack1

peer 1.1.1.3 group peb-pec
#
ipv4-family unicast
import-route ospf 1
peer peb-pea enable
peer peb-pea route-policy map2 export
peer peb-pea next-hop-local
peer peb-pea label-route-capability
peer 1.1.1.1 enable
peer 1.1.1.1 group peb-pea
peer peb-pec enable
peer peb-pec route-policy map1 export
peer peb-pec label-route-capability
peer 1.1.1.3 enable
peer 1.1.1.3 group peb-pec
#
ospf 1
area 0.0.0.0
network 10.10.0.0 0.0.255.255
network 11.11.11.11 0.0.0.0
network 1.1.1.2 0.0.0.0
#
route-policy map1 permit node 10
apply mpls-label
if-match mpls-label
apply mpls-label
#
pim
c-bsr LoopBack2
c-rp LoopBack2
#
msdp
encap-data-enable
#
return
l Configuration file of PE-C
#
sysname PE-C
#
#
mpls lsr-id 1.1.1.3
mpls
#
mpls ldp
#
undo shutdown
ip address 10.10.2.1 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 192.168.1.2 255.255.255.0
pim sm
pim bsr-boundary
mpls
#
interface LoopBack1
ip address 1.1.1.3 255.255.255.255
pim sm
#
interface LoopBack2

ip address 22.22.22.22 255.255.255.255

pim sm
#
ip route-static 1.1.1.2 255.255.255.255 GigabitEthernet2/0/0 192.168.1.1
#
bgp 200
group pec-ped internal
peer pec-ped connect-interface LoopBack1
peer 1.1.1.4 group pec-ped
group pec-peb external
peer pec-peb as-number 100
peer pec-peb ebgp-max-hop 255
peer pec-peb connect-interface LoopBack1
peer 1.1.1.2 group pec-peb
#
ipv4-family unicast
import-route ospf 1
peer pec-ped eanble
peer pec-ped route-policy map2 export
peer pec-ped next-hop-local
peer pec-ped label-route-capability
peer 1.1.1.4 enable
peer 1.1.1.4 group pec-ped
peer pec-peb enable
peer pec-peb route-policy map1 export
peer pec-peb label-route-capability
peer 1.1.1.2 enable
peer 1.1.1.2 group pec-peb
#
ospf 1
area 0.0.0.0
network 10.10.0.0 0.0.255.255
network 22.22.22.22 0.0.0.0
network 1.1.1.3 0.0.0.0
#
apply mpls-label
if-match mpls-label
apply mpls-label
#
pim
c-bsr LoopBack2
c-rp LoopBack2
#
msdp
encap-data-enable
#
return
l Configuration file of PE-D
#
sysname PE-D
#
#
#
ip vpn-instance RED
#


#
mpls lsr-id 1.1.1.4
mpls
#
mpls ldp
#
undo shutdown
ip address 10.10.2.2 255.255.255.0
pim sm
mpls
mpls ldp
#
undo shutdown
ip address 10.111.3.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.111.4.1 255.255.255.0
pim sm
#
interface LoopBack1
ip address 1.1.1.4 255.255.255.255
pim sm
#
interface MTunnel0
ip address 1.1.1.4 255.255.255.255
pim sm
#
interface MTunnel1
ip address 1.1.1.4 255.255.255.255
pim sm
#
bgp 200
group ped-pec internal
peer ped-pec connect-interface LoopBack1
peer 1.1.1.3 group ped-pec
group ped-pea external
peer ped-pea as-number 100
peer ped-pea ebgp-max-ho/p 255
peer ped-pea connect-interface LoopBack1
peer 1.1.1.1 group ped-pea
#
ipv4-family unicast
import-route direct
import-route ospf 1
peer ped-pec eanble
peer ped-pec route-policy map2 export
peer ped-pec next-hop-local
peer ped-pec label-route-capability
peer 1.1.1.3 enable
peer 1.1.1.3 group ped-pec
peer ped-pea enable
peer ped-pea route-policy map1 export
peer ped-pea label-route-capability
peer 1.1.1.1 enable
peer 1.1.1.1 group ped-pea

#
ipv4-family vpnv4
policy vpn-target
peer 1.1.1.1 enable
#
import-route direct
import-route ospf 2
#
import-route direct
import-route ospf 3
#
ospf 1
area 0.0.0.0
network 10.10.0.0 0.0.255.255
network 1.1.1.4 0.0.0.0
#
ospf 2 vpn-instance RED
import-route bgp
area 0.0.0.0
network 10.111.0.0 0.0.255.255
#
ospf 3 vpn-instance BLUE
import-route bgp
area 0.0.0.0
network 10.111.0.0 0.0.255.255
#
return
l Configuration file of CE-A
#
sysname CE-A
#
#
undo shutdown
ip address 10.111.5.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.111.1.2 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.111.0.0 0.0.255.255
#
return
l Configuration file of CE-B
#
sysname CE-B
#
#
undo shutdown
ip address 10.111.6.1 255.255.255.0
pim sm
#
undo shutdown
ip address 10.111.2.2 255.255.255.0
pim sm
#
interface Loopback0
ip address 2.2.2.2 255.255.255.255

pim sm
#
ospf 1
area 0.0.0.0
network 10.111.0.0 0.0.255.255
network 2.2.2.2 0.0.0.0
#
pim
c-bsr Loopback0
c-rp Loopback0
#
return
l Configuration file of CE-C

#
sysname CE-C
#
#
undo shutdown
ip address 10.111.7.1 255.255.255.0
pim sm
igmp enable
#
undo shutdown
ip address 10.111.3.2 255.255.255.0
pim sm
#
interface Loopback0
ip address 3.3.3.3 255.255.255.255
pim sm
#
ospf 1
area 0.0.0.0
network 10.111.0.0 0.0.255.255
network 3.3.3.3 0.0.0.0
#
pim
c-bsr Loopback0
c-rp Loopback0
#
return
l Configuration file of CE-D

#
sysname CE-D
#
#
undo shutdown
ip address 10.111.8.1 255.255.255.0
pim sm
igmp enable
#
undo shutdown
ip address 10.111.4.2 255.255.255.0
pim sm
#
ospf 1
area 0.0.0.0
network 10.111.0.0 0.0.255.255
#
return

Configuration Guide - IP Multicast 9 IPv4 Multicast CAC Configuration
9 IPv4 Multicast CAC Configuration
About This Chapter
This chapter describes the configurations and maintenance of IPv4 multicast CAC, and provides
configuration examples.
9.1 IPv4 Multicast CAC Introduction
This section describes the multicast CAC features supported by the NE80E/40E and the basic
principle of multicast CAC.
9.2 Configuring Multicast CAC
This section describes how to configure multicast CAC.
9.3 Maintaining Multicast CAC
This section describes how to monitor the running status of multicast CAC.
This section provides a configuration example of Multicast CAC.

9 IPv4 Multicast CAC Configuration Configuration Guide - IP Multicast
9.1 IPv4 Multicast CAC Introduction

This section describes the multicast CAC features supported by the NE80E/40E and the basic
principle of multicast CAC.
9.1.1 Multicast CAC Overview

9.1.2 Multicast CAC Features Supported by the NE80E/40E
9.1.1 Multicast CAC Overview
Internet Protocol Television (IPTV) carries real-time video services. With the development of
IPTV, operators propose higher requirements for the utilization of IPTV network resources and
management of video services. In the current multicast technologies, there are only two ways
to control multicast networks. One is to limit the number of multicast forwarding entries, and
the other is to limit the number of outgoing interfaces of a single entry. The two ways cannot
meet the requirements of operators.
Multicast Call Admission Control (CAC) refers to configuring a policy on the first-hop router
connected to the multicast source, intermediate routers, and the last-hop router connected to
receivers to limit the number of multicast entries that the routers can create. After multicast CAC
is configured, operators can control the range of IPTV services and the number of users accessing
IP core networks.
The design principles of multicast CAC are as follows:
l Control the range of multicast groups by limiting the number of PIM routing entries. This
prevents the introduction of large-volume multicast traffic beyond the forwarding
capability of routers.
l Plan multicast networks by reserving bandwidth for channels or interfaces. When
bandwidth resources of a channel or an interface are insufficient, no multicast group is
added to the channel or the interface. This ensures the quality of services.
l Control the range of multicast groups that users can join by limiting the number of IGMP
group memberships.
Related Terms and Concepts

The following concepts are involved in multicast CAC:
l Channel: It refers to a set of IPTV services of the same type defined by operators, such as
the Standard Definition Television (SDTV) channel and the High Definition Television
(HDTV) channel. Based on these channels, operators allocate bandwidth resources and
make charging policies. A channel can have multiple multicast groups.
l Multicast group: A multicast address represents a multicast group.
l IGMP only-link interface: It refers to the last-hop router interface that is connected to hosts
and meets one of the following requirements:
– The interface is enabled with IGMP rather than PIM-SM or PIM-DM.
– The interface is configured with static multicast groups but is not enabled with IGMP,
PIM-SM or PIM-DM.

IGMP only-link interfaces do not support multicast CAC. That is, to enable multicast CAC
on a router, ensure that the router does not have any IGMP only-link interface.
l Join status of an interface: It indicates that an interface is added to the outgoing interface
list of a PIM routing entry.
In the MAN shown in Figure 9-1, the IGMP Join message sent by the user is forwarded by Layer
2 devices such as the Digital Subscriber Line Access Multiplexer (DSLAM) and switch to the
Ultimate Provider Edge (UPE). The IP core network of operators may be connected to multiple
Internet Content Providers (ICPs). Each ICP uses multicast groups allocated in advance to carry
multicast data. The multicast data enters the MAN through the Network PE (NPE), and finally
reaches users.
To prevent multicast data entering networks from exceeding the processing capability of
routers or bandwidth limit of the access network, operators can adopt the following methods
when deploying IPTV services:
l Limiting the number of IGMP group memberships on the UPE globally, or based on an
instance or an interface.
l Limiting bandwidth and the number of groups in a channel or an interface on the UPE or
NPE.
Figure 9-1 Typical Applications of Multicast CAC
NPE
UPE VOD Server

IP/MPLS Backbone ICP1
NPE VOD Server

ICP2
Usage Guideline
Multicast CAC limits subsequent multicast entries only. For example, after the limit value is
configured, routers do not delete the existing entries or corresponding interfaces, even if the
number of existing entries, the number of interfaces in the Join state, or the occupied bandwidth
exceeds the limit value.
Here, the number of entries does not refer to the actual number of PIM or IGMP entries, but is
counted in the following ways:

l For groups in the Any Source Multicast (ASM) group address range: For the same G, all
(*, G) entries or (S, G) entries are counted as one entry.
l For groups in the Specified Source Multicast (SSM) group address range: An (S, G) entry
is counted as one entry.
The function of limiting the number of IGMP group memberships is applicable to PIM-DM and
PIM-SM networks, and the other multicast CAC functions are applicable to IPv4 PIM-SM
networks only.
9.1.2 Multicast CAC Features Supported by the NE80E/40E

NOTE
The function range of multicast CAC is as follows:
l Multicast CAC does not limit static (S, G) entries the PIM entries of the Join messages received from
private networks.
l The functions of multicast CAC are applicable to IPv4 PIM-SM networks.
Limiting the Number of PIM Routing Entries

Multicast CAC limits the number of PIM routing entries in the following ways:
l Limiting the number of PIM routing entries based on a single instance: The total number
of PIM routing entries related to an instance cannot exceed the limit value. When the total
number reaches the limit value, no PIM entry can be created.
l Limiting the number of PIM routing entries based on a channel: A channel can contain
multiple multicast groups. The total number of PIM routing entries related to a specified
channel cannot exceed the limit value. When the total number reaches the limit value, no
PIM entry can be created.
Limiting Bandwidth
When defining the range of multicast groups for a channel, you can specify the reserved
bandwidth for each multicast group. When a new group is added to the channel, a PIM entry is
created or an interface is added to the outgoing interface lists of an existing entry only when the
following conditions are met:
l The remaining bandwidth of the interface is equal to or greater than the reserved bandwidth
of the group.
l The remaining bandwidth of the channel is equal to or greater than the reserved bandwidth
of the group.
Limiting the Number of Outgoing Interface Lists to Which an Interface Is Added

Multicast CAC can limit the number of PIM outgoing interface lists to which an interface is
added. That is, the number of multicast groups that an interface can serve is limited. When the
number of outgoing interface lists to which an interface is added exceeds the limit value, no PIM
routing entry can be created or no interface can be added to the outgoing interface list.
9.2 Configuring Multicast CAC

This section describes how to configure multicast CAC.


9.2.2 Configuring a Channel
9.2.3 (Optional) Configuring the Maximum Number of PIM Routing Entries in a Single Instance
9.2.4 (Optional) Configuring the Maximum Number of PIM Routing Entries in a Channel
9.2.5 (Optional) Configuring the Maximum Number of Outgoing Interface Lists to Which an
Interface Is Added and Bandwidth Limit
To limit IPTV ICPs and the number of users accessing IP core networks, you can configure
multicast CAC.
Multicast CAC can be enabled on the first-hop router connected to the multicast source,
intermediate routers, and the last-hop router connected to users. You can make the CAC policy
as required.
The CAC solutions adopted by PIM-SM networks of different models and different scales are
as follows:
l SSM model: It is recommended to set up a channel on the DR at the source side and the
last-hop router connected to users, limit the number of PIM routing entries and bandwidth
related to the channel, and limit the number of IGMP group memberships on the last-hop
router.
l ASM model: It is recommended to set up a channel on the DR at the source side, the RP
and the last-hop router connected to users, limit the number of PIM routing entries and
bandwidth related to the channel, and limit the number of IGMP group memberships on
the last-hop router.
l Inter-domain PIM: It is recommended to set up a channel on the RP in each domain and
the last-hop router connected to users, limit the number of PIM routing entries and
bandwidth related to the channel, and limit the number of IGMP group memberships on
the last-hop router.
NOTE
The functions of multicast CAC functions are applicable to IPv4 PIM-SM networks.
Before configuring basic Multicast CAC functions, complete the following tasks:
l Configuring a PIM-SM network, and enabling PIM-SM and IGMP (or configuring static
multicast groups) on the last-hop router interface connected to users
NOTE
Ensure that no IGMP only-link interfaces or PIM-DM interfaces exist in the instance to be configured with
multicast CAC.
Data Preparation
To configure basic multicast CAC functions, you need the following data.

No. Data
1 Name of the channel
2 Maximum number of PIM routing entries in a single instance
3 Maximum number of PIM routing entries in a channel
4 Maximum number of outgoing interface lists to which an interface is added to and

bandwidth limit
9.2.2 Configuring a Channel
Context
Do as follows on the DR at the source side, the RP, and the last hop router connected to users:
Procedure
Step 1 Run:
system-view

Step 2 Run:
multicast-channel [ vpn-instance vpn-instance-name ]
Multicast CAC is enabled and the multicast-channel view is displayed.

Step 3 Run:
channel channel-name type { asm | ssm }
A channel is configured and the channel view is displayed.

Step 4 Run:
group group-address mask { group-mask-length | group-mask } [ source source-
address mask { source-mask-length | source-mask } ] [ per-bandwidth traffic-rate ]
The range of multicast groups and the range of multicast sources are configured.
per-bandwidth specifies the reserved bandwidth for each multicast group. To create PIM
routing entries of a multicast group, ensure that the remaining bandwidth is equal to or greater
than the reserved bandwidth of the multicast group; otherwise, no PIM entry can be created or
no interface can be added to the outgoing interface list.
----End
9.2.3 (Optional) Configuring the Maximum Number of PIM

Routing Entries in a Single Instance
Context
Do as follows on the DR at the source side, the RP, and the last-hop router connected to users:

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
multicast limit limit [ threshold threshold ]
The maximum number of PIM routing entries that can be created in the current instance is set.
If threshold is set, the system generates alarms in logs when the number of PIM entries exceeds
the value of threshold.
----End
9.2.4 (Optional) Configuring the Maximum Number of PIM

Routing Entries in a Channel
Context
Do as follows on the DR at the source side, the RP, and the last-hop router connected to users:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
channel channel-name
The channel view is displayed.
Step 4 Run:
multicast limit limit [ threshold threshold ]
The maximum number of PIM routing entries that can be created in the channel is set.
If threshold is set, the system generates alarms in logs when the number of PIM entries exceeds
the value of threshold.
----End

9.2.5 (Optional) Configuring the Maximum Number of Outgoing

Interface Lists to Which an Interface Is Added and Bandwidth Limit
Context
This configuration involves two cases, and you can perform the configuration as required. Do
as follows on the DR at the source side, the RP, and the last-hop router connected to users:
Procedure
l All multicast groups
1. Run:
system-view

2. Run:
The PIM interface view is displayed.

3. Run:
multicast limit out { max-entry limit | bandwidth traffic-rate } *
The maximum number of outgoing interface lists to which the interface is added and
bandwidth limit are set for all multicast groups.
l Single channel
1. Run:
system-view

2. Run:
The PIM interface view is displayed.

3. Run:
multicast limit channel channel-name out { max-entry limit | bandwidth
traffic-rate } *
The maximum number of outgoing interface lists to which the interface is added and
bandwidth limit are set for the channel.
----End

Procedure
l Run the display multicast [ vpn-instance vpn-instance-name ] limit channel channel-
name out-interface { interface-type interface-number | all } command to check CAC
statistics based on a channel on an interface.
l Run the display multicast [ vpn-instance vpn-instance-name ] limit out-interface
{ interface-type interface-number | all } command to check CAC statistics of all multicast
groups on an interface.

l Run the display multicast [ vpn-instance vpn-instance-name ] limit [ channel channel-

name ] global command to check the statistics of global entries based on a channel or all
multicast groups.
----End
9.3 Maintaining Multicast CAC

This section describes how to monitor the running status of multicast CAC.
9.3.1 Monitoring the Running Status of Multicast CAC
9.3.1 Monitoring the Running Status of Multicast CAC
Context
status of Multicast CAC.
Procedure
l Run the display multicast [ vpn-instance vpn-instance-name ] limit channel channel-
name out-interface { interface-type interface-number | all } command in any view to check
the outgoing interface lists to which an interface is added and bandwidth limit based on a
channel.
l Run the display multicast [ vpn-instance vpn-instance-name ] limit out-interface
{ interface-type interface-number | all } command in any view to check all multicast entries
and bandwidth limit on an interface.
l Run the display multicast [ vpn-instance vpn-instance-name ] limit [ channel channel-
name ] global command in any view to check the statistics of global entries of a channel
or all multicast groups.
l Run the display pim [ vpn-instance vpn-instance-name ] routing-table channel channel-
name command to check information about (*, G) entries or (S, G) entries of a specified
channel.
l Run the following commands to check information about IGMP multicast groups.
– display igmp igmp [ vpn-instance vpn-instance-name | all-instance ] group [ group-
address | interface interface-type interface-number ] * [ static ] [ verbose ]
– display igmp [ vpn-instance vpn-instance-name | all-instance ] group [ group-
address | interface interface-type interface-number ] ssm-mapping [ verbose ]
----End

This section provides a configuration example of Multicast CAC.
9.4.1 Example for Configuring Multicast CAC
9.4.1 Example for Configuring Multicast CAC

In the MAN shown in Figure 9-2, Router D is the first-hop router connected to the multicast
source, that is, the DR at the source side; Router A, Router B, and Router C are the last-hop
routers connected to users; Router E functions as the RP. The network of the carrier is planned
as follows:
l Set up SDTV and HDTV channels and work out different prices for the two channels.
l Configure different reserved bandwidth for the two types of channels to ensure the quality
of services (QoS).
l Configure users to receive multicast data from Source 1 and Source 2 only.
l Limit the number of multicast groups that a user joins on routers connected to users.
Figure 9-2 Networking diagram of configuring multicast CAC
RouterA
GE2/0/0
POS1/0/0
Receiver
PIM-SM HostA
RouterD RouterE POS3/0/0

POS1/0/0 POS2/0/0 GE2/0/0
Source1
POS4/0/0 POS1/0/0
GE2/0/0 POS1/0/0 RouterB
Receiver
POS1/0/0 HostB
GE2/0/0
Source2
RouterC
GE 2/0/0 192.168.1.1/24 GE 2/0/0 192.168.3.1/24
Router B POS 1/0/0 10.1.2.1/24 Router E POS 1/0/0 10.1.3.2/24
GE 2/0/0 192.168.2.1/24 POS 2/0/0 10.1.2.2/24
Router C POS 1/0/0 10.1.3.1/24 POS 3/0/0 10.1.1.2/24
GE 2/0/0 192.168.2.2/24 POS 4/0/0 10.1.4.1/24
1. Configure an IP address for each interface on the routers and a unicast routing protocol.

2. Enable multicast on routers, PIM-SM on each interface, and IGMP on the interface
connected to hosts.
3. Set up two channels on Router D, and configure multicast groups and reserved bandwidth
for the channel.
4. Limit the number of PIM routing entries and the number of IGMP group memberships on
Router A, Router B, and Router C.
Data Preparation
l IP address of each interface
l Multicast group address
l Reserved bandwidth of each multicast group
l The maximum number of PIM entries and the maximum number of IGMP group
memberships
Procedure
Step 1 Configure an IP address for each interface on the routers and configure a unicast routing protocol.
NOTE
In this configuration example, only the commands related to the multicast CAC configuration are
mentioned.
Step 2 Enable multicast on each router, PIM-SM on each interface, and IGMP and PIM-SM on the
# Enable multicast on each router, PIM-SM on each interface, and IGMP on interfaces through
which Router A, Router B, and Router C are connected to leaf networks.
[RouterA-GigabitEthernet2/0/0] igmp version 3
[RouterA] interface pos1/0/0
[RouterB-GigabitEthernet2/0/0] pim sm
[RouterB-GigabitEthernet2/0/0] igmp version 3
[RouterB] interface pos1/0/0
<RouterC> system-view
[RouterC] interface gigabitethernet2/0/0
[RouterC-GigabitEthernet2/0/0] igmp version 3
[RouterC] interface pos1/0/0

<RouterD> system-view
[RouterD] interface gigabitethernet2/0/0
[RouterD-GigabitEthernet2/0/0] pim sm
[RouterD-GigabitEthernet2/0/0] quit
[RouterD] interface pos1/0/0
<RouterE> system-view
[RouterE] interface pos1/0/0
[RouterE-Pos1/0/0] pim sm
[RouterE-Pos1/0/0] quit
Step 3 Configure multicast CAC to limit the number of entries and bandwidth on Router D.
# Set up the SDTV channel that contains multicast groups in the 225.0.0.0/24 range. The reserved
bandwidth of each multicast group is 3000 kbit/s, and a maximum of 10 PIM entries can be
created for the channel.
[RouterD] multicast-channel
[RouterD-multicast-channel] channel SDTV type asm
[RouterD-multicast-channel-SDTV] group 225.0.0.0 mask 255.255.255.0 per-bandwidth
3000
[RouterD-multicast-channel-SDTV] multicast limit 10
[RouterD-multicast-channel-SDTV] quit
# Set up the HDTV channel of the SSM model. The multicast groups contained in the channel
is in the 232.0.0.0/24 range, and the source address range is 192.168.3.0/24. The reserved
bandwidth of each multicast group is 4000 kbit/s. A maximum number of 12 PIM entries can
be created for the channel.
[RouterD-multicast-channel] channel HDTV type ssm
[RouterD-multicast-channel-HDTV] group 232.0.0.0 mask 255.255.255.0 source
192.168.3.0 mask 255.255.255.0 per-bandwidth 4000
[RouterD-multicast-channel-HDTV] multicast limit 12
[RouterD-multicast-channel-HDTV] quit
# Set the maximum number of PIM entries to 20 in the public network instance.
[RouterD-multicast-channel] multicast limit 20
[RouterD-multicast-channel] quit
# Set the number of PIM entries and bandwidth limit on POS 1/0/0.
[RouterD] interface pos1/0/0
[RouterD-Pos1/0/0] multicast limit out max-entry 12 bandwidth 160000
[RouterD-Pos1/0/0] multicast limit channel HDTV out max-entry 10 bandwidth 40000
[RouterD-Pos1/0/0] multicast limit channel SDTV out max-entry 10 bandwidth 20000
Step 4 Configure a channel and limit the number of PIM entries and bandwidth on the last-hop router
connected to users.
Set up SDTV and HDTV channels on Router A. The group range and source range are the same
as those on Router D. A maximum of 20 PIM entries can be created in the public network
instance. Configure the router not to create multicast entries for groups out of the channel.
Configurations of Router B and Router C are similar to those of Router A, and are not mentioned
here.

[RouterA] multicast-channel
[RouterA-multicast-channel] multicast limit 20
[RouterA-multicast-channel] channel SDTV type asm
[RouterA-multicast-channel-SDTV] group 225.0.0.0 mask 255.255.255.0 per-bandwidth
3000
[RouterA-multicast-channel-SDTV] multicast limit 10
[RouterA-multicast-channel-SDTV] quit
[RouterA-multicast-channel] channel HDTV type ssm
[RouterA-multicast-channel-HDTV] group 232.0.0.0 mask 255.255.255.0 source
192.168.3.0 mask 255.255.255.0 per-bandwidth 4000
[RouterA-multicast-channel-HDTV] multicast limit 12
[RouterA-multicast-channel-HDTV] quit
[RouterA-multicast-channel] unspecified-channel deny
Step 5 Limit the number of IGMP group memberships on the last-hop router connected to users.
# Configure the maximum number of IGMP group memberships to 30 on Router A.

[RouterA] igmp global limit 30
# Configure the maximum number of IGMP group memberships to 20 in the public network
instance.
[RouterA] igmp
[RouterA-igmp] limit 20
[RouterA-igmp] quit
# Configure the maximum number of IGMP group relationships to 15 on GE 2/0/0.

[RouterA-GigabitEthernet2/0/0] igmp limit 15
mentioned here.
Run the display multicast limit global command, and you can view the global configuration
of multicast CAC and related statistics on a router. Take Router A as an example.
<RouterA> display multicast limit global
Multicast limitation information of instance: public net
Global entries : 20
Global threshold : -
Global Used-Entries : 2
# Run the display multicast limit channel global command, and you can view the global CAC
configuration and related statistics of a specified channel on a router. Take Router A as an
example.
<RouterA> display multicast limit channel SDTV global
-----------------------------------------------------------------------
Channel Program Mode Entries threshold Used-Entries
-----------------------------------------------------------------------
SDTV ASM 10 - 0
-----------------------------------------------------------------------
# Run the display multicast limit out-interface command, and you can view the total number
of entries that takes this interface as the outgoing interface. Take Router A as an example.
<RouterD> display multicast limit out-interface all
All Channel:
-------------------------------------------------------------------------------
Interface Entries Bandwidth(kbit/s) Used-Entries Used-Bandwidth(kbit/s)
-------------------------------------------------------------------------------

Pos1/0/0 12 160000 0 0
-------------------------------------------------------------------------------
----End
Configuration Files
#
sysname RouterD
#
#
multicast-channel
multicast limit 20
channel HDTV type ssm
multicast limit 12
group 232.0.0.0 mask 255.255.255.0 source 192.168.3.0 mask 255.255.255.0 per-
bandwidth 4000
channel SDTV type asm
multicast limit 10
group 225.0.0.0 mask 255.255.255.0 per-bandwidth 3000
#
undo shutdown
ip address 192.168.3.1 255.255.255.0
pim sm
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.4.2 255.255.255.0
pim sm
multicast limit out max-entry 12 bandwidth 160000
multicast limit channel HDTV out max-entry 10 bandwidth 40000
multicast limit channel SDTV out max-entry 10 bandwidth 20000
#
interface NULL0
#
ospf 100
area 0.0.0.0
network 192.168.3.0 0.0.0.255
network 10.1.4.0 0.0.0.255
#
return

#
sysname RouterE
#
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.3.2 255.255.255.0
pim sm
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
ip address 10.1.2.2 255.255.255.0
pim sm
#
interface Pos3/0/0
undo shutdown
link-protocol ppp
ip address 10.1.1.2 255.255.255.0

pim sm
#
interface Pos4/0/0
undo shutdown
link-protocol ppp
ip address 10.1.4.1 255.255.255.0
pim sm
#
interface NULL0
#
ospf 100
area 0.0.0.0
network 10.1.4.0 0.0.0.255
network 10.1.3.0 0.0.0.255
network 10.1.2.0 0.0.0.255
network 10.1.1.0 0.0.0.255
#
return
#
sysname RouterA
#
#
#
multicast-channel
multicast limit 20
multicast limit 12
group 232.0.0.0 mask 255.255.255.0 source 192.168.3.0
mask 255.255.255.0 per-bandwidth 4000
multicast limit 10
#
undo shutdown
ip address 192.168.1.1 255.255.255.0
pim sm
igmp enable
igmp version 3
igmp limit 15
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.1.1 255.255.255.0
pim sm
#
interface NULL0
#
ospf 100
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 10.1.1.0 0.0.0.255
#
igmp
limit 20
#
return
#
sysname RouterB
#
#

#
multicast-channel
multicast limit 20
multicast limit 12
multicast limit 10
#
undo shutdown
ip address 192.168.2.1 255.255.255.0
pim sm
igmp enable
igmp version 3
igmp limit 15
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.2.1 255.255.255.0
pim sm
#
interface NULL0
#
ospf 100
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
igmp
limit 20
#
return
#
sysname RouterC
#
#
#
multicast-channel
multicast limit 20
multicast limit 12
multicast limit 10
#
undo shutdown
ip address 192.168.2.2 255.255.255.0
pim sm
igmp enable
igmp version 3
igmp limit 15
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
ip address 10.1.3.1 255.255.255.0

pim sm
#
interface NULL0
#
ospf 100
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 10.1.3.0 0.0.0.255
#
igmp
limit 20
#
return

Configuration Guide - IP Multicast 10 IPv4 Multicast Routing Management
10 IPv4 Multicast Routing Management
About This Chapter
This chapter describes the basic principles of IPv4 multicast forwarding, configuration methods
of forwarding policies, and maintenance of commands, and provides configuration examples.
10.1 IPv4 Multicast Routing Management Introduction
This section describes the principle and basic concepts of multicast routing, multicast
forwarding, and RPF.
10.2 Configuring a Static Multicast Route
This section describes how to configure static multicast routes.
10.3 Configuring the Multicast Routing Policy
This section describes how to configure a multicast routing policy.
10.4 Configuring the Multicast Forwarding Scope
This section describes how to configure the multicast forwarding range.
10.5 Configuring Control Parameters of the Multicast Forwarding Table
This section describes how to configure control parameters of the multicast forwarding table.
10.6 Maintaining the Multicast Policy
This section describes how to test multicast routing, check RPF paths and multicast paths, clear
multicast routing and forwarding entries, and monitor the status of multicast routing and
forwarding.
This section provides several configuration examples of IPv4 multicast routing management.
10.8 Troubleshooting of Static Multicast Routes
This section describes how to locate and clear the faults of a static multicast route.

10 IPv4 Multicast Routing Management Configuration Guide - IP Multicast

This section describes the principle and basic concepts of multicast routing, multicast
forwarding, and RPF.
10.1.1 Overview of IPv4 Multicast Routing Management

10.1.2 IPv4 Multicast Routing Management Features Supported by the NE80E/40E

In the NE80E/40E, multicast routing and forwarding consist of the following three aspects:
l Each multicast routing protocol has its routing table, such as PIM routing table.
l The multicast routing information of each multicast routing protocol forms a general
The multicast routing table resides in the multicast route management module. It is
composed of (S, G) entries. (S, G) indicates that S sends multicast data to G. If the multicast
route management module supports multiple multicast protocols, the routing table contains
multicast routes that are generated by the protocols. The routing entries are copied to the
forwarding table.
l The multicast forwarding table controls the forwarding of multicast data packets.
The multicast forwarding table guides the forwarding of multicast data packets. It remains
consistent with the multicast routing table.
To ensure that multicast data is transmitted along the correct path, multicast routing protocols
use the Reverse Path Forwarding (RPF) to create multicast routing entries.
The system performs RPF check based on the following types of routes:
l Unicast routes
The unicast routing table collects the shortest paths to each destination.
l MBGP routes
The MBGP routing table provides multicast routing information.
l MIGP routes
The MIGP routing table provides the routing information calculated based on physical
interfaces of the TE tunnel to guide the forwarding of multicast packets.
l Static multicast routes
The static multicast routing table provides RPF routing information that is specified through
static configuration.

10.1.2 IPv4 Multicast Routing Management Features Supported by

the NE80E/40E
Static Multicast Route

The static multicast route is an important factor of RPF check. By configuring the static multicast
route, users can specify the RPF interface and RPF neighbor for a specific source of packets on
the current router.
The static multicast route cannot be used to forward data. It only affects RPF check, and is also
called static RPF route.
The static multicast route is valid only on the configured multicast routers, and cannot be
advertised or imported to other routers.
Multicast Routing Policy

If multiple unicast routes with the same cost exist when a multicast router selects an upstream
interface, users can use one of following methods to configure the router to select the RPF route:
l By default, the router chooses the route with the largest next-hop address.
l According to the longest match, the router selects the route longest matching the address
of the source of the packet.
l Load splitting is configured among equal-cost routes. Performing load splitting of multicast
traffic according to different policies can optimize network traffic transmission in the
scenario where multiple multicast data flows exist.
There are five multicast load splitting policies: stable-preferred, balance-preferred, source
address-based, group address-based, and source and group addresses-based. The five load
splitting policies are mutually exclusive. In addition, you can configure load splitting
weights on the interfaces to achieve unbalanced multicast load splitting.
Controlling the Multicast Forwarding Range

In a network, the multicast information to which each multicast group corresponds is transmitted
in a certain range. Users can define the multicast forwarding range by using the following
methods:
l Configuring a multicast forwarding boundary on an interface to form a closed multicast

forwarding area.
l Setting the forwarding TTL threshold on an interface to limit the distance to which a packet
is forwarded.
Controlling the Capacity of a Multicast Forwarding Table

When planning a specific network according to network services, the Internet Service Provider
(ISP) can perform the following configurations:
l Limiting the number of entries in the multicast forwarding table

Each router maintains a forwarding entry for each received multicast packet. Too many
multicast forwarding entries, however, use up the memory of a router. Users can define the
maximum number of entries in the multicast forwarding table of a router. Limiting the

number of entries according to the actual networking and service performance can avoid
router faults caused by excessive entries.
l Limiting the number of downstream nodes of each forwarding entry
Router replicate a multicast packet for each downstream node, and then send it out. Each
downstream node forms a branch of an MDT. The number of downstream nodes determines
the maximum scale of the MDT and the multicast service range. Users can define the
number of downstream nodes of a single forwarding entry. Limiting the number of
downstream nodes according to the actual networking and service performance can reduce
the processing pressure of a router and control the multicast service range.
Testing Multicast Routing

When a fault occurs on a multicast network, you can run the ping multicast and mtrace
commands to test the connectivity of the network.
NOTE
The mtrace command can be used to trace multicast path on a specified multicast VPN network to maintain
multicast VPN services and locate faults on the network.
The ping multicast command is used to check whether a group is reachable and to implement
the following functions:
l Pinging a reserved group address

This is used to check whether a member of a group exists in the directly connected network
segment, and is not exclusive for multicast networks. You can ping devices that use
multicast addresses.
l Pinging a common group address
This function is applied as follows:
– To generate multicast traffic and trigger the creation of multicast routing entries: Based
on multicast routing information, you can check whether a protocol runs normally,
determine whether the network can carry multicast services, or test the forwarding
performance.
– To check the members of related groups in the network: Based on the ICMP-Echo-
Reply messages received from destination hosts, the router on which the command is
used checks the members of the groups in the network, and calculates response time
and the TTL from the router to members. You can run the command repeatedly in a
certain interval to calculate the network delay and route flapping.
The mtrace command can be used to trace the following paths and output the hop information:
l RPF path from a source to a querier

l Multicast path from a source to a querier
l RPF path from a source to a destination host
l Multicast path from a source to a destination host
NOTE
You can ping multicast addresses by using the Network Quality Analysis (NQA) test instances or related
commands. For detailed configurations of NQA test instances, refer to the HUAWEI NetEngine80E/40E
Router Configuration Guide - System Management NQA Configuration.

10.2 Configuring a Static Multicast Route

This section describes how to configure static multicast routes.
10.2.2 Configuring a Static Multicast Route
Static multicast route has the following functions:
l Changing RPF route

If the topology of multicast is the same as that of unicast, the transmission path of multicast
data is the same as that of unicast data. Users can change the RPF route by configuring a
static multicast route. Thus a transmission path of the multicast data, which is different
from the transmission path of unicast data, is established.
l Connecting RPF route
In the network segment where unicast routes are blocked, when multicast static routes are
not configured, packets cannot be forwarded because there is no RPF route. You can
configure multicast static routes. Therefore, the system can generate RPF routes, complete
RPF check, create routing entries, and guide the forwarding of packets.
Before configuring a static multicast route, complete the following tasks:

l Configuring basic multicast functions
Data Preparation
To configure a static multicast route, you need the following data.
No. Data
1 Multicast source address, mask or mask length
2 Unicast routing protocol
3 Filtering policy and its preference
10.2.2 Configuring a Static Multicast Route

Context
CAUTION
When configuring a static multicast route, configure the outgoing interface through the command
if the next hop is in the point-to-point format. If the next hop is not in the point-to-point format,
you must use the next hop.
Do as follows on the multicast router:
Procedure
Step 1 Run:
system-view

Step 2 Run:
ip rpf-route-static [ vpn-instance vpn-instance-name ] source-address { mask | mask-
length } [ protocol [ process-id ] ] [ route-policy policy-name ] { rpf-nbr |
interface-type interface-number } [ preference preference ] [ order order-num ]
A static multicast route is configured.

l source-address { mask |mask-length }: specifies a source address and mask.
l protocol [ process-id ]: specifies that the matching route must be present in the specified
unicast routing protocol. protocol specifies a unicast routing protocol. process-id specifies
the ID of a process.
l route-policy policy-name: specifies the matching rule of the static multicast route.
l rpf-nbr: specifies the next hop address that acts as the IP address of the RPF neighbor.
l interface-type interface-number: specifies the type and the number of the outgoing interface.
The outgoing interface acts as the RPF interface.
l preference preference: specifies the preference of the route. The greater the preference value
is, the lower the preference is.
l order order-num: specifies the configuration order of routes on the same network segment.
----End

Procedure
l Run the display multicast routing-table [ vpn-instance vpn-instance-name ] static
[ config ] [ source-address { mask | mask-length } ] command to check the static multicast
routing table.
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] rpf-info
source-address [ group-address ] [ rpt | spt ] command to check RPF routing information
of a specified multicast source.
----End

10.3 Configuring the Multicast Routing Policy

This section describes how to configure a multicast routing policy.
10.3.2 Configuring Longest Match of Multicast Route
10.3.3 Configuring Multicast Load Splitting
10.3.4 Configuring a Multicast Load Splitting Weight
If multiple equal-cost unicast routes exist when a multicast router select an upstream interface,
you can configure the router to the RPF router by using one of the following methods:
l By default, the router chooses the route with the largest next-hop address.
l According to the longest match rules, you can configure the router to select the route with
the destination address that longest matches the address of the source of the packet.
l You can configure load splitting among these routers. Performing load splitting of multicast
traffic according to different policies can optimize network traffic when multiple multicast
data flows exist.
Before configuring the multicast routing policy, complete the following tasks:

Data Preparation
To configure the multicast routing policy, you need the following data.
No. Data
1 Multicast load splitting policy
2 Multicast load splitting weight on the interface
10.3.2 Configuring Longest Match of Multicast Route

Context
CAUTION
Configurations related to VPN instances are applicable only to the PE router. When configuring
the longest match of multicast routes for a VPN instance on a PE, perform the configuration in
the VPN instance. In other cases, the longest match is configured in the public network instance.
By default, routes are selected in the order of routing entries.

Procedure
l Public network instance
1. Run:
system-view

2. Run:
multicast longest-match
Routes are selected according to the longest match.

l VPN instance
1. Run:
system-view

2. Run:

3. Run:
multicast longest-match
routers are selected according to the longest match.

----End
10.3.3 Configuring Multicast Load Splitting
Context
CAUTION
load splitting among multicast routes for a VPN instance on a PE, perform the configuration in
the VPN instance. In other cases, load balancing among multicast routes is configured in the
public network instance.

The multicast load splitting function extends multicast routing rules, which does not fully depend
on the RPF check. If multiple equal-cost optimal routes exist over the network, they all can be
used for multicast data forwarding and multicast traffic is load split among multiple equal-cost
routes.
By default, load splitting is not performed.
Do as follows on the multicast router router:
Procedure
1. Run:
system-view

2. Run:
multicast load-splitting { balance-preferred | stable-preferred | source
| group | source-group }
Multicast load balancing is configured. The parameters of the command are explained
as follows:
– balance-preferred: indicates balance-preferred load splitting. This policy is
applicable to the scenario where hosts frequently join or leave the groups, which
requires automatic load adjustment.
If balance-preferred is specified, the router automatically adjusts and balances
the entries on the equal-cost routes when equal-cost routes are added or deleted,
IPv4 multicast routing entries are deleted, or IPv4 load splitting weights on the
interfaces are changed.
– stable-preferred: indicates stable-preferred load splitting. This policy is
applicable to the stable multicast networking.
If stable-preferred is specified, the router automatically adjusts and balances the
entries when equal-cost routes are added or deleted; however, when IPv4 multicast
routing entries are deleted or load splitting weights on the interfaces are changed,
the router does not automatically adjust the entries on the equal-cost routes.
– group: indicates group address-based load splitting. This policy is applicable to
the scenario of one source to multiple groups.
– source: indicates source address-based load splitting. This policy is applicable to
the scenario of one group to multiple sources.
– source-group: indicates source and group addresses-based load splitting. This
policy is applicable to the scenario of multiple sources to multiple groups.
NOTE
It is recommended to adopt a fixed IPv4 multicast load splitting policy based on the actual
networking. It is recommended to use the balance-preferred or stable-preferred policy.
balance-preferred or stable-preferred cannot be configured on the interface enabled with
PIM-DM.
l VPN instance
1. Run:
system-view

2. Run:

3. Run:
multicast load-splitting { balance-preferred | stable-preferred | source
| group | source-group }
Multicast load splitting is configured.
----End
10.3.4 Configuring a Multicast Load Splitting Weight
Context
When stable-preferred or balance-preferred load splitting is configured, because the forwarding
capabilities of equal-cost routes are different from the actual load bearing situation on the equal-
cost routes, balanced load splitting cannot meet network requirements in some scenarios. In such
a case, you can configure a load splitting weight on an interface to achieve unbalanced multicast
load splitting.
Do as follows on the router enabled with multicast:
Procedure
Step 1 Run:
system-view
Step 2 Run:
By default, the multicast load splitting weight of an interface is 1.
The greater the multicast load splitting weight of an interface, the more multicast routing entries
with this interface being the upstream interface. When the multicast load splitting weight on an
interface is 0, it indicates that the routes with this interface being the upstream interface do not
take part in load splitting.
Step 3 Run:
multicast load-splitting weight weight-value
The multicast load splitting weight is set on the interface.
----End
Procedure
l Run the following commands to check the multicast routing table.

– display multicast { vpn-instance vpn-instance-name | all-instance } routing-table

[ group-address [ mask { group-mask | group-mask-length } ] | source-address
[ mask { source-mask | source-mask-length } ] | incoming-interface { interface-type
interface-number | register } | outgoing-interface { include | exclude | match }
{ interface-type interface-number | register | none } ] * [ outgoing-interface-
number [ number ] ]
– display multicast routing-table [ group-address [ mask { group-mask | group-mask-
length } ] | source-address [ mask { source-mask | source-mask-length } ] | incoming-
instance-name | register | none } ] * [ outgoing-interface-number [ number ] ]
l Run the following command to check the source-specific RPF route.
display multicast [ vpn-instance vpn-instance-name | all-instance ] rpf-info source-
address [ group-address ] [ rpt | spt ]
----End
10.4 Configuring the Multicast Forwarding Scope

This section describes how to configure the multicast forwarding range.
10.4.1 Establish the Configuration Task
10.4.2 Configuring the Multicast Forwarding Boundary
10.4.3 Configuring the TTL Threshold of Multicast Forwarding
10.4.1 Establish the Configuration Task
Multicast information to which each multicast group corresponds is forwarded in a certain scope
in network. Uers can define the multicast forwarding scope by using the following methods:
l Configuring the multicast forwarding boundary to form a close multicast forwarding area.
The interface configured with a forwarding boundary of a multicast group cannot send or
receive packets of the multicast group.
l Configuring the TTL threshold of multicast forwarding on an interface to limit the
forwarding distance of multicast packets. The interface forwards only the packet whose
TTL value is not smaller than the threshold. If the TTL value of a packet is smaller than
the threshold, the packet is discarded.
In the task of configuring multicast forwarding range, Configuring Multicast Forwarding

Boundary and Configuring TTL Threshold of Multicast Forwarding are parallel. Users can select
the configuration as required.
Before configuring the multicast forwarding scope, complete the following tasks:


Data Preparation
To configure the multicast forwarding scope, you need the following data.
No. Data
1 Group address, mask, and mask length of the multicast forwarding boundary
2 TTL threshold for multicast forwarding
10.4.2 Configuring the Multicast Forwarding Boundary
Context
By default, no multicast forwarding boundary is configured on the interface.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
multicast boundary group-address { mask | mask-length }
The multicast forwarding boundary is configured.
----End
10.4.3 Configuring the TTL Threshold of Multicast Forwarding
Context
By default, the forwarding TTL threshold is 1.
Procedure
Step 1 Run:
system-view

Step 2 Run:
Step 3 Run:
multicast minimum-ttl ttl-value
The multicast forwarding TTL threshold is configured.
----End
Procedure
l Run the following commands to check the multicast routing table.
number [ number ] ]
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] boundary
[ group-address [ mask | mask-length ] ] [ interface interface-type interface-number ]
command to check information about the multicast boundary of an interface.
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] minimum-
ttl [ interface-type interface-number ] command to check the forwarding TTL threshold on
an interface.
----End
10.5 Configuring Control Parameters of the Multicast

Forwarding Table
10.5.2 Setting the Maximum Number of Entries in Multicast Forwarding Table
10.5.3 Setting the Maximum Number of Downstream Nodes of Multicast Forwarding Entry

To plan a network according to the services, the ISP needs to perform the following configuration
policies:
l Limiting the number of entries in the multicast forwarding table

Each router maintains a routing entry for each received multicast packet. Too many entries,
however, may exhaust the memory of the router. In this case, you can define the maximum
number of multicast routing entries. Limiting the number of the entries can avoid faults in
the router.
l Limiting the number of downstream nodes of a single entry
Routers copy a multicast packet for each downstream node, and the downstream node sends
the copy out. Each downstream node forms a branch of the multicast distribution tree. The
number of the downstream nodes determines the maximum scale of the multicast
distribution tree and the multicast service scope. Users can define the number of the
downstream nodes of a single forwarding entry. Limiting the number of downstream nodes
according to the actual networking and the services can reduce the pressure of routers and
control the multicast service scope.
Before configuring control parameters of the multicast forwarding table, complete the following
tasks:

Data Preparation
To configure control parameters of the multicast forwarding table, you need the following data.
No. Data
1 Multicast source address, group address, and mask or mask length
2 Matching policy, router sequence, and route preference of the multicast routes
3 Maximum number of entries in the multicast forwarding table
4 Maximum number of downstream nodes of each entry in the multicast forwarding

table
10.5.2 Setting the Maximum Number of Entries in Multicast

Forwarding Table

Context
CAUTION
the maximum number of entries in the forwarding table for a VPN instance on a PE, perform
the configuration in the VPN instance. In other cases, the maximum number of entries in the
forwarding table is configured in the public network instance.
By default, the maximum number supported by the system is used.
Procedure
1. Run:
system-view

2. Run:
multicast forwarding-table route-limit limit
The maximum number of entries in the multicast forwarding table is configured.
By default, the maximum value is adopted.

l VPN instance
1. Run:
system-view

2. Run:

3. Run:
multicast forwarding-table route-limit limit
The maximum number of entries in the multicast forwarding table is configured.
By default, the maximum value is adopted.
----End
10.5.3 Setting the Maximum Number of Downstream Nodes of

Multicast Forwarding Entry

Context
CAUTION
This configuration becomes valid only after the reset multicast forwarding-table command is
used. Multicast services are interrupted after you run the reset multicast forwarding-table
command. So, confirm the action before you use the command.
Configurations related to the VPN instance are applicable only to the PE router. When
configuring the maximum number of downstream nodes for a forwarding entry in a VPN instance
on a PE, perform the configuration in the VPN instance. In other cases, the maximum number
of entries in the forwarding table is configured in the public network instance.
Procedure
1. Run:
system-view

2. Run:
multicast forwarding-table downstream-limit limit
The maximum number of downstream nodes of a forwarding entry in the multicast

forwarding table is configured.
The maximum number is valid when it is smaller than the default value.

l VPN instance
1. Run:
system-view

2. Run:

3. Run:
multicast forwarding-table downstream-limit limit
The maximum number of downstream nodes of a forwarding entry in the multicast

forwarding table is configured.
----End


Procedure
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-
table [ group-address [ mask { group-mask | group-mask-length } ] | source-address
interface-number | register } | outgoing-interface { { include | exclude | match }
{ interface-type interface-number | register |none } } | statistics | slot slot-number ] *
command to check the multicast forwarding table.
----End
10.6 Maintaining the Multicast Policy

This section describes how to test multicast routing, check RPF paths and multicast paths, clear
multicast routing and forwarding entries, and monitor the status of multicast routing and
forwarding.
10.6.1 Testing Multicast Routing
10.6.2 Check RPF Paths and Multicast Paths
10.6.3 Clearing Multicast Routing and Forwarding Entries
10.6.4 Monitoring the Status of Multicast Routing and Forwarding
10.6.1 Testing Multicast Routing

Context
When data transmission is abnormal, you can ping related multicast addresses to check the
multicast routing.
Procedure
l Run the ping multicast -i interface-type interface-number [ -c count | -m time | -p
pattern | -q | -s packetsize | -t timeout | -tos tos-value | -v ] * host command in any view to
ping a reserved group address.
l Run the ping multicast [ -c count | -h ttl-value | -m time | -p pattern | -q | -s packetsize | -
t timeout | -tos tos-value | -v ] * host command in any view to ping a common group address.
----End

10.6.2 Check RPF Paths and Multicast Paths
Context
NOTE
When checking the RPF path or multicast path from a source to a destination host, run the mtrace query-
policy [ acl-number ] command on the router connected to hosts to configure the filtering policy for queriers.
The ACL defines the address scope of reliable queriers. Based on the ACL, the last-hop router refuses the
IGMP-Tracert-Query messages sent by illegal queriers. Note the following when using this command:
l This command is valid only for the last-hop router, and the querier is not the last-hop router.
l This command is used to filter only the IGMP-Tracert-Query message encapsulated in a unicast IP
packet.
l This command is not applicable to the trace that is initiated by the local querier.
When a fault occurs during data transmission, you can run the following commands in any view
to check RPF paths and multicast paths.
Procedure
l Run the mtrace [ -ur resp-dest | -l [ stat-times ] [ -st stat-int ] | -m max-ttl | -q nqueries | -
ts ttl | -tr ttl | -v | -w timeout | -vpn-instance vpn-name ] * source source-address command
in any view to check the RPF path from a source to a querier.
l Run the mtrace -g group [ { -mr | -ur resp-dest } | -l [ stat-times ] [ -st stat-int ] | -m max-
ttl | -q nqueries | -ts ttl | -tr ttl | -v | -w timeout | -vpn-instance vpn-name ] * source source-
address command in any view to check the multicast path from a source to a querier.
l Run the mtrace [ -gw last-hop-router | -d ] -r receiver [ -ur resp-dest | -a source-ip-
address | -l [ stat-times ] [ -st stat-int ] | -m max-ttl | -q nqueries | -ts ttl | -tr ttl | -v | -w
timeout | -vpn-instance vpn-name ] * source source-address command in any view to
check the RPF path from a source to a destination host.
l Run the mtrace [ -gw last-hop-router | -b | -d ] -r receiver -g group [ { -mr | -ur resp-
dest } | -a source-ip-address | -l [ stat-times ] [ -st stat-int ] | -m max-ttl | -q nqueries | -ts
ttl | -tr ttl | -v | -w timeout | -vpn-instance vpn-name ] * source source-address command
in any view to check the multicast path from a source to a destination host.
----End
10.6.3 Clearing Multicast Routing and Forwarding Entries
Context
CAUTION
The reset command clears the entries in the multicast forwarding table or the multicast routing
table. It may result in abnormal multicast information forwarding. After the routing entries in
the multicast routing table are cleared, the corresponding forwarding entries corresponding to
the public network instance or VPN instance are also cleared. So, confirm the action before you
use the command.

Procedure
l Run the following commands to clear the forwarding entries in the multicast forwarding
table.
– reset multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table
all
– reset multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table
{ group-address [ mask { group-mask | group-mask-length } ] | source-address
interface-number | register } } *
l Run the following commands to clear the routing entries in the multicast routing table.
– reset multicast [ vpn-instance vpn-instance-name | all-instance ] routing-table all
– reset multicast [ vpn-instance vpn-instance-name | all-instance ] routing-table
{ group-address [ mask { group-mask | group-mask-length } ] | source-address
interface-number | register } } *
----End
10.6.4 Monitoring the Status of Multicast Routing and Forwarding
Context
In routine maintenance, you can run the following commands in any view to check the status of
multicast routing and forwarding.
Procedure
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] boundary
[ group-address [ mask | mask-length ] ] [ interface interface-type interface-number ]
command in any view to check the multicast boundary configured on an interface.
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-
table [ group-address [ mask { group-mask | group-mask-length } ] | source-address
interface-number | register } | outgoing-interface { { include | exclude | match }
{ interface-type interface-number | register | none } } | statistics | slot slot-number ] *
command in any view to check the multicast forwarding table.
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] minimum-
ttl [ interface-type interface-number ] command in any view to check the minimum TTL
value when a multicast data packet is forwarded by an interface.
l Run the following commands in any view to check the multicast routing table.
number [ number ] ]


l Run the display multicast routing-table [ vpn-instance vpn-instance-name ] static
[ config ] [ source-address { mask-length | mask } ] command in any view to check the
static multicast routing table.
l Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] rpf-info
source-address [ group-address ] [ rpt | spt ] command in any view to check the RPF
routing information.
----End

This section provides several configuration examples of IPv4 multicast routing management.
10.7.1 Example for Changing Static Multicast Routes to RPF Routes

10.7.2 Example for Connecting the RPF Route Through a Static Multicast Route
10.7.3 Example for Implementing Multicast Through a Static Multicast Routed Tunnel
10.7.4 Example for Configuring Multicast Load Splitting
In a PIM-SM network where multicast services are stable, it is required to configure the stable-
preferred multicast load splitting policy so that multicast traffic can be distributed to multiple
equal-cost routes for transmission. In addition, it is required to configure multicast load splitting
weights for different interfaces to achieve unbalanced multicast load splitting.
10.7.1 Example for Changing Static Multicast Routes to RPF Routes
As shown in Figure 10-1, the network runs PIM-DM, all routers support multicast, and the
receiver can receive information from the multicast source. Router A, Router B, and Router C
run OSPF. It is required to configure a static multicast route to distinguish the multicast path
from the source to the receiver from the unicast path from the source to the receiver.

Figure 10-1 Networking diagram for changing static multicast routes to RPF routes
RouterC
POS3/0/0 POS2/0/0
12.1.1.2/24 13.1.1.2/24
POS3/0/0 PIM-DM POS2/0/0

12.1.1.1/24 13.1.1.1/24
RouterA RouterB
POS1/0/0 POS1/0/0
GE2/0/0 9.1.1.1/24 9.1.1.2/24 GE3/0/0
8.1.1.1/24 7.1.1.1/24
8.1.1.2/24 7.1.1.2/24
Source Receiver
multicast static route
1. Configure an IP address and enable OSPF on each interface.
2. Enable multicast on each router, PIM-DM on each interface, and IGMP on the interface
connected to hosts.
3. Configure static multicast RPF routes on Router B, and specify Router C as the RPF
neighbor to the source.
Data Preparation
l IP address of the source
l POS 2/0/0 through which Router B connects to Router C
Procedure
# As shown in Figure 10-1, configure IP addresses and masks on the interfaces of each router.
OSPF is run on Router A, Router B, and Router C, and the three routers are able to update routes

among them through the unicast routing protocol. The configuration procedure is not mentioned
here.
Step 2 Enable multicast on each router and PIM-DM on each interface
# Enable multicast on each router, PIM-DM on each interface, and IGMP on the interface
connected to hosts. The configurations on other routers are similar to that of Router B, and are
not mentioned here.
[RouterB-Pos1/0/0] pim dm
[RouterB-GigabitEthernet3/0/0] pim dm
# Run the display multicast rpf-info command on Router B to view the RPF information of
the source. You can find that the RPF route is a unicast route, and the RPF neighbor is Router
A. The display is as follows:
<RouterB]> display multicast rpf-info 8.1.1.2
RPF information about source 8.1.1.2:
RPF interface: Pos1/0/0, RPF neighbor: 9.1.1.1
Referenced route/mask: 8.1.1.0/24
Referenced route type: unicast
Route selection rule: preference-preferred
Load splitting rule: disable
Step 3 Configure a static multicast route

# Configure a static multicast RPF route on Router B and configure Router C as the RPF neighbor
to the source.
[RouterB] ip rpf-route-static 8.1.1.0 255.255.255.0 13.1.1.2

# Run the display multicast rpf-info command on Router B to view the RPF information of
the source. The RPF route and the RPF neighbor are updated according to the static multicast
route. The display of RPF is as follows:
<RouterB> display multicast rpf-info 8.1.1.2
RPF interface: Pos2/0/0, RPF neighbor: 13.1.1.2
Referenced route type: mstatic
----End
Configuration Files
Configuration file of Router B
#
sysname RouterB

#
#
interface pos1/0/0
undo shutdown
link-protocol ppp
ip address 9.1.1.2 255.255.255.0
pim dm
#
interface pos2/0/0
undo shutdown
link-protocol ppp
ip address 13.1.1.1 255.255.255.0
pim dm
#
undo shutdown
ip address 7.1.1.1 255.255.255.0
pim dm
igmp enable
#
ospf 1
area 0.0.0.0
network 7.1.1.0 0.0.0.255
network 9.1.1.0 0.0.0.255
network 13.1.1.0 0.0.0.255
#
ip rpf-route-static 8.1.1.0 255.255.255.0 13.1.1.2
#
return
10.7.2 Example for Connecting the RPF Route Through a Static

Multicast Route
As shown in Figure 10-2, the network runs PIM-DM, all routers support multicast, and receiver
can receive information from the multicast source Source1. Router B and Router C run OSPF.
There is no unicast route between Router A and Router B. It is required to use a multicast static
route to enable the receiver to receive information sent by Source2.

Figure 10-2 Networking diagram for connecting the RPF route through static multicast routes
PIM-DM
OSPF
Source1
10.1.3.2/24
GE2/0/0
10.1.3.1/24 GE3/0/0 GE3/0/0 RouterA
10.1.4.1/24 10.1.4.2/24
RouterB
GE1/0/0
GE1/0/0 GE1/0/0
10.1.2.2/24
10.1.2.1/24 10.1.5.1/24
RouterC
GE2/0/0 Source2
10.1.1.1/24 10.1.5.2/24
Receiver
multicast static route
1. Configure an IP address and OSPF on each interface.
2. Enable multicast on each router, PIM-DM on each interface, and IGMP on the interface
connected to hosts.
3. Configure a static multicast RPF route between Router B and Router C.
Data Preparation
l IP address of Source 2.
l RPF interface through which Router B connects to Source2 is GE 3/0/0, and the RPF
neighbor is Router A.
l RPF interface through which Router C connects to Source2 is GE 1/0/0, and the RPF
neighbor is Router B.

Procedure
# As shown in Figure 10-2, configure IP addresses and masks of the interfaces on each router.
Router B and Router C belong to the same OSPF area, and the two routers are able to update
routes among them through the unicast routing protocol. The configuration procedure is not
mentioned here.
Step 2 Enable multicast on each router and PIM-DM on each interface
# Enable multicast on each router, enable PIM-DM on each interface, and enable IGMP on the
[RouterC-GigabitEthernet1/0/0] pim dm
[RouterC-GigabitEthernet2/0/0] pim dm
# Source 1 (10.1.3.2/24) and Source 2 (10.1.5.2/24) send multicast data to the multicast group
G (225.1.1.1). The receiver joins G. The receiver can then receive the multicast data sent by
Source 1, but cannot receive the multicast data sent by Source 2.
# Run the display multicast rpf-info 10.1.5.2 command on Router B and Router C. If there is
no display, it indicates that Router B and Router C have no RPF route to Source 2.
Step 3 Configure a static multicast route
# Configure a static multicast RPF route on Router B and configure Router A as the RPF neighbor
to Source 2.
# Configure a static multicast RPF route on Router C, and configure Router B as the RPF
neighbor to Source 2.
[RouterC] ip rpf-route-static 10.1.5.0 255.255.255.0 10.1.2.2

# Run the display multicast rpf-info 10.1.5.2 command on Router B and Router C to view the
RPF information of Source 2. The display information of RPF is as follows:
<RouterB> display multicast rpf-info 10.1.5.2

RPF information about: 10.1.5.2

RPF interface: GigabitEthernet3/0/0, RPF neighbor: 10.1.4.2
Route selecting rule: preference-preferred
<RouterC> display multicast rpf-info 10.1.5.2
RPF interface: GigabitEthernet1/0/0, RPF neighbor: 10.1.2.2
# Run the display pim routing-table command to view the routing table. Router C has the
multicast entry of Source 2. The receiver can receive the multicast data from Source 2.
(*, 225.1.1.1)
UpTime: 03:54:19
Upstream interface: NULL
(10.1.3.2, 225.1.1.1)
UpTime: 00:00:44
(10.1.5.2, 225.1.1.1)
UpTime: 00:00:44
----End
Configuration Files
#
sysname RouterA
#
#
undo shutdown
ip address 10.1.5.1 255.255.255.0
pim dm
#

undo shutdown
ip address 10.1.4.2 255.255.255.0
pim dm
#
ospf 1
area 0.0.0.0
network 10.1.5.0 0.0.0.255
network 10.1.4.0 0.0.0.255
#
return

#
sysname RouterB
#
#
undo shutdown
ip address 10.1.2.2 255.255.255.0
pim dm
#
undo shutdown
ip address 10.1.3.1 255.255.255.0
pim dm
#
undo shutdown
ip address 10.1.4.1 255.255.255.0
pim dm
#
ospf 1
area 0.0.0.0
network 10.1.2.0 0.0.0.255
network 10.1.3.0 0.0.0.255
#
ip rpf-route-static 10.1.5.0 24 10.1.4.2
#
return

#
sysname RouterC
#
#
undo shutdown
ip address 10.1.2.1 255.255.255.0
pim dm
#
undo shutdown
ip address 10.1.1.1 255.255.255.0
igmp enable
pim dm
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.1.2.0 0.0.0.255
#
ip rpf-route-static 10.1.5.0 24 10.1.2.2
#
return

10.7.3 Example for Implementing Multicast Through a Static

Multicast Routed Tunnel
As shown in Figure 10-3, the network runs PIM-DM; Router A and Router B support multicast;
Router C does not support multicast; The receiver in the network can normally receive
information sent by the source. Router A, Router B, and Router C run OSPF. It is required to
use a multicast static route to enable the receiver to receive the information sent by the Source.
Figure 10-3 Networking diagram of implementing multicast through a static multicast routed
tunnel
Multicast Unicast Multicast

Router Router Router
POS1/0/0 POS3/0/0
10.1.1.1/24 14.1.1.2/24
POS1/0/0 POS2/0/0
RouterA GE2/0/0 10.1.1.1/24 14.1.1.1/24 GE2/0/0 RouterB
9.1.1.1/24 RouterC 8.1.1.1/24
9.1.1.2/24 8.1.1.2/24
Source Receiver
1. Configure an IP address for each interface.

2. Establish a GRE tunnel between Router A and Router B.
3. Configure OSPF to interconnect Router A, Router B, and Router C in unicast mode.
4. Enable multicast on Router A and Router B, PIM-SM on each interface, and IGMP on the
5. Configure a static multicast RPF route on Router B and specify Router A as the RPF
neighbor.
Data Preparation
l IP address of the source

l IP address of each interface

Procedure
Step 1 Configure an IP address for each interface.
# Configure an IP address and mask for each interface as shown in Figure 10-3. The
configuration details are not mentioned here.
Step 2 Establish a GRE tunnel between Router A and Router B.
[RouterA] interface tunnel 1/0/1
[RouterA-Tunnel1/0/1] ip address 20.1.1.1 24
[RouterA-Tunnel1/0/1] tunnel-protocol gre
[RouterA-Tunnel1/0/1] source 10.1.1.1
[RouterA-Tunnel1/0/1] destination 14.1.1.2
[RouterA-Tunnel1/0/1] quit
[RouterB] interface tunnel 1/0/1
[RouterB-Tunnel1/0/1] ip address 20.1.1.2 24
[RouterB-Tunnel1/0/1] tunnel-protocol gre
[RouterB-Tunnel1/0/1] source 14.1.1.2
[RouterB-Tunnel1/0/1] destination 10.1.1.1
[RouterB-Tunnel1/0/1] quit
Step 3 Configure OSPF to interconnect Router A, Router B, and Router C.

# Configure OSPF on Router A.
[RouterA] ospf 1
[RouterA-ospf-1] area 0
[RouterA-ospf-1-area-0.0.0.0] quit
[RouterA-ospf-1] quit
# Configure OSPF on Router B.

[RouterB] ospf 1
[RouterB-ospf-1] area 0
[RouterB-ospf-1-area-0.0.0.0] quit
[RouterB-ospf-1] quit
# Configure OSPF on Router C.

[RouterC] ospf 1
[RouterC-ospf-1] area 0
[RouterC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[RouterC-ospf-1-area-0.0.0.0] network 14.1.1.0 0.0.0.255
[RouterC-ospf-1-area-0.0.0.0] quit
[RouterC-ospf-1] quit
Step 4 Enable multicast on Router A and Router B and enable PIM-DM on each interface.
# Enable multicast on Router A and Router B, enable PIM-DM on each interface, and enable
IGMP on the interface connected to hosts.

[RouterA-Pos1/0/0] pim dm
[RouterA] interface tunnel 1/0/1
[RouterA-Tunnel1/0/1] pim dm
[RouterA-Tunnel1/0/1] quit
[RouterB] interface tunnel 1/0/1
[RouterB-Tunnel1/0/1] pim dm
[RouterB-Tunnel1/0/1] quit
Step 5 Configure a static multicast route.

# Configure a static multicast RPF route on Router B and specify Router A as the RPF neighbor.

# Source 9.1.1.2/24 sends multicast data to G 225.1.1.1. The receiver joins G, and can receive
multicast data sent by Source1. Run the display pim routing-table command on RouterB to
check the routing table.
(9.1.1.2, 225.1.1.1)
UpTime: 00:13:29
Upstream interface: Tunnel1/0/1
Protocol: pim-dm, UpTime: - , Expires: -
----End
Configuration Files
#
sysname RouterA
#
#
interface Pos1/0/0
link-protocol ppp
ip address 10.1.1.1 255.255.255.0
pim dm
#
ip address 9.1.1.1 255.255.255.0
pim dm
#
interface Tunnel1/0/0

ip address 20.1.1.1 255.255.255.0

source 10.1.1.1
destination 14.1.1.2
pim dm
#
ospf 1
area 0.0.0.0
network 9.1.1.0 0.0.0.255
network 10.1.1.0 0.0.0.255
network 20.1.1.1 0.0.0.255
#
return

#
sysname RouterB
#
#
ip address 8.1.1.1 255.255.255.0
pim dm
igmp enable
#
interface Pos3/0/0
link-protocol ppp
ip address 14.1.1.2 255.255.255.0
pim dm
#
interface Tunnel1/0/0
ip address 20.1.1.2 255.255.255.0
source 14.1.1.2
destination 10.1.1.1
pim dm
#
ospf 1
area 0.0.0.0
network 8.1.1.0 0.0.0.255
network 14.1.1.0 0.0.0.255
network 20.1.1.1 0.0.0.255
#
ip rpf-route-static 9.1.1.0 255.255.255.0 20.1.1.1
#
return

#
sysname RouterC
#
interface Pos1/0/0
link-protocol ppp
ip address 10.1.1.2 255.255.255.0
#
interface Pos2/0/0
link-protocol ppp
ip address 14.1.1.1 255.255.255.0
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 14.1.1.0 0.0.0.255
#
return
10.7.4 Example for Configuring Multicast Load Splitting

In a PIM-SM network where multicast services are stable, it is required to configure the stable-
preferred multicast load splitting policy so that multicast traffic can be distributed to multiple

equal-cost routes for transmission. In addition, it is required to configure multicast load splitting
weights for different interfaces to achieve unbalanced multicast load splitting.
Multicast route selection is based on the RPF check, and the route selection policy depends on
unicast routes. The selected unique route is used to guide the forwarding of multicast data. If
the volume of multicast traffic is excessively large on a network, the network may be congested
and multicast services may be affected. Multicast load splitting extends the rules of multicast
route selection and makes multicast route selection not completely depend on the RPF check.
When there are multiple equal-cost optimal routes on a network and the routes can be used to
forward multicast data, multicast load splitting can be performed among the routes for multicast
traffic.
Currently, multicast load splitting is classified into multicast source-based load splitting,
multicast group-based load splitting, and multicast source- and multicast group-based load
splitting. These types of multicast load splitting cannot meet the requirements of multicast
splitting in all scenarios. In the case that multicast routing entries and network configurations
are stable, RPF interfaces and RPF neighbors keep unchanged. When the number of entries is
excessively small, balanced load splitting cannot be achieved.
Stable-preferred load splitting consummates the preceding types of multicast load splitting. As
shown in Figure 10-4, there are three equal-cost routes between Router E connected to Host A
and the multicast source, and stable-preferred load splitting is configured on Router E. Therefore,
entries can be evenly distributed on the equal-cost routes and balanced load splitting can be
implemented among the equal-cost routes.
If the forwarding capabilities and the severities of traffic congestion of the three equal-cost routes
on Router E are different, balanced load splitting cannot meet network requirements. In this case,
you need to configure unbalanced load splitting on Router E, and set different load splitting
weights on the upstream interfaces of Router E to change the number of entries distributed to
the equal-cost routes. Thus, you can flexibly control the number of entries distributed on the
equal-cost routes.

Figure 10-4 Networking diagram of configuring multicast load splitting
PIM-SM
Source
0/0 PO
S2/0/
1
O S1/ RouterB S2/0/0 POS1/0
GE1/0/0 PO P /1
POS2/0/2 POS1/0/2 GE2/0/0
RouterA POS
2/0/ POS1/0/0 POS2/0/0
S1/
0/3
3 PO
RouterC RouterE
POS 0/0 HostA
1/0/
0 S2/
Loopback0 PO
RouterD
Device Interface IP Address Device Interface IP Address
Router A GE1/0/0 10.110.1.1/24 Router C POS1/0/0 192.168.2.2/24
POS2/0/1 192.168.1.1/24 POS2/0/0 192.168.5.1/24
POS2/0/2 192.168.2.1/24 Router D POS1/0/0 192.168.3.2/24
POS2/0/3 192.168.3.1/24 POS2/0/0 192.168.6.1/24
LoopBack0 1.1.1.1/32 Router E POS1/0/1 192.168.4.2/24
Router B POS1/0/0 192.168.1.2/24 POS1/0/2 192.168.5.2/24
POS2/0/0 192.168.4.1/24 POS1/0/3 192.168.6.2/24
GE2/0/0 10.110.2.1/24
l Assign an IP address to each interface on routers.

l Configure IS-IS to implement interworking among routers and ensure that route costs are
equal.
l Enable multicast on routers, enable PIM-SM on each interface, and set the loopback
interface on Router A as an RP.
l Configure stable-preferred multicast load splitting on Router E to ensure the stability of
multicast services.
l Host A requires to receive data from some multicast groups for a long period. Therefore,
configure the interfaces at the host side of Router E to join the multicast groups statically
in batches.

l Host A requires to receive data from a new multicast group. Therefore, configure a multicast
load splitting weight for each upstream interface on Router E to achieve unbalanced
multicast load splitting.
Data Preparation
l IP address of the multicast source

l IP address of each interface on the routers
l Address of the multicast group that interfaces at the host side of Router E statically join in
batches
l RouterMulticast load splitting weight on each upstream interface on Router E
Procedure
Step 1 Assign an IP address to each interface on the routers according to Figure 10-4. The detailed
configuration procedure is not mentioned here.
Step 2 Configure IS-IS to implement interworking among routers and ensure that route costs are equal.
The detailed configuration procedure is not mentioned here.
Step 3 Enable multicast on all routers and enable PIM-SM on each interface.
# Configure Router A. Configurations on Routers B, C, D, and E are similar to those on

Router A. Therefore, configurations on these Routers are not mentioned here.
[RouterA-LoopBack0] pim sm
Step 4 Configure an RP on Router A.
# Configure the interface loopback0 on Router A as an RP.

[RouterA] pim
[RouterA-pim] c-bsr loopback 0
[RouterA-pim] c-rp loopback 0
[RouterA-pim] quit
Step 5 Configure stable-preferred multicast load splitting on Router E.

[RouterE] multicast load-splitting stable-preferred
Step 6 Configure the interfaces at the host side of Router E to join the multicast groups statically in
batches.
# Configure GE 2/0/0 to join multicast groups from 225.1.1.1 to 225.1.1.3 statically.

[RouterE] interface gigabitethernet 2/0/0

[RouterE-GigabitEthernet2/0/0] igmp static-group 225.1.1.1 inc-step-mask 32 number
3
[RouterE-GigabitEthernet2/0/0] quit
Step 7 Verify the configuration about stable-preferred multicast load splitting.

# The multicast source (10.110.1.1/24) sends multicast data to multicast groups (225.1.1.1 to
225.1.1.3). Host A can receive the multicast data from the source. On Router E, check brief
information about the PIM routing table.
<RouterE> display pim routing-table brief
Total 3 (*, G) entries; 3 (S, G) entries
Entries Upstream interface NDwnstrms

(*, 225.1.1.1) Pos1/0/3 1
(10.110.1.1, 225.1.1.1) Pos1/0/3 1
(*, 225.1.1.2) Pos1/0/2 1
(10.110.1.1, 225.1.1.2) Pos1/0/2 1
(*, 225.1.1.3) Pos1/0/1 1
(10.110.1.1, 225.1.1.3) Pos1/0/1 1
You can find that (*, G) and (S, G) entries are equally distributed to three equal-cost routes, with
the upstream interfaces being POS 1/0/3, POS 1/0/2, and POS 1/0/1 respectively.
NOTE
The load splitting algorithm processes (*, G) and (S, G) entries separately and the process rules are the
same.
Step 8 Configure multicast load splitting weights for different upstream interfaces of Router E to
achieve unbalanced multicast load splitting.
# Set the multicast load splitting weight on POS 1/0/1 to 2.
[RouterE] interface pos 1/0/1
[RouterE-Pos1/0/1] multicast load-splitting weight 2
# Set the multicast load splitting weight on POS 1/0/3 to 0.

[RouterE-Pos1/0/3] multicast load-splitting weight 0
Step 9 Configure the interfaces at the host side of Router E to join new multicast groups statically in
batches.
# Configure GE 2/0/0 to join multicast groups from 225.1.1.4 to 225.1.1.9 statically.
[RouterE-GigabitEthernet2/0/0] igmp static-group 225.1.1.4 inc-step-mask 32 number
6
Step 10 Verify the configuration about unbalanced multicast load splitting.

# The multicast source (10.110.1.1/24) sends multicast data to multicast groups (225.1.1.1 to
225.1.1.9). Host A can receive the multicast data from the source. On Router E, check brief
information about the PIM routing table.
<RouterE> display pim routing-table brief
Entries Upstream interface NDwnstrms

(*, 225.1.1.1) Pos1/0/3 1

(10.110.1.1, 225.1.1.1) Pos1/0/3 1
(*, 225.1.1.2) Pos1/0/2 1
(10.110.1.1, 225.1.1.2) Pos1/0/2 1
(*, 225.1.1.3) Pos1/0/1 1
(10.110.1.1, 225.1.1.3) Pos1/0/1 1
(*, 225.1.1.4) Pos1/0/1 1
(10.110.1.1, 225.1.1.4) Pos1/0/1 1
(*, 225.1.1.5) Pos1/0/1 1
(10.110.1.1, 225.1.1.5) Pos1/0/1 1
(*, 225.1.1.6) Pos1/0/1 1
(10.110.1.1, 225.1.1.6) Pos1/0/1 1
(*, 225.1.1.7) Pos1/0/2 1
(10.110.1.1, 225.1.1.7) Pos1/0/1 1
(*, 225.1.1.8) Pos1/0/1 1
(10.110.1.1, 225.1.1.8) Pos1/0/2 1
(*, 225.1.1.9) Pos1/0/1 1
(10.110.1.1, 225.1.1.9) Pos1/0/1 1
The upstream interfaces of existent (*, G) and (S, G) entries keep unchanged. Since the multicast
load splitting weight of POS 1/0/1 is higher than that of POS 1/0/2, the newly generated entries
with the upstream interface being POS 1/0/1 are more than those with the upstream interface
being POS 1/0/2. The multicast load splitting weight of POS 1/0/3 is 0, which indicates that this
interface does not take part in load splitting of new entries.
----End
Configuration Files
#
sysname RouterA
#
#
isis 1
network-entity 10.0000.0000.0001.00
#
undo shutdown
ip address 10.110.1.2 255.255.255.0
isis enable 1
pim sm
#
interface Pos2/0/1
link-protocol ppp
undo shutdown
ip address 192.168.1.1 255.255.255.0
isis enable 1
pim sm
#
interface Pos2/0/2
link-protocol ppp
undo shutdown
ip address 192.168.2.1 255.255.255.0
isis enable 1
pim sm
#
interface Pos2/0/3
link-protocol ppp
undo shutdown
ip address 192.168.3.1 255.255.255.0
isis enable 1
pim sm
#
interface LoopBack0
ip address 1.1.1.1 255.255.255.255

isis enable 1
pim sm
#
pim
c-bsr LoopBack0
c-rp LoopBack0
#
return
#
sysname RouterB
#
#
isis 1
network-entity 10.0000.0000.0002.00
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.1.2 255.255.255.0
isis enable 1
pim sm
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.4.1 255.255.255.0
isis enable 1
pim sm
#
return
#
sysname RouterC
#
#
isis 1
network-entity 10.0000.0000.0003.00
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ip address 192.168.2.2 255.255.255.0
isis enable 1
pim sm
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.5.1 255.255.255.0
isis enable 1
pim sm
#
return
#
sysname RouterD
#
#
isis 1
network-entity 10.0000.0000.0004.00
#
interface Pos1/0/0
link-protocol ppp

undo shutdown
ip address 192.168.3.2 255.255.255.0
isis enable 1
pim sm
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ip address 192.168.6.1 255.255.255.0
isis enable 1
pim sm
#
return

#
sysname RouterE
#
multicast load-splitting stable-preferred
#
isis 1
network-entity 10.0000.0000.0005.00
#
interface Pos1/0/1
link-protocol ppp
undo shutdown
ip address 192.168.4.2 255.255.255.0
isis enable 1
pim sm
multicast load-splitting weight 2
#
interface Pos1/0/2
link-protocol ppp
undo shutdown
ip address 192.168.5.2 255.255.255.0
isis enable 1
pim sm
#
interface Pos1/0/3
link-protocol ppp
undo shutdown
ip address 192.168.6.2 255.255.255.0
isis enable 1
pim sm
multicast load-splitting weight 0
#
undo shutdown
ip address 10.110.2.2 255.255.255.0
isis enable 1
pim sm
igmp static-group 225.1.1.1 inc-step-mask 0.0.0.1 number 3
igmp static-group 225.1.1.4 inc-step-mask 0.0.0.1 number 6
#
return
10.8 Troubleshooting of Static Multicast Routes

This section describes how to locate and clear the faults of a static multicast route.
Fault Symptom
A router is not configured with any dynamic routing protocol. Its physical status and the status
of the link layer protocol are UP. The static route of the router, however, fails.

Fault Analysis
The possible causes are as follows:
l The static route is not configured or updated correctly so that it does not exist in the multicast
routing table.
l An optimal route has been received. This may also lead to static route failure.
Troubleshooting
1. Check whether the static route exists in the multicast routing table. Run the display
multicast routing-table static command to check the multicast static routing table and to
ensure that the corresponding route is configured correctly and exists in the multicast
configuration table.
2. Check the interface type of the next hop of the multicast static route. If the interface is not
a point-to-point one, the outgoing interface must be configured in the format of next hop
address.
3. Check whether a static multicast route matches a specified routing protocol. If the protocol
is specified when the static multicast route is configured, you can run the display ip
routing-table command to check whether the route is added for the specified protocol.
4. Check whether a static multicast route matches a specified routing policy. If the routing
policy is specified when the static multicast route is configured, you can run the display
route-policy command to check the configured routing policy.

Configuration Guide - IP Multicast 11 MLD Configuration
11 MLD Configuration
About This Chapter
This chapter describes the MLD fundamentals and configuration steps and maintenance for MLD
functions, along with typical examples.
11.1 MLD Introduction
This section describes the principle and concepts of MLD.
11.2 Configuring Basic MLD Functions
This section describes how to configure MLD.
11.3 Configuring Options of an MLD Packet
This section describes how to configure options of an MLD packet.
11.4 Configuring MLD Query Control
This section describes how to configure an MLD querier.
11.6 Configuration MLD Limit Function
This section describes the application scene of MLD limit and how to configure the MLD limit
function.
11.7 Maintaining MLD
This section describes how to clear MLD statistics and monitor the running status of MLD.
This section provides a configuration example of MLD.

11 MLD Configuration Configuration Guide - IP Multicast
11.1 MLD Introduction

This section describes the principle and concepts of MLD.
11.1.1 MLD Overview

11.1.2 MLD Features Supported by the NE80E/40E
11.1.1 MLD Overview

The Multicast Listener Discovery (MLD) is a sub-protocol of the Internet Control Message
Protocol version 6 (ICMPv6). MLD is used to set up and maintain the membership of groups
between hosts and their directly connected multicast routers. The functions and principles of
MLD are the same as those of the Internet Group Management Protocol (IGMP).MLD has the
following versions:
l MLDv1
MLDv1 is defined in RFC 2710, and is derived from IGMPv2. MLDv1 supports the Any-
Source Multicast (ASM) model. With the help of SSM mapping, MLDv1 can support the
Source-Specific Multicast (SSM) model.
l MLDv2
MLDv2 is defined in RFC 3810, and is derived from IGMPv3. MLDv2 supports the ASM
and SSM models.
11.1.2 MLD Features Supported by the NE80E/40E
Basic MLD Function

You can enable MLD and configure the MLD version.
Static MLD Group

You can configure an interface to statically join a multicast group. After the interface statically
joins a group, the system considers that the network segment where the interface resides has a
member of the group.
Configuring the Range of Groups that an Interface Can Join

You can set the range of groups that an interface can join as required.
Controlling the Router-Alert Option in an MLD Packet

You can determine whether to set the Router-Alert option in the MLD packets to be sent, and
whether to require that the received MLD packets contain the Router-Alert option.
Configuring Parameters of an MLD Query Message

You can set the interval for sending general query messages, MLD robustness variable, the
maximum response time of MLD Query messages, Keepalive period of other MLD queriers,
the interval for sending MLD group-specific query messages, and MLD fast leave.

SSM Mapping
For MLDv1 hosts, you can configure SSM mapping to build a multicast network of the SSM
model.
Limiting the Number of MLD Group Memberships

l Limiting the total number of MLD group memberships on a router: The total number of
MLD group memberships created by a router cannot exceed the limit value. When the total
number of MLD group memberships created by a router exceeds the limit value, no MLD
entry can be created.
l Limiting the total number of MLD group memberships in a single instance: The total
number of MLD group memberships related to an instance cannot exceed the limit value.
When the total number of MLD group memberships related to an instance reaches the limit
value, no MLD entry can be created.
l Limiting the total number of MLD group memberships on an interface: The total number
of MLD group memberships created on an interface cannot exceed the limit value. When
the total number of MLD group memberships created on an interface reaches the limit
value, no MLD entry can be created.
11.2 Configuring Basic MLD Functions

This section describes how to configure MLD.
11.2.3 Enabling MLD
11.2.4 (Optional) Configuring the MLD Version
11.2.5 (Optional) Configuring an Interface to Statically Join a Group
11.2.6 (Optional) Configuring the Range of Groups an Interface Can Join

MLD is applicable to the router and the hosts directly connected to the router. The router and
hosts need to run MLD. This section only describes how to configure MLD on a router.
You must enable IPv6 multicast routing before configuring MLD. IPv6 multicast routing is the
prerequisite for configuring IPv6 multicast functions. If the IPv6 multicast routing is disabled,
all IPv6 multicast configurations are deleted.
Enable MLD on the interface connected to hosts. For different MLD versions, MLD packets are
different; therefore, you need to configure matching MLD versions for routers and hosts. Other
MLD configurations can be done only after the preceding operations are complete.
To enable hosts in the network segment to which the interface is connected to join the specified
groups and receive packets to the groups, you can set a group policy on the related interface to
limit the range of groups that the interface serves.

Before configuring basic MLD functions, configure a unicast routing protocol to interconnect
the entire multicast domain.
Data Preparation
To configure basic MLD functions, you need the following data.
No. Data
1 MLD version
2 Group address and source address
3 ACL6 rules for filtering multicast groups
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
multicast ipv6 routing-enable
IPv6 multicast routing is enabled in the public network instance.
----End
11.2.3 Enabling MLD
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

interface-type interface-number specifies the interface connected to hosts.
Step 3 Run:
mld enable
MLD is enabled on the interface.
By default, MLD is not enabled on the interface.
----End
11.2.4 (Optional) Configuring the MLD Version
Context
CAUTION
Ensure that all MLD router interfaces in the same network segment are configured with the same
MLD version. Otherwise, faults may occur.
This configuration is optional. By default, MLDv2 is adopted.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
mld version { 1 | 2 }
The MLD version of the interface level is configured.
By default, MLDv2 is adopted.
----End
11.2.5 (Optional) Configuring an Interface to Statically Join a Group
Context

NOTE
This configuration is optional. By default, the interface does not statically join any group.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
mld static-group ipv6-group-address [ inc-step-mask ipv6-group-mask-length number
group-number ] [ source ipv6-source-address ]
The interface is configured to statically join a single multicast group or multiple multicast groups
in batches. After the interface statically joins the multicast groups, the router considers that the
members of the multicast groups exist on the network segment where the interface resides.
----End
11.2.6 (Optional) Configuring the Range of Groups an Interface Can

Join
Context
NOTE
This configuration is optional. By default, the interface can join any group.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
mld group-policy { acl6-number | acl6-name acl6-name } [ 1 | 2 ]
The range of groups that the interface can join is configured.
----End

Procedure
l Run the display mld interface [ interface-type interface-number ] [ verbose ] command
to check the MLD configuration and running information on an interface.
l Run the display mld group [ ipv6-group-address | interface interface-type interface-
number ] * [ static ] [ verbose ] command to check information on members of an MLD
multicast group.
----End
11.3 Configuring Options of an MLD Packet

This section describes how to configure options of an MLD packet.
11.3.2 Configuring the Router-Alert Option of an MLD Packet
MLD has the group-specific and source/group-specific query messages. The groups are varied.
Routers cannot join all groups. The Router-Alert option is used to send the MLD packets of
which the multicast group is not specified by the upper-layer protocol of the IP layer to the upper-
layer protocol for processing.
Before configuring options of an MLD packet, complete the following tasks:

l Configuring Basic MLD Functions
Data Preparation
To configure options of an MLD packet, you need the following data.
No. Data
1 Whether the Router-Alert option is set in the packet
11.3.2 Configuring the Router-Alert Option of an MLD Packet

Context
This configuration is optional. By default, MLD packets sent by routers carry the Router-Alert
option, but the routers do not check the Router-Alert option. That is, the routers process all the
received MLD packets, including those without the Router-Alert option.
NOTE

Procedure
1. Run:
system-view

2. Run:
mld
The MLD view is displayed.

3. Run:
require-router-alert
The Router-Alert option is required in the received MLD packet.

If the received the MLD packet does not carry the Router-Alert option, the packet is
discarded.
4. Run:
send-router-alert
The Router-Alert option is set in the header of the MLD packet to be sent.
1. Run:
system-view

2. Run:

3. Run:
mld require-router-alert
The Router-Alert option is required in the received MLD packet.

If the received the MLD packet does not carry the Router-Alert option, the packet is
discarded.
4. Run:
mld send-router-alert

The Router-Alert option is set in the header of the MLD packet to be sent.
----End
Procedure
l Run the display mld interface [ interface-type interface-number | up | down ]
[ verbose ] command to check the MLD configuration and running information on an
interface.
----End
11.4 Configuring MLD Query Control

This section describes how to configure an MLD querier.
11.4.2 (Optional) Configuring MLD Query and Response
CAUTION
A great many of MLD interfaces exist in the network and these MLD interfaces are mutually
restricted. Ensure that all MLD parameters of all MLD router interfaces on the same network
segment are identical. Otherwise, the network may be faulty.
The MLD querier periodically sends MLD Query messages on the share network connected to
receivers. When receiving a Report message from a member, the routers on the shared network
refresh information about the member relationship.
If non-queriers do not receive any query message within the Keepalive period of the MLD
querier, the querier is considered faulty, and a new round of the querier election is triggered
automatically.
In the application of ADSL dial-up access, one host corresponds to a port. A querier, therefore,
corresponds to only one receiver host. When a receiver host switches among multiple groups
such as TV channels, you can enable the fast leave mechanism on the querier.
Before configuring MLD query control, complete the following tasks:

Data Preparation
To configure MLD query control, you need the following data.
No. Data
1 The interval for sending MLD general Query messages
2 Robustness variable
3 The maximum response time of the MLD Query message
4 Keepalive period of the other MLD queriers
5 The interval for sending MLD group-specific Query messages and group/source-
specific Query messages
6 ACL6 that limits the application range of prompt leave
11.4.2 (Optional) Configuring MLD Query and Response
Context
CAUTION
In the actual configuration, ensure that the interval for sending general Query messages is greater
than the maximum response time and is smaller than the Keepalive time of the other MLD
queriers.
NOTE

Procedure
1. Run:
system-view

2. Run:
mld


3. Run:
The interval for sending Query messages is set.

By default, the interval for sending Query messages is 125 seconds.
4. Run:
The MLD robustness variable is set.

By default, the MLD robustness variable is 2.
– When a router starts, the router sends general query messages for the number of
robust-value times. The sending interval is 1/4 of the interval for sending MLD
general query messages.
– When a router receives a Leave message, the router sends MLD last listener query
messages for the number of robust-value times.
The greater the robustness variable is, the longer the timeout period of the group is.
5. Run:
max-response-time interval
The maximum response time of the MLD Query message is set.

By default, the maximum MLD response time is 10 seconds.
6. Run:
timer other-querier-present interval
The interval for the Keepalive period of the other MLD queriers is set.
By default, the formula used to calculate the Keepalive period of the other queriers
is: the Keepalive period of the other MLD queriers = robustness variable x the interval
for sending MLD general query messages + 1/2 x the MLD maximum response time.
When default values of robustness variable, the interval for sending MLD general
query messages, and maximum response time are used, the Keepalive period of the
other MLD queriers is 255 seconds.
7. Run:
lastlistener-queryinterval interval
The interval for sending last listener query messages is set.

The shorter the interval, the more sensitive the querier. By default, the interval is 1
second.
1. Run:
system-view

2. Run:

3. Run:

mld timer query interval
The interval for sending MLD general query messages is set.

4. Run:
mld max-response-time interval
The maximum response time of the MLD Query message is set.

5. Run:
mld timer other-querier-present interval
The Keepalive period of the other MLD queriers is set.

6. Run:
mld robust-count robust-value
The MLD robustness variable is set.

7. Run:
mld lastlistener-queryinterval interval
The interval for sending MLD last listener query messages is set.
8. Run:
mld prompt-leave [ group-policy { basic-acl6-number | acl6-name acl6-
name } ]
MLD fast leave is configured.

When an interface receives a Leave message for a certain group, the interface
immediately deletes the downstream interface of the entry to which the group
corresponds, without sending the last listener query message.
By default, when a router receives a Leave message for a group, the router sends last
listener query messages.
This command is only valid for MLDv1.
----End

Procedure
interface.
----End

11.5.3 Configuring the Static SSM Mapping Policy

In the SSM host network segment, the router can know the specific source when a host joins a
group. The SSM solutions are as follows:
l Hosts and routers run MLDv2. When a host joins a group, the host specifies the source
from which the host wants to receive data.
l If some hosts in the network segment can run only MLDv1, the hosts cannot specify the
sources from which they want to receive data when joining related groups. In this case, you
need to configure SSM mapping and static mapping rules on the router. As a result, the (*,
G) information carried in the Report message is mapped to the (G, INCLUDE, (S1, S2, ...))
information.
Before configuring SSM mapping, complete the following tasks:

Data Preparation
To configure SSM mapping, you need the following data.
No. Data
1 Interface that needs to be enabled with SSM mapping
2 Group address/mask and source address/mask
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
mld enable
MLD is enabled.
Step 4 Run:
mld version 2
The MLD version is set to 2.
By default, the MLD version is 2.
To ensure that the hosts that run any MLD version on the network segment can obtain the SSM
services, it is recommended to configure MLDv2 on the router interface.
Step 5 Run:
mld ssm-mapping enable
The SSM mapping is enabled.
----End
11.5.3 Configuring the Static SSM Mapping Policy
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
mld
Step 3 Run:
ssm-mapping ipv6-group-address ipv6-group-mask-length ipv6-source-address
The mapping from the source to the group is set.
You can run the command repeatedly to configure the mapping from a group to multiple sources.
l ipv6-group-address ipv6-group-mask-length: specifies the group address and mask. The

group address must be in the SSM group address range.
l ipv6-source-address: specifies the address of the source that sets up the mapping relationship
with the group.
----End

Procedure
interface.
number ] * ssm-mapping [ verbose ] to check information about a source/group-specific
address.
l Run the display mld ssm-mapping interface [ interface-type interface-number [ group
ipv6-group-address ] ] command to check information about an interface enabled with SSM
mapping.
l Run the display mld ssm-mapping group [ ipv6-group-address ] command to check SSM
mapping rules of a specified group address.
----End
11.6 Configuration MLD Limit Function

This section describes the application scene of MLD limit and how to configure the MLD limit
function.
11.6.2 Configuring the Maximum Number of Global MLD Group Memberships
11.6.3 Configuring the Maximum Number of Global MLD Entries in a Single Instance
11.6.4 Configuring the Maximum Number of MLD Group Memberships on an Interface
To limit IPTV ICPs and the number of users accessing IP core networks, you can configure the
MLD limit function.
The MLD limit function is configured on the last-hop router connected to users. You can perform
the following configurations as required:
l Configure the maximum number of global MLD group memberships on a router.

l Configure the maximum number of MLD entries in a single instance.
l Configure the maximum number of MLD group memberships on an interface.
NOTE
If the MLD limit function is required to be configured globally, for a single instance, and for an interface
on the same router, it is recommended that the limits on the number of global MLD group memberships,
the number of MLD group memberships in the single instance, and the number of MLD group memberships
on the interface should be in descending order.

Before configuring the MLD limit function, complete the following task:

Data Preparation
To configure the MLD limit function, you need the following data.
No. Data
1 Maximum number of global MLD group memberships
2 Maximum number of MLD group memberships in a single instance
3 Maximum number of MLD group memberships on an interface
11.6.2 Configuring the Maximum Number of Global MLD Group

Memberships
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
mld global limit number
The maximum number of global MLD entries of all instances is set.
----End
11.6.3 Configuring the Maximum Number of Global MLD Entries

in a Single Instance
Context

Procedure
Step 1 Run:
system-view
Step 2 Run:
mld
Step 3 Run:
limit number
The maximum number of global MLD entries in a single instance is set.
----End
11.6.4 Configuring the Maximum Number of MLD Group

Memberships on an Interface
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The MLD interface view is displayed.
Step 3 Run:
mld limit number [ except { acl6-number | acl6-name acl6-name } ]
The maximum number of MLD group memberships is set on the interface.
NOTE
If except is not specified in the command, the router is limited by the maximum number of MLD entries
when creating the entries for all the groups or source/groups.
Before specifying except, you need to configure the corresponding ACl. Then, the interface filters the
received MLD Join messages according to the ACL. The number of entries that are filtered according to
the ACL is not limited by the maximum number of MLD entries.
----End

Procedure
[ verbose ] command to check the configuration and running of MLD on an interface.
l Run the following commands to check information about the members of an MLD multicast
group.
– display mld group [ ipv6-group-address | interface interface-type interface-number ]
*[ verbose ]
– display mld group [ ipv6-group-address | interface interface-type interface-number ]
*ssm-mapping [ verbose ]
# Run the display mld interface command to view the configuration and running status
of MLD on the router interface. The display information is as follows:
<RouterA> display mld interface gigabitethernet 1/0/0
GigabitEthernet1/0/0(FE80::200:5EFF:FE66:5100):
MLD is enabled
Current MLD version is 1
MLD state: up
MLD group policy: none
MLD limit: 30
Value of query interval for MLD (negotiated): 125 s
Value of query interval for MLD (configured): 125 s
Value of other querier timeout for MLD: 0 s
Value of maximum query response time for MLD: 10 s
Querier for MLD: FE80::200:5EFF:FE66:5100 (this router)
From the display, you can see the maximum number of MLD group members on GE1/0/0
of Router A.
----End
11.7 Maintaining MLD

This section describes how to clear MLD statistics and monitor the running status of MLD.
11.7.1 Clearing Information about MLD Groups
11.7.2 Monitoring the Running Status of MLD
11.7.1 Clearing Information about MLD Groups
Context
CAUTION
The MLD groups that an interface dynamically joins are deleted after you run the reset mld
group or the reset mld group ssm-mapping command. Receivers may not receive multicast
information normally. So, confirm the action before you use the command.

Procedure
l Run the reset mld explicit-tracking { all | interface interface-type interface-number
[ host ipv6-host-address [ group ipv6-group-address [ source ipv6-source-address ] ] ] }
command in the user view to clear the hosts that join a multicast group through MLD on
an interface.
l Run the following commands in the user view to clear the MLD groups that the interface
dynamically joins (not including the MLDv1 group in the SSM range).
– reset mld group all
– reset mld group interface interface-type interface-number { all | ipv6-group-
address [ ipv6-group-mask-length ] [ ipv6-source-address [ ipv6-source-mask-
length ] ] }
l Run the following commands in the user view to clear MLDv1 groups in the SSM range.
– reset mld group ssm-mapping all
– reset mld group ssm-mapping interface interface-type interface-number { all | ipv6-
group-address [ ipv6-group-mask-length ] }
l Run the reset mld control-message counters [ interface interface-type interface-
number ] [ message-type { query | report } ] command in the user view to delete statistics
of MLD messages.
----End
11.7.2 Monitoring the Running Status of MLD
Context
status of MLD.
Procedure
l Run the display mld explicit-tracking [ interface interface-type interface-number [ host-
address ipv6-host-address | group ipv6-group-address source ipv6-source-address ] ]
command in any view to check information about the MLD hosts on an interface.
number ] * [ static ] [ verbose ] command in any view to check information about groups
on each interface.
number ] * ssm-mapping [ verbose ] command in any view to check information about a
group configured with SSM mapping.
l Run the display mld interface [ interface-type interface-number ] [ verbose ] command
in any view to check the MLD configuration and running information on an interface.
l Run the display mld routing-table [ ipv6-source-address [ ipv6-source-mask-length ] |
ipv6-group-address [ ipv6-group-mask-length ] ] * [ static ] [ outgoing-interface-
number [ number ] ] command in any view to check the MLD routing table.
l Run the display mld ssm-mapping interface [ interface-type interface-number [ group
group-address ] ] command in any view to check information about an interface enabled
with SSM mapping.

l Run the display mld ssm-mapping group [ ipv6-group-address ] command in any view
to check SSM mapping rules of a specified group address.
l Run the display mld control-message counters [ interface interface-type interface-
number ] [ message-type { query | report } ] command in any view to check the statistics
of MLD messages received by interfaces.
----End

This section provides a configuration example of MLD.
11.8.1 Example for Configuring Basic MLD functions

11.8.2 Example for Configuring MLD Limit
11.8.1 Example for Configuring Basic MLD functions
In the IPv6 network shown in Figure 11-1, unicast routes are normal. You are required to
implement multicast in the network to enable hosts to receive the Video On Demand (VOD)
information.
Figure 11-1 Networking diagram of configuring basic MLD functions

Ethernet
HostA
RouterA Receiver
POS2/0/0 N1
GE1/0/0
3000::12/64 HostB
RouterB
Leaf network
POS2/0/0
GE1/0/0
3001::10/64 HostC
PIM network
RouterC Receiver
N2
POS2/0/0 GE1/0/0 HostD
3001::12/64
Ethernet
1. Enable IPv6 multicast.


3. Enable MLD on the interface at the host side.
Data Preparation
To complete the configuration, the version number of MLD of routers and user hosts is required.
Procedure
Step 1 Enable multicast on routers and MLD and PIM-IPv6-SM on the interface at the host side.
# Enable multicast on Router A, enable MLD and PIM-IPv6-SM on GE 1/0/0, and set the MLD
version to 1.
[RouterA] multicast ipv6 routing-enable
[RouterA-GigabitEthernet1/0/0] pim ipv6 sm
[RouterA-GigabitEthernet1/0/0] mld enable
[RouterA-GigabitEthernet1/0/0] mld version 1
# The configurations of Router B and Router C are the same as the configuration of Router A,
# Run the display mld interface command to view the configuration and running status of MLD
on the router interface. MLD information on GE 1/0/0 of Router B is as follows:
<RouterB> display mld interface gigabitethernet 1/0/0
MLD is enabled
MLD state: up
From the display, you can see that Router B is a querier. This is because the IPv6 link-local
address of GE 1/0/0 on Router B is the smallest in the network segment.
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
#
interface Pos2/0/0
undo shutdown
ipv6 enable
ipv6 address 2002::1/64
pim ipv6 sm
#

undo shutdown
ipv6 enable
pim ipv6 sm
mld enable
mld version 1
#
return

#
sysname RouterB
#
ipv6
#
#
interface Pos2/0/0
undo shutdown
ipv6 enable
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
mld enable
mld version 1
#
return

#
sysname RouterC
#
ipv6
#
#
interface Pos2/0/0
undo shutdown
ipv6 enable
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
mld enable
mld version 1
#
return
11.8.2 Example for Configuring MLD Limit
When a large number of users watch multiple programs simultaneously, great bandwidth of
devices is consumed, which degrades the performance of the devices and lowers the stability of
receiving multicast data.

The existing multicast technologies control multicast networks by limiting the number of
multicast forwarding entries or the number of outgoing interfaces of an entry, which cannot meet
the requirements of operators for real-time video services on IPTV networks and flexible
management of network resources.
Configuring MLD limit can enable operators to properly plan network resources and flexibly
control the number of multicast groups that hosts can join. In the network shown in Figure
11-2, multicast services are deployed. The global MLD limit, instance-based MLD limit, and
interface-based MLD limit are configured on Router A, Router B, and Router C connected to
hosts to limit the number of multicast groups that the hosts can join. When the number of
multicast groups that hosts can join reaches the limit, the devices are not allowed to create new
MLD entries. This ensures that the users that join related multicast groups more clearly and
stably watch related programs.
Figure 11-2 Networking diagram of configuring MLD Limit

Ethernet
HostA
RouterA Receiver
POS2/0/0 N1
2001::1/64 GE1/0/0
3000::12/64 HostB
RouterB
Leaf network
POS2/0/0
2002::1/64 GE1/0/0
PIM 3001::10/64 HostC
network RouterC Receiver
N2
POS2/0/0 GE1/0/0 HostD
2003::1/64 3001::12/64
Ethernet
1. Enable IPv6 multicast.

3. Enable MLD on the interface at the host side.
4. Limit the number of MLD group memberships on Router A, Router B, and Router C.
Data Preparation
l the version number of MLD of routers and user hosts.
l The maximum number of MLD group memberships.

Procedure
Step 1 Enable multicast on routers and MLD and PIM-IPv6-SM on the interface at the host side.
# Enable multicast on Router A, enable MLD and PIM-IPv6-SM on GE 1/0/0, and set the MLD
version to 1.
[RouterA-GigabitEthernet1/0/0] mld enable
[RouterA-GigabitEthernet1/0/0] mld version 1
[RouterA-Pos2/0/0] pim ipv6 sm
# The configurations of Router B and Router C are the same as the configuration of Router A,
Step 2 Limit the number of MLD group memberships on the last-hop router connected to users.
# Configure the maximum number of MLD group memberships to 50 on Router A.

[RouterA] mld global limit 50
# Configure the maximum number of MLD group memberships to 40 in the public network
instance.
[RouterA] mld
[RouterA-mld] limit 40
[RouterA-mld] quit
# Configure the maximum number of MLD group relationships to 30 on GE 1/0/0.

[RouterA-GigabitEthernet1/0/0] mld limit 30
mentioned here.
# Run the display mld interface command to view the configuration and running status of MLD
on the router interface. MLD information on GE 1/0/0 of Router B is as follows:
<RouterB> display mld interface gigabitethernet 1/0/0
MLD is enabled
MLD state: up
MLD limit: 30
From the display, you can see that the maximum number of MLD group members that the
GE1/0/0 of Router B can creat is 30.
----End

Configuration Files
#
sysname RouterA
#
ipv6
#
mld global limit 50
#
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ipv6 enable
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
mld enable
mld version 1
mld limit 30
#
mld
limit 40
#
return

#
sysname RouterB
#
ipv6
#
mld global limit 50
#
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ipv6 enable
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
mld enable
mld version 1
mld limit 30
#
mld
limit 40
#
return

#
sysname RouterC
#
ipv6

#
mld global limit 50
#
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ipv6 enable
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
mld enable
mld version 1
mld limit 30
#
mld
limit 40
#
return

12 PIM-DM (IPv6) Configuration
About This Chapter
This chapter describes the PIM-DM (IPv6) fundamentals and configuration steps and
maintenance for PIM-DM functions, along with typical examples. PIM-DM in this chapter refers
to the IPv6 PIM-DM, unless otherwise specified.
12.1 PIM-IPv6 Introduction
This section describes the principle and concepts of PIM-DM.
12.2 Configuring Basic PIM-DM (IPv6) Functions
This section describes how to configure PIM-DM.
12.3 Adjusting Control Parameters of a Source
source in the PIM-IPv6 network.
12.4 Adjusting Control Parameters for Maintaining Neighbors
This section describes how to configure control parameters of the PIM-DM Hello message.
This section describes how to configure control parameters of the PIM-DM Join/Prune message.
This section describes how to configure control parameters of the PIM-DM State-Refresh
message.
12.7 Adjusting Control Messages for Graft
This section describes how to configure control parameters of the PIM-DM Graft message.
12.8 Adjusting Control Messages for Assert
This section describes how to configure control parameters of the PIM-DM Assert message.
12.9 Configuring PIM-IPv6 Silent
This section describes how to configure PIM silent to prevent the malicious attack from a host.
12.10 Maintaining PIM-DM
This section describes how to clear statistics of IPv6 PIM control messages and monitor the
running status of IPv6 PIM-DM.

This section provides a configuration example of PIM-DM.

12.1 PIM-IPv6 Introduction

This section describes the principle and concepts of PIM-DM.
12.1.1 PIM-IPv6 Overview

In IPv4 multicast applications, the Protocol Independent Multicast (PIM) is used to establish
multicast routes between routers to replicate and forward multicast packets.
In IPv6 multicast applications, routers run PIM-IPv6. The functions and principles of PIM-IPv6
are similar to those of PIM-IPv4.
PIM-IPv6 consists of the following separate protocols:
l PIM-DM: indicates the Protocol Independent Multicast-Dense Mode. PIM-DM is

applicable to a small-scale network with densely-distributed members. The network adopts
the Any-Source Multicast (ASM) model to implement multicast services.
l PIM-SM: indicates the Protocol Independent Multicast-Sparse Mode. PIM-SM is
applicable to a large-scale network with sparsely-distributed members. The network adopts
the ASM and Source-Specific Multicast (SSM) models to implement multicast services.
NOTE
l This chapter is concerned only about the PIM-DM configuration in the IPv6 network. PIM-DM in this
chapter refers to IPv6 PIM-DM, unless otherwise specified.
l For details of PIM-SM (IPv6), refer to the chapter PIM-SM (IPv6) Configuration in the HUAWEI
l For details of ASM and SSM models, refer to the chapter "IP Multicast Overview" in the HUAWEI
NetEngine80E/40E Router Feature Description - IP Multicast.
Controlling the Forwarding of a Multicast Source

You can configure the Keepalive period of a multicast source and the filtering rules of the
multicast source.
Adjusting Control Parameters for Maintaining Neighbors

You can set the following control parameters by using the related commands:

l Period for keeping neighbors reachable
l Whether the Hello messages without the Generation ID option are accepted
l Maximum delay for triggering Hello messages

rules
Adjusting Control Parameters for Pruning

You can adjust the following control parameters for pruning:
l The interval for keeping the Prune state of the downstream interface
l The delay from the time when the current router receives a Prune message from a
downstream router to the time when the current router performs the prune action in the
LAN
l The period for overriding the prune action
Adjusting Control Parameters for State-Refresh

You can enable or disable State-Refresh, set the interval for sending PIM State-Refresh
messages, set the time for waiting to receive the next State-Refresh message, and set the TTL
values of State-Refresh messages.
Adjusting Control Parameters for Graft

You can set the interval for retransmitting Graft messages.

You can set the period for routers to keep the Assert state. The routers that fail in the election
forbid downstream interfaces to forward multicast data during this period. After the period
expires, the downstream interfaces continue to forward multicast data.

Some hosts may send a large number of malicious PIM Hello messages, which results in the
suspension of the router. By configuring the PIM Silent function on the interfaces of the
router connected with the host, you can protect the router from being attacked.
12.2 Configuring Basic PIM-DM (IPv6) Functions

This section describes how to configure PIM-DM.
12.2.3 Enabling Basic PIM-DM (IPv6) Functions

PIM-DM is applicable to a small-scale network. Most of network segments have receivers.

Before configure basic PIM-DM functions, complete the following tasks:
Data Preparation
To configure basic PIM-DM functions, you need the following data.
No. Data
1 Type and number of the interface to be enabled with PIM-DM (IPv6)
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The IPv6 multicast routing is enabled in the public network instance.
----End
12.2.3 Enabling Basic PIM-DM (IPv6) Functions
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim ipv6 dm
Basic PIM-DM (IPv6) functions are enabled.
After PIM-DM (IPv6) is enabled on interfaces, routers set up the PIM-IPv6 neighbor relationship
with each other. The routers can then process protocol packets received from PIM-IPv6
neighbors.
You can run the undo pim ipv6 dm command to disable PIM-DM (IPv6) on an interface.
NOTE
PIM-DM (IPv6) and PIM-SM (IPv6) cannot be enabled on an interface simultaneously. The PIM-IPv6
modes on all interfaces that belong to the same instance must be the same. When a router is deployed in a
PIM-DM (IPv6) domain, enable PIM-DM (IPv6) on all non-boundary interfaces.
----End
Procedure
l Run the display pim ipv6 interface [ interface-type interface-number | up | down ]
[ verbose ] command to check information about PIM-IPv6 interfaces.
l Run the display pim ipv6 neighbor [ ipv6-link-local-address | interface interface-type
interface-number | verbose ] * command to check information about PIM-IPv6 neighbors.
l Run the following commands to check the PIM-IPv6 multicast routing table.
– display pim ipv6 routing-table [ ipv6-source-address [ mask mask-length ] | ipv6-
group-address [ mask mask-length ] | flags { act | del | exprune | ext | loc | niif |
nonbr | none | rpt | sg_rcvr | sgjoin | spt | swt | wc | upchg } | fsm | incoming-
interface [ interface-type interface-number| register ] | mode { dm | sm | ssm } |
outgoing-interface { exclude | include | match } [ interface-type interface-number |
none | register ] ] * [ outgoing-interface-number [ number ] ]
– display pim ipv6 routing-table brief [ ipv6-source-address [ mask mask-length ] |
ipv6-group-address [ mask mask-length ] | incoming-interface { interface-type
----End

12.3.2 Configuring the Keepalive Period of a Source


This configuration is applicable to all PIM-DM networks.
PIM-IPv6 routers check the passing multicast data packets. By checking whether the data packets
match the filtering rule, the routers determine whether to forward the packets. That is, the
routers in the PIM-IPv6 domain act as filters. The filters help to control data flows and limit
information obtained by downstream receivers.
Before adjusting control parameters of a source, complete the following tasks:
l Configuring Basic PIM-DM (IPv6) Functions
Data Preparation
To adjust control parameters of a source, you need the following data.
No. Data
1 Keepalive period of a source
Context
Do as follows on the PIM-IPv6 router:
NOTE
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6
The PIM-IPv6 view is displayed.

Step 3 Run:

The Keepalive period of a source is configured.

If a router does not receive any (S, G) packet in the Keepalive period of the source, the router
considers that the source stops sending multicast data to G, and the (S, G) entry becomes invalid.
----End
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
source-policy { acl6-number | acl6-name acl6-name }
The nearer the filter to the source, the more obvious the effect of the filtering.
are forwarded.
NOTE
l If acl6-number | acl6-name acl6-name is specified in the source-policy command and ACL rules are
l If acl6-number | acl6-name acl6-name is specified in the source-policy command and no ACL rule is
l The source-policy command does not filter the static (S, G) entries.
----End

Procedure


----End
12.4 Adjusting Control Parameters for Maintaining

Neighbors
This section describes how to configure control parameters of the PIM-DM Hello message.
12.4.4 Refusing to Receive the Hello Message Without the Generation ID Option

PIM-IPv6 routers establish the neighbor relationship by exchanging Hello messages to negotiate
various control parameters.
Routers under the control of default values can work normally. In the NE80E/40E, users can
NOTE
Before adjusting control parameters for maintaining neighbors, complete the following tasks:
Data Preparation
To adjust control parameters for maintaining neighbors, you need the following data.
No. Data
1 Timeout period for waiting to receive Hello message from neighbors

No. Data
Context
NOTE
The configuration of the control parameters for maintaining PIM-IPv6 neighbors involves the following
cases:
configuration. If the configuration on an interface is not set, the global configuration is used.
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
The interval for sending Hello messages is configured.

1. Run:
system-view

2. Run:

3. Run:
pim ipv6 timer hello interval

4. Run:
pim ipv6 triggered-hello-delay interval

After the maximum delay is set, the conflict caused by multiple PIM-IPv6 routers
simultaneously sending Hello message is avoided.
----End
Context
NOTE
The configuration of the control parameters for maintaining PIM-IPv6 neighbors involves the following
cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
The timeout period for keeping a neighbor reachable is set.

Each router maintains a timer for each neighbor. When receiving a Hello message, a
router resets the timer. If the local router does not receive any Hello message from a
neighbor after the timer times out, the local router considers that the neighbor is
unreachable.
1. Run:
system-view

2. Run:

3. Run:

pim ipv6 hello-option holdtime interval
The timeout period for keeping the neighbor reachable is set.
If the local router does not receive any Hello message from a neighbor after the timer
times out, the local router considers that the neighbor is unreachable.
----End
12.4.4 Refusing to Receive the Hello Message Without the

Generation ID Option
Context
A router assigns a random Generation ID to an interface enabled with PIM. The Hello messages
sent by the interface carry the random Generation ID. If the status of the interface changes, the
random Generation ID is updated.
When the Generation ID option in the Hello message received from an upstream neighbor
changes, it indicates that the status of the upstream neighbor changes. If a router does not want
to receive data from an upstream neighbor, the router sends a Prune message after receiving a
data packet from the upstream neighbor.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim ipv6 require-genid
The Generation ID option is set in a Hello message.
The Hello message without the Generation ID option is rejected.
----End
Context
To prevent some router from being involved in PIM, filtering PIM neighbors is required.
Do as follows on the router running IPv6 PIM-DM:

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim ipv6 neighbor-policy { basic-acl6-number | acl6-name acl6-name }

NOTE
When configuring the neighbor filtering function on the interface, you must also configure the neighbor
filtering function correspondingly on the router that sets up the neighbor relationship with the interface.
----End

Procedure
----End

This section describes how to configure control parameters of the PIM-DM Join/Prune message.
12.5.3 Configuring the Delay for Transmitting Prune Messages in a LAN

When the last member of a group on a router leaves its group, the router sends a Prune message
through an upstream interface to request the upstream router to perform the prune action. After

receiving the Prune message, the upstream interface stops forwarding packets to this network
segment. If other downstream routers exist in this network segment, they must send the Join
message to override the prune action.
Before adjusting control parameters for prune, complete the following tasks:
Data Preparation
To adjust control parameters for prune, you need the following data.
No. Data
3 Period for overriding the prune action
12.5.2 Configuring the Period for an Interface to Keep the Prune

State
Context
NOTE
The configuration of the control parameters of prune involves the following cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
After the period expires, the pruned interface continues to forward packets. Before
the period expires, the router resets the Holdtime timer after receiving a State-Refresh
message.
1. Run:
system-view

2. Run:

3. Run:
pim ipv6 holdtime join-prune interval
After the period expires, the pruned interface continues to forward packets. Before
the period expires, the router resets the Holdtime timer after receiving a State-Refresh
message.
----End
12.5.3 Configuring the Delay for Transmitting Prune Messages in a

LAN
Context
The Hello message carries lan-delay and the override-interval. The relationship between lan-
delay, override-interval, and Prune-Pending Timer (PPT) is that lan-delay + override-interval =
PPT. PPT indicates the delay from the time when a router receives the Prune message from a
downstream interface to the time when the router performs the prune action to suppress the
forwarding on the downstream interface. If the router receives a Join message from a downstream
router within the PPT, the router does not perform the prune action.
NOTE
The configuration of control parameters for Prune involves the following two cases:
Procedure
1. Run:
system-view


2. Run:
pim-ipv6

3. Run:

1. Run:
system-view

2. Run:

3. Run:
pim ipv6 hello-option lan-delay interval
----End
Context
When a router receives a Prune message from an upstream interface, it indicates that router in
the LAN. When a router receives a Prune message from an upstream interface, it indicates that
the router still needs to receive multicast data. If the router still requests the multicast data, it
needs to send a Join message in the override-interval period to the upstream router.
NOTE
The configuration of control parameters for Prune involves the following two cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6


3. Run:
hello-option override-interval

1. Run:
system-view

2. Run:

3. Run:
pim ipv6 hello-option override-interval interval

----End

Procedure
l Run the display pim ipv6 control-message counters interface interface-type interface-
number [ message-type { assert | bsr | graft | graft-ack | hello | join-prune | state-
refresh } ] command to check the number of sent and received PIM-IPv6 control messages.
----End

This section describes how to configure control parameters of the PIM-DM State-Refresh
message.
12.6.1 Estalishing the Configuration Task

12.6.4 Configuring the Period for Receiving the Next State-Refresh Message
12.6.5 Configuring the TTL Value of a State-Refresh Message
12.6.1 Estalishing the Configuration Task
By default, a PIM-DM interface is in the forwarding state. The pruned interface continues to
forward packets after the prune timer times out. In the PIM-DM network, periodically flooding
State-Refresh messages can update the prune timer and maintain the suppressed state of the
prune interface.
NOTE
Before adjusting control parameters for State-Refresh, complete the following tasks:

Data Preparation
To adjust control parameters for State-Refresh, you need the following data.
No. Data
1 Interval for sending PIM State-Refresh messages
2 Period for waiting to receive the next State-Refresh message
3 TTL value used to forward State-Refresh messages
Context
Do as follows on all routers in the PIM-DM domain:
NOTE
By default, PIM-DM State-Refresh is enabled on an interface.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
undo pim ipv6 state-refresh-capable
State-Refresh is disabled.
The interface on which PIM-DM State-Refresh is disabled cannot forward any State-Refresh
message.
NOTE
You can run the pim state-refresh-capable command to re-enable the PIM-DM State-Refresh on the
interface.
----End
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
state-refresh-interval interval
The interval for sending PIM-IPv6 State-Refresh messages is set.
NOTE
The interval for sending PIM State-Refresh messages should be shorter than the timeout period for keeping
the Prune state. You can run the holdtime join-prune command to set the timeout period for keeping the
Prune state.
----End

12.6.4 Configuring the Period for Receiving the Next State-Refresh

Message
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
state-refresh-rate-limit interval
The period for waiting to receive the next State-Refresh message is set.
----End
12.6.5 Configuring the TTL Value of a State-Refresh Message
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
state-refresh-ttl ttl-value
The TTL value in the State-Refresh message is set.
----End

Procedure
----End
12.7 Adjusting Control Messages for Graft

This section describes how to configure control parameters of the PIM-DM Graft message.
12.7.2 Setting the Interval for Retransmitting Graft Messages
In the PIM-DM network, if State-Refresh is not enabled, the pruned interface can forward
packets only after the Prune timer times out. If State-Refresh is enabled, the pruned interface
may not continue to forward packets forever.
To enable new members in the network to quickly receive multicast data, the PIM-DM router
sends a Graft message through an upstream interface. After receiving the Graft message, the
upstream router immediately replies a Graft-Ack message and restores the forwarding of the
interface that receives the Graft message.
routers in the control of default values can work normally. In the NE80E/40E, users can adjust
NOTE

Before adjusting control parameters for graft, complete the following tasks:

Data Preparation
To adjust control parameters for graft, you need the following data.
No. Data
1 Interval for retransmitting Graft messages
12.7.2 Setting the Interval for Retransmitting Graft Messages
Context
If the local router does not receive any Graft-Ack message from the upstream router in the
specified time, the local router resends the Graft message.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim ipv6 timer graft-retry interval
The interval for retransmitting Graft messages is set.
----End
Procedure
l Run the display pim ipv6 grafts command to check the unacknowledged PIM-DM Graft
messages.

----End
12.8 Adjusting Control Messages for Assert

This section describes how to configure control parameters of the PIM-DM Assert message.
When a PIM-DM router receives multicast data through a downstream interface, this indicates
that other upstream routers exist in this network segment. The router sends an Assert message
through the downstream interface to take part in the assert election.
Routers in the control of default values can work normally. In the NE80E/40E, users can adjust
NOTE
Before adjusting control parameters for Assert, complete the following tasks:

Data Preparation
To adjust control parameters for asset, you need the following data.

No. Data
1 The period for keeping the Assert state
Context
NOTE

Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
The period for keeping the Assert state is set.

The router that fails in the election prohibits its downstream interface from forwarding
multicast data.
After the Holdtime timer times out, the downstream interface continues to forward
packets.
1. Run:
system-view

2. Run:

3. Run:
pim ipv6 holdtime assert interval

The router that fails in the election prohibits its downstream interface from forwarding
multicast data.
After the Holdtime timer times out, the downstream interface continues to forward
packets.
----End

Procedure
----End

This section describes how to configure PIM silent to prevent the malicious attack from a host.
12.9.2 Configuring PIM-IPv6 Silent

At the access layer, the router interface directly connected to hosts needs to be enabled with
PIM-IPv6. You can establish a PIM-IPv6 neighbor on the router interface to process various
PIM packets. The configuration, however, has the security vulnerability. When a host
maliciously generates PIM-IPv6 Hello packets and sends the packets in a large quantity, the
router may break down.
To avoid the preceding case, you can set the status of the router interface to PIM silent. When
the interface is in the PIM-IPv6 silent state, the interface is prohibited from receiving and
forwarding any PIM-IPv6 packet. All PIM-IPv6 neighbors and PIM-IPv6 state machines on the

interface are deleted. The interface then acts as the static DR, which takes effect immediately.
At the same time, MLD on the interface is not affected.
PIM silent is applicable only to the router interface directly connected to the host network
segment that is connected only to this router.
CAUTION
If PIM-IPv6 silent is enabled on the interface connected to a router, the PIM-IPv6 neighbor
If the host network segment is connected to multiple routers and PIM-IPv6 silent is enabled on
multiple router interfaces, the interfaces become static DRs. Therefore, multiple DRs exist in
this network segment, and a multicast fault occurs.
Before configuring PIM-IPv6 silent, complete the following tasks:
l Configuring PIM-DM
l Configuring MLD
Data Preparation
To configure PIM-IPv6 silent, you need the following data.
No. Data
1 Number of the router interface connected to hosts
Context
CAUTION
PIM silent is applicable only to the router interface directly connected to the host network
segment that can be connected to only one PIM router.
Do as follows on the router interface connected to the host network segment:
Procedure
Step 1 Run:

system-view
Step 2 Run:
Step 3 Run:
pim ipv6 silent
PIM-IPv6 silent is enabled.
After this function is enabled, the attacks from malicious hosts by sending Hello messages are
effectively prevented and the router is protected.
----End
Prerequisite
Procedure
----End
12.10 Maintaining PIM-DM

This section describes how to clear statistics of IPv6 PIM control messages and monitor the
running status of IPv6 PIM-DM.
12.10.2 Monitoring Running Status of PIM-DM
Context
CAUTION
The statistics of PIM-IPv6 control messages on an interface cannot be restored after you clear
them. So, confirm the action before you use the command.

Procedure
l Run the reset pim ipv6 control-message counters [ interface interface-type interface-
number ] command in the user view to clear statistics of PIM-IPv6 control messages on an
interface.
----End
12.10.2 Monitoring Running Status of PIM-DM
Context
status of PIM-DM.
Procedure
refresh } ] command in any view to check the statistics of sent and received PIM-IPv6
control messages.
l Run the display pim ipv6 grafts command in any view to check the unacknowledged PIM-
DM Graft messages.
[ verbose ] command in any view to check information about PIM-IPv6 interfaces.
interface-number | verbose ] * command in any view to check information about PIM-IPv6
neighbors.
l Run the following commands in any view to check the PIM-IPv6 multicast routing table.
none | register ] ] * [ outgoing-interface-number [ number ] ] [ | { begin | exclude |
include } regular-expression ]
----End

This section provides a configuration example of PIM-DM.

As shown in Figure 12-1, multicast is deployed in the experiment network. The integrated
Interior Gateway Protocol (IGP) is deployed in the network. The unicast routes work normally.
You are required to properly configure routers in the network to enable hosts to receive the Video
On Demand (VOD) information in multicast mode.
Figure 12-1 Networking diagram of configuring basic PIM-DM functions

Host A Host B
GE2/0/0
3001::1
POS1/0/0
2002::2 RouterB
POS2/0/0
Source 2002::1
GE1/0/0
2001::5 2001::1
RouterA
POS3/0/0
2003::1
POS1/0/0
2003::2 RouterC
GE2/0/0
4001::1
Host C Host D
The network is a small-scale experiment network, therefore, PIM-DM is adopted to configure
multicast. In this example, the host network segment is connected to only one router, therefore,
PIM silent can be used to prevent the Hello message attack. The configuration roadmap is as
follows:
1. Enable multicast on routers.
2. Enable PIM-DM on interfaces.
3. Enable PIM silent and MLD on the router interface connected to hosts.
Data Preparation
l The address of the group G is FF0E::1.

l The address of the source S is 2001::5.

l The version number of MLD run on the router and hosts is 1.
Procedure
Step 1 Enable IPv6 multicast on all routers and PIM-DM on all interfaces.
# Enable IPv6 multicast on Router A and PIM-DM on all interfaces. The configurations of Router
B and Router C are the same as the configuration of Router A, and are not mentioned here.
[RouterA-GigabitEthernet1/0/0] pim ipv6 dm
[RouterA-Pos2/0/0] pim ipv6 dm
[RouterA-Pos3/0/0] pim ipv6 dm
Step 2 Enable PIM silent and MLD on the router interface connected to hosts.
[RouterB-GigabitEthernet2/0/0] pim ipv6 silent
[RouterB-GigabitEthernet2/0/0] mld enable
[RouterB-GigabitEthernet2/0/0] mld version 1
The configuration of Router C is the same as the configuration of Router B, and is not mentioned
here.
# Run the display pim ipv6 interface command to view the PIM-IPv6 configuration and running
status on the router interface. The display of the PIM-IPv6 configuration on Router A is as
follows:
<RouterA> display pim ipv6 interface
GE1/0/0 up 0 30 1 FE80::200:AFF:FE01:109
(local)
Pos2/0/0 up 1 30 1 FE80::A01:109:1(local)
Pos3/0/0 up 1 30 1 FE80::A01:109:2(local)
# Run the display pim ipv6 neighbor command to check the PIM-IPv6 neighbor relationship
between routers. The display of the PIM-IPv6 neighbor relationship on Router A is as follows:
<RouterA> display pim ipv6 neighbor
Neighbor Interface Uptime Expires Dr-Priority
FE80::A01:104:1 Pos2/0/0 00:04:16 00: 01:29 1
FE80::A01:105:1 Pos3/0/0 00:03:54 00 :01:17 1
# Run the display pim ipv6 routing-table command to view the PIM-IPv6 routing table on a
router. Assume that Host A joins multicast group G FF0E::1. Router B generates a (*, G) entry.
When multicast source S 2001::5 sends multicast packets to G, a Shortest Path Tree (SPT) is
generated through flooding-prune. The (S, G) entry exists on each router in the network. The
display is as follows:
<RouterA> display pim ipv6 routing-table

(2001::5, FF0E::1)
Protocol: pim-dm, Flag: LOC ACT
UpTime: 00:01:20
1: Pos2/0/0
Protocol: pim-dm, UpTime: 00:01:20, Expires: -
<RouterB> display pim ipv6 routing-table
(*, FF0E::1)
UpTime: 01:46:23
Upstream neighbor: FE80::A01:109:1
RPF prime neighbor: FE80::A01:109:1
Protocol: mld, UpTime: 01:46:23, Expires: never
(2001::5, FF0E::1)
UpTime: 00:02:19
Protocol: pim-dm, UpTime: 00:02:19, Expires: -
<RouterC> display pim ipv6 routing-table
(2001::5, FF0E::1)
UpTime: 00:02:19
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
#
undo shutdown
ipv6 enable
ospfv3 1 area 0.0.0.0
pim ipv6 dm
#
interface Pos2/0/0
undo shutdown
link-protocol ppp
clock master

ipv6 enable
pim ipv6 dm
#
interface Pos3/0/0
undo shutdown
link-protocol ppp
clock master
ipv6 enable
pim ipv6 dm
#
ospfv3 1
router-id 1.1.1.1
area 0.0.0.0
#
return
#
sysname RouterB
#
ipv6
#
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
pim ipv6 dm
#
undo shutdown
pim ipv6 dm
pim ipv6 silent
mld enable
mld version 1
#
ospfv3 1
router-id 2.2.2.2
area 0.0.0.0
#
return
#
sysname RouterC
#
ipv6
#
#
interface Pos1/0/0
undo shutdown
link-protocol ppp
pim ipv6 dm
#
undo shutdown
pim ipv6 dm

pim ipv6 silent

mld enable
mld version 1
#
ospfv3 1
router-id 3.3.3.3
area 0.0.0.0
#
return

13 PIM-SM (IPv6) Configuration
About This Chapter
This chapter describes the PIM-SM (IPv6) and SSM fundamentals and configuration steps, and
maintenance for PIM-SM functions, along with typical examples. PIM-SM in this chapter refers
to the IPv6 PIM-SM, unless otherwise specified.
This section describes the principle and concepts of PIM-SM (IPv6).
13.2 Configuring Basic PIM-SM (IPv6) Functions
13.4 Adjusting Control Parameters of a C-RP and a C-BSR
13.5 Adjusting Control Parameters for Maintaining Neighbors
This section describes how to configure control parameters of the PIM-SM Hello message.
13.6 Adjusting Control Parameters of Source Registering
This section describes how to configure control parameters of the PIM-SM Register message.
This section describes how to configure control parameters of the PIM-SM Join/Prune message.
13.8 Configuring Control Parameters for Assert
This section describes how to configure control parameters of the PIM-SM Assert message.
13.9 Adjusting Control Parameters for the SPT Switchover
This section describes how to configure control parameters of the PIM-SM SPT switchover.
13.10 Configuring PIM GR (IPv6)
This section describes how to configure PIM GR (IPv6).

This section describes how to configure PIM silent to prevent the malicious attack from a
malicious host.
13.12 Maintaining PIM-SM
This section describes how to clear IPv6 PIM-SM statistics and monitor the running status of
IPv6 PIM-SM.
This section provides the configuration example of PIM-IPv6-SM.


This section describes the principle and concepts of PIM-SM (IPv6).


In the IPv4 multicast applications, the Protocol Independent Multicast (PIM) is used to set
multicast routes between routers to replicate and forward multicast packets.
In IPv6 multicast applications, routers run PIM-IPv6. The functions and principles of PIM-IPv6
are similar to the functions of PIM-IPv4.
PIM-IPv6 consists of the following separate protocols:
l PIM-DM: indicates the Protocol Independent Multicast-Dense Mode. PIM-DM is
applicable to a small-scale network with densely-distributed members. The network adopts
the Any-Source Multicast (ASM) model to implement multicast services.
l PIM-SM: indicates the Protocol Independent Multicast-Sparse Mode. PIM-SM is
applicable to a large-scale network with sparsely-distributed members. The network adopts
the ASM and Source-Specific Multicast (SSM) models to implement multicast services.
NOTE
l This chapter describes only the PIM-SM configuration in the IPv6 network. PIM-SM in this chapter
refers to the IPv6 PIM-SM, unless otherwise specified.
l For the configuration of PIM-DM, refer to the chapter PIM-DM (IPv6) Configuration in the
HUAWEI NetEngine80E/40E Router Configuration Guide - IP Multicast.
l For details of ASM and SSM models, refer to the chapter "IP Multicast Overview" in the HUAWEI
NetEngine80E/40E Router Feature Description - IP Multicast.
Embedded-RP
Based on PIM-SM (IPv4), embedded-Rendezvous Point (embedded-RP) is added in PIM-SM
(IPv6). The embedded-RP is a method of obtaining an RP. The function of the embedded-RP is
the same as that of the static RP and the dynamic RP.
Static RP
You can specify the static RP on all routers in the PIM-SM domain. When a dynamic RP exists
in the domain, the dynamic RP is preferred by default, but you can configure the static RP to be
preferred.
Dynamic RP
You can specify a C-RP in a BSR domain, adjust the priority for C-RP election, adjust the lifetime
of the advertisement message on the BSR received from the C-RP, adjust the interval for the C-

RP to advertise advertisement messages, and specify an Access Control List (ACL) to limit the
range of the multicast groups served by the C-RP.
BSR
You can specify a Candidate-BSR (C-BSR) in a BSR domain, adjust the hash mask length used
by the C-RP for C-RP election, adjust the priority for BSR election, and adjust the legal address
range of BSRs.
Controlling a Multicast Source

You can configure the filtering rules based on multicast source addresses to control a multicast
source.
BSR Administrative Domain

You can configure the service boundary of a BSR administrative domain and the boundary of
an administrative domain.
Adjusting Control Parameters for Maintaining PIM-SM Neighbors

l Time period for the neighbor to hold the reachable state
l Whether to accept the Hello messages with Generation IDs
l Maximum delay in triggering the sending of the Hello messages
l Priority for DR election
l DR switching delay
rules.
Adjusting Control Parameters for Source Registering

You can configure the policy to filter Register messages, and set the timeout period for being in
the register suppression state and interval for sending null Register messages by running related
commands.
Adjusting Control Parameters for Multicast Forwarding

You can adjust the control parameters for multicast forwarding, including:
l Interval for sending Join messages

l Time period for the downstream interface to keep the forwarding state
l Time for overriding the prune action
l Filtering join information in the Join/Prune messages
l Neighbor check function: checks whether the sent or received Join/Prune and Assert
messages are to or from a PIM neighbor. If not, stop sending these messages.


You can configure the period for keeping the Assert state of a router interface.
Adjusting Control Parameters for SPT Switchover

You can adjust the conditions of the SPT switchover and the interval for checking the forwarding
rate of multicast data.
PIM GR
The NE80E/40E supports the PIM GR function on the router with double MPUs. PIM GR
ensures normal multicast data forwarding during master-slave switchover of the router.

The interface acts as the static DR and immediately takes effect. At the same time, MLD on the
13.2 Configuring Basic PIM-SM (IPv6) Functions

13.2.3 Enabling Basic PIM-SM (IPv6) Functions
13.2.4 (Optional) Configuring an Embedded-RP
A PIM-SM network can adopt the ASM and SSM models to provide multicast services for hosts.
The integrated components (including the RP) of the ASM model must be configured in the
network first. The SSM group address range is then adjusted as required.

NOTE
The SSM model needs to be supported by the Multicast Listener Discovery version 2 (MLDv2). If a host
must run MLDv1, configure MLD SSM mapping on the router interface.
Through MLD, a router knows the multicast group G that a user wants to join.
l If G is in the SSM group address range and the source S is specified when the user joins G
through MLDv2, the SSM model is used to provide multicast services.
l If G is in the SSM group address range and the router is configured with the (S, G) SSM
mapping rules, the SSM model is used to provide multicast services.
l If G is not in the SSM group address range, the ASM model is used to provide multicast
services.
In the PIM-SM network, the ASM model supports the following methods used to obtain an RP.
You can select at least one method to obtain an RP.
l Embedded-RP: By default, the embedded-RP is started. The range of groups served by the
embedded-RP is limited.
l Dynamic RP: To obtain a dynamic RP, select several routers in the PIM-SM domain and
configure them as C-RPs and C-BSRs, and then configure the BSR boundary on the
router interface on the boundary of the domain. Each router in the PIM-SM domain can
then automatically obtain the RP.
l Static RP: To obtain a static RP, manually configure the RP on each router in the PIM-SM
domain. For the large-scale PIM-IPv6 network, configuring a static RP is complicated. To
enhance the robustness and the operation management of the multicast network, the static
RP is usually used as the backup of the BSR-RP.
A multicast group may be in the service range of the embedded-RP, dynamic -RP and static RP
simultaneously. By default, the sequence used by routers to select an RP is embedded-RP>
dynamic RP > the static RP. If the static RP precedence is configured, the static RP is preferred.
Compared with all groups corresponding to an RP, different multicast groups correspond to
different RPs can reduce the load of a single RP and enhance the robustness of the network.
Before configure basic PIM-SM functions, complete the following task:

l Enable IPv6 function globally
Data Preparation
To configure basic PIM-SM functions, you need the following data.
No. Data
1 The range of groups served by the embedded-RP
2 The IP address of the static RP
3 ACL6 that defines the range of multicast groups served by a static RP
4 The priority of a C-RP

No. Data
5 ACL6 that defines the range of multicast groups served by a C-RP
6 The interval taken by a C-RP to send advertisement messages
7 Timeout period during which a BSR waits to receive the advertisement message from
a C-RP
8 Hash mask length of a C-BSR
9 The priority of a C-BSR
10 SSM group address range
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
IPv6 multicast routing is enabled in the public network instance.
----End
13.2.3 Enabling Basic PIM-SM (IPv6) Functions
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim ipv6 sm
PIM-SM (IPv6) is enabled.
After PIM-SM (IPv6) is enabled on interfaces, routers set up PIM-IPv6 neighbor relationship
with each other. The routers can then process protocol packets received from PIM-IPv6
neighbors.
You can run the undo pim ipv6 sm command to disable PIM-SM (IPv6) on an interface.
NOTE
PIM-DM (IPv6) and PIM-SM (IPv6) cannot be enabled on an interface simultaneously. The PIM mode on
all interfaces that belong to the same instance must be the same. When a router is deployed in a PIM-SM
(IPv6) domain, enable PIM-SM (IPv6) on all non-boundary interfaces.
----End
13.2.4 (Optional) Configuring an Embedded-RP
Context
Do as follows on all routers in the PIM-SM (IPv6) domain:
NOTE
This configuration is optional. By default, the embedded-RP is enabled. The group address range of the
embedded-RP is FF7x::/12, and the value of x ranges from 0, 3 to F.
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
embedded-rp [ basic-acl6-number | acl6-name acl6-name ]
The group address range of an embedded-RP is specified.
If the address range defined by ACL6 is wider than the default group address range of an
embedded-RP, the embedded-RP is valid for the intersection part of the two address ranges.
NOTE
The group address scope of the embedded-RP on all routers in the PIM-SM (IPv6) domain must be the
same. You can run the undo embedded-rp command to shut down the embedded-RP.
----End

Context
CAUTION
Configuring a static RP and a BSR-RP in the PIM-SM simultaneously may cause a network
fault. Therefore, confirm the action before you perform this configuration.
If the static RP is not required in this PIM-SM network, this configuration is not necessary.
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
static-rp rp-address [ basic-acl6-number | acl6-name acl6-name ] [preferred ]
A static RP is specified.
l rp-address: specifies the static RP address.

l basic-acl6-number | acl6-name acl6-name: specifies the number of the ACL. This basic ACL
defines the scope of groups served by the static RP. When the scopes of multicast groups
that multiple static RP serves overlap, the static RP with the highest IP address acts as the
RP.
l preferred: indicates that the static RP takes precedence. The C-RP is configured in the
network at the same time. After preferred is set, routers prefer the static RP. Otherwise,
routers prefer the C-RP.
Multiple static RPs can be configured by using this command repeatedly, but the same ACL
cannot correspond to multiple static RPs. If the ACL is not configured, only one static RP can
be configured.
NOTE
The same static-rp command must be used on all routers in the PIM-SM domain.
----End


Context
CAUTION
This configuration is applicable only to the dynamic RP. If the dynamic RP is not used in this
network, this configuration is not necessary.
Do as follows on routers that may become RP in the PIM-SM domain:
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
c-rp ipv6-address [ group-policy { basic-acl6-number | acl6-name acl6-name } |
priority priority | holdtime hold-interval | advertisement-interval adv-interval ]
*
The C-RP is configured.

l ipv6-address: specifies the IPv6 address of the interface where the C-RP resides. PM-SM
must be enabled on that interface.
l group-policy basic-acl6-number: specifies that the C-RP serves only the multicast group
matching ACL6. basic-acl-number: specifies the number of the basic ACL6. By default, the
C-RP serves all multicast groups.
l priority priority: specifies the priority for electing the C-RP. The greater the value, the lower
the priority. By default, the priority is 192.
NOTE
In the RP election, the C-RP with the highest priority (with the lowest priority value) succeeds. In case
of the same priority, the hash function is calculated, and the C-RP with the greatest hash value succeeds.
In case of the same priority and the same hash value, the C-RP with the highest IP address succeeds.
l holdtime hold-interval: specifies the timeout period during which the BSR waits to receive
the advertisement message from the C-RP. By default, the value is 150s.
l advertisement-interval adv-interval: specifies the interval during which the C-RP sends
advertisement messages. By default, the value is 60s.
Step 4 Run:
c-bsr ipv6-address [ hash-length ]
A C-BSR is configured.

l ipv6-address: specifies the IPv6 address of the interface where the C-BSR resides. The
interface must be configured with PIM-SM.
l hash-length: specifies the length of the hash mask. According to the group address G, C-RP
address, and the value of hash-length, routers calculate the C-RPs that have the same priority
and want to serve G by operating hash functions, and compare the calculation results. The
C-RP with the greatest calculated value acts as the RP that serves G.
You can use the c-bsr hash-length hash-length command to set the global hash length of the
C-BSRs. The set hash length then applies to all the C-BSRs configured on the router.
----End
Context
NOTE
This configuration is optional. By default, the SSM group address range is FF3x::/32.
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
ssm-policy { basic-acl6-number | acl6-name acl6-name }
The SSM group address range is configured.
NOTE
Ensure that the SSM group address ranges of all routers in the network must be identical.
----End
Procedure
l Run the display pim ipv6 bsr-info command to check information about the BSR in the
PIM-SM (IPv6) domain.


l Run the display pim ipv6 rp-info [ ipv6-group-address ] command to check information
about RPs in the PIM-SM domain.
----End

All the configurations in this section are applicable to the ASM and SSM models.
PIM-IPv6 routers check the passing multicast data packets. By checking whether the data packets
match the filtering rule, the routers determine whether to forward the packets. That is, the
routers in the PIM domain act as filters. The filters help to control data flows, and limit
information obtained by downstream receivers.
NOTE
Routers under the control of default values can work normally. In the NE80E/40E, users can adjust related
parameters according to the actual environment. If there is no special requirement from the actual network,
it is recommended to use default values.
Before adjusting control parameters of a multicast source, complete the following tasks:

l Configuring Basic PIM-SM (IPv6) Functions

Data Preparation
To adjust control parameters of a multicast source, you need the following data.
No. Data
1 Keepalive period of a multicast source
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
The Keepalive period of a source is configured.

When the Keepalive period expires, the (S, G) entry becomes invalid.
----End
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6


Step 3 Run:
source-policy { acl6-number | acl6-name acl6-name }
are forwarded.
NOTE
l If acl6-number | acl6-name acl6-name is specified in the source-policy command and ACL rules are
l If acl6-number | acl6-name acl6-name is specified in the source-policy command and no ACL rule is
l The source-policy command does not filter the static (S, G) entries.
----End

Procedure
----End
13.4 Adjusting Control Parameters of a C-RP and a C-BSR

13.4.2 Adjusting Control Parameters of a C-RP
13.4.3 Adjusting Control Parameters of a C-BSR
13.4.4 Configuring the BSR Service Boundary
13.4.5 (Optional) Configuring the Range of Legal BSR addresses

13.4.6 (Optional) Configuring the Range of Legal C-RP Addresses

To enhance the performance of an RP or a BSR, you can adjust control parameters of C-RPs
and C-BSRs by using related commands.
NOTE
parameters according to the actual environment. If there is no special requirement of the actual network,
it is recommended to use default values.
Before adjusting control parameters of a C-RP and a C-BSR, complete the following tasks:

Data Preparation
To adjust control parameters of a C-RP and C-BSR, you need the following data.
No. Data
1 Priority of the C-RP
2 Interval during which the C-RP sending advertisement messages
3 Timeout period during which the BSR waits to receive the advertisement message
from the C-RP
4 Hash mask length of the C-BSR
5 Priority of the C-BSR
6 Interval during which the C-BSR sends Bootstrap messages
7 Period for keeping the Boostrap message received from the BSR
8 ACL6 that defines the legal BSR address range
9 ACL6 that defines the legal C-RP address range
13.4.2 Adjusting Control Parameters of a C-RP

Context
Do as follows on the router on which the C-RP is configured:
NOTE
Do as follows on the router that has been configured with a C-RP. This configuration is optional. If there
is no special requirement, default values are recommended.
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
c-rp priority priority
The priority of the C-RP is configured.
Step 4 Run:
c-rp advertisement-interval interval
The interval during which the C-RP sends advertisement messages is configured.
Step 5 Run:
c-rp holdtime interval
The period for keeping the advertisement message received from the C-RP is configured.
This period must be longer than the interval during the C-RP sends advertisement messages.
The C-RP periodically sends advertisement messages to the BSR. After receiving the
advertisement messages, the BSR obtains the Holdtime period from the messages. During the
Holdtime period, the advertisement message is valid. When the Holdtime period expires, the C-
RP ages.
----End
13.4.3 Adjusting Control Parameters of a C-BSR
Context
Do as follows on the router on which the C-BSR is configured:
NOTE
Do as follows on the router that has been configured with a C-BSR. This configuration is optional. If there
is no special requirement, default values are recommended.

Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
c-bsr hash-length hash-length
The hash mask length of the C-BSR is configured.
Step 4 Run:
c-bsr priority priority
The priority of the C-BSR is configured.
Step 5 Run:
c-bsr interval interval
The interval during which the C-BSR sends Bootstrap messages is configured.
Step 6 Run:
c-bsr holdtime interval
The period for keeping the Bootstrap received from the BSR is configured.
The BSR periodically sends a Bootstrap message to the network. After receiving the Bootstrap
message, the C-BSR keeps the message for a certain period. During the period, the BSR election
stops temporarily. If the Holdtime period expires, a new round of BSR election is triggered
among C-BSRs.
NOTE
Ensure that the period for keeping the Bootstrap message received from the BSR and the interval during
which the BSR sends Bootstrap messages must be the same on all C-BSRs in the PIM-IPv6 domains. The
period for keeping the Bootstrap message received from the BSR must be longer than the interval during
which the BSR sending Bootstrap messages.
----End
13.4.4 Configuring the BSR Service Boundary
Context
Do as follows the routers that may become BSR boundaries:
NOTE
The BSR boundary is used to divide a PIM-SM (IPv6) domain. routers outside the BSR boundary do not
take part in the process of multicast forwarding in the PIM-SM (IPv6) domain. This configuration is
optional. By default, all PIM-SM (IPv6) routers in the network can receive BSR messages.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim ipv6 bsr-boundary
The BSR boundary is configured.
BSR messages cannot pass the BSR boundary.
----End
13.4.5 (Optional) Configuring the Range of Legal BSR addresses
Context
NOTE
This configuration is optional. By default, source addresses of the received BSR packets are not checked,
and all received BSR packets are received.
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
Step 3 Run:
bsr-policy { basic-acl6-number | acl6-name acl6-name }
The range of legal BSR addresses is limited.
After receiving an IP packet carrying a Bootstrap message, a router checks the source address
of the IP packet. If the source address is not in the range of legal BSR addresses, the packet is
discarded. The BSR spoofing is thus avoided.
basic-acl6-number specifies the number of the basic ACL. The ACL defines the filtering policy
for the source addresses of BSR messages.
----End

13.4.6 (Optional) Configuring the Range of Legal C-RP Addresses
Context
Do as follows on all C-BSRs in the PIM-SM domain:
NOTE
This configuration is optional. By default, the C-RP address carried in the received advertisement message
and the address of the group that the C-RP serves are not checked, and all received advertisement messages
are received and added to the RP-set.
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
crp-policy { advanced-acl6-number | acl6-name acl6-name }
The range of legal C-RP addresses and the range of groups that C-RPs serve are limited. When
a router receives an advertisement message, the router checks the C-RP address and the address
of the group that the C-RP serves in the message. The advertisement message is received and
added to the RP-set only when the C-RP address and the group address are in the legal address
range. The C-RP spoofing is thus avoided.
{ advanced-acl6-number | acl6-name acl6-name }: specifies the number of the advanced ACL.
The ACL defines the filtering policy to limit the range of legal C-RP and the range of groups
that the C-RP serves.
----End

Procedure
l Run the display pim ipv6 bsr-info command to check information about BSRs in the PIM-
SM domain.
l Run the display pim ipv6 rp-info [ ipv6-group-address ] command to check information
about RPs in the PIM-SM domain.
----End
13.5 Adjusting Control Parameters for Maintaining

Neighbors
This section describes how to configure control parameters of the PIM-SM Hello message.


13.5.2 Configuring Control Parameters for Maintaining PIM Neighbors
The configuration in this section is applicable to both the ASM model and the SSM model.
The PIM routers send Hello messages to each other to establish the neighbor relationship,
negotiate the control parameters, and elect a DR.
The router can work normally by default. The NE80E/40E allows the users to adjust the
parameters as required.
NOTE
It is recommended to adopt the default value if there is no special requirement.
Before adjusting control parameters for maintaining neighbors, complete the following tasks:

Data Preparation
To adjust control parameters for maintaining neighbors, you need the following data.
No. Data
1 Priority for DR election
2 Timeout period for waiting to receive Hello message from neighbors
5 DR switching delay, that is, the remaining time for the entries to turn invalid after a
DR interface no longer functions as a DR.

13.5.2 Configuring Control Parameters for Maintaining PIM

Neighbors
Context
Do as follows on the PIM-SM (IPv6) router:
NOTE
The configuration of the control parameters for maintaining PIM neighbors involves the following cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
The interval for sending Hello messages is configured.

4. Run:
The period for keeping the reachable state of a neighbor is configured.

If the local router does not receive any Hello message from the neighbor after the
period expires, the local router considers that the neighbor is unreachable.
1. Run:
system-view

2. Run:

3. Run:
pim ipv6 timer hello interval

4. Run:
pim ipv6 triggered-hello-delay interval

After the maximum delay is set, the conflict caused by multiple PIM-IPv6 routers
simultaneously sending Hello message is avoided.
5. Run:
pim ipv6 hello-option holdtime interval
The period for keeping the reachable state of a neighbor is configured.

If the local router does not receive any Hello message from the neighbor after the
period expires, the local router considers that the neighbor is unreachable.
6. Run:
The Generation ID option is set in received Hello message.

The Hello message without the Generation ID option is refused.
----End
Context
NOTE
The configuration of the control parameters for electing a DR involves the following cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
pim ipv6 hello-option dr-priority priority
The priority for the DR election is configured.

On the shared network segment where all PIM-IPv6 routers support the DR priority,
the router interface with highest priority acts as the DR. In the case of the same priority,
the router interface with the highest IP address acts as the DR. If a minimum of one
PIM-IPv6 router does not support the DR priority, the router interface with the highest
IP address acts as the DR.
1. Run:

system-view

2. Run:

3. Run:
pim ipv6 hello-option dr-priority priority
The priority for the DR election is configured.

On the shared network segment where all PIM-IPv6 routers support the DR priority,
the router interface with highest priority acts as the DR. In the case of the same priority,
the router interface with the highest IP address acts as the DR. If a minimum of one
PIM-IPv6 router does not support the DR priority, the router interface with the highest
IP address acts as the DR.
4. Run:
pim ipv6 timer dr-switch-delay interval
The DR switching delay is configured and the value of the delay is set.
When an interface changes from a DR to a non-DR, the existing routing entries are
valid until the maximum delay expires.
----End
Context
Do as follows on the router running IPv6 PIM-SM:
NOTE

Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
hello-option neighbor-tracking
The function of tracking downstream neighbors is enabled.

NOTE
The function of tracking downstream neighbors cannot be implemented unless all the routers
running IPv6 PIM-SM in the shared network segment are enabled with this function.
1. Run:
system-view

2. Run:

3. Run:
pim ipv6 hello-option neighbor-tracking
The function of tracking downstream neighbors is enabled.
NOTE
The function of tracking downstream neighbors cannot be implemented unless all the routers
running IPv6 PIM-SM in the shared network segment are enabled with this function.
----End
Context
To prevent some router from being involved in the PIM protocol and prevent this router from
becoming the DR, filtering PIM neighbors is required.
Do as follows on the router enabled with IPv6 PIM-SM:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim ipv6 neighbor-policy { basic-acl6-number | acl6-name acl6-name }

NOTE
When configuring the PIM neighbor filtering function on the interface, you must also configure the
neighbor filtering function correspondingly on the router that sets up the neighbor relationship with the
interface.
----End

Procedure
----End
13.6 Adjusting Control Parameters of Source Registering

This section describes how to configure control parameters of the PIM-SM Register message.
13.6.2 Configuring Rules for Filtering PIM-SM (IPv6) Register Messages
13.6.3 Configuring PIM-SM (IPv6) Registering Suppression

This section describes how to configure the control parameters of the source registering through
In a PIM-SM network, the DR directly connected to the source S encapsulates the received
multicast data in a Register message and unicasts the Register message to the RP. The RP then
decapsulates the message, and forwards the multicast data to receivers along the RPT.
After the SPT switchover on the RP is complete, the multicast data reaches the RP along the
source tree in the multicast mode. The RP sends a Register-Stop message to the DR at the source
side. The DR then stops sending Register messages and enters the suppressed state. In the register
suppression period, the DR periodically sends a Probe message (null Register message) to notify
the RP that the multicast source is still in the active state. After the register suppression expires,
the DR resends the Register message carrying a multicast data packet.
NOTE
parameters according to the specific network environment. If there is no special requirement, default values
are recommended.

Before adjusting control parameters of source registering, complete the following tasks:
Data Preparation
To adjust control parameters of source registering, you need the following data.
No. Data
1 ACL6 rules used by the RP to filter Register messages
2 Timeout period for keeping the suppressed state of the source registering
3 Interval for sending null Register messages to the RP
13.6.2 Configuring Rules for Filtering PIM-SM (IPv6) Register

Messages
Context
Do as follows on routers that may become RPs:
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
register-policy { advanced-acl6-number | acl6-name acl6-name }
The rules for filtering Register messages are set.

The RP accepts or rejects to a Register message according to the rules.
----End
13.6.3 Configuring PIM-SM (IPv6) Registering Suppression
Context
Do as follows on the router that may become the DR at the source side:

Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
register-suppression-timeout interval
The timeout period for keeping the suppressed state of the registering is set.
Step 4 Run:
probe-interval interval
The interval for sending null Register messages is set.
----End

Procedure
----End

This section describes how to configure control parameters of the PIM-SM Join/Prune message.
13.7.2 Configuring Control Parameters for Keeping the Forwarding Relationship

Unless otherwise specified, the configurations in this section are applicable to both the ASM
model and the SSM model.
When the first member of a group appears on a router, the router sends a Join message through
the upstream interface to require the upstream router to forward packets to this network segment.

When the last member of a group on the router leaves its group, the router sends the Prune
message through the upstream interface to request the upstream router to perform the prune
action. After receiving the Prune message, the upstream interface stops forwarding packets to
this network segment. If other downstream routers exist in this network segment, they must send
the Join message to override the prune action.
In the ASM model, the routers periodically send Join messages to the RP in case the RPT branch
is deleted because of timeout.
NOTE
are recommended.
Before adjusting control parameters for forwarding, complete the following tasks:
Data Preparation
To adjust control parameters for forwarding, you need the following data.
No. Data
2 Period of overriding the Prune action
4 Interval for sending Join messages
5 Number or name of the ACL used to filter join information
6 Whether to perform neighbor check on the received or sent Join/Prune messages and
Assert messages
13.7.2 Configuring Control Parameters for Keeping the Forwarding

Relationship
Context

NOTE
The configuration of the control parameters for maintaining the forwarding relationship involves the
following cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:

4. Run:
The value of the Holdtime filed in the sent Join/Prune message is set.
The Holdtime period is the period for keeping the Forwarding/Prune state of the
downstream interface.
1. Run:
system-view

2. Run:

3. Run:
pim ipv6 timer join-prune interval

4. Run:
pim ipv6 holdtime join-prune interval
The value of the Holdtime filed in the sent Join/Prune message is set.
The Holdtime period is the period for keeping the Forwarding/Prune state of the
downstream interface.
5. Run:
The Generation ID option is set in received Hello message.

The Hello message without the Generation ID option is refused.

The change of the Generation ID in the Hello message received from the upstream
neighbor indicates that the upstream neighbor is lost or the status of the upstream
neighbor has changed.
----End
Context
The Hello message carries lan-delay ( which indicates the delay for transmitting prune message )
and override-interval ( which indicates the interval for overriding a prune ). The relationship
between lan-delay, override-interval, and PPT is that lan-delay + override-interval = PPT. Prune-
Pending Timer (PPT) indicates the delay from the time when a router receives the Prune message
from the downstream interface to the time when the router performs the prune action to suppress
the forwarding of the downstream interface. If the router receives a Join message from a
downstream router within the PPT, the router does not perform the prune action.
NOTE
The configuration of the control parameters of prune involves the following cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
The delay of transmitting messages in a LAN is set.

4. Run:
The period for overriding the prune action is set.

When a router receives a Prune message through an upstream interface, it indicates
that another downstream router exists in the LAN. If the router still needs to receive
the multicast data, the router must send a Join message to the upstream within the
override-interval.

1. Run:
system-view

2. Run:

3. Run:
pim ipv6 hello-option lan-delay interval

4. Run:
pim ipv6 hello-option override-interval interval
The period for overriding the prune action is set.
----End
Context
A Join/Prune message received by an interface may contain both join information and prune
information. You can configure the router to filter join information based on ACL6 rules. The
router then creates PIM entries for only the join information matching ACL6 rules, which can
prevent illegal users from accessing the group.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
pim ipv6 join-policy { asm { basic-acl6-number | acl6-name acl6-name } | ssm
{ advanced-acl6-number | acl6-name acl6-name } }
Join information filtering is configured.
----End

Context
By default, checking whether the Join/Prune message and Assert messages are sent to or received
from a PIM neighbor is not enabled.
If PIM neighbor checking is required, it is recommended to configure the neighbor checking
function on the devices connected with user devices rather than on the internal devices of the
network. Then, the router checks whether the Join/Prune and Assert messages are sent to or
received from a PIM neighbor. If not, the router drops the messages.
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6
The IPv6 PIM view is displayed.

Step 3 Run:
neighbor-check { receive | send }
The neighbor check function is configured.

You can specify both receive and send to enable the IPv6 PIM neighbor check function for both
the received and sent Join/Prune messages and Assert messages.
----End

Procedure
----End

13.8 Configuring Control Parameters for Assert

This section describes how to configure control parameters of the PIM-SM Assert message.
The configurations in this section are applicable to both the ASM model and the SSM model.
When a PIM-SM router receives multicast data through the downstream interface, this indicates
that other upstream routers exist in this network segment. The router sends an Assert message
through the downstream interface to take part in the assert election.
NOTE
routers under the control of default values can work normally. In the NE80E/40E, you can adjust related
are recommended.
Before adjusting control parameters for assert, complete the following tasks:

Data Preparation
To adjust control parameters for asset, you need the following data.
No. Data
1 The period for keeping the Assert state
Context
Do as follows on all routers in the PIM-SM (IPv6) domain:

NOTE
The configuration of control parameters for Assert involves the following cases:
Procedure
1. Run:
system-view

2. Run:
pim-ipv6

3. Run:
The period for keeping the Assert state is configured.
multicast data in this period. After the period expires, the router restores the forwarding
of the downstream interface.
1. Run:
system-view

2. Run:

3. Run:
pim ipv6 holdtime assert interval
multicast data in this period. After the period expires, the router restores the forwarding
of the downstream interface.
----End
Procedure

----End
13.9 Adjusting Control Parameters for the SPT Switchover

This section describes how to configure control parameters of the PIM-SM SPT switchover.
13.9.2 (Optional) Configuring the Interval for Checking the Forwarding Rate of Multicast Data
13.9.3 (Optional) Adjusting Conditions of the SPT Switchover

This section describes how to configure the control parameters of the SPT switchover through
In PIM-SM forwarding, each multicast group corresponds to an RPT. At first, all multicast
sources encapsulate data in Register messages, and send the messages to the RP in the unicast
mode. The RP decapsulates the messages and forwards the data along the RPT.
Forwarding multicast data by using the RPT has the following disadvantages:
l The DR at the source side and the RP need to encapsulate and decapsulate packets.
l The forwarding path may not be the shortest path from the source to receivers.
l Heavy data traffic increases the load of the RP, and may cause a fault.
The solution to the preceding disadvantages is that:

l SPT switchover triggered by the RP: The RP sends a Join message to the source, and
establishes a multicast route along the shortest path from the DR at the source side to the
RP. The subsequent packets are forwarded along the path.
l SPT switchover triggered by the DR at the receiver side: The DR at the receiver side checks
the forwarding rate of multicast data. If the DR finds that the rate exceeds the threshold,
the DR triggers the SPT switchover immediately. The DR sends a Join message to the

source, and establishes a multicast route along the shortest path from the DR at the source
side to the DR at the receiver side. The subsequent packets are forwarded along the path.
NOTE
routers under the control of default values can work normally. In the NE80E/40E, users can adjust related
are recommended.
Before adjusting control parameters for the SPT switchover, complete the following tasks:
Data Preparation
To adjust control parameters for the SPT switchover, you need the following data.
No. Data
1 Forwarding rate threshold that the DR at the receiver side switches packets from the
RPT to the SPT
2 Group filtering policy and sequence policy for the RPT-to-SPT switchover
3 Interval for checking the forwarding rate threshold of multicast data before RPT-to-
SPT switchover
13.9.2 (Optional) Configuring the Interval for Checking the

Forwarding Rate of Multicast Data
Context
Do as follows on the router that may become the DR at the receiver side:
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
timer spt-switch interval
The interval for checking the forwarding rate of multicast data is set.

By default, the DR at the receiver side performs SPT switchover after receiving the first multicast
data packet.
NOTE
Before configuring the timer spt-switch command, run the spt-switch-threshold command to set the
threshold of the rate that will trigger SPT switchover. Otherwise, timer spt-switch does not take effect.
----End
13.9.3 (Optional) Adjusting Conditions of the SPT Switchover
Context
Do as follows on the router that may become the DR at the receiver side:
NOTE
This configuration is optional. By default, the RP and the DR at the receiver side immediately perform the
SPT switchover after receiving the first multicast data packet.
Procedure
Step 1 Run:
system-view

Step 2 Run:
pim-ipv6

Step 3 Run:
spt-switch-threshold { traffic-rate | infinity } [ group-policy { basic-acl6-
number | acl6-name acl6-name } [ order order-value ] ]
Conditions of the SPT switchover are adjusted.

l traffic-rate: specifies the rate threshold of SPT switchover.
l infinity: indicates that the SPT switchover is not triggered.
l group-policy { basic-acl6-number | acl6-name acl6-name } [ order order-value]: specifies
the range of the multicast groups that use the threshold. By default, the threshold is applicable
to all multicast groups.
----End

Procedure
----End

13.10 Configuring PIM GR (IPv6)

This section describes how to configure PIM GR (IPv6).
13.10.2 Configuring PIM GR (IPv6)
In some multicast applications, the router may need to perform active/standby switchover. After
active/standby switchover, the new active main control board deletes the forwarding entries on
the interface board and re-learns the PIM routing table and multicast routing table. During this
process, multicast traffic is interrupted.
In the PIM-SM/SSM network, PIM Graceful Restart (GR) can be applied to the router with dual
main control boards to ensure normal multicast traffic forwarding during active/standby
switchover.
The active main control board of the router backs up PIM routing entries and Join/Prune
information to be sent upstream to the standby main control board. The interface board keeps
forwarding entries. Therefore, after active/standby switchover, the router can actively and fast
send Join messages upstream to maintain the Join state of the upstream. Then, the PIM protocol
sends Hello messages carrying new Generation ID to all routers enabled with PIM-SM. When
the downstream router finds that the Generation ID of its neighbor changes, it sends a Join/Prune
message to the neighbor for re-creating routing entries, thereby ensuring non-stop forwarding
of multicast data on the forwarding plane.
If a dynamic RP is used on the network, after receiving a Hello message with the Generation ID
being changed, the DR or candidate DR unicasts a BSM message to the router performing active/
standby switchover and the router learns and restores RP information based on the received BSM
message. If the router has not leant any RP information from the BSM messages, it obtains the
RP information from the Join/Prune message received from the downstream router and re-creates
NOTE
PIM GR is applicable to PIM-SM/SSM networks.
Before configuring PIM GR, complete the following task:
l Configuring a unicast routing protocol and enabling unicast GR
Data Preparation
To enable PIM GR, you need the following data.

No. Data
1 Unicast GR period
2 PIM-IPv6 GR period
13.10.2 Configuring PIM GR (IPv6)
Context
Do as follows on the router enabled with PIM SM (IPv6).
Procedure
Step 1 Run:
system-view
Step 2 Run:
pim-ipv6
The IPv6 PIM view is displayed.
Step 3 Run:
graceful-restart
PIM GR is enabled.

graceful-restart period period
The PIM GR period is set.
By default, the PIM GR period is 120 seconds.
----End
Procedure
Step 1 Run the following commands to check PIM routing table.
l display pim ipv6 routing-table [ ipv6-source-address [ mask mask-length ] | ipv6-group-
address [ mask mask-length ] | flags { act | del | exprune | ext | loc | niif | nonbr | none |
rpt | sg_rcvr | sgjoin | spt | swt | wc | upchg } | fsm | incoming-interface [ interface-type
interface-number| register ] | mode { dm | sm | ssm } | outgoing-interface { exclude |
include | match } [ interface-type interface-number | none | register ] ] * [ outgoing-
interface-number [ number ] ]

l display pim ipv6 routing-table brief [ ipv6-source-address [ mask mask-length ] | ipv6-

group-address [ mask mask-length ] | incoming-interface { interface-type interface-
number | register } ] *
----End

This section describes how to configure PIM silent to prevent the malicious attack from a
malicious host.
At the access layer, the router interface directly connected to hosts needs to be enabled with
PIM-IPv6. You can establish the PIM-IPv6 neighbor relationship on the router interface to
process various PIM-IPv6 packets. The configuration, however, has the security vulnerability.
When a host maliciously generates PIM-IPv6 Hello packets and sends the packets in large
quantity, the router may break down.
To avoid the preceding case, you can set the status of the router interface to PIM-IPv6 silent.
When the interface is in the PIM-IPv6 silent state, the interface is prohibited from receiving and
forwarding any PIM-IPv6 packet. All PIM-IPv6 neighbors and PIM-IPv6 state machines on the
interface are deleted. The interface acts as the static DR and immediately takes effect. At the
same time, MLD on the interface is not affected.
To enable PIM-IPv6 silent, the network environment must meet the following conditions:
l The network supports IPv4 and IPv6.

l The PIM-IPv6 silent is applicable only to the router interface directly connected to the host
network segment that is connected only to this router.
CAUTION
If PIM-IPv6 silent is enabled on the interface connected to a router, the PIM-IPv6 neighbor
If the host network segment is connected to multiple routers and PIM-IPv6 silent is enabled on
multiple router interfaces, the interface become static DRs. Therefore, multiple DRs exist in this
network segment, and a multicast fault occurs.
Before configuring PIM-IPv6 silent, complete the following tasks:


l Configuring PIM-SM
l Configuring MLD
Data Preparation
To configure PIM-IPv6 silent, you need the following data.
No. Data
1 The number of the router interface connected to hosts
Context
CAUTION
PIM-IPv6 silent is applicable only to the router interface connected to the host network segment
that can be connected to only one PIM-IPv6 router.
Do as follows on the router interface connected to the host network segment:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
pim ipv6 silent
PIM-IPv6 silent is enabled.

After this function is enabled, the Hello packet attack of malicious hosts is effectively prevented
and the connected routers are protected.
----End

Prerequisite

Procedure
----End
13.12 Maintaining PIM-SM

This section describes how to clear IPv6 PIM-SM statistics and monitor the running status of
IPv6 PIM-SM.
13.12.1 Clearing Statistics of PIM-IPv6 Control Messages
13.12.2 Clearing the PIM Status of the Specified Downstream Interfaces of PIM Entries
13.12.1 Clearing Statistics of PIM-IPv6 Control Messages

Context
CAUTION
The statistics of PIM-IPv6 control messages on an interface cannot be restored after you clear
it. Therefore, confirm the action before you use the command.
Procedure
l Run the reset pim ipv6 control-message counters [ interface interface-type interface-
number ] command in the user view to clear statistics of PIM-IPv6 control messages on an
interface.
----End
13.12.2 Clearing the PIM Status of the Specified Downstream

Interfaces of PIM Entries
Context
CAUTION
Clearing PIM status of the downstream interfaces may trigger the sending of corresponding Join/
Prune messages, which affects multicast services.
Using the following command can clear join information about illegal users, and clear the PIM
status of the specified interface in a specified entry, such as PIM Join/Prune status and Assert
status.

The command cannot be used to clear the MLD or static group join status on a specified interface.
Procedure
Step 1 After confirming that PIM status of the specified downstream interfaces of the specified PIM
entry need to be cleared, run the reset pim ipv6 routing-table group ipv6-group-address
mask ipv6-group-mask-length source ipv6-source-address interface interface-type interface-
number command in the user view.
----End
Context
status of PIM-SM.
Procedure
refresh } ] command in any view to check the number of sent and received PIM-IPv6
control messages.
l Run the display pim ipv6 bsr-info command in any view to check information about the
BSR.
l Run the display pim ipv6 claimed-route [ ipv6-source-address ] command in any view
to check unicast routing information used by (S, G) and (*, G) entries in the PIM-SM routing
table.
l Run the display pim ipv6 rp-info [ ipv6-group-address ] command in any view to check
information about the RP to which the multicast group corresponds.
l Run the display pim ipv6 grafts command in any view to check the unacknowledged PIM-
IPv6 Graft messages.
[ verbose ] command in any view to check information about PIM-IPv6 interfaces.
interface-number | verbose ] * command in any view to check information about PIM-IPv6
neighbors.
l Run the following commands in any view to check the PIM-IPv6 multicast routing table.
----End


This section provides the configuration example of PIM-IPv6-SM.
13.13.1 Example for Configuring Basic PIM-SM functions

13.13.2 Example for Configuring PIM GR (IPv6)
13.13.1 Example for Configuring Basic PIM-SM functions
As shown in Figure 13-1, multicast services are deployed in the Internet Service Provider (ISP)
network. The integrated Interior Gateway Protocol (IGP) is deployed in the network. The unicast
routes work normally and are connected to the Internet. You are required to properly configure
routers in the network to enable hosts to receive the Video On Demand (VOD) information in
multicast mode.
Figure 13-1 Networking diagram of configuring basic PIM-SM functions
RouterB HostA
GE2/0/0
3001::1
POS1/0/0
2002::2
POS3/0/0 HostB
2004::1
POS2/0/0
2002::1 POS2/0/0
RouterA 2003::1 2004::2
POS3/0/0 RouterD
GE1/0/0 POS1/0/0
2001::1 POS4/0/0 2003::2 POS3/0/0
Source 2006::1 2005::1
2001::5
POS1/0/0
2005::2 HostC
Internet
GE2/0/0
4001::2 HostD
RouterC
The ISP network is accessed to the Internet. To expand services, PIM-SM is adopted to configure
multicast, and ASM and SSM models are used to provide multicast services. In this example,
the host network segment is connected to only one router, so PIM silent can be used to prevent
the Hello message attack. The configuration roadmap is as follows:


2. Enable PIM-SM on all router interfaces.
3. Configure the C-BSR and C-RP on routerD.
4. On Router A, configure the BSR boundary on the interface connected to the Internet.
5. Configure the SSM group address range on each router.
6. Enable PIM silent and MLD on the router interface connected to hosts.
Data Preparation
l The router interface connected to the host network segment runs MLDv2.
l The IPv6 global unicast address of the C-BSR and C-RP is 2004::2.
l The SSM group address range is FF3E::1/64.
Procedure
Step 1 Enable IPv6 multicast on all routers and IPv6 PIM-SM on all interfaces.
# Enable IPv6 multicast on Router A and PIM-SM on all interfaces.
# The configurations of Router B, Router C, and Router D are the same as the configuration of
Router A, and are not mentioned here.
# Run the display pim ipv6 interface command to check the PIM configuration and the running
information on each interface.
Step 2 Configure the C-BSR and C-RP.
# Configure the C-RP on Router D and specify the range of groups that the C-RP served.
[RouterD] acl ipv6 number 2001
[RouterD-acl6-basic-2001] rule permit source ff3e::1 64
[RouterD-acl6-basic-2001] quit
[RouterD] pim-ipv6
[RouterD-pim6] c-rp 2004::2 group-policy 2001
# Configure the C-BSR on Router D.

[RouterD-pim6] c-bsr 2004::2
[RouterD-pim6] quit
# Running the display pim ipv6 bsr-info command on a router to check information about the
BSR election. Take information about the BSR on Router B and Router D as an example (on
Router D, information about the C-BSR is displayed).

<RouterB> display pim ipv6 bsr-info

Elected BSR Address: 2004::2
Priority: 0
State: Accept Preferred
Uptime: 00:04:22
Expires: 00:01:46
C-RP Count: 1
<RouterD> display pim ipv6 bsr-info
Elected BSR Address: 2004::2
Priority: 0
State: Elected
Uptime: 00:01:10
Next BSR message scheduled at: 00:00:48
C-RP Count: 1
Candidate AdminScoped BSR Count: 0
Candidate BSR Address: 2004::2
Priority: 0
State: Elected
Wait to be BSR: 0
# Run the display pim ipv6 rp-info command to check RP information on each router. Take
RP information on Router B as an example.
<RouterB> display pim ipv6 rp-info
PIM-SM BSR RP information:
Group/MaskLen: FF3E::1/64
RP: 2004::2
Priority: 192
Uptime: 00:05:19
Expires: 00:02:11
Step 3 On Router A, configure the BSR boundary on the interface connected to the Internet.
[RouterA-Pos4/0/0] pim ipv6 bsr-boundary
Step 4 Configure the SSM group address range on all routers in the network.
# Configure the PIM-IPv6 SSM group address range on Router A to FF3E::1/64.
[RouterA] acl ipv6 2000
[RouterA-acl6-basic-2000] rule permit source FF3E::1 64
[RouterA-acl6-basic-2000] quit
[RouterA] pim-ipv6
[RouterA-pim6] ssm-policy 2000
[RouterA-pim6] quit
# The configurations of Router B, Router C, and Router D are the same as the configuration of
Router A, and are not mentioned here.
Step 5 Enable PIM silent and MLD on the router interface connected to hosts.
# On Router B, enable PIM silent and MLD on the interface at the host side.
[RouterB-GigabitEthernet2/0/0] pim ipv6 silent
[RouterB-GigabitEthernet2/0/0] mld enable
# On Router C, the configuration of the interface at the host side is similar to the preceding one,
and is not mentioned here.

# Run the display pim ipv6 interface command to check the PIM configuration and the running
information on each interface. Take PIM information on Router B as an example.
<RouterB> display pim ipv6 interface
Pos1/0/0 up 1 30 1 FE80::A01:10E:1 (local)
GE2/0/0 up 0 30 1 FE80::200:AFF:FE01:10E
(local)
Pos3/0/0 up 1 30 1 FE80::9D62:0:FDC5:2
# The multicast source S 2001::5 simultaneously sends packets to group FF3E::1 (in the SSM
group address range) and FF0E::1 (not in the SSM group address range). Host A and Host C
need to receive information to group FF0E::1. Host B needs to receive information sent by S
2001::5 to group FF3E::1.
<RouterA> display pim ipv6 routing-table
(2001::5, FF0E::1)
RP: 2004::2
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 00:02:15
1: Register
2: Pos2/0/0
3: Pos3/0/0
(2001::5, FF3E::1)
Protocol: pim-ssm, Flag: LOC SG_RCVR
UpTime: 00:00:11
1: Pos2/0/0
Protocol: pim-ssm, UpTime: 00:00:11, Expires: 00:03:19
(*, FF0E::1)
RP: 2004::2
UpTime: 00:14:44
Upstream neighbor: FE80::9D62:0:FDC5:2
RPF prime neighbor: FE80::9D62:0:FDC5:2
Protocol: mld, UpTime: 00:14:44, Expires: -
(2001::5, FF0E::1)
RP: 2004::2
UpTime: 00:2:42
Upstream neighbor: FE80::A01:10C:1
RPF prime neighbor: FE80::A01:10C:1


(2001::5, FF3E::1)
Protocol: pim-ssm, Flag: SG_RCVR
UpTime: 00:08:02
Upstream neighbor: FE80::A01:10C:1
RPF prime neighbor: FE80::A01:10C:1
Protocol: pim-ssm, UpTime: 00:08:02, Expires: -
(*, FF0E::1)
RP: 2004::2
UpTime: 00:14:44
Upstream neighbor: FE80::7493:FE25:1
RPF prime neighbor: FE80::7493:FE25:1
(2001::5, FF0E::1)
RP: 2004::2
UpTime: 00:2:42
Upstream neighbor: FE80::7493:FE25:1
RPF prime neighbor: FE80::7493:FE25:1
<RouterD> display pim ipv6 routing-table
(*, FF0E::1)
RP: 2004::2 (local)
UpTime: 00:16:56
1: Pos2/0/0
2: Pos3/0/0
(2001::5, FF0E::1)
RP: 2004::2 (local)
Protocol: pim-sm, Flag: SWT ACT
UpTime: 00:02:54
Upstream neighbor: FE81::659:10C:3
RPF prime neighbor: FE81::659:10C:3
1: Pos3/0/0
----End

Configuration Files
#
sysname RouterA
#
ipv6
#
#
acl ipv6 number 2000
rule 0 permit source FF3E::1/64
#
undo shutdown
ipv6 enable
pim ipv6 sm
#
interface Pos2/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
#
interface Pos3/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
#
interface Pos4/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
pim ipv6 bsr-boundary
#
ospfv3 1
router-id 1.1.1.1
area 0.0.0.0
#
pim-ipv6
ssm-policy 2000
#
return

#
sysname RouterB
#
ipv6
#
#
#
interface Pos1/0/0
undo shutdown
ipv6 enable
link-protocol ppp


pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
pim ipv6 silent
mld enable
#
interface Pos3/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
#
ospfv3 1
router-id 2.2.2.2
area 0.0.0.0
#
pim-ipv6
ssm-policy 2000
#
return
#
sysname RouterC
#
ipv6
#
#
#
interface Pos1/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
pim ipv6 silent
mld enable
#
ospfv3 1
router-id 3.3.3.3
area 0.0.0.0
#
pim-ipv6
ssm-policy 2000
#
return
#
sysname RouterD

#
ipv6
#
#
#
#
interface Pos1/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
#
interface Pos2/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
#
interface Pos3/0/0
undo shutdown
ipv6 enable
link-protocol ppp
pim ipv6 sm
#
ospfv3 1
router-id 4.4.4.4
area 0.0.0.0
#
pim-ipv6
c-bsr 2004::2
c-rp 2004::2 group-policy 2001
#
pim-ipv6
ssm-policy 2000
#
return
13.13.2 Example for Configuring PIM GR (IPv6)
In multicast applications, if a device performs the active/standby switchover, the new main
control board deletes the multicast forwarding entries on the interface board and rebuilds the
PIM routing table and PIM forwarding table. During this process, multicast traffic of users is
interrupted.
Deploying IPv6 PIM GR on an IPTV network protects the core devices and edge devices. When
a device on the IPTV network performs the active/standby switchover, the interface board can
maintain the normal forwarding of multicast data, which increases the fault tolerance capacity
of the devices on the network.
In the network shown in Figure 13-2, multicast services are deployed and IPv6 PIM GR is
configured on Router C. During the process that Router C forwards multicast data to receiver,

the active main control board backs up the PIM routing entries and Join/Prune messages that
need to be sent to upstream device to the standby main control board. When Router C performs
the active/standby switchover, the interface board maintains the original forwarding entries,
which ensures the smooth forwarding of multicast data. Therefore, the receiver can normally
receive multicast data from the multicast source when the device performs the active/standby
switchover.
Figure 13-2 Networking diagram of PIM GR
Ethernet
Leaf networks
RouterA
POS1/0/0 POS2/0/0
Source
GE2/0/0 POS1/0/0 POS1/0/0 GE2/0/0
Router B RouterC
Receiver
PIM-SM HostA
Ethernet
Device Interface IPv6 Address

RouterA POS1/0/0 2001:2::1/64
GE2/0/0 2001:1::2/64
RouterB POS1/0/0 2001:2::2/64
POS2/0/0 2001:5::1/64
RouterC POS1/0/0 2001:5::2/64
GE2/0/0 2001:6::1/64
1. Configure IPv6 addresses for the interfaces and a unicast routing protocol on each router.
2. Enable unicast GR on each router and set unicast GR period.
3. Enable the multicast function, enable PIM SM (IPv6) on the interfaces of routers, and enable
MLD on the interface connecting router to the host.
4. Configure a RP. Configure a same static RP on routers.
5. On Router C, enable PIM GR and set the GR period.
Data Preparation

l Multicast source address (in this example, S is 2001:1::1)

l Multicast group address (in this example, G is FF2E::1)
l Unicast GR period
l PIM GR period
Procedure
Step 1 Configure IPv6 addresses for the interfaces and a unicast routing protocol on each router.
# Based on Figure 13-2, configure IPv6 addresses and masks for the interfaces on each router.
Configure OSPFv3 as the unicast routing protocol running between routers to ensure IP
interworking between Router A, Router B, and Router C. The detailed configuration is not
mentioned here.
Step 2 Enable unicast GR and set the GR period.
# Enable unicast GR and set the GR period to 200 seconds on each router. The configurations
[RouterC] ospfv3 1
[RouterC-ospfv3-1] graceful-restart
[RouterC-ospfv3-1] graceful-restart period 200
[RouterC-ospfv3-1] quit
Step 3 Enable the multicast function, enable PIM SM (IPv6) on the interfaces of routers, and enable
MLD on the interface connecting router and the host.
# Enable the multicast function on all routers, and enable PIM SM (IPv6) on the interfaces of
the routers, and enable MLD on the interface connecting Router C to the host. The configurations
[RouterC] multicast ipv6 routing-enable
[RouterC-GigabitEthernet2/0/0] pim ipv6 sm
[RouterC-GigabitEthernet2/0/0] mld enable
[RouterC-Pos1/0/0] pim ipv6 sm
# Create a loopback interface on Router A and enable PIM SM (IPv6) on the interface.
[RouterA] interface looplback 0
[RouterA-Loopback0] ipv6 enable
[RouterA-Loopback0] ipv6 address 2002:1::1 64
[RouterA-Loopback0] pim ipv6 sm
[RouterA-Loopback0] ospfv3 1 area 0
[RouterA-Loopback0] quit
# Configure a same static RP on each router. The configurations on Router B and Router C are
similar to those on Router A. The detailed configuration procedures are not mentioned here.
[RouterA] pim-ipv6
[RouterA-pim6] static-rp 2002:1::1
[RouterA-pim6] quit
Step 5 Enable PIM GR and set the PIM GR period.

# On Router C, enable PIM GR and set the PIM GR period to 300 seconds.
[RouterC] pim-ipv6
[RouterC-pim6] graceful-restart
[RouterC-pim6] graceful-restart period 300
[RouterC-pim6] quit

# The multicast source (2001:1::1) sends data to the multicast group (FF2E::1). Host A sends
MLD Report message to join multicast group and can receive the data from the multiast source.
Before Router C performs active/standby switchover, run the display pim ipv6 routing-table
command on Router B and Router C to view PIM routing table. The command output are as
follows:
(*, FF2E::1)
RP: 2002:1::1
UpTime: 00:00:53
Upstream neighbor: FE80::E0:F2C:3C02:1
RPF prime neighbor: FE80::E0:F2C:3C02:1
1: Pos2/0/0
(2001:1::1, FF2E::1)
RP: 2002:1::1
UpTime: 00:21:24
1: Pos2/0/0
(*, FF2E::1)
RP: 2002:1::1
UpTime: 00:01:16
Upstream neighbor: FE80::5463:0:9245:2
RPF prime neighbor: FE80::5463:0:9245:2
(2001:1::1, FF2E::1)
RP: 2002:1::1
UpTime: 00:01:16

# run the active/standby switchover command on Router C:

[RouterC] slave switchover
After Router C performs active/standby switchover, during PIM GR, run the display pim ipv6
routing-table command on Router B and Router C to view PIM routing table. The command
output are as follows:
(*, FF2E::1)
RP: 2002:1::1
UpTime: 00:02:20
1: Pos2/0/0
(2001:1::1, FF2E::1)
RP: 2002:1::1
UpTime: 00:02:20
1: Pos2/0/0
(*, FF2E::1)
RP: 2002:1::1
UpTime: 00:02:44
(2001:1::1, FF2E::1)
RP: 2002:1::1
UpTime: 00:02:44
In a normal multicast network, the downstream router periodically sends Join/Prune messages
upstream to refresh the timeout period of PIM routing entries on the upstream, thereby ensuring
normal multicast data forwarding.
If the GR function is not configured on Router C, the new active main control board deletes the
multicast forwarding entries on the interface board, receives MLD Report messages from the

host again, and re-creates PIM routing entries. During this process, multicast traffic is
interrupted.
From the preceding command output, it can be found that after Router C performs active/standby
switchover, the downstream interface of Router B, remains unchanged. That is, after Router C
performs active/standby switchover, Router C sends the backed up Join messages upstream. In
this way, multicast forwarding entries can be maintained during GR to ensure non-stop multicast
data forwarding.
During the process of restoring multicast routing entries on Router C after active/standby
switchover, users can receive multicast data normally and services are not interrupted.
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
#
ospfv3 1
router-id 2.2.2.2
area 0.0.0.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
ipv6 address 2001:2::1/64
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
#
interface LoopBack0
ipv6 enable
pim ipv6 sm
#
pim-ipv6
static-rp 2002:1::1
#
return

#
sysname RouterB
#
ipv6
#
#
ospfv3 1
router-id 3.3.3.3

area 0.0.0.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
pim ipv6 sm
#
interface Pos2/0/0
link-protocol ppp
undo shutdown
ipv6 enable
pim ipv6 sm
#
pim-ipv6
static-rp 2002:1::1
#
return

#
sysname RouterC
#
ipv6
#
#
ospfv3 1
router-id 5.5.5.5
area 0.0.0.0
#
interface Pos1/0/0
link-protocol ppp
undo shutdown
ipv6 enable
pim ipv6 sm
#
undo shutdown
ipv6 enable
pim ipv6 sm
mld enable
#
pim-ipv6
static-rp 2002:1::1
graceful-restart
#
return

14 IPv6 Multicast Routing Management
About This Chapter
This chapter describes the basic principles of IPv6 multicast forwarding, configuration methods
of forwarding policies, and maintenance of commands, and provides configuration examples.
This section describes the principle and basic concepts of IPv6 multicast routing and forwarding.
14.2 Configuring the IPv6 Multicast Routing Policy
This section describes how to configure the multicast routing policy.
14.3 Limiting the Range of Multicast Forwarding
This section describes how to configure the range of multicast forwarding.
14.4 Configuring Control Parameters of the IPv6 Multicast Forwarding Table
14.5 Maintaining IPv6 Multicast Routing Management
This section describes how to clear the statistics of multicast routing and forwarding and monitor
the running status of IPv6 multicast forwarding and routing.
This section provides several configuration examples for IPv6 multicast routing management.


This section describes the principle and basic concepts of IPv6 multicast routing and forwarding.

14.1.2 IPv6 Multicast Routing Management Features Supported by the NE80E/40E
In the IPv6 multicast network, PIM-IPv6 adopts the Reverse Path Forwarding (RPF) check,
creates, and updates routing entries, including the (*, G) entry and (S, G) entry. The RPF check
is implemented on the basis of RPF routes. IPv6 RPF routes are selected from unicast routes.
The multicast routing table records (S, G) entries and downloads the entries to the multicast
forwarding table. The multicast forwarding table directly guides the forwarding of multicast data
packets.
An (S, G) forwarding entry contains the following information:
l Source address S
l Group address G
l Incoming interface, which indicates that multicast data is received through this interface.
The incoming interface corresponds to the upstream interface of the related routing entry.
l Outgoing interface, which indicates that multicast data is sent out through this interface.
The outgoing interface corresponds to the downstream interface in the downstream
interface list of the related routing entry.
NOTE
IPv6 multicast forwarding and routing are similar to IPv4 multicast forwarding and routing. For details,
refer to the chapter "Multicast Forwarding and Routing" in the HUAWEI NetEngine80E/40E Router
Feature Description - IP Multicast.
14.1.2 IPv6 Multicast Routing Management Features Supported by

the NE80E/40E
Configuring the IPv6 Multicast Routing Policy

When a router enabled with IPv6 multicast selects the upstream interface, you need to configure
the route selection policy if multiple equal-cost unicast routes exist. You can configure the
router to select the the route with the highest next-hop address or configure load splitting.
Performing multicast load splitting according to different policies can optimize network traffic
transmission in the scenario where multiple multicast data flows exist.
There are five multicast load splitting policies: stable-preferred, balance-preferred, source
address-based, group address-based, and source and group addresses-based. The five load
splitting policies are mutually exclusive. In addition, you can configure IPv6 load splitting
weights on the interfaces to achieve unbalanced multicast load splitting.

Limiting the Range of Multicast Forwarding

In the IPv6 network, the multicast information each multicast group corresponds to is transmitted
in a certain range. In the NE80E/40E, you can define the multicast forwarding range by using
the following methods:
l Configuring an IPv6 multicast forwarding boundary on an interface to form a closed

multicast forwarding area
l Setting the TTL threshold for IPv6 multicast forwarding on an interface to limit the range
in which an IPv6 multicast packet can be forwarded
Configuring Control Parameters of the IPv6 Multicast Forwarding Table

When planning the specific Internet Service Provider (ISP) network according to the provided
multicast services, you can limit the number of entries and the number of downstream interfaces
of a single forwarding entry in the IPv6 multicast forwarding table.
14.2 Configuring the IPv6 Multicast Routing Policy

This section describes how to configure the multicast routing policy.
14.2.2 Configuring IPv6 Multicast Load Splitting
14.2.3 Configuring an IPv6 Multicast Load Splitting Weight
If multiple unicast routes with the same cost exist when a router enabled with IPv6 multicast
selects the upstream interface, you can use one of the following methods to configure the
router to select the RPF route:
l By default, the router selects the route with the highest next-hop address.
l Load splitting is configured among equal-cost routes. Performing load splitting of multicast
traffic according to different policies can optimize network traffic transmission in the
scenario where multiple multicast data flows exist.
Before configuring the IPv6 multicast routing policy, complete the following tasks:
l Configuring an IPv6 unicast routing protocol

Data Preparation
To configure the IPv6 multicast routing policy, you need the following data.

No. Data
1 IPv6 load splitting policy
2 IPv6 load splitting weight on the interface
14.2.2 Configuring IPv6 Multicast Load Splitting
Context
The IPv6 multicast load splitting function extends multicast routing rules, which does not fully
depend on the RPF check. If multiple equal-cost optimal routes exist over the network, they all
can be used for multicast data forwarding. In the case that the multicast service is guaranteed,
multicast traffic is load split to multiple equal-cost routes.
By default, IPv6 multicast load splitting is not configured.
Do as follows on the router enabled with IPv6 multicast:
Procedure
Step 1 Run:
system-view
Step 2 Run:
multicast ipv6 load-splitting { balance-preferred | stable-preferred | source |
group | source-group }
IPv6 multicast splitting is configured.
Parameters in the command are described as follows:
l balance-preferred: indicates balance-preferred load splitting. This policy is applicable to

the scenario where hosts frequently join or leave the groups, which requires automatic load
adjustment.
If balance-preferred is specified, the router automatically adjusts and balances the entries
on the equal-cost routes when equal-cost routes are added or deleted, IPv6 multicast routing
entries are deleted, or IPv6 load splitting weights on the interfaces are changed.
l stable-preferred: indicates stable-preferred load splitting. This policy is applicable to the
stable multicast networking.
If stable-preferred is specified, the router automatically adjusts and balances the entries
when equal-cost routes are added or deleted; however, when IPv6 multicast routing entries
are deleted or IPv6 load splitting weights on the interfaces are changed, the router does not
automatically adjust the entries on the equal-cost routes.
l group: indicates group address-based load splitting. This policy is applicable to the scenario
of one source to multiple groups.
l source: indicates source address-based load splitting. This policy is applicable to the scenario
of one group to multiple sources.

l source-group: indicates source and group addresses-based load splitting. This policy is
applicable to the scenario of multiple sources to multiple groups.
NOTE
It is recommended to adopt a fixed IPv6 multicast load splitting policy based on the actual networking.
The balance-preferred or stable-preferred policy is preferred.
balance-preferred or stable-preferred cannot be configured on the interface enabled with PIM-DM.
----End
14.2.3 Configuring an IPv6 Multicast Load Splitting Weight
Context
When stable-preferred or balance-preferred load splitting is configured, because the forwarding
capabilities of equal-cost routes are different from the actual load bearing situation on the equal-
cost routes, balanced load splitting cannot meet network requirements in some scenarios. In such
a case, you can configure an IPv6 multicast load splitting weight on an interface to achieve
unbalanced multicast load splitting.
Do as follows on the router enabled with IPv6 multicast:
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
multicast ipv6 load-splitting weight weight-value
The interface is configured with an IPv6 multicast load splitting weight.
By default, the IPv6 multicast load splitting weight of an interface is 1.
The greater the load splitting weight of an interface, the more IPv6 multicast routing entries with
this interface being the upstream interface. When the IPv6 multicast load splitting weight on an
interface is 0, it indicates that the routes with this interface being the upstream interface do not
take part in load splitting.
----End
Procedure
l Run the display multicast ipv6 routing-table [ ipv6-source-address [ ipv6-source-mask-
length ] | ipv6-group-address [ ipv6-group-mask-length ] | incoming-interface { interface-
type interface-number | register } | outgoing-interface { { exclude | include | match }

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

[ number ] ] command to check the IPv6 multicast routing table.
l Run the display multicast ipv6 rpf-info ipv6-source-address [ ipv6-group-address ]
[ rpt | spt ] command to display the IPv6 RPF routing information of a source-specific
multicast group.
----End
14.3 Limiting the Range of Multicast Forwarding

This section describes how to configure the range of multicast forwarding.
14.3.2 Configuring the IPv6 Multicast Forwarding Boundary on an Interface
14.3.3 Configuring the TTL Threshold for IPv6 Multicast Forwarding

In the IPv6 network, the multicast information each multicast group corresponds to is transmitted
in a certain range. In the NE80E/40E, you can define the IPv6 multicast forwarding range by
using the following methods:
l Configuring an IPv6 multicast forwarding boundary on an interface to form a closed
multicast forwarding area. When an interface of a router is configured with the forwarding
boundary for a group, the interface does not forward or receive any packet for the group.
l Setting the TTL threshold for IPv6 multicast forwarding on an interface to limit the range
in which an IPv6 multicast packet can be forwarded. The interface forwards only the packets
(including those generated by the local router) with the TTL value being equal to or greater
than the threshold value. If the TTL value of a packet is smaller than the threshold, the
interface discards the packet.
Before limiting the range of multicast forwarding, complete the following tasks:
Data Preparation
To limit the range of multicast forwarding, you need the following data.
No. Data
1 Group address, mask, and mask length of the IPv6 multicast forwarding boundary
2 TTL threshold for IPv6 multicast forwarding

14.3.2 Configuring the IPv6 Multicast Forwarding Boundary on an

Interface
Context
By default, the IPv6 multicast forwarding boundary is not set on an interface.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
multicast ipv6 boundary ipv6-group-address ipv6-group-mask-length
The IPv6 multicast forwarding boundary is configured.
----End
14.3.3 Configuring the TTL Threshold for IPv6 Multicast

Forwarding
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
multicast ipv6 minimum-ttl ttl-value
The minimum TTL value for forwarding IPv6 multicast packets is set on the interface.
By default, the TTL threshold for IPv6 multicast forwarding is 1.
----End

Procedure
[ number ] ] command to check the IPv6 multicast routing table.
l Run the display multicast ipv6 boundary [ ipv6-group-address [ ipv6-group-mask-
length ] | interface interface-type interface-number ] command to check the IPv6 multicast
boundary configured on the interface.
l Run the display multicast ipv6 minimum-ttl [ interface-type interface-number ]
command to check the TTL threshold for forwarding IPv6 multicast packets on the
interface.
----End
14.4 Configuring Control Parameters of the IPv6 Multicast

Forwarding Table
14.4.2 Configuring the Maximum Number of Entries in the IPv6 Multicast Forwarding Table
14.4.3 Configuring the Maximum Number of Downstream Nodes of a Single Forwarding Entry
When planning a specific network according to network services, the ISP needs to perform the
following configurations:
l Limiting the number of entries in the IPv6 multicast forwarding table

A router maintains a forwarding entry for each received multicast packet. Too many
multicast forwarding entries, however, use up the memory of the router. You can define
the maximum number of entries in the multicast forwarding table of a router. Limiting the
number of entries according to the actual networking and service performance can prevent
faults caused by too many entries.
l Limiting the number of downstream interfaces of a single forwarding entry
A router replicates a multicast packet for each downstream interface and sends them out.
Each downstream interface forms a branch of a multicast distribution tree (MDT). The
number of downstream interfaces determines the maximum scale of an MDT and the service
range. You can define the number of downstream interfaces of a single forwarding entry.
Limiting the number of downstream interfaces according to the actual networking and

service performance can reduce the processing pressure of a router and control the service
range.
Before configuring control parameters of the IPv6 multicast routing policy, complete the
following tasks:

Data Preparation
To configure control parameters of the IPv6 multicast routing policy, complete the following
tasks.
No. Data
1 Source address, group address, and mask or mask length
2 Matching policy, sequence, and preference of multicast routes
3 The maximum number of forwarding entries in the multicast forwarding table
4 The maximum number of downstream interfaces of each forwarding entry in the

multicast forwarding table
14.4.2 Configuring the Maximum Number of Entries in the IPv6

Multicast Forwarding Table
Context
By default, the maximum value permitted by the system is used.
Procedure
Step 1 Run:
system-view
Step 2 Run:
multicast ipv6 forwarding-table route-limit limit
The maximum number of entries in the IPv6 multicast forwarding table is set.
The configured value is valid only when it is smaller than the default value.
----End

14.4.3 Configuring the Maximum Number of Downstream Nodes

of a Single Forwarding Entry
Context
By default, the maximum value permitted by the system is used.
Procedure
Step 1 Run:
system-view

Step 2 Run:
multicast ipv6 forwarding-table downstream-limit limit
The maximum number of downstream nodes of a single entry in the IPv6 multicast forwarding
table is set.
The configured value is valid only when it is smaller than the default value.
----End

Procedure
l Run the display multicast ipv6 forwarding-table [ ipv6-source-address [ ipv6-source-
mask-length ] | ipv6-group-address [ ipv6-group-mask-length ] | incoming-interface
{ interface-type interface-number | register } | outgoing-interface { { exclude | include |
match } { interface-type interface-number | register | none } } | slot slot-number |
statistics ] * command to check the IPv6 multicast forwarding table.
----End
14.5 Maintaining IPv6 Multicast Routing Management

This section describes how to clear the statistics of multicast routing and forwarding and monitor
the running status of IPv6 multicast forwarding and routing.
14.5.1 Clearing IPv6 Multicast Forwarding Entries and Routing Entries
14.5.2 Monitoring the Running Status of IPv6 Multicast Forwarding and Routing

14.5.1 Clearing IPv6 Multicast Forwarding Entries and Routing

Entries
Context
CAUTION
After you run the reset command to clear information in the multicast forwarding table or in the
multicast routing table, multicast data cannot be normally transmitted. So, confirm the action
before you use the command.
Procedure
l Run the reset multicast ipv6 forwarding-table { ipv6-group-address [ ipv6-group-mask-
length ] | ipv6-source-address [ ipv6-source-mask-length ] | all | incoming-interface
{ interface-type interface-number | register } } * command in the user view to clear the
forwarding entry in the IPv6 multicast forwarding table.
l Run the reset multicast ipv6 routing-table { ipv6-source-address [ ipv6-source-mask-
length ] | ipv6-group-address [ ipv6-group-mask-length ] | all | incoming-interface
{ interface-type interface-number | register } } * command in the user view to clear the
routing entry in the IPv6 multicast routing table.
----End
14.5.2 Monitoring the Running Status of IPv6 Multicast Forwarding

and Routing
Context
status of IPv6 multicast forwarding and routing.
Procedure
l Run the display multicast ipv6 boundary [ ipv6-group-address [ ipv6-group-mask-
length ] | interface interface-type interface-number ] command in any view to check
information about boundaries of all interfaces.
l Run the display multicast ipv6 forwarding-table [ ipv6-source-address [ ipv6-source-
mask-length ] | ipv6-group-address [ ipv6-group-mask-length ] | incoming-interface
{ interface-type interface-number | register } | outgoing-interface { { exclude | include |
match } { interface-type interface-number | register | none } } | slot slot-number |
statistics ] * command in any view to check the IPv6 multicast forwarding table.
l Run the display multicast ipv6 minimum-ttl [ interface-type interface-number ]
command in any view to check the minimum TTL value when a multicast data packet is
forwarded by an interface.


[ number ] ] command in any view to check the IPv6 multicast routing table.
l Run the display multicast ipv6 rpf-info ipv6-source-address [ ipv6-group-address ]
[ rpt | spt ] command in any view to check the RPF routes of a specified multicast source.
----End

This section provides several configuration examples for IPv6 multicast routing management.
14.6.1 Example for Configuring IPv6 Multicast Load Splitting
14.6.1 Example for Configuring IPv6 Multicast Load Splitting
Multicast route selection is based on the RPF check, and the route selection policy depends on
unicast routes. The selected unique route is used to guide the forwarding of multicast data. If
the volume of multicast traffic is excessively large on a network, the network may be congested
and multicast services may be affected. Multicast load splitting extends the rules of multicast
route selection and makes multicast route selection not completely depend on the RPF check.
When there are multiple equal-cost optimal routes on a network and the routes can be used to
forward multicast data, multicast load splitting can be performed among the routes for multicast
traffic.
Currently, multicast load splitting is classified into multicast source-based load splitting,
multicast group-based load splitting, and multicast source- and multicast group-based load
splitting. These types of multicast load splitting cannot meet the requirements of multicast
splitting in all scenarios. In the case that multicast routing entries and network configurations
are stable, RPF interfaces and RPF neighbors keep unchanged. When the number of entries is
excessively small, balanced load splitting cannot be achieved.
Stable-preferred load splitting consummates the preceding types of multicast load splitting. As
shown in Figure 14-1, there are three equal-cost routes between Router E connected to Host A
and the multicast source, and stable-preferred load splitting is configured on Router E. Therefore,
entries can be evenly distributed on the equal-cost routes and balanced load splitting can be
implemented among the equal-cost routes.
If the forwarding capabilities and the severities of traffic congestion of the three equal-cost routes
on Router E are different, balanced load splitting cannot meet network requirements. In this case,
you need to configure unbalanced load splitting on Router E, and set different load splitting
weights on the upstream interfaces of Router E to change the number of entries distributed to
the equal-cost routes. Thus, you can flexibly control the number of entries distributed on the
equal-cost routes.

Figure 14-1 Networking diagram of configuring IPv6 multicast load splitting
PIM-SM
Source
0/0 PO
S2/0/
1
O S1/ RouterB S2/0/0 POS1/0
GE1/0/0 PO P /1
POS2/0/2 POS1/0/2 GE2/0/0
RouterA POS
2/0/ POS1/0/0 POS2/0/0
S1/
0/3
3 PO
RouterC RouterE
POS 0/0 HostA
1/0/
0 S2/
Loopback0 PO
RouterD
Device Interface IP Address Device Interface IP Address
Router A GE1/0/0 2001::2/64 Router C POS1/0/0 2003::2/64
POS2/0/1 2002::1/64 POS2/0/0 2006::1/64
POS2/0/2 2003::1/64 Router D POS1/0/0 2004::2/64
POS2/0/3 2004::1/64 POS2/0/0 2007::1/64
LoopBack0 2000::1/64 Router E POS1/0/1 2005::2/64
Router B POS1/0/0 2002::2/64 POS1/0/2 2006::2/64
POS2/0/0 2005::1/64 POS1/0/3 2007::2/64
GE2/0/0 3001::1/64
l Assign an IPv6 address to each interface on routers.

l Configure IS-IS IPv6 to implement interworking among routers and ensure that route costs
are equal.
l Enable multicast on routers, enable IPv6 PIM-SM on each interface, and set the loopback
interface on Router A as an RP.
l Configure stable-preferred IPv6 multicast load splitting on Router E to ensure the stability
of IPv6 multicast services.
l Host A requires to receive data from some multicast groups for a long period. Configure
the interfaces at the host side of Router E to join the multicast groups statically in batches.

l Host A requires to receive data from a new multicast group. Therefore, configure a multicast
load splitting weight for each upstream interface on Router E to achieve unbalanced IPv6
multicast load splitting.
Data Preparation
l IPv6 address of the multicast source

l IPv6 address of each interface on the routers
l Address of the multicast group that interfaces at the host side of Router E statically join in
batches
l IPv6 multicast load splitting weight on each upstream interface on Router E
Procedure
Step 1 Assign an IPv6 address to each interface on the routers according to Figure 14-1. The detailed
configuration procedure is not mentioned here.
Step 2 Configure IS-IS IPv6 to implement interworking among routers and ensure that route costs are
equal. The detailed configuration procedure is not mentioned here.
Step 3 Enable IPv6 multicast on all routers and enable IPv6 PIM-SM on each interface.
# Configure Router A. Configurations on Routers B, C, D, and E are similar to those on

RouterA. Therefore, configurations on these Routers are not mentioned here.
[RouterA-LoopBack0] pim ipv6 sm
Step 4 Configure an RP on Router A.
# Configure the interface loopback0 on Router A as an RP.

[RouterA] pim-ipv6
[RouterA-pim6] c-bsr 2000::1
[RouterA-pim6] c-rp 2000::1
[RouterA-pim6] quit
Step 5 Configure stable-preferred IPv6 multicast load splitting on Router E.

[RouterE] multicast ipv6 load-splitting stable-preferred
Step 6 Configure the interfaces at the host side of RouterE to join the multicast groups statically in
batches.
# Configure GE 2/0/0 to join multicast groups from FF13::1 to FF13::3 statically.


[RouterE-GigabitEthernet2/0/0] mld static-group ff13::1 inc-step-mask 128 number 3
Step 7 Verify the configuration about stable-preferred IPv6 multicast load splitting.
# The multicast source (2001::1/64) sends multicast data to multicast groups (FF13::1 to
FF13::3). Host A can receive the multicast data from the source. On Router E, check brief
information about the IPv6 PIM routing table.
<RouterE> display pim ipv6 routing-table brief
00001.(*, FF13::1)
Upstream interface:Pos1/0/1
Number of downstream:1
00002.(2001::1, FF13::1)
00003.(*, FF13::2)
00004.(2001::1, FF13::2)
00005.(*, FF13::3)
00006.(2001::1, FF13::3)
You can find that (*,G) and (S,G) entries are equally distributed to three equal-cost routes, with
the upstream interfaces being POS 1/0/1, POS 1/0/2, and POS 1/0/3 respectively.
NOTE
The load splitting algorithm processes (*,G) and (S,G) entries separately and the process rules are the same.
Step 8 Configure IPv6 multicast load splitting weights for different upstream interfaces of Router E to
achieve unbalanced IPv6 multicast load splitting.
# Set the IPv6 multicast load splitting weight on POS 1/0/1 to 2.

[RouterE-Pos1/0/1] multicast ipv6 load-splitting weight 2
# Set the IPv6 multicast load splitting weight on POS 1/0/3 to 0.

[RouterE-Pos1/0/3] multicast ipv6 load-splitting weight 0
Step 9 Configure the interfaces at the host side of Router E to join new multicast groups statically in
batches.
# Configure GE 2/0/0 to join multicast groups from FF13::4 to FF13::9 statically.

[RouterE-GigabitEthernet2/0/0] mld static-group ff13::4 inc-step-mask 128 number 6
Step 10 Verify the configuration about unbalanced IPv6 multicast load splitting.

# The multicast source (2001::1/64) sends multicast data to multicast groups (FF13::1 to
FF13::9). Host A can receive the multicast data from the source. On Router E, check brief
information about the IPv6 PIM routing table.
<RouterE> display pim ipv6 routing-table brief
00001.(*, FF13::1)
00002.(2001::1, FF13::1)
00003.(*, FF13::2)
00004.(2001::1, FF13::2)
00005.(*, FF13::3)
00006.(2001::1, FF13::3)
00007.(*, FF13::4)
00008.(2001::1, FF13::4)
00009.(*, FF13::5)
00010.(2001::1, FF13::5)
00011.(*, FF13::6)
00012.(2001::1, FF13::6)
00013.(*, FF13::7)
00014.(2001::1, FF13::7)
00015.(*, FF13::8)
00016.(2001::1, FF13::8)
00017.(*, FF13::9)
00018.(2001::1, FF13::9)
The upstream interfaces of existent (*,G) and (S,G) entries keep unchanged. Since the IPv6
multicast load splitting weight of POS 1/0/1 is higher than that of POS 1/0/2, the newly generated
entries with the upstream interface being POS 1/0/1 are more than those with the upstream

interface being POS 1/0/2. The IPv6 multicast load splitting weight of POS 1/0/3 is 0, which
indicates that this interface does not take part in load splitting of new entries.
----End
Configuration Files
#
sysname RouterA
#
ipv6
#
#
isis 1
network-entity 10.0000.0000.0001.00
#
ipv6 enable topology standard
#
#
undo shutdown
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface Pos2/0/1
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface Pos2/0/2
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface Pos2/0/3
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface LoopBack0
ipv6 enable
isis ipv6 enable 1
pim ipv6 sm
#
pim-ipv6
c-bsr 2000::1
c-rp 2000::1
#
return

#
sysname RouterB

#
ipv6
#
#
isis 1
network-entity 10.0000.0000.0002.00
#
#
#
interface Pos1/0/0
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface Pos2/0/0
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
return
#
sysname RouterC
#
ipv6
#
#
isis 1
network-entity 10.0000.0000.0003.00
#
#
#
interface Pos1/0/0
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface Pos2/0/0
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
return
#
sysname RouterD
#
ipv6
#
#
isis 1

network-entity 10.0000.0000.0004.00
#
#
#
interface Pos1/0/0
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface Pos2/0/0
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
return
#
sysname RouterE
#
ipv6
#
multicast ipv6 load-splitting stable-preferred
#
isis 1
network-entity 10.0000.0000.0005.00
#
#
#
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
mld static-group FF13::1 inc-step-mask 128 number 3
mld static-group FF13::4 inc-step-mask 128 number 6
#
interface Pos1/0/1
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
multicast ipv6 load-splitting weight 2
#
interface Pos1/0/2
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1
pim ipv6 sm
#
interface Pos1/0/3
link-protocol ppp
ipv6 enable
undo shutdown
isis ipv6 enable 1

pim ipv6 sm
multicast ipv6 load-splitting weight 0
#
return

Configuration Guide - IP Multicast 15 Multicast Network Management
15 Multicast Network Management
About This Chapter
This chapter describes the configuration methods and maintenance of the multicast network
management function.
15.1 Multicast Network Management Introduction
This section describes the multicast network management features supported by the NE80E/
40E and the basic principle of multicast network management.
15.2 Configuring Multicast Network Management
This section describes how to configure multicast network management.
15.3 Adjusting the Frequency for Multicast Protocols to Send Trap Messages
This section describes how to adjust the frequency for multicast protocols to send trap messages.

15 Multicast Network Management Configuration Guide - IP Multicast
15.1 Multicast Network Management Introduction

This section describes the multicast network management features supported by the NE80E/
40E and the basic principle of multicast network management.
15.1.1 Overview of Multicast Network Management

15.1.2 Multicast Network Management Features Supported by the NE80E/40E
15.1.1 Overview of Multicast Network Management

At present, with the increasingly wide application of IP multicast, the requirement for managing
multicast networks becomes more exigent. After multicast network management is enabled, you
can manage multicast routers through the Network Management Station (NMS).
By means of the Simple Network Management Protocol (SNMP), Multicast Management
Information Base (MIB) manages multicast information exchanged between the NMS and
agents. Multicast MIB supports the basic SNMP operations, such as Get-Request, GetNext-
Request, Set-Request, and Trap.
15.1.2 Multicast Network Management Features Supported by the

NE80E/40E
At present, the MIBs of the following objects are supported:
l IGMP
l MLD
l PIM-SM or PIM-SSM (IPv4 and IPv6)
l MSDP
l BSR (IPv4 and IPv6)
l Multicast routing management (MRM)
By default, the multicast trap function is disabled. You can enable the trap function for each
module and adjust the frequency of sending certain types of traps through command lines.
15.2 Configuring Multicast Network Management

This section describes how to configure multicast network management.
15.2.2 Enabling Multicast Network Management
15.2.3 Binding Multicast MIB to an Instance
15.2.4 Enabling the Trap Function for IGMP
15.2.5 Enabling the Trap Function for MLD
15.2.6 Enabling the Trap Function for MRM

15.2.7 Enabling the MSDP Trap Function

15.2.8 Enable the PIM Trap Function
15.2.9 Enabling the Trap Function for Layer 2 Multicast
At present, multicast network management does not support multi-instance. That is, multicast
MIB cannot send information about multiple multicast instances to the NMS simultaneously.
Therefore, you must bind multicast MIB with a specific instance (a public network instance or
a VPN instance) on a router.
After multicast network management is enabled, you can bind multicast MIB to VPN instances,
or enable the trap function of a specified module as required.
Before configuring multicast network management, complete the following tasks:
l ( Optional ) Configuring VPN instances
Data Preparation
To configure multicast network management, you need the following data.
No. Data
1 ( Optional ) Name of a VPN instance
15.2.2 Enabling Multicast Network Management
Context
Do as follows on the router managed by the NMS:
Procedure
Step 1 Run:
system-view

Step 2 Run:
multicast-mib
The multicast MIB view is displayed and multicast network management is enabled.

After this function is enabled, multicast MIB is bound to the public network instance.
----End
15.2.3 Binding Multicast MIB to an Instance
Context
To manage multicast VPN instances through the NMS, do as follows on the multicast router
managed by the NMS:
Procedure
Step 1 Run:
system-view

Step 2 Run:
multicast-mib
The multicast MIB view is displayed.

Step 3 Run:
mib-binding vpn-instance vpn-instance-name
Multicast MIB is bound to a specific VPN instance.

You need to ensure that the instance specified by vpn-instance-name exists; otherwise, this
command does not take effect.
By default, multicast MIB is bound to the public network instance.
----End
15.2.4 Enabling the Trap Function for IGMP
Context
Do as follows on the router that needs to be managed by the NMS:
Procedure
Step 1 Run:
system-view

Step 2 Run:
snmp-agent trap enable feature-name igmp [ trap-name { glblimit | iflimit |
inslimit | joingrp | leavegrp } ]
The trap function is enabled for IGMP.

By default, the trap function is disabled for IGMP.
----End

15.2.5 Enabling the Trap Function for MLD
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
snmp-agent trap enable feature-name mld [ trap-name { glblimit | iflimit |
inslimit | joingrp | leavegrp } ]
The trap function is enabled for MLD.
By default, the trap function is disabled for MLD.
----End
15.2.6 Enabling the Trap Function for MRM
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
snmp-agent trap enable feature-name mrm [ trap-name { cacglbchn | cacglbchnexceed
| cacglbtotal | cacglbtotalexceed | cacoifchn | cacoifchnexceed | cacoiftotal |
cacoiftotalexceed } ]
The trap function is enabled for MRM.
By default, the trap function is disabled for MRM.
----End
15.2.7 Enabling the MSDP Trap Function
Context

Procedure
Step 1 Run:
system-view

Step 2 Run:
snmp-agent trap enable feature-name msdp [ trap-name { backward | establish } ]
The trap function is enabled for MSDP.

By default, the trap function is disabled for MSDP.
----End
15.2.8 Enable the PIM Trap Function
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
snmp-agent trap enable feature-name pim [ trap-name { gr-end | gr-start | interface-
election | invalid-join-prune | invalid-register | neighbor-loss | new-neighbor |
rp-mapping-change } ]
The trap function is enabled for PIM.

By default, the trap function is disabled for PIM.
----End
15.2.9 Enabling the Trap Function for Layer 2 Multicast
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
snmp-agent trap enable feature-name l2-multicast

The trap function is enabled for Layer 2 multicast.
By default, the trap function is disabled for Layer 2 multicast.
----End
Procedure
l Run the display current-configuration configuration command to check the VPN
instance to which multicast MIB is bound.
l Run the display snmp-agent trap feature-name igmp all command to check the status
of the IGMP trap function.
l Run the display snmp-agent trap feature-name mld all command to check the status of
the MLD trap function.
l Run the display snmp-agent trap feature-name mrm all command to check the status of
the MRM trap function.
l Run the display snmp-agent trap feature-name msdp all command to check the status
of the MSDP trap function.
l Run the display snmp-agent trap feature-name pim all command to check the status of
the PIM trap function.
l Run the display snmp-agent trap feature-name l2-multicast all command to check the
status of the l2-multicast trap function.
----End
15.3 Adjusting the Frequency for Multicast Protocols to

Send Trap Messages
This section describes how to adjust the frequency for multicast protocols to send trap messages.
15.3.2 Adjusting the Frequency for IGMP or MLD to Send Trap Messages
15.3.3 Adjusting the Interval for PIM to Send Trap Messages
15.3.4 Adjusting the Interval for Sending Trap Messages About Join Failure due to Multicast
CAC
By adjusting the frequency for each multicast protocol to send trap messages, you can know the
current statuses of various multicast events on the routers in real time.

Before adjusting the frequency for multicast protocols to send trap messages, complete the
following tasks:
l Configuring basic IGMP/MLD functions

l Configuring basic PIM functions
l Configuring multicast CAC functions
l Enabling the multicast trap function
Data Preparation
To adjust the frequency for multicast protocols to send trap messages, you need the following
data.
No. Data
1 Number of trap messages about Join/Leave events sent by IGMP per second
2 Number of trap messages about Join/Leave events sent by MLD per second
3 Interval for sending PIM MIB notification messages
4 Interval for sending trap messages about join failure due to multicast CAC
15.3.2 Adjusting the Frequency for IGMP or MLD to Send Trap

Messages
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
multicast-mib
Step 3 Run:
multicast mib-notification join-leave frequency count
The number of trap messages about Join/Leave events sent by IGMP or MLD per second is set.
----End

15.3.3 Adjusting the Interval for PIM to Send Trap Messages
Context
After PIM is enabled on the routers, you can configure PIM-MIB notifications to set the interval
for sending PIM events. Therefore, you can know the current status of various PIM events on
the routers in real time. The PIM events include the neighbor loss event, neighbor addition, the
event of receiving invalid Join/Prune messages, RP-mapping change event, event of the interface
being elected as the DR, and the event of receiving invalid Register messages.
Procedure
Step 1 Run:
system-view

Step 2 Run:
multicast-mib

Step 3 Run:
pim mib-notification interval { interface-election-dr election-value | invalid-
join-prune jp-value | invalid-register register-value | neighbor-loss loss-value
| new-neighbor new-value | rp-mapping-change change-value }
The interval for PIM to send trap messages is set.

By default, the interval for sending trap messages for neighbor lost and neighbor addition is 0
seconds. That is, once the event occurs, PIM reports it immediately.
The default interval for sending the trap of event of receiving invalid Join/Prune messages, the
RP-mapping change event, the event of the interface being elected as the DR, or the event of
receiving invalid Register messages is 65535 seconds. After the events of these types occur,
PIM does not report them. To configure PIM to report these events, you can run the pim mib-
notification interval command to set an interval smaller than 65535 seconds.
----End
15.3.4 Adjusting the Interval for Sending Trap Messages About Join
Failure due to Multicast CAC
Context
Procedure
l Multicast CAC limit
1. Run:
system-view


2. Run:
multicast-mib

3. Run:
multicast trap-interval cac min-interval
The interval for sending trap messages about IGMP or PIM Join failure due to
multicast CAC is set.
The value of min-interval ranges from 0 to 65535. The default value is 0.
l IGMP entries limit
1. Run:
system-view

2. Run:
multicast-mib

3. Run:
igmp trap-interval limit min-interval
The interval for sending trap messages of the failure of IGMP joining because the
number of the IGMP entries exceeds the limit is set.
The value of min-interval ranges from 0 to 65535. The default value is 0.
----End

Procedure
l Run the display pim mib-notification interval command to check the configured interval
for sending PIM MIB notification messages.
----End

Configuration Guide - IP Multicast A Glossary
A Glossary
This appendix collates frequently used glossaries in this document.

(
(S, G) A multicast routing entry. S indicates a multicast source, and G indicates
a multicast group. After a multicast packet with S as the source address
and G as the group address reaches the router, it is forwarded through
the downstream interfaces of the (S, G) entry. The packet is expressed
as (S, G) packet.
(*, G) A PIM routing entry. * indicates any source, and G indicates a multicast
group.(*, G) entry is applicable to all multicast packets whose group
address is G. All multicast packets that are sent to G are forwarded
through the downstream interfaces of the (*, G) entry, regardless of
which source sends the packets out.
A
ASM Any-Source Multicast that is implemented through PIM-DM and PIM-
SM.
Assert A mechanism that is applicable to PIM-DM and PIM-SM. After
receiving a multicast packet from the downstream, a router performs
RPF check on the packet. If the RPF check fails, other multicast
forwarders exist in the network segment. The router sends Assert
message through the downstream interface to join the Assert election.
If the router fails in the Assert election, it removes the downstream
interface from the downstream interface list. Assert ensures that only
one multicast forwarder exists on a network segment and only a cpoy
of multicast packet is transmitted by the forwarder.
Issue 04 (2010-08-31) Huawei Proprietary and Confidential A-1

A Glossary Configuration Guide - IP Multicast
BSR BootStrap Router, which is the management core of the PIM-SM

network. The BSR collects advertisement information on Candidate-
RPs (C-RPs) to form a RP-Set, encapsulates the RP-Set in the Bootstrap
message, and then advertise it to each PIM-SM router. The router
calculates the RP corresponding to the specific multicast group
according to the RP-set.
BSR BSR administrative domain, which is applicable only to PIM-SM. Each
Administrative BSR administrative domain has its router that serves the specific
Scope multicast group. BSR and RP are valid only in the administrative
domain.
C
CAC Call Admission Control (CAC) is to configure policies on the multicast
router connecting the receiver, intermediate multicast routers, and the
multicast router connecting the multicast source to limit the number of
multicast entries that can be created on multicast routers. In this manner,
the operator can control the number of access users and available IPTV
services on the IP core network.
D
Downstream The interface that forwards multicast data. The router or the receiver
Interface host that the sent multicast data reaches is called downstream router or
downstream host. The network segment where the downstream
interface resides is called downstream network segment.
DR Designated Router that is applicable only to PIM-SM. In the network
segment that connects to S, DR sends Register message to RP. In the
network segment that connects to members, DR sends the Join message
to RP. In SSM mode, the DR at the group member side directly sends
Join messages to S.
F
First-hop Router The PIM router that directly connects to the multicast source and
forwards the multicast data sent by the multicast source.
Flooding The flooding that is applicable only to PIM-DM. PIM-DM assumes that
all members are densely distributed on the network and each network
segment may have members. According to the assumption, the multicast
source floods multicast data to each network segment and then prune
the network segment that does not have any member. Through the
periodical Flooding-Prune, PIM-DM establishes and maintains a
unidirectional SPT that connects the multicast source with members.
A-2 Huawei Proprietary and Confidential Issue 04 (2010-08-31)

Graft The Graft that is applicable only to PIM-DM. When a pruned

downstream node wants to restore the forwarding function, it sends a
graft message to the upstream node. The upstream node responds to the
message after receiving it. The previously pruned branch thus restores
the forwarding of multicast information immediately.
Graft-Ack Indicates the Graft Acknowledgement that is applicable only to PIM-
DM. After receiving a Graft message from the downstream node, the
router restores the forwarding function for the downstream node. Then
a Graft-Ack message is sent from the interface of the downstream node
to indicate the acceptance of the Graft message. If receiving no Graft-
Ack message within a specified period, the router that sends the Graft
message considers that the upstream node does not receive the Graft
message and sends it again.
H
Hash function A function that is expressed as Value (G, M, C ( i ) ) = (1103515245 *
( (1103515245 * (G & M )+12345 ) XOR C ( i ) ) + 12345 ) mod 2^31.
When using the dynamic RP, the PIM-SM uses the hash function. The
RP chosen from C-RPs serves the specific multicast group.
I
IGMP The Internet Group Management protocol that is a signaling mechanism
of the host towards the router and is used in IP multicast on the leaf
network. Hosts send an IGMP message to join or leave a multicast
group. Routers periodically send an IGMP message to hosts to check
whether multicast members exist.
J
Join The Join that is applicable to PIM-SM and PIM-DM.
l In PIM-SM, when a member exists in a network segment, the DR of
the network segment sends a Join message to the RP hop by hop. A
multicast route is thus generated. When the RP starts the SPT
switchover, the RP sends a Join message to the source hop by hop.
A multicast route is thus generated.
l In PIM-DM, the Join message is used for prune rejection.
L
Leaf Router The router that connects to user hosts.
Last-hop router The PIM router that directly connects to a multicast group member and
forwards multicast data to the member.

M
MBGP The Multicast BGP mainly refers to the application of Multiprotocol
Border Gateway Protocol (MP-BGP) to multicast. MP-BGP is the
multiprotocol extension of the Border Gateway Protocol (BGP). At
present, the BGP4 protocol is applied only in unicast. MP-BGP enables
BGP4 to support multiple routing protocols including multicast.
Mesh Group If multiple MSDP peers exist in the network, SA message is easily
caused to be flooded among peers. Configuring multiple MSDP peers
to join a Mesh group reduces the number of SA messages transmitted
between these MSDP peers. After receiving an SA message, a member
of the Mesh Group checks the source of the message first:
l If the SA message is from a certain MSDP peer outside the mesh
group. The member performs RPF check on the message. If the
message passes the check, the member forwards it to other members
in the mesh group.
l If the SA message is from a member of the mesh group, the member
does not perform RPF check and directly receives the message. At
the same time, the member does not forward the message to other
members in the mesh group.
MD The Multicast Domains that is an implementation mechanism of
multicast VPN. Only PE needs to support multi-instance. MD is
transparent to CE and P.MD refers to the set of all VPN instances that
can sends and receives multicast packets on each PE. Different VPN
instances belong to different MDs. An MD serves a specific VPN. All
private multicast data transmitted in the VPN is transmitted in the MD.
MDT Multicast Distribution Tree. In the PIM multicast domain, a point to
multi-points multicast forwarding path is set up. The multicast
forwarding path takes a group as unit. As the shape of the multicast
forwarding path likes a tree, it is also called multicast distribution tree.
The characteristic of the multicast distribution is: each link has only one
copy of multicast data, regardless of the number of members in the
network. The multicast data is copies and distributed at as far branch as
possible.
MLD Multicast Listener Discovery (MLD) is a sub-protocol of the Internet
Control Message Protocol Version 6 (ICMPv6) and applicable to IPv6
networks. MLD, whose function and implementation principle are
similar to those of IGMP, is used to set up a multicast group between
hosts and the nearest multicast router and maintain the relationship of
multicast members.
mping Multicast ping (mping) can be used to detect reserved multicast
members on the network segment or detect performance of the network
on bearing multicast services.

MSDP The Multicast Source Discovery Protocol that is applicable only to PIM-
SM and is useful for only Any-Source Multicast (ASM). The MSDP
peers set up by RPs of different PIM-SM domains share the information
on the multicast source by sending Source Active (SA). The inter-
domain multicast is thus implemented. The MSDP peers set up by RPs
of the same PIM-SM domain share the information on the multicast
source by sending Source Active (SA). The Anycast RP is thus
implemented.
MT Multicast Tunnel. In an MD, all PEs connect to an MT, which is equal
to that all PEs connects to the shared network segment. The PEs use MT
to transmit private data.The transmission process of MT is: the local PE
encapsulates a VPN data packet into a public network data packet, and
forwards it in the public network along the MDT. After receiving the
packet, the remote PE decapsulates it and reverts it to the VPN data
packet.
MTI Multicast Tunnel Interface is the outgoing interface or incoming
interface of MT. It is equal to the outgoing interface or incoming
interface of MD. The local PE sends the VPN data from MTI. The
remote PE receives it from MTI. The VRP defines MTI that calls back
the entire MT transmission process.MTI is the channel of the public
network instance and the VPN instance on a PE. PE connects to MT
through MTI, that is, PE connects to the shared network segment. On
each PE, VPN instances that belong to the MD set up PIM neighbor
relationship on the MTI.
mtrace Multicast trace route (mtrace) can be used to trace RPF paths or
multicast paths and applicable to routine maintenance and fault location
of multicast services.
P
PIM The Protocol Independent Multicast that belongs to multicast routing
protocol. Reachable unicast route is the basis of PIM forwarding.
According to the current unicast routing information, PIM performs
RPF check on multicast packets, creates multicast routing entry and
establishes multicast distribution tree.PIM is composed of two
independent protocols, namely PIM-DM and PIM-SM.
PIM-DM Protocol Independent Multicast Dense Mode (PIM-DM) is applicable
to small-scale multicast networks with dense members.
PIM-IPv6 PIM-IPv6 is the PIM protocol used on IPv6 networks. Its functions and
implementation principle are similar to those of PIM.
PIM-IPv6-DM PIM-IPv6-DM is the PIM-DM protocol used on IPv6 networks. Its
functions and implementation principle are similar to those of PIM-DM.
PIM-IPv6-SM PIM-IPv6-SM is the PIM-SM protocol used on IPv6 networks. Its
functions and implementation principle are similar to those of PIM-SM.
PIM-SM Protocol Independent Multicast Sparse Mode (PIM-SM) is applicable
to large-scale multicast networks with scattered members.

Prune The prune that is applicable to PIM-DM and PIM-SM. If there are no
downstream multicast group members, a router sends a prune message
to the upstream node to inform it not to forward any more data to it.
After receiving the prune message, the upstream node removes the
downstream interface from the downstream interface list.
R
Register The register that is applicable only to PIM-SM. When the active
multicast source exists on the network, the router of the first hop
encapsulates multicast data into a Register message, and unicasts the
packet to the RP to create an (S,G) entry on the RP and register the
multicast source information. .
RP The Rendezvous Point that is applicable only to PIM-SM. RP is the
forwarding core of the PIM-SM network. Members send Join message
to the RP and sets up a RPT with itself as root. Multicast source registers
with the RP and creates (S, G) entry on the RP. The multicast source
sends multicast packets to members through RP.
RPF Reverse Path Forwarding is the basis of the multicast routing. routers
perform RPF check on the received packets to create and maintain
multicast routing entries. As a result, the multicast data can be
forwarded along the correct path.After receiving a multicast packet, a
router searches the unicast routing table, MBGP routing table and static
multicast routing table according to the "packet source" to select the
RPF route. If the interface that the packet reaches is the same with the
RPF interface, the RPF check on the packet succeeds. Otherwise, the
RPF check fails.
Rpf route static RPF static route, also called static multicast route, is not used to forward
data. It affects only the RPF check. By configuration the static multicast
route, users can specify the RPF interface and the RPF neighbor for the
specific "packet source" on the current router.
RPT The multicast distribution tree that takes RP as root and multicast group
members as leaf. RPT is applicable only to PIM-SM.
S
SA Source Active is the message type of MSDP message. SA message
contains many groups of (S, G) information or a Register message.
MSDP peers share the multicast source by exchanging SA messages.
SA-Cache After receiving a SA message, an MSDP peer stores the (S, G)
information carried in the SA message to the SA-Cache. When there is
a receiving requirement, the (S, G) message can be obtained from the
SA-Cache.If a router is not configured with the SA-Cache, the router
cannot store the (S, G) entry carried in SA message. If the router need
to receive the packets of (S, G), it has to wait the SA message sent by
its MSDP Peer in the next period.

SA-request When the local MSDP peer has new members, but has no (S, G)
information that meet the requirements, it sends the SA request to the
specified remote MSDP peer. After receiving the SA request message,
the specified remote MSDP peer immediately responds to the SA
request message if it has the (S, G) information that meets the
requirements.
Share-Group A VPN instance uniquely specifies the address of a Share-Group. The
VPN data is transparent to the public network. PE does not distinguish
which multicast group a VPN packet belongs to or whether it is a
protocol packet or a data packet. PE uniformly encapsulates it into a
general public network multicast packet with Share-Group as its group.
The PE then sends it to the public network.
Share-MDT Share-Multicast Distribution Tree. One Share-Group uniquely maps a
MD. It uniquely sets up a Share-Multicast Distribution Tree (Share-
MDT) to guide routers to forward packets. All VPN packets are
forwarded along the Share-MDT; regardless of the PE from which they
enter the public network.
SPT The Shortest Path Tree is a multicast distribution tree that takes the
multicast source as root and multicast group members as leaf. The SPT
is applicable to PIM-DM, PIM-SM and PIM-SSM.
SPT switch The SPT switch is applicable only to the PIM-SM. When the rate of the
Register packet exceeds the threshold, The RP triggers the SPT switch,
sends a Join message to the multicast source, establishes the multicast
path from the source to the RP, and informs the DR not to send Register
message. When the packet rate of the RPT exceeds the threshold, DR
triggers the SPT switch, sends a Join message to the multicast source,
establishes the SPT from the source to the DR, and switch the multicast
data to the SPT.
SSM The Source-Specific Multicast is the technology that is implemented by
PIM-SM.
static-rpf-peer The static RPF peer is the special application of MSDP peer. You can
run the command to specify static RFP peer for the MSDP peer. The
SA message sent by the static RFP peer can be free of RFP check.
Switch-group-pool One Share-Group uniquely confirms a Switch-group-pool. The Switch-
group-pool defines an address scope of a multicast group for the Switch-
MDT switch. When the Switch-MDT is performed, an address that is
used for the smallest times is chosen from the Switch-group-pool. All
VPN multicast packets that enter the public network from a PE are
encapsulated with this Switch-group address.

Switch-MDT Switch-Multicast Distribution Tree. All PEs in the network monitor the
forwarding rate of the Share-MDT. When the forwarding rate of the
data that is sent to the public network through a PE exceeds the
threshold, The PE sends the switch notification to downstream receivers
along the Share-MDT. The switch notification carries the address of the
Switch-group. A Switch-MDT with the PE as source and Switch-group
as group address is set up between the PE and the remote PE. Compared
with Share-MDT, Switch-MDT prunes the remote PE without receiving
requirement. This implements the multicast according to requirements.
All VPN multicast data that enters the public network through the PE
is not encapsulated with the Share-Group address, but is encapsulated
into Switch-group packet of the public network and is forwarded along
the Switch-MDT.
U
Upstream Interface The interface through which the local router receives multicast data.
The router or the multicast source that forwards multicast data to the
local router is called the upstream router or upstream multicast source.
The network segment where the upstream interface resides is called the
upstream network segment.

Configuration Guide - IP Multicast B Acronyms and Abbreviations
B Acronyms and Abbreviations
This appendix collates frequently used acronyms and abbreviations in this document.
A
ASM Any-Source Multicast
B
BGP Border Gateway Protocol
BSR BootStrap Router
C
C-BSR Candidate-BSR
C-RP Candidate-RP
D
DR Designated Router
I
IGMP Internet Group Management Protocol
ISP Internet Service Provider
L
LSP Label Switched Path
Issue 04 (2010-08-31) Huawei Proprietary and Confidential B-1

B Acronyms and Abbreviations Configuration Guide - IP Multicast
MBGP Multicast BGP

MP-BGP Multiprotocol Border Gateway Protocol
MPLS Multiprotocol Label Switching
MSDP Multicast Source Discovery Protocol
MD Multicast Domains
MLD Multicast Listener Discovery
MT Multicast Tunnel
MTI Multicast Tunnel Interface
MTD Multicast Distribution Tree
O
OSPF Open Shortest Path First
P
PIM Protocol Independent Multicast
PIM-DM Protocol Independent Multicast Dense Mode
PIM-SM Protocol Independent Multicast Sparse Mode
R
PR Rendezvous Point
RPF Reverse Path Forwarding
RPT RP Tree
S
SA Source Active
SSM Source-Specific Multicast
SPT Shortest Path Tree
V
VPN Virtual Private Network
B-2 Huawei Proprietary and Confidential Issue 04 (2010-08-31)


Configuration Guide - IP Multicast (V600R001C00 - 04) - NE80E40E

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Guide - IP Multicast (V600R001C00 - 04) - NE80E40E

Uploaded by

Copyright:

Available Formats

HUAWEI NetEngine80E/40E Router

Configuration Guide - IP Multicast

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2010-08-31) Huawei Proprietary and Confidential i

About This Document

Product Name Version

HUAWEI NetEngine80E/40E V600R001C00

1 IP Multicast This chapter describes IP multicast fundamentals,

Issue 04 (2010-08-31) Huawei Proprietary and Confidential iii

2 IGMP Configuration This chapter describes the IGMP fundamentals and

3 Layer 2 Multicast This chapter describes the Layer 2 Multicas fundamentals

6 MSDP Configuration This chapter describes the MSDP fundamentals and

7 MBGP Configuration This chapter describes the MBGP fundamentals and

11 MLD Configuration This chapter describes the MLD fundamentals and

15 Multicast Network This chapter describes the configuration methods and

iv Huawei Proprietary and Confidential Issue 04 (2010-08-31)

A Glossary This appendix collates frequently used glossaries in this

B Acronyms and This appendix collates frequently used acronyms and

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Issue 04 (2010-08-31) Huawei Proprietary and Confidential v

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

# A line starting with the # sign is comments.

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

vi Huawei Proprietary and Confidential Issue 04 (2010-08-31)

Double-click Press the primary mouse button twice continuously and

Updates in Issue 04 (2010-08-31)

Updates in Issue 03 (2010-07-15)

Updates in Issue 02 (2009-12-10)

Updates in Issue 01 (2009-09-05)

Issue 04 (2010-08-31) Huawei Proprietary and Confidential vii

About This Document...................................................................................................................iii

Issue 04 (2010-08-31) Huawei Proprietary and Confidential ix

2.3.5 Checking the Configuration.................................................................................................................2-12

3 Layer 2 Multicast Configuration.............................................................................................3-1

x Huawei Proprietary and Confidential Issue 04 (2010-08-31)

3.2.8 Configuring Prompt Leave for Ports for a VSI....................................................................................3-15

Issue 04 (2010-08-31) Huawei Proprietary and Confidential xi

3.8 Configuring the Network Management Function for Layer 2 Multicast......................................................3-46

xii Huawei Proprietary and Confidential Issue 04 (2010-08-31)

3.14.1 Clearing the Dynamic Port in the Outbound Port Information..........................................................3-74

4 PIM-DM (IPv4) Configuration................................................................................................4-1

Issue 04 (2010-08-31) Huawei Proprietary and Confidential xiii

4.6 Adjusting Control Parameters for State-Refresh...........................................................................................4-18

5 PIM-SM (IPv4) Configuration.................................................................................................5-1

xiv Huawei Proprietary and Confidential Issue 04 (2010-08-31)

5.4.1 Establishing the Configuration Task....................................................................................................5-15

Issue 04 (2010-08-31) Huawei Proprietary and Confidential xv