CISCO-LWAPP-DOT11-CCX-CLIENT-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 (LWAPP) tunnel from Light-weight Access Points. Link Test is performed to learn the backhaul link quality between two mesh neighboring mesh nodes. The arrangement of the controller (referred to as CC in the diagram) and mesh nodes (RAP and MAP) LWAPP APs ,client(MN) and NMS appear as follows. +.......+ +.......+ + + + + + NMS + + NMS + + + + + +.......+ +.......+ . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ + + + + + + + + + CC + + CC + + CC + + CC + + + + + + + + + +......+ +......+ +......+ +......+ .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + RAP + + RAP + + RAP + + RAP + + RAP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . . . . . . . . . . . . . . . . . . . . . . . . +......+ +......+ +......+ +......+ +......+ + + + + + + + + + + + MAP + + MN + + MAP + + MAP + + MAP + + + + + + + + + + + +......+ +......+ +......+ +......+ +......+ . . .. . . . . .. . . . . .. . . . . . . +......+ +......+ +......+ +......+. +......+ + + + + + + + + + + + MAP + + MAP + + MAP + + MAP + + 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. The controllers and the IDS systems exchange information through Cisco proprietary event exchange mechanisms. 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 is also referred to as 'controller'. Mobile Node ( MN ) A roaming 802.11 wireless device in a wireless network associated with an access point. Mobile Node and client are used interchangeably. Network Management System ( NMS ) The station from which the administrator manages the wired and wireless networks. Mesh Node A mesh node is defined as a physical or logical entity in the mesh network participating in forming the mesh backhaul. There are two types of mesh nodes supported in Cisco mesh network:RAP and MAP. Root AP (RAP) The AP forming the bridge between a wired and a mesh network with an Ethernet interface to the wired network and a 802.11 radio interface to the mesh network Mesh AP (MAP). The AP extending wireless coverage similar to a repeater in a mesh network and consists of a 802.11 uplink and a 802.11 downlink. On a single-radio backhaul, both uplink and downlink exist on the same radio and are logical links only. On a multi-radio backhaul, they may exist on different radios.MAP APs associates directly with RAP APs or with another MAP AP. Each association of AP (MAP-MAP or RAP-MAP) with another AP forms parent-child relationship. Mesh Network Network starting with the wireless backhaul downlink of the RAP and all the entities below except any attached network to the Ethernet link of MAPs. A mesh network below a single RAP is also referred to as a 'Mesh Sector'.A mesh network consists of mesh nodes. A single mesh network is always augmented to a single wired network. Mesh Link A logical 802.11 link between two mesh nodes. A single link is point-to-point. All point-to-multipoint links are considered as multiple mesh links. Often referred to as mesh backhaul link. Mesh Backhaul A Mesh backhaul consists of mesh nodes and mesh links terminating at a RAP. This necessarily creates a one- to-one relationship between a 'mesh network', 'mesh sector' and a 'mesh backhaul' where these terms can be used interchangeably. SNR Signal to Noise ratio on the 802.11 radio. Bridged network The bridged network is defined as the network(s) attached to the Ethernet port of any MAP. There can be multiple such networks attached to a single mesh network. 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

This table contains list of clients to which the event log request has been sent for fetching the logs. The table has a column corresponding to the type of logs to be fetched for each client.The current logs supported are Roaming, RSNA and Syslog.

There is an entry in the table where entry is identified by the client Mac address.

This is the type of the logs which is required from the client.This can be Roaming,RSNA or Syslogs. Bits: 'syslog': 2, 'roaming': 0, 'rsna': 1.

This field is used to add/remove entries from this table.To add a row in this table, createAndGo row status will be used.

This table contains Sys logs of the various ccxv5 clients.

There is an entry in the table for each entry identified by the client mac address and dialog token.

This object stores the dialog token exchanged between client and controller for the give sys log request.

This object stores the time stamp when the syslog messages were generated.

This stores the syslog messages generated on the client side.

This table contains Roaming logs of the clients.

There is an entry in the table for where each entry is identified by the client mac address and dialog token.

This is the index of the roaming logs.

This is the time stamp of the log.

This is the BSSID of the AP that is target of the attempted transition.

This is the BSSID of the associated AP prior to transition.

This is the difference from last time a frame could have been transmitted on the source BSS to the time when a non-802.1x data frame can be attempted on the target BSS.

This field indicates the reason why a transition attempt occurred. Enumeration: 'max-retransmissions-excedded': 15, 'many-broadcast-disassociations': 17, 'failed-8021x-4way-handshake': 11, 'inf-directed-roam': 4, 'first-association-to-wlan': 5, 'insufficient-capacity': 3, 'failed-8021x-eap-auth': 10, 'excessive-interference': 16, 'normal-roam-better-ap': 8, 'many-data-mic-failures': 13, 'many-broadcast-deauth': 18, 'roaming-to-cellular': 7, 'roaming-from-cellular': 6, 'many-mgt-mic-failures': 14, 'normal-roam-load-bal': 2, 'disassociated-or-deauthenticated': 9, 'normal-roam-poor-link': 1, 'many-replay-counters': 12.

This field shows the results of the attempted transition.

This table contains Rsna data logs of the clients.

There is an entry in the table for where each entry is identified by the client mac address and dialog token.

This is the index of the Rsna Data.

This object stores the time stamp when the rsna data were generated.

This is the RSNA Data Version.

This is the BSSID of the AP that is targeted.

This attribute represents the authentication type used. Enumeration: 'ccx-dot1x-eap-md5': 6, 'ccx-dot1x-psk': 8, 'ccx-dot1x-leap': 0, 'ccx-dot1x-unknown': 255, 'ccx-dot1x-eap-sim': 7, 'ccx-dot1x-eap-tls': 2, 'ccx-dot1x-peap-v0': 4, 'ccx-dot1x-peap-v1': 5, 'ccx-dot1x-eap-fast': 1, 'ccx-dot1x-eap-ttls': 3.

This attribute stores the result of the RSNA Data.

This attribute represents the multicast ouis of a RSNA element.

This field represents the unicast ouis of a RSNA element.

This field represents the auth ouis of a RSNA element.

This field represents the capabilities of the RSNA element .

This table contains response status of the various event log requests sent from the controller.

There is an entry in the table for each entry identified by the client mac address.

This is the status of roaming log request.

This is the status of rsna log request.

This is the status of sys log request.

This table contains the stats req for the ccx clients.

There is an entry in the table where entry is identified by the client Mac address.

There is an entry in the table where entry is identified by the client Mac address. Enumeration: 'success': 4, 'refused': 1, 'invalid-state': 2, 'failure': 3, 'incapable': 0, 'inprogress': 5.

There is an entry in the table where entry is identified by the client Mac address. Enumeration: 'dot11-meas': 0, 'security-meas': 1.

This field represents the duration of the measurement.

This field is used to add/remove entries from this table.To add a row in this table, createAndGo row status will be used.

This table contains the stats response for the ccx clients.

There is an entry in the table where entry is identified by the client Mac address.

This field represents the transmitted fragment count.

This field represents the multicast transmitted frame count.

This field represents the failed count.

This field represents the duplicate frame count.

This field represents the retry count.

This field represents the duplicate frame count.

This field represents the RTS success count.

This field represents the RTS failure count.

This field represents the ack failure count.

This field represents the received fragment count.

This field represents the multicast received frame count.

This field represents the fcs error count.

This field represents the transmitted frame count.

This table contains the stats response for the ccx clients.

There is an entry in the table where entry is identified by the client Mac address.

This field represents the pairwise cipher.

This field represents the tkip icv error count.

This field represents the local tkip mic failure count.

This field represents the ccmp replay count.

This field represents the CCMP decrypt error count.

This field represents the tkip replay count.

This field represents the tkip icv error count.

This field represents the tkip local mic failure count.

This field represents the CCMP replay count.

This field represents the Ccmp decrypt error count.

This field represents the tkip replay count.

This field represents the tkip mhdr error count.

This field represents the Ccmp Mhdr error count.

This field represents the broadcast disassociate count.

This field represents the broadcast deauthenticate count.

This field represents the broadcast action frame count.