CISCO-LWAPP-PMIP-MIB

        This MIB is intended to be implemented on all those devices
operating as Wireless LAN Controllers (WLC) that terminate the 
Light Weight Access Point Protocol tunnel from light weight 
LWAPP Access Points.
        
This MIB provides configuration and status information about 
local mobility anchor to which the controller has joined.
        
The relationship between CC and the LWAPP APs can be depicted 
as follows:
        
+......+     +......+     +......+           +......+
+      +     +      +     +      +           +      +
+  LMA +     + LMA  +     + LMA  +           + LMA  +
+      +     +      +     +      +           +      +
+......+     +......+     +......+           +......+
..            .             .                 .
..            .             .                 .
.  .            .             .                 .
.    .            .             .                 .
.      .            .             .                 .
.        .            .             .                 .
+......+ +......+     +......+      +......+          +......+
+      + +      +     +      +      +      +          +      +
+  WLC + +  WLC +     + WLC  +      +  WLC +          +  WLC +
+      + +      +     +      +      +      +          +      +
+......+ +......+     +......+      +......+          +......+
.              .             .                 .
.  .              .             .                 .
.    .              .             .                 .
.      .              .             .                 .
.        .              .             .                 .
+......+ +......+     +......+      +......+          +......+
+      + +      +     +      +      +      +          +      +
+  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.
        
Wireless LAN Controller ( WLC )
        
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. 
        
Proxy Mobile IP (PMIP)
        
PMIP is a protocol intended for providing network-based IP 
mobility management support to a mobile node, without requiring
the participation of the mobile node in any IP mobility related 
signaling. The mobility entities in the network will track the 
mobile node's movements and will initiate the mobility signaling
and set up the required routing state.
        
Local Mobility Anchor (LMA)
        
Local Mobility Anchor is the home agent for the mobile node in 
a Proxy Mobile domain. It is the topological anchor point for 
the mobile node's home network prefix(es) and is the entity 
that manages the mobile node's binding state.
        
Network Access Identifier(NAI)
        
The Network Access Identifier (NAI) is the user identity 
submitted by the client during network access authentication. 
In roaming, the purpose of the NAI is to identify the user as 
well as to assist in the routing of the authentication request. 
        
Binding Revocation Indication(BRI)
        
Binding Revocation Indication(BRI) is a message sent by 
either the LMA or the controller to revoke the bindings present.
LMA can send a revocation for specific NAI or NAIs belonging to 
the controller.
        
Binding Revocation Acknowledgement(BRA)
        
When the BRI is received, the responder must send a Binding 
Revocation Acknowledgement message to indicate the receipt and 
the status of processing of the corresponding BRI message.
        
Mobile Access Gateway(MAG)
        
Mobile Access Gateway (MAG) performs mobility-related
signaling on behalf of the mobile nodes (MN) attached 
to its access links. 
        
REFERENCE
        
[1] Part 11 Wireless LAN Medium Access Control ( MAC )
and Physical Layer ( PHY ) Specifications.
        
[2] Draft-obara-capwap-lwapp-00.txt, IETF Light 
Weight Access Point Protocol.
        
[3] PMIPv6 RFC 5213.
    
Source file
CISCO-LWAPP-PMIP-MIB
Last revised
Identity
ciscoLwappPmipMIB
Base OID
1.3.6.1.4.1.9.9.845
Imported Objects
CISCO-LWAPP-DOT11-CLIENT-MIB cldcClientMacAddress
CISCO-LWAPP-WLAN-MIB cLWlanIndex (no object page)
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) TimeTicks Unsigned32
SNMPv2-TC MacAddress RowStatus TimeStamp
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-PMIP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-PMIP-MIB::ciscoLwappPmipMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-PMIP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-PMIP-MIB::ciscoLwappPmipMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (67)
.1.3.6.1.4.1.9.9.845
.1.3.6.1.4.1.9.9.845.0
.1.3.6.1.4.1.9.9.845.1
.1.3.6.1.4.1.9.9.845.1.1
.1.3.6.1.4.1.9.9.845.1.1.1
.1.3.6.1.4.1.9.9.845.1.1.10
.1.3.6.1.4.1.9.9.845.1.1.11
.1.3.6.1.4.1.9.9.845.1.1.12
.1.3.6.1.4.1.9.9.845.1.1.2
.1.3.6.1.4.1.9.9.845.1.1.3
.1.3.6.1.4.1.9.9.845.1.1.4
.1.3.6.1.4.1.9.9.845.1.1.5
.1.3.6.1.4.1.9.9.845.1.1.6
.1.3.6.1.4.1.9.9.845.1.1.7
.1.3.6.1.4.1.9.9.845.1.1.8
.1.3.6.1.4.1.9.9.845.1.1.9
.1.3.6.1.4.1.9.9.845.1.2
.1.3.6.1.4.1.9.9.845.1.2.1
.1.3.6.1.4.1.9.9.845.1.2.1.1
.1.3.6.1.4.1.9.9.845.1.2.1.1.1
.1.3.6.1.4.1.9.9.845.1.2.1.1.2
.1.3.6.1.4.1.9.9.845.1.2.1.1.3
.1.3.6.1.4.1.9.9.845.1.2.1.1.4
.1.3.6.1.4.1.9.9.845.1.2.2
.1.3.6.1.4.1.9.9.845.1.2.2.1
.1.3.6.1.4.1.9.9.845.1.2.2.1.1
.1.3.6.1.4.1.9.9.845.1.2.3
.1.3.6.1.4.1.9.9.845.1.2.3.1
.1.3.6.1.4.1.9.9.845.1.2.3.1.1
.1.3.6.1.4.1.9.9.845.1.2.3.1.2
.1.3.6.1.4.1.9.9.845.1.2.3.1.3
.1.3.6.1.4.1.9.9.845.1.2.3.1.4
.1.3.6.1.4.1.9.9.845.1.2.4
.1.3.6.1.4.1.9.9.845.1.2.4.1
.1.3.6.1.4.1.9.9.845.1.2.4.1.1
Enumeration
.1.3.6.1.4.1.9.9.845.1.2.4.1.2
.1.3.6.1.4.1.9.9.845.1.2.4.1.3
Enumeration
.1.3.6.1.4.1.9.9.845.1.2.4.1.4
.1.3.6.1.4.1.9.9.845.1.3
.1.3.6.1.4.1.9.9.845.1.3.1
.1.3.6.1.4.1.9.9.845.1.3.1.1
.1.3.6.1.4.1.9.9.845.1.3.1.1.1
.1.3.6.1.4.1.9.9.845.1.3.1.1.2
.1.3.6.1.4.1.9.9.845.1.3.1.1.3
.1.3.6.1.4.1.9.9.845.1.3.1.1.4
.1.3.6.1.4.1.9.9.845.1.3.1.1.5
.1.3.6.1.4.1.9.9.845.1.3.1.1.6
.1.3.6.1.4.1.9.9.845.1.3.1.1.7
.1.3.6.1.4.1.9.9.845.1.3.1.1.8
.1.3.6.1.4.1.9.9.845.1.3.1.1.9
.1.3.6.1.4.1.9.9.845.1.3.2
.1.3.6.1.4.1.9.9.845.1.3.2.1
.1.3.6.1.4.1.9.9.845.1.3.2.1.1
.1.3.6.1.4.1.9.9.845.1.3.2.1.10
.1.3.6.1.4.1.9.9.845.1.3.2.1.11
.1.3.6.1.4.1.9.9.845.1.3.2.1.12
.1.3.6.1.4.1.9.9.845.1.3.2.1.2
OctetString
.1.3.6.1.4.1.9.9.845.1.3.2.1.3
.1.3.6.1.4.1.9.9.845.1.3.2.1.4
.1.3.6.1.4.1.9.9.845.1.3.2.1.5
Enumeration
.1.3.6.1.4.1.9.9.845.1.3.2.1.6
.1.3.6.1.4.1.9.9.845.1.3.2.1.7
.1.3.6.1.4.1.9.9.845.1.3.2.1.8
.1.3.6.1.4.1.9.9.845.1.3.2.1.9
.1.3.6.1.4.1.9.9.845.2
.1.3.6.1.4.1.9.9.845.2.1
.1.3.6.1.4.1.9.9.845.2.2
Dependencies (32) 8 direct · 24 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
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.845.2.1.1
The compliance statement for the SNMP entities that
implement this MIB.
Required groups