All MIBs › CISCO-LWAPP-DOT11-CCX-CLIENT-DIAG-MIB
Organization: Cisco Systems Inc.
Last Updated: 2006-06-24
Description: Cisco LWAPP MIB for CCX v5 wireless client diagnostic channel tests and responses, enabling automated client troubleshooting on Cisco WLAN controllers
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-DOT11-CCX-CLIENT-DIAG-MIB?
The CISCO-LWAPP-DOT11-CCX-CLIENT-DIAG-MIB enables Cisco Compatible Extensions v5 diagnostic testing of 802.11 wireless clients from Cisco Wireless LAN Controllers that terminate LWAPP tunnels from lightweight access points. It exposes request/response table pairs for running DHCP tests and ping/link tests against a wireless client to diagnose connectivity issues without requiring physical access to the client. Administrators use it to monitor the software/connectivity health of wireless clients on demand, initiating a diagnostic test via a request table row and reading the corresponding response table, such as DHCP offer received or ping test result, to pinpoint whether a client's problem is DHCP, backhaul link quality, or general reachability. It is specific to Cisco's CCXv5 client-diagnostic extensions layered on the broader LWAPP/802.11 controller MIB family, rather than a generic IEEE 802.11 standard. It is deployed in enterprise WLAN troubleshooting scenarios, particularly for mesh or problematic client connections where remote diagnostics reduce the need for on-site support. Engineers can download the CISCO-LWAPP-DOT11-CCX-CLIENT-DIAG-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-LWAPP-DOT11-CCX-CLIENT-DIAG-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) with LWAPP-connected access points
- 802.11 wireless client
Monitoring Examples
An admin creates a row in cldccDiagDhcpTestReqTable via cldccDiagDhcpTestReqRowStatus to trigger a DHCP test for a specific client, then reads cldccDiagDhcpTestRespTable's cldccDiagDhcpTestRespDhcpOffer to confirm whether a DHCP offer was actually received. Similarly, setting cldccDiagPingTestType and cldccDiagPingTestReqRowStatus in cldccDiagPingTestReqTable initiates a ping/link test, with results retrieved from cldccDiagPingTestRespTable, useful for diagnosing whether a mesh backhaul link is dropping packets.
What Can Be Monitored
- on-demand DHCP diagnostic test results
- on-demand ping/link test results
- test request row status
- DHCP offer reception during test
This MIB depends on
Related MIBs
Imported Objects
From CISCO-LWAPP-DOT11-CLIENT-CCX-TC-MIB
| CLDot11ClientDiagAssocReason | |
| CiscoLwappDot11ClientAuthMethod |
From CISCO-LWAPP-DOT11-CLIENT-MIB
| ciscoLwappDot11ClientCcxMIBObjects | OBJECT-IDENTITY |
| cldcClientMacAddress | OBJECT-TYPE |
From CISCO-SMI
| ciscoMgmt | OBJECT-IDENTITY |
From CISCO-TC
| CiscoMilliSeconds |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| MacAddress | |
| RowStatus | |
| TEXTUAL-CONVENTION | |
| TimeStamp | |
| TruthValue |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ciscoClientCcxDiagRequest | 1.3.6.1.4.1.9.9.599.3.2.0.1 | |||
| ciscoClientCcxDiagResponse | 1.3.6.1.4.1.9.9.599.3.2.0.2 | |||
| ciscoClientCcxDiagStatus | 1.3.6.1.4.1.9.9.599.3.2.0.3 | |||
| ciscoLwappDot11CcxClientDiagMIB | 1.3.6.1.4.1.9.9.599.3.2 | 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 | ||
| ciscoLwappDot11CcxClientDiagMIBNotifObjs | 1.3.6.1.4.1.9.9.599.3.2.2 | |||
| ciscoLwappDot11CcxClientDiagMIBNotifs | 1.3.6.1.4.1.9.9.599.3.2.1 | |||
| ciscoLwappDot11CcxClientDiagMIBObjects | 1.3.6.1.4.1.9.9.599.3.2.0 | |||
| cldccDiagAssociationTestReqEntry | 1.3.6.1.4.1.9.9.599.3.2.0.1.4.1 | not-accessible | There is an entry in the table for each entry identified by the client mac address. | |
| cldccDiagAssociationTestReqTable | 1.3.6.1.4.1.9.9.599.3.2.0.1.4 | not-accessible | This table contains association test request values for various clients. | |
| cldccDiagAssociationTestRespEntry | 1.3.6.1.4.1.9.9.599.3.2.0.2.4.4 | not-accessible | There is an entry in the table for each entry identified by the client mac address. | |
| T/F cldccDiagAssociationTestRespIsAssocComplete | 1.3.6.1.4.1.9.9.599.3.2.0.2.4.4.1 | TruthValue | read-only | Value of this field shall be 1 if the 802.11 association concluded normally,0 otherwise. |
| cldccDiagAssociationTestRespTable | 1.3.6.1.4.1.9.9.599.3.2.0.2.4 | not-accessible | This table contains association test response values for various clients. | |
| CLD cldccDiagAssocReasonCode | 1.3.6.1.4.1.9.9.599.3.2.2.2 | CLDot11ClientDiagAssocReason | accessible-for-notify | This object indicates the reason code for which the client has associated the diagnostic WLAN. |
| INT cldccDiagAssocTestReqBand | 1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.4 | INTEGER | read-create | This is band on which the client will try to connect to the AP. |
| MAC cldccDiagAssocTestReqBssid | 1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.1 | MacAddress | read-create | This is the bssid of the AP which the client has to try connecting to as a part of association test. |
| INT cldccDiagAssocTestReqChannel | 1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.3 | INTEGER | read-create | This is channel number on which the client will try to connect to the AP. |
| INT cldccDiagAssocTestReqPhyType | 1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.5 | INTEGER | read-create | This is phy type. |
| ROW cldccDiagAssocTestReqRowStatus | 1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.6 | RowStatus | read-create | This field is used to add/remove entries from this table.To add a row in this table, createAndGo row status will be used.To remove a row, this field will be set to destroy. |
| OCT cldccDiagAssocTestReqSsid | 1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.2 | OCTET STRING | read-create | This is the name of the SSID which the client has to try connecting to as a part of association test. |
| U32 cldccDiagAssocTestRespReturnedStatus | 1.3.6.1.4.1.9.9.599.3.2.0.2.4.4.2 | Unsigned32 | read-only | Value of this field shall be the value returned in the final 802.11 association response frame during the test. |
| INT cldccDiagAuthenticationTestReqBand | 1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.5 | INTEGER | read-create | This attribute represents the band. |
| MAC cldccDiagAuthenticationTestReqBssid | 1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.1 | MacAddress | read-create | This is the name of the AP which the client has to try connecting to as a part of authentication test. |
| INT cldccDiagAuthenticationTestReqChannel | 1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.3 | INTEGER | read-create | This attribute represents the channel number. |
| cldccDiagAuthenticationTestReqEntry | 1.3.6.1.4.1.9.9.599.3.2.0.1.5.1 | not-accessible | There is an entry in the table for each entry identified by the client mac address. | |
| INT cldccDiagAuthenticationTestReqPhyType | 1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.6 | INTEGER | read-create | This attribute represents the phy type. |
| U32 cldccDiagAuthenticationTestReqProfileId | 1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.2 | Unsigned32 | read-create | This is the name of the ProfileId which the client has to try connecting to as a part of authentication test. |
| ROW cldccDiagAuthenticationTestReqRowStatus | 1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.9 | RowStatus | read-create | This field is used to add/remove entries from this table.To add a row in this table,createAndGo row status will be used.To remove a row, this field will be set to destroy. |
| cldccDiagAuthenticationTestReqTable | 1.3.6.1.4.1.9.9.599.3.2.0.1.5 | not-accessible | This table contains association test request values for various clients. | |
| OCT cldccDiagAuthenticationTestRespEAPMethod | 1.3.6.1.4.1.9.9.599.3.2.0.2.5.5.3 | OCTET STRING | read-only | Value of this field shall be the EAP method returned in the final 802.11 authentication response frame during the test. |
| cldccDiagAuthenticationTestRespEntry | 1.3.6.1.4.1.9.9.599.3.2.0.2.5.5 | not-accessible | There is an entry in the table for each entry identified by the client mac address. | |
| T/F cldccDiagAuthenticationTestRespIsCompleted | 1.3.6.1.4.1.9.9.599.3.2.0.2.5.5.1 | TruthValue | read-only | Value of this field shall be 1 if the 802.11 association concluded normally,0 otherwise. |
| INT cldccDiagAuthenticationTestRespReturnedStatus | 1.3.6.1.4.1.9.9.599.3.2.0.2.5.5.2 | INTEGER | read-only | Value of this field shall be the value returned in the final 802.11 authentication response frame during the test |
| cldccDiagAuthenticationTestRespTable | 1.3.6.1.4.1.9.9.599.3.2.0.2.5 | not-accessible | This table contains authentication test response values for various clients. | |
| NTF cldccDiagClientAssociatedToDiagWlan | 1.3.6.1.4.1.9.9.599.3.2.1.1 | This notification is generated when a client associates to a diagnostic WLAN. | ||
| MAC cldccDiagClientMacAddress | 1.3.6.1.4.1.9.9.599.3.2.2.1 | MacAddress | accessible-for-notify | This object indicates the macaddress of the client associated to the diagnostic WLAN. |
| cldccDiagDhcpTestReqEntry | 1.3.6.1.4.1.9.9.599.3.2.0.1.1.1 | not-accessible | There is an entry in the table identified by the client mac address. | |
| ROW cldccDiagDhcpTestReqRowStatus | 1.3.6.1.4.1.9.9.599.3.2.0.1.1.1.1 | RowStatus | read-create | This field is used to add/remove entries from this table.To add a row in this table, createAndGo row status will be used.To remove a row, this field will be set to destroy. |
| cldccDiagDhcpTestReqTable | 1.3.6.1.4.1.9.9.599.3.2.0.1.1 | not-accessible | This table contains request params for dhcp test to be performed by the client. | |
| OCT cldccDiagDhcpTestRespDhcpOffer | 1.3.6.1.4.1.9.9.599.3.2.0.2.1.1.1 | OCTET STRING | read-only | This field will have the complete set of DHCP options returned in the DHCP Offer. |
| cldccDiagDhcpTestRespEntry | 1.3.6.1.4.1.9.9.599.3.2.0.2.1.1 | not-accessible | There is an entry in the table identified by the client mac address. | |
| cldccDiagDhcpTestRespTable | 1.3.6.1.4.1.9.9.599.3.2.0.2.1 | not-accessible | This table contains response for dhcp test performed by the client. | |
| cldccDiagDnsNameResolTestReqEntry | 1.3.6.1.4.1.9.9.599.3.2.0.1.3.1 | not-accessible | There is an entry in the table where each entry is identified by the client mac address. | |
| OCT cldccDiagDnsNameResolTestReqNetworkName | 1.3.6.1.4.1.9.9.599.3.2.0.1.3.1.1 | OCTET STRING | read-create | This is the name of the network which will be resolved by the client and the result reported to the controller. |
| ROW cldccDiagDnsNameResolTestReqRowStatus | 1.3.6.1.4.1.9.9.599.3.2.0.1.3.1.2 | RowStatus | read-create | This field is used to add/remove entries from this table.To add a row in this table, createAndGo row status will be used.To remove a row, this field will be set to destroy. |
| cldccDiagDnsNameResolTestReqTable | 1.3.6.1.4.1.9.9.599.3.2.0.1.3 | not-accessible | This table contains Dns Name resolution request params to be used for sending out a Diagnostic request to a client for resolving a network name. | |
| cldccDiagDnsNameResolTestRespEntry | 1.3.6.1.4.1.9.9.599.3.2.0.2.3.1 | not-accessible | There is an entry in the table where each entry is identified by a client mac address. | |
| IP cldccDiagDnsNameResolTestRespIpAddress | 1.3.6.1.4.1.9.9.599.3.2.0.2.3.1.2 | InetAddress | read-only | This is the ip address of the DNS server whose name was sent in the request. |
| IPt cldccDiagDnsNameResolTestRespIpAddressType | 1.3.6.1.4.1.9.9.599.3.2.0.2.3.1.1 | InetAddressType | read-only | This is type of the ip address of the DNS server whose name was sent in the request. |
| OCT cldccDiagDnsNameResolTestRespServerName | 1.3.6.1.4.1.9.9.599.3.2.0.2.3.1.3 | OCTET STRING | read-only | This is the name of the server whose ip address was resolved. |
| cldccDiagDnsNameResolTestRespTable | 1.3.6.1.4.1.9.9.599.3.2.0.2.3 | not-accessible | This table contains Dns Name Resolution test results sent by the client to the controller. | |
| INT cldccDiagMsgDisplayMsgType | 1.3.6.1.4.1.9.9.599.3.2.0.1.6.1.1 | INTEGER | read-create | This attribute represents the type of message to be displayed. |
| cldccDiagMsgDisplayReqEntry | 1.3.6.1.4.1.9.9.599.3.2.0.1.6.1 | not-accessible | There is an entry in the table for each entry identified by the client mac address. | |
| ROW cldccDiagMsgDisplayReqRowStatus | 1.3.6.1.4.1.9.9.599.3.2.0.1.6.1.2 | RowStatus | read-create | This field is used to add/remove entries from this table. To add a row in this table, createAndGo row status will be used.To remove a row, this field will be set to destroy. |
| cldccDiagMsgDisplayReqTable | 1.3.6.1.4.1.9.9.599.3.2.0.1.6 | not-accessible | This table contains message display request values for various clients. | |
| cldccDiagMsgDisplayRespEntry | 1.3.6.1.4.1.9.9.599.3.2.0.2.6.1 | not-accessible | There is an entry in the table for each entry identified by the client mac address. | |
| OCT cldccDiagMsgDisplayRespString | 1.3.6.1.4.1.9.9.599.3.2.0.2.6.1.1 | OCTET STRING | read-only | This is string which was sent to the client for display. |
| cldccDiagMsgDisplayRespTable | 1.3.6.1.4.1.9.9.599.3.2.0.2.6 | not-accessible | This table contains message display request values for various clients. | |
| cldccDiagPingTestReqEntry | 1.3.6.1.4.1.9.9.599.3.2.0.1.2.1 | not-accessible | There is an entry in the table where each entry is identified by the client mac address. | |
| ROW cldccDiagPingTestReqRowStatus | 1.3.6.1.4.1.9.9.599.3.2.0.1.2.1.2 | RowStatus | read-create | This field is used to add/remove entries from this table.To add a row in this table, createAndGo row status will be used.To remove a row, this field will be set to destroy. |
| cldccDiagPingTestReqTable | 1.3.6.1.4.1.9.9.599.3.2.0.1.2 | not-accessible | This table contains the parameters for DNS ping test request. | |
| MAC cldccDiagPingTestRespDestMacAddress | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.3 | MacAddress | read-only | The value of this field shall be the MAC address of the destination of the ICMP Echo Request frames. |
| cldccDiagPingTestRespEntry | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2 | not-accessible | There is an entry in the table where each entry is identified by the client mac address. | |
| IP cldccDiagPingTestRespIPAddress | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.2 | InetAddress | read-only | The value of this field shall be the IP address of the destination of the ICMP Echo Request frames. |
| IPt cldccDiagPingTestRespIPAddressType | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.1 | InetAddressType | read-only | The value of this field shall be the IP address type of the destination of the ICMP echo request frames. |
| CIS cldccDiagPingTestRespMaxEchoTIme | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.7 | CiscoMilliSeconds | read-only | The value of this field shall be the longest time in milliseconds,between the transmission of an ICMP echo Request between the transmission of an ICMP echo request frame and the receipt of the corresponding ICMP echo response frame. ICMP echo request frames for which no corresponding response is received shall be ignored in the determination of this value. |
| CIS cldccDiagPingTestRespMinEchoTIme | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.6 | CiscoMilliSeconds | read-only | The value of this field shall be the shortest time,in milliseconds, between the transmission of an ICMP echo request frame and the receipt of the corresponding ICMP Echo Response frame. |
| U32 cldccDiagPingTestRespPingsReceived | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.5 | Unsigned32 | read-only | The value of this field shall be the number of ICMP Echo Response frames received. |
| U32 cldccDiagPingTestRespPingsSent | 1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.4 | Unsigned32 | read-only | The value of this field shall be the number of ICMP Echo Request frames sent. |
| cldccDiagPingTestRespTable | 1.3.6.1.4.1.9.9.599.3.2.0.2.2 | not-accessible | This table contains response for Dns ping test request. | |
| INT cldccDiagPingTestType | 1.3.6.1.4.1.9.9.599.3.2.0.1.2.1.1 | INTEGER | read-create | This field is used to distinguish the type of test.It can be a ping to the dns server or the default gateway. |
| cldccDiagProfileRedirectReqEntry | 1.3.6.1.4.1.9.9.599.3.2.0.1.7.1 | not-accessible | There is an entry in the table for each entry identified by the client mac address. | |
| U32 cldccDiagProfileRedirectReqProfileId | 1.3.6.1.4.1.9.9.599.3.2.0.1.7.1.1 | Unsigned32 | read-create | This attribute represents the profile Id to which the client should be redirected. |
| ROW cldccDiagProfileRedirectReqRowStatus | 1.3.6.1.4.1.9.9.599.3.2.0.1.7.1.2 | RowStatus | read-create | This field is used to add/remove entries from this table. To add a row in this table, createAndGo row status will be used.To remove a row, this field will be set to destroy. |
| cldccDiagProfileRedirectReqTable | 1.3.6.1.4.1.9.9.599.3.2.0.1.7 | not-accessible | This table contains profile redirect request values for various clients. | |
| CIS cldccDiagTestLastResponseStatus | 1.3.6.1.4.1.9.9.599.3.2.0.3.1.1.2 | CiscoLwappCcxDiagResponseStatus | read-only | This field is used to represent the response of the last test performed. |
| CIS cldccDiagTestLastTestStatus | 1.3.6.1.4.1.9.9.599.3.2.0.3.1.1.1 | CiscoLwappCcxDiagTestStatus | read-only | This field is used to represent the status of the last test performed. |
| OCT cldccDiagTestLoggedFrameData | 1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.4 | OCTET STRING | read-only | The value of this field shall be the actual frame that was transmitted or received. |
| INT cldccDiagTestLoggedFrameDirection | 1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.2 | INTEGER | read-only | The value of this field shall be zero, when the logged frame in the Frame Content field is sent from (transmitted by) the client. It shall be one, otherwise. |
| cldccDiagTestLoggedFrameEntry | 1.3.6.1.4.1.9.9.599.3.2.0.2.8.1 | not-accessible | There is an entry in the table where each entry is identified by the client mac address. | |
| U32 cldccDiagTestLoggedFrameIndex | 1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.1 | Unsigned32 | read-only | The value of this field shall be the ordinal value of the logged frame. |
| cldccDiagTestLoggedFrameTable | 1.3.6.1.4.1.9.9.599.3.2.0.2.8 | not-accessible | This table contains logged frame data. | |
| TIM cldccDiagTestLoggedFrameTimeStamp | 1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.3 | TimeStamp | read-only | The value of this field shall be the timestamp value of the logged frame. |
| cldccDiagTestStatusEntry | 1.3.6.1.4.1.9.9.599.3.2.0.3.1.1 | not-accessible | There is an entry in the table identified by the client mac address. | |
| cldccDiagTestStatusTable | 1.3.6.1.4.1.9.9.599.3.2.0.3.1 | not-accessible | This table contains the status params for all the tests performed on the client. |
RFC description
Wireless client diagnostic testing and troubleshooting for Cisco CCX/LWAPP access points.
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.