CISCO-LWAPP-MESH-BATTERY-MIB
This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight Access Point Protocol
(LWAPP) tunnel from Light-weight Access Points.
This MIB represents information about the status of the
Multipurpose Power Supply (MPS), used as backup power
supply for an Access Point (AP) in the Wireless Mesh Network.
The MPS reports status information to the AP periodically.
The AP inturn reports the battery status information to the
controller periodically as a part of the LWAPP information
packet.
General Infomation about Cisco Wireless Mesh network:
A Mesh AP (MAP) can associate directly with another
Root AP (RAP) or with another MAP AP.
Each association of AP (MAP-MAP or RAP-MAP)
with another AP forms parent-child relationship.
The arrangement of the controller
(referred to as CC in the diagram) and mesh nodes
(RAP and MAP) LWAPP APs ,client(MN) and NMS appear
as follows.
+.......+ +.......+
+ + + +
+ NMS + + NMS +
+ + + +
+.......+ +.......+
. .
. . . .
. . . .
. . . .
+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . .
.. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ RAP + + RAP + + RAP + + RAP + + RAP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MAP + + MN + + MAP + + MAP + + MAP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . .. .
. . . .. .
. . . .. .
. . . . .
+......+ +......+ +......+ +......+. +......+
+ + + + + + + + + +
+ MAP + + MAP + + MAP + + MAP + + 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 through the tunnel.
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 is also referred to as '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.
Network Management System (NMS)
The station from which the administrator manages the
wired and wireless networks.
Mesh Network
A network of APs where the AP are linked to each other through
wireless links. These wireless links are also called backhaul
links. At least one of these APs must be connected to a
controller through a wired link.
Mesh Node
A mesh node is defined as a physical or logical entity
in the mesh network participating in forming the mesh
backhaul. There are two types of mesh nodes supported
in Cisco mesh network - RAP and MAP.
Root AP (RAP)
The AP forming the bridge between a wired and a mesh
network with an Ethernet interface to the wired
network and a 802.11 radio interface to the mesh
network.
Mesh AP (MAP).
The AP extending wireless coverage similar to a
repeater in a mesh network and consists of a 802.11
uplink and a 802.11 downlink. On a single-radio
backhaul, both uplink and downlink exist on the same
radio and are logical links only. On a multi-radio
backhaul, they may exist on different radios.
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-MESH-BATTERY-MIB- Last revised
- Identity
ciscoLwappMeshBatteryMIB- Base OID
1.3.6.1.4.1.9.9.620
Imported Objects
| CISCO-LWAPP-AP-MIB | cLApName cLApSysMacAddress |
| CISCO-SMI | ciscoMgmt |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | 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-MESH-BATTERY-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-MESH-BATTERY-MIB::ciscoLwappMeshBatteryMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-MESH-BATTERY-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-MESH-BATTERY-MIB::ciscoLwappMeshBatteryMIB'
Objects (25)
Showing 25 of 25 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.620 |
||
.1.3.6.1.4.1.9.9.620.0 |
||
.1.3.6.1.4.1.9.9.620.1 |
||
.1.3.6.1.4.1.9.9.620.1.1 |
||
.1.3.6.1.4.1.9.9.620.1.1.1 |
||
.1.3.6.1.4.1.9.9.620.1.1.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.1 |
|
|
milliWattsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.10 |
|
|
milliVoltsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.11 |
|
|
degree CelsiusSNMPv2-SMIInteger32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.12 |
|
|
|
milliAmpsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.13 |
|
milliAmpsSNMPv2-SMIInteger32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.14 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.2 |
|
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.3 |
.1.3.6.1.4.1.9.9.620.1.1.1.1.4 |
||
|
|
minutesSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.5 |
|
OctetString
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.6 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.7 |
|
|
milliVoltsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.8 |
|
|
milliVoltsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.9.9.620.1.1.1.1.9 |
|
.1.3.6.1.4.1.9.9.620.1.2 |
||
.1.3.6.1.4.1.9.9.620.1.2.1 |
||
.1.3.6.1.4.1.9.9.620.2 |
||
.1.3.6.1.4.1.9.9.620.2.1 |
||
.1.3.6.1.4.1.9.9.620.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-MIBDependency tree
Suggested compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- CISCO-LWAPP-TC-MIBcisco
- SNMPv2-CONFrfc
- SNMP-FRAMEWORK-MIBrfc
- CISCO-LWAPP-DOT11-MIBcisco
- CISCO-TCcisco
- INET-ADDRESS-MIBrfc
- CISCO-LWAPP-WLAN-MIBcisco
- CISCO-LWAPP-RF-MIBcisco
- IANA-ENTITY-MIBrfc
- UUID-TC-MIBrfc
- ENTITY-MIBrfc
- IANAifType-MIBrfc
- CISCO-LWAPP-AP-MIBcisco
- CISCO-LWAPP-MESH-BATTERY-MIBciscoselected
Conformance Groups (5)
Compliance Statements (3)
OID
.1.3.6.1.4.1.9.9.620.2.1.1The compliance statement for the SNMP entities that
implement the ciscoLwappMeshBatteryMIB module.
implement the ciscoLwappMeshBatteryMIB module.
Required groups
| mandatory | ciscoLwappMeshBatteryInfoGroup | |
| mandatory | ciscoLwappMeshBatteryNotifsConfigGroup | |
| mandatory | ciscoLwappMeshBatteryNotifsGroup |
OID
.1.3.6.1.4.1.9.9.620.2.1.2The compliance statement for the SNMP entities that
implement the ciscoLwappMeshBatteryMIB module.
implement the ciscoLwappMeshBatteryMIB module.
Required groups
| mandatory | ciscoLwappMeshBatteryNotifsConfigGroup | |
| mandatory | ciscoLwappMeshBatteryNotifsGroup | |
| mandatory | ciscoLwappMeshBatteryInfoGroupRev1 |
OID
.1.3.6.1.4.1.9.9.620.2.1.3The compliance statement for the SNMP entities that
implement the ciscoLwappMeshBatteryMIB module.
implement the ciscoLwappMeshBatteryMIB module.
Required groups
| mandatory | ciscoLwappMeshBatteryNotifsConfigGroup | |
| mandatory | ciscoLwappMeshBatteryNotifsGroup | |
| mandatory | ciscoLwappMeshBatteryInfoGroupRev2 |
Notifications / Traps (1)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.9.620.0.1 |
This notification is sent by the agent when the value of
clMeshNodeBatteryStatus has been changed from 'normal' to one of the abnormal values ('overloaded', 'low', 'acfail', 'replace', 'missing'). |