All MIBs › CISCO-LWAPP-MOBILITY-MIB
Organization: Cisco Systems Inc.
Last Updated: 2020-10-05
Category: Cisco Devices, Wireless and WLAN
Description: Manages inter-controller wireless client mobility groups and roaming anchor configurations on Cisco WLCs.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is CISCO-LWAPP-MOBILITY-MIB?
CISCO-LWAPP-MOBILITY-MIB is a Cisco enterprise MIB implemented on Wireless LAN Controllers (WLCs) acting as Central Controllers (CC) that terminate the Lightweight Access Point Protocol (LWAPP) tunnel from lightweight access points. It exposes configuration and status data for 802.11 client mobility between controllers, including mobility anchor relationships for WLAN profiles, mobility group and multicast mobility enable states, and keep-alive parameters used between peer controllers. Its monitoring value is chiefly software/service-status oriented: cLMobilityAnchorStatus and cLMobilityAnchorRowStatus reveal whether an anchor mapping for a WLAN profile is active, while cLMobilityMCEnableStatus/cLMobilityMCAdminEnableStatus and cLMobilityMCKeepAliveCount indicate whether the mobility control-plane service between controllers is enabled and healthy. It is specific to Cisco's LWAPP/CAPWAP wireless architecture and depends on the broader Cisco wireless controller MIB family for AP and WLAN context. It is deployed in enterprise and campus Wi-Fi networks with multiple Cisco WLCs supporting seamless client roaming across controller boundaries. Engineers can download the CISCO-LWAPP-MOBILITY-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-LWAPP-MOBILITY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Cisco Wireless LAN Controller (WLC)
- Cisco lightweight access point (LWAPP/CAPWAP)
Monitoring Examples
An administrator would poll cLMobilityAnchorTable/cLMobilityAnchorEntry, keyed by cLMobilityAnchorWlanProfileName and cLMobilityAnchorSwitchIPAddress, to confirm an anchor controller mapping for a guest WLAN is in the expected cLMobilityAnchorStatus. Checking cLMobilityMCEnableStatus against cLMobilityMCAdminEnableStatus would reveal whether mobility control messaging between controllers has been administratively enabled but failed to actually come up. cLMobilityMCKeepAliveCount can be watched to detect missed keep-alives suggesting a peer controller has become unreachable, which would break seamless roaming for clients moving between its APs and others.
What Can Be Monitored
- mobility anchor mapping status
- WLAN profile anchor configuration
- mobility group enable state
- multicast mobility enable state
- controller keep-alive count
This MIB depends on
Related MIBs
Imported Objects
From CISCO-SMI
| ciscoMgmt | OBJECT-IDENTITY |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| MacAddress | |
| RowStatus | |
| TruthValue |
How to Use in IPNetwork Monitor
Example using cLMobilityIncomingCount OID:
Select a Cisco Wireless LAN Controller (LWAPP-based) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cLMobilityIncomingCount into the Find box to locate it in the OID tree, then select it and click OK. This object represents the number of successfully incoming inter-WLC roaming count for this WLC. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| NTF ciscoLwappMobilityAllAnchorsOnWlanDown | 1.3.6.1.4.1.9.9.576.0.5 | This trap will be generated by the controller when, successive EoIP ping attempts to all the anchors on WLAN, denoted by cLMobilityAnchorWlanId, fails and all the anchors are conclusively down. | ||
| NTF ciscoLwappMobilityAnchorControlPathDown | 1.3.6.1.4.1.9.9.576.0.1 | This trap will be generated by the controller when, successive ICMP ping attempts to the anchor fails and the anchor is conclusively down. Variable cLMobilityAnchorAddress denotes the IP address of the anchor. | ||
| NTF ciscoLwappMobilityAnchorControlPathUp | 1.3.6.1.4.1.9.9.576.0.2 | This trap will be generated by the controller when, ICMP ping to the anchor is restored and anchor is conclusively up. Variable cLMobilityAnchorAddress denotes the IP address of the anchor. | ||
| NTF ciscoLwappMobilityAnchorDataPathDown | 1.3.6.1.4.1.9.9.576.0.3 | This trap will be generated by the controller when, successive EoIP ping attempts to the anchor fails and the anchor is conclusively down. Variable cLMobilityAnchorAddress denotes the IP address of the anchor. | ||
| NTF ciscoLwappMobilityAnchorDataPathUp | 1.3.6.1.4.1.9.9.576.0.4 | This trap will be generated by the controller when, EoIP ping to the anchor is restored and anchor is conclusively up. Variable cLMobilityAnchorAddress denotes the IP address of the anchor. | ||
| ciscoLwappMobilityMCGlobalObjects | 1.3.6.1.4.1.9.9.576.1.8 | |||
| ciscoLwappMobilityMIB | 1.3.6.1.4.1.9.9.576 | 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. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. 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. Mobility Anchor When a Central Controller in the Mobility Group is designated as Mobility Anchor, then all the Mobile Node's traffic is tunneled 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 tunneled 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 address. If the path back to the source 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. | ||
| ciscoLwappMobilityMIBCompliance | 1.3.6.1.4.1.9.9.576.2.1.1 | The compliance statement for the SNMP entities that implement the ciscoLwappMobilityMIB module. | ||
| ciscoLwappMobilityMIBComplianceRev01 | 1.3.6.1.4.1.9.9.576.2.1.2 | The compliance statement for the SNMP entities that implement the ciscoLwappMobilityMIB module. | ||
| ciscoLwappMobilityMIBComplianceRev02 | 1.3.6.1.4.1.9.9.576.2.1.3 | The compliance statement for the SNMP entities that implement the ciscoLwappMobilityMIB module. | ||
| ciscoLwappMobilityMIBComplianceRev03 | 1.3.6.1.4.1.9.9.576.2.1.4 | The compliance statement for the SNMP entities that implement the ciscoLwappMobilityMIB module. | ||
| ciscoLwappMobilityMIBComplianceRev04 | 1.3.6.1.4.1.9.9.576.2.1.5 | The compliance statement for the SNMP entities that implement the ciscoLwappMobilityMIB module. | ||
| ciscoLwappMobilityMIBCompliances | 1.3.6.1.4.1.9.9.576.2.1 | |||
| ciscoLwappMobilityMIBConform | 1.3.6.1.4.1.9.9.576.2 | |||
| ciscoLwappMobilityMIBGroups | 1.3.6.1.4.1.9.9.576.2.2 | |||
| ciscoLwappMobilityMIBNotifs | 1.3.6.1.4.1.9.9.576.0 | |||
| ciscoLwappMobilityMIBObjects | 1.3.6.1.4.1.9.9.576.1 | |||
| NTF ciscoLwappMobilityOneAnchorOnWlanUp | 1.3.6.1.4.1.9.9.576.0.6 | This trap will be generated by the controller when, successive EoIP and UDP ping to atleast one anchor on the WLAN, denoted by cLMobilityAnchorWlanId, is restored and anchor is conclusively up. | ||
| IP cLMobilityAnchorAddress | 1.3.6.1.4.1.9.9.576.1.3.3 | InetAddress | accessible-for-notify | This object represents the guest/anchor switch address. The IP address is limited to IPv4 and IPv6. |
| IPt cLMobilityAnchorAddressType | 1.3.6.1.4.1.9.9.576.1.3.2 | InetAddressType | accessible-for-notify | This object represents the guest/anchor switch address type. |
| T/F cLMobilityAnchorCurrentSmt | 1.3.6.1.4.1.9.9.576.1.2.4 | TruthValue | read-only | This object represents whether the Symmetric Mobility Tunneling is enabled or disabled on the controller. A value of 'true' indicates that Symmetric Mobility Tunneling is currently enabled on the controller. A value of 'false' indicates that Symmetric Mobility Tunneling is currently disabled on the controller. |
| I32 cLMobilityAnchorDscpValue | 1.3.6.1.4.1.9.9.576.1.2.5 | Integer32 | read-write | This object specifies the intercontroller DSCP value. |
| cLMobilityAnchorEntry | 1.3.6.1.4.1.9.9.576.1.1.1 | not-accessible | Each entry in this table provides information about one 802.11 LWAPP mobility anchor configured on a WLAN on this controller. | |
| cLMobilityAnchorGlobalDot11Config | 1.3.6.1.4.1.9.9.576.1.2 | |||
| I32 cLMobilityAnchorGroupKeepAliveInterval | 1.3.6.1.4.1.9.9.576.1.2.2 | Integer32 | read-write | This object specifies the time interval (in seconds) between two consecutive ping attempts to an anchor. |
| I32 cLMobilityAnchorGroupKeepAliveNumber | 1.3.6.1.4.1.9.9.576.1.2.1 | Integer32 | read-write | This object specifies how many successive ping attempts to the anchor should fail before the anchor is declared DOWN. |
| ROW cLMobilityAnchorRowStatus | 1.3.6.1.4.1.9.9.576.1.1.1.4 | RowStatus | read-create | This is the status column for this row and is used to create and delete specific instances of rows in this table. |
| T/F cLMobilityAnchorSmtStatus | 1.3.6.1.4.1.9.9.576.1.2.3 | TruthValue | read-write | This object specifies whether it allows user to enable or disable symmetric mobility tunneling for the controller. The controller provides inter-subnet mobility for clients roaming from one AP to another within a wireless LAN. This mobility is asymmetric in nature where the client traffic to the wired network is routed out directly via the 'foreign' controller. See the diagram above. This mechanism breaks when an upstream router has RPF enabled. In this case the client traffic will be dropped at the router because the RPF check ensures that the path back to the source address matches the path the packet is coming from. This attribute is aimed at addressing this issue. It will allow enabling 'Symmetric Mobility Tunneling' or 'Bi-directional Tunneling' for mobile clients such that all the client traffic is sent to the 'anchor' controller and go successfully through RPF check. When set to 'true', Symmetric Mobility Tunneling will be enabled on the Controller on next reset. When set to 'false', Symmetric Mobility Tunneling will be disabled on the Controller on next reset. After setting this attribute to the desired value, user should reset the Controller for the change to take effect. |
| BIT cLMobilityAnchorStatus | 1.3.6.1.4.1.9.9.576.1.1.1.3 | Bits | read-only | This object represents operational and connectivity status of the mobility anchor. controlpath: When bit is set to '0', this means successive ICMP pings to the anchor have failed. When bit is set to '1', this means anchor is reachable and responding to ICMP pings. datapath: When bit is set to '0', this means successive EoIP pings to the anchor have failed. When bit is set to '1', this means anchor is reachable and responding to EoIP pings. |
| IP cLMobilityAnchorSwitchIPAddress | 1.3.6.1.4.1.9.9.576.1.1.1.2 | IpAddress | not-accessible | This object represents the guest/anchor switch IP address. |
| cLMobilityAnchorTable | 1.3.6.1.4.1.9.9.576.1.1 | not-accessible | 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 + + + + + +......+ +......+ 'typhoon' . ^'typhoon' . | . [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 configured in a Mobility Group. Currently the Mobile Node 'MN1' obtains its IP from the Central Controller 'CC1' with which it first associates via WLAN 'typhoon' 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 further 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 'typhoon' 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 'typhoon'. '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 'typhoon'. 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> Unnecessary 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 'typhoon'. As per the configuration, user creates a MobilityAnchor entry in 'CC2' for WLAN 'typhoon' with IP address as 'CC1', i.e. 10.16.109.112. So, when 'MN1' connects to WLAN 'typhoon' 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 | --------------------------------------------------------------- | cLMobilityAnchorWlanProfileName | typhoon | | --------------------------------------------------------------- | cLMobilityAnchorSwitchIPAddress | 10.16.109.112 | | --------------------------------------------------------------- | cLMobilityAnchorStatus | up(4) | | --------------------------------------------------------------- | cLMobilityAnchorRowStatus | 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 (i.e., engineering, marketing). Those groups can be 'anchored' on a particular subnet/switch rather than on the CC of first occurrence (i.e., the switch controlling the APs by the front door). | |
| I32 cLMobilityAnchorWlanId | 1.3.6.1.4.1.9.9.576.1.3.1 | Integer32 | accessible-for-notify | This object represents index of the WLAN in the controller. |
| OCT cLMobilityAnchorWlanProfileName | 1.3.6.1.4.1.9.9.576.1.1.1.1 | OCTET STRING | not-accessible | This object represenst local WLAN-profile name to connect to guest/anchor switch. |
| cLMobilityForeignWlcMapEntry | 1.3.6.1.4.1.9.9.576.1.6.1 | not-accessible | Each entry in this table represents a row in the cLMobilityForeignWlcIfMappingTable .Entries are added and deleted by explicit user driven action. | |
| STR cLMobilityForeignWlcMapIf | 1.3.6.1.4.1.9.9.576.1.6.1.2 | SnmpAdminString | read-create | This object specifies name of the interface/interface group which would be used for the communication with the clients connected to the foreign controller, represented by cLMobilityForeignWlcMapMacAddress. |
| MAC cLMobilityForeignWlcMapMacAddress | 1.3.6.1.4.1.9.9.576.1.6.1.1 | MacAddress | not-accessible | This object represents the MAC address of the foreign controller, to which the interface mapping is to be configured. |
| ROW cLMobilityForeignWlcMapRowStatus | 1.3.6.1.4.1.9.9.576.1.6.1.3 | RowStatus | read-create | This is the status column for this row and is used to create and delete specific instances of rows in this table. |
| cLMobilityForeignWlcMapTable | 1.3.6.1.4.1.9.9.576.1.6 | not-accessible | This table is used to create mappings of the foreign controller with the interface/interface group to be used, when clients are directly connected to the foreign controller send the DHCP request to the anchor controller. | |
| MAC cLMobilityGroupMacAddress | 1.3.6.1.4.1.9.9.576.1.4.2.1.1 | MacAddress | not-accessible | This object represents the mobility group MAC address present on the controller. |
| IP cLMobilityGroupMemberAddress | 1.3.6.1.4.1.9.9.576.1.5.1.7 | InetAddress | read-create | This object specifies the IP address of the mobility member corresponding to cLMobilityGroupMacAddress. The IP address is limited to IPv4 and IPv6. |
| IPt cLMobilityGroupMemberAddressType | 1.3.6.1.4.1.9.9.576.1.5.1.6 | InetAddressType | read-create | This object specifies the IP address type of the mobility member IP address represented by cLMobilityGroupMemberIPAddress. The IP address is limited to IPv4 and IPv6. |
| T/F cLMobilityGroupMemberControlPathStatusUp | 1.3.6.1.4.1.9.9.576.1.5.1.3 | TruthValue | read-only | This object represents the control path status of the mobility member corresponding to cLMobilityGroupMacAddress. A value of 'true' indicates that control path is up. A value of 'false' indicates that control path is down. |
| T/F cLMobilityGroupMemberDataDtls | 1.3.6.1.4.1.9.9.576.1.5.1.10 | TruthValue | read-create | This object specifies the data dtls status with a mobility member.Data DTLS modification can be performed once mobility member is created. A value of 'true' indicates that data DTLS is enabled. A value of 'false' indicates that data DTLS is disabled. |
| T/F cLMobilityGroupMemberDataPathStatusUp | 1.3.6.1.4.1.9.9.576.1.5.1.4 | TruthValue | read-only | This object represents the data path status of the mobility member corresponding to cLMobilityGroupMacAddress. A value of 'true' indicates that data path is up. A value of 'false' indicates that data path is down. |
| cLMobilityGroupMemberGlobalParametersGroup | 1.3.6.1.4.1.9.9.576.2.2.9 | This is a collection of objects which can configured to Global Mobility Group Configuration of WLC. | ||
| STR cLMobilityGroupMemberGroupName | 1.3.6.1.4.1.9.9.576.1.5.1.8 | SnmpAdminString | read-create | This object specifies member's group name. If left empty while adding a new group member, this assumes the default mobility group name of the switch. |
| OCT cLMobilityGroupMemberHashKey | 1.3.6.1.4.1.9.9.576.1.5.1.5 | OCTET STRING | read-write | 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 |
| IP cLMobilityGroupMemberIPAddress | 1.3.6.1.4.1.9.9.576.1.5.1.2 | InetAddress | read-only | This object represents the IP address of the mobility member corresponding to cLMobilityGroupMacAddress. The IP address is limited to IPv4 and IPv6. For clarity, this object is being deprecated in favor of the new read-write object 'cLMobilityGroupMemberAddress. |
| IP cLMobilityGroupMemberIPAddressRev1 | 1.3.6.1.4.1.9.9.576.1.5.1.12 | InetAddress | read-create | This object represents the IP address of the mobility tunnel corresponding to cLMobilityGroupMemberIPAddressTypeRev1. The IP address is limited to IPv4 and IPv6. |
| IPt cLMobilityGroupMemberIPAddressType | 1.3.6.1.4.1.9.9.576.1.5.1.1 | InetAddressType | read-only | This object represents the IP address type of the mobility member IP address represented by cLMobilityGroupMemberIPAddress. The IP address is limited to IPv4 and IPv6. For clarity, this object is being deprecated in favor of the new read-write object 'cLMobilityGroupMemberAddressType. |
| IPt cLMobilityGroupMemberIPAddressTypeRev1 | 1.3.6.1.4.1.9.9.576.1.5.1.11 | InetAddressType | read-create | This object represents the public IP Address type of the mobility tunnel. The Ip address is limited to ipv4 and ipv6. |
| cLMobilityGroupMemberRev02ConfigGroup | 1.3.6.1.4.1.9.9.576.2.2.8 | This is a collection of objects which can configured to Global Mobility Group Configuration of WLC. | ||
| cLMobilityGroupMemberRev02StatusGroup | 1.3.6.1.4.1.9.9.576.2.2.7 | This collection of objects represents the information about the Global Mobility Group Configuration of WLC. | ||
| ROW cLMobilityGroupMemberRowStatus | 1.3.6.1.4.1.9.9.576.1.5.1.9 | RowStatus | read-create | This is the status column for this row and is used to create and delete specific instances of rows in this table. |
| cLMobilityGroupMembersEntry | 1.3.6.1.4.1.9.9.576.1.5.1 | not-accessible | This object represents an entry (conceptual row) in the cLMobilityGroupMembers table. | |
| T/F cLMobilityGroupMembersOperControlPathStatus | 1.3.6.1.4.1.9.9.576.1.9.1.5 | TruthValue | read-only | This object represents the control path status of the mobility member corresponding to cLMobilityGroupMembersOperNodeAddress. |
| T/F cLMobilityGroupMembersOperDataPathStatus | 1.3.6.1.4.1.9.9.576.1.9.1.4 | TruthValue | read-only | This object represents the data path status of the mobility member corresponding to cLMobilityGroupMembersOperNodeAddress. |
| cLMobilityGroupMembersOperEntry | 1.3.6.1.4.1.9.9.576.1.9.1 | not-accessible | This object represents an Entry (conceptual row) in the cLMobilityGroupMembersOper table. | |
| IP cLMobilityGroupMembersOperNodeAddress | 1.3.6.1.4.1.9.9.576.1.9.1.2 | InetAddress | not-accessible | This object represents the IP Address of the mobility member This object support for only IPv4 and IPv6 addresses and so the size can be either 4 or 16 bytes. |
| IPt cLMobilityGroupMembersOperNodeAddressType | 1.3.6.1.4.1.9.9.576.1.9.1.1 | InetAddressType | not-accessible | This object represents the IP Address type of the mobility member |
| cLMobilityGroupMembersOperTable | 1.3.6.1.4.1.9.9.576.1.9 | not-accessible | This object represents the MWAR List (statically configured members of the mobility group).Entries are created to the table when configuring mobility group members. | |
| I32 cLMobilityGroupMembersOperTunnelStatus | 1.3.6.1.4.1.9.9.576.1.9.1.3 | Integer32 | read-only | This object represents the tunnel status of the mobility member corresponding to cLMobilityGroupMembersOperNodeAddress. |
| cLMobilityGroupMembersTable | 1.3.6.1.4.1.9.9.576.1.5 | not-accessible | This table represents the MWAR List (statically configured members of the mobility group). Entries are added to the table when configuring mobility group members. | |
| cLMobilityGroupRev01ConfigGroup | 1.3.6.1.4.1.9.9.576.2.2.6 | This collection of objects represents the information about the mobility groups and the interface mappings with foreign controllers. | ||
| C32 cLMobilityIncomingCountEx | 1.3.6.1.4.1.9.9.576.1.7.1 | Counter32 | read-only | This object represents the number of successfully incoming inter-WLC roaming count for this WLC. If a client roams in from other WLC with the same SSID and successfully re-associated, the count should be increased. |
| T/F cLMobilityMCAdminEnableStatus | 1.3.6.1.4.1.9.9.576.1.8.4 | TruthValue | read-write | 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 cLMobilityMCEnableStatus (operational value) can be false even if cLMobilityMCAdminEnableStatus is true. |
| U32 cLMobilityMCApCountLicensesInUse | 1.3.6.1.4.1.9.9.576.1.8.11 | Unsigned32 | read-only | This object represents the total APs directly associated with this MC and its MAs. |
| U32 cLMobilityMCDscpValue | 1.3.6.1.4.1.9.9.576.1.8.8 | Unsigned32 | read-write | 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. |
| T/F cLMobilityMCEnableStatus | 1.3.6.1.4.1.9.9.576.1.8.3 | TruthValue | read-only | 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. |
| U32 cLMobilityMCKeepAliveCount | 1.3.6.1.4.1.9.9.576.1.8.6 | Unsigned32 | read-write | 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. Valid value ranges from 3 to 20. |
| U32 cLMobilityMCKeepAliveInterval | 1.3.6.1.4.1.9.9.576.1.8.7 | Unsigned32 | read-write | 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. Valid value ranges from 1 to 30. |
| MAC cLMobilityMCMacAddress | 1.3.6.1.4.1.9.9.576.1.8.19 | MacAddress | read-write | This object represents the mac address of its own mobility group. |
| T/F cLMobilityMCMOAdminEnableStatus | 1.3.6.1.4.1.9.9.576.1.8.2 | TruthValue | read-write | 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 cLMobilityMOEnableStatus (operational value) can be false even if cLMobilityMOAdminEnableStatus is true. |
| STR cLMobilityMCMobilityGroupName | 1.3.6.1.4.1.9.9.576.1.8.14 | SnmpAdminString | read-write | This object represents the name for this mobility group. |
| T/F cLMobilityMCMOEnableStatus | 1.3.6.1.4.1.9.9.576.1.8.1 | TruthValue | read-only | 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. |
| U32 cLMobilityMCMONumberOfClients | 1.3.6.1.4.1.9.9.576.1.8.15 | Unsigned32 | read-only | This object represents the total number of clients reported by MO. |
| IP cLMobilityMCMOPublicAddress | 1.3.6.1.4.1.9.9.576.1.8.10 | InetAddress | read-write | This object represents the MO's public IP address. |
| IPt cLMobilityMCMOPublicAddressType | 1.3.6.1.4.1.9.9.576.1.8.9 | InetAddressType | read-write | This object represents the MO's public IP address type. |
| T/F cLMobilityMCMulticastMode | 1.3.6.1.4.1.9.9.576.1.8.5 | TruthValue | read-write | 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. |
| U32 cLMobilityMCNumberOfMCs | 1.3.6.1.4.1.9.9.576.1.8.16 | Unsigned32 | read-only | This object represents the total number of MCs. |
| U32 cLMobilityMCNumberOfReportedAPsInSubDomain | 1.3.6.1.4.1.9.9.576.1.8.18 | Unsigned32 | read-only | This object represents the total number of APs reported by this MC and its MAs. |
| IP cLMobilityMCOwnGroupMulticastAddress | 1.3.6.1.4.1.9.9.576.1.8.13 | InetAddress | read-write | This object represents the multicast IPv4 address of its own mobility group. |
| IPt cLMobilityMCOwnGroupMulticastAddressType | 1.3.6.1.4.1.9.9.576.1.8.12 | InetAddressType | read-write | This object represents the multicast IP address type of its own mobility group. |
| U32 cLMobilityMCTotalNumberOfReportedAPs | 1.3.6.1.4.1.9.9.576.1.8.17 | Unsigned32 | read-only | This object represents the total number of APs reported by this MC, its peer MCs and its MAs. |
| cLMobilityMulticastGroupConfig | 1.3.6.1.4.1.9.9.576.1.4 | |||
| cLMobilityMulticastGroupEntry | 1.3.6.1.4.1.9.9.576.1.4.2.1 | not-accessible | Each entry in this table provides information about multicast group IP address per mobility group. | |
| IP cLMobilityMulticastGroupIPAddress | 1.3.6.1.4.1.9.9.576.1.4.2.1.3 | InetAddress | read-write | This object specifies the multicast group IP address per group. The IP address is limited to IPv4 and IPv6. The IP address should be reset only after disabling the mobility multicast mode (cLMobilityMulticastMessagingEnable). |
| IPt cLMobilityMulticastGroupIPAddressType | 1.3.6.1.4.1.9.9.576.1.4.2.1.2 | InetAddressType | read-write | This object specifies the multicast group IP address type. The IP address is limited to IPv4 and IPv6. |
| cLMobilityMulticastGroupTable | 1.3.6.1.4.1.9.9.576.1.4.2 | not-accessible | This table is used to configure multicast group IP address per mobility group. Entries are added to the table when configuring multicast group IP address per mobility group. | |
| T/F cLMobilityMulticastMessagingEnable | 1.3.6.1.4.1.9.9.576.1.4.1 | TruthValue | read-write | This object specifies whether the mobility multicast messaging feature is enabled or disabled on the controller. A value of 'true' indicates that multicast messaging among the mobility group members is enabled. A value of 'false' indicates that multicast messaging among the mobility group members is disabled. |
| C32 cLMobilityOutgoingCount | 1.3.6.1.4.1.9.9.576.1.7.2 | Counter32 | read-only | This object represents the number of successfully outgoing inter-WLC roaming count for this WLC. If a client roams out to other WLC with the same SSID successfully, the count should be increased. |
| cLMobilityStats | 1.3.6.1.4.1.9.9.576.1.7 | |||
| cLMobilityTrapVariables | 1.3.6.1.4.1.9.9.576.1.3 | |||
| cLNplus1RedundancyRev01ConfigGroup | 1.3.6.1.4.1.9.9.576.2.2.1 | This is a collection of objects which can configured to control functional parameters of guest tunneling N+1 redundancy feature. | ||
| cLNplus1RedundancyRev01NotifsGroup | 1.3.6.1.4.1.9.9.576.2.2.3 | This is a collection of notifications about the general functional behavior of guest tunneling N+1 redundancy feature. | ||
| cLNplus1RedundancyRev01StatusGroup | 1.3.6.1.4.1.9.9.576.2.2.2 | This collection of objects represents the information about the general status attributes of guest tunneling N+1 redundancy feature. | ||
| cLNplus1RedundancyRev02NotifsGroup | 1.3.6.1.4.1.9.9.576.2.2.10 | This is a collection of notifications about the general functional behavior of guest tunneling N+1 redundancy feature. | ||
| cLSymmetricTunnelingRev01ConfigGroup | 1.3.6.1.4.1.9.9.576.2.2.4 | This is a collection of objects which can be configured to control functional parameters of symmetric mobility tunneling feature. | ||
| cLSymmetricTunnelingRev01StatusGroup | 1.3.6.1.4.1.9.9.576.2.2.5 | This collection of objects represents the information about the general status attributes of symmetric tunneling feature. |
RFC description
Cisco vendor-private MIB managing Lightweight Access Point Protocol (LWAPP) client mobility, roaming, and handoff operations.
Start monitoring Cisco Wireless LAN Controllers (LWAPP-based) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.