OID reference
1.3.6.1.4.1.1206.4.2.6.7.3.1.4
<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <DescriptiveName>AuxIOPort.resolution:quantity <DataConceptType>Data Element <Unit>bit
Identification
{1 3 6 1 4 1 1206 4 2 6 7 3 1 4}
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 NTCIP1201-2004, 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.4.2.6.7.3.1.4.<auxIOPortType>.<auxIOPortNumber>. Use values present on the device and permitted by its MIB. Other definitions can differ.
Published row index variants: auxIOPortType, auxIOPortNumber; auxIOv2PortType, auxIOv2PortNumber.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.6.7.3.1.4
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 5 distinct definitions; some records may not include a definition.
auxIOPortResolution OBJECT-TYPE
SYNTAX INTEGER (1..32)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent.
<DescriptiveName>AuxIOPort.resolution:quantity
<DataConceptType>Data Element
<Unit>bit"
::= {auxIOEntry 4}auxIOPortResolution OBJECT-TYPE
SYNTAX INTEGER (1..32)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>Defines number of bits used for the IO-port (e.g.
width of digital, resolution of analog). Thus, this feature allows
the digital monitoring (via NTCIP) of an analog port on the agent.
<DescriptiveName>AuxIOPort.resolution:quantity
<DataConceptType>Data Element
<Unit>bit"
::= {auxIOEntry 4}auxIOv2PortResolution OBJECT-TYPE
SYNTAX INTEGER (1..255)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>Defines number of bits used for the IO-port (e.g.
width of digital, resolution of analog). Thus, this feature
allows the digital monitoring (via NTCIP) of an analog port on
the agent.
<Informative> In NTCIP 1203 v01, ACCESS was listed as read-write;
however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed
because resolution is fixed by the hardware implementation and cannot
be changed by the management station.
The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is
now as it was originally under the experimental node defined in
NTCIP 1203v01. This changed to address backward compatibility and the
‘aliasing’ between the version 1 objects (see Section 2.10) and the
Version 02 objects.
<Unit>bit
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4"
::= {auxIOv2Entry 4}auxIOv2PortResolution OBJECT-TYPE
SYNTAX Integer32 (1..255)
UNITS "bits"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition>Defines number of bits used for the IO-port (e.g.
width of digital, resolution of analog). Thus, this feature
allows the digital monitoring (via NTCIP) of an analog port on
the agent.
<Informative> In NTCIP 1203 v01, ACCESS was listed as read-write;
however, in NTCIP 1201 v03, ACCESS changed to read-only . This
changed because resolution is fixed by the hardware implementation and
cannot be changed by the management station.
The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is
now as it was originally under the experimental node defined in
NTCIP 1203v01. This changed to address backward compatibility and the
'aliasing' between the version 1 objects (see Section 2.10) and the
Version 02 objects.
<Superseded by> FIELD-DEVICE-GPIO-MIB.fdGPIOPortMinValue &
FIELD-DEVICE-GPIO-MIB.fdGPIOPortMaxValue (ISO 20684-2)
<Informative> The GPIO table indicates the range over which
values can be considered reliable.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4"
::= {auxIOv2Entry 4}auxIOv2PortResolution OBJECT-TYPE
SYNTAX Integer32 (1..255)
UNITS "bits"
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition>Defines number of bits used for the IO-port (e.g. width of
digital, resolution of analog). Thus, this feature allows the digital
monitoring (via NTCIP) of an analog port on the agent.
<Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however,
in NTCIP 1201 v03, ACCESS changed to read-only . This changed because
resolution is fixed by the hardware implementation and cannot be changed by
the management station.
The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as
it was originally under the experimental node defined in NTCIP 1203v01.
This changed to address backward compatibility and the 'aliasing' between
the version 1 objects (see Section 2.10) and the Version 02 objects.
<Supplanted by> ISO26048-1-Srsa.fdSrsaPortMinValue & ISO26048-1-
Srsa.fdSrsaPortMaxValue (ISO 26048-1)
<Informative> The GPIO table indicates the range over which values can be
considered reliable.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4"
::= { auxIOv2Entry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <DescriptiveName>AuxIOPort.resolution:quantity <DataConceptType>Data Element <Unit>bit
ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the ‘aliasing’ between the version 1 objects (see Section 2.10) and the Version 02 objects. <Unit>bit <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4
NTCIP published standard MIB annexes (reviewed modules)
Description 3
<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the 'aliasing' between the version 1 objects (see Section 2.10) and the Version 02 objects. <Superseded by> FIELD-DEVICE-GPIO-MIB.fdGPIOPortMinValue & FIELD-DEVICE-GPIO-MIB.fdGPIOPortMaxValue (ISO 20684-2) <Informative> The GPIO table indicates the range over which values can be considered reliable. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4
Description 4
<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the 'aliasing' between the version 1 objects (see Section 2.10) and the Version 02 objects. <Supplanted by> ISO26048-1-Srsa.fdSrsaPortMinValue & ISO26048-1- Srsa.fdSrsaPortMaxValue (ISO 26048-1) <Informative> The GPIO table indicates the range over which values can be considered reliable. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4
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: auxIOPortResolution
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"auxIOPortResolution",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"1",
".",
".",
"32",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <DescriptiveName>AuxIOPort.resolution:quantity <DataConceptType>Data Element <Unit>bit\"",
"::=",
"{",
"auxIOEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
1,
32
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <DescriptiveName>AuxIOPort.resolution:quantity <DataConceptType>Data Element <Unit>bit"
],
null,
null,
null,
null
]
}Module: NTCIP1201-2004
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['devices', 'protocols', 'profiles', 'global']}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.
Source data warning: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004-A-2004, which is absent from the public repository snapshot. 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-1201 — NTCIP1201-Glo.mibRelated source files and packages:
Module: NTCIP1201-2004
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['devices', 'protocols', 'profiles', 'global']}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-A-2004. 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 NTCIP1201v0232f.pdf — NTCIP1201-2004 (MIB transcription)Status in source: mandatory.
Names: auxIOv2PortResolution
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"auxIOv2PortResolution",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"1",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the ‘aliasing’ between the version 1 objects (see Section 2.10) and the Version 02 objects. <Unit>bit <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4\"",
"::=",
"{",
"auxIOv2Entry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
1,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the ‘aliasing’ between the version 1 objects (see Section 2.10) and the Version 02 objects. <Unit>bit <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4"
],
null,
null,
null,
null
]
}Module: AuxIOv2-1201
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'NTCIP8004': ['global'], '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.
· Download NTCIP1201v0315r.pdf — AuxIOv2-1201 (MIB transcription)Related source files and packages:
Status in source: deprecated.
Names: auxIOv2PortResolution
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"auxIOv2PortResolution",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"1",
".",
".",
"255",
")",
"UNITS",
[
"literal",
"226269747322"
],
"MAX-ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the 'aliasing' between the version 1 objects (see Section 2.10) and the Version 02 objects. <Superseded by> FIELD-DEVICE-GPIO-MIB.fdGPIOPortMinValue & FIELD-DEVICE-GPIO-MIB.fdGPIOPortMaxValue (ISO 20684-2) <Informative> The GPIO table indicates the range over which values can be considered reliable. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4\"",
"::=",
"{",
"auxIOv2Entry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
1,
255
]
]
]
],
[
"UNITS",
"bits"
],
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the 'aliasing' between the version 1 objects (see Section 2.10) and the Version 02 objects. <Superseded by> FIELD-DEVICE-GPIO-MIB.fdGPIOPortMinValue & FIELD-DEVICE-GPIO-MIB.fdGPIOPortMaxValue (ISO 20684-2) <Informative> The GPIO table indicates the range over which values can be considered reliable. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4"
],
null,
null,
null,
null
]
}Module: NTCIP1201-AuxIOv2
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'NTCIP1201-Global': ['global']}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.mibSame file in ntcip1201-SNMPConfig.mib.
Same file in ntcip1201-Security.mib.
Same file in ntcip1201-ProfilesSTMP.mib.
Same file in ntcip1201-NtcipTraps.mib.
Status in source: deprecated.
Names: auxIOv2PortResolution
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"auxIOv2PortResolution",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"1",
".",
".",
"255",
")",
"UNITS",
[
"literal",
"226269747322"
],
"MAX-ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the 'aliasing' between the version 1 objects (see Section 2.10) and the Version 02 objects. <Supplanted by> ISO26048-1-Srsa.fdSrsaPortMinValue & ISO26048-1- Srsa.fdSrsaPortMaxValue (ISO 26048-1) <Informative> The GPIO table indicates the range over which values can be considered reliable. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4\"",
"::=",
"{",
"auxIOv2Entry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
1,
255
]
]
]
],
[
"UNITS",
"bits"
],
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition>Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. <Informative> In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the 'aliasing' between the version 1 objects (see Section 2.10) and the Version 02 objects. <Supplanted by> ISO26048-1-Srsa.fdSrsaPortMinValue & ISO26048-1- Srsa.fdSrsaPortMaxValue (ISO 26048-1) <Informative> The GPIO table indicates the range over which values can be considered reliable. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.7.3.1.4"
],
null,
null,
null,
null
]
}Module: NTCIP1201-AuxIOv2
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32'], 'NTCIP1201-Global': ['global']}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.
· Download 1201v4-0-0.pdf — NTCIP1201-AuxIOv2 (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.6.7.3.1.1 | auxIOPortType, auxIOv2PortType | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.7.3.1.2 | auxIOPortNumber, auxIOv2PortNumber | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.7.3.1.3 | auxIOPortDescription, auxIOv2PortDescription | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.7.3.1.5 | auxIOPortValue, auxIOv2PortValue | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.7.3.1.6 | auxIOPortDirection, auxIOv2PortDirection | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.7.3.1.7 | auxIOPortLastCommandedState, auxIOv2PortLastCommandedState | 0 | 0 |