From: John Galt Kupec (jkupec2@xxxxxxxxxx)
Date: Mon Jun 05 2000 - 23:46:48 GMT-3
To follow up to my last post.
In the manually-config'ed RP situation, the RP itself doesn't
need to be told it's the RP. But in the Auto-RP and PIM Bootstrap
cases I guess you can say that in those scenarios you actually
do configure the RP to be an RP because you are configuring
the RP with "send-rp-announce" or "rp-candidate", respectively,
which is saying "I _can_ be an RP".
John Galt Kupec wrote:
>
> Scott Morris wrote:
> >
> > There's really not a specific command to configure a router as an RP as far
> > as I'm aware... You do, however, let all the other routers know who the RP
> > is, and it kinda auto-magically happens from there.
> >
> > Scott
>
> Right. The RP will infer that it _is_ the RP by virtue of
> the multicast traffic that it sees.
>
> But to define the RP on the other routers in the multicast
> network you can:
>
> Manually assign an RP address
> ip pim rp-address
> Use auto-rp
> ip pim send-rp-announce
> ip pim send-rp-discovery
> Use PIM v2 bootstrapping
> ip pim rp-candidate
> ip pim bsr-candidate
>
> On page 343 of "Developing IP Multicast Networks" by Williamson
> there's a note where he says:
>
> "...a router always assumes the duties of RP for a group (subject
> to a couple of conditions) any time it receives an incoming (*,G)
> Join that contains the address of one of its multicast-enabled
> interfaces in this field." (read the book!).
>
> John
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:40 GMT-3