140 likes | 298 Views
Multicast Gigapop Deployment. Don Salvin Senior Network Engineer NLANR/NCNE. NCNE role in Advanced Network Service Deployment. The Abilene NOC and Qwest establish IP connectivity. NCNE helps with: Multicast QoS Security IPv6 Performance tuning.
E N D
Multicast Gigapop Deployment. Don Salvin Senior Network Engineer NLANR/NCNE
NCNE role in Advanced Network Service Deployment • The Abilene NOC and Qwest establish IP connectivity. • NCNE helps with: • Multicast • QoS • Security • IPv6 • Performance tuning
The mission: Great Plains Network multicast startup • Spend a morning discussing overall multicast protocols and issues. • Assume no existing multicast infrastructure. • After 3 hours of discussion in Kansas City, it looks easy. • Multicast deployment IS getting easier these days.
Multicast backbone distributionPIM-sparse, mBGP, & MSDP • PIM-Sparse • efficient multicast propagation over wide area circuits. • It is harder to debug.
Multicast backbone distributionPIM-sparse, mBGP, & MSDP • mBGP allows dissemination of multicast routes independent of Unicast routes. • important for incongruent Unicast/Multicast topologies.
Overall GPN topology • Two GigaPoints • Two Abilene connections. • Multiple I1 connections.
Typical GigaPoint configuration • Router per service/AUP type • Avoids the “fish” problem. • Campuses connected according to policy.
The Great Plains question • How do you do multicast here? • Straight forward! • PIM sparse • mBGP • MSDP
The PSC example • The Route servers complicates multicast. • Allows easier control of distribution of BGP information to client sites. • Useful when tuning traffic in multiple ISP environment. • But, current route server implementation doesn’t support mBGP (coming RSN). • Are we the only ones running them?
The PSC example • Furthermore, conflicting IOS feature sets don’t easily allow all of the appropriate machines to run mBGP and MSDP. • So we are forced to have incongruent unicast/multicast topologies.
Debugging Multicast • The tools are there. • The knowledge base isn’t. • Multicast traceroute protocol implementations themselves aren’t fully debugged.
So what’s next? • Develop the list of Abilene sites getting ready to do multicast. • Understand the features and limitations of the wide area and campus topologies for each connector/participant. • All of which gets a bit more interesting if existing PIM-dense or DVMRP.
What’s next? • Develop the knowledge base for the debugging tools. • Contact us when you start to think about implementing advanced network services. • Ncne@ncne.nlanr.net • Start polling Abilene connectors and participants about multicast deployment plans.