Resolved Issues

When the user mapped the same VLAN address to a different instance of MSTP, the switch configuration was updated with the same VLAN address for that MSTP instance without any error or warning message. The fix ensures that a error message is displayed when the user mapped the same VLAN address to a different instance of MSTP.

A LAG was able to be configured beyond the permitted limit (1-256). This unsupported LAG configuration caused the device to move to a conflict state. The fix ensures that such an unsupported configuration is not pushed onto the device and an Audit Log is created with the a message that the Configuration is blocked due to exceeding the permitted limit.

The prefix-len parameter led to inconsistencies in behavior across different interfaces as it was not mandatory. This issue occurred because of the previous decisions allowed the prefix-len parameter to remain optional. The fix ensures that the parameter is made mandatory for the configurations.

In HPE Aruba Networking Central, filters failed to apply dynamically when viewing alert details from the site health card. This issue occurred when different severities were dynamically generated for alerts and client health. The fix ensures that the filters apply dynamically.

On executing the [PATCH or DELETE] /network-config/v1alpha1/roles API call under Configuration > Roles & Policy, the API failed to update or delete the bandwidth contract (bw-contract) settings. The fix ensures that API call works as expected.

On the HPE Aruba Networking Central Device Details page, the temperature of Juniper switch was received in Fahrenheit and displayed in Celsius. The fix ensures that the temperature is received in Celsius.

Under the Devices > Profiles Management > Interfaces page, the Enable PoE option was disabled on the Switch Interface Configuration profile card although the option was enabled in Classic Central. Additionally, the Priority and PoE Allocation By details were missing from this page. The fix ensures that the Switch Interface Configuration card displays the PoE information correctly.

A  Configuration files got corrupted error was displayed for some devices while using NBAPI. The fix ensures that valid configuration files are generated in the NBAPI.

While configuring a static route under Profiles> Routing & Overlays cards, the system incorrectly accepted invalid subnet prefixes without throwing an error. The issue occurred because the validation mechanism failed to validate the prefixes, which lead to the acceptance of invalid configurations. The fix ensures that invalid prefixes are correctly identified and rejected, preventing the acceptance of erroneous configurations.

Unintended changes occurred to the arrangement of rules on the Network Policies page. This issue occurred when a duplicate rule was added to Network Policies under Roles & Policies > Security Policies. The position of the existing rule was removed and updated with a new position. The fix ensures that adding a duplicate rule does not change the existing rule's position preserving the intended arrangement.

In the Interface Management profile, updating the IP address and default gateway simultaneously caused the device to enter a configuration failure state upon repeated updates. This issue stemmed from improper handling of configuration sequencing.

The fix ensures the proper execution order of CLI commands during IP address and default gateway updates.

Users were unable to override the static route profile, under Library > Devices > Profiles, by adding a new alias IPv6 default address without deleting the existing alias. This issue occurred because the parent tree dependencies were not loaded correctly. The fix allows users to override the static route profile without deleting the existing alias.

An extra label for the SSID name was displayed incorrectly in the Top WLANs throughput Trend section of the Network Usage report. This issue occurred because the WebUI incorrectly rendered additional legend labels. It was resolved by implementing a linked label fix. The fix ensures accurate label rendering in report legends.

When a new NTP profile was created using a shared alias to override a global profile, the UI initially displayed both the global profile and the override profile simultaneously.

The fix ensures that the UI displays the override profile accurately.

The copilot query occasionally was stuck at the thinking stage, resulting in an unintended task failure. This issue occurred because of error codes triggered by various factors, including devices being offline, GraphQL throttling, closed Bedrock stream, null responses, and Redis timeouts. The fix ensures that queries are completed successfully without getting stuck at the thinking stage.

Duplicate alerts for queue drops and Tx drops caused alert fatigue. Frequent and unnecessary notifications for Tx drops overshadowed critical queue drop alerts. The implemented fix disabled Tx drop alerts and updated the queue drop alert conditions. These conditions now trigger alerts only when port utilization exceeds 5% and drops surpass 5%.

Users observed that a PATCH API call used to update IP addresses for the interface management profile succeeded even when the management port was shut down. As a result, the configuration change appeared successful despite the port being inactive. The issue is fixed in this release.

In HPE Aruba Networking Central, in the Configuration Overview > Profiles > Interfaces > Management Interface > Edit Profile side of a selected Management Interface profile, users were unable to uncheck the Enable Port option if IP addresses were visible or added. The fix ensures that users are able to check and check the required option.

In Library > Aliases, updates to the static route profile failed when a new IPv6 default gateway alias was added without removing the previously configured alias. This issue occurred because the system included both the old configured alias and the updated alias in the static route profile. The fix ensures that static route profile updates successfully.

Under Profiles > Edit Profile, the system now correctly handles scenarios in which a user unchecks Enable Port and adds IP addresses. Instead of causing a configuration failure, the fix ensures that an error message is displayed, guiding the user to resolve the issue. Note that the error displayed states Cannot configure ipv6-static when management interface mgmt is disabled. Please enable the interface first.

In the Network Overview > Sites > Topology > Link Node Diagram, the ISL LAG link between devices did not display the aggregated speed or the individual ports that are part of the LAG. The fix ensures complete visibility of the LAG information.

In the topology Link Node view, search strings with spaces before or after the string did not return a matching result. The fix ensures that the correct results are returned even with spaces before and after the search string.

When a VSX profile was deleted from the site configuration, the configuration of Keepalive (KA) and Inter-Switch Link (ISL) interfaces failed to revert to their default state on the associated switches. The fix ensures that the KA and ISL interfaces automatically revert to their default configuration.

Under Alerts > Switch CPU Utilization/ Switch Memory Utilization alert > Actions card, Failed to retrieve error message was displayed for the top five CPU/ memory consuming processes on the switch. The issue occurred in AOS-CX 4100/6000/6100 switches. The fix ensures that this error message is not displayed in the Actions card.

When multiple VNI profiles were mapped to a VXLAN tunnel profile with distinct VTEP-peer IPs, and one profile's VTEP-peer was updated to match another, the system failed to consolidate the VTEP-peer mapping as expected. Instead, during the sequential unmapping of all VNI profiles, duplicate no vtep-peer <ip> commands were pushed. This redundancy caused the device to enter a conflict state and display an error message when the last profile was unmapped. Note that static VXLAN tunnels must have unique source and destination IP combinations.

When devices configured with VSX profiles were removed from the Site where the profile was configured, the VSX configuration became corrupted, preventing the configuration push from reaching the VSX intent service. Additionally, re-adding the devices to the Site and attempting to push the same VSX profile via API failed. This issue occurred because the VSX profile was not properly deleted from the site-level configuration before the same profile was pushed again. The fix ensures that the VSX profiles are deleted properly from the site-level configuration, enabling successful configuration pushes and re-additions.

A Client Type Mismatch occurred in the Unified Client List (UCL) and the DHCP Lease Card. The fix ensures that the mismatch does not occur.

The AP Connected 10/100 Mbps alert did not generated in HPE Aruba Networking Central. The fix ensures that the alert is generated correctly.