DISMAN-SCHEDULE-MIB

All MIBs › DISMAN-SCHEDULE-MIB

Organization: IETF Distributed Management Working Group

Last Updated: 2002-01-07

Category: SNMP Framework

Description:

Defines objects for scheduling SNMP SET operations on the local agent at specified times or periodic intervals.

Imported Objects

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
mib-2
zeroDotZero

From SNMPv2-TC

DateAndTime
RowStatus
StorageType
TEXTUAL-CONVENTION
VariablePointer

What Is DISMAN-SCHEDULE-MIB?

DISMAN-SCHEDULE-MIB is a vendor-neutral IETF Distributed Management standard MIB that defines objects for scheduling SNMP SET operations on the local agent, either at specific calendar times or on periodic intervals. It exposes a schedule table describing when configured actions should run, along with the local time reference used for evaluation. Its monitoring role is administrative rather than hardware-focused: it lets an operator confirm which automated configuration changes are scheduled, verify the agent's local time is correct, and detect scheduling entries that may be misconfigured or disabled. It is commonly used in conjunction with DISMAN-EVENT-MIB and SNMPv3 SET operations to build self-managing, autonomous device behaviors. It is typically deployed on SNMP agents that need to perform recurring or time-based configuration changes, such as periodic resets or scheduled parameter updates, without external cron-like infrastructure. Engineers implementing or auditing this functionality typically reference the DISMAN-SCHEDULE-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in DISMAN-SCHEDULE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

scheduled task name and description
schedule interval/day/hour/minute
agent local time reference
scheduled objects targeted for SET

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer; applies to any SNMP agent supporting scheduled operations

Monitoring Examples

An operator can poll schedTable/schedEntry to review schedName, schedDescr, and the timing fields schedInterval, schedWeekDay, schedMonth, schedDay, schedHour, and schedMinute for each scheduled action, confirming whether a maintenance task is set to run at the intended time. Comparing schedLocalTime against the expected wall-clock time helps detect agent clock drift that would cause scheduled SETs (referenced via schedObjects) to fire at the wrong moment.

OIDs

OID symbolic	OID numeric	Type	Access	Description
NTF schedActionFailure	1.3.6.1.2.1.63.2.0.1			This notification is generated whenever the invocation of a scheduled action fails.
INT schedAdminStatus	1.3.6.1.2.1.63.1.2.1.14	INTEGER	read-create	The desired state of the schedule.
schedCalendarGroup	1.3.6.1.2.1.63.3.2.2			A collection of objects providing calendar based schedules.
schedCompliance	1.3.6.1.2.1.63.3.1.1			The compliance statement for SNMP entities which implement the scheduling MIB.
schedCompliance2	1.3.6.1.2.1.63.3.1.2			The compliance statement for SNMP entities which implement the scheduling MIB.
schedCompliances	1.3.6.1.2.1.63.3.1
schedConformance	1.3.6.1.2.1.63.3
STR schedContextName	1.3.6.1.2.1.63.1.2.1.10	SnmpAdminString	read-create	The context which contains the local MIB variable pointed to by schedVariable.
BIT schedDay	1.3.6.1.2.1.63.1.2.1.7	Bits	read-create	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.
STR schedDescr	1.3.6.1.2.1.63.1.2.1.3	SnmpAdminString	read-create	The human readable description of the purpose of this scheduling entry.
schedEntry	1.3.6.1.2.1.63.1.2.1		not-accessible	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.
C32 schedFailures	1.3.6.1.2.1.63.1.2.1.16	Counter32	read-only	This variable counts the number of failures while invoking the scheduled action. This counter at most increments once for a triggered action.
schedGroup	1.3.6.1.2.1.63.3.2.1			A collection of objects providing scheduling capabilities.
schedGroup2	1.3.6.1.2.1.63.3.2.4			A collection of objects providing scheduling capabilities.
schedGroups	1.3.6.1.2.1.63.3.2
BIT schedHour	1.3.6.1.2.1.63.1.2.1.8	Bits	read-create	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.
U32 schedInterval	1.3.6.1.2.1.63.1.2.1.4	Unsigned32	read-create	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.
DAT schedLastFailed	1.3.6.1.2.1.63.1.2.1.18	DateAndTime	read-only	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.
SNM schedLastFailure	1.3.6.1.2.1.63.1.2.1.17	SnmpPduErrorStatus	read-only	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.
DAT schedLocalTime	1.3.6.1.2.1.63.1.1	DateAndTime	read-only	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.
schedMIB	1.3.6.1.2.1.63			This MIB module defines a MIB which provides mechanisms to schedule SNMP set operations periodically or at specific points in time.
BIT schedMinute	1.3.6.1.2.1.63.1.2.1.9	Bits	read-create	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.
BIT schedMonth	1.3.6.1.2.1.63.1.2.1.6	Bits	read-create	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.
STR schedName	1.3.6.1.2.1.63.1.2.1.2	SnmpAdminString	not-accessible	The locally-unique, administratively assigned name for this scheduling entry. This object allows a schedOwner to have multiple entries in the schedTable.
schedNotifications	1.3.6.1.2.1.63.2
schedNotificationsGroup	1.3.6.1.2.1.63.3.2.3			The notifications emitted by the scheduler.
schedObjects	1.3.6.1.2.1.63.1
INT schedOperStatus	1.3.6.1.2.1.63.1.2.1.15	INTEGER	read-only	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.
STR schedOwner	1.3.6.1.2.1.63.1.2.1.1	SnmpAdminString	not-accessible	The owner of this scheduling entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
ROW schedRowStatus	1.3.6.1.2.1.63.1.2.1.20	RowStatus	read-create	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.
STO schedStorageType	1.3.6.1.2.1.63.1.2.1.19	StorageType	read-create	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.
schedTable	1.3.6.1.2.1.63.1.2		not-accessible	This table defines scheduled actions triggered by SNMP set operations.
schedTraps	1.3.6.1.2.1.63.2.0
C32 schedTriggers	1.3.6.1.2.1.63.1.2.1.21	Counter32	read-only	This variable counts the number of attempts (either successful or failed) to invoke the scheduled action.
INT schedType	1.3.6.1.2.1.63.1.2.1.13	INTEGER	read-create	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.
I32 schedValue	1.3.6.1.2.1.63.1.2.1.12	Integer32	read-create	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.
NUM schedVariable	1.3.6.1.2.1.63.1.2.1.11	VariablePointer	read-create	An object identifier pointing to a local MIB variable which resolves to an ASN.1 primitive type of INTEGER.
BIT schedWeekDay	1.3.6.1.2.1.63.1.2.1.5	Bits	read-create	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.

OID symbolic	OID numeric	Type	Access	Description
schedMIB	1.3.6.1.2.1.63			This MIB module defines a MIB which provides mechanisms to schedule SNMP set operations periodically or at specific points in time.
schedObjects	1.3.6.1.2.1.63.1
DAT schedLocalTime	1.3.6.1.2.1.63.1.1	DateAndTime	read-only	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.
schedTable	1.3.6.1.2.1.63.1.2		not-accessible	This table defines scheduled actions triggered by SNMP set operations.
schedEntry	1.3.6.1.2.1.63.1.2.1		not-accessible	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.
STR schedOwner	1.3.6.1.2.1.63.1.2.1.1	SnmpAdminString	not-accessible	The owner of this scheduling entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
STR schedName	1.3.6.1.2.1.63.1.2.1.2	SnmpAdminString	not-accessible	The locally-unique, administratively assigned name for this scheduling entry. This object allows a schedOwner to have multiple entries in the schedTable.
STR schedDescr	1.3.6.1.2.1.63.1.2.1.3	SnmpAdminString	read-create	The human readable description of the purpose of this scheduling entry.
U32 schedInterval	1.3.6.1.2.1.63.1.2.1.4	Unsigned32	read-create	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.
BIT schedWeekDay	1.3.6.1.2.1.63.1.2.1.5	Bits	read-create	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.
BIT schedMonth	1.3.6.1.2.1.63.1.2.1.6	Bits	read-create	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.
BIT schedDay	1.3.6.1.2.1.63.1.2.1.7	Bits	read-create	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.
BIT schedHour	1.3.6.1.2.1.63.1.2.1.8	Bits	read-create	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.
BIT schedMinute	1.3.6.1.2.1.63.1.2.1.9	Bits	read-create	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.
STR schedContextName	1.3.6.1.2.1.63.1.2.1.10	SnmpAdminString	read-create	The context which contains the local MIB variable pointed to by schedVariable.
NUM schedVariable	1.3.6.1.2.1.63.1.2.1.11	VariablePointer	read-create	An object identifier pointing to a local MIB variable which resolves to an ASN.1 primitive type of INTEGER.
I32 schedValue	1.3.6.1.2.1.63.1.2.1.12	Integer32	read-create	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.
INT schedType	1.3.6.1.2.1.63.1.2.1.13	INTEGER	read-create	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.
INT schedAdminStatus	1.3.6.1.2.1.63.1.2.1.14	INTEGER	read-create	The desired state of the schedule.
INT schedOperStatus	1.3.6.1.2.1.63.1.2.1.15	INTEGER	read-only	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.
C32 schedFailures	1.3.6.1.2.1.63.1.2.1.16	Counter32	read-only	This variable counts the number of failures while invoking the scheduled action. This counter at most increments once for a triggered action.
SNM schedLastFailure	1.3.6.1.2.1.63.1.2.1.17	SnmpPduErrorStatus	read-only	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.
DAT schedLastFailed	1.3.6.1.2.1.63.1.2.1.18	DateAndTime	read-only	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.
STO schedStorageType	1.3.6.1.2.1.63.1.2.1.19	StorageType	read-create	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.
ROW schedRowStatus	1.3.6.1.2.1.63.1.2.1.20	RowStatus	read-create	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.
C32 schedTriggers	1.3.6.1.2.1.63.1.2.1.21	Counter32	read-only	This variable counts the number of attempts (either successful or failed) to invoke the scheduled action.
schedNotifications	1.3.6.1.2.1.63.2
schedTraps	1.3.6.1.2.1.63.2.0
NTF schedActionFailure	1.3.6.1.2.1.63.2.0.1			This notification is generated whenever the invocation of a scheduled action fails.
schedConformance	1.3.6.1.2.1.63.3
schedCompliances	1.3.6.1.2.1.63.3.1
schedCompliance	1.3.6.1.2.1.63.3.1.1			The compliance statement for SNMP entities which implement the scheduling MIB.
schedCompliance2	1.3.6.1.2.1.63.3.1.2			The compliance statement for SNMP entities which implement the scheduling MIB.
schedGroups	1.3.6.1.2.1.63.3.2
schedGroup	1.3.6.1.2.1.63.3.2.1			A collection of objects providing scheduling capabilities.
schedCalendarGroup	1.3.6.1.2.1.63.3.2.2			A collection of objects providing calendar based schedules.
schedNotificationsGroup	1.3.6.1.2.1.63.3.2.3			The notifications emitted by the scheduler.
schedGroup2	1.3.6.1.2.1.63.3.2.4			A collection of objects providing scheduling capabilities.

Bits (5)
BIT schedDay	1.3.6.1.2.1.63.1.2.1.7	Bits	read-create	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.
BIT schedHour	1.3.6.1.2.1.63.1.2.1.8	Bits	read-create	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.
BIT schedMinute	1.3.6.1.2.1.63.1.2.1.9	Bits	read-create	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.
BIT schedMonth	1.3.6.1.2.1.63.1.2.1.6	Bits	read-create	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.
BIT schedWeekDay	1.3.6.1.2.1.63.1.2.1.5	Bits	read-create	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.
Counter32 (2)
C32 schedFailures	1.3.6.1.2.1.63.1.2.1.16	Counter32	read-only	This variable counts the number of failures while invoking the scheduled action. This counter at most increments once for a triggered action.
C32 schedTriggers	1.3.6.1.2.1.63.1.2.1.21	Counter32	read-only	This variable counts the number of attempts (either successful or failed) to invoke the scheduled action.
DateAndTime (2)
DAT schedLastFailed	1.3.6.1.2.1.63.1.2.1.18	DateAndTime	read-only	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.
DAT schedLocalTime	1.3.6.1.2.1.63.1.1	DateAndTime	read-only	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.
INTEGER (3)
INT schedAdminStatus	1.3.6.1.2.1.63.1.2.1.14	INTEGER	read-create	The desired state of the schedule.
INT schedOperStatus	1.3.6.1.2.1.63.1.2.1.15	INTEGER	read-only	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.
INT schedType	1.3.6.1.2.1.63.1.2.1.13	INTEGER	read-create	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.
Integer32 (1)
I32 schedValue	1.3.6.1.2.1.63.1.2.1.12	Integer32	read-create	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.
RowStatus (1)
ROW schedRowStatus	1.3.6.1.2.1.63.1.2.1.20	RowStatus	read-create	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.
SnmpAdminString (4)
STR schedContextName	1.3.6.1.2.1.63.1.2.1.10	SnmpAdminString	read-create	The context which contains the local MIB variable pointed to by schedVariable.
STR schedDescr	1.3.6.1.2.1.63.1.2.1.3	SnmpAdminString	read-create	The human readable description of the purpose of this scheduling entry.
STR schedName	1.3.6.1.2.1.63.1.2.1.2	SnmpAdminString	not-accessible	The locally-unique, administratively assigned name for this scheduling entry. This object allows a schedOwner to have multiple entries in the schedTable.
STR schedOwner	1.3.6.1.2.1.63.1.2.1.1	SnmpAdminString	not-accessible	The owner of this scheduling entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
SnmpPduErrorStatus (1)
SNM schedLastFailure	1.3.6.1.2.1.63.1.2.1.17	SnmpPduErrorStatus	read-only	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.
StorageType (1)
STO schedStorageType	1.3.6.1.2.1.63.1.2.1.19	StorageType	read-create	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.
Unsigned32 (1)
U32 schedInterval	1.3.6.1.2.1.63.1.2.1.4	Unsigned32	read-create	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.
VariablePointer (1)
NUM schedVariable	1.3.6.1.2.1.63.1.2.1.11	VariablePointer	read-create	An object identifier pointing to a local MIB variable which resolves to an ASN.1 primitive type of INTEGER.
No type (16)
NTF schedActionFailure	1.3.6.1.2.1.63.2.0.1			This notification is generated whenever the invocation of a scheduled action fails.
schedCalendarGroup	1.3.6.1.2.1.63.3.2.2			A collection of objects providing calendar based schedules.
schedCompliance	1.3.6.1.2.1.63.3.1.1			The compliance statement for SNMP entities which implement the scheduling MIB.
schedCompliance2	1.3.6.1.2.1.63.3.1.2			The compliance statement for SNMP entities which implement the scheduling MIB.
schedCompliances	1.3.6.1.2.1.63.3.1
schedConformance	1.3.6.1.2.1.63.3
schedEntry	1.3.6.1.2.1.63.1.2.1		not-accessible	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.
schedGroup	1.3.6.1.2.1.63.3.2.1			A collection of objects providing scheduling capabilities.
schedGroup2	1.3.6.1.2.1.63.3.2.4			A collection of objects providing scheduling capabilities.
schedGroups	1.3.6.1.2.1.63.3.2
schedMIB	1.3.6.1.2.1.63			This MIB module defines a MIB which provides mechanisms to schedule SNMP set operations periodically or at specific points in time.
schedNotifications	1.3.6.1.2.1.63.2
schedNotificationsGroup	1.3.6.1.2.1.63.3.2.3			The notifications emitted by the scheduler.
schedObjects	1.3.6.1.2.1.63.1
schedTable	1.3.6.1.2.1.63.1.2		not-accessible	This table defines scheduled actions triggered by SNMP set operations.
schedTraps	1.3.6.1.2.1.63.2.0

RFC description

Enables scheduling of SNMP set operations at specific times or periodic intervals for distributed network management automation.

Start monitoring SNMP agent supporting scheduled operations (vendor-neutral, DISMAN) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download DISMAN-SCHEDULE-MIB

This MIB depends on

Related MIBs

What Is DISMAN-SCHEDULE-MIB?

What Can Be Monitored

Supported Devices

Monitoring Examples

RFC description