This MIB is intended to be implemented on all those devices operating as Wireless LAN Controllers (WLC) that terminate the Light Weight Access Point Protocol tunnel from light weight LWAPP Access Points. This MIB provides configuration and status information about local mobility anchor to which the controller has joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + 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 it to the controller to which it is logically connected. Wireless LAN Controller ( WLC ) 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. Proxy Mobile IP (PMIP) PMIP is a protocol intended for providing network-based IP mobility management support to a mobile node, without requiring the participation of the mobile node in any IP mobility related signaling. The mobility entities in the network will track the mobile node's movements and will initiate the mobility signaling and set up the required routing state. Local Mobility Anchor (LMA) Local Mobility Anchor is the home agent for the mobile node in a Proxy Mobile domain. It is the topological anchor point for the mobile node's home network prefix(es) and is the entity that manages the mobile node's binding state. Network Access Identifier(NAI) The Network Access Identifier (NAI) is the user identity submitted by the client during network access authentication. In roaming, the purpose of the NAI is to identify the user as well as to assist in the routing of the authentication request. Binding Revocation Indication(BRI) Binding Revocation Indication(BRI) is a message sent by either the LMA or the controller to revoke the bindings present. LMA can send a revocation for specific NAI or NAIs belonging to the controller. Binding Revocation Acknowledgement(BRA) When the BRI is received, the responder must send a Binding Revocation Acknowledgement message to indicate the receipt and the status of processing of the corresponding BRI message. Mobile Access Gateway(MAG) Mobile Access Gateway (MAG) performs mobility-related signaling on behalf of the mobile nodes (MN) attached to its access links. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol. [3] PMIPv6 RFC 5213.
Status in source: unspecified.
Names: ciscoLwappPmipMIB
Technical details
{
"smi_kind": "MODULE-IDENTITY",
"definition": [
"ciscoLwappPmipMIB",
"MODULE-IDENTITY",
"LAST-UPDATED",
[
"literal",
"223230313730343238303030305a22"
],
"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-snmp@cisco.com\"",
"DESCRIPTION",
"\"This MIB is intended to be implemented on all those devices operating as Wireless LAN Controllers (WLC) that terminate the Light Weight Access Point Protocol tunnel from light weight LWAPP Access Points. This MIB provides configuration and status information about local mobility anchor to which the controller has joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + 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 it to the controller to which it is logically connected. Wireless LAN Controller ( WLC ) 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. Proxy Mobile IP (PMIP) PMIP is a protocol intended for providing network-based IP mobility management support to a mobile node, without requiring the participation of the mobile node in any IP mobility related signaling. The mobility entities in the network will track the mobile node's movements and will initiate the mobility signaling and set up the required routing state. Local Mobility Anchor (LMA) Local Mobility Anchor is the home agent for the mobile node in a Proxy Mobile domain. It is the topological anchor point for the mobile node's home network prefix(es) and is the entity that manages the mobile node's binding state. Network Access Identifier(NAI) The Network Access Identifier (NAI) is the user identity submitted by the client during network access authentication. In roaming, the purpose of the NAI is to identify the user as well as to assist in the routing of the authentication request. Binding Revocation Indication(BRI) Binding Revocation Indication(BRI) is a message sent by either the LMA or the controller to revoke the bindings present. LMA can send a revocation for specific NAI or NAIs belonging to the controller. Binding Revocation Acknowledgement(BRA) When the BRI is received, the responder must send a Binding Revocation Acknowledgement message to indicate the receipt and the status of processing of the corresponding BRI message. Mobile Access Gateway(MAG) Mobile Access Gateway (MAG) performs mobility-related signaling on behalf of the mobile nodes (MN) attached to its access links. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol. [3] PMIPv6 RFC 5213.\"",
"REVISION",
[
"literal",
"223230313730343238303030305a22"
],
"DESCRIPTION",
"\"Initial version of this MIB module.\"",
"::=",
"{",
"ciscoMgmt",
"845",
"}"
],
"syntax_tree": [
[
"LAST-UPDATED",
"201704280000Z"
],
[
"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-snmp@cisco.com"
],
[
"DESCRIPTION",
"This MIB is intended to be implemented on all those devices operating as Wireless LAN Controllers (WLC) that terminate the Light Weight Access Point Protocol tunnel from light weight LWAPP Access Points. This MIB provides configuration and status information about local mobility anchor to which the controller has joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + 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 it to the controller to which it is logically connected. Wireless LAN Controller ( WLC ) 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. Proxy Mobile IP (PMIP) PMIP is a protocol intended for providing network-based IP mobility management support to a mobile node, without requiring the participation of the mobile node in any IP mobility related signaling. The mobility entities in the network will track the mobile node's movements and will initiate the mobility signaling and set up the required routing state. Local Mobility Anchor (LMA) Local Mobility Anchor is the home agent for the mobile node in a Proxy Mobile domain. It is the topological anchor point for the mobile node's home network prefix(es) and is the entity that manages the mobile node's binding state. Network Access Identifier(NAI) The Network Access Identifier (NAI) is the user identity submitted by the client during network access authentication. In roaming, the purpose of the NAI is to identify the user as well as to assist in the routing of the authentication request. Binding Revocation Indication(BRI) Binding Revocation Indication(BRI) is a message sent by either the LMA or the controller to revoke the bindings present. LMA can send a revocation for specific NAI or NAIs belonging to the controller. Binding Revocation Acknowledgement(BRA) When the BRI is received, the responder must send a Binding Revocation Acknowledgement message to indicate the receipt and the status of processing of the corresponding BRI message. Mobile Access Gateway(MAG) Mobile Access Gateway (MAG) performs mobility-related signaling on behalf of the mobile nodes (MN) attached to its access links. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol. [3] PMIPv6 RFC 5213."
],
[
"Revisions",
[
[
"201704280000Z",
[
"DESCRIPTION",
"Initial version of this MIB module."
]
]
]
]
]
}- Cisco
· Publisher's source file
· Archived source file
Source location: CISCO-LWAPP-PMIP-MIB::ciscoLwappPmipMIB.Source version and references
Downloaded: 2026-10-19T00:18:11.700069+00:00. SHA-256:
676e3320c20f5f4510dfd3a3623171ce0261f9cb71892cd6e4430ecea081d585{'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-PMIP-MIB', 'imports': {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['MacAddress', 'RowStatus', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'TimeTicks'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'CISCO-LWAPP-WLAN-MIB': ['cLWlanIndex'], 'CISCO-LWAPP-DOT11-CLIENT-MIB': ['cldcClientMacAddress']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappPmipMIB MODULE-IDENTITY\n LAST-UPDATED "201704280000Z"\n ORGANIZATION "Cisco Systems Inc."\n CONTACT-INFO\n "Cisco Systems,\n Customer Service\n\n Postal: 170 West Tasman Drive\n San Jose, CA 95134\n USA\n\n Tel: +1 800 553-NETS\n\n Email: cs-snmp@cisco.com"\n DESCRIPTION\n "This MIB is intended to be implemented on all those devices\n operating as Wireless LAN Controllers (WLC) that terminate the \n Light Weight Access Point Protocol tunnel from light weight \n LWAPP Access Points.\n\n This MIB provides configuration and status information about \n local mobility anchor to which the controller has joined.\n\n The relationship between CC and the LWAPP APs can be depicted \n as follows:\n\n +......+ +......+ +......+ +......+\n + + + + + + + +\n + LMA + + LMA + + LMA + + LMA +\n + + + + + + + +\n +......+ +......+ +......+ +......+\n .. . . .\n .. . . .\n . . . . .\n . . . . .\n . . . . .\n . . . . .\n +......+ +......+ +......+ +......+ +......+\n + + + + + + + + + +\n + WLC + + WLC + + WLC + + WLC + + WLC +\n + + + + + + + + + +\n +......+ +......+ +......+ +......+ +......+\n . . . .\n . . . . .\n . . . . .\n . . . . .\n . . . . .\n +......+ +......+ +......+ +......+ +......+\n + + + + + + + + + +\n + AP + + AP + + AP + + AP + + AP +\n + + + + + + + + + +\n +......+ +......+ +......+ +......+ +......+\n . . . .\n . . . . .\n . . . . .\n . . . . .\n . . . . .\n +......+ +......+ +......+ +......+ +......+\n + + + + + + + + + +\n + MN + + MN + + MN + + MN + + MN +\n + + + + + + + + + +\n +......+ +......+ +......+ +......+ +......+\n\n\n The LWAPP tunnel exists between the controller and the APs. The\n MNs communicate with the APs through the protocol defined by \n the 802.11 standard.\n\n LWAPP APs, upon bootup, discover and join one of the \n controllers and the controller pushes the configuration, that \n includes the WLAN parameters, to the LWAPP APs. The APs then \n encapsulate all the 802.11 frames from wireless clients inside \n LWAPP frames and forward 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 control (MAC)\n and physical layer ( PHY ) interface and provides access to the\n distribution services via the wireless medium for associated \n clients. \n\n LWAPP APs encapsulate all the 802.11 frames in LWAPP frames and\n sends it to the controller to which it is logically connected.\n\n Wireless LAN Controller ( WLC )\n\n The central entity that terminates the LWAPP protocol tunnel \n from the LWAPP APs. Throughout this MIB, this entity also \n referred to as \'controller\'. \n\n Light Weight Access Point Protocol ( LWAPP ) \n\n This is a generic protocol that defines the communication \n between the Access Points and the Central Controller. \n\n Mobile Node ( MN )\n\n A roaming 802.11 wireless device in a wireless network \n associated with an access point. \n\n Proxy Mobile IP (PMIP)\n\n PMIP is a protocol intended for providing network-based IP \n mobility management support to a mobile node, without requiring\n the participation of the mobile node in any IP mobility related \n signaling. The mobility entities in the network will track the \n mobile node\'s movements and will initiate the mobility signaling\n and set up the required routing state.\n\n Local Mobility Anchor (LMA)\n\n Local Mobility Anchor is the home agent for the mobile node in \n a Proxy Mobile domain. It is the topological anchor point for \n the mobile node\'s home network prefix(es) and is the entity \n that manages the mobile node\'s binding state.\n\n Network Access Identifier(NAI)\n\n The Network Access Identifier (NAI) is the user identity \n submitted by the client during network access authentication. \n In roaming, the purpose of the NAI is to identify the user as \n well as to assist in the routing of the authentication request. \n\n Binding Revocation Indication(BRI)\n\n Binding Revocation Indication(BRI) is a message sent by \n either the LMA or the controller to revoke the bindings present.\n LMA can send a revocation for specific NAI or NAIs belonging to \n the controller.\n\n Binding Revocation Acknowledgement(BRA)\n\n When the BRI is received, the responder must send a Binding \n Revocation Acknowledgement message to indicate the receipt and \n the status of processing of the corresponding BRI message.\n \n Mobile Access Gateway(MAG)\n \n Mobile Access Gateway (MAG) performs mobility-related\n signaling on behalf of the mobile nodes (MN) attached \n to its access links. \n\n REFERENCE\n\n [1] Part 11 Wireless LAN Medium Access Control ( MAC )\n and Physical Layer ( PHY ) Specifications.\n\n [2] Draft-obara-capwap-lwapp-00.txt, IETF Light \n Weight Access Point Protocol.\n \n [3] PMIPv6 RFC 5213."\n \n \n REVISION "201704280000Z"\n DESCRIPTION\n "Initial version of this MIB module."\n ::= { ciscoMgmt 845 }', 'syntax_tree': [['LAST-UPDATED', '201704280000Z'], ['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-snmp@cisco.com'], ['DESCRIPTION', "This MIB is intended to be implemented on all those devices operating as Wireless LAN Controllers (WLC) that terminate the Light Weight Access Point Protocol tunnel from light weight LWAPP Access Points. This MIB provides configuration and status information about local mobility anchor to which the controller has joined. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + LMA + + LMA + + LMA + + LMA + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + WLC + + WLC + + WLC + + WLC + + WLC + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + AP + + AP + + AP + + AP + + AP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MN + + 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 it to the controller to which it is logically connected. Wireless LAN Controller ( WLC ) 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. Proxy Mobile IP (PMIP) PMIP is a protocol intended for providing network-based IP mobility management support to a mobile node, without requiring the participation of the mobile node in any IP mobility related signaling. The mobility entities in the network will track the mobile node's movements and will initiate the mobility signaling and set up the required routing state. Local Mobility Anchor (LMA) Local Mobility Anchor is the home agent for the mobile node in a Proxy Mobile domain. It is the topological anchor point for the mobile node's home network prefix(es) and is the entity that manages the mobile node's binding state. Network Access Identifier(NAI) The Network Access Identifier (NAI) is the user identity submitted by the client during network access authentication. In roaming, the purpose of the NAI is to identify the user as well as to assist in the routing of the authentication request. Binding Revocation Indication(BRI) Binding Revocation Indication(BRI) is a message sent by either the LMA or the controller to revoke the bindings present. LMA can send a revocation for specific NAI or NAIs belonging to the controller. Binding Revocation Acknowledgement(BRA) When the BRI is received, the responder must send a Binding Revocation Acknowledgement message to indicate the receipt and the status of processing of the corresponding BRI message. Mobile Access Gateway(MAG) Mobile Access Gateway (MAG) performs mobility-related signaling on behalf of the mobile nodes (MN) attached to its access links. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications. [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol. [3] PMIPv6 RFC 5213."], ['Revisions', [['201704280000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}