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 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...
Page 4 Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without an export license. Copyright © 2010, Juniper Networks, Inc.
Page 5 (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 N. Mathilda Ave., Sunnyvale, CA http://www.gnu.org/licenses/gpl.html...
Page 19: About The Documentation
Audience This guide is intended for experienced system and network specialists working with Juniper Networks E Series Broadband Services Routers in an Internet access environment. E Series and JunosE Text and Syntax Conventions Table 1 on page xx defines notice icons used in this documentation.
Page 20: Table 1: Notice Icons
Indicates that you must press two or more Press Ctrl + b. keys simultaneously. Syntax Conventions in the Command Reference Guide Plain text like this Represents keywords. terminal length Italic text like this Represents variables. mask, accessListName Copyright © 2010, Juniper Networks, Inc.
Page 21: About The Documentation
CD-ROMs or DVD-ROMs, see the Portable Libraries page at http://www.juniper.net/techpubs/resources/index.html Copies of the Management Information Bases (MIBs) for a particular software release are available for download in the software image bundle from the Juniper Networks Web site at http://www.juniper.net/...
Page 22: Self-Help Online Tools And Resources
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/...
Page 23: Internet Protocol Version
PART 1 Internet Protocol Version 4 Configuring IPv4 Multicast on page 3 Configuring IGMP on page 41 Configuring PIM for IPv4 Multicast on page 77 Configuring DVMRP on page 121 Copyright © 2010, Juniper Networks, Inc.
Page 25: Configuring Ipv4 Multicast
IPv4 defines three types of addresses: unicast, broadcast, and multicast. Each type of address enables a device to send datagrams to selected recipients: A unicast address enables a device to send a datagram to a single recipient. Copyright © 2010, Juniper Networks, Inc.
Page 26: Internet Protocol Version
When the router receives a multicast datagram from a source for a group, the router verifies that the packet was received on the correct RPF interface. If the packet was not Copyright © 2010, Juniper Networks, Inc.
Page 27: Multicast Packet Forwarding
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: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications.
Page 28: References
Multicast” on page 141. 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 traffic,...
Page 29: Defining Static Routes For Reverse-Path Forwarding
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 Copyright © 2010, Juniper Networks, Inc.
Page 30 N1- NSSA external type1, N2- NSSA external type2 L- MPLS label, V- VR/VRF, *- indirect next-hop 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. Copyright © 2010, Juniper Networks, Inc.
Page 31: Enabling And Disabling Rpf Checks
Use the show ip rpf-routes command to view the routes available for RPF. By default, IS-IS, OSPF, and RIP routes are available both for unicast forwarding and multicast reverse-path forwarding checks. Example host1(config)#router ospf host1(config-router)#ip route-type multicast Copyright © 2010, Juniper Networks, Inc.
Page 32: Defining Permanent Ip Multicast Forwarding Entries
Interface-level and port-level admission control is performed when an OIF on the interface or port is added to the mroute for a given (S,G) multicast data stream and the multicast Copyright © 2010, Juniper Networks, Inc.
Page 33: Using The Autosense Mechanism
A rate measurement mechanism runs on the ingress line card that polls the forwarding controller (FC) to obtain statistics for each mroute. This mechanism then reports the rate measurement to the SRP to update the bandwidth map. By computing the average Copyright © 2010, Juniper Networks, Inc.
Page 34: Figure 1: Example Of Adaptive Ipv4 Multicast Bandwidth Detection
This process is repeated every sampling interval, T , to yield rates R1, R2, R3, and so on. The first two sampling interval calculations are as follows: = (N = (N Copyright © 2010, Juniper Networks, Inc.
Page 35: Multicast Bandwidth Map Example
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 Copyright © 2010, Juniper Networks, Inc.
Page 36 The system records the priority when a new <S, G> entry is created. Example host1(config-route-map)#set priority 100 Use the no version to remove the priority value. See set priority. set qos-bandwidth Copyright © 2010, Juniper Networks, Inc.
Page 38: Multicast Traffic Receipt Without Forwarding
OIF list) and the router applies the QoS adjustment to the join interface. See Figure 3 on page 17. NOTE: Ensure that PIM-SM (or any other upstream multicast protocol) is informed of the group (or source-group) interest. Copyright © 2010, Juniper Networks, Inc.
Page 39: Activating Multicast Qos Adjustment Functions
(FC) on the router. 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 Copyright © 2010, Juniper Networks, Inc.
Page 40: Figure 4: Packet Flow Without Hardware Multicast Packet Replication
IP television (IPTV). Configuring hardware multicast packet replication enables you to: Reduce the number of packets sent from the FC to the module. Copyright © 2010, Juniper Networks, Inc.
Page 41: Figure 5: Packet Flow With Hardware Multicast Packet Replication
JunosE tracks the OIFs in an mroute that have been redirected to use the hardware multicast packet replication hardware. The system accepts only egress multicast traffic to traverse the interface stack on the enabled port. The system drops unicast traffic that is routed to this port. Copyright © 2010, Juniper Networks, Inc.
Page 42: Supported Modules And Encapsulations
NOTE: 802.3ad link aggregation group (LAG) bundles do not support hardware multicast packet replication. The hardware multicast packet replication feature also provides an interface over which you can configure the following: IP MTU Ethernet MTU Egress IP policy Egress VLAN policy Copyright © 2010, Juniper Networks, Inc.
Page 43: Relationship With Oif Mapping
MAC address that you configured. For more information, see Configuring Ethernet Interfaces in the JunosE Physical Layer Configuration Guide. The regular multicast implementation utilizes interface stacking that provides a unique IP attachment point for each elaboration of the egress multicast packet. Copyright © 2010, Juniper Networks, Inc.
Page 44: Configuring Hardware Multicast Packet Replication
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. Specify the Gigabit Ethernet interface on port 8. Create a VLAN major interface. Copyright © 2010, Juniper Networks, Inc.
Page 45 Use the no version to set the version to the default, IGMPv2. See ip igmp version. ip multicast ioa-packet-replication Use to configure hardware multicast packet replication on port 8 of a high-density Ethernet module. Example Copyright © 2010, Juniper Networks, Inc.
Page 46: Monitoring Hardware Multicast Packet Replication
The statistics for the IP or VLAN interface over port 8 reflect the number of packets that passed through this interface destined for the hardware multicast packet replication hardware. These statistics have no direct correlation to the number of packets being transmitted from any of the physical ports. Copyright © 2010, Juniper Networks, Inc.
Page 47: Igmp Statistics
(S,G) would exceed the admission-bandwidth limit for the interface. CAUTION: Before you can limit interface-level admission bandwidth, you must first create a bandwidth map. See “Defining a Multicast Bandwidth Map” on page 10 for details. Copyright © 2010, Juniper Networks, Inc.
Page 48: Enabling Interface Admission Bandwidth Limitation
For example, if you specify an admission bandwidth limit of 2000000 bps for the port and 3000000 bps groups for each interface, additional groups can only be accepted until the port limit of 2000000 bps is reached. Copyright © 2010, Juniper Networks, Inc.
Page 49: Creating Mroute Port Limits
IPv4 and IPv6 mroutes that have OIFs on the port. NOTE: Admission bandwidth values for a given (S,G) mroute are determined from the bandwidth map. See “Defining a Multicast Bandwidth Map” on page 10 for details. Copyright © 2010, Juniper Networks, Inc.
Page 50: Oif Port Reevaluation Example
However, no new OIFs are admitted until the total admitted bandwidth for the port 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. Copyright © 2010, Juniper Networks, Inc.
Page 51: Deleting Multicast Forwarding Entries
* There is no no version. See clear ip mroute. Monitoring IP Multicast Settings To display general information about the IP multicast configuration on the router, use the following show commands. show ip mroute Copyright © 2010, Juniper Networks, Inc.
Page 52 Other protocols—Route established by a protocol such as RIP or OSPF Incoming interface list—List of incoming interfaces on the router. Details include: Type of interface and its specifier Action that the interface takes with packets: Accept or Discard Multicast protocol that owns the interface Copyright © 2010, Juniper Networks, Inc.
Page 53 RPF route: 1.0.0.0/8, incoming interface ATM5/1.200 neighbor 2.2.2.2, owner Netmgmt Incoming interface list: ATM5/1.200 (2.1.1.1/8), Accept/Igmp (RPF IIF) Outgoing interface list: ATM5/1.300 (3.1.1.1/8), Forward/Igmp, 0 00:00:34/never Counts: 2 (S, G) entries 0 (*, G) entries Copyright © 2010, Juniper Networks, Inc.
Page 54 (S, G) uptime d h:m:s[, expires d h:m:s] [Admission bandwidth: bps] [QoS bandwidth: bps] RPF route: addr/mask, incoming interface neighbor address, owner route-owner Incoming interface list: Interface (addr/mask), State/Owner [(RPF IIF)] Outgoing interface list: Interface (addr/mask), State/Owner, Uptime/Expires Copyright © 2010, Juniper Networks, Inc.
Page 55 (S, G)—Number of (S,G) entries (* , G)—Number of (* ,G) entries Example host1#show ip mroute count IP Multicast Routing Table Counts: 2 (S, G) entries 0 (*, G) entries See show ip mroute. show ip mroute statistics Copyright © 2010, Juniper Networks, Inc.
Page 56 RPF route: 10.0.0.0/8, incoming interface ATM2/1.200 neighbor 21.1.1.1, owner Netmgmt Incoming interface list: ATM2/1.200 (21.2.2.2/8), Accept/Pim (RPF IIF) Outgoing interface list: ATM2/1.300 (31.2.2.2/8), Blocked (port-adm-limit)/Pim, 0 00:00:23/never Statistics: Received : 23 pkts, 1472 bytes Copyright © 2010, Juniper Networks, Inc.
Page 57 See show ip mroute. show ip multicast protocols Use to display information about multicast protocols enabled on the router. Use the brief option to display a summary of information rather than a detailed description. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 58 Protocol Pim Type: Sparse Interfaces: 1 registered, 1 owned Registered interfaces: ATM2/1.103 (103.0.0.2/24) owner Pim Protocol Igmp Type: Local Interfaces: 1000 registered, 1000 owned Registered interfaces: ATM2/0.131 (13.0.0.1/24) local Igmp owner Igmp Admission-bandwidth 2000000/10000000 bps Copyright © 2010, Juniper Networks, Inc.
Page 59 Interfaces --------- ---------- ---------- ------------------- Sparse Dense Igmp Local Count: 2 protocols See show ip multicast protocols. show ip multicast routing Use to display information about the status of IP multicast on the VR. Copyright © 2010, Juniper Networks, Inc.
Page 60: Support For Multicast Router Information
When you enable multicast routing on a virtual router, the router acts as a multicast router information (mrinfo) server. This feature enables the router to respond to mrinfo requests from other network hosts. Specifically, E Series virtual routers respond to DVMRP ask neighbors and DVMRP ask neighbors2 requests. Copyright © 2010, Juniper Networks, Inc.
Page 61: Bgp Multicasting
To direct the packets through a particular multicast group address, specify that multicast group address. If you do not specify a multicast group address, the router traces the route through the MBone audio multicast group. Copyright © 2010, Juniper Networks, Inc.
Page 62 Tracing multicast route from 100.4.4.4 to 40.1.1.1 for group 232.1.1.1 using response address 10.6.129.56 (Press ^c to stop.) Received mtrace response packet of length 88 1. 40.1.1.1 Protocol: PIM(3) FwdingCode: RPF iif(9) 2. 21.2.2.2 Protocol: PIM(3) FwdingCode: Reached RP(8) There is no no version. See mtrace. Copyright © 2010, Juniper Networks, Inc.
Page 63: Configuring Igmp
Disabling and Removing IGMP on page 58 Monitoring IGMP on page 59 IGMP Proxy Overview on page 69 Configuring IGMP Proxy on page 70 Establishing the IGMP Proxy Baseline on page 72 Monitoring IGMP Proxy on page 72 Copyright © 2010, Juniper Networks, Inc.
Page 64: Igmp Overview
General queries to the all-hosts group address (224.0.0.1) Specific queries to the appropriate multicast group address IGMPv3 mode interfaces send the following types of queries to IGMPv3 hosts: General queries Group-specific queries Source-specific queries Copyright © 2010, Juniper Networks, Inc.
Page 65: Group Membership Reports
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 IGMP. Copyright © 2010, Juniper Networks, Inc.
Page 68: Enabling Igmp On An Interface
Use to enable IGMP on an interface and to set the IGMP version to IGMPv2. Use the ip igmp version command to specify a different IGMP version. Example host1:boston(config-if)#ip igmp Use the no version to disable IGMP on an interface. See ip igmp. Copyright © 2010, Juniper Networks, Inc.
Page 69: Configuring Igmp Settings For An Interface
The time that a host can take to reply to a query (maximum response time) The number of times that the router sends each IGMP message from this interface ip igmp immediate-leave Copyright © 2010, Juniper Networks, Inc.
Page 70 Example host1:boston(config-if)#ip igmp querier-timeout 200 Use the no version to set the time to the default, twice the query interval. See ip igmp querier-timeout. Copyright © 2010, Juniper Networks, Inc.
Page 71 Use a higher value to ensure high reliability from IGMP. Specify a number in the range 1–4. Example host1:boston(config-if)#ip igmp robustness 2 Use the no version to restore the default, 3. See ip igmp robustness. Copyright © 2010, Juniper Networks, Inc.
Page 72: Specifying Multicast Groups
Note that in the access list specified when you issue this command, the source is specified before the group. Example host1:boston(config-if)#ip igmp access-source-group dallas-list Copyright © 2010, Juniper Networks, Inc.
Page 73: Assigning A Multicast Group To An Interface
Use to apply the specified outgoing interface (OIF) map to the current interface. Example host1(config-subif)#ip igmp apply-oif-map OIFMAP Use the no version to remove the outgoing interface map association from the interface. See ip igmp apply-oif-map. ip igmp oif-map Copyright © 2010, Juniper Networks, Inc.
Page 74: Configuring Access Node Control Protocol For Igmp
IGMPv1 and IGMPv2 membership reports and no change occurs to the SSM mapping for the group. When you statically configure SSM mapping, the router can discover source addresses from a statically configured table. Copyright © 2010, Juniper Networks, Inc.
Page 75: 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 Copyright © 2010, Juniper Networks, Inc.
Page 76 (E320 router). slot—Number of the chassis slot in the range 0–6 (ERX7xx models), 0–13 (ERX14xx models), or 0–16 (E320) adapter—Adapter number on the E320 IOA module port—Port number on the I/O or IOA module Copyright © 2010, Juniper Networks, Inc.
Page 77: Including And Excluding Traffic
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. See ip igmp static-include. Copyright © 2010, Juniper Networks, Inc.
Page 78: Configuring Explicit Host Tracking
You cannot configure explicit host tracking on passive IGMP interfaces or on IGMP V1 interfaces. When you enable IGMP V2 or V3 on an interface, explicit host tracking is not enabled by default. Copyright © 2010, Juniper Networks, Inc.
Page 79: Accepting Igmp Reports From Remote Subnetworks
See ip igmp explicit-tracking. Accepting IGMP Reports from Remote Subnetworks By default, IGMP interfaces accept IGMP reports only from associated subnetworks. You can configure the router to accept IGMP reports from subnetworks that are not associated Copyright © 2010, Juniper Networks, Inc.
Page 80: Disabling And Removing Igmp
IGMP reports. See ip igmp promiscuous. Disabling and Removing IGMP You can disable and reenable IGMP on the VR. You can also remove IGMP from the VR and recreate it on the VR. igmp disable Copyright © 2010, Juniper Networks, Inc.
Page 81: Monitoring Igmp
See baseline ip igmp. show ip igmp Use to display IGMP information for a VR. Field descriptions Routing Process—Routing process for this VR (IGMP) Administrative state—Status of IGMP in the software: enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 82 Field descriptions Grp Address—Address of the multicast group Interface—Interface that discovered the multicast group oif-map—Name of the OIF map and the mapped OIF interface, when a group or source has been mapped to an OIF Copyright © 2010, Juniper Networks, Inc.
Page 83 OIFMAP ATM5/0.121 232.1.1.2 ATM5/0.13 Version3 1.1.1.3 Included Sources: 10.1.1.2 oif-map OIFMAP self 10.1.1.10 oif-map OIFMAP ATM5/0.120 10.1.1.11 oif-map OIFMAP ATM5/0.121 Counts: 4 version-3, 0 version-2, 0 version-1, 0 check state, 0 disabled (4 total) Copyright © 2010, Juniper Networks, Inc.
Page 84 IGMP reports from hosts on any subnetwork Information about standard IP access lists configured with the ip igmp access-group command Inbound access group—Access list specified No inbound access group—No access list specified Copyright © 2010, Juniper Networks, Inc.
Page 85 Interface statistics Groups learned—Number of groups this interface has discovered Counts—Breakdown of IGMP interfaces down—Number of interfaces down init state—Number of interfaces in the initialization state querier—Number of querier interfaces non-querier—Number of non-querier interfaces Total—Total number of IGMP interfaces Example 1 Copyright © 2010, Juniper Networks, Inc.
Page 86 Group Count: 0 IOA packet replication gigabitEthernet 3/8.1 Interface statistics: Rcvd: 0 reports, 0 leaves, 0 wrong version queries Sent: 0 queries Groups learned: 0 See show ip igmp interface. show ip igmp interface brief Copyright © 2010, Juniper Networks, Inc.
Page 87 Group Address—Multicast group IP address associated with the OIF Source Address—Source IP address associated with the OIF Join I/F—IGMP interface associated with the OIF Map Name—Name of the map associated to the OIF Counts—Number of source-group mappings to OIFs Example Copyright © 2010, Juniper Networks, Inc.
Page 88 <ip-address> - last reporter if the group is not explicitly tracked <n>/<m> - <n> reporters include mode, <m> reporters in exclude Group Source Reporter ExpTim Flags Interface --------------- --------------- ------------- ------ ------ --------------- 224.0.1.40 10.10.1.1 02:41 FastEthernet2/1 Copyright © 2010, Juniper Networks, Inc.
Page 89 OIF—Outgoing interface associated with the group and source prefix Example host1#show ip igmp oif-map Map Name Group Prefix Source Prefix ------------------ ------------------ ------------------ ------------------ OIFMAP 232.1.1.0/24 0.0.0.0/0 ATM5/0.121 232.1.1.0/24 10.1.1.2/32 self 232.1.1.0/24 10.1.1.10/32 ATM5/0.120 Copyright © 2010, Juniper Networks, Inc.
Page 90 Source List—List of sources mapped to the multicast group address Example host1:boston#show ip igmp ssm-mapping 232.1.1.1 SSM Mapping : Enabled Group Address : 232.1.1.1 Source List : 172.1.1.1 : 172.1.1.2 See show ip igmp ssm-mapping. show multicast group limit Copyright © 2010, Juniper Networks, Inc.
Page 91: Igmp Proxy Overview
The router on the upstream interface is running IGMP. You enable IGMP on the interfaces that connect the router to its hosts that are farther away from the root of the tree. These interfaces are known as downstream interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 92: Configuring Igmp Proxy
600 (Optional) Specify how long the router calculates an IGMPv1 querier router to exists on the subnetwork after the router receives an IGMPv1 query on this interface. host1(config-if)#ip igmp-proxy V1-router-present-time 600 Copyright © 2010, Juniper Networks, Inc.
Page 93 NOTE: Issue this command only on the upstream interface. Otherwise, this command has no effect. Example host1(config-if)#ip igmp-proxy V1-router-present-time 600 Use the no version to set the time to the default value, 10 seconds. See ip igmp-proxy V1-router-present-time Copyright © 2010, Juniper Networks, Inc.
Page 94: Establishing The Igmp Proxy Baseline
IGMP proxy interfaces: enabled or disabled multicast group—Number of multicast groups associated with IGMP proxy interfaces Example host1#show ip igmp-proxy Routing Process IGMP Proxy, Administrative state enabled, Operational state enabled total 1 upstream interface, state enabled 6 multicast group Copyright © 2010, Juniper Networks, Inc.
Page 95 3/0. For details about interface types and specifiers, see Interface Types and Specifiers in JunosE Command Reference Guide. Specify the brief keyword to display a summary rather than a detailed description. Copyright © 2010, Juniper Networks, Inc.
Page 96 Administrative state enabled, Operational state enabled Interface parameters: Version 2 State No v1 Router Present Unsolicited report interval 10 secs Version 1 router present timeout 400 secs 0 multicast group Interface statistics: Rcvd: 0 v1 query, 6 v2 queries Copyright © 2010, Juniper Networks, Inc.
Page 99: Configuring Pim For Ipv4 Multicast
Using PIM Sparse Mode Join Filters on page 103 Configuring PIM SSM on page 103 Configuring the BFD Protocol for PIM on page 104 Removing PIM on page 106 Resetting PIM Counters and Mappings on page 106 Monitoring PIM on page 107 Copyright © 2010, Juniper Networks, Inc.
Page 100: Overview
Dense-mode routing protocols use SRT algorithms. An SRT algorithm establishes a tree that connects each source in a multicast group to the members of the group. All traffic for the multicast group passes along this tree. Copyright © 2010, Juniper Networks, Inc.
Page 101: Overriding Prunes
If a forwarding router receives a multicast packet on its outgoing interface, the router identifies that the packet is a duplicate and notifies the upstream routers. See Figure 10 on page 80. Copyright © 2010, Juniper Networks, Inc.
Page 102: Pim Sparse Mode
The designated router encapsulates the datagram and unicasts it to an assigned RP router, which then forwards the datagram to members of multicast groups. See Figure 11 on page 81. Copyright © 2010, Juniper Networks, Inc.
Page 103: Figure 11: Pim Sparse Mode Operation
The designated routers on the network determine when the source switches from a shared tree to an SPT. A designated router switches to the SPT when it receives a certain number of packets which you can configure. Copyright © 2010, Juniper Networks, Inc.
Page 104: Joining Groups
The BSR picks an RP set from the available candidates and periodically announces this set in a bootstrap message. Bootstrap messages are flooded hop by hop throughout the domain until all routers in the domain learn the RP set. Copyright © 2010, Juniper Networks, Inc.
Page 105: Pim Sparse-Dense Mode
An SSM-configured network has the following advantages 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). Copyright © 2010, Juniper Networks, Inc.
Page 106: Platform Considerations
RFC 3569—An Overview of Source-Specific Multicast (SSM) (July 2003) Source-Specific Multicast for IP—draft-ietf-ssm-arch-06.txt (March 2005 expiration) Source-Specific Protocol Independent Multicast in 232/8—draft-ietf-mboned-ssm232-08.txt (September 2004 expiration) Multicast in MPLS/BGP VPNs—draft-rosen-vpn-mcast-06.txt (April 2004 expiration) Multicast in MPLS/BGP IP VPNs—draft-rosen-vpn-mcast-08.txt (June 2005 expiration) Copyright © 2010, Juniper Networks, Inc.
Page 107: Before You Begin
To disable PIM processing on a router, use the pim disable command. pim disable Use to disable PIM processing. By default, PIM processing is enabled. Example host1:boston(config-router)#pim disable Use the no version to reenable PIM processing. See pim disable. Copyright © 2010, Juniper Networks, Inc.
Page 108: Enabling Pim On An Interface
The ip pim dr-priority command in Router Configuration mode sets the designated router priority on all the PIM interfaces on the router. To override this global setting on a particular interface, use the ip pim dr-priority command in Interface Configuration mode. Copyright © 2010, Juniper Networks, Inc.
Page 109: Configuring The Pim Join/Prune Message Interval
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. Copyright © 2010, Juniper Networks, Inc.
Page 110: Configuring An Rp Router For Pim Sparse Mode And Pim Sparse-Dense Mode
In PIM sparse-dense mode, you must prevent routers from advertising auto-RP messages to the multicast groups 224.0.1.39 and 224.0.1.40, which are reserved for forwarding auto-RP messages through the network. To configure an auto-RP router for PIM sparse-dense mode: Assign an RP mapping agent. Copyright © 2010, Juniper Networks, Inc.
Page 111 Specify a time interval in the range 1–65535 seconds to control how often the router sends announcements. The default is 60 seconds. Example host1(config)#ip pim send-rp-announce loopback 2 scope 23 group-list boston interval Copyright © 2010, Juniper Networks, Inc.
Page 112: Configuring Bsr And Rp Candidates For Pim Sparse Mode
Use the period keyword to specify the interval, in the range 1–65535 seconds, at which the BSR sends bootstrap messages. The default value is 60 seconds. Example host1(config)#ip pim bsr-candidate loopback 1 30 10 Copyright © 2010, Juniper Networks, Inc.
Page 113: Migrating To Bsr From Auto-Rp
Use the no ip pim send-rp-discovery scope command to stop PIM in the network by disabling all auto-RP mapping agents. This results in flooding to an empty map. Reconfigure auto-RP mapping agents as candidate BSRs by using the ip pim bsr-candidate command. Copyright © 2010, Juniper Networks, Inc.
Page 114: Switching To An Spt For Pim Sparse Mode
VPN (MVPN) group address of the MDT. A tunnel mdt command specifies that the tunnel is the MTI for the default MDT, enabling the creation of a second, layer 2 interface (interface tunnel gre:name.mdt) on which an Copyright © 2010, Juniper Networks, Inc.
Page 115: Multicast Vpn Configuration Example
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 116 VRF using the ip route-type both command. host1:PE2(config)#router bgp 100 host1:PE2(config-router)#address-family ipv4 unicast vrf PE21 host1:PE2(config-router-af)#ip route-type both host1:PE2(config-router-af)#exit host1:PE2(config-router)# Configure the GRE tunnel for VPN1. host1(config)#interface tunnel gre:MTI-21 transport-virtual-router PE2 Copyright © 2010, Juniper Networks, Inc.
Page 117 Lp. host1(config)#virtual-router PE2 host1: PE2(config)#interface tunnel gre:MTI-21.mdt host1:PE2(config-if)#ip unnumbered loopback 0 host1:PE2(config-if)#ip pim sparse-mode host1:PE2(config-if)#exit host1:PE2(config)# host1:PE2(config)#interface tunnel gre:MTI-22.mdt host1:PE2(config-if)#ip unnumbered loopback 0 host1:PE2(config-if)#ip pim sparse-mode host1:PE2(config-if)#exit host1:PE2(config)# tunnel mdt Copyright © 2010, Juniper Networks, Inc.
Page 118: Creating Multicast Vpns Using The Data Mdt
MDT is removed. The Source C-PIM-SM maintains sent MDT Join TLV messages in its database as long as they are active. While the data MDT is active, C-PIM-SM resends that MLD Join TLV Copyright © 2010, Juniper Networks, Inc.
Page 119: Data Mdt Receivers
If SSM is activated and the P-Group is in the SSM group range, P-PIM-SM performs an <S, G> join towards the P-Source, where the P-Source address is the SA of the MDT Join TLV. Copyright © 2010, Juniper Networks, Inc.
Page 120: Configuring The Default Mdt
NOTE: The IP address that you configure for the VRF must be identical to the IP address of the loopback interface in the parent virtual router. Configure the MTI interface in the VRF. host1:pe1:pe13(config)#interface tunnel gre:MTI-11 host1:pe1:pe13(config-if)#ip unnumbered loopback 0 host1:pe1:pe13(config-if)#ip pim sparse-mode host1:pe1:pe13(config-if)#exit Copyright © 2010, Juniper Networks, Inc.
Page 121: Configuring Data Mdts
MTI interface in the VRF. host1(config)#profile pe13DataMdtMti host1(config-profile)#ip virtual-router pe1:pe13 host1(config-profile)#ip unnumbered loopback 0 host1(config-profile)#ip pim sparse-mode 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 Copyright © 2010, Juniper Networks, Inc.
Page 122 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 Copyright © 2010, Juniper Networks, Inc.
Page 123 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 Copyright © 2010, Juniper Networks, Inc.
Page 124 See set threshold. tunnel group-address-pool 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. Copyright © 2010, Juniper Networks, Inc.
Page 125: Using Pim Sparse Mode Join Filters
(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. To configure PIM SSM: Copyright © 2010, Juniper Networks, Inc.
Page 126: Configuring The Bfd Protocol For Pim
Detection (BFD) protocol for PIM. The BFD protocol uses control packets and shorter detection time limits to more rapidly detect failures in a network. Also, because they are adjustable, you can modify the BFD timers for more or less aggressive failure detection. Copyright © 2010, Juniper Networks, Inc.
Page 127 BFD liveness detection interval can be different on each neighbor. The multiplier value is roughly equivalent to the number of packets that can be missed before the BFD session is declared to be down. The default value is 3. Copyright © 2010, Juniper Networks, Inc.
Page 128: Removing Pim
If you do not specify an IP address, the router clears the group-to-RP mappings on all RP routers learned through auto-RP. Example host1#clear ip pim auto-rp 192.34.56.7 There is no no version. See clear ip pim auto-rp. clear ip pim interface count Copyright © 2010, Juniper Networks, Inc.
Page 129: Monitoring Pim
To control how much information to display, specify a verbosity level. Example host1#debug ip pim events severity 1 verbosity low Use the no version to disable the display. See debug ip pim. undebug ip pim Copyright © 2010, Juniper Networks, Inc.
Page 130: Monitoring Pim Settings
Register TTL—TTL value (in PIM register packets) originated by this PIM router SSM—State of SSM on this PIM router (enabled or disabled) range—Default SSM group range or name of the access list specifying the range Sparse-Mode Graceful Restart Duration—Restart interval in seconds Copyright © 2010, Juniper Networks, Inc.
Page 131 PIM AutoRP candidate RP mapping(s) Candidate RP 122.0.0.1 Group(s) 224.0.0.0/4, AutoRP, ttl 64, interval 60, from access List 1 Candidate RP 122.0.0.1 Group(s) 224.0.1.39/32 (negative), AutoRP, ttl 64, interval 60, from access List 1 Copyright © 2010, Juniper Networks, Inc.
Page 132 This PIM router is a Candidate BSR. Configured on intf ATM3/0.100, address: 100.0.0.1 hashMaskLen 30, priority 2, period 60 seconds. Elected BSR is 101.0.0.1 (priority 0), expires in 73 seconds. Copyright © 2010, Juniper Networks, Inc.
Page 133 Time until next MDT Join TLV: 25 seconds Example 2—Displays information about a data MDT receiver host1:PE1#show ip pim data-mdt 225.2.2.2 PE31 - Receiver C-SG: 10.13.0.100, 225.2.2.2 P-SG: 3.3.3.3, 235.0.1.1 MTI: TUNNEL gre:mvpn-dynamic-3 Time until MDT Join TLV expires: 29 seconds Copyright © 2010, Juniper Networks, Inc.
Page 134 Pruned due to assert Pruned time remaining 129 <130.0.0.2, 224.0.1.39> EntryExpires: 100 RPF Route: 130.0.0.0/255.0.0.0 IIF: 107.0.8.4 UpNbr: 107.0.4.8 Pruned Oifs: Address: 108.0.8.5 IfId: 95 Pruned due to assert Pruned time remaining 130 <121.0.0.1, 224.0.1.40> EntryExpires: 102 Copyright © 2010, Juniper Networks, Inc.
Page 135 DR Addr—Address of the designated router SM—Number of PIM sparse mode interfaces DM—Number of PIM dense mode interfaces SM/DM—Number of PIM sparse-dense mode interfaces enabled—Number of interfaces administratively enabled disabled—Number of interfaces administratively disabled Copyright © 2010, Juniper Networks, Inc.
Page 136 Interface Name—Type and specifier of the interface to which the neighbor connects. For details about interface types and specifiers, see Interface Types and Specifiers in JunosE Command Reference Guide. Uptime—Time since the router discovered this neighbor in days hours:minutes:seconds format Copyright © 2010, Juniper Networks, Inc.
Page 137 RP mapping becomes invalid, unless the mapping agent (access list) reassigns the RP router to this group Example 1 host1:8#show ip pim rp mapping PIM Group-to-RP mapping(s) Group(s) 224.0.0.0/4 RP 122.0.0.1, priority 0, AutoRP, expiryTime 88 Group(s) 224.0.1.39/32 (negative) Copyright © 2010, Juniper Networks, Inc.
Page 138 Field descriptions (S, G) pair—Source, Group pair for which information is provided Group-to-RP mapping—IP addresses and network mask of the multicast group RP—IP address of RP router SSM group—Indicator that this is an SSM group Copyright © 2010, Juniper Networks, Inc.
Page 139 Local group membership present. <118.1.33.34, 232.0.0.1> SSM Group RPF Route: 118.1.0.0/255.255.0.0 IIF: 118.1.0.1 (Directly attached) Oifs: Register Oif to RP: 141.0.0.2 suppressed for SSM Group. Address: 134.0.0.1 Interface: ATM3/0.104 Joined as <S, G> Join Expires: 161 Copyright © 2010, Juniper Networks, Inc.
Page 140 Use to display the threshold for switching to the shortest path tree at a PIM designated router. Field descriptions Access List Name—Name of the IP access list that specifies the groups to which the threshold applies Copyright © 2010, Juniper Networks, Inc.
Page 141 SPT. A value of infinity indicates that PIM sparse mode never switches to an SPT. Example host1:2#show ip pim spt-threshold Access List Name SptThreshold(in kbps) ------------------------------------------------------- infinity See show ip pim spt-threshold. Copyright © 2010, Juniper Networks, Inc.
Page 143: Configuring Dvmrp
Preventing Dynamic Route Distribution on page 129 Exchanging DVMRP Unicast Routes on page 130 Disabling and Removing DVMRP on page 130 Clearing DVMRP Routes on page 131 Configuring DVMRP Tunnels on page 132 Monitoring DVMRP on page 132 Copyright © 2010, Juniper Networks, Inc.
Page 145: Platform Considerations
ERX310 Broadband Services Router: 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 DVMRP. Copyright © 2010, Juniper Networks, Inc.
Page 146: References
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. Copyright © 2010, Juniper Networks, Inc.
Page 147: Configuring Dvmrp Limits
Use the no version to restore the default value, 10,000 routes. See ip dvmrp route-hog-notification. 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 Copyright © 2010, Juniper Networks, Inc.
Page 148: Filtering Dvmrp Reports
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. Copyright © 2010, Juniper Networks, Inc.
Page 149: Changing The Metric For A Route
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. You can change the metric for an interface to promote or demote the preference for associated routes. ip dvmrp metric-offset Copyright © 2010, Juniper Networks, Inc.
Page 150: Importing Routes From Other Protocols
If you specify the route-map option, but no route map tags are listed, no routes are imported. Example—Importing routing information from BGP into DVMRP host1:boston(config-router)#redistribute bgp 100 route-map boston-map Copyright © 2010, Juniper Networks, Inc.
Page 151: Specifying Routes To Be Advertised
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. To prevent this dynamic redistribution, use the disable-dynamic-redistribute command. Copyright © 2010, Juniper Networks, Inc.
Page 152: Exchanging Dvmrp Unicast Routes
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. disable Copyright © 2010, Juniper Networks, Inc.
Page 153: Clearing Dvmrp Routes
Clearing DVMRP Routes You can clear one or more routes from the DVMRP routing table. However, if you do so, the routes might reappear in the routing table if they are rediscovered. clear ip dvmrp routes Copyright © 2010, Juniper Networks, Inc.
Page 154: Configuring Dvmrp Tunnels
Field descriptions Dvmrp Administrative State—State of DVMRP in the software: Enabled or Disabled Mcast Administrative State—State of multicasting in the software: Enabled or Disabled Dvmrp Version—Version of DVMRP with which this software is compatible Copyright © 2010, Juniper Networks, Inc.
Page 155 Interface—Type and specifier of the interface connected to a source. For details about interface types and specifiers, see Interface Types and Specifiers in JunosE Command Reference Guide. SourceAddress—IP address of the interface or, for an unnumbered interface, address of the loopback interface Copyright © 2010, Juniper Networks, Inc.
Page 156 Interface SourceAddress Network/Mask RBdPk RBdRt SntRt atm5/0.14 14.0.1.1 14.0.1.1/8 atm5/0.15 15.0.1.1 15.0.1.1/8 See show ip dvmrp interface. show ip dvmrp mroute Use to display information about DVMRP routes to multicast groups. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 157 Prune/P—Ability to send prune messages GenerationId/G—Ability to create a generation ID number Mtrace/M—Ability to trace multicast routes Netmask/N—Ability to send prunes and grafts with a network mask address Neighbor State/State—Status of communications with the neighbor Copyright © 2010, Juniper Networks, Inc.
Page 158 Specify an interface type and specifier to display routes associated with that interface. For details about interface types and specifiers, see Interface Types and Specifiers in JunosE Command Reference Guide. Specify the brief keyword to view a summary of information. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 159 Metric ExpireTime UpTime Interface 14.0.0.0/8 Dvmrp Local Never atm5/0.14 15.0.0.0/8 Dvmrp Local Never atm5/0.15 25.0.0.0/8 14.0.0.1 atm5/0.14 See show ip dvmrp route. show ip dvmrp routeNextHop Use to display information about the next hop. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 160 Type—Description of the next-hop router leaf—Neighbor with no downstream neighbors branch—Neighbor with downstream neighbors Example host1:boston>show ip dvmrp routeNextHop addr/mlen ifIndex Type 172.16.0.0/16 leaf 172.17.0.0/16 leaf 172.18.0.0/16 leaf 172.19.0.0/16 leaf 172.19.0.0/16 branch See show ip dvmrp routeNextHop. Copyright © 2010, Juniper Networks, Inc.
Page 161: Internet Protocol Version 6
PART 2 Internet Protocol Version 6 Configuring IPv6 Multicast on page 141 Configuring Multicast Listener Discovery on page 175 Configuring PIM for IPv6 Multicast on page 207 Copyright © 2010, Juniper Networks, Inc.
Page 163: Configuring Ipv6 Multicast
IPv6 defines three types of addresses: unicast, anycast, and multicast. Each type of address enables a device to send datagrams to selected recipients: A unicast address enables a device to send a datagram to a single recipient. Copyright © 2010, Juniper Networks, Inc.
Page 164: Reverse-Path Forwarding
When operating in sparse-mode, the routers perform an RPF lookup to identify the upstream router from which to request the data and then send join messages for the multicast stream only to that router. Copyright © 2010, Juniper Networks, Inc.
Page 165: Multicast Packet Forwarding
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 IPv6 multicasting. References For more information about IPv6 multicast, see the following resource: Copyright © 2010, Juniper Networks, Inc.
Page 166: Before You Begin
Use the no version to disable IPv6 multicast routing on the VR (the default). See ipv6 multicast-routing. 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. Copyright © 2010, Juniper Networks, Inc.
Page 167: Displaying Available Routes For Reverse-Path Forwarding
Prefix—Value of the logical AND of the IPv6 address of the destination network and the subnet address Length—Length of the subnet mask in bits Type Connect—Subnet directly connected to the interface Static—Static route Dst—Distance configured for this route Copyright © 2010, Juniper Networks, Inc.
Page 168: Enabling And Disabling Rpf Checks
Multicast routes established before you issue this command are not affected. ipv6 multicast-routing disable-rpf-check Use to disable RPF checks for specified (S,G) pairs. Specify a standard IPv6 access list that defines the (S,G) pairs. Example Copyright © 2010, Juniper Networks, Inc.
Page 169: Using Unicast Routes For Rpf
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. Example Copyright © 2010, Juniper Networks, Inc.
Page 170: Defining A Multicast Bandwidth Map
QoS adjustment, to be the actual measured rate of the stream. Using this feature to measure the actual bandwidth avoids the need to configure arbitrary bandwidth limits and enables Copyright © 2010, Juniper Networks, Inc.
Page 171: How Adaptive Mode Works
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) Copyright © 2010, Juniper Networks, Inc.
Page 172: Table 9: Adaptive Mode Algorithm Values
Number of history samples over which to compute measurement Samples Maximum number of samples maintained in history Percent Threshold value; percent difference by which a newly calculated rate must differ from the measured peak bandwidth before a rate update occurs Copyright © 2010, Juniper Networks, Inc.
Page 173: Multicast Bandwidth Map Example
When the router uses multicast OIF mapping, any multicast streams that a subscriber receives bypass any configured QoS treatment for that subscriber interface. The Multicast QoS adjust feature provides a way in which the router can account for this multicast traffic. Copyright © 2010, Juniper Networks, Inc.
Page 174: Multicast Oif Mapping Case
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, Copyright © 2010, Juniper Networks, Inc.
Page 175: Multicast Traffic Receipt Without Forwarding
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. See “Defining a Multicast Bandwidth Map” on page 148 for details. Copyright © 2010, Juniper Networks, Inc.
Page 176: Configuring Hardware Multicast Packet Replication
Figure 17 on page 155 displays how multicast traffic is typically replicated on the line module. Each of these replicated packets is transmitted from the line module to the I/O module or IOA. Copyright © 2010, Juniper Networks, Inc.
Page 177: Figure 17: Packet Flow Without Hardware Multicast Packet Replication
You can use the feature to increase the bandwidth of multicast traffic out of each of the Gigabit Ethernet ports. Figure 18 on page 156 displays the flow of a multicast packet using the hardware multicast packet feature. Copyright © 2010, Juniper Networks, Inc.
Page 178: Figure 18: Packet Flow With Optimized Multicast Packet Replication
This queue blocks when full and provides backpressure to the line module. This queue services unicast and multicast traffic that is not using the hardware multicast packet replication feature. Copyright © 2010, Juniper Networks, Inc.
Page 179: Supported Modules And Encapsulations
I/O module or IOA. The module then replicates this packet to the appropriate ports. For more information about configuring OIF mapping, see “Configuring Group Outgoing Interface Mapping” on page 184 in “Configuring Multicast Listener Discovery” on page 175. Copyright © 2010, Juniper Networks, Inc.
Page 180: Hardware Multicast Packet Replication Considerations
Therefore, you cannot apply different egress policies to multicast traffic for the interfaces stacked above different ports, or rate limit on an individual interface over a port. You also cannot monitor policy statistics on individual interfaces over a port. Copyright © 2010, Juniper Networks, Inc.
Page 181: Configuring Hardware Multicast Packet Replication
Create a VLAN major interface. Create a VLAN subinterface. Assign a VLAN ID. Configure an unnumbered IPv6 interface. Enable MLD on the interface with only multicast-data-forwarding capability. host1(config)#interface gigabitEthernet 2/8 host1(config-if)#encapsulation vlan host1(config-if)#interface gigabitEthernet 2/8.1 Copyright © 2010, Juniper Networks, Inc.
Page 182 Use the no version to disable hardware multicast packet replication. See ipv6 multicast ioa-packet-replication ipv6 unnumbered Use to configure an unnumbered IPv6 interface. This command enables IPv6 processing on an interface without assigning an explicit IPv6 address to the interface. Copyright © 2010, Juniper Networks, Inc.
Page 183: Monitoring Optimized Multicast Packet Replication
“Monitoring MLD” on page 190 in “Configuring Multicast Listener Discovery” on page 175. Blocking and Limiting Multicast Traffic You can either block mroute creation, limit the multicast bandwidth admitted on an outgoing interface, or limit outgoing interface creation on a port. Copyright © 2010, Juniper Networks, Inc.
Page 184: Blocking Mroutes
MLD. You can also use this command on a PIM (sparse-mode, dense-mode, or sparse-dense-mode) interface if MLD is configured on the interface (including the ipv6 mld version passive command). ipv6 multicast admission-bandwidth-limit Copyright © 2010, Juniper Networks, Inc.
Page 185: Oif Interface Reevaluation Example
Creating Mroute Port Limits When a multicast forwarding entry (that is, an mroute) is added with an outgoing interface (OIF) on a port, the OIF count for that port is incremented. If you configure a port limit Copyright © 2010, Juniper Networks, Inc.
Page 186: Limiting Port Admission Bandwidth
Use to configure a limit on the admission bandwidth of OIFs containing IPv4 or IPv6 mroutes, across different virtual routers, on a port. Example host1(config)#mroute port admission-bandwidth-limit 3000000 Use the no version to remove any OIF admission bandwidth limits. See mroute port admission-bandwidth-limit. Copyright © 2010, Juniper Networks, Inc.
Page 187: Oif Port Reevaluation Example
If you specify the IPv6 address of a multicast group and the IPv6 address of a multicast source, the router clears the multicast entry that matches that group and source. Example Copyright © 2010, Juniper Networks, Inc.
Page 188: Monitoring Ipv6 Multicast Settings
Incoming interface—Type and specifier of the incoming interface for the RPF route neighbor address—IPv6 address of the neighbor owner—Owner of the route Local—route belonging to the local interface Static—Static route Other protocols—Route established by a protocol Copyright © 2010, Juniper Networks, Inc.
Page 189 10:0:0:1::1, owner Local Incoming interface list: ATM2/3.1001 (10:0:0:1::1/64), Accept/Pim (RPF IIF) Outgoing interface list: ATM2/0.200 (21:2:2:21::2:1/60), Forward/Pim, 0 01:04:12/never (10:0:0:1:2::, ff0e::1) uptime 0 01:04:12 RPF route: 10:0:0:1::/64, incoming interface ATM2/3.1001 neighbor 10:0:0:1::1, owner Local Copyright © 2010, Juniper Networks, Inc.
Page 190 Admission bandwidth: 47000 bps (adaptive) QoS bandwidth: 47000 bps (adaptive) RPF route: 52::/112, incoming interface ATM2/1.17 neighbor 17::2, owner NetmgmtRpf Incoming interface list: ATM2/1.17 (fe80::90:1a00:3140:1ff8/128), Accept/MLD (RPF IIF) Outgoing interface list: NULL Counts: 1 (S, G) entries Copyright © 2010, Juniper Networks, Inc.
Page 191 Priority Port Limit Count BW bps Hysteresis Admitted ----- ----- ----- ----- -------- ---------- -------- 1/1/0 None None None 1/1/1 None 15000 10000 2000 See show mroute port count. show ipv6 mroute count Copyright © 2010, Juniper Networks, Inc.
Page 192 Forwarded—Number of packets and statistics that the VR has forwarded for this multicast route Rcvd on OIF—Number of packets and statistics that the VR has received on the OIF for this multicast route Example Copyright © 2010, Juniper Networks, Inc.
Page 193 Source Address—IP address of the multicast source RPF Route—IP address and network mask of the RPF route 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) mappings Copyright © 2010, Juniper Networks, Inc.
Page 194 MLD owns the interface. However, if you configure MLD and PIM on the same interface, PIM owns the interface. Registered interfaces—Includes the following information about interfaces on which the protocol is configured Copyright © 2010, Juniper Networks, Inc.
Page 195 Owned Interfaces—Number of interfaces that a protocol owns. If you configure only MLD on an interface, MLD owns the interface. However, if you configure MLD and PIM on the same interface, PIM owns the interface. Type—Mode of the multicast protocol Copyright © 2010, Juniper Networks, Inc.
Page 196: Bgp Multicast
VPN-IPv4, IPv6, and multicast IPv6. When you enable BGP, the router employs unicast IPv4 addresses by default. You should be thoroughly familiar with BGP before configuring MBGP. See Configuring BGP Routing in the JunosE BGP and MPLS Configuration Guide for detailed information about BGP and MBGP. Copyright © 2010, Juniper Networks, Inc.
Page 197: Configuring Multicast Listener Discovery
Disabling and Removing MLD on page 190 Monitoring MLD on page 190 MLD Proxy Overview on page 200 Configuring MLD Proxy on page 201 Setting the MLD Proxy Baseline on page 202 Monitoring MLD Proxy on page 203 Copyright © 2010, Juniper Networks, Inc.
Page 198: Overview
MLDv1 and MLDv2 mode interfaces send two types of multicast listener queries to hosts on the network: General queries to the all-nodes address (FF02::1) Specific queries to the appropriate multicast group address MLDv2 mode interfaces send the following type of queries to MLDv2 hosts: Copyright © 2010, Juniper Networks, Inc.
Page 199: Multicast Listener Reports
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 MLD. For information about modules that support MLD on the E120 and E320 Broadband Services Routers: Copyright © 2010, Juniper Networks, Inc.
Page 200: References
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. Copyright © 2010, Juniper Networks, Inc.
Page 201: Enabling Mld On An Interface
MLD owns that interface. If you configure MLD and PIM on an interface, the router determines that PIM owns the interface. In an MLDv1 or MLDv2 network, the querier is the router with the lowest IPv6 address. To start MLD, complete the following steps: Copyright © 2010, Juniper Networks, Inc.
Page 202: Configuring Mld Settings For An Interface
The time that a host can take to reply to a query (maximum response time) The number of times that the router sends each MLD message from this interface ipv6 mld immediate-leave Copyright © 2010, Juniper Networks, Inc.
Page 203 Example host1:boston(config-if)#ipv6 mld querier-timeout 200 Use the no version to set the time to the default, twice the query interval. See ipv6 mld querier-timeout. Copyright © 2010, Juniper Networks, Inc.
Page 204 Use a higher value to ensure high reliability from MLD. Specify a number in the range 1–4. Example host1:boston(config-if)#ipv6 mld robustness 2 Use the no version to restore the default, 3. See ipv6 mld robustness. Copyright © 2010, Juniper Networks, Inc.
Page 205: Specifying Multicast Groups
Use the MLD-Access-Src-Name RADIUS attribute (VSA 26-75) in RADIUS Access-Accept messages as an alternative method of configuring this value. Example host1:boston(config-if)#ipv6 mld access-source-group dallas-list Use the no version to remove any access list restriction. See ipv6 mld access-source-group. Copyright © 2010, Juniper Networks, Inc.
Page 206: Assigning A Multicast Group To An Interface
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. Example Copyright © 2010, Juniper Networks, Inc.
Page 207: Configuring Ssm Mapping
You can enter multiple ssm-map static commands for different access lists. Also, you can enter multiple ssm-map static commands for the same access list, as long as the access list uses different source addresses. SSM maps do not process statically configured groups. ipv6 mld ssm-map enable Copyright © 2010, Juniper Networks, Inc.
Page 209: Including And Excluding Traffic
MLDv2 is the industry-designated standard protocol for hosts to signal channel subscriptions in SSM. For additional information about SSM, see “PIM Source-Specific Multicast” on page 83. Copyright © 2010, Juniper Networks, Inc.
Page 210: Configuring Explicit Host Tracking
When the router is configured for explicit host tracking and starts performing immediate leave using the host information collected, every leave message received for a group or channel is treated as follows: Copyright © 2010, Juniper Networks, Inc.
Page 211 2 ip mld explicit-tracking ipv6 mld explicit-tracking Use to set explicit host tracking for MLD interfaces. To disable explicit host tracking if MLD V1 hosts are detected, use the disable-if-mld-detected keyword. Example Copyright © 2010, Juniper Networks, Inc.
Page 212: Disabling And Removing Mld
See ipv6 router mld. Monitoring MLD You can establish a reference point for MLD statistics by setting the statistics counters to zero. To display MLD parameters, use the show commands described in this section. Copyright © 2010, Juniper Networks, Inc.
Page 213 MLD Statistics Sent—Number of multicast listener queries sent Example host1:boston#show ipv6 mld Routing Process MLD, Administrative state enabled, Operational state Copyright © 2010, Juniper Networks, Inc.
Page 214 640:91d ff0e::4:1 ATM2/0.15 Version2 fe80::90:1a02:1 54 640:91d Included Sources: 51::1 51::2 Counts: 2 version-2, 0 version-1, 0 check state, 0 disabled (2 total) 0 excluded Source-groups: 2 included, 0 excluded Example 2—With OIF mapping Copyright © 2010, Juniper Networks, Inc.
Page 215 Administrative state—Status of the interface in the software: enabled or disabled Operational state—Physical status of the interface: enabled or disabled Version—MLD version State—Function of the interface: querier or nonquerier Query Interval—Time interval at which this interface sends query messages Copyright © 2010, Juniper Networks, Inc.
Page 216 Interface statistics Rcvd—Information about MLD messages received on this interface reports—Number of group multicast listener reports received leaves—Number of group multicast listener done messages received wrong version queries—Number of multicast listener queries received from devices running a different version of MLD Copyright © 2010, Juniper Networks, Inc.
Page 217 Immediate Leave: disabled Explicit Host Tracking: enabled Max-Group limit: No Limit Group Count: 0 IOA packet replication gigabitEthernet 3/8.1 Interface statistics: Rcvd: 0 reports, 0 leaves, 0 wrong version queries Sent: 14 queries Groups learned: 0 Copyright © 2010, Juniper Networks, Inc.
Page 218 OIF—Outgoing interface used in an OIF map Oper—Operation status of the outgoing interface Group Address—Multicast group IP address associated with the OIF Source Address—Source IP address associated with the OIF Join I/F—MLD protocol interface associated with the OIF Copyright © 2010, Juniper Networks, Inc.
Page 219 ATM5/0.130 See show ipv6 mld oif-map. show ipv6 mld membership Use to display MLD membership information for multicast groups and (S, G) channels. Specify the brief keyword to see a summary of the information. Copyright © 2010, Juniper Networks, Inc.
Page 220 02:41 FastEthernet2/1 ff0e::50 02:56 FastEthernet2/2 fe80::90:1a02:1640:911 02:30 fe80::90:1a02:1640:912 02:48 20::11 fe80::90:1a02:1640:913 02:56 20::12 fe80::90:1a02:1640:911 02:30 20::13 fe80::90:1a02:1640:911 02:30 fe80::90:1a02:1640:912 02:48 fe80::90:1a02:1640:913 02:56 ff0e::60 fe80::90:1a02:1640:901 01:56 FastEthernet2/3 10::10 02:45 10::11 02:35 10::12 02:15 10::14 stop Copyright © 2010, Juniper Networks, Inc.
Page 221 SSM Mapping—Status of SSM mapping on the interface (enabled or disabled) Group Address—Multicast group address requested Source List—List of sources mapped to the multicast group address Example host1:boston#show ipv6 mld ssm-mapping ff3e::1 SSM Mapping : Enabled Copyright © 2010, Juniper Networks, Inc.
Page 222: Mld Proxy Overview
MLD. You enable MLD on the interfaces that connect the router to its hosts that are farther away from the root of the tree. These interfaces are known as downstream interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 223: Configuring Mld Proxy
Use to enable MLD proxy on an interface. The interface for which you enable MLD proxy is the upstream interface. NOTE: You can enable only one upstream interface. Copyright © 2010, Juniper Networks, Inc.
Page 224: Setting The Mld Proxy Baseline
You can set the counters for the numbers of queries received and reports sent on the upstream interface to zero. This feature allows you to establish a reference point for MLD proxy statistics. baseline ipv6 mld-proxy interface Copyright © 2010, Juniper Networks, Inc.
Page 225: Monitoring Mld Proxy
Routing Process MLD Proxy, Administrative state enabled, Operational state enabled total 1 upstream interface, state enabled 1 multicast group See show ipv6 mld-proxy. show ipv6 mld-proxy groups Use to display information about multicast groups that MLD proxy reported. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 226 3/0. For details about interface types and specifiers, see Interface Types and Specifiers in JunosE Command Reference Guide. Specify the brief option to display a summary rather than a detailed description. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 227 Unsolicited report interval 100 (in 10ths of a second) 5 multicast groups Interface statistics: Rcvd: 0 v1 query, 0 v1 report, 25 v2 queries, 0 v2 report Sent: 0 v1 report, 0 v1 leave, 35 v2 reports Example 2 Copyright © 2010, Juniper Networks, Inc.
Page 228 JunosE 11.2.x Multicast Routing Configuration Guide host1#show ipv6 mld-proxy interface brief Interface Intf Address Ver State UnSlTime --------------- ------------------ --- -------------------- -------- ATM5/1.200 fe80::f7:0:231a:0 2 No v1 Router Present See show ipv6 mld-proxy interface. Copyright © 2010, Juniper Networks, Inc.
Page 229: Configuring Pim For Ipv6 Multicast
Removing PIM on page 221 Resetting PIM Counters and Mappings on page 222 Monitoring PIM on page 222 Overview This implementation of PIM supports PIM sparse mode and PIM source-specific multicast (PIM SSM) for IPv6 multicast. Copyright © 2010, Juniper Networks, Inc.
Page 230: Pim Sparse Mode
MLD. When the designated router no longer has any hosts that belong to a particular group, it sends a prune message to the RP. Timers PIM sparse mode uses timers to maintain the networking trees. Copyright © 2010, Juniper Networks, Inc.
Page 231: Pim Sparse Mode Bootstrap Router
You can use the ipv6 pim ssm range command to change the SSM group address range. Advantages that an SSM-configured network has over a traditionally configured PIM sparse mode network include the following: Copyright © 2010, Juniper Networks, Inc.
Page 232: Platform Considerations
RFC 2362—Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification (June 1998) RFC 3569—An Overview of Source-Specific Multicast (SSM) (July 2003) Source-Specific Multicast for IP—draft-ietf-ssm-arch-06.txt (March 2005 expiration) Source-Specific Protocol Independent Multicast in 232/8—draft-ietf-mboned-ssm232-08.txt (September 2004 expiration) Copyright © 2010, Juniper Networks, Inc.
Page 233: Before You Begin
Use the no version to remove PIM from the VR. See ipv6 router pim. pim disable Use to disable PIM processing. By default, PIM processing is enabled. Example host1:boston(config-router)#pim disable Use the no version to reenable PIM processing. See pim disable. Copyright © 2010, Juniper Networks, Inc.
Page 234: Enabling Pim On An Interface
PIM interfaces on the router. To 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. Copyright © 2010, Juniper Networks, Inc.
Page 235: Configuring The Pim Join/Prune Message Interval
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. To do so: Copyright © 2010, Juniper Networks, Inc.
Page 236: Configuring Bsr And Rp Candidates For Pim Sparse Mode
This mask is combined with the group address before the router calls the hash function. For example, specifying a value of 32 limits the group address to the first 32 bits. The default and maximum hash mask length is 126 bits. Copyright © 2010, Juniper Networks, Inc.
Page 237 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. See ipv6 pim rp-candidate. Copyright © 2010, Juniper Networks, Inc.
Page 238: Switching To An Spt For Pim Sparse Mode
PIM connection to a remote neighbor. host1(config-router-rn):boston#update-source atm 2/1.108 (Optional) Specify how often the router sends hello messages to the remote neighbor. host1(config-router-rn):boston#query-interval 40 Repeat Steps 2 to 3 for the other router. query-interval Copyright © 2010, Juniper Networks, Inc.
Page 239 1001::1 sparse-mode Specify the location of the interface that will transmit datagrams from router Boston to router Chicago. boston(config-router-rn)#update-source atm 2/1.108 Specify that router Boston will send hello messages to router Chicago every 40 seconds. Copyright © 2010, Juniper Networks, Inc.
Page 240: Using Pim Sparse Mode Join Filters
If an interface-level filter exists, it takes precedence over the global-level filter. Example 1 host1(config)#ipv6 pim join-filter gold Example 2 host1(config-interface)#ipv6 pim join-filter gold Use the no version to remove the filter association. See ipv6 pim join-filter. Copyright © 2010, Juniper Networks, Inc.
Page 241: Configuring Pim Ssm
PIM SSM also works with MLDv1 if you configure the ssm-map in MLD as in the following example: host1(config)#ipv6 pim ssm host1(config)#ipv6 access-list ssm_map1 permit any host ff3e::1 host1(config)#ipv6 mld ssm-map enable host1(config)#ipv6 mld ssm-map static ssm_map1 51::1 The no version disables ssm-map: host1(config)#no ipv6 mld ssm-map static ssm_map1 51::1 Copyright © 2010, Juniper Networks, Inc.
Page 242: Configuring The Bfd Protocol For Pim
BFD session to be down. NOTE: Before the router can use the ipv6 pim bfd-liveness-detection command, you must specify a BFD license key. To view an already configured license, use the show license bfd command. Copyright © 2010, Juniper Networks, Inc.
Page 243: Removing Pim
Removing PIM To remove PIM from a VR, use the no ipv6 router pim command. ipv6 router pim Use to create and enable PIM processing on a VR or to access Router Configuration mode. Example Copyright © 2010, Juniper Networks, Inc.
Page 244: Resetting Pim Counters And Mappings
You can use the debug PIM commands to view information about PIM events. debug ipv6 pim Use to show information about the selected event. To control the type of events displayed, specify a severity level. Copyright © 2010, Juniper Networks, Inc.
Page 245: Monitoring Pim Settings
Register Suppression Time—Period during which a designated router stops sending registers to the RP Register Probe Time—Time before register suppression time (RST) expires when a designated router might send a NULL-Register to the RP Copyright © 2010, Juniper Networks, Inc.
Page 246 Elected BSR—“ this router” or IP address of the elected bootstrap router next BSM—If BSR is “ this router,” time until the next bootstrap message is sent Copyright © 2010, Juniper Networks, Inc.
Page 247 Specify the summary keyword to view the number of configured, enabled, and disabled PIM sparse-mode interfaces. Specify the count keyword to view the number of multicast packets that the interface has sent and received. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 248 Example 2 host1#show ipv6 pim interface summary PIM Interface Summary 0, 0 enabled, 0 disabled Example 3 host1#show ipv6 pim interface count PIM Interface Count Interface Addr Interface Name ControlPktCount In|Out Hello JoinPrune Assert Copyright © 2010, Juniper Networks, Inc.
Page 249 OurEnd Addr—IPv6 address of local interface, such as the local endpoint of a tunnel, that transmits data to remote neighbor Ver—Version of PIM running on the local interface Mode—PIM mode running on the local interface; always PIM sparse mode Copyright © 2010, Juniper Networks, Inc.
Page 250 RP router was assigned (static, BSR) Example host1:8#show ipv6 pim rp mapping PIM Group-to-RP mapping(s) Group(s) ff00::/12 RP ::122:1, priority 0, static Group(s) ff0e::1:0/96 RP ::120:1, priority 0, static See show ipv6 pim rp show ipv6 pim rp-hash Copyright © 2010, Juniper Networks, Inc.
Page 251 (* ,G)—Mapping from any source to a specific group (* ,*,RP)—Mapping from any source to any group Join expires—Number of seconds before the (S,G) membership expires Count of entries—Total count of (S,G) pair mappings Copyright © 2010, Juniper Networks, Inc.
Page 252 Iif—Incoming interface for the unicast route Pref—Preference for the unicast route Metric—Value of metric for the unicast route (type of metric varies with the unicast protocol) Count of entries—Number of unicast routes that PIM sparse mode is using. Copyright © 2010, Juniper Networks, Inc.
Page 253 SPT. A value of infinity indicates that PIM sparse mode should never switch to an SPT. Example host1:2#show ipv6 pim spt-threshold Access List Name SptThreshold(in kbps) ------------------------------------------------------- infinity See show ipv6 pim spt-threshold. Copyright © 2010, Juniper Networks, Inc.
Page 258 ............58 ip igmp ssm-map enable..........52 IGMP proxy................69 ip igmp ssm-map static..........52 configuring................70 ip igmp static-exclude..........55 enabling................70 ip igmp static-group............51 ip igmp static-include...........55 Copyright © 2010, Juniper Networks, Inc.
Page 259 216 ipv6 block-multicast-sources........161 ipv6 pim................212 ipv6 mld robustness............182 ipv6 pim bsr-candidate..........214 ipv6 multicast-routing..........144 ipv6 pim join-filter............218 ipv6 multicast-routing disable-rpf-check..146 ipv6 pim query-interval..........212 Copyright © 2010, Juniper Networks, Inc.
Page 260 PIM SSM (PIM source-specific multicast) version................200 enabling..............103, 219 mrinfo requests, support for..........30 requirements for IGMPv3..........103 mtrace command..............39 requirements for MLDv2..........219 Protocol Independent Multicast. See PIM prune messages............79, 208 Copyright © 2010, Juniper Networks, Inc.
Page 261 RPF routes, monitoring...........7, 145 show ip pim data-mdt..........107 show ip pim dense-mode sg-state.......107 show ip pim interface..........107 set threshold command.............102 show ip pim neighbor..........107 show ip pim rp..............107 show ip pim rp-hash............107 show ip pim sparse-mode sg-state......107 Copyright © 2010, Juniper Networks, Inc.
Page 262 IP multicast groups..........50 specifying IPv6 multicast groups........183 SPTs (shortest path trees). See SRTs SRTs (source-rooted trees)....78, 92, 122, 207, 216 static routes configuring..............7, 144 summary addresses DVMRP routing..............126 support, technical See technical support Copyright © 2010, Juniper Networks, Inc.

Juniper JUNOSE 11.2.X MULTICAST ROUTING Configuration Manual

Chapter 1 Configuring Ipv4 Multicast

Chapter 2 Configuring IGMP

Chapter 3 Configuring PIM for Ipv4 Multicast

Chapter 4 Configuring DVMRP

Chapter 5 Configuring Ipv6 Multicast

Chapter 6 Configuring Multicast Listener Discovery

Chapter 7 Configuring PIM for Ipv6 Multicast

Quick Links

Related Manuals for Juniper JUNOSE 11.2.X MULTICAST ROUTING

Summary of Contents for Juniper JUNOSE 11.2.X MULTICAST ROUTING