Posted by: Richard @ Configureterminal.com | May 12, 2008

Week 18 Summary + some more multicast info

The end of Week 18, and the end of IP Multicast! J (well, at least for now):


Week’s Study Time:

Study Hours = 15.5  inc.
Lab Hours = 1.0

Total study time so far:
Total Study Hours = 228  inc.
Total Lab Hours = 18.5

What I have studied this week:
IGMP
IGMP Snooping
CGMP
DVMRP

PIM-DM
PIM-SM
PIM-SDM
MSDP
MBGP
Anycast RP
Multicast Scoping

Recent test scores:
All IP Multicast:
19/20
17/18
14/16

 

Here are a few hyperlinks that I have found useful over the last week:
RFC 4611
Using IP Multicast Over Frame Relay Networks
How to Implement a Filtering Policy for Rendezvous Points
Bidirection PIM Powerpoint Presentation
Interdomain Multicast Solutions Using MSDP
Multicast Source Discovery Protocol SA Filter Recommendations
Anycast RP
Multi-VRF and IP Multicast

I have spent some time with a number of ‘large-scale’ multicast design and implementation concepts/protocols over the last couple of evenings.  Here are a couple of diagrams resulting from this study focus including configuration examples I have created and added to my notes.  The first of the two diagrams details “Multicast Source Discovery Protocol” (MSDP) along with some of the various filtering options available to it.  Here’s a quick explanation of what MSDP does:

MSDP interconnects multiple PIM-SM domains – This enables PIM-SM to have Rendezvous Point (RP) redundancy and inter-domain multicasting.  Or to put it another way; it’s a protocol that allows a RP in one domain to share information about its local multicast sources to a RP in another domain – thus removing the need to have one domain relying on a RP in another domain


The Process =

The RP of a ‘neighbouring’ domain receives a MSDP SA Message from the ‘source’ domain’s RP (an explicitly configured peer relationship over TCP639 is used) à it then determines if there are group members within its own domain interested in the group’s traffic à if such a device exists the ‘neighbouring’ domain’s RP triggers a join towards the data source (in the source domain).


and the diagram:

This second diagram represents an Anycast RP deployment, which relies on an underlying intradomain MSDP full mesh:

It’s “Security” now – one of my favourite and strongest areas J

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: