For e series broadband services routers (122 pages)
Summary of Contents for Juniper JUNOSE 11.0.X MULTICAST ROUTING
Page 1
JUNOSe Software for E Series Broadband Services Routers Multicast Routing Configuration Guide Release 11.0.x Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 408-745-2000 www.juniper.net Published: 2009-12-29...
Page 2
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Page 3
AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS. 1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use of the Software (“Customer”)
Page 4
(“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 http://www.gnu.org/licenses/gpl.html...
Page 5
agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein.
Page 7
Abbreviated Table of Contents About the Documentation Part 1 Internet Protocol Version 4 Chapter 1 Configuring IPv4 Multicast Chapter 2 Configuring IGMP Chapter 3 Configuring PIM for IPv4 Multicast Chapter 4 Configuring DVMRP Part 2 Internet Protocol Version 6 Chapter 5 Configuring IPv6 Multicast Chapter 6 Configuring Multicast Listener Discovery...
Table of Contents About the Documentation E Series and JUNOSe Documentation and Release Notes ......xix Audience ......................xix E Series and JUNOSe Text and Syntax Conventions ........xix Obtaining Documentation ................xxi Documentation Feedback ................xxi Requesting Technical Support ..............xxi Self-Help Online Tools and Resources ...........xxii Opening a Case with JTAC ..............xxii Part 1 Internet Protocol Version 4...
List of Tables About the Documentation Table 1: Notice Icons ..................xx Table 2: Text and Syntax Conventions ............xx Part 1 Internet Protocol Version 4 Chapter 1 Configuring IPv4 Multicast Table 3: Function of Multicast Protocols on a Router ........4 Table 4: Adaptive Mode Algorithm Values .............13 Chapter 2 Configuring IGMP Table 5: IGMP Commands ................47...
Page 18
JUNOSe 11.0.x Multicast Routing Configuration Guide xviii List of Tables...
If the information in the latest release notes differs from the information in the documentation, follow the JUNOSe 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/...
JUNOSe 11.0.x Multicast Routing Configuration Guide Table 1: Notice Icons Icon Meaning Description Informational note 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 Alerts you to the risk of personal injury from a laser.
{ permit | deny } { in | out } { clusterId | ipAddress } Obtaining Documentation To obtain the most current version of all Juniper Networks technical documentation, see the products documentation page on the Juniper Networks Web site at http://www.juniper.net/...
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/...
Part 1 Internet Protocol Version 4 Configuring IPv4 Multicast on page 3 Configuring IGMP on page 43 Configuring PIM for IPv4 Multicast on page 79 Configuring DVMRP on page 125 Internet Protocol Version 4...
Page 24
JUNOSe 11.0.x Multicast Routing Configuration Guide Internet Protocol Version 4...
Chapter 1 Configuring IPv4 Multicast IPv4 multicast enables a device to send packets to a group of hosts rather than to a list of individual hosts. This chapter describes how to configure IP multicast on the E Series router; it contains the following sections: IPv4 Multicast Overview on page 3 Platform Considerations on page 5 References on page 6...
JUNOSe 11.0.x Multicast Routing Configuration Guide A broadcast address enables a device to send a datagram to all hosts on a subnetwork. A multicast address enables a device to send a datagram to a specified set of hosts, known as a multicast group, in different subnetworks. Multicast IP packets contain a class D address in the Destination Address fields of their headers.
See ERX Module Guide, Table 1, Module Combinations for detailed module specifications. See ERX Module Guide, Appendix A, Module Protocol Support for information about the modules that support IP multicasting. For information about modules that support IP multicasting on the Juniper Networks E120 and E320 Broadband Services Routers: Platform Considerations...
IPv6 Multicast” on page 147. Configuring the Switch Fabric Bandwidth By default, the switch fabric for the Juniper Networks ERX1440, ERX310, E120, and E320 Broadband Services Routers uses a bandwidth weighting ratio of 15:2 for multicast-to-unicast weighted round robin (WRR). In the absence of strict-priority...
Chapter 1: Configuring IPv4 Multicast Enabling IP Multicast In this implementation, IP multicast works on virtual routers (VRs). By default, IP multicast is disabled on a VR. To enable IP multicast on a VR, access the context for a VR, and then issue the ip multicast-routing command. ip multicast-routing Use to enable IP multicast routing on the VR.
Page 30
JUNOSe 11.0.x Multicast Routing Configuration Guide show ip rpf-route Use to display routes that the router can use for RPF. Specify the IP address and the network mask to view routes to a particular destination. Specify a unicast routing protocol to view routes associated with that protocol. Field descriptions Prefix Value of the logical AND of the IP address of the destination network and the subnet address...
Chapter 1: Configuring IPv4 Multicast Prefix/Length Type Next Hop Dist/Met Intf ------------- ---- -------- -------- -------------- 10.10.0.112/32 Static 192.168.1.1 fastEthernet0/0 See show ip rpf-route. Enabling and Disabling RPF Checks By default, the router accepts multicast packets for each Source, Group (S,G) pair on an incoming interface (IIF), which satisfies the RPF check (RPF-IIF).
JUNOSe 11.0.x Multicast Routing Configuration Guide Example host1(config)#router ospf host1(config-router)#ip route-type multicast There is no no version. See ip route-type. Defining Permanent IP Multicast Forwarding Entries An mroute is a multicast traffic flow (a (Source, Group) entry used for forwarding multicast traffic).
Chapter 1: Configuring IPv4 Multicast NOTE: Even though you can include any of the preceding commands several times in a route map entry, only the last admission-bandwidth command or qos-bandwidth command in the bandwidth map is used. In other words, if you included the set qos-bandwidth command first and then the set qos-bandwidth adaptive command, the bandwidth map uses the set qos-bandwidth adaptive command.
JUNOSe 11.0.x Multicast Routing Configuration Guide host1(config-route-map)#set admission-bandwidth adaptive host1(config-route-map)#set qos-bandwidth adaptive host1(config-route-map)#end In this example, any stream with an (S,G) that matches the sdtv access list performs adaptive bandwidth detection for admission control and QoS adjustment. A rate measurement mechanism runs on the ingress line card that polls the forwarding controller (FC) to obtain statistics for each mroute.
Chapter 1: Configuring IPv4 Multicast period T to yield the average rate. This process is repeated every sampling interval, , to yield rates R1, R2, R3, and so on. The first two sampling interval calculations are as follows: = (N = (N The router maintains a history of bandwidth measurements (H) for each mroute, up to a maximum of M measurements.
Page 36
JUNOSe 11.0.x Multicast Routing Configuration Guide Define a route-map using the set admission-bandwidth and set qos-bandwidth commands. You can optionally issue the set priority command. host1(config)#route-map mcast-bandwidths permit 10 host1(config-route-map)#match ip address sdtv host1(config-route-map)#set admission-bandwidth 2000000 host1(config-route-map)#set qos-bandwidth 2000000 host1(config-route-map)#set priority 100 host1(config-route-map)#route-map mcast-bandwidths permit 20 host1(config-route-map)#match ip address hdtv host1(config-route-map)#set admission-bandwidth 10000000...
Chapter 1: Configuring IPv4 Multicast Use to configure a priority value for the <S, G> data stream on a physical port. Dynamic multicast admission control enables only prioritized groups to join the interface after the configured priority limit is reached on the physical port. The system records the priority when a new <S, G>...
JUNOSe 11.0.x Multicast Routing Configuration Guide forwarding. This special interface can be on a different physical port or line module from that of the join interface. Using this mapping function, the router can send a single copy of each multicast stream over the special interface and the access nodes are configured to perform any final replication to the subscribers and merge unicast and multicast data flows onto the subscriber interfaces as necessary.
Chapter 1: Configuring IPv4 Multicast NOTE: Ensure that PIM-SM (or any other upstream multicast protocol) is informed of the group (or source-group) interest. Figure 3: Multicast Traffic Receipt Without Forwarding Activating Multicast QoS Adjustment Functions The ip multicast-routing bandwidth-map command activates the specified bandwidth map.
JUNOSe 11.0.x Multicast Routing Configuration Guide Configuring Hardware Multicast Packet Replication You can configure IPv4 multicast to replicate packets to optimized hardware on a logical port instead of using the forwarding controller (FC) on the router. The bandwidth between the line module and the I/O module or IOA on the E Series router is limited.
Chapter 1: Configuring IPv4 Multicast one copy of the packet is transmitted from the line module to the I/O module or IOA. Replication for each of the ports is performed on the I/O module or IOA. Configuring hardware multicast packet replication for high-density Ethernet is useful when you want to provide the same multicast stream out of some or all of the ports, such as for IP television (IPTV).
JUNOSe 11.0.x Multicast Routing Configuration Guide Each high-density Ethernet module has eight physical ports, numbered 0–7. A logical port is available for the hardware multicast packet replication feature, numbered port 8. JUNOSe tracks the OIFs in an mroute that have been redirected to use the hardware multicast packet replication hardware.
Chapter 1: Configuring IPv4 Multicast Egress IP policy Egress VLAN policy Relationship with OIF Mapping Multicast OIF mapping enables the router to decrease the inefficiencies associated with replicating streams of multicast traffic. Using OIF maps, IGMP joins that the router receives on a subscriber interface can be mapped to a dedicated multicast VLAN.
Page 44
JUNOSe 11.0.x Multicast Routing Configuration Guide When you configure a unique source MAC address for VLANs on port 8, the hardware multicast packet replication hardware stamps the source MAC address on the VLAN, overwriting any MAC address that you configured. For more information, see Configuring Ethernet Interfaces in the JUNOSe Physical Layer Configuration Guide.
Chapter 1: Configuring IPv4 Multicast Configuring Hardware Multicast Packet Replication To configure hardware multicast packet replication: Configure port 8 on a high-density Ethernet module to accept redirected egress multicast traffic. a. Specify the Gigabit Ethernet interface on port 8. b. Create a VLAN major interface. Create a VLAN subinterface.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to set the IGMP version (1, 2, or 3) for the interface or specify a passive interface with only multicast-data-forwarding capability (passive). Example host1:boston(config-if)#ip igmp version passive Use the no version to set the version to the default, IGMPv2. See ip igmp version.
Chapter 1: Configuring IPv4 Multicast IP and VLAN Statistics Use the show vlan subinterface command to display statistics for a VLAN interface configured over port 8. For more information, see Monitoring Ethernet Interfaces in the JUNOSe Physical Layer Configuration Guide. Use the show ip interface command to display statistics for an IP interface configured over port 8.
JUNOSe 11.0.x Multicast Routing Configuration Guide host1(config-if)#ip block-multicast-sources Use the no version to restore the default behavior of creating mroutes on received multicast packets. See ip block-multicast-sources. Limiting Interface Admission Bandwidth Interface-level multicast admission control is performed when an OIF on the interface is added to the mroute for a given (S,G) multicast data stream and the multicast bandwidth map contains a set admission-bandwidth action for that (S,G).
Chapter 1: Configuring IPv4 Multicast If the bandwidth limit is decreased, no currently admitted OIFs are blocked. However, no new OIFs are admitted until the total admitted bandwidth for the interface drops below the new limit. If the bandwidth is increased to the point that the bandwidth limit for an interface is now exceeded, no currently admitted OIFs for the affected mroutes are blocked.
JUNOSe 11.0.x Multicast Routing Configuration Guide When enabled, the admission-bandwidth for a particular (S,G) is read from the multicast bandwidth map and recorded in the mroute when the (S,G) mroute is created. If you configure a port limit and the OIF count on the port exceeds that limit, no OIFs on that port are added to mroutes (that is, OIFs are blocked).
Chapter 1: Configuring IPv4 Multicast Use to configure a limit on the total multicast bandwidth that can be admitted on a port. Use the priority-bandwidth-limit keyword to configure the priority bandwidth admitted on a port. Use the hysteresis keyword to configure the minimum priority bandwidth limit before the system evaluates mroutes and admits any blocked OIFs.
JUNOSe 11.0.x Multicast Routing Configuration Guide Deleting Multicast Forwarding Entries You can clear one or more forwarding entries from the multicast routing table. However, if you do so, the entries might reappear in the routing table if they are rediscovered. clear ip mroute Use to delete IPv4 multicast forwarding entries.
Page 53
Chapter 1: Configuring IPv4 Multicast QoS bandwidth QoS bandwidth per mroute, in bps Uptime Length of time that the (S,G) pair has been active, in days hours:minutes:seconds format Data Rate Flow rate for the threshold entry, in Kbps SPT Threshold SPT threshold value for the entry, in Kbps Threshold Threshold value for the entry, in Kpbs Expires Length of time that the (S,G) pair can be active, in days hours:minutes:seconds format or never...
Page 57
Chapter 1: Configuring IPv4 Multicast Received Number of packets and bytes that the VR received for this multicast route Forwarded Number of packets and bytes that the VR has forwarded for this multicast route Rcvd on OIF Number of packets that the VR has received on the outgoing interface (OIF) for this multicast route Example host1#show ip mroute statistics...
Page 58
JUNOSe 11.0.x Multicast Routing Configuration Guide RPF Iif Type and identifier for the incoming interface for the RPF route #Oifs Number of outgoing interfaces Counts Numbers of types of (S,G) pairs (S,G) Number of (S,G) entries (*,G) Number of (*,G) entries Example host1#show ip mroute summary IP Multicast Routing Table...
Page 59
Chapter 1: Configuring IPv4 Multicast Types and specifiers of interfaces. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide. Protocols configured on the interface and the protocol that owns the interface. If you configure only IGMP on an interface, IGMP owns the interface.
Page 60
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to display a summary of information about multicast protocols enabled on the router. Field descriptions Protocol Name of the multicast protocol Registered Interfaces Number of interfaces on which the protocol is configured Owned Interfaces Number of interfaces that a protocol owns. If you configure only IGMP on an interface, IGMP owns the interface.
Chapter 1: Configuring IPv4 Multicast Use to display the mroute port outgoing interface, limits, counts, bandwidth settings, and bandwidth accepted. NOTE: This command displays information for mroutes on a port across all virtual routers. Field descriptions Port Slot/port value on the router Limit Port limit value defined for the specified port;...
JUNOSe 11.0.x Multicast Routing Configuration Guide If PIM is configured on the interface, the virtual router supplies a list of the interface's PIM neighbors and indicates which neighbors are leaf neighbors. Information about DVMRP and GRE tunnels: If the interface is an endpoint of a tunnel, the virtual router specifies the IP address of the endpoint of the tunnel.
Page 63
Chapter 1: Configuring IPv4 Multicast a.a.a.a IP address of the source b.b.b.b IP address of the destination c.c.c.c IP address of the multicast group d.d.d.d IP address of the router to which the router sends the trace Received mtrace response packet of length n Length of the response packet, in bytes Each line of the trace has the following format: hops.
Chapter 2 Configuring IGMP IP hosts use Internet Group Management Protocol (IGMP) in IPv4 to report their multicast group memberships to neighboring routers. Similarly, multicast routers, such as an E Series router, use IGMP to discover which of their hosts belong to multicast groups.
JUNOSe 11.0.x Multicast Routing Configuration Guide IGMP Overview The IPv4 address scheme assigns class D addresses for IP multicast. IGMP is the protocol that uses these addresses, which can be in the range 224.0.0.0 to 239.255.255.255. The following addresses have specific functions or are unavailable: 224.0.0.0 is reserved you cannot assign it to a group.
Chapter 2: Configuring IGMP The purpose of a group membership query is to discover the multicast groups to which a host belongs. IGMPv2 and IGMPv3 group membership queries have a Max Response Time field. This response time is the maximum amount of time that a host can take to reply to a query.
JUNOSe 11.0.x Multicast Routing Configuration Guide References For more information about IGMP, see the following resources: IGMP-based Multicast Forwarding (“ IGMP Proxying” ) draft-ietf-magma-igmp-proxy-00.txt (May 2002 expiration) RFC 2236 Internet Group Management Protocol, Version 2 (November 1997) RFC 2933 Internet Group Management Protocol MIB (October 2000) RFC 3292 General Switch Management Protocol (GSMP) V3 (June 2002) RFC 3376 Internet Group Management Protocol (October 2002) GSMP extensions for layer2 control (L2C) Topology Discovery and Line...
Chapter 2: Configuring IGMP Figure 6: Static and Dynamic IGMP Interfaces You configure static IGMP interfaces by using software such as the CLI or an SNMP application; you configure dynamic IGMP interfaces by using a profile. A profile constitutes a set of attributes for an interface; a profile for dynamic IGMP interfaces contains attributes for configuring all the layers in the interface.
JUNOSe 11.0.x Multicast Routing Configuration Guide Table 5: IGMP Commands (continued) ip igmp last-member-query-interval ip igmp static-include ip igmp promiscuous ip igmp version ip igmp querier multicast group port limit ip igmp querier-timeout The following sections describe the tasks associated with these and other ip igmp commands.
Chapter 2: Configuring IGMP Use the no version to disable IGMP on an interface. See ip igmp. ip igmp querier Use to specify that this IGMPv1 interface acts as a querier. NOTE: This command is valid only for interfaces on which you configured IGMPv1. By default, IGMPv1 interfaces act as queriers.
Page 72
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to specify that, when the router receives a leave group membership message from a host associated with this interface, the router immediately removes that host from the multicast group. CAUTION: Issue this command only on IGMPv2 and IGMPv3 interfaces to which one IGMP host is connected.
Page 73
Chapter 2: Configuring IGMP Use the no version to set the time to the default, twice the query interval. See ip igmp querier-timeout. ip igmp query-interval Use to specify how often, in the range 1–300 seconds, the interface sends group membership queries.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to restore the default, 3. See ip igmp robustness. Specifying Multicast Groups You can use a standard-format or extended-format IP access list to specify the multicast groups that a host can join. ip igmp access-group Use to restrict hosts on this subnetwork to join only multicast groups that appear on the specified IP access list.
Chapter 2: Configuring IGMP Example host1:boston(config-if)#ip igmp access-source-group dallas-list Use the no version to remove any access list restriction. See ip igmp access-source-group. Assigning a Multicast Group to an Interface You can assign an interface to send and receive all traffic for a particular multicast group.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to remove the outgoing interface map association from the interface. See ip igmp apply-oif-map. ip igmp oif-map Use to create an OIF map. Example host1(config)#ip igmp oif-map OIFMAP atm 3/0.1 232.0.0.1/32 51.0.0.1/32 host1(config)#ip igmp oif-map OIFMAP atm 3/0.2 232.0.0.1/32 51.0.0.2/32 host1(config)#ip igmp oif-map OIFMAP atm 3/0.3 233.0.0.1/32 host1(config)#ip igmp oif-map OIFMAP atm 3/0.4 233.0.0.0/24 51.0.0.1/32...
Page 77
Chapter 2: Configuring IGMP IGMPv2 membership reports to an IGMPv3 report, enabling the router to continue as if it had initially received an IGMPv3 report. After the router is joined to these groups, it sends out PIM join messages and continues to enable joining from these groups, as long as it continues to receive IGMPv1 and IGMPv2 membership reports and no change occurs to the SSM mapping for the group.
JUNOSe 11.0.x Multicast Routing Configuration Guide Limiting the Number of Accepted IGMP Groups By default, there is no limit on the number of IGMP groups that an IGMP interface can accept. However, you can manage multicast traffic on the router by restricting the number of IGMP groups accepted by: A specific port on an I/O module A specific IGMP interface...
Chapter 2: Configuring IGMP Use to limit the number of IGMP groups that a port can accept. NOTE: This command is deprecated and might be removed completely in a future release. The function provided by this command has been replaced by the updated by limiting bandwidth of multicast streams using the mroute port admission-bandwidth-limit command.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to remove the static designation. See ip igmp static-exclude. ip igmp static-include Use to statically include the IGMP (S,G) membership for a host that is not capable of dynamically signaling group membership. Example host1:boston(config-if)#ip igmp static-include 10.1.1.1 225.1.2.3 Use the no version to remove the static designation.
Page 81
Chapter 2: Configuring IGMP If the host sending the leave message is not the only host receiving traffic for that group or channel, the router removes the host from the list of hosts on that interface, but keeps the interface in the outgoing interface list for the multicast group or channel.
JUNOSe 11.0.x Multicast Routing Configuration Guide host1(config)#ip igmp explicit-tracking Use the no version to disable explicit host tracking on the interface. Use the no version with the disable-if-igmp-v2-detected keyword to revert to the default explicit host tracking behavior. See ip igmp explicit-tracking. Accepting IGMP Reports from Remote Subnetworks By default, IGMP interfaces accept IGMP reports only from associated subnetworks.
Chapter 2: Configuring IGMP Use the off keyword to enable the interface to accept IGMP reports only from hosts on subnetworks associated with this interface. Example host1:boston(config-if)#ip igmp promiscuous on Use the no version to configure an IGMP interface to use the Router Configuration mode setting to determine the subnetworks from which it can accept IGMP reports.
Page 84
JUNOSe 11.0.x Multicast Routing Configuration Guide NOTE: The E120 and E320 routers output for monitor and show commands is identical to output from other E Series routers, except that the E120 and E320 routers output also includes information about the adapter identifier in the interface specifier (slot/adapter/port).
Page 85
Chapter 2: Configuring IGMP Total number of group membership queries sent Example host1:boston#show ip igmp Routing Process IGMP, Administrative state enabled, Operational state enabled 2 total interfaces, 2 enabled, 0 disabled 0 enabled interfaces performing graceful restart 2 learnt groups IGMP Statistics: Rvcd: 1 total, 0 checksum errors, 0 unknown types 0 queries, 1 reports, 0 leaves...
Page 87
Chapter 2: Configuring IGMP Operational state Physical status of the interface: enabled or disabled Version IGMP version State Function of the interface: querier or nonquerier Query Interval Time interval in seconds at which this interface sends query messages Other querier present interval Time in seconds that the interface waits before declaring itself as the querier Maximum response time Time interval, in tenths of a second, during which this interface waits for a host to respond...
Page 88
JUNOSe 11.0.x Multicast Routing Configuration Guide Group Count Number of IGMP groups that the interface has accepted IOA packet replication Hardware multicast packet replication interface to which egress multicast packets on this interface are redirected Interface statistics Rcvd Information about IGMP messages received on this interface reports Number of group membership reports received leaves Number of group leave messages received...
Page 89
Chapter 2: Configuring IGMP Counts: 0 down, 0 init state, 1 querier, 0 non-querier, 1 Total Counts: 0 down, 0 init state, 1 querier, 0 non-querier, 1 Total Example 2 host1#show ip igmp interface gigabitEthernet 3/0.0 Interface GigabitEthernet3/0.0 address 10.1.1.1/255.255.255.0 Administrative state enabled, Operational state disabled Interface parameters: Version 2...
Page 90
JUNOSe 11.0.x Multicast Routing Configuration Guide QPTime Time in seconds that the interface waits before declaring itself as the querier Count Total number of IGMP interfaces Example host1:boston# show ip igmp interface brief Interface Intf Address State Querier QTime QPTime -------------- ---------- ------...
Page 91
Chapter 2: Configuring IGMP Use to display IGMP membership information for multicast groups and (S, G) channels. Specify the tracked keyword to see interface information only for interfaces where explicit host tracking is enabled. Field descriptions Group Multicast group or (S, G) channel Source (S, G) entries that are forwarding traffic Reporter Hosts that requested including sources or have not requested excluding sources.
Page 92
JUNOSe 11.0.x Multicast Routing Configuration Guide 224.0.1.70 30.20.0.1 stop FastEthernet2/4 40.30.0.100 01:10 40.30.0.101 01.24 239.0.1.80 stop FastEthernet2/5 50.30.0.100 10.10.0.10 02:48 50.30.0.101 10.10.0.20 02:56 10.10.0.10 02:48 50.30.0.102 10.10.0.20 02:56 235.0.1.90 02:56 FastEthernet2/6 12.10.0.10 02:48 12.10.0.20 02:56 12.10.0.30 02:48 See show ip igmp membership. show ip igmp oif-map Use to display all outgoing interface (OIF) maps or the OIF map for the specified map name.
Page 93
Chapter 2: Configuring IGMP OIF-MAP Name Name of the map requested Group Address Multicast group IP address requested Source Address Source IP address requested Mapped OIF Interface associated with the OIF map Example host1#show ip igmp oif-mapping OIFMAP 232.1.1.1 10.1.1.10 OIF Mapping OIF-MAP Name : OIFMAP...
JUNOSe 11.0.x Multicast Routing Configuration Guide port Port number on the I/O module limit Maximum number of IGMP groups that the port can accept. A value of –1 indicates that no limit has been specified. count Actual number of IGMP groups that the port has accepted Example host1:boston#show multicast group limit Port...
Chapter 2: Configuring IGMP through the exchange of IGMP messages. However, when acting as the proxy, the router performs the host portion of the IGMP task on the upstream interface, as follows: When queried, sends group membership reports to the group. When one of its hosts joins a multicast address group to which none of its other hosts belong, sends unsolicited group membership reports to that group.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to specify the interval, in tenths of a second, at which the upstream interface transmits unsolicited reports. NOTE: Issue this command only on the upstream interface. Otherwise, this command has no effect. Example host1(config-if)#ip igmp-proxy unsolicited-report-interval 600 Use the no version to transmit unsolicited reports using the default value, 400 tenths of a second.
Chapter 2: Configuring IGMP (host1)#baseline ip igmp-proxy interface There is no no version. See baseline ip igmp-proxy interface. Monitoring IGMP Proxy To display IGMP proxy parameters, use the following show commands. show ip igmp-proxy Use to display IGMP proxy parameters for a VR. Field descriptions Routing Process IGMP proxy protocol Administrative state State of IGMP proxy in the software: enabled or...
Page 98
JUNOSe 11.0.x Multicast Routing Configuration Guide Delay Interface has responded to the latest group membership query for this group count Total number of multicast groups associated with this interface Example 1 host1#show ip igmp-proxy groups Grp Address Interface Member State --------------- --------------- -------------- 225.1.1.1 atm3/0.2...
Page 99
Chapter 2: Configuring IGMP State Presence of IGMPv1 routers on the same subnet as this upstream interface Unsolicited report interval Time interval, in tenths of a second, at which this upstream interface sends an unsolicited group membership report Version 1 router present timeout How long, in seconds, that the upstream interface calculates an IGMPv1 router to exist on the subnet after that interface receives an IGMPv1 group membership query multicast group Number of multicast groups associated with this upstream...
Chapter 3 Configuring PIM for IPv4 Multicast The Protocol Independent Multicast (PIM) protocol is a collection of multicast routing protocols that enables multicast routers to identify other multicast routers to receive packets. This chapter describes how to configure PIM for IPv4 on E Series routers; it contains the following sections: Overview on page 80 Platform Considerations on page 86...
JUNOSe 11.0.x Multicast Routing Configuration Guide Overview The IPv4 implementation of PIM supports PIM dense mode, PIM sparse mode, PIM sparse-dense mode, and PIM source-specific multicast (PIM SSM). Figure 8 on page 80 represents how PIM builds a source, group (S,G) entry in a source-rooted tree (SRT).
Chapter 3: Configuring PIM for IPv4 Multicast Figure 9 on page 81 illustrates how PIM dense mode works. When a source sends a multicast packet to a first-hop router, the first-hop router multicasts that packet to its neighbors. Those neighbors in turn forward the packet to their neighbors and their hosts that belong to the multicast group.
JUNOSe 11.0.x Multicast Routing Configuration Guide Figure 10: Detecting Duplication The upstream routers responsible for the duplication send assert messages to determine which router becomes the forwarder. Downstream routers listen to the assert messages to discover which router becomes the forwarder. PIM Sparse Mode This implementation of PIM sparse mode supports the following features: Rendezvous point (RP) routers...
Chapter 3: Configuring PIM for IPv4 Multicast Figure 11: PIM Sparse Mode Operation In PIM sparse mode, an RP announces a source and establishes paths from the source to members of a multicast group before multicasting any datagrams. RPs transmit join messages to become part of the shared tree that enables distribution of packets to the multicast group.
JUNOSe 11.0.x Multicast Routing Configuration Guide When all designated routers associated with a specific RP router have switched to the SPT, the RP router sends a join/prune message toward the multicast source. When the multicast source receives this message, it stops sending multicast data through the SPT.
Chapter 3: Configuring PIM for IPv4 Multicast NOTE: A PIM router can receive group-to-RP mappings from either BSR or auto-RP, but not from both. Because BSR and auto-RP use different mapping algorithms, the mechanisms cannot coexist. NOTE: Static-override is configured using the override switch in the ip pim rp-address command.
JUNOSe 11.0.x Multicast Routing Configuration Guide Simplified administrative deployment; you need only configure PIM sparse mode on all router interfaces and issue the necessary SSM commands (including specifying IGMPv3 on the receiver local area network). Support for source lists; you can use source lists, supported in IGMPv3, where only specified sources send traffic to the SSM group.
Chapter 3: Configuring PIM for IPv4 Multicast NOTE: IETF drafts are valid for only 6 months from the date of issuance. They must be considered as works in progress. Please refer to the IETF Web site at http://www.ietf.org for the latest drafts. Before You Begin You can configure PIM on IPv4 and IPv6 interfaces.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to reenable PIM processing. See pim disable. Enabling PIM on an Interface You can enable PIM on an interface in one of the PIM modes (dense, sparse, or sparse-dense) and specify how often the interface sends hello messages to neighbors. You can configure PIM and IGMP on the same interface.
Chapter 3: Configuring PIM for IPv4 Multicast Setting a Priority to Determine the Designated Router You can influence whether a particular router is selected as the designated router with the ip pim dr-priority command. A higher priority value increases the likelihood that a router is selected as the designated router, while a lower value decreases the likelihood.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to set an interval value, in the range 10–210 seconds, at which the router sends the PIM join/prune message; the default value is 60 seconds. Examples In Router Configuration mode: host1(config-if)#ip pim join-prune-interval 150 In Interface Configuration mode: host1(config-subif)#ip pim join-prune-interval 150 Use the no version to restore the default value, 60 seconds.
Chapter 3: Configuring PIM for IPv4 Multicast host1(config)#access-list 11 permit 224.0.1.39 0.0.0.0 host1(config)#access-list 11 permit 224.0.1.40 0.0.0.0 host1(config)#ip pim rp-address 192.48.1.22 11 override Assign an RP mapping agent. host1(config)#ip pim send-rp-discovery scope 23 loopback 1 Configure routers to send auto-RP announcement messages to the mapping agent.
Page 114
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to clear the filter from this interface. See ip pim rp-address. ip pim send-rp-announce Use to send auto-RP announcement messages from a router you configured as an RP. Specify an interface type and specifier, such as atm 3/0. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Chapter 3: Configuring PIM for IPv4 Multicast Configuring BSR and RP Candidates for PIM Sparse Mode When choosing candidate BSRs, select well-connected routers in the core of the network. Typically, candidate BSRs are a subset of the candidate RPs. A single BSR is elected for the domain of candidate BSRs.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the hold-time keyword to specify the amount of time the BSR keeps an RP in its C-RP list if the BSR does not receive a C-RP advertisement message. The default value is 150 seconds. Use the priority keyword to specify a priority field value that the C-RP sends to the BSR in C-RP advertisement messages.
Chapter 3: Configuring PIM for IPv4 Multicast Specify a value of 0 (default) to configure PIM to switch to an SPT when a source starts sending multicast messages. Example host1(config)#ip pim spt-threshold 4 Use the no version to restore the default value, 0. See ip pim spt-threshold.
(Lp). CAUTION: Defining the Tv interface with an address other than the loopback interface of the parent router might restrict operation with non-Juniper Networks routers. Tp is an unnumbered IP interface that is tied to the loopback interface of the provider edge router (PE).
Page 119
Chapter 3: Configuring PIM for IPv4 Multicast host1:PE2(config-router-af)#neighbor 3.3.3.3 next-hop-self host1:PE2(config-router-af)#exit-address-family See Configuring BGP-MPLS Applications in the JUNOSe BGP and MPLS Configuration Guide for details. Configure PIM sparse mode in the core and RP for MVPN group addresses. NOTE: For MVPN, it is a typical practice to use shared trees. host1:PE1(config-router)#virtual-router PE2 host1:PE2(config)#ip multicast-routing host1:PE2(config)#...
Page 120
JUNOSe 11.0.x Multicast Routing Configuration Guide host1(config-if)#exit host1(config)# Configure the GRE tunnel for VPN2 host1(config)#interface tunnel gre:MTI-22 transport-virtual-router PE2 thost1(config-if)#tunnel source 2.2.2.2 host1(config-if)#tunnel destination 235.1.1.2 host1(config-if)#tunnel mdt host1(config-if)#exit host1(config)# Configure the IP interface (Tv) in PE2:CE1 as a PIM sparse-mode interface with the address of the loopback interface.
Chapter 3: Configuring PIM for IPv4 Multicast host1(config-if)#tunnel mdt The no version disables MDT on the interface. See tunnel mdt. Creating Multicast VPNs Using the Data MDT A data multicast distribution tree (MDT), based on section 8 of Internet draft draft-rosen-vpn-mcast-08.txt, Multicast in MPLS/BGP IP VPNs, solves the problem of P routers flooding unnecessary multicast information to PE routers that have no interested receivers for a particular VPN multicast group.
JUNOSe 11.0.x Multicast Routing Configuration Guide Data MDT Receivers When the Receiver C-PIM-SM receives a <C-SG, P-G> MDT Join TLV message from the default MDT, it extracts the C-SG and the data MDT P-Group address from the TLV and queries the route map that you specified for the data MDT to determine whether the C-SG is a candidate for a data MDT.
Chapter 3: Configuring PIM for IPv4 Multicast Configuring the Default MDT To configure the default MDT: On the parent virtual-router, configure an IP interface over the MDT interface, and make it a PIM interface. host1(config)#virtual-router pe1 host1:pe1(config)#ip multicast-routing host1:pe1(config)#interface loopback 0 host1:pe1(config-if)#ip address 1.1.1.1 255.255.255.255 host1:pe1(config-if)#ip pim sparse-mode host1:pe1(config-if)#exit...
JUNOSe 11.0.x Multicast Routing Configuration Guide NOTE: You can use the ip unnumbered loopback 0 command to configure the MTI interface on the VRF as an unnumbered interface, or the ip address 1.1.1.1 255.255.255.255 command to configure it as a numbered interface. Specify the GRE tunnel configuration for the parent virtual router.
Page 125
Chapter 3: Configuring PIM for IPv4 Multicast host1(config-profile)#exit Configure a dynamic interface profile to specify the IP interface or MDT interface in the parent. host1(config-profile)#profile pe1DataMdtMdt host1(config-profile)#ip virtual-router pe1 host1(config-profile)#ip unnumbered loopback 0 host1(config-profile)#ip pim sparse-mode host1(config-profile)#exit Configure the destination profile for dynamic IP tunnel creation. host1(config)#gre destination profile pe13DataMdtProfile virtual-router pe1 host1(config-dest-profile)#tunnel source 1.1.1.1 host1(config-dest-profile)#tunnel destination ip subnet 233.3.0.0/16...
Page 126
JUNOSe 11.0.x Multicast Routing Configuration Guide host1:pe1:pe13(config)#access-list pe13DataMdtSend permit ip host 10.13.0.100 225.1.1.0 0.0.0.255 host1:pe1:pe13(config)#access-list pe13DataMdt permit ip any 225.1.0.0 0.0.255.255 Specify a route map to configure the set of <S, G> for which data MDTs can be created, and the threshold to be applied for each SG. host1:pe1:pe13(config)#route-map pe13MdtThresholds permit 10 host1:pe1:pe13(config-route-map)#match ip address pe13DataMdtSend host1:pe1:pe13(config-route-map)#set threshold 0...
Page 127
Chapter 3: Configuring PIM for IPv4 Multicast Use the no version to return to the default. See mdt-data-delay. mdt-data-holddown Use to configure the time in seconds before switching to the default MDT group from the data MDT group. The default is 60. Example host1(ip-pim-data-mdt-config)#mdt-data-holddown 200 Use the no version to return to the default.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to configure a group address pool for a data MDT tunnel. Example host1(ip-pim-data-mdt-config)#tunnel group-address-pool dataMDT1 Use the no version to delete the group address pool. See tunnel group-address-pool. Using PIM Sparse Mode Join Filters You can use PIM sparse mode join filters to prevent multicast state from being created in the PIM sparse mode router.
Page 129
Chapter 3: Configuring PIM for IPv4 Multicast To use PIM SSM, IGMPv3 must be configured on customer premise equipment (CPE)–facing interfaces to receivers, and PIM sparse mode must be configured on CPE-facing interfaces to sources and on core-facing interfaces. After configuring SSM, you can use the show ip pim sparse-mode sg-state command to display SSM group membership information.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to disable SSM. See ip pim ssm. Configuring the BFD Protocol for PIM The ip pim bfd-liveness-detection command configures the Bidirectional Forwarding Detection (BFD) protocol for PIM. The BFD protocol uses control packets and shorter detection time limits to more rapidly detect failures in a network.
Chapter 3: Configuring PIM for IPv4 Multicast You can use the minimum-receive-interval keyword to specify the minimum interval at which the local router must receive BFD control packets from its neighbors. The default value is 300 milliseconds. You can use the minimum-interval keyword to specify the same value for both of those intervals.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to clear the group-to-RP router mappings that the router learned through auto-RP. Specify the IP address of an RP to clear the group-to-RP mappings for a particular RP. If you do not specify an IP address, the router clears the group-to-RP mappings on all RP routers learned through auto-RP.
Chapter 3: Configuring PIM for IPv4 Multicast Monitoring PIM Events You can use the debug PIM commands to view information about PIM events. debug ip pim Use to show information about the selected event. To control the type of events displayed, specify a severity level. To control how much information to display, specify a verbosity level.
Page 134
JUNOSe 11.0.x Multicast Routing Configuration Guide Join-Prune Holdtime Hold time value (in seconds) set in the join/prune messages originated by the PIM router. The hold time is 3.5 times the PIM join/prune message interval value. Keepalive Period Time SG join state is maintained in the absence of SG Join message Assert Time Period after last assert before assert state is timed out Register Suppression Time Period during which a designated router stops...
Page 135
Chapter 3: Configuring PIM for IPv4 Multicast Configured with ttl Number of hops for which the RP discovery message is valid Using interface addr IP address of the interface from which the router sends RP discovery messages interval Time interval, in seconds, at which the router sends RP discovery messages PIM AutoRP candidate RP mapping(s) Routers that the RP mapping agent is evaluating to determine an RP router for this interface...
Page 136
JUNOSe 11.0.x Multicast Routing Configuration Guide expires in If BSR is not this router, time until the elected BSR expires if no bootstrap messages are received Local candidate RP mapping(s) Routers that the mapping agent is evaluating to determine an RP router for this interface Example 1 On a router that is the elected BSR host1:1#show ip pim bsr This PIM router is a Candidate BSR.
Page 137
Chapter 3: Configuring PIM for IPv4 Multicast PE Name Name of the PE C-SG Address of the C-SG P-SG Address of the P-SG MTI Name of the dynamic IP tunnel on which the data MDT was created Data rate/Threshold Rate and threshold of multicast data Time until next MDT Join TLV Configured delay until next MDT Join TLV Time until MDT Join TLV expires Configured delay until MDT Join TLV expires...
Page 138
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to display information for each (Source, Group) pair for PIM dense mode. Field descriptions (Source, Group) pair IP addresses of multicast source and group EntryExpires Time until the (S,G) pair entry expires RPF Route Reverse-path forwarding route IIF IP address of incoming interface UpNbr IP address of upstream neighbor Pruned Oifs Outgoing interfaces that have been pruned...
Page 139
Chapter 3: Configuring PIM for IPv4 Multicast Specify the summary keyword to view the number of configured, enabled, and disabled PIM dense mode, PIM sparse mode, and PIM sparse-dense mode interfaces. Specify the count keyword to view the number of multicast packets that the interface has sent and received.
Page 140
JUNOSe 11.0.x Multicast Routing Configuration Guide Example 2 host1#show ip pim interface summary PIM Interface Summary 0, 0 enabled, 0 disabled 0, 0 enabled, 0 disabled SM/DM: 1, 0 enabled, 1 disabled Example 3 host1#show ip pim interface count PIM Interface Count Interface Addr Interface Name ControlPktCount In|Out...
Page 141
Chapter 3: Configuring PIM for IPv4 Multicast 1.1.1.1 FastEthernet1/1 00:03:16 00:01:30 Sparse Neighbor Addr Interface Name Uptime Expires Mode -------- --------------- -------- -------- ------ ---- 1.1.1.1 FastEthernet1/1 00:00:07 00:01:39 Sparse down See show ip pim neighbor. show ip pim rp Use to display information about PIM group-to-RP mappings.
Page 142
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to show which RP router that a multicast group is using. Field descriptions Group(s) Multicast group or groups RP RP router for the multicast group priority Priority of the router via Method by which the RP router was assigned: AutoRP, Static RP, or expiryTime Time in seconds at which the RP mapping becomes invalid, unless it is renewed by the mapping agent Example 1...
Page 143
Chapter 3: Configuring PIM for IPv4 Multicast Address IP address of outgoing interface Interface Type and specifier of the interface. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide. Joined as Type of mapping (S, G) Mapping from a specific source to a specific group (*, G) Mapping from any source to a specific group (*, * , RP) Mapping from any source to any group...
Page 144
JUNOSe 11.0.x Multicast Routing Configuration Guide <*, G> <*, *, RP>: 0 See show ip pim sparse-mode sg-state. show ip pim sparse-mode unicast-route Use to display the unicast routes that PIM sparse mode is using. Field descriptions Route IP address and network mask for the unicast route RpfNbr RPF neighbor Iif Incoming interface for the unicast route Pref Preference value for the unicast route...
Chapter 4 Configuring DVMRP E Series routers support Distance Vector Multicast Routing Protocol (DVMRP) on VRs to forward multicast datagrams through a network. DVMRP is an interior gateway protocol that supports operations within an autonomous system, but not between autonomous systems. The multicast backbone of the Internet, MBone, uses DVMRP to forward multicast datagrams.
JUNOSe 11.0.x Multicast Routing Configuration Guide DVMRP is a dense-mode multicasting protocol and therefore uses a broadcast and prune mechanism. The protocol builds a source-rooted tree (SRT) in a similar way to PIM dense mode. DVMRP routers flood datagrams to all interfaces except the one that provides the shortest unicast route to the source.
Chapter 4: Configuring DVMRP Table 6: Sample Routing Table for a DVMRP Router (continued) Time Before Entry Is Deleted Source from Routing Input Output Subnet Subnet Mask From Router Metric Table Port Port 143.3.0.0 255.255.0.0 143.2.55.23 4/0, 4/1 143.4.0.0 255.255.0.0 143.78.6.43 4/0, 4/1 The DVMRP router maintains an (S,G) pair table that provides information to the...
JUNOSe 11.0.x Multicast Routing Configuration Guide For information about modules that support DVMRP on the E120 and E320 Broadband Services Routers: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications. See E120 and E320 Module Guide, Appendix A, IOA Protocol Support for information about the modules that support DVMRP.
Chapter 4: Configuring DVMRP Activating DVMRP on an Interface By default, DVMRP is not activated on an interface. Configuring any DVMRP parameter on an interface automatically activates DVMRP on that interface. You can also activate DVMRP on an interface and use the default parameters. ip dvmrp Use to activate DVMRP on an interface.
JUNOSe 11.0.x Multicast Routing Configuration Guide ip dvmrp route-limit Use to limit the number of routes that the router can advertise on each interface. Example host1:boston(config)#ip dvmrp route-limit 5000 Use the no version to restore the default value, 7000 routes. See ip dvmrp route-limit.
Chapter 4: Configuring DVMRP Use the no version to disable a filter. See ip dvmrp accept-filter. Configuring DVMRP Summary Addresses You can configure an interface to advertise a summary address with a known metric rather than a more specific route. DVMRP advertises the summary address if the DVMRP routing table contains a more specific route that matches the address and mask of the summary address.
JUNOSe 11.0.x Multicast Routing Configuration Guide Changing the Metric for a Route The metric for DVMRP is hop count. For example, a route with two hops over a slow serial line is preferable to a route with three hops over a faster optical line. The router increases the number of DVMRP routes in incoming reports by a default metric of one and in outgoing reports by a default of 0.
Chapter 4: Configuring DVMRP Use the connected keyword to redistribute routes that are established automatically in the RPF table when another multicast routing protocol, such as PIM, is enabled on an interface. Use the route-map keyword to configure the route map to filter imported routes from the source routing protocol to the current routing protocol.
JUNOSe 11.0.x Multicast Routing Configuration Guide host1:boston(config-if)#ip dvmrp announce-filter boston-list Use the no version to enable the interface to advertise all DVMRP routes that it has learned. See ip dvmrp announce-filter. Preventing Dynamic Route Distribution By default, if you make changes to a route map, the router dynamically redistributes the routes in DVMRP.
Chapter 4: Configuring DVMRP Use the no version to disable the exchange of DVMRP unicast routes on an interface not owned by DVMRP. See ip dvmrp unicast-routing. Disabling and Removing DVMRP You can disable DVMRP on a VR or an interface without removing the configuration. You can also remove DVMRP from a VR or an interface.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to create and enable DVMRP processing on a VR or to access Router Configuration mode. Example host1:boston(config)#router dvmrp Use the no version to remove DVMRP from a VR. See router dvmrp. Clearing DVMRP Routes You can clear one or more routes from the DVMRP routing table.
Page 159
Chapter 4: Configuring DVMRP Use to set the counters for DVMRP statistics to zero, which establishes a reference point, or baseline, for DVMRP statistics. Example (host1)#baseline ip dvmrp There is no no version. See baseline ip dvmrp. show ip dvmrp Use to display DVMRP information for a VR.
Page 160
JUNOSe 11.0.x Multicast Routing Configuration Guide Reachable Routes: route-hog-notification: 10000 route-limit: 7000 Send-S32-Prunes-Only: true unicastRoutingOnly: false Graceful Restart Duration: Graceful Restart is: complete (timer 0 seconds) Redistribution None Configured dynamic-redistribution: enabled See show ip dvmrp. show ip dvmrp interface Use to display DVMRP parameters for the specified interfaces. Field descriptions Interface Type and specifier of the interface connected to a source.
Page 161
Chapter 4: Configuring DVMRP SourceAddress: 1.0.0.1 Network/Mask: 1.0.0.1/24 Received Bad Packets: Received Bad Routes: Routes Sent: Administrative State: Enabled Summary Address(es) None Configured auto-summary: Disabed metric-offset in: metric-offset out: announce-filter: None accept-filter(s) None Configured Example 2 host1:boston#show ip dvmrp interface brief Interface SourceAddress Network/Mask...
Page 162
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to display information about DVMRP neighbors. Specify the brief keyword to view a summary of information. Field descriptions Neighbor Address/NbrAddress IP address of the neighbor Interface Interface type and specifier, such as atm3/0. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Page 163
Chapter 4: Configuring DVMRP Neighbor Major Version: Neighbor Minor Version: Neighbor Capabilities: Prune GenerationId Mtrace NetMask Neighbor State: Active Geneneration ID: 0x3a13fbc2 Routes Received: Bad Routes Received Bad Packets Received: Example 2 host1:v3#show ip dvmrp neighbor brief Interface NbrAddress UpTime Maj Min Cap State atm5/0.14 14.0.0.1...
Page 164
JUNOSe 11.0.x Multicast Routing Configuration Guide host1:boston>show ip dvmrp route Prefix/Length usNbr/Owner Metric ExpireTime UpTime Interface 14.0.0.0/8 Dvmrp Local Never atm5/0.14 Downstream Interface(s) Interface atm5/0.15 15.0.0.0/8 Dvmrp Local Never atm5/0.15 Downstream Interface(s) None 25.0.0.0/8 14.0.0.1 atm5/0.14 Downstream Interface(s) Interface atm5/0.15 Example 2 host1:v3# show ip dvmrp route brief Prefix/Length...
Page 165
Chapter 4: Configuring DVMRP 172.19.0.0/16 leaf 172.19.0.0/16 branch See show ip dvmrp routeNextHop. Monitoring DVMRP...
Part 2 Internet Protocol Version 6 Configuring IPv6 Multicast on page 147 Configuring Multicast Listener Discovery on page 183 Configuring PIM for IPv6 Multicast on page 215 Internet Protocol Version 6...
Page 168
JUNOSe 11.0.x Multicast Routing Configuration Guide Internet Protocol Version 6...
Chapter 5 Configuring IPv6 Multicast IPv6 multicast enables a device to send packets to a group of hosts rather than to a list of individual hosts. This chapter describes how to configure IPv6 multicast on the E Series router; it contains the following sections: IPv6 Multicast Overview on page 147 Platform Considerations on page 149 References on page 150...
JUNOSe 11.0.x Multicast Routing Configuration Guide A multicast address enables a device to send a datagram to a specified set of hosts, known as a multicast group, in different subnetworks. IPv6 multicast improves network efficiency by allowing a host to transmit a datagram to a targeted group of receivers.
Chapter 5: Configuring IPv6 Multicast When operating in dense-mode, routers that have multiple paths to the source of the multicast stream initially receive the same stream on more than one interface. In this case, the routers perform an RPF lookup to identify multicast data streams that are not arriving on the best path and send prune messages to terminate these flows.
JUNOSe 11.0.x Multicast Routing Configuration Guide References For more information about IPv6 multicast, see the following resource: A “ traceroute” Facility for IP Multicast draft-ietf-idmr-traceroute-ipm-07.txt (January 2001 expiration) Before You Begin You can configure multicast on IPv4 and IPv6 interfaces. For information about configuring IP interfaces, see Configuring IP in the JUNOSe IP, IPv6, and IGP Configuration Guide.
Chapter 5: Configuring IPv6 Multicast Defining Static Routes for Reverse-Path Forwarding Use the ipv6 rpf-route command to define reverse-path forwarding (RPF) to verify that a router receives a multicast packet on the correct incoming interface. ipv6 rpf-route Use to customize static routes that the router may use for RPF. Specify the IPv6 address and subnet mask of the destination network.
JUNOSe 11.0.x Multicast Routing Configuration Guide Dst Distance configured for this route Met Learned or configured cost associated with this route Intf Type of interface and interface specifier for the next hop. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Chapter 5: Configuring IPv6 Multicast Use to disable RPF checks for specified (S,G) pairs. Specify a standard IPv6 access list that defines the (S,G) pairs. Example host1(config)#ipv6 multicast-routing disable-rpf-check denver-list Use the no version to restore the default situation, in which the router performs RPF checks for all (S,G) pairs.
JUNOSe 11.0.x Multicast Routing Configuration Guide Permanent mroutes are removed if a topology change occurs that affects the mroute. Permanent mroutes may be removed due to certain protocol actions (for example, PIM sparse mode switching from shared to shortest path tree). Outgoing interface lists of permanent mroutes may change due to protocol actions.
Chapter 5: Configuring IPv6 Multicast Using the Auto-Sense Mechanism Video bandwidth is typically considered to be a constant rate 2 Mbps for standard definition television (SDTV) and 10 Mbps for high definition television (HDTV). However, in reality, and depending on achievable video compression, the bit rate can vary.
JUNOSe 11.0.x Multicast Routing Configuration Guide To calculate the measured bandwidth of a stream, the router uses the following equation: R = (N – N ) / 5 Where R = Calculated bandwidth of the stream during each sampling interval = Bytes measured at the start of each sampling period (t seconds) = Bytes measured at the end of each sampling period (t+5 seconds) NOTE: When the mroute is first installed in the FC (at t = 0), R...
Chapter 5: Configuring IPv6 Multicast Table 9: Adaptive Mode Algorithm Values (continued) Variable Value Units Description Seconds Sampling interval; zero (0) seconds indicates continuous sampling Samples Number of history samples over which to compute measurement Samples Maximum number of samples maintained in history Percent Threshold value;...
JUNOSe 11.0.x Multicast Routing Configuration Guide For additional information about configuring QoS adjustment, see “Configuring Multicast QoS Adjustment” on page 158. For additional information about configuring interface- and port-level admission control, see “Blocking and Limiting Multicast Traffic” on page 168. For additional information about creating route maps, see Configuring Routing Policy in the JUNOSe IP Services Configuration Guide .
Chapter 5: Configuring IPv6 Multicast Figure 15: Multicast OIF Mapping One disadvantage to using multicast OIF mapping is that the multicast traffic bypasses any QoS treatment that is applied to subscriber interfaces. Configuring QoS adjustment resolves this problem. (See Parameter Definition Attributes for QoS Administrators Overview for additional information about configuring QoS adjustment.) With QoS adjustment configured, when a subscriber requests to receive a multicast stream (or, more appropriately, when an OIF is added to the mroute), the router reduces the...
JUNOSe 11.0.x Multicast Routing Configuration Guide Figure 16: Multicast Traffic Receipt Without Forwarding Activating Multicast QoS Adjustment Functions The ipv6 multicast-routing bandwidth-map command activates the specified bandwidth map. By activating the bandwidth map, this command also activates the multicast QoS adjustment function contained in the bandwidth map. CAUTION: To activate multicast QoS adjustment, you must first create a bandwidth map.
Chapter 5: Configuring IPv6 Multicast The bandwidth between the line module and the I/O module or IOA on the E Series router is limited. A high-density Ethernet module provides eight physical ports that can consume the bandwidth between the line module and the I/O module or IOA before providing enough traffic to support egress line rate for all of these ports.
JUNOSe 11.0.x Multicast Routing Configuration Guide Reduce the number of packets sent from the FC to the module. Reduce the CPU consumed by the FC processing each elaboration of the packet. You can use the feature to increase the bandwidth of multicast traffic out of each of the Gigabit Ethernet ports.
Chapter 5: Configuring IPv6 Multicast Each port on the I/O module or IOA displayed in Figure 18 on page 162 has two queues. These queues are further down the egress path than the queues found on the line module and populated by the FC. The low-priority queue is dedicated to packets that are received from the line module queues that are dedicated to the physical ports.
JUNOSe 11.0.x Multicast Routing Configuration Guide Relationship with OIF Mapping Multicast OIF mapping enables the router to decrease the inefficiencies associated with replicating streams of multicast traffic. Using OIF maps, MLD joins that the router receives on a subscriber interface can be mapped to a special interface for forwarding.
Chapter 5: Configuring IPv6 Multicast information, see Configuring Ethernet Interfaces in JUNOSe Physical Layer Configuration Guide. The regular multicast implementation utilizes interface stacking that provides a unique IPv6 attachment point for each elaboration of the egress multicast packet. For the hardware multicast packet replication feature, you must attach policies to an interface stack over port 8 that defines the encapsulation of the egress multicast traffic.
Page 188
JUNOSe 11.0.x Multicast Routing Configuration Guide Configure port 8 on a high-density Ethernet module to accept redirected egress multicast traffic. a. Specify the Gigabit Ethernet interface on port 8. b. Create a VLAN major interface. Create a VLAN subinterface. d. Assign a VLAN ID. e.
Chapter 5: Configuring IPv6 Multicast Use the no version to set the version to the default, MLDv2. See ipv6 mld version. ipv6 multicast ioa-packet-replication Use to configure hardware multicast packet replication on port 8 of a high-density Ethernet module. Example host1(config-if)#ipv6 multicast ioa-packet-replication gigabitEthernet 3/8.1 Use the no version to disable hardware multicast packet replication.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the show ipv6 interface command to display statistics for an IPv6 interface configured over port 8. For more information, see Monitoring IPv6 in JUNOSe IP, IPv6, and IGP Configuration Guide. Multicast traffic redirected by the hardware multicast packet replication feature is displayed in the statistics for the IPv6 or VLAN interface over port 8, not the original IP or VLAN interface over the physical port.
Chapter 5: Configuring IPv6 Multicast Limiting Interface Admission Bandwidth Interface-level multicast admission control is performed when an OIF on the interface is added to the mroute for a given (S,G) multicast data stream and the multicast bandwidth map contains a set admission-bandwidth action for that (S,G). When enabled, the admission-bandwidth for a particular (S,G) is read from the multicast bandwidth map and recorded in the mroute when the (S,G) mroute is created.
JUNOSe 11.0.x Multicast Routing Configuration Guide If the bandwidth limit is decreased, no currently admitted OIFs are blocked. However, no new OIFs are admitted until the total admitted bandwidth for the interface drops below the new limit. If the bandwidth is increased to the point that the bandwidth limit for an interface is now exceeded, no currently admitted OIFs for the affected mroutes are blocked.
Chapter 5: Configuring IPv6 Multicast When enabled, the admission-bandwidth for a particular (S,G) is read from the multicast bandwidth map and recorded in the mroute when the (S,G) mroute is created. When an IOF is subsequently added to the mroute, the OIF is blocked from forwarding data if the additional bandwidth contributed by the (S,G) would exceed the admission-bandwidth limit for the port on which the interface resides.
JUNOSe 11.0.x Multicast Routing Configuration Guide NOTE: If the multicast bandwidth map that includes the set admission-bandwidth command is changed, all affected mroutes are reevaluated in the same manner described previously. As an example of this function, if the port has accepted a total bandwidth of 3000000 bps, and you set a limit of 2000000 bps on the port, the router does not disconnect any already connected OIFs but prevents the interfaces from accepting any more groups.
Page 195
Chapter 5: Configuring IPv6 Multicast Use to display information about all or specified multicast forwarding entries. Specify a multicast group IPv6 address or both a multicast group IPv6 address and a multicast source IPv6 address to display information about particular multicast forwarding entries.
Page 196
JUNOSe 11.0.x Multicast Routing Configuration Guide Outgoing interface list List of outgoing interfaces on the router. Details include: Type of interface and its specifier Action that the interface takes with packets: forward Protocol running on the interface: PIM or MLD Time that the interface has been active in this multicast forwarding entry, in days hours:minutes:seconds format Time that the interface will cease to be active in this multicast forwarding...
Page 197
Chapter 5: Configuring IPv6 Multicast Use to display the active multicast routes with admission bandwidth greater than the specified bandwidth threshold. The default is 4000 bps. Field descriptions See the show ipv6 mroute command and the show ipv6 mroute summary command for descriptions of all fields.
Page 199
Chapter 5: Configuring IPv6 Multicast Field descriptions Counts Number of types of source group mappings (S,G) Number of (S,G) entries (*,G) Number of (*,G) entries Example host1#show ipv6 mroute count IPv6 Multicast Routing Table Counts: 2000 (S, G) entries 0 (*, G) entries See show ipv6 mroute.
Page 202
JUNOSe 11.0.x Multicast Routing Configuration Guide interface. However, if you configure MLD and PIM on the same interface, PIM owns the interface. Admitted bandwidth / configured admission bandwidth (in bps) Number of blocked OIFs QoS adjustment bandwidth (in bps) Count Number of multicast protocols on the VR Example host1:2#show ipv6 multicast protocols Multicast protocols:...
Chapter 5: Configuring IPv6 Multicast For MLD Local Count Number of multicast protocols on the VR Example host1#show ipv6 multicast protocols brief Protocol Registered Owned Type Interfaces Interfaces --------- ---------- ---------- ------------------- Sparse Local Count: 2 protocols See show ipv6 multicast protocols. show ipv6 multicast routing Use to display information about the status of IPv6 multicast on the VR.
Chapter 6 Configuring Multicast Listener Discovery Hosts use Multicast Listener Discovery (MLD) protocol in IPv6 to report their multicast group memberships to neighboring routers. Similarly, multicast routers, such as the E Series router, use MLD to discover which of their hosts belong to multicast groups. This chapter describes how to configure MLD on an E Series router;...
JUNOSe 11.0.x Multicast Routing Configuration Guide Overview The IPv6 address scheme uses hexadecimal FF at the start of an address for IPv6 multicast. MLD is a protocol that uses these addresses. The following addresses have specific functions: You can assign only multicast addresses of global-scope (that is, containing an FFxE prefix, where x is the flags field) to a multicast group.
Chapter 6: Configuring Multicast Listener Discovery Group-specific queries Source-specific queries The purpose of a membership group query is to discover the multicast groups to which a host belongs. MLDv1 and MLDv2 multicast listener queries have a Max Response Time field. This response time is the maximum that a host can take to reply to a query.
JUNOSe 11.0.x Multicast Routing Configuration Guide For information about modules that support MLD on the E120 and E320 Broadband Services Routers: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications. See E120 and E320 Module Guide, Appendix A, IOA Protocol Support for information about the modules that support MLD.
Chapter 6: Configuring Multicast Listener Discovery Figure 19: Static and Dynamic MLD Interfaces Static MLD interfaces are configured with software such as the CLI or an SNMP application; dynamic MLD interfaces are configured with a profile. A profile comprises a set of attributes for an interface; a profile for dynamic MLD interfaces contains attributes for configuring all the layers in the interface.
JUNOSe 11.0.x Multicast Routing Configuration Guide The following sections describe the tasks associated with these and other ipv6 mld commands. You can also use various MLD-specific RADIUS attributes in RADIUS Access-Accept messages as an alternative method of configuring certain values. See Configuring RADIUS Attributes in the JUNOSe Broadband Access Configuration Guide for additional information.
Page 211
Chapter 6: Configuring Multicast Listener Discovery The method that the router uses to remove hosts from multicast groups The time interval at which the querier sends multicast listener queries The time that a querier waits before sending a new query to hosts from which it receives multicast listener done messages The time that a non-querier waits for queries from the current querier before sending query messages to assume responsibility of querier...
Page 212
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to restore the default, 10-tenths of a second (1 second). See ipv6 mld last-member-query-interval. ipv6 mld querier-timeout Use to set the time, in the range 1–400 seconds, that the interface waits for queries from the current querier before sending query messages to assume responsibility of querier.
Chapter 6: Configuring Multicast Listener Discovery Use the no version to restore the default, 100 tenths of a second (10 seconds). See ipv6 mld query-max-response-time. ipv6 mld robustness Use to specify the number of times that the router sends each MLD message from this interface.
JUNOSe 11.0.x Multicast Routing Configuration Guide or AllowNewSource group report). The request is ignored if the access list query fails. The ipv6 mld access-source-group command uses IPv6 access lists, which allow both source and destination group addresses to be specified. Use the MLD-Access-Src-Name RADIUS attribute (VSA 26-75) in RADIUS Access-Accept messages as an alternative method of configuring this value.
Chapter 6: Configuring Multicast Listener Discovery host1(config-subif)#ipv6 mld apply-oif-map OIFMAP Use the no version to remove the outgoing interface map association from the interface. See ipv6 mld apply-oif-map. ipv6 mld oif-map Use to create an OIF map. Use the MLD-OIF-Map-Name RADIUS attribute (VSA 26-76) in RADIUS Access-Accept messages as an alternative method of configuring this value.
JUNOSe 11.0.x Multicast Routing Configuration Guide The following applies when you configure SSM mapping: When enabled, and either you have not configured a static SSM map or the router cannot find any matching access lists, the router continues to accept (*,G) groups. The PIM SSM range must deny any unacceptable SSM group addresses.
Page 217
Chapter 6: Configuring Multicast Listener Discovery A specific MLD interface If you set limits for both a port and interfaces on that port, the router uses the lower of the two limits when determining how many MLD groups an interface can accept. For example, if you set a limit of 10 groups for the port and 15 groups for each interface, the router allows only 10 groups to be accepted among the interfaces.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to restore the default situation, in which there is no limit on the number of MLD groups that a port can accept. See multicast group port limit. Including and Excluding Traffic MLDv2 extends MLDv1 functionality with the ability to include or exclude specific multicast traffic sources.
Page 219
Chapter 6: Configuring Multicast Listener Discovery Minimal leave latency when a host leaves a multicast group or channel. When the router receives a leave message for a group or channel on an interface, it accesses a list of hosts and immediately stops forwarding traffic if the sender is the last host to request traffic for that group or channel.
JUNOSe 11.0.x Multicast Routing Configuration Guide option does not have any significance on an interface configured for MLD V1 and is ignored if selected. If you execute the command on an interface that was previously enabled for immediate-leave, the configuration is accepted, immediate-leave is turned off and an appropriate warning message logged.
Chapter 6: Configuring Multicast Listener Discovery ipv6 router mld Use to create and enable MLD on a VR or to access MLD Router Configuration mode. Example 1 host1(config)#virtual-router boston host1:boston(config)#router mld Example 2 host1(config)#virtual-router boston host1:boston(config)#ipv6 router mld Use the no version to delete MLD and MLD proxy from the VR. See router mld.
Page 222
JUNOSe 11.0.x Multicast Routing Configuration Guide total interfaces Number of interfaces on which you started MLD enabled Number of interfaces on which MLD is enabled disabled Number of interfaces on which MLD is disabled learned groups Number of multicast groups that the VR has discovered MLD Statistics Rcvd Statistics for MLD messages received total Number of MLD messages received checksum errors Number of MLD messages received with checksum...
Page 223
Chapter 6: Configuring Multicast Listener Discovery Reporter Link-local address of the host reporting the multicast group ExpTim Remaining time, in seconds, at which the router stops polling for more members of this group oldHTo Remaining time at which the router stops polling for more MLDv1 members of a group.
Page 224
JUNOSe 11.0.x Multicast Routing Configuration Guide 10::11 oif-map OIFMAP ATM5/0. Counts: 4 version-2, 0 version-1, 0 check state, 0 disabled (4 total) 0 excluded Source-groups: 6 included, 0 excluded See show ipv6 mld groups. show ipv6 mld interface Use to display MLD information for interfaces on which you enabled MLD. Specify the brief keyword to see a summary of the information.
Page 225
Chapter 6: Configuring Multicast Listener Discovery Inbound access source-group Access list specified No inbound access source-group No access list specified Information about OIF maps configured with the ipv6 mld apply-oif-map command Inbound apply-oif-map Map name specified No inbound apply-oif-map No map name specified Immediate Leave Setting of the ipv6 mld immediate-leave command: enabled or disabled Explicit Host Tracking Setting of the ipv6 mld explicit-tracking command:...
Page 226
JUNOSe 11.0.x Multicast Routing Configuration Guide Explicit Host Tracking: enabled Max-Group limit: No Limit Admission-Bandwidth limit: No limit IOA Packet Replication: None Group Count: 1 Interface statistics: Rcvd: 2 reports, 0 leaves, 0 wrong version queries Sent: 2 queries Groups learned: 1 Counts: 0 down, 0 init state, 1 querier, 0 non-querier, 1 Total Example 2 host1#show ipv6 mld interface gigabitEthernet 3/0.0...
Page 227
Chapter 6: Configuring Multicast Listener Discovery Querier IPv6 address of the querier on the network to which this interface connects QTime Remaining time interval at which this interface sends query messages QPTime Remaining time that the interface waits before declaring itself as the querier Example host1:boston# show ipv6 mld interface brief...
Page 228
JUNOSe 11.0.x Multicast Routing Configuration Guide show ipv6 mld oif-map Use to display all outgoing interface (OIF) maps or the OIF map for the specified map name. Field descriptions Map Name Name of the map associated to the show output Group Prefix Multicast group IPv6 prefix Source Prefix Source IPv6 prefix OIF Outgoing interface associated with the group and source prefix...
Page 229
Chapter 6: Configuring Multicast Listener Discovery M Uses Oifmap S SSM mapped T Tracked 1, 2 MLD version that the group is in Interface Type of interface and interface specifier. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Page 230
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to display the mapped OIF to be assigned to a given map-name, group address, and source address. Field descriptions OIF-MAP Name Name of the map requested Group Address Multicast group IP address requested Source Address Source IP address requested Mapped OIF Join interface associated with the OIF map Example...
Chapter 6: Configuring Multicast Listener Discovery slot Number of the chassis slot in the range 0–6 (ERX7xx models) or 0–13 (ERX14xx models) port Port number on the I/O module limit Maximum number of MLD groups that the port can accept. A value of –1 indicates that no limit has been specified.
JUNOSe 11.0.x Multicast Routing Configuration Guide As described in “Overview” on page 184, hosts interact with the router through the exchange of MLD messages. Similarly, when you configure MLD proxy, the router interacts with the router on its upstream interface through the exchange of MLD messages.
Chapter 6: Configuring Multicast Listener Discovery Use to specify, in tenths of a second, how often the upstream interface should transmit unsolicited reports. NOTE: Issue this command only on the upstream interface. Otherwise, this command has no effect. Example host1(config-if)#ipv6 mld-proxy unsolicited-report-interval 600 Use the no version to transmit unsolicited reports using the default value, 100-tenths of a second (10 seconds).
JUNOSe 11.0.x Multicast Routing Configuration Guide Monitoring MLD Proxy To display MLD proxy parameters, use the following show commands. show ipv6 mld-proxy Use to display MLD proxy parameters for a VR. Field descriptions Routing Process MLD proxy protocol Administrative state State of MLD proxy in the software Operational state Operational state of MLD proxy: enabled or disabled total interfaces Number of MLD proxy interfaces on the VR;...
Page 236
JUNOSe 11.0.x Multicast Routing Configuration Guide State Presence of MLDv1 routers on the same subnet as this upstream interface Unsolicited report interval Time interval at which this upstream interface sends unsolicited group membership report multicast group Number of multicast groups associated with this upstream interface Interface statistics Rcvd Statistics for messages received on this interface v1 queries Number of MLDv1 multicast listener queries received...
Chapter 7 Configuring PIM for IPv6 Multicast Protocol Independent Multicast (PIM) is a collection of multicast routing protocols that enable multicast routers to identify other multicast routers that can receive packets. This chapter describes how to configure PIM for IPv6 multicast on the E Series router; it contains the following sections: Overview on page 215 Platform Considerations on page 218...
JUNOSe 11.0.x Multicast Routing Configuration Guide SSM is an extension to the Any Source Multicast (ASM) service model and facilitates the deployment of broadcast (one-to-many) applications, such as Internet TV and radio where large receiver audiences require traffic from a few well-known sources. Figure 21 on page 216 represents how PIM builds an (S,G) entry in an SRT.
Chapter 7: Configuring PIM for IPv6 Multicast Timers PIM sparse mode uses timers to maintain the networking trees. NOTE: PIM sparse mode routers poll their neighbors and hosts for various pieces of information at set intervals. If a PIM sparse mode router does not receive information from a neighbor or host within a specific time, known as the hold time, it removes the associated information from its routing tables.
JUNOSe 11.0.x Multicast Routing Configuration Guide Advantages that an SSM-configured network has over a traditionally configured PIM sparse mode network include the following: No need for shared trees or RP mapping (no RP is required). No need for RP-to-RP source discovery through Multicast Source Discovery Protocol (MSDP).
Chapter 7: Configuring PIM for IPv6 Multicast NOTE: IETF drafts are valid for only 6 months from the date of issuance. They must be considered as works in progress. Please refer to the IETF Web site at for the latest drafts. http://www.ietf.org Before You Begin You can configure multicast on IPv4 and IPv6 interfaces.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the no version to reenable PIM processing. See pim disable. Enabling PIM on an Interface You can enable PIM on an interface in one of the allowed modes and specify how often the interface sends hello messages to neighbors. You can configure PIM and MLD on the same interface.
Chapter 7: Configuring PIM for IPv6 Multicast override this global setting on a particular interface, use the ipv6 pim dr-priority command in Interface Configuration mode. NOTE: You cannot configure the designated router priority on PIM DM interfaces. ipv6 pim dr-priority Use to set a priority value, in the range 1–254, by which a router is likely to be selected as the designated router.
JUNOSe 11.0.x Multicast Routing Configuration Guide In Interface Configuration mode: host1(config-subif)#ipv6 pim join-prune-interval 150 Use the no version to restore the default value, 60 seconds. Configuring an RP Router for PIM Sparse Mode When you use the router for PIM sparse mode, some VRs must act as RP routers. If you want to control PIM more tightly, you can configure a static RP router.
Page 245
Chapter 7: Configuring PIM for IPv6 Multicast ipv6 pim bsr-candidate Use to define a router as a BSR candidate. To assign an interface from which the router should send messages, specify an interface type and specifier, such as atm 3/0. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
JUNOSe 11.0.x Multicast Routing Configuration Guide Use the interval keyword to specify an interval (from 1 to 65535 seconds) at which the candidate RP sends advertisement messages to the BSR. The default is 60 seconds. Example host1(config)#ipv6 access-list 1 permit 1001::1 host1(config)#ipv6 access-list 1 permit 1002::1 host1(config)#ipv6 pim rp-candidate loopback 1 group-list 1 Use the no version to stop the router from acting as an RP candidate.
Page 247
Chapter 7: Configuring PIM for IPv6 Multicast On one router, specify the other router to be a remote neighbor, and identify the IP address of the interface on the other router that is used for the connection to this router. host1(config-router):boston#remote-neighbor 1001::1 sparse-mode Specify the location of the local interface whose address is used as the source address for the PIM connection to a remote neighbor.
JUNOSe 11.0.x Multicast Routing Configuration Guide host1(config-router-rn)#update-source loopback 5 Use the no version to delete the source address from the connection to the remote neighbor. Configuration Example This example uses the configuration shown in Figure 21 on page 216. Two E Series routers called router Boston and router Chicago are running PIM and are connected by MPLS tunnels.
Chapter 7: Configuring PIM for IPv6 Multicast of service (DOS) attacks where large numbers of joins forwarded to each router on the RPT can result in a PIM state explosion and very high memory consumption. For information about how to create access lists, see Configuring Routing Policy in the JUNOSe IP Services Configuration Guide.
JUNOSe 11.0.x Multicast Routing Configuration Guide Figure 22: Network on Which to Configure PIM SSM RP router 4 Source Receiver To configure PIM SSM: Enable PIM SSM on the E Series router. The IANA SSM range is configured by default. You can modify the SSM address range by using the access list. host1(config)#access-list 15 permit ip any host 239.0.0.2 host1(config)#access-list 15 permit ip any 232.0.0.0 0.225.225.225 host1(config)#ipv6 pim ssm range 15...
Chapter 7: Configuring PIM for IPv6 Multicast Use the no version to disable SSM. See ipv6 pim ssm. Configuring the BFD Protocol for PIM The ipv6 pim bfd-liveness-detection command configures the Bidirectional Forwarding Detection (BFD) protocol for PIM. The BFD protocol uses control packets and shorter detection time limits to more rapidly detect failures in a network.
JUNOSe 11.0.x Multicast Routing Configuration Guide You can use the minimum-receive-interval keyword to specify the minimum interval at which the local router must receive BFD control packets from its neighbors. The default value is 300 milliseconds. You can use the minimum-interval keyword to specify the same value for both of those intervals.
Chapter 7: Configuring PIM for IPv6 Multicast Use to clear the counters for multicast packet statistics on all interfaces or a specified interface. Specify an interface type and identifier, such as atm 3/0 to clear the counters on that interface. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
JUNOSe 11.0.x Multicast Routing Configuration Guide undebug ipv6 pim Use to turn off the display of information previously enabled with the debug ipv6 pim command. Example host1#undebug ipv6 pim events There is no no version. See undebug ipv6 pim. Monitoring PIM Settings You can use the show ipv6 pim commands to display information about PIM settings.
Page 255
Chapter 7: Configuring PIM for IPv6 Multicast Join filter Name of the join filter access-list (if configured) for this PIM router Designated Router Priority Designated router priority value Example host1:1#show ipv6 pim Default PIM Version: 2 Default Domain Id: 0 Default Hello Period: 30 Default Hello HoldTime: 105 Join-Prune Interval: 100...
Page 256
JUNOSe 11.0.x Multicast Routing Configuration Guide Configured on intf ATM3/0.101, address: ::107:9 hashMaskLen 30, priority 2, period 60 seconds. Elected BSR is this router, next BSM in 3 seconds. Local candidate RP mapping(s): Candidate RP ::107:9 ::108:86, BSR, hold-time 150, interval 60, priority 192 ::108:87, BSR, hold-time 150, interval 60, priority 192, from access-list ::108:88, BSR, hold-time 150, interval 60, priority 192, from access-list Example 2 On a router that is a candidate BSR...
Page 257
Chapter 7: Configuring PIM for IPv6 Multicast Hello Intvl Time interval at which the interface sends hello messages to neighbors J/P Interval Total number of join/prune message interval, in seconds, at which the interface sends the join/prune messages DR Address Address of the designated router SM Number of PIM sparse mode interfaces enabled Number of interfaces administratively enabled disabled Number of interfaces administratively disabled...
Page 258
JUNOSe 11.0.x Multicast Routing Configuration Guide Use to display information about PIM neighbors that the router discovered. Provide an interface type and specifier (such as atm 3/0) to display information about that interface only. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Page 259
Chapter 7: Configuring PIM for IPv6 Multicast In interface Type and identifier of the interface on which PIM router receives packets from remote neighbor. For details about interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Page 260
JUNOSe 11.0.x Multicast Routing Configuration Guide Group Multicast group RP RP router for the multicast group priority This field is not functional via Method by which the RP router was assigned (static, BSR) Example host1:2#show ipv6 pim rp-hash 232.1.1.1 Group(s) ff00::/12 RP ::122:1, priority 0, static...
Page 261
Chapter 7: Configuring PIM for IPv6 Multicast host1:2#show ipv6 pim sparse-mode sg-state PIM SM route table and oif information <*, ff0e::1:3> Group-to-RP mapping: ff00::/12 RP: ::123:1 RPF Route: ::123:1/96 IIF: :106:73 UpNbr: ::106:37 Oifs: Address: ::78:7:7 Interface: loopback7 Local group membership present. <*, ff0e::a:1>...
Page 262
JUNOSe 11.0.x Multicast Routing Configuration Guide host1:2#show ipv6 pim sparse-mode unicast-route PIM SM unicast route table information Route RpfNbr Pref Metric --------------------------------------------------------------------------- ::122:0 ::122:1 Count of entries: 1 See show ipv6 pim sparse-mode unicast-route show ipv6 pim spt-threshold Use to display the threshold for switching to the shortest path tree at a PIM designated router.
Index access lists, IP data MDT, creating............99 specifying multicast groups........52 data path failure access lists, IPv6 detecting RIP..........108, 229 specifying multicast groups.........191 debug commands advertising DVMRP routes........125, 133 debug ip pim............110 assert messages............82 debug ipv6 pim...........231 assigning multicast groups........53, 192 default MDT, creating...........95 auto-RP router detecting RIP data path failure......108, 229...
Page 266
JUNOSe 11.0.x Multicast Routing Configuration Guide ip commands ip block-multicast-sources........25 encapsulation commands ip multicast-routing...........7, 10 encapsulation vlan........23, 166 ip multicast-routing disable-rpf-check.....9 exchanging DVMRP unicast routes......134 ip multicast-routing permanent-mroute....10 ip route-type............9 ip rpf-route..............7 ip unnumbered..........24, 166 filtering mroute port limit........26, 28, 168 DVMRP reports...........130 ip dvmrp commands..........129 ip dvmrp.............129, 135...
Page 267
Index IP multicast routes............40 ipv6 mld-proxy unsolicited-report-interval..210 IP multicasting ipv6 mld-proxy version........210 benefits of...............3 See also show ipv6 mld commands deleting routes............30 IPv6 multicast enabling..............7 benefits of............147 M-BONE..............125 deleting routes............172 monitoring............30 enabling..............150 ip pim commands............88 monitoring............172 ip pim..............88 ipv6 multicast commands ip pim bsr-candidate..........93 ipv6 multicast admission-bandwidth-limit...168 ip pim data-mdt..........104...
Page 269
Index RP (rendezvous point) routers......90, 222 show ip pim neighbor.........110 assigning automatically.........90 show ip pim rp...........110 configuring show ip pim rp-hash...........110 automatic............90 show ip pim sparse-mode sg-state......110 static............90, 222 show ip pim sparse-mode unicast-route....110 RPF (reverse-path forwarding)......7, 147, 151 show ip pim spt-threshold........110 RPF routes, monitoring..........7, 151 show ipv6 commands show ipv6 mroute..........173...
Need help?
Do you have a question about the JUNOSE 11.0.X MULTICAST ROUTING and is the answer not in the manual?
Questions and answers