Skip to main content

Cisco Legacy WLC

Plugin: go.d.plugin Module: snmp

Overview

Monitor Cisco Legacy WLC (wireless lan controller) with Netdata over SNMP. Netdata recognizes the device automatically by its sysObjectID (recognized across 14 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration.

Netdata's SNMP collector matches the device to the cisco-legacy-wlc.yaml profile via sysObjectID/sysDescr, then polls the OIDs it declares.

This integration is supported on all platforms.

This integration supports multiple instances configured side-by-side.

Default Behavior

Auto-Detection

Auto-detected as Cisco Legacy WLC via sysObjectID/sysDescr.

Limits

The default configuration for this integration does not impose any limits.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Setup

You can configure the snmp collector in two ways:

MethodBest forHow to
UIFast setup without editing filesGo to Nodes → Configure this node → Collectors → Jobs, search for snmp, then click + to add a job.
FileIf you prefer configuring via file, or need to automate deployments (e.g., with Ansible)Edit go.d/snmp.conf and add a job.
important

UI configuration requires paid Netdata Cloud plan.

Prerequisites

SNMP access

SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site's SNMP hub.

Configuration

Options

Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.

via UI

Configure the snmp collector from the Netdata web interface:

  1. Go to Nodes.
  2. Select the node where you want the snmp data-collection job to run and click the (Configure this node). That node will run the data collection.
  3. The Collectors → Jobs view opens by default.
  4. In the Search box, type snmp (or scroll the list) to locate the snmp collector.
  5. Click the + next to the snmp collector to add a new job.
  6. Fill in the job fields, then click Test to verify the configuration and Submit to save.
    • Test runs the job with the provided settings and shows whether data can be collected.
    • If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.

via File

The configuration file name for this integration is go.d/snmp.conf.

The file format is YAML. Generally, the structure is:

update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/snmp.conf
Examples

There are no configuration examples.

Alerts

There are no alerts configured by default for this integration.

Metrics

On top of the generic SNMP baseline (the Generic SNMP Device integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Legacy WLC profile adds the metrics below. Each is collected only where the device exposes the matching OID — inclusion means the profile requests it; availability depends on the device model and software.

38 metrics in 7 groups; each row is a chart context usable in alerts.

GroupMetrics
Network / Interface4
Network / TCP12
Network / UDP6
Network / Wireless12
System / CPU1
System / Memory2
System / Uptime1

Network / Interface

Metric (chart context)UnitScopeDescription
snmp.device_prof_ifAdminStatus{status}per interface, interfaceCurrent administrative state of the interface
snmp.device_prof_ifHighSpeedbit/sper interface, interfaceEstimate of the interface's current bandwidth
snmp.device_prof_ifNumber{interface}deviceNumber of network interfaces regardless of their current state present on this system
snmp.device_prof_ifOperStatus{status}per interface, interfaceCurrent operational state of the interface

Network / TCP

Metric (chart context)UnitScopeDescription
snmp.device_prof_tcpActiveOpens{transition}/sdeviceTCP connections transitioning from CLOSED to SYN-SENT
snmp.device_prof_tcpAttemptFails{failure}/sdeviceFailed TCP connection attempts
snmp.device_prof_tcpCurrEstab{connection}deviceCurrent TCP connections in ESTABLISHED or CLOSE-WAIT state
snmp.device_prof_tcpEstabResets{reset}/sdeviceTCP connections reset from ESTABLISHED/CLOSE-WAIT
snmp.device_prof_tcpHCInSegs{packet}/sdeviceTCP segments received
snmp.device_prof_tcpHCOutSegs{packet}/sdeviceTCP segments sent
snmp.device_prof_tcpInErrs{error}/sdeviceTCP segments received with errors
snmp.device_prof_tcpInSegs{packet}/sdeviceTCP segments received
snmp.device_prof_tcpOutRsts{reset}/sdeviceTCP segments sent with RST flag
snmp.device_prof_tcpOutSegs{packet}/sdeviceTCP segments sent
snmp.device_prof_tcpPassiveOpens{transition}/sdeviceTCP connections transitioning from LISTEN to SYN-RCVD
snmp.device_prof_tcpRetransSegs{retransmit}/sdeviceTCP segments retransmitted

Network / UDP

Metric (chart context)UnitScopeDescription
snmp.device_prof_udpHCInDatagrams{packet}/sdeviceUDP datagrams received
snmp.device_prof_udpHCOutDatagrams{packet}/sdeviceUDP datagrams sent
snmp.device_prof_udpInDatagrams{packet}/sdeviceUDP datagrams received
snmp.device_prof_udpInErrors{error}/sdeviceUDP datagrams received but couldn't be delivered (not due to missing app)
snmp.device_prof_udpNoPorts{error}/sdeviceUDP datagrams received with no app on the destination port
snmp.device_prof_udpOutDatagrams{packet}/sdeviceUDP datagrams sent

Network / Wireless

Metric (chart context)UnitScopeDescription
snmp.device_prof_bsnAPAdminStatus{status}per ap_mac_address, ap_name, ap_location, ap_ip_addressAdmin State of the AP
snmp.device_prof_bsnAPIfAdminStatus{status}per ap_if_slot_id, ap_mac_address, ap_name, ap_location, ap_ip_addressAdmin status of the interface
snmp.device_prof_bsnAPIfLoadChannelUtilization%per ap_if_slot_id, ap_mac_address, ap_name, ap_location, ap_ip_addressChannel utilization
snmp.device_prof_bsnAPIfLoadRxUtilization%per ap_if_slot_id, ap_mac_address, ap_name, ap_location, ap_ip_addressPercentage of time the Airespace AP receiver is busy operating on packets
snmp.device_prof_bsnAPIfLoadTxUtilization%per ap_if_slot_id, ap_mac_address, ap_name, ap_location, ap_ip_addressPercentage of time the Airespace AP transmitter is busy operating on packets
snmp.device_prof_bsnAPIfOperStatus{status}per ap_if_slot_id, ap_mac_address, ap_name, ap_location, ap_ip_addressOperational status of the interface
snmp.device_prof_bsnAPIfPoorSNRClients{client}per ap_if_slot_id, ap_mac_address, ap_name, ap_location, ap_ip_addressNumber of clients with poor SNR attached to this Airespace AP at the last measurement interval
snmp.device_prof_bsnAPOperationStatus{status}per ap_mac_address, ap_name, ap_location, ap_ip_addressOperation State of the AP
snmp.device_prof_bsnApIfNoOfUsers{user}per ap_if_slot_id, ap_mac_address, ap_name, ap_location, ap_ip_addressNumber of users associated with this radio
snmp.device_prof_bsnDot11EssAdminStatus{status}per wlan_index, ssidAdministrative Status of ESS(WLAN)
snmp.device_prof_bsnDot11EssNumberOfMobileStations{station}per wlan_index, ssidNumber of mobile stations currently associated with the WLAN
snmp.device_prof_bsnDot11EssRowStatus{status}per wlan_index, ssidRow status type for the bsnDot11EssEntry

System / CPU

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpu_usage%deviceThe current CPU utilization

System / Memory

Metric (chart context)UnitScopeDescription
snmp.device_prof_memory_freeBydeviceFree RAM of the switch
snmp.device_prof_memory_totalBydeviceTotal RAM of the switch

System / Uptime

Metric (chart context)UnitScopeDescription
snmp.device_prof_systemUptimesdeviceTime since the system was last rebooted or powered on.

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.