Status in source: deprecated.
Names: dstBeginSecondsToTransition
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dstBeginSecondsToTransition",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"UNITS",
[
"literal",
"227365636f6e647322"
],
"MAX-ACCESS",
"read-write",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition> If dstBeginMonth = absolute, then this object defines when DST begins based on the seconds from midnight January 1, 1970 (UTC/GMT). If dstBeginMonth = 1-12 (January to December), then this object defines the time when DST begins in seconds past midnight relative to local time (see the controllerLocalTime object). NOTE: a set of parameters that causes a day transition that crosses the midnight boundary may result in unexpected behavior. <Superseded by> CLOCK-MIB.fdClockDstBeginTime (ISO 20684-7) <Informative> The original specification defined this parameter using INTEGER (0..4294967295); however, by convention, INTEGERs are limited to the range (-2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. The replacement object is a daily timestamp to the millisecond and does not support an absolute time. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.6\"",
"DEFVAL",
"{",
"7200",
"}",
"::=",
"{",
"dstEntry",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
[
"UNITS",
"seconds"
],
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition> If dstBeginMonth = absolute, then this object defines when DST begins based on the seconds from midnight January 1, 1970 (UTC/GMT). If dstBeginMonth = 1-12 (January to December), then this object defines the time when DST begins in seconds past midnight relative to local time (see the controllerLocalTime object). NOTE: a set of parameters that causes a day transition that crosses the midnight boundary may result in unexpected behavior. <Superseded by> CLOCK-MIB.fdClockDstBeginTime (ISO 20684-7) <Informative> The original specification defined this parameter using INTEGER (0..4294967295); however, by convention, INTEGERs are limited to the range (-2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. The replacement object is a daily timestamp to the millisecond and does not support an absolute time. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.6"
],
null,
null,
null,
[
"DEFVAL",
7200
]
]
}
- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1201 — ntcip1201-AuxIO.mib
Module: NTCIP1201-GlobalV1
See published definition above
Module imports
{'SNMPv2-TC': ['AutonomousType', 'VariablePointer'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Unsigned32', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'NTCIP1201-Global': ['global'], 'NTCIP8004-Transportation': ['profiles']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
· Download NTCIP-1201 — ntcip1201-AuxIO.mib
Same file in ntcip1201-SNMPConfig.mib.
Same file in ntcip1201-Security.mib.
Same file in ntcip1201-ProfilesSTMP.mib.
Same file in ntcip1201-NtcipTraps.mib.