From: Ben (bmunyao@gmail.com)
Date: Sat Jul 21 2007 - 17:11:02 ART
Milind,
Sorry i responded without looking at the config you attached. I notice you
have autorp as well as static rp on R1. Generally, you only need one method
of defining the RP, unless the task required otherwise. In your case autorp
takes precedence (i think), since you don't have the override keyword on
your static rp setting.
The answer probably lies somewhere in your R2 configuration, as Antonio
suggested.
Ben
On 7/21/07, Gadad, Milind <m-gadad1@ti.com> wrote:
>
> I am running RP and mapping agent on the same router.
>
>
>
>
> ------------------------------
>
> *From:* Ben [mailto:bmunyao@gmail.com]
> *Sent:* Saturday, July 21, 2007 2:33 PM
> *To:* Gadad, Milind
> *Cc:* ccielab@groupstudy.com
> *Subject:* Re: Multicast query
>
>
>
>
> Is the neighbor you refer to the RP or mapping agent?
>
>
> Ben
>
>
> On 7/21/07, *Gadad, Milind* <m-gadad1@ti.com > wrote:
>
> Ben,
>
>
>
> The neighbor is directly connected neighbor. I am able to ping neighbor
> address and loopback address of RP.
>
>
> Regards,
>
>
>
> Milind
>
>
>
>
> ------------------------------
>
> *From:* Ben [mailto:bmunyao@gmail.com]
> *Sent:* Saturday, July 21, 2007 2:23 PM
> *To:* Gadad, Milind
> *Cc:* ccielab@groupstudy.com
> *Subject:* Re: Multicast query
>
>
>
> Milind
>
> This problem manifests when the AutoRP discovery messages do not arrive on
> the RPF interface, probably due to a divergence in the muticast path from
> the unicast path.
>
> Solution: ip mroute command
>
> Alternative: Tune your IGP for change the routers next hop to the Mapping
> Agent, and multicast source.
>
> HTH
> Ben
>
> On 7/21/07, *Gadad, Milind* <m-gadad1@ti.com> wrote:
>
> I am running ip pim spare-mode on all the routers in the lab, the
> following is the config on RP router. On the other router in the lab
> when I run "sh ip pim rp mapping", I don't find any mapping.
>
>
>
> R1 (RP)
>
> ip pim rp-address 200.0.0.1
>
> ip pim autorp listener
>
> ip pim send-rp-announce Loopback0 scope 16 group-list 1
>
> ip pim send-rp-discovery Loopback1 scope 16
>
>
>
>
>
> access-list 1 permit 234.55.55.11
>
> access-list 1 permit 234.55.55.12
>
> access-list 1 permit 234.55.55.13
>
>
>
>
>
> r1#sh ip pim rp mapping
>
> PIM Group-to-RP Mappings
>
> This system is an RP (Auto-RP)
>
> This system is an RP-mapping agent (Loopback1)
>
>
>
> Group(s) 234.55.55.11/32
>
> RP 200.0.0.1 (?), v2v1
>
> Info source: 200.0.0.1 (?), elected via Auto-RP
>
> Uptime: 00:24:12, expires: 00:02:49
>
> Group(s) 234.55.55.12/32
>
> RP 200.0.0.1 (?), v2v1
>
> Info source: 200.0.0.1 (?), elected via Auto-RP
>
> Uptime: 00:24:30, expires: 00:02:27
>
> Group(s) 234.55.55.13/32
>
> RP 200.0.0.1 (?), v2v1
>
> Info source: 200.0.0.1 (?), elected via Auto-RP
>
> Uptime: 01:48:37, expires: 00:02:14
>
> Group(s): 224.0.0.0/4, Static
>
> RP: 200.0.0.1 (?)
>
>
>
> r1#sh ip pim neighbor
>
> PIM Neighbor Table
>
> Mode: B - Bidir Capable, DR - Designated Router, N - Default DR
> Priority,
>
> S - State Refresh Capable
>
> Neighbor Interface Uptime/Expires Ver DR
>
> Address
> Prio/Mode
>
> 150.50.17.2 FastEthernet1/0 02:06:13/00:01:38 v2 1 /
> DR S
>
>
>
>
>
>
>
> Other router
>
> r2#sh ip pim rp mapping
>
> PIM Group-to-RP Mappings
>
>
>
> r2#sh ip pim neighbor
>
> PIM Neighbor Table
>
> Mode: B - Bidir Capable, DR - Designated Router, N - Default DR
> Priority,
>
> S - State Refresh Capable
>
> Neighbor Interface Uptime/Expires Ver DR
>
> Address
> Prio/Mode
>
> 150.50.17.1 FastEthernet0/0 02:05:51/00:01:29 v2 1 / S
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:41 ART