Re: [pim] anycast-rp with pim (rfc4610) when an RP reboots
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pim] anycast-rp with pim (rfc4610) when an RP reboots
Pekka,
Two points, I did not understand fully,
1. When RP2 reboots, the receivers which were earlier to RP1 would re-learn the RP route and would try to reach RP1, right. I believe, that would be taken care by the underlying routing mechanism.
2. And when RP2 reboots, the MSDP session between them would break and comes back again once RP1 comes back. And MSDP would send the SA advertisements for every 60 sec. So, eventually, the router would get populated with SAs.
Regards,
Mani.
-----Original Message-----
From: pim-bounces at ietf.org [mailto:pim-bounces at ietf.org] On Behalf Of Pekka Savola
Sent: Wednesday, October 14, 2009 11:54 AM
To: pim at ietf.org
Subject: [pim] anycast-rp with pim (rfc4610) when an RP reboots
Hello,
My colleague started thinking on this and it seems there is a caveat
in the use of PIM for anycast-rp compared to MSDP.
Assume a stable state of 10 sources with two RPs in an anycast-RP set.
Both RPs have information about all sources. All sources are closer
to RP_1. All receivers are attached to RP_2.
Now, RP_2 reboots. RP_1 does not know that the router has rebooted.
In consequence, it does not re-register sources to RP_2 until DRs
restart registering. In consequence, the receivers attached to RP_2
do not get the transmissions after routing reconverges to RP_2.
Did I get this right? Are there any mitigations for this? PIM-PORT
could offer a way to fix this, obviously, but it may a bit far off
yet.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
pim mailing list
pim at ietf.org
https://www.ietf.org/mailman/listinfo/pim
DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.