Resolved Issues

Table 1: Resolved Issues in November 11th 2025 Release
Issue ID	Description
CNX-31997	When a VSF stack link was disconnected, whether by physically disconnecting the cable or disabling the port, the VSF Link Status was not updated or displayed in the Stack Expanded Card view (Network Operations > Devices > Switches > Select Stack > Stack Expanded Card). The fix ensures that the status is updated immediately after disconnecting the cable or disabling the port.
CNX-61316	The menu > Reports page incorrectly displayed Switch Stack IDs instead of the Switch conductor serial number in the Serial field for UDL. The fix ensures that the Switch conductor serial number is displayed correctly.
CNX-62236	The incorrect API endpoint was displayed on the policy-group Swagger documentation. This issue occurred because the PUT operation was incorrectly shown at the endpoint instead of the policy-name. The fix ensures that the incorrect PUT API is appropriately added.
CNX-77301	When configuring Dynamic DNS over HTTPS in the Library > System > Dynamic DNS page, the Server Interval field incorrectly displayed the range as greater than or equal to 900, instead of 3600 to 86400000. The fix ensures that an error message is displayed if an invalid value is entered in the Server Interval field.
CNX-97110	Users were unable to push a no-advertise-range configuration with type as INTER_AREA to the device. This issue occurred due to problems with the configuration format and device onboarding. The fix allows users to successfully push no-advertise-range with type as INTER_AREA to the device.
CNX-102386	The existing active alert lineages were not being cleared when telemetry data was absent for extended periods due to upgrades, converter crashes, or OOM events. The fix introduces a mechanism where the new lineage processing application receives alerts from the alert app, processes them, and stitches related lineages. Additionally, a cleanup job now runs every 5 minutes regardless of data availability, ensuring expired lineages are marked inactive.
CNX-168014	The VLAN data for Juniper switches was not being populated on the Wired Interfaces card, resulting in null values under the VLAN column for all ports even when VLAN assignments existed. The fix ensures that VLAN data is now correctly populated and displayed for Juniper switches in the interface.
CNX-180920	In the Topology Link Node View, nodes and links overlapped when a level 1 device was linked to a level 4 VSX-Primary, and the VSX-Secondary was part of a device group. Expanding the group triggered incorrect VSX grouping due to nodes having multiple parents across levels. The fix ensures the node positioning logic uses the most recent parent, ensuring correct alignment and preventing overlap in complex topologies.
CNX-180989	Users encounter the following issues while editing IPv6 static routing profiles at the device level: Adding the same IPv6 route twice to a profile results in the configuration ID to increment, but no configuration changes are pushed to the device. Deleting one of the duplicate routes causes the configuration ID to increment with partial configuration changes which led to the device entering a configuration failure state. This issue occurred because validation was not done and duplicate entries was allowed. The fix ensures that a custom validator checks duplicate route prefixes during profile creation or modification, preventing invalid configurations and maintaining device stability.
CNX-186215	In the topology Link Node View, the device-to-device edge side panel previously displayed VLAN information inconsistently. The side panel was showing only allowed VLANs for Gateway devices, and only native VLANs for Switch devices, while the wired interface card displayed both. The fix now ensures that the side panel consistently displays both native and allowed VLANs for all relevant device types and removes any empty fields.
CNX-189026	The Server Group field momentarily displayed red on the Wireless > WLAN > Update Profile page when the user tried to update a WLAN SSID profile. The fix ensures that the Server Group field is displayed correctly.
CNX-189498	The Cable Test option was not visible on the WebUI when the AP Connected 10/100 Mbps alert was triggered. The fix ensures that associated options along with the alerts are displayed on the WebUI.
CNX-190790	On the Device dashboard, when expanding the Connectivity card, the VPNC device IP address was missing. This fix ensures that the correct IP address is now displayed for VPNC devices.
CNX-191291	The Keep-Alive routed links in the Link-Node topology view failed to display both the source and destination IP addresses. Instead, only one side’s IP was shown. The fix ensures that the IP addresses on the source and destination ends of the Keep-Alive routed links are displayed in the Link-Node topology view.
CNX-193136	In the Site > Topology > Link Node Topology page, the unmanaged port details were not displayed correctly. This issue occurred due to the incorrect processing of the LLDP information from the managed device. The fix ensures that the unmanaged port information is correctly displayed.
CNX-193955	The IP address configured for the switch did not appear in the UI at the device level when a profile was moved from the device collection level to the individual device level, causing the SVI configuration to disappear. This issue occurred even though the IP address was still visible in the VLAN-interfaces. The fix ensures that the IP configurations can be assigned or modified as needed, and the corresponding SVI configuration is correctly displayed in the UI.
CNX-196434	A VSF split detect and secondary member configuration were removed after a VSF switchover. The fix ensures that the VSF stack has split detect management and secondary member configuration.
CNX-197797	In HPE Aruba Networking Central, in the Configuration Health device-specific error page, the profile names of some configuration items contain a single_scope suffix. The fix ensures that the profile names contain correct suffix.
CNX-199213	A VSF chain stack deletion failed and retained residual configurations. The fix ensures that the VSF stack is fully deleted with no residual configurations.
CNX-199273	The health status of the blocked clients under Clients > Blocked displayed incorrect entities. The fix ensures that the health of the blocked clients should display as Unknown and health reason as Denylisted.
CNX-200691	Provisioning failed on 2540 and 2530 PVOS switches when dfp-cppm-timer was included in the system profile because device fingerprinting (DFP) is not supported on these models. Missing validation in capability and capacity (CNC) filtration allowed invalid DFP timer configuration, leading to errors and authentication issues. The fix ensures that provisioning on the switches are completed correctly.
CNX-201339	An AP was not able to receive configuration of management-mode. The fix ensures that an AP can enable automatic configuration in the management mode.
CNX-201857	Users were unable to apply a port-profile on the interface after enabling and then disabling port-security. This issue occurred because the port-security field was not set as null. The fix ensures that the port-security field is set to null in the payload before applying the port-profile to successfully complete the operation.
CNX-201911	A CX VSF device entered a configuration conflict state following a conductor switchover operation. The fix ensures that VSF devices are in a synchronized state following a conductor switchover operation.
CNX-201983	Changes in the chassis linecard module configuration are not injected into the DB despite ports being added correctly. This results in switches displaying Configuration Status: Out of Sync. This is caused by a mismatch in the keys used to identify the changed component over API and in the DB. The fix ensures that the keys are parsed correctly so changes can be correctly injected into the DB.
CNX-202186	The roaming health card is filled with Good health by default for connected clients, even if no roaming event has occurred. The fix ensures that roaming health card displays the client health correctly.
CNX-202276	Although session export is limited to 10k sessions, users were still able to download all sessions including 100k or more. The fix ensures that users are unable to download sessions beyond the limited range.
CNX-202303	Updating VSX profiles for example, SVI ID with KA Type set to KA_SVI, created through the API, in the WebUI resulted in errors and configurations not intended by the user. Accessing such profiles in the WebUI, when they included unsupported options set through the API, could result in configuration failures and unexpected behavior on VSX pair devices. The fix ensures that VSX profiles created using the API should be updated using the API to prevent conflict issues with unsupported use cases in the WebUI.
CNX-202345	On expanding the Performance card in the Client dashboard, the Signal Quality graph was not plotted for certain values. This fix ensures that the Signal Quality graph is displayed correctly.
CNX-203076	On the Switch Interface configuration page, the port-profile reset did not clear port-security settings, resulting in inconsistent reset behavior. The fix ensures that all port-profile configurations, including port-security, are restored to their default values.
CNX- 203283	After a cluster upgrade, the Configuration Health card > Configuration Distribution Failures table does not display error messages for APs that are out of sync. Live configuration pushes are not affected. The fix ensures that the error messages are displayed correctly.
CNX-204964	A gateway's connection path was not displayed correctly. The fix moves the Mobility Gateway swap logic from the read side to the write side. However, the topology diagram remains unchanged.
CNX-205788 CNX-205607	In the Client Onboarding trend view, the Site filters were not applied as expected. This issue occurred because of a missing backport. The fix ensures HPE Aruba Networking Central correctly displays the data based on the filters that were selected on the Classification view.
CNX-208883	The UCL UI displays a drop-down menu allowing users to select time ranges from 3 hours, 1 day, 7 days and 1 month.

CNX-31997

When a VSF stack link was disconnected, whether by physically disconnecting the cable or disabling the port, the VSF Link Status was not updated or displayed in the Stack Expanded Card view (Network Operations > Devices > Switches > Select Stack > Stack Expanded Card). The fix ensures that the status is updated immediately after disconnecting the cable or disabling the port.

CNX-61316

The menu

> Reports page incorrectly displayed Switch Stack IDs instead of the Switch conductor serial number in the Serial field for UDL. The fix ensures that the Switch conductor serial number is displayed correctly.

CNX-62236

The incorrect API endpoint was displayed on the policy-group Swagger documentation. This issue occurred because the PUT operation was incorrectly shown at the endpoint instead of the policy-name. The fix ensures that the incorrect PUT API is appropriately added.

CNX-77301

When configuring Dynamic DNS over HTTPS in the Library > System > Dynamic DNS page, the Server Interval field incorrectly displayed the range as greater than or equal to 900, instead of 3600 to 86400000. The fix ensures that an error message is displayed if an invalid value is entered in the Server Interval field.

CNX-97110

Users were unable to push a no-advertise-range configuration with type as INTER_AREA to the device. This issue occurred due to problems with the configuration format and device onboarding.

The fix allows users to successfully push no-advertise-range with type as INTER_AREA to the device.

CNX-102386

The existing active alert lineages were not being cleared when telemetry data was absent for extended periods due to upgrades, converter crashes, or OOM events. The fix introduces a mechanism where the new lineage processing application receives alerts from the alert app, processes them, and stitches related lineages. Additionally, a cleanup job now runs every 5 minutes regardless of data availability, ensuring expired lineages are marked inactive.

CNX-168014

The VLAN data for Juniper switches was not being populated on the Wired Interfaces card, resulting in null values under the VLAN column for all ports even when VLAN assignments existed. The fix ensures that VLAN data is now correctly populated and displayed for Juniper switches in the interface.

CNX-180920

In the Topology Link Node View, nodes and links overlapped when a level 1 device was linked to a level 4 VSX-Primary, and the VSX-Secondary was part of a device group. Expanding the group triggered incorrect VSX grouping due to nodes having multiple parents across levels.

The fix ensures the node positioning logic uses the most recent parent, ensuring correct alignment and preventing overlap in complex topologies.

CNX-180989

Users encounter the following issues while editing IPv6 static routing profiles at the device level:

Adding the same IPv6 route twice to a profile results in the configuration ID to increment, but no configuration changes are pushed to the device.
Deleting one of the duplicate routes causes the configuration ID to increment with partial configuration changes which led to the device entering a configuration failure state.

This issue occurred because validation was not done and duplicate entries was allowed. The fix ensures that a custom validator checks duplicate route prefixes during profile creation or modification, preventing invalid configurations and maintaining device stability.

CNX-186215

In the topology Link Node View, the device-to-device edge side panel previously displayed VLAN information inconsistently. The side panel was showing only allowed VLANs for Gateway devices, and only native VLANs for Switch devices, while the wired interface card displayed both. The fix now ensures that the side panel consistently displays both native and allowed VLANs for all relevant device types and removes any empty fields.

CNX-189026

The Server Group field momentarily displayed red on the Wireless > WLAN > Update Profile page when the user tried to update a WLAN SSID profile. The fix ensures that the Server Group field is displayed correctly.

CNX-189498

The Cable Test option was not visible on the WebUI when the AP Connected 10/100 Mbps alert was triggered. The fix ensures that associated options along with the alerts are displayed on the WebUI.

CNX-190790

On the Device dashboard, when expanding the Connectivity card, the VPNC device IP address was missing. This fix ensures that the correct IP address is now displayed for VPNC devices.

CNX-191291

The Keep-Alive routed links in the Link-Node topology view failed to display both the source and destination IP addresses. Instead, only one side’s IP was shown. The fix ensures that the IP addresses on the source and destination ends of the Keep-Alive routed links are displayed in the Link-Node topology view.

CNX-193136

In the Site > Topology > Link Node Topology page, the unmanaged port details were not displayed correctly. This issue occurred due to the incorrect processing of the LLDP information from the managed device. The fix ensures that the unmanaged port information is correctly displayed.

CNX-193955

The IP address configured for the switch did not appear in the UI at the device level when a profile was moved from the device collection level to the individual device level, causing the SVI configuration to disappear. This issue occurred even though the IP address was still visible in the VLAN-interfaces.

The fix ensures that the IP configurations can be assigned or modified as needed, and the corresponding SVI configuration is correctly displayed in the UI.

CNX-196434

A VSF split detect and secondary member configuration were removed after a VSF switchover. The fix ensures that the VSF stack has split detect management and secondary member configuration.

CNX-197797

In HPE Aruba Networking Central, in the Configuration Health device-specific error page, the profile names of some configuration items contain a single_scope suffix. The fix ensures that the profile names contain correct suffix.

CNX-199213

A VSF chain stack deletion failed and retained residual configurations. The fix ensures that the VSF stack is fully deleted with no residual configurations.

CNX-199273

The health status of the blocked clients under Clients > Blocked displayed incorrect entities. The fix ensures that the health of the blocked clients should display as Unknown and health reason as Denylisted.

CNX-200691

Provisioning failed on 2540 and 2530 PVOS switches when dfp-cppm-timer was included in the system profile because device fingerprinting (DFP) is not supported on these models. Missing validation in capability and capacity (CNC) filtration allowed invalid DFP timer configuration, leading to errors and authentication issues. The fix ensures that provisioning on the switches are completed correctly.

CNX-201339

An AP was not able to receive configuration of management-mode. The fix ensures that an AP can enable automatic configuration in the management mode.

CNX-201857

Users were unable to apply a port-profile on the interface after enabling and then disabling port-security. This issue occurred because the port-security field was not set as null. The fix ensures that the port-security field is set to null in the payload before applying the port-profile to successfully complete the operation.

CNX-201911

A CX VSF device entered a configuration conflict state following a conductor switchover operation. The fix ensures that VSF devices are in a synchronized state following a conductor switchover operation.

CNX-201983

Changes in the chassis linecard module configuration are not injected into the DB despite ports being added correctly. This results in switches displaying Configuration Status: Out of Sync. This is caused by a mismatch in the keys used to identify the changed component over API and in the DB. The fix ensures that the keys are parsed correctly so changes can be correctly injected into the DB.

CNX-202186

The roaming health card is filled with Good health by default for connected clients, even if no roaming event has occurred. The fix ensures that roaming health card displays the client health correctly.

CNX-202276

Although session export is limited to 10k sessions, users were still able to download all sessions including 100k or more. The fix ensures that users are unable to download sessions beyond the limited range.

CNX-202303

Updating VSX profiles for example, SVI ID with KA Type set to KA_SVI, created through the API, in the WebUI resulted in errors and configurations not intended by the user. Accessing such profiles in the WebUI, when they included unsupported options set through the API, could result in configuration failures and unexpected behavior on VSX pair devices. The fix ensures that VSX profiles created using the API should be updated using the API to prevent conflict issues with unsupported use cases in the WebUI.

CNX-202345

On expanding the Performance card in the Client dashboard, the Signal Quality graph was not plotted for certain values. This fix ensures that the Signal Quality graph is displayed correctly.

CNX-203076

On the Switch Interface configuration page, the port-profile reset did not clear port-security settings, resulting in inconsistent reset behavior. The fix ensures that all port-profile configurations, including port-security, are restored to their default values.

CNX-
203283

After a cluster upgrade, the Configuration Health card > Configuration Distribution Failures table does not display error messages for APs that are out of sync. Live configuration pushes are not affected.

The fix ensures that the error messages are displayed correctly.

CNX-204964

A gateway's connection path was not displayed correctly. The fix moves the Mobility Gateway swap logic from the read side to the write side. However, the topology diagram remains unchanged.

CNX-205788

CNX-205607

In the Client Onboarding trend view, the Site filters were not applied as expected. This issue occurred because of a missing backport. The fix ensures HPE Aruba Networking Central correctly displays the data based on the filters that were selected on the Classification view.

CNX-208883

The UCL UI displays a drop-down menu allowing users to select time ranges from 3 hours, 1 day, 7 days and 1 month.