Alerts Dashboard

To navigate to the Alerts dashboard, complete the following steps:

1. In the HPE Aruba Networking Central landing page, select a site from the Sites menu.

   Alternatively, you can click the expand icon on the Sites menu to search for a site from the list.

   The site dashboard is displayed with the network and connectivity information for the site.

2. Click Alerts.

   The Alerts page is displayed.

3. Click the alert name.

   Alternatively, you can select an alert to view the alert side panel and then click Go to Alert. For more information on the alert side panel, see Viewing Alert-Specific Information in List View.

The dashboard context for the selected alert is displayed.

Figure 1: Alert Dashboard Sample 1

Figure 2: Alert Dashboard Sample 2

The following sections describe the UI elements that you can use to navigate through the UI and drill down into increasingly detailed information:

• Alert Context

• Site

• Network

• Clients

• Summary Card

• Performance Trend Card Graphs

• Impact Card

• Actions Card

• Troubleshooting Card

• Overall Impacted Clients for the Customer (1 Day)

• Events Card

• Alert History Card

Alert Context

Displays the alert name and a brief description of the alert.

You can also perform the following:

• Note—To add a note, complete the following steps:

  1. Click the icon.

     The Note pop-up window is displayed.

  2. Enter the note and click Save.

     Note: The note icon fills with black when a note is added. To delete a note, click the icon and click Delete.

Site

Displays the impacted site and its health.

Click Site to view the site information. For more information, see Monitoring Site Health.

Network

Displays the overall health and number of devices impacted by the alert.

Click Network to view the LAN and Services cards. For more information on LAN and Services card, see Unified Device List.

Clients

Displays the number of clients impacted by the alert.

Click Clients to view the Client Summary view and Client List view. For more information, see Unified Client List.

Summary Card

The Summary card displays the description of the alert and the time that it has been active.

The following table describes the Summary card parameters:

Table 1: Summary Card Parameters

Parameter	Description
Severity	Indicates the severity of the alert as one of the following: Critical —Indicates that the severity of the alert is greater than or equal to 75%. Major —Indicates that the severity of the alert is between 50% and 75%. Minor —Indicates that the severity of the alert is between 25% and 50%.
Description	Displays the description of the alert.
First Occurred	Displays the date and time when the alert was first triggered.
Last Occurred	Displays the date and time when the alert was last triggered.
Occurrences	Displays the number of times the alert was triggered within the last 30 days.
Duration	Displays the duration of the current alert instance. Note: For Cleared alerts, the duration of the last occurred alert is displayed. For event-based alert, the duration is not displayed. For AIOps alerts, the duration is calculated using the below formula: (Last Occurred - First Occurred) + 5 Minutes
Priority	Displays the priority of the alert.

For active alerts, you can click on the device Serial Number, Hostname, Cluster Name, or MAC address to navigate to the corresponding monitoring page.

Performance Trend Card Graphs

If applicable, the following performance trend graphs are displayed:

AP Radio Channel Utilization Graph

The AP Radio Channel Utilization graph indicates the percentage of channel utilization for the selected time. You can hover over the graph to view the actual values. The channel utilization information is categorized as follows:

• Transmitting—The percentage of channel currently being transmitted.

• Receiving—The percentage of channel currently being received.

• Non-life Interference—The percentage of channel currently being used by non-Wi-Fi interferences.

• Threshold—Indicates the threshold value.

  Figure 3: AP Radio Channel Utilization Graph

  

AP Radio Noise Floor Graph

The AP Radio Noise Floor graph indicates the noise floor (in DBm) detected in the network to which the device belongs. You can hover over the graph to view the actual values.

Figure 4: AP Radio Noise Floor Graph

AP Radio Non-Wi-Fi Interference Graph

The AP Radio Noise Floor graph displays the level of non-Wi-Fi interference over the selected timeline. You can hover over the graph to see the exact values at specific points in time.

Figure 5: AP Radio Non-Wi-Fi Interference Graph

AP Memory Utilization

The time series graph displays the count of access points (APs) experiencing high memory utilization within the network over the selected time period. Hover over each bar in the graph to view the precise number of affected APs.

Figure 6: AP Memory Utilization

AP CPU Utilization

The time series graph displays the number of access points (APs) with high CPU utilization in the network over the selected time period. You can hover over each bar in the graph to view the exact count of affected APs.

Figure 7: AP CPU Utilization

Impact Card

The card displays the percentage and actual number of impacted clients, APs, switches, and gateways by the alert. If no clients or devices are impacted, the card will display No Impact.

Figure 8: Impact Card Sample 1

Figure 9: Impact Card Sample 2

Actions Card

The Actions card displays the root cause of the alert along with recommendations to troubleshoot it. Click on the icon to view the following details:

• Root Cause—Lists the potential causes of the alert. AIOps utilizes alert grouping to analyze data and dynamically identify the contributing factors.

  For Switch CPU Utilization and Switch Memory Utilization alerts, the Root Cause section highlights the top five processes responsible for high utilization.

  Note: CPU utilization for processes is measured per CPU core. Since AOS-CX switches have multiple cores, the overall CPU utilization for a process can exceed 100%.

• Actions card—The Actions card provides recommendations to address the warning. These recommendations are generated using AI algorithms designed to optimize network configurations and suggest performance enhancements.

  Figure 10: Actions Card

  

  For alerts such as Interface CRC Errors, Port Flaps, and AP Connected at 10/100 Mbps, you can perform a Cable Test to determine if a faulty cable is causing the issue. To run a cable test, perform the following steps:

  1. Click the icon to view the expanded Actions page.

  2. Under Actions, click the Cable Test button.

     The results of the cable test are displayed. You can click the Troubleshoot icon to view the details on the Troubleshoot page. Alternatively, you can navigate to the Alerts Dashboard and locate the Troubleshooting card to review the results.

     Figure 11: Cable Test Sample

     

For Config Out of Sync alerts, you can use the Link option to navigate to the Configuration Health Dashboard to fix the errors on the device.

Figure 12: Config Out of Sync Alert - Action Card Sample

For more information, see Configuration Health Dashboard.

Troubleshooting Card

The card displays the steps performed by the system to resolve the issue, as well as the success or failure of each step.

The system can perform the following troubleshooting steps:

• Ping

• VLAN Configuration Check

• Other Client(s) IP Allocation Check in Same VLAN

The results of these steps are indicated using the following legends:

• Green—The step was successful.

• Red—The step failed.

Click on the icon to view the Troubleshoot page.

The ORCA (Orchestrated Root Cause Analysis) tab is displayed by default.

ORCA Tab

Figure 13: Troubleshoot - ORCA (Orchestrated Root Cause Analysis) Page

In the ORCA tab, you can view and perform the following:

• Potential Root Causes section—The ORCA tab renders the steps on the left side and the corresponding outputs of each step on the right-side window. You can use the Recipe Troubleshooting Time drop-down to review results from prior tests.

• Re-run Test—Click the Re-run Test button to execute the troubleshooting steps again. You can select one or more steps in the user interface to re-trigger specific actions.

  Note: The Re-run Test option is not supported for OSPF Peer Down and Radius Server Status alerts.

• Results window—The pane on the right-side displays the results of the troubleshooting steps. Use the icon to toggle to the Console View. Click the to return to the Widget View.

Tests Tab

The Tests tab offers a suite of diagnostic tools designed to identify and resolve network or device-related issues. For more information, see Tests.

Remote Console Tab

The Remote Console tab enables browser-based SSH access to devices using privileged administrator credentials. For more information, see Remote Console.

History Tab

The History tab displays information about troubleshooting tests conducted in the past. Users can click on individual session IDs to view the complete details of each test. For more information, see History.

Overall Impacted Clients for the Customer (1 Day)

The graph displays the count of impacted clients during the last 24 hours. Hover over the graph to view the actual count.

Figure 14: Overall Impacted Clients

Events Card

Displays the associated events that occurred in the last 10 minutes of alert creation for the impacted devices and clients.

Figure 15: Events Card

You can click on the icon to view the following details:

Table 2: Events Card Parameters

Parameter	Description
Occurred	Displays the date and time of the event.
Event	Displays the name of the event.
Category	Displays the category of the event.
Source Type	Displays from where the event was triggered.
Source Name	Displays the name of the impacted device or client.
Description	Displays the description of the event.
Device MAC Address	Displays the MAC address of the device.
Client MAC Address	Displays the MAC address of the client.

To customize the table, click the icon to select the required columns, or click Reset to Defaults to set the table to the default columns. For more information, see Viewing Devices in the List View.

You can also use the search bar to search for an alert by keywords. For more information, see Filtering Devices in the List View.

Alert History Card

The Alert History Card provides a graphical representation of the trend of the primary Key Performance Indicator (KPI) that triggered the alert over time. This card helps users understand when and why the alert was issued.

The card displays one of the following types of graphs based on the triggering mechanism:

• Alerts Triggered by a Threshold

  These alerts are triggered when the primary KPI exceeds a defined threshold.

  Figure 16: Alerts Triggered by Threshold Chart

  

  The y-axis represents the primary KPI, while the x-axis represents the timeline. Hover over the graph to view details including the date and time, alert severity, the reason for the alert, the KPI value at that time, and the defined threshold value.

• Alerts Triggered by a Baseline

  The alert is triggered when the primary KPI deviates by a specified percentage above or below the baseline.

  Figure 17: Alerts Triggered by Baseline Chart

  

  The y-axis represents the primary KPI, while the x-axis represents the timeline. Hover over the graph to view the baseline band and a tooltip showing the date and time, alert severity, the reason for the alert, the KPI value at that time, and the baseline range.

• Alerts Triggered by Change in State

  The alert is triggered when the primary KPI's state changes for a defined period of time.

  Figure 18: Alerts Triggered by Change in Status

  

  The y-axis represents the status of the primary KPI, while the x-axis represents the timeline. Hover over the graph to view the date and time, alert severity, the reason for the alert, the KPI value at that time, and the state change.

  Click the icon to view the expanded view of the Alert History card. In the expanded view, you can view both the primary KPI graph and, when applicable, the events graph for deeper insights.

  Figure 19: History Card - Expanded View