CISCO-LWAPP-LINKTEST-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.
        
Link Test is performed to learn the radio link quality 
between AP and Client.  CCX linktest is performed for 
CCX clients.  With CCX linktest radio link can be 
measured in both direction i.e. AP->Client(downLink) 
and Client->AP(uplink).  When client does not support 
CCX or CCX linktest fails,ping is done between AP and 
Client.  In ping test, only uplink (client->AP) quality
can be measured.
        
The relationship between the controller and the LWAPP
APs is 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 forward all the 802.11 frames to them
encapsulated inside LWAPP frames.
        
                   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. Mobile Node 
and client are used interchangeably. 
        
Received Signal Strength Indicator ( RSSI )
        
A measure of the strength of the signal as 
observed by the entity that received it,
expressed in 'dbm'.
        
Signal-Noise Ratio ( SNR )
        
A measure of the quality of the signal relative
to the strength of noise expressed in 'dB'.
        
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-LINKTEST-MIB
Last revised
Identity
ciscoLwappLinkTestMIB
Base OID
1.3.6.1.4.1.9.9.516
Imported Objects
CISCO-SMI ciscoMgmt
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC MacAddress RowStatus TimeInterval 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-LINKTEST-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-LINKTEST-MIB::ciscoLwappLinkTestMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-LINKTEST-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-LINKTEST-MIB::ciscoLwappLinkTestMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (50)
.1.3.6.1.4.1.9.9.516
.1.3.6.1.4.1.9.9.516.0
.1.3.6.1.4.1.9.9.516.1
.1.3.6.1.4.1.9.9.516.1.1
.1.3.6.1.4.1.9.9.516.1.1.1
Unsigned32
.1.3.6.1.4.1.9.9.516.1.1.2
Unsigned32
.1.3.6.1.4.1.9.9.516.1.1.3
secondsUnsigned32
.1.3.6.1.4.1.9.9.516.1.1.4
.1.3.6.1.4.1.9.9.516.1.2
.1.3.6.1.4.1.9.9.516.1.2.1
.1.3.6.1.4.1.9.9.516.1.2.1.1
Unsigned32
.1.3.6.1.4.1.9.9.516.1.2.1.1.1
.1.3.6.1.4.1.9.9.516.1.2.1.1.2
.1.3.6.1.4.1.9.9.516.1.2.1.1.3
.1.3.6.1.4.1.9.9.516.1.2.2
.1.3.6.1.4.1.9.9.516.1.2.2.1
.1.3.6.1.4.1.9.9.516.1.2.2.1.1
.1.3.6.1.4.1.9.9.516.1.2.2.1.10
.1.3.6.1.4.1.9.9.516.1.2.2.1.11
.1.3.6.1.4.1.9.9.516.1.2.2.1.12
.1.3.6.1.4.1.9.9.516.1.2.2.1.13
.1.3.6.1.4.1.9.9.516.1.2.2.1.14
.1.3.6.1.4.1.9.9.516.1.2.2.1.15
.1.3.6.1.4.1.9.9.516.1.2.2.1.16
.1.3.6.1.4.1.9.9.516.1.2.2.1.17
.1.3.6.1.4.1.9.9.516.1.2.2.1.18
.1.3.6.1.4.1.9.9.516.1.2.2.1.19
.1.3.6.1.4.1.9.9.516.1.2.2.1.2
.1.3.6.1.4.1.9.9.516.1.2.2.1.20
.1.3.6.1.4.1.9.9.516.1.2.2.1.21
.1.3.6.1.4.1.9.9.516.1.2.2.1.22
.1.3.6.1.4.1.9.9.516.1.2.2.1.23
.1.3.6.1.4.1.9.9.516.1.2.2.1.24
Enumeration
.1.3.6.1.4.1.9.9.516.1.2.2.1.25
.1.3.6.1.4.1.9.9.516.1.2.2.1.3
.1.3.6.1.4.1.9.9.516.1.2.2.1.4
.1.3.6.1.4.1.9.9.516.1.2.2.1.5
hundredths-secondsSNMPv2-TCTimeInterval
.1.3.6.1.4.1.9.9.516.1.2.2.1.6
hundredths-secondsSNMPv2-TCTimeInterval
.1.3.6.1.4.1.9.9.516.1.2.2.1.7
hundredths-secondsSNMPv2-TCTimeInterval
.1.3.6.1.4.1.9.9.516.1.2.2.1.8
.1.3.6.1.4.1.9.9.516.1.2.2.1.9
.1.3.6.1.4.1.9.9.516.1.3
.1.3.6.1.4.1.9.9.516.1.3.1
.1.3.6.1.4.1.9.9.516.1.3.1.1
OctetString
.1.3.6.1.4.1.9.9.516.1.3.1.1.1
.1.3.6.1.4.1.9.9.516.1.3.1.1.2
.1.3.6.1.4.1.9.9.516.1.3.1.1.3
.1.3.6.1.4.1.9.9.516.2
.1.3.6.1.4.1.9.9.516.2.1
.1.3.6.1.4.1.9.9.516.2.2
Dependencies (4) 4 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-CONFrfc
  4. SNMPv2-TCrfc
  5. CISCO-LWAPP-LINKTEST-MIBciscoselected
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.516.2.1.1
The compliance statement for the SNMP entities that
implement the ciscoLwappLinkTestMIB module.
Required groups