City leaf peers establish BGP EVPN, but large UPDATE messages carrying many Type-2 routes are silently dropped on the path. Which transport health issue is the most likely cause?
Select an answer to reveal the explanation.
Short Explanation
Huge EVPN UPDATEs are like overloaded city buses — if the tunnel is too small, they never arrive. MTU or TCP MSS trouble on the peer path drops those big BGP payloads even when the session looks up. ESI, IRB mode, or matching RTs are different problems.
Full Explanation
EVPN can advertise large batches of MAC/IP routes in BGP UPDATEs. When the underlay path MTU or TCP MSS is insufficient, oversized segments may be dropped or fragmented unsuccessfully, so route exchange fails intermittently despite an Established session. ESI configuration, IRB architecture, and RT policy affect membership and forwarding models, not whether large TCP BGP payloads traverse the path.