CISCO-LWAPP-CLOUD-SERVICES-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 provides configuration of Network Assurance
(NA) ,Connected Mobility Experience (CMX) and Data 
Externalization(dx) which comes under Cloud services. 
        
Network Assurance (NA)
Its a cloud based Assurance which provided by Cisco
to monitor the health of the network by collecting 
data from controllers and Sensors.
        
Connected Mobility Experience (CMX)
The MIB is used for programming Cloud based CMX services. 
The Network Mobility Service Protocol(NMSP) data is exported 
to CMX Cloud Server through https connection. The NMSP encoding 
will remain as it is for the TCP/TLS connection.
Use the MIB for configuring URL and Token ID and to enable 
this serrvice. The Controller will act as https client and 
will establish https connection with CMX URL. 
Controller will verify the CMX cloud server while the cloud 
server will authenticate the Controller using the configured 
id-token.
        
Data Externalization(dx)
dx is a feature in wlc which allows it to collect the 
data which may get published to the NA server for 
analaytics.
        
The relationship between CC, NA server and the 
LWAPP APs can be depicted as follows: 
        
          +......+     +......+     +......+
          +      +     +      +     +      +
          +  CC  +     +  CC  +.....+  NA  +
          +      +     +      +     +      +
          +......+     +......+     +......+
            ..            . .           .
            ..            .  .          .
           .  .            .    .        .
          .    .            .      .      .
         .      .            .       .     .
        .        .            .         .   .
    +......+ +......+     +......+      +..........+
    +      + +      +     +      +      +          +
    +  AP  + +  AP  +     +  AP  +......+  SENSOR  +
    +      + +      +     +      +      +   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.
        
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 
and client are used interchangeably.
        
Sensors 
        
These are wireless clients which periodically connect 
to a wireless network, run some tests and report back 
the test status to Cisco Network Assurance Server. 
        
The sensors are controlled and instructed by the 
Network Assurance server. APs can be tentatively put 
in Sensor mode to do the Sensor Job. There can be 
dedicated sensors as well.
        
Filtered Channels ( FC )
        
These are user-defined channels which use the filters
configured by the user to choose and carry the required 
data.
    
Source file
CISCO-LWAPP-CLOUD-SERVICES-MIB
Last revised
Identity
ciscoLwappCloudServicesMIB
Base OID
1.3.6.1.4.1.9.9.838
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType InetPortNumber
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC 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-CLOUD-SERVICES-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LWAPP-CLOUD-SERVICES-MIB::ciscoLwappCloudServicesMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LWAPP-CLOUD-SERVICES-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LWAPP-CLOUD-SERVICES-MIB::ciscoLwappCloudServicesMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (110)
.1.3.6.1.4.1.9.9.838
.1.3.6.1.4.1.9.9.838.0
.1.3.6.1.4.1.9.9.838.0.0
.1.3.6.1.4.1.9.9.838.0.1
.1.3.6.1.4.1.9.9.838.1
.1.3.6.1.4.1.9.9.838.1.1
.1.3.6.1.4.1.9.9.838.1.1.1
.1.3.6.1.4.1.9.9.838.1.1.1.1
.1.3.6.1.4.1.9.9.838.1.1.1.2
.1.3.6.1.4.1.9.9.838.1.1.1.3
clCSNAServerSyncInterval deprecated r/w
Enumeration
.1.3.6.1.4.1.9.9.838.1.1.1.4
Enumeration
.1.3.6.1.4.1.9.9.838.1.1.1.5
Bits
.1.3.6.1.4.1.9.9.838.1.1.1.6
.1.3.6.1.4.1.9.9.838.1.1.1.7
.1.3.6.1.4.1.9.9.838.1.1.2
.1.3.6.1.4.1.9.9.838.1.1.2.1
clCSNADiffSyncEnable deprecated r/w
.1.3.6.1.4.1.9.9.838.1.1.2.10
.1.3.6.1.4.1.9.9.838.1.1.2.2
Enumeration
.1.3.6.1.4.1.9.9.838.1.1.2.3
Enumeration
.1.3.6.1.4.1.9.9.838.1.1.2.4
.1.3.6.1.4.1.9.9.838.1.1.2.5
.1.3.6.1.4.1.9.9.838.1.1.2.6
Enumeration
.1.3.6.1.4.1.9.9.838.1.1.2.7
.1.3.6.1.4.1.9.9.838.1.1.2.8
clCSNAASIEnable deprecated r/w
.1.3.6.1.4.1.9.9.838.1.1.2.9
.1.3.6.1.4.1.9.9.838.1.1.3
.1.3.6.1.4.1.9.9.838.1.1.3.1
Enumeration
.1.3.6.1.4.1.9.9.838.1.1.3.2
Enumeration
.1.3.6.1.4.1.9.9.838.1.1.3.3
.1.3.6.1.4.1.9.9.838.1.1.4
.1.3.6.1.4.1.9.9.838.1.1.4.1
.1.3.6.1.4.1.9.9.838.1.1.4.1.1
.1.3.6.1.4.1.9.9.838.1.1.4.1.1.1
SecondsEnumeration
.1.3.6.1.4.1.9.9.838.1.1.4.1.1.2
.1.3.6.1.4.1.9.9.838.1.1.4.1.1.3
.1.3.6.1.4.1.9.9.838.1.1.4.1.1.4
.1.3.6.1.4.1.9.9.838.1.1.4.1.1.5
.1.3.6.1.4.1.9.9.838.1.2
.1.3.6.1.4.1.9.9.838.1.2.1
.1.3.6.1.4.1.9.9.838.1.2.1.1
.1.3.6.1.4.1.9.9.838.1.3
.1.3.6.1.4.1.9.9.838.1.3.1
.1.3.6.1.4.1.9.9.838.1.3.1.1
.1.3.6.1.4.1.9.9.838.1.3.1.2
.1.3.6.1.4.1.9.9.838.1.3.2
.1.3.6.1.4.1.9.9.838.1.3.2.1
.1.3.6.1.4.1.9.9.838.1.3.2.2
.1.3.6.1.4.1.9.9.838.1.4
.1.3.6.1.4.1.9.9.838.1.4.1
.1.3.6.1.4.1.9.9.838.1.4.1.1
.1.3.6.1.4.1.9.9.838.1.4.1.10
.1.3.6.1.4.1.9.9.838.1.4.1.10.1
.1.3.6.1.4.1.9.9.838.1.4.1.10.1.1
.1.3.6.1.4.1.9.9.838.1.4.1.10.1.2
.1.3.6.1.4.1.9.9.838.1.4.1.10.1.3
.1.3.6.1.4.1.9.9.838.1.4.1.10.1.4
.1.3.6.1.4.1.9.9.838.1.4.1.10.1.5
.1.3.6.1.4.1.9.9.838.1.4.1.2
.1.3.6.1.4.1.9.9.838.1.4.1.3
.1.3.6.1.4.1.9.9.838.1.4.1.4
.1.3.6.1.4.1.9.9.838.1.4.1.5
.1.3.6.1.4.1.9.9.838.1.4.1.6
.1.3.6.1.4.1.9.9.838.1.4.1.7
.1.3.6.1.4.1.9.9.838.1.4.1.8
.1.3.6.1.4.1.9.9.838.1.4.1.9
.1.3.6.1.4.1.9.9.838.1.4.2
Enumeration
.1.3.6.1.4.1.9.9.838.1.4.2.1
.1.3.6.1.4.1.9.9.838.1.4.2.2
.1.3.6.1.4.1.9.9.838.1.4.2.3
.1.3.6.1.4.1.9.9.838.1.4.2.4
.1.3.6.1.4.1.9.9.838.1.4.2.5
Enumeration
.1.3.6.1.4.1.9.9.838.1.4.2.6
.1.3.6.1.4.1.9.9.838.1.4.2.7
.1.3.6.1.4.1.9.9.838.1.4.2.7.1
.1.3.6.1.4.1.9.9.838.1.4.2.7.1.1
.1.3.6.1.4.1.9.9.838.1.4.2.7.1.2
.1.3.6.1.4.1.9.9.838.1.4.2.7.1.3
.1.3.6.1.4.1.9.9.838.1.4.2.7.1.4
.1.3.6.1.4.1.9.9.838.1.4.2.7.1.5
.1.3.6.1.4.1.9.9.838.1.5
.1.3.6.1.4.1.9.9.838.1.5.1
.1.3.6.1.4.1.9.9.838.1.5.2
.1.3.6.1.4.1.9.9.838.1.5.3
clCSWebhookOnchangeEnable deprecated r/w
.1.3.6.1.4.1.9.9.838.1.5.4
clCSWebhookSyncInterval deprecated r/w
Enumeration
.1.3.6.1.4.1.9.9.838.1.5.5
Enumeration
.1.3.6.1.4.1.9.9.838.1.5.6
Bits
.1.3.6.1.4.1.9.9.838.1.5.7
.1.3.6.1.4.1.9.9.838.1.5.8
.1.3.6.1.4.1.9.9.838.1.6
.1.3.6.1.4.1.9.9.838.1.6.1
.1.3.6.1.4.1.9.9.838.1.6.1.1
.1.3.6.1.4.1.9.9.838.1.6.1.1.1
SecondsEnumeration
.1.3.6.1.4.1.9.9.838.1.6.1.1.2
.1.3.6.1.4.1.9.9.838.1.6.1.1.3
.1.3.6.1.4.1.9.9.838.1.6.1.1.4
.1.3.6.1.4.1.9.9.838.1.7
.1.3.6.1.4.1.9.9.838.1.7.1
.1.3.6.1.4.1.9.9.838.1.7.1.1
.1.3.6.1.4.1.9.9.838.1.7.1.1.1
.1.3.6.1.4.1.9.9.838.1.7.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.838.1.7.1.1.3
.1.3.6.1.4.1.9.9.838.1.7.1.1.4
.1.3.6.1.4.1.9.9.838.1.7.1.1.5
.1.3.6.1.4.1.9.9.838.1.7.2
.1.3.6.1.4.1.9.9.838.1.7.2.1
.1.3.6.1.4.1.9.9.838.1.7.2.1.1
.1.3.6.1.4.1.9.9.838.1.7.2.1.2
.1.3.6.1.4.1.9.9.838.2
.1.3.6.1.4.1.9.9.838.2.1
.1.3.6.1.4.1.9.9.838.2.2
Dependencies (6) 6 direct 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 (16)
This collection of objects represent the
configuration of server on the controller to be passed
to an LWAPP AP.
.1.3.6.1.4.1.9.9.838.2.2.1
This collection of objects represent the
configuration of Network Assuranceon the controller
to be passed to an LWAPP AP.
.1.3.6.1.4.1.9.9.838.2.2.2
This collection of objects represent the
configuration of Connected Mobility Experience (CMX)
server on the controller to be passed to an LWAPP AP.
.1.3.6.1.4.1.9.9.838.2.2.3
This collection of objects represent the configuration
for Connected Mobility Experience (CMX) on the controller
to be passed to an LWAPP AP.
clCSCMXConfigGroup object is superseded by
clCSCMXConfigGroupRev1.
.1.3.6.1.4.1.9.9.838.2.2.4
This collection of objects represent the configuration
for data externalization(dx) on the controller to be
passed to an LWAPP AP.
.1.3.6.1.4.1.9.9.838.2.2.5
This collection of objects represent the
trap configuration of NA sent by the agent
to a network management station.
.1.3.6.1.4.1.9.9.838.2.2.6
This supplemental collection of objects represents the
NA related notifications sent by the agent to a network
management station.
.1.3.6.1.4.1.9.9.838.2.2.7
This collection of objects represent the
secure Tunnel configuration.
.1.3.6.1.4.1.9.9.838.2.2.8
This collection of objects represent the
secure Tunnel information.
.1.3.6.1.4.1.9.9.838.2.2.9
This supplemental collection of objects represents the
Secure Tunnel related notifications sent by the agent to
a network management station.
.1.3.6.1.4.1.9.9.838.2.2.10
This collection of objects represent the
configuration of Network Assuranceon the controller
to be passed to a Network Assurance Server.
clCSNAGlobalConfigGroupRev1 object is superseded by
clCSNAGlobalConfigGroupRev2.
.1.3.6.1.4.1.9.9.838.2.2.11
This collection of objects represent the
configuration of network assurance on the controller
to be passed to a network assurance server.
.1.3.6.1.4.1.9.9.838.2.2.12
This collection of objects represent the
configuration of a webhook server to receive telemetry
data from the controller
clCSWebhookConfigGroup object is superseded by
clCSWebhookConfigGroupRev1.
.1.3.6.1.4.1.9.9.838.2.2.13
This collection of objects represent the
configuration of a webhook server to receive telemetry
data from the controller
.1.3.6.1.4.1.9.9.838.2.2.14
This collection of objects represent the configuration
for Connected Mobility Experience (CMX) on the controller
to be passed to an LWAPP AP.
.1.3.6.1.4.1.9.9.838.2.2.15
This collection of objects represent the
configuration of telemetry filter channels.
.1.3.6.1.4.1.9.9.838.2.2.16
Compliance Statements (4)

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

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

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

OID .1.3.6.1.4.1.9.9.838.2.1.4
The compliance statement for the SNMP entities that
implement this MIB.
Required groups
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.9.838.0.0.1
This object is used to send a trap whenever the
device status moves out of compliance with
respect to smart-licensing
.1.3.6.1.4.1.9.9.838.0.1.1
This object is used to send secure
tunnel status change.