OID reference

alarmGroupEntry

1.3.6.1.4.1.1206.4.2.1.3.12.1

Description

Status for eight alarm inputs.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.1.3.12 (alarmGroupTable)
Node code: 1
Node name: alarmGroupEntry
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.1.3.12.1
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.1.3.12.1

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) unit(3) alarmGroupTable(12) alarmGroupEntry(1)}

OID-IRI notation

/1/3/6/1/4/1/1206/4/2/1/3/12/1
/ISO/Identified-Organization/6/1/4/1/1206/4/2/1/3/12/1
/ISO/3/6/1/4/1/1206/4/2/1/3/12/1

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/asc/unit/alarmGroupTable/alarmGroupEntry
Additional combinations skipped.

SNMP properties

Value type: AlarmGroupEntry
Maximum access defined by MIB: not-accessible
Status in MIB: mandatory, optional

Definitions may combine these properties differently.

Compare 2 source variants

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

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

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

Value type: AlarmGroupEntry
Maximum access defined by MIB: not-accessible
Status in MIB: optional

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

Show 4 published definitions

alarmGroupEntry · mandatory

alarmGroupEntry OBJECT-TYPE
          SYNTAX AlarmGroupEntry
          ACCESS not-accessible
          STATUS mandatory
          DESCRIPTION
              "Status for eight alarm inputs."
          INDEX { alarmGroupNumber }
::= { alarmGroupTable 1 }

alarmGroupEntry · optional

alarmGroupEntry   OBJECT-TYPE
   SYNTAX   AlarmGroupEntry
   ACCESS   not-accessible
   STATUS   optional
   DESCRIPTION
      "<Definition> Status for eight alarm inputs.
       <DescriptiveName> NTCIP-1202::ASC.alarmGroupEntry
       <DataConceptType> Entity Type"
   INDEX { alarmGroupNumber }
::= { alarmGroupTable 1 }

alarmGroupEntry · mandatory

alarmGroupEntry   OBJECT-TYPE
      SYNTAX AlarmGroupEntry
      ACCESS not-accessible
      STATUS mandatory
      DESCRIPTION "<Definition> Status for eight alarm inputs.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.12.1"
      INDEX { alarmGroupNumber }
::= { alarmGroupTable 1 }

alarmGroupEntry · mandatory

alarmGroupEntry   OBJECT-TYPE
      SYNTAX AlarmGroupEntry
      ACCESS not-accessible
      STATUS mandatory
      DESCRIPTION "<Definition> Status for eight alarm inputs.


                                                                                        

                                                                                     
                                                                                    

      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.12.1"
      INDEX { alarmGroupNumber }
::= { alarmGroupTable 1 }

Meaning

Descriptions

3 unique

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

Description 1

Status for eight alarm inputs.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> Status for eight alarm inputs. <DescriptiveName> NTCIP-1202::ASC.alarmGroupEntry <DataConceptType> Entity Type

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition> Status for eight alarm inputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.12.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

3 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

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

Status in source: mandatory.

Names: alarmGroupEntry

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "alarmGroupEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "AlarmGroupEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Status for eight alarm inputs.\"",
    "INDEX",
    "{",
    "alarmGroupNumber",
    "}",
    "::=",
    "{",
    "alarmGroupTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "AlarmGroupEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Status for eight alarm inputs."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "alarmGroupNumber"
        ]
      ]
    ],
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v01, Object Definitions for Actuated Traffic Signal Controller (ASC) Units) Published January 2005 (superceded by NTCIP 1202 v02) — original PDF · Official record
Module: ASC_MIB1

See published definition above
Module imports
```
{'TMIB': ['devices']}
```
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: TMIB. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1202v0107d.pdf — ASC_MIB1 (MIB transcription)
Related source files and packages:
Show more related files and packages
- NTCIP8004-NEMA.mib — ITE namespace dependency
- NTCIP8004-Transportation.mib — ITE namespace dependency

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

Description 2

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

Status in source: optional.

Names: alarmGroupEntry

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "alarmGroupEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "AlarmGroupEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"<Definition> Status for eight alarm inputs. <DescriptiveName> NTCIP-1202::ASC.alarmGroupEntry <DataConceptType> Entity Type\"",
    "INDEX",
    "{",
    "alarmGroupNumber",
    "}",
    "::=",
    "{",
    "alarmGroupTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "AlarmGroupEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "<Definition> Status for eight alarm inputs. <DescriptiveName> NTCIP-1202::ASC.alarmGroupEntry <DataConceptType> Entity Type"
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "alarmGroupNumber"
        ]
      ]
    ],
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 02 Published November 2005 — original PDF · Official record
Module: NTCIP1202-200x

See published definition above
Module imports
```
{'TMIB-II': ['OwnerString', 'devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}
```
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: TMIB-II. 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 NTCIP1202v0219f.pdf — NTCIP1202-200x (MIB transcription)
Related source files and packages:
- NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 02 Published November 2005 — original PDF

Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 3

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

Status in source: mandatory.

Names: alarmGroupEntry

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "alarmGroupEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "AlarmGroupEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> Status for eight alarm inputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.12.1\"",
    "INDEX",
    "{",
    "alarmGroupNumber",
    "}",
    "::=",
    "{",
    "alarmGroupTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "AlarmGroupEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> Status for eight alarm inputs. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.3.12.1"
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "alarmGroupNumber"
        ]
      ]
    ],
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — original PDF · Official record
Module: NTCIP1202-v03

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}
```
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 NTCIP-1202v03.35e-aspublished.pdf — NTCIP1202-v03 (MIB transcription)
Related source files and packages:
- NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — original PDF
NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF · Official record
Module: NTCIP1202-v03

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}
```
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 NTCIP-1202v0328A.pdf — NTCIP1202-v03 (MIB transcription)
Related source files and packages:
- NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (2)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.1.3.12.1.1	alarmGroupNumber	0	0
1.3.6.1.4.1.1206.4.2.1.3.12.1.2	alarmGroupState	0	0