Resolved Issues

Traffic flow from the default role to the destination role was not allowed, preventing Group-Based Policy clients from functioning as Application-Based Policy clients. This issue occurred because the required default configurations were not being pushed to devices during rule creation. The fix ensures proper traffic flow for default roles.

The RadSec client certificate and 802.1X supplicant client certificate fields were missing from the Certificate Usage profile in HPE Aruba Networking Central. The fix ensures that these fields are added in the Certificate Usage profile.

Users were unable to create a Certificate Usage profile for an AP if Radsec Use EST Sever was selected. This issue occurred as EST profile must be configured with EST activate before using the EST certificate as the RadSec client certificate and CA certificate for an AP. The fix ensures that users can create a profile even if Radsec Use EST Sever is selected.

In the VSF Profiles page, the same stack device was displayed under two different stack names in the same site.

When a switch was removed from a VSF stack profile and disconnected from the site in Classic Central, its details were not removed from the site and VSF stack. Upon being reconnected to the site and assigned to a new VSF stack profile, the same stack device was displayed under both the new and old VSF stack profiles on the VSF Profiles page.

The fix ensures that the same stack device displays stack names correctly.

The Movement of devices from one site to another site failed in HPE Aruba Networking Central. This issue occurred because the state publisher failed to process and publish updated site information for the devices, despite receiving notifications. The fix ensures that the processor correctly handles device grouping information updates and publishes device system states with updated site IDs and site names.

In the Devices table, the Configuration Status for switches entered a Conflict state when an AAA profile was updated with authorization roles and configured through port-profile-authentication. This issue occurred because the Power over Ethernet (PoE) configuration was applied to a non-PoE interface. The fix ensures that PoE configurations are no longer applied to non-PoE interfaces, preventing the Conflict state.

In HPE Aruba Networking Central, configuring Roles and Policies within the Library scope failed for Access Switch (AOS-S switches), when the policy name exceeded the maximum allowed limit. As a fix, upgrading the AOS-S firmware to version 16.11.0026 increases the maximum character limits for policy names to the following:

• QoS Policy: 54 characters

• ACL Policy: 50 characters

• Role-Based Policy: 35 characters

Multiple alerts were generated for the same LAG mismatch in stack switches. The fix ensures that only one alert is generated for LAG mismatch is stack switches.

In Network Usage reports, only 25 entries were displayed for the Max & Average WLAN Usage KPI, making it unsuitable for use cases requiring more extensive data. The issue was resolved by increasing the limit to 100 entries.

In the Network Usage reports, only 25 entries were displayed for the Top Devices by Wireless Usage KPI, instead of 100 entries. The fix ensures that the report displays 100 entries.

Users were unable to delete multiple reports and send email in the Find Reports page. The fix ensures that users can perform these operations as expected.

Users were unable to remove or delete a member from the stack configuration. This issue occurred because users deleted the members immediately after disabling the link. The delete action resulted in a conflict, and the configuration status went toConflictinstead ofSynchronized. The issue was resolved by adding a delay between disabling the link and deleting the member.

The device health of both CPU and memory changed to Fair, from Good, even when there were no alerts seen in the Alerts page. The fix ensures that the device health of both CPU and memory do not change when there are no alerts.

On the HPE Aruba Networking Central device details page, the temperature of Juniper switch was received in°F(Fahrenheit) and displayed in°C(Celsius). The fix ensures that the temperature is received in °C (Celsius).

In the device and site contexts in HPE Aruba Networking Central, the Alerts value is displayed as 0 even when there are multiple events logged in the Events card. The fix ensures that the Alerts value corresponds to the number of events.