RE: Subject: PIM shared tree source tree
Here's a really good papaer on Multicast: http://www.3com.com/nsc/501303.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Werner Sent: Wednesday, January 10, 2001 10:24 PM To: [EMAIL PROTECTED] Subject: Re: Subject: PIM shared tree source tree Do you have a link to this whitepaper? I could probably explain all of the information below, but I am curious at to what this white paper says in detail, before I attempted to try and explain it. v/r, Paul Werner Subject: PIM shared tree source tree this is taken from there white paper The following process describes the move from shared tree to source tree in more detail: 1 Receiver joins a group; leaf Router C sends a Join message toward RP. 2 RP puts link to Router C in its outgoing interface list. 3 Source sends data; Router A encapsulates data in Register and sends it to RP. 4 RP forwards data down the shared tree to Router C and sends a Join message toward Source. At this point, data may arrive twice at Router C, once encapsulated and once natively. WHY WHY WHY ...it dosent` say why it will arrive nativley.GIT 5 When data arrives natively (unencapsulated) at RP, RP sends a Register-Stop message to Router A.(i can understand that) 6 By default, reception of the first data packet prompts Router C to send a Join message toward Source. 7 When Router C receives data on (S,G),(???) it sends a Prune message for Source up the shared tree. WHY WHY WHY ? 8 RP deletes the link to Router C from outgoing interface of (S,G). RP triggers a Prune message toward Source. WHY WHY ! AM I MISSING SOMETHING..SORRY IVE BEEN AT IT ALL DAY ... and my brain now hurts TIA steve 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] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: RE: PIM shared tree source tree
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 UNPOPULARbut 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]
PIM shared tree source tree
this is taken from there white paper The following process describes the move from shared tree to source tree in more detail: 1 Receiver joins a group; leaf Router C sends a Join message toward RP. 2 RP puts link to Router C in its outgoing interface list. 3 Source sends data; Router A encapsulates data in Register and sends it to RP. 4 RP forwards data down the shared tree to Router C and sends a Join message toward Source. At this point, data may arrive twice at Router C, once encapsulated and once natively. WHY WHY WHY ...it dosent` say why it will arrive nativley.GIT 5 When data arrives natively (unencapsulated) at RP, RP sends a Register-Stop message to Router A.(i can understand that) 6 By default, reception of the first data packet prompts Router C to send a Join message toward Source. 7 When Router C receives data on (S,G),(???) it sends a Prune message for Source up the shared tree. WHY WHY WHY ? 8 RP deletes the link to Router C from outgoing interface of (S,G). RP triggers a Prune message toward Source. WHY WHY ! AM I MISSING SOMETHING..SORRY IVE BEEN AT IT ALL DAY ... and my brain now hurts TIA steve S6234 _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
PIM shared tree source tree
this is taken from there white paper The following process describes the move from shared tree to source tree in more detail: 1 Receiver joins a group; leaf Router C sends a Join message toward RP. 2 RP puts link to Router C in its outgoing interface list. 3 Source sends data; Router A encapsulates data in Register and sends it to RP. 4 RP forwards data down the shared tree to Router C and sends a Join message toward Source. At this point, data may arrive twice at Router C, once encapsulated and once natively. WHY WHY WHY ...it dosent` say why it will arrive nativley.GIT 5 When data arrives natively (unencapsulated) at RP, RP sends a Register-Stop message to Router A.(i can understand that) 6 By default, reception of the first data packet prompts Router C to send a Join message toward Source. 7 When Router C receives data on (S,G),(???) it sends a Prune message for Source up the shared tree. WHY WHY WHY ? 8 RP deletes the link to Router C from outgoing interface of (S,G). RP triggers a Prune message toward Source. WHY WHY ! AM I MISSING SOMETHING..SORRY IVE BEEN AT IT ALL DAY ... and my brain now hurts TIA steve S6234 _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Subject: PIM shared tree source tree
Do you have a link to this whitepaper? I could probably explain all of the information below, but I am curious at to what this white paper says in detail, before I attempted to try and explain it. v/r, Paul Werner Subject: PIM shared tree source tree this is taken from there white paper The following process describes the move from shared tree to source tree in more detail: 1 Receiver joins a group; leaf Router C sends a Join message toward RP. 2 RP puts link to Router C in its outgoing interface list. 3 Source sends data; Router A encapsulates data in Register and sends it to RP. 4 RP forwards data down the shared tree to Router C and sends a Join message toward Source. At this point, data may arrive twice at Router C, once encapsulated and once natively. WHY WHY WHY ...it dosent` say why it will arrive nativley.GIT 5 When data arrives natively (unencapsulated) at RP, RP sends a Register-Stop message to Router A.(i can understand that) 6 By default, reception of the first data packet prompts Router C to send a Join message toward Source. 7 When Router C receives data on (S,G),(???) it sends a Prune message for Source up the shared tree. WHY WHY WHY ? 8 RP deletes the link to Router C from outgoing interface of (S,G). RP triggers a Prune message toward Source. WHY WHY ! AM I MISSING SOMETHING..SORRY IVE BEEN AT IT ALL DAY ... and my brain now hurts TIA steve 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]
