[c-nsp] Multicast distribution over backbone

[Alexander Clouter]

Phil Mayers <p.mayers at imperial.ac.uk> wrote:
>>
>> I have 6 routers in 6 cities interconnected by 1Gbps links from third party
>> providers (just 1 VLAN over xconnects, no QinQ, MTU=1500).  Each city is
>> connected to main node.  I have to distribute multicast streams (around 100
>> channels of IPTV) from source 1 city to 5 others over these 1Gbps links.
>> All devices are Cat6500/Sup720.  All routers runs IS-IS and iBGP.  And in
>> each city local distrubution will be done over PIM Spare-Mode to L3 switches
>> (Cat3560-X).
>>
>> How do this best ? Use mBGP ? Use MSDP ? Configure just PIM-SM on backbone
>> interfaces ? Or maybe some hybrid solution ?
> 
> You just need PIM-SM.
> 
> Designate one router as the RP. Configure PIM-SM each router. Configure 
> them all with the same RP.
> 
> You only need MSDP to pass source info between PIM-SM RPs.
>
All our core routers are RPs with the same 'anycasted' address so we 
have resilence.  We use MSDP to then make sure everything is then 
sync'ed up:
----
interface Loopback0
 ip address 172.31.3.253 255.255.255.255
end

interface Loopback2
 description ANYCAST: mcast rp
 ip address 192.0.2.1 255.255.255.255
end

6500#show run | include pim
[snipped]
ip pim rp-address 192.0.2.1 mcast
ip pim accept-rp 192.0.2.1 mcast
ip pim ssm default

6500#show run | include msdp
ip msdp peer 172.31.3.161 connect-source Loopback0
ip msdp peer 172.31.3.249 connect-source Loopback0
ip msdp peer 172.31.3.93 connect-source Loopback0
ip msdp cache-sa-state
ip msdp originator-id Loopback0
ip msdp mesh-group soas 172.31.3.161
ip msdp mesh-group soas 172.31.3.249
ip msdp mesh-group soas 172.31.3.93
ip msdp password peer 172.31.3.161 7 [ahem]
ip msdp password peer 172.31.3.249 7 [ahem]
ip msdp rpf rfc3618
----

Cheers

-- 
Alexander Clouter
.sigmonster says: Confucius say too much.
                  		-- Recent Chinese Proverb