Resolved Issues

The AP image did not change based on the AP model in the site and device context. The fix ensures that the correct AP image is displayed in the AP side panel, AP details page, and the Connectivity card. The correct AP image is displayed if the image for the AP part number is present in the product image library. Otherwise, a generic image is displayed.

Tags were not displayed for some clients connected to the IAP. The fix ensures that tags are displayed for all clients connected to the IAP.

In the Application Visibility page, the UI was breaking when the Time travel was selected beyond 7 days. The fix ensures that Application Visibility page UI is stable.

The Category field was not visible for some tagged clients. This happened mostly to CX clients, both direct and LLDP. The fix ensures that the Category field is properly displayed for tagged clients.

While creating Sites, the timezone was shown as empty for some latitudes and longitudes. Due to this, Site creation was failing. The fix ensures that for instances where the timezone shows up as empty, the Timezone field is reset to Coordinated Universal Time (UTC), thus allowing Site creation.

The DNS alerts were not getting generated on time. The fix ensures that the DNS alerts are generated without any delay.

ASSOC denylist alerts were not generated for a few test scenarios. The fix ensures that the ASSOC denylist alerts are generated.

The timeline chart displayed both lineage and non-lineage alerts for the selected time alert, as well as bars that extended to the end of the current time. The fix ensures that the timeline chart displays the correct duration.

Multiple lineages for the same alert identity are not displayed on the timeline chart. The fix ensures that multiple lineages display for the same alert identity.

When the Gateway (7240XM) and AP were in the same group. The user created an ESS profile with Tunnel as the forwarding mode and then tried to connect the wireless clients to the ESS profile. During this, the user noticed that the Tunnel is not up between the gateway and the AP. This resulted the Client planet to appear empty and triggered the Association Failure for Gateway Down Alert Scenario. The fix ensure that the client planet is visible.

The Airflow job failed with name 'analyzer_type' is not defined error. This issue occurred because the name analyzer_type was changed to optimiser_type. The fix ensures that the Airflow job runs without any error.

To simulate DHCP Server Timeout, a user created one ESS Profile with a Static VLAN configuration as 411 and did not tag the VLAN 411 on the AP's uplink port. When the user connected four wireless clients and tried to generate the DHCP Discover Timeout scenario, the timetravel for lineage alerts displayed the Network Planet as Unknown. The fix ensures that the lineage alerts displays the Network Planet name correctly.

In the Switch dashboard, the Connectivity Performance card did not display the health reason for a high frame error rate after CRC errors. The fix ensures that the health reason is correctly displayed for the CRC errors.

HPE Aruba Networking Central displayed clients that were not local to a AOS-CX switch in the clients list. The fix ensures that AOS-CX switches only display clients that are local to it in the clients list.

The descriptions in the Events and Reasons had incorrect terminologies. This issue is resolved by using the correct terminologies in the descriptions of Events and Reasons.

The site health displayed invalid warnings. The fix ensures that the site health lists the correct warnings.

The AP WLANs card did not list all WLANs assigned to each radio in an AP. The fix ensures that the AP WLANs card lists all WLANs assigned to each radio in an AP.

The AP Connectivity Performance Channel Utilization card intermittently displayed incorrect values across the Timeline widget. The fix ensures that the AP Connectivity Performance Channel Utilization card displays the correct values across the Timeline widget.

The client DHCP acknowledge events listed Bands and Band Frequency fields. The fix ensures that the client DHCP acknowledge events lists the WiFi Standard field.

Source details of the client was not listed in the Events list. This issue occurred when the source details of a client was not available. The fix ensures that when source details of a client is not available its MAC address is listed as the source.

HPE Aruba Networking Central UI listed some AOS-CX switches as offline and clients as Connected. The fix ensures that HPE Aruba Networking Central lists the correct status of the switches and clients.

An AP disconnect alert did not auto-close after the AP was back online. The fix ensures that AP disconnect alerts auto-close when the AP is back online.

The Event details closes when Event List reloaded on auto-refresh. The fix ensures that the Event details is not affected by Event List auto-refresh.

Chatty events were not aggregated. The fix ensures that chatty events are aggregated to one event and display the count of how many occurrences of the same event occurred.

The Usage card in the site context displayed discrepancy with client usage data. The fix ensures that the Usage card in the site context displays the correct client usage data.

The Connection Path was incorrectly plotted in the Connectivity card for a wired client. The fix ensures that the Connection Path is plotted correctly.

Some events disappeared from the Events list unexpectedly. The fix ensures that the Events list works as expected.

The SFP ports were not displayed for switches. This issue is resolved by displaying the SFP ports for applicable switches.

The Connectivity card in the client context loaded slowly. The fix ensures that the Connectivity card loads as expected.

HPE Aruba Networking Central UI allowed a user to expand the cards in the page when the data was still loading. This issue is resolved by allowing a user to expand the cards in a page after the data is loaded.

The AOS-CX switches did not display the uplink performance and percentage. This issue is resolved by displaying the uplink performance and percentage for AOS-CX switches.

The classification of IoT devices was inconsistent. The fix ensures that IoT devices are classified consistently.

Sorting did not work correctly on the Critical Alerts column in the expanded sites card. The fix ensures that sorting works correctly.

The sequence of the radios in the AP Connectivity Performance card was inconsistent. The fix ensures consistent sequence of the radios in the AP Connectivity Performance card.

The client context incorrectly displayed the client count as connected when a VSF was offline. The fix ensures that correct client count is displayed.

The faceplate of a AOS-CX 8360 switch displayed incorrect port data. This issue is resolved by displaying the correct port data on the faceplate of AOS-CX switch.

Sorting the Last Used column at the site and client contexts displayed errors. The fix ensures that sorting the Last Used column works as expected.

The client count was inconsistent between HPE Aruba Networking Central and Classic Central. The fix ensures that the client count is inconsistent between HPE Aruba Networking Central and Classic Central.

Converting a VLAN from trunk or vice-versa did not work on an interface card. The fix ensures that converting a VLAN from trunk or vice-versa works as expected.

An incorrect destination name for VXLAN tunnel was displayed. This issue is resolved by displaying the correct destination name for VXLAN tunnel.

HPE Aruba Networking Central UI displayed the Error Loading Navigation page when a user clicked AP Disconnected Alert in Alerts. The fix ensures that clicking AP disconnected alerts works as expected.

Displaying the faceplate of an AOS-S switch longer than expected. The fix ensures that the faceplate of an AOS-S switch loads as expected.

In the Client context, the AP Connectivity card showed the AP datapath but not the correct color status of the AP. This issue is resolved by displaying the correct color status of an AP.

The AP connection path was not updated when an AP was moved to a different switch. The fix ensures that the AP connection path is updated when an AP is moved to a different switch.

An incorrect VLAN ID was displayed for an AOS-CX switch. The fix ensures that the correct VLAN ID is displayed.

The Timeline widget for poor health did not display the selected time and health for that time. The fix ensures that the Timeline widget works as expected.

Some pages in the HPE Aruba Networking Central UI too more than expected time to load. The fix ensures that the HPE Aruba Networking Central UI pages load as expected.

A discrepancy was observed in the client count in the Unified Clients list and the client count in the Devices context of a site. The fix ensures that the client count is consistent in the Unified Clients list and the Devices context of a site.

The wired interfaces faceplate displayed incorrect numbers for an AOS-S switch. The fix ensures that the wired interfaces faceplate displays the correct numbers.

The Unified Device list did not load completely when the Back button was clicked from AP, gateway, or switch dashboard. The fix ensures that the Unified Device list loads as expected.

The Alerts list took longer than usual to load when a user switched quick filters. The fix ensures that the Alerts list loads as expected.

The terminology in the uplink change description was incorrect. This issue is resolved by using the correct terminology in uplink change description.

The 6 GHz band information was not displayed in the client Connectivity and Properties cards. This issue is resolved by displaying the 6 GHz band information in the client Connectivity and Properties cards.

The Usage card displayed incorrect throughput data. The fix ensures that correct throughput data is displayed in the Usage card.

Incorrect state of clients was displayed in the Client Experience and Connectivity Performance cards. This issue is resolved by displaying the correct state of clients in the Client Experience and Connectivity Performance cards.

The AP Connectivity Performance card displayed an incorrect client count. The fix ensures that the correct client count is displayed in the AP Connectivity Performance card.

Sorting the by Uptime column in the Devices list did not work correctly after upgrading or restarting APs. The fix ensures that sorting by the Uptime column works as expected.

The client count did not match between the site context and the Unified Client list. This issue is resolved by displaying consistent client count between the site context and the Unified Client list.

The cursor moved faster than the floor plan when the floor plan was clicked and dragged. The fix ensures that the velocity of the cursor and floor match.

The Connected since time was truncated in the client details page. This issue is resolved by displaying the more icon to accommodate the time of day (AM or PM).

The Unified Client list displayed more clients when the Filter by network filter was applied although the graph displayed lesser clients. This issue is resolved by displaying correct clients in the Unified Client list and graph when the Filter by network filter is applied.

VLAN ID 3333 was displayed as available for some APs. This issue is resolved by not displaying VLAN ID 3333 for APS.

The Usage graph at the site context started at zero. The fix ensures that a flat line is displayed at the start of the Usage graph.

The gateway to AOS-CX stack relation was not formed in the topology graph. The fix ensures that the gateway to AOS-CX stack relation in the topology graph works as expected.

The overall AOS-CX stack health was displayed as Poor although the health of the stack members was good. This issue is resolved by considering the periodic stack member health information to determine and display the overall AOS-CX stack health.

The link health of back-to-back connected switches was displayed as Unknown although the interface and device health was good. The fix ensures that the link health is displayed.

The device count in the site expanded card and the Devices list did not match. This issue occurred when a switch stack was added to a site. The fix ensures that consistent device count is displayed in the site expanded card and the Devices list.

The chord view icon was not displayed for a gateway in the Device context. The fix ensures that the chord view icon is displayed for the gateway.