CISCO-LWAPP-DHCP-MIB

        This MIB is used to manage Dynamic Host Configuration
Protocol (DHCP) related information on the devices 
operating as Central controllers, that terminate the 
Light Weight Access Point Protocol tunnel from Cisco 
Light-weight LWAPP Access Points.
        
The relationship between CC and the LWAPP APs
can be depicted as follows:
        
+......+     +......+     +......+           +......+
+      +     +      +     +      +           +      +
+  CC  +     +  CC  +     +  CC  +           +  CC  +
+      +     +      +     +      +           +      +
+......+     +......+     +......+           +......+
..            .             .                 .
..            .             .                 .
.  .            .             .                 .
.    .            .             .                 .
.      .            .             .                 .
.        .            .             .                 .
+......+ +......+     +......+      +......+          +......+
+      + +      +     +      +      +      +          +      +
+  AP  + +  AP  +     +  AP  +      +  AP  +          +  AP  +
+      + +      +     +      +      +      +          +      +
+......+ +......+     +......+      +......+          +......+
.              .             .                 .
.  .              .             .                 .
.    .              .             .                 .
.      .              .             .                 .
.        .              .             .                 .
+......+ +......+     +......+      +......+          +......+
+      + +      +     +      +      +      +          +      +
+  MN  + +  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.
        
Central Controller ( CC )
        
The central entity that terminates the LWAPP protocol
tunnel from the LWAPP APs.  Throughout this MIB,
this entity also referred to as 'controller'. 
        
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,
Mobile Station(MS) and client are used interchangeably. 
        
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-DHCP-MIB
Last revised
Identity
ciscoLwappDhcpMIB
Base OID
1.3.6.1.4.1.9.9.792
Imported Objects
CISCO-SMI ciscoMgmt
CISCO-TC CiscoURLString
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC TimeStamp 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-DHCP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-DHCP-MIB::ciscoLwappDhcpMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-DHCP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-DHCP-MIB::ciscoLwappDhcpMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (52)
.1.3.6.1.4.1.9.9.792
.1.3.6.1.4.1.9.9.792.0
.1.3.6.1.4.1.9.9.792.1
.1.3.6.1.4.1.9.9.792.1.1
.1.3.6.1.4.1.9.9.792.1.1.1
Enumeration
.1.3.6.1.4.1.9.9.792.1.1.2
.1.3.6.1.4.1.9.9.792.1.1.3
.1.3.6.1.4.1.9.9.792.1.1.4
Enumeration
.1.3.6.1.4.1.9.9.792.1.1.5
.1.3.6.1.4.1.9.9.792.1.2
.1.3.6.1.4.1.9.9.792.1.2.1
.1.3.6.1.4.1.9.9.792.1.2.1.1
.1.3.6.1.4.1.9.9.792.1.2.1.1.1
.1.3.6.1.4.1.9.9.792.1.2.1.1.2
.1.3.6.1.4.1.9.9.792.1.2.1.1.3
.1.3.6.1.4.1.9.9.792.1.2.1.1.4
.1.3.6.1.4.1.9.9.792.1.3
.1.3.6.1.4.1.9.9.792.1.3.1
.1.3.6.1.4.1.9.9.792.1.3.1.1
.1.3.6.1.4.1.9.9.792.1.3.1.1.1
.1.3.6.1.4.1.9.9.792.1.3.1.1.10
.1.3.6.1.4.1.9.9.792.1.3.1.1.11
.1.3.6.1.4.1.9.9.792.1.3.1.1.12
.1.3.6.1.4.1.9.9.792.1.3.1.1.13
.1.3.6.1.4.1.9.9.792.1.3.1.1.14
.1.3.6.1.4.1.9.9.792.1.3.1.1.2
.1.3.6.1.4.1.9.9.792.1.3.1.1.3
.1.3.6.1.4.1.9.9.792.1.3.1.1.4
.1.3.6.1.4.1.9.9.792.1.3.1.1.5
.1.3.6.1.4.1.9.9.792.1.3.1.1.6
.1.3.6.1.4.1.9.9.792.1.3.1.1.7
.1.3.6.1.4.1.9.9.792.1.3.1.1.8
.1.3.6.1.4.1.9.9.792.1.3.1.1.9
.1.3.6.1.4.1.9.9.792.1.4
.1.3.6.1.4.1.9.9.792.1.4.1
.1.3.6.1.4.1.9.9.792.1.4.1.1
.1.3.6.1.4.1.9.9.792.1.4.1.1.1
.1.3.6.1.4.1.9.9.792.1.4.1.1.10
.1.3.6.1.4.1.9.9.792.1.4.1.1.11
.1.3.6.1.4.1.9.9.792.1.4.1.1.2
.1.3.6.1.4.1.9.9.792.1.4.1.1.3
.1.3.6.1.4.1.9.9.792.1.4.1.1.4
.1.3.6.1.4.1.9.9.792.1.4.1.1.5
.1.3.6.1.4.1.9.9.792.1.4.1.1.6
.1.3.6.1.4.1.9.9.792.1.4.1.1.7
.1.3.6.1.4.1.9.9.792.1.4.1.1.8
.1.3.6.1.4.1.9.9.792.1.4.1.1.9
.1.3.6.1.4.1.9.9.792.1.5
.1.3.6.1.4.1.9.9.792.1.5.1
.1.3.6.1.4.1.9.9.792.2
.1.3.6.1.4.1.9.9.792.2.1
.1.3.6.1.4.1.9.9.792.2.2
Dependencies (7) 7 direct 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
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. CISCO-TCcisco
  5. INET-ADDRESS-MIBrfc
  6. SNMPv2-CONFrfc
  7. SNMP-FRAMEWORK-MIBrfc
  8. CISCO-LWAPP-DHCP-MIBciscoselected
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.792.2.1.1
The compliance statement for the SNMP entities that
implement the ciscoLwappDhcpMIB module.
Required groups
Object refinements
ObjectAccessSyntaxDescription
cLDhcpClearAllStats readonly
Create/delete/modify access is not required.
cLDhcpOpt82RemoteIdFormat readonly
Create/delete/modify access is not required.
cLDhcpClearStats readonly
Create/delete/modify access is not required.
cLDhcpProxy readonly
Create/delete/modify access is not required.
cLDhcpOpt37RemoteIdFormat readonly
Create/delete/modify access is not required.
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.792.0.1
This notification will be sent whenever the DHCP Scope
has no IP address available, with cLDhcpTrapSet set to
true. When the clients released an IP address lately, this
notification is sent with cLDhcpTrapSet set to false.