The PIM Assert mechanism prevents duplicate traffic from flowing into a multi-access network. Assert messages are sent by the two forwarding routers and the router with the best metric will win the assert. There are several known cases in which assert can cause temporary routing loops and sub optimal behavior."
At the moment I have 3 x routers in PIM-SM that talk Auto-RP and in a packet capture I am seeing many assert messages. I understand Assert is only used in Dense-mode, however Auto-RP floods in Dense mode to 188.8.131.52(RP-ANNOUNCE) & 184.108.40.206(RP-DISCOVER), which are the 'groups' my routers are trying to assert over.
We have had some issues in which Auto-RP traffic has been amplified in our carrier network and I'm trying to understand if the PIM Assert process could have a hand in that.
As a starting point, can anyone offer insight into how PIM Assert has the potential to cause routing loops?
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...