Resolved Issues

HPE Aruba Networking Central did not display all the newly created floors and the updated status of the assigned devices in the site context after a successful site import operation using the import wizard. The fix ensures that all floor and device information is displayed within a few seconds.

On the device Connectivity card, HPE Aruba Networking Central unmanaged devices connected to AOS-CX switches were not displayed in the connection path, even though they appeared in the topology view. The fix ensures that these devices are now consistently shown in both the Connectivity card and the topology view.

If a device was included in a site health trend record and later moved to a different site, its hyperlink in the AP list remained disabled for that record. Additionally, health metric data was available only from the time of system upgrade, with no visibility into prior data, and the last_seen field updated only for APs that went offline after deployment. The fix ensures correct hyperlink behavior regardless of site movement, improved handling of historical health data visibility, and consistent population of the last_seen field for all APs.

In the Access Point Firmware Recommendation page under Sites > Insights > AI-Powered Network Optimization, the recommended firmware release dates shown in the tool tip for the Popularity of Recommended Firmware card did not match the actual dates listed in the release notes. The fix ensures that the correct firmware release dates are displayed in the tool tip.

In HPE Aruba Networking Central, on navigating to Menu > Central NAC > Configuration icon > Visitors > Edit Visitor Account, the Save option was incorrectly displayed when attempting to reset the password for a visitor account without contact information. This fix ensures that the Save option is hidden when contact information is not configured, preventing the password reset operation from being performed.

While configuring a Google social account by navigating to Menu > Central NAC > Configuration icon > Identity Management > Create Identity Store and selecting Provider as Google Social, a value was required for the Hosted Domain field. This fix ensures that the Hosted Domain field is optional, allowing the Google social account to be configured without specifying a hosted domain.

When creating or updating a policy with multiple rules in the cloud authentication policy management system, switching between rules without closing the previously opened one caused the Attributes section to display incorrect data. This issue occurred due to improper state management in the revamped Attributes module, which led to stale data being retained and shown. The fix ensures that the Attributes section refreshes correctly whenever a user switches between rules, resulting in an accurate display of rule-specific attributes.

In Topology view, if a gateway failed to establish a relation due to invalid or unsupported LLDP capabilities, the unmanaged device was not displayed. The fix ensures that the system capabilities are enabled, valid, and sent correctly to establish the relationship.

In HPE Aruba Networking Central, users were unable to view any information under ORCA after expanding the Troubleshooting card of DNS alerts. This issue was observed for DHCP and DNS alerts. The fix ensures that the Troubleshooting card displays the required information as expected.

Authentication failed because gateways resolved the captive portal to the default server group, which had no RADIUS servers configured. As a result, no authentication request was sent to ClearPass. The fix ensures recreating or correcting the pre-auth role so that it does not have an incorrectly assigned captive portal profile.

Incomplete metrics were displayed on the Application > Teams Audio > Health Metrics page. Only one Teams audio/video call was displayed instead of showing all the calls. The fix ensures that all Teams calls are consistently listed by aligning the display with the expected data availability and timing of updates.

When an interface from site level had an Interface Profile applied that included a port-profile, and a manual override to default at the switch level was performed, the interface did not re-inherit the expected port-profile from the Interface Profile. Instead, the interface remained in a default or unconfigured state until the Interface Profile was manually modified again. The fix ensures that the interface re-inherits configuration from the Interface Profile.

When LLDP Authentication (LLDP Auth) and CDP Authentication (CDP Auth) were applied to a Link Aggregation Group (LAG) and later removed, the default configurations were not correctly reinstated. After detaching the interfaces from the LAG, certain interfaces were left without the required AAA objects and authentication settings, leading to incomplete or inconsistent configurations. This behavior occurred because the modifier failed to properly restore default interface settings—such as LLDP and CDP authentication—upon LAG disassociation. The fix ensures that all default configurations are correctly reapplied once the LAG is removed.