CISCO-LWAPP-MOBILITY-EXT-MIB: View SNMP OID List / Download MIB

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.

This notification is sent by the agent when a mobility control path goes down.

This notification is sent by the agent when a mobility control path goes up.

This notification is sent by the agent when a mobility data path goes down.

This notification is sent by the agent when a mobility data path goes up.

This object represents the current status of the Mobility Oracle (MO). A value of 'true' indicates Mobility Oracle is enabled. A value of 'false' indicates Mobility Oracle (MO) is disabled.

This object allows the user to enable or disable MO mode. A value of 'true' indicates both Mobility Oracle (MO) is enabled. A value of 'false' indicates Mobility Oracle (MO) is disabled. Please note that cLMobilityExtMOEnableStatus (operational value) can be false even if cLMobilityExtMOAdminEnableStatus is true.

This object represents the current status of Mobility Controller (MC). The controller can operate either in MC/MA or MA only mode. A value of 'true' indicates both Mobility Controller (MC) is enabled. A value of 'false' indicates Mobility Controller (MC) is disabled.

This object allows the user to enable or disable MC mode. The controller can operate either in MC/MA or MA only mode. A value of 'true' indicates both Mobility Controller (MC) is enabled. A value of 'false' indicates Mobility Controller (MC) is disabled. Please note that cLMobilityExtMCEnableStatus (operational value) can be false even if cLMobilityExtMCAdminEnableStatus is true.

This object allows the user to enable or disable multicast mode. A value of 'true' indicates Multicast mode is enabled. A value of 'false' indicates Multicast mode is disabled.

This object represents the keep alive count. If keep alive response is not received consecutively for N (keep alive count) times, the mobility link is declared as down

Each MC sends periodically keep alive packet to other mobility devices (MA or MC). This object represents the keep alive interval. This object is valid for MC, not MA.

This object represents the Differentiated Services Code Point (DSCP) value. Here it is used for classifying and managing mobility control packets and providing quality of service (QoS) on IP networks. Valid value ranges from 0 to 63.

This object represents the MO's public IP address type.

This object represents the MO's public IP address.

This object represents the total APs directly associated with this MC and its MAs.

This object represents the multicast IP address type of its own mobility group.

This object represents the multicast IP address of its own mobility group.

This object represents the name for this mobility group.

The mobility manager is the management entity of MC or MA. This object represents the mobility manager's IP address type.

This object represents the mobility manager's IP address.

This object represents the mobility manager's netmask type.

This object represents the mobility manager's netmask.

This object represents the mac address for this mobility manager.

This object represents the VLAN ID for this mobility manager.

This object represents the name for this mobility manager.

This object represents the mobility manager interface type. It can be of two types: management: for in-band management of the controller ap: for L3 communications between the controller and LWAPP APs. Enumeration: 'ap': 2, 'management': 1.

This object represents the current status of the new mobility feature. A value of 'true' indicates new Mobility is enabled. A value of 'false' indicates new Mobility is disabled.

This object allows users to enable or disable new mobility feature. A value of 'true' indicates new Mobility is enabled. A value of 'false' indicates new Mobility is disabled.

This object represents the MC's public IP address type for this MA.

This object represents the MC's public IP address for this MA.

This object represents the MC's private IP address type for this MA.

This object represents the MC's private IP address for this MA.

This object specifies the control path and data path status of the link between this mobility agent and its mobility controller. notconfigured: This means group is not configured for ICMP or EoIP pings. datapathdown: This means group is not responding to EoIP pings. controlpathdown: This means successive ICMP pings to the group have failed. bothdown: This means group is not responding to ICMP or EOIP pings. up: This means group is responding to both EOIP and ICMP pings. Enumeration: 'up': 4, 'bothdown': 3, 'datapathdown': 1, 'notconfigured': 0, 'controlpathdown': 2.

This object represents the number of peer members of this mobility agent (MA).

This object represents the Switch Peer Group (SPG) name where this MA belongs.

This object represents the multicast address type for the own SPG group.

This object represents the multicast address for the own SPG group.

This object represents the keep alive count. If keep alive response is not received consecutively for N (keep alive count) times, the mobility link is declared as down.

Each MA sends periodically keep alive packet to other mobility devices (MA or MC). This object represents the keep alive interval.

This object represents the Differentiated Services Code Point (DSCP) value. Here it is used for classifying and managing mobility control packets and providing quality of service (QoS) on IP networks.

This object represents the received total.

This object represents the received drops.

This object represents the protocol received errors.

This object represents the protocol transmitted errors.

This object represents the state errors.

This object represents the protocol retransmitted.

This object represents the handoff requests received.

This object represents the handoff cmpl received.

This object represents the handoff client delete received.

This object represents the handoff requests transmitted.

This object represents the handoff cmpl transmitted.

This object represents the handoff client delete transmitted.

This object represents the total client count.

This object represents the wgb count.

This table represents the information about the 802.11 LWAPP Mobility Switch Peer Group (SPG).

Each entry in this table provides information about one 802.11 LWAPP Mobility SPG configured on this controller.

This object represents the group name for this SPG. This object is for human consumption.

This object represents the group ID for this SPG. This object is used in the control data packet for SPG.

This object represents the bridge domain ID for this SPG.

This object represents the number of members on this SPG.

This object represents the member's multicast IP address type.

This object represents the member's multicast IP address.

This object allows the user to enable or disable multicast mode. A value of 'true' indicates Multicast mode is enabled. A value of 'false' indicates Multicast mode is disabled.

This object creates or deletes an entry in this table.

This table represents the information about the 802.11 LWAPP Mobility Switch Peer Group (SPG) Members.

Each entry in this table provides information about one 802.11 LWAPP Mobility SPG Member configured on this controller.

This object represents the member's private IP address type.

This object represents the member's private IP address.

This object specifies the operational and connectivity status of the member. notconfigured: This means group is not configured for ICMP or EoIP pings. datapathdown: This means group is not responding to EoIP pings. controlpathdown: This means successive ICMP pings to the group have failed. bothdown: This means group is not responding to ICMP or EOIP pings. up: This means group is responding to both EOIP and ICMP pings. Enumeration: 'up': 4, 'bothdown': 3, 'datapathdown': 1, 'notconfigured': 0, 'controlpathdown': 2.

This object represents the member's public IP address type.

This object represents the member's public IP address.

This object creates or deletes an entry in this table.

This table represents the information about the 802.11 LWAPP Mobility Group Members.

Each entry in this table provides information about one 802.11 LWAPP Mobility Member configured on this controller.

This object represents the member's private IP address type.

This object represents the member's private IP address.

This object represents the member's mobility group name.

This object represents the member's public IP address type.

This object represents the member's public IP address.

This object specifies the operational and connectivity status of the member. notconfigured: This means group is not configured for ICMP or EoIP pings. datapathdown: This means group is not responding to EoIP pings. controlpathdown: This means successive ICMP pings to the group have failed. bothdown: This means group is not responding to ICMP or EOIP pings. up: This means group is responding to both EOIP and ICMP pings. Enumeration: 'up': 4, 'bothdown': 3, 'datapathdown': 1, 'notconfigured': 0, 'controlpathdown': 2.

This object represents the member's mac address.

This used represents the member's multicast IP address type.

This object represents the member's multicast IP address.

This object indicates the Hash key of the peer mobility member. It is a 40 hex digit value or 'none' to clear the previously configured hash key.

This is the status column for this row and used to create and delete specific instances of rows in this table.

This table represents the information about the 802.11 LWAPP Mobility Anchors on individual WLANs. +...............+ + + + ROUTER + + 10.16.1.1 + +...............+ .. . . . . . . . . . . 10.16.109.112 10.16.105.39 +......+ <<-------->> +......+ + + [3]CC2 tunnels + + + CC1 + MN1's traffic + CC2 + + + to Anchor CC1 + + +......+ using EoIP +......+ . . . Anchor Foreign . . . +......+ +......+ + + + + + AP1 + + AP2 + + + + + +......+ +......+ WLAN '1' . ^ WLAN '1' . | . [2] associates | . with AP2/CC2 | . | +......+ [1] +......+ + + moves to region + + + MN1 + ---------->>> + MN1 + + + serviced by AP2 + + +......+ +......+ 10.16.109.199 10.16.109.199 In the above diagram, Central Controllers CC1 and CC2 have been configure in a Mobility Group. Currently the Mobile Node 'MN1' obtains its IP from the Central Controller 'CC1' with which it first associates via WLAN '1' through Access Point 'AP1'. 'CC1' obtains DHCP address, say 10.16.109.199 for client 'MN1'. Now the client 'MN1' is identified by 10.16.109.199 for furthure communication with the network and the communication happens via 'CC1'. Since, 'CC1' and 'CC2' are in same mobility group, 'CC1' sends the authentication block of 'MN1' to 'CC2'. Central Controller 'CC2' has an associated Access Point 'AP2' which beams WLAN '1' and uses 10.16.105.0 / 255.255.255.0 subnet instead. Next, the Mobile Node 'MN1' moves out of range of 'AP1' and gets in to proximity with 'AP2' and continues to use WLAN '1'. 'CC2' locally authenticates 'MN1' against authentication block shared from 'CC1'. 'CC2' forwards all traffic from 'MN1' to router. This is called WLAN mobility. But hold on, 'CC2' uses 10.16.105.0 / 255.255.255.0 subnet for WLAN '1'. So we have two problems here : a> Traffic of 10.16.109.0 / 255.255.255.0 subnet has to be accessible from 10.16.105.0 / 255.255.255.0 subnet. b> Unneccessary overloading of 10.16.105.0 / 255.255.255.0 subnet by traffic from 10.16.109.0 / 255.255.255.0 subnet. How do we address these issues ?? If an EoIP tunnel can be established between 'CC1' and 'CC2' and 'CC1' sends all traffic bound to 'MN1', 10.16.109.199, on this tunnel to 'CC2', which in turn forwards it to 'MN1', then, above two subnet-problems are resolved. This is called Mobility Anchoring. 'CC1' is the Mobility Anchor and 'CC2' is the 'Foreign' for WLAN '1'. As per the configuration, user creates a MobilityAnchor entry in 'CC2' for WLAN '1' with IP address as 'CC1', i.e. 10.16.109.112. So, when 'MN1' connects to WLAN '1' via 'AP2', then 'CC2' establishes EoIP tunnel with 10.16.109.112 and forwards the packets to 'MN1'. Given the above example, the cLMobilityAnchorEntry on 'CC2' looks like : ------------------------------------------------------------------ | MIB - ATTRIBUTES | ROW#1 | ROW#2 | ------------------------------------------------------------------ | cLWlanIndex | 1 | | ------------------------------------------------------------------ | cLMobilityExtAnchorAssociatedMCAddressType | ipv4 | | ------------------------------------------------------------------ | cLMobilityExtAnchorAssociatedMCAddress | 10.16.109.112 | | ------------------------------------------------------------------ | cLMobilityExtAnchorStatus | up(4) | | ------------------------------------------------------------------ | cLMobilityExtAnchorRowStatus | active(1) | | ------------------------------------------------------------------ This feature has advantages for both security and load balancing. It can be used to restrict a WLAN to a single subnet, regardless of the MN's entry point into the network. A 'public' or guest WLAN can thus be accessed throughout an enterprise, but still is restricted to a specific subnet. It can also be used to provide some geographic load balancing, since the WLANs can represent a particular section of a building (ie., engineering, marketing). Those groups can be 'anchored' on a particular subnet/switch rather than on the CC of first occurrence (ie., the switch controlling the APs by the front door).

Each entry in this table provides information about one 802.11 LWAPP Mobility Anchor configured on a WLAN on this controller.

This object represents the anchor's IP address type.

This object represents the anchor's IP address

This object specifies the operational and connectivity status of the mobility anchor. notconfigured: This means anchor is not configured for ICMP or EoIP pings. datapathdown: This means anchor is not responding to EoIP pings. controlpathdown: This means successive ICMP pings to the anchor have failed. bothdown: This means anchor is not responding to ICMP or EOIP pings. up: This means anchor is responding to both EOIP and ICMP pings. Enumeration: 'up': 4, 'bothdown': 3, 'datapathdown': 1, 'notconfigured': 0, 'controlpathdown': 2.

This is the status column for this row and used to create and delete specific instances of rows in this table.

This table represents the information about the 802.11 LWAPP Mobility Controllers on this MO.

Each entry in this table provides information about one 802.11 LWAPP Mobility Controller on this MO.

This object represents the MC's IP address type.

This object represents the MC's IP address.

This object represents the MC's MAC IP address.

This object specifies the operational and connectivity status of the MC. notconfigured: This means MC is not configured for ICMP or EoIP pings. datapathdown: This means MC is not responding to EoIP pings. controlpathdown: This means successive ICMP pings to the MC have failed. bothdown: This means MC is not responding to ICMP or EOIP pings. up: This means MC is responding to both EOIP and ICMP pings. Enumeration: 'up': 4, 'bothdown': 3, 'datapathdown': 1, 'notconfigured': 0, 'controlpathdown': 2.

This object represents the MC's client count.

This table represents the information about the 802.11 LWAPP Mobility Clients on this MC.

Each entry in this table provides information about one 802.11 LWAPP Mobility Clients on this MC.

This object represents the client MAC IP address.

This object represents the client's anchor MC private IP address type.

This object represents the client's anchor MC private IP address.

This object represents the client's associated MC (local or foreign) IP address type.

This object represents the client's associated MC (local or foreign) IP address.

This object represents the client IP address type.

This object represents the client IP address.

This object represents the client state. Enumeration: 'init': 0, 'local': 1, 'anchor': 3, 'foreign': 2.

This object represents the client's association time. The object cLMobilityExtMCClientUpTime represents the MC client up time since its association.

This object specifies whether the client is local. A value of true indicates the client is local. A value of false indicates the client is not local to this MC.

This object represents the client's anchor MC mobility group ID.

This object represents the client's associated MC (local or foreign) mobility group ID.

This object represents the MA local or foreign IP address type.

This object represents the MA local or foreign IP address.

This object represents the MA anchor's IP address type.

This object represents the MA anchor's IP address.

The object cLMobilityExtMCClientUpTime represents the MC client up time since its association.

This table represents the information about the 802.11 LWAPP Mobility Clients on this MO.

Each entry in this table provides information about one 802.11 LWAPP Mobility Clients on this MO.

This object represents the client MAC address.

This object represents the client's anchor MC public IP address type.

This object represents the client's anchor MC public IP address.

This object represents the client's anchor MC private IP address type.

This object represents the client's anchor MC private IP address.

This object represents the client's associated MC (local or foreign) public IP address type.

This object represents the client's associated MC (local or foreign) public IP address.

This object represents the client's associated MC (local or foreign) private IP address type.

This object represents the client's associated MC (local or foreign) private IP address type.

This object represents the client IP address type.

This object represents the client IP address.

This object represents the client's local time.

This object represents the client's association time.The object cLMobilityExtMOClientUpTime represents the up time of the MO client since its association

This object represents the client's up time since its association.

This table represents the information about the 802.11 LWAPP Mobility AP Manager.

Each entry in this table provides information about one 802.11 LWAPP Mobility AP Manager configured on this controller.

This object represents the name for this AP manager.

This object represents the AP manager's IP address type.

This object represents the AP manager's IP address.

This object represents the AP manager's netmask type.

This object represents the AP manager's netmask.

This object represents the mac address for this AP manager.

This object represents the VLAN ID for this AP manager.

This object represents the AP manager interface type. It can be of two types: management: for in-band management of the controller ap: for L3 communications between the controller and LWAPP APs Enumeration: 'ap': 2, 'management': 1.

This object creates or deletes an entry in this table.

This table is used to create mappings of the foreign controller with the interface/interface group to be used, when clients directly connected to the foreign controller send the DHCP request to the anchor controller.

This represents a row in the cLMobilityExtForeignWlcIfMappingTable. The entries are added and deleted by explicit user driven action.

This object represents the IP address type of the foreign controller,to which the interface mapping is to be configured.

This object represents the IP address of the foreign controller,to which the interface mapping is to be configured

This object represents name of the interface/interface group which would be used for the communication with the clients connected to the foreign controller .

This is the status column for this row and used to create and delete specific instances of rows in this table.

This table represents the information about the mobility groups where clients from this MC can roam.

Each entry in this table provides information about one mobility group.

This object represents the name for the mobility group.

This object represents the multicast IP address type for the mobility group.

This object represents the multicast IP address for the mobility group.

This table represents the information about the 802.11 LWAPP SPG peer members of this MA.

Each entry in this table provides information about one 802.11 LWAPP Mobility SPG peer member of this MA.

This object represents this MA peer's private IP address type.

This object represents this MA peer's private IP address.

This object represents this MA peer's public IP address type.

This object represents this MA peer's public address.

This object specifies the control path and data path status of the link between this MA and its peer MA in the same SPG. notconfigured: This means group is not configured for ICMP or EoIP pings. datapathdown: This means group is not responding to EoIP pings. controlpathdown: This means successive ICMP pings to the group have failed. bothdown: This means group is not responding to ICMP or EOIP pings. up: This means group is responding to both EOIP and ICMP pings. Enumeration: 'up': 4, 'bothdown': 3, 'datapathdown': 1, 'notconfigured': 0, 'controlpathdown': 2.

This table represents the information about the MA statistics as reported by this MC.

Each entry in this table provides information about statistics of one MA that is associated with this MC.

This object represents the MA's private IP address type.

This object represents the MA's private IP address.

This object represents the MA's client count.

This object represents the source address type.

This object represents the sourc address

Mobility source type Enumeration: 'unknown': 0, 'mobilityOracle': 3, 'mobilityController': 2, 'mobilityAgent': 1.

Mobility destination type Enumeration: 'unknown': 0, 'mobilityOracle': 3, 'mobilityController': 2, 'mobilityAgent': 1.

The compliance statement for the SNMP entities that implement the ciscoLwappMobilityExtMIB module.

The compliance statement for the SNMP entities that implement the ciscoLwappMobilityExtMIB module.

This is a collection of objects which can be configured to control Mobility parameters.

This collection of objects provide the information about mobility trap configuration and trap definition. These objects are defined under cwciscoLwappMobilityExtNotifObjects.

This collection of objects provides the information about the notifications sent by the agent related to mobility.

This is a collection of objects which can be configured to control Mobility parameters.