CISCO-LWAPP-CLIENT-ROAMING-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.  
This MIB covers roaming RF parameters for CCX 
clients.
        
The relationship between CC and the LWAPP APs
can be depicted as follows:
        
      +......+     +......+     +......+
      +      +     +      +     +      +
      +  CC  +     +  CC  +     +  CC  +
      +      +     +      +     +      +
      +......+     +......+     +......+
        ..            .             .
        ..            .             .
       .  .            .             .
      .    .            .             .
     .      .            .             .
    .        .            .             .
+......+ +......+     +......+      +......+
+      + +      +     +      +      +      +
+  AP  + +  AP  +     +  AP  +      +  AP  +
+      + +      +     +      +      +      +
+......+ +......+     +......+      +......+
           .              .             .
         .  .              .             .
        .    .              .             .
       .      .              .             .
      .        .              .             .
   +......+ +......+     +......+      +......+
   +      + +      +     +      +      +      +
   +  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.
        
Basic Service Set ( BSS )
        
The IEEE 802.11 BSS of an AP comprises of the
stations directly associating with the AP.
        
Central Controller ( CC )
        
The central entity that terminates the LWAPP protocol
tunnel from the LWAPP APs.  Throughout this MIB,
this entity is 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.
        
Client Roaming
        
A client may decide to reassociate with another AP for
reasons of its own choosing. The decision of whether
or not to use the information contained in the AP list
is up to the discretion of the implementor, as long as 
the roam time requirement is met.
        
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. 
        
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-CLIENT-ROAMING-MIB
Last revised
Identity
ciscoLwappClRoamMIB
Base OID
1.3.6.1.4.1.9.9.523
Imported Objects
CISCO-LWAPP-AP-MIB cLApDot11IfSlotId cLApSysMacAddress
CISCO-LWAPP-TC-MIB CLDot11Channel CLDot11RfParamMode
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) TimeTicks
SNMPv2-TC MacAddress TimeInterval
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-CLIENT-ROAMING-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-CLIENT-ROAMING-MIB::ciscoLwappClRoamMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-CLIENT-ROAMING-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-CLIENT-ROAMING-MIB::ciscoLwappClRoamMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (46)
.1.3.6.1.4.1.9.9.523
.1.3.6.1.4.1.9.9.523.0
.1.3.6.1.4.1.9.9.523.1
.1.3.6.1.4.1.9.9.523.1.1
.1.3.6.1.4.1.9.9.523.1.1.1
clcrDot11aMinRssi deprecated r/w
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.1.2
clcrDot11aHysteresis deprecated r/w
dBInteger32
.1.3.6.1.4.1.9.9.523.1.1.3
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.1.4
clcrDot11aTransitionTime deprecated r/w
Integer32
.1.3.6.1.4.1.9.9.523.1.1.5
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.1.6
dBInteger32
.1.3.6.1.4.1.9.9.523.1.1.7
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.1.8
Integer32
.1.3.6.1.4.1.9.9.523.1.1.9
.1.3.6.1.4.1.9.9.523.1.2
.1.3.6.1.4.1.9.9.523.1.2.1
clcrDot11bMinRssi deprecated r/w
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.2.2
clcrDot11bHysteresis deprecated r/w
dBInteger32
.1.3.6.1.4.1.9.9.523.1.2.3
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.2.4
clcrDot11bTransitionTime deprecated r/w
Integer32
.1.3.6.1.4.1.9.9.523.1.2.5
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.2.6
dBInteger32
.1.3.6.1.4.1.9.9.523.1.2.7
dBmInteger32
.1.3.6.1.4.1.9.9.523.1.2.8
Integer32
.1.3.6.1.4.1.9.9.523.1.2.9
.1.3.6.1.4.1.9.9.523.1.3
.1.3.6.1.4.1.9.9.523.1.3.1
.1.3.6.1.4.1.9.9.523.1.3.1.1
.1.3.6.1.4.1.9.9.523.1.3.1.1.1
.1.3.6.1.4.1.9.9.523.1.3.1.1.2
.1.3.6.1.4.1.9.9.523.1.3.1.1.3
.1.3.6.1.4.1.9.9.523.1.3.1.1.4
.1.3.6.1.4.1.9.9.523.1.3.1.1.5
OctetString
.1.3.6.1.4.1.9.9.523.1.3.1.1.6
.1.3.6.1.4.1.9.9.523.1.3.1.1.7
Enumeration
.1.3.6.1.4.1.9.9.523.1.3.1.1.8
.1.3.6.1.4.1.9.9.523.1.4
.1.3.6.1.4.1.9.9.523.1.4.1
.1.3.6.1.4.1.9.9.523.1.4.1.1
.1.3.6.1.4.1.9.9.523.1.4.1.1.1
.1.3.6.1.4.1.9.9.523.1.4.1.1.2
.1.3.6.1.4.1.9.9.523.1.4.1.1.3
.1.3.6.1.4.1.9.9.523.1.4.1.1.4
.1.3.6.1.4.1.9.9.523.1.5
.1.3.6.1.4.1.9.9.523.1.5.1
.1.3.6.1.4.1.9.9.523.2
.1.3.6.1.4.1.9.9.523.2.1
.1.3.6.1.4.1.9.9.523.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 (6)
This collection of objects represent the radio
parameters for the 802.11a networks.
ciscoLwappClRoamDot11aRfParamsGroup object is superseded by ciscoLwappClRoamDot11aRfParamsGroupSup1.
.1.3.6.1.4.1.9.9.523.2.2.1
This collection of objects represent the radio
parameters for the 802.11b/g bands.
ciscoLwappClRoamDot11bRfParamsGroup object is superseded by ciscoLwappClRoamDot11bRfParamsGroupSup1.
.1.3.6.1.4.1.9.9.523.2.2.2
This collection of objects provide the reasons for
clients roaming between APs.
.1.3.6.1.4.1.9.9.523.2.2.3
This collection of objects provide the counters
related to roaming.
.1.3.6.1.4.1.9.9.523.2.2.4
This collection of objects represent the radio
parameters for the 802.11a networks.
.1.3.6.1.4.1.9.9.523.2.2.5
This collection of objects represent the radio
parameters for the 802.11b/g bands.
.1.3.6.1.4.1.9.9.523.2.2.6
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.523.2.1.1
The compliance statement for the SNMP entities that
implement the ciscoLwappRoamMIB module.
Required groups

OID .1.3.6.1.4.1.9.9.523.2.1.2
The compliance statement for the SNMP entities that
implement the ciscoLwappRoamMIB module.
Required groups