OID reference
1.3.6.1.4.1.1206.2.1.1.3.1.2
Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port.
Identification
{1 3 6 1 4 1 1206 2 1 1 3 1 2}
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 AuxIOv1-1203, the row index consists of these components in order:
auxIOPortType (INTEGER): one numeric subidentifier for the non-negative value.auxIOPortNumber (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.1206.2.1.1.3.1.2.<auxIOPortType>.<auxIOPortNumber>. 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.2.1.1.3.1.2
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.
auxIOPortNumber OBJECT-TYPE
SYNTAX INTEGER (1..255)
ACCESS read-only
STATUS mandatory
DESCRIPTION “Indicates the port number for the associated port type. Port numbers are used
sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for
digital port.”
::= {auxIOEntry 2}auxIOPortNumber OBJECT-TYPE
SYNTAX INTEGER (1..255)
ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition> Indicates the port number for the associated port type.
Port numbers are used sequentially from one to max for each port
type. There can be a port 1 for analog port and port 1 for digital
port.
<Object Identifier> 1.3.6.1.4.1.1206.2.1.1.3.1.2"
::= {auxIOEntry 2}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port.
NTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition> Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port. <Object Identifier> 1.3.6.1.4.1.1206.2.1.1.3.1.2
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: unconfirmed.
Names: auxIOPortNumber
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"auxIOPortNumber",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"1",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"“",
"Indicates",
"the",
"port",
"number",
"for",
"the",
"associated",
"port",
"type",
".",
"Port",
"numbers",
"are",
"used",
"sequentially",
"from",
"one",
"to",
"max",
"for",
"each",
"port",
"type",
".",
"There",
"can",
"be",
"a",
"port",
"1",
"for",
"analog",
"port",
"and",
"port",
"1",
"for",
"digital",
"port",
".",
"”",
"::=",
"{",
"auxIOEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
1,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port."
],
null,
null,
null,
null
]
}Module: DMS-MIB
See published definition above
{'TMIB': ['OwnerString', 'devices'], 'NEMA_SMI': ['experimental'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString']}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: A typographic opening 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: 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.
Source data warning: Unconfirmed interpretation of a historical NTCIP import: NTCIP 1203:1997 imports experimental from NEMA_SMI, but the retained original NEMA_SMI defines nemaExperimental instead. Section 2.10 explicitly locates these auxiliary I/O objects under the nema-experimental node. Here only that imported spelling is interpreted as the explicitly assigned nemaExperimental value. The original exp-global suffix 1 and all child numbers are retained. The later NTCIP 1201 v03 compatibility discussion also compares the old experimental spelling with nemaExperimental, but prints expGlobal suffix 2; that disagreement is not silently corrected or treated as proof that both historical branches are registered. These entries may be inaccurate; verify the linked original editions and your device. Native SMI STATUS is preserved separately.
nema OBJECT IDENTIFIER ::= { enterprises 1206 }nemaExperimental OBJECT IDENTIFIER ::= { nema 2 }
Related source files and packages:
Status in source: unconfirmed.
Names: auxIOPortNumber
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"auxIOPortNumber",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"1",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition> Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port. <Object Identifier> 1.3.6.1.4.1.1206.2.1.1.3.1.2\"",
"::=",
"{",
"auxIOEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
1,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition> Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port. <Object Identifier> 1.3.6.1.4.1.1206.2.1.1.3.1.2"
],
null,
null,
null,
null
]
}Module: AuxIOv1-1203
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'NTCIP8004': ['nemaExperimental'], 'RFC1213-MIB': ['DisplayString']}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: NTCIP8004. 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.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.2.2.1.3.1.2, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.2.1.1.3.1.2. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP1201v0315r.pdf — AuxIOv1-1203 (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.2.1.1.3.1.1 | auxIOPortType | 0 | 0 | |
| 1.3.6.1.4.1.1206.2.1.1.3.1.3 | auxIODescription | 0 | 0 | |
| 1.3.6.1.4.1.1206.2.1.1.3.1.4 | auxIOResolution | 0 | 0 | |
| 1.3.6.1.4.1.1206.2.1.1.3.1.5 | auxIOValue | 0 | 0 | |
| 1.3.6.1.4.1.1206.2.1.1.3.1.6 | auxIOPortDirection | 0 | 0 |