OID reference

eventLogNumber

1.3.6.1.4.1.1206.4.2.6.4.4.1.2

Description

<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class o…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.6.4.4.1 (eventLogEntry)
Node code
2
Node name
eventLogNumber
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.4.4.1.2
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.4.4.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 6 4 4 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) eventLogTable(4) eventLogEntry(1) eventLogNumber(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) defaultFlashOff(4) eventLogEntry(1) eventLogNumber(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/6/4/4/1/2
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/4/4/1/2
  • /ISO/3/6/1/4/1/1206/4/2/6/4/4/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalReport/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalReport/defaultFlashOff/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/multiCfg/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/multiCfg/defaultFlashOff/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalReport/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalReport/defaultFlashOff/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/multiCfg/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/multiCfg/defaultFlashOff/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalReport/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalReport/defaultFlashOff/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/multiCfg/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/multiCfg/defaultFlashOff/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalReport/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalReport/defaultFlashOff/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/multiCfg/eventLogTable/eventLogEntry/eventLogNumber
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/multiCfg/defaultFlashOff/eventLogEntry/eventLogNumber
  • Additional combinations skipped.

SNMP properties

Value type
Integer32, INTEGER
Maximum access defined by MIB
read-only
Status in MIB
deprecated, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)

Value type
Integer32
Maximum access defined by MIB
read-only
Status in MIB
deprecated
Allowed ranges
1–255

Variant 2 — ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
mandatory
Allowed ranges
1–255

Using this OID with SNMP

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:

  1. eventLogClass (INTEGER): one numeric subidentifier for the non-negative value.
  2. eventLogNumber (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.1206.4.2.6.4.4.1.2.<eventLogClass>.<eventLogNumber>. 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.6.4.4.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 8 distinct definitions; some records may not include a definition.

Show 8 published definitions

eventLogNumber · deprecated

eventLogNumber  OBJECT-TYPE
  SYNTAX  Integer32 (1..255)
  MAX-ACCESS  read-only
  STATUS      deprecated
  DESCRIPTION
    "<Definition>The event number within this class for this 
      event. Event numbers shall be assigned starting at 1 and 
      shall increase to the value specified by the associated 
      eventClassLimit for the class associated with the rows. 
      Events shall maintain a chronological ordering in the table 
      with the oldest event of a class occupying the row with 
      eventNumber = 1, and subsequent events filling subsequent 
      rows. This ordering shall be maintained for those rows 
      still remaining when events are cleared. 
    <Superseded by> LOG-MIB.fdLogIndex (ISO 20684-5)
    <Informative> The replacement object is an Unsigned32
    <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2"
::= { eventLogEntry 2 }

eventLogNumber · deprecated

eventLogNumber OBJECT-TYPE
SYNTAX       Integer32 (1..255)
MAX-ACCESS read-only
STATUS       deprecated
DESCRIPTION
   "<Definition>The event number within this class for this event. Event
   numbers shall be assigned starting at 1 and shall increase to the value
   specified by the associated eventClassLimit for the class associated with
   the rows. Events shall maintain a chronological ordering in the table with
   the oldest event of a class occupying the row with eventNumber = 1, and
   subsequent events filling subsequent rows. This ordering shall be
   maintained for those rows still remaining when events are cleared.
  <Supplanted by> ISO26048-1-Log.fdLogIndex (ISO 26048-1)
  <Informative> The replacement object is an Unsigned32
  <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2"
::= { eventLogEntry 2 }

eventLogNumber · mandatory

eventLogNumber OBJECT-TYPE
SYNTAX	INTEGER (1..255)
ACCESS	read-only
STATUS	mandatory
DESCRIPTION
"<Definition>The event number within this class for this event.  Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows.  Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. 
<DescriptiveName>Event.number:identifier
<DataConceptType>Data Element"
::= { eventLogEntry 2 }

eventLogNumber · mandatory

eventLogNumber OBJECT-TYPE
SYNTAX           INTEGER (1..255)
ACCESS           read-only
STATUS           mandatory
DESCRIPTION
         "<Definition>The event number within this class for this event. Event numbers shall be
         assigned starting at 1 and shall increase to the value specified by the associated
         eventClassLimit for the class associated with the rows. Events shall maintain a
         chronological ordering in the table with the oldest event of a class occupying the row with
         eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be
         maintained for those rows still remaining when events are cleared.
         <DescriptiveName>Event.number:identifier
         <DataConceptType>Data Element"
::= { eventLogEntry 2 }

eventLogNumber · mandatory

eventLogNumber OBJECT-TYPE
SYNTAX        INTEGER (1..255)
ACCESS        read-only
STATUS        mandatory
DESCRIPTION
       "<Definition>The event number within this class for this event.
       Event numbers shall be assigned starting at 1 and shall increase
       to the value specified by the associated eventClassLimit for the
       class associated with the rows. Events shall maintain a
       chronological ordering in the table with the oldest event of a
       class occupying the row with eventNumber = 1, and subsequent
       events filling subsequent rows. This ordering shall be maintained
       for those rows still remaining when events are cleared.
       <DescriptiveName>Event.number:identifier
      <DataConceptType>Data Element"
::= { eventLogEntry 2 }

eventLogNumber · mandatory

eventLogNumber OBJECT-TYPE
SYNTAX           INTEGER (1..255)
ACCESS           read-only
STATUS           mandatory
DESCRIPTION
"The event number within this class for this event. Event numbers shall be assigned starting at 1 and
shall increase to the value specified by the associated eventClassLimit for the class associated with the
rows. Events shall maintain a chronological ordering in the table with the oldest event of a class


© 2001 NEMA                                                                  Copy per MIB Distribution Notice

                      
         



occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering
shall be maintained when events are cleared."
::= { eventLogEntry 2 }

eventLogNumber · mandatory

eventLogNumber OBJECT-TYPE
   SYNTAX INTEGER (1..255)
   ACCESS read-only
   STATUS mandatory
   DESCRIPTION
      "<Definition>The event number within this class for this
        event. Event numbers shall be assigned starting at 1 and
        shall increase to the value specified by the associated
        eventClassLimit for the class associated with the rows.
        Events shall maintain a chronological ordering in the table
        with the oldest event of a class occupying the row with
        eventNumber = 1, and subsequent events filling subsequent


                                                                                     

                                                                                     
                                                                                    

         rows. This ordering shall be maintained for those rows
         still remaining when events are cleared.
        <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2
      "
::= { eventLogEntry 2 }

eventLogNumber · mandatory

eventLogNumber OBJECT-TYPE
    SYNTAX INTEGER (1..255)
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "<Definition>The event number within this class for this
          event. Event numbers shall be assigned starting at 1 and
          shall increase to the value specified by the associated
          eventClassLimit for the class associated with the rows.
          Events shall maintain a chronological ordering in the table
          with the oldest event of a class occupying the row with
          eventNumber = 1, and subsequent events filling subsequent
          rows. This ordering shall be maintained for those rows
          still remaining when events are cleared.
         <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2
        "
::= { eventLogEntry 2 }

Meaning

Descriptions

5 unique

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

Description 1

<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Superseded by> LOG-MIB.fdLogIndex (ISO 20684-5) <Informative> The replacement object is an Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 2

<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Supplanted by> ISO26048-1-Log.fdLogIndex (ISO 26048-1) <Informative> The replacement object is an Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <DescriptiveName>Event.number:identifier <DataConceptType>Data Element

Sources for this description

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

See 1 matching source record

Description 4

The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class © 2001 NEMA Copy per MIB Distribution Notice occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained when events are cleared.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 5

<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

5 records

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

Records for description 1ITE public NTCIP working repository MIBs1 record · 1 source

Description 1

eventLogNumber · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: eventLogNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Superseded by> LOG-MIB.fdLogIndex (ISO 20684-5) <Informative> The replacement object is an Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2\"",
    "::=",
    "{",
    "eventLogEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Superseded by> LOG-MIB.fdLogIndex (ISO 20684-5) <Informative> The replacement object is an Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

eventLogNumber · deprecatedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: deprecated.

Names: eventLogNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Supplanted by> ISO26048-1-Log.fdLogIndex (ISO 26048-1) <Informative> The replacement object is an Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2\"",
    "::=",
    "{",
    "eventLogEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Supplanted by> ISO26048-1-Log.fdLogIndex (ISO 26048-1) <Informative> The replacement object is an Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 3ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)1 record · 3 sources

Description 3

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

Status in source: mandatory.

Names: eventLogNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <DescriptiveName>Event.number:identifier <DataConceptType>Data Element\"",
    "::=",
    "{",
    "eventLogEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <DescriptiveName>Event.number:identifier <DataConceptType>Data Element"
    ],
    null,
    null,
    null,
    null
  ]
}
  • ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1201 — NTCIP1201-Glo.mib

    Module: NTCIP1201-2004

    See published definition above

    Module imports
    {'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.mib
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1103 v01, Transportation Management Protocols Published January 2009 (superceded by NTCIP 1103 v02) — original PDF · Official record

    Module: NTCIP1103v0127

    See published definition above

    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Gauge', 'Counter', 'NetworkAddress', 'Opaque', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['OwnerString', 'RowStatusStatic', 'dynObjMgmt', 'profiles', 'application', 'global', 'OerString']}

    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 NTCIP1103v0127r-1.pdf — NTCIP1103v0127 (MIB transcription)
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201:2005, Global Object Definitions – version 02 Published October 2005 (superceded by NTCIP 1201 v03) — original PDF · Official record

    Module: NTCIP1201-2004

    See published definition above

    Module imports
    {'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)
Records for description 4NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 4

eventLogNumber · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: eventLogNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class © 2001 NEMA Copy per MIB Distribution Notice occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained when events are cleared.\"",
    "::=",
    "{",
    "eventLogEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class © 2001 NEMA Copy per MIB Distribution Notice occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained when events are cleared."
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201:1996, Global Object Definitions Published December 2001 (superceded by NTCIP 1201 v02) — original PDF · Official record

    Module: GLOBAL

    See published definition above

    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: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

    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: The GLOBAL moduleMake/moduleVersion assignment closes its explicitly opened brace with a parenthesis. Normalize only that delimiter in the derived parsing copy; retain the original definition and unchanged numeric expression.

    Source data warning: The historical GLOBAL security grouping explicitly prints the parent global and suffix 5 but omits assignment braces. Reuse two adjacent whitespace bytes for those braces in the parsing copy; retain the original expression and qualify this syntactic interpretation. No numeric arc is invented or replaced.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogConfigTable, while its native table or entry declaration uses eventLogConfigTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogEntry, while its native table or entry declaration uses eventLogEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names globalmoduleTable, while its native table or entry declaration uses globalModuleTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names moduleTableEntry, while its native table or entry declaration uses moduleEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of devices, profiles. 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 NTCIP1201v0110b.pdf — GLOBAL (MIB transcription)
Records for description 5NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 5

eventLogNumber · mandatoryNTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: mandatory.

Names: eventLogNumber

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "eventLogNumber",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2 \"",
    "::=",
    "{",
    "eventLogEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.4.4.1.2"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.4.4.1.1 eventLogClass00
1.3.6.1.4.1.1206.4.2.6.4.4.1.3 eventLogID00
1.3.6.1.4.1.1206.4.2.6.4.4.1.4 eventLogTime00
1.3.6.1.4.1.1206.4.2.6.4.4.1.5 eventLogValue00
1.3.6.1.4.1.1206.4.2.6.4.4.1.6 eventLogTimeMilliseconds00