You recently made a configuration change on a switch, and shortly afterward, you noticed a spike in CPU utilization in the NAE dashboard. You are concerned that the high CPU could be affecting users. What should you do to restore service as quickly as possible?
Comprehensive Detailed Explanation:
When a recent configuration change causes a spike in CPU utilization that negatively impacts users, the fastest way to restore normal operation is to revert the change. This rollback immediately removes the offending configuration, potentially stabilizing the CPU and restoring service.
Rebooting the switch (Option A) is disruptive and takes more time.
Disabling debug logging (Option C) may help if debug is causing high CPU, but it doesn't undo config changes.
Pausing NAE monitoring (Option D) only suspends monitoring and doesn't address the root cause.
Hence, reverting the recent config change is the best immediate action.
ArubaOS-CX Network Automation Engine (NAE) Best Practices
Aruba Troubleshooting Guides for High CPU Utilization
HPE Aruba Configuration Rollback Procedures
Whitley
2 months agoHailey
3 months agoRosalind
3 months agoOlen
3 months agoCarlton
3 months agoCarmelina
3 months agoJean
3 months agoRutha
4 months agoJesus
4 months agoCeola
4 months agoJamie
5 months agoThomasena
5 months agoPaola
5 months agoDexter
5 months agoQuentin
5 months agoCaitlin
5 months agoKristel
6 months agoLaurel
6 months agoAshley
6 months agoIola
6 months agoJose
6 months agoTerrilyn
7 months agoBo
16 days agoRomana
2 months agoMicheline
2 months ago