All things related to multicast

["Kevin C. Almeroth" <>]

Still fumbling with aliases...  at least ya'll don't see any of the trash
that is filtered from the list!  

-Kevin


---------- Forwarded message ----------
From: John Zwiebel 
<>
To: Richard Murphy 
<>,
        
<>

On 9/3/02 8:25 PM, "Richard Murphy" 
<>
 wrote:

> I have followed the Abilene cookbook on setting up multicasting and all
> looks OK on my border router. However, machines on a router connected to
> the border router cannot join any multicast groups. The border router is
> logging these PIM-INVALID_RP_JOIN messages. I have read the cisco note
> on fixing this issue and it leads to this question:
> 
> How does auto-rp work if the Abilene recommended filter for multicast
> groups
> includes 224.0.1.39 and 224.0.1.40 as denies?

You need to have your own RP:
  "ip pim send-rp-discover..."
  "ip pim send-rp-announce ..."

Somewhere in your network and whatever interface address you choose needs
 to be an MSDP peer with your service provider.  Since you'll have only
 one, it will be default and you shouldn't have to worry about setting
 up an MBGP peering.

> Are RPs something that is
> used in lieu of MSDP or alone with MSDP? Both routers have pim
> sparse-mode set, but the second router uses some static routes, not iBGP
> and does not use MSDP either.


"some static routes" is a flag.  Please define "some".

I'm guessing that the second router is the "border router" which means
 it has static routes to RPF outside of your domain.  (ie everything
 except 239/8 -- but that's a guess that depends on what you've done).
 The size of your network doesn't sound like it needs iBGP.

Sorry that I don't have a pointer to the Abilene cookbook.  I'm sure that
 what they say is right.  It just may take some additional (not-so-obvious)
 obvious information for it to all make sense.

But, that cookbook "should have" explained that you either:
  a) need to filter auto-RP messages:  -OR-
  b) need to have a MSDP peering with the Abilene RP.

[I'm real good at missing "or".  I wouldn't be a very good Gold Miner]

If your network isn't "that big"  (you define "that big") you -may- want
 to consider a static RP on every router.  Then you can ignore auto-rp and
 the bootstrap router.  It will even be 'more obvious' how to set up
 different RP's for different group ranges.  Depending on how you
 assign those Group to RP mappings, you may find that MSDP and MBGP mean
 nothing to you.  But, this option requires close coordination with your
 provider and severely limits your flexibility.

And it may not be an option that Abilene even offers since it becomes
 a headache for everyone when things don't work right.

Anyway, I hope you can see that the information you've provided isn't
 enough for us to narrow down the options of what might be wrong.  The
 difficult part is going to be in figuring out the difference between
 what you think you said and what we think we heard.  <sigh>

This is important:  NOTHING I've said here disagrees with anything that
 Marshall said.
> 
> Thanks to those who have been down this path already!
> 
> Richard Murphy
> 
>