1
DISMAN-SCHEDULE-MIB DEFINITIONS ::= BEGIN
4
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
5
Integer32, Unsigned32, Counter32, mib-2
9
DateAndTime, RowStatus, StorageType, VariablePointer
13
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
17
FROM SNMP-FRAMEWORK-MIB;
19
schedMIB MODULE-IDENTITY
20
LAST-UPDATED "9811171800Z"
21
ORGANIZATION "IETF Distributed Management Working Group"
25
4401 Great America Parkway
26
Santa Clara, CA 95052-8185
29
E-mail: dlevi@nortelnetworks.com
37
E-mail: schoenw@ibr.cs.tu-bs.de"
39
"This MIB module defines a MIB which provides mechanisms
40
to schedule SNMP set operations periodically or at
41
specific points in time."
45
-- The various groups defined within this MIB definition:
48
schedObjects OBJECT IDENTIFIER ::= { schedMIB 1 }
49
schedNotifications OBJECT IDENTIFIER ::= { schedMIB 2 }
50
schedConformance OBJECT IDENTIFIER ::= { schedMIB 3 }
53
-- Textual Conventions:
56
SnmpPduErrorStatus ::= TEXTUAL-CONVENTION
59
"This TC enumerates the SNMPv1 and SNMPv2 PDU error status
60
codes as defined in RFC 1157 and RFC 1905. It also adds a
61
pseudo error status code `noResponse' which indicates a
77
inconsistentValue(12),
78
resourceUnavailable(13),
81
authorizationError(16),
87
-- Some scalars which provide information about the local time
91
schedLocalTime OBJECT-TYPE
92
SYNTAX DateAndTime (SIZE (11))
96
"The local time used by the scheduler. Schedules which
97
refer to calendar time will use the local time indicated
98
by this object. An implementation MUST return all 11 bytes
99
of the DateAndTime textual-convention so that a manager
100
may retrieve the offset from GMT time."
101
::= { schedObjects 1 }
104
-- The schedule table which controls the scheduler.
107
schedTable OBJECT-TYPE
108
SYNTAX SEQUENCE OF SchedEntry
109
MAX-ACCESS not-accessible
112
"This table defines scheduled actions triggered by
113
SNMP set operations."
114
::= { schedObjects 2 }
116
schedEntry OBJECT-TYPE
118
MAX-ACCESS not-accessible
121
"An entry describing a particular scheduled action."
122
INDEX { schedOwner, schedName }
125
SchedEntry ::= SEQUENCE {
126
schedOwner SnmpAdminString,
127
schedName SnmpAdminString,
128
schedDescr SnmpAdminString,
129
schedInterval Unsigned32,
135
schedContextName SnmpAdminString,
136
schedVariable VariablePointer,
137
schedValue Integer32,
139
schedAdminStatus INTEGER,
140
schedOperStatus INTEGER,
141
schedFailures Counter32,
142
schedLastFailure SnmpPduErrorStatus,
143
schedLastFailed DateAndTime,
144
schedStorageType StorageType,
145
schedRowStatus RowStatus
148
schedOwner OBJECT-TYPE
149
SYNTAX SnmpAdminString (SIZE(0..32))
150
MAX-ACCESS not-accessible
153
"The owner of this scheduling entry. The exact semantics of
154
this string are subject to the security policy defined by
156
the security administrator."
159
schedName OBJECT-TYPE
160
SYNTAX SnmpAdminString (SIZE(1..32))
161
MAX-ACCESS not-accessible
164
"The locally-unique, administratively assigned name for this
165
scheduling entry. This object allows a schedOwner to have
166
multiple entries in the schedTable."
169
schedDescr OBJECT-TYPE
170
SYNTAX SnmpAdminString
171
MAX-ACCESS read-create
174
"The human readable description of the purpose of this
179
schedInterval OBJECT-TYPE
182
MAX-ACCESS read-create
185
"The number of seconds between two action invocations of
186
a periodic scheduler. Implementations must guarantee
187
that action invocations will not occur before at least
188
schedInterval seconds have passed.
190
The scheduler must ignore all periodic schedules that
191
have a schedInterval value of 0. A periodic schedule
192
with a scheduling interval of 0 seconds will therefore
193
never invoke an action.
195
Implementations may be forced to delay invocations in the
196
face of local constraints. A scheduled management function
197
should therefore not rely on the accuracy provided by the
198
scheduler implementation."
202
schedWeekDay OBJECT-TYPE
213
MAX-ACCESS read-create
216
"The set of weekdays on which the scheduled action should
217
take place. Setting multiple bits will include several
218
weekdays in the set of possible weekdays for this schedule.
219
Setting all bits will cause the scheduler to ignore the
224
schedMonth OBJECT-TYPE
239
MAX-ACCESS read-create
242
"The set of months during which the scheduled action should
243
take place. Setting multiple bits will include several
244
months in the set of possible months for this schedule.
245
Setting all bits will cause the scheduler to ignore the
252
d1(0), d2(1), d3(2), d4(3), d5(4),
253
d6(5), d7(6), d8(7), d9(8), d10(9),
254
d11(10), d12(11), d13(12), d14(13), d15(14),
255
d16(15), d17(16), d18(17), d19(18), d20(19),
256
d21(20), d22(21), d23(22), d24(23), d25(24),
257
d26(25), d27(26), d28(27), d29(28), d30(29),
259
r1(31), r2(32), r3(33), r4(34), r5(35),
260
r6(36), r7(37), r8(38), r9(39), r10(40),
261
r11(41), r12(42), r13(43), r14(44), r15(45),
262
r16(46), r17(47), r18(48), r19(49), r20(50),
263
r21(51), r22(52), r23(53), r24(54), r25(55),
264
r26(56), r27(57), r28(58), r29(59), r30(60),
267
MAX-ACCESS read-create
270
"The set of days in a month on which a scheduled action
271
should take place. There are two sets of bits one can
272
use to define the day within a month:
274
Enumerations starting with the letter 'd' indicate a
275
day in a month relative to the first day of a month.
276
The first day of the month can therefore be specified
277
by setting the bit d1(0) and d31(30) means the last
278
day of a month with 31 days.
280
Enumerations starting with the letter 'r' indicate a
281
day in a month in reverse order, relative to the last
282
day of a month. The last day in the month can therefore
283
be specified by setting the bit r1(31) and r31(61) means
284
the first day of a month with 31 days.
286
Setting multiple bits will include several days in the set
287
of possible days for this schedule. Setting all bits will
288
cause the scheduler to ignore the day within a month.
289
Setting all bits starting with the letter 'd' or the
290
letter 'r' will also cause the scheduler to ignore the
295
schedHour OBJECT-TYPE
297
h0(0), h1(1), h2(2), h3(3), h4(4),
298
h5(5), h6(6), h7(7), h8(8), h9(9),
299
h10(10), h11(11), h12(12), h13(13), h14(14),
300
h15(15), h16(16), h17(17), h18(18), h19(19),
301
h20(20), h21(21), h22(22), h23(23)
303
MAX-ACCESS read-create
306
"The set of hours within a day during which the scheduled
307
action should take place."
311
schedMinute OBJECT-TYPE
313
m0(0), m1(1), m2(2), m3(3), m4(4),
314
m5(5), m6(6), m7(7), m8(8), m9(9),
315
m10(10), m11(11), m12(12), m13(13), m14(14),
316
m15(15), m16(16), m17(17), m18(18), m19(19),
317
m20(20), m21(21), m22(22), m23(23), m24(24),
318
m25(25), m26(26), m27(27), m28(28), m29(29),
319
m30(30), m31(31), m32(32), m33(33), m34(34),
320
m35(35), m36(36), m37(37), m38(38), m39(39),
321
m40(40), m41(41), m42(42), m43(43), m44(44),
322
m45(45), m46(46), m47(47), m48(48), m49(49),
323
m50(50), m51(51), m52(52), m53(53), m54(54),
324
m55(55), m56(56), m57(57), m58(58), m59(59)
326
MAX-ACCESS read-create
329
"The set of minutes within an hour when the scheduled action
334
schedContextName OBJECT-TYPE
335
SYNTAX SnmpAdminString (SIZE(0..32))
336
MAX-ACCESS read-create
339
"The context which contains the local MIB variable pointed
340
to by schedVariable."
341
::= { schedEntry 10 }
343
schedVariable OBJECT-TYPE
344
SYNTAX VariablePointer
345
MAX-ACCESS read-create
348
"An object identifier pointing to a local MIB variable
350
which resolves to an ASN.1 primitive type of INTEGER."
351
::= { schedEntry 11 }
353
schedValue OBJECT-TYPE
355
MAX-ACCESS read-create
358
"The value which is written to the MIB object pointed to by
359
schedVariable when the scheduler invokes an action. The
360
implementation shall enforce the use of access control
361
rules when performing the set operation on schedVariable.
362
This is accomplished by calling the isAccessAllowed abstract
363
service interface as defined in RFC 2271."
364
::= { schedEntry 12 }
366
schedType OBJECT-TYPE
372
MAX-ACCESS read-create
375
"The type of this schedule. The value periodic(1) indicates
376
that this entry specifies a periodic schedule. A periodic
377
schedule is defined by the value of schedInterval. The
378
values of schedWeekDay, schedMonth, schedDay, schedHour
379
and schedMinute are ignored.
381
The value calendar(2) indicates that this entry describes a
382
calendar schedule. A calendar schedule is defined by the
383
values of schedWeekDay, schedMonth, schedDay, schedHour and
384
schedMinute. The value of schedInterval is ignored. A
385
calendar schedule will trigger on all local times that
386
satisfy the bits set in schedWeekDay, schedMonth, schedDay,
387
schedHour and schedMinute.
389
The value oneshot(3) indicates that this entry describes a
390
one-shot schedule. A one-shot schedule is similar to a
391
calendar schedule with the additional feature that it
392
disables itself by changing in the `finished'
393
schedOperStatus once the schedule triggers an action.
395
Changing a schedule's type is equivalent to deleting the
396
old-type schedule and creating a new-type one."
398
::= { schedEntry 13 }
400
schedAdminStatus OBJECT-TYPE
405
MAX-ACCESS read-create
408
"The desired state of the schedule."
410
::= { schedEntry 14 }
412
schedOperStatus OBJECT-TYPE
421
"The current operational state of this schedule. The state
422
enabled(1) indicates this entry is active and that the
423
scheduler will invoke actions at appropriate times. The
424
disabled(2) state indicates that this entry is currently
425
inactive and ignored by the scheduler. The finished(3)
426
state indicates that the schedule has ended. Schedules
427
in the finished(3) state are ignored by the scheduler.
428
A one-shot schedule enters the finished(3) state when it
430
::= { schedEntry 15 }
432
schedFailures OBJECT-TYPE
437
"This variable counts the number of failures while invoking
438
the scheduled action."
439
::= { schedEntry 16 }
441
schedLastFailure OBJECT-TYPE
442
SYNTAX SnmpPduErrorStatus
446
"The most recent error that occured during the invocation of
447
a scheduled action. The value noError(0) is returned
448
if no errors have occurred yet."
450
::= { schedEntry 17 }
452
schedLastFailed OBJECT-TYPE
457
"The date and time when the most recent failure occured. The
458
value '0000000000000000'H is returned if no failure occured
459
since the last re-initialization of the scheduler."
460
DEFVAL { '0000000000000000'H }
461
::= { schedEntry 18 }
463
schedStorageType OBJECT-TYPE
465
MAX-ACCESS read-create
468
"This object defines whether this scheduled action is kept
469
in volatile storage and lost upon reboot or if this row is
470
backed up by non-volatile or permanent storage.
471
Conceptual rows having the value `permanent' must allow
472
write access to the columnar objects schedDescr,
473
schedInterval, schedContextName, schedVariable, schedValue,
474
and schedAdminStatus. If an implementation supports the
475
schedCalendarGroup, write access must be also allowed to
476
the columnar objects schedWeekDay, schedMonth, schedDay,
477
schedHour, schedMinute."
479
::= { schedEntry 19 }
481
schedRowStatus OBJECT-TYPE
483
MAX-ACCESS read-create
486
"The status of this scheduled action. A control that allows
487
entries to be added and removed from this table.
489
The miminum number of objects that need to be set during
490
row creation before a row can be set to `active' are
491
schedContextName, schedVariable and schedValue."
492
::= { schedEntry 20 }
495
-- Notifications that are emitted to indicate failures. The
496
-- definition of schedTraps makes notification registrations
497
-- reversible (see STD 58, RFC 2578).
500
schedTraps OBJECT IDENTIFIER ::= { schedNotifications 0 }
502
schedActionFailure NOTIFICATION-TYPE
503
OBJECTS { schedLastFailure, schedLastFailed }
506
"This notification is generated whenever the invocation of a
507
scheduled action fails."
510
-- conformance information
512
schedCompliances OBJECT IDENTIFIER ::= { schedConformance 1 }
513
schedGroups OBJECT IDENTIFIER ::= { schedConformance 2 }
515
-- compliance statements
517
schedCompliance MODULE-COMPLIANCE
520
"The compliance statement for SNMP entities which implement
522
MODULE -- this module
524
schedGroup, schedNotificationsGroup
526
GROUP schedCalendarGroup
528
"The schedCalendarGroup is mandatory only for those
529
implementations that support calendar based schedules."
532
"The values calendar(2) or oneshot(3) are not valid for
533
implementations that do not implement the
534
schedCalendarGroup. Such an implementation must return
535
inconsistentValue error responses for attempts to set
536
schedAdminStatus to calendar(2) or oneshot(3)."
537
::= { schedCompliances 1 }
539
schedGroup OBJECT-GROUP
557
"A collection of objects providing scheduling capabilities."
558
::= { schedGroups 1 }
560
schedCalendarGroup OBJECT-GROUP
571
"A collection of objects providing calendar based schedules."
572
::= { schedGroups 2 }
574
schedNotificationsGroup NOTIFICATION-GROUP
580
"The notifications emitted by the scheduler."
581
::= { schedGroups 3 }