Tacack, debugs on GM won't help. The problem is on the KS itself where it is not able to route the multicast packets. Something is stopping from routing the multicast packets out.
d=239.0.1.2, len 1080, unroutable With regards Kings On Mon, Nov 8, 2010 at 3:02 PM, Jerome Dolphin <[email protected]> wrote: > Hehe, well I'm not too bad with mcast and I'm pretty sure the mcast config > is accurate - I've tried lots of different mcast variations trying to get > this thing working :-/ > > Yep, when I ping the rekey mcast address it does arrive at both GMs, and > the GMs reply..... > > R2#ping 239.0.1.2 repeat 1 > > Type escape sequence to abort. > Sending 1, 100-byte ICMP Echos to 239.0.1.2, timeout is 2 seconds: > > Reply to request 0 from 192.1.26.6, 60 ms > Reply to request 0 from 192.1.25.5, 60 ms > R2# > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
