CISCO-LWAPP-MOBILITY-EXT-MIB
The CISCO-LWAPP-MOBILITY-EXT-MIB provides configuration and status monitoring for 802.11 WLAN mobility events on Cisco Wireless LAN Controllers (WLC) acting as Central Controllers within a Mobility Group. It exposes metrics related to Mobile Node roaming, Mobility Agent/Controller associations, and the tunneling of client traffic between Central Controllers to maintain seamless connectivity without re-authentication.
Imported Objects
Objects
184 total| Object Name |
|---|
ciscoLwappMobilityExtMIB MODULE-IDENTITY .1.3.6.1.4.1.9.9.999999 |
ciscoLwappMobilityExtMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.0 |
ciscoLwappMobilityControlPathDown NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.999999.0.1 |
ciscoLwappMobilityControlPathUp NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.999999.0.2 |
ciscoLwappMobilityDataPathDown NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.999999.0.3 |
ciscoLwappMobilityDataPathUp NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.999999.0.4 |
ciscoLwappMobilityExtMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.1 |
ciscoLwappMobilityExtGlobalObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.1.1 |
ciscoLwappMobilityExtMCGlobalObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.1.1.1 |
cLMobilityExtMCMOEnableStatusro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.1.1 |
cLMobilityExtMCMOAdminEnableStatusrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.1.2 |
cLMobilityExtMCEnableStatusro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.1.3 |
cLMobilityExtMCAdminEnableStatusrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.1.4 |
cLMobilityExtMCMulticastModerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.1.5 |
cLMobilityExtMCKeepAliveCountrw Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.1.6 |
cLMobilityExtMCKeepAliveIntervalrw Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.1.7 |
cLMobilityExtMCDscpValuerw Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.1.8 |
cLMobilityExtMCMOPublicAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.1.9 |
cLMobilityExtMCMOPublicAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.1.10 |
cLMobilityExtMCApCountLicensesInUsero Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.1.11 |
cLMobilityExtMCOwnGroupMulticastAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.1.12 |
cLMobilityExtMCOwnGroupMulticastAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.1.13 |
cLMobilityExtMCMobilityGroupNamerw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.999999.1.1.1.14 |
ciscoLwappMobilityExtMCMAGlobalObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.1.1.2 |
cLMobilityExtMgrAddressTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.2.1 |
cLMobilityExtMgrAddressro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.2.2 |
cLMobilityExtMgrNetmaskTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.2.3 |
cLMobilityExtMgrNetmaskro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.2.4 |
cLMobilityExtMgrMacAddressro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.2.5 |
cLMobilityExtMgrVlanIdro Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.2.6 |
cLMobilityExtMgrNamerw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.999999.1.1.2.7 |
cLMobilityExtMgrInterfaceTypero Enumeration .1.3.6.1.4.1.9.9.999999.1.1.2.8 |
cLMobilityExtNewArchitectureEnableStatusro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.2.9 |
cLMobilityExtNewArchitectureAdminEnableStatusrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.1.2.10 |
ciscoLwappMobilityExtMAGlobalObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.1.1.3 |
cLMobilityExtMAMCPublicAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.3.1 |
cLMobilityExtMAMCPublicAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.3.2 |
cLMobilityExtMAMCPrivateAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.3.3 |
cLMobilityExtMAMCPrivateAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.3.4 |
cLMobilityExtMAToMCLinkStatusro Enumeration .1.3.6.1.4.1.9.9.999999.1.1.3.5 |
cLMobilityExtMASpgPeerCountro Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.3.6 |
cLMobilityExtMASpgNamero SnmpAdminString .1.3.6.1.4.1.9.9.999999.1.1.3.7 |
cLMobilityExtMAOwnMulticastAddressTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.3.8 |
cLMobilityExtMAOwnMulticastAddressro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.1.3.9 |
cLMobilityExtMAKeepAliveCountro Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.3.10 |
cLMobilityExtMAKeepAliveIntervalro Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.3.11 |
cLMobilityExtMADscpValuero Unsigned32 .1.3.6.1.4.1.9.9.999999.1.1.3.12 |
ciscoLwappMobilityExtMCStats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.1.1.4 |
cLMobilityExtMCReceivedTotalro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.1 |
cLMobilityExtMCReceivedDropsro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.2 |
cLMobilityExtMCProtocolReceiveErrorsro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.3 |
cLMobilityExtMCProtocolTransmitErrorsro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.4 |
cLMobilityExtMCStateErrorsro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.5 |
cLMobilityExtMCProtocolRetransmittedro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.6 |
cLMobilityExtMCHandoffRequestsReceivedro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.7 |
cLMobilityExtMCHandoffCmplReceivedro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.8 |
cLMobilityExtMCHandoffClientDeleteReceivedro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.9 |
cLMobilityExtMCHandoffRequestsTransmittedro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.10 |
cLMobilityExtMCHandoffCmplTransmittedro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.11 |
cLMobilityExtMCHandoffClientDeleteTransmittedro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.12 |
cLMobilityExtMCTotalClientCountro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.13 |
cLMobilityExtMCWgbCountro Counter32 .1.3.6.1.4.1.9.9.999999.1.1.4.14 |
ciscoLwappMobilityExtTableObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.999999.1.2 |
cLMobilityExtSpgTable SEQUENCE OF CLMobilityExtSpgEntry .1.3.6.1.4.1.9.9.999999.1.2.1 |
cLMobilityExtSpgEntry CLMobilityExtSpgEntry .1.3.6.1.4.1.9.9.999999.1.2.1.1 |
cLMobilityExtSpgGroupName SnmpAdminString .1.3.6.1.4.1.9.9.999999.1.2.1.1.1 |
cLMobilityExtSpgGroupIdrw Unsigned32 .1.3.6.1.4.1.9.9.999999.1.2.1.1.2 |
cLMobilityExtSpgBridgeDomainIdrw Unsigned32 .1.3.6.1.4.1.9.9.999999.1.2.1.1.3 |
cLMobilityExtSpgMemberCountro Unsigned32 .1.3.6.1.4.1.9.9.999999.1.2.1.1.4 |
cLMobilityExtSpgMulticastAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.1.1.5 |
cLMobilityExtSpgMulticastAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.1.1.6 |
cLMobilityExtSpgMulticastModerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.2.1.1.7 |
cLMobilityExtSpgRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.2.1.1.8 |
cLMobilityExtSpgMemberTable SEQUENCE OF CLMobilityExtSpgMemberEntry .1.3.6.1.4.1.9.9.999999.1.2.2 |
cLMobilityExtSpgMemberEntry CLMobilityExtSpgMemberEntry .1.3.6.1.4.1.9.9.999999.1.2.2.1 |
cLMobilityExtSpgMemberPrivateAddressType InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.2.1.1 |
cLMobilityExtSpgMemberPrivateAddress InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.2.1.2 |
cLMobilityExtSpgMemberStatusro Enumeration .1.3.6.1.4.1.9.9.999999.1.2.2.1.3 |
cLMobilityExtSpgMemberPublicAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.2.1.4 |
cLMobilityExtSpgMemberPublicAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.2.1.5 |
cLMobilityExtSpgMemberRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.2.2.1.6 |
cLMobilityExtGroupMemberTable SEQUENCE OF CLMobilityExtGroupMemberEntry .1.3.6.1.4.1.9.9.999999.1.2.3 |
cLMobilityExtGroupMemberEntry CLMobilityExtGroupMemberEntry .1.3.6.1.4.1.9.9.999999.1.2.3.1 |
cLMobilityExtGroupMemberPrivateAddressType InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.3.1.1 |
cLMobilityExtGroupMemberPrivateAddress InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.3.1.2 |
cLMobilityExtGroupMemberGroupNamerw SnmpAdminString .1.3.6.1.4.1.9.9.999999.1.2.3.1.3 |
cLMobilityExtGroupMemberPublicAddressTyperw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.3.1.4 |
cLMobilityExtGroupMemberPublicAddressrw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.3.1.5 |
cLMobilityExtGroupMemberStatusro Enumeration .1.3.6.1.4.1.9.9.999999.1.2.3.1.6 |
cLMobilityExtGroupMemberMacAddressrw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.2.3.1.7 |
cLMobilityExtGroupMemberMulticastAddressTypero InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.3.1.8 |
cLMobilityExtGroupMemberMulticastAddressro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.3.1.9 |
cLMobilityExtGroupMemberHashKeyrw OCTET STRING .1.3.6.1.4.1.9.9.999999.1.2.3.1.10 |
cLMobilityExtGroupMemberRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.2.3.1.11 |
cLMobilityExtAnchorTable SEQUENCE OF CLMobilityExtAnchorEntry .1.3.6.1.4.1.9.9.999999.1.2.4 |
cLMobilityExtAnchorEntry CLMobilityExtAnchorEntry .1.3.6.1.4.1.9.9.999999.1.2.4.1 |
cLMobilityExtAnchorAssociatedMCAddressType InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.4.1.1 |
cLMobilityExtAnchorAssociatedMCAddress InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.999999.1.2.4.1.2 |
cLMobilityExtAnchorStatusro Enumeration .1.3.6.1.4.1.9.9.999999.1.2.4.1.3 |
cLMobilityExtAnchorRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.999999.1.2.4.1.4 |
CISCO-LWAPP-MOBILITY-EXT-MIB Technical Reference Overview
The CISCO-LWAPP-MOBILITY-EXT-MIB SNMP MIB module published by Cisco defines 184 managed OID objects, including 143 scalar/column metrics, 12 SNMP tables, and 4 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.999999. Key tabular structures include cLMobilityExtSpgTable, cLMobilityExtSpgMemberTable, cLMobilityExtGroupMemberTable, cLMobilityExtAnchorTable, cLMobilityExtMOMCTable, cLMobilityExtMCClientTable. Monitored SNMP traps/notifications include ciscoLwappMobilityControlPathDown, ciscoLwappMobilityControlPathUp, ciscoLwappMobilityDataPathDown, ciscoLwappMobilityDataPathUp.
Key OID Definitions in CISCO-LWAPP-MOBILITY-EXT-MIB
.1.3.6.1.4.1.9.9.999999This 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.
.1.3.6.1.4.1.9.9.999999.1.2.1This table represents the information about the 802.11 LWAPP Mobility Switch Peer Group (SPG).
.1.3.6.1.4.1.9.9.999999.1.2.2This table represents the information about the 802.11 LWAPP Mobility Switch Peer Group (SPG) Members.
.1.3.6.1.4.1.9.9.999999.1.2.3This table represents the information about the 802.11 LWAPP Mobility Group Members.
.1.3.6.1.4.1.9.9.999999.1.2.4This 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 + + + 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).
.1.3.6.1.4.1.9.9.999999.1.2.5This table represents the information about the 802.11 LWAPP Mobility Controllers on this MO.
.1.3.6.1.4.1.9.9.999999.1.2.6This table represents the information about the 802.11 LWAPP Mobility Clients on this MC.
.1.3.6.1.4.1.9.9.999999.1.2.7This table represents the information about the 802.11 LWAPP Mobility Clients on this MO.
.1.3.6.1.4.1.9.9.999999.1.2.8This table represents the information about the 802.11 LWAPP Mobility AP Manager.
.1.3.6.1.4.1.9.9.999999.1.2.9This 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.
.1.3.6.1.4.1.9.9.999999.1.2.10This table represents the information about the mobility groups where clients from this MC can roam.
.1.3.6.1.4.1.9.9.999999.1.2.11This table represents the information about the 802.11 LWAPP SPG peer members of this MA.
.1.3.6.1.4.1.9.9.999999.1.2.12This table represents the information about the MA statistics as reported by this MC.
.1.3.6.1.4.1.9.9.999999.0.1This notification is sent by the agent when a mobility control path goes down.
.1.3.6.1.4.1.9.9.999999.0.2This notification is sent by the agent when a mobility control path goes up.
.1.3.6.1.4.1.9.9.999999.0.3This notification is sent by the agent when a mobility data path goes down.
.1.3.6.1.4.1.9.9.999999.0.4This notification is sent by the agent when a mobility data path goes up.
.1.3.6.1.4.1.9.9.999999.1.1.1.1This 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.
.1.3.6.1.4.1.9.9.999999.1.1.1.2This 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.
.1.3.6.1.4.1.9.9.999999.1.1.1.3This 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.
.1.3.6.1.4.1.9.9.999999.1.1.1.4This 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.
.1.3.6.1.4.1.9.9.999999.1.1.1.5This 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.
.1.3.6.1.4.1.9.9.999999.1.1.1.6This 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
.1.3.6.1.4.1.9.9.999999.1.1.1.7Each 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.
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.
The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.
The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.
SNMP MIB module
The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.
The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.