CISCO-LWAPP-HA-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.
        
This MIB is used to show and configure High 
availability (HA) related statistics.
        
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.
        
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.
    
Source file
CISCO-LWAPP-HA-MIB
Last revised
Identity
ciscoLwappHaMIB
Base OID
1.3.6.1.4.1.9.9.843
Imported Objects
CISCO-RF-MIB cRFStatusPeerUnitState cRFStatusUnitState
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
RFC1213-MIB sysName
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString MacAddress 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-HA-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-HA-MIB::ciscoLwappHaMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-HA-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-HA-MIB::ciscoLwappHaMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (92)
.1.3.6.1.4.1.9.9.843
.1.3.6.1.4.1.9.9.843.0
.1.3.6.1.4.1.9.9.843.1
.1.3.6.1.4.1.9.9.843.1.1
.1.3.6.1.4.1.9.9.843.1.1.1
.1.3.6.1.4.1.9.9.843.1.1.10
.1.3.6.1.4.1.9.9.843.1.1.11
.1.3.6.1.4.1.9.9.843.1.1.12
.1.3.6.1.4.1.9.9.843.1.1.13
.1.3.6.1.4.1.9.9.843.1.1.14
.1.3.6.1.4.1.9.9.843.1.1.15
.1.3.6.1.4.1.9.9.843.1.1.16
Unsigned32
.1.3.6.1.4.1.9.9.843.1.1.17
Unsigned32
.1.3.6.1.4.1.9.9.843.1.1.18
secondsUnsigned32
.1.3.6.1.4.1.9.9.843.1.1.19
.1.3.6.1.4.1.9.9.843.1.1.2
.1.3.6.1.4.1.9.9.843.1.1.20
.1.3.6.1.4.1.9.9.843.1.1.3
.1.3.6.1.4.1.9.9.843.1.1.4
.1.3.6.1.4.1.9.9.843.1.1.5
.1.3.6.1.4.1.9.9.843.1.1.6
.1.3.6.1.4.1.9.9.843.1.1.7
.1.3.6.1.4.1.9.9.843.1.1.8
.1.3.6.1.4.1.9.9.843.1.1.9
.1.3.6.1.4.1.9.9.843.1.2
.1.3.6.1.4.1.9.9.843.1.2.1
.1.3.6.1.4.1.9.9.843.1.2.1.1
.1.3.6.1.4.1.9.9.843.1.2.1.1.1
.1.3.6.1.4.1.9.9.843.1.2.1.1.2
.1.3.6.1.4.1.9.9.843.1.2.1.1.3
.1.3.6.1.4.1.9.9.843.1.2.1.1.4
.1.3.6.1.4.1.9.9.843.1.2.1.1.5
.1.3.6.1.4.1.9.9.843.1.2.1.1.6
Enumeration
.1.3.6.1.4.1.9.9.843.1.2.1.1.7
.1.3.6.1.4.1.9.9.843.1.2.1.1.8
.1.3.6.1.4.1.9.9.843.1.3
Enumeration
.1.3.6.1.4.1.9.9.843.1.3.1
.1.3.6.1.4.1.9.9.843.1.3.2
Enumeration
.1.3.6.1.4.1.9.9.843.1.3.3
Enumeration
.1.3.6.1.4.1.9.9.843.1.3.4
.1.3.6.1.4.1.9.9.843.1.4
.1.3.6.1.4.1.9.9.843.1.4.1
.1.3.6.1.4.1.9.9.843.1.4.1.1
.1.3.6.1.4.1.9.9.843.1.4.1.1.1
.1.3.6.1.4.1.9.9.843.1.4.1.2
.1.3.6.1.4.1.9.9.843.1.4.1.2.1
.1.3.6.1.4.1.9.9.843.1.4.1.2.2
.1.3.6.1.4.1.9.9.843.1.4.1.2.3
.1.3.6.1.4.1.9.9.843.1.4.1.2.4
.1.3.6.1.4.1.9.9.843.1.4.1.3
.1.3.6.1.4.1.9.9.843.1.4.1.3.1
.1.3.6.1.4.1.9.9.843.1.4.1.3.10
.1.3.6.1.4.1.9.9.843.1.4.1.3.11
.1.3.6.1.4.1.9.9.843.1.4.1.3.12
.1.3.6.1.4.1.9.9.843.1.4.1.3.13
.1.3.6.1.4.1.9.9.843.1.4.1.3.2
.1.3.6.1.4.1.9.9.843.1.4.1.3.3
.1.3.6.1.4.1.9.9.843.1.4.1.3.4
.1.3.6.1.4.1.9.9.843.1.4.1.3.5
.1.3.6.1.4.1.9.9.843.1.4.1.3.6
.1.3.6.1.4.1.9.9.843.1.4.1.3.7
.1.3.6.1.4.1.9.9.843.1.4.1.3.8
.1.3.6.1.4.1.9.9.843.1.4.1.3.9
.1.3.6.1.4.1.9.9.843.1.5
.1.3.6.1.4.1.9.9.843.1.5.1
.1.3.6.1.4.1.9.9.843.1.5.2
.1.3.6.1.4.1.9.9.843.1.5.3
.1.3.6.1.4.1.9.9.843.1.6
.1.3.6.1.4.1.9.9.843.1.6.1
Unsigned32
.1.3.6.1.4.1.9.9.843.1.6.10
.1.3.6.1.4.1.9.9.843.1.6.2
.1.3.6.1.4.1.9.9.843.1.6.3
.1.3.6.1.4.1.9.9.843.1.6.4
.1.3.6.1.4.1.9.9.843.1.6.5
.1.3.6.1.4.1.9.9.843.1.6.6
Unsigned32
.1.3.6.1.4.1.9.9.843.1.6.7
Unsigned32
.1.3.6.1.4.1.9.9.843.1.6.8
.1.3.6.1.4.1.9.9.843.1.6.9
.1.3.6.1.4.1.9.9.843.1.7
Unsigned32
.1.3.6.1.4.1.9.9.843.1.7.1
Unsigned32
.1.3.6.1.4.1.9.9.843.1.7.10
.1.3.6.1.4.1.9.9.843.1.7.2
Unsigned32
.1.3.6.1.4.1.9.9.843.1.7.3
.1.3.6.1.4.1.9.9.843.1.7.4
.1.3.6.1.4.1.9.9.843.1.7.5
Unsigned32
.1.3.6.1.4.1.9.9.843.1.7.6
.1.3.6.1.4.1.9.9.843.1.7.7
.1.3.6.1.4.1.9.9.843.1.7.8
.1.3.6.1.4.1.9.9.843.1.7.9
.1.3.6.1.4.1.9.9.843.2
.1.3.6.1.4.1.9.9.843.2.1
.1.3.6.1.4.1.9.9.843.2.2
Dependencies (12) 8 direct · 4 transitive 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
Conformance Groups (7)
This collection of objects represents the information
about global config of the high availability objects on
the controller.
.1.3.6.1.4.1.9.9.843.2.2.1
This collection of objects represents the information
about network config of the high availability objects on
the controller.
.1.3.6.1.4.1.9.9.843.2.2.2
This collection of objects represents the information
about the Statistics of high availability objects on the
controller.
.1.3.6.1.4.1.9.9.843.2.2.3
This collection of objects represents the information
about the Notification of high availability objects on
the controller.
.1.3.6.1.4.1.9.9.843.2.2.4
This supplemental collection of objects represents the
HA related notifications sent by the agent to a network
management station.
.1.3.6.1.4.1.9.9.843.2.2.5
This collection of objects represents the information
about network config of the multi chassis high availability
RMI objects on the controller.
.1.3.6.1.4.1.9.9.843.2.2.6
This collection of objects represents the
information about network config of the multi
chassis RMI objects on the controller.
.1.3.6.1.4.1.9.9.843.2.2.7
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.843.2.1.1
This is a default module-compliance
containing default object groups.
Required groups

OID .1.3.6.1.4.1.9.9.843.2.1.2
This is a default module-compliance
containing default object groups.
Required groups
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.9.9.843.0.1
This notification is sent on the event of a generic failure
between the active and peer unit.
.1.3.6.1.4.1.9.9.843.0.2
The notification is sent by the active redundant
unit whenever its RF state changes or the RF state of the peer
unit changes.

To avoid a flurry of notifications for all state transitions,
notifications will only be sent for transitions to the
following RF states:
disabled (for the peer state)
standbyCold
standbyHot
active
activeExtraload.
.1.3.6.1.4.1.9.9.843.0.3
The notification is sent by the active redundant
unit whenever the BulkSync to peer is complete.
.1.3.6.1.4.1.9.9.843.0.4
The notification is sent by the active redundant
unit whenever its peer unit turned hot-standby.