RE: Multicast Question

From: Sheahan, John (John.Sheahan@priceline.com)
Date: Fri Jun 10 2005 - 16:31:39 GMT-3


That makes sense.

The hosts are all plugged into a 2948 switch and so is R1.
There is also a domain controller plugged into the 2948 that is
multicasting to 224.0.1.24 which is Microsofts DS address (I think). I
will occasionally see (63.240.45.101, 224.0.1.24) show up in the MROUTE
table with the correct Incoming interface so I know at least somethings
are working correctly.

-----Original Message-----
From: George Cassels [mailto:glcassels3@nc.rr.com]
Sent: Friday, June 10, 2005 3:13 PM
To: Sheahan, John; 'Lee Donald'; ccielab@groupstudy.com
Subject: RE: Multicast Question

John,

     The TTL of 1 would still reach the router unless there is another
layer three device between the host and the router performing the debug
below. Is there any switch modules (installed in the router) or switch
in-between the host and the router?

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Sheahan, John
Sent: Friday, June 10, 2005 10:21 AM
To: Lee Donald; ccielab@groupstudy.com
Subject: RE: Multicast Question

Yes, I am seeing several hosts (besides HOSTA) sending to 230.22.22.25.
Could it be that the applications MCAST TTL is set to 1? Perhaps that is
why I'm not seeing the hosts in the MROUTE table for this flow?

1d23h: IP: s=63.240.45.24 (FastEthernet0/0), d=230.22.22.25, len 32,
rcvd 0
1d23h: IGMP: Received v2 Report on FastEthernet0/0 from 63.240.45.24 for
230.22.22.25
1d23h: IGMP: Received Group record for group 230.22.22.25, mode 2 from
63.240.45.24 for 0 sources
1d23h: IGMP: Updating EXCLUDE group timer for 230.22.22.25

-----Original Message-----
From: Lee Donald [mailto:Lee.Donald@t-systems.co.uk]
Sent: Friday, June 10, 2005 11:09 AM
To: Sheahan, John; ccielab@groupstudy.com
Subject: RE: Multicast Question

Yes you should see an incoming interface for this traffic and at the
moment
it is null, which means nothing.

Are you sure your host is sending? Do a debug ip pack det on router1 and
make sure this host exists?

-----Original Message-----
From: Sheahan, John [mailto:John.Sheahan@priceline.com]
Sent: 10 June 2005 15:51
To: ccielab@groupstudy.com
Subject: Multicast Question

I'm running Dense mode between 2 routers and have the following config
on each

Ip multicast routing

Int fa0/0

  Ip pim dense

Int fa1/0

  Ip pim dense

(HOSTA's address is 63.240.45.33)

HOSTA--------------R1-------------------------R2-------------------HOSTB

host a is sending traffic to 223.22.22.25 and .27 but I'm not seeing it
on r2 when I do a show ip mroute.

On r1, I'm seeing the following when I do a show ip mroute:

(*, 230.22.22.27), 00:24:20/00:02:38, RP 0.0.0.0, flags: DC

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet1/0, Forward/Dense, 00:24:20/00:00:00

    FastEthernet0/0, Forward/Dense, 00:24:20/00:00:00

(*, 230.22.22.25), 00:24:17/00:02:36, RP 0.0.0.0, flags: DC

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet1/0, Forward/Dense, 00:24:17/00:00:00

    FastEthernet0/0, Forward/Dense, 00:24:17/00:00:00

R1 obviously knows about the two multicast destinations, shouldn't I be
seeing an entry in the mroute table if HOSTA is indeed sending to
230.22.22.25 and .27?

Also, why is the incoming interface marked as NULL?

I thought I should be seeing something more like:

(63.240.45.33,230.22.22.25) ), 00:24:20/00:02:38, RP 0.0.0.0, flags: DC

  Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet1/0, Forward/Dense, 00:24:20/00:00:00

    FastEthernet0/0, Forward/Dense, 00:24:20/00:00:00



This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:41 GMT-3