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
    
ciscoLwappDhcpMIB 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 OBJECT-GROUP
SNMPv2-SMI Counter32 IpAddress MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE Unsigned32
SNMPv2-TC TimeStamp TruthValue
Objects (52)
ciscoLwappDhcpMIB .1.3.6.1.4.1.9.9.792
ciscoLwappDhcpMIBNotif .1.3.6.1.4.1.9.9.792.0
ciscoLwappDhcpMIBObjects .1.3.6.1.4.1.9.9.792.1
ciscoLwappDhcpGlobalConfig .1.3.6.1.4.1.9.9.792.1.1
cLDhcpClearAllStats r/w SNMPv2-TCTruthValue .1.3.6.1.4.1.9.9.792.1.1.1
cLDhcpOpt82RemoteIdFormat r/w Enumeration .1.3.6.1.4.1.9.9.792.1.1.2
cLDhcpClearAllDiscontinuityTime SNMPv2-TCTimeStamp .1.3.6.1.4.1.9.9.792.1.1.3
cLDhcpTimeout r/w secondsUnsigned32 .1.3.6.1.4.1.9.9.792.1.1.4
cLDhcpOpt37RemoteIdFormat r/w Enumeration .1.3.6.1.4.1.9.9.792.1.1.5
ciscoLwappDhcpStatsConfig .1.3.6.1.4.1.9.9.792.1.2
cLDhcpStatsConfigTable .1.3.6.1.4.1.9.9.792.1.2.1
cLDhcpStatsConfigEntry cLDhcpServerInetAddressTypecLDhcpServerInetAddress .1.3.6.1.4.1.9.9.792.1.2.1.1
cLDhcpServerInetAddressType INET-ADDRESS-MIBInetAddressType .1.3.6.1.4.1.9.9.792.1.2.1.1.1
cLDhcpServerInetAddress INET-ADDRESS-MIBInetAddress .1.3.6.1.4.1.9.9.792.1.2.1.1.2
cLDhcpClearStats r/w SNMPv2-TCTruthValue .1.3.6.1.4.1.9.9.792.1.2.1.1.3
cLDhcpClearDiscontinuityTime SNMPv2-TCTimeStamp .1.3.6.1.4.1.9.9.792.1.2.1.1.4
ciscoLwappDhcpStats .1.3.6.1.4.1.9.9.792.1.3
cLDhcpStatsShowTable .1.3.6.1.4.1.9.9.792.1.3.1
cLDhcpStatsShowEntry cLDhcpServerInetAddressTypecLDhcpServerInetAddress .1.3.6.1.4.1.9.9.792.1.3.1.1
cLDhcpProxy r/w SNMPv2-TCTruthValue .1.3.6.1.4.1.9.9.792.1.3.1.1.1
cLDhcpNakPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.10
cLDhcpTxFailures SNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.11
cLDhcpLastResponseTime secondsSNMPv2-TCTimeStamp .1.3.6.1.4.1.9.9.792.1.3.1.1.12
cLDhcpLastRequestTime secondsSNMPv2-TCTimeStamp .1.3.6.1.4.1.9.9.792.1.3.1.1.13
cLDhcpRxDiscoverPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.14
cLDhcpDiscoverPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.2
cLDhcpRequestPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.3
cLDhcpDeclinePackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.4
cLDhcpInformPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.5
cLDhcpReleasePackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.6
cLDhcpReplyPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.7
cLDhcpOfferPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.8
cLDhcpAckPackets packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.3.1.1.9
ciscoLwappDhcpScopeStats .1.3.6.1.4.1.9.9.792.1.4
cLDhcpScopeStatsTable .1.3.6.1.4.1.9.9.792.1.4.1
cLDhcpScopeStatsEntry cLDhcpScopeIndex .1.3.6.1.4.1.9.9.792.1.4.1.1
cLDhcpScopeIndex Unsigned32 .1.3.6.1.4.1.9.9.792.1.4.1.1.1
cLDhcpScopeRequestPkts packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.10
cLDhcpScopeRequestGoodPkts packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.11
cLDhcpScopeAddressPoolUsage PercentUnsigned32 .1.3.6.1.4.1.9.9.792.1.4.1.1.2
cLDhcpScopeName SNMP-FRAMEWORK-MIBSnmpAdminString .1.3.6.1.4.1.9.9.792.1.4.1.1.3
cLDhcpScopeAllocatedIP SNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.4
cLDhcpScopeAvailableIP SNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.5
cLDhcpScopeDiscoverPkts packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.6
cLDhcpScopeAckPkts packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.7
cLDhcpScopeOfferPkts packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.8
cLDhcpScopeTotalAckPkts packetsSNMPv2-SMICounter32 .1.3.6.1.4.1.9.9.792.1.4.1.1.9
ciscoLwappDhcpMIBNotifObjects .1.3.6.1.4.1.9.9.792.1.5
cLDhcpTrapSet SNMPv2-TCTruthValue .1.3.6.1.4.1.9.9.792.1.5.1
ciscoLwappDhcpMIBConform .1.3.6.1.4.1.9.9.792.2
ciscoLwappDhcpMIBCompliances .1.3.6.1.4.1.9.9.792.2.1
ciscoLwappDhcpMIBGroups .1.3.6.1.4.1.9.9.792.2.2
Notifications / Traps (1)
NameOIDDescription
ciscoLwappDhcpScopeAddressExhaust .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.