From: Scott Morris (smorris@ipexpert.com)
Date: Wed May 09 2007 - 11:27:41 ART
It keeps some sanity in your network, and provides a central place (the RP)
that KNOWS about all of the sources within the network.
Your shared tree MAY be the shortest path. Depending on your topology of
course. If you want to never switch over, use the "infinity" threshold.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
IPexpert VP - Curriculum Development
IPexpert Sr. Technical Instructor
smorris@ipexpert.com
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
sirus MOGHADASIAN
Sent: Wednesday, May 09, 2007 7:44 AM
To: Cisco certification
Subject: multicast funny question!! shared trees leads to source tree at the
end of story!!!
Hello group,
I have a "why from first implement sth that at the ends leads to first place
problem?" question
we use share trees to prevent populating routing table with so many (S,G)
entries, when I study PIM-SM ,I realized that each source and destination
builds source tree (actually after bypassing RP and send packet to each
other directly) so what's the point to use share tree when eventually PIM-SM
cisco implementation (with default of zero threshold to make SPT) leads to
use source tree model?
Thanks
Sirus Moghadasian
This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:20 ART