CISCO-LWAPP-INTERFACE-MIB

        This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC)  that
terminate the Light Weight Access Point Protocol
tunnel from Cisco Light-weight LWAPP Access Points.
        
This MIB helps to manage the WLANs on the controller.
        
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 it to the controller to which
it is logically connected to.
        
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
controllers.
        
Mobile Node ( MN )
        
A roaming 802.11 wireless device in a wireless
network associated with an access point. 
        
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-INTERFACE-MIB
Last revised
Identity
ciscoLwappInterfaceMIB
Base OID
1.3.6.1.4.1.9.9.686
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus 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-INTERFACE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-INTERFACE-MIB::ciscoLwappInterfaceMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-INTERFACE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-INTERFACE-MIB::ciscoLwappInterfaceMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (51)
.1.3.6.1.4.1.9.9.686
.1.3.6.1.4.1.9.9.686.0
.1.3.6.1.4.1.9.9.686.1
.1.3.6.1.4.1.9.9.686.1.1
.1.3.6.1.4.1.9.9.686.1.1.1
.1.3.6.1.4.1.9.9.686.1.1.1.1
OctetString
.1.3.6.1.4.1.9.9.686.1.1.1.1.1
.1.3.6.1.4.1.9.9.686.1.1.1.1.10
Unsigned32
.1.3.6.1.4.1.9.9.686.1.1.1.1.11
.1.3.6.1.4.1.9.9.686.1.1.1.1.12
.1.3.6.1.4.1.9.9.686.1.1.1.1.13
OctetString
.1.3.6.1.4.1.9.9.686.1.1.1.1.14
.1.3.6.1.4.1.9.9.686.1.1.1.1.15
.1.3.6.1.4.1.9.9.686.1.1.1.1.16
.1.3.6.1.4.1.9.9.686.1.1.1.1.17
.1.3.6.1.4.1.9.9.686.1.1.1.1.18
.1.3.6.1.4.1.9.9.686.1.1.1.1.19
.1.3.6.1.4.1.9.9.686.1.1.1.1.2
.1.3.6.1.4.1.9.9.686.1.1.1.1.20
.1.3.6.1.4.1.9.9.686.1.1.1.1.21
.1.3.6.1.4.1.9.9.686.1.1.1.1.22
Enumeration
.1.3.6.1.4.1.9.9.686.1.1.1.1.23
Enumeration
.1.3.6.1.4.1.9.9.686.1.1.1.1.24
.1.3.6.1.4.1.9.9.686.1.1.1.1.3
.1.3.6.1.4.1.9.9.686.1.1.1.1.4
Enumeration
.1.3.6.1.4.1.9.9.686.1.1.1.1.5
.1.3.6.1.4.1.9.9.686.1.1.1.1.6
OctetString
.1.3.6.1.4.1.9.9.686.1.1.1.1.7
.1.3.6.1.4.1.9.9.686.1.1.1.1.8
.1.3.6.1.4.1.9.9.686.1.1.1.1.9
.1.3.6.1.4.1.9.9.686.1.1.2
.1.3.6.1.4.1.9.9.686.1.1.2.1
.1.3.6.1.4.1.9.9.686.1.1.2.1.1
.1.3.6.1.4.1.9.9.686.1.1.2.1.2
.1.3.6.1.4.1.9.9.686.1.1.2.1.3
.1.3.6.1.4.1.9.9.686.1.1.2.1.4
.1.3.6.1.4.1.9.9.686.1.1.2.1.5
Enumeration
.1.3.6.1.4.1.9.9.686.1.1.2.1.6
.1.3.6.1.4.1.9.9.686.1.1.3
.1.3.6.1.4.1.9.9.686.1.1.3.1
.1.3.6.1.4.1.9.9.686.1.1.3.1.1
.1.3.6.1.4.1.9.9.686.1.2
.1.3.6.1.4.1.9.9.686.1.2.1
.1.3.6.1.4.1.9.9.686.1.2.1.1
.1.3.6.1.4.1.9.9.686.1.2.1.1.1
.1.3.6.1.4.1.9.9.686.1.2.1.1.2
.1.3.6.1.4.1.9.9.686.1.2.1.1.3
.1.3.6.1.4.1.9.9.686.1.2.1.1.4
.1.3.6.1.4.1.9.9.686.2
.1.3.6.1.4.1.9.9.686.2.1
.1.3.6.1.4.1.9.9.686.2.2
Dependencies (6) 6 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. INET-ADDRESS-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMP-FRAMEWORK-MIBrfc
  7. CISCO-LWAPP-INTERFACE-MIBciscoselected
Conformance Groups (6)
This collection of objects represent the
configuration of interfaces on the controller.
ciscoLwappInterfaceConfigGroup object is superseded
by ciscoLwappInterfaceConfigGroupRev01.
.1.3.6.1.4.1.9.9.686.2.2.1
This collection of objects represent the
configuration of interface groups on the controller.
ciscoLwappInterfaceGroupConfigSup1 object is superseded
by ciscoLwappInterfaceGroupConfigSup1Rev01.
.1.3.6.1.4.1.9.9.686.2.2.2
This collection of objects represent the
configuration of interfaces on the controller.
.1.3.6.1.4.1.9.9.686.2.2.3
This collection of objects represent the
configuration of interface groups on the controller.
.1.3.6.1.4.1.9.9.686.2.2.4
This collection of objects represent the
configuration of interface info on the controller.
.1.3.6.1.4.1.9.9.686.2.2.5
This supplemental collection of objects represents the
Interface related notifications sent by the agent to a network
management station.
.1.3.6.1.4.1.9.9.686.2.2.6
Compliance Statements (3)

OID .1.3.6.1.4.1.9.9.686.2.1.1
The compliance statement for the SNMP entities that
implement the ciscoLwappInterfaceMIB module.
Required groups

OID .1.3.6.1.4.1.9.9.686.2.1.2
The compliance statement for the SNMP entities that
implement the ciscoLwappInterfaceMIB module.
Required groups

OID .1.3.6.1.4.1.9.9.686.2.1.3
The compliance statement for the SNMP entities that
implement the ciscoLwappInterfaceMIB module.
Required groups
Object refinements
ObjectAccessSyntaxDescription
clInterfaceWired readonly
Write access is not required.
clInterfaceQuarantineVlanId readonly
Write access is not required.
clInterfaceDhcpOpt82Enabled readonly
Write access is not required.
clInterfaceGroupDescr readonly
Write access is not required.
clInterfaceGroupRowStatus readonly
Write access is not required.
clInterfaceGroupMappingRowStatus readonly
Write access is not required.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.9.686.0.1
This notification is generated after the address of
an interface is changed.
.1.3.6.1.4.1.9.9.686.0.2
This notification is generated after the Ipv6
address is changed