From: Brian Hescock (bhescock@xxxxxxxxx)
Date: Wed Oct 24 2001 - 09:41:20 GMT-3
I hadn't added something I needed to at the end of the previous e-mail. If you
get
to a router where it has "null" in the outbound interface, turn off ip multicas
t
fast-switching on that outbound interface (no ip mroute-cache). Also if this
outbound interface is the one with the join-group command, the outbound interfa
ce
should not be null, it should have that outbound interface. However, there are
some
bugs related to this. Once you have multicast fast-switching turned off on th
e
outgoing interface, remove the join-group command, turn off pim, wait for pim t
o
time out, readd pim and readd join-group and see if that outbound interface is
in
the outbound interface list (OIL). Should it still not show up, repeat the pre
vious
steps but once you've removed pim and join-group, shut the interface, wait for
everything to clear out, then readd pim and the join-group command.
I've run into this many many times and the above steps are a workaround to get
it
working. It's a bug if you don't have an interface in the OIL when you have
join-group or static-group configured.
Brian
Brian Hescock wrote:
> Ok, dumb question I know, but I have to ask (I've learned never to assume
> anything): can you unicast ping the router that you're trying to get a respo
nse
> from via multicast? I just want to make sure we have connectivity. Severa
l
> other items:
>
> - I would assume you're using "ip igmp join-group x.x.x.x" and not "ip igmp
> static-group x.x.x.x" on the router? The router will only respond if using
> join-group, not static-group
> - Is the join-group command on the outbound interface on the router in questi
on?
> It won't work if it's on an incoming interface. PIM enabled on the pertinent
> interfaces? ip multicast-routing configured (pim will work without
> multicast-routing being enabled, multicast traffic just won't be routed
> (forwarded).
> - do a debug ip mpacket on the next-hop router from where you're doing the pi
ng
> (use "no ip mroute-cache" on the interfaces so you can see the debugs). Do y
ou
> see the multicast packets come in?
> - if you don't see the debugs, do "show ip mroute x.x.x.x", do you see the (S
,G)
> (source ip, multicast group) entry?
> - if you see the (S,G) for the group, do "show ip mroute x.x.x.x count" and l
ook
> at the counters for the group. You should see the "forward" value incrementi
ng,
> repeat the command to see if it does. Also, check the last three values (ther
e's
> two sets of values, four in the first set I believe and three in the second s
et),
> you should see the first value incrementing but not the second one (at least
not
> by much, if using dense mode you will see it increment a few packets every th
ree
> minutes when we flood out every interface, resulting in rpf failures on some
of
> the interfaces).
> - keep going router by router and see at what point we don't have an entry ot
her
> than null in the outbound interface list.
>
> Should it still not work, go to enable mode and capture "show tech ipmulticas
t"
> and send me the output from the various routers will the ping is in progress.
> Note: ipmulticast is one word in the command. Thanks,
>
> Brian
>
> Michael Wong wrote:
>
> > Yes, CGMP was enabled ... here is an output from the CAT below
> >
> > CAT> (enable) sh multicast group
> > CGMP enabled
> > IGMP disabled
> > GMRP disabled
> >
> > VLAN Dest MAC/Route Des [CoS] Destination Ports or VCs / [Protocol Typ
e]
> > ---- ------------------ ----- ----------------------------------------
--- > > 11 01-00-5e-00-01-27 2/7,2/24 > > 11 01-00-5e-00-01-28 2/7,2/24 > > 11 01-00-5e-00-05-05 * 2/7,2/24 > > > > Total Number of Entries = 3 > > > > CAT> (enable) ping 224.0.5.5 > > no answer from 224.0.5.5 > > > > .... and success from the router. > > > > r5#ping 224.0.5.5 > > > > Type escape sequence to abort. > > Sending 1, 100-byte ICMP Echos to 224.0.5.5, timeout is 2 seconds: > > > > Reply to request 0 from 200.100.100.13, 200 ms > > Reply to request 0 from 200.100.100.13, 316 ms > > Reply to request 0 from 200.100.100.13, 300 ms > > Reply to request 0 from 200.100.100.13, 216 ms > > > > -----Original Message----- > > From: Khalid Nafie [mailto:knafie@ncr.com.kw] > > Sent: Wednesday, 24 October 2001 7:45 pm > > To: Michael Wong; Groupstudy - CCIELAB (E-mail) > > Subject: RE: ccBootCamp Lab 20 - Multicast > > > > did u try to enable cgmp on the CAT > > > > -----Original Message----- > > From: Michael Wong [mailto:Michael.Wong@nec.com.au] > > Sent: Wednesday, October 24, 2001 1:16 AM > > To: Groupstudy - CCIELAB (E-mail) > > Subject: ccBootCamp Lab 20 - Multicast > > > > Hey Group > > > > I am having a problem with Section Three Task Seven, Question 3. I have > > setup R13 to join to an IGMP group and the IP address 224.0.5.5 is pingable > > from all multicast routers ... no problem there. However this question also > > states that the CAT should be able to ping this address also ?? Is this > > possible .... has anyone got this to work. Keep in mind that the CAT is abl e > > to ping all unicast addressees in the network. > > > > I tried placing a static CAM entry for the multicast MAC address to see wha t > > happens but no joy ..... Help please .... TIA > > > > MW :)
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:24 GMT-3