OID reference

pixelStatusEntry

1.3.6.1.4.1.1206.4.2.3.9.7.18.1

Description

<Definition> Parameters of the Pixel Status Table.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.3.9.7.18 (pixelStatusTable)
Node code: 1
Node name: pixelStatusEntry
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.3.9.7.18.1
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.3.9.7.18.1

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 1206 4 2 3 9 7 18 1}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) fontDefinition(3) dmsStatus(9) statError(7) pixelStatusTable(18) pixelStatusEntry(1)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/1206/4/2/3/9/7/18/1
/ISO/Identified-Organization/6/1/4/1/1206/4/2/3/9/7/18/1
/ISO/3/6/1/4/1/1206/4/2/3/9/7/18/1

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dms/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/fontDefinition/dmsStatus/statError/pixelStatusTable/pixelStatusEntry
Additional combinations skipped.

SNMP properties

Value type: PixelStatusEntry
Maximum access defined by MIB: not-accessible
Status in MIB: mandatory

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definitions

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

pixelStatusEntry · mandatory

pixelStatusEntry	OBJECT-TYPE
SYNTAX	PixelStatusEntry
ACCESS	not-accessible
STATUS	mandatory
DESCRIPTION "<Definition> Parameters of the Pixel Status Table.
"
INDEX { dmsPixelStatusIndex}
::= {pixelStatusTable 1}

pixelStatusEntry · mandatory

pixelStatusEntry OBJECT-TYPE
SYNTAX      PixelStatusEntry
ACCESS      not-accessible
STATUS      mandatory
DESCRIPTION "<Definition> Parameters of the Pixel Status Table.
"
INDEX { dmsPixelStatusIndex}
::= {pixelStatusTable 1}

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

<Definition> Parameters of the Pixel Status Table.

Sources for this description

ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)1 record · 3 sources

Description 1

pixelStatusEntry · mandatoryITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)3 sources

Status in source: mandatory.

Names: pixelStatusEntry

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pixelStatusEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "PixelStatusEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Parameters of the Pixel Status Table. \"",
    "INDEX",
    "{",
    "dmsPixelStatusIndex",
    "}",
    "::=",
    "{",
    "pixelStatusTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "PixelStatusEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Parameters of the Pixel Status Table."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "dmsPixelStatusIndex"
        ]
      ]
    ],
    null
  ]
}

ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP_1203 — v03/1203v03A-06g.mib
Module: NTCIP1203-v0305

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['OwnerString', 'dms']}
```
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 NTCIP8004v02, 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_1203 — v03/1203v03A-06g.mib
Related source files and packages:
- NTCIP 8004 v02 (2010) — normative namespace, pages 43–44
- RFC 1155 — original SMI enterprise namespace
NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1203 v03, Object Definitions for Dynamic Message Signs (DMS) Published September 2014 — original PDF · Official record
Module: NTCIP1203-v03-05

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'NTCIP8004': ['OwnerString', 'dms'], 'RFC1155-SMI': ['IpAddress', 'Counter'], '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: The PDF prints an invalid ASN.1 module label (NTCIP1203 v03.05). 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: 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 NTCIP1203v03f.pdf — NTCIP1203-v03-05 (MIB transcription)
Related source files and packages:
NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1203 v02, Object Definitins for Dynamic Message Signs (DMS) – Version 02 Published March 2007 (superceded by NTCIP 1203 v03) — original PDF · Official record
Module: NTCIP1203-2005

Same published definition
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['OwnerString', 'dms']}
```
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 NTCIP1203v02-35a.pdf — NTCIP1203-2005 (MIB transcription)
Related source files and packages:
- NTCIP 1203 v02, Object Definitins for Dynamic Message Signs (DMS) – Version 02 Published March 2007 (superceded by NTCIP 1203 v03) — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (3)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.3.9.7.18.1.1	dmsPixelStatusIndex	0	0
1.3.6.1.4.1.1206.4.2.3.9.7.18.1.2	dmsPixelStatus	0	0
1.3.6.1.4.1.1206.4.2.3.9.7.18.1.3	dmsPixelStatusV4	0	0