Hi,

Now I know which link you were referencing.  It is *okay* as a 
reference for IP multicast, but there are much better (and 
clearer) sources of information.  The most important conceptual 
thing you need to master before you deal with PIM (in any form) 
is to understand the fundamentals of any type of multicast 
routing, namely that it is "upside down routing".  By that I 
mean that in normal unicast routing we are always concerned 
about getting from a source to a destination.  In multicast 
routing, it is the exact opposite.  Destinations are multicast 
clients and they are trying to find a path to the source or 
sources of the multicast streams.  You probably would benefit 
tremendously by reading Beau Williamson's book, "Developing IP 
Multicast networks" ISBN: 1578700779.

I wanted to try to attempt to explain PIM Sparse Mode in very 
clear and concise terms.  OTOH, I came across this post:


> I AM ABOUT TO BECOME REALLY UNPOPULAR....but i have a crack 
for ALL the 
> BOSON test so you can get the FULL version for FREE.....
> 
> anybody!!!!!..


..And I decided to forego the explanation.


Paul Werner


> Subject: RE: PIM shared tree source tree
> 
> Sorry
> "Configuring IP multicast routing"
> As per above
> Understand PIM Shared Tree and Source Tree (Shortest Path 
Tree)
> 
> "
> If the data rate warrants, leaf routers on the shared tree 
may initiate
> a 
> switch to the data distribution
> tree rooted at the source. This type of distribution tree is 
called a 
> shortest path tree or source tree.
> By default, the Cisco IOS software switches to a source tree 
upon
> receiving 
> the first data packet from
> a source.
> The following process describes the move from shared tree to 
source tree
> in 
> more detail:

________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to