From: John Matus (John.Matus@tokiom.com)
Date: Wed Dec 07 2005 - 22:03:43 GMT-3
ok, so .39 and .40 only run in dense mode....
so even tho you configure an interface in sparse mode, the global command
"forces" the interface to run in dense mode for .39 and .40 only <?>
<You can also run
sparse mode only without auto-rp listener if you statically define an RP
to send joins for 224.0.1.39 and 224.0.1.40.>
this begs the question............how would you configure this???  i don't
have a router in front of me so i'm thinking perhaps an "ip igmp" command
of some-sort or else some kind for a static mroute perhaps???
Regards,
John D. Matus
Technical Support / PAS
Fujitsu Consulting
626-568-7716
John.Matus@tokiom.com
                                                                           
             "Brian McGahan"                                               
             <bmcgahan@interne                                             
             tworkexpert.com>                                           To 
                                       "John Matus"                        
             12/07/2005 04:57          <John.Matus@tokiom.com>,            
             PM                        <ccielab@groupstudy.com>            
                                                                        cc 
                                                                           
                                                                   Subject 
                                       RE: another dumb multicast question 
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
             It does run in dense mode, that's what auto-rp listener
accomplishes.  Auto-RP listener is essentially sparse-dense mode, but
you're only dense for 224.0.1.39 and 224.0.1.40.  You can also run
sparse mode only without auto-rp listener if you statically define an RP
to send joins for 224.0.1.39 and 224.0.1.40.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
John Matus
Sent: Wednesday, December 07, 2005 6:39 PM
To: ccielab@groupstudy.com
Subject: another dumb multicast question
just trying to get my information correct.
let's say you are running auto-rp and you have mapping agents that are
not
directly connected to the c-rp...........and you're running in sparse
mode.
will "ip pim auto-rp-listener overcome the issue for the mapping agent
like
it does for a client/router, or does 224.0.1.39 have to run in
dense-mode
only?
Regards,
John D. Matus
Technical Support / PAS
Fujitsu Consulting
626-568-7716
John.Matus@tokiom.com
========================================================================
================================
   This  e-mail  is  intended  solely  for  the  individual  to  whom it
is
addressed.   The   information  contained  in  this  transmission
contains
confidential  and/or proprietary information or is otherwise privileged.
If
the reader of this message is not the intended recipient, please be
advised
that  any  dissemination,  distribution  or copying of this transmission
is
strictly  prohibited.  If  you  have  received this e-mail in error,
please
notify  us immediately by returning it to the sender and deleting this
copy
from     your     system.     Thank     you     for    your
cooperation.
========================================================================
================================
This archive was generated by hypermail 2.1.4 : Mon Jan 09 2006 - 07:07:50 GMT-3