From: steveaggie@gmail.com
Date: Tue Nov 27 2007 - 00:57:17 ART
I figured it out. Multicast packets received by R5 were failing the RPF
check. The best route back to R2's Lo0 was through a different port than
the multicast packet was arriving on. I shutdown the culprit Ethernet port
and everything started working fine. I guess the route was selected due to
EIGRP having a lower administrative distance than OSPF, or maybe I missed
something along the way in the lab. Either way I learned a lot about
multicast tonight which I guess is the most important thing. J
Thanks for your help Kim.
From: Kim teu [mailto:kim.teu@gmail.com]
Sent: Monday, November 26, 2007 9:34 PM
To: steveaggie@gmail.com
Subject: Re: IEWBv4.1 Lab 1 - Q5.2 - Multicast Auto-RP
Check your S1/1 interface on R3 to make sure that it is truely sparse-dense
mode and make sure you have broadcast keyword defined in the fr map. For
some reason R3 is not forwarding anything out this interface.
On 11/26/07, steveaggie@gmail.com <steveaggie@gmail.com> wrote:
R2-
IP Multicast Statistics
4 routes using 2484 bytes of memory
2 groups, 1.00 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 224.0.1.39 <http://224.0.1.39/> , Source count: 1, Packets forwarded:
344, Packets received: 348
Source: 150.1.3.3/32, Forwarding: 344/0/48/0, Other: 348/4/0
Group: 224.0.1.40 <http://224.0.1.40/> , Source count: 1, Packets forwarded:
0, Packets received: 0
Source: 150.1.2.2/32, Forwarding: 0/0/0/0, Other: 0/0/0
R3-
IP Multicast Statistics
4 routes using 2308 bytes of memory
2 groups, 1.00 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 224.0.1.39 <http://224.0.1.39/> , Source count: 1, Packets forwarded:
0, Packets received: 0
Source: 150.1.3.3/32, Forwarding: 0/0/0/0, Other: 0/0/0
Group: 224.0.1.40 <http://224.0.1.40/> , Source count: 1, Packets forwarded:
106, Packets received: 106
Source: 150.1.2.2/32, Forwarding: 106/0/48/0, Other: 106/0/0
R5-
IP Multicast Statistics
4 routes using 2008 bytes of memory
3 groups, 0.33 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 226.26.26.26 <http://226.26.26.26/> , Source count: 0, Packets
forwarded: 0, Packets received: 0
Group: 224.0.1.39 <http://224.0.1.39/> , Source count: 1, Packets forwarded:
0, Packets received: 2
Source: 150.1.3.3/32, Forwarding: 0/-1/0/0, Other: 2/0/2
Group: 224.0.1.40 <http://224.0.1.40/> , Source count: 0, Packets forwarded:
0, Packets received: 0
From: Kim teu [mailto:kim.teu@gmail.com ]
Sent: Monday, November 26, 2007 9:10 PM
To: steveaggie@gmail.com
Subject: Re: IEWBv4.1 Lab 1 - Q5.2 - Multicast Auto-RP
do a sho ip mrout count
On 11/26/07, steveaggie@gmail.com < steveaggie@gmail.com
<mailto:steveaggie@gmail.com> > wrote:
Yes and they are PIM neighbors.
Here is a show ip mroute from each if that helps:
R2-
(*, 224.0.1.39 <http://224.0.1.39/> ), 02:45:36/stopped, RP 0.0.0.0
<http://0.0.0.0/> , flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list:
Serial1/0, Forward/Sparse-Dense, 00:44:34/00:00:00
FastEthernet0/0, Forward/Sparse-Dense, 02:45:36/00:00:00
Loopback0, Forward/Sparse, 02:45:36/00:02:24
(150.1.3.3 <http://150.1.3.3/> , 224.0.1.39 <http://224.0.1.39/> ),
02:45:24/00:02:39, flags: LT
Incoming interface: Serial1/0, RPF nbr 183.1.123.1 <http://183.1.123.1/>
Outgoing interface list:
Loopback0, Forward/Sparse, 02:45:24/00:02:24
FastEthernet0/0, Forward/Sparse-Dense, 02:45:24/00:00:00
(*, 224.0.1.40 <http://224.0.1.40/> ), 02:45:44/stopped, RP 0.0.0.0
<http://0.0.0.0/> , flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list:
Loopback0, Forward/Sparse, 02:45:44/00:02:21
(150.1.2.2 <http://150.1.2.2/> , 224.0.1.40 <http://224.0.1.40/> ),
02:42:27/00:02:35, flags: PLT
Incoming interface: Loopback0, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list: Null
R3-
(*, 224.0.1.39 <http://224.0.1.39/> ), 01:37:15/stopped, RP 0.0.0.0
<http://0.0.0.0/> , flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list:
Serial1/0, Forward/Sparse-Dense, 00:58:09/00:00:00
(150.1.3.3 <http://150.1.3.3/> , 224.0.1.39 <http://224.0.1.39/> ),
01:37:00/00:02:00, flags: T
Incoming interface: Loopback0, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list:
Serial1/1, Prune/Sparse-Dense, 00:02:59/00:00:30
Serial1/0, Forward/Sparse-Dense, 00:58:09/00:00:00
(*, 224.0.1.40 <http://224.0.1.40/> ), 01:37:15/stopped, RP 0.0.0.0
<http://0.0.0.0/> , flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list:
Loopback0, Forward/Sparse, 01:37:15/00:02:40
(150.1.2.2 <http://150.1.2.2/> , 224.0.1.40 <http://224.0.1.40/> ),
01:36:22/00:02:07, flags: LT
Incoming interface: Serial1/0, RPF nbr 183.1.123.2 <http://183.1.123.2/>
Outgoing interface list:
Loopback0, Forward/Sparse, 01:36:23/00:02:38
R5-
(*, 226.26.26.26 <http://226.26.26.26/> ), 00:45:11/00:02:38, RP 0.0.0.0
<http://0.0.0.0/> , flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list:
Ethernet0/0, Forward/Sparse-Dense, 00:45:11/00:00:00
(*, 224.0.1.39 <http://224.0.1.39/> ), 01:05:17/00:02:43, RP 0.0.0.0
<http://0.0.0.0/> , flags: DP
Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list: Null
(*, 224.0.1.40 <http://224.0.1.40/> ), 01:05:30/00:02:42, RP 0.0.0.0
<http://0.0.0.0/> , flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0/>
Outgoing interface list:
Ethernet0/0, Forward/Sparse-Dense, 01:05:30/00:00:00
From: Kim teu [mailto:kim.teu@gmail.com ]
Sent: Monday, November 26, 2007 8:59 PM
To: steveaggie@gmail.com
Cc: ccielab@groupstudy.com
Subject: Re: IEWBv4.1 Lab 1 - Q5.2 - Multicast Auto-RP
Do you have pim sparse-den mode enable on all the FR interfaces? Are they
all neighbored up?
Kim
On 11/26/07, steveaggie@gmail.com < steveaggie@gmail.com
<mailto:steveaggie@gmail.com> > wrote:
I am trying to set up the Auto-RP scenario.
The connection looks like this:
R2----(FR)------R3-------(FR)-------R5
R3 has separate physical interfaces for each frame relay connection.
R3 is set up as the only C-RP
R2 is setup as the mapping agent
R5 has a static join configured on it's E0/0 interface for group
226.26.26.26 <http://226.26.26.26/>
My problem is that R5 does not receive the RP mapping announcement from R2.
I have a feeling this has to do with some multicast limitation of Frame
Relay, but I can't figure out what. I have tried enabling PIM NBMA-mode on
all of the interfaces.
If I configure R5 with a static RP address of R3, then everything works
fine. (i.e. I can ping the multicast group from Fa0/0 of R2)
Thanks
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:31 ART