Intel Connectivity Analytics is a solution that facilitates the transmission of client-side analytics from wireless devices equipped with specific Intel Wi-Fi 6/6E chipsets to Cisco wireless controllers. These advanced analytics include critical details, including the Intel client model, driver version, insights into coverage gaps, reasons for roaming, and power source information.
Moreover, wireless clients supporting Intel Connectivity Analytics will relay client reports containing valuable data such as station information, instances of low Received Signal Strength Indications (RSSI), information on neighboring Access Points (APs), temporary disconnect incidents, encounters with unknown APs, and any failed AP connections, where applicable. This enhanced level of visibility empowers rapid identification and resolution of issues within any wireless network.
Unfortunately, there are some important details that we need to consider and keep in mind. They are as follows:
- this feature is currently exclusive between Cisco and Intel
- Intel Connectivity Analytics is not compatible with Cisco DNA Center at this time
- Cisco Access Point Hardware supporting such feature:
- All Wave 2 and Catalyst 11ax Aps managed by the software 17.6.1 or higher (only IOS XE)
- All Wave 2 and 802.11ax Meraki access point (MR) with firmware 28.5 and above
- Cisco IOS XE WLC Hardware supporting such feature:
- Embedded Wireless Controller on the AP and Switch, C9800-CL, C9800-L, C9800-40, C9800-80
- Intel Chipset supporting such feature: AC8561, AC9560, AX200, AX201, AX210, AX1650, AX1675. Driver version 22.50.1 or higher. Two AC cards are only listed as supported for Cisco Catalyst deployments.
- Intel Connectivity Analytics is enabled by default “Advertise PC Analytics” checkbox under WLAN, Advanced tab for Cisco Catalyst deployments. For the Mareki solution, firmware 28.x enables funcionality automatically.
- Protected Management Frames (PMF) must be set to Optional or Required for Intel Connectivity Analytics to work.
How does it work in practise?
In my test environment, I only worked with the Cisco Catalyst solution: AP: C9120 with a pair of two 9800-80 controllers. Below are the tests that I conducted.
- AX201 wireless card (MAC address 70cf.4950.697d): Driver’ version: 22.50.0.7 System: Windows 11 Version: 21H2
- Cisco IOS XE WLC Hardware: C9800-80. Catalyst 11ax AP: C9120AXI-E
Initial test, as I suspected, there were no analytical data due to the drivers. I immediately proceeded to update the drivers to the latest versions.
- AX201 wireless card (MAC address: 70cf.4950.697d) : Driver’ version: 22.250.1.2 System: Windows 11 Version: 21H2
After updating the drivers, I received additional analytical information, but there’s an issue I don’t understand. The problem is that on Cisco I see different driver information (22.180.16.01) than what I see directly on the computer (22.250.1.2). it’s quite confusing because if we want to know if someone has the latest drivers installed, we won’t find out from such output (my example).
WLC#show device classifier mac-address 70cf.4950.697d detail Client Mac: 70cf.4950.697d Device Type: American Megatrends Internationa ZenBook UX325EA_UX325EA Confidence Level: 40 Day Zero Classification: American Megatrends Internationa Device Name: INTEL CORPORATE Software Version: 22.180.19.01 Device OS: Windows 10 Device Vendor: Intel Power Type: DC Powered Hardware Model: AX201/AX1650 160Mhz
In addition to that, analytical data is being collected, and since I tested it on a single isolated AP, there isn’t much of it.
WLC#show wireless client mac-address 70cf.4950.697d stats pc-analytics
-------------------------
Failed AP Report:
-------------------------
Last Reported Time:: 10/03/2023 13:40:49
APs with Invalid IEs: None
APs not sending response:
-------------------------
BSSID Frame Type
9cd5.7d24.81ce Authentication Response
-------------------------
PC Analytics report stats
-------------------------
----------------------------------------------------------------------
Report Type Processed Reports Dropped Reports
----------------------------------------------------------------------
STA Info 0 0
Neigh AP 1 0
Low RSSI 0 0
Beacon Miss 0 0
Failed AP 1 0
Unknown APs 0 0
- AC9560 wireless card (MAC address: f8e4.e3ed.bef8): Driver’ version: 22.250.1.2 System: Windows 10
Unfortunately, the AC9560 card did not support the Intel Connectivity Analytics feature. After many attempts, I noticed that for some reason, this card with the latest drivers does not support 802.11w. Even though for this model 802.11w should work without any issues, as can be seen in Intel’s wi-fi adapter information guide and the information available on the device itself, still, with optional 802.11w enabled, it doesn’t show Intel Connectivity Analytics info. What’s more, with 802.11w set as required, the device doesn’t want to connect to the SSID at all. In packet capture, you can only observe Probe Requests and Response.
I tried to search the internet to see if anyone had similar problems to mine, and the only thing I managed to find is the fact that the AC9560 card had such issues when connected to networks with 802.11w enabled on Windows 10 devices. Link
After reading a few threads and being aware that the drivers installed are the latest, I upgraded to Windows 11 to see if the problem is also visible on this system.
- AC9560 wireless card (MAC address: f8e4.e3ed.bef8): Driver’ version: 22.250.1.2 System: Windows 11 Version: 21H2
Unfortunately, updating the system to the latest version along with the newest updates and drivers did not bring the expected result. It’s still the same as mentioned above. 802.11w doesn’t work.
Summary
At the moment, the results of my experiments are as follows:
- Following wireless cards will support Intel Connectivity Analytics AX200, AX201, AX210, AX1650, AX1675 with driver version 22.50.1 or higher.
- The information about installed drivers on the Windows machine doesn’t match the data from Intel Analytics provided to the WLC. Anyway, reports providing information such as station information, low Received Signal Strength Indications (RSSI), neighboring Access Points (APs), temporary disconnects, unknown APs, and failed Aps are key elements in my opinion these insights would greatly benefit anyone aiming to troubleshoot connectivity issues from an Intel end device.