Do you have a question about the JUNOSE SOFTWARE FOR E SERIES 11.3.X - MULTICAST ROUTING CONFIGURATION GUIDE 2010-10-07 and is the answer not in the manual?

Questions and answers

Summary of Contents for Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - MULTICAST ROUTING CONFIGURATION GUIDE 2010-10-07

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: Obtaining 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 4
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 123 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 143. 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 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
See ip multicast-routing bandwidth-map. 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. Copyright © 2010, Juniper Networks, Inc.
Page 40: Figure 4: Packet Flow Without Hardware Multicast Packet Replication
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). Configuring hardware multicast packet replication enables you to: 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
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. 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: Configuring Hardware Multicast Packet Replication With Oif-Mapping
For port 8, queue statistics have no direct relationship to any of the 8 ports because each packet transmitting through the queue can be sent through 1 or more of the 8 physical ports. For more information, see Monitoring Ethernet Interfaces in the JunosE Physical Layer Configuration Guide. Copyright © 2010, Juniper Networks, Inc.
Page 47: Ip And Vlan Statistics
NOTE: Issuing this command does not affect reception of link-local multicast packets. ip block-multicast-sources Use to prevent mroute creation by blocking multicast traffic that has a scope larger than link-local (for example, global). Example host1(config-if)#ip block-multicast-sources Copyright © 2010, Juniper Networks, Inc.
Page 48: Limiting Interface Admission Bandwidth
(S,G) streams become unblocked, is not specified. 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. Copyright © 2010, Juniper Networks, Inc.
Page 49: Creating Mroute Port Limits
(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). Copyright © 2010, Juniper Networks, Inc.
Page 50: Enabling Port Admission Bandwidth Control
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. Copyright © 2010, Juniper Networks, Inc.
Page 51: Oif Port Reevaluation Example
Use to delete IPv4 multicast forwarding entries. If you specify an *, the router clears all IP multicast forwarding entries. Copyright © 2010, Juniper Networks, Inc.
Page 52: Monitoring Ip Multicast Settings
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 Copyright © 2010, Juniper Networks, Inc.
Page 53 (S, G) uptime d h:m:s [Data rate: Kbps] [SPT Threshold: Kbps] [Threshold: Kbps] [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)] Copyright © 2010, Juniper Networks, Inc.
Page 54 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 Counts: 1 (S, G) entries 0 (*, G) entries See show ip mroute. Copyright © 2010, Juniper Networks, Inc.
Page 55 Use to display information about the number of groups and sources. Specify a multicast group address or both a multicast group address and a multicast source address to display information about a particular multicast forwarding entry. Copyright © 2010, Juniper Networks, Inc.
Page 56 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 IP Multicast Routing Table (S, G) uptime d h:m:s[, expires d h:m:s] [Admission bandwidth: bps] Copyright © 2010, Juniper Networks, Inc.
Page 57 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 Copyright © 2010, Juniper Networks, Inc.
Page 58 Admission-bandwidth—Actual admission bandwidth/configured admission bandwidth (in bps) QoS Adjust—Bandwidth of QoS adjustment, in bps Count—Number of multicast protocols on the VR Active <S,G> count—Number of active S,G data streams on the interface Copyright © 2010, Juniper Networks, Inc.
Page 59 IGMP on an interface, IGMP owns the interface. However, if you configure IGMP and either PIM or DVMRP on the same interface, PIM or DVMRP owns the interface. Type—Mode of the multicast protocol For DVMRP—Dense For PIM—Sparse, dense, or sparse-dense Copyright © 2010, Juniper Networks, Inc.
Page 60 Count—Number of mroute outgoing interfaces on the specified port BW bps—Bandwidth limit, in bits per second Priority BW bps—Priority bandwidth limit, in bits per second Admitted—Bandwidth admitted on the port, in bits per second Example Copyright © 2010, Juniper Networks, Inc.
Page 61: Support For Multicast Router Information
VPN-IPv4. When you enable BGP, the router employs unicast IPv4 addresses by default. We recommend you 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 62: Investigating Multicast Routes
Received mtrace response packet of length n—Length of the response packet, in bytes Each line of the trace has the following format: hops. ip-address Protocol: protocol FwdingCode:forwarding code hops—Number of hops from the destination to this intermediate router ip-address—IP address of the intermediate router Copyright © 2010, Juniper Networks, Inc.
Page 63 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 65: Configuring Igmp
Disabling and Removing IGMP on page 60 Monitoring IGMP on page 61 IGMP Proxy Overview on page 71 Configuring IGMP Proxy on page 72 Establishing the IGMP Proxy Baseline on page 74 Monitoring IGMP Proxy on page 74 Copyright © 2010, Juniper Networks, Inc.
Page 66: 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 67: 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 70: 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 71: 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 72 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. Example host1:boston(config-if)#ip igmp querier-timeout 200 Copyright © 2010, Juniper Networks, Inc.
Page 73 Use to specify the number of times that the router sends each IGMP message from this interface. 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 Copyright © 2010, Juniper Networks, Inc.
Page 75: 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 76: 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 77: 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 78 (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 79: 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 80: 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 81: 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 82: 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 83: 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 84 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 85 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 86 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 87 Interface statistics Groups learnt—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 88 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 learnt: 0 See show ip igmp interface. show ip igmp interface brief Copyright © 2010, Juniper Networks, Inc.
Page 89 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 90 <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 91 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 92 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 93: 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 94: 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 95 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 96: 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 97 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 98 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 101: Configuring Pim For Ipv4 Multicast
Using PIM Sparse Mode Join Filters on page 105 Configuring PIM SSM on page 105 Configuring the BFD Protocol for PIM on page 106 Removing PIM on page 108 Resetting PIM Counters and Mappings on page 108 Monitoring PIM on page 109 Copyright © 2010, Juniper Networks, Inc.
Page 102: 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 103: 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 82. Copyright © 2010, Juniper Networks, Inc.
Page 104: 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 83. Copyright © 2010, Juniper Networks, Inc.
Page 105: 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 106: 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 107: 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 108: 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 109: 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 110: 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 111: Configuring The Pim Join/Prune Message Interval
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 Copyright © 2010, Juniper Networks, Inc.
Page 112: Configuring An Rp Router For Pim Sparse Mode And Pim Sparse-Dense Mode
2 scope 16 group-list 1 Configuring an Auto-RP Router for 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 Copyright © 2010, Juniper Networks, Inc.
Page 113 Specify an access list that details which multicast groups the RP can include in announcement messages. Specify a time interval in the range 1–65535 seconds to control how often the router sends announcements. The default is 60 seconds. Example Copyright © 2010, Juniper Networks, Inc.
Page 114: Configuring Bsr And Rp Candidates For Pim Sparse Mode
BSR. The default value is 0 (address comparison only). 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. Copyright © 2010, Juniper Networks, Inc.
Page 115: Migrating To Bsr From Auto-Rp
After all routers are BSR-capable, switch from auto-RP to BSR as follows: 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. Copyright © 2010, Juniper Networks, Inc.
Page 116: Switching To An Spt For Pim Sparse Mode
(MTIs) explicitly. The MTI is an IP interface that is stacked on a GRE tunnel interface. The destination address of the GRE tunnel is the multicast VPN (MVPN) group address of the MDT. Copyright © 2010, Juniper Networks, Inc.
Page 117: Multicast Vpn Configuration Example
Networks routers. Tp is an unnumbered IP interface that is tied to the loopback interface of the provider edge router (PE). To configure the example, use the following general procedures: Copyright © 2010, Juniper Networks, Inc.
Page 118 Add PIM-SM to core-facing interfaces. host1:PE2(config)#interface atm2/1.20 host1:PE2(config-subif)#ip pim sparse-mode host1:PE2(config-subif)# Extend the BGP router configuration to contribute VPN routes into the multicast router table of the VRF using the ip route-type both command. Copyright © 2010, Juniper Networks, Inc.
Page 119 Configure the Tp interfaces in the parent router, PE2, as unnumbered PIM sparse-mode interfaces tied to the loopback interface, 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)# Copyright © 2010, Juniper Networks, Inc.
Page 120: Creating Multicast Vpns Using The Data Mdt
C-SG data on the default MDT to sending data on the data MDT. When the C-SG flow is switched to the data MDT, the Source C-PIM-SM starts a timer that you can configure using the mdt-data-holddown command to track the number of Copyright © 2010, Juniper Networks, Inc.
Page 121: Data Mdt Receivers
P-Group address. There might be one sender data MDT and possibly many receiver data MDTs sharing an IP tunnel. Each PE can assign MDT P-Groups from the same range, but the P-Group addresses must be administratively divided among the VPNs. Copyright © 2010, Juniper Networks, Inc.
Page 122: 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. Copyright © 2010, Juniper Networks, Inc.
Page 123: Configuring Data Mdts
To configure data MDTs: Configure a dynamic interface profile to specify the PIM configuration of the IP interface or 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 Copyright © 2010, Juniper Networks, Inc.
Page 124 233.3.2.255 host1:pe1(config)#ip pim group-address-pool pe13DataMdtSSMGroups 233.3.3.0 233.3.3.255 Configure the access list to match <S,G> and <*,G> entries. host1:pe1(config)#virtual-router pe1:pe13 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 Copyright © 2010, Juniper Networks, Inc.
Page 125 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. Copyright © 2010, Juniper Networks, Inc.
Page 126 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 127: 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 128: 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 129 The default value is 300 milliseconds. You can use the multiplier keyword to specify the detection multiplier value. The calculated BFD liveness detection interval can be different on each neighbor. The Copyright © 2010, Juniper Networks, Inc.
Page 130: 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 131: 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 132: 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 133 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 134 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 135 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 136 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 137 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 138 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 139 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 140 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 141 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 142 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 143 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 145: Configuring Dvmrp
Preventing Dynamic Route Distribution on page 132 Exchanging DVMRP Unicast Routes on page 132 Disabling and Removing DVMRP on page 133 Clearing DVMRP Routes on page 134 Configuring DVMRP Tunnels on page 134 Monitoring DVMRP on page 134 Copyright © 2010, Juniper Networks, Inc.
Page 147: 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 148: References
You must enable and configure DVMRP on one or more interfaces for DVMRP to function. See “Activating DVMRP on an Interface” on page 127. You can also set DVMRP limits for the VR; see “Configuring DVMRP Limits” on page 127. Copyright © 2010, Juniper Networks, Inc.
Page 149: Activating Dvmrp On An Interface
The warning alerts you so you can identify routers that are injecting large numbers of routes into the MBone. Example host1:boston(config)#ip dvmrp route-hog-notification 5000 Use the no version to restore the default value, 10,000 routes. See ip dvmrp route-hog-notification. Copyright © 2010, Juniper Networks, Inc.
Page 150: Filtering Dvmrp Reports
Specify a neighbor list to restrict the neighbors from which reports for routes on the first list can be accepted. Example host1:boston(config-if)#ip dvmrp accept-filter boston-list 4 neighbor-list boston-neighbors Use the no version to disable a filter. See ip dvmrp accept-filter. Copyright © 2010, Juniper Networks, Inc.
Page 151: Configuring Dvmrp Summary Addresses
Use the metric keyword to specify a DVMRP metric (hop count); the default metric value is 1. Example host1:boston(config-if)#ip dvmrp summary-address 192.48.1.2 255.255.255.0 metric Use the no version to stop advertising a summary address on the interface. See ip dvmrp summary-address. Copyright © 2010, Juniper Networks, Inc.
Page 152: Changing The Metric For A Route
Specify the source protocol from which routes are being redistributed. It can be one of the following keywords: bgp, isis, ospf, static, or connected. Use the static keyword to redistribute static IP multicast routes into DVMRP. Copyright © 2010, Juniper Networks, Inc.
Page 153: Specifying Routes To Be Advertised
The IP access list defines the DVMRP routes that are advertised. ip dvmrp announce-filter Use to specify the DVMRP routes for an interface to advertise. Specify a standard IP access list of routes for the interface to advertise. Example host1:boston(config-if)#ip dvmrp announce-filter boston-list Copyright © 2010, Juniper Networks, Inc.
Page 154: Preventing Dynamic Route Distribution
All interfaces, including tunnels, support DVMRP unicast routing. DVMRP tunnels use DVMRP multicast routing to support DVMRP unicast routing. ip dvmrp unicast-routing Use to enable the exchange of DVMRP unicast routes on an interface not owned by DVMRP. Example host1:boston(config-if)#ip dvmrp unicast-routing Copyright © 2010, Juniper Networks, Inc.
Page 155: Disabling And Removing Dvmrp
Use the no version to reenable DVMRP processing on an interface. See ip dvmrp disable. router dvmrp Use to create and enable DVMRP processing on a VR or to access Router Configuration mode. Example Copyright © 2010, Juniper Networks, Inc.
Page 156: Clearing Dvmrp Routes
You can display DVMRP information with the show ip dvmrp commands. baseline ip 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 Copyright © 2010, Juniper Networks, Inc.
Page 157 Enabled Dvmrp Version: 3.255 Generation ID: 0x46828e2b Number of Routes: Number of Triggered Routes: 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) Copyright © 2010, Juniper Networks, Inc.
Page 158 IP access lists that specify the sources for which the interface accepts routes Example 1 host1:v3#show ip dvmrp interface Interface: ATM2/0.1 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 Copyright © 2010, Juniper Networks, Inc.
Page 159 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. Copyright © 2010, Juniper Networks, Inc.
Page 160 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 Copyright © 2010, Juniper Networks, Inc.
Page 161 Example 1 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) Copyright © 2010, Juniper Networks, Inc.
Page 162 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 163: Internet Protocol Version 6
PART 2 Internet Protocol Version 6 Configuring IPv6 Multicast on page 143 Configuring Multicast Listener Discovery on page 179 Configuring PIM for IPv6 Multicast on page 211 Copyright © 2010, Juniper Networks, Inc.
Page 165: 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 166: 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 167: 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 168: 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 169: 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 170: 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 171: 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 172: Defining A Multicast Bandwidth Map
(for low-action programs) to 10 Mbps (for a fast-paced, high-action programs). The auto-sense mechanism allows the bandwidth value, used for admission control and QoS adjustment, to be the actual measured rate of the stream. Using this feature to measure Copyright © 2010, Juniper Networks, Inc.
Page 173: 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 174: Table 9: Adaptive Mode Algorithm Values
Sampling period; the time in which a sample is taken 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 Copyright © 2010, Juniper Networks, Inc.
Page 175: Multicast Bandwidth Map Example
For additional information about configuring interface- and port-level admission control, see “Blocking and Limiting Multicast Traffic” on page 164. For additional information about creating route maps, see Configuring Routing Policy in the JunosE IP Services Configuration Guide . Copyright © 2010, Juniper Networks, Inc.
Page 177: Multicast Traffic Receipt Without Forwarding
OIF list) and the router applies the QoS adjustment to the join interface. See Figure 16 on page 156. 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 178: Activating Multicast Qos Adjustment Functions
See ipv6 multicast-routing bandwidth-map. Configuring Hardware Multicast Packet Replication You can configure IPv6 multicast to replicate packets to optimized hardware on a logical port instead of using the forwarding controller (FC) on the router. Copyright © 2010, Juniper Networks, Inc.
Page 179: Figure 17: Packet Flow Without Hardware Multicast Packet Replication
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). Configuring hardware multicast packet replication enables you to: Copyright © 2010, Juniper Networks, Inc.
Page 180: Figure 18: Packet Flow With Optimized 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 181: Supported Modules And Encapsulations
NOTE: 802.3ad link aggregation group (LAG) bundles do not support optimized multicast packet replication. The optimized 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 182: Relationship With Oif Mapping
MAC address that you configured. For more 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. Copyright © 2010, Juniper Networks, Inc.
Page 183: 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. Copyright © 2010, Juniper Networks, Inc.
Page 184 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 Copyright © 2010, Juniper Networks, Inc.
Page 185: Monitoring Optimized Multicast Packet Replication
The statistics for the IPv6 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 186 (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 interface. Copyright © 2010, Juniper Networks, Inc.
Page 187 However, no new OIFs are admitted until the total admitted bandwidth drops below the configured limit. 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. Copyright © 2010, Juniper Networks, Inc.
Page 188 CAUTION: Before you can limit port-level admission bandwidth, you must first create a bandwidth map. See “Defining a Multicast Bandwidth Map” on page 150 for details. Copyright © 2010, Juniper Networks, Inc.
Page 189 OIFs but prevents the interfaces from accepting any more groups. Over time, some groups leave the interfaces and, eventually, the port limit of 2000000 bps is reached and maintained by the router. Copyright © 2010, Juniper Networks, Inc.
Page 190 Use the active option to display the active multicast routes with admission bandwidth greater than the specified bandwidth threshold. The default is 4000 bps. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 191 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 entry, in days hours:minutes:seconds format Counts—Numbers of types of source group mappings (S,G)—Number of (S,G) entries Copyright © 2010, Juniper Networks, Inc.
Page 192 Example 1—Displays active multicast routes with bandwidth above 10000 bps host1#show ipv6 mroute active 10000 Active IP Multicast Routes >=10000 bps (S, G) uptime d h:m:s[, expires d h:m:s] [Admission bandwidth: bps] [QoS bandwidth: bps] RPF route: addr/mask, incoming interface Copyright © 2010, Juniper Networks, Inc.
Page 193 See show ipv6 mroute. show mroute port count Use to display the mroute port outgoing interface, limits, and counts. NOTE: This command displays information for mroutes on a port across all virtual routers. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 194 Specify a multicast group IPv6 address or both a multicast group IPv6 address and a multicast source IPv6 address to display information about a particular multicast forwarding entry. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 195 (10:0:0:1:2::, ff0e::1) uptime 0 01:05:23 RPF route: 10:0:0:1::/64, incoming interface ATM2/3.1001 neighbor 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:05:26/never Statistics: Received : 346 pkts, 22144 bytes Copyright © 2010, Juniper Networks, Inc.
Page 196 ATM2/3.1001 ff0e::1 10:0:0:1:c:: 10:0:0:1::/64 ATM2/3.1001 ff0e::1 10:0:0:1:d:: 10:0:0:1::/64 ATM2/3.1001 ff0e::1 10:0:0:1:e:: 10:0:0:1::/64 ATM2/3.1001 ff0e::1 10:0:0:1:f:: 10:0:0:1::/64 ATM2/3.1001 Counts: 16 (S, G) entries 0 (*, G) entries See show ipv6 mroute. show ipv6 multicast protocols Copyright © 2010, Juniper Networks, Inc.
Page 197 ATM2/1.103 (21:2:2:22::1:2/60) owner Pim Protocol Mld Type: Local Interfaces: 1000 registered, 1000 owned Registered interfaces: ATM2/0.131 (31:2:2:22::2:2/604) local Mld owner Mld Admission-bandwidth 2000000/10000000 bps QoS Adjust 2000 bps ATM2/0.132 (31:2:2:22::2:3/60) local Mld owner Mld Copyright © 2010, Juniper Networks, Inc.
Page 198 Multicast cache-miss processing is enabled on this router Multicast forwarding is enabled on this router Multicast graceful restart is complete (timer 0 seconds) on this router Multicast cache-miss processing is enabled on this router Copyright © 2010, Juniper Networks, Inc.
Page 199 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 201: Chapter 6 Configuring Multicast Listener Discovery
Disabling and Removing MLD on page 194 Monitoring MLD on page 194 MLD Proxy Overview on page 204 Configuring MLD Proxy on page 205 Setting the MLD Proxy Baseline on page 206 Monitoring MLD Proxy on page 207 Copyright © 2010, Juniper Networks, Inc.
Page 202 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 203 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 204: Figure 19: Static And Dynamic Mld Interfaces
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 205: Table 10: Static Mld Commands
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 206 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 207 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. Example host1:boston(config-if)#ipv6 mld querier-timeout 200 Copyright © 2010, Juniper Networks, Inc.
Page 208 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 209 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 210 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 211 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 213 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 85. Copyright © 2010, Juniper Networks, Inc.
Page 214 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 215 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 216 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 218 ATM2/0.15 Version2 fe80::90:1a02:1 54 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 Copyright © 2010, Juniper Networks, Inc.
Page 219 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 Copyright © 2010, Juniper Networks, Inc.
Page 220 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 221 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 learnt: 0 Copyright © 2010, Juniper Networks, Inc.
Page 222 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 223 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 224 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 225 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 226 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 227: Figure 20: Upstream And Downstream Interfaces
(Optional) Specify how often the router should send unsolicited reports to routers on the upstream interface. ipv6 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 228 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 229 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 230 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 231 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 232 JunosE 11.3.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 233: Monitoring Pim Settings
Removing PIM on page 225 Resetting PIM Counters and Mappings on page 226 Monitoring PIM on page 226 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 234: Figure 21: Source-Rooted Tree
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 235 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 236 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 237: Enabling And Disabling Pim On A Vr
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 238 The ipv6 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 ipv6 pim dr-priority command in Interface Configuration mode. Copyright © 2010, Juniper Networks, Inc.
Page 239 PIM join/prune message; the default value is 60 seconds. Examples In Router Configuration mode: host1(config-if)#ipv6 pim join-prune-interval 150 In Interface Configuration mode: host1(config-subif)#ipv6 pim join-prune-interval 150 Use the no version to restore the default value, 60 seconds. Copyright © 2010, Juniper Networks, Inc.
Page 240 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. Copyright © 2010, Juniper Networks, Inc.
Page 241 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 Copyright © 2010, Juniper Networks, Inc.
Page 242 Specify the location of the local interface whose address is used as the source address for the 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. Copyright © 2010, Juniper Networks, Inc.
Page 243 To configure the routers as PIM remote neighbors: Specify that router Chicago will be a remote neighbor of router Boston, and identify the IP address on router Chicago that will transmit datagrams to router Boston. boston(config-router)#remote-neighbor 1001::1 sparse-mode Copyright © 2010, Juniper Networks, Inc.
Page 244 You can apply the join filter at the global level or at the interface level. 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 Copyright © 2010, Juniper Networks, Inc.
Page 245: Figure 22: Network On Which To Configure 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 Copyright © 2010, Juniper Networks, Inc.
Page 246 The negotiated value can be different on each neighbor. Each neighbor then calculates a BFD liveness detection interval. When a neighbor does not receive a BFD packet within the detection interval, it declares the BFD session to be down. Copyright © 2010, Juniper Networks, Inc.
Page 247 800 Use the no version to disable BFD on the PIM interface. See ipv6 pim bfd-liveness-detection. Removing PIM To remove PIM from a VR, use the no ipv6 router pim command. Copyright © 2010, Juniper Networks, Inc.
Page 248 If you do not specify an interface, the router clears the counters on all interfaces. Example host1#clear ipv6 pim remote-neighbor 1001::1 count There is no no version. See clear ipv6 pim remote-neighbor. Monitoring PIM You can display information about PIM events and parameters. Copyright © 2010, Juniper Networks, Inc.
Page 249 PIM router Join-Prune Holdtime— Hold time value (in seconds) set in the join/prune message originated by the PIM router. The hold time is 3.5 times the PIM join/prune message interval value. Copyright © 2010, Juniper Networks, Inc.
Page 250 RP in a PIM sparse mode environment. Field descriptions Candidacy—Whether or not the router is a candidate BSR Configured on—Interface on which the router is configured address—Address of the router hashMaskLen—Hash mask length priority—Priority of the router Copyright © 2010, Juniper Networks, Inc.
Page 251 Specify the detail keyword to view detailed information for all PIM interfaces or for a specified PIM interface. Specify the summary keyword to view the number of configured, enabled, and disabled PIM sparse-mode interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 252 Count Intvl Intvl 101::1 ATM2/0.100 Sparse 101::2 102::1 ATM2/0.101 Sparse 102::2 silver 103::1 ATM3/0.102 Sparse 103::1 gold Example 2 host1#show ipv6 pim interface summary PIM Interface Summary 0, 0 enabled, 0 disabled Example 3 Copyright © 2010, Juniper Networks, Inc.
Page 253 Use to view information about PIM remote neighbors. Field descriptions Remote Nbr Addr—IPv6 address of remote neighbor OurEnd Addr—IPv6 address of local interface, such as the local endpoint of a tunnel, that transmits data to remote neighbor Copyright © 2010, Juniper Networks, Inc.
Page 254 RP—IP address of 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:8#show ipv6 pim rp mapping PIM Group-to-RP mapping(s) Group(s) ff00::/12 RP ::122:1, priority 0, static Copyright © 2010, Juniper Networks, Inc.
Page 255 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 Copyright © 2010, Juniper Networks, Inc.
Page 256 Use to display the unicast routes that PIM sparse mode is using. Field descriptions Route—IPv6 address and network mask for the unicast route RpfNbr—RPF neighbor Iif—Incoming interface for the unicast route Copyright © 2010, Juniper Networks, Inc.
Page 257 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 262 ............60 ip igmp ssm-map enable..........54 IGMP proxy..................71 ip igmp ssm-map static..........54 configuring.................72 ip igmp static-exclude..........57 enabling................72 ip igmp static-group............53 ip igmp static-include...........57 Copyright © 2010, Juniper Networks, Inc.
Page 263 220 ipv6 block-multicast-sources.........164 ipv6 pim................216 ipv6 mld robustness...........186 ipv6 pim bsr-candidate..........218 ipv6 multicast-routing..........146 ipv6 pim join-filter............222 ipv6 multicast-routing disable-rpf-check..148 ipv6 pim query-interval..........216 Copyright © 2010, Juniper Networks, Inc.
Page 264 PIM SSM (PIM source-specific multicast) version................204 enabling..............105, 223 mrinfo requests, support for..........30 requirements for IGMPv3..........105 mtrace command..............40 requirements for MLDv2..........223 Protocol Independent Multicast. See PIM prune messages...............81, 212 Copyright © 2010, Juniper Networks, Inc.
Page 265 RPF routes, monitoring............7, 147 show ip pim data-mdt..........109 show ip pim dense-mode sg-state.......109 show ip pim interface..........109 set threshold command.............104 show ip pim neighbor..........109 show ip pim rp...............109 show ip pim rp-hash...........109 show ip pim sparse-mode sg-state......109 Copyright © 2010, Juniper Networks, Inc.
Page 266 IP multicast groups...........52 specifying IPv6 multicast groups........187 SPTs (shortest path trees). See SRTs SRTs (source-rooted trees).....80, 94, 124, 211, 220 static routes configuring..............7, 146 summary addresses DVMRP routing..............129 support, technical See technical support Copyright © 2010, Juniper Networks, Inc.

This manual is also suitable for:

Junose 11.3

Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - MULTICAST ROUTING CONFIGURATION GUIDE 2010-10-07 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

Need help?

Questions and answers

Related Manuals for Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - MULTICAST ROUTING CONFIGURATION GUIDE 2010-10-07

Summary of Contents for Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - MULTICAST ROUTING CONFIGURATION GUIDE 2010-10-07

This manual is also suitable for:

Table of Contents