Resolved Issues

AOS-CX alerts were not generated for half duplex when the link was set to half-duplex. The fix ensures that alerts are generated for half duplex when the link is set to half duplex.

The configuration pages in HPE Aruba Networking Central took more time to load data for the first time. This issue occurred because of the huge bundle size of the related modules. The fix ensures that the configuration pages take less time to load data.

The Experience card and Connection steps of a DNS client were not updated when a successfully onboarded DNS client encountered a DNS failure during renewal. The fix ensures that the Experience card and Connection steps are updated successfully for a DNS client during renewal.

A large number of classifier policies exceeding the switch limit were pushed by HPE Aruba Networking Central. The fix ensures that classifier policies are pushed as per the switch limit.

Users were unable to deploy more than one TACACS server to an onboarded device when multiple RADIUS servers were already configured on the device. This issue occurred because HPE Aruba Networking Central enforced a global limit of 16 authentication servers across all server types. The issue is resolved by updating the validation logic to automatically allow up to 16 servers per authentication type (such as RADIUS or TACACS), instead of enforcing a combined limit.

Users were unable to simultaneously delete the start and end time of the certificate lifetime through APIs. The issue is resolved by enhancing the APIs that are used to configure the start and end time of the certificate lifetime.

A few users were unable to create or edit a Source Interface profile with a management VRF profile. This issue occurred due to the missing L3 VLAN configuration parameter in the Create Profile > Add Source Interface page. The fix ensures that users can create or edit the Source Interface profile.

The Interface Collision Error alert was displayed twice on the Connectivity Performance card on the device dashboard. The fix ensures that the device dashboard displays the alert once.

In HPE Aruba Networking Central, configuration push failed if a role name included the strings GBP, ABP, or PAP. The fix ensures that the configuration push is successful regardless of these sub-strings in role names.

The interfaces list for switches displayed in the VLAN card is inaccurate. This issue occurs when an interface dropped by proxy is not seen in the list. The fix ensures that invalid interfaces are filtered and the interfaces list for switches is displayed correctly.

In HPE Aruba Networking Central, users were able to map mismatched IP address families through the UI—specifically, Source → IPv4 with Destination → IPv6, or vice versa. This issue led to discrepancies between UI and API behavior. The fix ensures that only matching IP address families can be mapped in HPE Aruba Networking Central, thereby aligning UI behavior with API constraints and preventing configuration discrepancies.

When users attempted to create role-based policies with special characters via Library > Security Policies > Role-based Policies in HPE Aruba Networking Central, the system threw an Invalid payload error. The fix ensures that role-based policies with special characters can be created successfully.

HPE Aruba Networking Central failed to push the default configuration to the device. This issue occurred when there were restrictions for specific platforms where the default configuration did not apply. When other configurations, which were mapped at a higher level than the device in the hierarchy, were used, it led to missing dependencies at the device level. The fix ensures that HPE Aruba Networking Central successfully pushes the default configuration to the device.

When a user performed a role configuration push to the gateway without a policy, and attached it to the PSK overlay WLAN, it created an aaa profile without a role profile on the gateway.

Reverse translation for EST profiles failed when using the following CLI commands.

• subject-alt-name ip
• subject-alt-name dns-name
• key-usage <digital-signature | non-repudiation | key-encipherment | data-encipherment | key-agreement>
• key-usage key-restriction <encipher-only | decipher-only>
• ext-key-usage <server-auth | client-auth>

This issue occurred because the AOS-CX commands for PKI, added in 10.15, were not supported. The fix ensures that the reverse translation is successful for EST profiles when using the AOS-CX commands.

Swagger incorrectly listed lag_role as a parameter for LAG configuration, but it applied to LAG member interfaces. The fix ensures that lag_role is listed as a parameter for LAG member interfaces.

The profile parameter was incorrectly displayed under profile-timers in Swagger API for both interfaces and LAG interfaces (port channels). This issue occurred because each Precision Time Protocol (PTP) timer already specified its associated profile, making the profile parameter redundant. The issue is resolved by removing the parameter from the schema to match the actual CLI behavior.

In HPE Aruba Networking Central, the Clients page failed to display a count of failed, connecting, and disconnected clients. Only a count of connected clients was displayed in the alert context. This issue occurred due to the filter selection. The fix ensures that the Clients page displays a count of all clients.

In HPE Aruba Networking Central, the Hardware card in the Unified Device List (UDL) > device context page for some switches did not display any information under the Fans and Power Supplies headings. The fix ensures that the correct information is displayed.

When users configured the DHCP profile for a gateway, it failed if the start IPv4 address and end IPv4 address matched the full IP address range, and the exclude address was not specified. The fix ensures that the DHCP profile works as expected.

The Health card in the site context in HPE Aruba Networking Central displayed a generalized gateway interface error statement for gateways in the site. The fix ensures that individual health alerts are displayed for each gateway interface error.

An error message IPv4 address DHCP could be created only as a local object was displayed when a VLAN profile was configured in the library scope. This issue occurred when the L3 was enabled and IP Address Assignment was set to DHCP. The fix ensures that VLAN profile configuration with L3 enabled is now supported using both DHCP and Static IP Address Assignment options.

When users created a network policy or role-based policies under the Library > Roles & Policies tab using net-group addresses for the source and destination, the configuration push to the AOS-S switch failed. The fix ensures users can successfully push the configuration to the AOS-S switch.

In the Configuration > Named Objects > Create Service page, users successfully created a netservice with UDP port numbers 6000 and 7000. However, when users tried to create a duplicate entry of the same profile with the same configuration, the duplicate entry failed with the error validation failed: Predicate missing for leaf-list 'ports' in path.: Predicate missing for leaf-list 'ports' in path.: Ports and port-range cannot both be present. The fix ensures that users can create a duplicate netservice profile with the same configuration.

The gateway Health Card did not have a hyperlink to navigate to the Alerts page for high interface error alerts. With the new enhancement, a hyperlink is added in the gateway Health Card when an alert exists for the respective interface error alerts.

The site health data displayed incorrect information despite having one device with good health and no clients present. High CPU utilization on one device impacted the overall health status reported. The fix ensures that the site health dashboard displays the correct device health information.

The VLAN mismatch between AP and Switch alert cleared automatically and reappeared after about 20 minutes. The fix ensures that the alert no longer clears automatically and remains active as expected.