No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ- Why ospf stuck in init state in NE40

Publication Date:  2012-07-27 Views:  120 Downloads:  0

Issue Description

ospf stuck in init state in many times . version:version:vrp (r) software, version 5.30 (ne40&80 v300r005c01b323spc001)

Alarm Information


Handling Process

The most common possible causes of this problem as follows: 1-an access list on one side is blocking ospf hellos. 2-multicast capabilities are broken on one side (6500 switch problem).
3-authentication is enabled on only one side (virtual link example).
4-the frame-relay map/dialer map statement on one side is missing the broadcast keyword. 5-hellos are getting lost on one side at layer 2.

Root Cause

Router receives an ospf hello from a neighbor, it sends the hello packet by including that neighbor's router id in the hello packet. if it doesn't include the neighbor's router id, the neighbor will be stuck in init. this is an indication of a problem. the first packet that a router receives will cause the router to go into init state. at this point, it is not a problem, but if the router stays in this state for a long time, it's an indication of a problem. it means that the neigh-bor router is not seeing hellos sent by this router—that's why it is not including the router id of the router in its hello packet.


As above mention points are the theory,we can check in configuration when such type of problem arise,