From: Wayne Gustavus (wgustavus@xxxxxxxxxxxxxx)
Date: Tue May 08 2001 - 19:15:40 GMT-3
Crl,
I believe that both you and Johnny had part of the answer. First, Johnny is
correct when he states that you need SR/TLB to go between your ethernet
domain and TR domain. Second, you are correct in stating that it is a
multicast issue that is causing problems since no m/cast packets make it
from the eth side through the SR/TLB process onto the TR (though they will
flow in the other direction). Even after switching over to neighbor
statments for the various routing protocols (RIPv2, EIGRP, OSPF) still will
not achieve the desired results.
If you really have to do this (run routing protocols across a bridged core
w/ SR/TLB), then I believe a tunnel is the only option. I can successfully
create an OSPF process and exchange routes in the scenario below. It
requires a tunnel between R1 and R7. Note that I have some extra routers in
the middle b/c I don't have any TR/Eth routers, though this does not matter.
Lo0
|
R1---token---R2---serial---R4---ethernet---R7--lo0
Notes:
-R2 and R4 have no ip routing
-R2 is performing SR/TLB
-R4 is transparently bridging traffic between R2 and R7
-R1 needs multiring ip
-the tunnel is between R1 To0 and R7 E1
-an OSPF adjcency forms between R1 and R7 over the tunnel
-R1 and R7 can see OSPF routes for the other's loopback
HTH,
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:36 GMT-3