i have played around with this auto-rp a bit and it seems to me that it is on auto-magiclly as it is just a cisco thing, pre-bsr pimv2 to solve the problem of static rp
and have seen that in this type of basic setup with broadcast segments like this that it will work as long as you set the scope high enough on the rp-annouce for it to make it to the end of the line... try changing the rp-annouce scope to 1 and you will see it will not make it to R1 anymore from R2, as you would expect... so i think the answer is no you do not need it for it to "work" but if you want it to "work and be supported and get points in a lab" then the answer is yes it is needed because it is the fix to get rid of the sparse-dense mode that was needed prior to this command... HTH, garry.. -- Garry L. Baker "There is no 'patch' for stupidity." - www.sqlsecurity.com On Sat, Aug 14, 2010 at 9:14 PM, jason lau <[email protected]> wrote: > in the Multicase Configuration lab, topology is R2 -- R4--- R1, R2 is RP > and mapping agent, all routers' interfaces are in PIM sparse mode.according > to docs, when R4 receives 224.0.1.40 traffic, it won't pass it to R1, the > solution is config PIM auotp listener on R4, so R4 can flood 224.0.1.40 to > R1. > > However, in my lab, why without PIM auotp listener command on any router, > R1 still receive 224.0.1.40 and get correct RP mapping? as I said, NO any > interface is in sparse-dense mode, all are in spare mode. > > Thanks > > Jason > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
