OSPF supports multiple equal-cost links between node A and node B, but equal-cost load sharing is not implemented. The possible reason is that OSPF limits the number of maximum load-sharing links.

Question

Options

• ATRUE
• BFALSE

• A
  83% (19)
• B
  17% (4)

Explanation

Option A is correct because OSPF implementations enforce a configurable maximum-paths (or maximum-load-sharing) parameter that caps how many equal-cost paths are used for traffic distribution. If this limit is set to 1, or the number of equal-cost links exceeds the configured threshold, load sharing will not occur across all available paths - even though OSPF has discovered multiple equal-cost routes in the topology.

Option B is wrong because it denies a real constraint: the maximum-paths limit is a genuine reason why load sharing can fail to activate, making the TRUE statement accurate.

Memory tip: Think of OSPF's ECMP behavior as a highway with a tollbooth that only lets a fixed number of lanes open - no matter how many parallel roads exist, traffic only spreads across however many lanes (paths) the configuration allows.

No community discussion yet for this question.