From: Daniel C. Young (danyoung99@xxxxxxxxxxxx)
Date: Sun Jul 01 2001 - 03:10:02 GMT-3
Cal,
Are you sure that's correct? My impression is that the D flag for 224.0.1.39
& 40 will show up for sparse-dense mode as soon as auto-rp is configured. By
the way, which is the "sparse-dense flag" that you speak of?
>From the output below, this is what I deduced about the current state:
-This router is not a mapping-agent, but has discovered the RP to be
172.30.0.1
-Groups 224.0.1.41 and 224.3.2.1 did not discover the RP, so it is using
dense mode (hence, the "D" flag)
-Groups 224.0.1.41 and 224.3.2.1 have exceeded their threshold (signified by
the "J" flag) and are switching to SPT.
-They have connected hosts (receivers) that are listed on the OIL, but there
is no source transmitting at this point. Hence, IIL is null.
BTW, what is group 224.0.1.41 used for? Can you show your (S, G) entries and
configs as well?
Cheers,
Daniel
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Cal
Michael
Sent: Wednesday, June 27, 2001 10:20 PM
To: ccielab@groupstudy.com
Cc: danyoung99@mediaone.net
Subject: RE: Multicast-Auto-RP
- Dan:
But in 12.1 I was under the impression that the the auto-rp sparse-dense
flag was only present
when the incoming interface was null.
You should still see a forward/sparse on the outgoing interface.
i.e.
(*, 224.0.1.41), 4d07h/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
TokenRing0/0, Forward/Sparse, 4d07h/00:02:22
Serial0/2:0, Forward/Sparse, 03:50:08/00:01:16
(*, 224.0.1.40), 11:02:32/00:00:00, RP 172.30.0.1, flags: SJCL
Incoming interface: Serial0/0, RPF nbr 172.30.40.3
Outgoing interface list:
Loopback0, Forward/Sparse, 11:02:35/00:02:01
(*, 224.3.2.1), 11:02:36/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse, 11:02:38/00:02:01
Has someone seen other behavior from 12.1?
--- ----- ---
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Daniel C. Young
Sent: Wednesday, June 27, 2001 11:23 PM
To: 'Brian'; 'Tony Ng'
Cc: 'Lachlan Kidd'; 'Mike Gutknecht'; 'CCIELAB (E-mail)'
Subject: RE: Multicast-Auto-RP
Folks,
I agree with the general consensus that you should use sparse-dense mode.
Cisco recommends this. Auto-rp itself depends on 224.0.1.39 for C-RPs to
announce their capabilities and 224.0.1.40 for all multicast routers to
discover the RP from the mapping-agents. If you look at the (*, G) entries
for these two groups, the D flag will be set indicating that it is operating
in dense mode.
Here is the caveat: if you are running 12.1.X, you can configure only
sparse-mode and the IOS will (sometime) still run sparse-dense if auto-rp is
configured. The configs will show only sparse-mode, but you will see (*, G)
entries for 224.0.1.39 and 224.0.1.40 with D flags on it. Having said that
though, for the lab exam I would definately just stick with sparse-dense.
Hope that helps.
Daniel
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Brian
Sent: Tuesday, June 26, 2001 7:21 PM
To: Tony Ng
Cc: Lachlan Kidd; 'Mike Gutknecht'; 'CCIELAB (E-mail)'
Subject: RE: Multicast-Auto-RP
I don't believe that is correct. If you have a purely sparse network,
your auto-rp announcements will only make it one hop. You must use
sparse-dense, so that the distant PIM routers now how to get to the RP.
Its a catch 22, the distant PIM router cannot join the 224.0.1.40, because
it doesn't know the RP........
If you are just working with 3 routers or so, and they are all directly
connected to the RP you may not see this............since even with pure
sparse it would still work.
Brian
On Tue, 26 Jun 2001, Tony Ng wrote:
> auto-rp announcements should traverse over all interfaces that are in
either
> sparse or sparse-dense-mode (that is acting in Sparse mode). for auto-rp
to
> work, the RP needs to "announce" that it is the RP to the mapping agents
in
> order for it to work. Make sure that the mapping agent is sending packets
> out to M/C group 224.0.1.40. In turn, the RP needs to send out M/C
traffic
> to group 224.0.1.39.
>
> Tony Ng
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Lachlan Kidd
> Sent: Sunday, June 24, 2001 7:34 PM
> To: 'Mike Gutknecht'; 'CCIELAB (E-mail)'
> Subject: RE: Multicast-Auto-RP
>
>
> I could only get it working in sparse-dense. I suspect it's because it
needs
> dense mode to get the auto-rp announcements throughout the network. I may
be
> wrong...
> L
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Mike Gutknecht
> Sent: Monday, 25 June 2001 12:10:PM
> To: CCIELAB (E-mail)
> Subject: Multicast-Auto-RP
>
>
> Can anyone get Auto-RP working in a pure sparse-mode network or do you
need
> sparse-dense on the pathway back to the mapping agent? I haven't been
> successful.
>
> Going in for the test on Wed.
>
> Mike Gutknecht
> Systems Engineer
> Planetary Networks
> 503.534.3668 - office
> 503.704.8365 - cell
> mike@justcisco.com
> **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
-----------------------------------------------
I'm buying / selling used CISCO gear!!
email me for a quote
Brian Feeny,CCDP,CCNP+VAS Scarlett Parria
signal@netjam.net scarlett@netjam.net
318-213-4709 318-213-4701
Netjam, LLC http://www.netjam.net
333 Texas St. VISA/MC/AMEX/COD
Suite 1401 30 day warranty
Shreveport, LA 71101 Cisco Channel Partner
toll free: 866-2NETJAM
phone: 318-212-0245
fax: 318-212-0246
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:28 GMT-3