Release Notes Wireless LAN Controller (WLC) Collector 8.2.0

Edit online

The Release Notes for Wireless LAN Controller Collector 8.2.0 are now available (release date: 2026-04-30). Contact your Technical Account Manager, Systems Engineering Team, or Support Team to plan the installation.

Note:

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.

Important:

The SevOne NMS enforces a limit of 10,000 indicators on the API endpoint /api/v3/data/performance_metrics. When a request exceeds this limit, the API returns an error and no results are generated.

In these situations, the Wi‑Fi AP Dashboard OOTB report displays Too much data requested. Please limit widget resources message.

For additional details, refer to the SevOne support article https://www.ibm.com/support/pages/sevone-nms-api-result-limit-10000-indicators-apiv3dataperformancemetrics-endpoint?view=full.

Compatibility Matrix

Edit online
Note:
  • T & S - Tested & Supported
Table 1. Wi-Fi Collector Compatibility Matrix
Wi-Fi Version SevOne NMS REST API Service-Oriented Architecture (SOA) Widget Version SevOne Data Insight
8.2.0 8.2.0(RHEL) 2.1.47 >=8.2.0 8.2.0 8.2 (T & S)

COLLECTORS

Table 2. Wireless LAN Controller Collectors Compatibility Matrix
Cisco Catalyst Aruba Enterprise Aruba Instant
8.2.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-635

- Aruba AP-655

Models tested:

-Aruba AP-303

-Aruba AP-505

Models tested: (for Wifi 6E Access Points)

- Aruba AP-615

<= 8.11.2

Model tested:(for Wifi 6E Access Points)

-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
Important: For multiple containers to run properly, minimum memory required is (2 + n * 1) or more GB where, n = number of containers.
When SevOne NMS is upgraded, Wi-Fi Plugin is upgraded automatically.
Note: Upgrade from SevOne NMS 7.0.x to SevOne NMS 8.2

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.

Important changes introduced by this change
  1. 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.
  2. All the settings that were historically controlled via aruba.env and cisco.env files are now automatically migrated over to:
  3. 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.

New Features / Enhancements

Edit online
New Feature: ICMP Plugin Enablement for Newly Discovered WAPs

A new configuration flag ENABLE_AP_ICMP in wifi_global_settings.json file has been introduced to control ICMP plugin enablement for newly discovered Wireless Access Points (WAPs).

By default, the ICMP plugin remains false (disabled). When the flag is changed to true, the ICMP plugin will automatically be enabled for all newly discovered or onboarded Access Points (APs) effective from version 8.2.0 onward. This change applies only to new devices and does not impact previously onboarded APs. No plugin reinstallation is required when toggling the flag.

For more details, refer to Enable ICMP Plugin for Newly Discovered CISCO Wireless Access Points (WAPs).

Feature Enhancement: OUI Configuration for New Installations
Automatic update capability for OUI configuration is supported only for new installations. During a new installation, manufacturer devices are created using the updated manufacturer name and address information from the oui.csv.sample file located in /config/collectors/wifi/configuration. This enhancement does not affect systems that are upgraded from earlier versions.
Feature Enhancement: Adaptive REST API Timeout

Added an adaptive timeout mechanism for REST API requests.

Previously, requests used a fixed timeout defined by SEVONE_API_READ_TIMEOUT (default: 60 seconds). The timeout is now dynamically adjusted based on request outcomes to improve resiliency during downstream delays and traffic spikes.

Configuration Updates
SEVONE_API_READ_TIMEOUT now defines the minimum timeout value used by the adaptive timeout logic.
New configuration parameters are available in advanced_config.env:
  • SEVONE_API_READ_TIMEOUT – Minimum timeout (default: 60 seconds)
  • SEVONE_API_MAX_TIMEOUT – Maximum timeout (default: 180 seconds)
  • SEVONE_API_BACKOFF_FACTOR – Multiplier applied after request failures (default: 1.50)
  • SEVONE_API_DECREASE_FACTOR – Multiplier applied after successful requests (default: 0.90)
Behavior
  • Timeout increases by 1.5× after failures, up to 180 seconds.
  • Timeout decreases by 0.9× after three consecutive successful requests, down to 60 seconds.
  • Failed requests are automatically retried using the updated timeout.
Configuration parameter update: unknown to default_retention_period

In version 8.2.0, the unknown parameter in the WiFi collector configuration file is deprecated and replaced with default_retention_period.

The configuration file is located at /config/collectors/wifi/configuration/disable_config.json.

In a fresh installation of version 8.2.0:
  • The unknown parameter is not included in the configuration file.
  • The default_retention_period parameter is set to 360 hours by default.
Example configuration: 
{
  "default_retention_period": 360
}
When you upgrade from version 8.1.0 to 8.2.0, the system automatically migrates your configuration:
Scenario Migration behavior
SSID (ESSID) is configured The existing SSID value is retained.
SSID (ESSID) is not configured SSID is not migrated.
unknown parameter is configured The value is migrated todefault_retention_period.
Example migration:
  • Version 8.1.0 configuration. 
    {
  "SSID": 24,
  "unknown": 120
}
  • Version 8.2.0 configuration after upgrade. 
    {
  "SSID": 24,
  "default_retention_period": 120
}

Resolved Issues

Edit online
Important: It is strongly recommended to run the external security scans such as Nessus, Snyk, or similar on the latest available patch for this release to verify whether the vulnerability has been addressed. If upgrading the production environment is not currently possible, these scans can still be performed in a lab or test environment.
Table 3. Resolved Issues in Release 8.2.0
Key Release Notes

S1NPM-118786

AP Details: Access Point (AP) drop-down now refreshes correctly when the data source is changed and works as expected.

S1NPM-119222

Platform: Improved handling of files in the /config/collectors/wifi/backup-config directory by introducing a cleanup/rotation mechanism. Backup files are now managed automatically to maintain history while ensuring efficient disk space utilization, eliminating the need for manual cleanup.
S1NPM-119650 Addressed CVE-2026-0094.
S1NPM-119773 / S1NPM-120018 Addressed CVE-2025-15467.

4 issues

Known Issues

Edit online
Table 4. Known Issues in Release 8.2.0
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-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.

2 issues