On 11/14/2012 02:07 PM, Bal Birdy wrote:
Interesting, but isn't the static-group command similiar to the
join-group command. Both effectively force the router to send a IGMP
Join to the MCAST Group, but the join-group command results in the
router processing mcast traffic, vs the static which though the router
has joined the router won't process the traffic.
Correct me if I'm wrong?
But, this to me seems a bit of a "fudge"? Surely this should be
working without the static joins?
I'm liking this thread as I'm currently going over Multicast, haven't
quite got to this topic area, but it's a great discussion.
B
The static-group command is designed to be used in cases where there is
a multicast listener on an interface that is not IGMP capable. In this
case the listener is IGMP capable, but its IGMP actions are stopping the
multicast flow to itself. So, its within the "spirit" of the
static-group command's design to insist R1's interface forward mcast
traffic for a group, because there is actually a listener out there
interested in the mcast flow.
I spent a few hours on this scenario trying find a workaround. Using
static-group * is a good solution, you could configure it and forget
about it as all mcast groups will be covered.
In the docs for pim nbma-mode, Cisco says (in so many words) "if you
want to use multicast on an NBMA network, reconfigure it to use
point-to-point subinterfaces. You're life will be easier that way."
This is a challenging scenario. Even though I found a way around it, I
will now also say "Multicast over NBMA makes my brain hurt"....
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
http://onlinestudylist.com/mailman/listinfo/ccie_rs
