Management, Monitoring, and Automation (NetEdit, NAE, REST API)
NetEdit, NAE, and REST automation
NetEdit provides centralized configuration and change management for supported Aruba switches, often using a plan-review-deploy workflow. Candidates should understand device discovery, configuration templates, compliance, and rollback concepts. NAE (Network Analytics Engine) runs agent scripts on ArubaOS-CX switches to monitor state, create time-series data, and trigger actions such as syslog or CLI commands when conditions match. REST API exposes configuration and operational data over HTTPS; authentication typically uses a login token or session, and API versioning matters. Supporting tools include SNMP, syslog, NTP, AAA, and telemetry. NetEdit is not the same as cloud-based Central; know which tool owns which lifecycle stage.
Traps: treating NetEdit as a real-time packet analyzer; assuming NAE scripts can do anything outside their sandbox; forgetting API version and content-type headers; and using automation without idempotency or change validation. Also watch RBAC and management VRF reachability.
Worked example/rule of thumb: An NAE agent watches an interface error counter; a condition triggers an alert and a CLI action. Rule: use NAE for closed-loop detection, NetEdit for planned configuration, and REST for inventory/telemetry integration; always validate the API response and rollback plan.