Ops wants to monitor control-plane CPU on leaves during MAC move storms. Why is that resource monitoring relevant in a DC fabric?
Select an answer to reveal the explanation.
Short Explanation
A MAC move storm is like a frantic roll call that keeps interrupting the principal—the leaf's control plane gets hammered while it relearns who sits where. Watching CPU/RE load tells you the office is overwhelmed before classrooms lose order. USB baud rates are not the story here.
Full Explanation
MAC moves and related overlay learning events increase control-plane processing on leaf devices. Monitoring Routing Engine or control-plane CPU during those storms helps operators see resource pressure that can precede protocol instability or delayed learning. Claiming leaf CPU is irrelevant, tying the issue to console baud rates, or dismissing leaf–spine coupling understates why device resource monitoring belongs in DC fabric operations.