OID reference
1.3.6.1.4.1.1206.4.2.1.7.3.1.3
Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the devices compatibility group.
Identification
{1 3 6 1 4 1 1206 4 2 1 7 3 1 3}
Definitions may combine these properties differently.
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 NTCIP1202-v03, the row index consists of these components in order:
sequenceNumber (INTEGER): one numeric subidentifier for the non-negative value.sequenceRingNumber (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.1206.4.2.1.7.3.1.3.<sequenceNumber>.<sequenceRingNumber>. Use values 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.1.7.3.1.3
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 4 distinct definitions; some records may not include a definition.
sequenceData OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Each octet is a Phase Number (binary value) within the associated ring number. The phase
number value shall not exceed the maxPhases object value. The order of phase numbers
determines the phase sequence for the ring. The phase numbers shall not be ordered in a
manner that would violate the devices compatibility group."
::= { sequenceEntry 3 }sequenceData OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS optional
DESCRIPTION
"<Definition> Each octet is a Phase Number (binary
value) within the associated ring number. The phase
number value shall not exceed the maxPhases object
value. The order of phase numbers determines the
phase sequence for the ring. The phase numbers
shall not be ordered in a manner that would violate
the Consistency Checks defined in Annex B.
<DescriptiveName> NTCIP-1202::ASC.sequenceData
<DataConceptType> Data Element"
::= { sequenceEntry 3 }sequenceData OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> Each octet is a Phase Number (binary value)
within the associated ring number. The phase number value shall
not exceed the maxPhases object value. The order of phase numbers
determines the phase sequence for the ring. The phase numbers
shall not be ordered in a manner that would violate the
Consistency Checks defined in Section 4.3.2.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3
<Object Type> P2"
::= { sequenceEntry 3 }sequenceData OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> Each octet is a Phase Number (binary value)
within the associated ring number. The phase number value shall
not exceed the maxPhases object value. The order of phase numbers
determines the phase sequence for the ring. The phase numbers
shall not be ordered in a manner that would violate the
Consistency Checks defined in Section 4.3.2.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3"
::= { sequenceEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the devices compatibility group.
NTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Annex B. <DescriptiveName> NTCIP-1202::ASC.sequenceData <DataConceptType> Data Element
NTCIP published standard MIB annexes (reviewed modules)
Description 3
<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Section 4.3.2. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3 <Object Type> P2
NTCIP published standard MIB annexes (reviewed modules)
Description 4
<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Section 4.3.2. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3
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: sequenceData
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sequenceData",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the devices compatibility group.\"",
"::=",
"{",
"sequenceEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the devices compatibility group."
],
null,
null,
null,
null
]
}Module: ASC_MIB1
See published definition above
{'TMIB': ['devices']}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: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB. 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 NTCIP1202v0107d.pdf — ASC_MIB1 (MIB transcription)Related source files and packages:
Status in source: optional.
Names: sequenceData
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sequenceData",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"read-write",
"STATUS",
"optional",
"DESCRIPTION",
"\"<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Annex B. <DescriptiveName> NTCIP-1202::ASC.sequenceData <DataConceptType> Data Element\"",
"::=",
"{",
"sequenceEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Annex B. <DescriptiveName> NTCIP-1202::ASC.sequenceData <DataConceptType> Data Element"
],
null,
null,
null,
null
]
}Module: NTCIP1202-200x
See published definition above
{'TMIB-II': ['OwnerString', 'devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}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 NTCIP1202v0219f.pdf — NTCIP1202-200x (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: sequenceData
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sequenceData",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Section 4.3.2. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3 <Object Type> P2\"",
"::=",
"{",
"sequenceEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Section 4.3.2. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3 <Object Type> P2"
],
null,
null,
null,
null
]
}Module: NTCIP1202-v03
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}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: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. 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 NTCIP-1202v03.35e-aspublished.pdf — NTCIP1202-v03 (MIB transcription)Status in source: mandatory.
Names: sequenceData
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sequenceData",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Section 4.3.2. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3\"",
"::=",
"{",
"sequenceEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Each octet is a Phase Number (binary value) within the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The phase numbers shall not be ordered in a manner that would violate the Consistency Checks defined in Section 4.3.2. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3.1.3"
],
null,
null,
null,
null
]
}Module: NTCIP1202-v03
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}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: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. 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 NTCIP-1202v0328A.pdf — NTCIP1202-v03 (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.1.7.3.1.1 | sequenceNumber | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.7.3.1.2 | sequenceRingNumber | 0 | 0 |