From: Danny Muizebelt (Danny.Muizebelt@osiatis.at)
Date: Fri Aug 26 2005 - 10:40:49 GMT-3
> When the sender will send multicast, then RB, as the DR, will send
> register
> to RA.
If we are talking here about sparse-dense mode with an unlimited SPF
threshold then the DR will send the multicast packet encapsulated in a
unicast packet to the RP. From there it goes down the usual (*.g) tree.
No problems here about any RPF issues.
Default Cisco behaviour will switch to a source tree after the first
multicast packet.
Correct me if I'm wrong but the way I see it both will accept the
multicast packets from 1.1.1.3 but only forward according any joins they
each have received. Receiver 5.5.5.3 will probably send his join for
source group (1.1.1.3, 239.255.0.1) towards RD (5.5.5.2) because both
paths are valid and PIM will select the highest IP number. (Brings us to
the question if RIP can load-balance but who cares? ;)
So in the end RB will receive on E0 and forward to E2.
RA will receive on E0 and forward to Null.
I guess the situation would be clearer if you had 2 networks with a
listener on each end and a multi-access network in the middle with the
sender. I believe you would end up with 2 (S,g) trees for each half of
the network.
I could be wrong though... ;)
-Danny
>
> But RA unicast routing table knows that SENDER should come from E0
> and not
> from E2, so will RFP fail?
Diese Information ist vertraulich und ausschlie_lich zur Kenntnisnahme durch den (die) genannten Adressaten bestimmt.
Wenn sie nicht der vorgesehene Adressat sind, informieren sie uns bitte unverz|glich.
The information herein is confidential and intended solely for the attention and use of the named addressee(s).
If you are not the intended recipient please inform us immediately.
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:20 GMT-3