County architects want each leaf to maintain fewer BGP sessions as…

Question

County architects want each leaf to maintain fewer BGP sessions as spine count grows, without abandoning multipath. Which control-plane approach best targets session-count scaling?

Accepted Answer

Use route reflection (or carefully limited peer sets) so leaves need not mesh every control-plane relationship densely — BGP sessions are like open phone lines—every extra spine can mean another call per leaf. Route reflection (or a deliberate peer design) keeps the conversation count manageable while multipath still does the heavy lifting for packets.

Answer

Require every leaf to open a full mesh of BGP sessions to every other leaf in addition to all spines

Answer

Replace BGP with RIP version 1 on leaf-spine links to cut TCP session state

Answer

Advertise only connected interfaces and never use loopbacks so session count drops automatically

County architects want each leaf to maintain fewer BGP sessions as spine count grows, without abandoning multipath. Which control-plane approach best targets session-count scaling?

Short Explanation

Full Explanation