Resolved Issues

The Connectivity Performance card for a switch did not show a timestamp on the X-axis of the uplink chart. The fix is updated to reflect the fact that the timestamp need not be shown on the uplink chart.

In the expanded Connectivity Performance card of a gateway, the Frames graph took more than expected time to load. The fix ensures that the graphs load on time.

In HPE Aruba Networking Central, the topology sunburst did not reflect the change of an unmanaged device name under Network Overview > Sites Card. This fix ensures that the system automatically updates the topology sunburst with the modified name of the unmanaged device.

AAA profiles created through the WLAN workflow were being deleted independently from the gateway, which caused system issues and inconsistencies. This issue occurred because the deletion mechanism lacked proper validation to distinguish between AAA profiles created by the system and those created by users. The fix ensures that the system prevents independent AAA profile deletions.

In the Events table, the search function returned incorrect results by including entries that did not match the keywords entered in the search text field. The fix ensures that search results display only entries that match the keywords.

In the HPE Aruba Networking Central, when non-alias configurations such as location and contact information were updated along with the hostname in the system-info. The system only reflected the updated hostname on the device, not the other configurations, like location and contact information. The issue occurred because the Global Config Manager (GCM) infrastructure did not process simultaneous updates to alias and non-alias fields within the same transaction. The fix ensures that the system displays configuration information correctly.

The health status of the standby port was incorrectly displayed as Poor. The PoE Denied and Inconsistent Ports Detected alerts were generated for the standby port. After clearing the PoE Denied alert for the standby port, the health status did not change to Fair. This issue occurred because the alert consumed data from the wrong topic in the message queue. The fix ensures that the health status of the standby port is displayed correctly.

A LAG beyond the upper permitted limit (unsupported) was able to be configured and this unsupported LAG configuration moved the device to a conflict state. This issue has been fixed in this version.

Role-based policy with Access Control Entry (ACE) entry that used 6 or 17 as the protocol number was not pushed to the device. This issue occurred because the role-based policy in HPE Aruba Networking Central accepts protocol numbers that are reserved, and conversion is not accepted due to device limitations. This issue was resolved by manually deleting, unassigning, or reassigning the device in Classic Central.

VSF member deletion failed due to a CLI configuration conflict. This issue occured when the CX-side PoE attempted to execute the CLI, but the database was found as empty, resulting the operation to fail. As a result, HPE Aruba Networking Central also failed and displayed the conflict. The fix ensures that the database is properly initialized before executing the CLI command, allowing the VSF member deletion to proceed as expected.

The device commands show logging server and show running-config | include logging returned empty results due to the configuration of syslog servers using source interfaces that are Layer 3 VLANs without assigned IP addresses. The fix ensures that VLANs without valid IP addresses are properly validated. This includes raising errors during syslog server creation or handling them differently for default VLAN configurations.

The UXI chart in HPE Aruba Networking Central is configured to provide data updates every 2 minutes. However, UXI sent probes every 3 minutes for certain applications. This mismatch caused noticeable gaps in the UXI HPE Aruba Networking Central chart, especially when there was only one UXI sensor present at a site. As a result, it was not possible to see a continuous line graph for UXI data with a single sensor. The fix ensures a continuous and accurate line graph for UXI data, even when only one sensor is present at the site.

When clients transitioned from Connected to Blocked state, the Clients table did not retain the values for Key Management, Authentication, and Capability columns. These values were displayed as Unspecified in the unified client list. This issue occurred because the blocked state prevented transmission of telemetry data from the AP to HPE Aruba Networking Central.

The fix ensures that, even in a blocked state, the client's previous state is retained for accurate monitoring.

While generating a pre-defined or custom report from the Reports page, PDF generation failed for users having large scale account. The fix ensures that PDF is generated successfully.

Despite the presence of loops in a few switches, the system did not regularly generate the Loop Detected alert on the Alerts page. The fix ensures that the system routinely generates the Loop Detected alert.

For all devices except gateways and PVOS switches, hostname is optional. If the hostname is removed, the hostname field will display a dash (-) in the System Information table.

The copilot output for HPE Aruba Networking Central occasionally did not display in the correct format. The fix ensures that copilot displays the correct output.

Duplicate entries of IPv4/IPv6 nexthop addresses were not blocked. Deleting the route device caused a configuration failure state. The fix ensures that there is no configuration failure.

In HPE Aruba Networking Central, CX update alerts were not accurately reflecting changes based on the latest production data, leading to delays and inconsistencies in user notifications. The fix ensures that CX update alerts consistently reflect real-time production data, ensuring timely and accurate notifications to users.

In HPE Aruba Networking Central, in the site context > Security > expanded Sessions card, the search field only supported device and application based keywords.