CISCO-LWAPP-CCX-RM-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 for CCX related 
features as specified in the CCX specifications. 
        
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'.
        
Cisco Compatible eXtensions (CCX)
        
Wireless LAN Access Points (APs) manufactured by Cisco
Systems have features and capabilities beyond those in
related standards (e.g., IEEE 802.11 suite of 
standards, Wi-Fi recommendations by WECA, 802.1X 
security suite, etc). A number of features provide 
higher performance. For example, Cisco AP transmits a 
specific Information Element, which the clients adapt 
to for enhanced performance. Similarly, a number of 
features are implemented by means of proprietary 
Information Elements, which Cisco clients use in 
specific ways to carry out tasks above and beyond the
standard. Other examples of feature categories are 
roaming and power saving.
        
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.  The terms  
'Mobile node' and 'client' are used interchangeably. 
        
Radio Management (RM)
        
This term refers to managing the 802.11 radio
environment to provide the best quality service to
to the 802.11 wireless clients. 
        
Service Set Identifier ( SSID ) 
        
SSID is a unique identifier that APs and clients
use to identify with each other.  SSID is a simple
means of access control and is not for security.
The SSID can be any alphanumeric entry up to 32
characters.
        
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-CCX-RM-MIB
Last revised
Identity
ciscoLwappCcxRmMIB
Base OID
1.3.6.1.4.1.9.9.520
Imported Objects
CISCO-LWAPP-AP-MIB cLApDot11IfSlotId cLApSysMacAddress
CISCO-LWAPP-WLAN-MIB cLWlanIndex (no object page)
CISCO-SMI ciscoMgmt
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC MacAddress TimeInterval 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-CCX-RM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-CCX-RM-MIB::ciscoLwappCcxRmMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-CCX-RM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-CCX-RM-MIB::ciscoLwappCcxRmMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (32)
.1.3.6.1.4.1.9.9.520
.1.3.6.1.4.1.9.9.520.0
.1.3.6.1.4.1.9.9.520.1
.1.3.6.1.4.1.9.9.520.1.1
.1.3.6.1.4.1.9.9.520.1.1.1
clcrdot11aBeaconInterval deprecated r/w
hundredths-secondsInteger32
.1.3.6.1.4.1.9.9.520.1.1.2
hundredths-secondsSNMPv2-TCTimeInterval
.1.3.6.1.4.1.9.9.520.1.1.3
.1.3.6.1.4.1.9.9.520.1.2
.1.3.6.1.4.1.9.9.520.1.2.1
clcrdot11bBeaconInterval deprecated r/w
hundredths-secondsInteger32
.1.3.6.1.4.1.9.9.520.1.2.2
hundredths-secondsSNMPv2-TCTimeInterval
.1.3.6.1.4.1.9.9.520.1.2.3
.1.3.6.1.4.1.9.9.520.1.3
.1.3.6.1.4.1.9.9.520.1.3.1
.1.3.6.1.4.1.9.9.520.1.3.1.1
.1.3.6.1.4.1.9.9.520.1.3.1.1.1
.1.3.6.1.4.1.9.9.520.1.3.1.1.2
clcrAPIfBeaconInterval deprecated r/w
hundredths-secondsInteger32
.1.3.6.1.4.1.9.9.520.1.3.1.1.3
hundredths-secondsSNMPv2-TCTimeInterval
.1.3.6.1.4.1.9.9.520.1.3.1.1.4
.1.3.6.1.4.1.9.9.520.1.4
.1.3.6.1.4.1.9.9.520.1.4.1
.1.3.6.1.4.1.9.9.520.1.4.1.1
.1.3.6.1.4.1.9.9.520.1.4.1.1.1
dBmInteger32
.1.3.6.1.4.1.9.9.520.1.4.1.1.2
.1.3.6.1.4.1.9.9.520.1.4.1.1.3
.1.3.6.1.4.1.9.9.520.1.5
.1.3.6.1.4.1.9.9.520.1.5.1
.1.3.6.1.4.1.9.9.520.1.5.1.1
.1.3.6.1.4.1.9.9.520.1.5.1.1.1
.1.3.6.1.4.1.9.9.520.1.5.1.1.2
.1.3.6.1.4.1.9.9.520.2
.1.3.6.1.4.1.9.9.520.2.1
.1.3.6.1.4.1.9.9.520.2.2
Dependencies (16) 6 direct · 10 transitive 1 circular 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.

Circular imports detected
CISCO-LWAPP-AP-MIB → CISCO-LWAPP-DOT11-MIB → CISCO-LWAPP-AP-MIB
Dependency tree
Conformance Groups (8)
This collection of objects represent the beacon
request and beacon interval parameters for 802.11a
networks.
ciscoLwappCcxRmDot11aConfigGroup object is superseded by
ciscoLwappCcxRmDot11aConfigGroupVer1.
.1.3.6.1.4.1.9.9.520.2.2.1
This collection of objects represent the beacon
request and beacon interval parameters for 802.11a
networks.
ciscoLwappCcxRmDot11bConfigGroup object is superseded by
ciscoLwappCcxRmDot11bConfigGroupVer1.
.1.3.6.1.4.1.9.9.520.2.2.2
This collection of objects represent the beacon
request and beacon interval parameters for the
respective 802.11 radio interfaces.
ciscoLwappCcxRmApIfConfigGroup object is superseded by
ciscoLwappCcxRmApIfConfigGroupVer1.
.1.3.6.1.4.1.9.9.520.2.2.3
This collection of objects represent information
about the beacon reports received from CCX
clients.
.1.3.6.1.4.1.9.9.520.2.2.4
This collection of objects represent the CCX
settings on a particular WLAN.
.1.3.6.1.4.1.9.9.520.2.2.5
This collection of objects represent the beacon
request and beacon interval parameters for 802.11a
networks.
.1.3.6.1.4.1.9.9.520.2.2.6
This collection of objects represent the beacon
request and beacon interval parameters for 802.11b
networks.
.1.3.6.1.4.1.9.9.520.2.2.7
This collection of objects represent the beacon
request and beacon interval parameters for the
respective 802.11 radio interfaces.
.1.3.6.1.4.1.9.9.520.2.2.8
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.520.2.1.1
The compliance statement for the SNMP entities that
implement the ciscoLwappCcxRmMIB module.
Required groups

OID .1.3.6.1.4.1.9.9.520.2.1.2
The compliance statement for the SNMP entities that
implement the ciscoLwappCcxRmMIB module.
Required groups