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 Light-weight LWAPP Access Points. This MIB provides configuration and status information about the 802.11 WLAN mobility. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. Basic Service Set Identifier (BSSID) The identifier for the service set comprising of all the 802.11 stations under the control of one coordinating Access Point. This identifier happens to be the MAC address of the dot11 radio interface of the Access Point. The wireless clients that associate with the Access Point get the wired uplink through this particular dot11 interface. 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. Mobility Oracle (MO) When a Central Controller in the Mobility Group is designated as Mobility Oracle, then all the Mobility Controller's (MC) traffic is tunnelled to it by other Mobility Controllers. Currently, MO resides along with MC but MC can reside in a box without MO. Mobility Controller (MC) When a Central Controller in the Mobility Group is designated as Mobility Controller, then all the Mobile Anchor's traffic is tunnelled to it by other Anchors. Each MC has its own/self mobility agent (MA), but MA can reside in a box without MC. Mobility Agent (MA) The Mobility Agent is an entity residing on the access switch that manages mobility events on the switch, and communicates with the Mobility Controller. Access Points can associate directly with MA. Wireless LAN Controller (WLC) Wireless LAN Controller are legacy mobility device which can participate in the new mobility architecture. Mobility Manager The Mobility Manager is the management entity in a mobility controller or mobility agent. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Anchor MC, Anchor MA Anchor MC or Anchor MA is the mobility entity where a mobile client was first anchored or associated. This is equivalent to home agent (HA). Associated MC, Associated MA Associated MC or Associated MA is the mobility entity where a mobile client roamed and get associated. This is equivalent to foreign agent (FA). It can be local or remote. Mobility Concept by which a Mobile Node can roam from one Access Point to another Access Point, across multiple Central Controllers, without need for repeated authentication. Mobility Group A set of Central Controllers which exchange Mobile Node's authentication information, so that the Mobile Node upon roaming need not re-authenticate. Switch Peer Group (SPG) A set of mobility agents (MAs) form a Switch Peer Group. One or more SPGs are associated with one mobility controller (MC). Traffic between mobility agents within a SPG group goes directly between them - not through their associated MC Mobility Anchor When a Central Controller in the Mobility Group is designated as Mobility Anchor, then all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Guest Tunneling (GT) The concept of designating a Central Controller in the Mobility Group as Mobility Anchor, so that all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Station Management (SMT) This term refers to the internal management of the 802.11 protocol operations by the AP to work cooperatively with the other APs and 802.11 devices in the network. Ethernet over Internet Protocol (EoIP) Ethernet over IP (EoIP) is a protocol that creates an Ethernet tunnel between two routers on top of an IP connection. The EoIP interface appears as an Ethernet interface. Reverse path filtering (RPF) Reverse path filtering (RPF) is a feature provided by most modern Internet Protocol routers, which may be used to reduce the risk of customers attacking other internet hosts. One of the problems network service providers face today is hackers generating packets with fake source IP addresses, a technique known as spoofing. This is often done in order to initiate a denial-of-service attack against another internet host or network. Since the source IP addresses of the incoming packets change, often randomly, and for every packet, the target of such an attack can't easily filter out the attacking packets. However, the source of the attack, i.e. the network service provider of the attacking host, has a simple way to stop such packets from ever leaving its network. A router always knows which networks are reachable via any of its interfaces. By checking the source IP address of all packets coming in via an interface against the networks known to be behind that interface, the router can simply drop packets that aren't supposed to come from there. Hence, reverse path filtering filters packets according to the 'reverse path' to their source IP address. If the path back to the source IP address does not match the path the packet is coming from, it is dropped. 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.
Status in source: unspecified.
Names: ciscoLwappMobilityExtMIB
Technical details
{
"smi_kind": "MODULE-IDENTITY",
"definition": [
"ciscoLwappMobilityExtMIB",
"MODULE-IDENTITY",
"LAST-UPDATED",
[
"literal",
"223230323030383133303030305a22"
],
"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 Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the 802.11 WLAN mobility. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. Basic Service Set Identifier (BSSID) The identifier for the service set comprising of all the 802.11 stations under the control of one coordinating Access Point. This identifier happens to be the MAC address of the dot11 radio interface of the Access Point. The wireless clients that associate with the Access Point get the wired uplink through this particular dot11 interface. 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. Mobility Oracle (MO) When a Central Controller in the Mobility Group is designated as Mobility Oracle, then all the Mobility Controller's (MC) traffic is tunnelled to it by other Mobility Controllers. Currently, MO resides along with MC but MC can reside in a box without MO. Mobility Controller (MC) When a Central Controller in the Mobility Group is designated as Mobility Controller, then all the Mobile Anchor's traffic is tunnelled to it by other Anchors. Each MC has its own/self mobility agent (MA), but MA can reside in a box without MC. Mobility Agent (MA) The Mobility Agent is an entity residing on the access switch that manages mobility events on the switch, and communicates with the Mobility Controller. Access Points can associate directly with MA. Wireless LAN Controller (WLC) Wireless LAN Controller are legacy mobility device which can participate in the new mobility architecture. Mobility Manager The Mobility Manager is the management entity in a mobility controller or mobility agent. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Anchor MC, Anchor MA Anchor MC or Anchor MA is the mobility entity where a mobile client was first anchored or associated. This is equivalent to home agent (HA). Associated MC, Associated MA Associated MC or Associated MA is the mobility entity where a mobile client roamed and get associated. This is equivalent to foreign agent (FA). It can be local or remote. Mobility Concept by which a Mobile Node can roam from one Access Point to another Access Point, across multiple Central Controllers, without need for repeated authentication. Mobility Group A set of Central Controllers which exchange Mobile Node's authentication information, so that the Mobile Node upon roaming need not re-authenticate. Switch Peer Group (SPG) A set of mobility agents (MAs) form a Switch Peer Group. One or more SPGs are associated with one mobility controller (MC). Traffic between mobility agents within a SPG group goes directly between them - not through their associated MC Mobility Anchor When a Central Controller in the Mobility Group is designated as Mobility Anchor, then all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Guest Tunneling (GT) The concept of designating a Central Controller in the Mobility Group as Mobility Anchor, so that all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Station Management (SMT) This term refers to the internal management of the 802.11 protocol operations by the AP to work cooperatively with the other APs and 802.11 devices in the network. Ethernet over Internet Protocol (EoIP) Ethernet over IP (EoIP) is a protocol that creates an Ethernet tunnel between two routers on top of an IP connection. The EoIP interface appears as an Ethernet interface. Reverse path filtering (RPF) Reverse path filtering (RPF) is a feature provided by most modern Internet Protocol routers, which may be used to reduce the risk of customers attacking other internet hosts. One of the problems network service providers face today is hackers generating packets with fake source IP addresses, a technique known as spoofing. This is often done in order to initiate a denial-of-service attack against another internet host or network. Since the source IP addresses of the incoming packets change, often randomly, and for every packet, the target of such an attack can't easily filter out the attacking packets. However, the source of the attack, i.e. the network service provider of the attacking host, has a simple way to stop such packets from ever leaving its network. A router always knows which networks are reachable via any of its interfaces. By checking the source IP address of all packets coming in via an interface against the networks known to be behind that interface, the router can simply drop packets that aren't supposed to come from there. Hence, reverse path filtering filters packets according to the 'reverse path' to their source IP address. If the path back to the source IP address does not match the path the packet is coming from, it is dropped. 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.\"",
"REVISION",
[
"literal",
"223230323030383133303030305a22"
],
"DESCRIPTION",
"\" Added cLGuestWlanAllAnchorsDown cLGuestWlanOneAnchorOnGuestLanUp notification\"",
"REVISION",
[
"literal",
"223230313930363230303030305a22"
],
"DESCRIPTION",
"\" Added C9800-specific attributes.\"",
"REVISION",
[
"literal",
"223230313730353032303030305a22"
],
"DESCRIPTION",
"\"Initial version of this MIB module.\"",
"::=",
"{",
"ciscoMgmt",
"846",
"}"
],
"syntax_tree": [
[
"LAST-UPDATED",
"202008130000Z"
],
[
"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 Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the 802.11 WLAN mobility. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. Basic Service Set Identifier (BSSID) The identifier for the service set comprising of all the 802.11 stations under the control of one coordinating Access Point. This identifier happens to be the MAC address of the dot11 radio interface of the Access Point. The wireless clients that associate with the Access Point get the wired uplink through this particular dot11 interface. 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. Mobility Oracle (MO) When a Central Controller in the Mobility Group is designated as Mobility Oracle, then all the Mobility Controller's (MC) traffic is tunnelled to it by other Mobility Controllers. Currently, MO resides along with MC but MC can reside in a box without MO. Mobility Controller (MC) When a Central Controller in the Mobility Group is designated as Mobility Controller, then all the Mobile Anchor's traffic is tunnelled to it by other Anchors. Each MC has its own/self mobility agent (MA), but MA can reside in a box without MC. Mobility Agent (MA) The Mobility Agent is an entity residing on the access switch that manages mobility events on the switch, and communicates with the Mobility Controller. Access Points can associate directly with MA. Wireless LAN Controller (WLC) Wireless LAN Controller are legacy mobility device which can participate in the new mobility architecture. Mobility Manager The Mobility Manager is the management entity in a mobility controller or mobility agent. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Anchor MC, Anchor MA Anchor MC or Anchor MA is the mobility entity where a mobile client was first anchored or associated. This is equivalent to home agent (HA). Associated MC, Associated MA Associated MC or Associated MA is the mobility entity where a mobile client roamed and get associated. This is equivalent to foreign agent (FA). It can be local or remote. Mobility Concept by which a Mobile Node can roam from one Access Point to another Access Point, across multiple Central Controllers, without need for repeated authentication. Mobility Group A set of Central Controllers which exchange Mobile Node's authentication information, so that the Mobile Node upon roaming need not re-authenticate. Switch Peer Group (SPG) A set of mobility agents (MAs) form a Switch Peer Group. One or more SPGs are associated with one mobility controller (MC). Traffic between mobility agents within a SPG group goes directly between them - not through their associated MC Mobility Anchor When a Central Controller in the Mobility Group is designated as Mobility Anchor, then all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Guest Tunneling (GT) The concept of designating a Central Controller in the Mobility Group as Mobility Anchor, so that all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Station Management (SMT) This term refers to the internal management of the 802.11 protocol operations by the AP to work cooperatively with the other APs and 802.11 devices in the network. Ethernet over Internet Protocol (EoIP) Ethernet over IP (EoIP) is a protocol that creates an Ethernet tunnel between two routers on top of an IP connection. The EoIP interface appears as an Ethernet interface. Reverse path filtering (RPF) Reverse path filtering (RPF) is a feature provided by most modern Internet Protocol routers, which may be used to reduce the risk of customers attacking other internet hosts. One of the problems network service providers face today is hackers generating packets with fake source IP addresses, a technique known as spoofing. This is often done in order to initiate a denial-of-service attack against another internet host or network. Since the source IP addresses of the incoming packets change, often randomly, and for every packet, the target of such an attack can't easily filter out the attacking packets. However, the source of the attack, i.e. the network service provider of the attacking host, has a simple way to stop such packets from ever leaving its network. A router always knows which networks are reachable via any of its interfaces. By checking the source IP address of all packets coming in via an interface against the networks known to be behind that interface, the router can simply drop packets that aren't supposed to come from there. Hence, reverse path filtering filters packets according to the 'reverse path' to their source IP address. If the path back to the source IP address does not match the path the packet is coming from, it is dropped. 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."
],
[
"Revisions",
[
[
"202008130000Z",
[
"DESCRIPTION",
"Added cLGuestWlanAllAnchorsDown cLGuestWlanOneAnchorOnGuestLanUp notification"
]
],
[
"201906200000Z",
[
"DESCRIPTION",
"Added C9800-specific attributes."
]
],
[
"201705020000Z",
[
"DESCRIPTION",
"Initial version of this MIB module."
]
]
]
]
]
}- Cisco
· Publisher's source file
· Archived source file
Source location: CISCO-LWAPP-MOBILITY-EXT-MIB::ciscoLwappMobilityExtMIB.Source version and references
Downloaded: 2026-10-19T00:18:11.696854+00:00. SHA-256:
d12132b9278e9ba2f7c374139d73a75648a61e04c2a7e9d63085df9b1a78f6cb{'kind': 'MODULE-IDENTITY', 'details': {'module': 'CISCO-LWAPP-MOBILITY-EXT-MIB', 'imports': {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'MacAddress', 'DateAndTime', 'TruthValue', 'RowStatus', 'StorageType'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32', 'Counter32', 'Counter64'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanIndex'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'CISCO-QOS-PIB-MIB': ['Dscp'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'CISCO-LWAPP-WLAN-MIB': ['cLWlanIndex', 'cLWlanProfileName'], 'CISCO-LWAPP-WLAN-POLICY-MIB': ['cLWlanWlanPolicyName']}, 'smi_kind': 'MODULE-IDENTITY', 'definition': 'ciscoLwappMobilityExtMIB MODULE-IDENTITY\n LAST-UPDATED "202008130000Z"\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\n devices operating as Central Controllers (CC) that\n terminate the Light Weight Access Point Protocol\n tunnel from Light-weight LWAPP Access Points.\n\n This MIB provides configuration and status information\n about the 802.11 WLAN mobility. \n\n The relationship between CC and the LWAPP APs\n can be depicted as follows:\n\n\n +......+ +......+ +......+ +......+\n + + + + + + + +\n + CC + + CC + + CC + + CC +\n + + + + + + + +\n +......+ +......+ +......+ +......+\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 . . . . .\n +......+ +......+ +......+ +......+ \n +......+\n + + + + + + + + + \n +\n + MN + + MN + + MN + + MN + + MN \n +\n + + + + + + + + + \n +\n +......+ +......+ +......+ +......+ \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\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\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\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 it to the controller to which\n it is logically connected.\n\n\n Basic Service Set Identifier (BSSID)\n\n The identifier for the service set comprising of\n all the 802.11 stations under the control of\n one coordinating Access Point. This identifier\n happens to be the MAC address of the dot11 radio\n interface of the Access Point. The wireless\n clients that associate with the Access Point\n get the wired uplink through this particular \n dot11 interface. \n\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\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\n Mobility Oracle (MO)\n\n When a Central Controller in the Mobility Group is \n designated as Mobility Oracle, then all the Mobility \n Controller\'s (MC) traffic is tunnelled to it by other\n Mobility Controllers. Currently, MO resides along with MC\n but MC can reside in a box without MO.\n\n\n Mobility Controller (MC)\n\n When a Central Controller in the Mobility Group is \n designated as Mobility Controller, then all the Mobile \n Anchor\'s traffic is tunnelled to it by other Anchors.\n Each MC has its own/self mobility agent (MA), but MA can\n reside in a box without MC.\n\n\n Mobility Agent (MA)\n\n The Mobility Agent is an entity residing on the access \n switch that manages mobility events on the switch, and \n communicates with the Mobility Controller. Access Points\n can associate directly with MA.\n\n\n Wireless LAN Controller (WLC)\n\n Wireless LAN Controller are legacy mobility device which \n can participate in the new mobility architecture.\n\n\n Mobility Manager\n\n The Mobility Manager is the management entity in a mobility\n controller or mobility agent.\n\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\n Anchor MC, Anchor MA\n\n Anchor MC or Anchor MA is the mobility entity where a mobile\n client was first anchored or associated. This is equivalent \n to home agent (HA).\n\n\n Associated MC, Associated MA\n\n Associated MC or Associated MA is the mobility entity where \n a mobile client roamed and get associated. This is equivalent\n to foreign agent (FA). It can be local or remote.\n\n\n Mobility \n\n Concept by which a Mobile Node can roam from one \n Access Point to another Access Point, across multiple\n Central Controllers, without need for repeated \n authentication. \n\n\n Mobility Group\n\n A set of Central Controllers which exchange Mobile \n Node\'s authentication information, so that the Mobile\n Node upon roaming need not re-authenticate. \n\n\n Switch Peer Group (SPG)\n\n A set of mobility agents (MAs) form a Switch Peer Group.\n One or more SPGs are associated with one mobility \n controller (MC). Traffic between mobility agents within\n a SPG group goes directly between them - not through their\n associated MC\n\n\n Mobility Anchor\n\n When a Central Controller in the Mobility Group is \n designated as Mobility Anchor, then all the Mobile \n Node\'s traffic is tunnelled to it by other\n Controllers in the Mobility Group.\n\n\n Guest Tunneling (GT)\n\n The concept of designating a Central Controller in \n the Mobility Group as Mobility Anchor, so that all\n the Mobile Node\'s traffic is tunnelled to it by other\n Controllers in the Mobility Group. \n\n\n Station Management (SMT)\n\n This term refers to the internal management of the\n 802.11 protocol operations by the AP to work\n cooperatively with the other APs and 802.11\n devices in the network.\n\n\n Ethernet over Internet Protocol (EoIP)\n\n Ethernet over IP (EoIP) is a protocol that creates \n an Ethernet tunnel between two routers on top of an\n IP connection. The EoIP interface appears as an \n Ethernet interface.\n\n\n Reverse path filtering (RPF) \n\n Reverse path filtering (RPF) is a feature provided\n by most modern Internet Protocol routers, which may\n be used to reduce the risk of customers attacking\n other internet hosts. One of the problems network\n service providers face today is hackers generating\n packets with fake source IP addresses, a technique\n known as spoofing. This is often done in order to\n initiate a denial-of-service attack against another\n internet host or network.\n Since the source IP addresses of the incoming packets\n change, often randomly, and for every packet, the\n target of such an attack can\'t easily filter out the\n attacking packets. However, the source of the attack,\n i.e. the network service provider of the attacking \n host, has a simple way to stop such packets from ever\n leaving its network. A router always knows which \n networks are reachable via any of its interfaces. \n\n By checking the source IP address of all packets \n coming in via an interface against the networks known\n to be behind that interface, the router can simply \n drop packets that aren\'t supposed to come from there.\n\n Hence, reverse path filtering filters packets \n according to the \'reverse path\' to their source \n IP address. If the path back to the source IP address \n does not match the path the packet is coming from,\n it is dropped.\n\n REFERENCE\n\n [1] Part 11 Wireless LAN Medium Access Control ( MAC )\n and Physical Layer ( PHY ) Specifications.\n\n\n [2] Draft-obara-capwap-lwapp-00.txt, IETF Light \n Weight Access Point Protocol."\n REVISION "202008130000Z"\n DESCRIPTION\n " Added cLGuestWlanAllAnchorsDown\n cLGuestWlanOneAnchorOnGuestLanUp notification"\n REVISION "201906200000Z"\n DESCRIPTION\n " Added C9800-specific attributes."\n REVISION "201705020000Z"\n DESCRIPTION\n "Initial version of this MIB module."\n ::= { ciscoMgmt 846 }', 'syntax_tree': [['LAST-UPDATED', '202008130000Z'], ['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 Central Controllers (CC) that terminate the Light Weight Access Point Protocol tunnel from Light-weight LWAPP Access Points. This MIB provides configuration and status information about the 802.11 WLAN mobility. The relationship between CC and the LWAPP APs can be depicted as follows: +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + 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. Basic Service Set Identifier (BSSID) The identifier for the service set comprising of all the 802.11 stations under the control of one coordinating Access Point. This identifier happens to be the MAC address of the dot11 radio interface of the Access Point. The wireless clients that associate with the Access Point get the wired uplink through this particular dot11 interface. 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. Mobility Oracle (MO) When a Central Controller in the Mobility Group is designated as Mobility Oracle, then all the Mobility Controller's (MC) traffic is tunnelled to it by other Mobility Controllers. Currently, MO resides along with MC but MC can reside in a box without MO. Mobility Controller (MC) When a Central Controller in the Mobility Group is designated as Mobility Controller, then all the Mobile Anchor's traffic is tunnelled to it by other Anchors. Each MC has its own/self mobility agent (MA), but MA can reside in a box without MC. Mobility Agent (MA) The Mobility Agent is an entity residing on the access switch that manages mobility events on the switch, and communicates with the Mobility Controller. Access Points can associate directly with MA. Wireless LAN Controller (WLC) Wireless LAN Controller are legacy mobility device which can participate in the new mobility architecture. Mobility Manager The Mobility Manager is the management entity in a mobility controller or mobility agent. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Anchor MC, Anchor MA Anchor MC or Anchor MA is the mobility entity where a mobile client was first anchored or associated. This is equivalent to home agent (HA). Associated MC, Associated MA Associated MC or Associated MA is the mobility entity where a mobile client roamed and get associated. This is equivalent to foreign agent (FA). It can be local or remote. Mobility Concept by which a Mobile Node can roam from one Access Point to another Access Point, across multiple Central Controllers, without need for repeated authentication. Mobility Group A set of Central Controllers which exchange Mobile Node's authentication information, so that the Mobile Node upon roaming need not re-authenticate. Switch Peer Group (SPG) A set of mobility agents (MAs) form a Switch Peer Group. One or more SPGs are associated with one mobility controller (MC). Traffic between mobility agents within a SPG group goes directly between them - not through their associated MC Mobility Anchor When a Central Controller in the Mobility Group is designated as Mobility Anchor, then all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Guest Tunneling (GT) The concept of designating a Central Controller in the Mobility Group as Mobility Anchor, so that all the Mobile Node's traffic is tunnelled to it by other Controllers in the Mobility Group. Station Management (SMT) This term refers to the internal management of the 802.11 protocol operations by the AP to work cooperatively with the other APs and 802.11 devices in the network. Ethernet over Internet Protocol (EoIP) Ethernet over IP (EoIP) is a protocol that creates an Ethernet tunnel between two routers on top of an IP connection. The EoIP interface appears as an Ethernet interface. Reverse path filtering (RPF) Reverse path filtering (RPF) is a feature provided by most modern Internet Protocol routers, which may be used to reduce the risk of customers attacking other internet hosts. One of the problems network service providers face today is hackers generating packets with fake source IP addresses, a technique known as spoofing. This is often done in order to initiate a denial-of-service attack against another internet host or network. Since the source IP addresses of the incoming packets change, often randomly, and for every packet, the target of such an attack can't easily filter out the attacking packets. However, the source of the attack, i.e. the network service provider of the attacking host, has a simple way to stop such packets from ever leaving its network. A router always knows which networks are reachable via any of its interfaces. By checking the source IP address of all packets coming in via an interface against the networks known to be behind that interface, the router can simply drop packets that aren't supposed to come from there. Hence, reverse path filtering filters packets according to the 'reverse path' to their source IP address. If the path back to the source IP address does not match the path the packet is coming from, it is dropped. 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."], ['Revisions', [['202008130000Z', ['DESCRIPTION', 'Added cLGuestWlanAllAnchorsDown cLGuestWlanOneAnchorOnGuestLanUp notification']], ['201906200000Z', ['DESCRIPTION', 'Added C9800-specific attributes.']], ['201705020000Z', ['DESCRIPTION', 'Initial version of this MIB module.']]]]], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4'}