All things related to multicast

[Marshall Eubanks <>]

I am at the RIPE meeting, and will not be able to give this any  
attention until tomorrow, but WG
members should feel free to jump in.

Also, the USHMM is a I2 member, but Chandra is not yet on this list,  
and so make sure to cc him in
any replies.

Regards
Marshall


Begin forwarded message:

> From: 
>
> Date: April 25, 2006 8:14:09 AM EDT
> To: Marshall Eubanks 
> <>
> Subject: Re: Quick question
>
> I tried to describe the issue as best as I can - I certainly would
> appreciate any help.
> ---------------------------------------------------------------------- 
> ---------------
>
> Chandra
> U S Holocaust Memorial Museum
>
> ---------------------------------------------------------------------- 
> --
> The problem may be on my edge router.  One of its Ethernet infaces  
> on this
> router connects to gigapop (MAX at UMd) and the other goes into a  
> small LAN
> subnet on my side - No firewall in between.  Our RP is already  
> setup, acc.
> to MAX folks, at the gigapop and the interface on their router  
> where my
> link goes to is multicast enabled as well.  I am not able to see any
> multicast SAP (or should I, since I am not the RP).  Also, I cannot  
> see a
> known multicast video stream from Ann Arbor, that is viewable from  
> other
> multicast-ebaled sites.  Here is what I did on our edge router:
>
> ENABLE MULTICAST ROUTING ON THE WAN ROUTER:
> The first item should be a no-brainer (enabling multicast routing  
> on the
> WAN router):
> ip multicast-routing
>
> ---------------------------------------------------------------------- 
> ----------
> SET UP MBGP:
> On the next item (setting up MBGP), I expect we’ll probably stick  
> with the
> same IP addresses and ASN as are currently used in the regular BGP
> statement, and modify that as recommended in the Abilene  
> instructions to
> be:
> neighbor 206.196.177.221 remote-as 10886
> address-family ipv4 unicast
>  neighbor 206.196.177.221 activate
> neighbor 206.196.177.221 remote-as 10886
> address-family ipv4 multicast
>  neighbor 206.196.177.221 activate
>
> ---------------------------------------------------------------------- 
> -------------
> CONFIGURE PIM: <<<<<< This is done on both Internet-2 interface and  
> myside
> LAN interface.
> Then, we must enable PIM on each of the interfaces involved in the
> multicast situation—the one connecting to the VBRICK VLAN and the  
> interface
> used to connect to the Internet 2 router.
> ip pim sparse-mode
>
> We will create this access list to block unwanted multicast streams:
> ip access-list standard multicast-boundary
> deny 224.0.1.39
> deny 224.0.1.40
> deny 239.0.0.0 0.255.255.255
> permit any
>
> That access list will then be applied to the interface connecting  
> to the
> Internet 2 router:
> ip multicast boundary multicast-boundary
>
> ---------------------------------------------------------------------- 
> ---------------
> CONFIGURE MSDP
> Finally, we enable MSDP to the Internet2 RP (206.196.177.247)
>
> ip msdp peer 206.196.177.247
> ip msdp sa-filter out 206.196.177.247 list 111
>
> access-list 111 deny ip any host 224.0.1.2
> access-list 111 deny ip any host 224.0.1.3
> access-list 111 deny ip 10.0.0.0 0.255.255.255 any
> access-list 111 deny ip 127.0.0.0 0.255.255.255 any
> access-list 111 deny ip 172.16.0.0 0.15.255.255 any
> access-list 111 deny ip 192.168.0.0 0.0.255.255 any
> access-list 111 permit ip any any