CISCO-LWAPP-DOT11-CLIENT-MIB :: cldcClientProtocol

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-LWAPP-DOT11-CLIENT-MIBcldcClientProtocol

cldcClientProtocol

Module: CISCO-LWAPP-DOT11-CLIENT-MIB

OID (symbolic): CISCO-LWAPP-DOT11-CLIENT-MIB::cldcClientProtocol

OID (numeric): 1.3.6.1.4.1.9.9.599.1.3.1.1.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This object represents 802.11 protocol type of the client it used to join to wireless network. A value of 'dot11a' represents that the client is using 802.11a standard to connect to the access point (AP) A value of 'dot11b' represents that the client is using 802.11b standard to connect to the access point (AP) A value of 'dot11g' represents that the client is using 802.11g standard to connect to the access point (AP) A value of 'unknown' represents that the client protocol is unknown A value of 'mobile' represents that the client using mobile wireless to connect to the access point (AP). A value of 'dot11n24' represents that the client is using 802.11n standard with 2.4 GHz frequency to connect to the access point (AP) A value of 'dot11n5' represents that the client is using 802.11n standard with 5 GHz frequency to connect to the access point (AP). A value of 'ethernet' represents that the client is using ethernet standard to connect to the access point (AP). A value of 'dot3' represents that the client is using dot3 standard to connect to the access point (AP). A value of 'dot11ac5' represents that the client is using 802.11ac standard with 5 GHz frequency to connect to the access point (AP).

What is cldcClientProtocol?

This object identifies which IEEE 802.11 wireless standard (such as 802.11a, 802.11b, 802.11g, 802.11n, or unknown) a connected client device is using. Operators use this to understand the mix of wireless protocols on their network and identify compatibility issues or devices using older standards. This information is useful for planning wireless upgrades and understanding client device capabilities.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.599.1.3.1.1.6
snmpwalk -v2c -c public <target> CISCO-LWAPP-DOT11-CLIENT-MIB::cldcClientProtocol

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.599.1.3.1.1.6.1
snmpget -v2c -c public <target> CISCO-LWAPP-DOT11-CLIENT-MIB::cldcClientProtocol.1

Start monitoring Cisco Wireless LAN Controllers (LWAPP-based) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-LWAPP-DOT11-CLIENT-MIB::cldcClientProtocol OID value, configure state conditions and alerts, and monitor any Cisco Wireless LAN Controllers (LWAPP-based) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.599ciscoLwappDot11ClientMIBCISCO-LWAPP-DOT11-CLIENT-MIB
1.3.6.1.4.1.9.9.599.1ciscoLwappDot11ClientMIBObjectsCISCO-LWAPP-DOT11-CLIENT-MIB
1.3.6.1.4.1.9.9.599.1.3cldcStatusObjectsCISCO-LWAPP-DOT11-CLIENT-MIB
1.3.6.1.4.1.9.9.599.1.3.1cldcClientTableCISCO-LWAPP-DOT11-CLIENT-MIB
1.3.6.1.4.1.9.9.599.1.3.1.1cldcClientEntryCISCO-LWAPP-DOT11-CLIENT-MIB
1.3.6.1.4.1.9.9.599.1.3.1.1.6cldcClientProtocolCISCO-LWAPP-DOT11-CLIENT-MIB