Ops incorrectly associates VXLAN with an IRB on a municipal leaf and routed tenant traffic breaks. What configuration caution applies?
Select an answer to reveal the explanation.
Short Explanation
IRB is the doorway between the L2 room and the L3 hallway—hang it on the wrong wall and nobody routes. Tie IRB to the right bridge domain and L3 VNI, don’t just sprinkle VXLAN keywords nearby. Mis-hung doorways are a classic leaf foot-gun.
Full Explanation
Integrated routing and bridging is required for inter-subnet overlay traffic, but the IRB must be bound to the correct L2 segments and participate properly with L3 VNIs/routing instances. Incorrect VXLAN-on-IRB associations can black-hole gateway traffic even when pure L2 VNI bridging still looks partially alive. Leaves hosting endpoints are exactly where IRB/VXLAN integration matters. Repair the binding model rather than removing multitenant overlay design entirely.