Resolved Issues

In the Alerts page, Switch Disconnected alerts were not automatically cleared. This issue occurred when a switch was converted from stack to standalone or from standalone to stack. The fix ensures that the Switch Disconnected alerts are now automatically cleared after switch conversion.

The sorting functionality was not working for the columns displayed on the expanded LAN Tunnels card for an AP. The fix ensures the sorting functionality works as expected.

In the New HPE Aruba Networking Central On-Premises WebUI, the PSM status for switches was incorrectly displayed as Active even after the links for these switches were disabled. The issue occurred because the PSM sync status for the connected switches did not get dynamically updated. The fix ensures that the PSM status for switches is displayed correctly.

Certain listed IP-related actions were not available. This issue occurred in the configuration pages where IP settings were viewed and managed and led to unsupported options being displayed. The fix ensures that only the supported options are displayed and instructions provided to use appropriate settings.

RADIUS timeouts and retries were not configurable on the UI. The fix ensures that RADIUS timeouts and retries are configurable using Authorization Server Profiles.

While editing a route map policy, the system displayed an error stating: failed to parse data tree: Node 'seq-no-op-type' not found as a child of 'route-map' node. This issue occurred when the object name matched the module name, preventing the profile update and blocking configuration from being pushed to the device. The fix ensures that object and module name conflicts are properly handled.

When users unmapped an EVPN profile from a Global scope and mapped it to a Site scope, the VLAN associated with the EVPN profile was not properly remapped to the new scope. This issue occurred because the UI submitted a single batch containing both POST and DELETE for the same EVPN resource and the GCM computation produced delete operations for VLAN entries. The fix ensures that the VLAN associated with the EVPN profile is properly remapped to the new scope.

Tooltips on the Health Metrics page displayed misaligned positions and identical timestamps across different charts. This issue occurred especially when hovering over health trend or horizontal stack bar components. The inconsistency occurred because latency or default component behavior renders previously hovered values to persist, particularly when the time range increases. The fix ensures that tooltips on the Health Metrics page displays data accurately.

Monitoring, Alerts, and Troubleshooting views failed to report gateway device fans as Down when their RPM was zero, except on 90xx series devices. The fix ensures consistent detection and alerting of fan failures.

In the Device Groups page, the search functionality was not working when a user tried to create or update a device group or add devices to an existing device group within a specific device group context. The fix ensures that the search functionality works as expected.

When users modified settings on a network port that was part of a LAG (port-channel), the system correctly blocked the change and showed an error internally. However, the WebUI did not display this error or any message. This issue occurred because the web interface was not configured properly to display errors. The fix ensures that the blocked changes and the corresponding error messages are correctly displayed in the WebUI.

During device registration, a LAG created with default values was not updated in the UI. The fix ensures that default configurations for an existing LAG is automatically updated in the UI.

Under Agentic Mesh Actions, the count of impacted clients was incorrectly displayed in cases of high roaming failure. The fix ensures that the count of impacted clients is correctly displayed.

When few alerts were selected in the Alerts card, the sites consisting of those alerts were not getting displayed. The fix ensures that associated sites are displayed when alerts are selected in the Alerts dashboard.

The VLAN modification made by automation did not override, though the settings were successfully applied. This was observed on the VLAN Details page at the device context. The VLAN had wrongly inherited details from the site and could not be edited or removed. The fix ensures that appropriate instructions are provided that matching VLAN details must be updated together at the device level, allowing the interface to correctly reflect overridden values and avoid errors.

Aruba 6000 device onboarding failed and went out of sync due to a client capacity violation with an AAA profile configured at the site level. Also, the name of specific AAA profile where the error occurred is not displayed. The fix ensures that Aruba 600 devices onboard successfully.

In the Library > Interfaces > Port Profile, the WebUI did not display any error when a user with read only permission attempted to create a new VLAN profile directly. This issue occurred when the read-only permission was assigned from a primary user account to a secondary user account. The fix ensures that the WebUI now displays an error message when the user with read only permission attempts to create a new VLAN profile.

When configuring a webhook with an invalid client ID and secret key, the system displayed a misleading error message: Invalid wellknown URL. The fix ensures that the correct error message is displayed: Invalid client-id or credentials.

In HPE Aruba Networking Central WebUI, there was a delay in opening of the Port profile for wired AP overlay. The fix ensures that the Port profile for wired AP overlay opens instantaneously.

Users with read-only permissions were able to initiate the creation of a new port profile directly from the Gateway Interface under Device scope without encountering any error or validation message. Despite insufficient access rights, the system did not restrict the action or notify the user, leading to unintended behavior and lack of proper permission enforcement. The fix ensures that users with read-only permissions are restricted from initiating port profile creation, and appropriate validation messages are displayed to enforce access control.

The system showed an incorrect error when referencing VLAN 20 in access_switchport_alias across scopes. The fix provides a clear message indicating that VLAN 20 is not available in the current scope and suggests mapping it to the correct scope.

Users were not allowed to enter IPv6 address starting with double colon (::). This issue occurred due to input restrictions.

The fix ensures that IPv6 addresses prefixed with double colons are accepted.

When a permission was assigned at the site collection level using a scope group, the system did not honor the RBAC hierarchy. As a result, access was not propagated to all underlying sites within the site collection, causing inconsistent permission behavior. The fix ensures that the permission assigned to the site collection is correctly propagated to all underlying sites.

On the Devices page, the information displayed in the List view and the Summary view were inconsistent during new device onboarding and device recovery performed via the CLI. The issue occurred due to discrepancies in synchronization between the view components. The fix ensures that the List and Summary views display correct information.

In HPE Aruba Networking Central, resynchronization failed when a device was powered on after being associated with a site and assigned a persona. The fix ensures that synchronization is successful regardless of whether the device is powered on before or after assigning a site or persona.

When a Port profile was created under Interfaces card, the WebUI displayed the Assign Pre-authentication role option even when the selected port mode did not support pre-authentication. The fix ensures that the WebUI displays Assign Pre-authentication Role for appropriate port modes only.

The licensing API intentionally returned separate entries for the same license tier to allow individual tracking and action at the subscription-key level.

After GDPR Opt-Out, the client did not reappear in the Unified Client list, even though it was connected. The fix ensures that after GDPR Opt-Out, a client is displayed in the UC list only when a real client state change is received, enforcing the intended event-driven and GDPR-compliant behavior.

The Common Config UI > Net Destination configuration screen incorrectly flagged valid IPv6 ranges as invalid due to faulty validation logic. The fix ensures IPv6 ranges are accepted and only truly invalid entries triggered errors.

Port-profile configuration push was failing on the device due to malformed composite keys in the aruba-ip-binding static-entry records stored in the Config DB. The ip-version-vlan-client-address field was incorrectly formatted with wrong separators and improper IP encoding. The issue was fixed by correcting the composite key formatting and ensuring proper IP address encoding in the Config DB records, allowing the configuration push to complete successfully.