Resolved Issues

Aliases were permitted to include both IPv4 and IPv6 addresses, which caused the translation process to misinterpret the address family and produce invalid device configurations. The fix ensures strict single-address-family alias validation.

The API did not validate invalid inputs, and returned empty results instead of errors. The fix ensures that validation is properly implemented and that appropriate error messages are provided when invalid data is entered.

While generating a network usage report from Reports > Manage > Create Report page, a mismatch is observed between the reporting and monitoring data. This issue occurs because of a shift in the timestamp of the interface throughput data points. The fix ensures that the interface throughput timestamps are aligned between monitoring and reporting modules to eliminate data mismatches.

The creation of aliases failed on the VLAN page. This issue occurred because the Active Gateway and Voice Enable options were unavailable under the Alias drop-down. The fix ensures that options are available in the VLAN page and allows direct alias creation as expected.

The MOS trend chart on the Tunnel Details page in AP was not updated to a zoned line chart format. The fix ensures that the MOS trend chart is updated to a zoned line chart format and MOS values are categorized as follows: scores of four and above are considered Good, scores between three and four are Fair, and scores below three are Poor.

When no AirGroup information was available, the system incorrectly sent an empty value instead of null. This issue occurred because the UI showed a blank cell instead of the expected hyphen [-]. The fix ensures that the missing AirGroup data is now correctly sent as null, allowing the UI to display a hyphen as intended.

After onboarding the switch to an HPE Aruba Networking Central group, the device entered a Blocked state when client-limit configurations (such as AAA and port-security) were applied through port profiles or interface profiles exceeded the supported values defined for the switch (for example, exceeding 32 on 6100/4100i or platform-specific limits). The fix ensures that the device remains in sync when client-limit configurations are exceeded.

When an alias was changed from TRUNK to ACCESS mode, the system correctly updated VLAN mode but failed to remove ACLs associated with the old trunk VLANs. The fix ensures that stale trunk-related configurations are properly cleaned up, preventing invalid and potentially risky configurations on the gateway interface.

In Configuration Overview>Profiles>Authentication Server Group, if the RADIUS server name contained spaces, the configuration would not be pushed to the CX-6000 Switch. The fix ensures users are notified that spaces are not allowed in new profile names while creating RADIUS servers.

On the Network Overview page, when expanding the Alerts card and selecting an alert, clicking the severity count for a site name navigated to the site alerts list, where no active alerts were displayed. This issue occurred due to a mismatch between the alert count displayed for the selected alert in the Alerts card and the alerts shown in the site context. The fix ensures that the number of alerts displayed in the site alerts list matches the count shown on the selected alerts page.

The extended-ssid command was no longer supported on AOS-10 access points, but existing documentation and configurations continued to referenced it. The fix ensures that all relevant documentation is updated and the extended-ssid is unsupported.

During gateway initialization using IPv6 over DHCPv6, reachability was temporarily disrupted when static addressing was applied due to configuration sequencing issues. The fix ensures that gateway reachability is preserved during setup by avoiding unintended connectivity loss when transitioning from DHCPv6 to static IPv6 addressing.

While unassigning a VLAN with an inbound ACL containing rules without source and destination fields, users observed a configuration push failure. This issue occurred because PCM processing incorrectly assumed the presence of source and destination fields in policy rules regardless, of the rule type. The fix ensures that the configuration pushes succeed when such rules are present.

During Virtual Switching Fabric (VSF) creation, the system overwrote previously pushed site, group, and global configurations by creating local profiles on the device. The issue occurred because VSF formation triggered an automatic configuration import during device re-onboarding. The fix ensures that the configurations are not overwritten.

When assigning shared-secret-config-alias to an auth-server that already has a password without alias, the first config push does not deliver the resolved password to the device. A subsequent change (e.g., updating description) triggers a second push that correctly delivers the password.

In the API Gateway landing page, the webhook UI was visible for MSP as notification support was not present. The fix ensures that the webhook UI is disabled for MSP.

The default DSCP values for audio and video applications in the Dynamic Application Prioritization user interface were intentionally updated from 56 and 46 to 48 and 40 as part of the product behavior change. Additionally, the delete or reset action for the DSCP override will not revert the values to the previous defaults, since the currently configured values are the intended system defaults.

When AirGroup (AG) was disabled at the Global level, administrators were unable to create or edit custom services and server (GSP) policies via the UI because the relevant cards were disabled. UI incorrectly tied the ability to manage custom services and server policies to the Global AirGroup enablement state, even though these should be configurable independently. The fix ensures that custom services and server (GSP) policies can be created or edited via the UI even when the AirGroup is disabled.

When AirGroup was turned on, the predefined services were also enabled by default and that lead to unnecessary usage and lack of user control. This issue occurred in the AirGroup configuration page. The fix ensures that no predefined services are enabled by default, allowing users to selectively enable only the required services.

During Virtual Switching Fabric (VSF) creation, the system overwrote previously pushed site, group, and global configurations by creating local profiles on the device. The issue occurred because VSF formation triggered an automatic configuration import during device re-onboarding. The fix ensures that the configurations are not overwritten.

Redis cache was explicitly invalidated after DR failover caused by stale customer data. The fix ensures there are no login failures.