From: Gianpietro Lavado (gianpietro1@gmail.com)
Date: Sat May 20 2006 - 13:46:02 ART
George,
Auto-RP uses groups 224.0.1.39 and .40 for the RP & mapping agent
announces, but this groups work only on dense mode. If you are restricted
to use sparse mode only, you can use the 'ip pim auto-rp listener' command
on every router (which activates dense-mode for this two groups only) or
else you can use BSR.
Also since you are working on a FR hub&spoke network, be careful with
multicast traffic between the spokes not getting through the spokes; if you
have this problem you should use nbma-mode on the hub.
Regards
Gianpietro
On 5/20/06, george stanza <cert2006@gmail.com> wrote:
>
> thats right..
> i used send-rp-announce and rp-discover/rp-filter commands as follows on
> the
> hub..
>
> ip pim send-rp-announce Loopback0 scope 16 group-list 55
> ip pim send-rp-discovery Loopback0 scope 16
> ip pim rp-announce-filter rp-list 23 group-list 55
> !
> access-list 23 permit 4.4.5.5
> access-list 55 permit 224.1.1.1
>
>
> One spoke router has an ethernet interface joining 224.1.1.1 but the
> spokes
> dont have their mroute tables populated..Any idea whats going on..
>
> r2#sh ip mroute 224.1.1.1
> Group 224.1.1.1 not found
>
> r2#sh ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
> Connected,
> L - Local, P - Pruned, R - RP-bit set, F - Register flag,
> T - SPT-bit set, J - Join SPT, M - MSDP created entry,
> X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
> U - URD, I - Received Source Specific Host Report,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 224.0.1.39), 00:02:16/stopped, RP 0.0.0.0, flags: DP
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (4.4.5.5, 224.0.1.39), 00:02:01/00:00:58, flags: PT
> Incoming interface: Serial2/2, RPF nbr 4.4.245.5
> Outgoing interface list: Null
>
> (*, 224.0.1.40), 00:02:20/stopped, RP 0.0.0.0, flags: DPL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (4.4.5.5, 224.0.1.40), 00:01:35/00:02:32, flags: PLT
> Incoming interface: Serial2/2, RPF nbr 4.4.245.5
> Outgoing interface list: Null
>
>
>
>
>
> On 5/20/06, Petr Lapukhov <petrsoft@gmail.com> wrote:
> >
> > You mean, without configuring static RP on any router? :)
> >
> > 2006/5/20, george stanza <cert2006@gmail.com>:
> > >
> > > group,
> >
> > i am puzzled with a little question here which says to configure a
> > sparse-mode on a frame-relay without using the RP on any of the
> routers..
> > I,
> > so, used the rp-discover and rp-announce commands, but then the
> multicast
> > groups wont form. The mroute database shows empty.. Any examples of
> this..
> >
> > //G
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:22 ART