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 pmSchedInterval. The
values of pmSchedWeekDay, pmSchedMonth, pmSchedDay,
pmSchedHour and pmSchedMinute are ignored.
The value calendar(2) indicates that this entry describes a
calendar schedule. A calendar schedule is defined by the
values of pmSchedWeekDay, pmSchedMonth, pmSchedDay,
pmSchedHour and pmSchedMinute. The value of pmSchedInterval
is ignored. A calendar schedule will be active on all local
times that satisfy the bits set in pmSchedWeekDay,
pmSchedMonth, pmSchedDay, pmSchedHour and pmSchedMinute.
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'
pmSchedOperStatus once the schedule becomes inactive after
its first activation.
Changing a schedule's type is equivalent to deleting the
old-type schedule and creating a new-type one.
Parsed from file POLICY-MANAGEMENT-MIB-snmpconf-05.txt
Company: ietf_drafts
Module: POLICY-MANAGEMENT-MIB
pmSchedType OBJECT-TYPE SYNTAX INTEGER { periodic(1), calendar(2), oneshot(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "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 pmSchedInterval. The values of pmSchedWeekDay, pmSchedMonth, pmSchedDay, pmSchedHour and pmSchedMinute are ignored. The value calendar(2) indicates that this entry describes a calendar schedule. A calendar schedule is defined by the values of pmSchedWeekDay, pmSchedMonth, pmSchedDay, pmSchedHour and pmSchedMinute. The value of pmSchedInterval is ignored. A calendar schedule will be active on all local times that satisfy the bits set in pmSchedWeekDay, pmSchedMonth, pmSchedDay, pmSchedHour and pmSchedMinute. 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' pmSchedOperStatus once the schedule becomes inactive after its first activation. Changing a schedule's type is equivalent to deleting the old-type schedule and creating a new-type one." DEFVAL { periodic } ::= { pmSchedEntry 11 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.3.107.8.1.1 | pmSchedIndex, pmDebuggingElement | 0 | 0 | The locally-unique, administratively assigned index for this scheduling entry. |
| 1.3.6.1.3.107.8.1.2 | pmSchedGroupIndex, pmDebuggingLogIndex | 0 | 0 | A unique index for this log entry amongst other log entries for this policy/element combination. |
| 1.3.6.1.3.107.8.1.3 | pmSchedDescr, pmDebuggingMessage | 0 | 0 | An error message generated by the expression runtime system. |
| 1.3.6.1.3.107.8.1.4 | pmSchedInterval, pmSchedTimePeriod | 0 | 0 | The number of seconds between two activations of a periodic scheduler. Implementations must guarantee that activations will not o… |
| 1.3.6.1.3.107.8.1.5 | pmSchedWeekDay, pmSchedMonth | 0 | 0 | The set of weekdays on which the schedule should be active. Setting multiple bits will include several weekdays in the set of pos… |
| 1.3.6.1.3.107.8.1.6 | pmSchedMonth, pmSchedDay | 0 | 0 | The set of months during which the schedule should be active. Setting multiple bits will include several months in the set of pos… |
| 1.3.6.1.3.107.8.1.7 | pmSchedDay, pmSchedWeekDay | 0 | 0 | The set of days in a month on which a schedule should be active. There are two sets of bits one can use to define the day within … |
| 1.3.6.1.3.107.8.1.8 | pmSchedHour, pmSchedTimeOfDay | 0 | 0 | The set of hours within a day during which the schedule should be active. |
| 1.3.6.1.3.107.8.1.9 | pmSchedMinute, pmSchedLocalOrUtc | 0 | 0 | The set of minutes within an hour when the schedule should be active. |
| 1.3.6.1.3.107.8.1.10 | pmSchedDuration, pmSchedStorageType | 0 | 0 | The number of seconds the schedule will be active after invocation. |
| 1.3.6.1.3.107.8.1.12 | pmSchedAdminStatus | 0 | 0 | The desired state of the schedule. |
| 1.3.6.1.3.107.8.1.13 | pmSchedOperStatus | 0 | 0 | The current operational state of this schedule. The state enabled(1) indicates this entry is active and that the scheduler will i… |
| 1.3.6.1.3.107.8.1.14 | pmSchedStorageType | 0 | 0 | This object defines whether this scheduled action is kept in volatile storage and lost upon reboot or if this row is backed up by… |
| 1.3.6.1.3.107.8.1.15 | pmSchedRowStatus | 0 | 0 | The status of this scheduled action. |