From: Tim (ccie2be@nyc.rr.com)
Date: Thu Jan 19 2006 - 19:15:14 GMT-3
This feature is a way of extending igmp function an extra hop.
I can't say whether this feature has real world value but that doesn't
matter with respect to the lab.
It's not a hard feature to configure. Just make sure you know how to
configure it and how to recognize the requirement for it in the lab and
you'll be fine.
Then move on to the other stuff.
HTH, Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
CCIEin2006
Sent: Thursday, January 19, 2006 5:00 PM
To: Cisco certification
Subject: What good is multicast stub routing?
According to Cisco:
"Stub IP multicast routing allows stub sites to be configured quickly and
easily for basic multicast connectivity, without the flooding of multicast
packets and subsequent group pruning that occurs in dense mode, and without
excessive administrative burden at the central site."
I'm not sure what you're really saving here. If there is a multicast
receiver at the stub site, the multicast packets still have to flow over the
same link. And how much more administrative burden is it to configure pim on
an interface than to configure a pim neighbor filter and igmp helper
address?
Can someone explain the utility of this feature?
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:49 GMT-3