CISCO-LWAPP-DOT11-LDAP-MIB

        This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Access Point Protocol
tunnel from Cisco Light-weight LWAPP Access Points.
        
Information provided by this MIB is used to manage
LDAP features on the controller.
        
The relationship between CC and the LWAPP APs
can be depicted as follows:
        
      +......+     +......+     +......+
      +      +     +      +     +      +
      +  CC  +     +  CC  +     +  CC  +
      +      +     +      +     +      +
      +......+     +......+     +......+
        ..            .             .
        ..            .             .
       .  .            .             .
      .    .            .             .
     .      .            .             .
    .        .            .             .
+......+ +......+     +......+      +......+
+      + +      +     +      +      +      +
+  AP  + +  AP  +     +  AP  +      +  AP  +
+      + +      +     +      +      +      +
+......+ +......+     +......+      +......+
           .              .             .
         .  .              .             .
        .    .              .             .
       .      .              .             .
      .        .              .             .
   +......+ +......+     +......+      +......+
   +      + +      +     +      +      +      +
   +  MN  + +  MN  +     +  MN  +      +  MN  +
   +      + +      +     +      +      +      +
   +......+ +......+     +......+      +......+
        
        
The LWAPP tunnel exists between the controller and
the APs.  The MNs communicate with the APs through
the protocol defined by the 802.11 standard.
        
LWAPP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the LWAPP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside LWAPP frames and forward
the LWAPP frames to the controller.
        
                   GLOSSARY
        
Access Point ( AP )
        
An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.  
        
LWAPP APs encapsulate all the 802.11 frames in
LWAPP frames and sends them to the controller to which
it is logically connected.
        
Gratuitous Probe Response (GPR)
        
The Gratuitous Probe Response feature aids in conserving
battery power of WLAN-enabled cell phones by providing
a high rate packet on the order of tens of milliseconds
such that these kind of phones can wake up and wait at
predefined intervals, to reduce battery power.  The 
GPR packet is transmitted from the AP at a predefined
time interval.
        
        
Light Weight Access Point Protocol ( LWAPP )
        
This is a generic protocol that defines the 
communication between the Access Points and the
Central Controller. 
        
Mobile Node ( MN )
        
A roaming 802.11 wireless device in a wireless
network associated with an access point. Mobile Node 
and client are used interchangeably. 
        
Lightweight Directory Access Protocol ( LDAP )
        
LDAP is a protocol used for obtaining directory services 
and runs over TCP/IP.
        
Transport Layer Security ( TLS )
        
This is a cryptographic protocol which provides secure 
communication over the network.
        
REFERENCE
        
[1] Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications
        
[2] Draft-obara-capwap-lwapp-00.txt, IETF Light 
Weight Access Point Protocol
    
Source file
CISCO-LWAPP-DOT11-LDAP-MIB
Last revised
Identity
ciscoLwappDot11LdapMIB
Base OID
1.3.6.1.4.1.9.9.614
Imported Objects
CISCO-LWAPP-WLAN-MIB cLWlanIndex (no object page)
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType InetPortNumber
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString RowStatus StorageType TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-LWAPP-DOT11-LDAP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-DOT11-LDAP-MIB::ciscoLwappDot11LdapMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-DOT11-LDAP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-DOT11-LDAP-MIB::ciscoLwappDot11LdapMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (30)
.1.3.6.1.4.1.9.9.614
.1.3.6.1.4.1.9.9.614.0
.1.3.6.1.4.1.9.9.614.1
.1.3.6.1.4.1.9.9.614.1.1
.1.3.6.1.4.1.9.9.614.1.1.1
.1.3.6.1.4.1.9.9.614.1.1.1.1
Unsigned32
.1.3.6.1.4.1.9.9.614.1.1.1.1.1
.1.3.6.1.4.1.9.9.614.1.1.1.1.10
.1.3.6.1.4.1.9.9.614.1.1.1.1.11
.1.3.6.1.4.1.9.9.614.1.1.1.1.12
.1.3.6.1.4.1.9.9.614.1.1.1.1.13
.1.3.6.1.4.1.9.9.614.1.1.1.1.14
.1.3.6.1.4.1.9.9.614.1.1.1.1.15
.1.3.6.1.4.1.9.9.614.1.1.1.1.2
.1.3.6.1.4.1.9.9.614.1.1.1.1.3
.1.3.6.1.4.1.9.9.614.1.1.1.1.4
.1.3.6.1.4.1.9.9.614.1.1.1.1.5
secondsUnsigned32
.1.3.6.1.4.1.9.9.614.1.1.1.1.6
.1.3.6.1.4.1.9.9.614.1.1.1.1.7
.1.3.6.1.4.1.9.9.614.1.1.1.1.8
.1.3.6.1.4.1.9.9.614.1.1.1.1.9
.1.3.6.1.4.1.9.9.614.1.1.2
.1.3.6.1.4.1.9.9.614.1.1.2.1
Unsigned32
.1.3.6.1.4.1.9.9.614.1.1.2.1.1
Unsigned32
.1.3.6.1.4.1.9.9.614.1.1.2.1.2
Unsigned32
.1.3.6.1.4.1.9.9.614.1.1.2.1.3
.1.3.6.1.4.1.9.9.614.1.2
.1.3.6.1.4.1.9.9.614.2
.1.3.6.1.4.1.9.9.614.2.1
.1.3.6.1.4.1.9.9.614.2.2
Dependencies (8) 7 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (1)
Enumeration
anonymous(1)
authenticated(2)
Conformance Groups (2)
This collection of objects specifies the LDAP
configuration on the controller.
.1.3.6.1.4.1.9.9.614.2.2.1
This group of objects supplements the
ciscoLwappDot11LdapMIBConfigGroup,
to configure the information about the Controller's
authentication done with the LDAP server.
.1.3.6.1.4.1.9.9.614.2.2.2
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.614.2.1.1
The compliance statement for the SNMP entities that
implement the ciscoLwappDot11LdapMIB module.
Required groups

OID .1.3.6.1.4.1.9.9.614.2.1.2
The compliance statement for the SNMP entities that
implement the ciscoLwappDot11LdapMIB module.
Required groups