PrepAway - Latest Free Exam Questions & Answers

What are three reasons an OSPF neighbor ship would be stuck in ExStart?

What are three reasons an OSPF neighbor ship would be stuck in ExStart? (Choose three.)

PrepAway - Latest Free Exam Questions & Answers

A.
Both OSPF routers are using the same router ID.

B.
There is a unicast communication problem between the OSPF routers.

C.
The LSA database exchange is not yet completed.

D.
There is an interface-type mismatch between the OSPF routers.

E.
There is an MTU mismatch between the OSPF routers.

Explanation:

5 Comments on “What are three reasons an OSPF neighbor ship would be stuck in ExStart?

  1. Mysteryman says:

    B,D,E

    If the same have the same RID the OSPF adjency never reaches the “init” state.

    Init
    This state specifies that the router has received a hello packet from its neighbor, but the receiving router’s ID was not included in the 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.

    2-Way
    This state designates that bi-directional communication has been established between two routers. Bi-directional means that each router has seen the other’s hello packet. This state is attained when the router receiving the hello packet sees its own Router ID within the received hello packet’s neighbor field. At this state, a router decides whether to become adjacent with this neighbor.




    0



    0

Leave a Reply