OID reference
1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26
Indicates the length of the yellow interval. This value shall be expressed in 0.1-second increments (i.e, 40 = 4.0 seconds). A suggested usable range is 0 and 5 to 50. A value of zero (0) shall cause the metered lane to bypass this interval. <Unit> tenth of second <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26
Identification
{1 3 6 1 4 1 1206 4 2 2 3 1 3 1 26}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In N207v0214-MIB, the row index rmcMeterNumber is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26.<rmcMeterNumber>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Available source records contain 2 distinct definitions; some records may not include a definition.
rmcYellow OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Indicates the length of the yellow interval.
This value shall be expressed in 0.1-second increments (i.e,
40 = 4.0 seconds).
A suggested usable range is 0 and 5 to 50.
A value of zero (0) shall cause the metered lane to bypass this interval.
<Unit> tenth of second
<Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26"
REFERENCE
"See Clause A.8.3.2.1, A.3.3, A.8.5.1.1 and A.8.5.2"
::={ rmcMeterCfgEntry 26 }rmcYellow OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Indicates the length of the yellow interval.
A suggested usable range is 0, 0.5 to 5.0 in 0.1-second increments.
A value of zero (0) indicates that the yellow interval shall be skipped."
REFERENCE
"See Clause A.8.3.2.1, A.3.3, A.85.1.1 and A.8.5.2"
::={ rmcMeterCfgEntry 26 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Indicates the length of the yellow interval. This value shall be expressed in 0.1-second increments (i.e, 40 = 4.0 seconds). A suggested usable range is 0 and 5 to 50. A value of zero (0) shall cause the metered lane to bypass this interval. <Unit> tenth of second <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26
NTCIP published standard MIB annexes (reviewed modules)
Description 2
Indicates the length of the yellow interval. A suggested usable range is 0, 0.5 to 5.0 in 0.1-second increments. A value of zero (0) indicates that the yellow interval shall be skipped.
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: rmcYellow
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcYellow",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Indicates the length of the yellow interval. This value shall be expressed in 0.1-second increments (i.e, 40 = 4.0 seconds). A suggested usable range is 0 and 5 to 50. A value of zero (0) shall cause the metered lane to bypass this interval. <Unit> tenth of second <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26\"",
"REFERENCE",
"\"See Clause A.8.3.2.1, A.3.3, A.8.5.1.1 and A.8.5.2\"",
"::=",
"{",
"rmcMeterCfgEntry",
"26",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates the length of the yellow interval. This value shall be expressed in 0.1-second increments (i.e, 40 = 4.0 seconds). A suggested usable range is 0 and 5 to 50. A value of zero (0) shall cause the metered lane to bypass this interval. <Unit> tenth of second <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.3.1.3.1.26"
],
[
"REFERENCE",
"See Clause A.8.3.2.1, A.3.3, A.8.5.1.1 and A.8.5.2"
],
null,
null,
null
]
}Module: N207v0214-MIB
See published definition above
{'NTCIP': ['ramp'], 'RFC-1212': ['OBJECT-TYPE']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: The PDF prints an invalid ASN.1 module label (1207v0214-MIB). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1207v0214hj.pdf — N207v0214-MIB (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: rmcYellow
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcYellow",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Indicates the length of the yellow interval. A suggested usable range is 0, 0.5 to 5.0 in 0.1-second increments. A value of zero (0) indicates that the yellow interval shall be skipped.\"",
"REFERENCE",
"\"See Clause A.8.3.2.1, A.3.3, A.85.1.1 and A.8.5.2\"",
"::=",
"{",
"rmcMeterCfgEntry",
"26",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates the length of the yellow interval. A suggested usable range is 0, 0.5 to 5.0 in 0.1-second increments. A value of zero (0) indicates that the yellow interval shall be skipped."
],
[
"REFERENCE",
"See Clause A.8.3.2.1, A.3.3, A.85.1.1 and A.8.5.2"
],
null,
null,
null
]
}Module: RMC-MIB1
See published definition above
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE']}Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download 1207v0117.pdf — RMC-MIB1 (MIB transcription)Related source files and packages:
Registration