Any ideas on why this error remains?

On Sat, Sep 25, 2010 at 11:31 AM, Jay Taylor <[email protected]> wrote:

> Working on this multicast ticket and when it appears to be complete I'm
> still seeing an error message that I'm not sure about.
>
> Before working on the ticket I had the following errors happening
> periodically and I see that Marko had them in the video solution as well:
>
> Sep 25 14:10:39.391: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.1.40) Join
> from 192.0.47.7 for invalid RP 192.0.0.4
> R4(config-router)#
> Sep 25 14:12:35.591: %PIM-6-INVALID_RP_JOIN: Received (*, 239.0.0.7) Join
> from 192.0.47.7 for invalid RP 192.0.0.4
> R4(config-router)#
>
>
> Working through the ticket I applied the following config and was able to
> ping all 4 of the 239.0.0.x addresses from each of the routers.
>
> R4
> --
> ip pim rp-candidate lo0
> ip mroute 0.0.0.0 0.0.0.0 192.0.47.7
>
>
> R6
> --
> ip mroute 0.0.0.0 0.0.0.0 192.0.69.9
>
>
> However I was still seeing the following message every couple of minutes:
>
> Sep 25 15:17:47.051: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.1.40) Join
> from 192.0.47.7 for invalid RP 192.0.0.4
> R4(config)#
> Sep 25 15:19:44.847: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.1.40) Join
> from 192.0.47.7 for invalid RP 192.0.0.4
> R4(config)#
> Sep 25 15:21:42.747: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.1.40) Join
> from 192.0.47.7 for invalid RP 192.0.0.4
> R4(config)#
>
>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to