CISCO-LWAPP-DOT11-CCX-CLIENT-DIAG-MIB
AI MIB Summary
The CISCO-LWAPP-DOT11-CCX-CLIENT-DIAG-MIB enables Cisco Central Controllers to monitor and manage diagnostic metrics for Client Control Extension (CCX) compliant wireless clients and mesh backhaul link quality within LWAPP-based architectures. This module specifically facilitates the collection of data regarding Mobile Node (MN) associations, Root AP (RAP) and Mesh AP (MAP) link tests, and signal-to-noise ratio (SNR) statistics to validate the integrity of the wireless distribution system.
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:
ciscoLwappDot11CcxClientDiagMIB.1.3.6.1.4.1.9.9.599.3.2
84
Objects
Active
Status
8
Dependencies
Imported Objects
Objects
84 total| Object Name |
|---|
ciscoLwappDot11CcxClientDiagMIBThis 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.2 |
ciscoLwappDot11CcxClientDiagMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.2.0 |
ciscoClientCcxDiagRequest OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.2.0.1 |
cldccDiagDhcpTestReqTableThis table contains request params for dhcp test to
be performed by the client. SEQUENCE OF CldccDiagDhcpTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.1 |
cldccDiagDhcpTestReqEntryThere is an entry in the table identified by the
client mac address. CldccDiagDhcpTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.1.1 |
cldccDiagDhcpTestReqRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.1.1.1 |
cldccDiagPingTestReqTableThis table contains the parameters for DNS ping test
request. SEQUENCE OF CldccDiagPingTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.2 |
cldccDiagPingTestReqEntryThere is an entry in the table where each entry is identified
by the client mac address. CldccDiagPingTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.2.1 |
cldccDiagPingTestTypeThis field is used to distinguish the type of
test.It can be a ping to the dns server or the
default gateway.rw Enumeration .1.3.6.1.4.1.9.9.599.3.2.0.1.2.1.1 |
cldccDiagPingTestReqRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.2.1.2 |
cldccDiagDnsNameResolTestReqTableThis table contains Dns Name resolution request
params to be used for sending out a Diagnostic
request to a client for resolving a network name. SEQUENCE OF CldccDiagDnsNameResolTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.3 |
cldccDiagDnsNameResolTestReqEntryThere is an entry in the table where each entry
is identified by the client mac address. CldccDiagDnsNameResolTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.3.1 |
cldccDiagDnsNameResolTestReqNetworkNameThis is the name of the network which will be
resolved by the client and the result reported
to the controller.rw OCTET STRING .1.3.6.1.4.1.9.9.599.3.2.0.1.3.1.1 |
cldccDiagDnsNameResolTestReqRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.3.1.2 |
cldccDiagAssociationTestReqTableThis table contains association test request values
for various clients. SEQUENCE OF CldccDiagAssociationTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.4 |
cldccDiagAssociationTestReqEntryThere is an entry in the table for each entry
identified by the client mac address. CldccDiagAssociationTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.4.1 |
cldccDiagAssocTestReqBssidThis is the bssid of the AP which the client
has to try connecting to as a part of association
test.rw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.1 |
cldccDiagAssocTestReqSsidThis is the name of the SSID which the client has
to try connecting to as a part of association test.rw OCTET STRING .1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.2 |
cldccDiagAssocTestReqChannelThis is channel number on which the client will
try to connect to the AP.rw INTEGER .1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.3 |
cldccDiagAssocTestReqBandThis is band on which the client will
try to connect to the AP.rw INTEGER .1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.4 |
cldccDiagAssocTestReqPhyTypeThis is phy type.rw INTEGER .1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.5 |
cldccDiagAssocTestReqRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.4.1.6 |
cldccDiagAuthenticationTestReqTableThis table contains association test request values
for various clients. SEQUENCE OF CldccDiagAuthenticationTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.5 |
cldccDiagAuthenticationTestReqEntryThere is an entry in the table for each entry
identified by the client mac address. CldccDiagAuthenticationTestReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.5.1 |
cldccDiagAuthenticationTestReqBssidThis is the name of the AP which the client has to try
connecting to as a part of authentication test.rw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.1 |
cldccDiagAuthenticationTestReqProfileIdThis is the name of the ProfileId which the client has to try
connecting to as a part of authentication test.rw Unsigned32 .1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.2 |
cldccDiagAuthenticationTestReqChannelThis attribute represents the channel number.rw INTEGER .1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.3 |
cldccDiagAuthenticationTestReqBandThis attribute represents the band.rw INTEGER .1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.5 |
cldccDiagAuthenticationTestReqPhyTypeThis attribute represents the phy type.rw INTEGER .1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.6 |
cldccDiagAuthenticationTestReqRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.5.1.9 |
cldccDiagMsgDisplayReqTableThis table contains message display request values for
various clients. SEQUENCE OF CldccDiagMsgDisplayReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.6 |
cldccDiagMsgDisplayReqEntryThere is an entry in the table for each entry
identified by the client mac address. CldccDiagMsgDisplayReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.6.1 |
cldccDiagMsgDisplayMsgTypeThis attribute represents the type of message
to be displayed.rw Enumeration .1.3.6.1.4.1.9.9.599.3.2.0.1.6.1.1 |
cldccDiagMsgDisplayReqRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.6.1.2 |
cldccDiagProfileRedirectReqTableThis table contains profile redirect request values for
various clients. SEQUENCE OF CldccDiagProfileRedirectReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.7 |
cldccDiagProfileRedirectReqEntryThere is an entry in the table for each entry
identified by the client mac address. CldccDiagProfileRedirectReqEntry .1.3.6.1.4.1.9.9.599.3.2.0.1.7.1 |
cldccDiagProfileRedirectReqProfileIdThis attribute represents the profile Id
to which the client should be redirected.rw Unsigned32 .1.3.6.1.4.1.9.9.599.3.2.0.1.7.1.1 |
cldccDiagProfileRedirectReqRowStatusThis 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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.1.7.1.2 |
ciscoClientCcxDiagResponse OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.2.0.2 |
cldccDiagDhcpTestRespTableThis table contains response for dhcp
test performed by the client. SEQUENCE OF CldccDiagDhcpTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.1 |
cldccDiagDhcpTestRespEntryThere is an entry in the table
identified by the client mac address. CldccDiagDhcpTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.1.1 |
cldccDiagDhcpTestRespDhcpOfferThis field will have the complete set
of DHCP options returned in the DHCP Offer.ro OCTET STRING .1.3.6.1.4.1.9.9.599.3.2.0.2.1.1.1 |
cldccDiagPingTestRespTableThis table contains response for Dns ping test
request. SEQUENCE OF CldccDiagPingTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.2 |
cldccDiagPingTestRespEntryThere is an entry in the table where each entry is
identified by the client mac address. CldccDiagPingTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2 |
cldccDiagPingTestRespIPAddressTypeThe value of this field shall be the IP address
type of the destination of the ICMP echo
request frames.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.1 |
cldccDiagPingTestRespIPAddressThe value of this field shall be the IP address
of the destination of the ICMP Echo Request
frames.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.2 |
cldccDiagPingTestRespDestMacAddressThe value of this field shall be the MAC address
of the destination of the ICMP Echo Request
frames.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.3 |
cldccDiagPingTestRespPingsSentThe value of this field shall be the number
of ICMP Echo Request frames sent.ro Unsigned32 .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.4 |
cldccDiagPingTestRespPingsReceivedThe value of this field shall be the number of
ICMP Echo Response frames received.ro Unsigned32 .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.5 |
cldccDiagPingTestRespMinEchoTImeThe 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.ro CiscoMilliSeconds (CISCO-TC) .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.6 |
cldccDiagPingTestRespMaxEchoTImeThe 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.ro CiscoMilliSeconds (CISCO-TC) .1.3.6.1.4.1.9.9.599.3.2.0.2.2.2.7 |
cldccDiagDnsNameResolTestRespTableThis table contains Dns Name Resolution test results
sent by the client to the controller. SEQUENCE OF CldccDiagDnsNameResolTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.3 |
cldccDiagDnsNameResolTestRespEntryThere is an entry in the table where each entry is
identified by a client mac address. CldccDiagDnsNameResolTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.3.1 |
cldccDiagDnsNameResolTestRespIpAddressTypeThis is type of the ip address of the
DNS server whose name was sent in the
request.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.599.3.2.0.2.3.1.1 |
cldccDiagDnsNameResolTestRespIpAddressThis is the ip address of the DNS server
whose name was sent in the request.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.599.3.2.0.2.3.1.2 |
cldccDiagDnsNameResolTestRespServerNameThis is the name of the server whose
ip address was resolved.ro OCTET STRING .1.3.6.1.4.1.9.9.599.3.2.0.2.3.1.3 |
cldccDiagAssociationTestRespTableThis table contains association test
response values for various clients. SEQUENCE OF CldccDiagAssociationTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.4 |
cldccDiagAssociationTestRespEntryThere is an entry in the table for each entry
identified by the client mac address. CldccDiagAssociationTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.4.4 |
cldccDiagAssociationTestRespIsAssocCompleteValue of this field shall be 1 if the 802.11
association concluded normally,0 otherwise.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.2.4.4.1 |
cldccDiagAssocTestRespReturnedStatusValue of this field shall be the value returned
in the final 802.11 association response frame
during the test.ro Unsigned32 .1.3.6.1.4.1.9.9.599.3.2.0.2.4.4.2 |
cldccDiagAuthenticationTestRespTableThis table contains authentication test response
values for various clients. SEQUENCE OF CldccDiagAuthenticationTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.5 |
cldccDiagAuthenticationTestRespEntryThere is an entry in the table for each entry
identified by the client mac address. CldccDiagAuthenticationTestRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.5.5 |
cldccDiagAuthenticationTestRespIsCompletedValue of this field shall be 1 if the 802.11
association concluded normally,0 otherwise.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.2.5.5.1 |
cldccDiagAuthenticationTestRespReturnedStatusValue of this field shall be the value returned in
the final 802.11 authentication response frame
during the testro INTEGER .1.3.6.1.4.1.9.9.599.3.2.0.2.5.5.2 |
cldccDiagAuthenticationTestRespEAPMethodValue of this field shall be the EAP method returned
in the final 802.11 authentication response frame
during the test.ro OCTET STRING .1.3.6.1.4.1.9.9.599.3.2.0.2.5.5.3 |
cldccDiagMsgDisplayRespTableThis table contains message display request values
for various clients. SEQUENCE OF CldccDiagMsgDisplayRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.6 |
cldccDiagMsgDisplayRespEntryThere is an entry in the table for each entry
identified by the client mac address. CldccDiagMsgDisplayRespEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.6.1 |
cldccDiagMsgDisplayRespStringThis is string which was sent to the client for display.ro OCTET STRING .1.3.6.1.4.1.9.9.599.3.2.0.2.6.1.1 |
cldccDiagTestLoggedFrameTableThis table contains logged frame data. SEQUENCE OF CldccDiagTestLoggedFrameEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.8 |
cldccDiagTestLoggedFrameEntryThere is an entry in the table where each entry
is identified by the client mac address. CldccDiagTestLoggedFrameEntry .1.3.6.1.4.1.9.9.599.3.2.0.2.8.1 |
cldccDiagTestLoggedFrameIndexThe value of this field shall be the ordinal
value of the logged frame.ro Unsigned32 .1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.1 |
cldccDiagTestLoggedFrameDirectionThe 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.ro Enumeration .1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.2 |
cldccDiagTestLoggedFrameTimeStampThe value of this field shall be the
timestamp value of the logged frame.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.3 |
cldccDiagTestLoggedFrameDataThe value of this field shall be the actual
frame that was transmitted or received.ro OCTET STRING .1.3.6.1.4.1.9.9.599.3.2.0.2.8.1.4 |
ciscoClientCcxDiagStatus OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.2.0.3 |
cldccDiagTestStatusTableThis table contains the status params for
all the tests performed on the client. SEQUENCE OF CldccDiagTestStatusEntry .1.3.6.1.4.1.9.9.599.3.2.0.3.1 |
cldccDiagTestStatusEntryThere is an entry in the table identified by the
client mac address. CldccDiagTestStatusEntry .1.3.6.1.4.1.9.9.599.3.2.0.3.1.1 |
cldccDiagTestLastTestStatusThis field is used to represent the status of the
last test performed.ro CiscoLwappCcxDiagTestStatus .1.3.6.1.4.1.9.9.599.3.2.0.3.1.1.1 |
cldccDiagTestLastResponseStatusThis field is used to represent the response of the
last test performed.ro CiscoLwappCcxDiagResponseStatus .1.3.6.1.4.1.9.9.599.3.2.0.3.1.1.2 |
ciscoLwappDot11CcxClientDiagMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.2.1 |
cldccDiagClientAssociatedToDiagWlanThis notification is generated when a client associates
to a diagnostic WLAN. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.599.3.2.1.1 |
ciscoLwappDot11CcxClientDiagMIBNotifObjs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.599.3.2.2 |
cldccDiagClientMacAddressThis object indicates the macaddress of the client
associated to the diagnostic WLAN.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.9.9.599.3.2.2.1 |
cldccDiagAssocReasonCodeThis object indicates the reason code for which
the client has associated the diagnostic WLAN.ro CLDot11ClientDiagAssocReason (CISCO-LWAPP-DOT11-CLIENT-CCX-TC-MIB) .1.3.6.1.4.1.9.9.599.3.2.2.2 |