RE: OSPF Neighboring with DLSW Lite Encap

From: Brian Dennis (brian@labforge.com)
Date: Sun May 25 2003 - 22:58:58 GMT-3


On R2 you do not have the broadcast keyword on the Frame-relay map
statements. Init state means you are receiving hellos from the remote
end but you are not seeing your own router ID in the hellos.

Also there is no need for the "ip ospf priority 0" command with a
point-to-multipoint OSPF network.

Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Jeongwoo Park
Sent: Sunday, May 25, 2003 5:01 PM
To: lab
Subject: OSPF Neighboring with DLSW Lite Encap

Hi all.
Here is the problem I have.
 
R2(spoke)-----------R1(Hub)
 
They are running ospf.
I don't get the neighboring between these two routers.
It is stuck in INIT stage.
 
R2;
interface Serial0/0
 backup delay 0 10
 backup interface BRI0/0
 ip address 172.16.123.2 255.255.255.0
 encapsulation frame-relay
 ip ospf message-digest-key 1 md5 cisco
 ip ospf network point-to-multipoint
 ip ospf priority 0
 no fair-queue
 frame-relay map llc2 201 broadcast
 frame-relay map ip 172.16.123.2 201
 frame-relay map ip 172.16.123.3 201
 no frame-relay inverse-arp
 
R1:
interface Serial0/0.123 multipoint
 ip address 172.16.123.1 255.255.255.0
 ip ospf message-digest-key 1 md5 cisco
 ip ospf network point-to-multipoint
 frame-relay map llc2 102 broadcast
 frame-relay map ip 172.16.123.1 102 broadcast
 frame-relay map ip 172.16.123.3 103 broadcast
 no frame-relay inverse-arp
 
r2#sh ip ospf nei
 
Neighbor ID Pri State Dead Time Address
192.168.1.1 1 INIT/ - 00:01:35 172.16.123.1
r2#
 
If you need more configs, let me know.
 
Any idea why this fails with the neighboring?
 
Thanks
 
JP



This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:47 GMT-3