Available source records contain 6 distinct definitions; some records may not include a definition.
Show 6 published definitions
timeBaseScheduleTable · mandatory
timeBaseScheduleTable OBJECT-TYPE
SYNTAX SEQUENCE OF TimeBaseScheduleEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"<Definition>A table containing the time base schedule parameters for the device. The number of rows in this table shall be equal to the maxTimeBaseScheduleEntries object. The table references the appropriate day plan for the device. The plan is determined by comparing the current month (MONTH), day of week (DOW) and date of month (DOM) to the appropriate fields. The settings for MONTH, DOW and DOM are connected with a logical AND. In order to determine which timebased event to select, determine the event which has the most specific date specified. Select the more specific event based on their MONTH settings; if the same, select the most specific DOM; if that is still the same, select the most specific DOW; if that's still the same, the first occurrence within the time base event table shall be selected. 'More specific' means the least number of bits set within an object. All entries in Time Base Schedule Table are expressed in local time and date. A row in the table may be deactivated by setting the Month, Day, Date, or DayPlan parameters to zero (0)
<DescriptiveName>TimeBaseScheduleTable
<DataConceptType>Entity Type
<TableType> static"
::= { timebase 2 }timeBaseScheduleTable · unconfirmed
timeBaseScheduleTable OBJECT-TYPE
SYNTAX SEQUENCE OF TimeBaseScheduleEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"<Definition> A table containing the time base schedule parameters for the
device. The number of rows in this table shall be equal to the
maxTimeBaseScheduleEntries object. The table references the appropriate day
plan for the device. The plan is determined by comparing the current month
(MONTH), day of week (DOW) and date of month (DOM) to the appropriate
fields. The settings for MONTH, DOW and DOM are connected with a logical
AND. To determine which timebased event to select, determine the event
which has the most specific date specified. Select the more specific event
based on their MONTH settings; if the same, select the most specific DOM;
if that is still the same, select the most specific DOW; if still the same,
the first occurrence within the time base event table shall be selected.
'More specific' means the least number of bits set within an object. All
entries in Time Base Schedule Table are expressed in local time and date. A
row in the table may be deactivated by setting the Month, Day, Date, or
DayPlan parameters to zero (0)
<Table Type> static
<Supplanted by> DAY-PLAN-MIB.fdDayPlanScheduleTable (ISO 26048-1)
<Informative> The original timeBaseScheuleDate object was defined as
INTEGER (0..4294967295); however, by convention, SNMPv1 does not allow
unsigned 32-bit integers and SNMPv3 prohibits them. The revise table
addresses this issue and is also treated using trigger logic so that it can
be used to activate a day plan (as originally envisioned) and/or to call
other actions (e.g., creating a log entry).
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.2"
::= { timebase 2 }timeBaseScheduleTable · mandatory
timeBaseScheduleTable OBJECT-TYPE
SYNTAX SEQUENCE OF TimeBaseScheduleEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table containing the time base schedule parameters for the device. The number of rows in this table
might be equal but is not allowed to exceed the value of the maxTimeBaseScheduleEntries object. The
table references the appropriate day plan for the device. The plan is determined by comparing the
current month (MONTH), day of week (DOW) and date of month (DOM) to the appropriate fields. The
settings for MONTH, DOW and DOM are connected with a logical AND. In order to determine which
timebased event to select, determine the event which has the most specific date specified. Select the
more specific event based on their MONTH settings; if the same, select the most specific DOM; if that is
still the same, select the most specific DOW; if that’s still the same, the first occurrence within the time
base event table shall be selected. "More specific" means the least number of bits set within an object.
All entries in Time Base Schedule Table are expressed in local time and date."
::= { timebase 2 }timeBaseScheduleTable · mandatory
timeBaseScheduleTable OBJECT-TYPE
SYNTAX SEQUENCE OF TimeBaseScheduleEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"<Definition>A table containing the time base schedule parameters
for the device. The number of rows in this table shall be equal
to the maxTimeBaseScheduleEntries object. The table references
the appropriate day plan for the device. The plan is determined
by comparing the current month (MONTH), day of week (DOW) and date
of month (DOM) to the appropriate fields. The settings for MONTH,
DOW and DOM are connected with a logical AND. To determine which
timebased event to select, determine the event which has the most
specific date specified. Select the more specific event based on
their MONTH settings; if the same, select the most specific DOM;
if that is still the same, select the most specific DOW; if still
the same, the first occurrence within the time base event table
shall be selected. ’More specific’ means the least number of bits
set within an object. All entries in Time Base Schedule Table are
expressed in local time and date. A row in the table may be
deactivated by setting the Month, Day, Date, or DayPlan parameters
to zero (0)
<TableType> static
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.2"
::= { timebase 2 }timeBaseScheduleTable · deprecated
timeBaseScheduleTable OBJECT-TYPE
SYNTAX SEQUENCE OF TimeBaseScheduleEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"<Definition> A table containing the time base schedule parameters for the device. The number of rows in this table shall be equal to the maxTimeBaseScheduleEntries object. The table references the appropriate day plan for the device. The plan is determined by comparing the current month (MONTH), day of week (DOW) and date of month (DOM) to the appropriate fields. The settings for MONTH, DOW and DOM are connected with a logical AND. To determine which timebased event to select, determine the event which has the most specific date specified. Select the more specific event based on their MONTH settings; if the same, select the most specific DOM; if that is still the same, select the most specific DOW; if still the same, the first occurrence within the time base event table shall be selected. 'More specific' means the least number of bits set within an object. All entries in Time Base Schedule Table are expressed in local time and date. A row in the table may be deactivated by setting the Month, Day, Date, or DayPlan parameters to zero (0)
<TableType> static
<Superseded by> DAY-PLAN-MIB.fdDayPlanScheduleTable (ISO 20684-3)
<Informative> The original timeBaseScheuleDate object was defined as INTEGER (0..4294967295); however, by convention, SNMPv1 does not allow unsigned 32-bit integers and SNMPv3 prohibits them. The revise table addresses this issue and is also treated using trigger logic so that it can be used to activate a day plan (as originally envisioned) and/or to call other actions (e.g., creating a log entry).
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.2"
::= { timebase 2 }timeBaseScheduleTable · mandatory
timeBaseScheduleTable OBJECT-TYPE
SYNTAX SEQUENCE OF TimeBaseScheduleEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"<Definition>A table containing the time base schedule parameters
for the device. The number of rows in this table shall be equal
to the maxTimeBaseScheduleEntries object. The table references
the appropriate day plan for the device. The plan is determined
by comparing the current month (MONTH), day of week (DOW) and date
of month (DOM) to the appropriate fields. The settings for MONTH,
DOW and DOM are connected with a logical AND. In order to
determine which timebased event to select, determine the event
which has the most specific date specified. Select the more
specific event based on their MONTH settings; if the same, select
the most specific DOM; if that is still the same, select the most
specific DOW; if that’s still the same, the first occurrence
within the time base event table shall be selected. ’More
specific’ means the least number of bits set within an object.
All entries in Time Base Schedule Table are expressed in local
time and date. A row in the table may be deactivated by setting
the Month, Day, Date, or DayPlan parameters to zero (0)
<DescriptiveName>TimeBaseScheduleTable
<DataConceptType>Entity Type
<TableType> static"
::= { timebase 2 }