RE: OSPF: Stuck in INIT (cont)

From: C. Warren (ccie2000@xxxxxxxx)
Date: Sun Aug 05 2001 - 20:21:15 GMT-3


   
That multicast address (224.0.0.10) is for EIGRP, OSPF is on
224.0.0.5/.6

Also, why do have a frame map statement under each interface for that
interface??? Excerpt follows....

interface Serial0
 ip address 170.10.235.2 255.255.255.240
 .
 .
 frame-relay map ip 170.10.235.2 102 broadcast

Chuck

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Daniel C. Young
Sent: Sunday, August 05, 2001 5:08 PM
To: ccielab@groupstudy.com
Subject: OSPF: Stuck in INIT (cont)

Additions:
All routers can ping one another.

It appears that the multicast on r2 is broken somehow. Here is the
output of
'deb ip pack' on r2:
00:28:33: IP: s=170.10.242.2 (local), d=224.0.0.10 (Loopback0), len 60,
sending
broad/multicast
00:28:33: IP: s=170.10.242.2 (Loopback0), d=224.0.0.10, len 60, rcvd 2
r2(config-if)#
00:28:35: IP: s=170.10.20.2 (local), d=224.0.0.10 (Ethernet0), len 60,
sending b
road/multicast

*Notice that it is not sending any multicast hellos to out of
170.10.235.2
(its serial interface to connect to r5).

Just in case you're thinking what I'm thinking, here is the ospf configs
on
r2:
!
router ospf 1
 network 170.10.23.0 0.0.0.255 area 0
 network 170.10.235.0 0.0.0.15 area 0

So, yes; it is in the ospf process, and yes, the interface is dlso
up/up:
r2#sh ip int brie
Interface IP-Address OK? Method Status
Prot
ocol
Ethernet0 170.10.20.2 YES NVRAM up
up

Loopback0 170.10.242.2 YES NVRAM up
up

Serial0 170.10.235.2 YES NVRAM up
up

So, why is it NOT showing up on the database?
r2#sh ip ospf data

       OSPF Router with ID (170.10.242.2) (Process ID 1)

                Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link
count
170.10.242.2 170.10.242.2 357 0x80000003 0x96A4 1

All it is showing is just the loopback/RID type 1 lsa. Any ideas?

Thanks,
Daniel

-----Original Message-----
From: Daniel C. Young [mailto:danyoung99@mediaone.net]
Sent: Sunday, August 05, 2001 2:56 PM
To: 'ccielab@groupstudy.com'
Subject: OSPF: Stuck in INIT

Scenario: OSPF over multipoint frame-relay; r5 as hub, r2 and r3 as
spokes.
r5 and r3 form adjacencies, but r2 and r5 do not. It appears that r5 is
not
receiving hellos from r2, although r2 receives them from r5.

r2#sh ip ospf nei
Neighbor ID Pri State Dead Time Address
Interface
170.10.245.5 100 INIT/ - 00:01:55 170.10.235.5
Serial0

r5#deb ip ospf adj
00:16:08: OSPF: Rcv hello from 170.10.245.5 area 0 from Serial0
170.10.235.5
00:16:08: OSPF: End of hello processing

r5#sh ip ospf nei
Neighbor ID Pri State Dead Time Address
Interface
170.10.243.3 0 FULL/ - 00:01:48 170.10.235.3
Serial0.1

r5#deb ip ospf adj
00:12:11: OSPF: Rcv hello from 170.10.243.3 area 0 from Serial0.1
170.10.235.3
00:12:11: OSPF: End of hello processing

[r2's config]
interface Serial0
 ip address 170.10.235.2 255.255.255.240
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-multipoint
 ip ospf priority 0
 no ip mroute-cache
 frame-relay map ip 170.10.235.2 102 broadcast
 frame-relay map ip 170.10.235.3 102 broadcast
 frame-relay map ip 170.10.235.5 102 broadcast
 frame-relay lmi-type ansi
end

[r3's config]
interface Serial0
 ip address 170.10.235.3 255.255.255.240
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-multipoint
 ip ospf interface-retry 0
 ip ospf priority 0
 no ip mroute-cache
 no fair-queue
 frame-relay map ip 170.10.235.2 204 broadcast
 frame-relay map ip 170.10.235.3 204 broadcast
 frame-relay map ip 170.10.235.5 204 broadcast
 frame-relay lmi-type ansi
end

[r5's config]
interface Serial0.1 multipoint
 ip address 170.10.235.5 255.255.255.240
 no ip directed-broadcast
 ip ospf network point-to-multipoint
 ip ospf priority 100
 frame-relay map ip 170.10.235.2 401 broadcast
 frame-relay map ip 170.10.235.3 402 broadcast
 frame-relay map ip 170.10.235.5 402 broadcast
end

Normally, stuck-in-INIT states are caused by leaving out the 'broadcast'
parameter, but this is not the case. Further, if it was a
misconfiguration
issue, r3 would also exhibit the same symptoms. IOS bug perhaps?

Regards,
Daniel

7 days and counting...
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:45 GMT-3