From: Gao, Lingping (Lingping.Gao@xxxxxxx)
Date: Thu Mar 02 2000 - 17:31:41 GMT-3
use "ip mroute" staticly nail down RPF check. Of course poing it to tunnel.
-----Original Message-----
From: Truman, Michelle, BNSVC [mailto:mtruman@att.com]
Sent: Wednesday, March 01, 2000 10:39 AM
To: 'ccielab@groupstudy.com'
Subject: Tunneling Multicast - PIM Sparse Mode and RPF checks
Hi All, just 8 days away from my test now. My how time flies!
I have a technical hurdle to overcome with Multicast. I am tunneling
multicast from Router A to router D. Router B and C are unaware of
Multicast. Diagram looks like this:
Router A
E0 network 12.1.1.1
EIGRP AS 1
E1 network
170.100.150.0
Tunnel 0 source e0
destination 170.100.16.4
|
|
Router B
E0 Network
170.100.150.0
EIGRP AS 1
redistribute to OSPF
10
S0 network
170.100.2.5
|
|
Router C
S0.1 network
170.100.2.1
S0.2 network
170.100.1.1
OSPF 10
|
|
Router D
S0 network
170.100.1.4
E0 network
170.100.16.4
Tunnel 0 source E0
destination 12.1.1.1
OSPF 10
Problem is that Multicast Routing performs an RPF check for the RP
destination. The route to 12.1.1.1 from Router D goes through Serial 0 and
is heard via OSPF. But the Multicast path is supposed to be Tunnel 0. I
don't have an ip address for Tunnel zero. The rest of the OSPF domain needs
to know to reach network 12 via OSPF, but Router D needs to know how to
reach the RP via Tunnel 0. Reverse Path forwarding is failing for Multicast
because it uses the unicast table for route look up and network 12 is known
via Router C, not the tunnel. I don't want to turn up routing on the tunnel
if I can avoid it.
Any ideas?
Michelle Truman, CCNP
Internet Technologies Consultant-AT&T
mtruman@att.com
w 612-376-5137 vo 651-917-8104
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:03 GMT-3