CISCO-LWAPP-DOT11-CLIENT-TS-MIB: View SNMP OID List / Download MIB

This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Access Point Protocol tunnel from Cisco Light-weight LWAPP Access Points. This MIB provides information about troubleshooting 802.11 clients during their association with the controller. The clients that need to be monitored are added by the controller to a watchlist. Once added the controller will start storing the messages related to that client. These messages are useful to troubleshoot the reasons for failures during assoication. 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 them to the controller to which it is logically connected. Central Controller ( CC ) The central entity that terminates the LWAPP protocol tunnel from the LWAPP APs. Throughout this MIB, this entity also referred to as 'controller'. Cisco Compatible eXtensions (CCX) Wireless LAN Access Points (APs) manufactured by Cisco Systems have features and capabilities beyond those in related standards (e.g., IEEE 802.11 suite of standards, Wi-Fi recommendations by WECA, 802.1X security suite, etc). A number of features provide higher performance. For example, Cisco AP transmits a specific Information Element, which the clients adapt to for enhanced performance. Similarly, a number of features are implemented by means of proprietary Information Elements, which Cisco clients use in specific ways to carry out tasks above and beyond the standard. Other examples of feature categories are roaming and power saving. 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. The terms 'Mobile node' and 'client' are used interchangeably. Radio Management (RM) This term refers to managing the 802.11 radio environment to provide the best quality service to to the 802.11 wireless clients. Service Set Identifier ( SSID ) SSID is a unique identifier that APs and clients use to identify with each other. SSID is a simple means of access control and is not for security. The SSID can be any alphanumeric entry up to 32 characters. REFERENCE [1] Wireless LAN Medium Access Control ( MAC ) and Physical Layer ( PHY ) Specifications [2] Draft-obara-capwap-lwapp-00.txt, IETF Light Weight Access Point Protocol

Ths table populates the messages generated during client's association with the controller. Entries are automatically addded by the controller when the client for the cldctWatchListTable associates with the controller. Each row represents a message generated on the controller for the client on the watch list. Entries are automatically removed by the controller when the client is removed from the watchlist. The number of message per client is limited to the number specified by the cldctClientInfoMaxEntries object. When the maximum number of entries is reached the older entries will be deleted.

Each entry in this table represents the messages generated on the controller during the client's association with it.

This object uniquely identifies the sequence number of the message for a watch listed client.

This object represents the absolute time when entry was added to table.

This object indicates the types of messages generated by the watch listed client. There can be three types of messages. 'phase' - This value represents phase transition of a wireless client. The various phases include 802.11, 8021x, dhcp etc. 'state' - This value represents a state transition of a wireless client. The states could be association request, authentication request etc. for 802.11 phase. 'normal' - This value represents an informational message generated during 802.11 client's association to the controller. Enumeration: 'phase': 1, 'state': 2, 'normal': 3.

This object indicates severity of the information of the client trouble shooting messages. This object holds good only if the corresponding cldctClientInfoLevel is set to 'normal'. 'info' - This is an information message. 'error' - This is an error message. 'critical' - This is a critical message. Enumeration: 'info': 1, 'critical': 3, 'error': 2.

This object indicates the module which generated the message. 'dot11' - This value represents the module in controller responsible for handling the 802.11 messages. 'dot1x' - This value represents the module responsible for handling the extensible authentication protocol. 'pem' - This value represents the module responsible for handling the policy enforcement module. 'dhcp' - This value represents the module responsible for handling dhcp related messages. 'aaa' - This value represents the module responsible for handling radius related messages. 'voiceQoS' - This value represents the module responsible for handling voice/Qos module related messages. 'misc' - This value represents the module responsible for handling miscellaneous module messages. (eg: roam history). 'mobility' - This value represents the module responsible for handling mobility related messages. Enumeration: 'aaa': 5, 'dot11': 1, 'voiceQoS': 6, 'mobility': 8, 'misc': 7, 'dot1x': 2, 'pem': 3, 'dhcp': 4.

This object indicates if this message is an informational message or an error message. This object holds good only if the corresponding cldctClientInfoLevel object has a value of 'phase' or 'state'. A value of true indicates that this message is an informational message. A value of false indicates that this message is an error message.

This object represents the variable part of the message generated by the controller for this client. For example if the message to be shown to the user is 'Client got ip address 10.52.43.54', the '10.52.43.54' is a variable part which will be different for different clients.

This object represents the type of the messsage generated by the controller for this client.

This objects represents sub-type of the messsage generated by the controller for this client.

This object represents the maximum number of entries per client(cldcClientMacAddress) in the cldctClientInfoTable.

This table represents the clients which are being monitored by the controller during association. The types of clients that can be monitored are CCX, non-CCX and WGB clients. Entries are created by explicit management action by the user. A row is created by specifying the cldctWatchListModuleList, cldctWatchListTimeRemaining and cldcClientMacAddress with the 'RowStatus' changed to createAndGo. This indicates that the request is made to start storing the the messages on the controller for the client identified by cldcClientMacAddress. The added row is deleted by setting the corresponding instance of the RowStatus object to 'destroy'. In case if the agent finds that the time duration represented by cldctWatchListTimeRemaining has elapsed since the addtion of the client to the watchlist, it proceeds to delete the row automatically, if the row exists at that point of time. The messages stored on the controller can be obtained from cldctClientInfoTable.

Each entry in this table represents one instance of the client troubleshooting initiated by the user through a network manager.

This object is used to specify the list of modules per client whose messages will be stored by the controller. Any combination of the modules can be set. 'dot11' - This value represents the module in controller responsible for handling the 802.11 messages. 'dot1x' - This value represents the module responsible for handling the extensible authentication protocol related messages. 'pem' - This value represents the module responsible for handling the policy enforcement module. 'dhcp' - This value represents the module responsible for handling dhcp related messages. 'aaa' - This value represents the module responsible for handling radius related messages. 'voiceQoS' - This value represents the module responsible for handling voice/Qos module related messages. 'misc' - This value represents the module responsible for handling miscellaneous module messages (eg: roam history). 'mobility' - This value represents the module responsible for handling mobility related messages. Bits: 'aaa': 4, 'dot11': 0, 'voiceQoS': 5, 'mobility': 7, 'misc': 6, 'dot1x': 1, 'pem': 2, 'dhcp': 3.

This object is used to specify the time after which the client will be automatically removed from the watchlist.

This object represents the status of a row and is used to create and delete specific instances of rows in this table.

This table stores the last policy enforcement state of client in the controller. The state here is represented as a string. For example the state can be 'RUN','WEBAUTH_REQUIRED' etc. Entries are automaticaly added to this table when a 802.11 client associates to a controller. Entries in this table are automaticaly deleted by the controller when the 802.11 client disassociates from the controller.

Each entry represents a conceptual row in this table. An entry represents the last PEM state report by a wireless client.

This object represents the last policy enforcement manager state of the client in controller.

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

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

This is a collection of objects which can be configured per 802.11 clients for the controller to start monitoring them.

This is a collection of objects which represent the information of various watch listed clients present on the controller. The information includes the various states and phases that the client goes through while getting associated with the controller.

This is a collection of objects which represent the information on the types and sub-types of messages generated by the controller for the clients.