Troubleshooting Tools

Are troubleshooting actions logged for auditing purposes?

Yes, all troubleshooting actions including test runs, reboots, and device location triggers are recorded in the Audit Trail. This ensures traceability and accountability for network diagnostics. Additionally, any configuration changes made through troubleshooting commands (where allowed) are also logged in the Audit Trail, beyond just test runs.

Can I review past troubleshooting sessions?

Yes, the History tab in Troubleshooting Tools displays:

  • A list of previously conducted tests

  • Session IDs for each test

  • Detailed results for review

The history of troubleshooting session is stored for 7 days.

Can I download the results of troubleshooting tests and commands?

When viewing a session in the History tab, export option is available under the Actions button. You can download results of tests, remote console, and show commands.

What is a troubleshooting session and how do we store the history of troubleshooting sessions?

A troubleshooting session begins when you open the troubleshooting page and start an action. The session continues until you close the troubleshooting page or until you log out of the UI session. Any pending tests during logout continue to run in the background and you can view the results later in the History tab within the troubleshooting page. You can add notes to the troubleshooting sessions for quick reference.

How long does HPE Aruba Networking Central retain audit trail logs?

Audit trail logs are retained for 90 days in HPE Aruba Networking Central. The logs can be exported as CSV files. In future updates, these logs will be accessible through Streaming APIs for extended retention and external integration.

Can I execute multiple commands on a device at once?

You can select up to 20 commands at once in one run before clicking the run button.

Can I run a command on multiple devices at once?

When you open a troubleshooting page from site, you can run a specific command on up to 10 devices in one run within the Commands tab. You can repeat a troubleshooting command for a specific duration and interval. For example, run a list of commands every 5 minutes for the next 1 hour.