From: Andrew Lissitz \(alissitz\) (alissitz@cisco.com)
Date: Sun Nov 13 2005 - 02:01:57 GMT-3
Hey Group,
Chris is right, this should be a very minimal and simple setup. It
appears that this router is confused whether it is running sparse or
dense mode. Have you labbed up some sparse mode configs recently?
Perhaps a reboot is needed ...
The reason I say this is because the router adds a 224.0.1.40 group
membership for the interface f0/0. This group is not needed for dense
mode operation. In my lab, this group is not joined unless a sparse or
sparse-dense mode interface is configured. In my lab, I do not see this
group with only dense mode on the router. My lab has been 'wrong'
before ... so please lab this up and see if what I see is the same as
what you see :-)
Loi, in your mroute output, you show:
(172.16.80.2, 229.10.10.10), 00:04:58/00:01:03, flags: PT
Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
From traffic sourced from R2 and going to the group on R1, what is the
outgoing interface listed? Where will this router send traffic destined
for the 229.10.10.10 group?
Please reboot your routers and try what Chris suggested. If this does
not work then perform debug ip packet on both R1 and R2. See if the
traffic leaves R2 and gets to R1 ...
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Loi, Choon Ho
Sent: Saturday, November 12, 2005 9:04 PM
To: Chris Lewis; ccielab@groupstudy.com
Subject: RE: Router as Multicast Host
here's the config:
R1:
interface FastEthernet0/0
ip address 172.16.80.1 255.255.255.0
ip igmp join-group 229.10.10.10
duplex auto
speed auto
R2:
ip multicast-routing
interface FastEthernet0/0
ip address 172.16.80.2 255.255.255.0
ip pim dense-mode
duplex auto
speed auto
here's the ping:
R2#ping 229.10.10.10 rep 10
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 229.10.10.10, timeout is 2 seconds:
..........
R2#ping 229.10.10.10 so f0/0 rep 10
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 229.10.10.10, timeout is 2 seconds:
Packet sent with a source address of 172.16.80.2 ..........
R2#ping 172.16.80.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.80.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
________________________________
From: Chris Lewis [mailto:chrlewiscsco@yahoo.com]
Sent: Saturday, November 12, 2005 11:00 PM
To: Loi, Choon Ho; ccielab@groupstudy.com
Subject: Re: Router as Multicast Host
I tihnk you'll have to post your configs. ip mulicast routing is not
required for R1 to respond to pings to 229.10.10.10 from R2, in my setup
I can enable just a join on the interface on R1 facing R2, then R2 is
able to ping 229.10.10.10, the only config on R2 is to enable multicast
routing and put pim dende on the interface going towards R1
Chris
"Loi, Choon Ho" <ChoonHo.Loi@getronics.com> wrote:
For this scenario:
R1(join 229.10.10.10)-----------(pim dense)R2(pim
dense)----------------(pim dense)R3
With the setup, R2 can't ping 229.10.10.10
What is the possible solution for this, if R1 can not enable ip
multicast-routing.
Following is the debug from R2:
Nov 12 05:01:24.330: IGMP(0): Received v2 Report on
FastEthernet0/0 from
172.16.80.1 for 229.10.10.10
*Nov 12 05:01:24.330: IGMP(0): Received Group record for group
229.10.10.10, mode 2 from 172.16.80.1 for 0 sources
*Nov 12 05:01:24.330: IGMP(0): Updating EXCLUDE group timer for
229.10.10.10
*Nov 12 05:01:24.330: IGMP(0): MRT Add/Update FastEthernet0/0
for
(*,229.10.10.10) by 0
Sh ip mroute from R2:
(*, 229.10.10.10), 00:05:37/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:05:37/00:00:00
(172.16.80.2, 229.10.10.10), 00:04:58/00:01:03, flags: PT
Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
(*, 224.0.1.40), 00:06:32/00:02:21, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:06:32/00:00:00
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3