From: Alexander Belov (abelov@technoserv.ru)
Date: Tue Apr 08 2008 - 06:14:49 ART
Hello,
What is exactly R4's and R5's tunnel configs?
I suppose You might need ip for tunnel source.... (instead of ip unnumbered)
Wbr,
Alex
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
theKonqueror
Sent: Tuesday, April 08, 2008 12:45 PM
To: groupstudy
Subject: RPF failures on multicast over gre tunnel
Hi,
I am trying to configure simple multicast in dense mode on 2 routers.
[R4]---------[R5]
Both routers are connected via frame-relay with static L3 mapping without
broadcast command.
----
R4#sh fram map
Serial1/0 (up): ip 155.1.0.5 dlci 405(0x195,0x6450), static,
CISCO, status defined, active
R4#
R5#sh fram map
Serial1/0 (up): ip 155.1.0.4 dlci 504(0x1F8,0x7C80), static,
CISCO, status defined, active
R5#
----
To make multicast work, I added a tunnel over serial interface on both
routers.
--
interface Tunnel0
ip unnumbered Serial1/0
ip pim dense-mode
tunnel source Serial1/0
tunnel destination 155.1.0.5
--
R4 e0/0 has joined group 224.2.2.2. Now when I try to ping 224.2.2.2 from
R5, R4 shows RPF failures as the rpf path is S1/0.
Even after adding mroute for rpf, incoming interface shows as S1/0 instead
of tunnel0.
--
ip mroute 155.1.0.5 255.255.255.255 Tunnel0
--
--
R4#sh ip mroute 224.2.2.2 | b 155
(155.1.0.5, 224.2.2.2), 00:00:17/00:02:42, flags: L
Incoming interface: Serial1/0, RPF nbr 0.0.0.0
Outgoing interface list:
Tunnel0, Forward/Dense, 00:00:17/00:00:00
Ethernet0/0, Forward/Dense, 00:00:17/00:00:00
R4#
--
Is there something wrong with the config, or do I need additional steps to
make multicast work over tunnel?
Thanks,
Rahul
--
Bugs can neither be created nor be removed from software by a developer.
They can only be converted from one form to another. The total number of
bugs in the software always remain constant.
.}l}..}l}.
This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:50 ART