Resolved Issues
The following are the resolved issues in this release:
|
Issue ID |
Description |
|---|---|
|
CNX-29156 |
The Health card of a switch incorrectly reported a power supply hardware issue. The fix ensures that the Health card does not display any incorrect issues. |
|
CNX-41024 |
A client was displayed as Client is not connected in the Connectivity Performance card and its connectivity was displayed in green in the Connectivity card. This issue occurred when a client was placed in special roles. The fix ensures that accurate client information is displayed in the Connectivity Performance card. |
|
CNX-50193 |
Pushing the APIs like eth/src-nat/dst-nat to some APs failed. The fix ensures that the APIs are pushed successfully to an AP. |
|
CNX-83215 |
HPE Aruba Networking Central did not support Configuration Status for gateways on the Devices page. The fix ensures that Configuration Status is displayed for gateways on the Devices page. |
|
CNX-91806 |
The report runs model window and detail view (HTML/PDF) displayed only the report period. The fix ensures that report runs model window and detail view (HTML/PDF) displays the expected report period and time slicing information. |
|
CNX-117539 |
Users were unable to update the Passphrase parameter for a WLAN SSID profile under the Update Profile side panel in HPE Aruba Networking Central. This issue occurred even when no other WLAN SSID profile parameters were modified. The fix ensures that users are able to update the Passphrase parameter as expected. |
|
CNX-114432 |
A few devices with VSF stack received incorrect interface configuration on vsf links, causing cyclic updates downstream. The Audit Trail page in Classic Central logged this issue with a repeated sequence of Pushing full config to the device (Config Status - Pending) and Config push successful message (Config Status – Sync). The fix ensures that the VSF stack configuration works as expected with no cyclic push towards the device. |
|
CNX-115799 |
There was a mismatch in the data and its order displayed for 7 days and 24 hours filters for the Roaming Recommender insight on the AI-Powered Network Optimization page. The fix ensures that data is consistent for both temporal filters. |
|
CNX-117941 |
Users were unable to update the Directory parameter for a dump-server profile in HPE Aruba Networking Central. The fix ensures that users are able to update the dump-server profile as expected. |
|
CNX-111947 |
Users were unable to modify the Distance in IPv6 routes that have Nexthop interfaces as VLAN or LAG. The issue occurred because the route update was not allowed with new distance. The fix ensures that the following work as expected:
|
|
CNX-118974 |
APs failed to receive HPE Aruba Networking Central configuration when a WLAN profile was created with Authentication Server Group profile. The Audit Trail page in the Classic Central logged this failure as internal server error. Could not process configuration task. The fix ensures that APs receive HPE Aruba Networking Central configuration as expected. |
|
CNX-45699 |
A change in Cluster Category from VLAN & STAMAC combination to site combination impacted the DHCP lineage functionality. The fix ensures that the DHCP lineage functionality works as expected. |
|
CNX-101629 |
In the Alerts dashboard, when the root cause could not be determined, the Action card displayed the default message, Currently, additional troubleshooting information is not available. The fix ensures that the root cause is displayed correctly. |
|
CNX-94895 |
During static route profile configuration, an invalid loopback address entered as the destination field caused the device into a conflict state. The fix ensures that a valid error message is displayed when a loopback address is entered in the static route destination. |
|
CNX-100793 |
User was unable to configure an auth server group profile with Fallback to Local Authentication in an AP, for System Local Administration profile. The fix ensures that now the users can configure an auth server group profile. |
|
CNX-116759 |
Users experienced VSF configuration push failure in some Aruba 6200 switches running AOS-CX 10.13 or later versions. This issue occurred when PoE configuration was pushed to the VSF link while configuring the VSF payload. The fix ensures that VSF is configured as expected. |