1--* Ambika Mohanty
2--
3--Copyright (c) 2006 by Cisco Systems, Inc.
4--All rights reserved.
5--
6--This MIB captures all the elements used to represent the requests
7--and responses during the dignostic tests of a ccxv5 client.
8--
9--The Diagnostic Channel capability is a mechanism that automates
10--the troubleshooting of client problems communicating with the WLAN.
11--The mechanism is available, on demand, from any AP in the WLAN
12--advertising the capability.When triggered by a client having
13--difficulties, the diagnostic channel is a WLAN configured to
14--provide the most robust communication methods with the least
15--obstacles to communication placed in the path of the client.
16--The client and AP will proceed through a defined set of tests
17--and responses in an attempt to identify the cause of the
18--communication difficulties experienced by the client.
19--*******************************************************************
20
21CISCO-LWAPP-DOT11-CCX-CLIENT-DIAG-MIB DEFINITIONS ::= BEGIN
22
23IMPORTS
24        MODULE-IDENTITY,
25        OBJECT-TYPE,
26        Unsigned32
27                FROM SNMPv2-SMI
28        MODULE-COMPLIANCE,
29        OBJECT-GROUP
30                FROM SNMPv2-CONF
31        MacAddress,
32        TruthValue,
33        RowStatus,
34        TimeStamp,
35	TEXTUAL-CONVENTION
36                FROM SNMPv2-TC
37        InetAddressType,
38        InetAddress
39                FROM INET-ADDRESS-MIB
40	CiscoMilliSeconds
41	        FROM CISCO-TC
42        CiscoLwappDot11ClientAuthMethod,
43	CLDot11ClientDiagAssocReason
44                FROM CISCO-LWAPP-DOT11-CLIENT-CCX-TC-MIB
45        cldcClientMacAddress,
46        ciscoLwappDot11ClientCcxMIBObjects
47                FROM CISCO-LWAPP-DOT11-CLIENT-MIB
48        ciscoMgmt
49                FROM CISCO-SMI;
50
51--********************************************************************
52--*  MODULE IDENTITY
53--********************************************************************
54
55ciscoLwappDot11CcxClientDiagMIB   MODULE-IDENTITY
56
57        LAST-UPDATED   "200606240000Z"
58        ORGANIZATION   "Cisco Systems Inc."
59        CONTACT-INFO
60               "        Cisco Systems,
61                        Customer Service
62                Postal: 170 West Tasman Drive
63                        San Jose, CA  95134
64                        USA
65                   Tel: +1 800 553-NETS
66
67                 Email: cs-wnbu-snmp@cisco.com"
68
69        DESCRIPTION
70                "This MIB is intended to be implemented on all those
71                devices operating as Central Controllers (CC) that
72                terminate the Light Weight Access Point Protocol
73                (LWAPP) tunnel from Light-weight  Access Points.
74
75                Link Test is performed to learn the backhaul link
76                quality between two mesh neighboring mesh nodes.
77
78                The arrangement of the controller
79                (referred to as CC in the diagram) and mesh nodes
80                (RAP and MAP) LWAPP APs ,client(MN) and NMS appear
81                as follows.
82
83                 +.......+                 +.......+
84                 +       +                 +       +
85                 +  NMS  +                 +  NMS  +
86                 +       +                 +       +
87                 +.......+                 +.......+
88                    .                         .
89                 .    .                     .   .
90              .         .                .        .
91            .            .             .            .
92        +......+     +......+     +......+           +......+
93        +      +     +      +     +      +           +      +
94        +  CC  +     +  CC  +     +  CC  +           +  CC  +
95        +      +     +      +     +      +           +      +
96        +......+     +......+     +......+           +......+
97          ..            .             .                 .
98          ..            .             .                 .
99         .  .            .             .                 .
100        .    .            .             .                 .
101       .      .            .             .                 .
102      .        .            .             .                 .
103   +......+ +......+     +......+      +......+          +......+
104   +      + +      +     +      +      +      +          +      +
105   +  RAP + +  RAP +     +  RAP  +     +  RAP +          +  RAP +
106   +      + +      +     +      +      +      +          +      +
107   +......+ +......+     +......+      +......+          +......+
108      .        .              .             .                 .
109       .        .              .             .                 .
110        .        .              .             .                 .
111        .          .              .             .                 .
112        .           .              .             .                 .
113      +......+ +......+     +......+      +......+          +......+
114      +      + +      +     +      +      +      +          +      +
115      +  MAP + +  MN  +     +  MAP +      +  MAP +          +  MAP +
116      +      + +      +     +      +      +      +          +      +
117      +......+ +......+     +......+      +......+          +......+
118          .                    .                          ..    .
119          . .                  .                     ..        .
120          .   .                .                  ..            .
121          .     .              .              .                .
122      +......+ +......+     +......+      +......+.         +......+
123      +      + +      +     +      +      +      +          +      +
124      +  MAP + +  MAP +     +  MAP +      +  MAP +          +  MN  +
125      +      + +      +     +      +      +      +          +      +
126      +......+ +......+     +......+      +......+          +......+
127
128
129
130
131                The LWAPP tunnel exists between the controller and
132                the APs.  The MNs communicate with the APs through
133                the protocol defined by the 802.11 standard.  The
134                controllers and the IDS systems exchange information
135                through Cisco proprietary event exchange mechanisms.
136
137                LWAPP APs, upon bootup, discover and join one of the
138                controllers and the controller pushes the
139                configuration, that includes the WLAN parameters, to
140                the LWAPP APs. The APs then encapsulate all the 802.11
141                frames from wireless clients inside LWAPP frames and
142                forward the LWAPP frames to the controller.
143
144                                   GLOSSARY
145
146                Access Point ( AP )
147
148                An entity that contains an 802.11 medium access
149                control ( MAC ) and physical layer ( PHY ) interface
150                and provides access to the distribution services via
151                the wireless medium for associated clients.
152
153                LWAPP APs encapsulate all the 802.11 frames in
154                LWAPP frames and sends them to the controller to which
155                it is logically connected.
156
157                Central Controller ( CC )
158
159                The central entity that terminates the LWAPP protocol
160                tunnel from the LWAPP APs.  Throughout this MIB,
161                this entity is also referred to as 'controller'.
162
163                Mobile Node ( MN )
164
165                A roaming 802.11 wireless device in a wireless
166                network associated with an access point. Mobile Node
167                and client are used interchangeably.
168
169                Network Management System ( NMS )
170
171                The station from which the administrator manages the
172                wired and wireless networks.
173
174                Mesh Node
175
176                A mesh node is defined as a physical or logical entity
177                in the mesh network participating in forming the mesh
178                backhaul. There are two types of mesh nodes supported
179                in Cisco mesh network:RAP and MAP.
180
181                Root AP (RAP)
182
183                The AP forming the bridge between a wired and a mesh
184                network with an Ethernet interface to the wired
185                network and a 802.11 radio interface to the mesh
186                network
187
188                Mesh AP (MAP).
189
190                The AP extending wireless coverage similar to a
191                repeater in a mesh network and consists of a 802.11
192                uplink and a 802.11 downlink. On a single-radio
193                backhaul, both uplink and downlink exist on the same
194                radio and are logical links only. On a multi-radio
195                backhaul, they may exist on different radios.MAP APs
196                associates directly with RAP APs or with another MAP
197                AP. Each association of AP (MAP-MAP or RAP-MAP) with
198                another AP forms parent-child relationship.
199
200                Mesh Network
201
202                Network starting with the wireless backhaul downlink
203                of the RAP and all the entities below except any
204                attached network to the Ethernet link of MAPs. A mesh
205                network below a single RAP is also referred to as a
206                'Mesh Sector'.A mesh network consists of mesh nodes.
207                A single mesh network is always augmented to a single
208                wired network.
209
210                Mesh Link
211
212                A logical 802.11 link between two mesh nodes. A single
213                link is point-to-point. All point-to-multipoint links
214                are considered as multiple mesh links. Often referred
215                to as mesh backhaul link.
216
217                Mesh Backhaul
218
219                A Mesh backhaul consists of mesh nodes and mesh links
220                terminating at a RAP. This necessarily creates a one-
221                to-one relationship between a 'mesh network', 'mesh
222                sector' and a 'mesh backhaul' where these terms can be
223                used interchangeably.
224
225                SNR
226                Signal to Noise ratio on the 802.11 radio.
227
228                Bridged network
229                The bridged network is defined as the network(s)
230                attached to the Ethernet port of any MAP. There can be
231                multiple such networks attached to a single mesh
232                network.
233
234                REFERENCE
235
236                [1] Wireless LAN Medium Access Control ( MAC ) and
237                Physical Layer ( PHY ) Specifications.
238
239                [2] Draft-obara-capwap-lwapp-00.txt, IETF Light
240                Weight Access Point Protocol "
241
242        REVISION      "200604100000Z"
243        DESCRIPTION
244                "Initial version of this MIB module."
245        ::= { ciscoLwappDot11ClientCcxMIBObjects 2 }
246
247ciscoLwappDot11CcxClientDiagMIBObjects  OBJECT IDENTIFIER
248        ::={ ciscoLwappDot11CcxClientDiagMIB 0 }
249
250ciscoLwappDot11CcxClientDiagMIBNotifs OBJECT IDENTIFIER
251	::={ ciscoLwappDot11CcxClientDiagMIB 1 }
252
253ciscoLwappDot11CcxClientDiagMIBNotifObjs OBJECT IDENTIFIER
254	::={ ciscoLwappDot11CcxClientDiagMIB 2 }
255
256ciscoClientCcxDiagRequest OBJECT IDENTIFIER
257	::={ ciscoLwappDot11CcxClientDiagMIBObjects 1 }
258
259ciscoClientCcxDiagResponse OBJECT IDENTIFIER
260	::={ ciscoLwappDot11CcxClientDiagMIBObjects 2 }
261
262ciscoClientCcxDiagStatus OBJECT IDENTIFIER
263	::={ ciscoLwappDot11CcxClientDiagMIBObjects 3 }
264
265--- *************************************************************
266--- This textual convention is used to represet the test result
267--- of the various diagnostic tests
268--- *************************************************************
269
270CiscoLwappCcxDiagResponseStatus ::= TEXTUAL-CONVENTION
271
272	STATUS    current
273	DESCRIPTION
274		"This attribute represents the response status of the ccx
275                diag tests."
276
277	SYNTAX INTEGER {
278         successful(0),
279         fail(1),
280         refused(3),
281         incapable(4),
282         unknown(5)
283	}
284
285CiscoLwappCcxDiagTestStatus ::= TEXTUAL-CONVENTION
286
287	STATUS    current
288	DESCRIPTION
289		"This attribute represents the last test status of the ccx
290                diag tests."
291
292	SYNTAX INTEGER {
293         successful(0),
294         pending(1),
295         timeout(3),
296         stopped(4),
297         mismatch(5)
298	}
299
300
301CiscoLwappDot11ClientDot1xCredential::= TEXTUAL-CONVENTION
302
303	STATUS    current
304	DESCRIPTION
305                "This attribute represents the dotx
306                credential identifier."
307
308	SYNTAX INTEGER {
309          pre-sharedkey(0),
310          username-password(1),
311          xdot(2),
312          other-cert(3),
313          one-time-password(4),
314          secure-id-token(5),
315          none(255)
316          }
317
318CiscoLwappDot11ClientAbortTestReason::= TEXTUAL-CONVENTION
319
320	STATUS    current
321	DESCRIPTION
322                "This attribute represents the reason
323                for abortion of ccx diag test."
324
325	SYNTAX INTEGER {
326	reserved(0),
327	timeout(1),
328	cancelled-by-operator(2)
329        }
330
331CiscoLwappDot11ClientInitiateTest::= TEXTUAL-CONVENTION
332
333	STATUS    current
334	DESCRIPTION
335                "This attribute says whether the test
336		is to be started or aborted."
337
338	SYNTAX INTEGER {
339	initiate-test(1),
340	abort-test(2)
341        }
342
343--- *******************************************************************
344--- To determine that DHCP is operating properly between the controller
345--- and client, the DHCP test executes a complete DHCP Discover/Offer/
346--- Request/ACK exchange.The client shall attempt to obtain a DHCP
347--- lease, beginning with a broadcast DHCP Discover packet.  The client
348--- shall log the time of transmission and reception of each DHCP
349--- packet, as well as the entire content of the frame containing those
350--- packets, for subsequent transmission to the AP.The frames captured
351--- and logged shall be in Cleartext, even if the frames were
352--- cldccDiagDhcpTestClientMacAddress  MacAddress,
353--- originally encrypted.The following two tables are used to represent
354--- request and response parameters of DHCP Test.
355--- *******************************************************************
356
357--- *******************************************************************
358-- DHCP Test Request Table
359--- *******************************************************************
360
361cldccDiagDhcpTestReqTable   OBJECT-TYPE
362
363    SYNTAX      SEQUENCE OF CldccDiagDhcpTestReqEntry
364    MAX-ACCESS  not-accessible
365    STATUS      current
366    DESCRIPTION
367               "This table contains request params for dhcp test to
368               be performed by the client."
369
370::= { ciscoClientCcxDiagRequest 1}
371
372cldccDiagDhcpTestReqEntry   OBJECT-TYPE
373
374    SYNTAX       CldccDiagDhcpTestReqEntry
375    MAX-ACCESS   not-accessible
376    STATUS       current
377    DESCRIPTION
378               "There is an entry in the table identified by the
379               client mac address."
380    INDEX
381    {
382      cldcClientMacAddress
383    }
384
385::= {cldccDiagDhcpTestReqTable 1}
386
387
388CldccDiagDhcpTestReqEntry::=
389
390    SEQUENCE
391    {
392       cldccDiagDhcpTestReqRowStatus RowStatus
393    }
394
395cldccDiagDhcpTestReqRowStatus OBJECT-TYPE
396
397    SYNTAX      RowStatus
398    MAX-ACCESS  read-create
399    STATUS      current
400    DESCRIPTION
401                "This field is used to add/remove entries from this
402		table.To add a row in this table, createAndGo row status
403                will be used.To remove a row, this field will be set to
404                destroy."
405
406::= { cldccDiagDhcpTestReqEntry 1}
407
408
409---*******************************************************************
410--- DHCP Test Response Table
411---*******************************************************************
412
413cldccDiagDhcpTestRespTable   OBJECT-TYPE
414
415   SYNTAX      SEQUENCE OF CldccDiagDhcpTestRespEntry
416   MAX-ACCESS  not-accessible
417   STATUS      current
418   DESCRIPTION
419               "This table contains response for dhcp
420               test performed by the client."
421
422::= { ciscoClientCcxDiagResponse  1}
423
424cldccDiagDhcpTestRespEntry  OBJECT-TYPE
425
426   SYNTAX       CldccDiagDhcpTestRespEntry
427   MAX-ACCESS   not-accessible
428   STATUS       current
429   DESCRIPTION
430              "There is an entry in the table
431              identified by the client mac address."
432   INDEX
433	{
434         cldcClientMacAddress
435        }
436
437::= { cldccDiagDhcpTestRespTable 1}
438
439
440CldccDiagDhcpTestRespEntry::=
441
442	SEQUENCE
443        {
444        cldccDiagDhcpTestRespDhcpOffer OCTET STRING
445	}
446
447
448cldccDiagDhcpTestRespDhcpOffer    OBJECT-TYPE
449
450     SYNTAX      OCTET STRING (SIZE(1..256 ))
451     MAX-ACCESS  read-only
452     STATUS      current
453     DESCRIPTION
454                 "This field will have the complete set
455                 of DHCP options returned in the DHCP Offer."
456
457::= { cldccDiagDhcpTestRespEntry 1}
458
459--- *******************************************************************
460--- To determine that IP connectivity exists to the Dns server,
461--- the Dns server ping test causes the client to execute a ping
462--- test of the Dns server obtained in the DHCP test.
463--- Upon receipt of the Dns server ping test request element, the client
464--- shall cause the normally instantiated protocol stack to transmit
465--- one or more ICMP echo request packets (ping packets) to the Dns
466--- server, using the parameters supplied in the ping request from the
467--- AP.For the duration of the test, the client shall log the time of
468--- transmission and reception of all packets, as well as the entire
469--- content of the frames containing those packets, for subsequent
470--- transmission to the AP.
471---
472--- The following two tables represent request and response tables for
473--- ping tests.
474--- *******************************************************************
475
476
477--- *******************************************************************
478--- Dns Server Ping Test  Request
479-- ********************************************************************
480
481
482cldccDiagPingTestReqTable  OBJECT-TYPE
483
484  SYNTAX       SEQUENCE OF CldccDiagPingTestReqEntry
485  MAX-ACCESS   not-accessible
486  STATUS       current
487  DESCRIPTION
488	     "This table contains the parameters for DNS ping test
489	     request."
490
491 ::= { ciscoClientCcxDiagRequest 2 }
492
493cldccDiagPingTestReqEntry  OBJECT-TYPE
494
495    SYNTAX      CldccDiagPingTestReqEntry
496    MAX-ACCESS 	not-accessible
497    STATUS     	current
498    DESCRIPTION
499	      "There is an entry in the table where each entry is identified
500	      by the client mac address."
501     INDEX
502     {
503	cldcClientMacAddress
504     }
505
506 ::= { cldccDiagPingTestReqTable 1 }
507
508
509CldccDiagPingTestReqEntry::=
510
511    SEQUENCE {
512        cldccDiagPingTestType INTEGER,
513	cldccDiagPingTestReqRowStatus RowStatus
514    }
515
516cldccDiagPingTestType OBJECT-TYPE
517
518    SYNTAX      INTEGER {
519                 dns-server(1),
520                 default-gw(2)
521		}
522    MAX-ACCESS  read-create
523    STATUS      current
524    DESCRIPTION
525                "This field is used to distinguish the type of
526                test.It can be a ping to the dns server or the
527	       	default gateway."
528
529::= { cldccDiagPingTestReqEntry 1 }
530
531cldccDiagPingTestReqRowStatus OBJECT-TYPE
532
533    SYNTAX      RowStatus
534    MAX-ACCESS  read-create
535    STATUS      current
536    DESCRIPTION
537                "This field is used to add/remove entries from this
538		table.To add a row in this table, createAndGo row status
539                will be used.To remove a row, this field will be set to
540                destroy."
541
542::= { cldccDiagPingTestReqEntry 2 }
543
544
545--- *******************************************************************
546--- Dns Server Ping Test  Response
547--- *******************************************************************
548
549cldccDiagPingTestRespTable  OBJECT-TYPE
550
551     SYNTAX       SEQUENCE OF CldccDiagPingTestRespEntry
552     MAX-ACCESS   not-accessible
553     STATUS       current
554     DESCRIPTION
555                  "This table contains response for Dns ping test
556		  request."
557
558::= { ciscoClientCcxDiagResponse  2 }
559
560
561cldccDiagPingTestRespEntry  OBJECT-TYPE
562
563        SYNTAX      CldccDiagPingTestRespEntry
564        MAX-ACCESS  not-accessible
565        STATUS      current
566        DESCRIPTION
567                    "There is an entry in the table where each entry is
568                    identified by the client mac address."
569	INDEX
570        {
571         cldcClientMacAddress
572        }
573
574::= { cldccDiagPingTestRespTable 2 }
575
576
577CldccDiagPingTestRespEntry ::=
578
579      SEQUENCE
580       {
581       cldccDiagPingTestRespIPAddressType InetAddressType,
582       cldccDiagPingTestRespIPAddress InetAddress,
583       cldccDiagPingTestRespDestMacAddress MacAddress,
584       cldccDiagPingTestRespPingsSent Unsigned32,
585       cldccDiagPingTestRespPingsReceived Unsigned32,
586       cldccDiagPingTestRespMaxEchoTIme CiscoMilliSeconds,
587       cldccDiagPingTestRespMinEchoTIme CiscoMilliSeconds
588      }
589
590cldccDiagPingTestRespIPAddressType  OBJECT-TYPE
591
592    SYNTAX       InetAddressType
593    MAX-ACCESS 	 read-only
594    STATUS     	 current
595    DESCRIPTION
596                  "The value of this field shall be the IP address
597		  type of the destination of the ICMP echo
598                  request frames."
599
600::= { cldccDiagPingTestRespEntry 1 }
601
602
603cldccDiagPingTestRespIPAddress  OBJECT-TYPE
604
605    SYNTAX       InetAddress
606    MAX-ACCESS 	 read-only
607    STATUS     	 current
608    DESCRIPTION
609                  "The value of this field shall be the IP address
610                  of the destination of the ICMP Echo Request
611                  frames."
612
613::= { cldccDiagPingTestRespEntry 2 }
614
615
616cldccDiagPingTestRespDestMacAddress OBJECT-TYPE
617
618     SYNTAX       MacAddress
619     MAX-ACCESS   read-only
620     STATUS       current
621     DESCRIPTION
622                  "The value of this field shall be the MAC address
623                  of the destination of the ICMP Echo Request
624                  frames."
625
626::= { cldccDiagPingTestRespEntry 3 }
627
628
629cldccDiagPingTestRespPingsSent OBJECT-TYPE
630
631    SYNTAX        Unsigned32
632    MAX-ACCESS 	  read-only
633    STATUS     	  current
634    DESCRIPTION
635                 "The value of this field shall be the number
636                 of ICMP Echo Request frames sent."
637
638::= { cldccDiagPingTestRespEntry 4 }
639
640
641cldccDiagPingTestRespPingsReceived OBJECT-TYPE
642
643     SYNTAX       Unsigned32
644     MAX-ACCESS   read-only
645     STATUS       current
646     DESCRIPTION
647                "The value of this field shall be the number of
648                ICMP Echo Response frames received."
649
650::= { cldccDiagPingTestRespEntry 5 }
651
652
653cldccDiagPingTestRespMinEchoTIme OBJECT-TYPE
654
655   SYNTAX      CiscoMilliSeconds
656   MAX-ACCESS  read-only
657   STATUS      current
658   DESCRIPTION
659              "The value of this field shall be the shortest time,in
660               milliseconds, between the transmission of an ICMP echo
661	       request frame and the receipt of the corresponding ICMP
662	       Echo Response frame."
663
664::= { cldccDiagPingTestRespEntry 6 }
665
666
667cldccDiagPingTestRespMaxEchoTIme OBJECT-TYPE
668
669   SYNTAX      CiscoMilliSeconds
670   MAX-ACCESS  read-only
671   STATUS      current
672   DESCRIPTION
673              "The value of this field shall be the longest time
674	      in milliseconds,between the transmission of an ICMP
675              echo Request between the transmission of an ICMP echo
676              request frame and the receipt of the corresponding
677	      ICMP echo response frame.
678              ICMP echo request  frames for which no corresponding
679              response is received shall be ignored in the
680	      determination of this value."
681
682::= { cldccDiagPingTestRespEntry 7 }
683
684-- *******************************************************************
685-- To determine that name resolution is functioning correctly,
686-- the DNS test causes the client to attempt to resolve a network
687-- name known to be resolvable.Upon receipt of the DNS name
688-- resolution test request element, the client shall cause the
689-- normally instantiated protocol stack to request the resolution
690-- of the network (host) name provided in the element.For the duration
691-- of the test, the client shall log the time of transmission and
692-- reception of all packets, as well as the content of the entire
693-- frame containing those packets, for subsequent transmission to the
694-- AP.Upon completion of the DNS exchange, whether by successful
695-- resolution of the network name or normal protocol timeout, the
696-- client shall report the success or failure of the test to the AP.
697-- *******************************************************************
698
699--- Dns Name Resolution Request Table ----
700
701cldccDiagDnsNameResolTestReqTable OBJECT-TYPE
702
703    SYNTAX      SEQUENCE OF CldccDiagDnsNameResolTestReqEntry
704    MAX-ACCESS 	not-accessible
705    STATUS     	current
706    DESCRIPTION
707               "This table contains Dns Name resolution request
708               params to be used for sending out a Diagnostic
709               request to a client for resolving a network name."
710
711::= { ciscoClientCcxDiagRequest  3}
712
713
714cldccDiagDnsNameResolTestReqEntry  OBJECT-TYPE
715
716    SYNTAX     	CldccDiagDnsNameResolTestReqEntry
717    MAX-ACCESS 	not-accessible
718    STATUS     	current
719    DESCRIPTION
720               "There is an entry in the table where each entry
721               is identified by the client mac address."
722    INDEX
723    {
724        cldcClientMacAddress
725    }
726
727::= { cldccDiagDnsNameResolTestReqTable 1}
728
729CldccDiagDnsNameResolTestReqEntry::=
730
731    SEQUENCE
732    {
733    cldccDiagDnsNameResolTestReqNetworkName OCTET STRING,
734    cldccDiagDnsNameResolTestReqRowStatus RowStatus
735    }
736
737cldccDiagDnsNameResolTestReqNetworkName    OBJECT-TYPE
738
739    SYNTAX      OCTET STRING(SIZE(1..256))
740    MAX-ACCESS 	read-create
741    STATUS     	current
742    DESCRIPTION
743               "This is the name of the network which will be
744	       resolved by the client and the result reported
745	       to the controller."
746
747::= { cldccDiagDnsNameResolTestReqEntry  1}
748
749cldccDiagDnsNameResolTestReqRowStatus OBJECT-TYPE
750
751    SYNTAX      RowStatus
752    MAX-ACCESS 	read-create
753    STATUS     	current
754    DESCRIPTION
755             "This field is used to add/remove entries from this
756             table.To add a row in this table, createAndGo row
757             status will be used.To remove a row, this field
758             will be set to destroy."
759
760::= { cldccDiagDnsNameResolTestReqEntry  2 }
761
762--- Dns Name Resolution Response Table ----
763
764cldccDiagDnsNameResolTestRespTable OBJECT-TYPE
765
766   SYNTAX      SEQUENCE OF CldccDiagDnsNameResolTestRespEntry
767   MAX-ACCESS  not-accessible
768   STATUS      current
769   DESCRIPTION
770              "This table contains Dns Name Resolution test results
771              sent by the client to the controller."
772
773::= { ciscoClientCcxDiagResponse  3}
774
775
776cldccDiagDnsNameResolTestRespEntry  OBJECT-TYPE
777
778   SYNTAX       CldccDiagDnsNameResolTestRespEntry
779   MAX-ACCESS 	not-accessible
780   STATUS     	current
781   DESCRIPTION
782              "There is an entry in the table where each entry is
783              identified by a client mac address."
784   INDEX
785   {
786      cldcClientMacAddress
787   }
788
789::= { cldccDiagDnsNameResolTestRespTable 1}
790
791
792CldccDiagDnsNameResolTestRespEntry::=
793
794    SEQUENCE  {
795    cldccDiagDnsNameResolTestRespIpAddressType  InetAddressType,
796    cldccDiagDnsNameResolTestRespIpAddress  InetAddress,
797    cldccDiagDnsNameResolTestRespServerName OCTET STRING
798    }
799
800cldccDiagDnsNameResolTestRespIpAddressType OBJECT-TYPE
801
802    SYNTAX     InetAddressType
803    MAX-ACCESS 	read-only
804    STATUS     	current
805    DESCRIPTION
806               "This is type of the ip address of the
807	       DNS server whose name was sent in the
808               request."
809
810::= { cldccDiagDnsNameResolTestRespEntry  1}
811
812
813cldccDiagDnsNameResolTestRespIpAddress OBJECT-TYPE
814
815    SYNTAX     InetAddress
816    MAX-ACCESS 	read-only
817    STATUS     	current
818    DESCRIPTION
819               "This is the ip address of the DNS server
820               whose name was sent in the request."
821
822::= { cldccDiagDnsNameResolTestRespEntry  2}
823
824cldccDiagDnsNameResolTestRespServerName OBJECT-TYPE
825
826    SYNTAX      OCTET STRING(SIZE(1..256))
827    MAX-ACCESS 	read-only
828    STATUS     	current
829    DESCRIPTION
830               "This is the name of the server whose
831	       ip address was resolved."
832
833::= { cldccDiagDnsNameResolTestRespEntry  3 }
834
835
836cldccDiagAssociationTestReqTable   OBJECT-TYPE
837
838   SYNTAX      SEQUENCE OF CldccDiagAssociationTestReqEntry
839   MAX-ACCESS  not-accessible
840   STATUS      current
841   DESCRIPTION
842              "This table contains association test request values
843              for various clients."
844
845::= { ciscoClientCcxDiagRequest 4}
846
847cldccDiagAssociationTestReqEntry  OBJECT-TYPE
848
849     SYNTAX        CldccDiagAssociationTestReqEntry
850     MAX-ACCESS    not-accessible
851     STATUS        current
852     DESCRIPTION
853                 "There is an entry in the table for each entry
854                 identified by the client mac address."
855    INDEX
856    {
857       cldcClientMacAddress
858    }
859
860::= {cldccDiagAssociationTestReqTable 1}
861
862CldccDiagAssociationTestReqEntry::=
863
864   SEQUENCE
865    {
866    cldccDiagAssocTestReqBssid	MacAddress,
867    cldccDiagAssocTestReqSsid	OCTET STRING,
868    cldccDiagAssocTestReqChannel INTEGER,
869    cldccDiagAssocTestReqBand INTEGER,
870    cldccDiagAssocTestReqPhyType INTEGER,
871    cldccDiagAssocTestReqRowStatus RowStatus
872    }
873
874cldccDiagAssocTestReqBssid OBJECT-TYPE
875
876    SYNTAX       MacAddress
877    MAX-ACCESS 	 read-create
878    STATUS     	 current
879    DESCRIPTION
880              "This is the bssid of the AP which the client
881              has to try connecting to as a part of association
882	      test."
883
884::= { cldccDiagAssociationTestReqEntry 1 }
885
886
887cldccDiagAssocTestReqSsid  OBJECT-TYPE
888
889    SYNTAX       OCTET STRING (SIZE(1..32))
890    MAX-ACCESS 	 read-create
891    STATUS     	 current
892    DESCRIPTION
893              "This is the name of the SSID which the client has
894              to try connecting to as a part of association test."
895
896::= { cldccDiagAssociationTestReqEntry 2 }
897
898cldccDiagAssocTestReqChannel OBJECT-TYPE
899
900    SYNTAX       INTEGER(0..255)
901    MAX-ACCESS 	 read-create
902    STATUS     	 current
903    DESCRIPTION
904              "This is channel number on which the client will
905	      try to connect to the AP."
906
907::= { cldccDiagAssociationTestReqEntry 3 }
908
909cldccDiagAssocTestReqBand OBJECT-TYPE
910
911    SYNTAX       INTEGER(0..255)
912    MAX-ACCESS 	 read-create
913    STATUS     	 current
914    DESCRIPTION
915              "This is band on which the client will
916	      try to connect to the AP."
917
918::= { cldccDiagAssociationTestReqEntry 4 }
919
920cldccDiagAssocTestReqPhyType OBJECT-TYPE
921
922    SYNTAX       INTEGER(0..255)
923    MAX-ACCESS 	 read-create
924    STATUS     	 current
925    DESCRIPTION
926              "This is phy type."
927
928::= { cldccDiagAssociationTestReqEntry 5 }
929
930cldccDiagAssocTestReqRowStatus OBJECT-TYPE
931
932    SYNTAX     	 RowStatus
933    MAX-ACCESS 	 read-create
934    STATUS     	 current
935    DESCRIPTION
936               "This field is used to add/remove entries from this
937               table.To add a row in this table, createAndGo row
938               status will be used.To remove a row, this field
939               will be set to destroy."
940
941::= { cldccDiagAssociationTestReqEntry 6 }
942
943-- Association Response Table
944
945cldccDiagAssociationTestRespTable   OBJECT-TYPE
946
947   SYNTAX       SEQUENCE OF CldccDiagAssociationTestRespEntry
948   MAX-ACCESS 	not-accessible
949   STATUS     	current
950   DESCRIPTION
951                "This table contains association test
952                response values for various clients."
953
954::= { ciscoClientCcxDiagResponse 4 }
955
956
957cldccDiagAssociationTestRespEntry  OBJECT-TYPE
958
959    SYNTAX       CldccDiagAssociationTestRespEntry
960    MAX-ACCESS 	 not-accessible
961    STATUS     	 current
962    DESCRIPTION
963                 "There is an entry in the table for each entry
964                  identified by the client mac address."
965    INDEX
966    {
967          cldcClientMacAddress
968    }
969
970::= { cldccDiagAssociationTestRespTable 4}
971
972
973CldccDiagAssociationTestRespEntry::=
974
975    SEQUENCE
976    {
977        cldccDiagAssociationTestRespIsAssocComplete    TruthValue,
978        cldccDiagAssocTestRespReturnedStatus Unsigned32
979    }
980
981  cldccDiagAssociationTestRespIsAssocComplete    OBJECT-TYPE
982
983    SYNTAX       TruthValue
984    MAX-ACCESS 	 read-only
985    STATUS     	 current
986    DESCRIPTION
987                "Value of this field shall be 1 if the 802.11
988                association concluded normally,0 otherwise."
989
990  ::= { cldccDiagAssociationTestRespEntry 1 }
991
992
993  cldccDiagAssocTestRespReturnedStatus	OBJECT-TYPE
994
995    SYNTAX        Unsigned32
996    MAX-ACCESS 	  read-only
997    STATUS     	  current
998    DESCRIPTION
999                "Value of this field shall be the value returned
1000	       	in the final 802.11 association response frame
1001                during the test. "
1002
1003  ::= { cldccDiagAssociationTestRespEntry 2 }
1004
1005--- Authentication Request Table
1006
1007cldccDiagAuthenticationTestReqTable    OBJECT-TYPE
1008
1009  SYNTAX       SEQUENCE OF CldccDiagAuthenticationTestReqEntry
1010  MAX-ACCESS   not-accessible
1011  STATUS       current
1012  DESCRIPTION
1013              "This table contains association test request values
1014	      for various clients."
1015
1016::= { ciscoClientCcxDiagRequest  5}
1017
1018cldccDiagAuthenticationTestReqEntry  OBJECT-TYPE
1019
1020  SYNTAX       CldccDiagAuthenticationTestReqEntry
1021  MAX-ACCESS   not-accessible
1022  STATUS       current
1023  DESCRIPTION
1024            "There is an entry in the table for each entry
1025	    identified by the client mac address."
1026  INDEX
1027  {
1028       cldcClientMacAddress
1029  }
1030
1031::= { cldccDiagAuthenticationTestReqTable 1}
1032
1033
1034CldccDiagAuthenticationTestReqEntry::=
1035
1036   SEQUENCE
1037   {
1038    cldccDiagAuthenticationTestReqBssid MacAddress,
1039    cldccDiagAuthenticationTestReqProfileId  Unsigned32,
1040    cldccDiagAuthenticationTestReqChannel  INTEGER,
1041    cldccDiagAuthenticationTestReqBand  INTEGER,
1042    cldccDiagAuthenticationTestReqPhyType INTEGER,
1043    cldccDiagAuthenticationTestReqRowStatus RowStatus
1044  }
1045
1046cldccDiagAuthenticationTestReqBssid OBJECT-TYPE
1047
1048  SYNTAX      MacAddress
1049  MAX-ACCESS  read-create
1050  STATUS      current
1051  DESCRIPTION
1052          "This is the name of the AP which the client has to try
1053	  connecting to as a part of authentication test."
1054
1055::= { cldccDiagAuthenticationTestReqEntry 1 }
1056
1057cldccDiagAuthenticationTestReqProfileId  OBJECT-TYPE
1058
1059  SYNTAX      Unsigned32
1060  MAX-ACCESS  read-create
1061  STATUS      current
1062  DESCRIPTION
1063             "This is the name of the ProfileId which the client has to try
1064	     connecting to as a part of authentication test."
1065
1066::= { cldccDiagAuthenticationTestReqEntry 2 }
1067
1068cldccDiagAuthenticationTestReqChannel OBJECT-TYPE
1069
1070  SYNTAX      INTEGER(0..255)
1071  MAX-ACCESS  read-create
1072  STATUS      current
1073  DESCRIPTION
1074          "This attribute represents the channel number."
1075
1076::= { cldccDiagAuthenticationTestReqEntry 3 }
1077
1078cldccDiagAuthenticationTestReqBand OBJECT-TYPE
1079
1080  SYNTAX      INTEGER(0..255)
1081  MAX-ACCESS  read-create
1082  STATUS      current
1083  DESCRIPTION
1084          "This attribute represents the band."
1085
1086::= { cldccDiagAuthenticationTestReqEntry 5 }
1087
1088cldccDiagAuthenticationTestReqPhyType OBJECT-TYPE
1089
1090  SYNTAX      INTEGER(0..255)
1091  MAX-ACCESS  read-create
1092  STATUS      current
1093  DESCRIPTION
1094          "This attribute represents the phy type."
1095
1096::= { cldccDiagAuthenticationTestReqEntry 6 }
1097
1098cldccDiagAuthenticationTestReqRowStatus OBJECT-TYPE
1099
1100  SYNTAX      RowStatus
1101  MAX-ACCESS  read-create
1102  STATUS      current
1103  DESCRIPTION
1104           "This field is used to add/remove entries from this
1105           table.To add a row in this table,createAndGo row
1106           status will be used.To remove a row, this field will
1107           be set to destroy."
1108
1109::= { cldccDiagAuthenticationTestReqEntry 9}
1110
1111--- Authentication Respose Table
1112
1113cldccDiagAuthenticationTestRespTable   OBJECT-TYPE
1114
1115    SYNTAX      SEQUENCE OF CldccDiagAuthenticationTestRespEntry
1116    MAX-ACCESS  not-accessible
1117    STATUS     	current
1118    DESCRIPTION
1119                 "This table contains authentication test response
1120                 values for various clients."
1121
1122::= { ciscoClientCcxDiagResponse 5}
1123
1124cldccDiagAuthenticationTestRespEntry  OBJECT-TYPE
1125
1126   SYNTAX        CldccDiagAuthenticationTestRespEntry
1127   MAX-ACCESS 	 not-accessible
1128   STATUS     	 current
1129   DESCRIPTION
1130                "There is an entry in the table for each entry
1131                identified by the client mac address."
1132   INDEX
1133    {
1134       cldcClientMacAddress
1135    }
1136
1137::= { cldccDiagAuthenticationTestRespTable 5}
1138
1139
1140CldccDiagAuthenticationTestRespEntry::=
1141
1142   SEQUENCE  {
1143   cldccDiagAuthenticationTestRespIsCompleted  TruthValue,
1144   cldccDiagAuthenticationTestRespReturnedStatus INTEGER,
1145   cldccDiagAuthenticationTestRespEAPMethod
1146	                       OCTET STRING
1147   }
1148
1149cldccDiagAuthenticationTestRespIsCompleted   OBJECT-TYPE
1150
1151  SYNTAX       TruthValue
1152  MAX-ACCESS   read-only
1153  STATUS       current
1154  DESCRIPTION
1155            "Value of this field shall be 1 if the 802.11
1156             association concluded normally,0 otherwise."
1157
1158::= { cldccDiagAuthenticationTestRespEntry 1 }
1159
1160
1161cldccDiagAuthenticationTestRespReturnedStatus	OBJECT-TYPE
1162
1163  SYNTAX       INTEGER(0..255)
1164  MAX-ACCESS    read-only
1165  STATUS     	current
1166  DESCRIPTION
1167                 "Value of this field shall be the value returned in
1168                 the final 802.11 authentication response frame
1169                 during the test "
1170
1171::= { cldccDiagAuthenticationTestRespEntry  2 }
1172
1173
1174cldccDiagAuthenticationTestRespEAPMethod  OBJECT-TYPE
1175
1176  SYNTAX        OCTET STRING(SIZE (0..255))
1177  MAX-ACCESS    read-only
1178  STATUS        current
1179  DESCRIPTION
1180                "Value of this field shall be the EAP method returned
1181                in the final 802.11 authentication response frame
1182                during the test. "
1183
1184::= { cldccDiagAuthenticationTestRespEntry 3 }
1185
1186
1187cldccDiagMsgDisplayReqTable    OBJECT-TYPE
1188
1189    SYNTAX       SEQUENCE OF CldccDiagMsgDisplayReqEntry
1190    MAX-ACCESS 	 not-accessible
1191    STATUS     	 current
1192    DESCRIPTION
1193                "This table contains message display request values for
1194                 various clients."
1195
1196::= { ciscoClientCcxDiagRequest  6}
1197
1198cldccDiagMsgDisplayReqEntry OBJECT-TYPE
1199
1200    SYNTAX       CldccDiagMsgDisplayReqEntry
1201    MAX-ACCESS   not-accessible
1202    STATUS     	 current
1203    DESCRIPTION
1204                "There is an entry in the table for each entry
1205	       	identified by the client mac address."
1206   INDEX
1207   {
1208       cldcClientMacAddress
1209   }
1210
1211::= { cldccDiagMsgDisplayReqTable 1}
1212
1213CldccDiagMsgDisplayReqEntry::=
1214
1215   SEQUENCE
1216    {
1217     cldccDiagMsgDisplayMsgType      INTEGER,
1218     cldccDiagMsgDisplayReqRowStatus RowStatus
1219  }
1220
1221cldccDiagMsgDisplayMsgType OBJECT-TYPE
1222
1223   SYNTAX        INTEGER
1224                 {
1225                  invalid-ssid(1),
1226                  invalid-network-settings(2),
1227                  wlan-capability-mismatch(3),
1228                  bad-credentials(4),
1229                  call-support(5),
1230                  problem-resolved(6),
1231                  resolution-incomplete(7),
1232                  try-again-later(8),
1233                  user-action-required(9),
1234                  trouble-shooting-refused-by-network(10),
1235                  retrieving-client-reports(11),
1236                  retrieving-client-logs(12),
1237                  retrieval-complete(13),
1238                  begining-association-test(14),
1239                  begining-dhcp-test(15),
1240                  begining-network-connectivity-test(16),
1241                  begining-dns-ping-test(17),
1242                  begining-name-resolution-test(18),
1243                  begining-dot1x-test(19),
1244                  redirecting-client-to-a-profile(20),
1245                  test-complete(21),
1246                  test-passed(22),
1247                  test-failed(23),
1248                  cancel-diag-channel-operation(24),
1249                  log-retrieval-refused(25),
1250                  client-report-retrieval-refused(26),
1251                  test-request-refused-by-client(27),
1252                  invalid-network-address(28),
1253                  known-problem-with-network(29),
1254                  scheduled-maint-period(30),
1255                  wlan-security-incorrect(31),
1256                  waln-encryption-incorrect(32),
1257                  wlan-auth-incorrect(33)
1258                 }
1259   MAX-ACCESS 	 read-create
1260   STATUS     	 current
1261   DESCRIPTION
1262              "This attribute represents the type of message
1263              to be displayed."
1264
1265::= { cldccDiagMsgDisplayReqEntry 1 }
1266
1267cldccDiagMsgDisplayReqRowStatus   OBJECT-TYPE
1268
1269	SYNTAX     RowStatus
1270	MAX-ACCESS read-create
1271	STATUS     current
1272	DESCRIPTION
1273               "This field is used to add/remove entries from this table.
1274               To add a row in this table, createAndGo row status will
1275               be used.To remove a row, this field will be set to
1276               destroy."
1277
1278::= { cldccDiagMsgDisplayReqEntry 2 }
1279
1280cldccDiagProfileRedirectReqTable    OBJECT-TYPE
1281
1282    SYNTAX       SEQUENCE OF CldccDiagProfileRedirectReqEntry
1283    MAX-ACCESS 	 not-accessible
1284    STATUS     	 current
1285    DESCRIPTION
1286                "This table contains profile redirect request values for
1287                 various clients."
1288
1289::= { ciscoClientCcxDiagRequest  7}
1290
1291cldccDiagProfileRedirectReqEntry OBJECT-TYPE
1292
1293    SYNTAX       CldccDiagProfileRedirectReqEntry
1294    MAX-ACCESS   not-accessible
1295    STATUS     	 current
1296    DESCRIPTION
1297                "There is an entry in the table for each entry
1298	       	identified by the client mac address."
1299   INDEX
1300   {
1301       cldcClientMacAddress
1302   }
1303
1304::= { cldccDiagProfileRedirectReqTable 1}
1305
1306CldccDiagProfileRedirectReqEntry::=
1307
1308   SEQUENCE
1309    {
1310     cldccDiagProfileRedirectReqProfileId      Unsigned32,
1311     cldccDiagProfileRedirectReqRowStatus RowStatus
1312    }
1313
1314cldccDiagProfileRedirectReqProfileId OBJECT-TYPE
1315
1316   SYNTAX        Unsigned32
1317   MAX-ACCESS 	 read-create
1318   STATUS     	 current
1319   DESCRIPTION
1320              "This attribute represents the profile Id
1321              to which the client should be redirected."
1322
1323::= { cldccDiagProfileRedirectReqEntry 1 }
1324
1325cldccDiagProfileRedirectReqRowStatus   OBJECT-TYPE
1326
1327    SYNTAX     RowStatus
1328    MAX-ACCESS read-create
1329    STATUS     current
1330    DESCRIPTION
1331               "This field is used to add/remove entries from this table.
1332               To add a row in this table, createAndGo row status will
1333               be used.To remove a row, this field will be set to
1334               destroy."
1335
1336::= { cldccDiagProfileRedirectReqEntry 2 }
1337
1338
1339cldccDiagMsgDisplayRespTable    OBJECT-TYPE
1340
1341     SYNTAX      SEQUENCE OF CldccDiagMsgDisplayRespEntry
1342     MAX-ACCESS  not-accessible
1343     STATUS      current
1344     DESCRIPTION
1345                "This table contains message display request values
1346                for various clients."
1347
1348::= { ciscoClientCcxDiagResponse 6}
1349
1350cldccDiagMsgDisplayRespEntry OBJECT-TYPE
1351
1352  SYNTAX      CldccDiagMsgDisplayRespEntry
1353  MAX-ACCESS  not-accessible
1354  STATUS      current
1355  DESCRIPTION
1356             "There is an entry in the table for each entry
1357	     identified by the client mac address."
1358  INDEX
1359  {
1360   cldcClientMacAddress
1361  }
1362
1363::= { cldccDiagMsgDisplayRespTable 1}
1364
1365CldccDiagMsgDisplayRespEntry::=
1366
1367      SEQUENCE
1368      {
1369       cldccDiagMsgDisplayRespString OCTET STRING
1370      }
1371
1372cldccDiagMsgDisplayRespString    OBJECT-TYPE
1373
1374   SYNTAX       OCTET STRING (SIZE(1..256))
1375   MAX-ACCESS 	read-only
1376   STATUS     	current
1377   DESCRIPTION
1378              "This is string which was sent to the client for display."
1379
1380::= { cldccDiagMsgDisplayRespEntry 1 }
1381
1382
1383cldccDiagTestLoggedFrameTable OBJECT-TYPE
1384
1385   SYNTAX     SEQUENCE OF CldccDiagTestLoggedFrameEntry
1386   MAX-ACCESS not-accessible
1387   STATUS     current
1388   DESCRIPTION
1389              "This table contains logged frame data."
1390
1391::= { ciscoClientCcxDiagResponse 8 }
1392
1393cldccDiagTestLoggedFrameEntry OBJECT-TYPE
1394
1395    SYNTAX     CldccDiagTestLoggedFrameEntry
1396    MAX-ACCESS not-accessible
1397    STATUS     current
1398    DESCRIPTION
1399               "There is an entry in the table where each entry
1400               is identified by the client mac address."
1401    INDEX
1402    {
1403       cldcClientMacAddress,
1404       cldccDiagTestLoggedFrameIndex
1405    }
1406
1407::= { cldccDiagTestLoggedFrameTable 1}
1408
1409
1410CldccDiagTestLoggedFrameEntry::=
1411
1412    SEQUENCE
1413    {
1414    cldccDiagTestLoggedFrameIndex Unsigned32,
1415    cldccDiagTestLoggedFrameDirection INTEGER,
1416    cldccDiagTestLoggedFrameTimeStamp TimeStamp,
1417    cldccDiagTestLoggedFrameData OCTET STRING
1418    }
1419
1420cldccDiagTestLoggedFrameIndex OBJECT-TYPE
1421
1422    SYNTAX      Unsigned32
1423    MAX-ACCESS 	read-only
1424    STATUS     	current
1425    DESCRIPTION
1426             "The value of this field shall be the ordinal
1427	     value of the logged frame."
1428
1429::= { cldccDiagTestLoggedFrameEntry 1 }
1430
1431
1432cldccDiagTestLoggedFrameDirection OBJECT-TYPE
1433
1434    SYNTAX     INTEGER
1435               {
1436                 up(0),
1437                 down(1)
1438               }
1439    MAX-ACCESS read-only
1440    STATUS     current
1441    DESCRIPTION
1442           "The value of this field shall be zero,
1443	   when the logged frame in the Frame Content field
1444	   is sent from (transmitted by) the client.
1445	   It shall be one, otherwise."
1446
1447::= { cldccDiagTestLoggedFrameEntry 2}
1448
1449
1450cldccDiagTestLoggedFrameTimeStamp OBJECT-TYPE
1451
1452    SYNTAX      TimeStamp
1453    MAX-ACCESS 	read-only
1454    STATUS     	current
1455    DESCRIPTION
1456             "The value of this field shall be the
1457	     timestamp value of the logged frame."
1458
1459::= { cldccDiagTestLoggedFrameEntry 3 }
1460
1461
1462cldccDiagTestLoggedFrameData OBJECT-TYPE
1463
1464    SYNTAX      OCTET STRING(SIZE(1..4096))
1465    MAX-ACCESS 	read-only
1466    STATUS     	current
1467    DESCRIPTION
1468             "The value of this field shall be the actual
1469             frame that was transmitted or received."
1470
1471::= { cldccDiagTestLoggedFrameEntry 4}
1472
1473cldccDiagTestStatusTable OBJECT-TYPE
1474
1475    SYNTAX      SEQUENCE OF CldccDiagTestStatusEntry
1476    MAX-ACCESS  not-accessible
1477    STATUS      current
1478    DESCRIPTION
1479               "This table contains the status params for
1480               all the tests performed on the client."
1481
1482::= { ciscoClientCcxDiagStatus 1}
1483
1484cldccDiagTestStatusEntry OBJECT-TYPE
1485
1486    SYNTAX       CldccDiagTestStatusEntry
1487    MAX-ACCESS   not-accessible
1488    STATUS       current
1489    DESCRIPTION
1490               "There is an entry in the table identified by the
1491               client mac address."
1492    INDEX
1493    {
1494      cldcClientMacAddress
1495    }
1496
1497::= {cldccDiagTestStatusTable 1}
1498
1499
1500CldccDiagTestStatusEntry::=
1501
1502    SEQUENCE
1503    {
1504    cldccDiagTestLastTestStatus CiscoLwappCcxDiagTestStatus,
1505    cldccDiagTestLastResponseStatus CiscoLwappCcxDiagResponseStatus
1506    }
1507
1508cldccDiagTestLastTestStatus OBJECT-TYPE
1509
1510    SYNTAX      CiscoLwappCcxDiagTestStatus
1511    MAX-ACCESS  read-only
1512    STATUS      current
1513    DESCRIPTION
1514                "This field is used to represent the status of the
1515                last test performed."
1516
1517::= { cldccDiagTestStatusEntry 1 }
1518
1519cldccDiagTestLastResponseStatus OBJECT-TYPE
1520
1521    SYNTAX      CiscoLwappCcxDiagResponseStatus
1522    MAX-ACCESS  read-only
1523    STATUS      current
1524    DESCRIPTION
1525                "This field is used to represent the response of the
1526                last test performed."
1527
1528::= { cldccDiagTestStatusEntry 2 }
1529
1530
1531--********************************************************************
1532--*    Notification objects
1533--********************************************************************
1534
1535cldccDiagClientMacAddress OBJECT-TYPE
1536        SYNTAX     MacAddress
1537        MAX-ACCESS accessible-for-notify
1538        STATUS     current
1539        DESCRIPTION
1540                "This object indicates the macaddress of the client
1541		associated to the diagnostic WLAN. "
1542        ::= { ciscoLwappDot11CcxClientDiagMIBNotifObjs 1 }
1543
1544cldccDiagAssocReasonCode OBJECT-TYPE
1545	SYNTAX	   CLDot11ClientDiagAssocReason
1546	MAX-ACCESS accessible-for-notify
1547	STATUS     current
1548	DESCRIPTION
1549		"This object indicates the reason code for which
1550		the client has associated the diagnostic WLAN."
1551	::= { ciscoLwappDot11CcxClientDiagMIBNotifObjs 2 }
1552
1553--********************************************************************
1554--*    Notifications
1555--********************************************************************
1556
1557cldccDiagClientAssociatedToDiagWlan NOTIFICATION-TYPE
1558        OBJECTS {
1559                cldccDiagClientMacAddress,
1560		cldccDiagAssocReasonCode
1561        }
1562        STATUS  current
1563        DESCRIPTION
1564             "This notification is generated when a client associates
1565             to a diagnostic WLAN. "
1566        ::= { ciscoLwappDot11CcxClientDiagMIBNotifs 1 }
1567
1568END
1569