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.

Imported Objects

cLApSysMacAddress, cLApNameCISCO-LWAPP-AP-MIB
ciscoMgmtCISCO-SMI
SnmpAdminStringSNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUPSNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, Integer32SNMPv2-SMI
TruthValueSNMPv2-TC
ciscoLwappMeshBatteryMIB .1.3.6.1.4.1.9.9.620
ciscoLwappMeshBatteryMIBNotifs .1.3.6.1.4.1.9.9.620.0
ciscoLwappMeshBatteryAlarm .1.3.6.1.4.1.9.9.620.0.1
ciscoLwappMeshBatteryMIBObjects .1.3.6.1.4.1.9.9.620.1
ciscoLwappMeshBatteryInfo .1.3.6.1.4.1.9.9.620.1.1
clMeshNodeBatteryTable .1.3.6.1.4.1.9.9.620.1.1.1
clMeshNodeBatteryEntry .1.3.6.1.4.1.9.9.620.1.1.1.1
clMeshNodeBatteryModelName .1.3.6.1.4.1.9.9.620.1.1.1.1.1
clMeshNodeBatteryOutputPower .1.3.6.1.4.1.9.9.620.1.1.1.1.10
clMeshNodeBatteryInternalVoltage .1.3.6.1.4.1.9.9.620.1.1.1.1.11
clMeshNodeBatteryTemperature .1.3.6.1.4.1.9.9.620.1.1.1.1.12
clMeshNodeBatteryCurrent deprecated.1.3.6.1.4.1.9.9.620.1.1.1.1.13
clMeshNodeBatteryCurrentValue .1.3.6.1.4.1.9.9.620.1.1.1.1.14
clMeshNodeBatteryStatus .1.3.6.1.4.1.9.9.620.1.1.1.1.2
clMeshNodeBatteryChargingState deprecated.1.3.6.1.4.1.9.9.620.1.1.1.1.3
clMeshNodeBatteryChargingLevel .1.3.6.1.4.1.9.9.620.1.1.1.1.4
clMeshNodeBatteryRemainingCapacity deprecated.1.3.6.1.4.1.9.9.620.1.1.1.1.5
clMeshNodeBatterySwVersion .1.3.6.1.4.1.9.9.620.1.1.1.1.6
clMeshNodeBatterySerialNumber .1.3.6.1.4.1.9.9.620.1.1.1.1.7
clMeshNodeBatteryInputVoltage .1.3.6.1.4.1.9.9.620.1.1.1.1.8
clMeshNodeBatteryOutputVoltage .1.3.6.1.4.1.9.9.620.1.1.1.1.9
ciscoLwappMeshBatteryNotifControlConfig .1.3.6.1.4.1.9.9.620.1.2
clMeshBatteryAlarmEnabled .1.3.6.1.4.1.9.9.620.1.2.1
ciscoLwappMeshBatteryMIBConform .1.3.6.1.4.1.9.9.620.2
ciscoLwappMeshBatteryMIBCompliances .1.3.6.1.4.1.9.9.620.2.1
ciscoLwappMeshBatteryMIBGroups .1.3.6.1.4.1.9.9.620.2.2