schedMonth OBJECT-TYPE
SYNTAX BITS {
january(0),
february(1),
march(2),
april(3),
may(4),
june(5),
july(6),
august(7),
september(8),
october(9),
november(10),
december(11)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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."
DEFVAL { {} }
View at oid-info.com
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.
Parsed from file DISMAN-SCHEDULE-MIB.txt
Company: None
Module: DISMAN-SCHEDULE-MIB
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.
Parsed from file DISMAN-SCHEDULE-MIB.mib
Module: DISMAN-SCHEDULE-MIB
Automatically extracted from RFC3231
schedMonth OBJECT-TYPE SYNTAX BITS { january(0), february(1), march(2), april(3), may(4), june(5), july(6), august(7), september(8), october(9), november(10), december(11) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { {} } ::= { schedEntry 6 }
schedMonth OBJECT-TYPE SYNTAX BITS { january(0), february(1), march(2), april(3), may(4), june(5), july(6), august(7), september(8), october(9), november(10), december(11) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { {} } ::= { schedEntry 6 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.63.1.2.1.1 | schedOwner | 0 | 0 | The owner of this scheduling entry. The exact semantics of this string are subject to the security policy defined by the securit… |
| 1.3.6.1.2.1.63.1.2.1.2 | schedName | 0 | 0 | The locally-unique, administratively assigned name for this scheduling entry. This object allows a schedOwner to have multiple en… |
| 1.3.6.1.2.1.63.1.2.1.3 | schedDescr | 0 | 0 | The human readable description of the purpose of this scheduling entry. |
| 1.3.6.1.2.1.63.1.2.1.4 | schedInterval | 0 | 0 | The number of seconds between two action invocations of a periodic scheduler. Implementations must guarantee that action invocati… |
| 1.3.6.1.2.1.63.1.2.1.5 | schedWeekDay | 0 | 0 | The set of weekdays on which the scheduled action should take place. Setting multiple bits will include several weekdays in the s… |
| 1.3.6.1.2.1.63.1.2.1.7 | schedDay | 0 | 0 | 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 da… |
| 1.3.6.1.2.1.63.1.2.1.8 | schedHour | 0 | 0 | The set of hours within a day during which the scheduled action should take place. |
| 1.3.6.1.2.1.63.1.2.1.9 | schedMinute | 0 | 0 | The set of minutes within an hour when the scheduled action should take place. |
| 1.3.6.1.2.1.63.1.2.1.10 | schedContextName | 0 | 0 | The context which contains the local MIB variable pointed to by schedVariable. |
| 1.3.6.1.2.1.63.1.2.1.11 | schedVariable | 0 | 0 | An object identifier pointing to a local MIB variable which resolves to an ASN.1 primitive type of INTEGER. |
| 1.3.6.1.2.1.63.1.2.1.12 | schedValue | 0 | 0 | The value which is written to the MIB object pointed to by schedVariable when the scheduler invokes an action. The implementation… |
| 1.3.6.1.2.1.63.1.2.1.13 | schedType | 0 | 0 | The type of this schedule. The value periodic(1) indicates that this entry specifies a periodic schedule. A periodic schedule is … |
| 1.3.6.1.2.1.63.1.2.1.14 | schedAdminStatus | 0 | 0 | The desired state of the schedule. |
| 1.3.6.1.2.1.63.1.2.1.15 | schedOperStatus | 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.2.1.63.1.2.1.16 | schedFailures | 0 | 0 | This variable counts the number of failures while invoking the scheduled action. |
| 1.3.6.1.2.1.63.1.2.1.17 | schedLastFailure | 0 | 0 | The most recent error that occured during the invocation of a scheduled action. The value noError(0) is returned if no errors hav… |
| 1.3.6.1.2.1.63.1.2.1.18 | schedLastFailed | 0 | 0 | The date and time when the most recent failure occured. The value '0000000000000000'H is returned if no failure occured since the… |
| 1.3.6.1.2.1.63.1.2.1.19 | schedStorageType | 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.2.1.63.1.2.1.20 | schedRowStatus | 0 | 0 | The status of this scheduled action. A control that allows entries to be added and removed from this table. The miminum number of… |
| 1.3.6.1.2.1.63.1.2.1.21 | schedTriggers | 0 | 0 | This variable counts the number of attempts (either successful or failed) to invoke the scheduled action. |