1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
|
-- ============================================================================
-- AT-SETUP.MIB, Allied Telesis enterprise MIB:
-- Device Setup for the AlliedWare Plus(tm) operating system
--
-- Copyright (c) 2010 by Allied Telesis, Inc.
-- All rights reserved.
--
-- ============================================================================
AT-SETUP-MIB DEFINITIONS ::= BEGIN
IMPORTS
modules
FROM AT-SMI-MIB
Integer32, OBJECT-TYPE, MODULE-IDENTITY
FROM SNMPv2-SMI
DisplayString, TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC;
setup MODULE-IDENTITY
LAST-UPDATED "201404300000Z"
ORGANIZATION
"Allied Telesis, Inc."
CONTACT-INFO
"http://www.alliedtelesis.com"
DESCRIPTION
"The AT Setup MIB for managing the software installation and
configuration files."
REVISION "201404300000Z"
DESCRIPTION
"Updated decriptions to refer to chassisMappingTable"
REVISION "201310140000Z"
DESCRIPTION
"Added new requirement to the objects nextBootLastSetResult and backupLastSetResult,
as to check for the existence of a valid release license on the device. If a valid license
is not found then these objects will give an appropriate error message."
REVISION "201209210000Z"
DESCRIPTION
"Added chassis switch (e.g. SBx8100) descriptions to stack-related MIB objects"
REVISION "201011200000Z"
DESCRIPTION
"Addition of new objects to support system file operations on
stacked devices."
REVISION "201010080000Z"
DESCRIPTION
"Minor changes to help messages."
REVISION "201009100000Z"
DESCRIPTION
"Generic syntax tidy up."
REVISION "201009080000Z"
DESCRIPTION
"Added backupConfig object. The nextBootPath and bootcnfgPath objects will
now accept a file stored in card:. The nextBootPath object will only accept
a file on card if this is supported by the bootloader."
REVISION "201006150015Z"
DESCRIPTION
"MIB revision history dates in descriptions updated."
REVISION "201004090000Z"
DESCRIPTION
"A set to the runCnfgSaveAs object will now be immediately responded before
the actual saving operation starts. This prevents the request from being
timed out while the saving is still progressing. A new object
runCnfgSaveAsStatus is defined which can be polled to obtain the status of
the current/previous saving operation."
REVISION "200810020000Z"
DESCRIPTION
"Added support for obtaining GUI applet version information."
REVISION "200809300000Z"
DESCRIPTION
"Add branch serviceConfig."
REVISION "200809240000Z"
DESCRIPTION
"Moved file copy branch to the new AT-FILEv2 MIB.
Allowed clearing of currentFirmware, nextBootFirmware and nextBootConfig
by setting the path objects with an empty string."
REVISION "200805210000Z"
DESCRIPTION
"Initial revision."
::= { modules 500 }
-- Textual Conventions
SystemFileOperationType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the current status of an attempt to modify a system
file setting."
SYNTAX INTEGER
{
idle(1),
success(2),
failure(3),
saving(4),
syncing(5)
}
--
-- Node definitions
--
restartDevice OBJECT-TYPE
SYNTAX Integer32 (0..1)
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"This object forces a standalone unit or stack of devices to
restart immediately when set with a value of 1. For a chassis
switch, this object causes the whole chassis to restart
immediately. Reading the object will always return zero.
NOTE: This object has been replaced by the
restartStkMemberDevice object."
::= { setup 1 }
restartStkMemberDevice OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object causes a specified device to restart immediately.
The restart is initiated by setting its value to the device's
stack member ID. For a chassis switch, it corresponds to the
card ID. For VCStack Plus, 1-12 refers to the cards on VCS
stack member 1 and 13-24 refers to the cards on VCS stack
member 2. Refer to chassisMappingTable for more details.
This object causes the specified card to restart immediately.
Setting its value to zero will cause all devices in the stack
(or a standalone device) to restart. Reading the object will
always return zero."
::= { setup 4 }
-- ---------------------------------------------------------- --
-- The firmware objects
-- ---------------------------------------------------------- --
firmware OBJECT IDENTIFIER ::= { setup 2 }
currentFirmware OBJECT IDENTIFIER ::= { firmware 1 }
currSoftVersion OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The major.minor.interim version of the firmware that the device is
currently running. Will return 0 if the version cannot be determined."
::= { currentFirmware 1 }
currSoftName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the firmware that the device is currently running."
::= { currentFirmware 2 }
currSoftSaveAs OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"Set with a filename to save the currently running software to
the root of flash. Only one save operation can be executed at a
time across all SNMP users, and the filename must not contain
whitespace characters.
Immediately upon executing the set action, the actual firmware
save operation will be started and continue on the device until
it has completed or a failure occurs.
Subsequent reads of the object will return one of several
results:
saving x A saving operation is currently in
progress. Another save cannot be started
while the object is returning this value.
x success The last save operation was successfully
completed.
x failure: [error] The last save operation failed, due to the
descriptive message attached. The most
common failure is lack of disk space.
idle There is no save operation in progress and
a new one may be started.
Upon reading a success or failure message, the message will be
cleared and the next read will result in an 'idle' message. A
new save operation can now be executed.
NOTE: This object has been replaced by objects currSoftSaveToFile,
currSoftSaveStatus and currSoftLastSaveResult."
::= { currentFirmware 3 }
currSoftSaveToFile OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set with a URL (e.g. 'flash:/filename.rel' or
'card:/filename.rel') to save the currently running software to
the root of flash or SD card. Only one save operation can be
executed at a time across all SNMP users, and an operation may
not be started unless the current value of currSoftSaveStatus
is 'idle'. The URL must not contain whitespace characters.
Immediately upon executing the set action, the actual firmware
save operation will be started and continue on the device until
it has completed or a failure occurs. The current status of the
operation can be determined by reading currSoftSaveStatus, and
the result of the last completed operation is indicated by
currSoftLastSaveResult.
When read, this object will return the URL of the last
firmware save operation that was attempted."
::= { currentFirmware 4 }
currSoftSaveStatus OBJECT-TYPE
SYNTAX SystemFileOperationType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Returns the status of any current operation to store the
running software to a release file. The following values may
be returned:
1 (idle) There is no release file save operation
in progress.
2 (success) The last release file save operation
completed successfully.
3 (failure) The last release file save operation
failed.
4 (saving) A release file save operation is
currently in progress.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new
operation may be initiated if desired. A detailed description
of the last completed operation may be determined by reading
currSoftLastSaveResult."
::= { currentFirmware 5 }
currSoftLastSaveResult OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Gives an indication of the result of the last completed SNMP
operation to save the running firmware to a release file."
::= { currentFirmware 6 }
nextBootFirmware OBJECT IDENTIFIER ::= { firmware 2 }
nextBootVersion OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The major.minor.interim version of the firmware that the
device is currently set to boot from. Will return 0 if the
version cannot be determined."
::= { nextBootFirmware 1 }
nextBootPath OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The full path of the release to be used the next time the
device restarts. There is no guarantee that the file
referenced exists (i.e. it may have been deleted since the boot
path was last set).
Only one set operation can be executed at a time across all
SNMP users, and an operation may not be started unless the
current value of nextBootSetStatus is 'idle'. The path must not
contain whitespace characters.
Immediately upon setting this object, the system will attempt
to set the new boot path, and the process will continue on the
device until it has completed or a failure occurs. The current
status of the operation can be determined by reading
nextBootSetStatus, and the result of the last completed
operation is indicated by nextBootLastSetResult.
This object can be set with an empty string in order to clear
the current boot firmware. Otherwise, the path should be of the
form 'flash:/filename.rel' or 'card:/filename.rel'.
There are several requirements that must be met in order to set
a boot release file successfully:
- The file must exist.
- The file must be in the root of flash (on the active master
in a stacked environment) or card.
- The file must not be the same as the currently set backup
release.
- The file must have a .rel suffix.
- The file must be a valid release file.
- In a stacked environment, there must be enough disk space
available to store the release file on each stack member.
- The device must have a current release license for the
specified release."
::= { nextBootFirmware 2 }
nextBootSetStatus OBJECT-TYPE
SYNTAX SystemFileOperationType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Returns the status of any current operation to set the next
boot release file. The following values may be returned:
1 (idle) There is no boot release setting
operation in progress.
2 (success) The last boot release setting
operation completed successfully.
3 (failure) The last boot release setting
operation failed.
5 (syncing) A boot release setting operation is
currently in progress and the file is
being syncronised across the stack or
system.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new
operation may be initiated if desired. A detailed description
of the last completed operation may be determined by reading
nextBootLastSetResult."
::= { nextBootFirmware 3 }
nextBootLastSetResult OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Gives an indication of the result of the last completed SNMP
operation to set the boot release filename."
::= { nextBootFirmware 4 }
backupFirmware OBJECT IDENTIFIER ::= { firmware 3 }
backupVersion OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The major.minor.interim version of the firmware that the
device will boot from as a backup. This will return 0 if the
version cannot be determined."
::= { backupFirmware 1 }
backupPath OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The full path of the release file to be used as a backup in
the event of the main release file failing to boot. There is no
guarantee that the file referenced exists (i.e. it may have
been deleted since the backup path was last set).
Only one set operation can be executed at a time across all
SNMP users, and an operation may not be started unless the
current value of backupSetStatus is 'idle'. The path must not
contain whitespace characters.
Immediately upon setting this object, the system will attempt
to set the new backup path, and the process will continue on
the device until it has completed or a failure occurs. The
current status of the operation can be determined by reading
backupSetStatus, and the result of the last completed operation
is indicated by backupLastSetResult.
This object can be set with an empty string in order to clear
the current backup firmware. Otherwise, the path should be of
the form 'flash:/filename.rel' or 'card:/filename.rel'.
There are several requirements that must be met in order to set
a backup release file successfully:
- The file must exist.
- The file must be in the root of flash (on the active master
in a stacked environment) or card.
- The file must not be the same as the currently set backup
release.
- The file must have a .rel suffix.
- The file must be a valid release file.
- In a stacked environment, there must be enough disk space
available to store the release file on each stack member.
- The device must have a current release license for the
specified release."
::= { backupFirmware 2 }
backupSetStatus OBJECT-TYPE
SYNTAX SystemFileOperationType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Returns the status of any current operation to set the backup
boot release file. The following values may be returned:
1 (idle) There is no backup boot release setting
operation in progress.
2 (success) The last backup boot release setting
operation completed successfully.
3 (failure) The last backup boot release setting
operation failed.
5 (syncing) A backup boot release setting operation
is currently in progress and the file
is being syncronised across the stack
or system.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new
operation may be initiated if desired. A detailed description
of the last completed operation may be determined by reading
backupLastSetResult."
::= { backupFirmware 3 }
backupLastSetResult OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Gives an indication of the result of the last completed SNMP
operation to set the backup boot release filename."
::= { backupFirmware 4 }
-- ---------------------------------------------------------- --
-- The configuration file objects
-- ---------------------------------------------------------- --
deviceConfiguration OBJECT IDENTIFIER ::= { setup 3 }
runningConfig OBJECT IDENTIFIER ::= { deviceConfiguration 1 }
runCnfgSaveAs OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Set with a URL to save the running configuration to the flash
or card filesystem using that filename (e.g.
'flash:/myconfig.cfg' or 'card:/myconfig.cfg').
Only one set operation can be executed at a time across all
SNMP users, and an operation may not be started unless the
current value of runCnfgSaveAsStatus is 'idle'. The URL must
not contain whitespace characters.
Immediately upon setting this object, the system will attempt
to save the running configuration, and the process will
continue on the device until it has completed or a failure
occurs. The current status of the operation can be determined
by reading runCnfgSaveAsStatus, and the result of the last
completed operation is indicated by runCnfgLastSaveResult.
When read, this object will return the URL of the last
configuration save operation that was attempted."
::= { runningConfig 1 }
runCnfgSaveAsStatus OBJECT-TYPE
SYNTAX SystemFileOperationType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Returns the status of any current operation to save the
running configuration. The following values may be returned:
1 (idle) There is no config file save operation
in progress.
2 (success) The last config file save operation
completed successfully.
3 (failure) The last config file save operation
failed.
4 (saving) A config file save operation is
currently in progress.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new
operation may be initiated if desired. A detailed description
of the last completed operation may be determined by reading
runCnfgLastSaveResult."
::= { runningConfig 2 }
runCnfgLastSaveResult OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Gives an indication of the result of the last completed SNMP
operation to save the running configuration."
::= { runningConfig 3 }
nextBootConfig OBJECT IDENTIFIER ::= { deviceConfiguration 2 }
bootCnfgPath OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The full path of the configuration file to be used the next
time the device restarts. There is no guarantee that the file
referenced exists (i.e. it may have been deleted since the
configuration path was last set).
Only one set operation can be executed at a time across all
SNMP users, and an operation may not be started unless the
current value of bootCnfgSetStatus is 'idle'. The path must not
contain whitespace characters.
Immediately upon setting this object, the system will attempt
to set the new configuration path, and the process will
continue on the device until it has completed or a failure
occurs. The current status of the operation can be determined
by reading bootCnfgSetStatus, and the result of the last
completed operation is indicated by bootCnfgLastSetResult.
This object can be set with an empty string in order to clear
the current boot configuration. Otherwise, the path should be
of the form 'flash:/filename.cfg' or 'card:/filename.cfg'.
There are several requirements that must be met in order to set
a boot configuration file successfully:
- The file must exist.
- The file must be in the flash (on the active master in a
stacked environment) or card filesystems.
- The file must have a .cfg suffix.
- In a stacked environment, there must be enough disk space
available to store the configuration file on each stack
member."
::= { nextBootConfig 1 }
bootCnfgExists OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object will return TRUE if the currently defined boot
configuration file exists, or FALSE otherwise."
::= { nextBootConfig 2 }
bootCnfgSetStatus OBJECT-TYPE
SYNTAX SystemFileOperationType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Returns the status of any current operation to set the next
boot configuration file. The following values may be returned:
1 (idle) There is no boot configuration setting
operation in progress.
2 (success) The last boot configuration setting
operation completed successfully.
3 (failure) The last boot configuration setting
operation failed.
5 (syncing) A boot configuration setting operation
is currently in progress and the file
is being syncronised across the stack
or system.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new
operation may be initiated if desired. A detailed description
of the last completed operation may be determined by reading
bootCnfgLastSetResult."
::= { nextBootConfig 3 }
bootCnfgLastSetResult OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Gives an indication of the result of the last completed SNMP
operation to set the boot configuration filename."
::= { nextBootConfig 4 }
defaultConfig OBJECT IDENTIFIER ::= { deviceConfiguration 3 }
dfltCnfgPath OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The full path of the configuration file to be used upon device
restart, if no user-defined boot or backup configuration files
can be found. There is no guarantee that the file referenced
exists (i.e. it may have been deleted).
This object is not settable - the default configuration file is
always 'flash:/default.cfg'"
::= { defaultConfig 1 }
dfltCnfgExists OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object will return TRUE if the currently defined default
configuration file exists, or FALSE otherwise."
::= { defaultConfig 2 }
backupConfig OBJECT IDENTIFIER ::= { deviceConfiguration 4 }
backupCnfgPath OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The full path of the backup configuration file to be used the
next time the device restarts, if the boot configuration file
cannot be accessed. There is no guarantee that the file
referenced exists (i.e. it may have been deleted since the
backup configuration path was last set).
Only one set operation can be executed at a time across all
SNMP users, and an operation may not be started unless the
current value of backupCnfgSetStatus is 'idle'. The path must
not contain whitespace characters.
Immediately upon setting this object, the system will attempt
to set the new backup configuration path, and the process will
continue on the device until it has completed or a failure
occurs. The current status of the operation can be determined
by reading backupCnfgSetStatus, and the result of the last
completed operation is indicated by backupCnfgLastSetResult.
This object can be set with an empty string in order to clear
the current backup configuration. Otherwise, the path should be
of the form 'flash:/filename.cfg' or 'card:/filename.cfg'.
There are several requirements that must be met in order to set
a backup configuration file successfully:
- The file must exist.
- The file must be in the flash (on the active master in a
stacked environment) or card filesystems.
- The file must have a .cfg suffix.
- In a stacked environment, there must be enough disk space
available to store the configuration file on each stack
member."
::= { backupConfig 1 }
backupCnfgExists OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object will return TRUE if the currently defined backup
configuration file exists, or FALSE otherwise."
::= { backupConfig 2 }
backupCnfgSetStatus OBJECT-TYPE
SYNTAX SystemFileOperationType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Returns the status of any current operation to set the next
backup boot configuration file. The following values may be
returned:
1 (idle) There is no backup boot configuration
setting operation in progress.
2 (success) The last backup boot configuration
setting operation completed
successfully.
3 (failure) The last backup boot configuration
setting operation failed.
5 (syncing) A backup boot configuration setting
operation is currently in progress and
the file is being syncronised across
the stack or system.
When a read of this object returns a value of 'success' or
'failure', it will immediately be reset to 'idle' and a new
operation may be initiated if desired. A detailed description
of the last completed operation may be determined by reading
backupCnfgLastSetResult."
::= { backupConfig 3 }
backupCnfgLastSetResult OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Gives an indication of the result of the last completed SNMP
operation to set the backup boot configuration filename."
::= { backupConfig 4 }
serviceConfig OBJECT IDENTIFIER ::= { setup 5 }
srvcTelnetEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object represents the state of the telnet server of a device.
A management application can find out the telnet server is either
enabled or disabled by reading this object.
To either enable or disable the telnet server, a management
application can SET this object with value 'enable(1)' or
'disable(2)' respectively."
::= { serviceConfig 1 }
srvcSshEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object represents the state of the ssh server of a device.
A management application can find out the ssh server is either
enabled or disabled by reading this object.
To either enable or disable the ssh server, a management
application can SET this object with value 'enable(1)' or
'disable(2)' respectively."
::= { serviceConfig 2 }
-- ---------------------------------------------------------- --
-- GUI applet configuration file objects
-- ---------------------------------------------------------- --
guiConfig OBJECT IDENTIFIER ::= { setup 6 }
guiAppletConfig OBJECT IDENTIFIER ::= { guiConfig 1 }
guiAppletSysSwVer OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the system software release that the
currently selected GUI applet was designed to run on.
The system will automatically search for GUI applet files
residing in the root directory of flash, and will select the
latest available one that is applicable to the currently
running system software. This will be the applet that is
uploaded to a user's web browser when they initiate use of the
GUI."
::= { guiAppletConfig 1 }
guiAppletSwVer OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the software version of the currently
selected GUI applet.
The system will automatically search for GUI applet files
residing in the root directory of flash, and will select the
latest available one that is applicable to the currently
running system software. This will be the applet that is
uploaded to a user's web browser when they initiate use of the
GUI."
::= { guiAppletConfig 2 }
END
--
-- at-setup.mib
--
|