OID reference

maxRings

1.3.6.1.4.1.1206.4.2.1.7.1

Description

The value of this object shall specify the maximum number of rings this device supports.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.1.7 (ring)
Node code: 1
Node name: maxRings
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.1.7.1
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.1.7.1

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ring(7) maxRings(1)}

OID-IRI notation

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

Named path variants

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

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-only
Status in MIB: mandatory, optional

Definitions may combine these properties differently.

Compare 3 source variants

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

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

Variant 2 — 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

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: 1–255

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.1.7.1.0

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.

Published definitions

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

Show 4 published definitions

maxRings · mandatory

maxRings OBJECT-TYPE
          SYNTAX INTEGER (0..255)
          ACCESS read-only
          STATUS mandatory
          DESCRIPTION
               "The value of this object shall specify the maximum number of rings this device supports."
::= { ring 1 }

maxRings · mandatory

maxRings   OBJECT-TYPE
      SYNTAX INTEGER (1..255)
      ACCESS read-only
      STATUS mandatory
      DESCRIPTION "<Definition> The value of this object shall specify the
            maximum number of rings this device supports.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1
      <Unit> ring"
::= { ring 1 }

maxRings · mandatory

maxRings   OBJECT-TYPE
      SYNTAX INTEGER (1..255)
      ACCESS read-only
      STATUS mandatory
      DESCRIPTION "<Definition> The value of this object shall specify the
            maximum number of rings this device supports.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1
      <Object Type> S
      <Unit> ring"
::= { ring 1 }

maxRings · optional

maxRings   OBJECT-TYPE
   SYNTAX   INTEGER (1..255)
   ACCESS   read-only
   STATUS   optional
   DESCRIPTION
      "<Definition> The value of this object shall specify
       the maximum number of rings this device supports.
       <DescriptiveName> NTCIP-1202::ASC.maxRings
       <DataConceptType> Data Element
       <Unit> ring"
::= { ring 1 }

Meaning

Descriptions

4 unique

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

Description 1

The value of this object shall specify the maximum number of rings this device supports.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> The value of this object shall specify the maximum number of rings this device supports. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1 <Unit> ring

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition> The value of this object shall specify the maximum number of rings this device supports. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1 <Object Type> S <Unit> ring

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 4

<Definition> The value of this object shall specify the maximum number of rings this device supports. <DescriptiveName> NTCIP-1202::ASC.maxRings <DataConceptType> Data Element <Unit> ring

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

4 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

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

Status in source: mandatory.

Names: maxRings

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxRings",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The value of this object shall specify the maximum number of rings this device supports.\"",
    "::=",
    "{",
    "ring",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The value of this object shall specify the maximum number of rings this device supports."
    ],
    null,
    null,
    null,
    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

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

Status in source: mandatory.

Names: maxRings

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxRings",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> The value of this object shall specify the maximum number of rings this device supports. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1 <Unit> ring\"",
    "::=",
    "{",
    "ring",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> The value of this object shall specify the maximum number of rings this device supports. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1 <Unit> ring"
    ],
    null,
    null,
    null,
    null
  ]
}

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

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

Description 3

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

Status in source: mandatory.

Names: maxRings

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxRings",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> The value of this object shall specify the maximum number of rings this device supports. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1 <Object Type> S <Unit> ring\"",
    "::=",
    "{",
    "ring",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> The value of this object shall specify the maximum number of rings this device supports. <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.1 <Object Type> S <Unit> ring"
    ],
    null,
    null,
    null,
    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

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

Description 4

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

Status in source: optional.

Names: maxRings

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxRings",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"<Definition> The value of this object shall specify the maximum number of rings this device supports. <DescriptiveName> NTCIP-1202::ASC.maxRings <DataConceptType> Data Element <Unit> ring\"",
    "::=",
    "{",
    "ring",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "<Definition> The value of this object shall specify the maximum number of rings this device supports. <DescriptiveName> NTCIP-1202::ASC.maxRings <DataConceptType> Data Element <Unit> ring"
    ],
    null,
    null,
    null,
    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

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (5)

OID	Name	Direct children	Descendants
1.3.6.1.4.1.1206.4.2.1.7.2	maxSequences	0	0
1.3.6.1.4.1.1206.4.2.1.7.3	sequenceTable	1	4
1.3.6.1.4.1.1206.4.2.1.7.4	maxRingControlGroups	0	0
1.3.6.1.4.1.1206.4.2.1.7.5	ringControlGroupTable	1	10
1.3.6.1.4.1.1206.4.2.1.7.6	ringStatusTable	1	2