Supported Metrics
The following tabs represent the Metric Category of Wireless Lan Controller.
| Native Type | Metric Name | Display Name | Metric Category | Unit | Application Version | Description |
|---|---|---|---|---|---|---|
| Wireless LAN Controller | wlan_controller_cpuUtilization | WLC CPU Utilization | Usage | % | 1.0.0 | Provides the current CPU load of the switch in percentage. |
| wlan_controller_apsCount | WLC Connected APs Count | Usage | count | 1.0.0 | Specifies the count of APs that are connected with WLC. | |
| wlan_controller_memoryUtilization | WLC Memory Utilization | Usage | % | 1.0.0 | Provides the current memory utilization of the switch in percentage. | |
| wlan_controller_temperature | WLC Temperature | Power | C | 1.0.0 | Provides the current internal temperature of the unit in centigrade. | |
| wlan_controller_clientsCount | WLC Maximum Clients | Usage | count | 1.0.0 | Provides the maximum clients present on the controller. | |
| wlan_controller_systemUpTime | WLC System UP Time | Usage | s | 1.0.0 | Time lapsed since last reboot. | |
| Wireless LAN Controller Access Point | wlan_controller_ap_operationStatus | WLC AP Operation Status | Availability | 1.0.0 | Operation State of the AP. Possible values: associated(1), disassociating(2), downloading(3). | |
| wlan_controller_ap_adminStatus | WLC AP Admin Status | Availability | 1.0.0 | Admin state of the AP. Possible values: enable(1), disable(2). | ||
| wlan_controller_ap_ifLoadRxUtilization | WLC AP Receiver Utilization | Usage | % | 1.0.0 | Percentage of time the AP receiver is busy operating on packets. | |
| wlan_controller_ap_ifLoadTxUtilization | WLC AP Transmitter Utilization | Usage | % | 1.0.0 | Percentage of time the AP transmitter is busy operating on packets. | |
| wlan_controller_ap_ifLoadChannelUtilization | WLC AP Load Channel Utilization | Usage | % | 1.0.0 | Monitors the AP channel utilization. | |
| wlan_controller_ap_coverageProfilestate | WLC AP Coverage Profile State | Availability | 1.0.0 | Measurement of client coverage. Possible values: Fail(0), Pass(1). | ||
| wlan_controller_ap_noiseProfilestate | WLC AP Noise Profile State | Availability | 1.0.0 | Measurement of noise levels. Possible values: Fail(0), Pass(1). | ||
| wlan_controller_ap_interferenceProfileState | WLC AP Interference Profile State | Availability | 1.0.0 | Measurement of interference levels. Possible values: Fail(0), Pass(1). | ||
| wlan_controller_ap_loadProfileState | WLC AP Load Profile State | Availability | 1.0.0 | Measurement of AP load. Possible values: Fail(0), Pass(1). |
Default Monitoring Configurations
wlan-controller have default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. User can customize these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommend to do this activity before installing the app to avoid noise alerts and data.
Default Global Device Management Policies available OpsRamp will have a Global Device Management Policy for the Native Type of Wireless LAN Controller. We can find those Device Management Policies at Setup -> Resources -> Device Management Policies -> Search with suggested names in global scope. Each Device Management Policy follows below naming convention:
{appName nativeType - version}Example: wlan-controller Wireless LAN Controller - 1 (i.e, appName = wlan-controller, nativeType = Wireless LAN Controller , version = 1)
Default Global Templates available OpsRamp will have a Global template for the Native Type of Wireless LAN Controller. We can find those templates at Setup -> Monitoring -> Templates -> Search with suggested names in global scope. Each template follows below naming convention:
{appName nativeType 'Template' - version}Example: wlan-controller Wireless LAN Controller Template - 1 (i.e, appName = wlan-controller, nativeType = Wireless LAN Controller, version = 1)
Default Global Monitors available OpsRamp will have a Global Monitors for the Native Type which has monitoring support. We can find those monitors at Setup -> Monitoring -> Monitors -> Search with suggested names in global scope. Each Monitors follows below naming convention:
{monitorKey appName nativeType - version}Example: Wireless LAN Controller Monitor wlan-controller Wireless LAN Controller 1 (i.e, monitorKey =Wireless LAN Controller Monitor, appName = wlan-controller, nativeType = Wireless LAN Controller , version = 1)