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.
Status in source: unspecified.
Names: ciscoLwappCloudServicesMIB
Technical details
{
"smi_kind": "MODULE-IDENTITY",
"definition": [
"ciscoLwappCloudServicesMIB",
"MODULE-IDENTITY",
"LAST-UPDATED",
[
"literal",
"223230313830373033303030305a22"
],
"ORGANIZATION",
"\"Cisco Systems Inc.\"",
"CONTACT-INFO",
"\"Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553 -NETS E-mail: cs-snmp@cisco.com\"",
"DESCRIPTION",
"\"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.\"",
"REVISION",
[
"literal",
"223230313830373033303030305a22"
],
"DESCRIPTION",
"\"Added cLCSNAServerResetSubscriptions, cLCSWebhookResetSubscriptions, clCSCMXOnPremisesEnable Added cLCSTelemetryFCTable, cLCSTelemetryFCFilterTable, cLCSNAServerChannelTable, cLCSWebhookChannelTable, clCSTelemetryConfigGroup, clCSNAGlobalConfigGroupRev2, clCSWebhookConfigGroupRev1, clCSCMXConfigGroupRev1 Deprecated clCSNAServerOnchangeEnable, clCSNAServerSyncInterval, clCSNAServerSubscriptionAction, clCSNAServerSubscriptionTopic, clCSNAGlobalConfigGroupRev1, clCSWebhookConfigGroup, clCSCMXConfigGroup\"",
"REVISION",
[
"literal",
"223230313830343234303030305a22"
],
"DESCRIPTION",
"\"Added clCSNAServerOnchangeEnable, clCSNAServerSyncInterval, clCSNAServerSubscriptionAction, clCSNAServerSubscriptionTopic Added clCSMIBComplianceRev2, clCSNAGlobalConfigGroupRev1, clCSWebhookConfigGroup Deprecated clCSNAASIEnable, clCSNADiffSyncEnable, clCSNAGlobalConfigGroup, clCSMIBComplianceRev1\"",
"REVISION",
[
"literal",
"223230313731323231303030305a22"
],
"DESCRIPTION",
"\"Updated clCSNAGlobalConfigGroup. Deprecate clCSMIBCompliance and replaced by clCSMIBComplianceRev1. Added clCSNAASIEnable,clCSNADiffSyncEnable,clCSSecTunObjects, clCSSecTunConfig,clCSSecTunInfo,clCSSecTunNotifs.\"",
"REVISION",
[
"literal",
"223230313730323232303030305a22"
],
"DESCRIPTION",
"\"Initial version of config cloud services MIB module.\"",
"::=",
"{",
"ciscoMgmt",
"838",
"}"
],
"syntax_tree": [
[
"LAST-UPDATED",
"201807030000Z"
],
[
"ORGANIZATION",
"Cisco Systems Inc."
],
[
"CONTACT-INFO",
"Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553 -NETS E-mail: cs-snmp@cisco.com"
],
[
"DESCRIPTION",
"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."
],
[
"Revisions",
[
[
"201807030000Z",
[
"DESCRIPTION",
"Added cLCSNAServerResetSubscriptions, cLCSWebhookResetSubscriptions, clCSCMXOnPremisesEnable Added cLCSTelemetryFCTable, cLCSTelemetryFCFilterTable, cLCSNAServerChannelTable, cLCSWebhookChannelTable, clCSTelemetryConfigGroup, clCSNAGlobalConfigGroupRev2, clCSWebhookConfigGroupRev1, clCSCMXConfigGroupRev1 Deprecated clCSNAServerOnchangeEnable, clCSNAServerSyncInterval, clCSNAServerSubscriptionAction, clCSNAServerSubscriptionTopic, clCSNAGlobalConfigGroupRev1, clCSWebhookConfigGroup, clCSCMXConfigGroup"
]
],
[
"201804240000Z",
[
"DESCRIPTION",
"Added clCSNAServerOnchangeEnable, clCSNAServerSyncInterval, clCSNAServerSubscriptionAction, clCSNAServerSubscriptionTopic Added clCSMIBComplianceRev2, clCSNAGlobalConfigGroupRev1, clCSWebhookConfigGroup Deprecated clCSNAASIEnable, clCSNADiffSyncEnable, clCSNAGlobalConfigGroup, clCSMIBComplianceRev1"
]
],
[
"201712210000Z",
[
"DESCRIPTION",
"Updated clCSNAGlobalConfigGroup. Deprecate clCSMIBCompliance and replaced by clCSMIBComplianceRev1. Added clCSNAASIEnable,clCSNADiffSyncEnable,clCSSecTunObjects, clCSSecTunConfig,clCSSecTunInfo,clCSSecTunNotifs."
]
],
[
"201702220000Z",
[
"DESCRIPTION",
"Initial version of config cloud services MIB module."
]
]
]
]
]
}- Cisco
· Publisher's source file
· Archived source file
Source location: CISCO-LWAPP-CLOUD-SERVICES-MIB::ciscoLwappCloudServicesMIB.Source version and references
Downloaded: 2026-10-19T00:18:11.670284+00:00. SHA-256:
5cbd3c3fbb960017ab661475f26277c93f1cd43a953c9ada6da80f8b03ca7545{'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-CLOUD-SERVICES-MIB', 'imports': {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['MacAddress', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetPortNumber'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappCloudServicesMIB MODULE-IDENTITY\n LAST-UPDATED "201807030000Z"\n ORGANIZATION "Cisco Systems Inc."\n CONTACT-INFO\n "Cisco Systems\n Customer Service\n Postal: 170 W Tasman Drive\n San Jose, CA 95134\n USA\n Tel: +1 800 553 -NETS\n E-mail: cs-snmp@cisco.com"\n DESCRIPTION\n "This MIB is intended to be implemented on all those\n devices operating as Central controllers, that \n terminate the Light Weight Access Point Protocol\n tunnel from Cisco Light-weight LWAPP Access Points.\n\n This MIB provides configuration of Network Assurance\n (NA) ,Connected Mobility Experience (CMX) and Data \n Externalization(dx) which comes under Cloud services. \n\n Network Assurance (NA)\n Its a cloud based Assurance which provided by Cisco\n to monitor the health of the network by collecting \n data from controllers and Sensors.\n\n Connected Mobility Experience (CMX)\n The MIB is used for programming Cloud based CMX services. \n The Network Mobility Service Protocol(NMSP) data is exported \n to CMX Cloud Server through https connection. The NMSP encoding \n will remain as it is for the TCP/TLS connection.\n Use the MIB for configuring URL and Token ID and to enable \n this serrvice. The Controller will act as https client and \n will establish https connection with CMX URL. \n Controller will verify the CMX cloud server while the cloud \n server will authenticate the Controller using the configured \n id-token.\n\n Data Externalization(dx)\n dx is a feature in wlc which allows it to collect the \n data which may get published to the NA server for \n analaytics.\n\n The relationship between CC, NA server and the \n LWAPP APs can be depicted as follows: \n\n +......+ +......+ +......+\n + + + + + +\n + CC + + CC +.....+ NA +\n + + + + + +\n +......+ +......+ +......+\n .. . . .\n .. . . .\n . . . . .\n . . . . .\n . . . . .\n . . . . .\n +......+ +......+ +......+ +..........+\n + + + + + + + +\n + AP + + AP + + AP +......+ SENSOR +\n + + + + + + + AP +\n +......+ +......+ +......+ +..........+\n . . .\n . . . .\n . . . .\n . . . .\n . . . .\n +......+ +......+ +......+ +......+\n + + + + + + + +\n + MN + + MN + + MN + + MN +\n + + + + + + + +\n +......+ +......+ +......+ +......+\n\n\n The LWAPP tunnel exists between the controller and\n the APs. The MNs communicate with the APs through\n the protocol defined by the 802.11 standard.\n\n LWAPP APs, upon bootup, discover and join one of the\n controllers and the controller pushes the configuration,\n that includes the WLAN parameters, to the LWAPP APs.\n The APs then encapsulate all the 802.11 frames from\n wireless clients inside LWAPP frames and forward\n the LWAPP frames to the controller.\n\n GLOSSARY\n\n Access Point ( AP )\n\n An entity that contains an 802.11 medium access\n control ( MAC ) and physical layer ( PHY ) interface\n and provides access to the distribution services via\n the wireless medium for associated clients. \n\n LWAPP APs encapsulate all the 802.11 frames in\n LWAPP frames and sends them to the controller to which\n it is logically connected.\n\n Light Weight Access Point Protocol ( LWAPP )\n\n This is a generic protocol that defines the \n communication between the Access Points and the\n Central Controller. \n\n Mobile Node ( MN )\n\n A roaming 802.11 wireless device in a wireless\n network associated with an access point. Mobile Node \n and client are used interchangeably.\n\n Sensors \n\n These are wireless clients which periodically connect \n to a wireless network, run some tests and report back \n the test status to Cisco Network Assurance Server. \n\n The sensors are controlled and instructed by the \n Network Assurance server. APs can be tentatively put \n in Sensor mode to do the Sensor Job. There can be \n dedicated sensors as well.\n\n Filtered Channels ( FC )\n\n These are user-defined channels which use the filters\n configured by the user to choose and carry the required \n data."\n REVISION "201807030000Z"\n DESCRIPTION\n "Added cLCSNAServerResetSubscriptions,\n cLCSWebhookResetSubscriptions,\n clCSCMXOnPremisesEnable\n Added cLCSTelemetryFCTable,\n cLCSTelemetryFCFilterTable,\n cLCSNAServerChannelTable,\n cLCSWebhookChannelTable,\n clCSTelemetryConfigGroup,\n clCSNAGlobalConfigGroupRev2,\n clCSWebhookConfigGroupRev1,\n clCSCMXConfigGroupRev1\n Deprecated clCSNAServerOnchangeEnable,\n clCSNAServerSyncInterval,\n clCSNAServerSubscriptionAction,\n clCSNAServerSubscriptionTopic,\n clCSNAGlobalConfigGroupRev1,\n clCSWebhookConfigGroup,\n clCSCMXConfigGroup"\n REVISION "201804240000Z"\n DESCRIPTION\n "Added clCSNAServerOnchangeEnable,\n clCSNAServerSyncInterval,\n clCSNAServerSubscriptionAction,\n clCSNAServerSubscriptionTopic\n Added clCSMIBComplianceRev2,\n clCSNAGlobalConfigGroupRev1,\n clCSWebhookConfigGroup\n Deprecated clCSNAASIEnable, \n clCSNADiffSyncEnable,\n clCSNAGlobalConfigGroup,\n clCSMIBComplianceRev1"\n REVISION "201712210000Z"\n DESCRIPTION\n "Updated clCSNAGlobalConfigGroup.\n Deprecate clCSMIBCompliance and replaced by \n clCSMIBComplianceRev1.\n Added clCSNAASIEnable,clCSNADiffSyncEnable,clCSSecTunObjects,\n clCSSecTunConfig,clCSSecTunInfo,clCSSecTunNotifs."\n REVISION "201702220000Z"\n DESCRIPTION\n "Initial version of config cloud services MIB module."\n ::= { ciscoMgmt 838 }', 'syntax_tree': [['LAST-UPDATED', '201807030000Z'], ['ORGANIZATION', 'Cisco Systems Inc.'], ['CONTACT-INFO', 'Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553 -NETS E-mail: cs-snmp@cisco.com'], ['DESCRIPTION', '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.'], ['Revisions', [['201807030000Z', ['DESCRIPTION', 'Added cLCSNAServerResetSubscriptions, cLCSWebhookResetSubscriptions, clCSCMXOnPremisesEnable Added cLCSTelemetryFCTable, cLCSTelemetryFCFilterTable, cLCSNAServerChannelTable, cLCSWebhookChannelTable, clCSTelemetryConfigGroup, clCSNAGlobalConfigGroupRev2, clCSWebhookConfigGroupRev1, clCSCMXConfigGroupRev1 Deprecated clCSNAServerOnchangeEnable, clCSNAServerSyncInterval, clCSNAServerSubscriptionAction, clCSNAServerSubscriptionTopic, clCSNAGlobalConfigGroupRev1, clCSWebhookConfigGroup, clCSCMXConfigGroup']], ['201804240000Z', ['DESCRIPTION', 'Added clCSNAServerOnchangeEnable, clCSNAServerSyncInterval, clCSNAServerSubscriptionAction, clCSNAServerSubscriptionTopic Added clCSMIBComplianceRev2, clCSNAGlobalConfigGroupRev1, clCSWebhookConfigGroup Deprecated clCSNAASIEnable, clCSNADiffSyncEnable, clCSNAGlobalConfigGroup, clCSMIBComplianceRev1']], ['201712210000Z', ['DESCRIPTION', 'Updated clCSNAGlobalConfigGroup. Deprecate clCSMIBCompliance and replaced by clCSMIBComplianceRev1. Added clCSNAASIEnable,clCSNADiffSyncEnable,clCSSecTunObjects, clCSSecTunConfig,clCSSecTunInfo,clCSSecTunNotifs.']], ['201702220000Z', ['DESCRIPTION', 'Initial version of config cloud services MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}