All things related to multicast

[debbie fligor <>]

On Sep 14, 2007, at 11:39, Stig Venaas wrote:
> > and then on all router interfaces towards multicast peers did the  
> > following:
> > interface g2/2
> > ip pim bsr-border
>
> bsr-border should help. I suggest you try to track down where the
> Bootstrap messages (BSMs) come from. Try "show ip pim bsr-router"  
> to see
> what the BSR address is, at least I think that will tell you. Once
> you know that, try to figure out which interface messages from that
> address must come from. You might try "show ip rpf <address>" on your
> border routers where <address> is the BSR address. This will show you
> which interface the BSMs are received on (there is an RPF check for
> receiving BSMs). Hopefully this will help you find some interface you
> have forgot to put "ip pim bsr-border" on. Of course it could be that
> bsr-border doesn't work for some reason, but that would be news to me
> at least.

it does appear to be blocking them correctly, the Cisco's no longer  
show them in their bsr list (they had before - I forgot to check that  
they were gone), apparently Foundry 12 GCF's don't "forget" RP's  
learned by BSR in a timely fashion.  yet another issue to bring up  
with them....


thanks, you pointed me in a useful direction.

> > ip multicast boundary multicast-boundary
> > I don't think I missed any interfaces, I've checked it over a  
> > couple of times.  Can anyone think of anything else to suggest or  
> > point out that I missed?
>
> Right. Hopefully checking for RPF of the BSR address will help you.

it was out one of the interfaces that did have the bsr-border command  
installed.

> Stig
> -----

-debbie
Debbie Fligor, n9dn       Network Engineer, CITES, Univ. of Il
email: 

          <http://www.uiuc.edu/ph/www/fligor>
                   "My turn."  -River