Multicast RP Recovery Time...what is default behavior?

Unanswered Question
Oct 23rd, 2008

In an AnyCast AutoRP setup, what is a typical (default) RP recover time?

I have an initial (defaults) multicast lab configuration using these mechanisms and when I interrupt a path OSPP/BGP recover unicast with almost no interruption. However, the multicast stream from same source stays down for 1.25 minutes.

I want to know if this is normal and if so, what tweaks are needed to improve what appears to be an RP election/response.

Seeing a timer count down with 'debug ip mpacket' "Next RP reachable timer..."

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Giuseppe Larosa Fri, 10/24/2008 - 04:23

Hello Mike,

the PIM source DR, the router connected to the source, verify every 60 seconds RP reachability by sending a register message and then waiting for an answer.

So 75 seconds is the time to detect the RP failure, the network infrastructure will send next register messages to new RP.

It takes time to build the SPT to the RP.

And there is the time for the AutoRP messages to propagate.

I've found a suggestion about using ip pim autorp-listener to achieve fast RP switchover

Use combined Anycast-RP & Auto-RP with autorplistener:

-When rapid RP failover is critical

-When dynamic Group/RP cache required

-When Admin scoping is required

Or even to use static RP commands with anycast-RP

Use combined Anycast-RP with Static:

-When rapid RP failover is critical

-When valid Group/RP cache is critical at all times

-No requirement for dynamic Group/RP cache


Hope to help



This Discussion