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 is used to show and configure High availability (HA) related statistics. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ + + + + + + + CC + + CC + + CC + + + + + + + +......+ +......+ +......+ .. . . .. . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + AP + + AP + + AP + + 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. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. 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, Mobile Station(Ms) and client are used interchangeably. 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.
Status in source: unspecified.
Names: ciscoLwappHaMIB
Technical details
{
"smi_kind": "MODULE-IDENTITY",
"definition": [
"ciscoLwappHaMIB",
"MODULE-IDENTITY",
"LAST-UPDATED",
[
"literal",
"223230323030363037303030305a22"
],
"ORGANIZATION",
"\"Cisco Systems Inc.\"",
"CONTACT-INFO",
"\"Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-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 is used to show and configure High availability (HA) related statistics. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ + + + + + + + CC + + CC + + CC + + + + + + + +......+ +......+ +......+ .. . . .. . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + AP + + AP + + AP + + 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. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. 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, Mobile Station(Ms) and client are used interchangeably. 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.\"",
"REVISION",
[
"literal",
"223230323030363037303030305a22"
],
"DESCRIPTION",
"\"Added Gateway Failover Interval object in (ciscoLwappMcRmiConfig)\"",
"REVISION",
[
"literal",
"223230313930373038303030305a22"
],
"DESCRIPTION",
"\"Added Multi-Chassis RMI configuration objects in (ciscoLwappMcRmiConfig)\"",
"REVISION",
[
"literal",
"223230313731313038303030305a22"
],
"DESCRIPTION",
"\"Added Multi-Chassis HA configuration objects in (ciscoLwappMcHaConfig)\"",
"REVISION",
[
"literal",
"223230313730333134303030305a22"
],
"DESCRIPTION",
"\"Initial version of this MIB module.\"",
"::=",
"{",
"ciscoMgmt",
"843",
"}"
],
"syntax_tree": [
[
"LAST-UPDATED",
"202006070000Z"
],
[
"ORGANIZATION",
"Cisco Systems Inc."
],
[
"CONTACT-INFO",
"Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-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 is used to show and configure High availability (HA) related statistics. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ + + + + + + + CC + + CC + + CC + + + + + + + +......+ +......+ +......+ .. . . .. . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + AP + + AP + + AP + + 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. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. 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, Mobile Station(Ms) and client are used interchangeably. 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."
],
[
"Revisions",
[
[
"202006070000Z",
[
"DESCRIPTION",
"Added Gateway Failover Interval object in (ciscoLwappMcRmiConfig)"
]
],
[
"201907080000Z",
[
"DESCRIPTION",
"Added Multi-Chassis RMI configuration objects in (ciscoLwappMcRmiConfig)"
]
],
[
"201711080000Z",
[
"DESCRIPTION",
"Added Multi-Chassis HA configuration objects in (ciscoLwappMcHaConfig)"
]
],
[
"201703140000Z",
[
"DESCRIPTION",
"Initial version of this MIB module."
]
]
]
]
]
}- Cisco
· Publisher's source file
· Archived source file
Source location: CISCO-LWAPP-HA-MIB::ciscoLwappHaMIB.Source version and references
Downloaded: 2026-10-19T00:18:11.684136+00:00. SHA-256:
7d85d1f4a2d148f2469fb27bd048491e0047714e7c6cc8af336f9bf7505b2016{'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-HA-MIB', 'imports': {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue', 'MacAddress', 'DisplayString', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32', 'Integer32', 'Counter32'], 'RFC1213-MIB': ['sysName'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'NOTIFICATION-GROUP', 'MODULE-COMPLIANCE'], 'CISCO-RF-MIB': ['cRFStatusPeerUnitState', 'cRFStatusUnitState'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappHaMIB MODULE-IDENTITY\n LAST-UPDATED "202006070000Z"\n ORGANIZATION "Cisco Systems Inc."\n CONTACT-INFO\n "Cisco Systems,\n Customer Service\n Postal: 170 West Tasman Drive\n San Jose, CA 95134\n USA\n Tel: +1 800 553-NETS\n\n Email: cs-wnbu-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 is used to show and configure High \n availability (HA) related statistics.\n\n The relationship between CC and the LWAPP APs\n can be depicted as follows:\n\n +......+ +......+ +......+ \n + + + + + + \n + CC + + CC + + CC + \n + + + + + + \n +......+ +......+ +......+ \n .. . . \n .. . . \n . . . . \n . . . . \n . . . . \n . . . . \n +......+ +......+ +......+ +......+ \n + + + + + + + + \n + AP + + AP + + AP + + AP + \n + + + + + + + + \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 Central Controller ( CC )\n\n The central entity that terminates the LWAPP protocol\n tunnel from the LWAPP APs. Throughout this MIB,\n this entity also referred to as \'controller\'. \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 Mobile Station(Ms) and client are used interchangeably. \n\n REFERENCE\n\n [1] Wireless LAN Medium Access Control ( MAC ) and\n Physical Layer ( PHY ) Specifications.\n\n [2] Draft-obara-capwap-lwapp-00.txt, IETF Light \n Weight Access Point Protocol."\n REVISION "202006070000Z"\n DESCRIPTION "Added Gateway Failover Interval object in\n (ciscoLwappMcRmiConfig)"\n REVISION "201907080000Z"\n DESCRIPTION "Added Multi-Chassis RMI configuration objects in\n (ciscoLwappMcRmiConfig)"\n REVISION "201711080000Z"\n DESCRIPTION "Added Multi-Chassis HA configuration objects in\n (ciscoLwappMcHaConfig)"\n REVISION "201703140000Z"\n DESCRIPTION "Initial version of this MIB module."\n ::= { ciscoMgmt 843 }', 'syntax_tree': [['LAST-UPDATED', '202006070000Z'], ['ORGANIZATION', 'Cisco Systems Inc.'], ['CONTACT-INFO', 'Cisco Systems, Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS Email: cs-wnbu-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 is used to show and configure High availability (HA) related statistics. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ + + + + + + + CC + + CC + + CC + + + + + + + +......+ +......+ +......+ .. . . .. . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + AP + + AP + + AP + + 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. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. 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, Mobile Station(Ms) and client are used interchangeably. 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."], ['Revisions', [['202006070000Z', ['DESCRIPTION', 'Added Gateway Failover Interval object in (ciscoLwappMcRmiConfig)']], ['201907080000Z', ['DESCRIPTION', 'Added Multi-Chassis RMI configuration objects in (ciscoLwappMcRmiConfig)']], ['201711080000Z', ['DESCRIPTION', 'Added Multi-Chassis HA configuration objects in (ciscoLwappMcHaConfig)']], ['201703140000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}