Question 490
A new Apstra agent stops reporting after a management VLAN migration while spine-to-leaf data-plane interfaces remain operational. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Test management-plane connectivity whenever changing out-of-band or device-agent networks. That is important in this case because controller-to-device management reachability uses its own routed and authorized path separate from the switching fabric's ordinary tenant forwarding. The scenario was: A new Apstra agent stops reporting after a management VLAN migration while spine-to-leaf data-plane interfaces remain operational.
Incorrect Answers
Retest interface-map compatibility and required breakouts for each hardware substitution. That concerns interface map assignment for new hardware, while the issue here is appliance onboarding management route. Verify management addressing, gateway, DNS or certificate dependencies where applicable and least-privilege firewall reachability to restore agent communication.
Apstra uses planned physical link relationships and observed neighbor data to validate whether actual cabling matches the staged blueprint. For this issue, verify management addressing, gateway, DNS or certificate dependencies where applicable and least-privilege firewall reachability to restore agent communication.
Distinguish rendered preview, uncommitted intent and active configuration in commissioning records. Here, controller-to-device management reachability uses its own routed and authorized path separate from the switching fabric's ordinary tenant forwarding.