Auto-Rendezvous Point (RP) provides administrators a way to distribute group-to-RP mappings within a multicast network without having to manually configure static RPs on every router.
To accomplish this, auto-RP uses these mechanisms:
Candidate RPs (C-RPs) send RP announcements to multicast group 188.8.131.52.
Mapping agents receive the RP announcements from C-RPs. They decide which should be the RP for any given group (or groups) based on the highest IP address. The mapping agents then distribute that information to all multicast routers to the auto-RP multicast group 184.108.40.206. This is done using using RP discovery messages.
The sending of both RP announcements and RP discovery messages occurs every 60 seconds by default with a holdtime of 180 seconds. If no RP is found, the next search is done locally on each router for a static RP mapping. If no static RP mapping is configured, the router defaults to dense mode.
An improperly-configured ip pim rp-announce-filter command may result in RP announcements being ignored. In addition, issuing the ip pim rp-announce-filter command on any other router but the mapping agent itself fails. This is because non-mapping agents do not listen to group 220.127.116.11. Even if non-mapping agents were to receive these messages, they still would not distribute the necessary group-to-RP mappings to everyone on the shared tree because they would not know what to do with them.
To resolve this issue, check the Protocol Independent Multicast (PIM) auto-RP mapping agent router for the ip pim rp-announce-filter command. Make sure the correct filters are set.
We'd like to learn a little about your network, your pain points with monitoring an enterprise network, and your preferred solution and workflow to solve issues.
We ask that you complete our brief survey: https://ciscoux.az1.qualtrics.com/jfe/form/SV...
Good day !I'm in the process of building a common configuration that I'm using to bootstrap multiple xrv 9k instances. The configuration comprises groups that are then applied in the relevant section. While I have verified that the groups are defined on s...
The first error we get is an error message that states: "SYS-2-MALLOCFAIL - Memory allocation of 962820 bytes failed from 0x8000561D10652750, alignment 8 Pool: Processor Free: 71887584 Cause: Memory fragmentation Alternate Pool: None Free: 0 Cause: N...
How to check Nexus 9K switches can be managed with Dnac current version 18.104.22.168 or not. Is there any possibility of checking compatibility with our existing version ? We want to deploy Nexus switches in DNAC tool with version 22.214.171.124, So please sugge...
Have you ever wondered why pluggable optics exist? Have you ever wondered what acronyms like QSFP, LR4, FEC, and PAM4 actually mean? In this episode I continue my conversation with my colleague Ray Nering. He explains to me how a lot of these came to be, ...