Resolved Issues

For switches running the firmware versions 16.11.009 and later versions, the configured duplex value was displayed for connected ports instead of negotiated duplex value. The fix ensures that the negotiated duplex value is displayed for connected ports. The negotiated duplex for a connected port will be displayed only on devices running firmware 16.11.009 and later versions. For all versions earlier than this, the configured duplex value will be displayed.

The HPE Aruba Networking Central UI incorrectly allowed users to create alias names exceeding 255 characters. The fix ensures that the Name field under the Create an Alias panel accepts only up to 255 characters.

The root cause for DHCP timeout alert was wrongly generated as Discover Server Timeout on the AI Insights tab. This issue occurred because timeout requests are not segregated as discover, offer, or request. The fix ensures that the alert does not display as Discover Server Timeout.

The client experience was not updated in the Connectivity card when the time selection was closed in the Timeline widget. The fix ensures that the client experience is updated as expected.

To filter clients, you can select multiple filtering criteria on the Standard and Classification tabs. When you select fields on either tab and switch to the other tab to make selections, none of the selections made on the previous tab are displayed.

The fix ensures that the filter selections made on both the tabs appear correctly.

In the client context of AOS-S switch authentication alerts, the count of impacted clients was not displayed. The fix ensures that the count of impacted clients is displayed correctly.

DHCP discover timeout alert was not generated for AOS-10 APs and not displayed on the Alerts page. This issue occurred because the AP sent the DHCP server information as Null for the DHCP discover timeout messages. The fix ensures that null values are handled in the DHCP discover timeout messages for AOS-10 APS.

VLAN mismatch alert was generated incorrectly on the Alerts page. This issue occurred because the transitions were not updated on the access platform. The fix ensures that trunk to access and routing transitions are updated and incorrect VLAN mismatch alerts are not generated.

In the Clients WPA Passphrase is Incorrect alert context, the Root Causes and Recommendation cards displayed incorrect SSID information. The cards displayed the SSID of the initial connected Access Point, rather than the SSID of the attempted connection that triggered the alert. The fix ensures that the correct SSID is displayed.

The timeline widget displayed alerts until the end of the current time and the lineage was continuous. The fix ensures that the timeline widget displays the alerts until the correct time and the lineage is not continuous.

In the Applications Visibility dashboard, a mismatch was noticed between the displayed number of applications in the list view and in the Applications planet view. The fix ensures that the number of active applications in the list match the number of applications displayed in the Applications planet.

A client count mismatch was observed between the client's context of a site and the Clients table. The fix ensures that the number of clients displayed in the clients context of a site and Clients table match.

In the Timestamp section for Alerts page, when updating the relative Timestamp and alert data a mismatch in Timestamp was observed. The fix ensures that the correct timestamp is observed.

In the Clients page, the reason for client failure appeared as Internal Error instead of MIC_FAILURE. The fix ensures that the correct failure message is displayed for MIC_FAILURE.

List of impacted clients for AP Association Threshold Exceeded alert was missing in the alert context. The fix ensures that the list of clients is displayed.

The Security context in the HPE Aruba Networking Central UI was clickable but did not navigate to the security page. The fix ensures that the Security context in the HPE Aruba Networking Central UI is disabled.

The Client page was deleting clients when they were missing from the alert context. This occurred when multiple instances of Wireless Client Deny Listed and DHCP alerts got deleted after few hours of being displayed. The fix ensures that no clients with alerts are deleted after few hours.

On the Topology page, under Layers > Network > VLAN, when you select a VLAN, the associated devices were not displayed. This fix ensures that the VLAN associated devices are displayed.

The client count in the table header in the Clients list view is displayed as 0, even when there are clients present. This fix ensures that the client count remains consistent across all instances based on the number of clients available.

The app category and web category rules were not applied to the access point. This issue was seen when NB API and graph API were executed. The fix ensures that the rules are applied to the AP.