Question 460
In the fictional Metro-8 east pod, a multi-tenant fabric undergoing documented validation, the team reports that the same tenant MAC oscillates between attachments and causes instability. A peer suggested: "Turn the tenant L3 prefix into a static blackhole" That did not solve the constraint. What should be chosen instead?
Explanation
Correct Answer
MAC move visibility and controls address repeated endpoint relocation or loops in a bridge instance. For Metro-8, confirm the actual outcome: MAC learning stabilizes on the intended attachment without recurrent move alarms.
Incorrect Answers
“Turn the tenant L3 prefix into a static blackhole” targets a different operation from the reported requirement: “the same tenant MAC oscillates between attachments and causes instability”. MAC move visibility and controls address repeated endpoint relocation or loops in a bridge instance. Use the appropriate method: Inspect and apply the MAC move controls and investigate the attachment loop. Observe the relevant forwarding/control-plane behavior under the approved test.
“Increase BGP timers without examining the shifting MAC” targets a different operation from the reported requirement: “the same tenant MAC oscillates between attachments and causes instability”. MAC move visibility and controls address repeated endpoint relocation or loops in a bridge instance. Use the appropriate method: Inspect and apply the MAC move controls and investigate the attachment loop. Observe the relevant forwarding/control-plane behavior under the approved test.
“Change only the management username to stop MAC flaps” targets a different operation from the reported requirement: “the same tenant MAC oscillates between attachments and causes instability”. MAC move visibility and controls address repeated endpoint relocation or loops in a bridge instance. Use the appropriate method: Inspect and apply the MAC move controls and investigate the attachment loop. Observe the relevant forwarding/control-plane behavior under the approved test.