OSPF Neighbor Stuck in INIT State
2
OSPF Neighbor Stuck in INIT When a router receives an OSPF Hello from a neighbor, it sends the Hello packet that includes that neighbor's router ID If it doesn't include the neighbor's router ID, the neighbor !ill be stuck in I"I# #his is an indicatio a problem #he $rst packet that a router receives !ill cause the router to go into I"I# state #he most common possible causes of this problem are as follo!s% & (n access list on one side is blocking OSPF Hellos ) *ulticast capabilities are broken on one side + -.. s!itch problem / (uthentication is enabled on onl0 one side +virtual link e1ample 2 #he frame3rela0 map4dialer map statement on one side is missing the broadcast ke0!ord - Hellos are getting lost on one side at 5a0er )
-
Upload
prashant-srivastava -
Category
Documents
-
view
6 -
download
0
description
WHY OSPF Neighbor Stuck in INIT State
Transcript of OSPF Neighbor Stuck in INIT State
OSPF Neighbor Stuck in INITWhen a router receives an OSPF Hello from a neighbor, it sends the Hello packet that includes that neighbor's router ID. 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.
The most common possible causes of this problem are 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.
![Babel Routing Protocol for OMNeT++ - arxiv.org · majority of wired network designs are stuck with OSPF ... (based on [9]) – This method ... Wireshark 1.12.7 packet sniffer) ...](https://static.fdocuments.in/doc/165x107/5ad8e29f7f8b9a865b8e03b2/babel-routing-protocol-for-omnet-arxivorg-of-wired-network-designs-are-stuck.jpg)
