OID reference

dynamicObjectPersistence

1.3.6.1.4.1.1206.4.1.2.2.1

Description

<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definintions shall be invalidated on device power up. If this object is set to its maximum value (65535) then …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.1.2.2 (profilesSTMP, profilesPMPP)
Node code
1
Node names
  • dynamicObjectPersistence
  • maxGroupAddresses
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.1.2.2.1
URN notation
urn:oid:1.3.6.1.4.1.1206.4.1.2.2.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) maxGroupAddresses(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) maxGroupAddresses(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) maxGroupAddresses(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) maxGroupAddresses(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) maxGroupAddresses(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) maxGroupAddresses(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesSTMP(2) maxGroupAddresses(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) dynamicObjectPersistence(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) protocols(1) profiles(2) profilesPMPP(2) maxGroupAddresses(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/1/2/2/1
  • /ISO/Identified-Organization/6/1/4/1/1206/4/1/2/2/1
  • /ISO/3/6/1/4/1/1206/4/1/2/2/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/profiles/profilesSTMP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/profiles/profilesSTMP/maxGroupAddresses
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/profiles/profilesPMPP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/protocols/profiles/profilesPMPP/maxGroupAddresses
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/profiles/profilesSTMP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/profiles/profilesSTMP/maxGroupAddresses
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/profiles/profilesPMPP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/Protocols/profiles/profilesPMPP/maxGroupAddresses
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/profiles/profilesSTMP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/profiles/profilesSTMP/maxGroupAddresses
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/profiles/profilesPMPP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/protocols/profiles/profilesPMPP/maxGroupAddresses
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/profiles/profilesSTMP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/profiles/profilesSTMP/maxGroupAddresses
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/profiles/profilesPMPP/dynamicObjectPersistence
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/Protocols/profiles/profilesPMPP/maxGroupAddresses
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER, Integer32
Units
minutes
Maximum access defined by MIB
read-write, read-only
Status in MIB
mandatory, deprecated
Default value
65535

Definitions may combine these properties differently.

Compare 4 source variants

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

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

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

Value type
Integer32
Units
minutes
Maximum access defined by MIB
read-write
Status in MIB
deprecated
Default value
65535
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
mandatory
Allowed ranges
1–255

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

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

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.1.2.2.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.

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

Show 7 published definitions

dynamicObjectPersistence · mandatory

dynamicObjectPersistence OBJECT-TYPE
    SYNTAX INTEGER (0..65535)
    ACCESS read-write
    STATUS mandatory
    DESCRIPTION
        "<Definition> The maximum power outage time in minutes that
          may occur before all STMP dynamic object definitions in a
          device shall be invalidated. If this object is set to zero
          then the existing dynamic object definintions shall be
          invalidated on device power up. If this object is set to
          its maximum value (65535) then the existing dynamic object
          definitions shall nominally persist for an infinite period
          (in practice this will be limited by the non-volatile memory
          capabilities of the device) This object shall not be
          invalidated due to power outages of any duration. A device
          that supports STMP dynamic objects shall support this object.
         <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1
         "
    DEFVAL {65535}
::= { profilesSTMP 1 }

dynamicObjectPersistence · deprecated

dynamicObjectPersistence  OBJECT-TYPE
  SYNTAX      Integer32 (0..65535)
  UNITS       "minutes"
  MAX-ACCESS  read-write
  STATUS      deprecated
  DESCRIPTION
      "<Definition> The maximum power outage time in minutes that 
        may occur before all STMP dynamic object definitions in a 
        device shall be invalidated. If this object is set to zero 
        then the existing dynamic object definitions shall be 
        invalidated on device power up. If this object is set to 
        its maximum value (65535), then the existing dynamic object 
        definitions shall nominally persist for an infinite period 
        (in practice this is limited by the non-volatile memory 
        capabilities of the device).  This object shall not be 
        invalidated due to power outages of any duration. A device 
        that supports STMP dynamic objects shall support this object. 
       <Informative> This object has been deprecated along with STMP.
       <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1"
   DEFVAL {65535}
::= { profilesSTMP 1 }

dynamicObjectPersistence · mandatory

dynamicObjectPersistence OBJECT-TYPE
     SYNTAX     INTEGER (0..65535)
     ACCESS     read-write
     STATUS     mandatory
     DESCRIPTION
          "The maximum power outage time in minutes that may occur before all
          STMP dynamic object definitions in a device shall be invalidated. If
          this object is set to zero then existing dynamic object definitions
          shall be invalidated on device power up. If this object is set to its
          maximum value (65535) the existing dynamic object definitions shall
          nominally persist for an infinite period (in practice this will be
limited
          by the non-volatile memory capabilities of the device)
          This object shall not be invalidated due to power outages of any
          duration. A device that supports STMP dynamic objects
          shall support this object."
     DEFVAL {65535}
     ::= { profilesSTMP 1 }

dynamicObjectPersistence · mandatory

dynamicObjectPersistence OBJECT-TYPE
   SYNTAX INTEGER (0..65535)
   ACCESS read-write
   STATUS mandatory
   DESCRIPTION
      "<Definition> The maximum power outage time in minutes that
        may occur before all STMP dynamic object definitions in a
        device shall be invalidated. If this object is set to zero
        then the existing dynamic object definintions shall be
        invalidated on device power up. If this object is set to
        its maximum value (65535), then the existing dynamic object
        definitions shall nominally persist for an infinite period
        (in practice this is limited by the non-volatile memory
        capabilities of the device). This object shall not be
        invalidated due to power outages of any duration. A device
        that supports STMP dynamic objects shall support this object.
       <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1


                                                                                         

                 
       

       "
   DEFVAL {65535}
::= { profilesSTMP 1 }

maxGroupAddresses · unconfirmed

maxGroupAddresses OBJECT-TYPE
SYNTAX      INTEGER (1..255)
ACCESS      read-only
STATUS      mandatory
DESCRIPTION
      "<Definition>The maximum number of group addresses this device
      supports. This object indicates the maximum number of rows in the
      hdlcGroupAddressTable.
      <Unit>address
      <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.3.1"
::= {profilesPMPP 1 }

dynamicObjectPersistence · mandatory

dynamicObjectPersistence OBJECT-TYPE
SYNTAX             INTEGER (0..65535)
ACCESS             read-write
STATUS             mandatory
DESCRIPTION
"The maximum power outage time in minutes that may occur before all STMP dynamic object definitions
in a device shall be invalidated.
If this object is set to zero then existing dynamic object definitions shall be invalidated on device power
up.
If this object is set to its maximum value (65535) the existing dynamic object definitions shall not be
invalidated due to power outages of any duration.

A device that supports STMP dynamic objects shall support this object."
REFERENCE
"NEMA TS 3.2 Clause 4.2.1.1"
::= { profilesSTMP 1 }

dynamicObjectPersistence · deprecated

dynamicObjectPersistence OBJECT-TYPE
SYNTAX      Integer32 (0..65535)
UNITS       "minutes"
MAX-ACCESS read-write
STATUS      deprecated
DESCRIPTION
   "<Definition> The maximum power outage time in minutes that may occur
   before all STMP dynamic object definitions in a device shall be
   invalidated. If this object is set to zero then the existing dynamic object
   definitions shall be invalidated on device power up. If this object is set
   to its maximum value (65535), then the existing dynamic object definitions
   shall nominally persist for an infinite period (in practice this is limited
   by the non-volatile memory capabilities of the device). This object shall
   not be invalidated due to power outages of any duration. A device that
   supports STMP dynamic objects shall support this object.
  <Supplanted by> ISO26048-1-DynObj.fdOwnerDynObjPersistence
  <Informative> This object has been deprecated along with STMP.
  <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1"
DEFVAL     { 65535 }
::= { profilesSTMP 1 }

Meaning

Descriptions

7 unique

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

Description 1

<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definintions shall be invalidated on device power up. If this object is set to its maximum value (65535) then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this will be limited by the non-volatile memory capabilities of the device) This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 3

The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535) the existing dynamic object definitions shall nominally persist for an infinite period (in practice this will be limited by the non-volatile memory capabilities of the device) This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 4

<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definintions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 5

<Definition>The maximum number of group addresses this device supports. This object indicates the maximum number of rows in the hdlcGroupAddressTable. <Unit>address <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.3.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 6

The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535) the existing dynamic object definitions shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 7

<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Supplanted by> ISO26048-1-DynObj.fdOwnerDynObjPersistence <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.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

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

Status in source: mandatory.

Names: dynamicObjectPersistence

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynamicObjectPersistence",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definintions shall be invalidated on device power up. If this object is set to its maximum value (65535) then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this will be limited by the non-volatile memory capabilities of the device) This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1 \"",
    "DEFVAL",
    "{",
    "65535",
    "}",
    "::=",
    "{",
    "profilesSTMP",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definintions shall be invalidated on device power up. If this object is set to its maximum value (65535) then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this will be limited by the non-volatile memory capabilities of the device) This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      65535
    ]
  ]
}
Records for description 2ITE public NTCIP working repository MIBs1 record · 1 source

Description 2

dynamicObjectPersistence · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: dynamicObjectPersistence

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynamicObjectPersistence",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "UNITS",
    [
      "literal",
      "226d696e7574657322"
    ],
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1\"",
    "DEFVAL",
    "{",
    "65535",
    "}",
    "::=",
    "{",
    "profilesSTMP",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "minutes"
    ],
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      65535
    ]
  ]
}
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

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

Status in source: mandatory.

Names: dynamicObjectPersistence

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynamicObjectPersistence",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535) the existing dynamic object definitions shall nominally persist for an infinite period (in practice this will be limited by the non-volatile memory capabilities of the device) This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object.\"",
    "DEFVAL",
    "{",
    "65535",
    "}",
    "::=",
    "{",
    "profilesSTMP",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535) the existing dynamic object definitions shall nominally persist for an infinite period (in practice this will be limited by the non-volatile memory capabilities of the device) This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      65535
    ]
  ]
}
Records for description 4NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 4

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

Status in source: mandatory.

Names: dynamicObjectPersistence

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynamicObjectPersistence",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definintions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1 \"",
    "DEFVAL",
    "{",
    "65535",
    "}",
    "::=",
    "{",
    "profilesSTMP",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definintions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      65535
    ]
  ]
}
Records for description 5NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 5

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

Status in source: unconfirmed.

Names: maxGroupAddresses

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxGroupAddresses",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The maximum number of group addresses this device supports. This object indicates the maximum number of rows in the hdlcGroupAddressTable. <Unit>address <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.3.1\"",
    "::=",
    "{",
    "profilesPMPP",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The maximum number of group addresses this device supports. This object indicates the maximum number of rows in the hdlcGroupAddressTable. <Unit>address <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.3.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.

    Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.1.2.2.1, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.1.2.3.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 NTCIP1201v0315r.pdf — NTCIP1201-v03 (MIB transcription)
Records for description 6NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 6

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

Status in source: mandatory.

Names: dynamicObjectPersistence

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynamicObjectPersistence",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535) the existing dynamic object definitions shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object.\"",
    "REFERENCE",
    "\"NEMA TS 3.2 Clause 4.2.1.1\"",
    "::=",
    "{",
    "profilesSTMP",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535) the existing dynamic object definitions shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object."
    ],
    [
      "REFERENCE",
      "NEMA TS 3.2 Clause 4.2.1.1"
    ],
    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 7NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 7

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

Status in source: deprecated.

Names: dynamicObjectPersistence

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dynamicObjectPersistence",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "UNITS",
    [
      "literal",
      "226d696e7574657322"
    ],
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Supplanted by> ISO26048-1-DynObj.fdOwnerDynObjPersistence <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1\"",
    "DEFVAL",
    "{",
    "65535",
    "}",
    "::=",
    "{",
    "profilesSTMP",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "minutes"
    ],
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. <Supplanted by> ISO26048-1-DynObj.fdOwnerDynObjPersistence <Informative> This object has been deprecated along with STMP. <Object Identifier> 1.3.6.1.4.1.1206.4.1.2.2.1"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      65535
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.1.2.2.2 dynamicObjectTableConfigID, hdlcGroupAddressTable, dynamicObjectTable-ConfigID14
1.3.6.1.4.1.1206.4.1.2.2.127 profilesSTMPConformance23