Ok, I'd just like a little clarification on another solution after
just having gone through this myself.

My solution was to configure "ip pim spt-threshold infinity" on all
participating routers.  When I did a "show ip mroute" while the MRM
test was running (from next task), I did not see any (S,G) entries,
only (*,G) entries except on the sender's table.  On a whim, I removed
the "ip pim spt-threshold infinity" command from all routers, then
enabled "ip pim bidir-enable" on each, configured the RP to send out
bidir, and re-ran MRM.  My "show ip mroute" tables looked identical
with the exception that every entry had "bidir" in it.

And finally, I removed all instances of "bidir" and "spt-threshold"
and just ran everything normal, and the mroute tables DID show (S,G)
entries, like I'd expect them too.

So, would the "ip pim spt-threshold infinity" command been an
acceptable solution for this?

Thanks,

Jason

>Bryan Bartik
>Wed, 15 Jul 2009 04:03:01 -0700
>
>Carlos,
>
>Take a look here, first paragraph:
>
>http://www.cisco.com/en/US/docs/ios/12_1t/12_1t2/feature/guide/dtbipim.html#wp1054540
>
>On Sat, Jul 11, 2009 at 3:17 PM, Carlos Valero <[email protected]>wrote:
>
>> Sorry, but I have another question about Multicast
>>
>> In Task 5.2 of this Lab (Vol 3, lab 6) the requirements state:
>>
>> "Multicast Traffic should distributed exclusively on Shared Trees"
>>
>>
>> In the solution, BIDIR is enabled in all participating Routers:
>>
>> - ip pim bidir-enable
>>
>> But I'm not sure why.
>>
>> What part of these requirements "forces" us to use ip pim bidir-enable ?
>>
>> I guess it is not the fact we are using Shared Trees, right?
>>
>> I believe that we can have Sparse Mode using Unidirectional Shared Trees,
>> correct?
>>
>> So is it the fact that says: "exclusively on Shared Trees" what makes us
>> use BIDIR?
>>
>> Could you please explain?
>>
>>
>> Thank you!!
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to