What can you determine about the OSPF operations from the debug output?

Refer to the exhibit.

You are the network administrator responsible for the NProuter, the 10.1.1.1 router, and the
10.1.1.2 router. What can you determine about the OSPF operations from the debug output?

Refer to the exhibit.

You are the network administrator responsible for the NProuter, the 10.1.1.1 router, and the
10.1.1.2 router. What can you determine about the OSPF operations from the debug output?

A.
The NProuter has two OSPF neighbors in the “Full” adjacency state.

B.
The NProuter serial0/0 interface has the OSPF dead timer set to 10 seconds.

C.
The NProuter serial0/0 interface has been configured with an OSPF network type of “pointtopoint”.

D.
The 10.1.1.1 and 10.1.1.2 routers are not using the default OSPF dead and hello timers setting.

E.
The “Mismatched” error is caused by the expiration of the OSPF timers.

Explanation:
First we should understand clearly about the line
Dead R120 C10,Hello R30 C30
The “R” here means “Received” and “C” means “Configured”. In other words, “Dead R” is the
Dead Timer Received from the neighbor and the “Dead C” is the Dead Timer of the local router.
Therefore in this case “Dead R 120 C 10 means the Death Timer of the neighbor is 120 seconds
while the local Dead Timer is 10 seconds, which causes a mismatch. Also we can learn that the
local OSPF dead timer is set to 10 seconds.
For your information, by default, OSPF uses a 10-second hello timer and 40-second hold timer on
broadcast and point-to-point links, and a 30-second hello timer and 120-second hold timer for all
other network types.



Leave a Reply 0

Your email address will not be published. Required fields are marked *