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.