Thankyou.
That is all I ws looking for..that I got it right and now I can move on.
Petr wrote the WB I believe and I doubt he's capable of genetically being technically wrong!
Just making sure my poor brain got it right..
once again thank you for the help :)
Tox!
On Thu, May 30, 2013 at 11:37 PM, HS628 <bounce-HS628@ieoc.com> wrote:
I don't think there is anything wrong with your understanding. Be it IPv4 or IPv6, there is only one shared tree in PIM-SM, which is rooted at RP and branches towards the receivers. Between FHR and RP, there's never a shared tree. I'm 100% sure the author of the SG is fully aware of this fact :) IMHO, this is all just a matter of wording. Therefore, mutlticast traffic will be forwarded out the virtual tunnel interface towards the RP to be sent down the shared tree to the receivers....maybe a little awkward? but still tehnically correct :)
--
View this message online at: http://ieoc.com/forums/p/26171/211834.aspx#211834
--
INE - The Industry Leader in CCIE Preparation
http://www.INE.com
Subscription information may be found at:
http://www.ieoc.com/forums/ForumSubscriptions.aspx
--------------------------------------------------------------------------------------------------------------------------------------------------------------
*****NEVER_FORGET >> Neighbor <ip> send-community [NOT_SENT_BY_DEFAULT]*****
[If K1=K2=K3=K4=K5=0
Then FD = 1]
[If NBMA BW > T1
Then Hello = 5 sec]
"NBMA starts sending UC hellos in response to MC hellos (without a neighbor command) PROVIDED all OSPF hello parameters other than the UC/MC match up" Nic
BGP private AS -->> 65535 - 1023 = 64512 [ 64512 thru 65535 ]
OSPF TRANSIT AREA NON_DIRECTLY CONNECTED TO BB ABR PRODUCES LSA 3 FOR LSA 1,2 AND 3 RECEIVED THRU V-LINK?
V_BIT SET = ABOVE CONDITION FALSE
V_BIT NOT SET = ABOVE CONDITION TRUE
BGP Community MATCHING and DELETION (comm-list) REQUIRES COMMUNITY_LISTS
W/ COMM_LIST community-lists multiple entries/ community-list DO_NOT_WORK!! ONE entry/community-list ONLY