The overall range of calendar dates and times over which this
schedule is active. It is stored in a slightly extended version
of the format for a 'period-explicit' defined in RFC 2445.
This format is expressed as a string representing the
starting date and time, in which the character 'T' indicates
the beginning of the time portion, followed by the solidus
character, '/', followed by a similar string representing an
end date and time. The start of the period MUST be before the
end of the period. Date-Time values are expressed as
substrings of the form 'yyyymmddThhmmss'. For example:
20000101T080000/20000131T130000
January 1, 2000, 0800 through January 31, 2000, 1PM
The 'Date with UTC time' format defined in RFC 2445 in which
the Date-Time string ends with the character 'Z' is not
allowed.
This 'period-explicit' format is also extended to allow two
special cases in which one of the Date-Time strings is
replaced with a special string defined in RFC 2445:
1. If the first Date-Time value is replaced with the string
'THISANDPRIOR', then the value indicates that the schedule
is active at any time prior to the Date-Time that appears
after the '/'.
2. If the second Date-Time is replaced with the string
'THISANDFUTURE', then the value indicates that the schedule
is active at any time after the Date-Time that appears
before the '/'.
Note that although RFC 2445 defines these two strings, they are
not specified for use in the 'period-explicit' format. The use
of these strings represents an extension to the
'period-explicit' format.
Parsed from file POLICY-BASED-MANAGEMENT-MIB.mib
Module: POLICY-BASED-MANAGEMENT-MIB
Vendor: IETF RFCs
Module: POLICY-BASED-MANAGEMENT-MIB (rfc4011-Policy-Based-Management.mib)
Type: TABULAR
Access: read-create
Syntax: PmUTF8String
(
0..31 )
Automatically extracted from www.mibdepot.com
pmSchedTimePeriod OBJECT-TYPE SYNTAX PmUTF8String (SIZE (0..31)) MAX-ACCESS read-create STATUS current DESCRIPTION "The overall range of calendar dates and times over which this schedule is active. It is stored in a slightly extended version of the format for a 'period-explicit' defined in RFC 2445. This format is expressed as a string representing the starting date and time, in which the character 'T' indicates the beginning of the time portion, followed by the solidus character, '/', followed by a similar string representing an end date and time. The start of the period MUST be before the end of the period. Date-Time values are expressed as substrings of the form 'yyyymmddThhmmss'. For example: 20000101T080000/20000131T130000 January 1, 2000, 0800 through January 31, 2000, 1PM The 'Date with UTC time' format defined in RFC 2445 in which the Date-Time string ends with the character 'Z' is not allowed. This 'period-explicit' format is also extended to allow two special cases in which one of the Date-Time strings is replaced with a special string defined in RFC 2445: 1. If the first Date-Time value is replaced with the string 'THISANDPRIOR', then the value indicates that the schedule is active at any time prior to the Date-Time that appears after the '/'. 2. If the second Date-Time is replaced with the string 'THISANDFUTURE', then the value indicates that the schedule is active at any time after the Date-Time that appears before the '/'. Note that although RFC 2445 defines these two strings, they are not specified for use in the 'period-explicit' format. The use of these strings represents an extension to the 'period-explicit' format." ::= { pmSchedEntry 4 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.124.8.1.1 | pmSchedIndex | 0 | 0 | The locally unique, administratively assigned index for this scheduling entry. |
| 1.3.6.1.2.1.124.8.1.2 | pmSchedGroupIndex | 0 | 0 | The locally unique, administratively assigned index for the schedule group this scheduling entry belongs to. To assign multiple s… |
| 1.3.6.1.2.1.124.8.1.3 | pmSchedDescr | 0 | 0 | The human-readable description of the purpose of this scheduling entry. |
| 1.3.6.1.2.1.124.8.1.5 | pmSchedMonth | 0 | 0 | Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the specific months … |
| 1.3.6.1.2.1.124.8.1.6 | pmSchedDay | 0 | 0 | Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the specific days of… |
| 1.3.6.1.2.1.124.8.1.7 | pmSchedWeekDay | 0 | 0 | Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the specific days of… |
| 1.3.6.1.2.1.124.8.1.8 | pmSchedTimeOfDay | 0 | 0 | Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the range of times i… |
| 1.3.6.1.2.1.124.8.1.9 | pmSchedLocalOrUtc | 0 | 0 | This object indicates whether the times represented in the TimePeriod object and in the various Mask objects represent local time… |
| 1.3.6.1.2.1.124.8.1.10 | pmSchedStorageType | 0 | 0 | This object defines whether this schedule entry is kept in volatile storage and lost upon reboot or backed up by non-volatile or … |
| 1.3.6.1.2.1.124.8.1.11 | pmSchedRowStatus | 0 | 0 | The status of this schedule entry. If the value of this object is active, no object in this row may be modified. |