OSPF Adjacency: Loading State vs Full State

Why is one device in the Loading state?

Prev Question Next Question

Question

Two Junos devices are trying to form an OSPF adjacency. When you issue the "show ospf neighbor" command, you see that one device is in the Loading state and the other is in the Full state. Why is one device in the Loading state?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B

The Loading state indicates that a device has finished transmitting its database to its peer but is still receiving database information from the neighboring device.

In OSPF, the adjacency between two devices is formed through a series of steps. During this process, the devices exchange link-state advertisements (LSAs) to build their databases and synchronize their network topology information. The devices go through different states until they reach the full adjacency state, which means that they have exchanged all the necessary information to converge their topology information.

In this scenario, one of the devices is in the Loading state, while the other device has already reached the Full state. This suggests that there might be an issue with the synchronization of their databases. The Loading state is an intermediate state that a device goes through when it receives an LSA that it does not have in its database.

Therefore, the correct answer is A. The device does not know about the received LSA header and has transmitted a link-state request. The device in the Loading state has requested more information from its neighbor, which is in the Full state, to complete its database. The neighbor device has responded to this request, and the devices are in the process of exchanging more LSAs until the Loading state device has a complete database and can transition to the Full state.

Option B, "The device has finished transmitting, but is still receiving database information," is incorrect because the device would not have finished transmitting if it is still in the Loading state. Similarly, option C, "The device is waiting for a start event," is incorrect because the devices have already established communication and are in the process of exchanging LSAs. Option D, "The device has established bidirectional communication with its peer," is not a sufficient explanation of why one device is in the Loading state while the other is in the Full state.