CISCO-LWAPP-DOT11-CCX-CLIENT-MIB
AI MIB Summary
The CISCO-LWAPP-DOT11-CCX-CLIENT-MIB monitors Cisco Central Controllers terminating LWAPP tunnels to manage 802.11 wireless clients (Mobile Nodes) and mesh network backhaul link quality metrics, specifically facilitating Client Context Exchange (CCX) and Link Test operations between Root Access Points (RAPs) and Mesh Access Points (MAPs).
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
Main OID:
ciscoLwappDot11CcxClientMIB.1.3.6.1.4.1.9.9.599.3.3
81
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
81 total| Object Name |
|---|
ciscoLwappDot11CcxClientMIBThis 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 MODULE-IDENTITY .1.3.6.1.4.1.9.9.599.3.3 |
ciscoLwappDot11CcxClientMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.3.0 |
ciscoClientCcxEventLogRequest OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.3.0.1 |
cldccEventLogsRequestTableThis 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. SEQUENCE OF CldccEventLogsRequestEntry .1.3.6.1.4.1.9.9.599.3.3.0.1.1 |
cldccEventLogsRequestEntryThere is an entry in the table where entry is identified
by the client Mac address. CldccEventLogsRequestEntry .1.3.6.1.4.1.9.9.599.3.3.0.1.1.1 |
cldccEventLogsRequestLogTypeThis is the type of the logs which is required from
the client.This can be Roaming,RSNA or Syslogs.rw Bits .1.3.6.1.4.1.9.9.599.3.3.0.1.1.1.1 |
cldccEventLogsRequestRowStatusThis field is used to add/remove entries from this
table.To add a row in this table, createAndGo
row status will be used.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.1.1.1.2 |
ciscoClientCcxEventLogResponse OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.3.0.2 |
cldccSysLogsTableThis table contains Sys logs of the various
ccxv5 clients. SEQUENCE OF CldccSysLogsEntry .1.3.6.1.4.1.9.9.599.3.3.0.2.1 |
cldccSysLogsEntryThere is an entry in the table for each entry
identified by the client mac address and dialog
token. CldccSysLogsEntry .1.3.6.1.4.1.9.9.599.3.3.0.2.1.1 |
cldccSysLogsIndexThis object stores the dialog token
exchanged between client and controller
for the give sys log request. Unsigned32 .1.3.6.1.4.1.9.9.599.3.3.0.2.1.1.1 |
cldccSysLogsTimeStampThis object stores the time stamp when the
syslog messages were generated.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.2.1.1.3 |
cldccSysLogsBufferThis stores the syslog messages generated on
the client side.ro OCTET STRING ( SIZE(256) ) .1.3.6.1.4.1.9.9.599.3.3.0.2.1.1.4 |
cldccRoamingLogsTableThis table contains Roaming logs of the clients. SEQUENCE OF CldccRoamingLogsEntry .1.3.6.1.4.1.9.9.599.3.3.0.2.2 |
cldccRoamingLogsEntryThere is an entry in the table for where each entry
is identified by the client mac address and dialog
token. CldccRoamingLogsEntry .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1 |
cldccRoamingLogsIndexThis is the index of the roaming logs.ro Unsigned32 .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1.1 |
cldccRoamingLogsTimeStampThis is the time stamp of the log.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1.2 |
cldccRoamingLogsTargetSSIDThis is the BSSID of the AP that is target of the
attempted transition.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1.3 |
cldccRoamingLogsSourceSSIDThis is the BSSID of the associated AP prior to
transition.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1.4 |
cldccRoamingLogsTransitionTimeThis 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.ro CiscoMilliSeconds (CISCO-TC) .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1.5 |
cldccRoamingLogsTransitionReasonThis field indicates the reason why a transition attempt occurred.ro Enumeration .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1.6 |
cldccRoamingLogsTransitionResultThis field shows the results of the attempted transition.ro INTEGER .1.3.6.1.4.1.9.9.599.3.3.0.2.2.1.7 |
cldccRsnaDataTableThis table contains Rsna data logs of the clients. SEQUENCE OF CldccRsnaDataEntry .1.3.6.1.4.1.9.9.599.3.3.0.2.3 |
cldccRsnaDataEntryThere is an entry in the table for where each entry
is identified by the client mac address and dialog
token. CldccRsnaDataEntry .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1 |
cldccRsnaDataIndexThis is the index of the Rsna Data. Unsigned32 .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.1 |
cldccRsnaDataTimeStampThis object stores the time stamp when the
rsna data were generated.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.2 |
cldccRsnaDataVersionThis is the RSNA Data Version.ro Unsigned32 .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.3 |
cldccRsnaDataTargetSSIDThis is the BSSID of the AP that is targeted.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.4 |
cldccRsnaDataAuthTypeThis attribute represents the authentication type
used.ro Enumeration .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.5 |
cldccRsnaDataResultThis attribute stores the result of the RSNA Data.ro INTEGER .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.6 |
cldccRsnaDataElemMultiCastOuisThis attribute represents the multicast ouis
of a RSNA element.ro OCTET STRING ( SIZE .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.7 |
cldccRsnaDataElemUnicastCastOuisThis field represents the unicast ouis
of a RSNA element.ro OCTET STRING ( SIZE .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.8 |
cldccRsnaDataElemAuthOuisThis field represents the auth ouis
of a RSNA element.ro OCTET STRING ( SIZE .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.9 |
cldccRsnaDataElemCapabilitiesThis field represents the
capabilities of the RSNA element .ro Unsigned32 .1.3.6.1.4.1.9.9.599.3.3.0.2.3.1.10 |
ciscoClientCcxEventLogStatus OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.3.0.3 |
cldccEventLogStatusTableThis table contains response status of the various
event log requests sent from the controller. SEQUENCE OF CldccEventLogStatusEntry .1.3.6.1.4.1.9.9.599.3.3.0.3.1 |
cldccEventLogStatusEntryThere is an entry in the table for each entry
identified by the client mac address. CldccEventLogStatusEntry .1.3.6.1.4.1.9.9.599.3.3.0.3.1.1 |
cldccRoamingLogsResponseStatusThis is the status of roaming log request.ro CcxEventLogResponseStatus .1.3.6.1.4.1.9.9.599.3.3.0.3.1.1.1 |
cldccRsnaLogsResponseStatusThis is the status of rsna log request.ro CcxEventLogResponseStatus .1.3.6.1.4.1.9.9.599.3.3.0.3.1.1.2 |
cldccSysLogsResponseStatusThis is the status of sys log request.ro CcxEventLogResponseStatus .1.3.6.1.4.1.9.9.599.3.3.0.3.1.1.3 |
ciscoClientCcxStatsRequest OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.3.0.4 |
cldccStatsReqTableThis table contains the stats req for the
ccx clients. SEQUENCE OF CldccStatsReqEntry .1.3.6.1.4.1.9.9.599.3.3.0.4.1 |
cldccStatsReqEntryThere is an entry in the table where entry
is identified by the client Mac address. CldccStatsReqEntry .1.3.6.1.4.1.9.9.599.3.3.0.4.1.1 |
cldccStatsReqStatusThere is an entry in the table where entry
is identified by the client Mac address.rw Enumeration .1.3.6.1.4.1.9.9.599.3.3.0.4.1.1.1 |
cldccStatsReqGroupIdThere is an entry in the table where entry
is identified by the client Mac address.rw Enumeration .1.3.6.1.4.1.9.9.599.3.3.0.4.1.1.2 |
cldccStatsReqDurationThis field represents the duration of the
measurement.rw CiscoMilliSeconds (CISCO-TC) .1.3.6.1.4.1.9.9.599.3.3.0.4.1.1.3 |
cldccStatsReqRowStatusThis field is used to add/remove entries from this
table.To add a row in this table, createAndGo
row status will be used.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.3.0.4.1.1.4 |
ciscoClientCcxStatsResponse OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.3.0.5 |
cldccStatsDot11RespTableThis table contains the stats response for the
ccx clients. SEQUENCE OF CldccStatsDot11RespEntry .1.3.6.1.4.1.9.9.599.3.3.0.5.1 |
cldccStatsDot11RespEntryThere is an entry in the table where entry
is identified by the client Mac address. CldccStatsDot11RespEntry .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1 |
cldccStatsRespTransmittedFragmentCountThis field represents the transmitted fragment
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.1 |
cldccStatsRespMulticastTransmittedFrameCountThis field represents the multicast
transmitted frame count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.2 |
cldccStatsRespFailedCountThis field represents the failed count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.3 |
cldccStatsRespRetryCountThis field represents the duplicate frame
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.4 |
cldccStatsRespMultipleRetryCountThis field represents the retry
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.5 |
cldccStatsRespFrameDuplicateCountThis field represents the duplicate frame
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.6 |
cldccStatsRespRtsSuccessCountThis field represents the RTS success
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.7 |
cldccStatsRespRtsFailureCountThis field represents the RTS failure
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.8 |
cldccStatsRespAckFailureCountThis field represents the ack failure
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.9 |
cldccStatsRespReceivedFragmentCountThis field represents the received fragment
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.10 |
cldccStatsRespMulticastReceivedFrameCountThis field represents the multicast received
frame count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.11 |
cldccStatsRespFcsErrorCountThis field represents the fcs error
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.12 |
cldccStatsRespTransmittedFrameCountThis field represents the transmitted frame
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.1.1.13 |
cldccStatsSecurityRespTableThis table contains the stats response for the
ccx clients. SEQUENCE OF CldccStatsSecurityRespEntry .1.3.6.1.4.1.9.9.599.3.3.0.5.2 |
cldccStatsSecurityRespEntryThere is an entry in the table where entry
is identified by the client Mac address. CldccStatsSecurityRespEntry .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1 |
cldccStatsRespSelectedPairwiseCipherThis field represents the pairwise
cipher.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.1 |
cldccStatsRespTkipIcvErrorsThis field represents the tkip icv error
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.2 |
cldccStatsRespTkipLocalMicFailuresThis field represents the local tkip
mic failure count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.3 |
cldccStatsRespCcmpReplaysThis field represents the ccmp replay
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.4 |
cldccStatsRespCcmpDecrypErrorsThis field represents the CCMP decrypt error
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.5 |
cldccStatsRespTkipReplaysThis field represents the tkip replay
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.6 |
cldccStatsRespMgmtStatsTkipIcvErrorsThis field represents the tkip icv error
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.7 |
cldccStatsRespMgmtStatsTkipLocalMicFailuresThis field represents the tkip local mic failure
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.8 |
cldccStatsRespMgmtStatsCcmpReplaysThis field represents the CCMP replay
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.9 |
cldccStatsRespMgmtStatsCcmpDecryptErrorsThis field represents the Ccmp decrypt error
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.10 |
cldccStatsRespMgmtStatsTkipReplaysThis field represents the tkip replay
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.11 |
cldccStatsRespMgmtStatsTkipMhdrErrorsThis field represents the tkip mhdr error
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.12 |
cldccStatsRespMgmtStatsCcmpMhdrErrorsThis field represents the Ccmp Mhdr error
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.13 |
cldccStatsRespMgmtStatsBroadcastDisassociateCountThis field represents the broadcast disassociate
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.14 |
cldccStatsRespMgmtStatsBroadcastDeauthenticateCountThis field represents the broadcast deauthenticate
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.15 |
cldccStatsRespMgmtStatsBroadcastActionFrameCountThis field represents the broadcast action frame
count.ro Counter32 .1.3.6.1.4.1.9.9.599.3.3.0.5.2.1.16 |