Download this guide: Multicast Protocols Feature Guide for EX4600 Switches
Add to my manuals
528 Pages
advertisement
Multicast Protocols Feature Guide for EX4600
Switches
Release
15.1
Modified: 2016-03-30
Copyright © 2016, Juniper Networks, Inc.
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000 www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
Multicast Protocols Feature Guide for EX4600 Switches
Release 15.1
Copyright © 2016, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at http://www.juniper.net/support/eula.html
. By downloading, installing or using such software, you agree to the terms and conditions of that EULA.
ii Copyright © 2016, Juniper Networks, Inc.
Table of Contents
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Preserving Multicast Performance by Disabling Response to the ping Utility . . . . . 9
Configuring Interface Priority for PIM Designated Router Selection . . . . . . . . . . . . 15
Configuring PIM Designated Router Election on Point-to-Point Links . . . . . . . . . . 16
Configuring BFD Authentication Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Viewing Authentication Information for BFD Sessions . . . . . . . . . . . . . . . . . . 19
Copyright © 2016, Juniper Networks, Inc.
iii
Multicast Protocols Feature Guide for EX4600 Switches iv
Example: Configuring an SSM-Only Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Example: Configuring Source-Specific Multicast Groups with Any-Source
Example: Configuring SSM Maps for Different Groups to Different Sources . . . . . 49
Multiple SSM Maps and Groups for Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 49
Example: Configuring Multiple SSM Maps Per Interface . . . . . . . . . . . . . . . . . 49
Configuring the Static PIM RP Address on the Non-RP Routing Device . . . . . . . . . 57
Example: Configuring PIM Anycast With or Without MSDP . . . . . . . . . . . . . . . . . . 60
Configuring a PIM Anycast RP Router with MSDP . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring a PIM Anycast RP Router Using Only PIM . . . . . . . . . . . . . . . . . . . . . . 64
Example: Configuring Multiple RPs in a Domain with Anycast RP . . . . . . . . . . . . . 66
Configuring PIM Bootstrap Properties for IPv4 or IPv6 . . . . . . . . . . . . . . . . . . . . . 69
Configuring Register Message Filters on a PIM RP and DR . . . . . . . . . . . . . . . . . . . 79
Copyright © 2016, Juniper Networks, Inc.
Table of Contents
Understanding Multicast Rendezvous Points, Shared Trees, and
Example: Configuring the PIM SPT Threshold Policy . . . . . . . . . . . . . . . . . . . . . . . 92
Understanding Group Membership Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Modifying the IGMP Host-Query Message Interval . . . . . . . . . . . . . . . . . . . . . . . . 105
Modifying the IGMP Last-Member Query Interval . . . . . . . . . . . . . . . . . . . . . . . . . 106
Specifying Immediate-Leave Host Removal for IGMP . . . . . . . . . . . . . . . . . . . . . 107
Filtering Unwanted IGMP Reports at the IGMP Interface Level . . . . . . . . . . . . . . 108
Accepting IGMP Messages from Remote Subnetworks . . . . . . . . . . . . . . . . . . . . 109
Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces . . . . . 120
How IGMP Snooping Works with Routed VLAN Interfaces . . . . . . . . . . . . . . 126
How Hosts Join and Leave Multicast Groups . . . . . . . . . . . . . . . . . . . . . . . . . 126
IGMP Snooping and Forwarding Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Configuring VLAN-Specific IGMP Snooping Parameters . . . . . . . . . . . . . . . . . . . 129
Verifying the IGMP Snooping Group Timeout Value . . . . . . . . . . . . . . . . . . . . . . . 134
Copyright © 2016, Juniper Networks, Inc.
v
Multicast Protocols Feature Guide for EX4600 Switches vi
Modifying the MLD Host-Query Message Interval . . . . . . . . . . . . . . . . . . . . . 145
Modifying the MLD Query Response Interval . . . . . . . . . . . . . . . . . . . . . . . . . 146
Modifying the MLD Last-Member Query Interval . . . . . . . . . . . . . . . . . . . . . . 146
Specifying Immediate-Leave Host Removal for MLD . . . . . . . . . . . . . . . . . . . 147
Filtering Unwanted MLD Reports at the MLD Interface Level . . . . . . . . . . . . 148
Example: Modifying the MLD Robustness Variable . . . . . . . . . . . . . . . . . . . . 149
Limiting the Maximum MLD Message Rate . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Enabling MLD Static Group Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Create a MLD Static Group Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Automatically create static groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Automatically increment group addresses . . . . . . . . . . . . . . . . . . . . . . . 153
Specify multicast source address (in SSM mode) . . . . . . . . . . . . . . . . . 154
Automatically specify multicast sources . . . . . . . . . . . . . . . . . . . . . . . . . 155
Automatically increment source addresses . . . . . . . . . . . . . . . . . . . . . . 156
Exclude multicast source addresses (in SSM mode) . . . . . . . . . . . . . . . 157
Example: Recording MLD Join and Leave Events . . . . . . . . . . . . . . . . . . . . . . 158
Configuring the Number of MLD Multicast Group Joins on Logical
Configuring the Interface to Accept Traffic from a Remote Source . . . . . . . . . . . 170
Example: Configuring MSDP with Active Source Limits and Mesh Groups . . . . . . 172
Example: Configuring PIM Anycast With or Without MSDP . . . . . . . . . . . . . . . . . 178
Configuring a PIM Anycast RP Router with MSDP . . . . . . . . . . . . . . . . . . . . . . . . . 181
Configuration Statements and Operational Commands
Copyright © 2016, Juniper Networks, Inc.
Table of Contents
minimum-interval (PIM BFD Liveness Detection) . . . . . . . . . . . . . . . . . . . . . . . . 223
minimum-interval (PIM BFD Transmit Interval) . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Copyright © 2016, Juniper Networks, Inc.
vii
Multicast Protocols Feature Guide for EX4600 Switches viii
transmit-interval (PIM BFD Liveness Detection) . . . . . . . . . . . . . . . . . . . . . . . . . 249
query-last-member-interval (Protocols IGMP) . . . . . . . . . . . . . . . . . . . . . . . . . . 273
IGMP Snooping Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Copyright © 2016, Juniper Networks, Inc.
Table of Contents
query-last-member-interval (Bridge Domains) . . . . . . . . . . . . . . . . . . . . . . . . . . 298
maximum (MSDP Active Source Messages) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Copyright © 2016, Juniper Networks, Inc.
ix
Multicast Protocols Feature Guide for EX4600 Switches
IGMP Snooping Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
x Copyright © 2016, Juniper Networks, Inc.
Table of Contents
Copyright © 2016, Juniper Networks, Inc.
xi
Multicast Protocols Feature Guide for EX4600 Switches xii Copyright © 2016, Juniper Networks, Inc.
List of Figures
Figure 1: Rendezvous Point As Part of the RPT and SPT . . . . . . . . . . . . . . . . . . . . 25
Figure 3: Receiver Announces Desire to Join Group G and Source S . . . . . . . . . . . 40
Figure 4: Router 3 (Last-Hop Router) Joins the Source Tree . . . . . . . . . . . . . . . . . 40
Figure 5: (S,G) State Is Built Between the Source and the Receiver . . . . . . . . . . . 40
Figure 6: Network on Which to Configure PIM SSM . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 7: Receiver Sends Messages to Join Group G and Source S . . . . . . . . . . . . 46
Figure 8: Router 3 (Last-Hop Router) Joins the Source Tree . . . . . . . . . . . . . . . . . 47
Figure 9: (S,G) State Is Built Between the Source and the Receiver . . . . . . . . . . . 47
Figure 11: Building an RPT Between the RP and the Receiver . . . . . . . . . . . . . . . . . 83
Figure 12: PIM Register Message and PIM Join Message Exchanged . . . . . . . . . . . 84
Figure 13: Traffic Sent from the Source to the RP Router . . . . . . . . . . . . . . . . . . . . 85
Figure 14: Traffic Sent from the RP Router Toward the Receiver . . . . . . . . . . . . . . 85
Figure 15: Receiver DR Sends a PIM Join Message to the Source . . . . . . . . . . . . . . 87
Figure 16: PIM Prune Message Is Sent from the Receiver’s DR Toward the RP
Figure 17: RP Router Receives PIM Prune Message . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 18: RP Router Sends a PIM Prune Message to the Source DR . . . . . . . . . . . 89
Figure 19: Source’s DR Stops Sending Duplicate Multicast Packets Toward the
Figure 24: Reports Are Received by the Querier Routing Device . . . . . . . . . . . . . . 139
Figure 25: Host Has No Interested Receivers and Sends a Done Message to
Figure 26: Host Address Timer Expires and Address Is Removed from Multicast
Copyright © 2016, Juniper Networks, Inc.
xiii
Multicast Protocols Feature Guide for EX4600 Switches
Figure 30: Reports Are Received by the Querier Routing Device . . . . . . . . . . . . . . 142
Figure 31: Host Has No Interested Receivers and Sends a Done Message to
Figure 32: Host Address Timer Expires and Address Is Removed from Multicast
Figure 33: Accepting Multicast Traffic from a Remote Source . . . . . . . . . . . . . . . 170
xiv Copyright © 2016, Juniper Networks, Inc.
List of Tables
Table 6: Components of the IGMP Snooping Topology . . . . . . . . . . . . . . . . . . . . 130
Table 7: Summary of IGMP Snooping Output Fields . . . . . . . . . . . . . . . . . . . . . . . 133
Table 9: Source-Active Message Flooding Explanation . . . . . . . . . . . . . . . . . . . . . 174
Configuration Statements and Operational Commands
Table 14: show multicast flow-map Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 362
Table 17: show multicast next-hops Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 369
Copyright © 2016, Juniper Networks, Inc.
xv
Multicast Protocols Feature Guide for EX4600 Switches
Table 18: show multicast pim-to-igmp-proxy Output Fields . . . . . . . . . . . . . . . . . 371
Table 19: show multicast pim-to-mld-proxy Output Fields . . . . . . . . . . . . . . . . . 373
IGMP Snooping Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Table 36: show igmp-snooping membership Output Fields . . . . . . . . . . . . . . . . 470
Table 37: show igmp-snooping route Output Fields . . . . . . . . . . . . . . . . . . . . . . . 473
Table 38: show igmp-snooping statistics Output Fields . . . . . . . . . . . . . . . . . . . 475
Table 39: show igmp-snooping vlans Output Fields . . . . . . . . . . . . . . . . . . . . . . . 477
Table 42: show msdp source-active Output Fields . . . . . . . . . . . . . . . . . . . . . . . 487
xvi Copyright © 2016, Juniper Networks, Inc.
About the Documentation
•
Documentation and Release Notes on page xvii
•
Supported Platforms on page xvii
•
Using the Examples in This Manual on page xvii
•
Documentation Conventions on page xix
•
Documentation Feedback on page xxi
•
Requesting Technical Support on page xxi
Documentation and Release Notes
To obtain the most current version of all Juniper Networks
® technical documentation, see the product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/ .
If the information in the latest release notes differs from the information in the documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at http://www.juniper.net/books .
Supported Platforms
For the features described in this document, the following platforms are supported:
• EX Series
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load merge relative command. These commands cause the software to merge the incoming configuration into the current candidate configuration. The example does not become active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example is a full example. In this case, use the load merge command.
Copyright © 2016, Juniper Networks, Inc.
xvii
Multicast Protocols Feature Guide for EX4600 Switches
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the load merge relative command. These procedures are described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1.
From the HTML or PDF version of the manual, copy a configuration example into a text file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following configuration to a file and name the file ex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system { scripts { commit { file ex-script.xsl;
}
}
} interfaces { fxp0 { disable; unit 0 { family inet { address 10.0.0.1/24;
}
}
}
}
2.
Merge the contents of the file into your routing platform configuration by issuing the load merge configuration mode command:
[edit] user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
1.
From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file ex-script-snippet.conf
. Copy the ex-script-snippet.conf file to the /var/tmp directory on your routing platform.
commit { file ex-script-snippet.xsl; }
2.
Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode command: xviii Copyright © 2016, Juniper Networks, Inc.
About the Documentation
[edit] user@host# edit system scripts
[edit system scripts]
3.
Merge the contents of the file into your routing platform configuration by issuing the load merge relative configuration mode command:
[edit system scripts] user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see the CLI User Guide.
Documentation Conventions
defines notice icons used in this guide.
Table 1: Notice Icons
Icon Meaning
Informational note
Description
Indicates important features or instructions.
Caution Indicates a situation that might result in loss of data or hardware damage.
Warning Alerts you to the risk of personal injury or death.
Laser warning
Tip
Best practice
Alerts you to the risk of personal injury from a laser.
Indicates helpful information.
Alerts you to a recommended use or implementation.
defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Convention Description Examples
Bold text like this Represents text that you type.
To enter configuration mode, type the configure command: user@host> configure
Copyright © 2016, Juniper Networks, Inc.
xix
Multicast Protocols Feature Guide for EX4600 Switches
Table 2: Text and Syntax Conventions (continued)
Convention Description
Fixed-width text like this
Italic text like this
Italic text like this
Text like this
Examples
Represents output that appears on the terminal screen.
user@host> show chassis alarms
No alarms currently active
•
•
•
Introduces or emphasizes important new terms.
Identifies guide names.
Identifies RFC and Internet draft titles.
•
•
•
A policy term is a named structure that defines match conditions and actions.
Junos OS CLI User Guide
RFC 1997, BGP Communities Attribute
Represents variables (options for which you substitute a value) in commands or configuration statements.
Configure the machine’s domain name:
[edit] root@# set system domain-name domain-name
Represents names of configuration statements, commands, files, and directories; configuration hierarchy levels; or labels on routing platform components.
•
•
To configure a stub area, include the stub statement at the [edit protocols ospf area area-id] hierarchy level.
The console port is labeled CONSOLE .
< > (angle brackets)
| (pipe symbol)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
Encloses optional keywords or variables.
stub <default-metric metric>;
Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity.
broadcast | multicast
(string1 | string2 | string3)
Indicates a comment specified on the same line as the configuration statement to which it applies.
rsvp { # Required for dynamic MPLS only
Encloses a variable for which you can substitute one or more values.
Identifies a level in the configuration hierarchy.
Identifies a leaf statement at a configuration hierarchy level.
community name members [
community-ids ]
[edit] routing-options { static { route default { nexthop address; retain;
}
}
}
GUI Conventions
Bold text like this Represents graphical user interface (GUI) items you click or select.
•
•
In the Logical Interfaces box, select
All Interfaces .
To cancel the configuration, click
Cancel .
xx Copyright © 2016, Juniper Networks, Inc.
About the Documentation
Table 2: Text and Syntax Conventions (continued)
Convention Description
> (bold right angle bracket)
Examples
Separates levels in a hierarchy of menu selections.
In the configuration editor hierarchy, select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can provide feedback by using either of the following methods:
• Online feedback rating system—On any page of the Juniper Networks TechLibrary site at http://www.juniper.net/techpubs/index.html
, simply click the stars to rate the content, and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at http://www.juniper.net/techpubs/feedback/ .
• E-mail—Send your comments to [email protected]. Include the document or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.
• JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf
.
• Product warranties—For product warranty information, visit http://www.juniper.net/support/warranty/ .
• JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:
• Find CSC offerings: http://www.juniper.net/customers/support/
• Search for known bugs: http://www2.juniper.net/kb/
• Find product documentation: http://www.juniper.net/techpubs/
• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
Copyright © 2016, Juniper Networks, Inc.
xxi
Multicast Protocols Feature Guide for EX4600 Switches
• Download the latest versions of software and review release notes: http://www.juniper.net/customers/csc/software/
• Search technical bulletins for relevant hardware and software notifications: http://kb.juniper.net/InfoCenter/
• Join and participate in the Juniper Networks Community Forum: http://www.juniper.net/company/communities/
• Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
• Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .
• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see http://www.juniper.net/support/requesting-support.html
.
xxii Copyright © 2016, Juniper Networks, Inc.
PART 1
PIM
•
•
Using PIM Sparse Mode on page 23
•
Using Source-Specific Multicast on page 37
•
•
•
Using PIM Bootstrap Router on page 69
•
Using PIM Filtering on page 73
•
Using PIM RPT and SPT Cutover on page 81
Copyright © 2016, Juniper Networks, Inc.
1
Multicast Protocols Feature Guide for EX4600 Switches
2 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 1
Using PIM Basics
•
•
PIM on Aggregated Interfaces on page 6
•
Changing the PIM Version on page 6
•
Modifying the PIM Hello Interval on page 6
•
Understanding Multicast VLAN Registration on page 7
•
Preserving Multicast Performance by Disabling Response to the ping Utility on page 9
•
Configuring PIM Trace Options on page 10
•
•
Configuring Interface Priority for PIM Designated Router Selection on page 15
•
Configuring PIM Designated Router Election on Point-to-Point Links on page 16
•
Configuring BFD for PIM on page 16
•
Configuring BFD Authentication for PIM on page 18
PIM Overview
The predominant multicast routing protocol in use on the Internet today is Protocol
Independent Multicast, or PIM. The type of PIM used on the Internet is PIM sparse mode.
PIM sparse mode is so accepted that when the simple term “PIM” is used in an Internet context, some form of sparse mode operation is assumed.
PIM emerged as an algorithm to overcome the limitations of dense-mode protocols such as the Distance Vector Multicast Routing Protocol (DVMRP), which was efficient for dense clusters of multicast receivers, but did not scale well for the larger, sparser, groups encountered on the Internet. The Core Based Trees (CBT) Protocol was intended to support sparse mode as well, but CBT, with its all-powerful core approach, made placement of the core critical, and large conference-type applications (many-to-many) resulted in bottlenecks in the core. PIM was designed to avoid the dense-mode scaling issues of DVMRP and the potential performance issues of CBT at the same time.
PIM is one of the most rapidly evolving specifications on the Internet today. Since its introduction in 1995, PIM has already seen two major revisions to its packet structure
(PIM version 1 [PIMv1] and PIM version 2 [PIMv2]), two major RFCs (RFC 2362 obsoleted
RFC 2117), and numerous drafts describing major components of PIM, such as many-to-many trees and source-specific multicast (SSM). Long-lasting RFCs are not a
Copyright © 2016, Juniper Networks, Inc.
3
Multicast Protocols Feature Guide for EX4600 Switches
4 feature of PIM, and virtually all of PIM must be researched, understood, and implemented directly from Internet drafts. In fact, no current RFC describes PIMv1 at all. The drafts have all expired, and PIMv1 was never issued as an official RFC.
PIM itself is not nonstandard or unstable, however. PIM has been a promising multicast routing protocol since its inception, especially PIM sparse mode, the first real sparse-mode multicast routing protocol. Work continues on PIM in a number of areas, from bidirectional trees to network management, and the rapid pace of development makes drafts essential for PIM.
PIMv1 and PIMv2 can coexist on the same router and even on the same interface. The main difference between PIMv1 and PIMv2 is the packet format. PIMv1 messages use
Internet Group Management Protocol (IGMP) packets, whereas PIMv2 has its own IP protocol number (103) and packet structure. All routers connecting to an IP subnet such as a LAN must use the same PIM version. Some PIM implementations can recognize
PIMv1 packets and automatically switch the router interface to PIMv1. Because the difference between PIMv1 and PIMv2 involves the message format, but not the meaning of the message or how the router processes the PIM message, a router can easily mix
PIMv1 and PIMv2 interfaces.
PIM is used for efficient routing to multicast groups that might span wide-area and interdomain internetworks. It is called “protocol independent” because it does not depend on a particular unicast routing protocol. Junos OS supports bidirectional mode, sparse mode, dense mode, and sparse-dense mode.
PIM operates in several modes: bidirectional mode, sparse mode, dense mode, and sparse-dense mode. In sparse-dense mode, some multicast groups are configured as dense mode (flood-and-prune, [S,G] state) and others are configured as sparse mode
(explicit join to rendezvous point [RP], [*,G] state).
PIM drafts also establish a mode known as PIM source-specific mode, or PIM SSM. In
PIM SSM there is only one specific source for the content of a multicast group within a given domain.
Because the PIM mode you choose determines the PIM configuration properties, you first must decide whether PIM operates in bidirectional, sparse, dense, or sparse-dense mode in your network. Each mode has distinct operating advantages in different network environments.
• In sparse mode, routers must join and leave multicast groups explicitly. Upstream routers do not forward multicast traffic to a downstream router unless the downstream router has sent an explicit request (by means of a join message) to the rendezvous point (RP) router to receive this traffic. The RP serves as the root of the shared multicast delivery tree and is responsible for forwarding multicast data from different sources to the receivers.
Sparse mode is well suited to the Internet, where frequent interdomain join messages and prune messages are common.
• Bidirectional PIM is similar to sparse mode, and is especially suited to applications that must scale to support a large number of dispersed sources and receivers. In bidirectional
PIM, routers build shared bidirectional trees and do not switch to a source-based tree.
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics
Bidirectional PIM scales well because it needs no source-specific (S,G) state. Instead, it builds only group-specific (*,G) state.
• Unlike sparse mode and bidirectional mode, in which data is forwarded only to routers sending an explicit PIM join request, dense mode implements a flood-and-prune mechanism, similar to the Distance Vector Multicast Routing Protocol (DVMRP). In dense mode, a router receives the multicast data on the incoming interface, then forwards the traffic to the outgoing interface list. Flooding occurs periodically and is used to refresh state information, such as the source IP address and multicast group pair. If the router has no interested receivers for the data, and the outgoing interface list becomes empty, the router sends a PIM prune message upstream.
Dense mode works best in networks where few or no prunes occur. In such instances, dense mode is actually more efficient than sparse mode.
• Sparse-dense mode, as the name implies, allows the interface to operate on a per-group basis in either sparse or dense mode. A group specified as “dense” is not mapped to an RP. Instead, data packets destined for that group are forwarded by means of PIM dense mode rules. A group specified as “sparse” is mapped to an RP, and data packets are forwarded by means of PIM sparse-mode rules. Sparse-dense mode is useful in networks implementing auto-RP for PIM sparse mode.
NOTE: On SRX Series devices, PIM does not support upstream and downstream interfaces across different virtual routers in flow mode.
Basic PIM Network Components
PIM dense mode requires only a multicast source and series of multicast-enabled routers running PIM dense mode to allow receivers to obtain multicast content. Dense mode makes sure that all multicast traffic gets everywhere by periodically flooding the network with multicast traffic, and relies on prune messages to make sure that subnets where all receivers are uninterested in that particular multicast group stop receiving packets.
PIM sparse mode is more complicated and requires the establishment of special routers called rendezvous points (RPs) in the network core. These routers are where upstream join messages from interested receivers meet downstream traffic from the source of the multicast group content. A network can have many RPs, but PIM sparse mode allows only one RP to be active for any multicast group.
If there is only one RP in a routing domain, the RP and adjacent links might become congested and form a single point of failure for all multicast traffic. Thus, multiple RPs are the rule, but the issue then becomes how other multicast routers find the RP that is the source of the multicast group the receiver is trying to join. This RP-to-group mapping is controlled by a special bootstrap router (BSR) running the PIM BSR mechanism. There can be more than one bootstrap router as well, also for single-point-of-failure reasons.
The bootstrap router does not have to be an RP itself, although this is a common implementation. The bootstrap router's main function is to manage the collection of RPs and allow interested receivers to find the source of their group's multicast traffic.
Copyright © 2016, Juniper Networks, Inc.
5
Multicast Protocols Feature Guide for EX4600 Switches
PIM SSM can be seen as a subset of a special case of PIM sparse mode and requires no specialized equipment other than that used for PIM sparse mode (and IGMP version 3).
Bidirectional PIM RPs, unlike RPs for PIM sparse mode, do not need to perform PIM
Register tunneling or other specific protocol action. Bidirectional PIM RPs implement no specific functionality. RP addresses are simply a location in the network to rendezvous toward. In fact, for bidirectional PIM, RP addresses need not be loopback interface addresses or even be addresses configured on any router, as long as they are covered by a subnet that is connected to a bidirectional PIM-capable router and advertised to the network.
Related
Documentation
• Supported IP Multicast Protocol Standards
PIM on Aggregated Interfaces
If you configure PIM on an aggregated (ae- or as-) interface, each of the interfaces in the aggregate is included in the multicast output interface list and carries the single stream of replicated packets in a load-sharing fashion. The multicast aggregate interface is
“expanded” into its constituent interfaces in the next-hop database.
Related
Documentation
•
•
Changing the PIM Version
All systems on a subnet must run the same version of PIM.
The default PIM version can be version 1 or version 2, depending on the mode you are configuring. PIMv1 is the default for rendezvous point (RP) mode (at the [edit protocols pim rp static address address] hierarchy level). However, PIMv2 is the default for interface mode (at the [edit protocols pim interface interface-name] hierarchy level). Explicitly configured versions override the defaults.
To configure the PIM version, include the version statement:
(1 | 2);
Modifying the PIM Hello Interval
Routing devices send hello messages at a fixed interval on all PIM-enabled interfaces.
By using hello messages, routing devices advertise their existence as PIM routing devices on the subnet. With all PIM-enabled routing devices advertised, a single designated router for the subnet is established.
When a routing device is configured for PIM, it sends a hello message at a 30-second default interval. The interval range is from 0 through 255. When the interval counts down to 0, the routing device sends another hello message, and the timer is reset. A routing device that receives no response from a neighbor in 3.5 times the interval value drops
6 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics the neighbor. In the case of a 30-second interval, the amount of time a routing device waits for a response is 105 seconds.
If a PIM hello message contains the hold-time option, the neighbor timeout is set to the hold-time sent in the message. If a PIM hello message does not contain the hold-time option, the neighbor timeout is set to the default hello hold time.
To modify how often the routing device sends hello messages out of an interface:
1.
This example shows the configuration for the routing instance. Configure the interface globally or in the routing instance.
[edit routing-instances PIM.master protocols pim interface fe-3/0/2.0] user@host# set
255
2.
Verify the configuration by checking the Hello Option Holdtime field in the output of the show pim neighbors detail command.
user@host> show pim neighbors detail
Instance: PIM.master
Interface: fe-3/0/2.0
Address: 192.168.195.37, IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 255 seconds
Hello Option DR Priority: 1
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Rx Join: Group Source Timeout
225.1.1.1 192.168.195.78 0
225.1.1.1 0
Interface: lo0.0
Address: 10.255.245.91, IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 255 seconds
Hello Option DR Priority: 1
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Interface: pd-6/0/0.32768
Address: 0.0.0.0, IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 255 seconds
Hello Option DR Priority: 0
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Related
Documentation
•
show pim neighbors on page 419
Understanding Multicast VLAN Registration
Multicast VLAN registration (MVR) enables you to efficiently distribute IPTV multicast streams across an Ethernet ring-based Layer 2 network and reduce the amount of bandwidth consumed by this multicast traffic.
In a standard Layer 2 network, a multicast stream received on one VLAN is never distributed to interfaces outside that VLAN. If hosts in multiple VLANs request the same multicast stream, a separate copy of that multicast stream is distributed to the requesting
VLANs.
Copyright © 2016, Juniper Networks, Inc.
7
Multicast Protocols Feature Guide for EX4600 Switches
How MVR Works
MVR introduces the concept of a multicast source VLAN (MVLAN), which is created by
MVR and becomes the only VLAN over which IPTV multicast traffic flows throughout the Layer 2 network. A Juniper Networks EX Series switch or QFX Series switch that is enabled for MVR selectively forwards IPTV multicast traffic from interfaces on the MVLAN
(source interfaces) to hosts that are connected to interfaces that are not part of the
MVLAN. These interfaces are known as MVR receiver ports. The MVR receiver ports can receive traffic from a port on the MVLAN but cannot send traffic onto the MVLAN, and they remain in their own VLANs for bandwidth and security reasons.
This topic includes:
•
In many ways, MVR is similar to IGMP snooping. Both MVR and IGMP snooping monitor
IGMP join and leave messages and build forwarding tables based on the media access control (MAC) addresses of the hosts sending those IGMP messages. Whereas IGMP snooping operates within a given VLAN to regulate multicast traffic, MVR can operate with hosts on different VLANs in a Layer 2 network to selectively deliver IPTV multicast traffic to requesting hosts, thereby reducing the amount of bandwidth needed to forward multicast traffic.
When you configure an MVLAN, you assign a range of multicast group addresses to it.
You then configure other VLANs to be MVR receiver VLANs, which receive multicast streams from the MVLAN. The MVR receiver ports comprise all the interfaces that exist on any of the MVR receiver VLANs. Interfaces that are on the MVLAN itself cannot be
MVR receiver ports for that MVLAN.
NOTE: MVR is supported on VLANs running IGMP version 2 (IGMPv2) only.
MVR Modes
MVR operates in two modes: MVR transparent mode and MVR proxy mode. Both modes enable MVR to forward only one copy of a multicast stream to the Layer 2 network.
•
MVR Transparent Mode on page 8
•
MVR Transparent Mode
In MVR transparent mode, the switch receives one copy of each IPTV multicast stream and then replicates the stream only to those hosts that want to receive it, while forwarding all other types of multicast traffic without modification. Transparent mode is the default mode.
The switch handles IGMP packets destined for both the multicast source VLAN and multicast receiver VLANs in the same way that it handles them when MVR is not being used. That is, when a host on a VLAN sends IGMP join and leave messages, the switch
8 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics floods the messages to all router interfaces in the VLAN. Similarly, when a VLAN receives
IGMP queries from its router interfaces, it floods the queries to all interfaces in the VLAN.
If a host on a multicast receiver port joins an MVR group on the multicast receiver VLAN, the appropriate bridging entry is added and the MVLAN forwards that group’s IPTV multicast traffic on that port (even though that port is not in the MVLAN). Likewise, if a host on a multicast receiver port leaves an MVR group on the multicast receiver VLAN, the appropriate bridging entry is deleted, and the MVLAN stops forwarding that group’s
IPTV multicast traffic on that port. In addition, you can configure the switch to statically install the bridging entries on the multicast receiver VLAN.
MVR Proxy Mode
When you use MVR in proxy mode, the switch acts as a proxy for any MVR group in both the upstream and downstream directions. In the downstream direction, the switch acts as the querier for the groups in the MVR receiver VLANs. In the upstream direction, the switch originates the IGMP reports and leaves and answers IGMP queries from multicast routers. When the MVR receiver VLANs receive IGMP joins and leaves, the switch creates bridging entries on the MVLAN as needed, as it does in MVR transparent mode. In addition, the switch sends out IGMP joins and leaves on the MVLAN based on these bridging entries.
Configuring MVR proxy mode on the MVLAN automatically enables IGMP snooping proxy mode on all MVR receiver VLANs as well as on the MVLAN.
Related
Documentation
• Understanding FIP Snooping, FBF, and MVR Filter Scalability
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure)
Preserving Multicast Performance by Disabling Response to the ping Utility
The ping utility uses ICMP Echo messages to verify connectivity to any device with an IP address. However, in the case of multicast applications, a single ping sent to a multicast address can degrade the performance of routers because the stream of packets is replicated multiple times.
You can disable the router's response to ping (ICMP Echo) packets sent to multicast addresses. The system responds normally to unicast ping packets.
To disable the router's response to ping packets sent to multicast addresses:
1.
Include the no-multicast-echo statement:
[edit system] user@host# set no-multicast-echo
2.
Verify the configuration by checking the echo drops with broadcast or multicast destination address field in the output of the show system statistics icmp command.
user@host> show system statistics icmp icmp:
0 drops due to rate limit
0 calls to icmp_error
Copyright © 2016, Juniper Networks, Inc.
9
Multicast Protocols Feature Guide for EX4600 Switches
0 errors not generated because old message was icmp
Output histogram: echo reply: 21
0 messages with bad code fields
0 messages less than the minimum length
0 messages with bad checksum
0 messages with bad source address
0 messages with bad length
100 echo drops with broadcast or multicast destination address
0 timestamp drops with broadcast or multicast destination address
Input histogram: echo: 21
21 message responses generated
Related
Documentation
• Configuring Junos OS to Disable the Routing Engine Response to Multicast Ping Packets
• show system statistics icmp
Configuring PIM Trace Options
Tracing operations record detailed messages about the operation of routing protocols, such as the various types of routing protocol packets sent and received, and routing policy actions. You can specify which trace operations are logged by including specific tracing flags. The following table describes the flags that you can include.
Flag all assert autorp bidirectional-df-election bootstrap general graft hello join mdt
Description
Trace all operations.
Trace assert messages, which are used to resolve which of the parallel routers connected to a multiaccess LAN is responsible for forwarding packets to the LAN.
Trace bootstrap, RP, and auto-RP messages.
Trace bidirectional PIM designated-forwarder (DF) election events.
Trace bootstrap messages, which are sent periodically by the PIM domain's bootstrap router and are forwarded, hop by hop, to all routers in that domain.
Trace general events.
Trace graft and graft acknowledgment messages.
Trace hello packets, which are sent so that neighboring routers can discover one another.
Trace join messages, which are sent to join a branch onto the multicast distribution tree.
Trace messages related to multicast data tunnels.
10 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics
Flag normal nsr-synchronization packets policy prune register route rp state task timer
Description
Trace normal events.
Trace nonstop routing synchronization events
Trace all PIM packets.
Trace poison-route-reverse packets.
Trace prune messages, which are sent to prune a branch off the multicast distribution tree.
Trace register and register-stop messages. Register messages are sent to the RP when a multicast source first starts sending to a group.
Trace routing information.
Trace candidate RP advertisements.
Trace state transitions.
Trace task processing.
Trace timer processing.
In the following example, tracing is enabled for all routing protocol packets. Then tracing is narrowed to focus only on PIM packets of a particular type.
To configure tracing operations for PIM:
1.
(Optional) Configure tracing at the [routing-options hierarchy level to trace all protocol packets.
[edit routing-options traceoptions] user@host# set file all-packets-trace user@host# set flag all
2.
Configure the filename for the PIM trace file.
[edit protocols pim
] user@host# set file pim-trace
3.
(Optional) Configure the maximum number of trace files.
[edit protocols pim
] user@host# set file files 5
4.
(Optional) Configure the maximum size of each trace file.
[edit protocols pim
] user@host# set file size 1m
5.
(Optional) Enable unrestricted file access.
Copyright © 2016, Juniper Networks, Inc.
11
Multicast Protocols Feature Guide for EX4600 Switches
[edit protocols pim
] user@host# set file world-readable
6.
Configure tracing flags.
Suppose you are troubleshooting issues with PIM version 1 control packets that are received on an interface configured for PIM version 2. The following example shows how to trace messages associated with this problem.
[edit protocols pim
] user@host# set flag packets | match “Rx V1 Require V2”
7.
View the trace file.
user@host> file list /var/log user@host> file show /var/log/pim-trace
Related
Documentation
•
• Tracing and Logging Junos OS Operations
Disabling PIM
By default, when configured, the PIM protocol is enabled on all interfaces for all families.
If desired, you can disable PIM at the protocol, interface, or family hierarchy levels.
The hierarchy in which you configure PIM is critical. In general, the most specific configuration takes precedence. However, if PIM is disabled at the protocol level, then any disable statements with respect to an interface or family are ignored.
For example, the order of precedence for disabling PIM on a particular interface family is:
1.
If PIM is disabled at the [edit protocols pim interface interface-name family] hierarchy level, then PIM is disabled for that interface family.
2.
If PIM is not configured at the [edit protocols pim interface interface-name family] hierarchy level, but is disabled at the [edit protocols pim interface interface-name] hierarchy level, then PIM is disabled for all families on the specified interface.
3.
If PIM is not configured at either the [edit protocols pim interface interface-name family] hierarchy level or the [edit protocols pim interface interface-name] hierarchy level, but is disabled at the [edit protocols pim] hierarchy level, then the PIM protocol is disabled globally for all interfaces and all families.
The following sections describe how to disable PIM at the various hierarchy levels.
•
Disabling the PIM Protocol on page 13
•
Disabling PIM on an Interface on page 13
•
Disabling PIM for a Family on page 14
•
Disabling PIM for a Rendezvous Point on page 14
12 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics
Disabling the PIM Protocol
You can explicitly disable the PIM protocol. Disabling the PIM protocol disables the protocol for all interfaces and all families. This is accomplished at the [edit protocols pim] hierarchy level:
[edit protocols] pim { disable;
}
To disable the PIM protocol:
1.
Include the disable statement.
2.
user@host# set protocols pim disable
(Optional) Verify your configuration settings before committing them by using the show protocols pim command.
user@host# run show protocols pim
Disabling PIM on an Interface
You can disable the PIM protocol on a per-interface basis. This is accomplished at the
[edit protocols pim interface interface-name] hierarchy level:
[edit protocols] pim { interface interface-name { disable;
}
}
To disable PIM on an interface:
1.
Include the disable statement.
2.
user@host# set protocols pim interface fe-0/1/0 disable
(Optional) Verify your configuration settings before committing them by using the show protocols pim command.
user@host# run show protocols pim
Copyright © 2016, Juniper Networks, Inc.
13
Multicast Protocols Feature Guide for EX4600 Switches
Disabling PIM for a Family
You can disable the PIM protocol on a per-family basis. This is accomplished at the [edit protocols pim family] hierarchy level:
[edit protocols] pim { family inet { disable;
} family inet6 { disable;
}
}
To disable PIM for a family:
1.
Include the disable statement.
2.
user@host# set protocols pim family inet disable user@host# set protocols pim family inet6 disable
(Optional) Verify your configuration settings before committing them by using the show protocols pim command.
user@host# run show protocols pim
Disabling PIM for a Rendezvous Point
You can disable the PIM protocol for a rendezvous point (RP) on a per-family basis. This is accomplished at the [edit protocols pim rp local family] hierarchy level:
[edit protocols] pim { rp { local { family inet { disable;
} family inet6 { disable;
}
}
}
}
To disable PIM for an RP family:
1.
Use the disable statement.
2.
user@host# set protocols pim rp local family inet disable user@host# set protocols pim rp local family inet6 disable
(Optional) Verify your configuration settings before committing them by using the show protocols pim command.
user@host# run show protocols pim
14 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics
Configuring Interface Priority for PIM Designated Router Selection
A designated router (DR) sends periodic join messages and prune messages toward a group-specific rendezvous point (RP) for each group for which it has active members.
When a Protocol Independent Multicast (PIM) router learns about a source, it originates a Multicast Source Discovery Protocol (MSDP) source-address message if it is the DR on the upstream interface.
By default, every PIM interface has an equal probability (priority 1) of being selected as the DR. Configuring the interface DR priority helps ensure that changing an IP address does not alter your forwarding model.
To configure the interface designated router priority:
1.
This example shows the configuration for the routing instance. Configure the interface globally or in the routing instance.
[edit routing-instances PIM.master protocols pim interface ge-0/0/0.0 family inet] user@host# set
5
2.
Verify the configuration by checking the Hello Option DR Priority field in the output of the show pim neighbors detail command.
user@host> show pim neighbors detail
Instance: PIM.master
Interface: ge-0/0/0.0
Address: 192.168.195.37, IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 5
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Rx Join: Group Source Timeout
225.1.1.1 192.168.195.78 0
225.1.1.1 0
Interface: lo0.0
Address: 10.255.245.91, IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Interface: pd-6/0/0.32768
Address: 0.0.0.0, IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 0
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Related
Documentation
•
Configuring PIM Designated Router Election on Point-to-Point Links on page 16
•
Understanding PIM Sparse Mode on page 23
•
show pim neighbors on page 419
Copyright © 2016, Juniper Networks, Inc.
15
Multicast Protocols Feature Guide for EX4600 Switches
Configuring PIM Designated Router Election on Point-to-Point Links
To comply with the latest PIM drafts, enable designated router (DR) election on all PIM interfaces, including point-to-point (P2P) interfaces. (DR election is enabled by default on all other interfaces.) One of the two routers might join a multicast group on its P2P link interface. The DR on that link is responsible for initiating the relevant join messages.
To enable DR election on point-to-point interfaces:
1.
On both point-to-point link routers, configure the router globally or in the routing instance. This example shows the configuration for the routing instance.
[edit routing-instances PIM.master protocols pim] user@host# set
2.
Verify the configuration by checking the State field in the output of the show pim interfaces command. The possible values for the State field are DR, NotDR, and P2P.
When a point-to-point link interface is elected to be the DR, the interface state becomes DR instead of P2P.
3.
If the show pim interfaces command continues to report the P2P state, consider running the restart routing command on both routers on the point-to-point link. Then recheck the state.
CAUTION: Do not restart a software process unless specifically asked to do so by your Juniper Networks customer support representative.
Restarting a software process during normal operation of a routing platform could cause interruption of packet forwarding and loss of data.
[edit] user@host# run restart routing
Related
Documentation
•
Understanding PIM Sparse Mode on page 23
•
Configuring Interface Priority for PIM Designated Router Selection on page 15
•
show pim interfaces on page 395
Configuring BFD for PIM
The Bidirectional Forwarding Detection (BFD) Protocol is a simple hello mechanism that detects failures in a network. BFD works with a wide variety of network environments and topologies. A pair of routing devices exchanges BFD packets. Hello packets are sent at a specified, regular interval. A neighbor failure is detected when the routing device stops receiving a reply after a specified interval. The BFD failure detection timers have shorter time limits than the Protocol Independent Multicast (PIM) hello hold time, so they provide faster detection.
The BFD failure detection timers are adaptive and can be adjusted to be faster or slower.
The lower the BFD failure detection timer value, the faster the failure detection and vice
16 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics versa. For example, the timers can adapt to a higher value if the adjacency fails (that is, the timer detects failures more slowly). Or a neighbor can negotiate a higher value for a timer than the configured value. The timers adapt to a higher value when a BFD session flap occurs more than three times in a span of 15 seconds. A back-off algorithm increases the receive (Rx) interval by two if the local BFD instance is the reason for the session flap. The transmission (Tx) interval is increased by two if the remote BFD instance is the reason for the session flap. You can use the clear bfd adaptation command to return BFD interval timers to their configured values. The clear bfd adaptation command is hitless, meaning that the command does not affect traffic flow on the routing device.
You must specify the minimum transmit and minimum receive intervals to enable BFD on PIM.
To enable failure detection:
1.
Configure the interface globally or in a routing instance.
This example shows the global configuration.
[edit protocols pim] user@host# edit interface fe-1/0/0.0 family inet
2.
Configure the minimum transmit interval.
This is the minimum interval after which the routing device transmits hello packets to a neighbor with which it has established a BFD session. Specifying an interval smaller than 300 ms can cause undesired BFD flapping.
[edit protocols pim interface fe-1/0/0.0 family inet
] user@host# set transmit-interval 350
3.
Configure the minimum interval after which the routing device expects to receive a reply from a neighbor with which it has established a BFD session.
Specifying an interval smaller than 300 ms can cause undesired BFD flapping.
[edit protocols pim interface fe-1/0/0.0 family inet
] user@host# set
350
4.
(Optional) Configure other BFD settings.
As an alternative to setting the receive and transmit intervals separately, configure one interval for both.
[edit protocols pim interface fe-1/0/0.0 family inet
] user@host# set
350
5.
Configure the threshold for the adaptation of the BFD session detection time.
When the detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent.
[edit protocols pim interface fe-1/0/0.0 family inet
] user@host# set detection-time threshold 800
6.
Configure the number of hello packets not received by a neighbor that causes the originating interface to be declared down.
[edit protocols pim interface fe-1/0/0.0 family inet
]
Copyright © 2016, Juniper Networks, Inc.
17
Multicast Protocols Feature Guide for EX4600 Switches user@host# set
50
7.
Configure the BFD version.
[edit protocols pim interface fe-1/0/0.0 family inet
] user@host# set
1
8.
Specify that BFD sessions should not adapt to changing network conditions.
We recommend that you not disable BFD adaptation unless it is preferable not to have BFD adaptation enabled in your network.
[edit protocols pim interface fe-1/0/0.0 family inet
] user@host# set no-adaptation
9.
Verify the configuration by checking the output of the show bfd session command.
Related
Documentation
• show bfd session
Configuring BFD Authentication for PIM
Beginning with Junos OS Release 9.6, you can configure authentication for Bidirectional
Forwarding Detection (BFD) sessions running over Protocol Independent Multicast (PIM).
Routing instances are also supported. The following steps are needed to configure authentication on a BFD session:
1.
Specify the BFD authentication algorithm for the PIM protocol.
2.
Associate the authentication keychain with the PIM protocol.
3.
Configure the related security authentication keychain.
The following sections provide instructions for configuring and viewing BFD authentication on PIM:
•
Configuring BFD Authentication Parameters on page 18
•
Viewing Authentication Information for BFD Sessions on page 19
Configuring BFD Authentication Parameters
BFD authentication is only supported in the Canada and United States version of the
Junos OS image and is not available in the export version.
To configure BFD authentication:
1.
Specify the algorithm (keyed-md5, keyed-sha-1, meticulous-keyed-md5, meticulous-keyed-sha-1 , or simple-password) to use for BFD authentication on a PIM route or routing instance.
[edit protocols pim] user@host# set interface ge-0/1/5 family inet bfd-liveness-detection authentication algorithm keyed-sha-1
18 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics
NOTE: Nonstop active routing (NSR) is not supported with the meticulous-keyed-md5 and meticulous-keyed-sha-1 authentication algorithms. BFD sessions using these algorithms might go down after a switchover.
2.
Specify the keychain to be used to associate BFD sessions on the specified PIM route or routing instance with the unique security authentication keychain attributes.
The keychain you specify must match the keychain name configured at the [edit security authentication key-chains] hierarchy level.
[edit protocols pim] user@host# set interface ge-0/1/5 family inet bfd-liveness-detection authentication keychain bfd-pim
NOTE: The algorithm and keychain must be configured on both ends of the BFD session, and they must match. Any mismatch in configuration prevents the BFD session from being created.
3.
Specify the unique security authentication information for BFD sessions:
• The matching keychain name as specified in Step
• At least one key, a unique integer between 0 and 63. Creating multiple keys allows multiple clients to use the BFD session.
• The secret data used to allow access to the session.
• The time at which the authentication key becomes active, in the format
yyyy-mm-dd.hh:mm:ss.
[edit security] user@host# set authentication-key-chains key-chain bfd-pim key 53 secret
$9$ggaJDmPQ6/tJgF/AtREVsyPsnCtUHm start-time 2009-06-14.10:00:00
4.
(Optional) Specify loose authentication checking if you are transitioning from nonauthenticated sessions to authenticated sessions.
[edit protocols pim] user@host# set interface ge-0/1/5 family inet bfd-liveness-detection authentication loose-check
5.
(Optional) View your configuration by using the show bfd session detail or show bfd session extensive command.
6.
Repeat these steps to configure the other end of the BFD session.
Viewing Authentication Information for BFD Sessions
You can view the existing BFD authentication configuration by using the show bfd session detail and show bfd session extensive commands.
Copyright © 2016, Juniper Networks, Inc.
19
Multicast Protocols Feature Guide for EX4600 Switches
The following example shows BFD authentication configured for the ge-0/1/5 interface.
It specifies the keyed SHA-1 authentication algorithm and a keychain name of bfd-pim.
The authentication keychain is configured with two keys. Key 1 contains the secret data
“$9$ggaJDmPQ6/tJgF/AtREVsyPsnCtUHm” and a start time of June 1, 2009, at 9:46:02
AM PST. Key 2 contains the secret data “$9$a5jiKW9l.reP38ny.TszF2/9” and a start time of June 1, 2009, at 3:29:20 PM PST.
[edit protocols pim] interface ge-0/1/5 { family inet { bfd-liveness-detection { authentication { key-chain bfd-pim; algorithm keyed-sha-1;
}
}
}
}
[edit security] authentication key-chains { key-chain bfd-pim { key 1 { secret “$9$ggaJDmPQ6/tJgF/AtREVsyPsnCtUHm”; start-time “2009-6-1.09:46:02 -0700”;
} key 2 { secret “$9$a5jiKW9l.reP38ny.TszF2/9”; start-time “2009-6-1.15:29:20 -0700”;
}
}
}
If you commit these updates to your configuration, you see output similar to the following example. In the output for the show bfd session detail command, Authenticate is displayed to indicate that BFD authentication is configured. For more information about the configuration, use the show bfd session extensive command. The output for this command provides the keychain name, the authentication algorithm and mode for each client in the session, and the overall BFD authentication configuration status, keychain name, and authentication algorithm and mode.
show bfd session detail user@host# show bfd session detail
Detect Transmit
Address State Interface Time Interval Multiplier
50.0.0.2 Up ge-0/1/5.0 0.900 0.300 3
Client PIM, TX interval 0.300, RX interval 0.300, Authenticate
Session up time 3d 00:34
Local diagnostic None, remote diagnostic NbrSignal
Remote state Up, version 1
Replicated show bfd session extensive user@host# show bfd session extensive
Detect Transmit
20 Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Using PIM Basics
Address State Interface Time Interval Multiplier
50.0.0.2 Up ge-0/1/5.0 0.900 0.300 3
Client PIM, TX interval 0.300, RX interval 0.300, Authenticate keychain bfd-pim, algo keyed-sha-1, mode strict
Session up time 00:04:42
Local diagnostic None, remote diagnostic NbrSignal
Remote state Up, version 1
Replicated
Min async interval 0.300, min slow interval 1.000
Adaptive async TX interval 0.300, RX interval 0.300
Local min TX interval 0.300, minimum RX interval 0.300, multiplier 3
Remote min TX interval 0.300, min RX interval 0.300, multiplier 3
Local discriminator 2, remote discriminator 2
Echo mode disabled/inactive
Authentication enabled/active, keychain bfd-pim, algo keyed-sha-1, mode strict
Related
Documentation
• Understanding Bidirectional Forwarding Detection Authentication for PIM
•
Configuring BFD for PIM on page 16
• authentication-key-chains
•
bfd-liveness-detection on page 194
• show bfd session
Copyright © 2016, Juniper Networks, Inc.
21
Multicast Protocols Feature Guide for EX4600 Switches
22 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 2
Using PIM Sparse Mode
•
Understanding PIM Sparse Mode on page 23
•
•
Enabling PIM Sparse Mode on page 26
•
Configuring PIM Join Load Balancing on page 27
•
Modifying the Join State Timeout on page 31
•
Example: Enabling Join Suppression on page 31
Understanding PIM Sparse Mode
A Protocol Independent Multicast (PIM) sparse-mode domain uses reverse-path forwarding (RPF) to create a path from a data source to the receiver requesting the data.
When a receiver issues an explicit join request, an RPF check is triggered. A (*,G) PIM join message is sent toward the RP from the receiver's designated router (DR). (By definition, this message is actually called a join/prune message, but for clarity in this description, it is called either join or prune, depending on its context.) The join message is multicast hop by hop upstream to the ALL-PIM-ROUTERS group (224.0.0.13) by means of each router’s RPF interface until it reaches the RP. The RP router receives the (*,G) PIM join message and adds the interface on which it was received to the outgoing interface list
(OIL) of the rendezvous-point tree (RPT) forwarding state entry. This builds the RPT connecting the receiver with the RP. The RPT remains in effect, even if no active sources generate traffic.
NOTE: State—the (*,G) or (S,G) entries—is the information used for forwarding unicast or multicast packets. S is the source IP address, G is the multicast group address, and * represents any source sending to group G.
Routers keep track of the multicast forwarding state for the incoming and outgoing interfaces for each group.
When a source becomes active, the source DR encapsulates multicast data packets into a PIM register message and sends them by means of unicast to the RP router.
If the RP router has interested receivers in the PIM sparse-mode domain, it sends a PIM join message toward the source to build a shortest-path tree (SPT) back to the source.
The source sends multicast packets out on the LAN, and the source DR encapsulates
Copyright © 2016, Juniper Networks, Inc.
23
Multicast Protocols Feature Guide for EX4600 Switches the packets in a PIM register message and forwards the message toward the RP router by means of unicast. The RP router receives PIM register messages back from the source, and thus adds a new source to the distribution tree, keeping track of sources in a PIM table. Once an RP router receives packets natively (with S,G), it sends a register stop message to stop receiving the register messages by means of unicast.
In actual application, many receivers with multiple SPTs are involved in a multicast traffic flow. To illustrate the process, we track the multicast traffic from the RP router to one receiver. In such a case, the RP router begins sending multicast packets down the RPT toward the receiver’s DR for delivery to the interested receivers. When the receiver’s DR receives the first packet from the RPT, the DR sends a PIM join message toward the source DR to start building an SPT back to the source. When the source DR receives the
PIM join message from the receiver’s DR, it starts sending traffic down all SPTs. When the first multicast packet is received by the receiver’s DR, the receiver’s DR sends a PIM prune message to the RP router to stop duplicate packets from being sent through the
RPT. In turn, the RP router stops sending multicast packets to the receiver’s DR, and sends a PIM prune message for this source over the RPT toward the source DR to halt multicast packet delivery to the RP router from that particular source.
If the RP router receives a PIM register message from an active source but has no interested receivers in the PIM sparse-mode domain, it still adds the active source into the PIM table. However, after adding the active source into the PIM table, the RP router sends a register stop message. The RP router discovers the active source’s existence and no longer needs to receive advertisement of the source (which utilizes resources).
NOTE: If the number of PIM join messages exceeds the configured MTU, the messages are fragmented in IPv6 PIM sparse mode. To avoid the fragmentation of PIM join messages, the multicast traffic receives the interface MTU instead of the path MTU.
The major characteristics of PIM sparse mode are as follows:
• Routers with downstream receivers join a PIM sparse-mode tree through an explicit join message.
• PIM sparse-mode RPs are the routers where receivers meet sources.
• Senders announce their existence to one or more RPs, and receivers query RPs to find multicast sessions.
• Once receivers get content from sources through the RP, the last-hop router (the router closest to the receiver) can optionally remove the RP from the shared distribution tree
(*,G) if the new source-based tree (S,G) is shorter. Receivers can then get content directly from the source.
The transitional aspect of PIM sparse mode from shared to source-based tree is one of the major features of PIM, because it prevents overloading the RP or surrounding core links.
24 Copyright © 2016, Juniper Networks, Inc.
Chapter 2: Using PIM Sparse Mode
There are related issues regarding source, RPs, and receivers when sparse mode multicast is used:
• Sources must be able to send to all RPs.
• RPs must all know one another.
• Receivers must send explicit join messages to a known RP.
• Receivers initially need to know only one RP (they later learn about others).
• Receivers can explicitly prune themselves from a tree.
• Receivers that never transition to a source-based tree are effectively running Core
Based Trees (CBT).
PIM sparse mode has standard features for all of these issues.
Rendezvous Point
The RP router serves as the information exchange point for the other routers. All routers in a PIM domain must provide mapping to an RP router. It is the only router that needs to know the active sources for a domain—the other routers just need to know how to reach the RP. In this way, the RP matches receivers with sources.
The RP router is downstream from the source and forms one end of the shortest-path tree. As shown in
Figure 1 on page 25 , the RP router is upstream from the receiver and
thus forms one end of the rendezvous-point tree.
Figure 1: Rendezvous Point As Part of the RPT and SPT
The benefit of using the RP as the information exchange point is that it reduces the amount of state in non-RP routers. No network flooding is required to provide non-RP routers information about active sources.
RP Mapping Options
RPs can be learned by one of the following mechanisms:
• Static configuration
• Anycast RP
• Auto-RP
• Bootstrap router
We recommend a static RP mapping with anycast RP and a bootstrap router (BSR) with auto-RP configuration, because static mapping provides all the benefits of a bootstrap router and auto-RP without the complexity of the full BSR and auto-RP mechanisms.
Copyright © 2016, Juniper Networks, Inc.
25
Multicast Protocols Feature Guide for EX4600 Switches
Related
Documentation
•
Understanding Static RP on page 55
•
Understanding RP Mapping with Anycast RP on page 59
•
Understanding the PIM Bootstrap Router on page 69
• Understanding PIM Auto-RP
Designated Router
In a PIM sparse mode (PIM-SM) domain, there are two types of designated routers to consider:
• The receiver DR sends PIM join and PIM prune messages from the receiver network toward the RP.
• The source DR sends PIM register messages from the source network to the RP.
Neighboring PIM routers multicast periodic PIM hello messages to each other every
30 seconds (the default). The PIM hello message usually includes a holdtime value for the neighbor to use, but this is not a requirement. If the PIM hello message does not include a holdtime value, a default timeout value (in Junos OS, 105 seconds) is used. On receipt of a PIM hello message, a router stores the IP address and priority for that neighbor.
If the DR priorities match, the router with the highest IP address is selected as the DR.
If a DR fails, a new one is selected using the same process of comparing IP addresses.
NOTE: In PIM dense mode (PIM-DM), a DR is elected by the same process that PIM-SM uses. However, the only time that a DR has any effect in PIM-DM is when IGMPv1 is used on the interface. (IGMPv2 is the default.) In this case, the DR also functions as the IGMP Query Router because IGMPv1 does not have a Query Router election mechanism.
Enabling PIM Sparse Mode
In PIM sparse mode (PIM-SM), the assumption is that very few of the possible receivers want packets from a source, so the network establishes and sends packets only on branches that have at least one leaf indicating (by message) a desire for the traffic.
WANs are appropriate networks for sparse-mode operation.
By default, PIM is disabled. When you enable PIM, it operates in sparse mode by default.
You do not need to configure Internet Group Management Protocol (IGMP) version 2 for a sparse mode configuration. After you enable PIM, by default, IGMP version 2 is also enabled.
26 Copyright © 2016, Juniper Networks, Inc.
Chapter 2: Using PIM Sparse Mode
All systems on a subnet must run the same version of PIM.
The default PIM version can be version 1 or version 2, depending on the mode you are configuring. PIMv1 is the default for rendezvous point (RP) mode (at the [edit protocols pim rp static address address] hierarchy level). However, PIMv2 is the default for interface mode (at the [edit protocols pim interface interface-name] hierarchy level). Explicitly configured versions override the defaults. The following example explicitly configures
PIMv2 on the interfaces.
You can configure PIM sparse mode globally or for a routing instance. This example shows how to configure PIM sparse mode globally on all interfaces. It also shows how to configure a static RP router and how to configure the non-RP routers.
To configure the router properties for PIM sparse mode:
1.
Configure the static RP router.
[edit protocols pim] user@host# set
inet address 192.168.3.253
2.
Configure the RP router interfaces. When configuring all interfaces, exclude the fxp0.0
management interface by including the disable statement for that interface.
[edit protocols pim] user@host# set interface all mode sparse user@host# set interface all
2 user@host# set interface fxp0.0 disable
3.
Configure the non-RP routers. Include the following configuration on all of the non-RP routers.
[edit protocols pim] user@host# set
static address 192.168.3.253 version 2 user@host# set interface all mode sparse user@host# set interface all version 2 user@host# set interface fxp0.0 disable
4.
Monitor the operation of PIM sparse mode.
•
•
•
•
Related
Documentation
•
Understanding PIM Sparse Mode on page 23
Configuring PIM Join Load Balancing
By default, PIM join messages are sent toward a source based on the RPF routing table check. If there is more than one equal-cost path toward the source, then one upstream interface is chosen to send the join message. This interface is also used for all downstream
Copyright © 2016, Juniper Networks, Inc.
27
Multicast Protocols Feature Guide for EX4600 Switches traffic, so even though there are alternative interfaces available, the multicast load is concentrated on one upstream interface and routing device.
For PIM sparse mode, you can configure PIM join load balancing to spread join messages and traffic across equal-cost upstream paths (interfaces and routing devices) provided by unicast routing toward a source. PIM join load balancing is only supported for PIM sparse mode configurations.
PIM join load balancing is supported on draft-rosen multicast VPNs (also referred to as dual PIM multicast VPNs). PIM join load balancing is not supported on multiprotocol
BGP-based multicast VPNs (also referred to as next-generation Layer 3 VPN multicast).
When PIM join load balancing is enabled in a draft-rosen Layer 3 VPN scenario, the load balancing is achieved based on the join counts for the far-end PE routing devices, not for any intermediate P routing devices.
If an internal BGP (IBGP) multipath forwarding VPN route is available, the Junos OS uses the multipath forwarding VPN route to send join messages to the remote PE routers to achieve load balancing over the VPN.
By default, when multiple PIM joins are received for different groups, all joins are sent to the same upstream gateway chosen by the unicast routing protocol. Even if there are multiple equal-cost paths available, these alternative paths are not utilized to distribute multicast traffic from the source to the various groups.
When PIM join load balancing is configured, the PIM joins are distributed equally among all equal-cost upstream interfaces and neighbors. Every new join triggers the selection of the least-loaded upstream interface and neighbor. If there are multiple neighbors on the same interface (for example, on a LAN), join load balancing maintains a value for each of the neighbors and distributes multicast joins (and downstream traffic) among these as well.
Join counts for interfaces and neighbors are maintained globally, not on a per-source basis. Therefore, there is no guarantee that joins for a particular source are load-balanced.
However, the joins for all sources and all groups known to the routing device are load-balanced. There is also no way to administratively give preference to one neighbor over another: all equal-cost paths are treated the same way.
You can configure message filtering globally or for a routing instance. This example shows the global configuration.
28 Copyright © 2016, Juniper Networks, Inc.
Chapter 2: Using PIM Sparse Mode
You configure PIM join load balancing on the non-RP routers in the PIM domain.
1.
Determine if there are multiple paths available for a source (for example, an RP) with the output of the show pim join extensive or show pim source commands.
user@host> show pim join extensive
Instance: PIM.master Family: INET
Group: 224.1.1.1
Source: *
RP: 10.255.245.6
Flags: sparse,rptree,wildcard
Upstream interface: t1-0/2/3.0
Upstream neighbor: 192.168.38.57
Upstream state: Join to RP
Downstream neighbors:
Interface: t1–0/2/1.0
192.168.38.16 State: JOIN Flags; SRW Timeout: 164
Group: 224.2.127.254
Source: *
RP: 10.255.245.6
Flags: sparse,rptree,wildcard
Upstream interface: so–0/3/0.0
Upstream neighbor: 192.168.38.47
Upstream state: Join to RP
Downstream neighbors:
Interface: t1–0/2/3.0
192.168.38.16 State: JOIN Flags; SRW Timeout: 164
Note that for this router, the RP at IP address 10.255.245.6 is the source for two multicast groups: 224.1.1.1 and 224.2.127.254. This router has two equal-cost paths through two different upstream interfaces (t1-0/2/3.0 and so-0/3/0.0) with two different neighbors (192.168.38.57 and 192.168.38.47). This router is a good candidate for PIM join load balancing.
2.
On the non-RP router, configure PIM sparse mode and join load balancing.
[edit protocols pim ] user@host# set interface all mode sparse version 2 user@host# set
3.
Then configure the static address of the RP.
[edit protocols pim
user@host# set
address 10.10.10.1
4.
Monitor the operation.
user@host> show pim interfaces
Instance: PIM.master
If load balancing is enabled for this router, the number of PIM joins sent on each interface is shown in the output for the show pim interfaces command.
Name Stat Mode IP V State NbrCnt JoinCnt DR address lo0.0 Up Sparse 4 2 DR 0 0 10.255.168.58
pe-1/2/0.32769 Up Sparse 4 2 P2P 0 0 so-0/3/0.0 Up Sparse 4 2 P2P 1 1 t1-0/2/1.0 Up Sparse 4 2 P2P 1 0 t1-0/2/3.0 Up Sparse 4 2 P2P 1 1 lo0.0 Up Sparse 6 2 DR 0 0 fe80::2a0:a5ff:4b7
Copyright © 2016, Juniper Networks, Inc.
29
Multicast Protocols Feature Guide for EX4600 Switches
Note that the two equal-cost paths shown by the show pim interfaces command now have nonzero join counts. If the counts differ by more than one and were zero (0) when load balancing commenced, an error occurs (joins before load balancing are not redistributed). The join count also appears in the show pim neighbors detail output: user@host> show pim neighbors detail
Interface: so-0/3/0.0
Address: 192.168.38.46, IPv4, PIM v2, Mode: Sparse, Join Count: 0
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 1689116164
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Address: 192.168.38.47, IPv4, PIM v2, Join Count: 1
BFD: Disabled
Hello Option Holdtime: 105 seconds 102 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 792890329
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Interface: t1-0/2/3.0
Address: 192.168.38.56, IPv4, PIM v2, Mode: Sparse, Join Count: 0
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 678582286
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Address: 192.168.38.57, IPv4, PIM v2, Join Count: 1
BFD: Disabled
Hello Option Holdtime: 105 seconds 97 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1854475503
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Note that the join count is nonzero on the two load-balanced interfaces toward the upstream neighbors.
PIM join load balancing only takes effect when the feature is configured. Prior joins are not redistributed to achieve perfect load balancing. In addition, if an interface or neighbor fails, the new joins are redistributed among remaining active interfaces and neighbors. However, when the interface or neighbor is restored, prior joins are not redistributed. The clear pim join-distribution command redistributes the existing flows to new or restored upstream neighbors. Redistributing the existing flows causes traffic to be disrupted, so we recommend that you perform PIM join redistribution during a maintenance window.
Related
Documentation
• clear pim join-distribution
•
show pim interfaces on page 395
•
show pim neighbors on page 419
•
30 Copyright © 2016, Juniper Networks, Inc.
Chapter 2: Using PIM Sparse Mode
Modifying the Join State Timeout
This section describes how to configure the join state timeout.
A downstream router periodically sends join messages to refresh the join state on the upstream router. If the join state is not refreshed before the timeout expires, the join state is removed.
By default, the join state timeout is 210 seconds. You can change this timeout to allow additional time to receive the join messages. Because the messages are called join-prune messages, the name used is the join-prune-timeout statement.
To modify the timeout, include the join-prune-timeout statement: user@host# set protocols pim join-prune-timeout 230
The join timeout value can be from 210 through 420 seconds.
Related
Documentation
•
join-prune-timeout on page 217
Example: Enabling Join Suppression
This example describes how to enable PIM join suppression.
•
•
•
•
Requirements
Before you begin:
• Configure the router interfaces.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing
Protocols Library for Routing Devices.
• Configure PIM Sparse Mode on the interfaces. See
“Enabling PIM Sparse Mode” on page 26 .
Overview
PIM join suppression enables a router on a multiaccess network to defer sending join messages to an upstream router when it sees identical join messages on the same network. Eventually, only one router sends these join messages, and the other routers suppress identical messages. Limiting the number of join messages improves scalability and efficiency by reducing the number of messages sent to the same router.
Copyright © 2016, Juniper Networks, Inc.
31
Multicast Protocols Feature Guide for EX4600 Switches
This example includes the following statements:
• override-interval —Sets the maximum time in milliseconds to delay sending override join messages. When a router sees a prune message for a join it is currently suppressing, it waits before it sends an override join message. Waiting helps avoid multiple downstream routers sending override join messages at the same time. The override interval is a random timer with a value of 0 through the maximum override value.
• propagation-delay —Sets a value in milliseconds for a prune pending timer, which specifies how long to wait before executing a prune on an upstream router. During this period, the router waits for any prune override join messages that might be currently suppressed. The period for the prune pending timer is the sum of the override-interval value and the value specified for propagation-delay.
• reset-tracking-bit —Enables PIM join suppression on each multiaccess downstream interface. This statement resets a tracking bit field (T-bit) on the LAN prune delay hello option from the default of 1 (join suppression disabled) to 0 (join suppression enabled).
When multiple identical join messages are received, a random join suppression timer is activated, with a range of 66 through 84 milliseconds. The timer is reset each time join suppression is triggered.
shows the topology used in this example.
32 Copyright © 2016, Juniper Networks, Inc.
Chapter 2: Using PIM Sparse Mode
Figure 2: Join Suppression
Host 0
R0
R1
Host 5
R3
R5
R4
Host 4
Host 1 Host 3
Host 2
The items in
represent the following functions:
• Host 0 is the multicast source.
• Host 1, Host 2, Host 3, and Host 4 are receivers.
• Router R0 is the first-hop router and the RP.
• Router R1 is an upstream router.
• Routers R2, R3, R4, and R5 are downstream routers in the multicast LAN.
This example shows the configuration of the downstream devices: Routers R2, R3, R4, and R5.
Copyright © 2016, Juniper Networks, Inc.
33
Multicast Protocols Feature Guide for EX4600 Switches
Configuration
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
[edit] set protocols pim traceoptions file pim.log
set protocols pim traceoptions file size 5m set protocols pim traceoptions file world-readable set protocols pim traceoptions flag join detail set protocols pim traceoptions flag prune detail set protocols pim traceoptions flag normal detail set protocols pim traceoptions flag register detail set protocols pim rp static address 10.255.112.160
set protocols pim interface all mode sparse set protocols pim interface all version 2 set protocols pim interface fxp0.0 disable set protocols pim reset-tracking-bit set protocols pim propagation-delay 500 set protocols pim override-interval 4000
Step-by-Step
Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure PIM join suppression on a non-RP downstream router in the multicast LAN:
1.
2.
3.
4.
Configure PIM sparse mode on the interfaces.
[edit] user@host# edit protocols pim
[edit protocols pim] user@host# set rp static address 10.255.112.160
[edit protocols pim] user@host# set interface all mode sparse version 2
[edit protocols pim] user@host# set interface all version 2
[edit protocols pim] user@host# set interface fxp0.0 disable
Enable the join suppression timer.
[edit protocols pim] user@host# set reset-tracking-bit
Configure the prune override interval value.
[edit protocols pim] user@host# set override-interval 4000
Configure the propagation delay of the link.
[edit protocols pim] user@host# set propagation-delay 500
34 Copyright © 2016, Juniper Networks, Inc.
Chapter 2: Using PIM Sparse Mode
Verification
5.
6.
(Optional) Configure PIM tracing operations.
[edit protocols pim] user@host# set traceoptions file pim.log size 5m world-readable
[edit protocols pim] user@host# set traceoptions flag join detail
[edit protocols pim] user@host# set traceoptions flag normal detail
[edit protocols pim] user@host# set traceoptions flag register detail
If you are done configuring the device, commit the configuration.
[edit protocols pim] user@host# commit
Results
From configuration mode, confirm your configuration by entering the show protocols command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
user@host# show protocols pim { traceoptions { file pim.log size 5m world-readable; flag join detail; flag prune detail; flag normal detail; flag register detail;
} rp { static { address 10.255.112.160;
}
} interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
} reset-tracking-bit; propagation-delay 500; override-interval 4000;
}
To verify the configuration, run the following commands on the upstream and downstream routers:
•
extensive
Copyright © 2016, Juniper Networks, Inc.
35
Multicast Protocols Feature Guide for EX4600 Switches
•
extensive
Related
Documentation
•
Example: Configuring the PIM Assert Timeout on page 90
• Example: Configuring PIM RPF Selection
•
Example: Configuring the PIM SPT Threshold Policy on page 92
•
Enabling PIM Sparse Mode on page 26
•
36 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 3
Using Source-Specific Multicast
•
Source-Specific Multicast Groups Overview on page 37
•
Understanding PIM Source-Specific Mode on page 38
•
•
Example: Configuring PIM SSM on a Network on page 41
•
Example: Configuring an SSM-Only Domain on page 43
•
Example: Configuring SSM Mapping on page 43
•
Example: Configuring Source-Specific Multicast Groups with Any-Source
•
Example: Configuring SSM Maps for Different Groups to Different Sources on page 49
Source-Specific Multicast Groups Overview
Source-specific multicast (SSM) is a service model that identifies session traffic by both source and group address. SSM implemented in Junos OS has the efficient explicit join procedures of Protocol Independent Multicast (PIM) sparse mode but eliminates the immediate shared tree and rendezvous point (RP) procedures using (*,G) pairs. The (*) is a wildcard referring to any source sending to group G, and “G” refers to the IP multicast group. SSM builds shortest-path trees (SPTs) directly represented by (S,G) pairs. The
“S” refers to the source's unicast IP address, and the “G” refers to the specific multicast group address. The SSM (S,G) pairs are called channels to differentiate them from any-source multicast (ASM) groups. Although ASM supports both one-to-many and many-to-many communications, ASM's complexity is in its method of source discovery.
For example, if you click a link in a browser, the receiver is notified about the group information, but not the source information. With SSM, the client receives both source and group information.
SSM is ideal for one-to-many multicast services such as network entertainment channels.
However, many-to-many multicast services might require ASM.
To deploy SSM successfully, you need an end-to-end multicast-enabled network and applications that use an Internet Group Management Protocol version 3 (IGMPv3) or
Multicast Listener Discovery version 2 (MLDv2) stack, or you need to configure SSM mapping from IGMPv1 or IGMPv2 to IGMPv3. An IGMPv3 stack provides the capability of a host operating system to use the IGMPv3 protocol. IGMPv3 is available for Windows
XP, Windows Vista, and most UNIX operating systems.
Copyright © 2016, Juniper Networks, Inc.
37
Multicast Protocols Feature Guide for EX4600 Switches
SSM mapping allows operators to support an SSM network without requiring all hosts to support IGMPv3. This support exists in static (S,G) configurations, but SSM mapping also supports dynamic per-source group state information, which changes as hosts join and leave the group using IGMP.
SSM is typically supported with a subset of IGMPv3 and PIM sparse mode known as PIM
SSM. Using SSM, a client can receive multicast traffic directly from the source. PIM SSM uses the PIM sparse-mode functionality to create an SPT between the client and the source, but builds the SPT without the help of an RP.
An SSM-configured network has distinct advantages over a traditionally configured PIM sparse-mode network. There is no need for shared trees or RP mapping (no RP is required), or for RP-to-RP source discovery through the Multicast Source Discovery Protocol (MSDP).
Understanding PIM Source-Specific Mode
RFC 1112, the original multicast RFC, supported both many-to-many and one-to-many models. These came to be known collectively as any-source multicast (ASM) because
ASM allowed one or many sources for a multicast group's traffic. However, an ASM network must be able to determine the locations of all sources for a particular multicast group whenever there are interested listeners, no matter where the sources might be located in the network. In ASM, the key function of source discovery is a required function of the network itself.
Multicast source discovery appears to be an easy process, but in sparse mode it is not.
In dense mode, it is simple enough to flood traffic to every router in the whole network so that every router learns the source address of the content for that multicast group.
However, the flooding presents scalability and network resource use issues and is not a viable option in sparse mode.
PIM sparse mode (like any sparse mode protocol) achieves the required source discovery functionality without flooding at the cost of a considerable amount of complexity. The
RP routers must be added and must know all multicast sources, and complicated shared distribution trees must be built to the RPs.
In an environment where many sources come and go, such as for a videoconferencing service, ASM is appropriate. However, by ignoring the many-to-many model and focusing attention on the one-to-many source-specific multicast (SSM) model, several commercially promising multicast applications, such as television channel distribution over the Internet, might be brought to the Internet much more quickly and efficiently than if full ASM functionality were required of the network.
PIM SSM is simpler than PIM sparse mode because only the one-to-many model is supported. Initial commercial multicast Internet applications are likely to be available to
subscribers (that is, receivers that issue join messages) from only a single source (a special case of SSM covers the need for a backup source). PIM SSM therefore forms a subset of PIM sparse mode. PIM SSM builds shortest-path trees (SPTs) rooted at the source immediately because in SSM, the router closest to the interested receiver host is informed of the unicast IP address of the source for the multicast traffic. That is, PIM SSM bypasses the RP connection stage through shared distribution trees, as in PIM sparse mode, and goes directly to the source-based distribution tree.
38 Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
PIM SSM
PIM SSM introduces new terms for many of the concepts in PIM sparse mode. PIM SSM can technically be used in the entire 224/4 multicast address range, although PIM SSM operation is guaranteed only in the 232/8 range (232.0.0/24 is reserved). The new SSM terms are appropriate for Internet video applications and are summarized in
.
Table 3: ASM and SSM Terminology
Term Any-Source Multicast Source-Specific Multicast
Address identifier
Address designation
G group
S,G channel
Receiver operations
Group address range join, leave
224/4 excluding 232/8 subscribe, unsubscribe
224/4 (guaranteed only for
232/8)
Although PIM SSM describes receiver operations as subscribe and unsubscribe, the same
PIM sparse mode join and leave messages are used by both forms of the protocol. The terminology change distinguishes ASM from SSM even though the receiver messages are identical.
PIM source-specific multicast (SSM) uses a subset of PIM sparse mode and IGMP version 3
(IGMPv3) to allow a client to receive multicast traffic directly from the source. PIM SSM uses the PIM sparse-mode functionality to create an SPT between the receiver and the source, but builds the SPT without the help of an RP.
By default, the SSM group multicast address is limited to the IP address range from
232.0.0.0 through 232.255.255.255. However, you can extend SSM operations into another
Class D range by including the ssm-groups statement at the [edit routing-options multicast] hierarchy level. The default SSM address range from 232.0.0.0 through 232.255.255.255
cannot be used in the ssm-groups statement. This statement is for adding other multicast addresses to the default SSM group addresses. This statement does not override the default SSM group address range.
You can also configure Junos OS to accept any-source multicast (ASM) join messages
(*,G) for group addresses that are within the default or configured range of source-specific multicast (SSM) groups. This allows you to support a mix of any-source and source-specific multicast groups simultaneously.
An SSM-configured network has distinct advantages over a traditionally configured PIM sparse-mode network. There is no need for shared trees or RP mapping (no RP is required), or for RP-to-RP source discovery through MSDP.
Deploying SSM is easy. You need to configure PIM sparse mode on all router interfaces and issue the necessary SSM commands, including specifying IGMPv3 on the receiver's
LAN. If PIM sparse mode is not explicitly configured on both the source and group member
Copyright © 2016, Juniper Networks, Inc.
39
Multicast Protocols Feature Guide for EX4600 Switches interfaces, multicast packets are not forwarded. Source lists, supported in IGMPv3, are used in PIM SSM. As sources become active and start sending multicast packets, interested receivers in the SSM group receive the multicast packets.
In a PIM SSM-configured network, a host subscribes to an SSM channel (by means of
IGMPv3), announcing a desire to join group G and source S (see
The directly connected PIM sparse-mode router, the receiver's DR, sends an (S,G) join message to its RPF neighbor for the source. Notice in
that the RP is not contacted in this process by the receiver, as would be the case in normal PIM sparse-mode operations.
Figure 3: Receiver Announces Desire to Join Group G and Source S
The (S,G) join message initiates the source tree and then builds it out hop by hop until it reaches the source. In
Figure 4 on page 40 , the source tree is built across the network to
Router 3, the last-hop router connected to the source.
Figure 4: Router 3 (Last-Hop Router) Joins the Source Tree
Using the source tree, multicast traffic is delivered to the subscribing host (see
Figure 5: (S,G) State Is Built Between the Source and the Receiver
40
To configure additional SSM groups, include the ssm-groups statement at the [edit routing-options multicast] hierarchy level.
Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
Related
Documentation
•
Source-Specific Multicast Groups Overview on page 37
•
Example: Configuring Source-Specific Multicast Groups with Any-Source Override on page 46
Example: Configuring PIM SSM on a Network
The following example shows how PIM SSM is configured between a receiver and a source in the network illustrated in
Figure 6: Network on Which to Configure PIM SSM
RP router 4
Source 3 2 1 Receiver
This example shows how to configure the IGMP version to IGMPv3 on all receiving host interfaces.
1.
Enable IGMPv3 on all host-facing interfaces, and disable IGMP on the fxp0.0 interface on Router 1.
user@router1# set protocols igmp interface all version 3 user@router1# set protocols igmp interface fxp0.0 disable
NOTE: When you configure IGMPv3 on a router, hosts on interfaces configured with IGMPv2 cannot join the source tree.
2.
After the configuration is committed, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@router1> show configuration protocol igmp
[edit protocols igmp] interface all { version 3;
} interface fxp0.0 { disable;
}
3.
Use the show igmp interface command to verify that IGMP interfaces are configured.
user@router1> show igmp interface
Interface State Querier Timeout Version Groups fe-0/0/0.0 Up 198.58.3.245 213 3 0 fe-0/0/1.0 Up 198.58.3.241 220 3 0 fe-0/0/2.0 Up 198.58.3.237 218 3 0
Configured Parameters:
IGMP Query Interval (1/10 secs): 1250
Copyright © 2016, Juniper Networks, Inc.
41
Multicast Protocols Feature Guide for EX4600 Switches
IGMP Query Response Interval (1/10 secs): 100
IGMP Last Member Query Interval (1/10 secs): 10
IGMP Robustness Count: 2
Derived Parameters:
IGMP Membership Timeout (1/10 secs): 2600
IGMP Other Querier Present Timeout (1/10 secs): 2550
4.
Use the show pim join extensive command to verify the PIM join state on Router 2 and
Router 3 (the upstream routers).
user@router2> show pim join extensive
232.1.1.1 10.4.1.2 sparse
Upstream interface: fe-1/1/3.0
Upstream State: Local Source
Keepalive timeout: 209
Downstream Neighbors:
Interface: so-1/0/2.0
10.10.71.1 State: Join Flags: S Timeout: 209
5.
Use the show pim join extensive command to verify the PIM join state on Router 1 (the router connected to the receiver).
user@router1> show pim join extensive
232.1.1.1 10.4.1.2 sparse
Upstream interface: so-1/0/2.0
Upstream State: Join to Source
Keepalive timeout: 209
Downstream Neighbors:
Interface: fe-0/2/3.0
10.3.1.1 State: Join Flags: S Timeout: Infinity
NOTE: IP version 6 (IPv6) multicast routers use the Multicast Listener
Discovery (MLD) Protocol to manage the membership of hosts and routers in multicast groups and to learn which groups have interested listeners for each attached physical networks. Each routing device maintains a list of host multicast addresses that have listeners for each subnetwork, as well as a timer for each address. However, the routing device does not need to know the address of each listener—just the address of each host. The routing device provides addresses to the multicast routing protocol it uses, which ensures that multicast packets are delivered to all subnetworks where there are interested listeners. In this way, MLD is used as the transport for the Protocol
Independent Multicast (PIM) Protocol. MLD is an integral part of IPv6 and must be enabled on all IPv6 routing devices and hosts that need to receive
IP multicast traffic. The Junos OS supports MLD versions 1 and 2. Version 2 is supported for source-specific multicast (SSM) include and exclude modes.
Related
Documentation
•
•
Example: Configuring SSM Mapping on page 43
42 Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
Example: Configuring an SSM-Only Domain
Deploying an SSM-only domain is much simpler than deploying an ASM domain because it only requires a few configuration steps. Enable PIM sparse mode on all interfaces by adding the mode statement at the [edit protocols pim interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by adding the disable statement for that interface. Then configure IGMPv3 on all host-facing interfaces by adding the version statement at the [edit protocols igmp interface interface-name] hierarchy level.
In the following example, the host-facing interface is fe-0/1/2:
[edit] protocols { pim { interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
} igmp { interface fe-0/1/2 { version 3;
}
}
}
Example: Configuring SSM Mapping
SSM mapping does not require that all hosts support IGMPv3. SSM mapping translates
IGMPv1 or IGMPv2 membership reports to an IGMPv3 report. This enables hosts running
IGMPv1 or IGMPv2 to participate in SSM until the hosts transition to IGMPv3.
SSM mapping applies to all group addresses that match the policy, not just those that conform to SSM addressing conventions (232/8 for IPv4, ff30::/32 through ff3F::/32 for
IPv6).
We recommend separate SSM maps for IPv4 and IPv6 if both address families require
SSM support. If you apply an SSM map containing both IPv4 and IPv6 addresses to an interface in an IPv4 context (using IGMP), only the IPv4 addresses in the list are used. If there are no such addresses, no action is taken. Similarly, if you apply an SSM map containing both IPv4 and IPv6 addresses to an interface in an IPv6 context (using MLD), only the IPv6 addresses in the list are used. If there are no such addresses, no action is taken.
Copyright © 2016, Juniper Networks, Inc.
43
Multicast Protocols Feature Guide for EX4600 Switches
In this example, you create a policy to match the group addresses that you want to translate to IGMPv3. Then you define the SSM map that associates the policy with the source addresses where these group addresses are found. Finally, you apply the SSM map to one or more IGMP (for IPv4) or MLD (for IPv6) interfaces.
1.
Create an SSM policy named ssm-policy-example. The policy terms match the IPv4
SSM group address 232.1.1.1/32 and the IPv6 SSM group address ff35::1/128. All other addresses are rejected.
user@router1# set policy-options policy-statement ssm-policy-example term A from route-filter 232.1.1.1/32 exact user@router1# set policy-options policy-statement ssm-policy-example term A then accept user@router1# set policy-options policy-statement ssm-policy-example term B from route-filter ff35::1/128 exact user@router1# set policy-options policy-statement ssm-policy-example term B then accept
2.
After the configuration is committed, use the show configuration policy-options command to verify the policy configuration.
user@host> show configuration policy-options
[edit policy-options] policy-statement ssm-policy-example { term A { from { route-filter 232.1.1.1/32 exact;
} then accept;
} term B { from { route-filter ff35::1/128 exact;
} then accept;
} then reject;
}
The group addresses must match the configured policy for SSM mapping to occur.
3.
Define two SSM maps, one called ssm-map-ipv6-example and one called ssm-map-ipv4-example , by applying the policy and configuring the source addresses as a multicast routing option.
user@host# set routing-options multicast ssm-map ssm-map-ipv6-example policy ssm-policy-example user@host# set routing-options multicast ssm-map ssm-map-ipv6-example source fec0::1 fec0::12 user@host# set routing-options multicast ssm-map ssm-map-ipv4-example policy ssm-policy-example user@host# set routing-options multicast ssm-map ssm-map-ipv4-example source
10.10.10.4
user@host# set routing-options multicast ssm-map ssm-map-ipv4-example source
192.168.43.66
44 Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
4.
After the configuration is committed, use the show configuration routing-options command to verify the policy configuration.
user@host> show configuration routing-options
[edit routing-options] multicast { ssm-map ssm-map-ipv6-example { policy ssm-policy-example; source [ fec0::1 fec0::12 ];
} ssm-map ssm-map-ipv4-example { policy ssm-policy-example; source [ 10.10.10.4 192.168.43.66 ];
}
}
We recommend separate SSM maps for IPv4 and IPv6.
5.
Apply SSM maps for IPv4-to-IGMP interfaces and SSM maps for IPv6-to-MLD interfaces: user@host# set protocols igmp interface fe-0/1/0.0 ssm-map ssm-map-ipv4-example user@host# set protocols mld interface fe-0/1/1.0 ssm-map ssm-map-ipv6-example
6.
After the configuration is committed, use the show configuration protocol command to verify the IGMP and MLD protocol configuration.
user@router1> show configuration protocol
[edit protocols] igmp { interface fe-0/1/0.0 { ssm-map ssm-map-ipv4-example;
}
} mld { interface fe-/0/1/1.0 { ssm-map ssm-map-ipv6-example;
}
}
7.
Use the show igmp interface and the show mld interface commands to verify that the
SSM maps are applied to the interfaces.
user@host> show igmp interface fe-0/1/0.0
Interface: fe-0/1/0.0
Querier: 192.168.224.28
State: Up Timeout: None Version: 2 Groups: 2
SSM Map: ssm-map-ipv4-example user@host> show mld interface fe-0/1/1.0
Interface: fe-0/1/1.0
Querier: fec0:0:0:0:1::12
State: Up Timeout: None Version: 2 Groups: 2
SSM Map: ssm-map-ipv6-example
Copyright © 2016, Juniper Networks, Inc.
45
Multicast Protocols Feature Guide for EX4600 Switches
Example: Configuring Source-Specific Multicast Groups with Any-Source Override
This example shows how to extend source-specific multicast (SSM) group operations beyond the default IP address range of 232.0.0.0 through 232.255.255.255. This example also shows how to accept any-source multicast (ASM) join messages (*,G) for group addresses that are within the default or configured range of SSM groups. This allows you to support a mix of any-source and source-specific multicast groups simultaneously.
•
•
•
•
Requirements
Before you begin, configure the router interfaces.
Overview
To deploy SSM, configure PIM sparse mode on all routing device interfaces and issue the necessary SSM commands, including specifying IGMPv3 or MLDv2 on the receiver's LAN.
If PIM sparse mode is not explicitly configured on both the source and group members interfaces, multicast packets are not forwarded. Source lists, supported in IGMPv3 and
MLDv2, are used in PIM SSM. Only sources that are specified send traffic to the SSM group.
In a PIM SSM-configured network, a host subscribes to an SSM channel (by means of
IGMPv3 or MLDv2) to join group G and source S (see
). The directly connected PIM sparse-mode router, the receiver's designated router (DR), sends an (S,G) join message to its reverse-path forwarding (RPF) neighbor for the source. Notice in
that the RP is not contacted in this process by the receiver, as would be the case in normal PIM sparse-mode operations.
Figure 7: Receiver Sends Messages to Join Group G and Source S
46
The (S,G) join message initiates the source tree and then builds it out hop by hop until it reaches the source. In
Figure 8 on page 47 , the source tree is built across the network to
Router 3, the last-hop router connected to the source.
Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
Figure 8: Router 3 (Last-Hop Router) Joins the Source Tree
Using the source tree, multicast traffic is delivered to the subscribing host (see
Figure 9: (S,G) State Is Built Between the Source and the Receiver
SSM can operate in include mode or in exclude mode. In exclude mode the receiver specifies a list of sources that it does not want to receive the multicast group traffic from.
The routing device forwards traffic to the receiver from any source except the sources specified in the exclusion list. The receiver accepts traffic from any sources except the sources specified in the exclusion list.
This example works with the simple RPF topology shown in
.
Figure 10: Simple RPF Topology
Host 1 Router A
RP
Receiver
Configuration
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
set protocols ospf area 0.0.0.0 interface fxp0.0 disable set protocols ospf area 0.0.0.0 interface all set protocols pim rp local address 10.255.72.46
set protocols pim rp local group-ranges 239.0.0.0/24 set protocols pim interface fe-1/0/0.0 mode sparse set protocols pim interface lo0.0 mode sparse set routing-options multicast ssm-groups 232.0.0.0/8
Copyright © 2016, Juniper Networks, Inc.
47
Multicast Protocols Feature Guide for EX4600 Switches
48 set routing-options multicast ssm-groups 239.0.0.0/8 set routing-options multicast asm-override-ssm
Step-by-Step
Procedure
The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure an RPF policy:
1.
2.
3.
4.
5.
Configure OSPF.
[edit protocols ospf] user@host# set area 0.0.0.0 interface fxp0.0 disable user@host# set area 0.0.0.0 interface all
Configure PIM sparse mode.
[edit protocols pim] user@host# set rp local address 10.255.72.46
user@host# set rp local group-ranges 239.0.0.0/24 user@host# set interface fe-1/0/0.0 mode sparse user@host# set interface lo0.0 mode sparse
Configure additional SSM groups.
[edit routing-options] user@host# set
[ 232.0.0.0/8 239.0.0.0/8 ]
Configure the RP to accept ASM join messages for groups within the SSM address range.
[edit routing-options] user@host# set multicast
If you are done configuring the device, commit the configuration.
user@host# commit
Results
Confirm your configuration by entering the show protocols and show routing-options commands.
user@host# show protocols ospf { area 0.0.0.0 { interface fxp0.0 { disable;
} interface all;
}
} pim { rp { local { address 10.255.72.46; group-ranges {
Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
}
239.0.0.0/24;
}
}
} interface fe-1/0/0.0 { mode sparse;
} interface lo0.0 { mode sparse;
} user@host# show routing-options multicast { ssm-groups [ 232.0.0.0/8 239.0.0.0/8 ]; asm-override-ssm;
}
Verification
To verify the configuration, run the following commands:
•
•
•
Related
Documentation
•
Source-Specific Multicast Groups Overview on page 37
Example: Configuring SSM Maps for Different Groups to Different Sources
•
Multiple SSM Maps and Groups for Interfaces on page 49
•
Example: Configuring Multiple SSM Maps Per Interface on page 49
Multiple SSM Maps and Groups for Interfaces
You can configure multiple source-specific multicast (SSM) maps so that different groups map to different sources, which enables a single multicast group to map to different sources for different interfaces.
Example: Configuring Multiple SSM Maps Per Interface
This example shows how to assign more than one SSM map to an IGMP interface.
•
•
•
•
Copyright © 2016, Juniper Networks, Inc.
49
Multicast Protocols Feature Guide for EX4600 Switches
Requirements
This example requires Junos OS Release 11.4 or later.
Overview
In this example, you configure a routing policy, POLICY-ipv4-example1, that maps multicast group join messages over an IGMP logical interface to IPv4 multicast source addresses based on destination IP address as follows:
Routing Policy Name
Multicast Group Join Messages for a Route Filter at This
Destination Address
Multicast Source
Addresses
POLICY-ipv4-example1 term
1
232.1.1.1
10.10.10.4,
192.168.43.66
POLICY-ipv4-example1 term
2
232.1.1.2
10.10.10.5,
192.168.43.67
You apply routing policy POLICY-ipv4-example1 to IGMP logical interface fe-0/1/0.0.
Configuration
The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see the CLI User Guide.
CLI Quick
Configuration
To configure this example, perform the following task:
To quickly configure this example, copy the following configuration commands into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
set policy-options policy-statement POLICY-ipv4-example1 term 1 from route-filter
232.1.1.1/32 exact set policy-options policy-statement POLICY-ipv4-example1 term 1 then ssm-source
10.10.10.4
set policy-options policy-statement POLICY-ipv4-example1 term 1 then ssm-source
192.168.43.66
set policy-options policy-statement POLICY-ipv4-example1 term 1 then accept set policy-options policy-statement POLICY-ipv4-example1 term 2 from route-filter
232.1.1.2/32 exact set policy-options policy-statement POLICY-ipv4-example1 term 2 then ssm-source
10.10.10.5
set policy-options policy-statement POLICY-ipv4-example1 term 2 then ssm-source
192.168.43.67
set policy-options policy-statement POLICY-ipv4-example1 term 2 then accept set protocols igmp interface fe-0/1/0.0 ssm-map-policy POLICY-ipv4-example1
50 Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
Step-by-Step
Procedure
To configure multiple SSM maps per interface:
1.
Configure protocol-independent routing options for route filter 232.1.1.1, and specify the multicast source addresses to which matching multicast groups are to be mapped.
2.
3.
[edit policy-options policy-statement POLICY-ipv4-example1 term 1] user@host# set from route-filter 232.1.1.1/32 exact user@host# set then ssm-source 10.10.10.4
user@host# set then ssm-source 192.168.43.66
user@host# set then accept
Configure protocol-independent routing options for route filter 232.1.1.2, and specify the multicast source addresses to which matching multicast groups are to be mapped.
[edit policy-options policy-statement POLICY-ipv4-example1 term 2] user@host# set from route-filter 232.1.1.2/32 exact user@host# set then ssm-source 10.10.10.5
user@host# set then ssm-source 192.168.43.67
user@host# set then accept
Apply the policy map POLICY-ipv4-example1 to IGMP logical interface fe-0/1/1/0.
[edit protocols
fe-0/1/0.0] user@host# set
POLICY-ipv4-example1
Results After the configuration is committed, confirm the configuration by entering the show policy-options and show protocols configuration mode commands. If the command output does not display the intended configuration, repeat the instructions in this procedure to correct the configuration.
user@host# show policy-options policy-statement POLICY-ipv4-example1 { term 1 { from { route-filter 232.1.1.1/32 exact;
} then { ssm-source [ 10.10.10.4 192.168.43.66 ]; accept;
}
} term 2{ from { route-filter 232.1.1.2/32 exact;
} then { ssm-source [ 10.10.10.5 192.168.43.67 ]; accept;
}
}
} user@host# show protocols igmp { interface fe-0/1/0.0 {
Copyright © 2016, Juniper Networks, Inc.
51
Multicast Protocols Feature Guide for EX4600 Switches
52
}
} ssm-map-policy POLICY-ipv4-example1;
Verification
Confirm that the configuration is working properly.
•
Displaying Information About IGMP-Enabled Interfaces on page 52
•
Displaying the PIM Groups on page 52
•
Displaying the Entries in the IP Multicast Forwarding Table on page 52
Displaying Information About IGMP-Enabled Interfaces
Purpose Verify that the SSM map policy POLICY-ipv4-example1 is applied to logical interface fe-0/1/0.0.
Action Use the
operational mode command for the IGMP logical interface to which you applied the SSM map policy.
user@host> show igmp interface
Interface: fe-0/1/0.0
Querier: 10.111.30.1
State: Up Timeout: None Version: 2 Groups: 2
SSM Map Policy: POLICY-ipv4-example1;
Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Derived Parameters:
IGMP Membership Timeout: 260.0
IGMP Other Querier Present Timeout: 255.0
The command output displays the name of the IGMP logical interface (fe-0/1/0.0), which is the address of the routing device that has been elected to send membership queries and group information.
Displaying the PIM Groups
Purpose Verify the Protocol Independent Multicast (PIM) source and group pair (S,G) entries.
Action Use the
extensive 232.1.1.1
operational mode command to display the PIM source and group pair (S,G) entries for the 232.1.1.1 group.
Displaying the Entries in the IP Multicast Forwarding Table
Purpose Verify that the IP multicast forwarding table displays the multicast route state.
Action Use the
extensive operational mode command to display the entries in the IP multicast forwarding table to verify that the Route state is active and that the
Forwarding state is forwarding.
Copyright © 2016, Juniper Networks, Inc.
Chapter 3: Using Source-Specific Multicast
Related
Documentation
• Example: Configuring Source-Specific Multicast
• Example: Configuring Source-Specific Draft-Rosen 7 Multicast VPNs
Copyright © 2016, Juniper Networks, Inc.
53
Multicast Protocols Feature Guide for EX4600 Switches
54 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 4
Using Static RP
•
Understanding Static RP on page 55
•
Configuring Local PIM RPs on page 55
•
Configuring the Static PIM RP Address on the Non-RP Routing Device on page 57
Understanding Static RP
You can configure a static rendezvous point (RP) configuration that is similar to static routes. A static configuration has the benefit of operating in PIM version 1 or version 2.
When you configure the static RP, the RP address that you select for a particular group must be consistent across all routers in a multicast domain.
A static configuration is simple and convenient. However, if the statically defined RP router becomes unreachable, there is no automatic failover to another RP router. To remedy this problem, you can use anycast RP.
Related
Documentation
•
Configuring Local PIM RPs on page 55
•
Configuring the Static PIM RP Address on the Non-RP Routing Device on page 57
Configuring Local PIM RPs
Local RP configuration makes the routing device a statically defined RP. Consider statically defining an RP if the network does not have many different RPs defined or if the RP assignment does not change very often. The Junos IPv6 PIM implementation supports only static RP configuration. Automatic RP announcement and bootstrap routers are not available with IPv6.
You can configure a local RP globally or for a routing instance. This example shows how to configure a local RP in a routing instance for IPv4 or IPv6.
To configure the routing device’s RP properties:
1.
Configure the routing instance as the local RP.
[routing-instances VPN-A protocols pim] user@host# set
2.
Configure the IP protocol family and IP address.
Copyright © 2016, Juniper Networks, Inc.
55
Multicast Protocols Feature Guide for EX4600 Switches
56
IPv6 PIM hello messages are sent to every interface on which you configure family inet6 , whether at the PIM level of the hierarchy or not. As a result, if you configure an interface with both family inet at the [edit interface interface-name] hierarchy level and family inet6 at the [edit protocols pim interface interface-name] hierarchy level,
PIM sends both IPv4 and IPv6 hellos to that interface.
By default, PIM operates in sparse mode on an interface. If you explicitly configure sparse mode, PIM uses this setting for all IPv6 multicast groups. However, if you configure sparse-dense mode, PIM does not accept IPv6 multicast groups as dense groups and operates in sparse mode over them.
[edit routing-instances VPN-A protocols pim
] user@host# set family inet6
2001:db8:85a3::8a2e:370:7334 user@host# set family inet
10.1.2.254
3.
(IPv4 only) Configure the routing device’s RP priority.
NOTE: The priority statement is not supported for IPv6, but is included here for informational purposes. The routing device’s priority value for becoming the RP is included in the bootstrap messages that the routing device sends. Use a smaller number to increase the likelihood that the routing device becomes the RP for local multicast groups. Each PIM routing device uses the priority value and other factors to determine the candidate
RPs for a particular group range. After the set of candidate RPs is distributed, each routing device determines algorithmically the RP from the candidate RP set using a hash function. By default, the priority value is set to 1. If this value is set to 0, the bootstrap router can override the group range being advertised by the candidate RP.
[edit routing-instances VPN-A protocols pim
] user@host# set
5
4.
Configure the groups for which the routing device is the RP.
By default, a routing device running PIM is eligible to be the RP for all IPv4 or IPv6 groups (224.0.0.0/4 or FF70::/12 to FFF0::/12). The following example limits the groups for which this routing device can be the RP.
[edit routing-instances VPN-A protocols pim
] user@host# set
fec0::/10 user@host# set
10.1.2.0/24
5.
(IPv4 only) Modify the local RP hold time.
If the local routing device is configured as an RP, it is considered a candidate RP for its local multicast groups. For candidate RPs, the hold time is used by the bootstrap router to time out RPs, and applies to the bootstrap RP-set mechanism. The RP hold time is part of the candidate RP advertisement message sent by the local routing device to the bootstrap router. If the bootstrap router does not receive a candidate
RP advertisement from an RP within the hold time, it removes that routing device from its list of candidate RPs. The default hold time is 150 seconds.
[edit routing-instances VPN-A protocols pim
] user@host# set
200
Copyright © 2016, Juniper Networks, Inc.
Chapter 4: Using Static RP
6.
(Optional) Override dynamic RP for the specified group address range.
If you configure both static RP mapping and dynamic RP mapping (such as auto-RP) in a single routing instance, allow the static mapping to take precedence for the given static RP group range, and allow dynamic RP mapping for all other groups.
If you exclude this statement from the configuration and you use both static and dynamic RP mechanisms for different group ranges within the same routing instance, the dynamic RP mapping takes precedence over the static RP mapping, even if static
RP is defined for a specific group range.
[edit routing-instances VPN-A protocols pim
] user@host# set override
7.
Monitor the operation of PIM by running the show pim commands. Run show pim ? to display the supported commands.
Related
Documentation
•
•
Configuring the Static PIM RP Address on the Non-RP Routing Device
Consider statically defining an RP if the network does not have many different RPs defined or if the RP assignment does not change very often. The Junos IPv6 PIM implementation supports only static RP configuration. Automatic RP announcement and bootstrap routers are not available with IPv6.
You configure a static RP address on the non-RP routing device. This enables the non-RP routing device to recognize the local statically defined RP. For example, if R0 is a non-RP router and R1 is the local RP router, you configure R0 with the static RP address of R1.
The static IP address is the routable address assigned to the loopback interface on R1.
In the following example, the loopback address of the RP is
2001:db8:85a3::8a2e:370:7334.
You can configure a static RP address globally or for a routing instance. This example shows how to configure a static RP address in a routing instance for IPv6.
To configure the static RP address:
1.
On a non-RP routing device, configure the routing instance to point to the routable address assigned to the loopback interface of the RP.
[routing-instances VPN-A protocols pim
user@host# set
2001:db8:85a3::8a2e:370:7334
NOTE: Logical systems are also supported. You can configure a static RP address in a logical system only if the logical system is not directly connected to a source.
2.
(Optional) Set the PIM sparse mode version.
Copyright © 2016, Juniper Networks, Inc.
57
Multicast Protocols Feature Guide for EX4600 Switches
For each static RP address, you can optionally specify the PIM version. The default
PIM version is version 1.
[edit routing-instances VPN-A protocols pim
] user@host# set
2001:db8:85a3::8a2e:370:7334
2
NOTE: The default PIM version can be version 1 or version 2, depending on the mode you are configuring. PIM version 1 is the default for RP mode
([edit pim rp static address address]). PIM version 2 is the default for interface mode ([edit pim interface interface-name]). Explicitly configured versions override the defaults.
3.
(Optional) Set the group address range.
By default, a routing device running PIM is eligible to be the RP for all IPv4 or IPv6 groups (224.0.0.0/4 or FF70::/12 to FFF0::/12). The following example limits the groups for which the 2001:db8:85a3::8a2e:370:7334 address can be the RP.
[edit routing-instances VPN-A protocols pim
] user@host# set
2001:db8:85a3::8a2e:370:7334
fec0::/10
The RP that you select for a particular group must be consistent across all routers in a multicast domain.
4.
(Optional) Override dynamic RP for the specified group address range.
If you configure both static RP mapping and dynamic RP mapping (such as auto-RP) in a single routing instance, allow the static mapping to take precedence for the given static RP group range, and allow dynamic RP mapping for all other groups.
If you exclude this statement from the configuration and you use both static and dynamic RP mechanisms for different group ranges within the same routing instance, the dynamic RP mapping takes precedence over the static RP mapping, even if static
RP is defined for a specific group range.
[edit routing-instances VPN-A protocols pim
address
2001:db8:85a3::8a2e:370:7334] user@host# set override
5.
Monitor the operation of PIM by running the show pim commands. Run show pim ? to display the supported commands.
Related
Documentation
•
•
58 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 5
Using Anycast RP
•
Understanding RP Mapping with Anycast RP on page 59
•
Example: Configuring PIM Anycast With or Without MSDP on page 60
•
Configuring a PIM Anycast RP Router with MSDP on page 63
•
Configuring a PIM Anycast RP Router Using Only PIM on page 64
•
Configuring All PIM Anycast Non-RP Routers on page 65
•
Example: Configuring Multiple RPs in a Domain with Anycast RP on page 66
Understanding RP Mapping with Anycast RP
Having a single active rendezvous point (RP) per multicast group is much the same as having a single server providing any service. All traffic converges on this single point, although other servers are sitting idle, and convergence is slow when the resource fails.
In multicast specifically, there might be closer RPs on the shared tree, so the use of a single RP is suboptimal.
For the purposes of load balancing and redundancy, you can configure anycast RP. You can use anycast RP within a domain to provide redundancy and RP load sharing. When an RP fails, sources and receivers are taken to a new RP by means of unicast routing.
When you configure anycast RP, you bypass the restriction of having one active RP per multicast group, and instead deploy multiple RPs for the same group range. The RP routers share one unicast IP address. Sources from one RP are known to other RPs that use the Multicast Source Discovery Protocol (MSDP). Sources and receivers use the closest RP, as determined by the interior gateway protocol (IGP).
Anycast means that multiple RP routers share the same unicast IP address. Anycast addresses are advertised by the routing protocols. Packets sent to the anycast address are sent to the nearest RP with this address. Anycast addressing is a generic concept and is used in PIM sparse mode to add load balancing and service reliability to RPs.
Anycast RP is defined in Internet draft draft-ietf-mboned-anycast-rp-08.txt, Anycast RP
Mechanism Using PIM and MSDP. To access Internet RFCs and drafts, go to the IETF website at http://www.ietf.org
.
Related
Documentation
•
Configuring the Static PIM RP Address on the Non-RP Routing Device on page 57
•
Example: Configuring Multiple RPs in a Domain with Anycast RP on page 66
Copyright © 2016, Juniper Networks, Inc.
59
Multicast Protocols Feature Guide for EX4600 Switches
•
Example: Configuring PIM Anycast With or Without MSDP on page 60
Example: Configuring PIM Anycast With or Without MSDP
When you configure anycast RP, you bypass the restriction of having one active rendezvous point (RP) per multicast group, and instead deploy multiple RPs for the same group range. The RP routers share one unicast IP address. Sources from one RP are known to other RPs that use the Multicast Source Discovery Protocol (MSDP). Sources and receivers use the closest RP, as determined by the interior gateway protocol (IGP).
You can use anycast RP within a domain to provide redundancy and RP load sharing.
When an RP stops operating, sources and receivers are taken to a new RP by means of unicast routing.
You can configure anycast RP to use PIM and MSDP for IPv4, or PIM alone for both IPv4 and IPv6 scenarios. Both are discussed in this section.
We recommend a static RP mapping with anycast RP over a bootstrap router and auto-RP configuration because it provides all the benefits of a bootstrap router and auto-RP without the complexity of the BSR and auto-RP mechanisms.
All systems on a subnet must run the same version of PIM.
The default PIM version can be version 1 or version 2, depending on the mode you are configuring. PIMv1 is the default RP mode (at the [edit protocols pim rp static address
address] hierarchy level). However, PIMv2 is the default for interface mode (at the [edit protocols pim interface interface-name] hierarchy level). Explicitly configured versions override the defaults. This example explicitly configures PIMv2 on the interfaces.
The following example shows an anycast RP configuration for the RP routers, first with
MSDP and then using PIM alone, and for non-RP routers.
1.
For a network using an RP with MSDP, configure the RP using the lo0 loopback interface, which is always up. Include the address statement and specify the unique and routable router ID and the RP address at the [edit interfaces lo0 unit 0 family inet] hierarchy level. In this example, the router ID is 198.58.3.254 and the shared RP address is 198.58.3.253. Include the primary statement for the first address. Including the primary statement selects the router’s primary address from all the preferred addresses on all interfaces.
interfaces { lo0 { description "PIM RP"; unit 0 { family inet { address 198.58.3.254/32; primary; address 198.58.3.253/32;
}
}
}
}
60 Copyright © 2016, Juniper Networks, Inc.
Chapter 5: Using Anycast RP
2.
Specify the RP address. Include the address statement at the [edit protocols pim rp local] hierarchy level (the same address as the secondary lo0 interface).
For all interfaces, include the mode statement to set the mode to sparse and the version statement to specify PIM version 2 at the [edit protocols pim rp local interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by including the disable statement for that interface.
protocols { pim { rp { local { family inet; address 198.58.3.253;
} interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
}
3.
Configure MSDP peering. Include the peer statement to configure the address of the
MSDP peer at the [edit protocols msdp] hierarchy level. For MSDP peering, use the unique, primary addresses instead of the anycast address. To specify the local address for MSDP peering, include the local-address statement at the [edit protocols msdp peer] hierarchy level.
protocols { msdp { peer 198.58.3.250 { local-address address 198.58.3.254;
}
}
}
NOTE: If you need to configure a PIM RP for both IPv4 and IPv6 scenarios, perform Step
and Step
4.
Configure an RP using the lo0 loopback interface, which is always up. Include the address statement to specify the unique and routable router address and the RP address at the [edit interfaces lo0 unit 0 family inet] hierarchy level. In this example, the router ID is 198.58.3.254 and the shared RP address is 198.58.3.253. Include the primary statement on the first address. Including the primary statement selects the router’s primary address from all the preferred addresses on all interfaces.
interfaces { lo0 { description "PIM RP"; unit 0 {
Copyright © 2016, Juniper Networks, Inc.
61
Multicast Protocols Feature Guide for EX4600 Switches
}
}
} family inet { address 198.58.3.254/32 { primary;
} address 198.58.3.253/32;
}
5.
Include the address statement at the [edit protocols pim rp local] hierarchy level to specify the RP address (the same address as the secondary lo0 interface).
For all interfaces, include the mode statement to set the mode to sparse, and the version statement to specify PIM version 2 at the [edit protocols pim rp local interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by Including the disable statement for that interface.
Include the anycast-pim statement to configure anycast RP without MSDP (for example, if IPv6 is used for multicasting). The other RP routers that share the same
IP address are configured using the rp-set statement. There is one entry for each RP, and the maximum that can be configured is 15. For each RP, specify the routable IP address of the router and whether MSDP source active (SA) messages are forwarded to the RP.
MSDP configuration is not necessary for this type of IPv4 anycast RP configuration.
protocols { pim { rp { local { family inet { address 198.58.3.253; anycast-pim { rp-set { address 198.58.3.240; address 198.58.3.241 forward-msdp-sa;
} local-address 198.58.3.254; #If not configured, use lo0 primary
}
}
}
} interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
6.
Configure the non-RP routers. The anycast RP configuration for a non-RP router is the same whether MSDP is used or not. Specify a static RP by adding the address at
62 Copyright © 2016, Juniper Networks, Inc.
Chapter 5: Using Anycast RP the [edit protocols pim rp static] hierarchy level. Include the version statement at the
[edit protocols pim rp static address] hierarchy level to specify PIM version 2.
protocols { pim { rp { static { address 198.58.3.253 { version 2;
}
}
}
}
}
7.
Include the mode statement at the [edit protocols pim interface all] hierarchy level to specify sparse mode on all interfaces. Then include the version statement at the [edit protocols pim rp interface all mode] to configure all interfaces for PIM version 2. When configuring all interfaces, exclude the fxp0.0 management interface by including the disable statement for that interface.
protocols { pim { interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
Configuring a PIM Anycast RP Router with MSDP
Add the address statement at the [edit protocols pim rp local] hierarchy level to specify the RP address (the same address as the secondary lo0 interface).
For all interfaces, use the mode statement to set the mode to sparse and the version statement to specify PIM version 2 at the [edit protocols pim rp local interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by adding the disable statement for that interface.
protocols { pim { rp { local { family inet; address 198.58.3.253;
} interface all { mode sparse; version 2;
}
Copyright © 2016, Juniper Networks, Inc.
63
Multicast Protocols Feature Guide for EX4600 Switches
}
}
} interface fxp0.0 { disable;
}
To configure MSDP peering, add the peer statement to configure the address of the MSDP peer at the [edit protocols msdp] hierarchy level. For MSDP peering, use the unique, primary addresses instead of the anycast address. To specify the local address for MSDP peering, add the local-address statement at the [edit protocols msdp peer] hierarchy level.
protocols { msdp { peer 198.58.3.250 { local-address 198.58.3.254;
}
}
}
Configuring a PIM Anycast RP Router Using Only PIM
In this example, configure an RP using the lo0 loopback interface, which is always up.
Use the address statement to specify the unique and routable router address and the
RP address at the [edit interfaces lo0 unit 0 family inet] hierarchy level. In this case, the router ID is 198.58.3.254/32 and the shared RP address is 198.58.3.253/32. Add the flag statement primary to the first address. Using this flag selects the router's primary address from all the preferred addresses on all interfaces.
interfaces { lo0 { description "PIM RP"; unit 0 { family inet { address 198.58.3.254/32 { primary;
} address 198.58.3.253/32;
}
}
}
}
Add the address statement at the [edit protocols pim rp local] hierarchy level to specify the RP address (the same address as the secondary lo0 interface).
For all interfaces, use the mode statement to set the mode to sparse, and include the version statement to specify PIM version 2 at the [edit protocols pim rp local interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by adding the disable statement for that interface.
Use the anycast-pim statement to configure anycast RP without MSDP (for example, if
IPv6 is used for multicasting). The other RP routers that share the same IP address are
64 Copyright © 2016, Juniper Networks, Inc.
Chapter 5: Using Anycast RP configured using the rp-set statement. There is one entry for each RP, and the maximum that can be configured is 15. For each RP, specify the routable IP address of the router and whether MSDP source active (SA) messages are forwarded to the RP.
protocols { pim { rp { local { family inet { address 198.58.3.253; anycast-pim { rp-set { address 198.58.3.240; address 198.58.3.241 forward-msdp-sa;
} local-address 198.58.3.254; #If not configured, use lo0 primary
}
}
}
} interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
MSDP configuration is not necessary for this type of IPv4 anycast RP configuration.
Configuring All PIM Anycast Non-RP Routers
Use the mode statement at the [edit protocols pim rp interface all] hierarchy level to specify sparse mode on all interfaces. Then add the version statement at the [edit protocols pim rp interface all mode] to configure all interfaces for PIM version 2. When configuring all interfaces, exclude the fxp0.0 management interface by adding the disable statement for that interface.
protocols { pim { interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
Copyright © 2016, Juniper Networks, Inc.
65
Multicast Protocols Feature Guide for EX4600 Switches
Example: Configuring Multiple RPs in a Domain with Anycast RP
This example shows how to configure anycast RP on each RP router in the PIM-SM domain. With this configuration you can deploy more than one RP for a single group range. This enables load balancing and redundancy.
•
•
•
•
Requirements
Before you begin:
• Configure the router interfaces.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing
Protocols Library for Routing Devices.
• Configure PIM Sparse Mode on the interfaces. See
“Enabling PIM Sparse Mode” on page 26 .
Overview
When you configure anycast RP, the RP routers in the PIM-SM domain use a shared address. In this example, the shared address is 10.1.1.2/32. Anycast RP uses Multicast
Source Discovery Protocol (MSDP) to discover and maintain a consistent view of the active sources. Anycast RP also requires an RP selection method, such as static, auto-RP, or bootstrap RP. This example uses static RP and shows only one RP router configuration.
Configuration
CLI Quick
Configuration
RP Routers
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
set interfaces lo0 unit 0 family inet address 192.168.132.1/32 primary set interfaces lo0 unit 0 family inet address 10.1.1.2/32 set protocols msdp local-address 192.168.132.1
set protocols msdp peer 192.168.12.1
set protocols pim rp local address 10.1.1.2
set routing-options router-id 192.168.132.1
Non-RP Routers set protocols pim rp static address 10.1.1.2
66 Copyright © 2016, Juniper Networks, Inc.
Chapter 5: Using Anycast RP
Step-by-Step
Procedure
The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure anycast RP:
1.
2.
On each RP router in the domain, configure the shared anycast address on the router’s loopback address.
[edit interfaces] user@host# set lo0 unit 0 family inet address 10.1.1.2/32
On each RP router in the domain, make sure that the router’s regular loopback address is the primary address for the interface, and set the router ID.
[edit interfaces] user@host# set lo0 unit 0 family inet address 192.168.132.1/32 primary
3.
4.
5.
6.
[edit routing-options] user@host# set router-id 192.168.132.1
On each RP router in the domain, configure the local RP address, using the shared address.
[edit protocols pim] user@host# set rp local address 10.1.1.2
On each RP router in the domain, create MSDP sessions to the other RPs in the domain.
[edit protocols msdp] user@host# set local-address 192.168.132.1
user@host# set peer 192.168.12.1
On each non-RP router in the domain, configure a static RP address using the shared address.
[edit protocols pim] user@host# set rp static address 10.1.1.2
If you are done configuring the devices, commit the configuration.
user@host# commit
Results
From configuration mode, confirm your configuration by entering the show interfaces, show protocols , and show routing-options commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
user@host# show interfaces lo0 { unit 0 { family inet { address 192.168.132.1/32 { primary;
}
Copyright © 2016, Juniper Networks, Inc.
67
Multicast Protocols Feature Guide for EX4600 Switches
}
}
} address 10.1.1.2/32;
On the RP routers: user@host# show protocols msdp { local-address 192.168.132.1; peer 192.168.12.1;
} pim { rp { local { address 10.1.1.2;
}
}
}
On the non-RP routers: user@host# show protocols pim { rp { static { address 10.1.1.2;
}
}
} user@host# show routing-options router-id 192.168.132.1;
Verification
To verify the configuration, run the
extensive inet command.
Related
Documentation
•
Example: Configuring PIM Anycast With or Without MSDP on page 60
•
Understanding PIM Sparse Mode on page 23
•
Understanding RP Mapping with Anycast RP on page 59
68 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 6
Using PIM Bootstrap Router
•
Understanding the PIM Bootstrap Router on page 69
•
Configuring PIM Bootstrap Properties for IPv4 or IPv6 on page 69
•
Example: Rejecting PIM Bootstrap Messages at the Boundary of a PIM Domain on page 71
•
Example: Configuring PIM BSR Filters on page 71
Understanding the PIM Bootstrap Router
To determine which router is the rendezvous point (RP), all routers within a PIM sparse-mode domain collect bootstrap messages. A PIM sparse-mode domain is a group of routers that all share the same RP router. The domain bootstrap router initiates bootstrap messages, which are sent hop by hop within the domain. The routers use bootstrap messages to distribute RP information dynamically and to elect a bootstrap router when necessary.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
Configuring PIM Bootstrap Properties for IPv4 or IPv6
For correct operation, every multicast router within a PIM domain must be able to map a particular multicast group address to the same rendezvous point (RP). The bootstrap router mechanism is one way that a multicast router can learn the set of group-to-RP mappings. Bootstrap routers are supported in IPv4 and IPv6.
To determine which routing device is the RP, all routing devices within a PIM domain collect bootstrap messages. A PIM domain is a contiguous set of routing devices that implement PIM. All devices are configured to operate within a common boundary. The domain's bootstrap router initiates bootstrap messages, which are sent hop by hop within the domain. The routing devices use bootstrap messages to distribute RP information dynamically and to elect a bootstrap router when necessary.
Copyright © 2016, Juniper Networks, Inc.
69
Multicast Protocols Feature Guide for EX4600 Switches
70
You can configure bootstrap properties globally or for a routing instance. This example shows the global configuration.
To configure the bootstrap router properties:
1.
Configure the bootstrap priority.
By default, each routing device has a bootstrap priority of 0, which means the routing device can never be the bootstrap router. The routing device with the highest priority value is elected to be the bootstrap router. In the case of a tie, the routing device with the highest IP address is elected to be the bootstrap router. A simple bootstrap configuration assigns a bootstrap priority value to a routing device.
NOTE: In the IPv4-only configuration, specifying a bootstrap priority of 0 disables the bootstrap function and does not cause the routing device to send BSR packets with a 0 in the priority field. In the combined IPv4 and
IPv6 configuration, specifying a bootstrap priority of 0 does not disable the function, but causes the routing device to send BSR packets with a 0 in the priority field. To disable the bootstrap function in the IPv4 and IPv6 configuration, delete the bootstrap statement.
user@host# edit protocols pim
user@host# set
inet
3
2.
(Optional) Create import and export policies to control the flow of bootstrap messages to and from the RP, and apply the policies to PIM. Import and export policies are useful when some of the routers in your PIM domain have interfaces that connect to other
PIM domains. Configuring a policy prevents bootstrap messages from crossing domain boundaries. The import statement prevents messages from being imported into the
RP. The export statement prevents messages from being exported from the RP.
[edit protocols pim
user@host# set
inet
pim-bootstrap-import user@host# set
inet
pim-bootstrap-export user@host# exit
3.
Configure the policies.
user@host# edit policy-options policy-statement pim-bootstrap-import
[edit policy-options policy-statement pim-bootstrap-import] user@host# set from interface se-0/0/0 user@host# set then reject user@host# exit user@host# edit policy-options policy-statement pim-bootstrap-export user@host# set from interface se-0/0/0 user@host# set then reject user@host# exit
4.
Monitor the operation of PIM bootstrap routers by running the show pim bootstrap command.
Related
Documentation
•
Understanding PIM Sparse Mode on page 23
Copyright © 2016, Juniper Networks, Inc.
Chapter 6: Using PIM Bootstrap Router
•
Example: Rejecting PIM Bootstrap Messages at the Boundary of a PIM Domain on page 71
•
show pim bootstrap on page 393
in the CLI Explorer
Example: Rejecting PIM Bootstrap Messages at the Boundary of a PIM Domain
In this example, the from interface so-0-1/0 then reject policy statement rejects bootstrap messages from the specified interface (the example is configured for both IPv4 and IPv6 operation): protocols { pim { rp { bootstrap { family inet { priority 1; import pim-import; export pim-export;
} family inet6 { priority 1; import pim-import; export pim-export;
}
}
}
}
} policy-options { policy-statement pim-import { from interface so-0/1/0; then reject;
} policy-statement pim-export { to interface so-0/1/0; then reject;
}
}
Example: Configuring PIM BSR Filters
Configure a filter to prevent BSR messages from entering or leaving your network. Add this configuration to all routers: protocols { pim { rp { bootstrap-import no-bsr; bootstrap-export no-bsr;
}
}
}
Copyright © 2016, Juniper Networks, Inc.
71
Multicast Protocols Feature Guide for EX4600 Switches policy-options { policy-statement no-bsr { then reject;
}
}
72 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 7
Using PIM Filtering
•
Understanding Multicast Message Filters on page 73
•
Filtering MAC Addresses on page 74
•
Filtering RP and DR Register Messages on page 74
•
Configuring Interface-Level PIM Neighbor Policies on page 75
•
Filtering Outgoing PIM Join Messages on page 76
•
Filtering Incoming PIM Join Messages on page 77
•
Configuring Register Message Filters on a PIM RP and DR on page 79
Understanding Multicast Message Filters
Multicast sources and routers generate a considerable number of control messages, especially when using PIM sparse mode. These messages form distribution trees, locate rendezvous points (RPs) and designated routers (DRs), and transition from one type of tree to another. In most cases, this multicast messaging system operates transparently and efficiently. However, in some configurations, more control over the sending and receiving of multicast control messages is necessary.
You can configure multicast filtering to control the sending and receiving of multicast control messages.
To prevent unauthorized groups and sources from registering with an RP router, you can define a routing policy to reject PIM register messages from specific groups and sources and configure the policy on the designated router or the RP router.
• If you configure the reject policy on an RP router, it rejects incoming PIM register messages from the specified groups and sources. The RP router also sends a register stop message by means of unicast to the designated router. On receiving the register stop message, the designated router sends periodic null register messages for the specified groups and sources to the RP router.
• If you configure the reject policy on a designated router, it stops sending PIM register messages for the specified groups and sources to the RP router.
Copyright © 2016, Juniper Networks, Inc.
73
Multicast Protocols Feature Guide for EX4600 Switches
NOTE: If you have configured the reject policy on an RP router, we recommend that you configure the same policy on all the RP routers in your multicast network.
NOTE: If you delete a group and source address from the reject policy configured on an RP router and commit the configuration, the RP router will register the group and source only when the designated router sends a null register message.
Related
Documentation
•
Filtering MAC Addresses on page 74
•
Filtering RP and DR Register Messages on page 74
•
Filtering MSDP SA Messages on page 166
Filtering MAC Addresses
When a router is exclusively configured with multicast protocols on an interface, multicast sets the interface media access control (MAC) filter to multicast promiscuous mode, and the number of multicast groups is unlimited. However, when the router is not exclusively used for multicasting and other protocols such as OSPF, Routing Information
Protocol version 2 (RIPv2), or Network Time Protocol (NTP) are configured on an interface, each of these protocols individually requests that the interface program the MAC filter to pick up its respective multicast group only. In this case, without multicast configured on the interface, the maximum number of multicast MAC filters is limited to 20. For example, the maximum number of interface MAC filters for protocols such as OSPF
(multicast group 224.0.0.5) is 20, unless a multicast protocol is also configured on the interface.
No configuration is necessary for MAC filters.
Filtering RP and DR Register Messages
You can filter Protocol Independent Multicast (PIM) register messages sent from the designated router (DR) or to the rendezvous point (RP). The PIM RP keeps track of all active sources in a single PIM sparse mode domain. In some cases, more control over which sources an RP discovers, or which sources a DR notifies other RPs about, is desired.
A high degree of control over PIM register messages is provided by RP and DR register message filtering. Message filtering also prevents unauthorized groups and sources from registering with an RP router.
Register messages that are filtered at a DR are not sent to the RP, but the sources are available to local users. Register messages that are filtered at an RP arrive from source
DRs, but are ignored by the router. Sources on multicast group traffic can be limited or directed by using RP or DR register message filtering alone or together.
74 Copyright © 2016, Juniper Networks, Inc.
Chapter 7: Using PIM Filtering
If the action of the register filter policy is to discard the register message, the router needs to send a register-stop message to the DR. Register-stop messages are throttled to prevent malicious users from triggering them on purpose to disrupt the routing process.
Multicast group and source information is encapsulated inside unicast IP packets. This feature allows the router to inspect the multicast group and source information before sending or accepting the PIM register message.
Incoming register messages to an RP are passed through the configured register message filtering policy before any further processing. If the register message is rejected, the RP router sends a register-stop message to the DR. When the DR receives the register-stop message, the DR stops sending register messages for the filtered groups and sources to the RP. Two fields are used for register message filtering:
• Group multicast address
• Source address
The syntax of the existing policy statements is used to configure the filtering on these two fields. The route-filter statement is useful for multicast group address filtering, and the source-address-filter statement is useful for source address filtering. In most cases, the action is to reject the register messages, but more complex filtering policies are possible.
Filtering cannot be performed on other header fields, such as DR address, protocol, or port. In some configurations, an RP might not send register-stop messages when the policy action is to discard the register messages. This has no effect on the operation of the feature, but the router will continue to receive register messages.
When anycast RP is configured, register messages can be sent or received by the RP. All the RPs in the anycast RP set need to be configured with the same RP register message filtering policies. Otherwise, it might be possible to circumvent the filtering policy.
Related
Documentation
•
Understanding RP Mapping with Anycast RP on page 59
•
Configuring Register Message Filters on a PIM RP and DR on page 79
Configuring Interface-Level PIM Neighbor Policies
You can configure a policy to filter unwanted PIM neighbors. In the following example, the PIM interface compares neighbor IP addresses with the IP address in the policy statement before any hello processing takes place. If any of the neighbor IP addresses
(primary or secondary) match the IP address specified in the prefix list, PIM drops the hello packet and rejects the neighbor.
If you configure a PIM neighbor policy after PIM has already established a neighbor adjacency to an unwanted PIM neighbor, the adjacency remains intact until the neighbor hold time expires. When the unwanted neighbor sends another hello message to update its adjacency, the router recognizes the unwanted address and rejects the neighbor.
Copyright © 2016, Juniper Networks, Inc.
75
Multicast Protocols Feature Guide for EX4600 Switches
To configure a policy to filter unwanted PIM neighbors:
1.
Configure the policy. The neighbor policy must be a properly structured policy statement that uses a prefix list (or a route filter) containing the neighbor primary address (or any secondary IP addresses) in a prefix list, and the reject option to reject the unwanted address.
[edit policy-options] user@host# set prefix-list nbrGroup 1 20.20.20.1/32 user@host# set policy-statement nbr-policy from prefix-list nbrGroup1 user@host# set policy-statement nbr-policy then reject
2.
Configure the interface globally or in the routing instance. This example shows the configuration for the routing instance.
[edit routing-instances PIM.master protocols pim] user@host# set
nbr-policy
3.
Verify the configuration by checking the Hello dropped on neighbor policy field in the output of the show pim statistics command.
Related
Documentation
•
Understanding PIM Sparse Mode on page 23
•
show pim statistics on page 433
Filtering Outgoing PIM Join Messages
When the core of your network is using MPLS, PIM join and prune messages stop at the customer edge (CE) routers and are not forwarded toward the core, because these routers do not have PIM neighbors on the core-facing interfaces. When the core of your network is using IP, PIM join and prune messages are forwarded to the upstream PIM neighbors in the core of the network.
When the core of your network is using a mix of IP and MPLS, you might want to filter certain PIM join and prune messages at the upstream egress interface of the CE routers.
You can filter PIM sparse mode (PIM-SM) join and prune messages at the egress interfaces for IPv4 and IPv6 in the upstream direction. The messages can be filtered based on the group address, source address, outgoing interface, PIM neighbor, or a combination of these values. If the filter is removed, the join is sent after the PIM periodic join timer expires.
To filter PIM sparse mode join and prune messages at the egress interfaces, create a policy rejecting the group address, source address, outgoing interface, or PIM neighbor, and then apply the policy.
The following example filters PIM join and prune messages for group addresses 224.0.1.2
and 225.1.1.1.
1.
In configuration mode, create the policy.
user@host# set policy-options policy-statement block-groups term t1 from route-filter
224.0.1.2/32 exact user@host# set policy-options policy-statement block-groups term t1 from route-filter
225.1.1.1/32 exact
76 Copyright © 2016, Juniper Networks, Inc.
Chapter 7: Using PIM Filtering user@host# set policy-options policy-statement block-groups term t1 then reject user@host# set policy-options policy-statement block-groups term last then accept
2.
Verify the policy configuration by running the show policy-options command.
user@host# show policy-options policy-statement block-groups { term t1 { from { route-filter 224.0.1.2/32 exact; route-filter 225.1.1.1/32 exact; then reject;
} term last { then accept;
}
}
3.
Apply the PIM join and prune message filter.
user@host> set protocols pim export block-groups
4.
After the configuration is committed, use the show pim statistics command to verify that outgoing PIM join and prune messages are being filtered.
user@host> show pim statistics | grep filtered
RP Filtered Source 0
Rx Joins/Prunes filtered 0
Tx Joins/Prunes filtered 254
The egress filter count is shown on the Tx Joins/Prunes filtered line.
Related
Documentation
•
Filtering Incoming PIM Join Messages on page 77
Filtering Incoming PIM Join Messages
Multicast scoping controls the propagation of multicast messages. Whereas multicast scoping prevents the actual multicast data packets from flowing in or out of an interface,
PIM join filters prevent a state from being created in a router. A state—the (*,G) or (S,G) entries—is the information used for forwarding unicast or multicast packets. Using PIM join filters prevents the transport of multicast traffic across a network and the dropping of packets at a scope at the edge of the network. Also, PIM join filters reduce the potential for denial-of-service (DoS) attacks and PIM state explosion—large numbers of PIM join messages forwarded to each router on the rendezvous-point tree (RPT), resulting in memory consumption.
To use PIM join filters to efficiently restrict multicast traffic from certain source addresses, create and apply the routing policy across all routers in the network.
See
for a list of match conditions.
Copyright © 2016, Juniper Networks, Inc.
77
Multicast Protocols Feature Guide for EX4600 Switches
Table 4: PIM Join Filter Match Conditions
Match Condition Matches On interface neighbor
Router interface or interfaces specified by name or IP address
Neighbor address (the source address in the IP header of the join and prune message)
Multicast group address embedded in the join and prune message route-filter source-address-filter Multicast source address embedded in the join and prune message
The following example shows how to create a PIM join filter. The filter is composed of a route filter and a source address filter—bad-groups and bad-sources, respectively. the bad-groups filter prevents (*,G) or (S,G) join messages from being received for all groups listed. The bad-sources filter prevents (S,G) join messages from being received for all sources listed. The bad-groups filter and bad-sources filter are in two different terms. If route filters and source address filters are in the same term, they are logically ANDed.
To filter incoming PIM join messages:
1.
Configure the policy.
[edit policy-statement pim-join-filter term bad-groups] user@host# set from route-filter 224.0.1.2/32 exact user@host# set from route-filter 239.0.0.0/8 orlonger user@host# set then reject
[edit policy-statement pim-join-filter term bad-sources] user@host# set from source-address-filter 10.0.0.0/8 orlonger user@host# set from source-address-filter 127.0.0.0/8 orlonger user@host# set then reject
[edit policy-statement pim-join-filter term last] user@host# set then accept
2.
Apply one or more policies to routes being imported into the routing table from PIM.
[edit protocols pim] user@host# set
pim-join-filter
3.
Verify the configuration by checking the output of the show pim join and show policy commands.
Related
Documentation
• Understanding Multicast Administrative Scoping
•
Filtering Outgoing PIM Join Messages on page 76
•
in the CLI Explorer
• show policy in the CLI Explorer
78 Copyright © 2016, Juniper Networks, Inc.
Chapter 7: Using PIM Filtering
Configuring Register Message Filters on a PIM RP and DR
PIM register messages are sent to the rendezvous point (RP) by a designated router (DR).
When a source for a group starts transmitting, the DR sends unicast PIM register packets to the RP.
Register messages have the following purposes:
• Notify the RP that a source is sending to a group.
• Deliver the initial multicast packets sent by the source to the RP for delivery down the shortest-path tree (SPT).
The PIM RP keeps track of all active sources in a single PIM sparse mode domain. In some cases, you want more control over which sources an RP discovers, or which sources a
DR notifies other RPs about. A high degree of control over PIM register messages is provided by RP or DR register message filtering. Message filtering prevents unauthorized groups and sources from registering with an RP router.
You configure RP or DR register message filtering to control the number and location of multicast sources that an RP discovers. You can apply register message filters on a DR to control outgoing register messages, or apply them on an RP to control incoming register messages.
When anycast RP is configured, all RPs in the anycast RP set need to be configured with the same register message filtering policy.
You can configure message filtering globally or for a routing instance. These examples show the global configuration.
To configure an RP filter to drop the register packets for multicast group range 224.1.1.0/24 from source address 10.10.94.2:
1.
On the RP, configure the policy.
[edit policy-options policy-statement incoming-policy-for-rp from] user@host# set route-filter 224.1.1.0/24 orlonger user@host# set source-address-filter 10.10.94.2/32 exact user@host# set then reject user@host# exit
2.
Apply the policy to the RP.
[edit protocols pim
user@host# set
incoming-policy-for-rp user@host# set
address 10.10.10.5
user@host# exit
To configure a DR filter to prevent sending register packets for group range 224.1.1.0/24 and source address 10.10.10.1/32:
1.
On the DR, configure the policy.
[edit policy-options policy-statement outgoing-policy-for-rp]
Copyright © 2016, Juniper Networks, Inc.
79
Multicast Protocols Feature Guide for EX4600 Switches user@host# set from route-filter 224.1.1.0/24 orlonger user@host# set from source-address-filter 10.10.10.1/32 exact user@host# set then reject user@host# exit
2.
Apply the policy to the DR.
The static address is the address of the RP to which you do not want the DR to send the filtered register messages.
[edit protocols pim
user@host# set
outgoing-policy-for-dr user@host# set
10.10.10.3
user@host# exit
To configure a policy expression to accept register messages for multicast group 224.1.1.5
but reject those for 224.1.1.1:
1.
On the RP, configure the policies.
[edit policy-options policy-statement reject_224_1_1_1] user@host# set from route-filter 224.1.1.0/24 orlonger user@host# set from source-address-filter 10.10.94.2/32 exact user@host# set then reject user@host# exit
[edit policy-options policy-statement accept_224_1_1_5] user@host# set term one from route-filter 224.1.1.5/32 exact user@host# set term one from source-address-filter 10.10.94.2/32 exact user@host# set term one then accept user@host# set term two then reject user@host# exit
2.
Apply the policies to the RP.
[edit protocols pim
user@host# set
[ reject_224_1_1_1 | accept_224_1_1_5 ] user@host# set
address 10.10.10.5
To monitor the operation of the filters, run the show pim statistics command. The command output contains the following fields related to filtering:
• RP Filtered Source
• Rx Joins/Prunes filtered
• Tx Joins/Prunes filtered
• Rx Register msgs filtering drop
• Tx Register msgs filtering drop
Related
Documentation
•
PIM Sparse Mode Source Registration on page 83
•
Filtering RP and DR Register Messages on page 74
•
show pim statistics on page 433
80 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 8
Using PIM RPT and SPT Cutover
•
Understanding Multicast Rendezvous Points, Shared Trees, and Rendezvous-Point
•
Building an RPT Between the RP and Receivers on page 82
•
PIM Sparse Mode Source Registration on page 83
•
Multicast Shortest-Path Tree on page 86
•
•
SPT Cutover Control on page 90
•
Example: Configuring the PIM Assert Timeout on page 90
•
Example: Configuring the PIM SPT Threshold Policy on page 92
Understanding Multicast Rendezvous Points, Shared Trees, and Rendezvous-Point
Trees
In a shared tree, the root of the distribution tree is a router, not a host, and is located somewhere in the core of the network. In the primary sparse mode multicast routing protocol, Protocol Independent Multicast sparse mode (PIM SM), the core router at the root of the shared tree is the rendezvous point (RP). Packets from the upstream source and join messages from the downstream routers “rendezvous” at this core router.
In the RP model, other routers do not need to know the addresses of the sources for every multicast group. All they need to know is the IP address of the RP router. The RP router discovers the sources for all multicast groups.
The RP model shifts the burden of finding sources of multicast content from each router
(the (S,G) notation) to the network (the (*,G) notation knows only the RP). Exactly how the RP finds the unicast IP address of the source varies, but there must be some method to determine the proper source for multicast content for a particular group.
Consider a set of multicast routers without any active multicast traffic for a certain group.
When a router learns that an interested receiver for that group is on one of its directly connected subnets, the router attempts to join the distribution tree for that group back to the RP, not to the actual source of the content.
To join the shared tree, or rendezvous-point tree (RPT) as it is called in PIM sparse mode, the router must do the following:
Copyright © 2016, Juniper Networks, Inc.
81
Multicast Protocols Feature Guide for EX4600 Switches
• Determine the IP address of the RP for that group. Determining the address can be as simple as static configuration in the router, or as complex as a set of nested protocols.
• Build the shared tree for that group. The router executes an RPF check on the RP address in its routing table, which produces the interface closest to the RP. The router now detects that multicast packets from this RP for this group need to flow into the router on this RPF interface.
• Send a join message out on this interface using the proper multicast protocol (probably
PIM sparse mode) to inform the upstream router that it wants to join the shared tree for that group. This message is a (*,G) join message because S is not known. Only the
RP is known, and the RP is not actually the source of the multicast packets. The router receiving the (*,G) join message adds the interface on which the message was received to its outgoing interface list (OIL) for the group and also performs an RPF check on the
RP address. The upstream router then sends a (*,G) join message out from the RPF interface toward the source, informing the upstream router that it also wants to join the group.
Each upstream router repeats this process, propagating join messages from the RPF interface, building the shared tree as it goes. The process stops when the join message reaches one of the following:
• The RP for the group that is being joined
• A router along the RPT that already has a multicast forwarding state for the group that is being joined
In either case, the branch is created, and packets can flow from the source to the RP and from the RP to the receiver. Note that there is no guarantee that the shared tree (RPT) is the shortest path tree to the source. Most likely it is not. However, there are ways to
“migrate” a shared tree to an SPT once the flow of packets begins. In other words, the forwarding state can transition from (*,G) to (S,G). The formation of both types of tree depends heavily on the operation of the RPF check and the RPF table. For more information about the RPF table, see Understanding Multicast Reverse Path Forwarding.
Building an RPT Between the RP and Receivers
The RPT is the path between the RP and receivers (hosts) in a multicast group (see
Figure 11 on page 83 ). The RPT is built by means of a PIM join message from a receiver's
DR:
1.
A receiver sends a request to join group (G) in an Internet Group Management Protocol
(IGMP) host membership report. A PIM sparse-mode router, the receiver’s DR, receives the report on a directly attached subnet and creates an RPT branch for the multicast group of interest.
2.
The receiver’s DR sends a PIM join message to its RPF neighbor, the next-hop address in the RPF table, or the unicast routing table.
3.
The PIM join message travels up the tree and is multicast to the ALL-PIM-ROUTERS group (224.0.0.13). Each router in the tree finds its RPF neighbor by using either the
RPF table or the unicast routing table. This is done until the message reaches the RP
82 Copyright © 2016, Juniper Networks, Inc.
Chapter 8: Using PIM RPT and SPT Cutover and forms the RPT. Routers along the path set up the multicast forwarding state to forward requested multicast traffic back down the RPT to the receiver.
Figure 11: Building an RPT Between the RP and the Receiver
PIM Sparse Mode Source Registration
The RPT is a unidirectional tree, permitting traffic to flow down from the RP to the receiver in one direction. For multicast traffic to reach the receiver from the source, another branch of the distribution tree, called the shortest-path tree, needs to be built from the source's
DR to the RP.
The shortest-path tree is created in the following way:
1.
The source becomes active, sending out multicast packets on the LAN to which it is attached. The source’s DR receives the packets and encapsulates them in a PIM register message, which it sends to the RP router (see
).
2.
When the RP router receives the PIM register message from the source, it sends a PIM join message back to the source.
Copyright © 2016, Juniper Networks, Inc.
83
Multicast Protocols Feature Guide for EX4600 Switches
Figure 12: PIM Register Message and PIM Join Message Exchanged
3.
The source’s DR receives the PIM join message and begins sending traffic down the
SPT toward the RP router (see
4.
Once traffic is received by the RP router, it sends a register stop message to the source’s
DR to stop the register process.
84 Copyright © 2016, Juniper Networks, Inc.
Chapter 8: Using PIM RPT and SPT Cutover
Figure 13: Traffic Sent from the Source to the RP Router
5.
The RP router sends the multicast traffic down the RPT toward the receiver (see
Figure 14: Traffic Sent from the RP Router Toward the Receiver
Copyright © 2016, Juniper Networks, Inc.
85
Multicast Protocols Feature Guide for EX4600 Switches
Multicast Shortest-Path Tree
The distribution tree used for multicast is rooted at the source and is the shortest-path tree (SPT) as well. Consider a set of multicast routers without any active multicast traffic for a certain group (that is, they have no multicast forwarding state for that group). When a router learns that an interested receiver for that group is on one of its directly connected subnets, the router attempts to join the tree for that group.
To join the distribution tree, the router determines the unicast IP address of the source for that group. This address can be a simple static configuration on the router, or as complex as a set of protocols.
To build the SPT for that group, the router executes an a reverse path forwarding (RPF) check on the source address in its routing table. The RPF check produces the interface closest to the source, which is where multicast packets from this source for this group need to flow into the router.
The router next sends a join message out on this interface using the proper multicast protocol to inform the upstream router that it wants to join the distribution tree for that group. This message is an (S,G) join message because both S and G are known. The router receiving the (S,G) join message adds the interface on which the message was received to its output interface list (OIL) for the group and also performs an RPF check on the source address. The upstream router then sends an (S,G) join message out on the RPF interface toward the source, informing the upstream router that it also wants to join the group.
Each upstream router repeats this process, propagating joins out on the RPF interface, building the SPT as it goes. The process stops when the join message does one of two things:
• Reaches the router directly connected to the host that is the source.
• Reaches a router that already has multicast forwarding state for this source-group pair.
In either case, the branch is created, each of the routers has multicast forwarding state for the source-group pair, and packets can flow down the distribution tree from source to receiver. The RPF check at each router makes sure that the tree is an SPT.
SPTs are always the shortest path, but they are not necessarily short. That is, sources and receivers tend to be on the periphery of a router network, not on the backbone, and multicast distribution trees have a tendency to sprawl across almost every router in the network. Because multicast traffic can overwhelm a slow interface, and one packet can easily become a hundred or a thousand on the opposite side of the backbone, it makes sense to provide a shared tree as a distribution tree so that the multicast source can be located more centrally in the network, on the backbone. This sharing of distribution trees with roots in the core network is accomplished by a multicast rendezvous point. For more information about RPs, see
“Understanding Multicast Rendezvous Points, Shared Trees, and Rendezvous-Point Trees” on page 81
.
86 Copyright © 2016, Juniper Networks, Inc.
Chapter 8: Using PIM RPT and SPT Cutover
SPT Cutover
Instead of continuing to use the SPT to the RP and the RPT toward the receiver, a direct
SPT is created between the source and the receiver in the following way:
1.
Once the receiver’s DR receives the first multicast packet from the source, the DR sends a PIM join message to its RPF neighbor (see
).
2.
The source’s DR receives the PIM join message, and an additional (S,G) state is created to form the SPT.
3.
Multicast packets from that particular source begin coming from the source's DR and flowing down the new SPT to the receiver’s DR. The receiver’s DR is now receiving two copies of each multicast packet sent by the source—one from the RPT and one from the new SPT.
Figure 15: Receiver DR Sends a PIM Join Message to the Source
4.
To stop duplicate multicast packets, the receiver’s DR sends a PIM prune message toward the RP router, letting it know that the multicast packets from this particular source coming in from the RPT are no longer needed (see
Copyright © 2016, Juniper Networks, Inc.
87
Multicast Protocols Feature Guide for EX4600 Switches
Figure 16: PIM Prune Message Is Sent from the Receiver’s DR Toward the
RP Router
5.
The PIM prune message is received by the RP router, and it stops sending multicast packets down to the receiver’s DR. The receiver’s DR is getting multicast packets only for this particular source over the new SPT. However, multicast packets from the source are still arriving from the source’s DR toward the RP router (see
Figure 17: RP Router Receives PIM Prune Message
88 Copyright © 2016, Juniper Networks, Inc.
Chapter 8: Using PIM RPT and SPT Cutover
6.
To stop the unneeded multicast packets from this particular source, the RP router sends a PIM prune message to the source’s DR (see
Figure 18: RP Router Sends a PIM Prune Message to the Source DR
7.
The receiver’s DR now receives multicast packets only for the particular source from the SPT (see
Figure 19: Source’s DR Stops Sending Duplicate Multicast Packets Toward the RP Router
Copyright © 2016, Juniper Networks, Inc.
89
Multicast Protocols Feature Guide for EX4600 Switches
SPT Cutover Control
In some cases, the last-hop router needs to stay on the shared tree to the RP and not transition to a direct SPT to the source. You might not want the last-hop router to transition when, for example, a low-bandwidth multicast stream is forwarded from the
RP to a last-hop router. All routers between last hop and source must maintain and refresh the SPT state. This can become a resource-intensive activity that does not add much to the network efficiency for a particular pair of source and multicast group addresses.
In these cases, you configure an SPT threshold policy on the last-hop router to control the transition to a direct SPT. An SPT cutover threshold of infinity applied to a source-group address pair means the last-hop router will never transition to a direct SPT.
For all other source-group address pairs, the last-hop router transitions immediately to a direct SPT rooted at the source DR.
Example: Configuring the PIM Assert Timeout
This example shows how to configure the timeout period for a PIM assert forwarder.
•
•
•
Requirements
Before you begin:
• Configure the router interfaces.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing
Protocols Library for Routing Devices.
• Configure PIM Sparse Mode on the interfaces. See
“Enabling PIM Sparse Mode” on page 26 .
Overview
The role of PIM assert messages is to determine the forwarder on a network with multiple routers. The forwarder is the router that forwards multicast packets to a network with multicast group members. The forwarder is generally the same as the PIM DR.
A router sends an assert message when it receives a multicast packet on an interface that is listed in the outgoing interface list of the matching routing entry. Receiving a message on an outgoing interface is an indication that more than one router forwards the same multicast packets to a network.
In
, both routing devices R1 and R2 forward multicast packets for the same (S,G) entry on a network. Both devices detect this situation and both devices send assert messages on the Ethernet network. An assert message contains, in addition to a source address and group address, a unicast cost metric for sending packets to the
90 Copyright © 2016, Juniper Networks, Inc.
Chapter 8: Using PIM RPT and SPT Cutover source, and a preference metric for the unicast cost. The preference metric expresses a preference between unicast routing protocols. The routing device with the smallest preference metric becomes the forwarder (also called the assert winner). If the preference metrics are equal, the device that sent the lowest unicast cost metric becomes the forwarder. If the unicast metrics are also equal, the routing device with the highest IP address becomes the forwarder. After the transmission of assert messages, only the forwarder continues to forward messages on the network.
When an assert message is received and the RPF neighbor is changed to the assert winner, the assert timer is set to an assert timeout period. The assert timeout period is restarted every time a subsequent assert message for the route entry is received on the incoming interface. When the assert timer expires, the routing device resets its RPF neighbor according to its unicast routing table. Then, if multiple forwarders still exist, the forwarders reenter the assert message cycle. In effect, the assert timeout period determines how often multicast routing devices enter a PIM assert message cycle.
The range is from 5 through 210 seconds. The default is 180 seconds.
Assert messages are useful for LANs that connect multiple routing devices and no hosts.
shows the topology for this example.
Figure 20: PIM Assert Topology
PIM network src: S dest: G
R1
Assert:
(S,G)
Assert:
(S,G)
R2 src: S dest: G
Ethernet
Host
Copyright © 2016, Juniper Networks, Inc.
91
Multicast Protocols Feature Guide for EX4600 Switches
Configuration
Step-by-Step
Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure an assert timeout:
1.
2.
3.
4.
Configure the timeout period, in seconds.
[edit protocols pim] user@host# set
60
(Optional) Trace assert messages.
[edit protocols pim] user@host# set traceoptions file PIM.log
user@host# set traceoptions flag assert detail
If you are done configuring the device, commit the configuration.
user@host# commit
To verify the configuration, run the following commands:
•
•
Related
Documentation
•
Configuring PIM Trace Options on page 10
•
•
SPT Cutover Control on page 90
Example: Configuring the PIM SPT Threshold Policy
This example shows how to apply a policy that suppresses the transition from the rendezvous-point tree (RPT) rooted at the RP to the shortest-path tree (SPT) rooted at the source.
•
•
•
•
Requirements
Before you begin:
• Configure the router interfaces.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing
Protocols Library for Routing Devices.
92 Copyright © 2016, Juniper Networks, Inc.
Overview
Chapter 8: Using PIM RPT and SPT Cutover
• Configure PIM Sparse Mode on the interfaces. See
“Enabling PIM Sparse Mode” on page 26 .
Multicast routing devices running PIM sparse mode can forward the same stream of multicast packets onto the same LAN through an RPT rooted at the RP or through an
SPT rooted at the source. In some cases, the last-hop routing device needs to stay on the shared RPT to the RP and not transition to a direct SPT to the source. Receiving the multicast data traffic on SPT is optimal but introduces more state in the network, which might not be desirable in some multicast deployments. Ideally, low-bandwidth multicast streams can be forwarded on the SPT, and high-bandwidth streams can use the SPT.
This example shows how to configure such a policy.
This example includes the following settings:
• spt-threshold —Enables you to configure an SPT threshold policy on the last-hop routing device to control the transition to a direct SPT. When you include this statement in the main PIM instance, the PE router stays on the RPT for control traffic.
• infinity —Applies an SPT cutover threshold of infinity to a source-group address pair, so that the last-hop routing device never transitions to a direct SPT. For all other source-group address pairs, the last-hop routing device transitions immediately to a direct SPT rooted at the source DR. This statement must reference a properly configured policy to set the SPT cutover threshold for a particular source-group pair to infinity.
The use of values other than infinity for the SPT threshold is not supported. You can configure more than one policy.
• policy-statement —Configures the policy. The simplest type of SPT threshold policy uses a route filter and source address filter to specify the multicast group and source addresses and to set the SPT threshold for that pair of addresses to infinity. The policy is applied to the main PIM instance.
This example sets the SPT transition value for the source-group pair 10.10.10.1 and
224.1.1.1 to infinity. When the policy is applied to the last-hop router, multicast traffic from this source-group pair never transitions to a direct SPT to the source. Traffic will continue to arrive through the RP. However, traffic for any other source-group address combination at this router transitions to a direct SPT to the source.
Copyright © 2016, Juniper Networks, Inc.
93
Multicast Protocols Feature Guide for EX4600 Switches
Note these points when configuring the SPT threshold policy:
• Configuration changes to the SPT threshold policy affect how the routing device handles the SPT transition.
Note these points when configuring the SPT threshold policy:
• Configuration changes to the SPT threshold policy affect how the routing device handles the SPT transition.
Note these points when configuring the SPT threshold policy:
• Configuration changes to the SPT threshold policy affect how the routing device handles the SPT transition.
• When the policy is configured for the first time, the routing device continues to transition to the direct SPT for the source-group address pair until the PIM-join state is cleared with the clear pim join command.
• If you do not clear the PIM-join state when you apply the infinity policy configuration for the first time, you must apply it before the PE router is brought up.
• When the policy is deleted for a source-group address pair for the first time, the routing device does not transition to the direct SPT for that source-group address pair until the PIM-join state is cleared with the clear pim join command.
• When the policy is changed for a source-group address pair for the first time, the routing device does not use the new policy until the PIM-join state is cleared with the clear pim join command.
Configuration
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
[edit] set policy-options policy-statement spt-infinity-policy term one from route-filter
224.1.1.1/32 exact set policy-options policy-statement spt-infinity-policy term one from source-address-filter
10.10.10.1/32 exact set policy-options policy-statement spt-infinity-policy term one then accept set policy-options policy-statement spt-infinity-policy term two then reject set protocols pim spt-threshold infinity spt-infinity-policy
Step-by-Step
Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see the CLI User Guide.
To configure an SPT threshold policy:
1.
Apply the policy.
[edit] user@host# edit protocols pim
94 Copyright © 2016, Juniper Networks, Inc.
Chapter 8: Using PIM RPT and SPT Cutover
2.
3.
4.
[edit protocols pim] user@host# set
spt-infinity-policy
[edit protocols pim] user@host# exit
Configure the policy.
[edit] user@host# edit policy-options policy-statement spt-infinity-policy
[edit policy-options policy-statement spt-infinity-policy] user@host# set term one from route-filter 224.1.1.1/32 exact
[edit policy-options policy-statement spt-infinity-policy] user@host# set term one from source-address-filter 10.10.10.1/32 exact
[edit policy-options policy-statement spt-infinity-policy] user@host# set term one then accept
[edit policy-options policy-statement spt-infinity-policy] user@host# set term two then reject
[edit policy-options policy-statement spt-infinity-policy] user@host# exit policy-statement {
If you are done configuring the device, commit the configuration.
[edit] user@host# commit
Clear the PIM join cache to force the configuration to take effect.
[edit] user@host# run clear pim join
Results
Confirm your configuration by entering the show policy-options command and the show protocols command from configuration mode. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
user@host# show policy-options policy-statement spt-infinity-policy { term one { from { route-filter 224.1.1.1/32 exact; source-address-filter 10.10.10.1/32 exact;
} then accept;
} term two { then reject;
}
} user@host# show protocols pim { spt-threshold { infinity spt-infinity-policy;
}
}
Copyright © 2016, Juniper Networks, Inc.
95
Multicast Protocols Feature Guide for EX4600 Switches
Verification
To verify the configuration, run the
command.
Related
Documentation
•
SPT Cutover Control on page 90
96 Copyright © 2016, Juniper Networks, Inc.
PART 2
IGMP and IGMP Snooping
•
•
Using IGMP Snooping on page 125
Copyright © 2016, Juniper Networks, Inc.
97
Multicast Protocols Feature Guide for EX4600 Switches
98 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 9
Using IGMP
•
Understanding Group Membership Protocols on page 99
•
Understanding IGMP on page 100
•
•
•
Changing the IGMP Version on page 104
•
Modifying the IGMP Host-Query Message Interval on page 105
•
Modifying the IGMP Last-Member Query Interval on page 106
•
Specifying Immediate-Leave Host Removal for IGMP on page 107
•
Filtering Unwanted IGMP Reports at the IGMP Interface Level on page 108
•
Accepting IGMP Messages from Remote Subnetworks on page 109
•
Modifying the IGMP Query Response Interval on page 110
•
Modifying the IGMP Robustness Variable on page 111
•
Limiting the Maximum IGMP Message Rate on page 112
•
Enabling IGMP Static Group Membership on page 112
•
Recording IGMP Join and Leave Events on page 119
•
Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces on page 120
•
Tracing IGMP Protocol Traffic on page 121
•
Understanding Group Membership Protocols
There is a big difference between the multicast protocols used between host and routing device and between the multicast routing devices themselves. Hosts on a given subnetwork need to inform their routing device only whether or not they are interested in receiving packets from a certain multicast group. The source host needs to inform its routing devices only that it is the source of traffic for a particular multicast group. In other words, no detailed knowledge of the distribution tree is needed by any hosts; only a group membership protocol is needed to inform routing devices of their participation in a multicast group. Between adjacent routing devices, on the other hand, the multicast routing protocols must avoid loops as they build a detailed sense of the network topology
Copyright © 2016, Juniper Networks, Inc.
99
Multicast Protocols Feature Guide for EX4600 Switches and distribution tree from source to leaf. So, different multicast protocols are used for the host-router portion and the router-router portion of the multicast network.
Multicast group membership protocols enable a routing device to detect when a host on a directly attached subnet, typically a LAN, wants to receive traffic from a certain multicast group. Even if more than one host on the LAN wants to receive traffic for that multicast group, the routing device sends only one copy of each packet for that multicast group out on that interface, because of the inherent broadcast nature of LANs. When the multicast group membership protocol informs the routing device that there are no interested hosts on the subnet, the packets are withheld and that leaf is pruned from the distribution tree.
The Internet Group Management Protocol (IGMP) and the Multicast Listener Discovery
(MLD) Protocol are the standard IP multicast group membership protocols: IGMP and
MLD have several versions that are supported by hosts and routing devices:
• IGMPv1—The original protocol defined in RFC 1112. An explicit join message is sent to the routing device, but a timeout is used to determine when hosts leave a group. This process wastes processing cycles on the routing device, especially on older or smaller routing devices.
• IGMPv2—Defined in RFC 2236. Among other features, IGMPv2 adds an explicit leave message to the join message so that routing devices can more easily determine when a group has no interested listeners on a LAN.
• IGMPv3—Defined in RFC 3376. Among other features, IGMPv3 optimizes support for a single source of content for a multicast group, or source-specific multicast (SSM).
• MLDv1—Defined in RFC 2710. MLDv1 is similar to IGMPv2.
• MLDv2—Defined in RFC 3810. MLDv2 similar to IGMPv3.
The various versions of IGMP and MLD are backward compatible. It is common for a routing device to run multiple versions of IGMP and MLD on LAN interfaces. Backward compatibility is achieved by dropping back to the most basic of all versions run on a LAN.
For example, if one host is running IGMPv1, any routing device attached to the LAN running
IGMPv2 can drop back to IGMPv1 operation, effectively eliminating the IGMPv2 advantages.
Running multiple IGMP versions ensures that both IGMPv1 and IGMPv2 hosts find peers for their versions on the routing device.
Related
Documentation
•
Examples: Configuring MLD on page 140
Understanding IGMP
The Internet Group Management Protocol (IGMP) manages the membership of hosts and routing devices in multicast groups. IP hosts use IGMP to report their multicast group memberships to any immediately neighboring multicast routing devices. Multicast routing devices use IGMP to learn, for each of their attached physical networks, which groups have members.
100 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
IGMP is also used as the transport for several related multicast protocols (for example,
Distance Vector Multicast Routing Protocol [DVMRP] and Protocol Independent Multicast version 1 [PIMv1]).
A routing device receives explicit join and prune messages from those neighboring routing devices that have downstream group members. When PIM is the multicast protocol in use, IGMP begins the process as follows:
1.
To join a multicast group, G, a host conveys its membership information through IGMP.
2.
The routing device then forwards data packets addressed to a multicast group G to only those interfaces on which explicit join messages have been received.
3.
A designated router (DR) sends periodic join and prune messages toward a group-specific rendezvous point (RP) for each group for which it has active members.
One or more routing devices are automatically or statically designated as the RP, and all routing devices must explicitly join through the RP.
4.
Each routing device along the path toward the RP builds a wildcard (any-source) state for the group and sends join and prune messages toward the RP.
The term route entry is used to refer to the state maintained in a routing device to represent the distribution tree.
A route entry can include such fields as:
• source address
• group address
• incoming interface from which packets are accepted
• list of outgoing interfaces to which packets are sent
• timers
• flag bits
The wildcard route entry's incoming interface points toward the RP.
The outgoing interfaces point to the neighboring downstream routing devices that have sent join and prune messages toward the RP as well as the directly connected hosts that have requested membership to group G.
5.
This state creates a shared, RP-centered, distribution tree that reaches all group members.
IGMP is an integral part of IP and must be enabled on all routing devices and hosts that need to receive IP multicast traffic.
For each attached network, a multicast routing device can be either a querier or a nonquerier. The querier routing device periodically sends general query messages to solicit group membership information. Hosts on the network that are members of a multicast group send report messages. When a host leaves a group, it sends a leave group message.
Copyright © 2016, Juniper Networks, Inc.
101
Multicast Protocols Feature Guide for EX4600 Switches
IGMP version 3 (IGMPv3) supports inclusion and exclusion lists. Inclusion lists enable you to specify which sources can send to a multicast group. This type of multicast group is called a source-specific multicast (SSM) group, and its multicast address is 232/8.
IGMPv3 provides support for source filtering. For example, a routing device can specify particular routing devices from which it accepts or rejects traffic. With IGMPv3, a multicast routing device can learn which sources are of interest to neighboring routing devices.
Exclusion mode works the opposite of an inclusion list. It allows any source but the ones listed to send to the SSM group.
IGMPv3 interoperates with versions 1 and 2 of the protocol. However, to remain compatible with older IGMP hosts and routing devices, IGMPv3 routing devices must also implement versions 1 and 2 of the protocol. IGMPv3 supports the following membership-report record types: mode is allowed, allow new sources, and block old sources.
Related
Documentation
• Supported IP Multicast Protocol Standards
• Configuring IGMP
Configuring IGMP
Before you begin:
1.
Determine whether the router is directly attached to any multicast sources. Receivers must be able to locate these sources.
2.
Determine whether the router is directly attached to any multicast group receivers. If receivers are present, IGMP is needed.
3.
Determine whether to configure multicast to use sparse, dense, or sparse-dense mode.
Each mode has different configuration considerations.
4.
Determine the address of the RP if sparse or sparse-dense mode is used.
5.
Determine whether to locate the RP with the static configuration, BSR, or auto-RP method.
6.
Determine whether to configure multicast to use its own RPF routing table when configuring PIM in sparse, dense, or sparse-dense mode.
7.
Configure the SAP and SDP protocols to listen for multicast session announcements.
See Configuring the Session Announcement Protocol.
To configure the Internet Group Management Protocol (IGMP), include the igmp statement:
{
;
interface-name {
(
[ policy-names ];
map-name;
102 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
}
ssm-map-name;
{
multicast-group-address {
number;
increment;
ip-address {
number;
increment;
}
}
}
version;
}
seconds;
seconds;
seconds;
number;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
You can include this statement at the following hierarchy levels:
• [edit protocols]
• [edit logical-systems logical-system-name protocols]
By default, IGMP is enabled on all interfaces on which you configure Protocol Independent
Multicast (PIM), and on all broadcast interfaces on which you configure the Distance
Vector Multicast Routing Protocol (DVMRP).
NOTE: You can configure IGMP on an interface without configuring PIM. PIM is generally not needed on IGMP downstream interfaces. Therefore, only one
“pseudo PIM interface” is created to represent all IGMP downstream
(IGMP-only) interfaces on the router. This reduces the amount of router resources, such as memory, that are consumed. You must configure PIM on upstream IGMP interfaces to enable multicast routing, perform reverse-path forwarding for multicast data packets, populate the multicast forwarding table for upstream interfaces, and in the case of bidirectional PIM and PIM sparse mode, to distribute IGMP group memberships into the multicast routing domain.
Enabling IGMP
The Internet Group Management Protocol (IGMP) manages multicast groups by establishing, maintaining, and removing groups on a subnet. Multicast routing devices use IGMP to learn which groups have members on each of their attached physical
Copyright © 2016, Juniper Networks, Inc.
103
Multicast Protocols Feature Guide for EX4600 Switches networks. IGMP must be enabled for the router to receive IPv4 multicast packets. IGMP is only needed for IPv4 networks, because multicast is handled differently in IPv6 networks.
IGMP is automatically enabled on all IPv4 interfaces on which you configure PIM and on all IPv4 broadcast interfaces when you configure DVMRP.
If IGMP is not running on an interface—either because PIM and DVMRP are not configured on the interface or because IGMP is explicitly disabled on the interface—you can explicitly enable IGMP.
To explicitly enable IGMP:
1.
If PIM and DVMRP are not running on the interface, explicitly enable IGMP by including the interface name.
[edit protocols igmp] user@host# set interface fe-0/0/0.0
2.
See if IGMP is disabled on any interfaces. In the following example, IGMP is disabled on a Gigabit Ethernet interface.
[edit protocols igmp] user@host# show interface fe-0/0/0.0; interface ge-1/0/0.0 { disable;
}
3.
Enable IGMP on the interface by deleting the disable statement.
[edit protocols igmp] delete interface ge-1/0/0.0
4.
Verify the configuration.
[edit protocols igmp] user@host# show interface fe-0/0/0.0; interface ge-1/0/0.0;
5.
Verify the operation of IGMP on the interfaces by checking the output of the show igmp interface command.
Related
Documentation
•
Understanding IGMP on page 100
•
•
show igmp interface on page 455
Changing the IGMP Version
By default, the routing device runs IGMPv2. Routing devices running different versions of
IGMP determine the lowest common version of IGMP that is supported by hosts on their subnet and operate in that version.
104 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
To enable source-specific multicast (SSM) functionality, you must configure version 3 on the host and the host’s directly connected routing device. If a source address is specified in a multicast group that is statically configured, the version must be set to IGMPv3.
If a static multicast group is configured with the source address defined, and the IGMP version is configured to be version 2, the source is ignored and only the group is added.
In this case, the join is treated as an IGMPv2 group join.
If you configure the IGMP version setting at the individual interface hierarchy level, it overrides the interface all statement.
If you have already configured the routing device to use IGMP version 1 (IGMPv1) and then configure it to use IGMPv2, the routing device continues to use IGMPv1 for up to 6 minutes and then uses IGMPv2.
To change to IGMPv3 for SSM functionality:
1.
Configure the IGMP interface.
[edit protocols
] user@host# set
ge-0/0/0
3
2.
Verify the configuration by checking the version field in the output of the show igmp interfaces command. The show igmp statistics command has version-specific output fields, such as V1 Membership Report, V2 Membership Report, and V3 Membership
Report.
CAUTION: On MX Series platforms, IGMPv2 and IGMPv3 cannot be configured together on the same interface. Configuring both together causes unexpected behavior in multicast traffic forwarding.
Related
Documentation
•
Understanding IGMP on page 100
•
show pim interfaces on page 395
•
show igmp statistics on page 459
• RFC 2236, Internet Group Management Protocol, Version 2
• RFC 3376, Internet Group Management Protocol, Version 3
Modifying the IGMP Host-Query Message Interval
The objective of IGMP is to keep routers up to date with group membership of the entire subnet. Routers need not know who all the members are, only that members exist. Each host keeps track of which multicast groups are subscribed to. On each link, one router is elected the querier. The IGMP querier router periodically sends general host-query messages on each attached network to solicit membership information. The messages are sent to the all-systems multicast group address, 224.0.0.1.
Copyright © 2016, Juniper Networks, Inc.
105
Multicast Protocols Feature Guide for EX4600 Switches
The query interval, the response interval, and the robustness variable are related in that they are all variables that are used to calculate the group membership timeout. The group membership timeout is the number of seconds that must pass before a multicast router determines that no more members of a host group exist on a subnet. The group membership timeout is calculated as the (robustness variable x query-interval) +
(query-response-interval). If no reports are received for a particular group before the group membership timeout has expired, the routing device stops forwarding remotely-originated multicast packets for that group onto the attached network.
By default, host-query messages are sent every 125 seconds. You can change this interval to change the number of IGMP messages sent on the subnet.
To modify the query interval:
1.
Configure the interval.
[edit protocols igmp] user@host# set
200
The value can be from 1 through 1024 seconds.
2.
Verify the configuration by checking the IGMP Query Interval field in the output of the show igmp interface command.
3.
Verify the operation of the query interval by checking the Membership Query field in the output of the show igmp statistics command.
Related
Documentation
•
Understanding IGMP on page 100
•
Modifying the IGMP Query Response Interval on page 110
•
Modifying the IGMP Robustness Variable on page 111
•
show igmp interface on page 455
•
show igmp statistics on page 459
Modifying the IGMP Last-Member Query Interval
The last-member query interval is the maximum amount of time between group-specific query messages, including those sent in response to leave-group messages. You can configure this interval to change the amount of time it takes a routing device to detect the loss of the last member of a group.
When the routing device that is serving as the querier receives a leave-group message from a host, the routing device sends multiple group-specific queries to the group being left. The querier sends a specific number of these queries at a specific interval. The number of queries sent is called the last-member query count. The interval at which the queries are sent is called the last-member query interval. Because both settings are configurable, you can adjust the leave latency. The IGMP leave latency is the time between a request to leave a multicast group and the receipt of the last byte of data for the multicast group.
106 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
The last-member query count x (times) the last-member query interval = (equals) the amount of time it takes a routing device to determine that the last member of a group has left the group and to stop forwarding group traffic.
The default last-member query interval is 1 second. You can configure a subsecond interval up to one digit to the right of the decimal point. The configurable range is 0.1
through 0.9, then in 1-second intervals 1 through 999,999.
To modify this interval:
1.
Configure the time (in seconds) that the routing device waits for a report in response to a group-specific query.
[edit protocols
] user@host# set
0.1
2.
Verify the configuration by checking the IGMP Last Member Query Interval field in the output of the show igmp interfaces command.
NOTE: You can configure the last-member query count by configuring the robustness variable. The two are always equal.
Related
Documentation
•
Modifying the IGMP Robustness Variable on page 111
•
show pim interfaces on page 395
Specifying Immediate-Leave Host Removal for IGMP
The immediate leave setting is useful for minimizing the leave latency of IGMP memberships. When this setting is enabled, the routing device leaves the multicast group immediately after the last host leaves the multicast group.
The immediate-leave setting enables host tracking, meaning that the device keeps track of the hosts that send join messages. This allows IGMP to determine when the last host sends a leave message for the multicast group.
When the immediate leave setting is enabled, the device removes an interface from the forwarding-table entry without first sending IGMP group-specific queries to the interface.
The interface is pruned from the multicast tree for the multicast group specified in the
IGMP leave message. The immediate leave setting ensures optimal bandwidth management for hosts on a switched network, even when multiple multicast groups are being used simultaneously.
When immediate leave is disabled and one host sends a leave group message, the routing device first sends a group query to determine if another receiver responds. If no receiver responds, the routing device removes all hosts on the interface from the multicast group.
Immediate leave is disabled by default for both IGMP version 2 and IGMP version 3.
Copyright © 2016, Juniper Networks, Inc.
107
Multicast Protocols Feature Guide for EX4600 Switches
NOTE: Although host tracking is enabled for IGMPv2 and MLDv1 when you enable immediate leave, use immediate leave with these versions only when there is one host on the interface. The reason is that IGMPv2 and MLDv1 use a report suppression mechanism whereby only one host on an interface sends a group join report in response to a membership query. The other interested hosts suppress their reports. The purpose of this mechanism is to avoid a flood of reports for the same group. But it also interferes with host tracking, because the router only knows about the one interested host and does not know about the others.
To enable immediate leave on an interface:
1.
Configure immediate leave on the IGMP interface.
[edit protocols IGMP] user@host# set
ge-0/0/0.1
2.
Verify the configuration by checking the Immediate Leave field in the output of the show igmp interface command.
Related
Documentation
•
Understanding IGMP on page 100
•
show igmp interface on page 455
Filtering Unwanted IGMP Reports at the IGMP Interface Level
Suppose you need to limit the subnets that can join a certain multicast group. The group-policy statement enables you to filter unwanted IGMP reports at the interface level. When this statement is enabled on a router running IGMP version 2 (IGMPv2) or version 3 (IGMPv3), after the router receives an IGMP report, the router compares the group against the specified group policy and performs the action configured in that policy
(for example, rejects the report if the policy matches the defined address or network).
You define the policy to match only IGMP group addresses (for IGMPv2) by using the policy's route-filter statement to match the group address. You define the policy to match
IGMP (source, group) addresses (for IGMPv3) by using the policy's route-filter statement to match the group address and the policy's source-address-filter statement to match the source address.
CAUTION: On MX Series platforms, IGMPv2 and IGMPv3 cannot be configured together on the same interface. Configuring both together causes unexpected behavior in multicast traffic forwarding.
To filter unwanted IGMP reports:
1.
Configure an IGMPv2 policy.
[edit policy-statement reject_policy_v2]
108 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP user@host# set from route-filter 224.1.1.1/32 exact user@host# set from route-filter 239.0.0.0/8 orlonger user@host# set then reject
2.
Configure an IGMPv3 policy.
[edit policy-statement reject_policy_v3] user@host# set from route-filter 224.1.1.1/32 exact user@host# set from route-filter 239.0.0.0/8 orlonger user@host# set from source-address-filter 10.0.0.0/8 orlonger user@host# set from source-address-filter 127.0.0.0/8 orlonger user@host# set then reject
3.
Apply the policies to the IGMP interfaces on which you prefer not to receive specific group or (source, group) reports. In this example, ge-0/0/0.1 is running IGMPv2, and ge-0/1/1.0
is running IGMPv3.
[edit protocols igmp] user@host# set
ge-0/0/0.1
reject_policy_v2 user@host# set
ge-0/1/1.0
reject_policy_v3
4.
Verify the operation of the filter by checking the Rejected Report field in the output of the show igmp statistics command.
Related
Documentation
•
Understanding IGMP on page 100
• Example: Configuring Policy Chains and Route Filters
•
show igmp statistics on page 459
Accepting IGMP Messages from Remote Subnetworks
By default, IGMP interfaces accept IGMP messages only from the same subnet. Including the promiscuous-mode statement enables the routing device to accept IGMP messages from indirectly connected subnets.
NOTE: When you enable IGMP on an unnumbered Ethernet interface that uses a /32 loopback address as a donor address, you must configure IGMP promiscuous mode to accept the IGMP packets received on this interface.
NOTE: When enabling promiscuous-mode, all routers on the ethernet segment must be configured with the promiscuous mode statement.
Otherwise, only the interface configured with lowest IPv4 address acts as the querier for IGMP for this Ethernet segment.
To enable IGMP promiscuous mode on an interface:
1.
Configure the IGMP interface.
[edit protocols
] user@host# set
ge-0/1/1.0
Copyright © 2016, Juniper Networks, Inc.
109
Multicast Protocols Feature Guide for EX4600 Switches
2.
Verify the configuration by checking the Promiscuous Mode field in the output of the show igmp interface command.
3.
Verify the operation of the filter by checking the Rx non-local field in the output of the show igmp statistics command.
Related
Documentation
•
Understanding IGMP on page 100
• Configuring the Loopback Interface in the Junos OS Network Interfaces Library for Routing
Devices
•
show igmp interface on page 455
•
show igmp statistics on page 459
Modifying the IGMP Query Response Interval
The query response interval is the maximum amount of time that can elapse between when the querier router sends a host-query message and when it receives a response from a host. Configuring this interval allows you to adjust the burst peaks of IGMP messages on the subnet. Set a larger interval to make the traffic less bursty. Bursty traffic refers to an uneven pattern of data transmission: sometimes a very high data transmission rate, whereas at other times a very low data transmission rate.
The query response interval, the host-query interval, and the robustness variable are related in that they are all variables that are used to calculate the group membership timeout. The group membership timeout is the number of seconds that must pass before a multicast router determines that no more members of a host group exist on a subnet.
The group membership timeout is calculated as the (robustness variable x query-interval)
+ (query-response-interval). If no reports are received for a particular group before the group membership timeout has expired, the routing device stops forwarding remotely originated multicast packets for that group onto the attached network.
The default query response interval is 10 seconds. You can configure a subsecond interval up to one digit to the right of the decimal point. The configurable range is 0.1 through 0.9, then in 1-second intervals 1 through 999,999.
To modify the query response interval:
1.
Configure the interval.
[edit protocols igmp] user@host# set
0.4
2.
Verify the configuration by checking the IGMP Query Response Interval field in the output of the show igmp interface command.
3.
Verify the operation of the query interval by checking the Membership Query field in the output of the show igmp statistics command.
Related
Documentation
•
Understanding IGMP on page 100
•
Modifying the IGMP Host-Query Message Interval on page 105
110 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
•
Modifying the IGMP Robustness Variable on page 111
•
show igmp interface on page 455
•
show igmp statistics on page 459
Modifying the IGMP Robustness Variable
Fine-tune the IGMP robustness variable to allow for expected packet loss on a subnet.
The robust count automatically changes certain IGMP message intervals for IGMPv2 and
IGMPv3. Increasing the robust count allows for more packet loss but increases the leave latency of the subnetwork.
When the query router receives an IGMP leave message on a shared network running
IGMPv2, the query router must send an IGMP group query message a specified number of times. The number of IGMP group query messages sent is determined by the robust count.
The value of the robustness variable is also used in calculating the following IGMP message intervals:
• Group member interval—Amount of time that must pass before a multicast router determines that there are no more members of a group on a network. This interval is calculated as follows: (robustness variable x query-interval) + (1 x query-response-interval).
• Other querier present interval—The robust count is used to calculate the amount of time that must pass before a multicast router determines that there is no longer another multicast router that is the querier. This interval is calculated as follows: (robustness variable x query-interval) + (0.5 x query-response-interval).
• Last-member query count—Number of group-specific queries sent before the router assumes there are no local members of a group. The number of queries is equal to the value of the robustness variable.
In IGMPv3, a change of interface state causes the system to immediately transmit a state-change report from that interface. In case the state-change report is missed by one or more multicast routers, it is retransmitted. The number of times it is retransmitted is the robust count minus one. In IGMPv3, the robust count is also a factor in determining the group membership interval, the older version querier interval, and the other querier present interval.
By default, the robustness variable is set to 2. You might want to increase this value if you expect a subnet to lose packets.
The number can be from 2 through 10.
To change the value of the robustness variable:
1.
Configure the robust count.
When you set the robust count, you are in effect configuring the number of times the querier retries queries on the connected subnets.
Copyright © 2016, Juniper Networks, Inc.
111
Multicast Protocols Feature Guide for EX4600 Switches
[edit protocols
] user@host# set
5
2.
Verify the configuration by checking the IGMP Robustness Count field in the output of the show igmp interfaces command.
Related
Documentation
•
Modifying the IGMP Host-Query Message Interval on page 105
•
Modifying the IGMP Query Response Interval on page 110
•
Modifying the IGMP Last-Member Query Interval on page 106
•
show pim interfaces on page 395
• RFC 2236, Internet Group Management Protocol, Version 2
• RFC 3376, Internet Group Management Protocol, Version 3
Limiting the Maximum IGMP Message Rate
This section describes how to change the limit for the maximum number of IGMP packets transmitted in 1 second by the router.
Increasing the maximum number of IGMP packets transmitted per second might be useful on a router with a large number of interfaces participating in IGMP.
To change the limit for the maximum number of IGMP packets the router can transmit in 1 second, include the maximum-transmit-rate statement and specify the maximum number of packets per second to be transmitted.
Related
Documentation
•
maximum-transmit-rate (Protocols IGMP) on page 269
Enabling IGMP Static Group Membership
You can create IGMP static group membership to test multicast forwarding without a receiver host. When you enable IGMP static group membership, data is forwarded to an interface without that interface receiving membership reports from downstream hosts.
The router on which you enable static IGMP group membership must be the designated router (DR) for the subnet. Otherwise, traffic does not flow downstream.
When enabling IGMP static group membership, you cannot configure multiple groups using the group-count, group-increment, source-count, and source-increment statements if the all option is specified as the IGMP interface.
Class-of-service (CoS) adjustment is not supported with IGMP static group membership.
In this example, you create static group 225.1.1.1.
1.
On the DR, configure the static groups to be created by including the static statement and group statement and specifying which IP multicast address of the group to be created. When creating groups individually, you must specify a unique address for each group.
112 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
[edit protocols
] user@host# set interface fe-0/1/2
225.1.1.1
2.
After you commit the configuration, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@host> show configuration protocol igmp interface fe-0/1/2.0 { static { group 225.1.1.1 ;
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show igmp group command to verify that static group 225.1.1.1 has been created.
user@host> show igmp group
Interface: fe-0/1/2
Group: 225.1.1.1
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
NOTE: When you configure static IGMP group entries on point-to-point links that connect routing devices to a rendezvous point (RP), the static IGMP group entries do not generate join messages toward the RP.
When you create IGMP static group membership to test multicast forwarding on an interface on which you want to receive multicast traffic, you can specify that a number of static groups be automatically created. This is useful when you want to test forwarding to multiple receivers without having to configure each receiver separately.
In this example, you create three groups.
1.
On the DR, configure the number of static groups to be created by including the group-count statement and specifying the number of groups to be created.
[edit protocols
] user@host# set interface fe-0/1/2
225.1.1.1
3
2.
After you commit the configuration, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@host> show configuration protocol igmp interface fe-0/1/2.0 { static { group 225.1.1.1 { group-count 3;
}
}
}
Copyright © 2016, Juniper Networks, Inc.
113
Multicast Protocols Feature Guide for EX4600 Switches
114
3.
After you have committed the configuration and after the source is sending traffic, use the show igmp group command to verify that static groups 225.1.1.1, 225.1.1.2, and
225.1.1.3 have been created.
user@host> show igmp group
Interface: fe-0/1/2
Group: 225.1.1.1
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.2
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.3
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
When you create IGMP static group membership to test multicast forwarding on an interface on which you want to receive multicast traffic, you can also configure the group address to be automatically incremented for each group created. This is useful when you want to test forwarding to multiple receivers without having to configure each receiver separately and when you do not want the group addresses to be sequential.
In this example, you create three groups and increase the group address by an increment of two for each group.
1.
On the DR, configure the group address increment by including the group-increment statement and specifying the number by which the address should be incremented for each group. The increment is specified in dotted decimal notation similar to an
IPv4 address.
[edit protocols
] user@host# set interface fe-0/1/2
225.1.1.1
3
0.0.0.2
2.
After you commit the configuration, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@host> show configuration protocol igmp interface fe-0/1/2.0 { version 3; static { group 225.1.1.1 { group-increment 0.0.0.2; group-count 3;
}
}
}
3.
After you have committed the configuration and after the source is sending traffic, use the show igmp group command to verify that static groups 225.1.1.1, 225.1.1.3, and
225.1.1.5 have been created.
user@host> show igmp group
Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
Interface: fe-0/1/2
Group: 225.1.1.1
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.3
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.5
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
When you create IGMP static group membership to test multicast forwarding on an interface on which you want to receive multicast traffic, and your network is operating in source-specific multicast (SSM) mode, you can also specify that the multicast source address be accepted. This is useful when you want to test forwarding to multicast receivers from a specific multicast source.
If you specify a group address in the SSM range, you must also specify a source.
If a source address is specified in a multicast group that is statically configured, the IGMP version on the interface must be set to IGMPv3. IGMPv2 is the default value.
In this example, you create group 225.1.1.1 and accept IP address 10.0.0.2 as the only source.
1.
On the DR, configure the source address by including the source statement and specifying the IPv4 address of the source host.
[edit protocols
] user@host# set interface fe-0/1/2
225.1.1.1
10.0.0.2
2.
After you commit the configuration, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@host> show configuration protocol igmp interface fe-0/1/2.0 { version 3; static { group 225.1.1.1 { source 10.0.0.2;
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show igmp group command to verify that static group 225.1.1.1 has been created and that source 10.0.0.2 has been accepted.
user@host> show igmp group
Interface: fe-0/1/2
Group: 225.1.1.1
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Copyright © 2016, Juniper Networks, Inc.
115
Multicast Protocols Feature Guide for EX4600 Switches
When you create IGMP static group membership to test multicast forwarding on an interface on which you want to receive multicast traffic, you can specify that a number of multicast sources be automatically accepted. This is useful when you want to test forwarding to multicast receivers from more than one specified multicast source.
In this example, you create group 255.1.1.1 and accept addresses 10.0.0.2, 10.0.0.3, and
10.0.0.4 as the sources.
1.
On the DR, configure the number of multicast source addresses to be accepted by including the source-count statement and specifying the number of sources to be accepted.
[edit protocols
] user@host# set interface fe-0/1/2
225.1.1.1
10.0.0.2
3
2.
After you commit the configuration, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@host> show configuration protocol igmp interface fe-0/1/2.0 { version 3; static { group 225.1.1.1 { source 10.0.0.2 { source-count 3;
}
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show igmp group command to verify that static group 225.1.1.1 has been created and that sources 10.0.0.2, 10.0.0.3, and 10.0.0.4 have been accepted.
user@host> show igmp group
Interface: fe-0/1/2
Group: 225.1.1.1
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.1
Source: 10.0.0.3
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.1
Source: 10.0.0.4
Last reported by: Local
Timeout: 0 Type: Static
116 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
When you configure static groups on an interface on which you want to receive multicast traffic, and specify that a number of multicast sources be automatically accepted, you can also specify the number by which the address should be incremented for each source accepted. This is useful when you want to test forwarding to multiple receivers without having to configure each receiver separately and you do not want the source addresses to be sequential.
In this example, you create group 225.1.1.1 and accept addresses 10.0.0.2, 10.0.0.4, and
10.0.0.6 as the sources.
1.
Configure the multicast source address increment by including the source-increment statement and specifying the number by which the address should be incremented for each source. The increment is specified in dotted decimal notation similar to an
IPv4 address.
[edit protocols
] user@host# set interface fe-0/1/2
225.1.1.1
10.0.0.2
3
0.0.0.2
2.
After you commit the configuration, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@host> show configuration protocol igmp interface fe-0/1/2.0 { version 3; static { group 225.1.1.1 { source 10.0.0.2 { source-count 3; source-increment 0.0.0.2;
}
}
}
}
3.
After you have committed the configuration and after the source is sending traffic, use the show igmp group command to verify that static group 225.1.1.1 has been created and that sources 10.0.0.2, 10.0.0.4, and 10.0.0.6 have been accepted.
user@host> show igmp group
Interface: fe-0/1/2
Group: 225.1.1.1
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.1
Source: 10.0.0.4
Last reported by: Local
Timeout: 0 Type: Static
Group: 225.1.1.1
Source: 10.0.0.6
Last reported by: Local
Timeout: 0 Type: Static
Copyright © 2016, Juniper Networks, Inc.
117
Multicast Protocols Feature Guide for EX4600 Switches
118
When you configure static groups on an interface on which you want to receive multicast traffic and your network is operating in source-specific multicast (SSM) mode, you can specify that certain multicast source addresses be excluded.
By default the multicast source address configured in a static group operates in include mode. In include mode the multicast traffic for the group is accepted from the source address configured. You can also configure the static group to operate in exclude mode.
In exclude mode the multicast traffic for the group is accepted from any address other than the source address configured.
If a source address is specified in a multicast group that is statically configured, the IGMP version on the interface must be set to IGMPv3. IGMPv2 is the default value.
In this example, you exclude address 10.0.0.2 as a source for group 225.1.1.1.
1.
On the DR, configure a multicast static group to operate in exclude mode by including the exclude statement and specifying which IPv4 source address to exclude.
[edit protocols
] user@host# set interface fe-0/1/2
225.1.1.1 exclude
10.0.0.2
2.
After you commit the configuration, use the show configuration protocol igmp command to verify the IGMP protocol configuration.
user@host> show configuration protocol igmp interface fe-0/1/2.0 { version 3; static { group 225.1.1.1 { exclude; source 10.0.0.2;
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show igmp group detail command to verify that static group 225.1.1.1 has been created and that the static group is operating in exclude mode.
user@host> show igmp group detail
Interface: fe-0/1/2
Group: 225.1.1.1
Group mode: Exclude
Source: 10.0.0.2
Last reported by: Local
Timeout: 0 Type: Static
Related
Documentation
•
Enabling MLD Static Group Membership on page 151
•
group (Protocols IGMP) on page 261
•
group-count (Protocols IGMP) on page 262
•
group-increment (Protocols IGMP) on page 262
•
source-count (Protocols IGMP) on page 277
Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
•
source-increment (Protocols IGMP) on page 278
•
static (Protocols IGMP) on page 279
Recording IGMP Join and Leave Events
To determine whether IGMP tuning is needed in a network, you can configure the routing device to record IGMP join and leave events. You can record events globally for the routing device or for individual interfaces.
describes the recordable IGMP events.
Table 5: IGMP Event Messages
ERRMSG Tag Definition
RPD_IGMP_JOIN
RPD_IGMP_LEAVE
RPD_IGMP_ACCOUNTING_ON
RPD_IGMP_ACCOUNTING_OFF
RPD_IGMP_MEMBERSHIP_TIMEOUT
Records IGMP join events.
Records IGMP leave events.
Records when IGMP accounting is enabled on an IGMP interface.
Records when IGMP accounting is disabled on an IGMP interface.
Records IGMP membership timeout events.
To enable IGMP accounting:
1.
Enable accounting globally or on an IGMP interface. This example shows both options.
[edit protocols
] user@host# set
user@host# set
fe-0/1/0.2
2.
Configure the events to be recorded and filter the events to a system log file with a descriptive filename, such as igmp-events.
[edit system syslog file igmp-events] user@host# set any info user@host# set match “.*RPD_IGMP_JOIN.* | .*RPD_IGMP_LEAVE.* |
.*RPD_IGMP_ACCOUNTING.* | .*RPD_IGMP_MEMBERSHIP_TIMEOUT.*”
3.
Periodically archive the log file.
This example rotates the file size when it reaches 100 KB and keeps three files.
[edit system syslog file igmp-events] user@host# set archive size 100000 user@host# set archive files 3 user@host# set archive archive-sites “ftp://user@host1//var/tmp” password
“anonymous” user@host# set archive archive-sites “ftp://user@host2//var/tmp” password “test” user@host# set archive transfer-interval 24 user@host# set archive start-time 2011-01-07:12:30
Copyright © 2016, Juniper Networks, Inc.
119
Multicast Protocols Feature Guide for EX4600 Switches
4.
You can monitor the system log file as entries are added to the file by running the monitor start and monitor stop commands.
user@host> monitor start igmp-events
*** igmp-events ***
Apr 16 13:08:23 host mgd[16416]: UI_CMDLINE_READ_LINE: User 'user', command
'run monitor start igmp-events ' monitor
Related
Documentation
•
Understanding IGMP on page 100
• Specifying Log File Size, Number, and Archiving Properties
Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces
The group-limit statement enables you to limit the number of IGMP multicast group joins for logical interfaces. When this statement is enabled on a router running IGMP version 2
(IGMPv2) or version 3 (IGMPv3), the limit is applied upon receipt of the group report.
Once the group limit is reached, subsequent join requests are rejected.
When configuring limits for IGMP multicast groups, keep the following in mind:
• Each any-source group (*,G) counts as one group toward the limit.
• Each source-specific group (S,G) counts as one group toward the limit.
• Groups in IGMPv3 exclude mode are counted toward the limit.
• Multiple source-specific groups count individually toward the group limit, even if they are for the same group. For example, (S1, G1) and (S2, G1) would count as two groups toward the configured limit.
• Combinations of any-source groups and source-specific groups count individually toward the group limit, even if they are for the same group. For example, (*, G1) and
(S, G1) would count as two groups toward the configured limit.
• Configuring and committing a group limit on a network that is lower than what already exists on the network results in the removal of all groups from the configuration. The groups must then request to rejoin the network (up to the newly configured group limit).
• You can dynamically limit multicast groups on IGMP logical interfaces using dynamic profiles.
Beginning with Junos OS 12.2, you can optionally configure a system log warning threshold for IGMP multicast group joins received on the logical interface. It is helpful to review the system log messages for troubleshooting purposes and to detect if an excessive amount of IGMP multicast group joins have been received on the interface. These log messages convey when the configured group limit has been exceeded, when the configured threshold has been exceeded, and when the number of groups drop below the configured threshold.
The group-threshold statement enables you to configure the threshold at which a warning message is logged. The range is 1 through 100 percent. The warning threshold is a
120 Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP percentage of the group limit, so you must configure the group-limit statement to configure a warning threshold. For instance, when the number of groups exceed the configured warning threshold, but remain below the configured group limit, multicast groups continue to be accepted, and the device logs the warning message. In addition, the device logs a warning message after the number of groups drop below the configured warning threshold.
You can further specify the amount of time (in seconds) between the log messages by configuring the log-interval statement. The range is 6 through 32,767 seconds.
You might consider throttling log messages because every entry added after the configured threshold and every entry rejected after the configured limit causes a warning message to be logged. By configuring a log interval, you can throttle the amount of system log warning messages generated for IGMP multicast group joins.
To limit multicast group joins on an IGMP logical interface:
1.
Access the logical interface at the IGMP protocol hierarchy level.
[edit] user@host# edit protocols igmp interface interface-name
2.
Specify the group limit for the interface.
[edit protocols igmp interface interface-name] user@host# set
limit
3.
(Optional) Configure the threshold at which a warning message is logged.
[edit protocols igmp interface interface-name] user@host# set group-threshold value
4.
(Optional) Configure the amount of time between log messages.
[edit protocols igmp interface interface-name] user@host# set log-interval seconds
To confirm your configuration, use the show protocols igmp command. To verify the operation of IGMP on the interface, including the configured group limit and the optional warning threshold and interval between log messages, use the
command.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
Tracing IGMP Protocol Traffic
Tracing operations record detailed messages about the operation of routing protocols, such as the various types of routing protocol packets sent and received, and routing policy actions. You can specify which trace operations are logged by including specific tracing flags. The following table describes the flags that you can include.
Flag all client-notification
Description
Trace all operations.
Trace notifications.
Copyright © 2016, Juniper Networks, Inc.
121
Multicast Protocols Feature Guide for EX4600 Switches
122
Flag general report route state task timer group host-notification leave mtrace normal packets policy query
Description
Trace general flow.
Trace group operations.
Trace host notifications.
Trace leave group messages (IGMPv2 only).
Trace mtrace packets. Use the mtrace command to troubleshoot the software.
Trace normal events.
Trace all IGMP packets.
Trace policy processing.
Trace IGMP membership query messages, including general and group-specific queries.
Trace membership report messages.
Trace routing information.
Trace state transitions.
Trace task processing.
Trace timer processing.
In the following example, tracing is enabled for all routing protocol packets. Then tracing is narrowed to focus only on IGMP packets of a particular type. To configure tracing operations for IGMP:
1.
(Optional) Configure tracing at the routing options level to trace all protocol packets.
[edit routing-options traceoptions] user@host# set file all-packets-trace user@host# set flag all
2.
Configure the filename for the IGMP trace file.
[edit protocols igmp
] user@host# set file igmp-trace
3.
(Optional) Configure the maximum number of trace files.
[edit protocols igmp
] user@host# set file files 5
4.
(Optional) Configure the maximum size of each trace file.
Copyright © 2016, Juniper Networks, Inc.
Chapter 9: Using IGMP
[edit protocols igmp
] user@host# set file size 1m
5.
(Optional) Enable unrestricted file access.
[edit protocols igmp
] user@host# set file world-readable
6.
Configure tracing flags. Suppose you are troubleshooting issues with a particular multicast group. The following example shows how to flag all events for packets associated with the group IP address.
[edit protocols igmp
] user@host# set flag group | match 232.1.1.2
7.
View the trace file.
user@host> file list /var/log user@host> file show /var/log/igmp-trace
Related
Documentation
•
Understanding IGMP on page 100
• Tracing and Logging Junos OS Operations
•
Disabling IGMP
To disable IGMP on an interface, include the disable statement:
You can include this statement at the following hierarchy levels:
• [edit protocols igmp interface interface-name]
• [edit logical-systems logical-system-name protocols igmp interface interface-name]
Related
Documentation
•
Copyright © 2016, Juniper Networks, Inc.
123
Multicast Protocols Feature Guide for EX4600 Switches
124 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 10
Using IGMP Snooping
•
IGMP Snooping Overview on page 125
•
Configuring IGMP Snooping on page 128
•
Configuring VLAN-Specific IGMP Snooping Parameters on page 129
•
Example: Configuring IGMP Snooping on page 130
•
Using a Switch as an IGMP Querier on page 132
•
Monitoring IGMP Snooping on page 133
•
Verifying the IGMP Snooping Group Timeout Value on page 134
IGMP Snooping Overview
With IGMP snooping enabled, a switch monitors the IGMP (Internet Group Management
Protocol) traffic between hosts and multicast routers and uses what it learns to forward multicast traffic to only the downstream interfaces that are connected to interested receivers. This conserves bandwidth by allowing the switch to send multicast traffic to only those interfaces that are connected to devices that want to receive the traffic
(instead of flooding the traffic to all the downstream VLAN interfaces).
This IGMP snooping topic includes:
•
How IGMP Snooping Works on page 125
•
How IGMP Snooping Works with Routed VLAN Interfaces on page 126
•
How Hosts Join and Leave Multicast Groups on page 126
•
IGMP Snooping and Forwarding Interfaces on page 127
•
General Forwarding Rules on page 127
How IGMP Snooping Works
A switch usually learns unicast MAC addresses by checking the source address field of the frames it receives and then sends any traffic for that unicast address only to the appropriate interface. However, a multicast MAC address can never be the source address for a packet. As a result, when a switch receives traffic for a multicast destination address, it floods the traffic on the relevant VLAN, which can cause a significant amount of traffic to be sent unnecessarily.
Copyright © 2016, Juniper Networks, Inc.
125
Multicast Protocols Feature Guide for EX4600 Switches
IGMP snooping prevents this flooding. When you enable IGMP snooping, the switch monitors IGMP packets between receivers and multicast routers and uses the content of the packets to build a multicast cache table—a database of multicast groups and the interfaces that are connected to members of the groups. When the switch receives multicast packets, it uses the cache table to selectively forward the traffic to only the interfaces that are connected to members of the appropriate multicast groups.
NOTE: IGMP snooping is enabled by default on the default VLAN only. With versions of Junos OS for the QFX Series previous to 13.2, IGMP snooping is enabled by default on all VLANs.
NOTE: You cannot configure IGMP snooping on a secondary (private) VLAN.
How IGMP Snooping Works with Routed VLAN Interfaces
A switch can use a routed VLAN interface (RVI) to forward traffic between VLANs that connect to it. IGMP snooping works with Layer 2 interfaces and RVIs to forward multicast traffic in a switched network.
When a switch receives a multicast packet, its Packet Forwarding Engines perform a multicast lookup on the packet to determine how to forward the packet to its local interfaces. From the results of the lookup, each Packet Forwarding Engine extracts a list of Layer 3 interfaces that have ports local to the Packet Forwarding Engine. If the list includes an RVI, the switch provides a bridge multicast group ID for the RVI to the Packet
Forwarding Engine.
For VLANs that include multicast receivers, the bridge multicast ID includes a sub-next-hop
ID, which identifies the Layer 2 interfaces in the VLAN that are interested in receiving the multicast stream. The Packet Forwarding Engine then forwards multicast traffic to bridge multicast IDs that have multicast receivers for a given multicast group.
How Hosts Join and Leave Multicast Groups
Hosts can join multicast groups in two ways:
• By sending an unsolicited IGMP join message to a multicast router that specifies the
IP multicast group that the host is attempting to join.
• By sending an IGMP join message in response to a general query from a multicast router.
A multicast router continues to forward multicast traffic to a VLAN provided that at least one host on that VLAN responds to the periodic general IGMP queries. For a host to remain a member of a multicast group, therefore, it must continue to respond to the periodic general IGMP queries.
126 Copyright © 2016, Juniper Networks, Inc.
Chapter 10: Using IGMP Snooping
To leave a multicast group, either a host cannot respond to the periodic general IGMP queries, which results in a “silent leave” (the only leave option for IGMPv1), or a host can send a group-specific IGMPv2 leave message.
IGMP Snooping and Forwarding Interfaces
To determine how to forward multicast traffic, a switch with IGMP snooping enabled maintains information about the following interfaces in its multicast forwarding table:
• Multicast-router interfaces—These interfaces lead toward multicast routers or IGMP queriers.
• Group-member interfaces—These interfaces lead toward hosts that are members of multicast groups.
The switch learns about these interfaces by monitoring IGMP traffic. If an interface receives IGMP queries or Protocol Independent Multicast (PIM) updates, the switch adds the interface to its multicast forwarding table as a multicast-router interface. If an interface receives membership reports for a multicast group, the switch adds the interface to its multicast forwarding table as a group-member interface.
Table entries for interfaces that the switch learns about are subject to aging. For example, if a learned multicast-router interface does not receive IGMP queries or PIM hellos within a certain interval, the switch removes the entry for that interface from its multicast forwarding table.
NOTE: For a switch to learn multicast-router interfaces and group-member interfaces, an IGMP querier must exist in the network. This is often a multicast router, but if there is no multicast router on the local network, you can configure the switch itself to be an IGMP querier.
You can statically configure an interface to be a multicast-router interface or a group-member interface. The switch adds a static interface to its multicast forwarding table without having to learn about the interface, and the entry in the table is not subject to aging. You can have a mix of statically configured and dynamically learned interfaces on a switch.
General Forwarding Rules
Multicast traffic received on a switch interface in a VLAN on which IGMP snooping is enabled is forwarded according to the following rules.
IGMP traffic is forwarded as follows:
• IGMP general queries received on a multicast-router interface are forwarded to all other interfaces in the VLAN.
• IGMP group-specific queries received on a multicast-router interface are forwarded to only those interfaces in the VLAN that are members of the group.
• IGMP reports received on a host interface are forwarded to multicast-router interfaces in the same VLAN, but not to the other host interfaces in the VLAN.
Copyright © 2016, Juniper Networks, Inc.
127
Multicast Protocols Feature Guide for EX4600 Switches
Multicast traffic that is not IGMP traffic is forwarded as follows:
• A multicast packet with a destination address of 224.0.0.0/24 is flooded to all other interfaces on the VLAN.
• An unregistered multicast packet—that is, a packet for a group that has no current members—is forwarded to all multicast-router interfaces in the VLAN.
• A registered multicast packet is forwarded only to those host interfaces in the VLAN that are members of the multicast group and to all multicast-router interfaces in the
VLAN.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
•
Monitoring IGMP Snooping on page 133
•
• RFC 3171, IANA Guidelines for IPv4 Multicast Address Assignments
• IGMPv1—See RFC 1112, Host extensions for IP multicasting.
• IGMPv2—See RFC 2236, Internet Group Management Protocol, Version 2.
• IGMPv3—See RFC 3376, Internet Group Management Protocol, Version 3.
Configuring IGMP Snooping
With IGMP snooping enabled, a switch monitors the IGMP (Internet Group Management
Protocol) traffic between hosts and multicast routers and uses what it learns to forward multicast traffic to only the downstream interfaces that are connected to interested receivers. This conserves bandwidth by allowing the switch to send multicast traffic to only those interfaces that are connected to devices that want to receive the traffic
(instead of flooding the traffic to all the downstream VLAN interfaces).
NOTE: You cannot configure IGMP snooping on a secondary VLAN.
To enable IGMP snooping and configure individual options as needed for your network by using the CLI:
1.
Enable IGMP snooping on a VLAN:
2.
[edit protocols] user@switch# set igmp-snooping vlan employee-vlan
Configure the switch to immediately remove group membership from interfaces on a VLAN when it receives a leave message through that VLAN, and have it not forward any membership queries for the multicast group to the VLAN (IGMPv2 only):
3.
[edit protocols] user@switch# set igmp-snooping vlan vlan-name immediate-leave
Configure an interface to belong to a multicast group:
128 Copyright © 2016, Juniper Networks, Inc.
Chapter 10: Using IGMP Snooping
4.
[edit protocols] user@switch# set igmp-snooping vlan-name interface interface-name
group group-address
Configure an interface to forward IGMP queries received from multicast routers.
5.
[edit protocols] user@switch# set igmp-snooping vlan vlan-name interface interface-name
Configure the switch to wait for four timeout intervals before timing out a multicast group on a VLAN:
6.
[edit protocols] user@switch# set igmp-snooping vlan vlan-name
4
If you want a standalone switch to act as an IGMP querier, enter the following:
[edit protocols] user@switch# set igmp-snooping vlan vlan-name
source address
The switch uses the address that you configure as the source address in the IGMP queries that it sends. If there are any multicast routers on the same local network, make sure the source address for the IGMP querier is greater (a higher number) than the IP addresses for those routers on the network. This ensures that switch is always the IGMP querier on the network.
Related
Documentation
•
IGMP Snooping Overview on page 125
•
Example: Configuring IGMP Snooping on page 130
•
Monitoring IGMP Snooping on page 133
Configuring VLAN-Specific IGMP Snooping Parameters
All of the IGMP snooping statements configured with the igmp-snooping statement, with the exception of the traceoptions statement, can be qualified with the same statement at the VLAN level. To configure IGMP snooping parameters at the VLAN level, include the vlan statement: vlan vlan-id;
interface-name {
limit;
multicast-router-interface; static {
}
} proxy {
ip-address;
} group ip-address { source ip-address;
}
seconds;
seconds;
seconds; robust-count number;
Copyright © 2016, Juniper Networks, Inc.
129
Multicast Protocols Feature Guide for EX4600 Switches
}
You can include this statement at the following hierarchy levels:
• [edit bridge-domains bridge-domain-name protocols igmp-snooping]
• [edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping]
Related
Documentation
• Multicast Overview
• Understanding Multicast Snooping
Example: Configuring IGMP Snooping
With IGMP snooping enabled, a switch monitors the IGMP (Internet Group Management
Protocol) traffic between hosts and multicast routers and uses what it learns to forward multicast traffic to only the downstream interfaces that are connected to interested receivers. This conserves bandwidth by allowing the switch to send multicast traffic to only those interfaces that are connected to devices that want to receive the traffic
(instead of flooding the traffic to all the downstream VLAN interfaces).
This example describes how to configure IGMP snooping:
•
•
Overview and Topology on page 130
•
Requirements
This example requires Junos OS Release 11.1 or later on a QFX Series product.
Before you configure IGMP snooping, be sure you have:
• Configured the employee-vlan VLAN
• Assigned interfaces ge-0/0/1, ge-0/0/2, and ge-0/0/3 to employee-vlan
Overview and Topology
In this example you configure an interface to receive multicast traffic from a source and configure some multicast-related behavior for downstream interfaces. The example assumes that IGMP snooping was previously disabled for the VLAN.
shows the components of the topology for this example.
Table 6: Components of the IGMP Snooping Topology
Components Settings
VLAN name
Interfaces in employee-vlan employee-vlan , tag 20 ge-0/0/1 , ge-0/0/2 , ge-0/0/3
130 Copyright © 2016, Juniper Networks, Inc.
Chapter 10: Using IGMP Snooping
Table 6: Components of the IGMP Snooping Topology (continued)
Components Settings
Multicast IP address for employee-vlan 225.100.100.100
Configuration
CLI Quick
Configuration
Step-by-Step
Procedure
To configure basic IGMP snooping on a switch:
To quickly configure IGMP snooping, copy the following commands and paste them into a terminal window:
[edit protocols] set igmp-snooping vlan employee-vlan set igmp-snooping vlan employee-vlan interface ge-0/0/3 static group 225.100.100.100
set igmp-snooping vlan employee-vlan interface ge-0/0/2 multicast-router-interface set igmp-snooping vlan employee-vlan robust-count 4
Configure IGMP snooping:
1.
2.
3.
4.
Enable and configure IGMP snooping on the VLAN employee-vlan:
[edit protocols] user@switch# set igmp-snooping vlan employee-vlan
Configure a interface to belong to a multicast group:
[edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/3
group
225.100.100.100
Configure an interface to forward IGMP queries received from multicast routers.
[edit protocols] user@switch# set igmp-snooping vlan employee-vlan interface ge-0/0/2
Configure the switch to wait for four timeout intervals before timing out a multicast group on a VLAN:
[edit protocols] user@switch# set igmp-snooping vlan employee-vlan
4
Results Check the results of the configuration: user@switch# show protocols igmp-snooping vlan employee-vlan { robust-count 4;
} interface ge-0/0/2 { multicast-router-interface;
} interface ge-0/0/3 { static { group 255.100.100.100;
}
}
}
Copyright © 2016, Juniper Networks, Inc.
131
Multicast Protocols Feature Guide for EX4600 Switches
Related
Documentation
•
IGMP Snooping Overview on page 125
•
Configuring IGMP Snooping on page 128
• Changing the IGMP Snooping Group Timeout Value
•
Monitoring IGMP Snooping on page 133
• Example: Setting Up Bridging with Multiple VLANs.
Using a Switch as an IGMP Querier
If IGMP snooping is enabled on a pure Layer 2 a local network (that is, Layer 3 is not enabled on the network), and there is not multicast router in the network, multicast traffic might not be properly forwarded through the network. This problem occurs if the local network is configured such that multicast traffic must be forwarded between switches in order to reach a multicast receiver. In this case, an upstream switch does not forward multicast traffic to a downstream switch (and therefore to the multicast receivers attached to the downstream switch) because the downstream switch does not forward
IGMP reports to the upstream switch. You can solve this problem by configuring one of the switches to be an IGMP querier. This switch sends periodic general query packets to all the switches in the network, which ensures that the snooping membership tables are updated and prevents any multicast traffic loss.
If you configure multiple switches to be IGMP queriers, the switch with the lowest
(smallest) IGMP querier source address takes precedence and acts as the querier.
Switches with higher IGMP querier source addresses stop sending IGMP queries unless they do not receive IGMP queries for 255 seconds. If a switch with a higher IGMP querier source address does not receive any IGMP queries during that period, it starts sending queries again.
NOTE: The igmp-querier statement is supported on QFabric systems in Junos
OS 14.1X53-D15 but is not supported in Junos OS 15.1.
To configure a standalone switch to act as an IGMP querier, enter the following:
[edit protocols] user@switch# set igmp-snooping vlan vlan-name
source address
To configure a QFabric Node device to act as an IGMP querier, enter the following:
[edit protocols] user@switch# set igmp-snooping vlan vlan-name
source address
Related
Documentation
•
IGMP Snooping Overview on page 125
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
• Changing the IGMP Snooping Group Timeout Value
•
Monitoring IGMP Snooping on page 133
132 Copyright © 2016, Juniper Networks, Inc.
Chapter 10: Using IGMP Snooping
Monitoring IGMP Snooping
Purpose Use the monitoring feature to view status and information about the IGMP snooping configuration.
Action To display IGMP snooping details in the CLI, enter the following commands:
• show igmp-snooping vlans
• show igmp-snooping statistics
• show igmp-snooping route
• show igmp-snooping membership
Meaning
summarizes the IGMP snooping details displayed.
Table 7: Summary of IGMP Snooping Output Fields
Field
IGMP Snooping Monitor
Values
VLAN
Interfaces
Groups
MRouters
VLAN for which IGMP snooping is enabled.
Interface connected to a multicast router.
Number of the multicast groups learned by the VLAN.
Multicast router.
Receivers
IGMP Route Information
VLAN
Next-Hop
Group
Multicast receiver.
VLAN for which IGMP snooping is enabled.
Next hop assigned by the switch after performing the route lookup.
Multicast groups learned by the VLAN.
Related
Documentation
•
IGMP Snooping Overview on page 125
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
• Changing the IGMP Snooping Group Timeout Value
Copyright © 2016, Juniper Networks, Inc.
133
Multicast Protocols Feature Guide for EX4600 Switches
Verifying the IGMP Snooping Group Timeout Value
Purpose Verify that the IGMP snooping group timeout value has been changed correctly from its default value.
Action Display the IGMP snooping membership information, which contains the group timeout value that was derived from the IGMP configuration: user@switch> show
detail
VLAN: v43 Tag: 43 (Index: 4)
Group: 225.0.0.1
Receiver count: 1, Flags: <v2–hosts>
ge-0/0/15.0 Uptime: 00:00:05 timeout: 510
Meaning The IGMP snooping group timeout value determines how long a switch waits to receive an IGMP query from a multicast router before removing a multicast group from its multicast cache table. When you enable IGMP snooping, the default IGMP snooping group timeout value of 260 seconds is applied to all VLANs, which means that the switch waits 260 seconds to receive an IGMP query before removing a multicast group from its multicast cache table. You can change the timeout value by using the robust-count option.
Related
Documentation
• Changing the IGMP Snooping Group Timeout Value
134 Copyright © 2016, Juniper Networks, Inc.
PART 3
MLD
•
Copyright © 2016, Juniper Networks, Inc.
135
Multicast Protocols Feature Guide for EX4600 Switches
136 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 11
Using MLD
Understanding MLD
•
•
Examples: Configuring MLD on page 140
The Multicast Listener Discovery (MLD) Protocol manages the membership of hosts and routers in multicast groups. IP version 6 (IPv6) multicast routers use MLD to learn, for each of their attached physical networks, which groups have interested listeners. Each routing device maintains a list of host multicast addresses that have listeners for each subnetwork, as well as a timer for each address. However, the routing device does not need to know the address of each listener—just the address of each host. The routing device provides addresses to the multicast routing protocol it uses, which ensures that multicast packets are delivered to all subnetworks where there are interested listeners.
In this way, MLD is used as the transport for the Protocol Independent Multicast (PIM)
Protocol.
MLD is an integral part of IPv6 and must be enabled on all IPv6 routing devices and hosts that need to receive IP multicast traffic. The Junos OS supports MLD versions 1 and 2.
Version 2 is supported for source-specific multicast (SSM) include and exclude modes.
In include mode, the receiver specifies the source or sources it is interested in receiving the multicast group traffic from. Exclude mode works the opposite of include mode. It allows the receiver to specify the source or sources it is not interested in receiving the multicast group traffic from.
For each attached network, a multicast routing device can be either a querier or a nonquerier. A querier routing device, usually one per subnet, solicits group membership information by transmitting MLD queries. When a host reports to the querier routing device that it has interested listeners, the querier routing device forwards the membership information to the rendezvous point (RP) routing device by means of the receiver's
(host's) designated router (DR). This builds the rendezvous-point tree (RPT) connecting the host with interested listeners to the RP routing device. The RPT is the initial path used by the sender to transmit information to the interested listeners. Nonquerier routing devices do not transmit MLD queries on a subnet but can do so if the querier routing device fails.
Copyright © 2016, Juniper Networks, Inc.
137
Multicast Protocols Feature Guide for EX4600 Switches
All MLD-configured routing devices start as querier routing devices on each attached subnet (see
). The querier routing device on the right is the receiver's
DR.
Figure 21: Routing Devices Start Up on a Subnet
To elect the querier routing device, the routing devices exchange query messages containing their IPv6 source addresses. If a routing device hears a query message whose
IPv6 source address is numerically lower than its own selected address, it becomes a nonquerier. In
Figure 22 on page 138 , the routing device on the left has a source address
numerically lower than the one on the right and therefore becomes the querier routing device.
NOTE: In the practical application of MLD, several routing devices on a subnet are nonqueriers. If the elected querier routing device fails, query messages are exchanged among the remaining routing devices. The routing device with the lowest IPv6 source address becomes the new querier routing device. The
IPv6 Neighbor Discovery Protocol (NDP) implementation drops incoming
Neighbor Announcement (NA) messages that have a broadcast or multicast address in the target link-layer address option. This behavior is recommended by RFC 2461.
Figure 22: Querier Routing Device Is Determined
The querier routing device sends general MLD queries on the link-scope all-nodes multicast address FF02::1 at short intervals to all attached subnets to solicit group membership information (see
Figure 23 on page 139 ). Within the query message is the maximum
response delay value, specifying the maximum allowed delay for the host to respond with a report message.
138 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
Figure 23: General Query Message Is Issued
If interested listeners are attached to the host receiving the query, the host sends a report containing the host's IPv6 address to the routing device (see
the reported address is not yet in the routing device's list of multicast addresses with interested listeners, the address is added to the list and a timer is set for the address. If the address is already on the list, the timer is reset. The host's address is transmitted to the RP in the PIM domain.
Figure 24: Reports Are Received by the Querier Routing Device
If the host has no interested multicast listeners, it sends a done message to the querier routing device. On receipt, the querier routing device issues a multicast address-specific query containing the last listener query interval value to the multicast address of the host.
If the routing device does not receive a report from the multicast address, it removes the multicast address from the list and notifies the RP in the PIM domain of its removal (see
Figure 25: Host Has No Interested Receivers and Sends a Done Message to Routing Device
If a done message is not received by the querier routing device, the querier routing device continues to send multicast address-specific queries. If the timer set for the address on receipt of the last report expires, the querier routing device assumes there are no longer interested listeners on that subnet, removes the multicast address from the list, and notifies the RP in the PIM domain of its removal (see
).
Copyright © 2016, Juniper Networks, Inc.
139
Multicast Protocols Feature Guide for EX4600 Switches
Figure 26: Host Address Timer Expires and Address Is Removed from
Multicast Address List
Related
Documentation
•
•
Example: Recording MLD Join and Leave Events on page 158
•
Example: Modifying the MLD Robustness Variable on page 149
Examples: Configuring MLD
•
•
•
•
Modifying the MLD Version on page 145
•
Modifying the MLD Host-Query Message Interval on page 145
•
Modifying the MLD Query Response Interval on page 146
•
Modifying the MLD Last-Member Query Interval on page 146
•
Specifying Immediate-Leave Host Removal for MLD on page 147
•
Filtering Unwanted MLD Reports at the MLD Interface Level on page 148
•
Example: Modifying the MLD Robustness Variable on page 149
•
Limiting the Maximum MLD Message Rate on page 150
•
Enabling MLD Static Group Membership on page 151
•
Example: Recording MLD Join and Leave Events on page 158
•
Configuring the Number of MLD Multicast Group Joins on Logical Interfaces on page 160
•
Understanding MLD
The Multicast Listener Discovery (MLD) Protocol manages the membership of hosts and routers in multicast groups. IP version 6 (IPv6) multicast routers use MLD to learn, for each of their attached physical networks, which groups have interested listeners. Each routing device maintains a list of host multicast addresses that have listeners for each subnetwork, as well as a timer for each address. However, the routing device does not need to know the address of each listener—just the address of each host. The routing device provides addresses to the multicast routing protocol it uses, which ensures that multicast packets are delivered to all subnetworks where there are interested listeners.
In this way, MLD is used as the transport for the Protocol Independent Multicast (PIM)
Protocol.
140 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
MLD is an integral part of IPv6 and must be enabled on all IPv6 routing devices and hosts that need to receive IP multicast traffic. The Junos OS supports MLD versions 1 and 2.
Version 2 is supported for source-specific multicast (SSM) include and exclude modes.
In include mode, the receiver specifies the source or sources it is interested in receiving the multicast group traffic from. Exclude mode works the opposite of include mode. It allows the receiver to specify the source or sources it is not interested in receiving the multicast group traffic from.
For each attached network, a multicast routing device can be either a querier or a nonquerier. A querier routing device, usually one per subnet, solicits group membership information by transmitting MLD queries. When a host reports to the querier routing device that it has interested listeners, the querier routing device forwards the membership information to the rendezvous point (RP) routing device by means of the receiver's
(host's) designated router (DR). This builds the rendezvous-point tree (RPT) connecting the host with interested listeners to the RP routing device. The RPT is the initial path used by the sender to transmit information to the interested listeners. Nonquerier routing devices do not transmit MLD queries on a subnet but can do so if the querier routing device fails.
All MLD-configured routing devices start as querier routing devices on each attached subnet (see
). The querier routing device on the right is the receiver's
DR.
Figure 27: Routing Devices Start Up on a Subnet
To elect the querier routing device, the routing devices exchange query messages containing their IPv6 source addresses. If a routing device hears a query message whose
IPv6 source address is numerically lower than its own selected address, it becomes a nonquerier. In
Figure 22 on page 138 , the routing device on the left has a source address
numerically lower than the one on the right and therefore becomes the querier routing device.
NOTE: In the practical application of MLD, several routing devices on a subnet are nonqueriers. If the elected querier routing device fails, query messages are exchanged among the remaining routing devices. The routing device with the lowest IPv6 source address becomes the new querier routing device. The
IPv6 Neighbor Discovery Protocol (NDP) implementation drops incoming
Neighbor Announcement (NA) messages that have a broadcast or multicast address in the target link-layer address option. This behavior is recommended by RFC 2461.
Copyright © 2016, Juniper Networks, Inc.
141
Multicast Protocols Feature Guide for EX4600 Switches
Figure 28: Querier Routing Device Is Determined
The querier routing device sends general MLD queries on the link-scope all-nodes multicast address FF02::1 at short intervals to all attached subnets to solicit group membership information (see
Figure 23 on page 139 ). Within the query message is the maximum
response delay value, specifying the maximum allowed delay for the host to respond with a report message.
Figure 29: General Query Message Is Issued
If interested listeners are attached to the host receiving the query, the host sends a report containing the host's IPv6 address to the routing device (see
the reported address is not yet in the routing device's list of multicast addresses with interested listeners, the address is added to the list and a timer is set for the address. If the address is already on the list, the timer is reset. The host's address is transmitted to the RP in the PIM domain.
Figure 30: Reports Are Received by the Querier Routing Device
If the host has no interested multicast listeners, it sends a done message to the querier routing device. On receipt, the querier routing device issues a multicast address-specific query containing the last listener query interval value to the multicast address of the host.
If the routing device does not receive a report from the multicast address, it removes the multicast address from the list and notifies the RP in the PIM domain of its removal (see
142 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
Figure 31: Host Has No Interested Receivers and Sends a Done Message to Routing Device
If a done message is not received by the querier routing device, the querier routing device continues to send multicast address-specific queries. If the timer set for the address on receipt of the last report expires, the querier routing device assumes there are no longer interested listeners on that subnet, removes the multicast address from the list, and notifies the RP in the PIM domain of its removal (see
).
Figure 32: Host Address Timer Expires and Address Is Removed from
Multicast Address List
Configuring MLD
To configure the Multicast Listener Discovery (MLD) Protocol, include the mld statement: mld { accounting; interface interface-name { disable;
(accounting | no-accounting); group-policy [ policy-names ]; immediate-leave; oif-map [ map-names ]; passive; ssm-map ssm-map-name; static (Protocols MLD) { group multicast-group-address { exclude;
number; group-increment increment; source ip-address { source-count number; source-increment increment;
}
}
} version version;
} maximum-transmit-rate packets-per-second;
Copyright © 2016, Juniper Networks, Inc.
143
Multicast Protocols Feature Guide for EX4600 Switches
Enabling MLD
} query-interval seconds; query-last-member-interval seconds; query-response-interval seconds; robust-count number;
You can include this statement at the following hierarchy levels:
• [edit protocols]
• [edit logical-systems logical-system-name protocols]
By default, MLD is enabled on all broadcast interfaces when you configure Protocol
Independent Multicast (PIM) or the Distance Vector Multicast Routing Protocol (DVMRP).
The Multicast Listener Discovery (MLD) Protocol manages multicast groups by establishing, maintaining, and removing groups on a subnet. Multicast routing devices use MLD to learn which groups have members on each of their attached physical networks.
MLD must be enabled for the router to receive IPv6 multicast packets. MLD is only needed for IPv6 networks, because multicast is handled differently in IPv4 networks. MLD is enabled on all IPv6 interfaces on which you configure PIM and on all IPv6 broadcast interfaces when you configure DVMRP.
MLD specifies different behaviors for multicast listeners and for routers. When a router is also a listener, the router responds to its own messages. If a router has more than one interface to the same link, it needs to perform the router behavior over only one of those interfaces. Listeners, on the other hand, must perform the listener behavior on all interfaces connected to potential receivers of multicast traffic.
If MLD is not running on an interface—either because PIM and DVMRP are not configured on the interface or because MLD is explicitly disabled on the interface—you can explicitly enable MLD.
To explicitly enable MLD:
1.
If PIM and DVMRP are not running on the interface, explicitly enable MLD by including the interface name.
[edit protocols mld] user@host# set interface fe-0/0/0.0
2.
Check to see if MLD is disabled on any interfaces. In the following example, MLD is disabled on a Gigabit Ethernet interface.
[edit protocols mld] user@host# show interface fe-0/0/0.0; interface ge-0/0/0.0 {
disable;
}
3.
Enable MLD on the interface by deleting the disable statement.
[edit protocols mld]
144 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD delete interface ge-0/0/0.0 disable
4.
Verify the configuration.
[edit protocols mld] user@host# show interface fe-0/0/0.0; interface ge-0/0/0.0;
5.
Verify the operation of MLD by checking the output of the show mld interface command.
Modifying the MLD Version
By default, the router supports MLD version 1 (MLDv1). To enable the router to use MLD version 2 (MLDv2) for source-specific multicast (SSM) only, include the version 2 statement.
If you configure the MLD version setting at the individual interface hierarchy level, it overrides configuring the IGMP version using the interface all statement.
If a source address is specified in a multicast group that is statically configured, the version must be set to MLDv2.
To change an MLD interface to version 2:
1.
Configure the MLD interface.
[edit protocols mld] user@host# set interface fe-0/0/0.0 version 2
2.
Verify the configuration by checking the version field in the output of the show mld interface command. The show mld statistics command has version-specific output fields, such as the counters in the MLD Message type field.
Modifying the MLD Host-Query Message Interval
The objective of MLD is to keep routers up to date with IPv6 group membership of the entire subnet. Routers need not know who all the members are, only that members exist.
Each host keeps track of which multicast groups are subscribed to. On each link, one router is elected the querier. The MLD querier router periodically sends general host-query messages on each attached network to solicit membership information. These messages solicit group membership information and are sent to the link-scope all-nodes address
FF02::1 . A general host-query message has a maximum response time that you can set by configuring the query response interval.
The query response timeout, the query interval, and the robustness variable are related in that they are all variables that are used to calculate the multicast listener interval. The multicast listener interval is the number of seconds that must pass before a multicast router determines that no more members of a host group exist on a subnet. The multicast listener interval is calculated as the (robustness variable x query-interval) + (1 x query-response-interval). If no reports are received for a particular group before the multicast listener interval has expired, the routing device stops forwarding remotely-originated multicast packets for that group onto the attached network.
Copyright © 2016, Juniper Networks, Inc.
145
Multicast Protocols Feature Guide for EX4600 Switches
By default, host-query messages are sent every 125 seconds. You can change this interval to change the number of MLD messages sent on the subnet.
To modify the query interval:
1.
Configure the interval.
[edit protocols mld] user@host# set query-interval 200
The value can be from 1 through 1024 seconds.
2.
Verify the configuration by checking the MLD Query Interval field in the output of the show mld interface command.
3.
Verify the operation of the query interval by checking the Listener Query field in the output of the show mld statistics command.
Modifying the MLD Query Response Interval
The query response interval is the maximum amount of time that can elapse between when the querier router sends a host-query message and when it receives a response from a host. You can change this interval to adjust the burst peaks of MLD messages on the subnet. Set a larger interval to make the traffic less bursty.
The query response timeout, the query interval, and the robustness variable are related in that they are all variables that are used to calculate the multicast listener interval. The multicast listener interval is the number of seconds that must pass before a multicast router determines that no more members of a host group exist on a subnet. The multicast listener interval is calculated as the (robustness variable x query-interval) + (1 x query-response-interval). If no reports are received for a particular group before the multicast listener interval has expired, the routing device stops forwarding remotely-originated multicast packets for that group onto the attached network.
The default query response interval is 10 seconds. You can configure a subsecond interval up to one digit to the right of the decimal point. The configurable range is 0.1 through 0.9, then in 1-second intervals 1 through 999,999.
To modify the query response interval:
1.
Configure the interval.
[edit protocols mld] user@host# set query-response-interval 0.5
2.
Verify the configuration by checking the MLD Query Response Interval field in the output of the show mld interface command.
3.
Verify the operation of the query interval by checking the Listener Query field in the output of the show mld statistics command.
Modifying the MLD Last-Member Query Interval
The last-member query interval (also called the last-listener query interval) is the maximum amount of time between group-specific query messages, including those sent
146 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD in response to done messages sent on the link-scope-all-routers address FF02::2. You can lower this interval to reduce the amount of time it takes a router to detect the loss of the last member of a group.
When the routing device that is serving as the querier receives a leave-group (done) message from a host, the routing device sends multiple group-specific queries to the group. The querier sends a specific number of these queries, and it sends them at a specific interval. The number of queries sent is called the last-listener query count. The interval at which the queries are sent is called the last-listener query interval. Both settings are configurable, thus allowing you to adjust the leave latency. The IGMP leave latency is the time between a request to leave a multicast group and the receipt of the last byte of data for the multicast group.
The last-listener query count x (times) the last-listener query interval = (equals) the amount of time it takes a routing device to determine that the last member of a group has left the group and to stop forwarding group traffic.
The default last-listener query interval is 1 second. You can configure a subsecond interval up to one digit to the right of the decimal point. The configurable range is 0.1 through 0.9, then in 1-second intervals 1 through 999,999.
To modify this interval:
1.
Configure the time (in seconds) that the routing device waits for a report in response to a group-specific query.
[edit protocols mld] user@host# set query-last-member-interval 0.1
2.
Verify the configuration by checking the MLD Last Member Query Interval field in the output of the show igmp interfaces command.
NOTE: You can configure the last-member query count by configuring the robustness variable. The two are always equal.
Specifying Immediate-Leave Host Removal for MLD
The immediate leave setting is useful for minimizing the leave latency of MLD memberships. When this setting is enabled, the routing device leaves the multicast group immediately after the last host leaves the multicast group.
The immediate-leave setting enables host tracking, meaning that the device keeps track of the hosts that send join messages. This allows MLD to determine when the last host sends a leave message for the multicast group.
When the immediate leave setting is enabled, the device removes an interface from the forwarding-table entry without first sending MLD group-specific queries to the interface.
The interface is pruned from the multicast tree for the multicast group specified in the
MLD leave message. The immediate leave setting ensures optimal bandwidth management for hosts on a switched network, even when multiple multicast groups are being used simultaneously.
Copyright © 2016, Juniper Networks, Inc.
147
Multicast Protocols Feature Guide for EX4600 Switches
When immediate leave is disabled and one host sends a leave group message, the routing device first sends a group query to determine if another receiver responds. If no receiver responds, the routing device removes all hosts on the interface from the multicast group.
Immediate leave is disabled by default for both MLD version 1 and MLD version 2.
NOTE: Although host tracking is enabled for IGMPv2 and MLDv1 when you enable immediate leave, use immediate leave with these versions only when there is one host on the interface. The reason is that IGMPv2 and MLDv1 use a report suppression mechanism whereby only one host on an interface sends a group join report in response to a membership query. The other interested hosts suppress their reports. The purpose of this mechanism is to avoid a flood of reports for the same group. But it also interferes with host tracking, because the router only knows about the one interested host and does not know about the others.
To enable immediate leave:
1.
Configure immediate leave on the MLD interface.
[edit protocols mld] user@host# set interface ge-0/0/0.1 immediate-leave
2.
Verify the configuration by checking the Immediate Leave field in the output of the show mld interface command.
Filtering Unwanted MLD Reports at the MLD Interface Level
Suppose you need to limit the subnets that can join a certain multicast group. The group-policy statement enables you to filter unwanted MLD reports at the interface level.
When the group-policy statement is enabled on a router, after the router receives an MLD report, the router compares the group against the specified group policy and performs the action configured in that policy (for example, rejects the report if the policy matches the defined address or network).
You define the policy to match only MLD group addresses (for MLDv1) by using the policy's route-filter statement to match the group address. You define the policy to match MLD
(source, group) addresses (for MLDv2) by using the policy's route-filter statement to match the group address and the policy's source-address-filter statement to match the source address.
To filter unwanted MLD reports:
1.
Configure an MLDv1 policy.
[edit policy-statement reject_policy_v1] user@host# set from route-filter fec0:1:1:4::/64 exact user@host# set then reject
2.
Configure an MLDv2 policy.
[edit policy-statement reject_policy_v2]
148 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD user@host# set from route-filter fec0:1:1:4::/64 exact user@host# set from source-address-filter fe80::2e0:81ff:fe05:1a8d/32 orlonger user@host# set then reject
3.
Apply the policies to the MLD interfaces where you prefer not to receive specific group or (source, group) reports. In this example, ge-0/0/0.1 is running MLDv1 and ge-0/1/1.0
is running MLDv2.
[edit protocols mld] user@host# set interface ge-0/0/0.1 group-policy reject_policy_v1 user@host# set interface ge-0/1/1.0 group-policy reject_policy_v2
4.
Verify the operation of the filter by checking the Rejected Report field in the output of the show mld statistics command.
Example: Modifying the MLD Robustness Variable
This example shows how to configure and verify the MLD robustness variable in a multicast domain.
•
•
•
•
Requirements
Before you begin:
• Configure the router interfaces.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing
Protocols Library for Routing Devices.
• Enable IPv6 unicast routing. See the Junos OS Routing Protocols Library for Routing
Devices.
• Enable PIM. See
Overview
The MLD robustness variable can be fine-tuned to allow for expected packet loss on a subnet. Increasing the robust count allows for more packet loss but increases the leave latency of the subnetwork.
The value of the robustness variable is used in calculating the following MLD message intervals:
• Group member interval—Amount of time that must pass before a multicast router determines that there are no more members of a group on a network. This interval is calculated as follows: (robustness variable x query-interval) + (1 x query-response-interval).
Copyright © 2016, Juniper Networks, Inc.
149
Multicast Protocols Feature Guide for EX4600 Switches
• Other querier present interval—Amount of time that must pass before a multicast router determines that there is no longer another multicast router that is the querier.
This interval is calculated as follows: (robustness variable x query-interval) + (0.5 x query-response-interval).
• Last-member query count—Number of group-specific queries sent before the router assumes there are no local members of a group. The default number is the value of the robustness variable.
By default, the robustness variable is set to 2. The number can be from 2 through 10. You might want to increase this value if you expect a subnet to lose packets.
CLI Quick
Configuration
Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
set protocols mld robust-count 5
Step-by-Step
Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To change the value of the robustness variable:
1.
2.
Configure the robust count.
[edit protocols mld] user@host# set robust-count 5
If you are done configuring the device, commit the configuration.
[edit protocols mld] user@host# commit
Verification
To verify the configuration is working properly, check the MLD Robustness Count field in the output of the show mld interfaces command.
Limiting the Maximum MLD Message Rate
You can change the limit for the maximum number of MLD packets transmitted in 1 second by the router.
Increasing the maximum number of MLD packets transmitted per second might be useful on a router with a large number of interfaces participating in MLD.
150 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
To change the limit for the maximum number of MLD packets the router can transmit in
1 second, include the maximum-transmit-rate statement and specify the maximum number of packets per second to be transmitted.
Enabling MLD Static Group Membership
•
Create a MLD Static Group Member on page 151
•
Automatically create static groups on page 152
•
Automatically increment group addresses on page 153
•
Specify multicast source address (in SSM mode) on page 154
•
Automatically specify multicast sources on page 155
•
Automatically increment source addresses on page 156
•
Exclude multicast source addresses (in SSM mode) on page 157
Create a MLD Static Group Member
You can create MLD static group membership to test multicast forwarding without a receiver host. When you enable MLD static group membership, data is forwarded to an interface without that interface receiving membership reports from downstream hosts.
Class-of-service (CoS) adjustment is not supported with MLD static group membership.
When you configure static groups on an interface on which you want to receive multicast traffic, you can specify the number of static groups to be automatically created.
In this example, you create static group ff0e::1:ff05:1a8d.
1.
Configure the static groups to be created by including the static statement and group statement and specifying which IPv6 multicast address of the group to be created.
[edit protocols mld] user@host# set interface fe-0/1/2 static (Protocols MLD) group ff0e::1:ff05:1a8d
2.
After you commit the configuration, use the show configuration protocol mld command to verify the MLD protocol configuration.
user@host> show configuration protocol mld interface fe-0/1/2.0 { static { group ff0e::1:ff05:1a8d;
}
}
3.
After you have committed the configuration and after the source is sending traffic, use the show mld group command to verify that static group ff0e::1:ff05:1a8d has been created.
user@host> show mld group
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Group mode: Include
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Copyright © 2016, Juniper Networks, Inc.
151
Multicast Protocols Feature Guide for EX4600 Switches
NOTE: You must specify a unique address for each group.
Automatically create static groups
When you create MLD static group membership to test multicast forwarding on an interface on which you want to receive multicast traffic, you can specify that a number of static groups be automatically created. This is useful when you want to test forwarding to multiple receivers without having to configure each receiver separately.
In this example, you create three groups.
1.
Configure the number of static groups to be created by including the group-count statement and specifying the number of groups to be created.
[edit protocols mld] user@host# set interface fe-0/1/2 static (Protocols MLD) group ff0e::1:ff05:1a8d
3
2.
After you commit the configuration, use the show configuration protocol mld command to verify the MLD protocol configuration.
user@host> show configuration protocol mld interface fe-0/1/2.0 { static { group ff0e::1:ff05:1a8d { group-count 3;
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show mld group command to verify that static groups ff0e::1:ff05:1a8d, ff0e::1:ff05:1a8e, and ff0e::1:ff05:1a8f have been created.
user@host> show mld group
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8e
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8f
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
152 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
Automatically increment group addresses
When you configure static groups on an interface on which you want to receive multicast traffic and you specify the number of static groups to be automatically created, you can also configure the group address to be automatically incremented by some number of addresses.
In this example, you create three groups and increase the group address by an increment of two for each group.
1.
Configure the group address increment by including the group-increment statement and specifying the number by which the address should be incremented for each group. The increment is specified in a format similar to an IPv6 address.
[edit protocols mld] user@host# set interface fe-0/1/2 static (Protocols MLD) group ff0e::1:ff05:1a8d
3 group-increment ::2
2.
After you commit the configuration, use the show configuration protocol mld command to verify the MLD protocol configuration.
user@host> show configuration protocol mld interface fe-0/1/2.0 { static { group ff0e::1:ff05:1a8d { group-increment ::2; group-count 3;
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show mld group command to verify that static groups ff0e::1:ff05:1a8d, ff0e::1:ff05:1a8f, and ff0e::1:ff05:1a91 have been created.
user@host> show mld group
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8f
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a91
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Copyright © 2016, Juniper Networks, Inc.
153
Multicast Protocols Feature Guide for EX4600 Switches
Specify multicast source address (in SSM mode)
When you configure static groups on an interface on which you want to receive multicast traffic and your network is operating in source-specific multicast (SSM) mode, you can specify the multicast source address to be accepted.
If you specify a group address in the SSM range, you must also specify a source.
If a source address is specified in a multicast group that is statically configured, the MLD version must be set to MLDv2 on the interface. MLDv1 is the default value.
In this example, you create group ff0e::1:ff05:1a8d and accept IPv6 address fe80::2e0:81ff:fe05:1a8d as the only source.
1.
Configure the source address by including the source statement and specifying the
IPv6 address of the source host.
[edit protocols mld] user@host# set interface fe-0/1/2 static (Protocols MLD) group ff0e::1:ff05:1a8d source fe80::2e0:81ff:fe05:1a8d
2.
After you commit the configuration, use the show configuration protocol mld command to verify the MLD protocol configuration.
user@host> show configuration protocol mld interface fe-0/1/2.0 { static { group ff0e::1:ff05:1a8d { source fe80::2e0:81ff:fe05:1a8d;
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show mld group command to verify that static group ff0e::1:ff05:1a8d has been created and that source fe80::2e0:81ff:fe05:1a8d has been accepted.
user@host> show mld group
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
154 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
Automatically specify multicast sources
When you configure static groups on an interface on which you want to receive multicast traffic, you can specify a number of multicast sources to be automatically accepted.
In this example, you create static group ff0e::1:ff05:1a8d and accept fe80::2e0:81ff:fe05:1a8d, fe80::2e0:81ff:fe05:1a8e, and fe80::2e0:81ff:fe05:1a8f as the source addresses.
1.
Configure the number of multicast source addresses to be accepted by including the source-count statement and specifying the number of sources to be accepted.
[edit protocols mld] user@host# set interface fe-0/1/2 static (Protocols MLD) group ff0e::1:ff05:1a8d source fe80::2e0:81ff:fe05:1a8d source-count 3
2.
After you commit the configuration, use the show configuration protocol mld command to verify the MLD protocol configuration.
user@host> show configuration protocol mld interface fe-0/1/2.0 { static { group ff0e::1:ff05:1a8d { source fe80::2e0:81ff:fe05:1a8d { source-count 3;
}
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show mld group command to verify that static group ff0e::1:ff05:1a8d has been created and that sources fe80::2e0:81ff:fe05:1a8d, fe80::2e0:81ff:fe05:1a8e, and fe80::2e0:81ff:fe05:1a8f have been accepted.
user@host> show mld group
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8e
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8f
Last reported by: Local
Timeout: 0 Type: Static
Copyright © 2016, Juniper Networks, Inc.
155
Multicast Protocols Feature Guide for EX4600 Switches
156
Automatically increment source addresses
When you configure static groups on an interface on which you want to receive multicast traffic, and specify a number of multicast sources to be automatically accepted, you can also specify the number by which the address should be incremented for each source accepted.
In this example, you create static group ff0e::1:ff05:1a8d and accept fe80::2e0:81ff:fe05:1a8d, fe80::2e0:81ff:fe05:1a8f, and fe80::2e0:81ff:fe05:1a91 as the sources.
1.
Configure the number of multicast source addresses to be accepted by including the source-increment statement and specifying the number of sources to be accepted.
[edit protocols mld] user@host# set interface fe-0/1/2 static (Protocols MLD) group ff0e::1:ff05:1a8d source fe80::2e0:81ff:fe05:1a8d source-count 3 source-increment ::2
2.
After you commit the configuration, use the show configuration protocol mld command to verify the MLD protocol configuration.
user@host> show configuration protocol mld interface fe-0/1/2.0 { static { group ff0e::1:ff05:1a8d { source fe80::2e0:81ff:fe05:1a8d { source-count 3; source-increment ::2;
}
}
}
}
3.
After you have committed the configuration and the source is sending traffic, use the show mld group command to verify that static group ff0e::1:ff05:1a8d has been created and that sources fe80::2e0:81ff:fe05:1a8d, fe80::2e0:81ff:fe05:1a8f, and fe80::2e0:81ff:fe05:1a91 have been accepted.
user@host> show mld group
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a8f
Last reported by: Local
Timeout: 0 Type: Static
Interface: fe-0/1/2
Group: ff0e2::1:ff05:1a8d
Source: fe80::2e0:81ff:fe05:1a91
Last reported by: Local
Timeout: 0 Type: Static
Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Group mode: Include
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Group: ff0e::1:ff05:1a8d
Group mode: Include
Source: fe80::2e0:81ff:fe05:1a8f
Last reported by: Local
Timeout: 0 Type: Static
Group: ff0e::1:ff05:1a8d
Group mode: Include
Source: fe80::2e0:81ff:fe05:1a91
Last reported by: Local
Timeout: 0 Type: Static
Exclude multicast source addresses (in SSM mode)
When you configure static groups on an interface on which you want to receive multicast traffic and your network is operating in source-specific multicast (SSM) mode, you can specify that certain multicast source addresses be excluded.
By default the multicast source address configured in a static group operates in include mode. In include mode the multicast traffic for the group is accepted from the configured source address. You can also configure the static group to operate in exclude mode. In exclude mode the multicast traffic for the group is accepted from any address other than the configured source address.
If a source address is specified in a multicast group that is statically configured, the MLD version must be set to MLDv2 on the interface. MLDv1 is the default value.
In this example, you exclude address fe80::2e0:81ff:fe05:1a8d as a source for group ff0e::1:ff05:1a8d.
1.
Configure a multicast static group to operate in exclude mode by including the exclude statement and specifying which IPv6 source address to be excluded.
[edit protocols mld] user@host# set interface fe-0/1/2 static (Protocols MLD) group ff0e::1:ff05:1a8d exclude source fe80::2e0:81ff:fe05:1a8d
2.
After you commit the configuration, use the show configuration protocol mld command to verify the MLD protocol configuration.
user@host> show configuration protocol mld interface fe-0/1/2.0 { static { group ff0e::1:ff05:1a8d { exclude; source fe80::2e0:81ff:fe05:1a8d;
}
}
}
Copyright © 2016, Juniper Networks, Inc.
157
Multicast Protocols Feature Guide for EX4600 Switches
3.
After you have committed the configuration and the source is sending traffic, use the show mld group detail command to verify that static group ff0e::1:ff05:1a8d has been created and that the static group is operating in exclude mode.
user@host> show mld group detail
Interface: fe-0/1/2
Group: ff0e::1:ff05:1a8d
Group mode: Exclude
Source: fe80::2e0:81ff:fe05:1a8d
Last reported by: Local
Timeout: 0 Type: Static
Similar configuration is available for IPv4 multicast traffic using the IGMP protocol.
Example: Recording MLD Join and Leave Events
This example shows how to determine whether MLD tuning is needed in a network by configuring the routing device to record MLD join and leave events.
•
•
•
•
Requirements
Before you begin:
• Configure the router interfaces.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing
Protocols Library for Routing Devices.
• Enable IPv6 unicast routing. See the Junos OS Routing Protocols Library for Routing
Devices.
• Enable PIM. See
Overview
describes the recordable MLD join and leave events.
Table 8: MLD Event Messages
ERRMSG Tag Definition
RPD_MLD_JOIN Records MLD join events.
RPD_MLD_LEAVE
RPD_MLD_ACCOUNTING_ON
RPD_MLD_ACCOUNTING_OFF
Records MLD leave events.
Records when MLD accounting is enabled on an MLD interface.
Records when MLD accounting is disabled on an MLD interface.
158 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD
Table 8: MLD Event Messages (continued)
ERRMSG Tag Definition
RPD_MLD_MEMBERSHIP_TIMEOUT Records MLD membership timeout events.
CLI Quick
Configuration
Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
set protocols mld interface fe-0/1/0.2 accounting set system syslog file mld-events any info set system syslog file mld-events match ".*RPD_MLD_JOIN.* | .*RPD_MLD_LEAVE.* |
.*RPD_MLD_ACCOUNTING.* | .*RPD_MLD_MEMBERSHIP_TIMEOUT.*" set system syslog file mld-events archive size 100000 set system syslog file mld-events archive files 3 set system syslog file mld-events archive transfer-interval 1440 set system syslog file mld-events archive archive-sites "ftp://user@host1//var/tmp" password "anonymous" set system syslog file mld-events archive archive-sites "ftp://user@host2//var/tmp" password "test"
Step-by-Step
Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure recording of MLD join and leave events:
1.
2.
3.
Enable accounting globally or on an MLD interface. This example shows the interface configuration.
[edit protocols mld] user@host# set
fe–0/1/0.2
Configure the events to be recorded, and filter the events to a system log file with a descriptive filename, such as mld-events.
[edit system syslog file mld-events] user@host# set any info
[edit system syslog file mld-events] user@host# set match “.*RPD_MLD_JOIN.* | .*RPD_MLD_LEAVE.* |
.*RPD_MLD_ACCOUNTING.* | .*RPD_MLD_MEMBERSHIP_TIMEOUT.*”
Periodically archive the log file.
This example rotates the file every 24 hours (1440 minutes) when it reaches 100 KB and keeps three files.
[edit system syslog file mld-events] user@host# set archive size 100000
[edit system syslog file mld-events] user@host# set archive files 3
[edit system syslog file mld-events]
Copyright © 2016, Juniper Networks, Inc.
159
Multicast Protocols Feature Guide for EX4600 Switches
4.
user@host# set archive archive-sites “ftp://user@host1//var/tmp” password
“anonymous”
[edit system syslog file mld-events] user@host# set archive archive-sites “ftp://user@host2//var/tmp” password “test”
[edit system syslog file mld-events] user@host# set archive transfer-interval 1440
[edit system syslog file mld-events] user@host# set archive start-time 2011–01–07:12:30
If you are done configuring the device, commit the configuration.
[edit system syslog file mld-events]] user@host# commit
Verification
You can view the system log file by running the file show command.
user@host> file show mld-events
You can monitor the system log file as entries are added to the file by running the monitor start and monitor stop commands.
user@host> monitor start mld-events
*** mld-events ***
Apr 16 13:08:23 host mgd[16416]: UI_CMDLINE_READ_LINE: User 'user', command 'run
monitor start mld-events ' monitor
Configuring the Number of MLD Multicast Group Joins on Logical Interfaces
The group-limit statement enables you to limit the number of MLD multicast group joins for logical interfaces. When this statement is enabled on a router running MLD version 2, the limit is applied upon receipt of the group report. Once the group limit is reached, subsequent join requests are rejected.
When configuring limits for MLD multicast groups, keep the following in mind:
• Each any-source group (*,G) counts as one group toward the limit.
• Each source-specific group (S,G) counts as one group toward the limit.
• Groups in MLDv2 exclude mode are counted toward the limit.
• Multiple source-specific groups count individually toward the group limit, even if they are for the same group. For example, (S1, G1) and (S2, G1) would count as two groups toward the configured limit.
• Combinations of any-source groups and source-specific groups count individually toward the group limit, even if they are for the same group. For example, (*, G1) and
(S, G1) would count as two groups toward the configured limit.
• Configuring and committing a group limit on a network that is lower than what already exists on the network results in the removal of all groups from the configuration. The
160 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Using MLD groups must then request to rejoin the network (up to the newly configured group limit).
• You can dynamically limit multicast groups on MLD logical interfaces by using dynamic profiles. For detailed information about creating dynamic profiles, see the Junos OS
Broadband Subscriber Management and Services Library.
Beginning with Junos OS 12.2, you can optionally configure a system log warning threshold for MLD muticast group joins received on the logical interface. It is helpful to review the system log messages for troubleshooting purposes and to detect if an excessive amount of MLD multicast group joins have been received on the interface. These log messages convey when the configured group limit has been exceeded, when the configured threshold has been exceeded, and when the number of groups drop below the configured threshold.
The group-threshold statement enables you to configure the threshold at which a warning message is logged. The range is 1 through 100 percent. The warning threshold is a percentage of the group limit, so you must configure the group-limit statement to configure a warning threshold. For instance, when the number of groups exceed the configured warning threshold, but remain below the configured group limit, multicast groups continue to be accepted, and the device logs a warning message. In addition, the device logs a warning message after the number of groups drop below the configured warning threshold.
You can further specify the amount of time (in seconds) between the log messages by configuring the log-interval statement. The range is 6 through 32,767 seconds.
You might consider throttling log messages because every entry added after the configured threshold and every entry rejected after the configured limit causes a warning message to be logged. By configuring a log interval, you can throttle the amount of system log warning messages generated for MLD multicast group joins.
To limit multicast group joins on an MLD logical interface:
1.
Access the logical interface at the MLD protocol hierarchy level.
[edit] user@host# edit protocols mld interface interface-name
2.
Specify the group limit for the interface.
[edit protocols mld interface interface-name] user@host# set group-limit limit
3.
(Optional) Configure the threshold at which a warning message is logged.
[edit protocols mld interface interface-name] user@host# set group-threshold value
4.
(Optional) Configure the amount of time between log messages.
[edit protocols mld interface interface-name] user@host# set log-interval seconds
To confirm your configuration, use the show protocols mld command. To verify the operation of MLD on the interface, including the configured group limit and the optional warning threshold and interval between log messages, use the show mld interface command.
Copyright © 2016, Juniper Networks, Inc.
161
Multicast Protocols Feature Guide for EX4600 Switches
Disabling MLD
To disable MLD on an interface, include the disable statement: interface interface-name { disable;
}
You can include this statement at the following hierarchy levels:
• [edit protocols mld]
• [edit logical-systems logical-system-name protocols mld]
Related
Documentation
• Configuring IGMP
162 Copyright © 2016, Juniper Networks, Inc.
PART 4
MSDP
•
Copyright © 2016, Juniper Networks, Inc.
163
Multicast Protocols Feature Guide for EX4600 Switches
164 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 12
Using MSDP
•
Understanding MSDP on page 165
•
Filtering MSDP SA Messages on page 166
•
•
Tracing MSDP Protocol Traffic on page 168
•
Configuring the Interface to Accept Traffic from a Remote Source on page 170
•
Example: Configuring MSDP on page 171
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
•
Example: Configuring PIM Anycast With or Without MSDP on page 178
•
Configuring a PIM Anycast RP Router with MSDP on page 181
Understanding MSDP
The Multicast Source Discovery Protocol (MSDP) is used to connect multicast routing domains. It typically runs on the same router as the Protocol Independent Multicast (PIM) sparse-mode rendezvous point (RP). Each MSDP router establishes adjacencies with internal and external MSDP peers similar to the way BGP establishes peers. These peer routers inform each other about active sources within the domain. When they detect active sources, the routers can send PIM sparse-mode explicit join messages to the active source.
The peer with the higher IP address passively listens to a well-known port number and waits for the side with the lower IP address to establish a Transmission Control Protocol
(TCP) connection. When a PIM sparse-mode RP that is running MSDP becomes aware of a new local source, it sends source-active type, length, and values (TLVs) to its MSDP peers. When a source-active TLV is received, a peer-reverse-path-forwarding (peer-RPF) check (not the same as a multicast RPF check) is done to make sure that this peer is in the path that leads back to the originating RP. If not, the source-active TLV is dropped.
This TLV is counted as a “rejected” source-active message.
The MSDP peer-RPF check is different from the normal RPF checks done by non-MSDP multicast routers. The goal of the peer-RPF check is to stop source-active messages from looping. Router R accepts source-active messages originated by Router S only from neighbor Router N or an MSDP mesh group member. For more information about configuring MSDP mesh groups, see
“Example: Configuring MSDP with Active Source
Limits and Mesh Groups” on page 172 .
Copyright © 2016, Juniper Networks, Inc.
165
Multicast Protocols Feature Guide for EX4600 Switches
Router R locates its MSDP peer-RPF neighbor (Router N) deterministically. A series of rules is applied in a particular order to received source-active messages, and the first rule that applies determines the peer-RPF neighbor. All source-active messages from other routers are rejected.
The six rules applied to source-active messages originating at Router S received at
Router R from Router X are as follows:
1.
If Router X originated the source-active message (Router X is Router S), then Router X is also the peer-RPF neighbor, and its source-active messages are accepted.
2.
If Router X is a member of the Router R mesh group, or is the configured peer, then
Router X is the peer-RPF neighbor, and its source-active messages are accepted.
3.
If Router X is the BGP next hop of the active multicast RPF route toward Router S
(Router X installed the route on Router R), then Router X is the peer-RPF neighbor, and its source-active messages are accepted.
4.
If Router X is an external BGP (EBGP) or internal BGP (IBGP) peer of Router R, and the last autonomous system (AS) number in the BGP AS-path to Router S is the same as Router X's AS number, then Router X is the peer-RPF neighbor, and its source-active messages are accepted.
5.
If Router X uses the same next hop as the next hop to Router S, then Router X is the peer-RPF neighbor, and its source-active messages are accepted.
6.
If Router X fits none of these criteria, then Router X is not an MSDP peer-RPF neighbor, and its source-active messages are rejected.
The MSDP peers that receive source-active TLVs can be constrained by BGP reachability information. If the AS path of the network layer reachability information (NLRI) contains the receiving peer's AS number prepended second to last, the sending peer is using the receiving peer as a next hop for this source. If the split horizon information is not being received, the peer can be pruned from the source-active TLV distribution list.
Related
Documentation
•
Filtering MSDP SA Messages
Along with applying MSDP source active (SA) filters on all external MSDP sessions (in and out) to prevent SAs for groups and sources from leaking in and out of the network, you need to apply bootstrap router (BSR) filters. Applying a BSR filter to the boundary of a network prevents foreign BSR messages (which announce RP addresses) from leaking into your network. Since the routers in a PIM sparse-mode domain need to know the address of only one RP router, having more than one in the network can create issues.
If you did not use multicast scoping to create boundary filters for all customer-facing interfaces, you might want to use PIM join filters. Multicast scopes prevent the actual multicast data packets from flowing in or out of an interface. PIM join filters prevent PIM sparse-mode state from being created in the first place. Since PIM join filters apply only to the PIM sparse-mode state, it might be more beneficial to use multicast scoping to filter the actual data.
166 Copyright © 2016, Juniper Networks, Inc.
Chapter 12: Using MSDP
NOTE: When you apply firewall filters, firewall action modifiers, such as log, sample , and count, work only when you apply the filter on an inbound interface.
The modifiers do not work on an outbound interface.
Related
Documentation
•
Filtering Incoming PIM Join Messages on page 77
•
Example: Configuring PIM BSR Filters on page 71
Configuring MSDP
To configure the Multicast Source Discovery Protocol (MSDP), include the msdp statement:
{
{
number;
number;
}
(disable | enable);
[ policy-names ]; group group-name {
... group-configuration ...
} hold-time seconds;
[ policy-names ];
address; keep-alive seconds; peer address {
... peer-configuration ...
}
group-name;
ip-prefix</prefix-length> {
{
number;
number;
}
} sa-hold-time seconds;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier > <disable>;
}
group-name {
[ policy-names ];
[ policy-names ];
address;
(mesh-group | standard); peer address {
... same statements as at the [edit protocols msdp
address] hierarchy level shown
just following ...
Copyright © 2016, Juniper Networks, Inc.
167
Multicast Protocols Feature Guide for EX4600 Switches
}
}
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
}
address {
{
number;
number;
}
peer-key;
[ policy-names ];
[ policy-names ];
address;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
}
You can include this statement at the following hierarchy levels:
• [edit protocols]
• [edit routing-instances routing-instance-name protocols]
• [edit logical-systems logical-system-name protocols]
• [edit logical-systems logical-system-name routing-instances routing-instance-name protocols]
By default, MSDP is disabled.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
Tracing MSDP Protocol Traffic
Tracing operations record detailed messages about the operation of routing protocols, such as the various types of routing protocol packets sent and received, and routing policy actions. You can specify which trace operations are logged by including specific tracing flags. The following table describes the flags that you can include.
Flag all general
Description
Trace all operations.
Trace general events.
168 Copyright © 2016, Juniper Networks, Inc.
Chapter 12: Using MSDP
Flag keepalive normal packets policy route source-active source-active-request source-active-response state task timer
Description
Trace keepalive messages.
Trace normal events.
Trace all MSDP packets.
Trace policy processing.
Trace MSDP changes to the routing table.
Trace source-active packets.
Trace source-active request packets.
Trace source-active response packets.
Trace state transitions.
Trace task processing.
Trace timer processing.
You can configure MSDP tracing for all peers, for all peers in a particular group, or for a particular peer.
In the following example, tracing is enabled for all routing protocol packets. Then tracing is narrowed to focus only on MSDP peers in a particular group. To configure tracing operations for MSDP:
1.
(Optional) Configure tracing by including the traceoptions statement at the [edit routing-options] hierarchy level and set the all-packets-trace and all flags to trace all protocol packets.
[edit routing-options traceoptions] user@host# set file all-packets-trace user@host# set flag all
2.
Configure the filename for the MSDP trace file.
[edit protocols msdp group groupa
user@host# set file msdp-trace
3.
(Optional) Configure the maximum number of trace files.
[edit protocols msdp group groupa
user@host# set file files 5
4.
(Optional) Configure the maximum size of each trace file.
[edit protocols msdp group groupa
user@host# set file size 1m
5.
(Optional) Enable unrestricted file access.
Copyright © 2016, Juniper Networks, Inc.
169
Multicast Protocols Feature Guide for EX4600 Switches
[edit protocols msdp group groupa
user@host# set file world-readable
6.
Configure tracing flags. Suppose you are troubleshooting issues with the source-active cache for groupa. The following example shows how to trace messages associated with the group address.
[edit protocols msdp group groupa
user@host# set flag source-active | match 230.0.0.3
7.
View the trace file.
user@host> file list /var/log user@host> file show /var/log/msdp-trace
Related
Documentation
•
Understanding MSDP on page 165
• Tracing and Logging Junos OS Operations in the Junos OS Administration Library for
Routing Devices
Configuring the Interface to Accept Traffic from a Remote Source
You can configure an incoming interface to accept multicast traffic from a remote source.
A remote source is a source that is not on the same subnet as the incoming interface.
shows such a topology, where R2 connects to the R1 source on one subnet, and to the incoming interface on R3 (ge-1/3/0.0 in the figure) on another subnet.
Figure 33: Accepting Multicast Traffic from a Remote Source
170
In this topology R2 is a pass-through device not running PIM, so R3 is the first hop router for multicast packets sent from R1. Because R1 and R3 are in different subnets, the default behavior of R3 is to disregard R1 as a remote source. You can have R3 accept multicast traffic from R1, however, by enabling accept-remote-source on the target interface.
To accept traffic from a remote source:
1.
Identify the router and physical interface that you want to receive multicast traffic from the remote source.
2.
Configure the interface to accept traffic from the remote source.
[edit protocols pim interface ge-1/3/0.0] user@host# set accept-remote-source
Copyright © 2016, Juniper Networks, Inc.
Chapter 12: Using MSDP
NOTE: If the interface you identified is not the only path from the remote source, you need to ensure that it is the best path. For example you can configure a static route on the receiver side PE router to the source, or you can prepend the AS path on the other possible routes:
[edit policy-options policy-statement as-path-prepend term prepend] user@host# set from route-filter 192.168.0.0/16 orlonger user@host# set from route-filter 172.16.0.0/16 orlonger user@host# set then as-path-prepend "1 1 1 1"
3.
Commit the configuration changes.
4.
Confirm that the interface you configured accepts traffic from the remote source.
user@host#
Related
Documentation
• Example: Allowing MBGP MVPN Remote Sources
• Understanding Prepending AS Numbers to BGP AS Paths
•
show pim statistics on page 433
Example: Configuring MSDP
Configure a router to act as a PIM sparse-mode rendezvous point and an MSDP peer:
[edit] routing-options { interface-routes { rib-group ifrg;
} rib-groups { ifrg { import-rib [inet.0 inet.2];
} mcrg { export-rib inet.2; import-rib inet.2;
}
}
} protocols { bgp { group lab { type internal; family any; neighbor 192.168.6.18 { local-address 192.168.6.17;
}
}
} pim { dense-groups {
Copyright © 2016, Juniper Networks, Inc.
171
Multicast Protocols Feature Guide for EX4600 Switches
}
} msdp { rib-group mcrg; group lab { peer 192.168.6.18 { local-address 192.168.6.17;
}
}
}
224.0.1.39/32;
224.0.1.40/32;
} rib-group mcrg; rp {
} interface all { mode sparse-dense; version 1;
} local { address 192.168.1.1;
}
Example: Configuring MSDP with Active Source Limits and Mesh Groups
This example shows how to configure MSDP to filter source-active messages and limit the flooding of source-active messages.
•
•
•
•
Requirements
Before you begin:
• Configure the router interfaces.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing
Protocols Library for Routing Devices.
• Enable PIM sparse mode. See
• Configure the router as a PIM sparse-mode RP. See
“Configuring Local PIM RPs” on page 55 .
Overview
A router interested in MSDP messages, such as an RP, might have to process a large number of MSDP messages, especially source-active messages, arriving from other routers. Because of the potential need for a router to examine, process, and create state tables for many MSDP packets, there is a possibility of an MSDP-based denial-of-service
172 Copyright © 2016, Juniper Networks, Inc.
Chapter 12: Using MSDP
(DoS) attack on a router running MSDP. To minimize this possibility, you can configure the router to limit the number of source active messages the router accepts. Also, you can configure a threshold for applying random early detection (RED) to drop some but not all MSDP active source messages.
By default, the router accepts 25,000 source active messages before ignoring the rest.
The limit can be from 1 through 1,000,000. The limit is applied to both the number of messages and the number of MSDP peers.
By default, the router accepts 24,000 source-active messages before applying the RED profile to prevent a possible DoS attack. This number can also range from 1 through
1,000,000. The next 1000 messages are screened by the RED profile and the accepted messages processed. If you configure no drop profiles (as this example does not), RED is still in effect and functions as the primary mechanism for managing congestion. In the default RED drop profile, when the packet queue fill-level is 0 percent, the drop probability is 0 percent. When the fill-level is 100 percent, the drop probability is 100 percent.
NOTE: The router ignores source-active messages with encapsulated TCP packets. Multicast does not use TCP; segments inside source-active messages are most likely the result of worm activity.
The number configured for the threshold must be less than the number configured for the maximum number of active MSDP sources.
You can configure an active source limit globally, for a group, or for a peer. If active source limits are configured at multiple levels of the hierarchy (as shown in this example), all are applied.
You can configure an active source limit for an address range as well as for a specific peer. A per-source active source limit uses an IP prefix and prefix length instead of a specific address. You can configure more than one per-source active source limit. The longest match determines the limit.
Per-source active source limits can be combined with active source limits at the peer, group, and global (instance) hierarchy level. Per-source limits are applied before any other type of active source limit. Limits are tested in the following order:
• Per-source
• Per-peer or group
• Per-instance
An active source message must “pass” all limits established before being accepted. For example, if a source is configured with an active source limit of 10,000 active multicast groups and the instance is configured with a limit of 5000(and there are no other sources or limits configured), only 5000 active source messages are accepted from this source.
MSDP mesh groups are groups of peers configured in a full-mesh topology that limits the flooding of source-active messages to neighboring peers. Every mesh group member must have a peer connection with every other mesh group member. When a source-active
Copyright © 2016, Juniper Networks, Inc.
173
Multicast Protocols Feature Guide for EX4600 Switches message is received from a mesh group member, the source-active message is always accepted but is not flooded to other members of the same mesh group. However, the source-active message is flooded to non-mesh group peers or members of other mesh groups. By default, standard flooding rules apply if mesh-group is not specified.
CAUTION: When configuring MSDP mesh groups, you must configure all members the same way. If you do not configure a full mesh, excessive flooding of source-active messages can occur.
A common application for MSDP mesh groups is peer-reverse-path-forwarding (peer-RPF) check bypass. For example, if there are two MSDP peers inside an autonomous system
(AS), and only one of them has an external MSDP session to another AS, the internal
MSDP peer often rejects incoming source-active messages relayed by the peer with the external link. Rejection occurs because the external MSDP peer must be reachable by the internal MSDP peer through the next hop toward the source in another AS, and this next-hop condition is not certain. To prevent rejections, configure an MSDP mesh group on the internal MSDP peer so it always accepts source-active messages.
NOTE: An alternative way to bypass the peer-RPF check is to configure a default peer. In networks with only one MSDP peer, especially stub networks, the source-active message always needs to be accepted. An MSDP default peer is an MSDP peer from which all source-active messages are accepted without performing the peer-RPF check. You can establish a default peer at the peer or group level by including the
statement.
explains how flooding is handled by peers in this example. .
Table 9: Source-Active Message Flooding Explanation
Source-Active Message
Received From
Source-Active Message
Flooded To
Source-Active Message Not
Flooded To
Peer 21 Peer 22
Peer 11
Peer 31
Peer 11, Peer 12, Peer 13,
Peer 31, Peer 32
Peer 21, Peer 22, Peer 31,
Peer 32
Peer 21, Peer 22, Peer 11,
Peer 12, Peer 13, Peer 32
Peer 12, Peer 13
–
illustrates source-active message flooding between different mesh groups and peers within the same mesh group.
174 Copyright © 2016, Juniper Networks, Inc.
Figure 34: Source-Active Message Flooding
Chapter 12: Using MSDP
This example includes the following settings:
• active-source-limit maximum 10000 —Applies a limit of 10,000 active sources to all other peers.
• data-encapsulation disable —On an RP router using MSDP, disables the default encapsulation of multicast data received in MSDP register messages inside MSDP source-active messages.
MSDP data encapsulation mainly concerns bursty sources of multicast traffic. Sources that send only one packet every few minutes have trouble with the timeout of state relationships between sources and their multicast groups (S,G). Routers lose data while they attempt to reestablish (S,G) state tables. As a result, multicast register messages contain data, and this data encapsulation in MSDP source-active messages can be turned on or off through configuration.
By default, MSDP data encapsulation is enabled. An RP running MSDP takes the data packets arriving in the source's register message and encapsulates the data inside an
MSDP source-active message.
However, data encapsulation creates both a multicast forwarding cache entry in the inet.1
table (this is also the forwarding table) and a routing table entry in the inet.4
table. Without data encapsulation, MSDP creates only a routing table entry in the inet.4
table. In some circumstances, such as the presence of Internet worms or other forms of DoS attack, the router's forwarding table might fill up with these entries. To prevent the forwarding table from filling up with MSDP entries, you can configure the router not to use MSDP data encapsulation. However, if you disable data encapsulation, the router ignores and discards the encapsulated data. Without data encapsulation, multicast applications with bursty sources having transmit intervals greater than about
3 minutes might not work well.
• group MSDP-group local-address 10.1.2.3
—Specifies the address of the local router (this router).
• group MSDP-group mode mesh-group —Specifies that all peers belonging to the
MSDP-group group are mesh group members.
Copyright © 2016, Juniper Networks, Inc.
175
Multicast Protocols Feature Guide for EX4600 Switches
• group MSDP-group peer 10.10.10.10
—Prevents the sending of source-active messages to neighboring peer 10.10.10.10.
• group MSDP-group peer 10.10.10.10 active-source-limit maximum 7500 —Applies a limit of 7500 active sources to MSDP peer 10.10.10.10 in group MSDP-group.
• peer 10.0.0.1 active-source-limit maximum 5000 threshold 4000 —Applies a threshhold of 4000 active sources and a limit of 5000 active sources to MSDP peer 10.0.0.1.
• source 10.1.0.0/16 active-source-limit maximum 500 —Applies a limit of 500 active sources to any source on the 10.1.0.0/16 network.
Configuration
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.
set protocols msdp data-encapsulation disable set protocols msdp active-source-limit maximum 10000 set protocols msdp peer 10.0.0.1 active-source-limit maximum 5000 set protocols msdp peer 10.0.0.1 active-source-limit threshold 4000 set protocols msdp source 10.1.0.0/16 active-source-limit maximum 500 set protocols msdp group MSDP-group mode mesh-group set protocols msdp group MSDP-group local-address 10.1.2.3
set protocols msdp group MSDP-group peer 10.10.10.10 active-source-limit maximum
7500
Step-by-Step
Procedure
The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure MSDP source active routes and mesh groups:
1.
2.
3.
(Optional) Disable data encapsulation.
[edit protocols msdp] user@host# set
disable
Configure the active source limits.
[edit protocols msdp] user@host# set
10.0.0.1
maximum 5000 threshold 4000 user@host# set
MSDP-group peer 10.10.10.10 active-source-limit maximum
7500 user@host# set active-source-limit maximum 10000 user@host# set
10.1.0.0/16 active-source-limit maximum 500
Configure the mesh group.
[edit protocols msdp] user@host# set group MSDP-group
mesh-group user@host# set group MSDP-group peer 10.10.10.10
user@host# set group MSDP-group
10.1.2.3
176 Copyright © 2016, Juniper Networks, Inc.
Chapter 12: Using MSDP
4.
If you are done configuring the device, commit the configuration.
[edit routing-instances] user@host# commit
Results
Confirm your configuration by entering the show protocols command.
user@host# show protocols msdp { data-encapsulation disable; active-source-limit { maximum 10000;
} peer 10.0.0.1 { active-source-limit { maximum 5000; threshold 4000;
}
} source 10.1.0.0/16 { active-source-limit { maximum 500;
}
} group MSDP-group { mode mesh-group; local-address 10.1.2.3; peer 10.10.10.10 { active-source-limit { maximum 7500;
}
}
}
}
Verification
To verify the configuration, run the following commands:
•
•
Related
Documentation
• Examples: Configuring MSDP
•
Filtering MSDP SA Messages on page 166
•
Configuring Local PIM RPs on page 55
Copyright © 2016, Juniper Networks, Inc.
177
Multicast Protocols Feature Guide for EX4600 Switches
Example: Configuring PIM Anycast With or Without MSDP
When you configure anycast RP, you bypass the restriction of having one active rendezvous point (RP) per multicast group, and instead deploy multiple RPs for the same group range. The RP routers share one unicast IP address. Sources from one RP are known to other RPs that use the Multicast Source Discovery Protocol (MSDP). Sources and receivers use the closest RP, as determined by the interior gateway protocol (IGP).
You can use anycast RP within a domain to provide redundancy and RP load sharing.
When an RP stops operating, sources and receivers are taken to a new RP by means of unicast routing.
You can configure anycast RP to use PIM and MSDP for IPv4, or PIM alone for both IPv4 and IPv6 scenarios. Both are discussed in this section.
We recommend a static RP mapping with anycast RP over a bootstrap router and auto-RP configuration because it provides all the benefits of a bootstrap router and auto-RP without the complexity of the BSR and auto-RP mechanisms.
All systems on a subnet must run the same version of PIM.
The default PIM version can be version 1 or version 2, depending on the mode you are configuring. PIMv1 is the default RP mode (at the [edit protocols pim rp static address
address] hierarchy level). However, PIMv2 is the default for interface mode (at the [edit protocols pim interface interface-name] hierarchy level). Explicitly configured versions override the defaults. This example explicitly configures PIMv2 on the interfaces.
The following example shows an anycast RP configuration for the RP routers, first with
MSDP and then using PIM alone, and for non-RP routers.
1.
For a network using an RP with MSDP, configure the RP using the lo0 loopback interface, which is always up. Include the address statement and specify the unique and routable router ID and the RP address at the [edit interfaces lo0 unit 0 family inet] hierarchy level. In this example, the router ID is 198.58.3.254 and the shared RP address is 198.58.3.253. Include the primary statement for the first address. Including the primary statement selects the router’s primary address from all the preferred addresses on all interfaces.
interfaces { lo0 { description "PIM RP"; unit 0 { family inet { address 198.58.3.254/32; primary; address 198.58.3.253/32;
}
}
}
}
178 Copyright © 2016, Juniper Networks, Inc.
Chapter 12: Using MSDP
2.
Specify the RP address. Include the address statement at the [edit protocols pim rp local] hierarchy level (the same address as the secondary lo0 interface).
For all interfaces, include the mode statement to set the mode to sparse and the version statement to specify PIM version 2 at the [edit protocols pim rp local interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by including the disable statement for that interface.
protocols { pim { rp { local { family inet; address 198.58.3.253;
} interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
}
3.
Configure MSDP peering. Include the peer statement to configure the address of the
MSDP peer at the [edit protocols msdp] hierarchy level. For MSDP peering, use the unique, primary addresses instead of the anycast address. To specify the local address for MSDP peering, include the local-address statement at the [edit protocols msdp peer] hierarchy level.
protocols { msdp { peer 198.58.3.250 { local-address address 198.58.3.254;
}
}
}
NOTE: If you need to configure a PIM RP for both IPv4 and IPv6 scenarios, perform Step
and Step
4.
Configure an RP using the lo0 loopback interface, which is always up. Include the address statement to specify the unique and routable router address and the RP address at the [edit interfaces lo0 unit 0 family inet] hierarchy level. In this example, the router ID is 198.58.3.254 and the shared RP address is 198.58.3.253. Include the primary statement on the first address. Including the primary statement selects the router’s primary address from all the preferred addresses on all interfaces.
interfaces { lo0 { description "PIM RP"; unit 0 {
Copyright © 2016, Juniper Networks, Inc.
179
Multicast Protocols Feature Guide for EX4600 Switches
}
}
} family inet { address 198.58.3.254/32 { primary;
} address 198.58.3.253/32;
}
5.
Include the address statement at the [edit protocols pim rp local] hierarchy level to specify the RP address (the same address as the secondary lo0 interface).
For all interfaces, include the mode statement to set the mode to sparse, and the version statement to specify PIM version 2 at the [edit protocols pim rp local interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by Including the disable statement for that interface.
Include the anycast-pim statement to configure anycast RP without MSDP (for example, if IPv6 is used for multicasting). The other RP routers that share the same
IP address are configured using the rp-set statement. There is one entry for each RP, and the maximum that can be configured is 15. For each RP, specify the routable IP address of the router and whether MSDP source active (SA) messages are forwarded to the RP.
MSDP configuration is not necessary for this type of IPv4 anycast RP configuration.
protocols { pim { rp { local { family inet { address 198.58.3.253; anycast-pim { rp-set { address 198.58.3.240; address 198.58.3.241 forward-msdp-sa;
} local-address 198.58.3.254; #If not configured, use lo0 primary
}
}
}
} interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
6.
Configure the non-RP routers. The anycast RP configuration for a non-RP router is the same whether MSDP is used or not. Specify a static RP by adding the address at
180 Copyright © 2016, Juniper Networks, Inc.
Chapter 12: Using MSDP the [edit protocols pim rp static] hierarchy level. Include the version statement at the
[edit protocols pim rp static address] hierarchy level to specify PIM version 2.
protocols { pim { rp { static { address 198.58.3.253 { version 2;
}
}
}
}
}
7.
Include the mode statement at the [edit protocols pim interface all] hierarchy level to specify sparse mode on all interfaces. Then include the version statement at the [edit protocols pim rp interface all mode] to configure all interfaces for PIM version 2. When configuring all interfaces, exclude the fxp0.0 management interface by including the disable statement for that interface.
protocols { pim { interface all { mode sparse; version 2;
} interface fxp0.0 { disable;
}
}
}
Configuring a PIM Anycast RP Router with MSDP
Add the address statement at the [edit protocols pim rp local] hierarchy level to specify the RP address (the same address as the secondary lo0 interface).
For all interfaces, use the mode statement to set the mode to sparse and the version statement to specify PIM version 2 at the [edit protocols pim rp local interface all] hierarchy level. When configuring all interfaces, exclude the fxp0.0 management interface by adding the disable statement for that interface.
protocols { pim { rp { local { family inet; address 198.58.3.253;
} interface all { mode sparse; version 2;
}
Copyright © 2016, Juniper Networks, Inc.
181
Multicast Protocols Feature Guide for EX4600 Switches
}
}
} interface fxp0.0 { disable;
}
To configure MSDP peering, add the peer statement to configure the address of the MSDP peer at the [edit protocols msdp] hierarchy level. For MSDP peering, use the unique, primary addresses instead of the anycast address. To specify the local address for MSDP peering, add the local-address statement at the [edit protocols msdp peer] hierarchy level.
protocols { msdp { peer 198.58.3.250 { local-address 198.58.3.254;
}
}
}
182 Copyright © 2016, Juniper Networks, Inc.
PART 5
Configuration Statements and
Operational Commands
•
PIM Configuration Statements on page 185
•
IGMP Configuration Statements on page 257
•
IGMP Snooping Configuration Statements on page 283
•
MSDP Configuration Statements on page 309
•
Source-Specific Multicast Configuration Statements on page 331
•
Multicast Operational Commands on page 337
•
IGMP Operational Commands on page 443
•
IGMP Snooping Operational Commands on page 467
•
MSDP Operational Commands on page 479
Copyright © 2016, Juniper Networks, Inc.
183
Multicast Protocols Feature Guide for EX4600 Switches
184 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 13
PIM Configuration Statements
•
address (Anycast RPs) on page 187
•
address (Local RPs) on page 188
•
address (Static RPs) on page 189
•
•
•
•
authentication (Protocols PIM) on page 193
•
bfd-liveness-detection (Protocols PIM) on page 194
•
•
•
•
bootstrap-priority on page 198
•
detection-time (BFD for PIM) on page 199
•
•
dr-election-on-p2p on page 201
•
dr-register-policy on page 201
•
•
export (Protocols PIM Bootstrap) on page 203
•
export (Protocols PIM) on page 204
•
family (Bootstrap) on page 205
•
family (Protocols PIM) on page 206
•
•
group (RPF Selection) on page 208
•
•
hello-interval (Protocols PIM) on page 210
•
hold-time (Protocols PIM) on page 211
•
import (Protocols PIM Bootstrap) on page 212
•
import (Protocols PIM) on page 213
Copyright © 2016, Juniper Networks, Inc.
185
Multicast Protocols Feature Guide for EX4600 Switches
186
•
•
•
•
join-prune-timeout on page 217
•
key-chain (Protocols PIM) on page 218
•
•
local-address (Protocols PIM) on page 220
•
•
•
minimum-interval (PIM BFD Liveness Detection) on page 223
•
minimum-interval (PIM BFD Transmit Interval) on page 224
•
minimum-receive-interval on page 225
•
mode (Protocols PIM) on page 225
•
•
•
next-hop (PIM RPF Selection) on page 227
•
no-adaptation (PIM BFD Liveness Detection) on page 227
•
•
•
prefix-list (PIM RPF Selection) on page 232
•
priority (Bootstrap) on page 233
•
priority (PIM Interfaces) on page 234
•
priority (PIM RPs) on page 235
•
•
reset-tracking-bit on page 237
•
rib-group (Protocols PIM) on page 238
•
•
rp-register-policy on page 241
•
•
•
source (PIM RPF Selection) on page 244
•
•
static (Protocols PIM) on page 246
•
threshold (PIM BFD Detection Time) on page 247
•
threshold (PIM BFD Transmit Interval) on page 248
•
transmit-interval (PIM BFD Liveness Detection) on page 249
•
traceoptions (Protocols PIM) on page 250
Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements
•
•
•
wildcard-source (PIM RPF Selection) on page 255
address (Anycast RPs)
Syntax address address <forward-msdp-sa>;
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)
],
[edit protocols pim
(inet | inet6)
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)
Release Information Statement introduced in Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the anycast rendezvous point (RP) addresses in the RP set. Multiple addresses can be configured in an RP set. If the RP has peer Multicast Source Discovery Protocol
(MSDP) connections, then the RP must forward MSDP source active (SA) messages.
Options address —RP address in an RP set.
forward-msdp-sa —(Optional) Forward MSDP SAs to this address.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Copyright © 2016, Juniper Networks, Inc.
187
Multicast Protocols Feature Guide for EX4600 Switches address (Local RPs)
Syntax address address;
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the local rendezvous point (RP) address.
Options address —Local RP address.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Local PIM RPs on page 55
188 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements address (Static RPs)
Syntax address address {
{
destination-ip-prefix</prefix-length>;
} override;
version;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
],
[edit routing-instances routing-instance-name protocols pim
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure static rendezvous point (RP) addresses. You can configure a static RP in a logical system only if the logical system is not directly connected to a source.
For each static RP address, you can optionally specify the PIM version and the groups for which this address can be the RP. The default PIM version is version 1.
Options address —Static RP address.
Default: 224.0.0.0/4
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring the Static PIM RP Address on the Non-RP Routing Device on page 57
Copyright © 2016, Juniper Networks, Inc.
189
Multicast Protocols Feature Guide for EX4600 Switches algorithm
Syntax algorithm algorithm-name;
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection authentication],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection authentication]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the algorithm to use for BFD authentication.
Options algorithm-name —Name of algorithm to use for BFD authentication:
• simple-password —Plain-text password. One to 16 bytes of plain text. One or more passwords can be configured.
• keyed-md5 —Keyed Message Digest 5 hash algorithm for sessions with transmit and receive rates greater than 100 ms.
• meticulous-keyed-md5 —Meticulous keyed Message Digest 5 hash algorithm.
• keyed-sha-1 —Keyed Secure Hash Algorithm I for sessions with transmit and receive rates greater than 100 ms.
• meticulous-keyed-sha-1 —Meticulous keyed Secure Hash Algorithm I.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Understanding Bidirectional Forwarding Detection Authentication for PIM
•
Configuring BFD Authentication for PIM on page 18
•
190 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements anycast-pim
Syntax anycast-pim {
{
address <forward-msdp-sa>;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced in Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure properties for anycast RP using PIM.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring PIM Anycast With or Without MSDP on page 60
Copyright © 2016, Juniper Networks, Inc.
191
Multicast Protocols Feature Guide for EX4600 Switches assert-timeout
Syntax assert-timeout seconds;
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Multicast routing devices running PIM sparse mode often forward the same stream of multicast packets onto the same LAN through the rendezvous-point tree (RPT) and shortest-path tree (SPT). PIM assert messages help routing devices determine which routing device forwards the traffic and prunes the RPT for this group. By default, routing devices enter an assert cycle every 180 seconds. You can configure this assert timeout to be between 5 and 210 seconds.
Options seconds —Time for routing device to wait before another assert message cycle.
Range: 5 through 210 seconds
Default: 180 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring the PIM Assert Timeout on page 90
192 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements authentication (Protocols PIM)
Syntax authentication {
algorithm-name;
key-chain-name;
}
Hierarchy Level [edit protocols pim interface interface-name family (inet | inet6) bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface family (inet | inet6)
interface-name bfd-liveness-detection]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the algorithm, security keychain, and level of authentication for BFD sessions running on PIM interfaces.
The remaining statements are explained separately.
Options The statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD Authentication for PIM on page 18
•
Configuring BFD for PIM on page 16
• Understanding Bidirectional Forwarding Detection Authentication for PIM
•
bfd-liveness-detection on page 194
•
key-chain (Protocols PIM) on page 218
•
Copyright © 2016, Juniper Networks, Inc.
193
Multicast Protocols Feature Guide for EX4600 Switches bfd-liveness-detection (Protocols PIM)
Syntax bfd-liveness-detection {
{
algorithm-name;
key-chain-name;
}
{
milliseconds;
}
milliseconds;
milliseconds;
number;
{
milliseconds;
milliseconds;
}
(0 | 1 | automatic);
}
Hierarchy Level [edit protocols pim interface interface-name
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim interface interface-name
(inet | inet6)]
Release Information Statement introduced in Junos OS Release 8.1.
authentication option introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure bidirectional forwarding detection (BFD) timers and authentication for PIM.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
•
Configuring BFD Authentication for PIM on page 18
194 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements bootstrap
Syntax bootstrap {
(inet | inet6) {
[ policy-names ];
[ policy-names ];
number;
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced in Junos OS Release 7.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure parameters to control bootstrap routers and messages.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
Copyright © 2016, Juniper Networks, Inc.
195
Multicast Protocols Feature Guide for EX4600 Switches bootstrap-export
Syntax bootstrap-export [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more export policies to control outgoing PIM bootstrap messages.
Options policy-names —Name of one or more import policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
•
196 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements bootstrap-import
Syntax bootstrap-import [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more import policies to control incoming PIM bootstrap messages.
Options policy-names —Name of one or more import policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
•
Copyright © 2016, Juniper Networks, Inc.
197
Multicast Protocols Feature Guide for EX4600 Switches bootstrap-priority
Syntax bootstrap-priority number;
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure whether this routing device is eligible to be a bootstrap router. In the case of a tie, the routing device with the highest IP address is elected to be the bootstrap router.
Options number —Priority for becoming the bootstrap router. A value of 0 means that the routing device is not eligible to be the bootstrap router.
Range: 0 through 255
Default: 0
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
198 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements detection-time (BFD for PIM)
Syntax detection-time {
milliseconds;
}
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection]
Release Information Statement introduced in Junos OS Release 8.2.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for BFD authentication introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable BFD failure detection. The BFD failure detection timers are adaptive and can be adjusted to be faster or slower. The lower the BFD failure detection timer value, the faster the failure detection and vice versa. For example, the timers can adapt to a higher value if the adjacency fails (that is, the timer detects failures more slowly). Or a neighbor can negotiate a higher value for a timer than the configured value. The timers adapt to a higher value when a BFD session flap occurs more than three times in a span of 15 seconds.
A back-off algorithm increases the receive (Rx) interval by two if the local BFD instance is the reason for the session flap. The transmission (Tx) interval is increased by two if the remote BFD instance is the reason for the session flap. You can use the clear bfd adaptation command to return BFD interval timers to their configured values. The clear bfd adaptation command is hitless, meaning that the command does not affect traffic flow on the routing device.
The remaining statement is explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
•
bfd-liveness-detection on page 194
•
Copyright © 2016, Juniper Networks, Inc.
199
Multicast Protocols Feature Guide for EX4600 Switches disable (PIM)
Syntax disable;
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name protocols pim
(inet | inet6)],
[edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name protocols pim
(inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit protocols pim],
[edit protocols pim
(inet | inet6)],
[edit protocols pim interface interface-name],
[edit protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced before Junos OS Release 7.4.
disable statement extended to the [family] hierarchy level in Junos OS Release 9.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Explicitly disable PIM at the protocol, interface or family hierarchy levels.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
• disable (PIM Graceful Restart)
200 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements dr-election-on-p2p
Syntax dr-election-on-p2p;
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced in Junos OS Release 9.1.
Statement introduced in Junos OS Release 9.1 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable PIM designated router (DR) election on point-to-point (P2P) links.
Default No PIM DR election is performed on point-to-point links.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring PIM Designated Router Election on Point-to-Point Links on page 16
dr-register-policy
Syntax dr-register-policy [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced in Junos OS Release 7.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more policies to control outgoing PIM register messages.
Options policy-names —Name of one or more import policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Register Message Filters on a PIM RP and DR on page 79
•
rp-register-policy on page 241
Copyright © 2016, Juniper Networks, Inc.
201
Multicast Protocols Feature Guide for EX4600 Switches embedded-rp
Syntax embedded-rp {
{
destination-ip-prefix</prefix-length>;
}
limit;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure properties for embedded IP version 6 (IPv6) RPs.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Embedded RP for IPv6
202 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements export (Protocols PIM Bootstrap)
Syntax export [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced in Junos OS Release 7.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more export policies to control outgoing PIM bootstrap messages.
Options policy-names —Name of one or more import policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
•
import (Protocols PIM Bootstrap) on page 212
Copyright © 2016, Juniper Networks, Inc.
203
Multicast Protocols Feature Guide for EX4600 Switches export (Protocols PIM)
Syntax export [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more export policies to control outgoing PIM join and prune messages. PIM join and prune filters can be applied to PIM-SM and PIM-SSM messages. PIM join and prune filters cannot be applied to PIM-DM messages.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
•
Filtering Outgoing PIM Join Messages on page 76
204 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements family (Bootstrap)
Syntax family (inet | inet6) {
[ policy-names ];
[ policy-names ];
number;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
]
Release Information Statement introduced in Junos OS Release 7.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure which IP protocol type bootstrap properties to apply.
Options inet —Apply IP version 4 (IPv4) local RP properties.
inet6 —Apply IPv6 local RP properties.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
Copyright © 2016, Juniper Networks, Inc.
205
Multicast Protocols Feature Guide for EX4600 Switches family (Protocols PIM)
Syntax family (inet | inet6) { disable;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS 11.3 for the QFX Series.
Description Enable the PIM protocol for the specified family.
Options inet —Enable the PIM protocol for the IP version 4 (IPv4) address family.
inet6 —Enable the PIM protocol for the IP version 6 (IPv6) address family.
The remaining statement is explained separately.
Related
Documentation
•
• disable (PIM Graceful Restart)
•
206 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements family (Local RP)
Syntax family (inet | inet6) {
address;
{
address;
{
address <forward-msdp-sa>;
}
}
{
destination-ip-prefix</prefix-length>;
}
seconds; override;
number;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure which IP protocol type local RP properties to apply.
Options inet —Apply IP version 4 (IPv4) local RP properties.
inet6 —Apply IPv6 local RP properties.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Local PIM RPs on page 55
Copyright © 2016, Juniper Networks, Inc.
207
Multicast Protocols Feature Guide for EX4600 Switches group (RPF Selection)
Syntax group group-address{
source-address{
next-hop-address;
}
{
next-hop-address;
}
}
Hierarchy Level [edit routing-instances routing-instance-name edit protocols pim rpf-selection]
Release Information Statement introduced in JUNOS Release 10.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description
Configure the PIM group address for which you configure RPF selection group (RPF
Default By default, PIM RPF selection is not configured.
Options group-address —PIM group address for which you configure RPF selection.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
• Example: Configuring PIM RPF Selection
208 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements group-ranges
Syntax group-ranges {
destination-ip-prefix</prefix-length>;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim rp bidirectional address address],
[edit logical-systems logical-system-name protocols pim
],
[edit logical-systems logical-system-name routing-instances instance-name protocols pim rp bidirectional address address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim rp bidirectional address address],
[edit protocols pim
],
[edit protocols pim
(inet | inet6)],
[edit protocols pim
address],
[edit routing-instances instance-name protocols pim rp bidirectional address address],
[edit routing-instances routing-instance-name protocols pim
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Support for bidirectional RP addresses introduced in Junos OS Release 12.1.
Statement introduced in Junos OS Release 13.3 for the PTX5000 router.
Description Configure the address ranges of the multicast groups for which this routing device can be a rendezvous point (RP).
Default The routing device is eligible to be the RP for all IPv4 or IPv6 groups (224.0.0.0/4 or
FF70::/12 to FFF0::/12).
Options destination-ip-prefix</prefix-length> —Addresses or address ranges for which this routing device can be an RP.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Local PIM RPs on page 55
• Configuring PIM Embedded RP for IPv6
• Example: Configuring Bidirectional PIM
Copyright © 2016, Juniper Networks, Inc.
209
Multicast Protocols Feature Guide for EX4600 Switches hello-interval (Protocols PIM)
Syntax hello-interval seconds;
Hierarchy Level [edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name],
[edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify how often the routing device sends PIM hello packets out of an interface.
Options seconds —Length of time between PIM hello packets.
Range: 0 through 255
Default: 30 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
•
Modifying the PIM Hello Interval on page 6
210 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements hold-time (Protocols PIM)
Syntax hold-time seconds;
Hierarchy Level [edit logical-systems logical-system-name protocols pim rp bidirectional address address],
[edit logical-systems logical-system-name routing-instances instance-name protocols pim rp bidirectional address address],
[edit protocols pim rp bidirectional address address],
[edit protocols pim
(inet | inet6)],
[edit routing-instances instance-name protocols pim rp bidirectional address address],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Support for bidirectional RP addresses introduced in Junos OS Release 12.1.
Statement introduced in Junos OS Release 13.3 for the PTX5000 router.
Description Specify the time period for which a neighbor is to consider the sending routing device
(this routing device) to be operative (up).
Options seconds —Hold time.
Range: 0 through 255
Default: 150 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Local PIM RPs on page 55
in the Multicast Protocols Feature Guide for
Routing Devices
• Example: Configuring Bidirectional PIM
Copyright © 2016, Juniper Networks, Inc.
211
Multicast Protocols Feature Guide for EX4600 Switches import (Protocols PIM Bootstrap)
Syntax import [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced in Junos OS Release 7.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more import policies to control incoming PIM bootstrap messages.
Options policy-names —Name of one or more import policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
•
export (Protocols PIM Bootstrap) on page 203
212 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements import (Protocols PIM)
Syntax import [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more policies to routes being imported into the routing table from PIM. Use the import statement to filter PIM join messages and prevent them from entering the network.
Options policy-names —Name of one or more policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Filtering Incoming PIM Join Messages on page 77
Copyright © 2016, Juniper Networks, Inc.
213
Multicast Protocols Feature Guide for EX4600 Switches infinity
Syntax infinity [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
[edit protocols pim
],
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced in Junos OS Release 8.0.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more policies to set the SPT threshold to infinity for a source-group address pair. Use the infinity statement to prevent the last-hop routing device from transitioning from the RPT rooted at the RP to an SPT rooted at the source for that source-group address pair.
Options policy-names —Name of one or more policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring the PIM SPT Threshold Policy on page 92
214 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements interface
Syntax
(all | interface-name) {
family (inet | inet6) { disable;
}
seconds; mode (dense | sparse | sparse-dense);
[ policy-names ];
milliseconds;
number;
milliseconds;
;
version;
}
Hierarchy Level [edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable PIM on an interface and configure interface-specific properties.
Options interface-name —Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all .
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
PIM on Aggregated Interfaces on page 6
Copyright © 2016, Juniper Networks, Inc.
215
Multicast Protocols Feature Guide for EX4600 Switches join-load-balance
Syntax join-load-balance { automatic;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced in Junos OS Release 9.0.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable load balancing of PIM join messages across interfaces and routing devices.
Options automatic —Enables automatic load balancing of PIM join messages. When a new interface or neighbor is introduced into the network, ECMP joins are redistributed with minimal disruption to traffic.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring PIM Make-Before-Break Join Load Balancing
•
Configuring PIM Join Load Balancing on page 27
• clear pim join-distribution
216 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements join-prune-timeout
Syntax join-prune-timeout seconds;
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced in Junos OS Release 8.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the timeout for the join state. If the periodic join refresh message is not received before the timeout expires, the join state is removed.
Options seconds —Number of seconds to wait for the periodic join message to arrive.
Range: 210 through 240 seconds
Default: 210 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Modifying the Join State Timeout on page 31
Copyright © 2016, Juniper Networks, Inc.
217
Multicast Protocols Feature Guide for EX4600 Switches key-chain (Protocols PIM)
Syntax key-chain key-chain-name;
Hierarchy Level [edit protocols pim interface interface-name family {inet | inet6} bfd-liveness-detection authentication],
[edit routing-instances routing-instance-name protocols pim interface interface-name family
{inet | inet6} bfd-liveness-detection authentication]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement modified in Junos OS Release 12.2 to include family in the hierarchy level.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the security keychain to use for BFD authentication.
Options key-chain-name —Name of the security keychain to use for BFD authentication. The name is a unique integer between 0 and 63. This must match one of the keychains in the authentication-key-chains statement at the [edit security] hierarchy level.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD Authentication for PIM on page 18
• Understanding Bidirectional Forwarding Detection Authentication for PIM
•
218 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements local
Syntax local {
address;
(inet | inet6) {
address;
{
address;
{
address <forward-msdp-sa>;
}
}
{
destination-ip-prefix</prefix-length>;
}
seconds; override;
number;
}
{
destination-ip-prefix</prefix-length>;
}
seconds; override;
number;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the routing device’s RP properties.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Local PIM RPs on page 55
Copyright © 2016, Juniper Networks, Inc.
219
Multicast Protocols Feature Guide for EX4600 Switches local-address (Protocols PIM)
Syntax local-address address;
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)
],
[edit protocols pim
(inet | inet6)
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)
Release Information Statement introduced in Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the routing device local address for the anycast rendezvous point (RP). If this statement is omitted, the router ID is used as this address.
Options address —Anycast RP IPv4 or IPv6 address, depending on family configuration.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring PIM Anycast With or Without MSDP on page 60
220 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements loose-check
Syntax loose-check;
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection authentication],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection authentication]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify loose authentication checking on the BFD session. Use loose authentication for transitional periods only when authentication might not be configured at both ends of the BFD session.
By default, strict authentication is enabled and authentication is checked at both ends of each BFD session. Optionally, to smooth migration from nonauthenticated sessions to authenticated sessions, you can configure loose checking. When loose checking is configured, packets are accepted without authentication being checked at each end of the session.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD Authentication for PIM on page 18
• Understanding Bidirectional Forwarding Detection Authentication for PIM
•
Copyright © 2016, Juniper Networks, Inc.
221
Multicast Protocols Feature Guide for EX4600 Switches maximum-rps
Syntax maximum-rps limit;
Hierarchy Level [edit logical-systems logical-system-name protocols pim
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
],
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Limit the number of RPs that the routing device acknowledges.
Options limit —Number of RPs.
Range: 1 through 500
Default: 100
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Embedded RP for IPv6
222 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements minimum-interval (PIM BFD Liveness Detection)
Syntax minimum-interval milliseconds;
Hierarchy Level [edit protocols pim interface interface-name
],
[edit routing-instances routing-instance-name protocols pim interface interface-name
]
Release Information Statement introduced in Junos OS Release 8.1.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the minimum interval after which the local routing device transmits hello packets and then expects to receive a reply from a neighbor with which it has established a BFD session. Optionally, instead of using this statement, you can specify the minimum transmit and receive intervals separately using the transmit-interval minimum-interval and minimum-receive-interval statements.
Options milliseconds —Minimum transmit and receive interval.
Range: 1 through 255,000 milliseconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
Copyright © 2016, Juniper Networks, Inc.
223
Multicast Protocols Feature Guide for EX4600 Switches minimum-interval (PIM BFD Transmit Interval)
Syntax minimum-interval milliseconds;
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection transmit-interval],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection transmit-interval]
Release Information Statement introduced in Junos OS Release 8.2.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for BFD authentication introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the minimum interval after which the local routing device transmits hello packets to a neighbor with which it has established a BFD session. Optionally, instead of using this statement, you can configure the minimum transmit interval using the minimum-interval statement at the [edit protocols pim interface interface-name bfd-liveness-detection] hierarchy level.
Options milliseconds —Minimum transmit interval value.
Range: 1 through 255,000
NOTE: The threshold value specified in the threshold statement must be greater than the value specified in the minimum-interval statement for the transmit-interval statement.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
•
bfd-liveness-detection on page 194
•
•
224 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements minimum-receive-interval
Syntax minimum-receive-interval milliseconds;
Hierarchy Level [edit protocols pim interface interface-name
],
[edit routing-instances routing-instance-name protocols pim interface interface-name
]
Release Information Statement introduced in Junos OS Release 8.1.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the minimum interval after which the local routing device must receive a reply from a neighbor with which it has established a BFD session. Optionally, instead of using this statement, you can configure the minimum receive interval using the minimum-interval statement at the [edit protocols pim interface interface-name bfd-liveness-detection] hierarchy level.
Options milliseconds —Minimum receive interval.
Range: 1 through 255,000 milliseconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
mode (Protocols PIM)
Syntax mode (dense | sparse | sparse-dense);
Hierarchy Level [edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure PIM to operate in sparse, dense, or sparse-dense mode.
Options dense —Operate in dense mode.
sparse —Operate in sparse mode.
sparse-dense —Operate in sparse-dense mode.
Default: sparse
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Copyright © 2016, Juniper Networks, Inc.
225
Multicast Protocols Feature Guide for EX4600 Switches multiplier
Syntax multiplier number;
Hierarchy Level [edit protocols pim interface interface-name
],
[edit routing-instances routing-instance-name protocols pim interface interface-name
]
Release Information Statement introduced in Junos OS Release 8.1.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the number of hello packets not received by a neighbor that causes the originating interface to be declared down.
Options number —Number of hello packets.
Range: 1 through 255
Default: 3
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation neighbor-policy
•
Configuring BFD for PIM on page 16
Syntax neighbor-policy [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name],
[edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced in Junos OS Release 8.2.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply a PIM interface-level policy to filter neighbor IP addresses.
Options policy-name —Name of the policy that filters neighbor IP addresses.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Interface-Level PIM Neighbor Policies on page 75
226 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements next-hop (PIM RPF Selection)
Syntax next-hop next-hop-address;
Hierarchy Level [edit routing-instances routing-instance-name protocols pim rpf-selection group group-address source source-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection group group-address wildcard-source],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list
prefix-list-addresses source source-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list
prefix-list-addresses wildcard-source]
Release Information Statement introduced in JUNOS Release 10.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the specific next-hop address for the PIM group source.
Options next-hop-address —Specific next-hop address for the PIM group source.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
• Example: Configuring PIM RPF Selection no-adaptation (PIM BFD Liveness Detection)
Syntax no-adaptation;
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection]
Release Information Statement introduced in Junos OS Release 9.0
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for BFD authentication introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure BFD sessions not to adapt to changing network conditions. We recommend that you do not disable BFD adaptation unless it is preferable to have BFD adaptation disabled in your network.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
•
bfd-liveness-detection on page 194
Copyright © 2016, Juniper Networks, Inc.
227
Multicast Protocols Feature Guide for EX4600 Switches override-interval
Syntax override-interval milliseconds;
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name],
[edit protocols pim],
[edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim]
[edit routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced in Junos OS Release 10.1.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Set the maximum time in milliseconds to delay sending override join messages for a multicast network that has join suppression enabled. When a router or switch sees a prune message for a join it is currently suppressing, it waits for the interval specified by the override timer before it sends an override join message.
Options This is a random timer with a value in milliseconds.
Range: 0 through maximum override value
Default: 2000 milliseconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Enabling Join Suppression on page 31
•
•
reset-tracking-bit on page 237
228 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements pim
Syntax pim {
seconds; dense-groups {
addresses;
}
; family (inet | inet6) { disable;
} graceful-restart { disable; restart-duration seconds;
}
[ policy-names ];
interface-name { accept-remote-source;
family (inet | inet6) { disable;
}
seconds;
(dense | sparse | sparse-dense);
[ policy-names ];
milliseconds;
number;
milliseconds;
;
version;
}
; join-prune-timeout; nonstop-routing;
milliseconds;
milliseconds;
;
group-name;
{ auto-rp {
(announce | discovery | mapping);
(mapping-agent-election | no-mapping-agent-election);
}
{
(inet | inet6) {
[ policy-names ];
[ policy-names ];
number;
}
}
[ policy-names ];
[ policy-names ];
Copyright © 2016, Juniper Networks, Inc.
229
Multicast Protocols Feature Guide for EX4600 Switches
number;
[ policy-names ];
{
{
destination-ip-prefix</prefix-length>;
}
limit;
}
{
(inet | inet6) {
address;
{
{
address <forward-msdp-sa>;
}
address;
}
{
destination-ip-prefix</prefix-length>;
}
seconds;
number;
}
}
[ policy-names ];
{
[ policy-names ];
}
{
address {
{
version;
destination-ip-prefix</prefix-length>;
}
}
}
}
{
group-address{
source-address{
next-hop-address;
}
{
next-hop-address;
}
}
prefix-list-addresses {
source-address {
next-hop-address;
}
{
next-hop-address;
}
}
{
230 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements
} file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
} tunnel-devices [ mt-fpc/pic/port ];
Hierarchy Level [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols]
Release Information Statement introduced before Junos OS Release 7.4.
family statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable PIM on the routing device.
The statements are explained separately.
Default PIM is disabled on the routing device.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Copyright © 2016, Juniper Networks, Inc.
231
Multicast Protocols Feature Guide for EX4600 Switches prefix-list (PIM RPF Selection)
Syntax prefix-list prefix-list-addresses {
source-address {
next-hop-address;
}
{
next-hop-address;
}
}
Hierarchy Level [edit routing-instances routing-instance-name protocols pim rpf-selection group group-address source source-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection group group-address wildcard-source],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list
prefix-list-addresses source source-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list
prefix-list-addresses wildcard-source]
Release Information Statement introduced in Junos OS Release 10.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description (Optional) Configure a list of prefixes (addresses) for multiple PIM groups.
Options prefix-list-addresses —List of prefixes (addresses) for multiple PIM groups.
The remaining statements are explained separately.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
• Example: Configuring PIM RPF Selection
232 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements priority (Bootstrap)
Syntax priority number;
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)],
[edit protocols pim
(inet | inet6)],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced in Junos OS Release 7.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the routing device’s likelihood to be elected as the bootstrap router.
Options number —Routing device’s priority for becoming the bootstrap router. A higher value corresponds to a higher priority.
Range: 0 through a 32-bit number
Default: 0 (The routing device has the least likelihood of becoming the bootstrap router and sends packets with a priority of 0.)
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring PIM Bootstrap Properties for IPv4
• Configuring PIM Bootstrap Properties for IPv4 or IPv6
•
bootstrap-priority on page 198
Copyright © 2016, Juniper Networks, Inc.
233
Multicast Protocols Feature Guide for EX4600 Switches priority (PIM Interfaces)
Syntax priority number;
Hierarchy Level [edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name],
[edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the routing device’s likelihood to be elected as the designated router.
Options number —Routing device’s priority for becoming the designated router. A higher value corresponds to a higher priority.
Range: 0 through 4294967295
Default: 1 (Each routing device has an equal probability of becoming the DR.)
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Interface Priority for PIM Designated Router Selection on page 15
234 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements priority (PIM RPs)
Syntax priority number;
Hierarchy Level [edit logical-systems logical-system-name protocols pim rp bidirectional address address],
[edit logical-systems logical-system-name routing-instances instance-name protocols pim rp bidirectional address address],
[edit protocols pim rp bidirectional address address],
[edit protocols pim
(inet | inet6)],
[edit routing-instances instance-name protocols pim rp bidirectional address address],
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Support for bidirectional RP addresses introduced in Junos OS Release 12.1.
Statement introduced in Junos OS Release 13.3 for the PTX5000 router.
Description For PIM-SM, configure this routing device’s priority for becoming an RP.
For bidirectional PIM, configure this RP address’ priority for becoming an RP.
The bootstrap router uses this field when selecting the list of candidate rendezvous points to send in the bootstrap message. A smaller number increases the likelihood that the routing device or RP address becomes the RP. A priority value of 0 means that bootstrap router can override the group range being advertised by the candidate RP.
Options number —Priority for becoming an RP. A lower value corresponds to a higher priority.
Range: 0 through 255
Default: 1
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Local PIM RPs on page 55
• Example: Configuring Bidirectional PIM
Copyright © 2016, Juniper Networks, Inc.
235
Multicast Protocols Feature Guide for EX4600 Switches propagation-delay
Syntax propagation-delay milliseconds;
Hierarchy Level [edit protocols pim],
[edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim interface interface-name],
[edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced in Junos OS Release 10.1.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Set a delay for implementing a PIM prune message on the upstream routing device on a multicast network for which join suppression has been enabled. The routing device waits for the prune pending period to detect whether a join message is currently being suppressed by another routing device.
Options milliseconds —Interval for the prune pending timer, which is the sum of the propagation-delay value and the override-interval value.
Range: 250 through 2000 milliseconds
Default: 500 milliseconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Enabling Join Suppression on page 31
•
•
reset-tracking-bit on page 237
236 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements reset-tracking-bit
Syntax reset-tracking-bit;
Hierarchy Level [edit protocols pim],
[edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim interface interface-name],
[edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name]
Release Information Statement introduced in Junos OS Release 10.1.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Change the value of a tracking bit (T-bit) field in the LAN prune delay hello option from the default of 1 to 0, which enables join suppression for a multicast interface. When the network starts receiving multiple identical join messages, join suppression triggers a random timer with a value of 66 through 84 milliseconds (1.1 × periodic through 1.4 × periodic, where periodic is 60 seconds). This creates an interval during which no identical join messages are sent. Eventually, only one of the identical messages is sent. Join suppression is triggered each time identical messages are sent for the same join.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Enabling Join Suppression on page 31
•
•
Copyright © 2016, Juniper Networks, Inc.
237
Multicast Protocols Feature Guide for EX4600 Switches rib-group (Protocols PIM)
Syntax rib-group { inet group-name; inet6 group-name;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Associate a routing table group with PIM.
Options table-name —Name of the routing table. The name must be one that you defined with the rib-groups statement at the [edit routing-options] hierarchy level.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring a Dedicated PIM RPF Routing Table
238 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements rp
Syntax
{ auto-rp {
(announce | discovery | mapping);
(mapping-agent-election | no-mapping-agent-election);
} bidirectional { address address {
{
destination-ip-prefix</prefix-length>;
}
seconds;
number;
}
}
{
(inet | inet6) {
[ policy-names ];
[ policy-names ];
number;
}
}
[ policy-names ];
[ policy-names ];
number;
[ policy-names ];
{
{
destination-ip-prefix</prefix-length>;
}
limit;
} group-rp-mapping { family (inet | inet6) { log-interval seconds; maximum limit; threshold value;
}
} log-interval seconds; maximum limit; threshold value;
}
}
{
(inet | inet6) {
address;
{
address;
address <forward-msdp-sa>;
{
}
Copyright © 2016, Juniper Networks, Inc.
239
Multicast Protocols Feature Guide for EX4600 Switches
}
}
{
destination-ip-prefix</prefix-length>;
}
seconds; override;
number;
}
} register-limit { family (inet | inet6) { log-interval seconds; maximum limit; threshold value;
}
} log-interval seconds; maximum limit; threshold value;
}
} register-probe-time register-probe-time;
}
[ policy-names ];
{
address { override;
version;
{
destination-ip-prefix</prefix-length>;
}
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the routing device as an actual or potential RP. A routing device can be an RP for more than one group.
The remaining statements are explained separately.
Default If you do not include the rp statement, the routing device can never become the RP.
240 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Understanding PIM Sparse Mode on page 23
rp-register-policy
Syntax rp-register-policy [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced in Junos OS Release 7.6.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more policies to control incoming PIM register messages.
Options policy-names —Name of one or more import policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring Register Message Filters on a PIM RP and DR on page 79
•
dr-register-policy on page 201
Copyright © 2016, Juniper Networks, Inc.
241
Multicast Protocols Feature Guide for EX4600 Switches rp-set
Syntax rp-set {
address <forward-msdp-sa>;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
(inet | inet6)
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
(inet | inet6)
[edit protocols pim
(inet | inet6)
[edit routing-instances routing-instance-name protocols pim
(inet | inet6)
Release Information Statement introduced in Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure a set of rendezvous point (RP) addresses for anycast RP. You can configure up to 15 RPs.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring PIM Anycast With or Without MSDP on page 60
242 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements rpf-selection
Syntax rpf-selection {
group-address {
source-address {
next-hop-address;
}
{
next-hop-address;
}
}
prefix-list-addresses {
source-address {
next-hop-address;
}
{
next-hop-address;
}
}
Hierarchy Level [edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced in JUNOS Release 10.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the PIM RPF next-hop neighbor for a specific group and source for a VRF routing instance.
The remaining statements are explained separately.
Default If you omit the rpf-selection statement, PIM RPF checks typically choose the best path determined by the unicast protocol for all multicast flows.
Options source-address —Specific source address for the PIM group.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
• Example: Configuring PIM RPF Selection
Copyright © 2016, Juniper Networks, Inc.
243
Multicast Protocols Feature Guide for EX4600 Switches source (PIM RPF Selection)
Syntax source source-address {
next-hop-address;
}
Hierarchy Level [edit routing-instances routing-instance-name protocols pim rpf-selection group
group-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list
prefix-list-addresses]
Release Information Statement introduced in JUNOS Release 10.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the source address for the PIM group.
Options source-address —Specific source address for the PIM group.
The remaining statements are explained separately.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
• Example: Configuring PIM RPF Selection
244 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements spt-threshold
Syntax spt-threshold {
[ policy-names ];
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced in Junos OS Release 8.0.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Set the SPT threshold to infinity for a source-group address pair. Last-hop multicast routing devices running PIM sparse mode can forward the same stream of multicast packets onto the same LAN through an RPT rooted at the RP or an SPT rooted at the source. By default, last-hop routing devices transition to a direct SPT to the source. You can configure this routing device to set the SPT transition value to infinity to prevent this transition for any source-group address pair.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring the PIM SPT Threshold Policy on page 92
Copyright © 2016, Juniper Networks, Inc.
245
Multicast Protocols Feature Guide for EX4600 Switches static (Protocols PIM)
Syntax static {
address {
{
destination-ip-prefix</prefix-length>;
} override;
version;
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
],
[edit protocols pim
[edit routing-instances routing-instance-name protocols pim
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure static RP addresses. The default static RP address is 224.0.0.0/4. To configure other addresses, include one or more address statements. You can configure a static RP in a logical system only if the logical system is not directly connected to a source.
For each static RP address, you can optionally specify the PIM version and the groups for which this address can be the RP. The default PIM version is version 1.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring the Static PIM RP Address on the Non-RP Routing Device on page 57
246 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements threshold (PIM BFD Detection Time)
Syntax threshold milliseconds;
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection detection-time],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection detection-time]
Release Information Statement introduced in Junos OS Release 8.2.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for BFD authentication introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the threshold for the adaptation of the BFD session detection time. When the detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent.
NOTE: The threshold value must be equal to or greater than the transmit interval.
The threshold time must be equal to or greater than the value specified in the
or the
statement.
Options milliseconds —Value for the detection time adaptation threshold.
Range: 1 through 255,000
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
•
bfd-liveness-detection on page 194
•
•
•
minimum-receive-interval on page 225
Copyright © 2016, Juniper Networks, Inc.
247
Multicast Protocols Feature Guide for EX4600 Switches threshold (PIM BFD Transmit Interval)
Syntax threshold milliseconds;
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection transmit-interval],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection transmit-interval]
Release Information Statement introduced in Junos OS Release 8.2.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the threshold for the adaptation of the BFD session transmit interval. When the transmit interval adapts to a value greater than the threshold, a single trap and a single system message are sent.
Options milliseconds —Value for the transmit interval adaptation threshold.
Range: 0 through 4,294,967,295 (2
32
– 1)
NOTE: The threshold value specified in the threshold statement must be greater than the value specified in the minimum-interval statement for the transmit-interval statement.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
•
bfd-liveness-detection on page 194
248 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements transmit-interval (PIM BFD Liveness Detection)
Syntax transmit-interval {
milliseconds;
milliseconds;
}
Hierarchy Level [edit protocols pim interface interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-liveness-detection]
Release Information Statement introduced in Junos OS Release 8.2.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for BFD authentication introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the transmit interval for the bfd-liveness-detection statement. The negotiated transmit interval for a peer is the interval between the sending of BFD packets to peers.
The receive interval for a peer is the minimum interval between receiving packets sent from its peer; the receive interval is not negotiated between peers. To determine the transmit interval, each peer compares its configured minimum transmit interval with its peer's minimum receive interval. The larger of the two numbers is accepted as the transmit interval for that peer.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
•
bfd-liveness-detection on page 194
•
•
•
minimum-receive-interval on page 225
Copyright © 2016, Juniper Networks, Inc.
249
Multicast Protocols Feature Guide for EX4600 Switches traceoptions (Protocols PIM)
Syntax traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
Hierarchy Level [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure PIM tracing options.
To specify more than one tracing operation, include multiple flag statements.
Default The default PIM trace options are those inherited from the routing protocol's traceoptions statement included at the [edit routing-options] hierarchy level.
Options disable —(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all.
file filename —Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place tracing output in the pim-log file.
files number —(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
If you specify a maximum number of files, you must also include the size statement to specify the maximum file size.
Range: 2 through 1000 files
Default: 2 files flag flag —Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements.
PIM Tracing Flags
• assert —Assert messages
• bidirectional-df-election —Bidirectional PIM designated-forwarder (DF) election events
250 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements
• bootstrap —Bootstrap messages
• cache —Packets in the PIM sparse mode routing cache
• graft —Graft and graft acknowledgment messages
• hello —Hello packets
• join —Join messages
• mt —Multicast tunnel messages
• nsr-synchronization —Nonstop active routing (NSR) synchronization messages
• packets —All PIM packets
• prune —Prune messages
• register —Register and register stop messages
• rp —Candidate RP advertisements
• all —All tracing operations
• general —A combination of the normal and route trace operations
• normal —All normal operations
Default: If you do not specify this option, only unusual or abnormal operations are traced.
• policy —Policy operations and actions
• route —Routing table changes
• state —State transitions
• task —Interface transactions and processing
• timer —Timer usage flag-modifier —(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers:
• detail —Detailed trace information
• receive —Packets being received
• send —Packets being transmitted no-stamp —(Optional) Do not place timestamp information at the beginning of each line in the trace file.
Default: If you omit this option, timestamp information is placed at the beginning of each line of the tracing output.
Copyright © 2016, Juniper Networks, Inc.
251
Multicast Protocols Feature Guide for EX4600 Switches no-world-readable —(Optional) Do not allow users to read the log file.
replace —(Optional) Replace an existing trace file if there is one.
Default: If you do not include this option, tracing output is appended to an existing trace file.
size size —(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0
. When trace-file again reaches this size, trace-file.0 is renamed trace-file.1
and trace-file is renamed trace-file.0. This renaming scheme continues until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
If you specify a maximum file size, you must also include the files statement to specify the maximum number of trace files.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 0 KB through the maximum file size supported on your system
Default: 1 MB world-readable —(Optional) Allow any user to read the log file.
Required Privilege
Level routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration.
Related
Documentation
•
Configuring PIM Trace Options on page 10
• Tracing DVMRP Protocol Traffic
•
Tracing MSDP Protocol Traffic on page 168
•
Configuring PIM Trace Options on page 10
252 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements version (BFD)
Syntax version (0 | 1 | automatic);
Hierarchy Level [edit protocols piminterface interface-name
[edit routing-instances routing-instance-name protocols pim interface interface-name
]
Release Information Statement introduced in Junos OS Release 8.1.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the bidirectional forwarding detection (BFD) protocol version that you want to detect.
Options Configure the BFD version to detect: 1 (BFD version 1) or automatic (autodetect the BFD version)
Default: automatic
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring BFD for PIM on page 16
Copyright © 2016, Juniper Networks, Inc.
253
Multicast Protocols Feature Guide for EX4600 Switches version (PIM)
Syntax version version;
Hierarchy Level [edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name protocols pim
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
address],
[edit protocols pim interface interface-name],
[edit protocols pim
address],
[edit routing-instances routing-instance-name protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the version of PIM.
Options version —PIM version number.
Range: 1 or 2
Default: PIMv1 for rendezvous point (RP) mode (at the [edit protocols pim rp static address address] hierarchy level). PIMv2 for interface mode (at the [edit protocols pim interface interface-name] hierarchy level).
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Enabling PIM Sparse Mode on page 26
• Configuring PIM Dense Mode Properties
• Configuring PIM Sparse-Dense Mode Properties
254 Copyright © 2016, Juniper Networks, Inc.
Chapter 13: PIM Configuration Statements wildcard-source (PIM RPF Selection)
Syntax wildcard-source {
next-hop-address;
}
Hierarchy Level [edit routing-instances routing-instance-name protocols pim rpf-selection group
group-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list
prefix-list-addresses]
Release Information Statement introduced in Junos OS Release 10.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Use a wildcard for the multicast source instead of (or in addition to) a specific multicast source.
The remaining statements are explained separately.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
• Example: Configuring PIM RPF Selection
Copyright © 2016, Juniper Networks, Inc.
255
Multicast Protocols Feature Guide for EX4600 Switches
256 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 14
IGMP Configuration Statements
•
accounting (Protocols IGMP) on page 258
•
accounting (Protocols IGMP Interface) on page 258
•
•
disable (Protocols IGMP) on page 259
•
exclude (Protocols IGMP) on page 260
•
group (Protocols IGMP) on page 261
•
group-count (Protocols IGMP) on page 262
•
group-increment (Protocols IGMP) on page 262
•
group-limit (IGMP) on page 263
•
group-policy (Protocols IGMP) on page 264
•
•
immediate-leave (Protocols IGMP) on page 267
•
interface (Protocols IGMP) on page 268
•
maximum-transmit-rate (Protocols IGMP) on page 269
•
oif-map (IGMP Interface) on page 269
•
•
promiscuous-mode (Protocols IGMP) on page 271
•
query-interval (Protocols IGMP) on page 272
•
query-last-member-interval (Protocols IGMP) on page 273
•
query-response-interval (Protocols IGMP) on page 274
•
robust-count (Protocols IGMP) on page 275
•
source (Protocols IGMP) on page 276
•
source-count (Protocols IGMP) on page 277
•
source-increment (Protocols IGMP) on page 278
•
static (Protocols IGMP) on page 279
•
traceoptions (Protocols IGMP) on page 280
•
version (Protocols IGMP) on page 282
Copyright © 2016, Juniper Networks, Inc.
257
Multicast Protocols Feature Guide for EX4600 Switches accounting (Protocols IGMP)
Syntax accounting;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit protocols
]
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable the collection of IGMP join and leave event statistics on the system.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Recording IGMP Join and Leave Events on page 119
accounting (Protocols IGMP Interface)
Syntax (accounting | no-accounting);
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable or disable the collection of IGMP join and leave event statistics for an interface.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Recording IGMP Join and Leave Events on page 119
258 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements asm-override-ssm
Syntax asm-override-ssm;
Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast]
Release Information Statement introduced in Junos OS Release 9.4.
Statement introduced in Junos OS Release 9.5 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable the routing device to accept any-source multicast join messages (*,G) for group addresses that are within the default or configured range of source-specific multicast groups.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring Source-Specific Multicast Groups with Any-Source Override on page 46
disable (Protocols IGMP)
Syntax disable;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Disable IGMP on the system.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Copyright © 2016, Juniper Networks, Inc.
259
Multicast Protocols Feature Guide for EX4600 Switches exclude (Protocols IGMP)
Syntax exclude;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name
multicast-group-address],
[edit protocols
interface-name
multicast-group-address]
Release Information Statement introduced in Junos OS Release 9.3.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the static group to operate in exclude mode. In exclude mode all sources except the address configured are accepted for the group. If this statement is not included, the group operates in include mode.
Required Privilege
Level view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
260 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements group (Protocols IGMP)
Syntax group multicast-group-address {
number;
increment;
ip-address {
number;
increment;
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name
[edit protocols
interface-name
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the IGMP multicast group address and (optionally) the source address for the multicast group being statically configured on an interface.
NOTE: You must specify a unique address for each group.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
Copyright © 2016, Juniper Networks, Inc.
261
Multicast Protocols Feature Guide for EX4600 Switches group-count (Protocols IGMP)
Syntax group-count number;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name
multicast-group-address],
[edit protocols
interface-name
multicast-group-address]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the number of static groups to be created.
Options number —Number of static groups.
Range: 1 through 512
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
group-increment (Protocols IGMP)
Syntax group-increment increment;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name
multicast-group-address],
[edit protocols
interface-name
multicast-group-address]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the number of times the address should be incremented for each static group created. The increment is specified in dotted decimal notation similar to an IPv4 address.
Options increment —Number of times the address should be incremented.
Default: 0.0.0.1
Range: 0.0.0.1 through 255.255.255.255
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
262 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements group-limit (IGMP)
Syntax group-limit limit;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 10.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure a limit for the number of multicast groups (or [S,G] channels in IGMPv3) allowed on an interface. After this limit is reached, new reports are ignored and all related flows are not flooded on the interface.
To confirm the configured group limit on the interface, use the
command.
Default By default, there is no limit to the number of multicast groups that can join the interface.
Options limit —group limit value for the interface.
Range: 1 through 32767
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces on page 120
• group-threshold
• log-interval
Copyright © 2016, Juniper Networks, Inc.
263
Multicast Protocols Feature Guide for EX4600 Switches group-policy (Protocols IGMP)
Syntax group-policy [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 9.1.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description When this statement is enabled on a router running IGMP version 2 (IGMPv2) or version 3
(IGMPv3), after the router receives an IGMP report, the router compares the group against the specified group policy and performs the action configured in that policy (for example, rejects the report).
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Filtering Unwanted IGMP Reports at the IGMP Interface Level on page 108
264 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements igmp
Syntax igmp {
;
interface-name {
(
limit;
[ policy-names ]; group-threshold
log-interval
map-name;
ssm-map-name;
ssm-map-policy-name;
{
multicast-group-address {
number;
increment;
ip-address {
number;
increment;
}
}
}
version;
}
seconds;
seconds;
seconds;
number;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols],
[edit protocols]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Description Enable IGMP on the router or switch. IGMP must be enabled for the router or switch to receive multicast packets.
The remaining statements are explained separately.
Copyright © 2016, Juniper Networks, Inc.
265
Multicast Protocols Feature Guide for EX4600 Switches
Default IGMP is disabled on the router or switch. IGMP is automatically enabled on all broadcast interfaces when you configure Protocol Independent Multicast (PIM) or Distance Vector
Multicast Routing Protocol (DVMRP).
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
266 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements immediate-leave (Protocols IGMP)
Syntax immediate-leave;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 8.3.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description The immediate leave setting is useful for minimizing the leave latency of IGMP memberships. When this setting is enabled, the routing device leaves the multicast group immediately after the last host leaves the multicast group.
Starting in Junos OS Release 9.3, both IGMP version 2 and IGMP version 3 do host tracking when the immediate-leave statement is configured. This means that the multicast group leaves only when the last host leaves. The routing device keeps track of the hosts that send join messages. This allows IGMP to determine when the last host sends a leave message for the multicast group.
When the immediate leave setting is enabled, the device removes an interface from the forwarding-table entry without first sending IGMP group-specific queries to the interface.
The interface is pruned from the multicast tree for the multicast group specified in the
IGMP leave message. The immediate leave setting ensures optimal bandwidth management for hosts on a switched network, even when multiple multicast groups are being used simultaneously.
When immediate leave is disabled and one host sends a leave group message, the routing device first sends a group query to determine if another receiver responds. If no receiver responds, the routing device removes all hosts on the interface from the multicast group.
Immediate leave is disabled by default for both IGMP version 2 and IGMP version 3.
NOTE: Although host tracking is enabled for IGMPv2 and MLDv1 when you enable immediate leave, use immediate leave with these versions only when there is one host on the interface. The reason is that IGMPv2 and MLDv1 use a report suppression mechanism whereby only one host on an interface sends a group join report in response to a membership query. The other interested hosts suppress their reports. The purpose of this mechanism is to avoid a flood of reports for the same group. But it also interferes with host tracking, because the routing device only knows about the one interested host and does not know about the others.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Copyright © 2016, Juniper Networks, Inc.
267
Multicast Protocols Feature Guide for EX4600 Switches
Related
Documentation
•
Specifying Immediate-Leave Host Removal for IGMP on page 107
interface (Protocols IGMP)
Syntax interface interface-name {
(
limit;
[ policy-names ];
map-name;
ssm-map-name;
ssm-map-policy-name;
{
multicast-group-address {
number;
increment;
ip-address {
number;
increment;
}
}
}
version;
}
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable IGMP on an interface and configure interface-specific properties.
Options interface-name —Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all .
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
268 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements maximum-transmit-rate (Protocols IGMP)
Syntax maximum-transmit-rate packets-per-second;
Hierarchy Level [edit logical-systems logical-system-name protocols igmp],
[edit protocols igmp]
Release Information Statement introduced in Junos OS Release 9.3.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Limit the transmission rate of IGMP packets
Options packets-per-second —Maximum number of IGMP packets transmitted in one second by the routing device.
Range: 1 through 10000
Default: 500 packets
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Limiting the Maximum IGMP Message Rate on page 112
oif-map (IGMP Interface)
Syntax oif-map map-name;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Associates an outgoing interface (OIF) map to the IGMP interface. The OIF map is a routing policy statement that can contain multiple terms.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast with Subscriber VLANs
Copyright © 2016, Juniper Networks, Inc.
269
Multicast Protocols Feature Guide for EX4600 Switches passive (IGMP)
Syntax passive <allow-receive> <send-general-query> <send-group-query>;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 9.6.
allow-receive , send-general-query, and send-group-query options were added in Junos
OS Release 10.0.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify that IGMP run on the interface and either not send and receive control traffic or selectively send and receive control traffic such as IGMP reports, queries, and leaves.
NOTE: You can selectively activate up to two out of the three available options for the passive statement while keeping the other functions passive
(inactive). Activating all three options would be equivalent to not using the passive statement.
Options allow-receive —Enables IGMP to receive control traffic on the interface.
send-general-query —Enables IGMP to send general queries on the interface.
send-group-query —Enables IGMP to send group-specific and group-source-specific queries on the interface.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast with Subscriber VLANs
•
270 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements promiscuous-mode (Protocols IGMP)
Syntax promiscuous-mode;
Hierarchy Level [edit dynamic-profiles profile-name protocols igmp interface interface-name],
[edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 8.3.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 9.2 for dynamic profiles.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify that the interface accepts IGMP reports from hosts on any subnetwork. Note that when enabling promiscuous-mode, all routing devices on the ethernet segment must be configured with the promiscuous mode statement. Otherwise, only the interface configured with lowest IPv4 address acts as the querier for IGMP for this Ethernet segment.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Dynamic IGMP Configuration Overview
• Configuring Dynamic DHCP Client Access to a Multicast Network
•
Accepting IGMP Messages from Remote Subnetworks on page 109
Copyright © 2016, Juniper Networks, Inc.
271
Multicast Protocols Feature Guide for EX4600 Switches query-interval (Protocols IGMP)
Syntax query-interval seconds;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify how often the querier routing device sends general host-query messages.
Options seconds—Time interval.
Range: 1 through 1024
Default: 125 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Modifying the IGMP Host-Query Message Interval on page 105
•
query-last-member-interval (Protocols IGMP) on page 273
•
query-response-interval (Protocols IGMP) on page 274
272 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements query-last-member-interval (Protocols IGMP)
Syntax query-last-member-interval seconds;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify how often the querier routing device sends group-specific query messages.
Options seconds —Time interval, in fractions of a second or seconds.
Range: 0.1 through 0.9, then in 1-second intervals 1 through 999999
Default: 1 second
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Modifying the IGMP Last-Member Query Interval on page 106
•
query-interval (Protocols IGMP) on page 272
•
query-response-interval (Protocols IGMP) on page 274
Copyright © 2016, Juniper Networks, Inc.
273
Multicast Protocols Feature Guide for EX4600 Switches query-response-interval (Protocols IGMP)
Syntax query-response-interval seconds;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify how long the querier routing device waits to receive a response to a host-query message from a host.
Options seconds —The query response interval must be less than the query interval.
Range: 1 through 1024
Default: 10 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Modifying the IGMP Query Response Interval on page 110
•
query-interval (Protocols IGMP) on page 272
•
query-last-member-interval (Protocols IGMP) on page 273
274 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements robust-count (Protocols IGMP)
Syntax robust-count number;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Tune the expected packet loss on a subnet. This factor is used to calculate the group member interval, other querier present interval, and last-member query count.
Options number —Robustness variable.
Range: 2 through 10
Default: 2
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Modifying the IGMP Robustness Variable on page 111
Copyright © 2016, Juniper Networks, Inc.
275
Multicast Protocols Feature Guide for EX4600 Switches source (Protocols IGMP)
Syntax source ip-address {
number;
increment;
}
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name
multicast-group-address],
[edit protocols
interface-name
multicast-group-address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the IP version 4 (IPv4) unicast source address for the multicast group being statically configured on an interface.
Options ip-address —IPv4 unicast address.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
276 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements source-count (Protocols IGMP)
Syntax source-count number;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name
multicast-group-address
[edit protocols
interface-name
multicast-group-address
]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the number of multicast source addresses that should be accepted for each static group created.
Options number —Number of source addresses.
Default: 1
Range: 1 through 1024
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
Copyright © 2016, Juniper Networks, Inc.
277
Multicast Protocols Feature Guide for EX4600 Switches source-increment (Protocols IGMP)
Syntax source-increment number;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name
multicast-group-address
[edit protocols
interface-name
multicast-group-address
]
Release Information Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the number of times the multicast source address should be incremented for each static group created. The increment is specified in dotted decimal notation similar to an IPv4 address.
Options increment —Number of times the source address should be incremented.
Default: 0.0.0.1
Range: 0.0.0.1 through 255.255.255.255
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
278 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements static (Protocols IGMP)
Syntax static {
multicast-group-address { exclude;
number;
increment;
ip-address {
number;
increment;
}
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Test multicast forwarding on an interface without a receiver host.
The static statement simulates IGMP joins on a routing device statically on an interface without any IGMP hosts. It is supported for both IGMPv2 and IGMPv3 joins. This statement is especially useful for testing multicast forwarding on an interface without a receiver host.
NOTE: To prevent joining too many groups accidentally, the static statement is not supported with the interface all statement.
The remaining statements are explained separately.
Required Privilege
Level routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration.
Related
Documentation
•
Enabling IGMP Static Group Membership on page 112
Copyright © 2016, Juniper Networks, Inc.
279
Multicast Protocols Feature Guide for EX4600 Switches traceoptions (Protocols IGMP)
Syntax traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure IGMP tracing options.
To specify more than one tracing operation, include multiple flag statements.
To trace the paths of multicast packets, use the mtrace command.
Default The default IGMP trace options are those inherited from the routing protocols traceoptions statement included at the [edit routing-options] hierarchy level.
Options disable —(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all.
file filename —Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place tracing output in the file igmp-log.
files number —(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
If you specify a maximum number of files, you must also include the size statement to specify the maximum file size.
Range: 2 through 1000 files
Default: 2 files flag —Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements.
IGMP Tracing Flags
• leave —Leave group messages (for IGMP version 2 only).
• mtrace —Mtrace packets. Use the mtrace command to troubleshoot the software.
280 Copyright © 2016, Juniper Networks, Inc.
Chapter 14: IGMP Configuration Statements
• packets —All IGMP packets.
• query —IGMP membership query messages, including general and group-specific queries.
• report —Membership report messages.
Global Tracing Flags
• all —All tracing operations
• general —A combination of the normal and route trace operations
• normal —All normal operations
Default: If you do not specify this option, only unusual or abnormal operations are traced.
• policy —Policy operations and actions
• route —Routing table changes
• state —State transitions
• task —Interface transactions and processing
• timer —Timer usage flag-modifier —(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers:
• detail —Detailed trace information
• receive —Packets being received
• send —Packets being transmitted no-stamp —(Optional) Do not place timestamp information at the beginning of each line in the trace file.
Default: If you omit this option, timestamp information is placed at the beginning of each line of the tracing output.
no-world-readable —(Optional) Do not allow users to read the log file.
replace —(Optional) Replace an existing trace file if there is one.
Default: If you do not include this option, tracing output is appended to an existing trace file.
size size —(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0
. When trace-file again reaches this size, trace-file.0 is renamed trace-file.1
and trace-file is renamed trace-file.0. This renaming scheme continues until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
Copyright © 2016, Juniper Networks, Inc.
281
Multicast Protocols Feature Guide for EX4600 Switches
If you specify a maximum file size, you must also include the files statement to specify the maximum number of trace files.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through the maximum file size supported on your system
Default: 1 MB world-readable —(Optional) Allow any user to read the log file.
Required Privilege
Level routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration.
Related
Documentation
•
Tracing IGMP Protocol Traffic on page 121
version (Protocols IGMP)
Syntax version version;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Specify the version of IGMP.
Options version —IGMP version number.
Range: 1, 2, or 3
Default: IGMP version 2
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Changing the IGMP Version on page 104
282 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 15
IGMP Snooping Configuration Statements
•
•
disable (IGMP Snooping) on page 284
•
group (IGMP Snooping) on page 285
•
group-limit (IGMP and MLD Snooping) on page 286
•
groups (Multicast VLAN Registration) on page 287
•
host-only-interface on page 288
•
•
•
immediate-leave (Bridge Domains) on page 291
•
install (Multicast VLAN Registration) on page 292
•
interface (IGMP Snooping) on page 293
•
interface (Bridge Domains) on page 294
•
•
multicast-router-interface (IGMP Snooping) on page 295
•
proxy (Multicast VLAN Registration) on page 296
•
query-interval (Bridge Domains) on page 297
•
query-last-member-interval (Bridge Domains) on page 298
•
query-response-interval (Bridge Domains) on page 299
•
•
robust-count (IGMP Snooping) on page 300
•
source (Multicast VLAN Registration) on page 301
•
•
src-address (IGMP Querier) on page 302
•
•
static (IGMP Snooping) on page 303
•
traceoptions (IGMP Snooping) on page 304
•
version (IGMP Snooping) on page 306
•
vlan (IGMP Snooping) on page 307
Copyright © 2016, Juniper Networks, Inc.
283
Multicast Protocols Feature Guide for EX4600 Switches data-forwarding
Syntax data-forwarding {
{
vlan-list;
}
{
group-prefix;
}
}
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name)]
Release Information Statement introduced in Junos OS Release 9.6 for EX Series switches.
Statement introduced in Junos OS Release 12.3 for the QFX Series.
Description Configure the VLAN to be a multicast source VLAN (MVLAN) or a multicast VLAN registration (MVR) receiver VLAN. Each data-forwarding VLAN, which can be a multicast source VLAN (MVLAN) or a multicast receiver VLAN, must have exactly one source statement or exactly one receiver statement. A data-forwarding VLAN can operate only in IGMP version 2 (IGMPv2) mode.
The remaining statements are explained separately.
Default Disabled
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure) disable (IGMP Snooping)
Syntax disable;
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name]
Release Information Statement introduced in Junos OS Release 11.1 for the QFX Series.
Description Disable IGMP snooping on all interfaces in a VLAN.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
284 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements group (IGMP Snooping)
Syntax group ip-address;
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name
interface-name
]
Release Information Statement introduced in Junos OS Release 11.1 for the QFX Series.
Description Configure a static multicast group using a valid IP multicast address.
Default None.
Options ip-address —IP address of the multicast group receiving data on an interface.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
show igmp-snooping vlans on page 477
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
Copyright © 2016, Juniper Networks, Inc.
285
Multicast Protocols Feature Guide for EX4600 Switches group-limit (IGMP and MLD Snooping)
Syntax group-limit limit;
Hierarchy Level [edit bridge-domains bridge-domain-name protocols igmp-snooping
interface-name]
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id
interface-name]
[edit bridge-domains bridge-domain-name protocols mld-snooping interface interface-name]
[edit bridge-domains bridge-domain-name protocols mld-snooping vlan mld-snooping-vlan interface interface-name]
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols vlan vlan-id igmp-snooping
interface-name]
[edit protocols igmp-snooping vlan
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Description Configure a limit for the number of multicast groups (or [S,G] channels in IGMPv3) allowed on an interface. After this limit is reached, new reports are ignored and all related flows are not flooded on the interface.
Default By default, there is no limit to the number of multicast groups joining an interface.
Options limit—a 32-bit number for the limit on the interface.
Range: 1 through 32,767. For MX series routers, the range is 1 to 65535. Starting with
Junos OS release 14.2, a value of 0, which was treated as null, is not supported.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping
286 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements groups (Multicast VLAN Registration)
Syntax groups group-prefix;
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name) data-forwarding source]
Release Information Statement introduced in Junos OS Release 9.6 for EX Series switches.
Description Specify the IP address range of the multicast VLAN (MVLAN) source interfaces.
Default Disabled
Options group-prefix—IP address range of the source group. Each MVLAN must have exactly one groups statement. If there are multiple MVLANs on the switch, their group ranges must be unique.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure)
Copyright © 2016, Juniper Networks, Inc.
287
Multicast Protocols Feature Guide for EX4600 Switches host-only-interface
Syntax host-only-interface;
Hierarchy Level [edit bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols vlan vlan-id igmp-snooping
interface-name]
[edit protocols igmp-snooping vlan
[edit protocols mld-snooping vlan vlan-id interface interface-name]
[edit routing-instances routing-instance-name protocols mld-snooping vlan vlan-id interface
interface-name]
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Support at the [edit protocols mld-snooping vlan vlan-id interface interface-name] and the [edit routing-instances routing-instance-name protocols mld-snooping vlan vlan-id interface interface-name] hierarchy levels introduced in Junos OS Release 13.3 for EX
Series switches.
Description Configure an interface as a host-facing interface. IGMP and MLD queries received on these interfaces are dropped.
Default The interface can either be a host-side or multicast-routing device interface.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping
• multicast-router-interface
288 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements igmp-querier
Syntax igmp-querier
source-address source address;
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name]
Release Information Statement introduced in Junos OS Release 14.1X53-D15 for QFabric Systems.
Description Configure a QFabric Node device to be an IGMP querier. If there are any multicast routers on the same local network, make sure the source address for the IGMP querier is lower
(a smaller number) than the IP addresses for those routers on the network. This ensures that Node is always the IGMP querier on the network.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping vlans on page 477
•
show configuration protocols igmp on page 453
Copyright © 2016, Juniper Networks, Inc.
289
Multicast Protocols Feature Guide for EX4600 Switches igmp-snooping
Syntax igmp-snooping { vlan vlan-id { all
interface-name {
limit;
multicast-router-interface; static { group ip-address { source ip-address;
}
}
}
{
ip-address;
} proxy {
ip-address;
}
seconds;
seconds;
seconds; robust-count number; traceoptions { file filename <files number> <no-stamp> <replace> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier>;
}
}
}
Hierarchy Level [edit protocols]
Release Information Statement introduced in Junos OS Release 13.2 for the QFX Series.
Description Enable IGMP snooping on the router or switch.
Default IGMP snooping is disabled on the router or switch.
Options The statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Understanding IGMP Snooping
• IGMP Snooping in MC-LAG Active-Active Mode
290 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements immediate-leave (Bridge Domains)
Syntax immediate-leave;
Hierarchy Level [edit bridge-domains bridge-domain-name protocols igmp-snooping],
[edit bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols vlan vlan-id igmp-snooping
interface-name]
[edit protocols igmp-snooping vlan
[edit bridge-domains bridge-domain-name protocols mld-snooping ] ,
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols mld-snooping ]
[edit routing-instances routing-instance-name protocols mld-snooping ]
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Statement introduced in Junos OS Release 14.2 for MX series Routers with MPC.
Description The immediate leave setting is useful for minimizing the leave latency of IGMP or MLD
(for IPv6) memberships. When this setting is enabled, the routing device leaves the multicast group immediately after the last host leaves the multicast group.
The immediate-leave setting enables host tracking, meaning that the device keeps track of the hosts that send join messages. This allows IGMP or MLD to determine when the last host sends a leave message for the multicast group.
When the immediate leave setting is enabled, the device removes an interface from the forwarding-table entry without first sending IGMP or MLD group-specific queries to the interface. The interface is pruned from the multicast tree for the multicast group specified in the leave message. The immediate leave setting ensures optimal bandwidth management for hosts on a switched network, even when multiple multicast groups are being used simultaneously.
When immediate leave is disabled and one host sends a leave group message, the routing device first sends a group query to determine if another receiver responds. If no receiver responds, the routing device removes all hosts on the interface from the multicast group.
Immediate leave is disabled by default for both IGMP version 2 and IGMP version 3.
NOTE: Although host tracking is enabled for IGMPv2 and MLDv1 when you enable immediate leave, use immediate leave with these versions only when there is one host on the interface. The reason is that IGMPv2 and MLDv1 use a report suppression mechanism whereby only one host on an interface sends a group join report in response to a membership query. The other interested
Copyright © 2016, Juniper Networks, Inc.
291
Multicast Protocols Feature Guide for EX4600 Switches hosts suppress their reports. The purpose of this mechanism is to avoid a flood of reports for the same group. But it also interferes with host tracking, because the routing device only knows about the one interested host and does not know about the others.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping install (Multicast VLAN Registration)
Syntax install;
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name) data-forwarding receiver]
Release Information Statement introduced in Junos OS Release 9.6 for EX Series switches.
Description Install forwarding entries in the multicast receiver VLAN. By default, the multicast VLAN
(MVLAN) installs forwarding entries for MVLAN groups only.
Default Disabled
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure)
292 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements interface (IGMP Snooping)
Syntax interface interface-name {
;
{
ip-address;
}
}
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name]
Release Information Statement introduced in Junos OS Release 11.1 for the QFX Series.
Description Enable IGMP snooping on an interface and configure interface-specific properties.
The remaining statements are explained separately.
Options interface-name —Name of the interface.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping vlans on page 477
Copyright © 2016, Juniper Networks, Inc.
293
Multicast Protocols Feature Guide for EX4600 Switches interface (Bridge Domains)
Syntax interface interface-name {
limit;
multicast-router-interface; static { group ip-address { source ip-address;
}
}
}
Hierarchy Level [edit bridge-domains bridge-domain-name protocols igmp-snooping],
[edit bridge-domains bridge-domain-name protocols mld-snooping ] ,
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols mld-snooping ]
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols vlan vlan-id igmp-snooping]
[edit routing-instances routing-instance-name protocols mld-snooping ]
[edit protocols igmp-snooping vlan],
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Statement introduced in Junos OS Release 14.2 for MX series Routers with MPC.
Description Enable IGMP or MLD snooping on an interface and configure interface-specific properties.
Options interface-name —Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all .
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping
• mld-snooping
• igmp-snooping
294 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements l2-querier
Syntax l2-querier {
ip-address;
}
Hierarchy Level [edit protocols igmp-snooping vlan],
Release Information Statement introduced in Junos OS Release 13.2 for the QFX Series.
Description Configure the switch to be an IGMP querier. Use the source-address statement to configure the source address to use for IGMP snooping queries.
Options seconds —Time interval.
Range: 1 through 1024
Default: 125 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation multicast-router-interface (IGMP Snooping)
Syntax multicast-router-interface;
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name
interface-name]
Release Information Statement introduced in Junos OS Release 11.1 for the QFX Series.
Description Configure an interface to forward IGMP messages to multicast routers.
Default Disabled. If this statement is disabled, the interface drops IGMP messages it receives.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
show igmp-snooping vlans on page 477
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
Copyright © 2016, Juniper Networks, Inc.
295
Multicast Protocols Feature Guide for EX4600 Switches proxy (Multicast VLAN Registration)
Syntax proxy source-address ip-address;
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name)]
Release Information Statement introduced in Junos OS Release 9.6 for EX Series switches.
Description Specify that the VLAN operate in proxy mode. The proxy option is supported only for a
VLAN acting as a data-forwarding source.
Default Disabled
Options source-address ip-address —IP address of the source VLAN to act as proxy.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure)
296 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements query-interval (Bridge Domains)
Syntax query-interval seconds;
Hierarchy Level [edit bridge-domains bridge-domain-name protocols mld-snooping ] ,
[edit bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],[ edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols mld-snooping ]
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id
interface-name]
[edit routing-instances routing-instance-name protocols mld-snooping ]
[edit protocols igmp-snooping vlan]
Release Information Statement introduced before Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Statement introduced in Junos OS Release 14.2 for MX series Routers with MPC.
Description Configure the interval for host-query message timeouts.
Options seconds—Time interval. This value must be greater than the interval set for query-response-interval.
Range: 1 through 1024
Default: 125 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping
•
query-last-member-interval (Bridge Domains) on page 298
•
query-response-interval (Bridge Domains) on page 299
• mld-snooping
• igmp-snooping
Copyright © 2016, Juniper Networks, Inc.
297
Multicast Protocols Feature Guide for EX4600 Switches query-last-member-interval (Bridge Domains)
Syntax query-last-member-interval seconds;
Hierarchy Level [edit bridge-domains bridge-domain-name protocols mld-snooping ] ,
[edit bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols mld-snooping ]
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id
[edit routing-instances routing-instance-name protocols mld-snooping ]
interface-name]
[edit protocols igmp-snooping vlan],
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Statement introduced in Junos OS Release 14.2 for MX series Routers with MPC.
Description Configure the interval for group-specific query timeouts.
Options seconds —Time interval, in fractions of a second or seconds.
Range: 0.1 through 0.9, then in 1-second intervals 1 through 1024
Default: 1 second
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping
•
•
query-response-interval on page 299
• mld-snooping
• igmp-snooping
298 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements query-response-interval (Bridge Domains)
Syntax query-response-interval seconds;
Hierarchy Level [edit bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snoopingvlan vlan-id
interface-name],
[edit bridge-domains bridge-domain-name protocols mld-snooping ] ,
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping
interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snoopingvlan vlan-id
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols
interface-name]
[edit routing-instances routing-instance-name protocols mld-snooping ]
[edit protocols igmp-snooping vlan],
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Statement introduced in Junos OS Release 14.2 for MX series Routers with MPC.
Description Specify how long to wait to receive a response to a specific query message from a host.
Options seconds—Time interval. This interval should be less than the host-query interval.
Range: 1 through 1024
Default: 10 seconds
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping
•
query-interval (Bridge Domains) on page 297
•
query-last-member-interval (Bridge Domains) on page 298
• mld-snooping
• igmp-snooping
Copyright © 2016, Juniper Networks, Inc.
299
Multicast Protocols Feature Guide for EX4600 Switches receiver
Syntax receiver {
vlan-list;
}
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name) data-forwarding]
Release Information Statement introduced in Junos OS Release 9.6 for EX Series switches.
Statement introduced in Junos OS Release 12.3 for the QFX Series.
Description Configure a VLAN as a multicast receiver VLAN of the multicast VLAN (MVLAN).
The remaining statements are explained separately.
Default Disabled
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure) robust-count (IGMP Snooping)
Syntax robust-count number;
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name]
Release Information Statement introduced in Junos OS Release 11.1 for the QFX Series.
Description Configure the number of intervals the switch waits before removing a multicast group from the multicast forwarding table. Configure the length of each interval using the query-interval statement.
Default 2 intervals
Options number —Number of intervals the switch waits before timing out a multicast group.
Range: 2 through 10
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping vlans on page 477
300 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements source (Multicast VLAN Registration)
Syntax source {
group-prefix;
}
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name) data-forwarding]
Release Information Statement introduced in Junos OS Release 9.6 for EX Series switches.
Description Configure a VLAN to be a multicast source VLAN (MVLAN).
The remaining statement is explained separately.
Default Disabled
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure) source-address
Syntax source-address ip-address;
Hierarchy Level [edit bridge-domains bridge-domain-name protocols igmp-snooping proxy],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id proxy],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping proxy],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id proxy]
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Description Specify the IP address to use as the source for IGMP snooping reports in proxy mode.
Reports are sent with address 0.0.0.0 as the source address unless there is a source address configured. You can also use this statement to configure the source address to use for IGMP snooping queries.
Options ip-address —IP address to use as the source for proxy-mode IGMP snooping reports.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring IGMP Snooping
Copyright © 2016, Juniper Networks, Inc.
301
Multicast Protocols Feature Guide for EX4600 Switches src-address (IGMP Querier)
Syntax src-address source address;
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name
[edit protocols igmp-snooping vlan vlan-name
Release Information Statement introduced in Junos OS Release 12.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D15 for QFabric Systems.
Description Configure the address that the switch uses as the source address in the IGMP queries that it sends. If there are any multicast routers on the same local network, make sure the source address for the IGMP querier is smaller (a lower number) than the IP addresses for those routers on the network. This ensures that switch is always the IGMP querier on the network.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping vlans on page 477
•
show configuration protocols igmp on page 453
source-vlans
Syntax source-vlans vlan-list;
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name) data-forwarding receiver]
Release Information Statement introduced in Junos OS Release 9.6 for EX Series switches.
Statement introduced in Junos OS Release 12.3 for the QFX Series.
Description Specify a list of multicast VLANs (MVLANs) from which this multicast receiver VLAN receives multicast traffic. Either all of these MVLANs must be in proxy mode or none of them can be in proxy mode.
Default Disabled
Options vlan-list —Names of the MVLANs.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring Multicast VLAN Registration
• Configuring Multicast VLAN Registration (CLI Procedure)
302 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements static (IGMP Snooping)
Syntax static {
ip-address;
}
Hierarchy Level [edit protocols igmp-snooping vlan vlan-name
interface-name]
Release Information Statement introduced in Junos OS Release 11.1 for the QFX Series.
Description Statically define multicast groups on an interface.
The remaining statement is explained separately.
Default No multicast groups are statically defined.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping vlans on page 477
Copyright © 2016, Juniper Networks, Inc.
303
Multicast Protocols Feature Guide for EX4600 Switches traceoptions (IGMP Snooping)
Syntax traceoptions { file filename <files number> <no-stamp> <size size> <replace> <world-readable | no-world-readable>; flag flag (detail | disable | receive | send);
}
Hierarchy Level For platforms without ELS:
[edit protocols igmp-snooping]
For platforms with ELS:
[edit protocols igmp-snooping vlan]
Release Information Statement introduced in Junos OS Release 11.1 for the QFX Series.
Description Define tracing operations for IGMP snooping.
Default The traceoptions feature is disabled by default.
Options file filename —Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log.
files number —(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached (xk to specify KB, xm to specify MB, or xg to specify gigabytes), at which point the oldest trace file is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the size option.
Range: 2 through 1000
Default: 3 files flag flag —Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:
• all —All tracing operations.
• general —Trace general IGMP snooping protocol events.
• krt —Trace communication over routing sockets.
• nexthop — Trace next-hop related events.
• normal —Trace normal IGMP snooping protocol events.
• packets —Trace all IGMP packets.
• policy —Trace policy processing.
• query —Trace IGMP membership query messages.
• report —Trace membership report messages.
304 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements
• route —Trace routing information.
• state —Trace IGMP state transitions.
• task —Trace routing protocol task processing.
• timer —Trace routing protocol timer processing.
• vlan —Trace VLAN related events.
no-stamp —(Optional) Do not time stamp trace file.
no-world-readable —(Optional) Restrict file access to the user who created the file.
size size —(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten. If you specify a maximum number of files, you also must specify a maximum file size with the files option. Use xk to specify KB, xm to specify MB, or xg to specify gigabytes.
Range: 10 KB through 1 gigabytes
Default: 128 KB world-readable —(Optional) Enable unrestricted file access.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring IGMP Snooping on page 130
•
Configuring IGMP Snooping on page 128
Copyright © 2016, Juniper Networks, Inc.
305
Multicast Protocols Feature Guide for EX4600 Switches version (IGMP Snooping)
Syntax version number;
Hierarchy Level [edit protocols igmp-snooping vlan (all | vlan-name)]
Release Information Statement introduced in Junos OS Release 11.1 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Description Specify the IGMP version for the IGMP general query that the switch sends to hosts when an interface comes up. The configured IGMP version affects only the version of the general queries sent by a switch. It does not affect the version of IGMP messages that the switch can snoop. For example, If the switch is configured for IGMP version 1 (IGMPv1), it can snoop IGMPv2 and IGMPv3 messages.
Default If you do not configure the version statement, the default is IGMPv2.
Options version —IGMP version number.
Range: 1 and 2.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Configuring IGMP Snooping (CLI Procedure)
•
Configuring IGMP Snooping on page 128
306 Copyright © 2016, Juniper Networks, Inc.
Chapter 15: IGMP Snooping Configuration Statements vlan (IGMP Snooping)
Syntax vlan vlan-name {
interface-name {
limit;
multicast-router-interface; static { group multicast-group-address { source ip-address;
}
}
} qualified-vlan ; proxy {
ip-address;
}
seconds;
seconds;
seconds; robust-count number;
}
Hierarchy Level [edit protocols igmp-snooping ],
Release Information Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 13.2 for the QFX series.
Description Configure IGMP snooping parameters for a particular VLAN.
Default By default, IGMP snooping options apply to all VLANs.
Options vlan-name —Apply the parameters to this VLAN.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Configuring VLAN-Specific IGMP Snooping Parameters on page 129
•
Copyright © 2016, Juniper Networks, Inc.
307
Multicast Protocols Feature Guide for EX4600 Switches
308 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 16
MSDP Configuration Statements
•
active-source-limit on page 310
•
authentication-key on page 311
•
data-encapsulation on page 312
•
•
disable (Protocols MSDP) on page 314
•
export (Protocols MSDP) on page 315
•
group (Protocols MSDP) on page 316
•
import (Protocols MSDP) on page 317
•
local-address (Protocols MSDP) on page 318
•
maximum (MSDP Active Source Messages) on page 319
•
mode (Protocols MSDP) on page 320
•
•
peer (Protocols MSDP) on page 323
•
rib-group (Protocols MSDP) on page 324
•
source (Protocols MSDP) on page 325
•
threshold (MSDP Active Source Messages) on page 326
•
traceoptions (Protocols MSDP) on page 327
Copyright © 2016, Juniper Networks, Inc.
309
Multicast Protocols Feature Guide for EX4600 Switches active-source-limit
Syntax active-source-limit { log-interval seconds; log-warning value;
number;
number;
}
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name protocols
ip-address/prefix-length],
[edit logical-systems logical-system-name routing-instances instance-name protocols
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ip-address/prefix-length],
[edit protocols
],
[edit protocols
group-name
address],
[edit protocols
address],
[edit protocols
ip-address/prefix-length],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address],
[edit routing-instances routing-instance-name protocols
ip-address/prefix-length]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Limit the number of active source messages the routing device accepts.
Default If you do not include this statement, the router accepts any number of MSDP active source messages.
Options The options are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
310 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements authentication-key
Syntax authentication-key peer-key;
Hierarchy Level [edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit protocols
group-name
address],
[edit protocols
address],
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Associate a Message Digest 5 (MD5) signature option authentication key with an MSDP peering session.
Default If you do not include this statement, the routing device accepts any valid MSDP messages from the peer address.
Options peer-key —MD5 authentication key. The peer key can be a text string up to 16 letters and digits long. Strings can include any ASCII characters with the exception of (, ), &, and
[. If you include spaces in an MSDP authentication key, enclose all characters in quotation marks (“ ”).
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance
Copyright © 2016, Juniper Networks, Inc.
311
Multicast Protocols Feature Guide for EX4600 Switches data-encapsulation
Syntax data-encapsulation (disable | enable);
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit protocols
],
[edit routing-instances routing-instance-name protocols
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure a rendezvous point (RP) using MSDP to encapsulate multicast data received in MSDP register messages inside forwarded MSDP source-active messages.
Default If you do not include this statement, the RP encapsulates multicast data.
Options disable —(Optional) Do not use MSDP data encapsulation.
enable —Use MSDP data encapsulation.
Default: enable
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
312 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements default-peer
Syntax default-peer;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit protocols
],
[edit protocols
group-name],
[edit protocols
group-name
address],
[edit protocols
address],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name],
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Establish this peer as the default MSDP peer and accept source-active messages from the peer without the usual peer-reverse-path-forwarding (peer-RPF) check.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
Copyright © 2016, Juniper Networks, Inc.
313
Multicast Protocols Feature Guide for EX4600 Switches disable (Protocols MSDP)
Syntax disable;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit protocols
],
[edit protocols
group-name],
[edit protocols
group-name
address],
[edit protocols
address],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name],
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Explicitly disable MSDP.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Disabling MSDP
314 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements export (Protocols MSDP)
Syntax export [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit protocols
],
[edit protocols
group-name],
[edit protocols
group-name
address],
[edit protocols
address],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name],
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more policies to routes being exported from the routing table into MSDP.
Options policy-names —Name of one or more policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance
•
Copyright © 2016, Juniper Networks, Inc.
315
Multicast Protocols Feature Guide for EX4600 Switches group (Protocols MSDP)
Syntax group group-name {
[ policy-names ];
[ policy-names ];
address;
(mesh-group | standard);
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
address; {
{
number;
number;
}
peer-key;
[ policy-names ];
[ policy-names ];
address;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit protocols
],
[edit routing-instances routing-instance-name protocols
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Define an MSDP peer group. MSDP peers within groups share common tracing options, if present and not overridden for an individual peer with the
statement. To configure multiple MSDP groups, include multiple group statements.
By default, the group's options are identical to the global MSDP options. To override the global options, include group-specific options within the group statement.
The group must contain at least one peer.
Options group-name —Name of the MSDP group.
The remaining statements are explained separately.
316 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance import (Protocols MSDP)
Syntax import [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit protocols
],
[edit protocols
group-name],
[edit protocols
group-name
address],
[edit protocols
address],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name],
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more policies to routes being imported into the routing table from MSDP.
Options policy-names —Name of one or more policies.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance
•
Copyright © 2016, Juniper Networks, Inc.
317
Multicast Protocols Feature Guide for EX4600 Switches local-address (Protocols MSDP)
Syntax local-address address;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit protocols
],
[edit protocols
group-name],
[edit protocols
group-name
address],
[edit protocols
address],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name],
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the local end of an MSDP session. You must configure at least one peer for
MSDP to function. When configuring a peer, you must include this statement. This address is used to accept incoming connections to the peer and to establish connections to the remote peer.
Options address —IP address of the local end of the connection.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance
318 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements maximum (MSDP Active Source Messages)
Syntax maximum number;
Hierarchy Level [edit logical-systems logical-system-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
],
[edit protocols
[edit routing-instances routing-instance-name protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the maximum number of MSDP active source messages the router accepts.
Options number —Maximum number of active source messages.
Range: 1 through 1,000,000
Default: 25,000
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
•
threshold (MSDP Active Source Messages) on page 326
Copyright © 2016, Juniper Networks, Inc.
319
Multicast Protocols Feature Guide for EX4600 Switches mode (Protocols MSDP)
Syntax mode (mesh-group | standard);
Hierarchy Level [edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit protocols
group-name],
[edit routing-instances routing-instance-name protocols
group-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure groups of peers in a full mesh topology to limit excessive flooding of source-active messages to neighboring peers. The default flooding mode is standard.
Default If you do not include this statement, default flooding is applied.
Options mesh-group —Group of peers that are mesh group members.
standard —Use standard MSDP source-active flooding rules.
Default: standard
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
320 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements msdp
Syntax msdp {
{ log-interval seconds; log-warning value;
number;
number;
}
(disable | enable);
[ policy-names ]; group group-name {
... group-configuration ...
} hold-time seconds;
[ policy-names ];
address; keep-alive seconds; peer address {
... peer-configuration ...
}
group-name;
ip-prefix</prefix-length> {
{
number;
number;
}
} sa-hold-time seconds;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
group-name {
[ policy-names ];
[ policy-names ];
address;
(mesh-group | standard); peer address {
... same statements as at the [edit protocols msdp
address] hierarchy level shown
just following ...
}
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
}
address {
{
number;
number;
Copyright © 2016, Juniper Networks, Inc.
321
Multicast Protocols Feature Guide for EX4600 Switches
}
}
}
peer-key;
[ policy-names ];
[ policy-names ];
address;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
Hierarchy Level [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.4 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable MSDP on the router or switch. You must also configure at least one peer for MSDP to function.
Default MSDP is disabled on the router or switch.
Options The statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance
322 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements peer (Protocols MSDP)
Syntax peer address {
{
number;
number;
}
peer-key;
[ policy-names ];
[ policy-names ];
address;
{ file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit protocols
],
[edit protocols
group-name],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Define an MSDP peering relationship. An MSDP routing device must know which routing devices are its peers. You define the peer relationships explicitly by configuring the neighboring routing devices that are the MSDP peers of the local routing device. After peer relationships are established, the MSDP peers exchange messages to advertise active multicast sources. To configure multiple MSDP peers, include multiple peer statements.
By default, the peer's options are identical to the global or group-level MSDP options.
To override the global or group-level options, include peer-specific options within the
statement.
At least one peer must be configured for MSDP to function. You must configure address and local-address.
Options address —Name of the MSDP peer.
The remaining statements are explained separately.
Copyright © 2016, Juniper Networks, Inc.
323
Multicast Protocols Feature Guide for EX4600 Switches
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance rib-group (Protocols MSDP)
Syntax rib-group group-name;
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit protocols
],
[edit routing-instances routing-instance-name protocols
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Associate a routing table group with MSDP.
Options group-name —Name of the routing table group. The name must be one that you defined with the rib-groups statement at the [edit routing-options] hierarchy level.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
• Example: Configuring MSDP in a Routing Instance
324 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements source (Protocols MSDP)
Syntax source ip-address</prefix-length> {
{
number;
number;
}
}
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit protocols
],
[edit routing-instances routing-instance-name protocols
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Limit the number of active source messages the routing device accepts from sources in this address range.
Default If you do not include this statement, the routing device accepts any number of MSDP active source messages.
Options The other statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
Copyright © 2016, Juniper Networks, Inc.
325
Multicast Protocols Feature Guide for EX4600 Switches threshold (MSDP Active Source Messages)
Syntax threshold number;
Hierarchy Level [edit logical-systems logical-system-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
],
[edit protocols
[edit routing-instances routing-instance-name protocols
]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure the random early detection (RED) threshold for MSDP active source messages.
This number must be less than the configured or default maximum.
Options number —RED threshold for active source messages.
Range: 1 through 1,000,000
Default: 24,000
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring MSDP with Active Source Limits and Mesh Groups on page 172
•
maximum (MSDP Active Source Messages) on page 319
326 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements traceoptions (Protocols MSDP)
Syntax traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>;
}
Hierarchy Level [edit logical-systems logical-system-name protocols
],
[edit logical-systems logical-system-name protocols
group-name],
[edit logical-systems logical-system-name protocols
group-name
address],
[edit logical-systems logical-system-name protocols
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
group-name
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
address],
[edit protocols
],
[edit protocols
group-name],
[edit protocols
group-name
address],
[edit protocols
address],
[edit routing-instances routing-instance-name protocols
[edit routing-instances routing-instance-name protocols
group-name],
[edit routing-instances routing-instance-name protocols
group-name
address],
[edit routing-instances routing-instance-name protocols
address]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure MSDP tracing options.
To specify more than one tracing operation, include multiple flag statements.
Default The default MSDP trace options are those inherited from the routing protocol's traceoptions statement included at the [edit routing-options] hierarchy level.
Options disable —(Optional) Disable the tracing operation. You can use this option to disable a single operation when you have defined a broad group of tracing operations, such as all.
file filename —Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. We recommend that you place tracing output in the msdp-log file.
files number —(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
Copyright © 2016, Juniper Networks, Inc.
327
Multicast Protocols Feature Guide for EX4600 Switches
If you specify a maximum number of files, you must also include the size statement to specify the maximum file size.
Range: 2 through 1000 files
Default: 2 files flag flag —Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements.
MSDP Tracing Flags
• keepalive— Keepalive messages
• packets —All MSDP packets
• route —MSDP changes to the routing table
• source-active —Source-active packets
• source-active-request —Source-active request packets
• source-active-response —Source-active response packets
Global Tracing Flags
• all —All tracing operations
• general —A combination of the normal and route trace operations
• normal —All normal operations
Default: If you do not specify this option, only unusual or abnormal operations are traced.
• policy —Policy operations and actions
• route —Routing table changes
• state —State transitions
• task —Interface transactions and processing
• timer —Timer usage flag-modifier —(Optional) Modifier for the tracing flag. You can specify one or more of these modifiers:
328 Copyright © 2016, Juniper Networks, Inc.
Chapter 16: MSDP Configuration Statements
• detail —Detailed trace information
• receive —Packets being received
• send —Packets being transmitted no-stamp —(Optional) Do not place timestamp information at the beginning of each line in the trace file.
Default: If you omit this option, timestamp information is placed at the beginning of each line of the tracing output.
no-world-readable —(Optional) Do not allow any user to read the log file.
replace —(Optional) Replace an existing trace file if there is one.
Default: If you do not include this option, tracing output is appended to an existing trace file.
size size —(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0
. When trace-file again reaches this size, trace-file.0 is renamed trace-file.1
and trace-file is renamed trace-file.0. This renaming scheme continues until the maximum number of trace files is reached. Then the oldest trace file is overwritten.
If you specify a maximum file size, you must also include the files statement to specify the maximum number of trace files.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through the maximum file size supported on your system
Default: 1 MB world-readable —(Optional) Allow any user to read the log file.
Required Privilege
Level routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration.
Related
Documentation
•
Tracing MSDP Protocol Traffic on page 168
Copyright © 2016, Juniper Networks, Inc.
329
Multicast Protocols Feature Guide for EX4600 Switches
330 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 17
Source-Specific Multicast Configuration
Statements
•
•
•
•
ssm-map (Protocols IGMP) on page 334
•
ssm-map (Routing Options Multicast) on page 335
•
ssm-map-policy (IGMP) on page 336
asm-override-ssm
Syntax asm-override-ssm;
Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast]
Release Information Statement introduced in Junos OS Release 9.4.
Statement introduced in Junos OS Release 9.5 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Enable the routing device to accept any-source multicast join messages (*,G) for group addresses that are within the default or configured range of source-specific multicast groups.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring Source-Specific Multicast Groups with Any-Source Override on page 46
Copyright © 2016, Juniper Networks, Inc.
331
Multicast Protocols Feature Guide for EX4600 Switches policy (SSM Maps)
Syntax policy [ policy-names ];
Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast
ssm-map-name],
[edit logical-systems logical-system-name routing-options multicast
ssm-map-name],
[edit routing-instances routing-instance-name routing-options multicast
ssm-map-name],
[edit routing-options multicast
ssm-map-name]
Release Information Statement introduced in Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply one or more policies to an SSM map.
Options policy-names —Name of one or more policies for SSM mapping.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To view this statement in the configuration.
Related
Documentation
•
Example: Configuring SSM Mapping on page 43
332 Copyright © 2016, Juniper Networks, Inc.
Chapter 17: Source-Specific Multicast Configuration Statements ssm-groups
Syntax ssm-groups [ ip-addresses ];
Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure source-specific multicast (SSM) groups.
By default, the SSM group multicast address is limited to the IP address range from
232.0.0.0 through 232.255.255.255. However, you can extend SSM operations into another
Class D range by including the ssm-groups statement in the configuration. The default
SSM address range from 232.0.0.0 through 232.255.255.255 cannot be used in the ssm-groups statement. This statement is for adding other multicast addresses to the default SSM group addresses. This statement does not override the default SSM group address range.
IGMPv3 supports SSM groups. By utilizing inclusion lists, only sources that are specified send to the SSM group.
Options ip-addresses —List of one or more additional SSM group addresses separated by a space.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring Source-Specific Multicast Groups with Any-Source Override on page 46
Copyright © 2016, Juniper Networks, Inc.
333
Multicast Protocols Feature Guide for EX4600 Switches ssm-map (Protocols IGMP)
Syntax ssm-map ssm-map-name;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply an SSM map to an IGMP interface.
Options ssm-map-name —Name of SSM map.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring SSM Mapping on page 43
334 Copyright © 2016, Juniper Networks, Inc.
Chapter 17: Source-Specific Multicast Configuration Statements ssm-map (Routing Options Multicast)
Syntax ssm-map ssm-map-name {
[ policy-names ]; source [ addresses ];
}
Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast]
Release Information Statement introduced in Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Configure SSM mapping.
Options ssm-map-name —Name of the SSM map.
The remaining statements are explained separately.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring SSM Mapping on page 43
Copyright © 2016, Juniper Networks, Inc.
335
Multicast Protocols Feature Guide for EX4600 Switches ssm-map-policy (IGMP)
Syntax ssm-map-policy ssm-map-policy-name;
Hierarchy Level [edit logical-systems logical-system-name protocols
interface-name],
[edit protocols
interface-name]
Release Information Statement introduced in Junos OS Release 11.4.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Apply an SSM map policy to an IGMP interface.
Options ssm-map-policy-name —Name of SSM map policy.
Required Privilege
Level routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related
Documentation
•
Example: Configuring SSM Maps for Different Groups to Different Sources on page 49
336 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 18
Multicast Operational Commands
•
clear multicast bandwidth-admission
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
show multicast pim-to-igmp-proxy
•
show multicast pim-to-mld-proxy
•
•
•
•
•
•
•
•
•
•
Copyright © 2016, Juniper Networks, Inc.
337
Multicast Protocols Feature Guide for EX4600 Switches
•
•
338 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands clear multicast bandwidth-admission
Syntax clear multicast bandwidth-admission
<group group-address>
<inet | inet6>
<instance instance-name>
<interface interface-name>
<source source-address>
Release Information Command introduced in Junos OS Release 8.3.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Reapply IP multicast bandwidth admissions.
Options none —Reapply multicast bandwidth admissions for all IPv4 forwarding entries in the master routing instance.
group group-address —(Optional) Reapply multicast bandwidth admissions for the specified group.
inet —(Optional) Reapply multicast bandwidth admission settings for IPv4 flows.
inet6 —(Optional) Reapply multicast bandwidth admission settings for IPv6 flows.
instance instance-name —(Optional) Reapply multicast bandwidth admission settings for the specified instance. If you do not specify an instance, the command applies to the master routing instance.
interface interface-name —(Optional) Examines the corresponding outbound interface in the relevant entries and acts as follows:
• If the interface is congested, and it was admitted previously, it is removed.
• If the interface was rejected previously, the clear multicast bandwidth-admission command enables the interface to be admitted as long as enough bandwidth exists on the interface.
• If you do not specify an interface, issuing the clear multicast bandwidth-admission command readmits any previously rejected interface for the relevant entries as long as enough bandwidth exists on the interface.
To manually reject previously admitted outbound interfaces, you must specify the interface.
source source-address —(Optional) Use with the group option to reapply multicast bandwidth admission settings for the specified (source, group) entry.
Required Privilege
Level clear
Copyright © 2016, Juniper Networks, Inc.
339
Multicast Protocols Feature Guide for EX4600 Switches
Related
Documentation
•
show multicast interface on page 364
List of Sample Output
clear multicast bandwidth-admission on page 340
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output clear multicast bandwidth-admission user@host> clear multicast bandwidth-admission
340 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands clear multicast scope
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 341
Syntax clear multicast scope
<inet | inet6>
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) clear multicast scope
<inet | inet6>
<interface interface-name>
Release Information Command introduced in Junos OS Release 7.6.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 option introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Clear IP multicast scope statistics.
Options none —(Same as logical-system all) Clear multicast scope statistics.
inet —(Optional) Clear multicast scope statistics for IPv4 family addresses.
inet6 —(Optional) Clear multicast scope statistics for IPv6 family addresses.
interface interface-name —(Optional) Clear multicast scope statistics on a specific interface.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level clear
Related
Documentation
•
show multicast scope on page 385
List of Sample Output
clear multicast scope on page 341
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output clear multicast scope user@host> clear multicast scope
Copyright © 2016, Juniper Networks, Inc.
341
Multicast Protocols Feature Guide for EX4600 Switches clear multicast sessions
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 342
Syntax clear multicast sessions
<logical-system (all | logical-system-name)>
<regular-expression>
Syntax (EX Series
Switch and the QFX
Series) clear multicast sessions
<regular-expression>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Clear IP multicast sessions.
Options none —(Same as logical-system all) Clear multicast sessions.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
regular-expression —(Optional) Clear only multicast sessions that contain the specified regular expression.
Required Privilege
Level clear
Related
Documentation
•
show multicast sessions on page 387
List of Sample Output
clear multicast sessions on page 342
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output clear multicast sessions user@host> clear multicast sessions
342 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands clear multicast statistics
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 343
Syntax clear multicast statistics
<inet | inet6>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) clear multicast statistics
<inet | inet6>
<instance instance-name>
<interface interface-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Clear IP multicast statistics.
Options none —Clear multicast statistics for all supported address families on all interfaces.
inet —(Optional) Clear multicast statistics for IPv4 family addresses.
inet6 —(Optional) Clear multicast statistics for IPv6 family addresses.
instance instance-name —(Optional) Clear multicast statistics for the specified instance.
interface interface-name —(Optional) Clear multicast statistics on a specific interface.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level clear
Related
Documentation
• show multicast statistics
List of Sample Output
clear multicast statistics on page 343
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output clear multicast statistics user@host> clear multicast statistics
Copyright © 2016, Juniper Networks, Inc.
343
Multicast Protocols Feature Guide for EX4600 Switches clear pim join
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 344
Syntax clear pim join
<group-address>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) clear pim join
<group-address>
<inet | inet6>
<instance instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Clear the Protocol Independent Multicast (PIM) join and prune states.
Options none —Clear the PIM join and prune states for all groups, family addresses, and instances.
group-address —(Optional) Clear the PIM join and prune states for a group address.
inet | inet6 —(Optional) Clear the PIM join and prune states for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Clear the join and prune states for a specific
PIM-enabled routing instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Additional Information The clear pim join command cannot be used to clear the PIM join and prune state on a backup Routing Engine when nonstop active routing is enabled.
Required Privilege
Level clear
Related
Documentation
•
List of Sample Output
Output Fields When you enter this command, you are provided feedback on the status of your request.
344 Copyright © 2016, Juniper Networks, Inc.
Sample Output clear pim join user@host> clear pim join
Chapter 18: Multicast Operational Commands
Copyright © 2016, Juniper Networks, Inc.
345
Multicast Protocols Feature Guide for EX4600 Switches clear pim register
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 346
Syntax (PTX Series) on page 346
Syntax clear pim register
<inet | inet6>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) clear pim register
<inet | inet6>
<instance instance-name>
<interface interface-name>
Syntax (PTX Series) clear pim register
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
Release Information Command introduced in Junos OS Release 7.6.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Clear Protocol Independent Multicast (PIM) register message counters.
Options none—Clear PIM register message counters for all family addresses, instances, and interfaces.
inet | inet6 —(Optional) Clear PIM register message counters for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Clear register message counters for a specific
PIM-enabled routing instance.
interface interface-name —(Optional) Clear PIM register message counters for a specific interface.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Additional Information The clear pim register command cannot be used to clear the PIM register state on a backup Routing Engine when nonstop active routing is enabled.
Required Privilege
Level clear
346 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Related
Documentation
•
show pim statistics on page 433
List of Sample Output
clear pim register on page 347
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output clear pim register user@host> clear pim register
Copyright © 2016, Juniper Networks, Inc.
347
Multicast Protocols Feature Guide for EX4600 Switches clear pim statistics
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 348
Syntax clear pim statistics
<inet | inet6>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) clear pim statistics
<inet | inet6>
<instance instance-name>
<interface interface-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Clear Protocol Independent Multicast (PIM) statistics.
Options none —Clear PIM statistics for all family addresses, instances, and interfaces.
inet | inet6 —(Optional) Clear PIM statistics for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Clear statistics for a specific PIM-enabled routing instance.
interface interface-name —(Optional) Clear PIM statistics for a specific interface.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Additional Information The clear pim statistics command cannot be used to clear the PIM statistics on a backup
Routing Engine when nonstop active routing is enabled.
Required Privilege
Level clear
Related
Documentation
•
show pim statistics on page 433
List of Sample Output
clear pim statistics on page 349
Output Fields See
for an explanation of output fields.
348 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Sample Output clear pim statistics
The following sample output displays PIM statistics before and after the clear pim statistics command is entered: user@host> show pim statistics
PIM statistics on all interfaces:
PIM Message type Received Sent Rx errors
Hello 0 0 0
Register 0 0 0
Register Stop 0 0 0
Join Prune 0 0 0
Bootstrap 0 0 0
Assert 0 0 0
Graft 0 0 0
Graft Ack 0 0 0
Candidate RP 0 0 0
V1 Query 2111 4222 0
V1 Register 0 0 0
V1 Register Stop 0 0 0
V1 Join Prune 14200 13115 0
V1 RP Reachability 0 0 0
V1 Assert 0 0 0
V1 Graft 0 0 0
V1 Graft Ack 0 0 0
PIM statistics summary for all interfaces:
Unknown type 0
V1 Unknown type 0
Unknown Version 0
Neighbor unknown 0
Bad Length 0
Bad Checksum 0
Bad Receive If 0
Rx Intf disabled 2007
Rx V1 Require V2 0
Rx Register not RP 0
RP Filtered Source 0
Unknown Reg Stop 0
Rx Join/Prune no state 1040
Rx Graft/Graft Ack no state 0
...
user@host> clear pim statistics user@host> show pim statistics
PIM statistics on all interfaces:
PIM Message type Received Sent Rx errors
Hello 0 0 0
Register 0 0 0
Register Stop 0 0 0
Join Prune 0 0 0
Bootstrap 0 0 0
Assert 0 0 0
Graft 0 0 0
Graft Ack 0 0 0
Candidate RP 0 0 0
V1 Query 1 0 0
V1 Register 0 0 0
...
Copyright © 2016, Juniper Networks, Inc.
349
Multicast Protocols Feature Guide for EX4600 Switches
350 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands mtrace
Syntax mtrace source
<logical-system logical-system-name>
<routing-instance routing-instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 9.5 for SRX1400, SRX3400, SRX3600,
SRX5600, and SRX5800 devices.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Command introduced in Junos OS Release 12.3 for the PTX Series.
Description Display trace information about an IP multicast path.
Options source —Source hostname or address.
logical-system (logical-system-name) —(Optional) Perform this operation on a logical system.
routing-instance routing-instance-name —(Optional) Trace a particular routing instance.
Additional Information The mtrace command for multicast traffic is similar to the traceroute command used for unicast traffic. Unlike traceroute, mtrace traces traffic backwards, from the receiver to the source.
Required Privilege
Level view
List of Sample Output
Output Fields
describes the output fields for the mtrace command. Output fields are listed in the approximate order in which they appear.
Table 10: mtrace Output Fields
Field Name Field Description
Mtrace from to via group
IP address of the receiver.
IP address of the source.
IP address of the multicast group (if any).
Indicates the full reverse path query has begun.
Querying full reverse path number-of-hops router-name address
Number of hops from the source to the named router or switch.
Name of the router or switch for this hop.
Address of the router or switch for this hop.
Copyright © 2016, Juniper Networks, Inc.
351
Multicast Protocols Feature Guide for EX4600 Switches
Table 10: mtrace Output Fields (continued)
Field Name Field Description protocol Protocol used (for example, PIM).
Average round-trip time, in milliseconds (ms).
Round trip time total ttl of Time-to-live (TTL) threshold.
352 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Sample Output mtrace source user@host> mtrace 192.1.4.2
Mtrace from 192.1.4.2 to 192.1.1.2 via group 0.0.0.0
Querying full reverse path... * *
0 routerA.lab.mycompany.net (192.1.1.2)
-1 routerB.lab.mycompany.net (192.1.2.2) PIM thresh^ 1
-2 routerC.lab.mycompany.net (192.1.3.2) PIM thresh^ 1
-3 hostA.lab.mycompany.net (192.1.4.2)
Round trip time 2 ms; total ttl of 2 required.
Copyright © 2016, Juniper Networks, Inc.
353
Multicast Protocols Feature Guide for EX4600 Switches mtrace from-source
Syntax mtrace from-source source source
<brief | detail>
<extra-hops extra-hops>
<group group>
<interval interval>
<loop>
<max-hops max-hops>
<max-queries max-queries>
<multicast-response | unicast-response>
<no-resolve>
<no-router-alert>
<response response>
<routing-instance routing-instance-name>
<ttl ttl>
<wait-time wait-time>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display trace information about an IP multicast path from a source to this router or switch.
If you specify a group address with this command, Junos OS returns additional information, such as packet rates and losses.
Options brief | detail —(Optional) Display the specified level of output.
extra-hops extra-hops —(Optional) Number of hops to take after reaching a nonresponsive router. You can specify a number between 0 and 255.
group group —(Optional) Group address for which to trace the path. The default group address is 0.0.0.0.
interval interval —(Optional) Number of seconds to wait before gathering statistics again.
The default value is 10 seconds.
loop —(Optional) Loop indefinitely, displaying rate and loss statistics.
max-hops max-hops —(Optional) Maximum hops to trace toward the source. The range of values is 0 through 255. The default value is 32 hops.
max-queries max-queries —(Optional) Maximum number of query attempts for any hop.
The range of values is 1 through 32. The default is 3.
multicast-response —(Optional) Always request the response using multicast.
no-resolve —(Optional) Do not attempt to display addresses symbolically.
no-router-alert —(Optional) Do not use the router-alert IP option.
response response —(Optional) Send trace response to a host or multicast address.
354 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands routing-instance routing-instance-name —(Optional) Trace a particular routing instance.
source source —Source hostname or address.
ttl ttl —(Optional) IP time-to-live (TTL) value. You can specify a number between 0 and
255 . Local queries to the multicast group use a value of 1. Otherwise, the default value is 127.
unicast-response —(Optional) Always request the response using unicast.
wait-time wait-time —(Optional) Number of seconds to wait for a response. The default value is 3.
Required Privilege
Level view
List of Sample Output
mtrace from-source on page 356
Output Fields
describes the output fields for the mtrace from-source command.
Output fields are listed in the approximate order in which they appear.
Table 11: mtrace from-source Output Fields
Field Name Field Description
Mtrace from to via group
IP address of the receiver.
IP address of the source.
IP address of the multicast group (if any).
Querying full reverse path Indicates the full reverse path query has begun.
number-of-hops Number of hops from the source to the named router or switch.
router-name Name of the router or switch for this hop.
Address of the router or switch for this hop.
address protocol Protocol used (for example, PIM).
Average round-trip time, in milliseconds (ms).
Round trip time total ttl of source
Time-to-live (TTL) threshold.
Source address.
Response destination address.
Response Dest
Overall Average packet rate for all traffic at each hop.
Copyright © 2016, Juniper Networks, Inc.
355
Multicast Protocols Feature Guide for EX4600 Switches
Table 11: mtrace from-source Output Fields (continued)
Field Name Field Description
Packet Statistics for Traffic
From
Number of packets lost, number of packets sent, percentage of packets lost, and average packet rate at each hop.
Receiver
Query source
IP address receiving the multicast.
IP address sending the mtrace query.
Sample Output mtrace from-source user@host> mtrace from-source source 192.1.4.2 group 225.1.1.1
Mtrace from 192.1.4.2 to 192.1.1.2 via group 225.1.1.1
Querying full reverse path... * *
0 routerA.lab.mycompany.net (192.1.1.2)
-1 routerB.lab.mycompany.net (192.1.2.2) PIM thresh^ 1
-2 routerC.lab.mycompany.net (192.1.3.2) PIM thresh^ 1
-3 hostA.lab.mycompany.net (192.1.4.2)
Round trip time 2 ms; total ttl of 2 required.
Waiting to accumulate statistics...Results after 10 seconds:
Source Response Dest Overall Packet Statistics For Traffic From
192.1.4.2 192.1.1.2 Packet 192.1.4.2 To 225.1.1.1
v __/ rtt 2 ms Rate Lost/Sent = Pct Rate
192.1.2.1
192.1.3.2 routerC.lab.mycompany.net
v ^ ttl 2 0/0 = -- 0 pps
192.1.4.1
192.1.2.2 routerB.lab.mycompany.net
v \__ ttl 3 ?/0 0 pps
192.1.1.2 192.1.1.2
Receiver Query Source
356 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands mtrace monitor
Syntax mtrace monitor
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Listen passively for IP multicast responses. To exit the mtrace monitor command, type
Ctrl+c.
Options none —Trace the master instance.
Required Privilege
Level view
List of Sample Output
Output Fields
describes the output fields for the mtrace monitor command. Output fields are listed in the approximate order in which they appear.
Table 12: mtrace monitor Output Fields
Field Name Field Description
Mtrace query at Date and time of the query.
Address of the host issuing the query.
by resp to qid packet from...to
from...to
Response destination.
Query ID number.
IP address of the query source and default group destination.
IP address of the multicast source and the response address.
IP address of the group to trace.
via group mxhop Maximum hop setting.
Copyright © 2016, Juniper Networks, Inc.
357
Multicast Protocols Feature Guide for EX4600 Switches
Sample Output mtrace monitor user@host> mtrace monitor
Mtrace query at Oct 22 13:36:14 by 192.1.3.2, resp to 224.0.1.32, qid 74a5b8 packet from 192.1.3.2 to 224.0.0.2
from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60)
Mtrace query at Oct 22 13:36:17 by 192.1.3.2, resp to 224.0.1.32, qid 1d07ba packet from 192.1.3.2 to 224.0.0.2
from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60)
Mtrace query at Oct 22 13:36:20 by 192.1.3.2, resp to same, qid 2fea1d packet from 192.1.3.2 to 224.0.0.2
from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60)
Mtrace query at Oct 22 13:36:30 by 192.1.3.2, resp to same, qid 7c88ad packet from 192.1.3.2 to 224.0.0.2
from 192.1.3.2 to 192.1.3.38 via group 224.1.1.1 (mxhop=60)
358 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands mtrace to-gateway
Syntax mtrace to-gateway gateway gateway
<brief | detail>
<extra-hops extra-hops>
<group group>
<interface interface-name>
<interval interval>
<loop>
<max-hops max-hops>
<max-queries max-queries>
<multicast-response | unicast-response>
<no-resolve>
<no-router-alert>
<response response>
<routing-instance routing-instance-name>
<ttl ttl>
<unicast-response>
<wait-time wait-time>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display trace information about a multicast path from this router or switch to a gateway router or switch.
Options gateway gateway —Send the trace query to a gateway multicast address.
brief | detail —(Optional) Display the specified level of output.
extra-hops extra-hops —(Optional) Number of hops to take after reaching a nonresponsive router or switch. You can specify a number between 0 and 255.
group group —(Optional) Group address for which to trace the path. The default group address is 0.0.0.0.
interface interface-name —(Optional) Source address for sending the trace query.
interval interval —(Optional) Number of seconds to wait before gathering statistics again.
The default value is 10.
loop —(Optional) Loop indefinitely, displaying rate and loss statistics.
max-hops max-hops —(Optional) Maximum hops to trace toward the source. You can specify a number between 0 and 255.. The default value is 32.
max-queries max-queries —(Optional) Maximum number of query attempts for any hop.
You can specify a number between 0 and 255. The default value is 3.
multicast-response —(Optional) Always request the response using multicast.
no-resolve —(Optional) Do not attempt to display addresses symbolically.
Copyright © 2016, Juniper Networks, Inc.
359
Multicast Protocols Feature Guide for EX4600 Switches no-router-alert —(Optional) Do not use the router-alert IP option.
response response —(Optional) Send trace response to a host or multicast address.
routing-instance routing-instance-name —(Optional) Trace a particular routing instance.
ttl ttl —(Optional) IP time-to-live value. You can specify a number between 0 and 225.
Local queries to the multicast group use TTL 1. Otherwise, the default value is 127.
unicast-response —(Optional) Always request the response using unicast.
wait-time wait-time —(Optional) Number of seconds to wait for a response. The default value is 3.
Required Privilege
Level view
List of Sample Output
Output Fields
describes the output fields for the mtrace to-gateway command.
Output fields are listed in the approximate order in which they appear.
Table 13: mtrace to-gateway Output Fields
Field Name Field Description
IP address of the receiver.
Mtrace from to via group
Querying full reverse path number-of-hops
IP address of the source.
IP address of the multicast group (if any).
Indicates the full reverse path query has begun.
Number of hops from the source to the named router or switch.
Name of the router or switch for this hop.
router-name address protocol
Round trip time total ttl of
Address of the router or switch for this hop.
Protocol used (for example, PIM).
Average round-trip time, in milliseconds (ms).
Time-to-live (TTL) threshold.
Sample Output mtrace to-gateway user@host> mtrace to-gateway gateway 192.1.3.2 group 225.1.1.1 interface 192.1.1.73 brief
Mtrace from 192.1.1.73 to 192.1.1.2 via group 225.1.1.1
360 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Querying full reverse path... * *
0 routerA.lab.mycompany.net (192.1.1.2)
-1 routerA.lab.mycompany.net (192.1.1.2) PIM thresh^ 1
-2 routerB.lab.mycompany.net (192.1.2.2) PIM thresh^ 1
-3 routerC.lab.mycompany.net (192.1.3.2) PIM thresh^ 1
Round trip time 2 ms; total ttl of 3 required.
Copyright © 2016, Juniper Networks, Inc.
361
Multicast Protocols Feature Guide for EX4600 Switches show multicast flow-map
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 362
Syntax show multicast flow-map
<brief | detail>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show multicast flow-map
<brief | detail>
Release Information Command introduced in Junos OS Release 8.2.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display configuration information about IP multicast flow maps.
Options none —Display configuration information about IP multicast flow maps on all systems.
brief | detail —(Optional) Display the specified level of output.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show multicast flow-map on page 363 show multicast flow-map detail on page 363
Output Fields
describes the output fields for the show multicast flow-map command. Output fields are listed in the approximate order in which they appear.
Table 14: show multicast flow-map Output Fields
Field Name Field Description Levels of Output
Name
Policy
Cache-timeout
Name of the flow map.
Name of the policy associated with the flow map.
All levels
All levels
Cache timeout value assigned to the flow map.
Bandwidth setting associated with the flow map.
All levels
All levels Bandwidth
Adaptive none
Flow-map
Whether or not adaptive mode is enabled for the flow map.
Name of the flow map.
detail
362 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 14: show multicast flow-map Output Fields (continued)
Field Name Field Description
Adaptive
Bandwidth
Whether or not adaptive mode is enabled for the flow map.
Redundant Sources Redundant sources defined for the same destination group.
Levels of Output detail detail
Sample Output show multicast flow-map user@host> show multicast flow-map
Instance: master
Name Policy Cache timeout Bandwidth Adaptive map2 policy2 never 2000000 no map1 policy1 60 seconds 2000000 no
Sample Output show multicast flow-map detail user@host> show multicast flow-map detail
Instance: master
Flow-map: map1
Policy: policy1
Cache Timeout: 600 seconds
Bandwidth: 2000000
Adaptive Bandwidth: yes
Redundant Sources: 11.11.11.11
Redundant Sources: 11.11.11.12
Redundant Sources: 11.11.11.13
Copyright © 2016, Juniper Networks, Inc.
363
Multicast Protocols Feature Guide for EX4600 Switches show multicast interface
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 364
Syntax show multicast interface
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show multicast interface
Release Information Command introduced in Junos OS Release 8.3.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display bandwidth information about IP multicast interfaces.
Options none —Display all interfaces that have multicast configured.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show multicast interface on page 365
Output Fields
describes the output fields for the show multicast interface command.
Output fields are listed in the approximate order in which they appear.
Table 15: show multicast interface Output Fields
Field Name Field Description
Interface Name of the multicast interface.
Maximum bandwidth (bps) Maximum bandwidth setting, in bits per second, for this interface.
Remaining bandwidth (bps) Amount of bandwidth, in bits per second, remaining on the interface.
Mapped bandwidth deduction (bps)
Amount of bandwidth, in bits per second, used by any flows that are mapped to the interface.
NOTE: Adding the mapped bandwidth deduction value to the local bandwidth deduction value results in the total deduction value for the interface.
This field does not appear in the output when the no QoS adjustment feature is disabled.
364 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 15: show multicast interface Output Fields (continued)
Field Name Field Description
Local bandwidth deduction
(bps)
Amount of bandwidth, in bits per second, used by any mapped flows that are traversing the interface.
NOTE: Adding the mapped bandwidth deduction value to the local bandwidth deduction value results in the total deduction value for the interface.
This field does not appear in the output when the no QoS adjustment feature is disabled.
Reverse OIF mapping
Reverse OIF mapping no
QoS adjustment
Leave timer
State of the reverse OIF mapping feature ( on or off ).
NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled.
State of the no QoS adjustment feature ( on or off ) for interfaces that are using reverse OIF mapping.
NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled.
Amount of time a mapped interface remains active after the last mapping ends.
NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled.
No QoS adjustment State ( on ) of the no QoS adjustment feature when this feature is enabled.
NOTE: This field does not appear in the output when the no QoS adjustment feature is disabled.
Sample Output show multicast interface user@host> show multicast interface
Interface Maximum bandwidth (bps) Remaining bandwidth (bps) fe-0/0/3 10000000 0 fe-0/0/3.210 10000000 –2000000 fe-0/0/3.220 100000000 100000000 fe-0/0/3.230 20000000 18000000 fe-0/0/2.200 100000000 100000000
Copyright © 2016, Juniper Networks, Inc.
365
Multicast Protocols Feature Guide for EX4600 Switches show multicast mrinfo
Syntax show multicast mrinfo
<host>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display configuration information about IP multicast networks, including neighboring multicast router addresses.
Options none —Display configuration information about all multicast networks.
host —(Optional) Display configuration information about a particular host. Replace host with a hostname or IP address.
Required Privilege
Level view
List of Sample Output
show multicast mrinfo on page 367
Output Fields
describes the output fields for the show multicast mrinfo command.
Output fields are listed in the approximate order in which they appear.
Table 16: show multicast mrinfo Output Fields
Field Name Field Description source-address Query address, hostname (DNS name or IP address of the source address), and multicast protocol version or the software version of another vendor.
ip-address-1--->ip-address-2 Queried router interface address and directly attached neighbor interface address, respectively.
(name or ip-address) Name or IP address of neighbor.
[metric/threshold/type/
flags]
Neighbor's multicast profile:
•
•
•
• metric —Always has a value of 1 , because mrinfo queries the directly connected interfaces of a device.
threshold —Multicast threshold time-to-live (TTL). The range of values is 0 through 255 .
type —Multicast connection type: pim or tunnel .
flags —Flags for this route:
• querier —Queried router is the designated router for the neighboring session.
• leaf —Link is a leaf in the multicast network.
• down —Link status indicator.
366 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Sample Output show multicast mrinfo user@host> show multicast mrinfo 10.35.4.1
10.35.4.1 (10.35.4.1) [version 12.0]:
192.168.195.166 -> 0.0.0.0 (local) [1/0/pim/querier/leaf]
10.38.20.1 -> 0.0.0.0 (local) [1/0/pim/querier/leaf]
10.47.1.1 -> 10.47.1.2 (10.47.1.2) [1/5/pim]
0.0.0.0 -> 0.0.0.0 (local) [1/0/pim/down]
Copyright © 2016, Juniper Networks, Inc.
367
Multicast Protocols Feature Guide for EX4600 Switches show multicast next-hops
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 368
Syntax show multicast next-hops
<brief | detail>
<identifier-number>
<inet | inet6>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show multicast next-hops
<brief | detail>
<identifier-number>
<inet | inet6>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 option introduced in Junos OS Release 10.0 for EX Series switches.
detail option display of next-hop ID number introduced in Junos OS Release 11.1 for M Series and T Series routers and EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Description Display the entries in the IP multicast next-hop table.
Options none —Display standard information about all entries in the multicast next-hop table for all supported address families.
brief | detail —(Optional) Display the specified level of output.
When you include the detail option on M Series and T Series routers and EX Series switches, the downstream interface name includes the next-hop ID number in parentheses, in the form fe-0/1/2.0-(1048574) where 1048574 is the next-hop ID number.
identifier-number —(Optional) Show a particular next hop by ID number. The range of values is 1 through 65,535.
inet | inet6 —(Optional) Display entries for IPv4 or IPv6 family addresses, respectively.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show multicast next-hops on page 369 show multicast next-hops (Bidirectional PIM on page 369
show multicast next-hops brief on page 370 show multicast next-hops detail on page 370
368 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Output Fields
describes the output fields for the show multicast next-hops command. Output fields are listed in the approximate order in which they appear.
Table 17: show multicast next-hops Output Fields
Field Name Field Description
Family
ID
Protocol family (such as INET ).
Next-hop identifier of the prefix. The identifier is returned by the routing device's
Packet Forwarding Engine.
Refcount Number of cache entries that are using this next hop.
Kernel reference count for the next hop.
KRefcount
Downstream interface
Interface names associated with each multicast next-hop ID.
Incoming interface list
List of interfaces that accept incoming traffic. Only shown for routes that do not use strict RPF-based forwarding, for example for bidirectional PIM.
Sample Output show multicast next-hops user@host> show multicast next-hops
Family: INET
ID Refcount KRefcount Downstream interface
262142 4 2 so-1/0/0.0
262143 2 1 mt-1/1/0.49152
262148 2 1 mt-1/1/0.32769
show multicast next-hops (Bidirectional PIM user@host> show multicast next-hops
Family: INET
ID Refcount KRefcount Downstream interface
2097151 8 4 ge-0/0/1.0
Family: INET6
ID Refcount KRefcount Downstream interface
2097157 2 1 ge-0/0/1.0
Family: Incoming interface list
ID Refcount KRefcount Downstream interface
513 5 2 lo0.0
ge-0/0/1.0
514 5 2 lo0.0
ge-0/0/1.0
xe-4/1/0.0
515 3 1 lo0.0
ge-0/0/1.0
xe-4/1/0.0
544 1 0 lo0.0
xe-4/1/0.0
Copyright © 2016, Juniper Networks, Inc.
369
Multicast Protocols Feature Guide for EX4600 Switches show multicast next-hops brief
The output for the show multicast next-hops brief command is identical to that for the show multicast next-hops command. For sample output, see
show multicast next-hops on page 369
.
show multicast next-hops detail user@host> show multicast next-hops detail
Family: INET
ID Refcount KRefcount Downstream interface
1048577 2 1 fe-0/1/2.0-(1048574)
ge-0/2/3.0-(1048576)
370 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show multicast pim-to-igmp-proxy
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 371
Syntax show multicast pim-to-igmp-proxy
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show multicast pim-to-igmp-proxy
<instance instance-name>
Release Information Command introduced in Junos OS Release 9.6.
Command introduced in Junos OS Release 9.6 for EX Series switches.
instance option introduced in Junos OS Release 10.0.
instance option introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display configuration information about PIM-to-IGMP message translation, also known as PIM-to-IGMP proxy.
Options none —Display configuration information about PIM-to-IGMP message translation for all routing instances.
instance instance-name —(Optional) Display configuration information about PIM-to-IGMP message translation for a specific multicast instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show multicast pim-to-igmp-proxy on page 372 show multicast pim-to-igmp-proxy instance on page 372
Output Fields
describes the output fields for the show multicast pim-to-igmp-proxy command. Output fields are listed in the order in which they appear.
Table 18: show multicast pim-to-igmp-proxy Output Fields
Field Name Field Description
Instance
Proxy state interface-name
Routing instance. Default instance is master (inet.0 routing table).
State of PIM-to-IGMP message translation, also known as
PIM-to-IGMP proxy, on the configured upstream interfaces: enabled or disabled .
Name of upstream interface (no more than two allowed) on which
PIM-to-IGMP message translation is configured.
Copyright © 2016, Juniper Networks, Inc.
371
Multicast Protocols Feature Guide for EX4600 Switches
Sample Output show multicast pim-to-igmp-proxy user@host> show multicast pim-to-igmp-proxy
Instance: master Proxy state: enabled ge-0/1/0.1
ge-0/1/0.2
show multicast pim-to-igmp-proxy instance user@host> show multicast pim-to-igmp-proxy instance VPN-A
Instance: VPN-A Proxy state: enabled ge-0/1/0.1
372 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show multicast pim-to-mld-proxy
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 373
Syntax show multicast pim-to-mld-proxy
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show multicast pim-to-mld-proxy
<instance instance-name>
Release Information Command introduced in Junos OS Release 9.6.
Command introduced in Junos OS Release 9.6 for EX Series switches.
instance option introduced in Junos OS Release 10.3.
instance option introduced in Junos OS Release 10.3 for EX Series switches.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display configuration information about PIM-to-MLD message translation, also known as PIM-to-MLD proxy.
Options none —Display configuration information about PIM-to-MLD message translation for all routing instances.
instance instance-name —(Optional) Display configuration information about PIM-to-MLD message translation for a specific multicast instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show multicast pim-to-mld-proxy on page 374 show multicast pim-to-mld-proxy instance on page 374
Output Fields
describes the output fields for the show multicast pim-to-mld-proxy command. Output fields are listed in the order in which they appear.
Table 19: show multicast pim-to-mld-proxy Output Fields
Field Name Field Description
Proxy state interface-name
State of PIM-to-MLD message translation, also known as
PIM-to-MLD proxy, on the configured upstream interfaces: enabled or disabled .
Name of upstream interface (no more than two allowed) on which
PIM-to-MLD message translation is configured.
Copyright © 2016, Juniper Networks, Inc.
373
Multicast Protocols Feature Guide for EX4600 Switches
Sample Output show multicast pim-to-mld-proxy user@host> show multicast pim-to-mld-proxy
Instance: master Proxy state: enabled ge-0/5/0.1
ge-0/5/0.2
show multicast pim-to-mld-proxy instance user@host> show multicast pim-to-mld-proxy instance VPN-A
Instance: VPN-A Proxy state: enabled ge-0/5/0.1
374 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show multicast route
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 375
Syntax show multicast route
<brief | detail | extensive | summary>
<active | all | inactive>
<group group>
<inet | inet6>
<instance instance name>
<logical-system (all | logical-system-name)>
<regular-expression>
<source-prefix source-prefix>
Syntax (EX Series
Switch and the QFX
Series) show multicast route
<brief | detail | extensive | summary>
<active | all | inactive>
<group group>
<inet | inet6>
<instance instance name>
<regular-expression>
<source-prefix source-prefix>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display the entries in the IP multicast forwarding table. You can display similar information with the show route table inet.1 command.
Options none —Display standard information about all entries in the multicast forwarding table for all routing instances.
brief | detail | extensive | summary —(Optional) Display the specified level of output.
active | all | inactive —(Optional) Display all active entries, all entries, or all inactive entries, respectively, in the multicast forwarding table.
group group —(Optional) Display the cache entries for a particular group.
inet | inet6 —(Optional) Display multicast forwarding table entries for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display entries in the multicast forwarding table for a specific multicast instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Copyright © 2016, Juniper Networks, Inc.
375
Multicast Protocols Feature Guide for EX4600 Switches regular-expression —(Optional) Display information about the multicast forwarding table entries that match a UNIX OS-style regular expression.
source-prefix source-prefix —(Optional) Display the cache entries for a particular source prefix.
Required Privilege
Level view
Related
Documentation
• Example: Configuring Bidirectional PIM
List of Sample Output
show multicast route on page 377
show multicast route (Bidirectional PIM) on page 378 show multicast route brief on page 378
Output Fields
describes the output fields for the show multicast route command.
Output fields are listed in the approximate order in which they appear.
Table 20: show multicast route Output Fields
Field Name Field Description Level of Output family
Group
IPv4 address family ( INET ) or IPv6 address family ( INET6 ).
Group address.
For any-source multicast routes, for example for bidirectional PIM, the group address includes the prefix length.
Source Prefix and length of the source as it is in the multicast forwarding table.
Incoming interface list
List of interfaces that accept incoming traffic. Only shown for routes that do not use strict RPF-based forwarding, for example for bidirectional PIM.
All levels
All levels
All levels
All levels
Upstream interface Name of the interface on which the packet with this source prefix is expected to arrive.
All levels
Upstream rpf interface list
When multicast-only fast reroute (MoFRR) is enabled, a PIM router propagates join messages on two upstream RPF interfaces to receive multicast traffic on both links for the same join request.
All levels
Downstream interface list
List of interface names to which the packet with this source prefix is forwarded.
Number of outgoing interfaces
Total number of outgoing interfaces for each (S,G) entry.
Session description Name of the multicast session.
All levels extensive detail extensive
376 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 20: show multicast route Output Fields (continued)
Field Name Field Description Level of Output
Statistics Rate at which packets are being forwarded for this source and group entry (in
Kbps and pps), and number of packets that have been forwarded to this prefix.
If one or more of the kilobits per second packet forwarding statistic queries fails or times out, the statistics field displays Forwarding statistics are not available .
detail extensive
NOTE: On QFX Series switches and OCX Series switches, this field does not report valid statistics.
Next-hop ID Next-hop identifier of the prefix. The identifier is returned by the routing device’s
Packet Forwarding Engine and is also displayed in the output of the show multicast nexthops command.
detail extensive
Incoming interface list ID
For bidirectional PIM, incoming interface list identifier.
Identifiers for interfaces that accept incoming traffic. Only shown for routes that do not use strict RPF-based forwarding, for example for bidirectional PIM.
detail extensive
Upstream protocol The protocol that maintains the active multicast forwarding route for this group or source.
detail extensive
When the show multicast route extensive command is used with the display-origin-protocol option, the field name is only Protocol and not Upstream
Protocol . However, this field also displays the protocol that installed the active route.
Route type Type of multicast route. Values can be (S,G) or (*,G).
summary
Route state
Route count
Forwarding state
Cache lifetime/timeout
Whether the group is Active
Number of multicast routes.
or Inactive .
summary extensive summary extensive Whether the prefix is pruned or forwarding.
Number of seconds until the prefix is removed from the multicast forwarding table. A value of never indicates a permanent forwarding entry. A value of forever indicates routes that do not have keepalive times.
extensive
Wrong incoming interface notifications
Uptime
Number of times that the upstream interface was not available.
Time since the creation of a multicast route.
extensive extensive
Sample Output show multicast route user@host> show multicast route
Family: INET
Group: 228.0.0.0
Copyright © 2016, Juniper Networks, Inc.
377
Multicast Protocols Feature Guide for EX4600 Switches
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Group: 239.1.1.1
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Group: 239.1.1.1
Source: 10.255.70.15/32
Upstream interface: so-1/0/0.0
Downstream interface list:
mt-1/1/0.1081344
Family: INET6 show multicast route (Bidirectional PIM) user@host> show multicast route
Family: INET
Group: 224.1.1.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0
Downstream interface list:
ge-0/0/1.0
Group: 224.1.3.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0 xe-4/1/0.0
Downstream interface list:
ge-0/0/1.0
Group: 225.1.1.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0
Downstream interface list:
ge-0/0/1.0
Group: 225.1.3.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0 xe-4/1/0.0
Downstream interface list:
ge-0/0/1.0
Family: INET6 show multicast route brief
The output for the show multicast route brief command is identical to that for the show multicast route command. For sample output, see
show multicast route on page 377
or
show multicast route (Bidirectional PIM) on page 378
.
378 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show multicast route detail user@host> show multicast route detail
Family: INET
Group: 228.0.0.0
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Session description: Unknown
Statistics: 8 kBps, 100 pps, 45272 packets
Next-hop ID: 262142
Upstream protocol: PIM
Group: 239.1.1.1
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Session description: Administratively Scoped
Statistics: 0 kBps, 0 pps, 13404 packets
Next-hop ID: 262142
Upstream protocol: PIM
Group: 239.1.1.1
Source: 10.255.70.15/32
Upstream interface: so-1/0/0.0
Downstream interface list:
mt-1/1/0.1081344
Session description: Administratively Scoped
Statistics: 46 kBps, 1000 pps, 921077 packets
Next-hop ID: 262143
Upstream protocol: PIM
Family: INET6 show multicast route extensive (Bidirectional PIM) user@host> show multicast route extensive
Family: INET
Group: 224.1.1.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0
Downstream interface list:
ge-0/0/1.0
Number of outgoing interfaces: 1
Session description: NOB Cross media facilities
Statistics: 0 kBps, 0 pps, 0 packets
Next-hop ID: 2097153
Incoming interface list ID: 585
Upstream protocol: PIM
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 0
Group: 224.1.3.0/24
Copyright © 2016, Juniper Networks, Inc.
379
Multicast Protocols Feature Guide for EX4600 Switches
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0 xe-4/1/0.0
Downstream interface list:
ge-0/0/1.0
Number of outgoing interfaces: 1
Session description: NOB Cross media facilities
Statistics: 0 kBps, 0 pps, 0 packets
Next-hop ID: 2097153
Incoming interface list ID: 589
Upstream protocol: PIM
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 0
Family: INET6 show multicast route instance <instance-name> extensive user@host> show multicast route instance mvpn extensive
Family: INET
Group: 239.10.10.10
Source: 2.0.0.2/32
Upstream interface: xe-0/0/0.102
Downstream interface list:
xe-10/3/0.0 xe-0/3/0.0 xe-0/0/0.106 xe-0/0/0.105
xe-0/0/0.103 xe-0/0/0.104 xe-0/0/0.107 xe-0/0/0.108
Session description: Administratively Scoped
Statistics: 256 kBps, 3998 pps, 670150 packets
Next-hop ID: 1048579
Upstream protocol: MVPN
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 58
Uptime: 00:00:04 show multicast route summary user@host> show multicast route summary
Instance: master Family: INET
Route type Route state Route count
(S,G) Active 2
(S,G) Inactive 3
Instance: master Family: INET6
380 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show multicast rpf
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 381
Syntax show multicast rpf
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<prefix>
<summary>
Syntax (EX Series
Switch and the QFX
Series) show multicast rpf
<inet | inet6>
<instance instance-name>
<prefix>
<summary>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display information about multicast reverse-path-forwarding (RPF) calculations.
Options none —Display RPF calculation information for all supported address families.
inet | inet6 —(Optional) Display the RPF calculation information for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display information about multicast RPF calculations for a specific multicast instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
prefix —(Optional) Display the RPF calculation information for the specified prefix.
summary —(Optional) Display a summary of all multicast RPF information.
Required Privilege
Level view
List of Sample Output
show multicast rpf on page 382
show multicast rpf inet6 on page 383
show multicast rpf prefix on page 384 show multicast rpf summary on page 384
Copyright © 2016, Juniper Networks, Inc.
381
Multicast Protocols Feature Guide for EX4600 Switches
Output Fields
describes the output fields for the show multicast rpf command.
Output fields are listed in the approximate order in which they appear.
Table 21: show multicast rpf Output Fields
Field Name Field Description
Instance
Source prefix
Protocol
Name of the routing instance. (Displayed when multicast is configured within a routing instance.)
Prefix and length of the source as it exists in the multicast forwarding table.
How the route was learned.
Interface
Neighbor
Upstream RPF interface.
NOTE: The displayed interface information does not apply to bidirectional PIM RP addresses. This is because the show multicast rpf command does not take into account equal-cost paths or the designated forwarder. For accurate upstream RPF interface information, always use the show pim join extensive command when bidirectional PIM is configured.
Upstream RPF neighbor.
NOTE: The displayed neighbor information does not apply to bidirectional PIM. This is because the show multicast rpf command does not take into account equal-cost paths or the designated forwarder. For accurate upstream RPF neighbor information, always use the show pim join extensive command when bidirectional PIM is configured.
Sample Output show multicast rpf user@host> show multicast rpf
Multicast RPF table: inet.0, 12 entries
0.0.0.0/0
Protocol: Static
10.255.14.132/32
Protocol: Direct
Interface: lo0.0
10.255.245.91/32
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: 192.168.195.21
127.0.0.1/32
Inactive172.16.0.0/12
Protocol: Static
Interface: fxp0.0
382 Copyright © 2016, Juniper Networks, Inc.
Neighbor: 192.168.14.254
192.168.0.0/16
Protocol: Static
Interface: fxp0.0
Neighbor: 192.168.14.254
192.168.14.0/24
Protocol: Direct
Interface: fxp0.0
192.168.14.132/32
Protocol: Local
192.168.195.20/30
Protocol: Direct
Interface: so-1/1/1.0
192.168.195.22/32
Protocol: Local
192.168.195.36/30
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: 192.168.195.21
show multicast rpf inet6 user@host> show multicast rpf inet6
Multicast RPF table: inet6.0, 12 entries
::10.255.14.132/128
Protocol: Direct
Interface: lo0.0
::10.255.245.91/128
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: fe80::2a0:a5ff:fe28:2e8c
::192.168.195.20/126
Protocol: Direct
Interface: so-1/1/1.0
::192.168.195.22/128
Protocol: Local
::192.168.195.36/126
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: fe80::2a0:a5ff:fe28:2e8c
::192.168.195.76/126
Protocol: Direct
Interface: fe-2/2/0.0
::192.168.195.77/128
Protocol: Local
Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
383
Multicast Protocols Feature Guide for EX4600 Switches fe80::/64
Protocol: Direct
Interface: so-1/1/1.0
fe80::290:69ff:fe0c:993a/128
Protocol: Local fe80::2a0:a5ff:fe12:84f/128
Protocol: Direct
Interface: lo0.0
ff02::2/128
Protocol: PIM ff02::d/128
Protocol: PIM show multicast rpf prefix user@host> show multicast rpf ff02::/16
Multicast RPF table: inet6.0, 13 entries ff02::2/128
Protocol: PIM ff02::d/128
Protocol: PIM
...
show multicast rpf summary user@host> show multicast rpf summary
Multicast RPF table: inet.0, 16 entries
Multicast RPF table: inet6.0, 12 entries
384 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show multicast scope
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 385
Syntax show multicast scope
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show multicast scope
<inet | inet6>
<instance instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display administratively scoped IP multicast information.
Options none —Display standard information about administratively scoped multicast information for all supported address families in all routing instances.
inet | inet6 —(Optional) Display scoped multicast information for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display administratively scoped information for a specific multicast instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
Output Fields
describes the output fields for the show multicast scope command.
Output fields are listed in the approximate order in which they appear.
Table 22: show multicast scope Output Fields
Field Name Field Description
Scope name
Group Prefix
Interface
Name of the multicast scope.
Range of multicast groups that are scoped.
Interface that is the boundary of the administrative scope.
Copyright © 2016, Juniper Networks, Inc.
385
Multicast Protocols Feature Guide for EX4600 Switches
Table 22: show multicast scope Output Fields (continued)
Field Name Field Description
Resolve Rejects Number of kernel resolve rejects.
Sample Output show multicast scope user@host> show multicast scope
Resolve
Scope name Group Prefix Interface Rejects
232-net 232.232.0.0/16 fe-0/0/0.1 0 local 239.255.0.0/16 fe-0/0/0.1 0 local ff05::/16 fe-0/0/0.1 0 larry ff05::1234/128 fe-0/0/0.1 0 show multicast scope inet user@host> show multicast scope inet
Resolve
Scope name Group Prefix Interface Rejects
232-net 232.232.0.0/16 fe-0/0/0.1 0 local 239.255.0.0/16 fe-0/0/0.1 0 show multicast scope inet6 user@host> show multicast scope inet6
Resolve
Scope name Group Prefix Interface Rejects local ff05::/16 fe-0/0/0.1 0 larry ff05::1234/128 fe-0/0/0.1 0
386 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show multicast sessions
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 387
Syntax show multicast sessions
<brief | detail | extensive>
<logical-system (all | logical-system-name)>
<regular-expression>
Syntax (EX Series
Switch and the QFX
Series) show multicast sessions
<brief | detail | extensive>
<regular-expression>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display information about announced IP multicast sessions.
Options none —Display standard information about all multicast sessions for all routing instances.
brief | detail | extensive —(Optional) Display the specified level of output.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
regular-expression —(Optional) Display information about announced sessions that match a UNIX-style regular expression.
Required Privilege
Level view
List of Sample Output
show multicast sessions on page 388 show multicast sessions regular-expression detail on page 388
Output Fields
describes the output fields for the show multicast sessions command.
Output fields are listed in the approximate order in which they appear.
Table 23: show multicast sessions Output Fields
Field Name Field Description session-name Name of the known announced multicast sessions.
Copyright © 2016, Juniper Networks, Inc.
387
Multicast Protocols Feature Guide for EX4600 Switches
Sample Output show multicast sessions user@host> show multicast sessions
1-Department of Biological Sciences, LSU
...
Monterey Bay - DockCam
Monterey Bay - JettyCam
Monterey Bay - StandCam
Monterey DockCam
Monterey DockCam / ROV cam
...
NASA TV (MPEG-1)
...
UO Broadcast - NASA Videos - 25 Years of Progress
UO Broadcast - NASA Videos - Journey through the Solar System
UO Broadcast - NASA Videos - Life in the Universe
UO Broadcast - NASA Videos - Nasa and the Airplane
UO Broadcasts OPB's Oregon Story
UO DOD News Clips
UO Medical Management of Biological Casualties (1)
UO Medical Management of Biological Casualties (2)
UO Medical Management of Biological Casualties (3)
...
376 active sessions.
show multicast sessions regular-expression detail user@host> show multicast sessions "NASA TV" detail
SDP Version: 0 Originated by: [email protected]
Session: NASA TV (MPEG-1)
Description: NASA television in MPEG-1 format, provided by Private University.
Please contact the UO if you have problems with this feed.
Email: Your Name Here <[email protected]>
Phone: Your Name Here <888/555-1212>
Bandwidth: AS:1000
Start time: permanent
Stop time: none
Attribute: type:broadcast
Attribute: tool:IP/TV Content Manager 3.4.14
Attribute: live:capture:1
Attribute: x-iptv-capture:mp1s
Media: video 54302 RTP/AVP 32 31 96 97
Connection Data: 224.2.231.45 ttl 127
Attribute: quality:8
Attribute: framerate:30
Attribute: rtpmap:96 WBIH/90000
Attribute: rtpmap:97 MP4V-ES/90000
Attribute: x-iptv-svr:video 128.223.91.191 live
Attribute: fmtp:32 type=mpeg1
Media: audio 28848 RTP/AVP 14 0 96 3 5 97 98 99 100 101 102 10 11 103 104 105 106
Connection Data: 224.2.145.37 ttl 127
Attribute: rtpmap:96 X-WAVE/8000
Attribute: rtpmap:97 L8/8000/2
Attribute: rtpmap:98 L8/8000
Attribute: rtpmap:99 L8/22050/2
Attribute: rtpmap:100 L8/22050
Attribute: rtpmap:101 L8/11025/2
Attribute: rtpmap:102 L8/11025
Attribute: rtpmap:103 L16/22050/2
388 Copyright © 2016, Juniper Networks, Inc.
Attribute: rtpmap:104 L16/22050
1 matching sessions.
Chapter 18: Multicast Operational Commands
Copyright © 2016, Juniper Networks, Inc.
389
Multicast Protocols Feature Guide for EX4600 Switches show multicast usage
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 390
Syntax show multicast usage
<brief | detail>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show multicast usage
<brief | detail>
<inet | inet6>
<instance instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display usage information about the 10 most active Distance Vector Multicast Routing
Protocol (DVMRP) or Protocol Independent Multicast (PIM) groups.
Options none —Display multicast usage information for all supported address families for all routing instances.
brief | detail —(Optional) Display the specified level of output.
inet | inet6 —(Optional) Display usage information for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display information about the most active DVMRP or PIM groups for a specific multicast instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show multicast usage detail on page 392
Output Fields
describes the output fields for the show multicast usage command.
Output fields are listed in the approximate order in which they appear.
390 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 24: show multicast usage Output Fields
Field Name Field Description
Instance
Group
Sources
Name of the routing instance. (Displayed when multicast is configured within a routing instance.)
Group address.
Number of sources.
Packets
Bytes
Prefix
Number of packets that have been forwarded to this prefix. If one or more of the packets forwarded statistic queries fails or times out, the packets field displays unavailable .
Number of bytes that have been forwarded to this prefix. If one or more of the packets forwarded statistic queries fails or times out, the bytes field displays unavailable .
IP address.
Prefix length.
/len
Groups Number of multicast groups.
Sample Output show multicast usage user@host> show multicast usage
Group Sources Packets Bytes
228.0.0.0 1 52847 4439148
239.1.1.1 2 13450 1125530
Prefix /len Groups Packets Bytes
10.255.14.144 /32 2 66254 5561304
10.255.70.15 /32 1 43 3374...
show multicast usage brief
The output for the show multicast usage brief command is identical to that for the show multicast usage command. For sample output, see
show multicast usage on page 391
.
show multicast usage instance user@host> show multicast usage instance VPN-A
Group Sources Packets Bytes
224.2.127.254 1 5538 509496
224.0.1.39 1 13 624
224.0.1.40 1 13 624
Prefix /len Groups Packets Bytes
192.168.195.34 /32 1 5538 509496
10.255.14.30 /32 1 13 624
Copyright © 2016, Juniper Networks, Inc.
391
Multicast Protocols Feature Guide for EX4600 Switches
10.255.245.91 /32 1 13 624
...
show multicast usage detail user@host> show multicast usage detail
Group Sources Packets Bytes
228.0.0.0 1 53159 4465356
Source: 10.255.14.144 /32 Packets: 53159 Bytes: 4465356
239.1.1.1 2 13450 1125530
Source: 10.255.14.144 /32 Packets: 13407 Bytes: 1122156
Source: 10.255.70.15 /32 Packets: 43 Bytes: 3374
Prefix /len Groups Packets Bytes
10.255.14.144 /32 2 66566 5587512
Group: 228.0.0.0 Packets: 53159 Bytes: 4465356
Group: 239.1.1.1 Packets: 13407 Bytes: 1122156
10.255.70.15 /32 1 43 3374
Group: 239.1.1.1 Packets: 43 Bytes: 3374
392 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim bootstrap
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 393
Syntax show pim bootstrap
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show pim bootstrap
<instance instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
instance option introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description For sparse mode only, display information about Protocol Independent Multicast (PIM) bootstrap routers.
Options none —Display PIM bootstrap router information for all routing instances.
instance instance-name —(Optional) Display information about bootstrap routers for a specific PIM-enabled routing instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show pim bootstrap on page 394 show pim bootstrap instance on page 394
Output Fields
describes the output fields for the show pim bootstrap command.
Output fields are listed in the approximate order in which they appear.
Table 25: show pim bootstrap Output Fields
Field Name Field Description
Instance Name of the routing instance.
BSR
Pri
Local address
Bootstrap router.
Priority of the routing device as elected to be the bootstrap router.
Pri
Local routing device address.
Local routing device address priority to be elected as the bootstrap router.
Copyright © 2016, Juniper Networks, Inc.
393
Multicast Protocols Feature Guide for EX4600 Switches
Table 25: show pim bootstrap Output Fields (continued)
Field Name Field Description
State
Timeout
Local routing device election state: Candidate , Elected , or Ineligible .
How long until the local routing device declares the bootstrap router to be unreachable, in seconds.
Sample Output show pim bootstrap user@host> show pim bootstrap
Instance: PIM.master
BSR Pri Local address Pri State Timeout
None 0 10.255.71.46 0 InEligible 0 feco:1:1:1:1:0:aff:785c 34 feco:1:1:1:1:0:aff:7c12 0 InEligible 0 show pim bootstrap instance user@host> show pim bootstrap instance VPN-A
Instance: PIM.VPN-A
BSR Pri Local address Pri State Timeout
None 0 192.168.196.105 0 InEligible 0
394 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim interfaces
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 395
Syntax show pim interfaces
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show pim interfaces
<inet | inet6>
<instance instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Commmand introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Description Display information about the interfaces on which Protocol Independent Multicast (PIM) is configured.
Options none —Display interface information for all family addresses for all routing instances.
inet | inet6 —(Optional) Display interface information for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display information about interfaces for a specific
PIM-enabled routing instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show pim interfaces on page 396
Output Fields
describes the output fields for the show pim interfaces command.
Output fields are listed in the approximate order in which they appear.
Table 26: show pim interfaces Output Fields
Field Name Field Description
Instance Name of the routing instance.
Interface name.
Name
State State of the interface. The state also is displayed in the show interfaces command.
Copyright © 2016, Juniper Networks, Inc.
395
Multicast Protocols Feature Guide for EX4600 Switches
Table 26: show pim interfaces Output Fields (continued)
Field Name Field Description
Mode
IP
V
State
PIM mode running on the interface:
•
•
B —In bidirectional mode, multicast groups are carried across the network over bidirectional shared trees. This type of tree minimizes PIM routing state, which is especially important in networks with numerous and dispersed senders and receivers.
S —In sparse mode, routing devices must join and leave multicast groups explicitly. Upstream routing devices do not forward multicast traffic to this routing device unless this device has sent an explicit request (using a join message) to receive multicast traffic.
• Dense —Unlike sparse mode, where data is forwarded only to routing devices sending an explicit request, dense mode implements a flood-and-prune mechanism, similar to DVMRP (the first multicast protocol used to support the multicast backbone). (Not supported on QFX Series.)
• Sparse-Dense —Sparse-dense mode allows the interface to operate on a per-group basis in either sparse or dense mode. A group specified as dense is not mapped to a rendezvous point (RP).
Instead, data packets destined for that group are forwarded using PIM-Dense Mode (PIM-DM) rules. A group specified as sparse is mapped to an RP, and data packets are forwarded using
PIM-Sparse Mode (PIM-SM) rules. (Not supported on QFX Series.)
When sparse-dense mode is configured, the output includes both S and D . When bidirectional-sparse mode is configured, the output includes S and B . When bidirectional-sparse-dense mode is configured, the output includes B , S , and D .
Version number of the address family on the interface: 4 (IPv4) or 6 (IPv6).
PIM version running on the interface: 1 or 2 .
State of PIM on the interface:
•
•
•
•
•
Active —Bidirectional mode is enabled on the interface and on all PIM neighbors.
DR —Designated router.
NotCap —Bidirectional mode is not enabled on the interface. This can happen when bidirectional
PIM is not configured locally, when one of the neighbors is not configured for bidirectional PIM, or when one of the neighbors has not implemented the bidirectional PIM protocol.
NotDR —Not the designated router.
P2P —Point to point.
Number of neighbors that have been seen on the interface.
NbrCnt
JoinCnt(sg)
JointCnt(*g)
DR address
Number of (s,g) join messages that have been seen on the interface.
Number of (*,g) join messages that have been seen on the interface.
Address of the designated router.
Sample Output show pim interfaces user@host> show pim interfaces
Stat = Status, V = Version, NbrCnt = Neighbor Count,
S = Sparse, D = Dense, B = Bidirectional,
DR = Designated Router, P2P = Point-to-point link,
396 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Active = Bidirectional is active, NotCap = Not Bidirectional Capable
Name Stat Mode IP V State NbrCnt JoinCnt(sg/*g) DR address ge-0/3/0.0 Up S 4 2 NotDR,NotCap 1 0/0 40.0.0.3
ge-0/3/3.50 Up S 4 2 DR,NotCap 1 9901/100 50.0.0.2
ge-0/3/3.51 Up S 4 2 DR,NotCap 1 0/0 51.0.0.2
pe-1/2/0.32769 Up S 4 2 P2P,NotCap 0 0/0
Copyright © 2016, Juniper Networks, Inc.
397
Multicast Protocols Feature Guide for EX4600 Switches show pim join
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 398
Syntax show pim join
<brief | detail | extensive | summary>
<bidirectional | dense | sparse>
<exact>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<range>
<rp ip-address/prefix | source ip-address/prefix>
<sg | star-g>
Syntax (EX Series
Switch and the QFX
Series) show pim join
<brief | detail | extensive | summary>
<dense | sparse>
<exact>
<inet | inet6>
<instance instance-name>
<range>
<rp ip-address/prefix | source ip-address/prefix>
<sg | star-g>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
summary option introduced in Junos OS Release 9.6.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Support for bidirectional PIM added in Junos OS Release 12.1.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Multiple new filter options introduced in Junos OS Release 13.2.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display information about Protocol Independent Multicast (PIM) groups for all PIM modes.
For bidirectional PIM, display information about PIM group ranges (*,G-range) for each active bidirectional RP group range, in addition to each of the joined (*,G) routes.
Options none —Display the standard information about PIM groups for all supported family addresses for all routing instances.
brief | detail | extensive | summary —(Optional) Display the specified level of output.
bidirectional | dense | sparse —(Optional) Display information about PIM bidirectional mode, dense mode, or sparse and source-specific multicast (SSM) mode entries.
exact —(Optional) Display information about only the group that exactly matches the specified group address.
398 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands inet | inet6 —(Optional) Display PIM group information for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display information about groups for the specified
PIM-enabled routing instance only.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
range —(Optional) Address range of the group, specified as prefix/prefix-length.
rp ip-address/prefix | source ip-address/prefix —(Optional) Display information about the
PIM entries with a specified rendezvous point (RP) address and prefix or with a specified source address and prefix. You can omit the prefix.
sg | star-g —(Optional) Display information about PIM (S,G) or (*,G) entries.
Required Privilege
Level view
Related
Documentation
•
• Example: Configuring Bidirectional PIM
List of Sample Output
show pim join summary on page 403 show pim join (PIM Sparse Mode) on page 403
show pim join (Bidirectional PIM) on page 404 show pim join inet6 on page 404
show pim join extensive (PIM Sparse Mode) on page 406
show pim join extensive (Bidirectional PIM) on page 407
show pim join extensive (Bidirectional PIM with a Directly Connected Phantom
RP) on page 408 show pim join instance <instance-name> extensive on page 408
show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for
Point-to-Multipoint LSPs) on page 409
show pim join extensive (Egress Node with Multipoint LDP Inband Signaling for
Point-to-Multipoint LSPs) on page 410
show pim join summary on page 411
show pim join (PIM Sparse Mode) on page 412 show pim join (Bidirectional PIM) on page 412
show pim join detail on page 414 show pim join extensive (PIM Sparse Mode) on page 414
show pim join extensive (Bidirectional PIM) on page 415
Copyright © 2016, Juniper Networks, Inc.
399
Multicast Protocols Feature Guide for EX4600 Switches
show pim join extensive (Bidirectional PIM with a Directly Connected Phantom
RP) on page 416 show pim join instance <instance-name> extensive on page 416
show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for
Point-to-Multipoint LSPs) on page 417
show pim join extensive (Multipoint LDP with Multicast-Only Fast Reroute) on page 418
Output Fields
describes the output fields for the show pim join command. Output fields are listed in the approximate order in which they appear.
Table 27: show pim join Output Fields
Field Name Field Description Level of Output
R
S
Instance
Family
Route type
Route count
W
Group
Name of the routing instance.
Name of the address family: inet (IPv4) or inet6
(IPv6).
Type of multicast route: (S,G) or (*,G).
summary
Number of (S,G) routes and number of (*,G) routes.
summary
Rendezvous Point Tree.
brief detail extensive none brief detail extensive none Sparse.
Wildcard.
brief detail extensive summary none brief detail extensive summary none
Group address.
brief detail extensive none brief detail extensive none
Bidirectional group prefix length
For bidirectional PIM, length of the IP prefix for RP group ranges.
All levels
Source brief detail extensive none Multicast source:
•
•
•
* (wildcard value) ipv4-address ipv6-address
Rendezvous point for the PIM group.
RP
Flags brief detail extensive none brief detail extensive none PIM flags:
•
•
•
•
•
• bidirectional —Bidirectional mode entry.
dense rptree sparse
—Dense mode entry.
—Entry is on the rendezvous point tree.
source.
—Sparse mode entry.
spt —Entry is on the shortest-path tree for the wildcard —Entry is on the shared tree.
400 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 27: show pim join Output Fields (continued)
Field Name Field Description Level of Output
Upstream interface RPF interface toward the source address for the source-specific state (S,G) or toward the rendezvous point (RP) address for the non-source-specific state (*,G).
For bidirectional PIM, RP Link means that the interface is directly connected to a subnet that contains a phantom RP address.
A pseudo multipoint LDP (M-LDP) interface appears on egress nodes in M-LDP point-to-multipoint LSPs with inband signaling.
brief detail extensive none
Upstream neighbor Information about the upstream neighbor: Direct ,
Local , Unknown , or a specific IP address.
For bidirectional PIM, Direct means that the interface is directly connected to a subnet that contains a phantom RP address.
extensive
The multipoint LDP (M-LDP) root appears on egress nodes in M-LDP point-to-multipoint LSPs with inband signaling.
Upstream state When multicast-only fast reroute (MoFRR) is configured in a PIM domain, the upstream interface for the active path. A PIM router propagates join messages on two upstream RPF interfaces to receive multicast traffic on both links for the same join request. Preference is given to two paths that do not converge to the same immediate upstream router. PIM installs appropriate multicast routes with upstream neighbors as RPF next hops with two
(primary and backup) interfaces.
extensive
Active upstream neighbor
On the MoFRR primary path, the IP address of the neighbor that is directly connected to the active upstream interface.
extensive
MoFRR Backup upstream interface
The MoFRR upstream interface that is used when the primary path fails.
When the primary path fails, the backup path is upgraded to primary, and traffic is forwarded accordingly. If there are alternate paths available, a new backup path is calculated and the appropriate multicast route is updated or installed.
extensive
Copyright © 2016, Juniper Networks, Inc.
401
Multicast Protocols Feature Guide for EX4600 Switches
Table 27: show pim join Output Fields (continued)
Field Name Field Description
Upstream state
Downstream neighbors
Level of Output
Information about the upstream interface:
•
•
•
Join to RP —Sending a join to the rendezvous point.
Join to Source —Sending a join to the source.
Local RP —Sending neither join messages nor prune messages toward the RP, because this routing device is the rendezvous point.
•
•
•
Local Source —Sending neither join messages nor prune messages toward the source, because the source is locally attached to this routing device.
No Prune to RP —Automatically sent to RP when
SPT and RPT are on the same path.
Prune to RP —Sending a prune to the rendezvous point.
• Prune to Source —Sending a prune to the source.
NOTE: RP group range entries have None in the
Upstream state field because RP group ranges do not trigger actual PIM join messages between routing devices.
extensive
Information about downstream interfaces:
• Interface —Interface name for the downstream neighbor.
A pseudo PIM-SM interface appears for all
IGMP-only interfaces.
•
•
•
•
A pseudo multipoint LDP (M-LDP) interface appears on ingress root nodes in M-LDP point-to-multipoint LSPs with inband signaling.
Interface address —Address of the downstream neighbor.
State —Information about the downstream neighbor: join or prune .
Flags —PIM join flags: R (RPtree) , S (Sparse) , W
(Wildcard) , or zero .
Uptime —Time since the downstream interface joined the group.
•
•
Time since last Join —Time since the last join message was received from the downstream interface.
Time since last Prune —Time since the last prune message was received from the downstream interface.
extensive
Assert Timeout
Assert Timeout Length of time between assert cycles on the downstream interface. Not displayed if the assert timer is null.
extensive
402 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 27: show pim join Output Fields (continued)
Field Name Field Description Level of Output
Keepalive timeout Time remaining until the downstream join state is updated (in seconds). If the downstream join state is not updated before this keepalive timer reaches zero, the entry is deleted. If there is a directly connected host, Keepalive timeout is Infinity .
extensive
Uptime
Bidirectional accepting interfaces
Time since the creation of (S,G) or (*,G) state. The uptime is not refreshed every time a PIM join message is received for an existing (S,G) or (*,G) state.
extensive
Interfaces on the router that forward bidirectional
PIM traffic.
The reasons for forwarding bidirectional PIM traffic are that the interface is the winner of the designated forwarder election ( DF Winner ), or the interface is the reverse path forwarding (RPF) interface toward the RP ( RPF ).
extensive
Sample Output show pim join summary user@host> show pim join summary
Instance: PIM.master Family: INET
Route type Route count
(s,g) 2
(*,g) 1
Instance: PIM.master Family: INET6 show pim join (PIM Sparse Mode) user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Copyright © 2016, Juniper Networks, Inc.
403
Multicast Protocols Feature Guide for EX4600 Switches show pim join (Bidirectional PIM) user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join inet6
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard user@host> show pim join inet6
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: ff04::e000:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
Group: ff04::e800:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
404 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Group: ff04::e800:101
Source: ::1.1.1.2
Flags: sparse
Upstream interface: unknown (no neighbor) show pim join inet6 star-g user@host> show pim join inet6 star-g
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local show pim join instance <instance-name> user@host> show pim join instance VPN-A
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Instance: PIM.VPN-A Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join detail user@host> show pim join detail
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Copyright © 2016, Juniper Networks, Inc.
405
Multicast Protocols Feature Guide for EX4600 Switches
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join extensive (PIM Sparse Mode) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
10.111.10.2 State: Join Flags: SRW Timeout: 174
Uptime: 00:03:49 Time since last Join: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: SRW Timeout: Infinity
Uptime: 00:03:49 Time since last Join: 00:01:49
Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local Source, Local RP
Keepalive timeout: 344
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
10.111.10.2 State: Join Flags: S Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: S Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Upstream neighbor: 10.111.10.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 344
Uptime: 00:03:49
Downstream neighbors:
Interface: Pseudo-GMP
fe-0/0/0.0 fe-0/0/1.0 fe-0/0/3.0
Interface: so-1/0/0.0 (pruned)
10.111.10.2 State: Prune Flags: SR Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
406 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
10.10.47.100 State: Join Flags: S Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 3
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join extensive (Bidirectional PIM) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Number of downstream interfaces: 0
Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Downstream neighbors:
Interface: lt-1/0/10.24
10.0.24.4 State: Join RW Timeout: 185
Interface: lt-1/0/10.23
10.0.23.3 State: Join RW Timeout: 184
Number of downstream interfaces: 2
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Upstream neighbor: Direct
Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Interface: xe-4/1/0.0 (DF Winner)
Number of downstream interfaces: 0
Copyright © 2016, Juniper Networks, Inc.
407
Multicast Protocols Feature Guide for EX4600 Switches
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join extensive (Bidirectional PIM with a Directly Connected Phantom RP) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Upstream neighbor: Direct
Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Interface: xe-4/1/0.0 (DF Winner)
Number of downstream interfaces: 0 show pim join instance <instance-name> extensive user@host> show pim join instance VPN-A extensive
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
Interface: mt-1/1/0.32768
10.10.47.101 State: Join Flags: SRW Timeout: 156
Uptime: 00:03:49 Time since last Join: 00:01:49
Number of downstream interfaces: 1
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Upstream neighbor: 10.111.30.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52
Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Upstream neighbor: 10.111.20.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52
408 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 232.1.1.1
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:55
Downstream neighbors:
Interface: Pseudo-MLDP
Interface: lt-1/2/0.25
1.2.5.2 State: Join Flags: S Timeout: Infinity
Uptime: 11:27:55 Time since last Join: 11:27:55
Group: 232.1.1.2
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.1.1.3
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.2.2.2
Source: 1.2.7.7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:25
Downstream neighbors:
Interface: Pseudo-MLDP
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff3e::1:2
Source: abcd::1:2:7:7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Copyright © 2016, Juniper Networks, Inc.
409
Multicast Protocols Feature Guide for EX4600 Switches
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:26
Downstream neighbors:
Interface: Pseudo-MLDP show pim join extensive (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 227.1.1.1
Source: *
RP: 1.1.1.1
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 11:31:33
Downstream neighbors:
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: SRW Timeout: Infinity
Uptime: 11:31:33 Time since last Join: 11:31:32
Group: 232.1.1.1
Source: 192.168.219.11
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:32
Downstream neighbors:
Interface: so-0/1/3.0
192.168.92.9 State: Join Flags: S Timeout: Infinity
Uptime: 11:31:30 Time since last Join: 11:31:30
Downstream neighbors:
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: S Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32
Group: 232.1.1.2
Source: 192.168.219.11
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:32
Downstream neighbors:
Interface: so-0/1/3.0
192.168.92.9 State: Join Flags: S Timeout: Infinity
Uptime: 11:31:30 Time since last Join: 11:31:30
Downstream neighbors:
Interface: lt-1/2/0.14
1.1.4.4 State: Join Flags: S Timeout: 177
Uptime: 11:30:33 Time since last Join: 00:00:33
Downstream neighbors:
410 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: S Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32
Group: 232.1.1.3
Source: 192.168.219.11
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:32
Downstream neighbors:
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: S Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32
Group: 232.2.2.2
Source: 1.2.7.7
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:30
Downstream neighbors:
Interface: so-0/1/3.0
192.168.92.9 State: Join Flags: S Timeout: Infinity
Uptime: 11:31:30 Time since last Join: 11:31:30
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff3e::1:2
Source: abcd::1:2:7:7
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:32
Downstream neighbors:
Interface: fe-1/3/0.0
fe80::21f:12ff:fea5:c4db State: Join Flags: S Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32
Sample Output show pim join summary user@host> show pim join summary
Instance: PIM.master Family: INET
Route type Route count
(s,g) 2
(*,g) 1
Instance: PIM.master Family: INET6
Copyright © 2016, Juniper Networks, Inc.
411
Multicast Protocols Feature Guide for EX4600 Switches show pim join (PIM Sparse Mode) user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join (Bidirectional PIM) user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
412 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim join inet6 user@host> show pim join inet6
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: ff04::e000:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
Group: ff04::e800:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
Group: ff04::e800:101
Source: ::1.1.1.2
Flags: sparse
Upstream interface: unknown (no neighbor) show pim join inet6 star-g user@host> show pim join inet6 star-g
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local show pim join instance <instance-name> user@host> show pim join instance VPN-A
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Copyright © 2016, Juniper Networks, Inc.
413
Multicast Protocols Feature Guide for EX4600 Switches
Instance: PIM.VPN-A Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join detail user@host> show pim join detail
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join extensive (PIM Sparse Mode) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
10.111.10.2 State: Join Flags: SRW Timeout: 174
Uptime: 00:03:49 Time since last Join: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: SRW Timeout: Infinity
Uptime: 00:03:49 Time since last Join: 00:01:49
Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local Source, Local RP
Keepalive timeout: 344
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
414 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
10.111.10.2 State: Join Flags: S Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: S Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Upstream neighbor: 10.111.10.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 344
Uptime: 00:03:49
Downstream neighbors:
Interface: Pseudo-GMP
fe-0/0/0.0 fe-0/0/1.0 fe-0/0/3.0
Interface: so-1/0/0.0 (pruned)
10.111.10.2 State: Prune Flags: SR Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: S Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 3
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join extensive (Bidirectional PIM) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Number of downstream interfaces: 0
Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Copyright © 2016, Juniper Networks, Inc.
415
Multicast Protocols Feature Guide for EX4600 Switches
Downstream neighbors:
Interface: lt-1/0/10.24
10.0.24.4 State: Join RW Timeout: 185
Interface: lt-1/0/10.23
10.0.23.3 State: Join RW Timeout: 184
Number of downstream interfaces: 2
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Upstream neighbor: Direct
Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Interface: xe-4/1/0.0 (DF Winner)
Number of downstream interfaces: 0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard show pim join extensive (Bidirectional PIM with a Directly Connected Phantom RP) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Upstream neighbor: Direct
Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0 (RPF)
Interface: lo0.0 (DF Winner)
Interface: xe-4/1/0.0 (DF Winner)
Number of downstream interfaces: 0 show pim join instance <instance-name> extensive user@host> show pim join instance VPN-A extensive
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
416 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Interface: mt-1/1/0.32768
10.10.47.101 State: Join Flags: SRW Timeout: 156
Uptime: 00:03:49 Time since last Join: 00:01:49
Number of downstream interfaces: 1
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Upstream neighbor: 10.111.30.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52
Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Upstream neighbor: 10.111.20.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52 show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs) user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 232.1.1.1
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:55
Downstream neighbors:
Interface: Pseudo-MLDP
Interface: lt-1/2/0.25
1.2.5.2 State: Join Flags: S Timeout: Infinity
Uptime: 11:27:55 Time since last Join: 11:27:55
Group: 232.1.1.2
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.1.1.3
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Copyright © 2016, Juniper Networks, Inc.
417
Multicast Protocols Feature Guide for EX4600 Switches
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.2.2.2
Source: 1.2.7.7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:25
Downstream neighbors:
Interface: Pseudo-MLDP
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff3e::1:2
Source: abcd::1:2:7:7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:26
Downstream neighbors:
Interface: Pseudo-MLDP show pim join extensive (Multipoint LDP with Multicast-Only Fast Reroute) user@host> show pim join 225.1.1.1 extensive sg
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 225.1.1.1
Source: 10.0.0.1
Flags: sparse,spt
Active upstream interface: fe-1/2/13.0
Active upstream neighbor: 10.0.0.9
MoFRR Backup upstream interface: fe-1/2/14.0
MoFRR Backup upstream neighbor: 10.0.0.21
Upstream state: Join to Source, No Prune to RP
Keepalive timeout: 354
Uptime: 00:00:06
Downstream neighbors:
Interface: fe-1/2/15.0
10.0.0.13 State: Join Flags: S Timeout: Infinity
Uptime: 00:00:06 Time since last Join: 00:00:06
Number of downstream interfaces: 1
418 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim neighbors
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 419
Syntax show pim neighbors
<brief | detail>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show pim neighbors
<brief | detail>
<inet | inet6>
<instance instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Support for the instance all option added in Junos OS Release 12.1.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display information about Protocol Independent Multicast (PIM) neighbors.
Options none —(Same as brief) Display standard information about PIM neighbors for all supported family addresses for the main instance.
brief | detail —(Optional) Display the specified level of output.
inet | inet6 —(Optional) Display information about PIM neighbors for IPv4 or IPv6 family addresses, respectively.
instance (instance-name | all) —(Optional) Display information about neighbors for the specified PIM-enabled routing instance or for all routing instances.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show pim neighbors detail (With BFD) on page 422
Output Fields
describes the output fields for the show pim neighbors command.
Output fields are listed in the approximate order in which they appear.
Copyright © 2016, Juniper Networks, Inc.
419
Multicast Protocols Feature Guide for EX4600 Switches
Table 28: show pim neighbors Output Fields
Field Name Field Description
Instance Name of the routing instance.
Interface through which the neighbor is reachable.
Interface
Neighbor addr
IP
V
Mode
Option
Uptime
Level of Output
All levels
All levels
Address of the neighboring PIM routing device.
IP version: 4 or 6 .
All levels
All levels
PIM version running on the neighbor: 1 or 2 .
All levels
PIM mode of the neighbor: Sparse , Dense , SparseDense , or Unknown . When the neighbor is running PIM version 2, this mode is always Unknown .
All levels
Can be one or more of the following:
•
•
•
•
•
•
B —Bidirectional Capable.
G —Generation Identifier.
H
L
P
T
—Hello Option Holdtime.
—Hello Option LAN Prune Delay.
—Hello Option DR Priority.
—Tracking bit.
brief none
Time the neighbor has been operational since the PIM process was last initialized, in the format dd:hh:mm:ss ago for less than a week and nwnd:hh:mm:ss ago for more than a week.
All levels
Address
BFD
Hello Option
Holdtime
Address of the neighboring PIM routing device.
Default holdtime and the time remaining if the holdtime option is not in the received hello message.
detail
Status and operational state of the Bidirectional Forwarding Detection (BFD) protocol on the interface: Enabled , Operational state is up , or Disabled .
detail
Time for which the neighbor is available, in seconds. The range of values is
0 through 65,535.
detail detail Hello Default
Holdtime
Hello Option DR
Priority
Designated router election priority. The range of values is 0 through 255 .
detail
Hello Option
Generation ID
Hello Option LAN
Prune Delay
9-digit or 10-digit number used to tag hello messages.
Hello Option
Bi-Directional PIM supported
Neighbor can process bidirectional PIM messages.
detail detail
Time to wait before the neighbor receives prune messages, in the format delay
nnn ms override nnnn ms .
detail
420 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 28: show pim neighbors Output Fields (continued)
Field Name Field Description
Neighbor is capable of join suppression.
Join Suppression supported
Rx Join Information about joins received from the neighbor.
•
•
•
Group —Group addresses in the join message.
Source —Address of the source in the join message.
Timeout —Time for which the join is valid.
Level of Output detail detail
Sample Output show pim neighbors user@host> show pim neighbors
Instance: PIM.master
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority, T = Tracking bit
Interface IP V Mode Option Uptime Neighbor addr so-1/0/0.0 4 2 HPLG 00:07:10 10.111.10.2
show pim neighbors brief
The output for the show pim neighbors brief command is identical to that for the show pim neighbors command. For sample output, see
show pim neighbors on page 421
.
show pim neighbors instance user@host> show pim neighbors instance VPN-A
Instance: PIM.VPN-A
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority, T = Tracking bit
Interface IP V Mode Option Uptime Neighbor addr at-0/3/1.0 4 2 HPLG 00:07:54 10.111.30.2
mt-1/1/0.32768 4 2 HPLG 00:07:22 10.10.47.101
so-1/0/1.0 4 2 HPLG 00:07:50 10.111.20.2
show pim neighbors detail user@host> show pim neighbors detail
Instance: PIM.master
Interface: ge-0/0/1.0
Address: 10.10.1.1, IPv4, PIM v2, Mode: SparseDense, sg Join Count: 0, tsg
Join Count: 2
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 2053759302
Hello Option Bi-Directional PIM supported
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Copyright © 2016, Juniper Networks, Inc.
421
Multicast Protocols Feature Guide for EX4600 Switches
Address: 10.10.1.2, IPv4, PIM v2, sg Join Count: 0, tsg Join Count: 2
BFD: Disabled
Hello Option Holdtime: 105 seconds 93 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1734018161
Hello Option Bi-Directional PIM supported
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Interface: lo0.0
Address: 10.255.179.246, IPv4, PIM v2, Mode: SparseDense, sg Join Count:
0, tsg Join Count: 0
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 1997462267
Hello Option Bi-Directional PIM supported
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported show pim neighbors detail (With BFD) user@host> show pim neighbors detail
Instance: PIM.master
Interface: fe-1/0/0.0
Address: 192.168.11.1, IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 836607909
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Address: 192.168.11.2, IPv4, PIM v2
BFD: Enabled, Operational state is up
Hello Default Holdtime: 105 seconds 104 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1907549685
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Interface: fe-1/0/1.0
Address: 192.168.12.1, IPv4, PIM v2
BFD: Disabled
Hello Default Holdtime: 105 seconds 80 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1971554705
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
422 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim rps
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 423
Syntax show pim rps
<brief | detail | extensive>
<group-address>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show pim rps
<brief | detail | extensive>
<group-address>
<inet | inet6>
<instance instance-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display information about Protocol Independent Multicast (PIM) rendezvous points
(RPs).
Options none —Display standard information about PIM RPs for all groups and family addresses for all routing instances.
brief | detail | extensive —(Optional) Display the specified level of output.
group-address —(Optional) Display the RPs for a particular group. If you specify a group address, the output lists the routing device that is the RP for that group.
inet | inet6 —(Optional) Display information for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display information about RPs for a specific
PIM-enabled routing instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
Related
Documentation
• Example: Configuring Bidirectional PIM
List of Sample Output
show pim rps on page 426 show pim rps brief on page 426
Copyright © 2016, Juniper Networks, Inc.
423
Multicast Protocols Feature Guide for EX4600 Switches
Output Fields
describes the output fields for the show pim rps command. Output fields are listed in the approximate order in which they appear.
Table 29: show pim rps Output Fields
Field Name Field Description Level of Output
Instance
Family or Address family
Name of the routing instance.
Name of the address family: inet (IPv4) or inet6 (IPv6).
RP address
Type
Address of the rendezvous point.
All levels
Type of RP:
•
•
•
• auto-rp —Address of the RP known through the Auto-RP protocol.
bootstrap
(BSR).
—Address of the RP known through the bootstrap router protocol embedded —Address of the RP known through an embedded RP (IPv6).
static —Address of RP known through static configuration.
How long to keep the RP active, with time remaining, in seconds.
brief none
All levels Holdtime
Timeout
All levels
All levels
Groups
Group prefixes
Learned via
Mode
How long until the local routing device determines the RP to be unreachable, in seconds.
All levels
Number of groups currently using this RP.
Addresses of groups that this RP can span.
All levels brief none detail extensive Address and method by which the RP was learned.
The PIM mode of the RP: bidirectional or sparse.
If a sparse and bidirectional RPs are configured with the same RP address, they appear as separate entries in both formats.
All levels
424 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 29: show pim rps Output Fields (continued)
Field Name Field Description Level of Output
Time Active
Device Index
Subunit
How long the RP has been active, in the format hh:mm:ss .
detail extensive
Index value of the order in which Junos OS finds and initializes the interface.
For bidirectional RPs, the Device Index output field is omitted because bidirectional RPs do not require encapsulation and de-encapsulation interfaces.
detail extensive
Logical unit number of the interface.
For bidirectional RPs, the Subunit output field is omitted because bidirectional
RPs do not require encapsulation and de-encapsulation interfaces.
detail extensive
Interface
Group Ranges
Either the encapsulation or the de-encapsulation logical interface, depending on whether this routing device is a designated router (DR) facing an RP router, or is the local RP, respectively.
For bidirectional RPs, the Interface output field is omitted because bidirectional
RPs do not require encapsulation and de-encapsulation interfaces.
detail extensive
Addresses of groups that this RP spans.
detail extensive group-address
Active groups using
RP
Number of groups currently using this RP.
total Total number of active groups for this RP.
Register State for
RP detail extensive detail extensive
Current register state for each group:
•
•
Group —Multicast group address.
Source —Multicast source address for which the PIM register is sent or received, depending on whether this router is a designated router facing an RP router, or is the local RP, respectively:
• First Hop —PIM-designated routing device that sent the Register message
(the source address in the IP header).
•
•
•
•
RP Address —RP to which the Register message was sent (the destination address in the IP header).
State :
On the designated router:
•
Send —Sending Register messages.
Probe —Sent a null register. If a Register-Stop message does not arrive in
5 seconds, the designated router resumes sending Register messages.
Suppress —Received a Register-Stop message. The designated router is waiting for the timer to resume before changing to Probe state.
• On the RP:
• Receive —Receiving Register messages.
extensive
Anycast-PIM rpset If anycast RP is configured, the addresses of the RPs in the set.
extensive
Copyright © 2016, Juniper Networks, Inc.
425
Multicast Protocols Feature Guide for EX4600 Switches
Table 29: show pim rps Output Fields (continued)
Field Name Field Description Level of Output
Anycast-PIM local address used
If anycast RP is configured, the local address used by the RP.
Anycast-PIM
Register State extensive
If anycast RP is configured, the current register state for each group:
•
•
•
Group —Multicast group address.
Source —Multicast source address for which the PIM register is sent or received, depending on whether this routing device is a designated router facing an RP router, or is the local RP, respectively.
•
•
•
Origin —How the information was obtained:
DIRECT —From a local attachment
MSDP
DR
—From the Multicast Source Discovery Protocol (MSDP)
—From the designated router extensive
RP selected For sparse mode and bidirectional mode, the identity of the RP for the specified group address.
group-address
Sample Output show pim rps user@host> show pim rps
Instance: PIM.master
Address family INET
RP address Type Mode Holdtime Timeout Groups Group prefixes
10.10.1.3 static bidir 150 None 2 224.1.3.0/24
225.1.3.0/24
10.10.13.2 static bidir 150 None 2 224.1.1.0/24
225.1.1.0/24 show pim rps brief
The output for the show pim rps brief command is identical to that for the show pim rps command. For sample output, see
.
show pim rps <group-address> user@host> show pim rps 235.100.100.0
Instance: PIM.master
Instance: PIM.master
RP selected: 100.100.100.100
show pim rps <group-address> (Bidirectional PIM) user@host> show pim rps 224.1.1.1
Instance: PIM.master
224.1.0.0/16
11.4.12.75 (Bidirectional)
RP selected: 11.4.12.75
426 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim rps <group-address> (PIM Dense Mode) user@host> show pim rps 224.1.1.1
Instance: PIM.master
Dense Mode active for group 224.1.1.1
show pim rps <group-address> (SSM Range Without asm-override-ssm Configured) user@host> show pim rps 224.1.1.1
Instance: PIM.master
Source-specific Mode (SSM) active for group 224.1.1.1
show pim rps <group-address> (SSM Range With asm-override-ssm Configured and a Sparse-Mode RP) user@host> show pim rps 224.1.1.1
Instance: PIM.master
Source-specific Mode (SSM) active with Sparse Mode ASM override for group 224.1.1.1
224.1.0.0/16
11.4.12.75
RP selected: 11.4.12.75
show pim rps <group-address> (SSM Range With asm-override-ssm Configured and a Bidirectional RP) user@host> show pim rps 224.1.1.1
Instance: PIM.master
Source-specific Mode (SSM) active with Sparse Mode ASM override for group 224.1.1.1
224.1.0.0/16
11.4.12.75 (Bidirectional)
RP selected: (null) show pim rps instance user@host> show pim rps instance VPN-A
Instance: PIM.VPN-A
Address family INET
RP address Type Holdtime Timeout Groups Group prefixes
10.10.47.100 static 0 None 1 224.0.0.0/4
Address family INET6 show pim rps extensive (PIM Sparse Mode) user@host> show pim rps extensive
Instance: PIM.master
Family: INET
RP: 10.255.245.91
Learned via: static configuration
Time Active: 00:05:48
Holdtime: 45 with 36 remaining
Device Index: 122
Subunit: 32768
Interface: pd-6/0/0.32768
Group Ranges:
Copyright © 2016, Juniper Networks, Inc.
427
Multicast Protocols Feature Guide for EX4600 Switches
224.0.0.0/4, 36s remaining
Active groups using RP:
225.1.1.1
total 1 groups active
Register State for RP:
Group Source FirstHop RP Address State Timeout
225.1.1.1 192.168.195.78 10.255.14.132 10.255.245.91 Receive 0 show pim rps extensive (Bidirectional PIM) user@host> show pim rps extensive
Instance: PIM.master
Address family INET
RP: 10.10.1.3
Learned via: static configuration
Mode: Bidirectional
Time Active: 01:58:07
Holdtime: 150
Group Ranges:
224.1.3.0/24
225.1.3.0/24
RP: 10.10.13.2
Learned via: static configuration
Mode: Bidirectional
Time Active: 01:58:07
Holdtime: 150
Group Ranges:
224.1.1.0/24
225.1.1.0/24 show pim rps extensive (PIM Anycast RP in Use) user@host> show pim rps extensive
Instance: PIM.master
Family: INET
RP: 10.10.10.2
Learned via: static configuration
Time Active: 00:54:52
Holdtime: 0
Device Index: 130
Subunit: 32769
Interface: pimd.32769
Group Ranges:
224.0.0.0/4
Active groups using RP:
224.10.10.10
total 1 groups active
Anycast-PIM rpset:
10.100.111.34
10.100.111.17
10.100.111.55
Anycast-PIM local address used: 10.100.111.1
Anycast-PIM Register State:
428 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Group Source Origin
224.1.1.1 10.10.95.2 DIRECT
224.1.1.2 10.10.95.2 DIRECT
224.10.10.10 10.10.70.1 MSDP
224.10.10.11 10.10.70.1 MSDP
224.20.20.1 10.10.71.1 DR
Address family INET6
Anycast-PIM rpset:
ab::1
ab::2
Anycast-PIM local address used: cd::1
Anycast-PIM Register State:
Group Source Origin
::224.1.1.1 ::10.10.95.2 DIRECT
::224.1.1.2 ::10.10.95.2 DIRECT
::224.20.20.1 ::10.10.71.1 DR
Copyright © 2016, Juniper Networks, Inc.
429
Multicast Protocols Feature Guide for EX4600 Switches show pim source
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 430
Syntax show pim source
<brief | detail>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<source-prefix>
Syntax (EX Series
Switch and the QFX
Series) show pim source
<brief | detail>
<inet | inet6>
<instance instance-name>
<source-prefix>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display information about the Protocol Independent Multicast (PIM) source reverse path forwarding (RPF) state.
Options none —Display standard information about the PIM RPF state for all supported family addresses for all routing instances.
brief | detail —(Optional) Display the specified level of output.
inet | inet6 —(Optional) Display information for IPv4 or IPv6 family addresses, respectively.
instance instance-name —(Optional) Display information about the RPF state for a specific
PIM-enabled routing instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
source-prefix —(Optional) Display the state for source RPF states in the given range.
Required Privilege
Level view
List of Sample Output
show pim source on page 431 show pim source brief on page 431 show pim source detail on page 431
Output Fields
describes the output fields for the show pim source command.
Output fields are listed in the approximate order in which they appear.
430 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 30: show pim source Output Fields
Field Name Field Description
Instance Name of the routing instance.
Address of the source or reverse path.
Source
Prefix/length Prefix and prefix length for the route used to reach the RPF address.
Upstream interface RPF interface toward the source address.
Upstream Neighbor Address of the RPF neighbor used to reach the source address.
Sample Output show pim source user@host> show pim source
Instance: PIM.master Family: INET
Source 10.255.14.144
Prefix 10.255.14.144/32
Upstream interface Local
Upstream neighbor Local
Source 10.255.70.15
Prefix 10.255.70.15/32
Upstream interface so-1/0/0.0
Upstream neighbor 10.111.10.2
Instance: PIM.master Family: INET6 show pim source brief
The output for the show pim source brief command is identical to that for the show pim source command. For sample output, see
.
show pim source detail user@host> show pim source detail
Instance: PIM.master Family: INET
Source 10.255.14.144
Prefix 10.255.14.144/32
Upstream interface Local
Upstream neighbor Local
Active groups:228.0.0.0
239.1.1.1
239.1.1.1
Source 10.255.70.15
Prefix 10.255.70.15/32
Upstream interface so-1/0/0.0
Upstream neighbor 10.111.10.2
Active groups:239.1.1.1
Copyright © 2016, Juniper Networks, Inc.
431
Multicast Protocols Feature Guide for EX4600 Switches
Instance: PIM.master Family: INET6
432 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands show pim statistics
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 433
Syntax show pim statistics
<inet |inet6)>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show pim statistics
<inet |inet6)>
<instance instance-name>
<interface interface-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Description Display Protocol Independent Multicast (PIM) statistics.
Options none —Display PIM statistics.
inet | inet6 —(Optional) Display IPv4 or IPv6 PIM statistics, respectively.
instance instance-name —(Optional) Display statistics for a specific routing instance enabled by Protocol Independent Multicast (PIM).
interface interface-name —(Optional) Display statistics about the specified interface.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
Related
Documentation
•
clear pim statistics on page 348
List of Sample Output
show pim statistics on page 439
show pim statistics inet interface <interface-name> on page 440
Output Fields
describes the output fields for the show pim statistics command.
Output fields are listed in the approximate order in which they appear.
Copyright © 2016, Juniper Networks, Inc.
433
Multicast Protocols Feature Guide for EX4600 Switches
Table 31: show pim statistics Output Fields
Field Name Field Description
Instance
Family
PIM statistics
PIM message type
Received
Name of the routing instance.
This field only appears if you specify an interface, for example:
•
•
• inet interface interface-name inet6 interface interface-name interface interface-name
Output is for IPv4 or IPv6 PIM statistics.
INET indicates IPv4 statistics, and INET6 indicates IPv6 statistics.
This field only appears if you specify an interface, for example:
•
•
• inet interface interface-name inet6 interface interface-name interface interface-name
PIM statistics for all interfaces or for the specified interface.
Message type for which statistics are displayed.
Number of received statistics.
Number of messages sent of a certain type.
Sent
Rx errors Number of received packets that contained errors.
PIM version 2 hello packets.
V2 Hello
V2 Register
V2 Register Stop
V2 Join Prune
V2 Bootstrap
PIM version 2 register packets.
PIM version 2 register stop packets.
PIM version 2 join and prune packets.
PIM version 2 bootstrap packets.
PIM version 2 assert packets.
V2 Assert
V2 Graft
V2 Graft Ack
V2 Candidate RP
PIM version 2 graft packets.
PIM version 2 graft acknowledgment packets.
PIM version 2 candidate RP packets.
434 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 31: show pim statistics Output Fields (continued)
Field Name Field Description
V2 State Refresh PIM version 2 control messages related to PIM dense mode
(PIM-DM) state refresh.
State refresh is an extension to PIM-DM. It not supported in Junos
OS.
V2 DF Election PIM version 2 send and receive messages associated with bidirectional PIM designated forwarder election.
V1 Query PIM version 1 query packets.
PIM version 1 register packets.
V1 Register
V1 Register Stop PIM version 1 register stop packets.
PIM version 1 join and prune packets.
V1 Join Prune
V1 RP Reachability
V1 Assert
PIM version 1 RP reachability packets.
PIM version 1 assert packets.
PIM version 1 graft packets.
V1 Graft
V1 Graft Ack PIM version 1 graft acknowledgment packets.
Auto-RP announce packets.
AutoRP Announce
AutoRP Mapping
AutoRP Unknown type
Auto-RP mapping packets.
Auto-RP packets with an unknown type.
Auto-RP announce packets.
Anycast Register
Anycast Register Stop
Global Statistics
Hello dropped on neighbor policy
Number of hello packets dropped because of a configured neighbor policy.
Number of PIM control packets received with an unknown type.
Unknown type
V1 Unknown type
Auto-RP announce packets.
Summary of PIM statistics for all interfaces.
Unknown Version
Number of PIM version 1 control packets received with an unknown type.
Number of PIM control packets received with an unknown version.
The version is not version 1 or version 2.
Copyright © 2016, Juniper Networks, Inc.
435
Multicast Protocols Feature Guide for EX4600 Switches
Table 31: show pim statistics Output Fields (continued)
Field Name Field Description
Neighbor unknown
Bad Length
Bad Checksum
Bad Receive If
Number of PIM control packets received (excluding PIM hello) without first receiving the hello packet.
Number of PIM control packets received for which the packet size does not match the PIM length field in the packet.
Number of PIM control packets received for which the calculated checksum does not match the checksum field in the packet.
Number of PIM control packets received on an interface that does not have PIM configured.
Rx Bad Data
Rx Intf disabled
Rx V1 Require V2
Rx V2 Require V1
Rx Register not RP
Rx Register no route
Rx Register no decap if
Null Register Timeout
RP Filtered Source
Number of PIM control packets received that contain data for TCP
Bad register packets.
Number of PIM control packets received on an interface that has
PIM disabled.
Number of PIM version 1 control packets received on an interface configured for PIM version 2.
Number of PIM version 2 control packets received on an interface configured for PIM version 1.
Number of PIM register packets received when the router is not the
RP for the group.
Number of PIM register packets received when the RP does not have a unicast route back to the source.
Number of PIM register packets received when the RP does not have a de-encapsulation interface.
Number of NULL register timeout packets.
Number of PIM packets received when the router has a source address filter configured for the RP.
Rx Unknown Reg Stop
Rx Join/Prune no state
Number of register stop messages received with an unknown type.
Number of join and prune messages received for which the router has no state.
Rx Join/Prune on upstream if
Number of join and prune messages received on the interface used to reach the upstream router, toward the RP.
Rx Join/Prune for invalid group
Number of join or prune messages received for invalid multicast group addresses.
436 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 31: show pim statistics Output Fields (continued)
Field Name Field Description
Rx Join/Prune messages dropped
Rx sparse join for dense group
Rx Graft on upstream if
Number of join and prune messages received and dropped.
Number of PIM sparse mode join messages received for a group that is configured for dense mode.
Rx Graft/Graft Ack no state Number of graft and graft acknowledgment messages received for which the router or switch has no state.
Number of graft messages received on the interface used to reach the upstream router, toward the RP.
Rx CRP not BSR
Rx BSR when BSR
Rx BSR not RPF if
Rx unknown hello opt
Rx data no state
Rx RP no state
Rx aggregate
Rx malformed packet
No RP
No register encap if
No route upstream
Nexthop Unusable
RP mismatch
Number of BSR messages received in which the PIM message type is Candidate-RP-Advertisement, not Bootstrap.
Number of BSR messages received in which the PIM message type is Bootstrap.
Number of BSR messages received on an interface that is not the
RPF interface.
Number of PIM hello packets received with options that Junos OS does not support.
Number of PIM control packets received for which the router has no state for the data type.
Number of PIM control packets received for which the router has no state for the RP.
Number of PIM aggregate MDT packets received.
Number of PIM control packets received with a malformed IP unicast or multicast address family.
Number of PIM control packets received with no RP address.
Number of PIM register packets received when the first-hop router does not have an encapsulation interface.
Number of PIM control packets received when the router does not have a unicast route to the the interface used to reach the upstream router, toward the RP.
Number of PIM control packets with an unusable nexthop. A path can be unusable if the route is hidden or the link is down.
Number of PIM control packets received for which the router has an RP mismatch.
Copyright © 2016, Juniper Networks, Inc.
437
Multicast Protocols Feature Guide for EX4600 Switches
Table 31: show pim statistics Output Fields (continued)
Field Name Field Description
RP mode mismatch
RPF neighbor unknown
Rx Joins/Prunes filtered
Tx Joins/Prunes filtered
RP mode (sparse or bidirectional) mismatches encountered when processing join and prune messages.
Number of PIM control packets received for which the router has an unknown RPF neighbor for the source.
The number of join and prune messages filtered because of configured route filters and source address filters.
The number of join and prune messages filtered because of configured route filters and source address filters.
Embedded-RP invalid addr Number of packets received with an invalid embedded RP address in PIM join messages and other types of messages sent between routing domains.
Embedded-RP limit exceed Number of times the limit configured with the maximum-rps statement is exceeded. The maximum-rps statement limits the number of embedded RPs created in a specific routing instance.
The range is from 1 through 500. The default is 100.
Embedded-RP added Number of packets in which the embedded RP for IPv6 is added.
The following receive events trigger extraction of an IPv6 embedded
RP address on the router:
•
•
•
•
Multicast Listener Discovery (MLD) report for an embedded RP multicast group address
PIM join message with an embedded RP multicast group address
Static embedded RP multicast group address associated with an interface
Packets sent to an embedded RP multicast group address received on the DR
An embedded RP node discovered through these receive events is added if it does not already exist on the routing platform.
Embedded-RP removed
Rx Register msgs filtering drop
Tx Register msgs filtering drop
Rx Bidir Join/Prune on non-Bidir if
Number of packets in which the embedded RP for IPv6 is removed.
The embedded RP is removed whenever all PIM join states using this RP are removed or the configuration changes to remove the embedded RP feature.
Number of received register messages dropped because of a filter configured for PIM register messages.
Number of register messages dropped because of a filter configured for PIM register messages.
Error counter for join and prune messages received on non-bidirectional PIM interfaces.
438 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
Table 31: show pim statistics Output Fields (continued)
Field Name Field Description
Rx Bidir Join/Prune on non-DF if
Error counter for join and prune messages received on non-designated forwarder interfaces.
Sample Output show pim statistics user@host> show pim statistics
PIM Message type Received Sent Rx errors
V2 Hello 15 32 0
V2 Register 0 362 0
V2 Register Stop 483 0 0
V2 Join Prune 18 518 0
V2 Bootstrap 0 0 0
V2 Assert 0 0 0
V2 Graft 0 0 0
V2 Graft Ack 0 0 0
V2 Candidate RP 0 0 0
V2 State Refresh 0 0 0
V2 DF Election 0 0 0
V1 Query 0 0 0
V1 Register 0 0 0
V1 Register Stop 0 0 0
V1 Join Prune 0 0 0
V1 RP Reachability 0 0 0
V1 Assert 0 0 0
V1 Graft 0 0 0
V1 Graft Ack 0 0 0
AutoRP Announce 0 0 0
AutoRP Mapping 0 0 0
AutoRP Unknown type 0
Anycast Register 0 0 0
Anycast Register Stop 0 0 0
Global Statistics
Hello dropped on neighbor policy 0
Unknown type 0
V1 Unknown type 0
Unknown Version 0
Neighbor unknown 0
Bad Length 0
Bad Checksum 0
Bad Receive If 0
Rx Bad Data 0
Rx Intf disabled 0
Rx V1 Require V2 0
Rx V2 Require V1 0
Rx Register not RP 0
Rx Register no route 0
Rx Register no decap if 0
Null Register Timeout 0
RP Filtered Source 0
Rx Unknown Reg Stop 0
Rx Join/Prune no state 0
Copyright © 2016, Juniper Networks, Inc.
439
Multicast Protocols Feature Guide for EX4600 Switches
Rx Join/Prune on upstream if 0
Rx Join/Prune for invalid group 5
Rx Join/Prune messages dropped 0
Rx sparse join for dense group 0
Rx Graft/Graft Ack no state 0
Rx Graft on upstream if 0
Rx CRP not BSR 0
Rx BSR when BSR 0
Rx BSR not RPF if 0
Rx unknown hello opt 0
Rx data no state 0
Rx RP no state 0
Rx aggregate 0
Rx malformed packet 0
Rx illegal TTL 0
Rx illegal destination address 0
No RP 0
No register encap if 0
No route upstream 0
Nexthop Unusable 0
RP mismatch 0
RP mode mismatch 0
RPF neighbor unknown 0
Rx Joins/Prunes filtered 0
Tx Joins/Prunes filtered 0
Embedded-RP invalid addr 0
Embedded-RP limit exceed 0
Embedded-RP added 0
Embedded-RP removed 0
Rx Register msgs filtering drop 0
Tx Register msgs filtering drop 0
Rx Bidir Join/Prune on non-Bidir if 0
Rx Bidir Join/Prune on non-DF if 0
Sample Output show pim statistics inet interface <interface-name> user@host> show pim statistics inet interface ge-0/3/0.0
Instance: PIM.master Family: INET
PIM Interface statistics for ge-0/3/0.0
PIM Message type Received Sent Rx errors
V2 Hello 0 4 0
V2 Register 0 0 0
V2 Register Stop 0 0 0
V2 Join Prune 0 0 0
V2 Bootstrap 0 0 0
V2 Assert 0 0 0
V2 Graft 0 0 0
V2 Graft Ack 0 0 0
V2 Candidate RP 0 0 0
V1 Query 0 0 0
V1 Register 0 0 0
V1 Register Stop 0 0 0
V1 Join Prune 0 0 0
V1 RP Reachability 0 0 0
V1 Assert 0 0 0
V1 Graft 0 0 0
V1 Graft Ack 0 0 0
440 Copyright © 2016, Juniper Networks, Inc.
Chapter 18: Multicast Operational Commands
AutoRP Announce 0 0 0
AutoRP Mapping 0 0 0
AutoRP Unknown type 0
Anycast Register 0 0 0
Anycast Register Stop 0 0 0
Sample Output show pim statistics inet6 interface <interface-name> user@host> show pim statistics inet6 interface ge-0/3/0.0
Instance: PIM.master Family: INET6
PIM Interface statistics for ge-0/3/0.0
PIM Message type Received Sent Rx errors
V2 Hello 0 4 0
V2 Register 0 0 0
V2 Register Stop 0 0 0
V2 Join Prune 0 0 0
V2 Bootstrap 0 0 0
V2 Assert 0 0 0
V2 Graft 0 0 0
V2 Graft Ack 0 0 0
V2 Candidate RP 0 0 0
Anycast Register 0 0 0
Anycast Register Stop 0 0 0
Sample Output show pim statistics interface <interface-name> user@host> show pim statistics interface ge-0/3/0.0
Instance: PIM.master Family: INET
PIM Interface statistics for ge-0/3/0.0
PIM Message type Received Sent Rx errors
V2 Hello 0 3 0
V2 Register 0 0 0
V2 Register Stop 0 0 0
V2 Join Prune 0 0 0
V2 Bootstrap 0 0 0
V2 Assert 0 0 0
V2 Graft 0 0 0
V2 Graft Ack 0 0 0
V2 Candidate RP 0 0 0
V1 Query 0 0 0
V1 Register 0 0 0
V1 Register Stop 0 0 0
V1 Join Prune 0 0 0
V1 RP Reachability 0 0 0
V1 Assert 0 0 0
V1 Graft 0 0 0
V1 Graft Ack 0 0 0
AutoRP Announce 0 0 0
AutoRP Mapping 0 0 0
AutoRP Unknown type 0
Anycast Register 0 0 0
Anycast Register Stop 0 0 0
Copyright © 2016, Juniper Networks, Inc.
441
Multicast Protocols Feature Guide for EX4600 Switches
Instance: PIM.master Family: INET6
PIM Interface statistics for ge-0/3/0.0
PIM Message type Received Sent Rx errors
V2 Hello 0 3 0
V2 Register 0 0 0
V2 Register Stop 0 0 0
V2 Join Prune 0 0 0
V2 Bootstrap 0 0 0
V2 Assert 0 0 0
V2 Graft 0 0 0
V2 Graft Ack 0 0 0
V2 Candidate RP 0 0 0
Anycast Register 0 0 0
Anycast Register Stop 0 0 0
442 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 19
IGMP Operational Commands
•
•
•
•
show configuration protocols igmp
•
•
•
Copyright © 2016, Juniper Networks, Inc.
443
Multicast Protocols Feature Guide for EX4600 Switches clear igmp membership
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 444
Syntax clear igmp membership
<group address-range>
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) clear igmp membership
<group address-range>
<interface interface-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Clear Internet Group Management Protocol (IGMP) group members.
Options none —Clear all IGMP members on all interfaces and for all address ranges.
group address-range —(Optional) Clear all IGMP members that are in a particular address range. An example of a range is 224.2/16. If you omit the destination prefix length, the default is /32.
interface interface-name —(Optional) Clear all IGMP group members on an interface.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level clear
Related
Documentation
•
•
show igmp interface on page 455
List of Sample Output
clear igmp membership on page 444
clear igmp membership interface on page 445
clear igmp membership group on page 446
Output Fields See
for an explanation of output fields.
Sample Output clear igmp membership
The following sample output displays IGMP group information before and after the clear igmp membership command is entered:
444 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands user@host> show igmp group
Interface Group Last Reported Timeout so-0/0/0 224.2.127.253 10.1.128.1 186 so-0/0/0 224.2.127.254 10.1.128.1 186 so-0/0/0 239.255.255.255 10.1.128.1 187 so-0/0/0 224.1.127.255 10.1.128.1 188 local 224.0.0.6 (null) 0 local 224.0.0.5 (null) 0 local 224.2.127.254 (null) 0 local 239.255.255.255 (null) 0 local 224.0.0.2 (null) 0 local 224.0.0.13 (null) 0 user@host> clear igmp membership
Clearing Group Membership Info for so-0/0/0
Clearing Group Membership Info for so-1/0/0
Clearing Group Membership Info for so-2/0/0 user@host> show igmp group
Interface Group Last Reported Timeout local 224.0.0.6 (null) 0 local 224.0.0.5 (null) 0 local 224.2.127.254 (null) 0 local 239.255.255.255 (null) 0 local 224.0.0.2 (null) 0 local 224.0.0.13 (null) 0 clear igmp membership interface
The following sample output displays IGMP group information before and after the clear igmp membership interface command is issued: user@host> show igmp group
Interface Group Last Reported Timeout so-0/0/0 224.2.127.253 10.1.128.1 210 so-0/0/0 239.255.255.255 10.1.128.1 210 so-0/0/0 224.1.127.255 10.1.128.1 215 so-0/0/0 224.2.127.254 10.1.128.1 216 local 224.0.0.6 (null) 0 local 224.0.0.5 (null) 0 local 224.2.127.254 (null) 0 local 239.255.255.255 (null) 0 local 224.0.0.2 (null) 0 local 224.0.0.13 (null) 0 user@host> clear igmp membership interface so-0/0/0
Clearing Group Membership Info for so-0/0/0 user@host> show igmp group
Interface Group Last Reported Timeout local 224.0.0.6 (null) 0 local 224.0.0.5 (null) 0 local 224.2.127.254 (null) 0 local 239.255.255.255 (null) 0 local 224.0.0.2 (null) 0 local 224.0.0.13 (null) 0
Copyright © 2016, Juniper Networks, Inc.
445
Multicast Protocols Feature Guide for EX4600 Switches clear igmp membership group
The following sample output displays IGMP group information before and after the clear igmp membership group command is entered: user@host> show igmp group
Interface Group Last Reported Timeout so-0/0/0 224.2.127.253 10.1.128.1 210 so-0/0/0 239.255.255.255 10.1.128.1 210 so-0/0/0 224.1.127.255 10.1.128.1 215 so-0/0/0 224.2.127.254 10.1.128.1 216 local 224.0.0.6 (null) 0 local 224.0.0.5 (null) 0 local 224.2.127.254 (null) 0 local 239.255.255.255 (null) 0 local 224.0.0.2 (null) 0 local 224.0.0.13 (null) 0 user@host> clear igmp membership group 239.225/16
Clearing Group Membership Range 239.225.0.0/16 on so-0/0/0
Clearing Group Membership Range 239.225.0.0/16 on so-1/0/0
Clearing Group Membership Range 239.225.0.0/16 on so-2/0/0 user@host> show igmp group
Interface Group Last Reported Timeout so-0/0/0 224.1.127.255 10.1.128.1 231 so-0/0/0 224.2.127.254 10.1.128.1 233 so-0/0/0 224.2.127.253 10.1.128.1 236 local 224.0.0.6 (null) 0 local 224.0.0.5 (null) 0 local 224.2.127.254 (null) 0 local 239.255.255.255 (null) 0 local 224.0.0.2 (null) 0 local 224.0.0.13 (null) 0
446 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands clear igmp statistics
List of Syntax
Syntax (EX Series Switches) on page 447
Syntax clear igmp statistics
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switches) clear igmp statistics
<interface interface-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Clear Internet Group Management Protocol (IGMP) statistics.
Options none —Clear IGMP statistics on all interfaces.
interface interface-name —(Optional) Clear IGMP statistics for the specified interface only.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level clear
List of Sample Output
clear igmp statistics on page 447
Output Fields See
for an explanation of output fields.
Sample Output clear igmp statistics
The following sample output displays IGMP statistics information before and after the clear igmp statistics command is entered: user@host> show igmp statistics
IGMP packet statistics for all interfaces
IGMP Message type Received Sent Rx errors
Membership Query 8883 459 0
V1 Membership Report 0 0 0
DVMRP 19784 35476 0
PIM V1 18310 0 0
Cisco Trace 0 0 0
V2 Membership Report 0 0 0
Group Leave 0 0 0
Mtrace Response 0 0 0
Mtrace Request 0 0 0
Domain Wide Report 0 0 0
V3 Membership Report 0 0 0
Other Unknown types 0
Copyright © 2016, Juniper Networks, Inc.
447
Multicast Protocols Feature Guide for EX4600 Switches
IGMP v3 unsupported type 0
IGMP v3 source required for SSM 0
IGMP v3 mode not applicable for SSM 0
IGMP Global Statistics
Bad Length 0
Bad Checksum 0
Bad Receive If 0
Rx non-local 1227 user@host> clear igmp statistics user@host> show igmp statistics
IGMP packet statistics for all interfaces
IGMP Message type Received Sent Rx errors
Membership Query 0 0 0
V1 Membership Report 0 0 0
DVMRP 0 0 0
PIM V1 0 0 0
Cisco Trace 0 0 0
V2 Membership Report 0 0 0
Group Leave 0 0 0
Mtrace Response 0 0 0
Mtrace Request 0 0 0
Domain Wide Report 0 0 0
V3 Membership Report 0 0 0
Other Unknown types 0
IGMP v3 unsupported type 0
IGMP v3 source required for SSM 0
IGMP v3 mode not applicable for SSM 0
IGMP Global Statistics
Bad Length 0
Bad Checksum 0
Bad Receive If 0
Rx non-local 0
448 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands show igmp group
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 449
Syntax show igmp group
<brief | detail>
<group-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show igmp group
<brief | detail>
<group-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display Internet Group Management Protocol (IGMP) group membership information.
Options none —Display standard information about membership for all IGMP groups.
brief | detail —(Optional) Display the specified level of output.
group-name —(Optional) Display group membership for the specified IP address only.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
show igmp group (Include Mode) on page 450
Output Fields
describes the output fields for the show igmp group command.
Output fields are listed in the approximate order in which they appear.
Table 32: show igmp group Output Fields
Field Name Field Description Level of Output
Interface All levels
Group
Group Mode
Source
Name of the interface that received the IGMP membership report. A name of local indicates that the local routing device joined the group itself.
Group address.
Mode the SSM group is operating in: Include or Exclude .
Source address.
All levels
All levels
All levels
Copyright © 2016, Juniper Networks, Inc.
449
Multicast Protocols Feature Guide for EX4600 Switches
Table 32: show igmp group Output Fields (continued)
Field Name Field Description
Source timeout
Last reported by
Timeout
Group timeout
Type
Level of Output
Time remaining until the group traffic is no longer forwarded. The timer is refreshed when a listener in include mode sends a report. A group in exclude mode or configured as a static group displays a zero timer.
detail
Address of the host that last reported membership in this group.
Time remaining until the group membership is removed.
All levels brief none
Time remaining until a group in exclude mode moves to include mode. The timer is refreshed when a listener in exclude mode sends a report. A group in include mode or configured as a static group displays a zero timer.
detail
All levels Type of group membership:
•
•
Dynamic —Host reported the membership.
Static —Membership is configured.
Sample Output show igmp group (Include Mode) user@host> show igmp group
Interface: t1-0/1/0.0
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.2
Last reported by: 10.9.5.2
Timeout: 24 Type: Dynamic
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.3
Last reported by: 10.9.5.2
Timeout: 24 Type: Dynamic
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.4
Last reported by: 10.9.5.2
Timeout: 24 Type: Dynamic
Group: 232.1.1.2
Group mode: Include
Source: 10.0.0.4
Last reported by: 10.9.5.2
Timeout: 24 Type: Dynamic
Interface: t1-0/1/1.0
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Interface: local
Group: 224.0.0.2
Source: 0.0.0.0
Last reported by: Local
Timeout: 0 Type: Dynamic
Group: 224.0.0.22
Source: 0.0.0.0
450 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands show igmp group (Exclude Mode) user@host> show igmp group
Interface: t1-0/1/0.0
Interface: t1-0/1/1.0
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Interface: local
Group: 224.0.0.2
Source: 0.0.0.0
Last reported by: Local
Timeout: 0 Type: Dynamic
Group: 224.0.0.22
Source: 0.0.0.0
Last reported by: Local
Timeout: 0 Type: Dynamic show igmp group brief
Last reported by: Local
Timeout: 0 Type: Dynamic
The output for the show igmp group brief command is identical to that for the show igmp group command.
show igmp group detail user@host> show igmp group detail
Interface: t1-0/1/0.0
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.2
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout: 0 Type: Dynamic
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.3
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout: 0 Type: Dynamic
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.4
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout: 0 Type: Dynamic
Group: 232.1.1.2
Group mode: Include
Source: 10.0.0.4
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout: 0 Type: Dynamic
Interface: t1-0/1/1.0
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Interface: local
Group: 224.0.0.2
Group mode: Exclude
Source: 0.0.0.0
Source timeout: 0
Copyright © 2016, Juniper Networks, Inc.
451
Multicast Protocols Feature Guide for EX4600 Switches
Last reported by: Local
Group timeout: 0 Type: Dynamic
Group: 224.0.0.22
Group mode: Exclude
Source: 0.0.0.0
Source timeout: 0
Last reported by: Local
Group timeout: 0 Type: Dynamic
452 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands show configuration protocols igmp
Syntax show configuration protocols igmp
Release Information Command introduced in Junos OS Release 11.3 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display Internet Group Management Protocol (IGMP) information.
Required Privilege
Level view
Related
Documentation
•
IGMP Snooping Overview on page 125
•
Configuring IGMP Snooping on page 128
List of Sample Output
show configuration protocols igmp on page 453
Output Fields
describes the output fields for the show configuration protocols igmp command that relate to IGMP querying.
Table 33: show igmp group Output Fields
Field Name Field Description Level of Output accounting igmp-querier interface
Enables notification for join and leave events.
Configured source address for the IGMP querier.
Name of the interface that receives IGMP membership reports.
All levels
All levels
All levels query-interval query-responseinterval src-address version
Interval at which the IGMP querier sends general host-query messages to solicit membership information.
All levels
How long the IGMP querier waits to receive a response from a query message before sending another query.
All levels
Source address of IGMP queries.
IGMP version.
All levels
Sample Output show configuration protocols igmp user@switch> show configuration protocols igmp query-interval 150; query-response-interval 50; accounting; interface vlan.43 {
version 2;
} igmp-querier {
Copyright © 2016, Juniper Networks, Inc.
453
Multicast Protocols Feature Guide for EX4600 Switches
src-address 10.0.0.2;
}
454 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands show igmp interface
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 455
Syntax show igmp interface
<brief | detail>
<interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show igmp interface
<brief | detail>
<interface-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display information about Internet Group Management Protocol (IGMP)-enabled interfaces.
Options none —Display standard information about all IGMP-enabled interfaces.
brief | detail —(Optional) Display the specified level of output.
interface-name —(Optional) Display information about the specified IGMP-enabled interface only.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
Related
Documentation
•
clear igmp membership on page 444
List of Sample Output
show igmp interface on page 457 show igmp interface brief on page 457
show igmp interface detail on page 458
Output Fields
describes the output fields for the show igmp interface command.
Output fields are listed in the approximate order in which they appear.
Table 34: show igmp interface Output Fields
Field Name Field Description Level of Output
Name of the interface.
All levels Interface
Querier Address of the routing device that has been elected to send membership queries.
All levels
Copyright © 2016, Juniper Networks, Inc.
455
Multicast Protocols Feature Guide for EX4600 Switches
Table 34: show igmp interface Output Fields (continued)
Field Name Field Description Level of Output
State
SSM Map Policy
State of the interface: Up or Down .
How long until the IGMP querier is declared to be unreachable, in seconds.
All levels
Name of the source-specific multicast (SSM) map policy that has been applied to the
IGMP interface.
All levels
All levels Timeout
Version
Groups
IGMP version being used on the interface:
Number of groups on the interface.
1 , 2 , or 3 .
All levels
All levels
Immediate Leave State of the immediate leave option:
• On —Indicates that the router removes a host from the multicast group as soon as the router receives a leave group message from a host associated with the interface.
• Off —Indicates that after receiving a leave group message, instead of removing a host from the multicast group immediately, the router sends a group query to determine if another receiver responds.
All levels
Promiscuous Mode State of the promiscuous mode option:
• On —Indicates that the router can accept IGMP reports from subnetworks that are not associated with its interfaces.
• Off —Indicates that the router can accept IGMP reports only from subnetworks that are associated with its interfaces.
All levels
Passive
OIF map
State of the passive mode option:
•
•
On —Indicates that the router can run IGMP on the interface but not send or receive control traffic such as IGMP reports, queries, and leaves.
Off —Indicates that the router can run IGMP on the interface and send or receive control traffic such as IGMP reports, queries, and leaves.
The passive statement enables you to selectively activate up to two out of a possible three available query or control traffic options. When enabled, the following options appear after the on state declaration:
•
•
• send-general-query —The interface sends general queries.
send-group-query —The interface sends group-specific and group-source-specific queries.
allow-receive —The interface receives control traffic.
All levels
Name of the OIF map (if configured) associated with the interface.
All levels
SSM map Name of the source-specific multicast (SSM) map (if configured) used on the interface.
All levels
456 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands
Table 34: show igmp interface Output Fields (continued)
Field Name Field Description Level of Output
Configured
Parameters
Information configured by the user:
•
•
IGMP Query Interval —Interval (in seconds) at which this router sends membership queries when it is the querier.
IGMP Query Response Interval —Time (in seconds) that the router waits for a report in response to a general query.
• IGMP Last Member Query Interval —Time (in seconds) that the router waits for a report in response to a group-specific query.
• IGMP Robustness Count —Number of times the router retries a query.
All levels
Derived Parameters Derived information:
•
•
IGMP Membership Timeout —Timeout period (in seconds) for group membership. If no report is received for these groups before the timeout expires, the group membership is removed.
IGMP Other Querier Present Timeout —Time (in seconds) that the router waits for the
IGMP querier to send a query.
All levels
Sample Output show igmp interface user@host> show igmp interface
Interface: at-0/3/1.0
Querier: 10.111.30.1
State: Up Timeout: None Version: 2 Groups: 4
SSM Map Policy: ssm-policy-A
Interface: so-1/0/0.0
Querier: 10.111.10.1
State: Up Timeout: None Version: 2 Groups: 2
SSM Map Policy: ssm-policy-B
Interface: so-1/0/1.0
Querier: 10.111.20.1
State: Up Timeout: None Version: 2 Groups: 4
SSM Map Policy: ssm-policy-C
Immediate Leave: On
Promiscuous Mode: Off
Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Derived Parameters:
IGMP Membership Timeout: 260.0
IGMP Other Querier Present Timeout: 255.0
show igmp interface brief
The output for the show igmp interface brief command is identical to that for the show igmp interface command. For sample output, see
show igmp interface on page 457
.
Copyright © 2016, Juniper Networks, Inc.
457
Multicast Protocols Feature Guide for EX4600 Switches show igmp interface detail
The output for the show igmp interface detail command is identical to that for the show igmp interface command. For sample output, see
show igmp interface on page 457
.
458 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands show igmp statistics
List of Syntax
Syntax (EX Series Switch and the QFX Series) on page 459
Syntax show igmp statistics
<brief | detail>
<interface interface-name>
<logical-system (all | logical-system-name)>
Syntax (EX Series
Switch and the QFX
Series) show igmp statistics
<brief | detail>
<interface interface-name>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description Display Internet Group Management Protocol (IGMP) statistics.
Options none —Display IGMP statistics for all interfaces.
brief | detail —(Optional) Display the specified level of output.
interface interface-name —(Optional) Display IGMP statistics about the specified interface only.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
Related
Documentation
•
clear igmp statistics on page 447
List of Sample Output
show igmp statistics on page 460
show igmp statistics interface on page 461
Output Fields
describes the output fields for the show igmp statistics command.
Output fields are listed in the approximate order in which they appear.
Table 35: show igmp statistics Output Fields
Field Name Field Description
IGMP packet statistics Heading for IGMP packet statistics for all interfaces or for the specified interface name.
Copyright © 2016, Juniper Networks, Inc.
459
Multicast Protocols Feature Guide for EX4600 Switches
Table 35: show igmp statistics Output Fields (continued)
Field Name Field Description
IGMP Message type Summary of IGMP statistics:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Membership Query —Number of membership queries sent and received.
V1 Membership Report —Number of version 1 membership reports sent and received.
DVMRP —Number of DVMRP messages sent or received.
PIM V1 —Number of PIM version 1 messages sent or received.
Cisco Trace —Number of Cisco trace messages sent or received.
V2 Membership Report —Number of version 2 membership reports sent or received.
Group Leave —Number of group leave messages sent or received.
Mtrace Response —Number of Mtrace response messages sent or received.
Mtrace Request —Number of Mtrace request messages sent or received.
Domain Wide Report —Number of domain-wide reports sent or received.
V3 Membership Report —Number of version 3 membership reports sent or received.
Other Unknown types —Number of unknown message types received.
IGMP v3 unsupported type —Number of messages received with unknown and unsupported IGMP version 3 message types.
IGMP v3 source required for SSM —Number of IGMP version 3 messages received that contained no source.
IGMP v3 mode not applicable for SSM —Number of IGMP version 3 messages received that did not contain a mode applicable for source-specific multicast (SSM).
Number of messages received.
Received
Sent
Rx errors
Number of messages sent.
Number of received packets that contained errors.
IGMP Global Statistics Summary of IGMP statistics for all interfaces.
•
•
•
•
•
•
•
Bad Length —Number of messages received with length errors so severe that further classification could not occur.
Bad Checksum —Number of messages received with a bad IP checksum. No further classification was performed.
Bad Receive If —Number of messages received on an interface not enabled for IGMP.
Rx non-local —Number of messages received from senders that are not local.
Timed out —Number of groups that timed out as a result of not receiving an explicit leave message.
Rejected Report —Number of reports dropped because of the IGMP group policy.
Total Interfaces —Number of interfaces configured to support IGMP.
Sample Output show igmp statistics user@host> show igmp statistics
IGMP packet statistics for all interfaces
IGMP Message type Received Sent Rx errors
Membership Query 8883 459 0
V1 Membership Report 0 0 0
460 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands
DVMRP 0 0 0
PIM V1 0 0 0
Cisco Trace 0 0 0
V2 Membership Report 0 0 0
Group Leave 0 0 0
Mtrace Response 0 0 0
Mtrace Request 0 0 0
Domain Wide Report 0 0 0
V3 Membership Report 0 0 0
Other Unknown types 0
IGMP v3 unsupported type 0
IGMP v3 source required for SSM 0
IGMP v3 mode not applicable for SSM 0
IGMP Global Statistics
Bad Length 0
Bad Checksum 0
Bad Receive If 0
Rx non-local 1227
Timed out 0
Rejected Report 0
Total Interfaces 2 show igmp statistics interface user@host> show igmp statistics interface fe-1/0/1.0
IGMP interface packet statistics for fe-1/0/1.0
IGMP Message type Received Sent Rx errors
Membership Query 0 230 0
V1 Membership Report 0 0 0
Copyright © 2016, Juniper Networks, Inc.
461
Multicast Protocols Feature Guide for EX4600 Switches show system statistics igmp
List of Syntax
Syntax (EX Series Switches) on page 462
Syntax (TX Matrix Router) on page 462
Syntax (TX Matrix Plus Router) on page 462
Syntax show system statistics igmp
Syntax (EX Series
Switches) show system statistics igmp
<all-members>
<local>
<member member-id>
Syntax (TX Matrix
Router) show system statistics igmp
<all-chassis | all-lcc | lcc number | scc>
Syntax (TX Matrix Plus
Router) show system statistics igmp
<all-chassis | all-lcc | lcc number | sfc number>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display system-wide Internet Group Management Protocol (IGMP) statistics.
Options none —Display system statistics for IGMP.
all-chassis —(TX Matrix routers and TX Matrix Plus routers only ) (Optional) Display system statistics for IGMP for all the routers in the chassis.
all-lcc —(TX Matrix routers and TX Matrix Plus routers only) (Optional) On a TX Matrix router, display system statistics for IGMP for all T640 routers (or line-card chassis) connected to the TX Matrix router. On a TX Matrix Plus router, display system statistics for IGMP for all connected T1600 or T4000 LCCs.
all-members —(EX4200 switches only) (Optional) Display IGMP statistics for all members of the Virtual Chassis configuration.
lcc number —(TX Matrix routers and TX Matrix Plus routers only) (Optional) On a TX
Matrix router, display system statistics for IGMP for a specific T640 router that is connected to the TX Matrix router. On a TX Matrix Plus router, display system statistics for IGMP for a specific router that is connected to the TX Matrix Plus router.
462 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands
Replace number with the following values depending on the LCC configuration:
• 0 through 3, when T640 routers are connected to a TX Matrix router in a routing matrix.
• 0 through 3, when T1600 routers are connected to a TX Matrix Plus router in a routing matrix.
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
• 0, 2, 4, or 6, when T4000 routers are connected to a TX Matrix Plus router with
3D SIBs in a routing matrix.
local —(EX4200 switches only) (Optional) Display IGMP statistics for the local Virtual
Chassis member.
member member-id —(EX4200 switches only) (Optional) Display IGMP statistics for the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9.
scc —(TX Matrix routers only) (Optional) Display system statistics for IGMP for the TX
Matrix router (or switch-card chassis).
sfc number —(TX Matrix Plus routers only) (Optional) Display system statistics for IGMP for the TX Matrix Plus router. Replace number with 0.
Additional Information By default, when you issue the show system statistics igmp command on the master
Routing Engine of a TX Matrix router or a TX Matrix Plus router, the command is broadcast to all the master Routing Engines of the LCCs connected to it in the routing matrix.
Likewise, if you issue the same command on the backup Routing Engine of a TX Matrix or a TX Matrix Plus router, the command is broadcast to all backup Routing Engines of the LCCs that are connected to it in the routing matrix.
Required Privilege
Level view
Related
Documentation
• Routing Matrix with a TX Matrix Plus Router Solutions Page
List of Sample Output
show system statistics igmp on page 463
Sample Output show system statistics igmp user@host> show system statistics igmp igmp:
17178 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
Copyright © 2016, Juniper Networks, Inc.
463
Multicast Protocols Feature Guide for EX4600 Switches
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 membership reports sent show system statistics igmp (EX Series Switches) user@host> show system statistics igmp igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid fields
0 membership reports received
0 membership reports received with invalid fields
0 membership reports received for groups to which we belong
0 Membership reports sent show system statistics igmp (TX Matrix Plus Router) user@host> show system statistics igmp sfc0-re0:
-------------------------------------------------------------------------igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 membership reports sent lcc0-re0:
-------------------------------------------------------------------------igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 membership reports sent lcc1-re0:
-------------------------------------------------------------------------igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 membership reports sent
464 Copyright © 2016, Juniper Networks, Inc.
Chapter 19: IGMP Operational Commands lcc2-re0:
-------------------------------------------------------------------------igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 membership reports sent lcc3-re0:
-------------------------------------------------------------------------igmp:
0 messages received
0 messages received with too few bytes
0 messages received with bad checksum
0 membership queries received
0 membership queries received with invalid field(s)
0 membership reports received
0 membership reports received with invalid field(s)
0 membership reports received for groups to which we belong
0 membership reports sent
Copyright © 2016, Juniper Networks, Inc.
465
Multicast Protocols Feature Guide for EX4600 Switches
466 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 20
IGMP Snooping Operational Commands
•
clear igmp-snooping membership
•
clear igmp-snooping statistics
•
•
•
•
Copyright © 2016, Juniper Networks, Inc.
467
Multicast Protocols Feature Guide for EX4600 Switches clear igmp-snooping membership
Syntax clear igmp-snooping membership
<vlan vlan-name>
Release Information Command introduced in Junos OS Release 11.1 for the QFX Series.
Description Clear IGMP snooping membership information.
Options vlan vlan-name —(Optional) Name of the VLAN.
Required Privilege
Level view
Related
Documentation
•
show igmp-snooping membership on page 470
List of Sample Output
clear igmp-snooping membership on page 468
Sample Output clear igmp-snooping membership user@switch> clear igmp-snooping membership vlan employee-vlan
468 Copyright © 2016, Juniper Networks, Inc.
Chapter 20: IGMP Snooping Operational Commands clear igmp-snooping statistics
Syntax clear igmp-snooping statistics
Release Information Command introduced in Junos OS Release 11.1 for the QFX Series.
Description Clear IGMP snooping statistics.
Required Privilege
Level view
Related
Documentation
•
show igmp-snooping statistics on page 475
List of Sample Output
clear igmp-snooping statistics on page 469
Sample Output clear igmp-snooping statistics user@switch> clear igmp-snooping statistics
Copyright © 2016, Juniper Networks, Inc.
469
Multicast Protocols Feature Guide for EX4600 Switches show igmp-snooping membership
Syntax show igmp-snooping membership
<brief | detail>
<interface interface-name>
<vlan vlan-id | vlan-name>
Release Information Command introduced in Junos OS Release 11.1 for the QFX Series.
IGMPv3 output introduced in Junos OS Release 12.1 for the QFX Series.
Description Display IGMP snooping membership information.
Options none —Display general parameters.
brief | detail —(Optional) Display the specified level of output.
interface interface-name —(Optional) Display IGMP snooping information for the specified interface.
vlan vlan-id | vlan-name —(Optional) Display IGMP snooping information for the specified
VLAN.
Required Privilege
Level view
Related
Documentation
•
Monitoring IGMP Snooping on page 133
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping route on page 473
•
show igmp-snooping statistics on page 475
•
show igmp-snooping vlans on page 477
List of Sample Output
show igmp-snooping membership on page 471
show igmp-snooping membership detail on page 472
Output Fields
lists the output fields for the show igmp-snooping membership command. Output fields are listed in the approximate order in which they appear.
Table 36: show igmp-snooping membership Output Fields
Field Name Field Description Level of Output
VLAN
Interfaces
Tag
Name of the VLAN.
Interfaces assigned to the VLAN.
All
All
Numerical identifier of the VLAN.
detail
470 Copyright © 2016, Juniper Networks, Inc.
Chapter 20: IGMP Snooping Operational Commands
Table 36: show igmp-snooping membership Output Fields (continued)
Field Name Field Description Level of Output
Router interfaces
• static or dynamic
• Uptime
Names of multicast router interfaces.
detail
Whether the multicast router interface is static or dynamic .
detail
For static interfaces, length of time since the interface was configured as a multicast router interface; for dynamic interfaces, length of time since the first query was received on the interface.
detail
• timeout
Group
Receiver count
Flags
Uptime timeout
Last reporter
Include source
Query timeout in seconds.
IP multicast address of the multicast group.
detail detail
Number of interfaces that have membership in a multicast group.
detail
IGMP version of the host sending a join message.
detail
Length of time a multicast group has been active on the interface.
detail
Time (in seconds) left until the entry for the multicast group is removed.
Source addresses from which multicast streams are allowed based on IGMPv3 reports.
All
Last host to report membership for the multicast group.
detail detail
Sample Output show igmp-snooping membership user@switch> show igmp-snooping membership
VLAN: v1
224.1.1.1 * 258 secs
Interfaces: ge-0/0/0.0
224.1.1.3 * 258 secs
Interfaces: ge-0/0/0.0
224.1.1.5 * 258 secs
Interfaces: ge-0/0/0.0
224.1.1.7 * 258 secs
Copyright © 2016, Juniper Networks, Inc.
471
Multicast Protocols Feature Guide for EX4600 Switches
Interfaces: ge-0/0/0.0
224.1.1.9 * 258 secs
Interfaces: ge-0/0/0.0
224.1.1.11 * 258 secs
Interfaces: ge-0/0/0.0
show igmp-snooping membership detail user@switch> show igmp-snooping membership detail
VLAN: v43 Tag: 43 (Index: 4)
Group: 225.0.0.2
Receiver count: 1, Flags: <V3-hosts>
ge-0/0/15.0 Uptime: 00:00:11 timeout: 248 Last reporter: 10.2.10.16
Include source: 1.2.1.1, 1.3.1.1
VLAN: v44 Tag: 44 (Index: 5)
Group: 225.0.0.1
Receiver count: 1, Flags: <V2-hosts>
ge-0/0/21.0 Uptime: 00:00:02 timeout: 257
VLAN: v110 Tag: 110 (Index: 4)
Router interfaces:
ge-0/0/3.0 static Uptime: 00:08:45
ge-0/0/2.0 static Uptime: 00:08:45
ge-0/0/4.0 dynamic Uptime: 00:16:41 timeout: 254
Group: 225.0.0.3
Receiver count: 1, Flags: <V3-hosts>
ge-0/0/5.0 Uptime: 00:00:19 timeout: 259
Group: 225.1.1.1
Receiver count: 1, Flags: <V2-hosts>
ge-0/0/5.0 Uptime: 00:22:43 timeout: 96
Group: 225.2.2.2
Receiver count: 1, Flags: <V2-hosts Static>
ge-0/0/5.0 Uptime: 00:23:13
472 Copyright © 2016, Juniper Networks, Inc.
Chapter 20: IGMP Snooping Operational Commands show igmp-snooping route
Syntax show igmp-snooping route
<brief | detail>
<ethernet-switching <brief | detail | vlan (vlan-id | vlan-name )>>
<inet <brief | detail | vlan vlan-name>>
<vlan vlan-name>
Release Information Command introduced in Junos OS Release 11.1 for the QFX Series.
Description Display IGMP snooping route information.
Options none —Display general parameters.
brief | detail —(Optional) Display the specified level of output.
ethernet-switching —(Optional) Display Ethernet switching information.
inet —(Optional) Display inet information.
vlan vlan-name —(Optional) Display route information for the specified VLAN.
Required Privilege
Level view
Related
Documentation
•
Monitoring IGMP Snooping on page 133
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping statistics on page 475
•
show igmp-snooping vlans on page 477
List of Sample Output
show igmp-snooping route on page 474 show igmp-snooping route vlan v1 on page 474
Output Fields
lists the output fields for the show igmp-snooping route command.
Output fields are listed in the approximate order in which they appear.
Table 37: show igmp-snooping route Output Fields
Field Name Field Description
Table
VLAN
Group
(For internal use only. Value is always 0.)
Name of the VLAN.
Multicast group address.
Interfaces on which IGMP packets were snooped.
Interfaces
Next-hop ID associated with the next-hop device.
Copyright © 2016, Juniper Networks, Inc.
473
Multicast Protocols Feature Guide for EX4600 Switches
Sample Output show igmp-snooping route user@switch> show igmp-snooping route
VLAN Group Next-hop
V11 224.1.1.1, * 533
Interfaces: ge-0/0/13.0, ge-0/0/1.0
VLAN Group Next-hop v12 224.1.1.3, * 534
Interfaces: ge-0/0/13.0, ge-0/0/0.0
show igmp-snooping route vlan v1 user@switch> show igmp-snooping route vlan v1
Table: 0
VLAN Group Next-hop v1 224.1.1.1, * 1266
Interfaces: ge-0/0/0.0
v1 224.1.1.3, * 1266
Interfaces: ge-0/0/0.0
v1 224.1.1.5, * 1266
Interfaces: ge-0/0/0.0
v1 224.1.1.7, * 1266
Interfaces: ge-0/0/0.0
v1 224.1.1.9, * 1266
Interfaces: ge-0/0/0.0
v1 224.1.1.11, * 1266
Interfaces: ge-0/0/0.0
474 Copyright © 2016, Juniper Networks, Inc.
Chapter 20: IGMP Snooping Operational Commands show igmp-snooping statistics
Syntax show igmp-snooping statistics
Release Information Command introduced in Junos OS Release 11.1 for the QFX Series.
Description Display IGMP snooping statistics.
Required Privilege
Level view
Related
Documentation
•
Monitoring IGMP Snooping on page 133
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping route on page 473
•
show igmp-snooping vlans on page 477
List of Sample Output
show igmp-snooping statistics on page 476
Output Fields
lists the output fields for the show igmp-snooping statistics command.
Output fields are listed in the approximate order in which they appear.
Table 38: show igmp-snooping statistics Output Fields
Field Name Field Description
Bad length IGMP packet has illegal or bad length.
IGMP or IP checksum is incorrect.
Bad checksum
Invalid interface
Not local
Receive unknown
Packet was received through an invalid interface.
Number of packets received from senders that are not local.
Unknown IGMP type.
Timed out
IGMP Type
Received
Transmitted
Recv Errors
Number of timeouts for all multicast groups.
Type of IGMP message ( Queries , Reports , Leaves , or Other ).
Number of IGMP packets received.
Number of IGMP packets transmitted.
Number of general receive errors.
Copyright © 2016, Juniper Networks, Inc.
475
Multicast Protocols Feature Guide for EX4600 Switches
Sample Output show igmp-snooping statistics user@switch> show igmp-snooping statistics
Bad length: 0 Bad checksum: 0 Invalid interface: 0
Not local: 0 Receive unknown: 0 Timed out: 58
IGMP Type Received Transmitted Recv Errors
Queries: 74295 0 0
Reports: 18148423 0 16333523
Leaves: 0 0 0
Other: 0 0 0
476 Copyright © 2016, Juniper Networks, Inc.
Chapter 20: IGMP Snooping Operational Commands show igmp-snooping vlans
Syntax show igmp-snooping vlans
<brief | detail>
<vlan vlan-id | vlan-name>
Release Information Command introduced in Junos OS Release 11.1 for the QFX Series.
Description Display IGMP snooping VLAN information.
Options none —Display general parameters.
brief | detail —(Optional) Display the specified level of output.
vlan vlan-id | vlan vlan-number —(Optional) Display VLAN information for the specified
VLAN.
Required Privilege
Level view
Related
Documentation
•
Monitoring IGMP Snooping on page 133
•
Configuring IGMP Snooping on page 128
•
show igmp-snooping route on page 473
•
show igmp-snooping statistics on page 475
List of Sample Output
Output Fields
lists the output fields for the show igmp-snooping vlans command.
Output fields are listed in the approximate order in which they appear.
Table 39: show igmp-snooping vlans Output Fields
Field Name Field Description Level of Output
VLAN
IGMP-L2-Querier
Name of the VLAN.
Source address for IGMP snooping queries (if switch is an IGMP querier)
Number of interfaces in the VLAN.
All levels
All levels
All levels Interfaces
Groups
MRouters
Receivers
Number of groups in the VLAN.
Number of multicast routers associated with the VLAN.
Number of host receivers in the VLAN.
All levels
All levels
All levels
Copyright © 2016, Juniper Networks, Inc.
477
Multicast Protocols Feature Guide for EX4600 Switches
Table 39: show igmp-snooping vlans Output Fields (continued)
Field Name Field Description
Tag tagged | untagged vlan-interface
Membership timeout
Querier timeout
Level of Output
Numerical identifier of the VLAN.
Interface participates in a tagged (802.1Q) or untagged (native)
VLAN.
Internal VLAN interface identifier.
detail detail detail
Membership timeout value.
detail
Timeout value for interfaces dynamically marked as router or switch interfaces (interfaces that receive queries). When the querier timeout is reached, the switch marks the interface as a host interface.
detail
Interface
Reporters
Name of the interface.
Number of dynamic groups on an interface.
detail detail
Sample Output show igmp-snooping vlans user@switch> show igmp-snooping vlans
VLAN Interfaces Groups MRouters Receivers default 0 0 0 0 v1 11 50 0 0 v10 1 0 0 0 v11 1 0 0 0 v180 3 0 1 0 v181 3 0 0 0 v182 3 0 0 0 show igmp-snooping vlans vlan user@switch> show igmp-snooping vlans vlan v10 user@switch> show igmp-snooping vlans vlan v10
VLAN Interfaces Groups MRouters Receivers v10 1 0 0 0 show igmp-snooping vlans vlan detail user@switch> show igmp-snooping vlans vlan v10 detail
VLAN: v10, Tag: 10, vlan-interface: vlan.10
Interface: ge-0/0/10.0, tagged, Groups: 0
IGMP-L2-Querier: Stopped, SourceAddress: 10.10.1.2
478 Copyright © 2016, Juniper Networks, Inc.
CHAPTER 21
MSDP Operational Commands
•
•
•
•
•
•
•
Copyright © 2016, Juniper Networks, Inc.
479
Multicast Protocols Feature Guide for EX4600 Switches clear msdp cache
Syntax clear msdp cache
<all>
<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Clear the entries in the Multicast Source Discovery Protocol (MSDP) source-active cache.
Options all — Clear all MSDP source-active cache entries in the master instance..
instance instance-name —(Optional) Clear entries for a specific MSDP instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
peer peer-address —(Optional) Clear the MSDP source-active cache entries learned from a specific peer.
Required Privilege
Level clear
Related
Documentation
•
show msdp source-active on page 486
List of Sample Output
clear msdp cache all on page 480
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output clear msdp cache all user@host> clear msdp cache all
480 Copyright © 2016, Juniper Networks, Inc.
Chapter 21: MSDP Operational Commands clear msdp statistics
Syntax clear msdp statistics
<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Description Clear Multicast Source Discovery Protocol (MSDP) peer statistics.
Options none —Clear MSDP statistics for all peers.
instance instance-name —(Optional) Clear statistics for the specified instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
peer peer-address —(Optional) Clear the statistics for the specified peer.
Required Privilege
Level clear
Related
Documentation
•
show msdp statistics on page 489
List of Sample Output
clear msdp statistics on page 481
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output clear msdp statistics user@host> clear msdp statistics
Copyright © 2016, Juniper Networks, Inc.
481
Multicast Protocols Feature Guide for EX4600 Switches show msdp
Syntax show msdp
<brief | detail>
<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display Multicast Source Discovery Protocol (MSDP) information.
Options none —Display standard MSDP information for all routing instances.
brief | detail —(Optional) Display the specified level of output.
instance instance-name —(Optional) Display information for the specified instance only.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
peer peer-address —(Optional) Display information about the specified peer only,
Required Privilege
Level view
Related
Documentation
•
•
show msdp source-active on page 486
•
show msdp statistics on page 489
List of Sample Output
show msdp on page 483 show msdp brief on page 483 show msdp detail on page 483
Output Fields
describes the output fields for the show msdp command. Output fields are listed in the approximate order in which they appear.
Table 40: show msdp Output Fields
Field Name Field Description Level of Output
IP address of the peer.
All levels Peer address
Local address
State
Last up/down
Local address of the peer.
Status of the MSDP connection: Listen , Established , or Inactive .
Time at which the most recent peer-state change occurred.
All levels
All levels
All levels
482 Copyright © 2016, Juniper Networks, Inc.
Chapter 21: MSDP Operational Commands
Table 40: show msdp Output Fields (continued)
Field Name Field Description
Peer-Group
SA Count
SA received
Peer group name.
Number of source-active cache entries advertised by each peer that were accepted, compared to the number that were received, in the format
number-accepted/number-received .
Peer Connect Retries Number of peer connection retries.
Number of seconds before another message is sent to a peer.
State timer expires
Peer Times out Number of seconds to wait for a response from the peer before the peer is declared unavailable.
SA accepted Number of entries in the source-active cache accepted from the peer.
Number of entries in the source-active cache received by the peer.
Level of Output
All levels
All levels detail detail detail detail detail
Sample Output show msdp user@host> show msdp
Peer address Local address State Last up/down Peer-Group SA Count
198.32.8.193 198.32.8.195 Established 5d 19:25:44 North23 120/150
198.32.8.194 198.32.8.195 Established 3d 19:27:27 North23 300/345
198.32.8.196 198.32.8.195 Established 5d 19:39:36 North23 10/13
198.32.8.197 198.32.8.195 Established 5d 19:32:27 North23 5/6
198.32.8.198 198.32.8.195 Established 3d 19:33:04 North23 2305/3000 show msdp brief
The output for the show msdp brief command is identical to that for the show msdp command. For sample output, see
show msdp detail user@host> show msdp detail
Peer: 10.255.70.15
Local address: 10.255.70.19
State: Established
Peer Connect Retries: 0
State timer expires: 22
Peer Times out: 49
SA accepted: 0
SA received: 0
Copyright © 2016, Juniper Networks, Inc.
483
Multicast Protocols Feature Guide for EX4600 Switches show msdp source
Syntax show msdp source
<instance instance-name>
<logical-system (all | logical-system-name)>
<source-address>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display multicast sources learned from Multicast Source Discovery Protocol (MSDP).
Options none —Display standard MSDP source information for all routing instances.
instance instance-name —(Optional) Display information for the specified instance only.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
source-address —(Optional) IP address and optional prefix length. Display information for the specified source address only.
Required Privilege
Level view
Related
Documentation
•
•
show msdp source-active on page 486
•
show msdp statistics on page 489
List of Sample Output
484 Copyright © 2016, Juniper Networks, Inc.
Chapter 21: MSDP Operational Commands
Output Fields
describes the output fields for the show msdp source command.
Output fields are listed in the approximate order in which they appear.
Table 41: show msdp source Output Fields
Field Name Field Description
IP address of the source.
Source address
/Len
Type
Maximum
Threshold
Exceeded
Length of the prefix for this IP address.
Discovery method for this multicast source:
•
•
Configured —Source-active limit explicitly configured for this source.
Dynamic —Source-active limit established when this source was discovered.
Source-active limit applied to this source.
Source-active threshold applied to this source.
Number of source-active messages received from this source exceeding the established maximum.
Sample Output show msdp source user@host> show msdp source
Source address /Len Type Maximum Threshold Exceeded
0.0.0.0 /0 Configured 5 none 0
10.1.0.0 /16 Configured 500 none 0
10.1.1.1 /32 Configured 10000 none 0
10.1.1.2 /32 Dynamic 6936 none 0
10.1.5.5 /32 Dynamic 500 none 123
10.2.1.1 /32 Dynamic 2 none 0
Copyright © 2016, Juniper Networks, Inc.
485
Multicast Protocols Feature Guide for EX4600 Switches show msdp source-active
Syntax show msdp source-active
<brief | detail>
<group group>
<instance instance-name>
<local>
<logical-system (all | logical-system-name)>
<originator originator>
<peer peer-address>
<source source-address>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display the Multicast Source Discovery Protocol (MSDP) source-active cache.
Options none —Display standard MSDP source-active cache information for all routing instances.
brief | detail —(Optional) Display the specified level of output.
group group —(Optional) Display source-active cache information for the specified group.
instance instance-name —(Optional) Display information for the specified instance.
local —(Optional) Display all source-active caches originated by this router.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
originator originator —(Optional) Display information about the peer that originated the source-active cache entries.
peer peer-address —(Optional) Display the source-active cache of the specified peer.
source source-address —(Optional) Display the source-active cache of the specified source.
Required Privilege
Level view
Related
Documentation
•
•
•
show msdp statistics on page 489
List of Sample Output
show msdp source-active on page 487
486 Copyright © 2016, Juniper Networks, Inc.
Chapter 21: MSDP Operational Commands
Output Fields
describes the output fields for the show msdp source-active command. Output fields are listed in the approximate order in which they appear.
Table 42: show msdp source-active Output Fields
Field Name Field Description
Number of times all peers have exceeded configured active source limits.
Global active source limit exceeded
Configured number of active source messages accepted by the device.
Global active source limit maximum
Global active source limit threshold
Global active source limit log-warning
Global active source limit log interval
Group address
Source address
Configured threshold for applying random early discard (RED) to drop some but not all MSDP active source messages.
Threshold at which a warning message is logged (percentage of the number of active source messages accepted by the device).
Time (in seconds) between consecutive log messages.
Multicast address of the group.
IP address of the source.
IP address of the peer.
Peer address
Originator
Flags
Router ID configured on the source of the rendezvous point (RP) that originated the message, or the loopback address when the router ID is not configured.
Flags: Accept , Reject , or Filtered .
Sample Output show msdp source-active user@host> show msdp source-active
Group address Source address Peer address Originator Flags
230.0.0.0 192.168.195.46 local 10.255.14.30 Accept
230.0.0.1 192.168.195.46 local 10.255.14.30 Accept
230.0.0.2 192.168.195.46 local 10.255.14.30 Accept
230.0.0.3 192.168.195.46 local 10.255.14.30 Accept
230.0.0.4 192.168.195.46 local 10.255.14.30 Accept
Copyright © 2016, Juniper Networks, Inc.
487
Multicast Protocols Feature Guide for EX4600 Switches show msdp source-active brief
The output for the show msdp source-active brief command is identical to that for the show msdp source-active command. For sample output, see
show msdp source-active on page 487 .
show msdp source-active detail
The output for the show msdp source-active detail command is identical to that for the show msdp source-active command. For sample output, see
show msdp source-active on page 487 .
show msdp source-active source user@host> show msdp source-active source 192.168.215.246
Global active source limit exceeded: 0
Global active source limit maximum: 25000
Global active source limit threshold: 24000
Global active source limit log-warning: 100
Global active source limit log interval: 0
Group address Source address Peer address Originator Flags
226.2.2.1 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.3 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.4 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.5 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.7 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.10 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.11 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.13 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.14 192.168.215.246 10.255.182.140 10.255.182.140 Accept
226.2.2.15 192.168.215.246 10.255.182.140 10.255.182.140 Accept
488 Copyright © 2016, Juniper Networks, Inc.
Chapter 21: MSDP Operational Commands show msdp statistics
Syntax show msdp statistics
<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Display statistics about Multicast Source Discovery Protocol (MSDP) peers.
Options none —Display statistics about all MSDP peers for all routing instances.
instance instance-name —(Optional) Display statistics about a specific MSDP instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
peer peer-address —(Optional) Display statistics about a particular MSDP peer.
Required Privilege
Level view
Related
Documentation
•
clear msdp statistics on page 481
List of Sample Output
show msdp statistics on page 491 show msdp statistics peer on page 491
Output Fields
describes the output fields for the show msdp statistics command.
Output fields are listed in the approximate order in which they appear.
Table 43: show msdp statistics Output Fields
Field Name Field Description
Global active source limit exceeded
Global active source limit maximum
Number of times all peers have exceeded configured active source limits.
Configured number of active source messages accepted by the device.
Global active source limit threshold
Global active source limit log-warning
Global active source limit log interval
Configured threshold for applying random early discard (RED) to drop some but not all MSDP active source messages.
Threshold at which a warning message is logged (percentage of the number of active source messages accepted by the device).
Time (in seconds) between consecutive log messages.
Copyright © 2016, Juniper Networks, Inc.
489
Multicast Protocols Feature Guide for EX4600 Switches
Table 43: show msdp statistics Output Fields (continued)
Field Name Field Description
Peer Address of peer.
How long ago the peer state changed.
Last State Change
Last message received from the peer
How long ago the last message was received from the peer.
RPF Failures Number of reverse path forwarding (RPF) failures.
Remote Closes Number of times the remote peer closed.
Number of peer timeouts.
Peer Timeouts
SA messages sent Number of source-active messages sent.
SA messages received Number of source-active messages received.
SA request messages sent Number of source-active request messages sent.
SA request messages received
Number of source-active request messages received.
SA response messages sent Number of source-active response messages sent.
Number of source-active response messages received.
SA response messages received
SA messages with zero
Entry Count received
Entry Count is a field within SA message that defines how many source/group tuples are present in the SA message. The counter is incremented each time an SA with an Entry Count of zero is received.
Active source exceeded
Active source Maximum
Number of times this peer has exceeded configured source-active limits.
Configured number of active source messages accepted by this peer.
Active source threshold
Active source log-warning
Configured threshold on this peer for applying random early discard
(RED) to drop some but not all MSDP active source messages.
Configured threshold on this peer at which a warning message is logged (percentage of the number of active source messages accepted by the device).
Time (in seconds) between consecutive log messages on this peer.
Active source log-interval
Keepalive messages sent Number of keepalive messages sent.
490 Copyright © 2016, Juniper Networks, Inc.
Chapter 21: MSDP Operational Commands
Table 43: show msdp statistics Output Fields (continued)
Field Name Field Description
Number of keepalive messages received.
Keepalive messages received
Unknown messages received
Number of unknown messages received.
Error messages received Number of error messages received.
Sample Output show msdp statistics user@host> show msdp statistics
Global active source limit exceeded: 0
Global active source limit maximum: 10
Global active source limit threshold: 8
Global active source limit log-warning: 60
Global active source limit log interval: 60
Peer: 10.255.245.39
Last State Change: 11:54:49 (00:24:59)
Last message received from peer: 11:53:32 (00:26:16)
RPF Failures: 0
Remote Closes: 0
Peer Timeouts: 0
SA messages sent: 376
SA messages received: 459
SA messages with zero Entry Count received: 0
SA request messages sent: 0
SA request messages received: 0
SA response messages sent: 0
SA response messages received: 0
Active source exceeded: 0
Active source Maximum: 10
Active source threshold: 8
Active source log-warning: 60
Active source log-interval 120
Keepalive messages sent: 17
Keepalive messages received: 19
Unknown messages received: 0
Error messages received: 0 show msdp statistics peer user@host> show msdp statistics peer 10.255.182.140
Peer: 10.255.182.140
Last State Change: 8:19:23 (00:01:08)
Last message received from peer: 8:20:05 (00:00:26)
RPF Failures: 0
Remote Closes: 0
Peer Timeouts: 0
SA messages sent: 17
SA messages received: 16
SA request messages sent: 0
SA request messages received: 0
Copyright © 2016, Juniper Networks, Inc.
491
Multicast Protocols Feature Guide for EX4600 Switches
SA response messages sent: 0
SA response messages received: 0
Active source exceeded: 20
Active source Maximum: 10
Active source threshold: 8
Active source log-warning: 60
Active source log-interval: 120
Keepalive messages sent: 0
Keepalive messages received: 0
Unknown messages received: 0
Error messages received: 0
492 Copyright © 2016, Juniper Networks, Inc.
Chapter 21: MSDP Operational Commands test msdp
Syntax test msdp (dependent-peers prefix | rpf-peer originator)
<instance instance-name>
<logical-system (all | logical-system-name)>
Release Information Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description Find Multicast Source Discovery Protocol (MSDP) peers.
Options dependent-peers prefix —Find downstream dependent MSDP peers.
rpf-peer originator —Find the MSDP reverse-path-forwarding (RPF) peer for the originator.
instance instance-name —(Optional) Find MDSP peers for the specified routing instance.
logical-system (all | logical-system-name) —(Optional) Perform this operation on all logical systems or on a particular logical system.
Required Privilege
Level view
List of Sample Output
test msdp dependent-peers on page 493
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output test msdp dependent-peers user@host> test msdp dependent-peers 10.0.0.1/24
Copyright © 2016, Juniper Networks, Inc.
493
Multicast Protocols Feature Guide for EX4600 Switches
494 Copyright © 2016, Juniper Networks, Inc.
PART 6
Index
•
Copyright © 2016, Juniper Networks, Inc.
495
Multicast Protocols Feature Guide for EX4600 Switches
496 Copyright © 2016, Juniper Networks, Inc.
Index
Symbols
#, comments in configuration statements....................
( ), in syntax descriptions.....................................................
< >, in syntax descriptions....................................................
[ ], in configuration statements.........................................
{ }, in configuration statements.........................................
| (pipe), in syntax descriptions...........................................
A accept-remote-source statement usage guidelines...........................................................
accounting statement
IGMP.................................................................................
IGMP interface..............................................................
active-source-limit statement.........................................
usage guidelines............................................................
address statement anycast RPs....................................................................
usage guidelines...........................................
local RPs..........................................................................
static RPs........................................................................
usage guidelines....................................................
algorithm statement
BFD authentication.....................................................
anycast RP................................................................................
overview............................................................................
anycast-pim statement.......................................................
usage guidelines....................................................
asm-override-ssm statement................................
,
assert (tracing flag)............................................................
assert timeout configuring.......................................................................
assert-timeout statement.................................................
usage guidelines............................................................
authentication configuration
BFD.......................................................................................
authentication statement
BFD....................................................................................
BFD protocol..................................................................
authentication-key statement
MSDP.................................................................................
B
BFD
authentication configuration......................................
protocol..............................................................................
BFD authentication
algorithm statement..................................................
authentication statement.........................................
key-chain statement...................................................
loose-check statement..............................................
bfd-liveness-detection statement
PIM............................................................................
,
minimum-interval...............................................
threshold................................................................
transmit-interval.................................................
usage guidelines.....................................................
bootstrap (tracing flag).....................................................
bootstrap messages.............................................................
bootstrap routers
overview............................................................................
bootstrap routers, displaying...........................................
bootstrap statement...........................................................
bootstrap-export statement............................................
bootstrap-import statement............................................
bootstrap-priority statement...........................................
braces, in configuration statements.................................
brackets
angle, in syntax descriptions......................................
BSR
square, in configuration statements........................
policy, import..................................................................
C
cache (tracing flag).............................................................
CBT issues.....................................................................................
clear igmp membership command..............................
clear igmp statistics command......................................
clear igmp-snooping membership command.........
clear igmp-snooping statistics command.................
clear msdp cache command..........................................
clear msdp statistics command.....................................
clear multicast bandwidth-admission command...........................................................................
clear multicast scope command....................................
clear multicast sessions command..............................
clear multicast statistics command.............................
clear pim join command....................................................
clear pim register command............................................
clear pim statistics command........................................
Copyright © 2016, Juniper Networks, Inc.
497
Multicast Protocols Feature Guide for EX4600 Switches
comments, in configuration statements........................
conventions
text and syntax...............................................................
curly braces, in configuration statements......................
customer support...................................................................
xxi contacting JTAC..............................................................
D
data-encapsulation statement........................................
usage guidelines............................................................
default-peer statement......................................................
usage guidelines............................................................
designated router....................................................................
detection-time statement
PIM.....................................................................................
disable statement
IGMP.................................................................................
usage guidelines...................................................
IGMP snooping.............................................................
MLD
usage guidelines..................................................
MSDP................................................................................
PIM family......................................................................
PIM interfaces..............................................................
PIM protocol.................................................................
distribution trees
RPT.......................................................................................
shared..................................................................................
documentation
comments on..................................................................
dr-election-on-p2p statement........................................
PIM usage guidelines.....................................................
dr-register-policy statement............................................
usage guidelines.............................................................
DVMRP
groups, displaying.......................................................
dynamic IGMP statements promiscuous-mode interface...................................................................
E embedded-rp statement..................................................
enable IGMP static group membership.........................
enable MLD static group membership...........................
event recording
IGMP...................................................................................
MLD...................................................................................
exclude statement
IGMP................................................................................
MLD usage guidelines....................................................
usage guidelines....................................................
export statement
MSDP................................................................................
PIM..........................................................................
,
configuring...............................................................
PIM RP usage guidelines....................................................
F family statement bootstrap........................................................................
local RP............................................................................
PIM protocol..................................................................
font conventions.....................................................................
forwarding table
multicast information, displaying..........................
G graft (tracing flag)
PIM....................................................................................
group joins
limiting....................................................................
group membership
SSM maps........................................................................
group statement
IGMP..................................................................................
usage guidelines....................................................
IGMP snooping.............................................................
MLD
usage guidelines....................................................
MSDP................................................................................
PIM RPF selection.......................................................
group-count statement
IGMP.................................................................................
MLD usage guidelines....................................................
usage guidelines....................................................
group-increment statement
IGMP.................................................................................
usage guidelines....................................................
MLD
usage guidelines....................................................
group-limit statement configuring......................................................................
IGMP interface..............................................................
498 Copyright © 2016, Juniper Networks, Inc.
Index
IGMP snooping.............................................................
MLD
usage guidelines..................................................
group-policy statement
IGMP.................................................................................
usage guidelines..................................................
MLD
usage guidelines..................................................
group-ranges statement...................................................
usage guidelines.............................................................
groups
DVMRP, displaying.....................................................
IGMP membership, displaying...............................
PIM general information, displaying....................
usage information, displaying.......................
SSM...................................................................................
H hello (tracing flag)
PIM....................................................................................
hello-interval statement
PIM.....................................................................................
usage guidelines......................................................
hold-time statement
PIM......................................................................................
host-only-interface statement.......................................
I
IGMP..........................................................................................
configuration statements.........................................
102 configuring......................................................................
disabling...........................................................................
enabling.................................................................
event recording...............................................................
group membership
SSM maps for different groups to different sources.................................................................
group membership, displaying..............................
host-query message interval..........................
interface group limit...................................................
interfaces, displaying.................................................
last-member query interval............................
overview..........................................................................
PIM-to-IGMP message translation information, displaying.....................................................................
query response interval.....................................
,
robustness variable..............................................
static group membership...........................................
statistics, displaying...................................................
tracing operations.........................................................
version....................................................................
IGMP snooping configure the switch to be an IGMP querier..........................................................................
enabling..........................................................................
group limit......................................................................
group statement..........................................................
host-only interface.....................................................
host-query message interval..................................
last-member query interval....................................
query response interval............................................
source address..............................................................
static statement..........................................................
igmp statement....................................................................
usage guidelines...........................................................
IGMP statements promiscuous-mode interface...................................................................
igmp-querier statement..........................................
igmp-snooping statement...............................................
IGMPv3......................................................................................
102 interoperability with older versions.......................
immediate-leave statement
IGMP.................................................................................
usage guidelines...................................................
IGMP snooping..............................................................
MLD
usage guidelines...................................................
import statement bootstrap.........................................................................
usage guidelines....................................................
MSDP.................................................................................
PIM.....................................................................................
usage guidelines.....................................................
infinity statement..................................................................
usage guidelines.............................................................
interface statement
IGMP.................................................................................
usage guidelines..................................................
IGMP snooping...................................................
MLD
usage guidelines..................................................
PIM.....................................................................................
Internet Group Management Protocol See IGMP
Copyright © 2016, Juniper Networks, Inc.
499
Multicast Protocols Feature Guide for EX4600 Switches
IP multicast announced sessions, displaying............................
bandwidth admission
clearing...................................................................
flow map information, displaying.........................
forwarding table, displaying....................................
interface information, displaying..........................
network information, displaying............................
next-hop table, displaying.......................................
PIM-to-IGMP message translation information, displaying.....................................................................
PIM-to-MLD message translation information, displaying....................................................................
RPF calculations, displaying....................................
scope, clearing...............................................................
scoped information, displaying..............................
sessions, clearing.........................................................
statistics clearing...................................................................
tracing routes from the receiver to the source......................
from the source to the gateway router..................................................................
from the source to the receiver.....................
listen for responses............................................
J
join (tracing flag)..................................................................
join states, clearing PIM.....................................................
join-load-balance statement...........................................
usage guidelines.............................................................
join-prune-timeout statement.........................................
K keepalive (tracing flag)
MSDP................................................................................
key-chain statement
BFD authentication......................................................
L l2-querier statement
IGMP snooping.............................................................
leave (tracing flag)
IGMP................................................................................
load balancing for PIM join.........................................................................
local statement
PIM.....................................................................................
usage guidelines....................................................
local-address statement
MSDP group...................................................................
MSDP peer......................................................................
PIM....................................................................................
loose-check statement
BFD authentication......................................................
M manuals
comments on..................................................................
mappings
SSM...................................................................................
maximum statement
MSDP................................................................................
usage guidelines...................................................
maximum-rps statement..................................................
maximum-transmit-rate statement
IGMP.................................................................................
MLD usage guidelines....................................................
usage guidelines..................................................
mesh groups
MSDP.................................................................................
minimum-interval
PIM....................................................................................
minimum-interval statement
PIM.....................................................................................
usage guidelines.....................................................
minimum-receive-interval statement
PIM...........................................................................
,
usage guidelines.....................................................
MLD disabling...........................................................................
event recording.............................................................
group membership
SSM maps for different groups to different
sources.................................................................
host-query message interval...................................
immediate-leave host removal
configuring..............................................................
last-member query interval.....................................
overview..................................................................
,
PIM-to-MLD message translation information,
displaying....................................................................
query response interval.............................................
robustness variable.....................................................
static group membership...........................................
mld enabling...........................................................................
500 Copyright © 2016, Juniper Networks, Inc.
Index
MLD snooping
host-query message interval..................................
proxy.................................................................................
mld statement usage guidelines..................................................
,
mode statement
MSDP...............................................................................
usage guidelines...................................................
PIM....................................................................................
usage guidelines....................................................
MSDP
active source limit........................................................
maximum...............................................................
per-source.............................................................
threshold................................................................
authentication................................................................
cache entries, clearing..............................................
configuration statements..........................................
167 configuring.......................................................................
data-encapsulation.....................................................
default peer............................................................
,
enabling............................................................................
general information, displaying.............................
groups...............................................................................
local address..................................................................
message source information, displaying...........
mode................................................................................
peer statistics clearing....................................................................
displaying..............................................................
policy, routing.........................................................
routing tables................................................................
source-active cache, displaying............................
tracing operations........................................................
msdp statement....................................................................
mt (tracing flag)...................................................................
mtrace (tracing flag)
IGMP...................................................................................
mtrace command.................................................................
mtrace from-source command......................................
mtrace monitor command................................................
mtrace to-gateway command........................................
multicast
anycast RP........................................................................
bootstrap router.............................................................
protocols group membership...............................................
SSM groups....................................................................
SSM mapping...............................................................
multicast filters........................................................................
MAC filters.........................................................................
MSDP SA messages...................................................
RP/DR register messages............................................
configuring...............................................................
multicast group joins
limiting....................................................................
Multicast Listener Discovery See MLD
Multicast Source Discovery Protocol See MSDP multicast-router-interface statement
IGMP snooping.............................................................
multiplier statement
PIM...........................................................................
,
usage guidelines.....................................................
N
neighbor-policy statement...............................................
usage guidelines.............................................................
next hops multicast entries, displaying...................................
no-accounting statement
IGMP.................................................................................
no-adaptation
PIM.....................................................................................
no-multicast-echo statement
PIM
usage guidelines......................................................
nsr-synchronization (tracing flag)..................................
O oif-map statement
IGMP.................................................................................
override-interval
PIM....................................................................................
override-interval statement
usage guidelines..............................................................
P packets (tracing flag)
IGMP..................................................................................
PIM.....................................................................................
parentheses, in syntax descriptions.................................
passive statement
IGMP.................................................................................
peer statement
MSDP................................................................................
Copyright © 2016, Juniper Networks, Inc.
501
Multicast Protocols Feature Guide for EX4600 Switches
PIM
anycast RP.............................................................
,
assert timeout......................................................
configuring..............................................................
background.........................................................................
BFD.......................................
,
,
,
bootstrap messages import and export...............
bootstrap routers...........................................................
bootstrap routers, displaying..................................
configuring..........................................................................
designated router...........................................................
embedded RP...............................................................
enabling..........................................................................
filters See multicast filters groups general information, displaying....................
usage information, displaying.......................
hello interval.......................................................................
hold-time period............................................................
incoming join filter policy, applying..........................
interfaces displaying..............................................................
join load balancing configuring................................................................
join states, clearing.....................................................
join suppression
configuring................................................................
join-prune-timeout.......................................................
maximum RPs...............................................................
neighbors, displaying..................................................
network components......................................................
outgoing join filter policy, applying..........................
overview...............................................................................
PIM-to-IGMP message translation information, displaying.....................................................................
PIM-to-MLD message translation information, displaying....................................................................
policy, routing.................................................................
prune states, clearing................................................
register clearing...................................................................
remote source................................................................
rendezvous point tree...................................................
routing tables................................................................
RPF, displaying source state...................................
RPs...............................................................
,
,
,
anycast.....................................................................
anycast RP...............................................................
displaying...............................................................
embedded.............................................................
mapping options...................................................
maximum...............................................................
source registration................................................
SPT cutover control.............................................
sparse mode.............................................................
SSM......................................................................
,
,
statistics clearing...................................................................
displaying...............................................................
version.................................................................
,
pim statement.......................................................................
usage guidelines...............................................................
PIM-RP
SPT configuring threshold cutover policy.............
policer, single-rate two-color example.............................................................................
policy statement
SSM map........................................................................
policy, import
BSR.....................................................................................
policy, routing
MSDP........................................................................
,
PIM.....................................................................................
PIM join filter..............................................................
prefix-list statement
PIM RPF selection........................................................
priority
PIM RPs...........................................................................
priority statement
bootstrap........................................................................
PIM....................................................................................
usage guidelines.....................................................
usage guidelines............................................................
promiscuous-mode statement
IGMP interface...................................................................
usage guidelines..................................................
propagation-delay statement.........................................
usage guidelines..............................................................
Protocol Independent Multicast See PIM protocols
group membership.......................................................
proxy statement
MLD snooping...............................................................
prune (tracing flag)
PIM.....................................................................................
prune states, clearing PIM................................................
502 Copyright © 2016, Juniper Networks, Inc.
Index
Q query-interval statement
IGMP..................................................................................
usage guidelines..................................................
IGMP snooping.............................................................
MLD
usage guidelines..................................................
MLD snooping...............................................................
query-last-member-interval statement
IGMP..................................................................................
usage guidelines..................................................
IGMP snooping.............................................................
MLD
usage guidelines..................................................
query-response-interval statement
IGMP..................................................................................
usage guidelines...................................................
IGMP snooping.............................................................
MLD
usage guidelines..................................................
R real-time monitoring
IP multicast paths........................................................
register (tracing flag)...........................................................
regular expressions
IP multicast scope clearing....................................................................
IP multicast sessions clearing...................................................................
displaying...............................................................
rendezvous points See RPs See PIM and RP report (tracing flag)
IGMP..................................................................................
reset-tracking-bit statement............................................
usage guidelines..............................................................
reverse path forwarding See RPF rib-group statement
MSDP...............................................................................
PIM....................................................................................
robust-count statement...................................................
IGMP.................................................................................
usage guidelines.....................................................
MLD usage guidelines..................................................
route (tracing flag)
MSDP................................................................................
routing tables
MSDP...............................................................................
PIM....................................................................................
RP
anycast..............................................................................
embedded......................................................................
rp (tracing flag)......................................................................
rp statement..........................................................................
rp-register-policy statement.............................................
usage guidelines.............................................................
rp-set statement..................................................................
usage guidelines....................................................
RPF calculations, displaying..............................................
PIM source state, displaying...................................
rpf-selection statement
PIM....................................................................................
RPs
displaying........................................................................
maximum........................................................................
RPT................................................................................................
S
shared trees...............................................................................
shortest-path trees................................................................
See also SPT
show igmp group command...........................................
show igmp interface command.....................................
show igmp statistics command.....................................
show igmp-snooping membership command.........
show igmp-snooping route command........................
show igmp-snooping statistics command.................
show igmp-snooping vlans command.........................
show msdp command.......................................................
show msdp source command........................................
show msdp source-active command..........................
show msdp statistics command...................................
show multicast flow-map command..........................
show multicast interface command............................
show multicast mrinfo command.................................
show multicast next-hops command.........................
show multicast pim-to-igmp-proxy command.........
show multicast pim-to-mld-proxy command..........
show multicast route command....................................
show multicast rpf command..........................................
show multicast scope command..................................
show multicast sessions command..............................
show multicast usage command..................................
show pim bootstrap command......................................
Copyright © 2016, Juniper Networks, Inc.
503
Multicast Protocols Feature Guide for EX4600 Switches show pim interfaces command......................................
show pim join command..................................................
show pim neighbors command.......................................
show pim rps command....................................................
show pim source command............................................
show pim statistics command........................................
show protocols igmp command....................................
show system statistics igmp command.....................
snooping
IGMP and VLANs..........................................................
source filtering........................................................................
source statement
IGMP.................................................................................
usage guidelines....................................................
MLD usage guidelines....................................................
MSDP...............................................................................
PIM RPF selection..............................................
,
SSM usage guidelines....................................................
source-active (tracing flag)..............................................
327 source-active-request (tracing flag).............................
327 source-active-response (tracing flag)..........................
source-address statement
IGMP snooping..............................................................
source-count statement
IGMP..................................................................................
usage guidelines....................................................
MLD usage guidelines....................................................
source-increment statement
IGMP.................................................................................
MLD
usage guidelines....................................................
usage guidelines....................................................
source-specific multicast See SSM
SPT..............................................................................................
configuring threshold cutover policy......................
cutover control...............................................................
spt-threshold statement...................................................
usage guidelines.............................................................
SSM......................................................................................
,
configuring.........................................................................
domains.............................................................................
43 mapping............................................................................
SSM maps.................................................................................
example.............................................................................
SSM maps for different groups to different sources...................................................................................
ssm-groups statement......................................................
usage guidelines............................................................
ssm-map statement
IGMP.................................................................................
MLD usage guidelines....................................................
usage guidelines....................................................
SSM...................................................................................
usage guidelines....................................................
ssm-map-policy statement
IGMP interface..............................................................
static statement
IGMP.................................................................................
usage guidelines....................................................
IGMP snooping...................................................
MLD
usage guidelines....................................................
PIM....................................................................................
usage guidelines....................................................
support, technical See technical support
syntax conventions................................................................
T technical support
contacting JTAC..............................................................
test msdp command..........................................................
threshold
PIM...........................................................................
threshold statement
MSDP...............................................................................
usage guidelines...................................................
traceoptions statement
IGMP................................................................................
usage guidelines....................................................
IGMP snooping.............................................................
MSDP................................................................................
usage guidelines..................................................
PIM....................................................................................
usage guidelines.....................................................
tracing flags
assert...............................................................................
bootstrap........................................................................
250 cache, PIM......................................................................
graft hello
PIM...........................................................................
PIM...........................................................................
join.....................................................................................
504 Copyright © 2016, Juniper Networks, Inc.
Index keepalive
MSDP.......................................................................
leave
IGMP........................................................................
mt......................................................................................
mtrace
IGMP..........................................................................
nsr-synchronization.....................................................
packets
IGMP.........................................................................
PIM.............................................................................
prune
PIM.............................................................................
251 register..............................................................................
report
IGMP.........................................................................
route
MSDP.......................................................................
rp.........................................................................................
source-active.................................................................
327 source-active-request................................................
source-active-response............................................
tracing IP multicast path from receiver to source...............................................
from router to gateway.............................................
from server to router..................................................
tracing operations
IGMP.........................................................................
,
MSDP.......................................................................
PIM....................................................................................
tracing routes from the receiver to the source...............................
from the source to the gateway router...............
from the source to the receiver..............................
monitoring......................................................................
transmit-interval
PIM....................................................................................
V version statement
BFD....................................................................................
IGMP.................................................................................
MLD usage guidelines..................................................
usage guidelines..................................................
PIM....................................................................................
usage guidelines..................................
,
vlan statement
IGMP snooping.............................................................
usage guidelines..................................................
VLANs
IGMP snooping..............................................................
W wildcard-source statement
PIM RPF selection.......................................................
Copyright © 2016, Juniper Networks, Inc.
505
Multicast Protocols Feature Guide for EX4600 Switches
506 Copyright © 2016, Juniper Networks, Inc.
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
advertisement