OID reference

globalSetIDParameter

1.3.6.1.4.1.1206.4.2.6.1.1

Description

<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.6.1 (globalConfiguration, dmsSignCfg)
Node code
1
Node names
  • globalSetIDParameter
  • dmsSignAccess
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.1.1
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) dmsSignAccess(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) dmsSignAccess(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) dmsSignAccess(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) dmsSignAccess(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) dmsSignAccess(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) dmsSignAccess(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) dmsSignAccess(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) globalSetIDParameter(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) dmsSignAccess(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/6/1/1
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/1/1
  • /ISO/3/6/1/4/1/1206/4/2/6/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalConfiguration/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalConfiguration/dmsSignAccess
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/dmsSignCfg/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/dmsSignCfg/dmsSignAccess
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalConfiguration/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalConfiguration/dmsSignAccess
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/dmsSignCfg/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/dmsSignCfg/dmsSignAccess
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalConfiguration/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalConfiguration/dmsSignAccess
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/dmsSignCfg/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/dmsSignCfg/dmsSignAccess
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalConfiguration/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalConfiguration/dmsSignAccess
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/dmsSignCfg/globalSetIDParameter
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/dmsSignCfg/dmsSignAccess
  • Additional combinations skipped.

SNMP properties

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

Definitions may combine these properties differently.

Compare 4 source variants

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

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

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

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

Variant 3 — NTCIP published standard MIB annexes (reviewed modules)

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
optional
Allowed ranges
0–65535

Variant 4 — ITE public NTCIP working repository MIBs

Value type
NtcipIntegerBitmap8
Maximum access defined by MIB
read-only
Status in MIB
current

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 7 distinct definitions; some records may not include a definition.

Show 7 published definitions

globalSetIDParameter · unconfirmed

globalSetIDParameter OBJECT-TYPE
SYNTAX      Integer32 (0..65535)
MAX-ACCESS read-only
STATUS      deprecated
DESCRIPTION
   "<Definition> Specifies a relatively unique ID (e.g., this could be a
   counter, a check-sum, etc.) for all user-changeable parameters of the
   particular device-type currently implemented in the device. Often this ID
   is calculated using a CRC algorithm. This value shall be calculated when a
   change of any parameter object has occurred. The value reported by this
   object shall not change unless there has been a change in the static data
   since the last request. If the actual objects, which are to be included to
   create this object value, are not defined in the actual device-level
   standard such as 1202 or 1203, then the general guidance is to include all
   configuration objects that are stored in a type of memory that survives
   power outages. A management station can use this object to detect any
   change in the parameter objects by monitoring this value after it has
   established a baseline.
  <Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 26048-1)
  <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1"
::= { globalConfiguration 1 }

globalSetIDParameter · mandatory

globalSetIDParameter OBJECT-TYPE
    SYNTAX   INTEGER (0..65535)
    ACCESS   read-only
    STATUS   mandatory
    DESCRIPTION
         "<Definition>Specifies a relatively unique ID (e.g., this could be
         a counter, a check-sum, etc.) for current values stored in all
         user-changeable static database objects of the particular device-
         type currently implemented in the device. This value shall be
         calculated on the change of any static database object. The value
         reported by this object shall not change unless there has been a
         change in the static data since the last request; however a genErr
         shall be returned if the unique ID value has not yet been updated.
         A management station will be able to detect any change in the
         static database objects by monitoring this value after it has
         established a baseline. Often this ID is calculated using a CRC
         algorithm.
         <DescriptiveName>Controller.databaseID:number
         <DataConceptType>Data Element"
      ::= { globalConfiguration 1}

globalSetIDParameter · optional

globalSetIDParameter OBJECT-TYPE
    SYNTAX INTEGER (0..65535)
    ACCESS read-only
    STATUS optional
    DESCRIPTION "Specifies a relatively unique ID for all user-changeable parameters of the particular
    device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm."
    ::= { globalConfiguration 1 }

globalSetIDParameter · deprecated

globalSetIDParameter OBJECT-TYPE
SYNTAX      Integer32 (0..65535)
MAX-ACCESS  read-only
STATUS      deprecated
DESCRIPTION 
"<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device.  Often this ID is calculated using a CRC algorithm. 
This value shall be calculated when a change of any parameter object has occurred.  The value reported by this object shall not change unless there has been a change in the static data since the last request.  If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages.
A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. 
<Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 20684-2)
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1"
::= { globalConfiguration 1}

dmsSignAccess · unconfirmed

dmsSignAccess  OBJECT-TYPE 
SYNTAX      NtcipIntegerBitmap8 
MAX-ACCESS  read-only 
STATUS      current 
DESCRIPTION  
"<Definition> Indicates the access method to the sign. Methods that are 
defined are:
<Format>
  Bit 0- Other 
  Bit 1- Walk-in access
  Bit 2- Rear access
  Bit 3- Front access
If a bit is set to one (1), then the associated feature exists; if the bit is 
set to zero (0), then the associated feature does not exist. 
<Parameter Type> Status
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.1" 
::= { dmsSignCfg 1 }

globalSetIDParameter · mandatory

globalSetIDParameter OBJECT-TYPE
SYNTAX	INTEGER (0..65535)
ACCESS	read-only
STATUS	mandatory
DESCRIPTION 
"<Definition>Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for current values stored in all user-changeable static database objects of the particular device-type currently implemented in the device.  This value shall be calculated on the change of any static database object.  The value reported by this object shall not change unless there has been a change in the static data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated.  A management station will be able to detect any change in the static database objects by monitoring this value after it has established a baseline. Often this ID is calculated using a CRC algorithm. 
<DescriptiveName>Controller.databaseID:number
<DataConceptType>Data Element"
::= { globalConfiguration 1}

globalSetIDParameter · mandatory

globalSetIDParameter OBJECT-TYPE
    SYNTAX   INTEGER (0..65535)
    ACCESS   read-only
    STATUS   mandatory
    DESCRIPTION
       "<Definition> Specifies a relatively unique ID (e.g., this could be a
       counter, a check-sum, etc.) for all user-changeable parameters of the
       particular device-type currently implemented in the device. Often this
       ID is calculated using a CRC algorithm.
       This value shall be calculated when a change of any static database
       object has occurred. The value reported by this object shall not change
       unless there has been a change in the static data since the last
       request. If the actual objects, which are to be included to create this
       object value, are not defined in the actual device-level standard such
       as 1202 or 1203, then the general guidance is to include all
       configuration objects that are stored in a type of memory that survives
       power outages.
       A management station can use this object to detect any change in the
       static database objects by monitoring this value after it has
       established a baseline.




                                                                                   

                                                                                    
                                                                                   

      <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1"
   ::= { globalConfiguration 1}

Meaning

Descriptions

7 unique

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

Description 1

<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. <Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition>Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for current values stored in all user-changeable static database objects of the particular device- type currently implemented in the device. This value shall be calculated on the change of any static database object. The value reported by this object shall not change unless there has been a change in the static data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated. A management station will be able to detect any change in the static database objects by monitoring this value after it has established a baseline. Often this ID is calculated using a CRC algorithm. <DescriptiveName>Controller.databaseID:number <DataConceptType>Data Element

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

Specifies a relatively unique ID for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 4

<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. <Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 20684-2) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 5

<Definition> Indicates the access method to the sign. Methods that are defined are: <Format> Bit 0- Other Bit 1- Walk-in access Bit 2- Rear access Bit 3- Front access If a bit is set to one (1), then the associated feature exists; if the bit is set to zero (0), then the associated feature does not exist. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.1

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 6

<Definition>Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for current values stored in all user-changeable static database objects of the particular device-type currently implemented in the device. This value shall be calculated on the change of any static database object. The value reported by this object shall not change unless there has been a change in the static data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated. A management station will be able to detect any change in the static database objects by monitoring this value after it has established a baseline. Often this ID is calculated using a CRC algorithm. <DescriptiveName>Controller.databaseID:number <DataConceptType>Data Element

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 7

<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any static database object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the static database objects by monitoring this value after it has established a baseline. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

7 records

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

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 1

globalSetIDParameter · unconfirmedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unconfirmed.

Names: globalSetIDParameter

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "globalSetIDParameter",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. <Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1\"",
    "::=",
    "{",
    "globalConfiguration",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. <Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

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

Status in source: mandatory.

Names: globalSetIDParameter

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "globalSetIDParameter",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for current values stored in all user-changeable static database objects of the particular device- type currently implemented in the device. This value shall be calculated on the change of any static database object. The value reported by this object shall not change unless there has been a change in the static data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated. A management station will be able to detect any change in the static database objects by monitoring this value after it has established a baseline. Often this ID is calculated using a CRC algorithm. <DescriptiveName>Controller.databaseID:number <DataConceptType>Data Element\"",
    "::=",
    "{",
    "globalConfiguration",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for current values stored in all user-changeable static database objects of the particular device- type currently implemented in the device. This value shall be calculated on the change of any static database object. The value reported by this object shall not change unless there has been a change in the static data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated. A management station will be able to detect any change in the static database objects by monitoring this value after it has established a baseline. Often this ID is calculated using a CRC algorithm. <DescriptiveName>Controller.databaseID:number <DataConceptType>Data Element"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

globalSetIDParameter · optionalNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: optional.

Names: globalSetIDParameter

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "globalSetIDParameter",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"Specifies a relatively unique ID for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm.\"",
    "::=",
    "{",
    "globalConfiguration",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "Specifies a relatively unique ID for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm."
    ],
    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 4ITE public NTCIP working repository MIBs1 record · 1 source

Description 4

globalSetIDParameter · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: globalSetIDParameter

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "globalSetIDParameter",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. <Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 20684-2) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1\"",
    "::=",
    "{",
    "globalConfiguration",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. <Superseded by> FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 20684-2) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 5ITE public NTCIP working repository MIBs1 record · 1 source

Description 5

dmsSignAccess · unconfirmedITE public NTCIP working repository MIBs1 source

Status in source: unconfirmed.

Names: dmsSignAccess

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsSignAccess",
    "OBJECT-TYPE",
    "SYNTAX",
    "NtcipIntegerBitmap8",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Indicates the access method to the sign. Methods that are defined are: <Format> Bit 0- Other Bit 1- Walk-in access Bit 2- Rear access Bit 3- Front access If a bit is set to one (1), then the associated feature exists; if the bit is set to zero (0), then the associated feature does not exist. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.1\"",
    "::=",
    "{",
    "dmsSignCfg",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "NtcipIntegerBitmap8"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Indicates the access method to the sign. Methods that are defined are: <Format> Bit 0- Other Bit 1- Walk-in access Bit 2- Rear access Bit 3- Front access If a bit is set to one (1), then the associated feature exists; if the bit is set to zero (0), then the associated feature does not exist. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.1"
    ],
    null,
    null,
    null,
    null
  ]
}
  • ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1203 — NTCIP1203-Dms.mib

    Module: NTCIP1203-Dms

    See published definition above

    Module imports
    {'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'StorageType', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'ISO26048-1-Srsa': ['fdSrsaTypeCode', 'fdSrsaPortIndex'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'ISO26048-1-Global-TC': ['ITSDirection', 'ITSInteger8', 'ITSLatitude84', 'ITSLongitude84', 'ITSBitmap'], 'TRANSPORT-ADDRESS-MIB': ['TransportAddressType', 'TransportAddress'], 'NTCIP8004-Transportation': ['NtcipOwnerString', 'NtcipIntegerBitmap8', 'NtcipIntegerBitmap16', 'NtcipTwoColors', 'devices']}

    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: Published module-root disagreement: dms has an SMI assignment resolving to 1.3.6.1.4.1.1206.4.2.6, while its DESCRIPTION explicitly prints 1.3.6.1.4.1.1206.4.2.3. All dependent assignments from this module require verification. No root number has been silently corrected.

    Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.6.1.1, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.1.1. 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 NTCIP-1203 — NTCIP1203-Dms.mib
Records for description 6ITE public NTCIP working repository MIBs1 record · 1 source

Description 6

globalSetIDParameter · mandatoryITE public NTCIP working repository MIBs1 source

Status in source: mandatory.

Names: globalSetIDParameter

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "globalSetIDParameter",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for current values stored in all user-changeable static database objects of the particular device-type currently implemented in the device. This value shall be calculated on the change of any static database object. The value reported by this object shall not change unless there has been a change in the static data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated. A management station will be able to detect any change in the static database objects by monitoring this value after it has established a baseline. Often this ID is calculated using a CRC algorithm. <DescriptiveName>Controller.databaseID:number <DataConceptType>Data Element\"",
    "::=",
    "{",
    "globalConfiguration",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for current values stored in all user-changeable static database objects of the particular device-type currently implemented in the device. This value shall be calculated on the change of any static database object. The value reported by this object shall not change unless there has been a change in the static data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated. A management station will be able to detect any change in the static database objects by monitoring this value after it has established a baseline. Often this ID is calculated using a CRC algorithm. <DescriptiveName>Controller.databaseID:number <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
Records for description 7NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 7

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

Status in source: mandatory.

Names: globalSetIDParameter

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "globalSetIDParameter",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any static database object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the static database objects by monitoring this value after it has established a baseline. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1\"",
    "::=",
    "{",
    "globalConfiguration",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any static database object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the static database objects by monitoring this value after it has established a baseline. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.1"
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201 v03.15 — Global Object (GO) Definitions, published March 2011 — original PDF · Official record

    Module: NTCIP1201-v03

    See published definition above

    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['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: 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 NTCIP1201v0315r.pdf — NTCIP1201-v03 (MIB transcription)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.1.2 globalMaxModules, dmsSignType00
1.3.6.1.4.1.1206.4.2.6.1.3 globalModuleTable, moduleTable, dmsSignHeight17
1.3.6.1.4.1.1206.4.2.6.1.4 controllerBaseStandards, dmsSignWidth00
1.3.6.1.4.1.1206.4.2.6.1.5 dmsHorizontalBorder00
1.3.6.1.4.1.1206.4.2.6.1.6 dmsVerticalBorder00
1.3.6.1.4.1.1206.4.2.6.1.7 dmsLegend00
1.3.6.1.4.1.1206.4.2.6.1.8 dmsBeaconType00
1.3.6.1.4.1.1206.4.2.6.1.9 dmsSignTechnology00
1.3.6.1.4.1.1206.4.2.6.1.10 dmsDisplayLatitude00
1.3.6.1.4.1.1206.4.2.6.1.11 dmsDisplayLongitude00
1.3.6.1.4.1.1206.4.2.6.1.12 dmsDisplayDirection00
1.3.6.1.4.1.1206.4.2.6.1.13 dmsDisplayOffsetLatitude00
1.3.6.1.4.1.1206.4.2.6.1.14 dmsDisplayOffsetLongitude00
1.3.6.1.4.1.1206.4.2.6.1.15 dmsBeacon524