Ospf state INIT and not FULL

[iccjflores]

Hello i have a problem beacuse the ospf protocol can´t pass to FULL state, this said that is INIT, the configuration in both interface are:

R_1#sh int multilink 11	R_2#sh int multilink 11
Multilink11 is up, line protocol is up	Multilink11 is up, line protocol is up
Hardware is multilink group interface	Hardware is multilink group interface
Description: R_2	Description: R_1
Internet address is 172.16.49.17/30	Internet address is 172.16.49.18/30
MTU 4470 bytes, BW 9920 Kbit, DLY 20000 usec,	MTU 4470 bytes, BW 9920 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255	reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Open, multilink Open	Encapsulation PPP, LCP Open, multilink Open
Open: IPCP, TAGCP, CDPCP, loopback not set	Open: IPCP, TAGCP, CDPCP, loopback not set
Keepalive set (10 sec)	Keepalive set (10 sec)
DTR is pulsed for 2 seconds on reset	DTR is pulsed for 2 seconds on reset
Last input 00:00:00, output 00:00:03, output hang never	Last input 6d21h, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:14:12	Last clearing of "show interface" counters 3d14h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0	Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: Class-based queueing	Queueing strategy: Class-based queueing
Output queue: 0/40 (size/max)	Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec	5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec	5 minute output rate 0 bits/sec, 0 packets/sec
1137 packets input, 52394 bytes, 0 no buffer	0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)	Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles	0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort	0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
840 packets output, 13440 bytes, 0 underruns	109525 packets output, 9386764 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets	0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out	0 output buffer failures, 0 output buffers swapped out
0 carrier transitions	0 carrier transitions
R_1#sh run int multilin11	R_2#sh run int multili11
interface Multilink11	interface Multilink11
Description: R_2	Description: R_1
mtu 4470	mtu 4470
ip address 172.16.49.17 255.255.255.252	ip address 172.16.49.18 255.255.255.252
ip ospf cost 7999	ip flow ingress
ip ospf mtu-ignore	ip ospf cost 7999
logging event link-status	ip ospf mtu-ignore
logging ip access-list cache in	logging event link-status
logging ip access-list cache out	mpls label protocol ldp
mpls label protocol ldp	mpls ip
mpls ip	ppp multilink
ppp multilink	ppp multilink links minimum 1
ppp multilink links maximum 5	ppp multilink group 11
ppp multilink links minimum 1	service-policy output TK-MPLS
ppp multilink group 11	end
service-policy output TK-MPLS
end Only on R1 i see the state of INIT
R_1#sh ip ospf neighbor	R_2#sh ip ospf neighbor
Neighbor ID     Pri   State           Dead Time   Address         Interface
150.220.250.180   0   INIT/  -        00:00:36    172.16.49.18    Multilink11

[Jan Hrnko · Accepted solution]

Hi,

there seems to be something wrong with your interface on R2. It has NO inputs whatsoever.

  Last input 6d21h, output 00:00:00, output hang never
  0 packets input, 0 bytes, 0 no buffer
  109525 packets output, 9386764 bytes, 0 underruns

Your show ip ospf neighbor output just underlines this fact.

The INIT state on R1 means, that R1 has received a hello packet from R2, but R1 can't see its own ID included in R2's hello packet. When a router receives a hello packet from a neighbor, it should list the sender's router ID in its hello packet as an acknowledgment that it received a valid hello packet. If it doesn't, OSPF remains stuck in INIT.

So, your output clearly says that R1 is sending hello packets and receiving some, but not with its own ID in it. R2 is sending hello packets to R1, but isn't receiving any.

The problem seems to be in underlying technology - link itself or the interface - have you tried to ping that interface? It shouldn't work.

I am sorry, but I don't know how to fix this, I just saw that you want make OSPF work but the problem seems to be somewhere else, not in OSPF itself or anything related to it.

Best regards,

Jan

[iccjflores]

Thanks....

ok, Ready...

when i make a ping between R1 and R2 don´t answer...

I do reset of interface because this have a problem with the Overload traffic and this bloked and dont work

[JohnTylerPearce]

This does sound like a connectivity issue between the two routers.

Can you post the output of 'show ip ospf int mu11' for me?

The link between these two routers, is this something you control, or is it provider equipment?

I also see 'mpls ip' is on each one, but labels are created from IGP.

Would it hurt anything to take off the 'mpls' config and try a test ping?

[iccjflores]

Hi...

Here is the command...

Multilink11 is up, line protocol is up

  Internet Address 172.16.49.17/30, Area 0

  Process ID 1, Router ID 150.220.250.1, Network Type POINT_TO_POINT, Cost: 12500

  Topology-MTID    Cost    Disabled    Shutdown      Topology Name

        0           12500     no          no            Base

  Transmit Delay is 1 sec, State POINT_TO_POINT

  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

    oob-resync timeout 40

    Hello due in 00:00:08

  Supports Link-local Signaling (LLS)

  Cisco NSF helper support enabled

  IETF NSF helper support enabled

  Index 16/16, flood queue length 0

  Next 0x0(0)/0x0(0)

  Last flood scan length is 1, maximum is 39

  Last flood scan time is 0 msec, maximum is 8 msec

  Neighbor Count is 1, Adjacent neighbor count is 1

    Adjacent with neighbor 150.220.250.180

  Suppress hello for 0 neighbor(s

Yes i have the control, the interface is saturated and bloeked,which although the status and protocol are up.

Apparently is a BUG so I'll have to upgrade the IOS