From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Mon Jul 25 2005 - 00:08:33 GMT-3
Ah, yes. Thanks for pointing that out! That other frame map was left over
from a previous configuration (I hate when I do that)...arg! Thanks, Alex.
Dave
-----Original Message-----
From: nobody@groupstudy.com
To: ccielab@groupstudy.com
Sent: 7/24/2005 7:43 PM
Subject: RE: Tunneling to area 0 in OSPF
You don't have a frame-relay map on R3 Serial0 pointing back to
172.16.1.1:
interface Serial0
ip address 172.16.1.2 255.255.255.0
encapsulation frame-relay
ip ospf network point-to-point
frame-relay map ip 160.10.32.2 203 broadcast
no frame-relay inverse-arp
frame-relay lmi-type ansi
So Your Tunnel0 interface will be UP on R3 because it has a route to the
tunnel destination but
R3 is unable to send GRE-encapsulated OSPF Hello/traffic back to R2 due
to missing FR map - You most probably would
have also "encapsulation failed" messages scrolling down on R3 console
if You enable "debig ip packets"...
HTH
Cheers
Alex
#13405
Schulz, Dave wrote:
> Group -
>
> I tried doing a tunnel from a router (R3) with only OSPF area 50
configured to
> another (R2) through a serial link running only RIP. I set up a
tunnel
> (extending the area 0 to R3). But for some reason, I get the
following
> reoccuring message:
>
> R3.....
> 06:05:16: OSPF: Rcv hello from 160.10.37.2 area 0 from Tunnel0
10.1.1.1
> 06:05:16: OSPF: End of hello processing
>
> This only occurs at R3. At first, I thought the hello/dead timer were
an
> issue, but that is not the case. the links come up and so does the
tunnel.
> However, OSPF routes from area 50 will not get passed into the other
routers
> on area O. Here are the configs....any ideas on this one?
>
>
> R2.....
>
> interface Tunnel0
> ip address 10.1.1.1 255.255.255.0
> tunnel source Serial0.1
> tunnel destination 172.16.1.2
> !
> !
> interface Serial0.1 point-to-point
> ip address 172.16.1.1 255.255.255.0
> ip ospf network point-to-point
> frame-relay interface-dlci 302 protocol ip 160.10.32.1
> !
> interface Serial0.2 multipoint
> ip address 160.10.37.2 255.255.255.0
> frame-relay map ip 160.10.37.4 214 broadcast
> frame-relay map ip 160.10.37.5 215 broadcast
> !
> !
> router ospf 1
> log-adjacency-changes
> no auto-cost
> network 10.0.0.0 0.255.255.255 area 0
> network 160.10.37.0 0.0.0.255 area 0
> neighbor 160.10.37.5
> neighbor 160.10.37.4
> !
> router rip
> version 2
> network 172.16.0.0
> no auto-summary
> !
>
> R3.....
> interface Loopback0
> ip address 44.44.44.33 255.255.255.240 secondary
> ip address 44.44.44.65 255.255.255.240 secondary
> ip address 44.44.44.129 255.255.255.240 secondary
> ip address 44.44.44.49 255.255.255.240 secondary
> ip address 44.44.44.17 255.255.255.240
> ip ospf network point-to-point
> !
> interface Tunnel0
> ip address 10.1.1.2 255.255.255.0
> tunnel source Serial0
> tunnel destination 172.16.1.1
> !
> interface Serial0
> ip address 172.16.1.2 255.255.255.0
> encapsulation frame-relay
> ip ospf network point-to-point
> frame-relay map ip 160.10.32.2 203 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type ansi
> !
> !
> router ospf 1
> log-adjacency-changes
> no auto-cost
> network 10.0.0.0 0.255.255.255 area 0
> network 44.44.44.0 0.0.0.255 area 50
> !
> router rip
> version 2
> network 172.16.0.0
> !
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:31 GMT-3