From: Kelly, Russell G (Russell_Kelly@eu1.bp.com)
Date: Sun Nov 16 2003 - 17:42:21 GMT-3
Sorry.....meant Run a sh ip pim rp mapping and sh ip pim rp on R2 to see what it thinks the RP is for this group.....
-----Original Message-----
From: Kelly, Russell G
Sent: 16 November 2003 10:36
To: Paul Chen; ccielab@groupstudy.com
Subject: RE: Auto RP
Hi,
I believe R2 does not see 151.10.102.1 as the RP for the MC group. Run a sh ip pim rp mapping and sh ip pim rp on R3 to see what it thinks the RP is for this group. Need a little more info on your topology, however this has happened to me when a router on the MC path was not MC enabled (and pim-sparse-dense and passing auto-rp info)
Russ
-----Original Message-----
From: Paul Chen [mailto:cpjchen@starhub.net.sg]
Sent: 16 November 2003 08:08
To: ccielab@groupstudy.com
Subject: Auto RP
Hi,
Just wondering if anyone knows the reason for the error message ?
R2 is the candidate RP and R3 - 151.10.23.3 is the mapping agent.
Running auto rp.
Does anyone know what causes this message ?
R2#
*Mar 1 02:31:16.607: %PIM-6-INVALID_RP_JOIN: Received (*, 225.12.12.12)
Join fr
om 151.10.23.3 for invalid RP 151.10.102.1
*Mar 1 02:33:14.527: %PIM-6-INVALID_RP_JOIN: Received (*, 225.12.12.12)
Join fr
om 151.10.23.3 for invalid RP 151.10.102.1
R3>en
R3#sh ip pim rp
Group: 225.12.12.12, RP: 151.10.102.1, v2, v1, uptime 02:06:06, expires
00:02:51
R3#
R3#sh ip rpf 151.10.102.1
RPF information for ? (151.10.102.1)
RPF interface: Serial0/0.23
RPF neighbor: ? (151.10.23.2)
RPF route/mask: 151.10.102.0/24
RPF type: unicast (eigrp 100)
RPF recursion count: 0
Doing distance-preferred lookups across tables
R3#
Thanks.
Paul
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:12 GMT-3