CISCO-LWAPP-MESH-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 used in Wireless Mesh
        Network. MAP APs associates directly with RAP APs or 
        with another MAP AP. Each association of AP (MAP-MAP 
        or RAP-MAP) with another AP forms parent-child 
        relationship. 
        
        The deployment of the controller 
        (referred to as CC in the diagram), mesh nodes 
        (RAP and MAP) LWAPP APs, client(MS) and NMS appear 
        as follows.
        
         +.......+                 +.......+
         +       +                 +       +
         +  NMS  +                 +  NMS  +
         +       +                 +       +
         +.......+                 +.......+
            .                         .
         .    .                     .   .
        .         .                .        .
        .            .             .            .
        +......+     +......+     +......+           +......+
        +      +     +      +     +      +           +      +
        +  CC  +     +  CC  +     +  CC  +           +  CC  +
        +      +     +      +     +      +           +      +
        +......+     +......+     +......+           +......+
        ..            .             .                 .
        ..            .             .                 .
        .  .            .             .                 .
        .    .            .             .                 .
        .      .            .             .                 .
        .        .            .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  RAP + +  RAP +     +  RAP  +     +  RAP +          +  RAP +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+
        .        .              .             .                 .
        .        .              .             .                 .
        .        .              .             .                 .
        .          .              .             .                 .
        .           .              .             .                 .
        +......+ +......+     +......+      +......+          +......+
        +      + +      +     +      +      +      +          +      +
        +  MAP + +  MS  +     +  MAP +      +  MAP +          +  MAP +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+
        .                    .                          ..    . 
        . .                  .                     ..        .
        .   .                .                  ..            .
        .     .              .              .                .
        +......+ +......+     +......+      +......+.         +......+
        +      + +      +     +      +      +      +          +      +
        +  MAP + +  MAP +     +  MAP +      +  MAP +          +  MS  +
        +      + +      +     +      +      +      +          +      +
        +......+ +......+     +......+      +......+          +......+
        
        
        
        
        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 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 Station ( MS )
        
        A roaming 802.11 wireless device in a wireless
        network associated with an access point. Mobile Station
        and client are used interchangeably. 
        
        Network Management System ( NMS )
        
        The station from which the administrator manages the
        wired and wireless networks.
        
        Mesh Node
        
        A mesh node is defined as a physical or logical entity
        in the mesh network participating in forming the mesh 
        backhaul. RAP and MAP are two types of mesh nodes 
        supported in mesh network.
        
        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.
        
        Mesh Network
        
        Network starting with the wireless backhaul downlink
        of the RAP and all the entities below except any 
        attached network to the Ethernet link of MAPs. A mesh 
        network below a single RAP is also referred to as a 
        'Mesh Sector'.A mesh network consists of mesh nodes. 
        A single mesh network is always augmented to a single 
        wired network.
        
        Mesh Link
        
        A logical 802.11 link between two mesh nodes. A single 
        link is point-to-point. All point-to-multipoint links 
        are considered as multiple mesh links. Often referred 
        to as mesh backhaul link.
        
        Mesh Backhaul
        
        A mesh backhaul consists of mesh nodes and mesh links 
        terminating at a RAP. This necessarily creates a one-
        to-one relationship between a 'mesh network', 'mesh
        sector' and a 'mesh backhaul' where these terms can be 
        used interchangeably.
        
        SNR
        
        Signal to Noise ratio on the 802.11 radio.
        
        Bridged network 
        
        The bridged network is defined as the network(s)
        attached to the Ethernet port of any MAP. There can be
        multiple such networks attached to a single mesh 
        network.
        
        Mesh Node Roaming
        
        A mesh node may change its parent mesh node naturally 
        when the RF/network condition changes. Child Mesh node 
        will re-associate and re-authenticate to new parent 
        mesh node. Mesh Security supports two types of mesh 
        node roaming.
           Intra-controller - LWAPP session is not lost.
           Inter-controller - LWAPP session is lost.
        
        AMSDU
        
        Aggregate MAC Service Data Unit. A structure containing 
        multiple MSDUs, transported within a single (unfragmented)
        or multiple (fragmented) Data MPDU.
        
        	IDS
        
        	Intrusion Detection Sysytem. A software to detect unwanted
        	attempts at accessing,manipulating, and or disabling of WLC.
        
        		ExtendedUA
        		
        For 1524 APs, it has two 802.11a radios (slot1, slot2) and 
        one 802.11b/g radio (slot0). This will enable the client 
        access on 802.11a (slot1) for 152x series mesh access points
        with two 802.11a radios, where the wireless client association 
        can be done over the 802.11a radio (slot1). With this feature 
        we are providing an option to enable/disable backhaul client 
        on another 802.11a radio (slot2) as well. This implies that 
        a 152x series mesh access points with two 802.11a radios 
        can carry both backhaul traffic and 802.11a (slot1, slot2) 
        client traffic over the same 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
CLDot11ChannelCISCO-LWAPP-TC-MIB
ciscoMgmtCISCO-SMI
SnmpAdminStringSNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUPSNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32, Gauge32, NOTIFICATION-TYPESNMPv2-SMI
TruthValue, TimeStamp, MacAddress, TimeIntervalSNMPv2-TC
ciscoLwappMeshMIB .1.3.6.1.4.1.9.9.616
ciscoLwappMeshMIBNotifs .1.3.6.1.4.1.9.9.616.0
ciscoLwappMeshAuthFailure .1.3.6.1.4.1.9.9.616.0.1
ciscoLwappMeshExcessiveHopCount .1.3.6.1.4.1.9.9.616.0.10
ciscoLwappMeshExcessiveChildren .1.3.6.1.4.1.9.9.616.0.11
ciscoLwappMeshOnsetHighSNR .1.3.6.1.4.1.9.9.616.0.12
ciscoLwappMeshAbateHighSNR .1.3.6.1.4.1.9.9.616.0.13
ciscoLwappMeshChildExcludedParent .1.3.6.1.4.1.9.9.616.0.2
ciscoLwappMeshParentChange .1.3.6.1.4.1.9.9.616.0.3
ciscoLwappMeshChildMoved .1.3.6.1.4.1.9.9.616.0.4
ciscoLwappMeshExcessiveParentChange .1.3.6.1.4.1.9.9.616.0.5
ciscoLwappMeshOnsetSNR .1.3.6.1.4.1.9.9.616.0.6
ciscoLwappMeshAbateSNR .1.3.6.1.4.1.9.9.616.0.7
ciscoLwappMeshConsoleLogin .1.3.6.1.4.1.9.9.616.0.8
ciscoLwappMeshDefaultBridgeGroupName .1.3.6.1.4.1.9.9.616.0.9
ciscoLwappMeshMIBObjects .1.3.6.1.4.1.9.9.616.1
ciscoLwappMeshConfig .1.3.6.1.4.1.9.9.616.1.1
clMeshNodeTable .1.3.6.1.4.1.9.9.616.1.1.1
clMeshNodeEntry .1.3.6.1.4.1.9.9.616.1.1.1.1
clMeshNodeRole .1.3.6.1.4.1.9.9.616.1.1.1.1.1
clMeshNodeInternalTemp .1.3.6.1.4.1.9.9.616.1.1.1.1.10
clMeshNodeType .1.3.6.1.4.1.9.9.616.1.1.1.1.11
clMeshNodeHops .1.3.6.1.4.1.9.9.616.1.1.1.1.12
clMeshNodeChildCount .1.3.6.1.4.1.9.9.616.1.1.1.1.13
clMeshNodeBackhaulRadio .1.3.6.1.4.1.9.9.616.1.1.1.1.14
clMeshNodeBHDataRate .1.3.6.1.4.1.9.9.616.1.1.1.1.15
clMeshDaisyChainEnabled .1.3.6.1.4.1.9.9.616.1.1.1.1.16
clMeshPrefParentMacAddress .1.3.6.1.4.1.9.9.616.1.1.1.1.17
clMeshNodeBGNStrictMatch .1.3.6.1.4.1.9.9.616.1.1.1.1.18
clMeshNodeVlanEnabled .1.3.6.1.4.1.9.9.616.1.1.1.1.19
clMeshNodeGroupName .1.3.6.1.4.1.9.9.616.1.1.1.1.2
clMeshNodeNativeVlanId .1.3.6.1.4.1.9.9.616.1.1.1.1.20
clMeshNodeBackhaul .1.3.6.1.4.1.9.9.616.1.1.1.1.3
clMeshNodeBackhaulDataRate deprecated.1.3.6.1.4.1.9.9.616.1.1.1.1.4
clMeshNodeEthernetBridge .1.3.6.1.4.1.9.9.616.1.1.1.1.5
clMeshNodeEthernetLinkStatus .1.3.6.1.4.1.9.9.616.1.1.1.1.6
clMeshNodePublicSafetyBackhaul deprecated.1.3.6.1.4.1.9.9.616.1.1.1.1.7
clMeshNodeParentMacAddress .1.3.6.1.4.1.9.9.616.1.1.1.1.8
clMeshNodeHeaterStatus .1.3.6.1.4.1.9.9.616.1.1.1.1.9
ciscoLwappMeshGlobalConfig .1.3.6.1.4.1.9.9.616.1.2
clMeshNodeRange .1.3.6.1.4.1.9.9.616.1.2.1
clMeshExcessiveParentChangeThreshold .1.3.6.1.4.1.9.9.616.1.2.10
clMeshExcessiveParentChangeInterval .1.3.6.1.4.1.9.9.616.1.2.11
clMeshBackgroundScan .1.3.6.1.4.1.9.9.616.1.2.12
clMeshAuthenticationMode .1.3.6.1.4.1.9.9.616.1.2.13
clMeshExcessiveHopCountThreshold .1.3.6.1.4.1.9.9.616.1.2.14
clMeshExcessiveRapChildThreshold .1.3.6.1.4.1.9.9.616.1.2.15
clMeshExcessiveMapChildThreshold .1.3.6.1.4.1.9.9.616.1.2.16
clMeshHighSNRThresholdAbate .1.3.6.1.4.1.9.9.616.1.2.17
clMeshHighSNRThresholdOnset .1.3.6.1.4.1.9.9.616.1.2.18
clMeshPublicSafetyBackhaulGlobal .1.3.6.1.4.1.9.9.616.1.2.19
clMeshBackhaulClientAccess .1.3.6.1.4.1.9.9.616.1.2.2
clMeshisAMSDUEnable .1.3.6.1.4.1.9.9.616.1.2.20
clMeshIsIdsEnable .1.3.6.1.4.1.9.9.616.1.2.21
clMeshIsDCAChannelsEnable .1.3.6.1.4.1.9.9.616.1.2.22
clMeshIsExtendedUAEnable .1.3.6.1.4.1.9.9.616.1.2.23
clMeshMacFilterList .1.3.6.1.4.1.9.9.616.1.2.3
clMeshMeshNodeAuthFailureThreshold .1.3.6.1.4.1.9.9.616.1.2.4
clMeshMeshChildAssociationFailuresThreshold .1.3.6.1.4.1.9.9.616.1.2.5
clMeshMeshChildExcludedParentInterval .1.3.6.1.4.1.9.9.616.1.2.6
clMeshSNRThresholdAbate .1.3.6.1.4.1.9.9.616.1.2.7
clMeshSNRThresholdOnset .1.3.6.1.4.1.9.9.616.1.2.8
clMeshSNRCheckTimeInterval .1.3.6.1.4.1.9.9.616.1.2.9
ciscoLwappMeshNeighborsStatus .1.3.6.1.4.1.9.9.616.1.3
clMeshNeighborTable .1.3.6.1.4.1.9.9.616.1.3.1
clMeshNeighborEntry .1.3.6.1.4.1.9.9.616.1.3.1.1
clMeshNeighborMacAddress .1.3.6.1.4.1.9.9.616.1.3.1.1.1
clMeshNeighborType .1.3.6.1.4.1.9.9.616.1.3.1.1.2
clMeshNeighborLinkSnr .1.3.6.1.4.1.9.9.616.1.3.1.1.3
clMeshNeighborChannel .1.3.6.1.4.1.9.9.616.1.3.1.1.4
clMeshNeighborUpdate .1.3.6.1.4.1.9.9.616.1.3.1.1.5
ciscoLwappMeshNotifControlConfig .1.3.6.1.4.1.9.9.616.1.4
clMeshAuthFailureNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.1
clMeshExcessiveChildrenNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.10
clMeshHighSNRNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.11
clMeshChildExcludedParentNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.2
clMeshParentChangeNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.3
clMeshChildMovedNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.4
clMeshExcessiveParentChangeNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.5
clMeshPoorSNRNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.6
clMeshConsoleLoginNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.7
clMeshDefaultBridgeGroupNameNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.8
clMeshExcessiveHopCountNotifEnabled .1.3.6.1.4.1.9.9.616.1.4.9
ciscoLwappMeshMIBNotifObjects .1.3.6.1.4.1.9.9.616.1.5
clMeshNodeMacAddress .1.3.6.1.4.1.9.9.616.1.5.1
clMeshAuthFailureReason .1.3.6.1.4.1.9.9.616.1.5.2
clMeshPreviousParentMacAddress .1.3.6.1.4.1.9.9.616.1.5.3
clMeshConsoleLoginStatus .1.3.6.1.4.1.9.9.616.1.5.4
ciscoLwappMeshGpsObjects .1.3.6.1.4.1.9.9.616.1.6
clMeshGpsInfoTable .1.3.6.1.4.1.9.9.616.1.6.1
clMeshGpsInfoEntry .1.3.6.1.4.1.9.9.616.1.6.1.1
clMeshGpsLocationPresent .1.3.6.1.4.1.9.9.616.1.6.1.1.1
clMeshGpsLocationValid .1.3.6.1.4.1.9.9.616.1.6.1.1.2
clMeshGpsLatitude .1.3.6.1.4.1.9.9.616.1.6.1.1.3
clMeshGpsLongitude .1.3.6.1.4.1.9.9.616.1.6.1.1.4
clMeshGpsAltitude .1.3.6.1.4.1.9.9.616.1.6.1.1.5
clMeshGpsCollectionTime .1.3.6.1.4.1.9.9.616.1.6.1.1.6
ciscoLwappMeshMIBConform .1.3.6.1.4.1.9.9.616.2
ciscoLwappMeshMIBCompliances .1.3.6.1.4.1.9.9.616.2.1
ciscoLwappMeshMIBGroups .1.3.6.1.4.1.9.9.616.2.2