Resolved Issues
The following are the resolved issues in this release:
|
Issue ID |
Description |
|---|---|
|
CNX-31416 CNX-53012 |
The Health card for either a standalone or stack switch did not display any value for the Last Restart Reason field. The fix ensures that the Last Restart Reason field displays information as expected. |
|
CNX-34964 |
The Ports field in the Named Objects > Services > Manage services page did not turn red when a user typed a value more than 65535. Red indicates that the typed value has exceeded the defined range. This issue occurred when a user tried to create a service. The fix ensures that the Ports field turns red when the typed value exceeds the defined range. |
|
CNX-46689 CNX-48834 CNX-58000 |
There was a mismatch in the value displayed for the client count in expanded Sites card, clients context at a site, and the Clients table. This issue occured either because of stale entries or data consumed from the client state of UC reconciliation instead of device. The fix ensures that client count is consistent in all the pages. |
|
CNX-48846 |
Services accepted both port range and protocol, instead of displaying an error. This issue occurred when creating a service. The fix ensures services do not accept port range and protocol together. |
|
CNX-49285 |
A drop was observed in the client count graph in the Usage card at the site level for a client. This issue occurred when the AP statistics were received late in the five-minute time frame. The fix ensures that the AP client count remains stable. |
|
CNX-49546 |
In HPE Aruba Networking Central, if the role-based policy name contained special characters, then adding a rule to the policy failed. The fix ensures that the use of special characters in a policy name is restricted and the rule is successfully added to the policy. |
|
CNX-53196 |
In both HTML and CSV formats of the inventory report, the value in the Status column was displayed in capital letters. The fix ensures that only the first letter of the value in the Status column is capitalized. |
|
CNX-54593 |
The Root Causes card on the Alert Dashboard page did not display the updated information when the configuration was changed. The fix ensures that the Root Causes card displays the updated information. |
|
CNX-61462 |
The Filters dialog box in the Alerts page displayed the Last Occurred information incorrectly. The fix ensures that the Filters dialog box displays the correct Last Occurred information. |
|
CNX-62241 |
The DHCP Alerts and corresponding AI-OPS recommendations were not updated in HPE Aruba Networking Central > Sites > Alerts Page. The issue occurred when a mismatch occurred in the timeline for APs. The fix ensures that DHCP Service is triggered if timeline changes are observed for the APs. |
|
CNX-64676 |
In the list of VRFs listed under object_type=Library, the default VRF profile name is missing from the VRF profile list. The fix ensures that a VRF name default can be added for the object_type=Library by other profiles such as DNS or SNMP. |
|
CNX-66801 |
The Create RF Profile option under Profile Management > RF Profile in the HPE Aruba Networking Central configuration view did not display the selected Allowed Channels after a successful Save operation intermittently. The fix ensures that the values in the Allowed Channels are displayed, as expected. |
|
CNX-70755 |
The Create Profile option under Profile Management > RF Profile in the HPE Aruba Networking Central configuration view did not allow users to select the Allowed Channels for the 5 GHz and 6 GHz radio frequencies. This issue occurred when the Use Non-DFS only check box was cleared and the channel selection was updated repeatedly. The fix ensures that the Allowed Channels for all the radio frequencies can be selected as expected. |
|
CNX-70757 |
In the RF Profile > Allowed Channels page, users were unable to update the channel list as the Allow button was not available in the Channels and Bandwidth section. The fix ensures that the Allow button is displayed and the channel lists are editable. |
|
CNX-71790 |
Users were not able to create profiles under the System Local Administration tab in the HPE Aruba Networking Central UI. The fix ensures that users are able to create profiles under the System Local Administration tab in the HPE Aruba Networking Central UI. |
|
CNX-73124 |
In the Configuration > Profiles > WLAN page, a user was required to assign the ESSID profile scope via NBAPI. The fix ensures that the user is able to assign scope for the WLAN profile as expected. |
|
CNX-73805 |
After editing a report, the time in the Last Updated By column of the Reports table remained unchanged. The fix ensures that the time in the Last Updated By column gets updated on editing a report. |
|
CNX-74281 |
In the Gateway Interfaces Summary report, when the interface was down, the interface speed and duplex mode Incorrectly displayed Auto Auto instead of -. The fix ensures that the interface speed and duplex mode information is accurately displayed. |
|
CNX-74528 |
When creating or removing a device profile through the API, if the payload is sent without attributes, an invalid configuration is pushed to HPE Aruba Networking Central. This impacts the AOS-CX switch onboarding to HPE Aruba Networking Central. To avoid this, you must provide at least one of the following attributes when creating or removing a device profile:
Additionally, an action is mandatory for entries. It must be set to either match or ignore. |
|
CNX-77289 |
Users were unable to create a local object by editing the server IP of a shared object for NTP and dynamic DNS over HTTP. The fix ensures that users are able to create a local object. |
|
CNX-78972 |
Users were unable to change the accounting mode from START_STOP to STOP_ONLY through API. This issue was observed when users had configured interim updates for the START_STOP accounting mode. Hence, it is recommended to remove the interim updates before changing the accounting mode to STOP_ONLY. |