This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information represented by this MIB is passed by the controller to those Cisco LWAPP APs, that can operate in stand-alone mode. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + EWLC + + EWLC + + EWLC + + EWLC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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 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 is 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. Native VLAN ID A switch port and/or AP can be configured with a 'native VLAN ID'. Untagged or priority-tagged frames are implicitly associated with the native VLAN ID. The default native VLAN ID is '1' if VLAN tagging is enabled. The native VLAN ID is '0' or 'no VLAN ID' if VLAN tagging is not enabled. Remote Edge Access Point ( REAP ) The LWAPP AP that can also act as a stand-alone AP when it loses communication with the controller it was associated with. When REAP can reach the controller (connected state), it gets help from controller to complete client authentication. When a controller is not reachable by REAP, it goes into standalone state and does client authentication by itself. All data packets from clients are either bridged locally (local-switch) or forwarded to the controller (central-switch) depending on the WLAN configuration. Virtual LAN VLAN defined in the IEEE 802.1Q VLAN standard supports logically segmenting of LAN infrastructure into different subnets or workgroups so that packets are switched only between ports within the same VLAN. VLAN ID Each VLAN is identified by a 12-bit 'VLAN ID'. A VLAN ID of '0' is used to indicate 'no VLAN ID'. Valid VLAN IDs range from '1' to '4095'. Home AP A REAP AP can be installed at end-user home. Home AP ethernet port will be connected to DSL or cable modem at home. Home AP will be primed with Controller IP Address so that it will join with controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications
Status in source: unspecified.
Names: ciscoLwappTagsMIB
Technical details
{
"smi_kind": "MODULE-IDENTITY",
"definition": [
"ciscoLwappTagsMIB",
"MODULE-IDENTITY",
"LAST-UPDATED",
[
"literal",
"223230313830393230303030305a22"
],
"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 (CC) that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information represented by this MIB is passed by the controller to those Cisco LWAPP APs, that can operate in stand-alone mode. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + EWLC + + EWLC + + EWLC + + EWLC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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 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 is 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. Native VLAN ID A switch port and/or AP can be configured with a 'native VLAN ID'. Untagged or priority-tagged frames are implicitly associated with the native VLAN ID. The default native VLAN ID is '1' if VLAN tagging is enabled. The native VLAN ID is '0' or 'no VLAN ID' if VLAN tagging is not enabled. Remote Edge Access Point ( REAP ) The LWAPP AP that can also act as a stand-alone AP when it loses communication with the controller it was associated with. When REAP can reach the controller (connected state), it gets help from controller to complete client authentication. When a controller is not reachable by REAP, it goes into standalone state and does client authentication by itself. All data packets from clients are either bridged locally (local-switch) or forwarded to the controller (central-switch) depending on the WLAN configuration. Virtual LAN VLAN defined in the IEEE 802.1Q VLAN standard supports logically segmenting of LAN infrastructure into different subnets or workgroups so that packets are switched only between ports within the same VLAN. VLAN ID Each VLAN is identified by a 12-bit 'VLAN ID'. A VLAN ID of '0' is used to indicate 'no VLAN ID'. Valid VLAN IDs range from '1' to '4095'. Home AP A REAP AP can be installed at end-user home. Home AP ethernet port will be connected to DSL or cable modem at home. Home AP will be primed with Controller IP Address so that it will join with controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications\"",
"REVISION",
[
"literal",
"223230313830393230303030305a22"
],
"DESCRIPTION",
"\"Initial version of this MIB module.\"",
"::=",
"{",
"ciscoMgmt",
"987",
"}"
],
"syntax_tree": [
[
"LAST-UPDATED",
"201809200000Z"
],
[
"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 (CC) that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information represented by this MIB is passed by the controller to those Cisco LWAPP APs, that can operate in stand-alone mode. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + EWLC + + EWLC + + EWLC + + EWLC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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 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 is 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. Native VLAN ID A switch port and/or AP can be configured with a 'native VLAN ID'. Untagged or priority-tagged frames are implicitly associated with the native VLAN ID. The default native VLAN ID is '1' if VLAN tagging is enabled. The native VLAN ID is '0' or 'no VLAN ID' if VLAN tagging is not enabled. Remote Edge Access Point ( REAP ) The LWAPP AP that can also act as a stand-alone AP when it loses communication with the controller it was associated with. When REAP can reach the controller (connected state), it gets help from controller to complete client authentication. When a controller is not reachable by REAP, it goes into standalone state and does client authentication by itself. All data packets from clients are either bridged locally (local-switch) or forwarded to the controller (central-switch) depending on the WLAN configuration. Virtual LAN VLAN defined in the IEEE 802.1Q VLAN standard supports logically segmenting of LAN infrastructure into different subnets or workgroups so that packets are switched only between ports within the same VLAN. VLAN ID Each VLAN is identified by a 12-bit 'VLAN ID'. A VLAN ID of '0' is used to indicate 'no VLAN ID'. Valid VLAN IDs range from '1' to '4095'. Home AP A REAP AP can be installed at end-user home. Home AP ethernet port will be connected to DSL or cable modem at home. Home AP will be primed with Controller IP Address so that it will join with controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications"
],
[
"Revisions",
[
[
"201809200000Z",
[
"DESCRIPTION",
"Initial version of this MIB module."
]
]
]
]
]
}- Cisco
· Publisher's source file
· Archived source file
Source location: CISCO-LWAPP-EWLC-TAGS-MIB::ciscoLwappTagsMIB.Source version and references
Downloaded: 2026-10-19T00:18:11.710778+00:00. SHA-256:
8b46012fa91015f04bcc1a1ad9bb76d9fc8c807aa06886eeea26774b70a0a2e5{'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-EWLC-TAGS-MIB', 'imports': {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappTagsMIB MODULE-IDENTITY\n LAST-UPDATED "201809200000Z"\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\n Tel: +1 800 553-NETS\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 (CC) that\n terminate the Light Weight Access Point Protocol\n tunnel from Cisco Light-weight LWAPP Access Points.\n\n Information represented by this MIB is \n passed by the controller to those Cisco LWAPP APs, that can\n operate in stand-alone mode.\n\n The relationship between CC and the LWAPP APs can be depicted\n as follows:\n\n +......+ +......+ +......+ +......+\n + + + + + + + +\n + EWLC + + EWLC + + EWLC + + EWLC +\n + + + + + + + +\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\n and 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 is 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. \n\n Native VLAN ID\n\n A switch port and/or AP can be configured with a\n \'native VLAN ID\'. Untagged or priority-tagged\n frames are implicitly associated with the native\n VLAN ID. The default native VLAN ID is \'1\' if\n VLAN tagging is enabled. The native VLAN ID is \'0\'\n or \'no VLAN ID\' if VLAN tagging is not enabled. \n\n Remote Edge Access Point ( REAP ) \n\n The LWAPP AP that can also act as a stand-alone AP\n when it loses communication with the controller\n it was associated with. \n\n When REAP can reach the controller (connected state),\n it gets help from controller to complete client\n authentication. When a controller is not reachable by\n REAP, it goes into standalone state and does client\n authentication by itself. All data packets from\n clients are either bridged locally (local-switch)\n or forwarded to the controller (central-switch)\n depending on the WLAN configuration. \n\n Virtual LAN \n\n VLAN defined in the IEEE 802.1Q VLAN standard\n supports logically segmenting of LAN\n infrastructure into different subnets or\n workgroups so that packets are switched only\n between ports within the same VLAN. \n\n VLAN ID\n\n Each VLAN is identified by a 12-bit \'VLAN ID\'.\n A VLAN ID of \'0\' is used to indicate \'no VLAN ID\'.\n Valid VLAN IDs range from \'1\' to \'4095\'. \n\n Home AP \n A REAP AP can be installed at end-user home. Home \n AP ethernet port will be connected to DSL or cable\n modem at home. Home AP will be primed with Controller\n IP Address so that it will join with controller. \n\n REFERENCE\n [1] Part 11 Wireless LAN Medium Access Control ( MAC )\n and Physical Layer ( PHY ) Specifications"\n REVISION "201809200000Z"\n DESCRIPTION\n "Initial version of this MIB module."\n ::= { ciscoMgmt 987 }', 'syntax_tree': [['LAST-UPDATED', '201809200000Z'], ['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 (CC) that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. Information represented by this MIB is passed by the controller to those Cisco LWAPP APs, that can operate in stand-alone mode. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + EWLC + + EWLC + + EWLC + + EWLC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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 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 is 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. Native VLAN ID A switch port and/or AP can be configured with a 'native VLAN ID'. Untagged or priority-tagged frames are implicitly associated with the native VLAN ID. The default native VLAN ID is '1' if VLAN tagging is enabled. The native VLAN ID is '0' or 'no VLAN ID' if VLAN tagging is not enabled. Remote Edge Access Point ( REAP ) The LWAPP AP that can also act as a stand-alone AP when it loses communication with the controller it was associated with. When REAP can reach the controller (connected state), it gets help from controller to complete client authentication. When a controller is not reachable by REAP, it goes into standalone state and does client authentication by itself. All data packets from clients are either bridged locally (local-switch) or forwarded to the controller (central-switch) depending on the WLAN configuration. Virtual LAN VLAN defined in the IEEE 802.1Q VLAN standard supports logically segmenting of LAN infrastructure into different subnets or workgroups so that packets are switched only between ports within the same VLAN. VLAN ID Each VLAN is identified by a 12-bit 'VLAN ID'. A VLAN ID of '0' is used to indicate 'no VLAN ID'. Valid VLAN IDs range from '1' to '4095'. Home AP A REAP AP can be installed at end-user home. Home AP ethernet port will be connected to DSL or cable modem at home. Home AP will be primed with Controller IP Address so that it will join with controller. REFERENCE [1] Part 11 Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications"], ['Revisions', [['201809200000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}