DISMAN-SCHEDULE-MIB: View SNMP OID List / Download MIB

This MIB module defines a MIB which provides mechanisms to schedule SNMP set operations periodically or at specific points in time.

The local time used by the scheduler. Schedules which refer to calendar time will use the local time indicated by this object. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time.

This table defines scheduled actions triggered by SNMP set operations.

An entry describing a particular scheduled action. Unless noted otherwise, writable objects of this row can be modified independent of the current value of schedRowStatus, schedAdminStatus and schedOperStatus. In particular, it is legal to modify schedInterval and the objects in the schedCalendarGroup when schedRowStatus is active and schedAdminStatus and schedOperStatus are both enabled.

The owner of this scheduling entry. The exact semantics of this string are subject to the security policy defined by the security administrator.

The locally-unique, administratively assigned name for this scheduling entry. This object allows a schedOwner to have multiple entries in the schedTable.

The human readable description of the purpose of this scheduling entry.

The number of seconds between two action invocations of a periodic scheduler. Implementations must guarantee that action invocations will not occur before at least schedInterval seconds have passed. The scheduler must ignore all periodic schedules that have a schedInterval value of 0. A periodic schedule with a scheduling interval of 0 seconds will therefore never invoke an action. Implementations may be forced to delay invocations in the face of local constraints. A scheduled management function should therefore not rely on the accuracy provided by the scheduler implementation. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.

The set of weekdays on which the scheduled action should take place. Setting multiple bits will include several weekdays in the set of possible weekdays for this schedule. Setting all bits will cause the scheduler to ignore the weekday. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed. Bits: 'monday': 1, 'tuesday': 2, 'friday': 5, 'wednesday': 3, 'thursday': 4, 'sunday': 0, 'saturday': 6.

The set of months during which the scheduled action should take place. Setting multiple bits will include several months in the set of possible months for this schedule. Setting all bits will cause the scheduler to ignore the month. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed. Bits: 'february': 1, 'october': 9, 'march': 2, 'august': 7, 'september': 8, 'may': 4, 'january': 0, 'june': 5, 'april': 3, 'december': 11, 'july': 6, 'november': 10.

The set of days in a month on which a scheduled action should take place. There are two sets of bits one can use to define the day within a month: Enumerations starting with the letter 'd' indicate a day in a month relative to the first day of a month. The first day of the month can therefore be specified by setting the bit d1(0) and d31(30) means the last day of a month with 31 days. Enumerations starting with the letter 'r' indicate a day in a month in reverse order, relative to the last day of a month. The last day in the month can therefore be specified by setting the bit r1(31) and r31(61) means the first day of a month with 31 days. Setting multiple bits will include several days in the set of possible days for this schedule. Setting all bits will cause the scheduler to ignore the day within a month. Setting all bits starting with the letter 'd' or the letter 'r' will also cause the scheduler to ignore the day within a month. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed. Bits: 'r29': 59, 'r17': 47, 'r8': 38, 'r28': 58, 'r9': 39, 'r27': 57, 'd8': 7, 'd9': 8, 'd6': 5, 'd7': 6, 'd4': 3, 'd5': 4, 'd2': 1, 'd3': 2, 'r21': 51, 'd1': 0, 'd14': 13, 'd15': 14, 'd16': 15, 'd17': 16, 'd10': 9, 'd11': 10, 'd12': 11, 'd13': 12, 'r23': 53, 'r11': 41, 'd18': 17, 'd19': 18, 'd30': 29, 'd31': 30, 'r22': 52, 'r20': 50, 'r16': 46, 'r4': 34, 'r14': 44, 'r15': 45, 'r12': 42, 'r13': 43, 'r10': 40, 'r5': 35, 'r31': 61, 'r18': 48, 'r19': 49, 'r30': 60, 'r26': 56, 'r25': 55, 'd29': 28, 'd28': 27, 'r6': 36, 'r7': 37, 'r1': 31, 'r2': 32, 'r3': 33, 'd21': 20, 'd20': 19, 'd23': 22, 'd22': 21, 'd25': 24, 'd24': 23, 'd27': 26, 'd26': 25, 'r24': 54.

The set of hours within a day during which the scheduled action should take place. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed. Bits: 'h8': 8, 'h9': 9, 'h2': 2, 'h3': 3, 'h0': 0, 'h1': 1, 'h6': 6, 'h7': 7, 'h4': 4, 'h5': 5, 'h21': 21, 'h20': 20, 'h23': 23, 'h22': 22, 'h18': 18, 'h19': 19, 'h10': 10, 'h11': 11, 'h12': 12, 'h13': 13, 'h14': 14, 'h15': 15, 'h16': 16, 'h17': 17.

The set of minutes within an hour when the scheduled action should take place. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed. Bits: 'm41': 41, 'm46': 46, 'm47': 47, 'm11': 11, 'm10': 10, 'm13': 13, 'm12': 12, 'm15': 15, 'm14': 14, 'm17': 17, 'm16': 16, 'm19': 19, 'm18': 18, 'm45': 45, 'm44': 44, 'm55': 55, 'm54': 54, 'm57': 57, 'm56': 56, 'm51': 51, 'm50': 50, 'm39': 39, 'm38': 38, 'm37': 37, 'm36': 36, 'm35': 35, 'm34': 34, 'm33': 33, 'm32': 32, 'm31': 31, 'm30': 30, 'm5': 5, 'm4': 4, 'm7': 7, 'm6': 6, 'm1': 1, 'm0': 0, 'm3': 3, 'm2': 2, 'm52': 52, 'm53': 53, 'm9': 9, 'm8': 8, 'm58': 58, 'm59': 59, 'm48': 48, 'm49': 49, 'm28': 28, 'm29': 29, 'm24': 24, 'm25': 25, 'm26': 26, 'm27': 27, 'm20': 20, 'm21': 21, 'm22': 22, 'm23': 23, 'm42': 42, 'm43': 43, 'm40': 40.

The context which contains the local MIB variable pointed to by schedVariable.

An object identifier pointing to a local MIB variable which resolves to an ASN.1 primitive type of INTEGER.

The value which is written to the MIB object pointed to by schedVariable when the scheduler invokes an action. The implementation shall enforce the use of access control rules when performing the set operation on schedVariable. This is accomplished by calling the isAccessAllowed abstract service interface as defined in RFC 2571. Note that an implementation may choose to issue an SNMP Set message to the SNMP engine and leave the access control decision to the normal message processing procedure.

The type of this schedule. The value periodic(1) indicates that this entry specifies a periodic schedule. A periodic schedule is defined by the value of schedInterval. The values of schedWeekDay, schedMonth, schedDay, schedHour and schedMinute are ignored. The value calendar(2) indicates that this entry describes a calendar schedule. A calendar schedule is defined by the values of schedWeekDay, schedMonth, schedDay, schedHour and schedMinute. The value of schedInterval is ignored. A calendar schedule will trigger on all local times that satisfy the bits set in schedWeekDay, schedMonth, schedDay, schedHour and schedMinute. The value oneshot(3) indicates that this entry describes a one-shot schedule. A one-shot schedule is similar to a calendar schedule with the additional feature that it disables itself by changing in the `finished' schedOperStatus once the schedule triggers an action. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed. Enumeration: 'oneshot': 3, 'calendar': 2, 'periodic': 1.

The desired state of the schedule. Enumeration: 'disabled': 2, 'enabled': 1.

The current operational state of this schedule. The state enabled(1) indicates this entry is active and that the scheduler will invoke actions at appropriate times. The disabled(2) state indicates that this entry is currently inactive and ignored by the scheduler. The finished(3) state indicates that the schedule has ended. Schedules in the finished(3) state are ignored by the scheduler. A one-shot schedule enters the finished(3) state when it deactivates itself. Note that the operational state must not be enabled(1) when the schedRowStatus is not active. Enumeration: 'disabled': 2, 'finished': 3, 'enabled': 1.

This variable counts the number of failures while invoking the scheduled action. This counter at most increments once for a triggered action.

The most recent error that occurred during the invocation of a scheduled action. The value noError(0) is returned if no errors have occurred yet.

The date and time when the most recent failure occurred. The value '0000000000000000'H is returned if no failure occurred since the last re-initialization of the scheduler.

This object defines whether this scheduled action is kept in volatile storage and lost upon reboot or if this row is backed up by non-volatile or permanent storage. Conceptual rows having the value `permanent' must allow write access to the columnar objects schedDescr, schedInterval, schedContextName, schedVariable, schedValue, and schedAdminStatus. If an implementation supports the schedCalendarGroup, write access must be also allowed to the columnar objects schedWeekDay, schedMonth, schedDay, schedHour, schedMinute.

The status of this scheduled action. A control that allows entries to be added and removed from this table. Note that the operational state must change to enabled when the administrative state is enabled and the row status changes to active(1). Attempts to destroy(6) a row or to set a row notInService(2) while the operational state is enabled result in inconsistentValue errors. The value of this object has no effect on whether other objects in this conceptual row can be modified.

This variable counts the number of attempts (either successful or failed) to invoke the scheduled action.

This notification is generated whenever the invocation of a scheduled action fails.

The compliance statement for SNMP entities which implement the scheduling MIB.

The compliance statement for SNMP entities which implement the scheduling MIB.

A collection of objects providing scheduling capabilities.

A collection of objects providing calendar based schedules.

The notifications emitted by the scheduler.

A collection of objects providing scheduling capabilities.