From: Emmanuel Oppong (e-oppong@xxxxxxxxx)
Date: Fri May 31 2002 - 16:07:24 GMT-3
Don't you need sparse-dense mode on the ethernet interface instead instead
of dense mode?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Michael Popovich
Sent: Friday, May 31, 2002 11:35 AM
To: Tommy C; ccielab@groupstudy.com
Subject: Re: Multicast Question
That is something I missed but I am still unable to ping the multicast
address of 229.10.10.10.
The following is my mroute cache. I notice that it seems to be pointing to
Null on all routers:
R2
R2#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
M - MSDP created entry, X - Proxy Join Timer Running
A - Candidate for MSDP Advertisement
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 03:08:43/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 03:08:43/00:00:00
(150.50.17.2, 224.0.1.39), 02:58:50/00:02:10, flags: PCLT
Incoming interface: Ethernet0/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
(*, 224.0.1.40), 03:29:41/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 03:29:41/00:00:00
(*, 229.10.10.10), 00:02:59/00:03:29, RP 150.50.17.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:02:58/00:02:31
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:02:58/00:03:29
(150.50.17.2, 229.10.10.10), 00:02:59/00:00:00, flags: T
Incoming interface: Ethernet0/0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:02:58/00:02:01
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:02:58/00:02:59
(192.100.2.2, 229.10.10.10), 00:02:59/00:00:00, flags: P
Incoming interface: Serial0/0.2, RPF nbr 0.0.0.0
Outgoing interface list: Null
(192.100.2.5, 229.10.10.10), 00:00:23/00:02:37, flags: T
Incoming interface: Serial0/0.2, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:00:23/00:02:36
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:00:23/00:02:36
(192.100.2.6, 229.10.10.10), 00:01:39/00:01:20, flags: T
Incoming interface: Serial0/0.2, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:01:39/00:01:20
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:01:39/00:01:20
(192.168.50.5, 229.10.10.10), 00:00:24/00:02:35, flags:
Incoming interface: Serial0/0.2, RPF nbr 192.100.2.5
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:00:24/00:02:35
(192.168.50.6, 229.10.10.10), 00:01:39/00:01:20, flags:
Incoming interface: Serial0/0.2, RPF nbr 192.100.2.5
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:01:39/00:01:20
R2#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
M - MSDP created entry, X - Proxy Join Timer Running
A - Candidate for MSDP Advertisement
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 03:08:43/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 03:08:43/00:00:00
(150.50.17.2, 224.0.1.39), 02:58:50/00:02:10, flags: PCLT
Incoming interface: Ethernet0/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
(*, 224.0.1.40), 03:29:41/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Dense, 03:29:41/00:00:00
(*, 229.10.10.10), 00:02:59/00:03:29, RP 150.50.17.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:02:58/00:02:31
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:02:58/00:03:29
(150.50.17.2, 229.10.10.10), 00:02:59/00:00:00, flags: T
Incoming interface: Ethernet0/0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:02:58/00:02:01
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:02:58/00:02:59
(192.100.2.2, 229.10.10.10), 00:02:59/00:00:00, flags: P
Incoming interface: Serial0/0.2, RPF nbr 0.0.0.0
Outgoing interface list: Null
(192.100.2.5, 229.10.10.10), 00:00:23/00:02:37, flags: T
Incoming interface: Serial0/0.2, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:00:23/00:02:36
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:00:23/00:02:36
(192.100.2.6, 229.10.10.10), 00:01:39/00:01:20, flags: T
Incoming interface: Serial0/0.2, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.2, 192.100.2.5, Forward/Sparse, 00:01:39/00:01:20
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:01:39/00:01:20
(192.168.50.5, 229.10.10.10), 00:00:24/00:02:35, flags:
Incoming interface: Serial0/0.2, RPF nbr 192.100.2.5
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:00:24/00:02:35
(192.168.50.6, 229.10.10.10), 00:01:39/00:01:20, flags:
Incoming interface: Serial0/0.2, RPF nbr 192.100.2.5
Outgoing interface list:
Serial0/0.2, 192.100.2.6, Forward/Sparse, 00:01:39/00:01:20
R5
R5#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
M - MSDP created entry, X - Proxy Join Timer Running
A - Candidate for MSDP Advertisement
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 03:28:56/00:02:59, RP 0.0.0.0, flags: DJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, 224.0.1.39, Forward/Sparse, 03:09:09/00:02:54
FastEthernet0/0, Forward/Dense, 03:28:56/00:00:00
(150.50.17.2, 224.0.1.39), 00:01:15/00:01:44, flags: PCT
Incoming interface: Serial0/0, RPF nbr 192.100.2.2
Outgoing interface list:
FastEthernet0/0, Prune/Dense, 00:01:15/00:01:44
(*, 224.0.1.40), 03:29:32/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 03:28:57/00:00:00
Serial0/0, 224.0.1.40, Forward/Sparse, 03:29:33/00:02:54
(192.100.2.2, 224.0.1.40), 03:08:57/00:02:25, flags: PCLT
Incoming interface: Serial0/0, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Prune/Dense, 03:08:57/00:02:25
(*, 229.10.10.10), 00:03:23/00:02:59, RP 150.50.17.2, flags: SF
Incoming interface: Serial0/0, RPF nbr 192.100.2.2
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:03:23/00:00:00
(192.100.2.5, 229.10.10.10), 00:00:47/00:02:12, flags: PFT
Incoming interface: Serial0/0, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Prune/Dense, 00:00:47/00:02:12
(192.100.2.6, 229.10.10.10), 00:02:02/00:00:57, flags: PFT
Incoming interface: Serial0/0, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Prune/Dense, 00:02:02/00:00:57
(192.168.50.5, 229.10.10.10), 00:00:48/00:02:41, flags: T
Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, 192.100.2.2, Forward/Sparse, 00:00:48/00:03:05
(192.168.50.6, 229.10.10.10), 00:02:03/00:00:56, flags: T
Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, 192.100.2.2, Forward/Sparse, 00:02:03/00:03:05
R6
R6#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
M - MSDP created entry, X - Proxy Join Timer Running
A - Candidate for MSDP Advertisement
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.39), 03:29:21/00:02:59, RP 0.0.0.0, flags: DJC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0, 224.0.1.39, Forward/Sparse, 03:09:33/00:02:30
Ethernet0, Forward/Dense, 03:29:21/00:00:00
(150.50.17.2, 224.0.1.39), 00:01:39/00:01:20, flags: PCT
Incoming interface: Serial0, RPF nbr 192.100.2.2
Outgoing interface list:
Ethernet0, Prune/Dense, 00:01:39/00:01:25
(*, 224.0.1.40), 03:29:31/00:00:00, RP 0.0.0.0, flags: DJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0, Forward/Dense, 03:29:22/00:00:00
Serial0, 224.0.1.40, Forward/Sparse, 03:29:30/00:02:28
(192.100.2.2, 224.0.1.40), 03:09:21/00:02:01, flags: PCLT
Incoming interface: Serial0, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0, Prune/Dense, 03:09:21/00:02:06
(*, 229.10.10.10), 00:03:47/00:02:59, RP 150.50.17.2, flags: SF
Incoming interface: Serial0, RPF nbr 192.100.2.2
Outgoing interface list:
Ethernet0, Forward/Dense, 00:03:47/00:00:00
(192.100.2.5, 229.10.10.10), 00:01:11/00:01:48, flags: T
Incoming interface: Serial0, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0, Forward/Dense, 00:01:11/00:00:00
(192.100.2.6, 229.10.10.10), 00:02:26/00:00:33, flags: T
Incoming interface: Serial0, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0, Forward/Dense, 00:02:27/00:00:00
(192.168.50.5, 229.10.10.10), 00:01:12/00:01:47, flags: PFT
Incoming interface: Ethernet0, RPF nbr 0.0.0.0, Registering
Outgoing interface list: Null
(192.168.50.6, 229.10.10.10), 00:02:27/00:00:32, flags: PFT
Incoming interface: Ethernet0, RPF nbr 0.0.0.0, Registering
Outgoing interface list: Null
Any ideas on this?
MP
----- Original Message -----
From: "Tommy C" <tkc9789@hotmail.com>
To: <m.popovich@mchsi.com>; <ccielab@groupstudy.com>
Sent: Friday, May 31, 2002 1:04 PM
Subject: Re: Multicast Question
> Michael,
> If I remember correctly, you need IP Pim nbma on r2's frame interface.
>
> Tommy
>
>
> >From: "Michael Popovich" <m.popovich@mchsi.com>
> >Reply-To: "Michael Popovich" <m.popovich@mchsi.com>
> >To: "CCIE GROUPSTUDY" <ccielab@groupstudy.com>
> >Subject: Multicast Question
> >Date: Fri, 31 May 2002 10:44:54 -0500
> >
> >I have the following setup
> >
> >--E-----R2
> > \
> > \
> > Frame
> > / \
> > / \
> > R5 R6
> > | |
> > |---------E------|
> >
> >The multicast group of 229.10.10.10 is on the Ethernet segment of R2. I
> >have
> >R2 setup using Auto-RP with R2 being the RP and the Mapping Agent.
> >
> >R5 and R6 have 229.10.10.10 in the rp-mapping table and mroute cache
> >pointing
> >to the Ethernet interface of R2. Using PIM Sparse on the Frame and PIM
> >Dense
> >on the Ethernet segments.
> >
> >What do I need to do in order to ping 229.10.10.10? I can't right now and
I
> >thought I should be able to.
> >
> >TIA
> >
> >MP
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:13 GMT-3