Resolved Issues

Users were able to create library objects like policy, role, netservice, or time-range with an empty name value through APIs. The fix ensures that the library objects are not created with empty name values.

The Events card's expanded view and search feature took over 500 milliseconds to load a high volume of event data. This issue occurred when the number of events exceeded half a million, which was typically observed for a time range of one month. The fix ensures the Events card search feature works as expected.

The Unified Device List (UDL) in HPE Aruba Networking Central did not display the configuration status of gateways under the Configuration Status column. The fix ensures that the configuration status, Synchronized or Unsynchronized, for gateways is displayed.

In HPE Aruba Networking Central, the switch stack details were not displayed in the Reports page when users selected the Include Devices check box under Additional Preferences. Similarly, the switch stack details were not excluded when users selected the Exclude Devices option. The fix ensures that the switch stack details are displayed correctly based on the selected preference.

The HPE Aruba Networking Central APIs incorrectly allowed the DHCP clients to connect to multiple VLAN interfaces. The fix restricts the DHCP clients to connect to only one VLAN interface (VLAN1).

There was a mismatch in the value for client count on the expanded view of the Sites card and UCL for a site. The fix ensures that the client count is the same in the expanded view of the Sites card and the UCL for a site.

Downloading a report in the PDF format from the Reports page in HPE Aruba Networking Central results in the truncation of the last row in the report. This issue occurs in reports with data that covers multiple pages in the PDF file. The fix ensures that the data in the downloaded report is displayed correctly, irrespective of the quantity of data in the report.

In HPE Aruba Networking Central, users were unable to delete a VLAN profile that was created through a site or device level. The issue occurred when devices were removed and reassigned to the cluster or another tenant account in HPE GreenLake cluster. In such scenarios, devices were still assigned to the site or group in Classic Central but were removed from the inventory in HPE Aruba Networking Central. The fix ensures that the VLAN profile deletion works as expected.

The configuration push failed when users tried to configure http-server access-mode at all scopes. This issue occurred due to a default profile created in the UI during onboarding. The fix ensures that the configuration push works as expected.

The Roaming Recommender data was not visible in the Insights card on the Site dashboard, but was visible in the Network Overview page. The resolution ensures that Roaming Recommender is now correctly displayed in the Insights card.

While editing HPE Aruba Networking CentralProfiles under Library, authentication failed, if user entered plain text key length greater than 8 bytes in the Plain Text field on the Edit Profile sliding bar.

API request call for a gateway returned the error message 404 Route Not Found when special characters were included in Path Variables. The fix ensures that API request call for a gateway is successful when special characters are included in Path Variables.

In the Network Overview configuration page in HPE Aruba Networking Central, a default User Administration profile is automatically created at the library level, assigned to the global scope, and has the device function set to Access Point. This prevents users from manually creating a User Administration profile at the global level. The fix ensures that the default profile can be deleted and a User Administration profile can be created at the global level.

Although a device was moved to another site, the Device Inventory page still displayed the site name to which the device was initially associated. The fix ensures that Device Inventory shows the device mapped to the correct site.

LAG association was observed in the API GET operation and the Switch Interface Configuration card. It was displayed wrongly though LAG configuration was removed on the Ethernet interface. The fix ensures that the API GET operation and the Switch Interface Configuration card displays accurate information.

The faceplate displayed an incorrect port number for Juniper devices. In Juniper switches, port numbering starts at 0, but in HPE Aruba Networking Central, the faceplate displayed port numbers starting at 1. The fix ensures that HPE Aruba Networking Central displays correct faceplate port numbers as printed on the Juniper switch.

The DHCP client configuration failed when IPv6 was enabled for a non-default VLAN. This issue occurred because IP DHCP was not implemented for IPv6. The fix ensures that the DHCP client configuration works as expected even on a non-default VLAN.

Users were unable to delete the default VLAN 1 profile (Configuration > Profiles > VLANs & Networks > VLAN) at site level when no updates were made to the profile. The delete operation resulted in Delete for unexpected req_xpath=”/aruba-interface-vlan:vlan-interfaces/interface[id=’1’] error. This issue only affects L2 VLAN and not L3 VLAN. The fix ensures that the profile can be deleted seamlessly.

The two-step clock configuration using Postman wrongly indicated as successful. However, the device failed to configure the two-step clock mode. This discrepancy occurred because the Titleist platform supports only single-step and does not allow two-step clock configuration. The fix ensures that the message is displayed as invalid for the two-step clock configuration.

Users could not enable APM configuration in the API payload. This issue was observed both at the global and site levels. The fix ensures that the APM configuration can be successfully enabled.