banner



Home  ›  Which Mode Of Pim Uses A Rendezvous Point (Rp)?

Which Mode Of Pim Uses A Rendezvous Point (Rp)?

Written By Monday 28 March 2022 Add Comment Edit

Table Of Contents

Configuring a Rendezvous Point

Rendezvous Bespeak Overview

RP Configuration Overview

Sparse-Dense Style for Machine-RP

Auto-RP Filters

Recommended Methods for Configuring an RP

Car-RP with Multiple RPs Scenario

Configuration Files

BSR with Multiple RPs Scenario

Configuration Files

Anycast Static RP Scenario

Configuration Files

Anycast RP with Automobile-RP Scenario

Configuration Files

Related Documents


Configuring a Rendezvous Signal

Version History

Version Number

Date

Notes

i

03/15/2002

This certificate was created.


The purpose of this document is to outline 4 recommended methods for configuring a rendezvous indicate (RP) in a Protocol Independent Multicast sparse mode (PIM-SM) network. It provides scenario descriptions and bones configuration examples for each selection.

This document has the following sections:

•Rendezvous Point Overview

•RP Configuration Overview

•Recommended Methods for Configuring an RP

•Related Documents

Rendezvous Point Overview

A rendezvous point (RP) is required only in networks running Protocol Independent Multicast sparse mode (PIM-SM). The protocol is described in RFC 2362. In PIM-SM, just network segments with active receivers that have explicitly requested multicast data will exist forwarded the traffic. This method of delivering multicast data is in contrast to the PIM dense mode (PIM-DM) model. In PIM-DM, multicast traffic is initially flooded to all segments of the network. Routers that have no downstream neighbors or directly continued receivers prune back the unwanted traffic.

An RP acts as the meeting identify for sources and receivers of multicast data. In a PIM-SM network, sources must ship their traffic to the RP. This traffic is then forwarded to receivers down a shared distribution tree. By default, when the showtime hop router of the receiver learns about the source, information technology will transport a join message directly to the source, creating a source-based distribution tree from the source to the receiver. This source tree does not include the RP unless the RP is located within the shortest path between the source and receiver.

In about cases, the placement of the RP in the network is not a circuitous decision. By default, the RP is needed just to start new sessions with sources and receivers. Consequently, the RP experiences little overhead from traffic flow or processing. In PIM-SM version ii, the RP requires less processing than in PIM-SM version i because sources must only periodically annals with the RP to create country.

RP Configuration Overview

In the first version of PIM-SM, all leaf routers (routers direct continued to sources or receivers) were required to be manually configured with the IP accost of the RP. This blazon of configuration is also known as static RP configuration. Configuring static RPs is relatively easy in a small network, just it can be laborious in a large, complex network.

Following the introduction of PIM-SM version ane, Cisco implemented a version of PIM-SM with the Auto-RP feature. Machine-RP automates the distribution of grouping-to-RP mappings in a PIM network. To make Auto-RP work, a router must be designated as an RP mapping amanuensis, which receives the RP announcement messages from the RPs and arbitrates conflicts. The RP mapping amanuensis and so sends the consistent group-to-RP mappings to all other routers by dumbo way flooding. Thus, all routers automatically discover which RP to utilise for the groups they support. The Internet Assigned Numbers Authority (IANA) has assigned ii group addresses, 224.0.1.39 and 224.0.i.40, for Auto-RP. I advantage of Auto-RP is that any change to the RP designation must exist configured merely on the routers that are RPs and not on the leaf routers. Another advantage of Auto-RP is that it offers the ability to scope the RP accost inside a domain. Scoping can exist achieved by defining the time-to-live (TTL) value allowed for the Auto-RP advertisements.

Some other RP selection model called bootstrap router (BSR) was introduced after Motorcar-RP in PIM-SM version two. BSR performs similarly to Auto-RP in that it uses candidate routers for the RP function and for relaying the RP information for a group. RP information is distributed through BSR messages, which are carried within PIM letters. PIM letters are link-local multicast messages that travel from PIM router to PIM router. Because of this single hop method of disseminating RP data, TTL scoping cannot be used with BSR. A BSR performs similarly as an RP, except that information technology does not run the gamble of reverting to dumbo mode operation, and it does not offer the ability to scope within a domain.

Each method for configuring an RP has its own strengths, weaknesses, and level of complication. In conventional IP multicast network scenarios, we recommend using Automobile-RP to configure RPs because it is easy to configure, well-tested, and stable.

Thin-Dense Mode for Automobile-RP

A prerequisite of Car-RP is that all interfaces must be configured in sparse-dense mode using the ip pim thin-dense-mode interface configuration command. An interface configured in thin-dumbo mode is treated in either sparse manner or dense mode of operation, depending on which mode the multicast group operates. If a multicast grouping has a known RP, the interface is treated in sparse manner. If a group has no known RP, the interface is treated in dense mode and information will exist flooded over this interface.

To successfully implement Auto-RP and prevent whatsoever groups other than 224.0.ane.39 and 224.0.i.40 from operating in dumbo fashion, we recommend configuring a "sink RP" (likewise known every bit "RP of last resort"). A sink RP is a statically configured RP that may or may not actually exist in the network. Configuring a sink RP does not interfere with Auto-RP operation because, by default, Machine-RP messages supersede static RP configurations. We recommend configuring a sink RP for all possible multicast groups in your network, considering it is possible for an unknown or unexpected source to become agile. If no RP is configured to limit source registration, the group may revert to dense mode functioning and exist flooded with data.

Auto-RP Filters

When using Automobile-RP, configure the ip pim rp-announce-filter global configuration command on Auto-RP mapping amanuensis routers to filter Auto-RP announcement messages that make it on group 224.0.1.39 from candidate RP routers. This control prevents unwanted candidate RP announcement messages from beingness processed by the mapping agent. Unwanted messages could interfere with the RP election mechanism of the mapping agent.

Note Only routers configured as mapping agents subscribe to candidate RP proclamation messages. Therefore, the ip pim rp-announce-filter global configuration command is constructive only when configured on a mapping agent router. This command has no effect when configured on any other router.

The following example shows how to configure the router to accept announcements from RP addresses 10.0.0.1 and 10.0.0.2. This router is also configured to accept announcements for all groups. 

ip pim rp-announce-filter rp-list 1 group-list 2          
access-list one permit 10.0.0.1          
access-list ane permit 10.0.0.2          
access-list 2 permit 224.0.0.0 15.255.255.255

Recommended Methods for Configuring an RP

The following sections describe the four recommended methods for configuring an RP in a PIM-SM network. Sample configurations are likewise provided for each scenario. Figure 1 shows the network topology used for the sample configurations.

•Machine-RP with Multiple RPs Scenario

•BSR with Multiple RPs Scenario

•Anycast Static RP Scenario

•Anycast RP with Auto-RP Scenario

Figure 1 Network Topology Used for Sample Configurations

Note Unicast routing must be configured and stable in your network earlier implementing any of the sample configurations provided in the post-obit sections.

Note The sample configurations provided in the following sections employ boldface text to indicate pertinent configuration commands used for deploying the IP multicast scenarios described in this document.

Auto-RP with Multiple RPs Scenario

In this scenario, RP data is distributed to the routers by the Auto-RP machinery. For more information nearly Auto-RP, see the "RP Configuration Overview" department earlier in this document. A prerequisite of Machine-RP is that all interfaces must be configured in PIM sparse-dumbo fashion. For more information about using sparse-dense way with Auto-RP, encounter the "Sparse-Dumbo Mode for Auto-RP" department earlier in this document.

In the following sample configuration, routers 72a and 75a are configured equally both a candidate RP and RP mapping agent. At whatever given fourth dimension, but 1 RP accost is active (either per group or, as in the post-obit sample configuration, for all groups).

Having multiple candidates for the role of RP and mapping agent greatly enhances the redundancy of the PIM-SM network. Redundancy reduces the take a chance of groups (configured in thin-dumbo mode) reverting to dumbo mode operation if an RP cannot be located. To eliminate this risk, nosotros recommend configuring a sink RP on every router in the network. In the following sample configuration, a sink RP with the fictitious accost 1.i.1.ane is configured on all routers. For more information on sink RPs, see the "Sparse-Dense Way for Auto-RP" department before in this document.

For the Machine-RP with Multiple RPs scenario, no load balancing is provided, and, when an RP changes, convergence is normally on the order of 3 minutes.

The following relevant multicast commands are used in this scenario:

• ip pim thin-dense-mode

• ip pim rp-accost rp-address access-list

• ip pim send-rp-announce

• ip pim send-rp-discovery

Configuration Files

Router 36a 

ip address 20.0.seven.vi 255.255.255.0          
interface FastEthernet2/0          
ip accost 20.0.6.6 255.255.255.0          
            ip pim rp-address i.one.ane.1 20                      
            access-list twenty deny 224.0.1.39                      
            access-list xx deny 224.0.i.40                      
            access-list 20 permit 224.0.0.0 15.255.255.255

Router 36b 

ip address 20.0.seven.seven 255.255.255.0          
ip address 20.0.x.vii 255.255.255.0          
interface FastEthernet2/0          
ip address 20.0.eight.seven 255.255.255.0          
            ip pim rp-address 1.1.one.1 20                      
            admission-list 20 deny 224.0.1.39                      
            access-list twenty deny 224.0.ane.twoscore                      
            access-list 20 permit 224.0.0.0 xv.255.255.255

Router 36c 

ip address twenty.0.nine.ten 255.255.255.0          
ip address 20.0.x.10 255.255.255.0          
interface FastEthernet1/0          
ip address 20.0.3.10 255.255.255.0          
            ip pim rp-address 1.1.ane.1 20                      
            access-list 20 deny 224.0.1.39                      
            access-listing 20 deny 224.0.1.twoscore                      
            admission-list 20 permit 224.0.0.0 xv.255.255.255

Router 36d 

ip address 20.0.9.11 255.255.255.0          
ip address twenty.0.5.11 255.255.255.0          
            ip pim rp-address 1.1.1.1 20                      
            access-listing 20 deny 224.0.1.39                      
            access-listing 20 deny 224.0.ane.40                      
            access-list xx permit 224.0.0.0 15.255.255.255

Router 72a 

ip address 20.0.0.3 255.255.255.255          
interface FastEthernet0/0          
ip accost 20.0.i.3 255.255.255.0          
ip accost 20.0.3.three 255.255.255.0          
ip accost 20.0.two.3 255.255.255.0          
            ip pim rp-address 1.one.1.1 20                      
            ip pim send-rp-denote Loopback0 scope 32 group-list 10                      
            ip pim send-rp-discovery Loopback0 telescopic 32                      
            access-listing 10 allow 224.0.0.0 15.255.255.255                      
            access-list 20 deny 224.0.1.39                      
            access-list twenty deny 224.0.one.forty                      
            access-list 20 let 224.0.0.0 15.255.255.255

Router 75a 

            ip multicast-routing distributed                      
ip address 20.0.0.2 255.255.255.255          
interface FastEthernet0/0/0          
ip address 20.0.1.2 255.255.255.0          
ip route-cache distributed          
interface FastEthernet0/1/0          
ip address 20.0.6.2 255.255.255.0          
ip road-enshroud distributed          
            ip pim rp-accost 1.i.1.1 xx                      
            ip pim send-rp-announce Loopback0 scope 32 grouping-listing x                      
            ip pim transport-rp-discovery Loopback0 scope 32                      
            access-listing 10 permit 224.0.0.0 xv.255.255.255                      
            admission-list 20 deny 224.0.ane.39                      
            admission-list twenty deny 224.0.1.40                      
            access-list 20 permit 224.0.0.0 15.255.255.255

The following example shows output from the testify ip pim rp and show ip pim rp mapping commands. In this example, all groups are using 20.0.0.3 equally the RP address. This address was chosen by the RP mapping agent because it was the highest IP address. 

Group: 224.128.1.1, RP: 20.0.0.3, v2, v1, uptime 00:03:01, expires 00:02:50          
The RP has now changed to 20.0.0.3          
36b#            show ip pim rp mapping                      
Info source: 20.0.0.two (?), via Auto-RP          
Uptime: 00:22:08, expires: 00:02:forty

BSR with Multiple RPs Scenario

In this scenario, RP data is distributed to the routers by the BSR mechanism. For more data about the BSR machinery, encounter the "RP Configuration Overview" section earlier in this certificate.

In the post-obit sample configuration, routers 72a and 75a are configured as both a BSR candidate and an RP candidate. Having multiple candidates for the role of BSR and RP profoundly enhances the redundancy of the PIM-SM network. At any given time, only one RP accost is active (either per group or, as in the following sample configuration, for all groups).

For the BSR with Multiple RPs scenario, no load balancing is provided, and, when an RP changes, convergence is ordinarily on the order of 3 minutes.

The following relevant multicast commands areused in this scenario:

• ip pim sparse-mode

• ip pim bsr-candidate

• ip pim rp-candidate

Configuration Files

Router 36a 

ip address 20.0.7.half-dozen 255.255.255.0          
interface FastEthernet2/0          
ip accost 20.0.6.6 255.255.255.0

Router 36b 

ip address 20.0.7.7 255.255.255.0          
ip address xx.0.10.7 255.255.255.0          
interface FastEthernet2/0          
ip address 20.0.8.7 255.255.255.0

Router 36c 

ip address 20.0.9.ten 255.255.255.0          
ip accost 20.0.ten.10 255.255.255.0

Router 36d 

ip address 20.0.9.eleven 255.255.255.0          
ip address xx.0.5.11 255.255.255.0

Router 72a 

ip address 20.0.0.3 255.255.255.255          
interface FastEthernet0/0          
ip address 20.0.1.three 255.255.255.0          
ip address xx.0.3.3 255.255.255.0          
ip accost 20.0.2.3 255.255.255.0          
            ip pim bsr-candidate Loopback0 1                      
            ip pim rp-candidate Loopback0

Router 75a 

            ip multicast-routing distributed                      
ip address 20.0.0.two 255.255.255.255          
interface FastEthernet0/0/0          
ip accost 20.0.1.2 255.255.255.0          
interface FastEthernet0/1/0          
ip address 20.0.6.two 255.255.255.0          
            ip pim bsr-candidate Loopback0 1                      
            ip pim rp-candidate Loopback0

The following example shows output from the testify ip pim bsr command. The IP addresses of the two candidates for BSR are 20.0.0.2 and 20.0.0.iii. The 20.0.0.three accost is chosen equally the BSR considering it is the higher IP accost. 

PIMv2 Bootstrap information          
BSR address: twenty.0.0.3 (?)          
Uptime: 00:23:32, BSR Priority: 0, Hash mask length: 1          
This organization is a candidate BSR          
Candidate BSR accost: 20.0.0.ii, priority: 0, hash mask length: ane          
Next C and_RP_advertisement in 00:00:18

Anycast Static RP Scenario

In this scenario, Anycast RPs are configured statically and interfaces are configured to operate in PIM-SM. In Anycast RP, 2 or more RPs are configured with the "same" IP address on loopback interfaces. The Anycast RP loopback address should be configured with a 32-scrap mask, making information technology a host address. This scenario is like shooting fish in a barrel to configure and troubleshoot because the same host accost is used as the RP accost regardless of which router it is configured on.

Note The Interior Gateway Protocol (IGP) used in your network must support host addresses. Ensure that the loopback interface used for Anycast RP does not conflict with the loopback interface used to uniquely identify routers inside the IGP.

All the downstream routers should be configured to "know" that the Anycast RP loopback address is the IP address of their local RP. IP routing will automatically select the topologically closest RP for each source and receiver. Assuming that the sources are evenly distributed effectually the network, an equal number of sources will register with each RP. That is, the procedure of registering the sources will exist shared equally by all the RPs in the network.

In the post-obit sample configuration, routers 72a and 75a are configured equally Anycast RPs. Considering two routers are configured with the same RP accost, there is not a unmarried bespeak of failure. At any given time, simply one RP address is active (either per grouping or, as in the following sample configuration, for all groups).

Anycast RP provides excellent redundancy and load balancing. The load balancing is achieved through Multicast Source Discovery Protocol (MSDP), which allows RPs to exchange information about active sources.

For the Anycast Static RP scenario, when an RP changes, convergence is normally on the club of seconds.

Note In the post-obit sample configuration, an MSDP mesh group is configured. The apply of an MSDP mesh grouping is unnecessary when merely two Anycast RPs are configured. However, if in that location are more than than 2 Anycast RPs, you should configure MSDP mesh groups to prevent looping of Source-Active (SA) messages.

The post-obit relevant multicast commands are used in this scenario:

• ip pim sparse-mode

• ip pim rp-address rp-accost

• ip msdp peer {peer-address | peer-name} connect-source type number

• ip msdp mesh-group mesh-name {peer-address | peer-name}

• ip msdp originator-id blazon number

Configuration Files

Router 36a 

ip address 20.0.7.6 255.255.255.0          
interface FastEthernet2/0          
ip address xx.0.6.vi 255.255.255.0          
            ip pim rp-address 20.0.0.ane

Router 36b 

ip address 20.0.7.seven 255.255.255.0          
ip address xx.0.10.7 255.255.255.0          
interface FastEthernet2/0          
ip accost twenty.0.8.7 255.255.255.0          
            ip pim rp-address 20.0.0.1

Router 36c 

ip address xx.0.nine.10 255.255.255.0          
ip address 20.0.x.ten 255.255.255.0          
interface FastEthernet1/0          
ip address twenty.0.3.ten 255.255.255.0          
            ip pim rp-address 20.0.0.1

Router 36d 

ip accost 20.0.nine.11 255.255.255.0          
ip address xx.0.v.11 255.255.255.0          
            ip pim rp-accost twenty.0.0.1

Router 72a 

ip address 20.0.0.3 255.255.255.255          
ip address 20.0.0.ane 255.255.255.255          
interface FastEthernet0/0          
ip address 20.0.1.iii 255.255.255.0          
ip accost xx.0.three.three 255.255.255.0          
ip accost 20.0.ii.three 255.255.255.0          
            ip pim rp-address 20.0.0.i                      
            ip msdp peer 20.0.0.2 connect-source Loopback0                      
            ip msdp mesh-grouping anycast 20.0.0.2                      
            ip msdp originator-id Loopback0

Router 75a 

            ip multicast-routing distributed                      
ip address 20.0.0.2 255.255.255.255          
ip address 20.0.0.1 255.255.255.255          
interface FastEthernet0/0/0          
ip address 20.0.1.ii 255.255.255.0          
ip route-enshroud distributed          
interface FastEthernet0/1/0          
ip address xx.0.half dozen.2 255.255.255.0          
ip route-cache distributed          
            ip pim rp-accost 20.0.0.1                      
            ip msdp peer 20.0.0.3 connect-source Loopback0                      
            ip msdp mesh-group anycast 20.0.0.three                      
            ip msdp originator-id Loopback0

Anycast RP with Machine-RP Scenario

In this scenario, Anycast RP data is distributed to the routers by the Auto-RP mechanism. For more data about Anycast RP, see the "Anycast Static RP Scenario" section earlier in this certificate. For more than information about Auto-RP, see the "RP Configuration Overview" section earlier in this certificate. A prerequisite of Auto-RP is that all interfaces must be configured in PIM thin-dense mode. For more information virtually using thin-dense mode with Automobile-RP, see the "Sparse-Dense Mode for Auto-RP" section earlier in this document.

In the post-obit sample configuration, routers 72a and 75a are configured as Anycast RPs. Because ii routers are configured with the same RP address, there is not a unmarried bespeak of failure. At any given time, just one RP address is active (either per group or, equally in the following sample configuration, for all groups).

Anycast RP provides excellent redundancy and load balancing. The load balancing is achieved through Multicast Source Discovery Protocol (MSDP), which allows RPs to exchange information about active sources. Redundancy reduces the risk of groups (configured in thin-dumbo mode) reverting to dumbo mode performance if an RP cannot exist located. To eliminate this risk, nosotros recommend configuring a sink RP on every router in the network. In the following sample configuration, a sink RP with the fictitious accost i.1.1.one is configured on all routers. For more information on sink RPs, see the "Thin-Dense Style for Auto-RP" department before in this document.

For the Anycast RP with Auto-RP scenario, when an RP changes, convergence is normally on the club of seconds.

Notation In the following sample configuration, an MSDP mesh group is configured. The utilize of an MSDP mesh grouping is unnecessary when only two Anycast RPs are configured. However, if at that place are more than two Anycast RPs, you lot should configure MSDP mesh groups to forestall looping of SA messages.

The following relevant multicast commands are used in this scenario:

• ip pim sparse-dense-fashion

• ip pim rp-accost rp-address access-list

• ip pim send-rp-announce

• ip pim send-rp-discovery

• ip msdp peer {peer-address | peer-name} connect-source blazon number

• ip msdp mesh-group mesh-proper name {peer-accost | peer-proper name}

• ip msdp originator-id type number

Configuration Files

Router 36a 

ip address 20.0.7.6 255.255.255.0          
interface FastEthernet2/0          
ip address 20.0.6.6 255.255.255.0          
            ip pim rp-address i.i.1.1 20                      
            admission-listing twenty deny 224.0.1.39                      
            access-listing 20 deny 224.0.i.xl                      
            admission-list 20 let 224.0.0.0 15.255.255.255

Router 36b 

ip address 20.0.7.vii 255.255.255.0          
ip address 20.0.x.vii 255.255.255.0          
interface FastEthernet2/0          
ip address 20.0.8.7 255.255.255.0          
            ip pim rp-address 1.i.1.1 20                      
            access-list twenty deny 224.0.1.39                      
            access-list twenty deny 224.0.one.40                      
            access-listing 20 permit 224.0.0.0 15.255.255.255

Router 36c 

ip accost 20.0.9.10 255.255.255.0          
ip accost 20.0.x.x 255.255.255.0          
interface FastEthernet1/0          
ip accost twenty.0.iii.ten 255.255.255.0          
            ip pim rp-address 1.1.i.1 20                      
            access-list 20 deny 224.0.i.39                      
            admission-listing xx deny 224.0.1.40                      
            access-listing twenty permit 224.0.0.0 15.255.255.255

Router 36d 

ip address 20.0.9.11 255.255.255.0          
ip address 20.0.v.11 255.255.255.0          
            ip pim rp-address 1.1.1.1 20                      
            access-list 20 deny 224.0.i.39                      
            access-listing 20 deny 224.0.1.40                      
            access-list xx permit 224.0.0.0 fifteen.255.255.255

Router 72a 

ip accost twenty.0.0.three 255.255.255.255          
ip address 20.0.0.i 255.255.255.255          
interface FastEthernet0/0          
ip address twenty.0.1.three 255.255.255.0          
ip address xx.0.iii.3 255.255.255.0          
ip accost xx.0.2.3 255.255.255.0          
            ip pim rp-address 1.1.1.1 xx                      
            ip pim transport-rp-announce Loopback1 telescopic 32 group-list 10                      
            ip pim send-rp-discovery Loopback1 telescopic 32                      
            ip msdp peer 20.0.0.2 connect-source Loopback0                      
            ip msdp mesh-group anycast 20.0.0.2                      
            ip msdp originator-id Loopback0                      
            admission-list ten permit 224.0.0.0 15.255.255.255                      
            access-list xx deny 224.0.1.39                      
            access-list 20 deny 224.0.1.xl                      
            admission-list 20 permit 224.0.0.0 15.255.255.255

Router 75a 

            ip multicast-routing distributed                      
ip address 20.0.0.two 255.255.255.255          
ip accost xx.0.0.one 255.255.255.255          
interface FastEthernet0/0/0          
ip address twenty.0.ane.two 255.255.255.0          
ip route-cache distributed          
interface FastEthernet0/1/0          
ip address 20.0.6.2 255.255.255.0          
ip route-enshroud distributed          
            ip pim rp-address one.one.1.ane 20                      
            ip pim transport-rp-denote Loopback1 telescopic 32 grouping-list 10                      
            ip pim send-rp-discovery Loopback1 scope 32                      
            ip msdp peer xx.0.0.3 connect-source Loopback0                      
            ip msdp mesh-group anycast 20.0.0.three                      
            ip msdp originator-id Loopback0                      
            access-listing 10 permit 224.0.0.0 15.255.255.255                      
            access-list 20 deny 224.0.1.39                      
            admission-list 20 deny 224.0.1.40                      
            access-list xx allow 224.0.0.0 15.255.255.255

Related Documents

• Anycast RP, Cisco white paper

http://www.cisco.com/univercd/cc/td/physician/cisintwk/intsolns/mcst_sol/anycast.htm

• IP Multicast Applied science Overview, Cisco white paper

http://world wide web.cisco.com/univercd/cc/td/dr./cisintwk/intsolns/mcst_sol/mcst_ovr.htm

• Developing IP Multicast Networks, Cisco Press

• Cisco IOS IP Configuration Guide, Release 12.2

http://world wide web.cisco.com/univercd/cc/td/doctor/product/software/ios122/122cgcr/fipr_c/index.htm

• Cisco IOS IP Command Reference, Volume iii of 3: Multicast, Release 12.2

http://www.cisco.com/univercd/cc/td/doc/production/software/ios122/122cgcr/fiprmc_r/alphabetize.htm

•Cisco IOS Software Multicast Services web page

http://www.cisco.com/go/ipmulticast

•Cisco IOS Software IP Multicast Groups External Homepage

ftp://ftpeng.cisco.com/ipmulticast.html

Source: https://www.cisco.com/c/en/us/td/docs/ios/solutions_docs/ip_multicast/White_papers/rps.html

Posted by: perkinsamor1939.blogspot.com

0 Response to "Which Mode Of Pim Uses A Rendezvous Point (Rp)?"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel