Release Notes Wireless LAN Controller (WLC) Collector 8.0.0
Below please find the Release Notes for Wireless LAN Controller Collector 8.0.0 (Release Date: July 24, 2025). Please contact your Technical Account Manager (if applicable) or Systems Engineering Team or Support Team to discuss and plan the installation. Thank you for being a customer.
When running on an unsupported OS version, the collector does not automatically stop execution. Instead, it continues to run and logs a warning about the unsupported environment in /var/log/wifi-wlc/wlc_run.log. This log entry can be used for troubleshooting purposes.
Compatibility Matrix
- T – Tested & S – Supported
| Wi-Fi Version | SevOne NMS | REST API | Service-Oriented Architecture (SOA) | Widget Version | SevOne Data Insight |
|---|---|---|---|---|---|
| 8.0.0 | 8.0.0 (RHEL) | 2.1.47 | >=8.0.0 | 8.0.0 | 8.0 (T & S) |
COLLECTORS
| Cisco Catalyst | Aruba Enterprise | Aruba Instant | |
|---|---|---|---|
| 8.0.0 | <= 17.17.1
Models tested: - 9800-40 Wireless Controller - 9800-80 Wireless Controller - 9800-L-C Wireless Controller - 9800-L-F Wireless Controller - 9800-CL Wireless Controller for Cloud |
<= 8.12.0.4
Models unsupported (for Wifi 6E Access Points): - Aruba AP-615 - Aruba AP-635 - Aruba AP-655 Models tested: Aruba AP - 303 Aruba AP - 505 |
<= 8.11.2 Models tested: - Aruba AP-615 |
| Other Requirements |
CPU: 2 or more RAM: 4GB or more HDD: 20GB or more Docker: 18.06.1-ce or higher |
CPU: 2 or more RAM: 4GB or more HDD: 20GB or more Docker: 18.06.1-ce or higher |
CPU: 2 or more RAM: 4GB or more HDD: 20GB or more Docker: 18.06.1-ce or higher |
The Wi-Fi solution has been refactored to use native integration. If you are upgrading from SevOne NMS version 7.0 or earlier, the Wi-Fi plugin is automatically configured and upgraded to the corresponding version.
- Every Controller that was previously enabled for the Wi-Fi solution, will have the Wi-Fi Plugin automatically enabled and configured as part of the upgrade process.
- All the settings that were historically controlled via aruba.env and cisco.env files are now automatically migrated over to:
- SevOne NMS Wi-Fi Plugin user interface.
- wifi_global_settings.json file which contains the environment variables.
- advanced_config.env file which contains the advanced environment variables.
- Other configuration files remain unchanged and are configurable on every peer. Existing configurations are also migrated to their new locations. Please refer to Additional Configuration Files for details on the following files.
- oui.csv.sample - contains mapping information between the first six characters of MAC addresses for station objects and their corresponding manufacturers.
- disable_config.json - input file for the script that disables objects.
- phy_types.json - contains mapping information for the physical radio types of stations.
Useful Guides
From IBM's Documentation Portal (https://www.ibm.com/docs/en/sevone-npm), please refer to Wireless LAN Controller (WLC) / SevOne Data Insight guides for this release for details.
Resolved Issues
| Key | Release Notes |
|---|---|
| S1NPM-100819 | Please note that the OOTB reports are no longer supported starting from version 8.0.0 and onwards. As a result, this ticket has been removed. |
| S1NPM-100822 | Please note that the OOTB reports are no longer supported starting from version 8.0.0 and onwards. As a result, this ticket has been removed. |
| S1NPM-100830 | Please note that the OOTB reports are no longer supported starting from version 8.0.0 and onwards. As a result, this ticket has been removed. |
| S1NPM-114904 | Addressed CVE-2025-27516. |
| S1NPM-115599 | Platform: Wi-Fi collector is now collecting Deferred Data correctly. |
| S1NPM-116637 | Addressed CVE-2025-4565. |
6 issues
Known Issues
| Key | Known Issues |
|---|---|
| S1NPM-113199 |
Wifi-Solution-6a_Cisco-WLC-AP-Inventory-Report: The device drop-down may not populate due to incorrect variable binding to the WiFi device group; this is not a synchronization or connectivity issue. Workaround: Edit Select a Cisco Wifi WLC Device, manually select the WiFi device group, and then choose the device to display data. |
| S1NPM-116559 | When the device is onboarded to SevOne NMS, certain metadata values in the Performance Metrics - SNMP Availabiltiy page are not populated as expected. |
| S1NPM-116837 |
After adding Wireless LAN Controllers (WLCs) on SevOne NMS 8.0.0, 400 Client Error is observed on the endpoint /api/v3/indicators/last-seen in the /var/log/wifi-wlc/disable_objects log . |
| S1NPM-116928 | WiFi: In SevOne NMS versions 8.0.0 through 8.0.6, after integrating Wireless LAN Controllers (WLCs) with a large number of Access Points, WiFi collector polling on the NMS peer may become interrupted or stop unexpectedly, impacting data collection.
Workaround: From the SevOne NMS command line interface, restart the WiFi collector container.
Note: This issue is resolved in SevOne NMS version 8.0.7 and later.
|
| S1NPM-117039 |
Platform: In a fresh installation of SevOne NMS version 7.2.0, the Device Type Membership tab does not display device-related details for both the SC CISCO ACI HYPERVISOR and SC CISCO ACI VM device types. Furthermore, after upgrading SevOne NMS from version 7.2.0 to 8.0.0, the Device Type Membership tab does not display device-related details for the SC CISCO ACI VM device type. |
| S1NPM-117227 | After the installation of SevOne NMS 8.0.0, the WiFi Station Monitor policy is not displayed on the Policy Browser page. |
| S1NPM-119222 |
Files in the Workaround: Until an automated cleanup solution is implemented, files can be manually deleted on a periodic basis to control disk space utilization. |
| S1NPM-119377 | When WiFi collector becomes unavailable and later resumes operation, the SevOne NMS graph connects the latest data point to the last recorded value. As a result, the graph does not display the gap in data collection during the collector outage. |
| S1NPM-119869 |
WiFi Disable Object script may fail when the indicators/last-seen API endpoint returns objects with id = 0 due to unresolved indicators. The script does not validate object IDs before processing and proceeds with API requests using the invalid id = 0, resulting in execution errors and failure logs. This issue requires a validation check to skip objects with id = 0. |
9 issues