Hi
PIM Assert mechanism is to choose which is the outgoing router to forward
traffic from a source. When there is a source starts transmitting traffic
and it has been received by two or more First Hop Routers and they sent on
the LAN Segment and when they receive the same traffic from each other .
So they start a PIM Assert Mechanism. It decides on three factors
1.The router generating an Assert with the lowest Administrative distance
is elected the forwarder. The AD would only differ if the routes are from
different routing protocols. If AD are same then step 2
2.The best unicast routing metric is used . The combination of AD and the
unicast routing metric is referred to as a tuple
3.Then the highest IP Address will be elected as PIM Forwarder.
PIM Forwarder is elected in PIM Asset Mechanism .
PIM Forwarder is from the source side
PIM DR is responsible on both the source side and receiver side.
On the source side, PIM DR does the source registration and from the
receiver perspective, it is the one which forwards the traffic to the
receiver.
So DR is the designated router for processing all the multicast control
plane on the source side and data plane on the receiver side.
Hope this helps..
On Sun, Jan 22, 2012 at 8:18 AM, ccie routing <mike.ccie_at_gmail.com> wrote:
> Hi Experts,
>
> I am little confused about PIM Assert and PIM DR and PIM forwarder. From
> what I read Assert is used when there are two or more routers connected to
> LAN and one of them is elected to forward traffic on to the LAN. Is this
> the same as PIM forwarder ?
>
> PIM DR does the role of sending join/prune to RP in sparse mode. Is a DR
> needed in Dense mode.
>
> Thanks.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- With Warmest Regards, CCIE KID CCIE#29992 (Security) Blogs and organic groups at http://www.ccie.netReceived on Sun Jan 22 2012 - 13:14:36 ART
This archive was generated by hypermail 2.2.0 : Thu Feb 02 2012 - 11:52:51 ART