Monitoring and Alerting with Aruba Central
A network operations center (NOC) uses Aruba Central to monitor 200 Aruba access points and 50 switches across multiple sites. The NOC wants to proactively detect issues such as AP down, high channel utilization, and switch port flapping. Currently, they only look at the dashboard manually. The team wants to set up alerts and reports. They also want to integrate with their existing ticketing system via webhooks. The network is configured with Aruba Central as the management platform, and all devices are connected and licensed.
1. What steps would you take to set up proactive monitoring and alerting in Aruba Central?
Read the worked answer
- Navigate to the Alerts & Events section in Aruba Central. 2. Create alert configurations for specific conditions: e.g., Device Down, High Channel Utilization (threshold >80%), Port Flapping (multiple up/down within a time window). 3. Define alert rules with severity levels and notification channels (email, webhook). 4. For webhook integration, configure the webhook URL provided by the ticketing system and select the alert types to send. 5. Set up scheduled reports for daily/weekly summaries. Reasoning: Aruba Central allows custom alerts based on device health and performance metrics. Webhooks enable integration with external systems. The NOC should also use the API for more advanced automation if needed.
2. How would you use the monitoring data to troubleshoot a recurring AP down issue?
Read the worked answer
Use the Alerts & Events list to identify which APs are going down and when. Check the AP details for uptime, reboot history, and connectivity. Use the 'Audit Trail' to see configuration changes. Analyze the switch port connected to the AP for PoE issues or errors. In Aruba Central, use the 'Connectivity' tab to see the AP's last seen time and reason for disconnection. Correlate with network events. Reasoning: Aruba Central provides historical data and event logs. By correlating alerts with switch port statistics and power events, you can identify root causes like PoE budget exhaustion or faulty cabling. Set up alerts for AP down with a delay to avoid false positives from reboots.