QuestionQ13Verified/OSPFCopy linkReport a problemAsk AstroTutorSave question With reference to the exhibit, why does this OSPF adjacency remain in this state?AA subnet mask mismatch exists between the OSPF neighbors.BAn MTU mismatch exists between the OSPF neighbors.CA hello interval mismatch exists between the OSPF neighborsDAn area ID mismatch exists between the OSPF neighbors.Show AnswerAnswerExplanationAn OSPF adjacency stuck in ExStart typically indicates an interface MTU mismatch. During database-description packet negotiation, the routers compare MTU-related information; incompatible interface MTUs prevent the adjacency from advancing to Exchange and Full. Area ID, Hello interval, and subnet-mask mismatches prevent successful neighbor formation earlier in the process.Show comments0Show commentsCommunity DiscussionNo comments yet. Be the first to start the discussion!
Community Discussion